Section 10. Troubleshooting
If any of the previous are not the apparent cause, contact a Campbell Scientific
application engineer for assistance. Causes that require assistance include the
following:
• Memory corruption. Check for memory failures with M command in
terminal mode
(p. 501).
• Operating-system problem
• Hardware problem
Watchdog errors may cause telecommunication disruptions, which can make
diagnosis and remediation difficult. The CR1000KD Keyboard Display will often
work as a user interface when telecommunications fail. Information on CR1000
crashes may be found in three places.
• WatchdogErrors field in the Status table
(p. 603)
• Watchdog.txt file on the CPU: drive
(p. 374). 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 application engineer.
• Crash information may be posted at the end of the CompileResults register
in the Status
(p. 603) table.
10.5.4.8.1 Status Table WatchdogErrors
Non-zero indicates the CR1000 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 CR1000 probably needs an
operating-system update or repair
(p. 3) by Campbell Scientific.
10.5.4.8.2 Watchdoginfo.txt File
A WatchdogInfo.txt file is created on the CPU: drive when the CR1000
experiences a software reset (as opposed to a hardware reset that increment the
WatchdogError register in the Status table). Postings of WatchdogInfo.txt
files are rare. Please consult with a Campbell Scientific application engineer at
any occurrence.
Debugging beyond identifying the source of the watchdog is quite involved.
Please contact a Campbell Scientific application engineer for assistance. Key
things to look for include the following:
• Are multiple tasks waiting for the same resource? This is always caused by a
software bug.
• In newer operating systmes, there is information about the memory regions. If
anything like ColorX: fail is seen, this means that the memory is corrupted.
• The comms memory information can also be a clue for PakBus and TCP
triggered watchdogs. For example, if COM1 is the source of the watchdog,
knowing exactly what is connected to the port and at what baud rate and
frequency (how often) the port is communicating are valuable pieces of
information.
489
To Next Page
Loading...
Need help?
General
