Campbell CR6 Series, Operator'S Manual

Page: 560 / 690

Section 10. Troubleshooting
560
'Call Data Tables and Store Data
CallTable (TempC_Data)
NextScan
EndProg
10.5.4 Status Table as Debug Resource
Related Topics:
• Info Tables and Settings
(p. 613)
•
Common Uses of the Status Table
(p. 616)
•
Status Table as Debug Resource
(p. 560)
Consult the CR6 Status table when developing a program or when a problem with
a program is suspected. Critical
Status
table fields to review include
CompileResults , SkippedScan , SkippedSlowScan , SkippedRecord ,
ProgErrors , MemoryFree , VarOutOfBounds , WatchdogErrors and
Calibration .
10.5.4.1 CompileResults
CompileResults reports messages generated by the CR6 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. 97)
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.