Section 10. Troubleshooting
10.5.4.1 CompileResults
CompileResults reports messages generated by the CR800 at program upload and
compile-time. Messages may also added as the program runs. Error messages
may not be obvious because the display is limited. Much of this information is
more easily accessed through the datalogger support software
(p. 86) station status
report. The message reports the following:
• program compiled OK
• warnings about possible problems
• run-time errors
• variables that caused out-of-bounds conditions
• watchdog information
• memory errors
Warning messages are posted by the CRBasic compiler to advise that some
expected feature may not work. Warnings are different from error messages in
that the program will still operate when a warning condition is identified.
A rare error is indicated by mem3 fail type messages. These messages can be
caused by random internal memory corruption. When seen on a regular basis with
a given program, an operating system error is indicated. Mem3 fail messages are
not caused by user error, and only rarely by a hardware fault. Report any
occurrence of this error to a Campbell Scientific support engineer, especially if
the problem is reproducible. Any program generating these errors is unlikely to be
running correctly.
Examples of some of the more common warning messages are listed in table
Warning Message Examples
(p. 471).
Warning Message Examples
Message Meaning
• CPU:DEFAULT.CR1 --
Compiled in PipelineMode.
• Error(s) in
CPU:NewProg.CR1:
• line 13: Undeclared variable
Battvolt.
A new program sent to the datalogger failed to compile, and the datalogger
reverted to running DEFAULT.cr8.
Warning: Cannot open include
file CPU: Filename.cr8
The filename in the Include instruction does not match any file found on
the specified drive. Since it was not found, the portion of code referenced
by Include will not be executed.
Warning: Cannot open voice.txt
voice.txt, a file required for use with a COM310 voice phone modem, was
not found on the CPU: drive.