Section 3. Instruction Set Basics
3-11
3.10 Error Codes
There are four types of errors flagged by the CR10X: Compile, Run Time, Editor
and *D Mode.
Compile errors are errors in programming which are detected when the program
is entered and compiled for the first time (*0, *6 or *B Mode entered). If a
programming error is detected during compilation, an E is displayed with the two-
digit error code. The Instruction Location Number of the instruction which caused
the error is displayed to the right of the error code (e.g. 105 indicates that the fifth
instruction in Table 1 caused the error). Error 22, missing End, indicates the
location of the instruction which the compiler cannot match with an End in-
struction.
Run time errors are detected while the program is running. The number of the
instruction being executed at the time the error is detected is displayed to the right
of the error code (e.g. E09 06 indicates that an Instruction 6 in the program is
attempting to store data in input locations beyond those allocated). Run time
errors 9 and 31 are the result of programming errors. While EO8 will display the
number of the instruction that was being executed when the error occurred, it is
unlikely that the instruction has anything to do with the error (see below).
If there is a run time error in a table with a short execution interval, the error may
be written to the display so frequently that it seems the CR10X is not responding
to the keyboard. Once the program is stopped, normal function will return. To
stop the program an entry must be changed which requires recompiling (see
Section 1). For example, enter 0 for the execution interval of Table 1 (i.e. enter
*1A0A
) and then recompile. (This should be done quickly since error messages
are queued and it may take some time to communicate with the CR10X if many
such messages have accumulated.) If using a CR10KD keyboard/display you can
stop a program by switching the CR10X off and back on. While the display is
showing ‘HELLO’ on start up, program execution is delayed for about two
minutes, allowing you to carry out any changes.
Error 8 is the result of a hardware and software ‘watchdog’ that checks the
processor state, software timers and program-related counters. The watchdog at-
tempts to reset the processor and program execution if it finds that the processor
has crashed or is neglecting standard system updates, or if the counters are out of
allowable limits. Error code 08 is displayed when the watchdog performs this
reset. E08 is occasionally caused by voltage surges or transients. Frequent repeti-
tions of E08 are indicative of a hardware problem or a software bug and should be
reported to Campbell Scientific. The CR10X keeps track of the number of times
(up to 99) that E08 has occurred. The number can be displayed and reset in the *B
Mode (see Section 1) or with the Telecommunications A command (see Section
5).
Error 10 is displayed if the primary power drops below 9.6 volts. If this happens,
the CR10X stops executing programs. The low voltage counter (*B Mode window
9 – see Section 1) counts the number of times the voltage drops below 9.6 volts
and displays a double dash (--) if the CR10X is currently in a low voltage shut
down state. Below approximately 8.5V the CR10X will not communicate with the
CR10KD or modem, although there may be enough power to display characters
on the CR10KD.
Editor errors are detected as soon as an incorrect value is entered and are dis-
played immediately. Only the error code is displayed. *D Mode errors indicate
problems with saving or loading a program. Only the error code is displayed.