Instruction manual

SECTION 4. DLSMGR
4-2
remote, the RF base will direct the packets to
the CR10T using the specified path and return
the response as soon as possible.
If directly routed packet deliveries fail, the base
will attempt several retries. Retries are done at
the end of each polling cycle for remotes that
failed to respond to the broadcast. When
retries fail consistently, the base will mark the
remote site as not responding and will not
attempt further packet delivery or collection
from that site until it responds to a broadcast.
Direct connect, short haul, and MD9 − The
computer handles packet delivery with these
systems. Signature and dialing failures are
retried immediately. The remote dataloggers
are checked at the user-entered polling interval
for any packets they need to send to the
computer (normally data). Direct connect
(SC32A) and short haul modems (Rad
modems) access one datalogger per serial port.
The MD9 modems allow multiple remotes on
the same serial port. With MD9 modems, the
computer accesses the remotes sequentially by
dialing the base MD9.
4.1.3 DATA COLLECTION
DlsMgr also oversees the data collection
process. If the current retry period or four times
the polling period (whichever is longer) elapses
without a valid data response from a datalogger,
DlsMgr will restart the data collection from that
site. The datalogger will send a valid response
even if it has no data to send as long as it is
configured to send data. This prevents DlsMgr
from restarting the data collection if slow data
(compared to the retry and polling interval) is
being collected. Normally DlsMgr will need to
restart data collection when the following type of
event occurs:
• The datalogger is called by a computer
other than the RTMS computer (i.e.,
GraphTerm or other RTMS computer).
• The datalogger has cancelled sending data
because a long period has elapsed since
the last valid collection.
• The datalogger has lost power.
• The datalogger has been reprogrammed.