9. Tips and troubleshooting
Start with these basic procedures if a system is not operating properly.
1. Using a voltmeter, check the voltage of the primary power source at the POWER IN
terminals on the face of the datalogger, it should be 10 to 18 Vdc.
2. Check wires and cables for the following:
l Incorrect wiring connections. Make sure each sensor and device are wired to the
terminals assigned in the program. If the program was written in Short Cut, check
wiring against the generated wiring diagram. If written in CRBasic Editor, check
wiring against each measurement and control instruction.
l Loose connection points
l Faulty connectors
l Cut wires
l Damaged insulation, which allows water to migrate into the cable. Water, whether or
not it comes in contact with wire, can cause system failure. Water may increase the
dielectric constant of the cable sufficiently to impede sensor signals, or it may
migrate into the sensor, which will damage sensor electronics.
3. Check the CRBasic program. If the program was written solely with Short Cut, the program
is probably not the source of the problem. If the program was written or edited with
CRBasic Editor, logic and syntax errors could easily have crept in. To troubleshoot, create a
simpler version of the program, or break it up into multiple smaller units to test
individually. For example, if a sensor signal-to-data conversion is faulty, create a program
that only measures that sensor and stores the data, absent from all other inputs and data.
4. Reset the datalogger. Sometimes the easiest way to resolve a problem is by resetting the
datalogger (see Resetting the datalogger (p. 118) for more information).
For additional troubleshooting options, see:
9.1 Checking station status 113
9.2 Understanding NAN and INF occurrences 115
9.3 Timekeeping 116
9.4 CRBasic program errors 117
9.5 Resetting the datalogger 118
9.6 Troubleshooting power supplies 120
9.7 Minimizing ground loop errors 121
9. Tips and troubleshooting 112
To Next Page
Loading...
