Campbell Scientific LoggerNet Datalogger Support Software - Manual (Page 466)

Section 14. Troubleshooting Guide
14.2.3 Data Collection Issues
Problem: Scheduled data collection is enabled but no data is being saved in the
data files, or data is not updating on numeric or graphical display.
Remedy 1: Make sure that communications are enabled for the
datalogger and all the devices in the communications link.
Remedy 2: For table-based dataloggers, make sure tables are
included for collection and the table definitions are current. For
array-based dataloggers, make sure the correct final storage areas are
included for collection.
Remedy 3: Check communication state on Status Monitor. An
indication of Primary or Secondary retry indicates that LoggerNet is
waiting for the next collect time. If the station is waiting in
Secondary Retry mode, open the Connect Screen and click the
Collect Now button. This will force collection from the datalogger
and will return the datalogger to the normal collection state.
Invalid Table Defs indicates that LoggerNet does not have a current copy of
the datalogger table definitions. You will need to update the table definitions
from the Setup Screen or the Connect Screen.
Network Paused indicates that data collection for the entire network has been
suspended. You will need to go to the Status Monitor and remove the check
mark from the Pause Schedule check box.
14.3 Application Screen Problems
Problem: Table-based datalogger program won’t compile and returns an E43
error.
Remedy: There is an interval mismatch between the P84 instructions
and the program scan rate. If the P84 intervals are not multiples of
the scan rate, the program won’t compile and will return this error.
14.4 General Communication Link Problems
Problem: Communications are not solid and difficulty is experienced sending
programs to the datalogger.
Remedy 1: If there are slow serial devices in the communication
path, such as older modems, the server might be overrunning the
buffers. Set the maximum packet size in the Setup Screen for the
datalogger to a smaller number.
Remedy 2: On noisy phone links try lowering the max baud rate for
the datalogger on the Setup Screen.
Remedy 3: On RF networks, make sure that the extra response time
is sufficient for the reply to come back, especially if there are
repeaters in the network. Use the minimum value necessary to make
the link function; usually less than 5 seconds.
14-4