Table of Contents
Advertisement
a conversation. If calibration or repair is needed, the procedure shown in
should be followed when sending the product.
12. Troubleshooting
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
l
Faulty connectors
l
Cut wires
l
Damaged insulation, which allows water to migrate into the cable. Water, whether or
l
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. Create a simplified 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 TEMP 120 in the network has a unique CPI address.
5. Check the data logger and TEMP 120 operating system and update them as needed.
6. Check that the scan rate is long enough for the measurement time. The data logger
compiler often catches scan rates that are too fast.
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
12.1 CPIStatus table
Information in the CPIStatus table, located in the data logger, 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 the following table.
CPI network bit rate
About this manual
(p. 22).)
TEMP 120
24
Advertisement
Table of Contents
