Instruction manual

APPENDIX A. TROUBLESHOOTING
A-10
First message indicates the RTM or DBSelect
requested a specific range of data using hole
collection. Second message indicates what
data was collected using hole collection.
Several hole collections may be required to
collect a single hole depending on the amount
of data. Normally these messages can occur
following Data Advise messages (see next
message) or when holes are manually entered
in DBSelect. See Section 7 in RTMS manual.
RTM optionally uses hole collection to backfill
strip charts when the monitor mode is started.
Frequent hole collection during routine
operation (i.e., no user intervention or changes)
may indicate that data is being lost en route
from datalogger to DBSelect. A poor but
sometime functional communication link could
cause this (check communication Section 1.3
above). If the OS/2 computer is exceedingly
burdened (Section 2.2 in RTMS manual) data
may be collected but discarded because the
computer cannot process it as fast as it is
collected and buffers overflow.
'08-18-94 14:59:52','S','PC1','CR10T','Send:
Data Advise.'
'08-18-94 15:01:24','W','PC1','CR10T',
'Advise Transaction re-started (CR10T).'
The computer sent a list of the data it requires
to the datalogger (advised the datalogger).
This normally occurs when RTM or DBSelect is
stopped, started, or edited so the data needed
from the datalogger changes. This can also
occur when the datalogger clock has changed
or has a new program downloaded.
Abnormally these messages occur when
DlsMgr tries to reset data collection with a given
datalogger. DlsMgr does this when it detects
that a significantly long period has elapsed
without data or a valid no data response is
being received from the datalogger. Period is
current retry period or four times the polling
interval (whichever is longer). Note that the
datalogger will return a valid no-data response
as long as it has been “advised” of what data to
return. This prevents DlsMgr from resetting
data collection when slow data is being
collected. If DlsMgr successfully restarts the
transaction data should resume. Check
communication with datalogger (see Section 2).
Check RTM and DBSelect to see if they have
stopped collecting data from station (see
Section 3).
'09-02-94 16:03:59','S','PC1','RF1','Unused
'Data Advise Notification' from 'RF1'.'
This indicates that data from a previous data
advise arrived. These messages occur
normally when the list of data to be collected
has been changed. Data already en route to
the computer will be based on the old list of
data to be collected (data advise) and will not be
used by the computer. Once the new data
advise is in place, these messages should stop.
Note that when the data advise changes,
usually there will be some data hole collected.
'08-24-94 13:42:15','S','PC1','Stn2','Hayes
dialing: '513' (COM1).'
DlsMgr is attempting communication with a
remote station accessed by telephone. The
station name is Stn2, and the phone number is
513. This message occurs each time the
phone is dialed.
'08-18-94 15:01:38','S','PC1','CR10T',
'Send: Get Table Definitions.'
The computer has requested a list of data
available from the datalogger. This normally
occurs when the station has just been added to
the network or a datalogger program.DLD file
has been downloaded. Otherwise, it indicates
that DlsMgr thinks the datalogger program has
changed. This can indicate that power has
been lost at the datalogger site or the
datalogger has been reprogrammed manually,
i.e., keyboard display or laptop.
'08-18-94 15:01:39','S','PC1','CR10T','Table
Definitions from 'CR10T' changed.'
A follow up message to a previous message
indicats that the data available from a
datalogger has changed. Same conditions as
previous message.
'08-18-94 15:02:31','S','PC1','CR10T','Send:
Clock Set/Check.'
'08-18-94 15:02:31','S','CR10T','CR10T',
'Clock changed'
'08-18-94 15:19:11','S','CR10T','CR10T',
'Clock changed; Program running'
Clock was checked or set (first message). This
message occurs when the clocks are