Campbell Scientific CR6 CR6 Measurement and Control System - Page 476
Status Table WatchdogErrors, 5.1.8.2, Watchdoginfo.txt File
View all Campbell Scientific CR6 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 476 highlights
Section 10. Troubleshooting 10.5.1.8.1 10.5.1.8.2 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 application engineer for assistance. Causes that require assistance include the following: • Memory corruption. Check for memory failures with M command in terminal mode (p. 484). • Operating-system problem • Hardware problem Watchdog errors may cause telecommunication disruptions, which can make diagnosis and remediation difficult. The external keyboard display will often work as a user interface when telecommunications fail. Information on CR6 crashes may be found in three places. • WatchdogErrors field in the Status table (p. 581) • Watchdog.txt file on the CPU: drive (p. 376). 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. 581) table. Status Table WatchdogErrors Non-zero indicates the CR6 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 CR6 probably needs an operatingsystem update or repair (p. 3) by Campbell Scientific. Watchdoginfo.txt File A CPU: WatchdogInfo.txt file is created on the CPU: drive when the CR6 experiences a software reset (as opposed to a hardware reset that increment the Status-table WatchdogError register). Postings of WatchdogInfo.txt files are rare. Please consult with a Campbell Scientific application engineer at any occurrence. Debugging beyond the source of the watchdog is quite involved. Please contact Campbell Scientific for assistance. There are a few key things to look for: 1. Are multiple tasks waiting for the same resource? This is always caused by a software bug. 2. 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. 3. The comms memory information can also be a clue for PakBus and TCP triggered watchdogs. 476