Software Bugs
Version 3: Old Digital Board with 500K/Sys disk
OPEN 3.4
AutoProgram Builder errors out (PICK out of range) - fixed in 3.4.3, 4.0, and 5.0
Quantum tracking doesn't turn lamp back on - fixed in 3.4.2 and 4.0
Not computing after autoprompting for user constants - fixed in 3.4.2
Error in soil flux computations - fixed in 3.4.3
OPEN 3.4.2
AutoProgram Builder errors out (PICK out of range) - fixed in 3.4.3, 4.0, and 5.0
Error in soil flux computations - fixed in 3.4.3
OPEN 3.4.3
<none reported>
Version 4: Old Digital Board with 2 MB/Sys disk
OPEN 4.01
Not computing after autoprompting for user constants - fixed in 4.02
Error in soil flux computations - fixed in 4.03
LCF quantum tracking mode can't be turned off without changing modes first (Fixed in 4.04)
Crashes when pgdn pressed in new measurements when configured for soil respiration (Fixed in 4.04)
OPEN 4.02
Error in soil flux computations - fixed in 4.03
LCF quantum tracking mode can't be turned off without changing modes first (Fixed in 4.04)
Crashes when pgdn pressed in new measurements when configured for soil respiration (Fixed in 4.04)
OPEN 4.03
LCF quantum tracking mode can't be turned off without changing modes first (Fixed in 4.04)
Crashes when pgdn pressed in new measurements when configured for soil respiration (Fixed in 4.04)
ParIn zeroing routine doesn't make sure LCF is on first. (Fixed in 4.04 and 5.1)
OPEN 4.04
Picking an item off the end of the list in a control panel (flow, CO2, temp, or light) will crash the program - fixed in 4.06
Tracking ambient light with the LCF through zero can leave percent blue too high, and response sluggish, as the target increases - fixed in 5.2, but no fix in 4.x
Autoprograms build with the AutoProgram Builder that use "Wait, with logging at intervals", have a chance of waiting forever - fixed in 4.06
alphaK and actinity factors (used with quantum sensor for energy balance and correction for alternative light sources) are not initialized correctly - fixed in 4.06
Version 5: New Digital Board (64 MB)
OPEN 5.0
Not computing after autoprompting for user constants - fixed in 5.0.1
Error in soil flux computations - fixed in 5.0.2
LCF quantum tracking mode can't be turned off without changing modes first - fixed in 5.0.4
Computations not done after manually logged LCF event - fixed in 5.0.4
/User disk may not have been initialized correctly. /Sys and /User show same size. - fixed in 5.0.4
ParIn zeroing routine doesn't make sure LCF is on first. (Fixed in 4.04 and 5.1)
Error when trying to graph from the Filer, if OPEN not running. (Fixed in 5.1)
Several problems when storing configuration related files. (Fixed in 5.1)
Error when defining log button to "Flash (no assign)" or "Dark (no assign)". (Fixed in 5.1)
Control Panel utility won't run on top of OPEN. (Fixed in 5.1)
When using the 6400-40 as a light source only (an option available in Light Source Control in the Config Menu), the par readings may be 5X too low.
Workaround: Go to Welcome Menu->Diagnostics and Test Menu->LCF Control Panel. Press right arrow twice to move to "PdGain" field. If the value is 1, press up arrow to change it to 5. (Fixed in 5.3.1)
OPEN 5.0.1
Error in soil flux computations - fixed in 5.0.2
LCF quantum tracking mode can't be turned off without changing modes first - fixed in 5.0.4
Computations not done after manually logged LCF event - fixed in 5.0.4
/User disk may not have been initialized correctly. /Sys and /User show same size. - fixed in 5.0.4
ParIn zeroing routine doesn't make sure LCF is on first. (Fixed in 4.04 and 5.1)
Error when trying to graph from the Filer, if OPEN not running. (Fixed in 5.1)
Several problems when storing configuration related files. (Fixed in 5.1)
Error when defining log button to "Flash (no assign)" or "Dark (no assign)". (Fixed in 5.1)
Control Panel utility won't run on top of OPEN. (Fixed in 5.1)
When using the 6400-40 as a light source only (an option available in Light Source Control in the Config Menu), the par readings may be 5X too low.
Workaround: Go to Welcome Menu->Diagnostics and Test Menu->LCF Control Panel. Press right arrow twice to move to "PdGain" field. If the value is 1, press up arrow to change it to 5. (Fixed in 5.3.1)
OPEN 5.0.2
Soil chamber installation errors. Fixed in 5.0.3
LCF quantum tracking mode can't be turned off without changing modes first - fixed in 5.0.4
Computations not done after manually logged LCF event - fixed in 5.0.4
/User disk may not have been initialized correctly. /Sys and /User show same size. - fixed in 5.0.4
ParIn zeroing routine doesn't make sure LCF is on first. (Fixed in 4.04 and 5.1)
Error when trying to graph from the Filer, if OPEN not running. (Fixed in 5.1)
Several problems when storing configuration related files. (Fixed in 5.1)
Error when defining log button to "Flash (no assign)" or "Dark (no assign)". (Fixed in 5.1)
Control Panel utility won't run on top of OPEN. (Fixed in 5.1)
When using the 6400-40 as a light source only (an option available in Light Source Control in the Config Menu), the par readings may be 5X too low.
Workaround: Go to Welcome Menu->Diagnostics and Test Menu->LCF Control Panel. Press right arrow twice to move to "PdGain" field. If the value is 1, press up arrow to change it to 5. (Fixed in 5.3.1)
OPEN 5.0.3
LCF quantum tracking mode can't be turned off - fixed in 5.0.4
Computations not done after manually logged LCF event - fixed in 5.0.4
/User disk may not have been initialized correctly. /Sys and /User show same size. - fixed in 5.0.4
ParIn zeroing routine doesn't make sure LCF is on first. (Fixed in 4.04 and 5.1)
Several problems when storing configuration related files. (Fixed in 5.1)
Error when trying to graph from the Filer, if OPEN not running. (Fixed in 5.1)
Error when defining log button to "Flash (no assign)" or "Dark (no assign)". (Fixed in 5.1)
Control Panel utility won't run on top of OPEN. (Fixed in 5.1)
When using the 6400-40 as a light source only (an option available in Light Source Control in the Config Menu), the par readings may be 5X too low.
Workaround: Go to Welcome Menu->Diagnostics and Test Menu->LCF Control Panel. Press right arrow twice to move to "PdGain" field. If the value is 1, press up arrow to change it to 5. (Fixed in 5.3.1)
OPEN 5.0.4
ParIn zeroing routine doesn't make sure LCF is on first. (Fixed in 4.04 and 5.1)
Error when trying to graph from the Filer, if OPEN not running. (Fixed in 5.1)
Several problems when storing configuration related files. (Fixed in 5.1)
Error when defining log button to "Flash (no assign)" or "Dark (no assign)". (Fixed in 5.1)
Control Panel utility won't run on top of OPEN. (Fixed in 5.1)
When using the 6400-40 as a light source only (an option available in Light Source Control in the Config Menu), the par readings may be 5X too low.
Workaround: Go to Welcome Menu->Diagnostics and Test Menu->LCF Control Panel. Press right arrow twice to move to "PdGain" field. If the value is 1, press up arrow to change it to 5. (Fixed in 5.3.1)
OPEN 5.1
CO2R value wrong in diagnostic display 'C' - fixed in 5.2
Autoprograms build with the AutoProgram Builder that use "Wait, with logging at intervals", have a chance of waiting forever - fixed in 5.2
Response time to keystrokes gets sluggish, and environmental control degrades with logging very large data files - fixed in 5.2
Soil respiration: only logs 30 seconds of data per observation - fixed in 5.2
Installing an energy balance Tleaf for the LCF causes "file not found" error - fixed in 5.2
Tracking ambient light with the LCF through zero can leave percent blue too high, and response sluggish, as the target increases - fixed in 5.2
Some units built after Nov 2003 show memory 50% used with it is only 2% - fixed in 5.2
Picking an item off the end of the list in a control panel (flow, CO2, temp, or light) will crash the program - fixed in 5.3
alphaK and actinity factors(used with quantum sensor for energy balance and correction for alternative light sources) are not initialized correctly - fixed in 5.3
When using the 6400-40 as a light source only (an option available in Light Source Control in the Config Menu), the par readings may be 5X too low.
Workaround: Go to Welcome Menu->Diagnostics and Test Menu->LCF Control Panel. Press right arrow twice to move to "PdGain" field. If the value is 1, press up arrow to change it to 5. (Fixed in 5.3.1)
OPEN 5.2
Changing light source while configured for LCF causes crash when New Measurements re-entered - fixed in 5.3
FQuantum (lamp control in LCF) leaves blue unchanged when total drops below blue target - fixed in 5.3
alphaK and actinity factors(used with quantum sensor for energy balance and correction for alternative light sources) are not initialized correctly - fixed in 5.3
Crashes when entering New Measurements when configured for LCF, after recomputing a non-LCFdata file - fixed in 5.3
When using the 6400-40 as a light source only (an option available in Light Source Control in the Config Menu), the par readings may be 5X too low.
Workaround: Go to Welcome Menu->Diagnostics and Test Menu->LCF Control Panel. Press right arrow twice to move to "PdGain" field. If the value is 1, press up arrow to change it to 5. (Fixed in 5.3.1)
OPEN 5.3
User defined constants in compute lists that are defined by UCON are initialized to integer values, not floating point in version 5.3. This affects the 6400-40 fluorometer configuration, which has three constants thusly defined: red absorption (0.85), blue absorption (0.85), and photosynthesis distribution factor (0.5), which all are initialized to 0.
Workaround: Press PromptAll in New Measurements to define these constants. (Fixed in 5.3.1)
When using the 6400-40 as a light source only (an option available in Light Source Control in the Config Menu), the par readings may be 5X too low.
Workaround: Go to Welcome Menu->Diagnostics and Test Menu->LCF Control Panel. Press right arrow twice to move to "PdGain" field. If the value is 1, press up arrow to change it to 5. (Fixed in 5.3.1)
