Section 10.  Troubleshooting 
 
 
o  Channel assignments, input-range codes, and measurement mode 
arguments are common sources of error. 
•  Hardware 
o  Mis-wired sensors or power sources are common. 
o  Damaged hardware 
o  Water, humidity, lightning, voltage transients, EMF 
o  Visible symptoms 
o  Self-diagnostics 
o  Watchdog errors 
•  Firmware 
o  Operating system bugs are rare, but possible. 
•  Datalogger support software 
o  Bugs are uncommon, but do occur. 
•  Externally caused errors 
 
10.4  Troubleshooting — Status Table 
Information in the Status table lends insight into many problems.    Info Tables 
and Settings 
(p. 527) documents Status table fields and provides some insights as to 
how to use the information in troubleshooting. 
Review Status Table as Debug Resource 
(p. 470). Many of these errors match up 
with like-sounding errors in the Station Status utility in datalogger support 
software. 
 
10.5  Troubleshooting — CRBasic Programs 
Analyze data soon after deployment to ensure the CR800 is measuring and storing 
data as intended.    Most measurement and data-storage problems are a result of 
one or more CRBasic program bugs. 
 
10.5.1  Program Does Not Compile 
Although the CRBasic Editor compiler states that a program compiles OK, the 
program may not run or even compile in the CR800.    This is rare, but reasons 
may include: 
•  The CR800 has a different (usually older) operating system that is not 
fully compatible with the PC compiler. Check the two versions if in