Table of Contents
Advertisement
CDM-A100 Series
10. Troubleshooting
10.1 Troubleshooting – Basic Procedure
10.2 Troubleshooting – CPIStatus Table
30
telephone conversation. If calibration or repair is needed, the procedure shown
in
Assistance
should be followed when sending the product.
1.
Check the voltage of the power source at the Power connector. It should
be between 9.6 and 32 Vdc.
2.
Check wires and cables for the following:
•
Loose connection points
•
Faulty connectors
•
Cut wires
•
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
could easily have crept into the code. To troubleshoot, create a stripped
down 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. Write these mini-programs before
going to the field, if possible.
4.
Verify that each CDM-A100 in the network has a unique CPI address.
5.
Check the datalogger and CDM-A100 operating system and update them
as needed.
6.
Check that the scan rate is long enough for the measurement time. (See
Section 8.2.1, Measurement Speed
7.
Ensure that the CPI network bit rate is fast enough for the data generated
and that it can accommodate the cable lengths in use. (See Section 8.2.2,
CPI Network Bit Rate
(p. 28)
Information in the CPIStatus table, which is located in the datalogger, helps in
troubleshooting. The ModuleInfo() array shows the following information:
CDM Type, Serial Number, Device Name, CPI Address, Activity
The last entry in the ModuleInfo() index shows the activity of the module.
Possible entries and their meanings are shown in TABLE 10-1.
CRBasic Editor
, logic and syntax errors
(p. 32)
.)
(p. 26)
.)
Advertisement
Table of Contents
