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 VOLT 100 series in the network has a unique CPI address.
5. Check the data logger and VOLT 100 series operating system and update them as needed.
6. Check that the scan rate is long enough for the measurement time. (See
(p. 33).) 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
(p. 36).)
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.
Table 12-1: CPIStatus activity
Response
Meaning
Active
The module is connected to the CPI bus and is making measurements according to
the data logger program.
Offline
The module was present after startup but is no longer responding.
Unused
The module is or was connected and powered but is not included in the data
logger program.
Wait Config The module has not yet responded to a data logger’s attempts to configure it.
Config Fail
The module could not be configured. A configuration error message is appended
to this response.
12.2 COMM status LED
The COMM status LED indicates the current operation of the VOLT 100 series, as shown in the
following table..
VOLT 100 series
39