Occasionally, the CRBasic Editor compiler states that a program compiles OK; however, the
program may not compile in the data logger itself. This is rare, but reasons may include:
l
The data logger has a different operating system than the computer compiler. Check the
two versions if in doubt. The computer compiler version is shown on the first line of the
compile results. Update the computer compiler by first downloading the executable OS file
from
. When run, the executable file updates the computer compiler.
To update the data logger operating system, see
l
The program has large memory requirements for data tables or variables and the data
logger does not have adequate memory. This normally is flagged at compile time in the
compile results. If this type of error occurs:
o
Check the CPU drive for copies of old programs. The data logger keeps copies of all
program files unless they are deleted, the drive is formatted, or a new operating
system is loaded with Device Configuration Utility.
o
Check the USR drive size. If it is too large it may be using memory needed for the
program.
o
Ensure a memory card is available when a program is attempting to access the CRD
drive.
9.4.2 Program compiles but does not run correctly
If the program compiles but does not run correctly, timing discrepancies may be the cause. If a
program is tight on time, look further at the execution times. Check the measurement and
processing times in the Status table (MeasureTime, ProcessTime, MaxProcTime) for all scans, then
try experimenting with the
InstructionTimes()
instruction in the program. Analyzing
InstructionTimes()
results can be difficult due to the multitasking nature of the data
logger, but it can be a useful tool for fine-tuning a program. For more information, see
Information tables and settings (advanced)
See the CRBasic Editor help for detailed instruction information and program examples:
https://help.campbellsci.com/crbasic/cr6/.
9.5 Troubleshooting Radio Communications
If there are intermittent communication problems when connecting via radio, there may be
another network in the area causing interference. To help remove the interference, use Device
Configuration Utility to change the Network ID and RF Hop Sequence in all RF407, RF412, and
RF422 radios within a network (standalone or included in a data logger) to another value. Each
of these settings must have the same value in all radios and dataloggers within a network. For
9. Tips and troubleshooting
134
