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
Summary of Contents for CR1000
Page 2: ......
Page 4: ......
Page 6: ......
Page 32: ......
Page 36: ......
Page 38: ......
Page 40: ......
Page 60: ...Section 4 System Quickstart Figure 16 PC200W View Line Graph 60 ...
Page 96: ......
Page 98: ...98 ...
Page 302: ......
Page 453: ...Section 8 Operation Figure 115 Using the Keyboard Display 453 ...
Page 456: ...Section 8 Operation Figure 118 Real Time Custom 456 ...
Page 457: ...Section 8 Operation 8 8 1 3 Final Memory Tables Figure 119 Final Memory Tables 457 ...
Page 458: ...Section 8 Operation 8 8 2 Run Stop Program Figure 120 Run Stop Program 458 ...
Page 460: ...Section 8 Operation Figure 122 File Edit 460 ...
Page 461: ...Section 8 Operation 8 8 4 PCCard Memory Card Display Figure 123 PCCard CF Card Display 461 ...
Page 478: ......
Page 506: ......
Page 536: ......
Page 636: ......
Page 642: ......
Page 644: ......
Page 676: ......
Page 677: ......