Campbell Scientific CR10X CR10X Measurement and Control System - Page 63

Error Codes

Page 63 highlights

SECTION 3. INSTRUCTION SET BASICS 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 once 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 2 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., E23 105; 105 indicates that the fifth instruction in Table 1 caused error 23). Error 22, missing END, will indicate the location of the instruction which the compiler cannot match with an END instruction. 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 E08 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. If there is a run time error in a table with a fast 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 some entry must be changed which requires recompiling (Section 1.1.4). For example, enter 0 for the execution interval of Table 1 (i.e., enter ∗1A0A as fast as possible). The program can easily be stopped by pressing any key while the CR10KD is displaying "HELLO" after applying power (turn the CR10X off and then on again). This delays program execution for about two minutes, allowing the program to be changed. Error 8 is the result of a hardware and software "watchdog" that checks the processor state, software timers, and program related counters. The watchdog will attempt to reset the processor and program execution if it finds that the processor has bombed or is neglecting standard system updates, or if the counters are out of allowable limits. Error code 08 is flagged when the watchdog performs this reset. E08 is occasionally caused by voltage surges or transients. Frequent repetitions 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 (Section 1.6) or with the Telecommunications A command (Section 5.1). Error 10 is displayed if the primary power drops below 9.6 volts. When this happens, the CR10X stops executing programs. The low voltage counter (∗B Window 9, Section 1.6) 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. Below approximately 8.5 volts 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 displayed immediately. Only the error code is displayed. ∗D Mode errors indicate problems with saving or loading a program. Only the error code is displayed. TABLE 3.10-1. Error Codes Code Type Description 03 Editor Program table full 04 Compile Intermediate Storage full 05 Compile Storage Area #2 not allocated 08 Run Time CR10X reset by watchdog timer 09 Run Time Insufficient Input Storage 10 Run Time Low battery voltage 11 Editor Attempt to allocate more Input or Intermediate Storage than is available 12 Compile Duplicate ∗4 ID 20 Compile SUBROUTINE encountered before END of previous subroutine 21 Compile END without IF, LOOP or SUBROUTINE 22 Compile Missing END 23 Compile Nonexistent SUBROUTINE 24 Compile ELSE in SUBROUTINE without IF 25 Compile ELSE without IF 26 Compile EXIT LOOP without LOOP 27 Compile IF CASE without BEGIN CASE 3-9

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362

SECTION 3. INSTRUCTION SET BASICS
3-9
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 once 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 2 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., E23 105; 105
indicates that the fifth instruction in Table 1 caused
error 23).
Error 22, missing END, will indicate the
location of the instruction which the compiler
cannot match with an END instruction.
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 E08 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.
If there is a run time error in a table with a fast
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 some entry
must be changed which requires recompiling
(Section 1.1.4).
For example, enter 0 for the
execution interval of Table 1 (i.e., enter
1A0A
as fast as possible).
The program can easily be
stopped by pressing any key while the CR10KD
is displaying “HELLO” after applying power (turn
the CR10X off and then on again).
This delays
program execution for about two minutes,
allowing the program to be changed.
Error 8 is the result of a hardware and software
"watchdog" that checks the processor state,
software timers, and program related counters.
The watchdog will attempt to reset the
processor and program execution if it finds that
the processor has bombed or is neglecting
standard system updates, or if the counters are
out of allowable limits.
Error code 08 is flagged
when the watchdog performs this reset.
E08 is
occasionally caused by voltage surges or
transients.
Frequent repetitions 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 (Section 1.6) or with the
Telecommunications A command (Section 5.1).
Error 10 is displayed if the primary power drops
below 9.6 volts.
When this happens, the
CR10X stops executing programs.
The low
voltage counter (
B Window 9, Section 1.6)
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.
Below approximately 8.5 volts 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 displayed
immediately.
Only the error code is displayed.
D Mode errors indicate problems with saving
or loading a program.
Only the error code is
displayed.
TABLE 3.10-1.
Error Codes
Code
Type
Description
03
Editor
Program table full
04
Compile
Intermediate Storage full
05
Compile
Storage Area #2 not
allocated
08
Run Time
CR10X reset by
watchdog timer
09
Run Time
Insufficient Input Storage
10
Run Time
Low battery voltage
11
Editor
Attempt to allocate more
Input or Intermediate
Storage than is available
12
Compile
Duplicate
4 ID
20
Compile
SUBROUTINE encountered
before END of previous
subroutine
21
Compile
END without IF, LOOP or
SUBROUTINE
22
Compile
Missing END
23
Compile
Nonexistent
SUBROUTINE
24
Compile
ELSE in SUBROUTINE
without IF
25
Compile
ELSE without IF
26
Compile
EXIT LOOP without
LOOP
27
Compile
IF CASE without BEGIN
CASE