Campbell CR6 Series, Руководство оператора

Страница: 563 / 690

Section 10. Troubleshooting
563
10.5.4.7 VarOutOfBounds
Related Topics:
•
Declaring Arrays
(p. 194)
•
VarOutOfBounds
(p. 563)
When programming with variable arrays, care must be taken to match the array
size to the demands of the program. For example, if an operation attempts to
write to 16 elements in array ExArray() , but ExArray() was declared with 15
elements (for example, Public ExArray(15)), the VarOutOfBound runtime error
counter is incremented in the Status table each time the absence of a sixteenth
element is encountered.
The CR6 attempts to catch VarOutOfBound errors at compile time (not to be
confused with the CRBasic Editor pre-compiler, which does not). When a
VarOutOfBound error is detected at compile time, the CR6 attempts to
document which variable is out of bounds at the end of the CompileResults
message in the Status table. For example, the CR6 may detect that ExArray() is
not large enough and write Warning:Variable ExArray out of bounds to the
CompileErrors field.
The CR6 does not catch all out-of-bounds errors, so take care that all arrays are
sized as needed.
10.5.4.8 Watchdog Errors
Watchdog errors indicate the CR6 has crashed and reset itself. A few watchdogs
indicate the CR6 is working as designed and are not a concern.
Following are possible root causes sorted in order of most to least probable:
•
Transient voltage
•
Running the CRBasic program very fast
• Many PortSet() instructions back-to-back with no delay
•
High-speed serial data on multiple ports with very large data packets or
bursts of data
If any of the previous are not the apparent cause, contact a Campbell Scientific
support engineer for assistance. Causes that require assistance include the
following:
• Memory corruption. Check for memory failures with
M
command in
terminal mode
(p. 567).
• Operating-system problem
•
Hardware problem