Campbell CR3000 Micrologger, Руководство оператора

Страница: 514 / 644

Section 10. Troubleshooting
514
The CR3000 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 CR3000 has crashed and reset itself. A few
watchdogs indicate the CR3000 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. 523).
•
Operating-system problem
•
Hardware problem
Watchdog errors may cause comms disruptions, which can make diagnosis and
remediation difficult. The CR1000KD Keyboard/Display will often work as a
user interface when comms fail. Information on CR3000 crashes may be found
in three places.
•
WatchdogErrors
(p. 593)
field in the Status table
•
Watchdog.txt file on the CPU: drive
(p. 446).
Some time may elapse
between when the error occurred and the Watchdog.txt file is created.
Not all errors cause a file to be created. Any time a watchdog.txt file is
created, please consult with a Campbell Scientific support engineer.
•
Crash information may be posted at the end of the CompileResults
(p.
579)
register in the Status table.
10.5.4.8.1 Status Table WatchdogErrors
Non-zero indicates the CR3000 has crashed, which can be caused by power or
transient-voltage problems, or an operating-system or hardware problem. If
power or transient problems are ruled out, the CR3000 probably needs an
operating-system update or repair
(p. 5)
by Campbell Scientific.