Instruction manual

APPENDIX A. TROUBLESHOOTING
A-7
response to transmissions the radio hears. If
the frequency is in use, turn off the radio and
repeat the power up test.
With successful communication to the base
RF232T, the remotes should be verified. The
best tool for verifying RF communication with a
remote is the RF LINK TEST found in NetAdmin.
Section 2.4 of the RF Telemetry manual gives
information on using this test. Section 4.2.2 of
the RF Telemetry manual describes the RF LINK
TEST using the DOS-based GT program. The
following type messages CAN indicate a RF
remote failure. Note that RF1 is the remote site
and RF2BASE is the RF232T base. With a
failure, several warnings will usually precede a
fault message. This pattern is repeated each
time polling occurs.
'08-24-94 14:22:02','W','RF2Base','RF1','
RF Broadcast failure.'
'08-24-94 14:22:02','W','RF2Base','RF1','
RF Broadcast failure.'
'08-24-94 14:22:02','W','RF2Base','RF1','
RF Broadcast failure.'
'08-24-94 14:22:02','F','RF2Base','RF1',' RF
Poll failure.'
For direct maintenance operations (e.g., clock
set) the following type messages indicate a
failure.
'08-24-94 14:26:15','W','PC1','RF1','SerLine
timeout retry on: COM1.'
'08-24-94 14:23:38','F','PC1','RF1','Link
failed.'
The following message indicates a link that was
failing is working again.
'08-24-94 14:25:22','S','PC1','RF1',
'Communication restored with: RF1.'
Section 2.5 of the RF Telemetry manual gives
suggestions of things to check when a remote
RF station does not respond.
The RF Broadcast failure warning message
may occur occasionally on RF networks that are
functioning properly. These can be caused by
outside interference or conditions affecting the
quality of the link. They also can occur if the
Net Description has been changed. As long as
data is collect properly, occasional messages
are probably no reason for concern. Failures
are characterized by repeated warning; followed
by a fault.
A.3 COMPUTER COMMUNICATES WITH
DATALOGGER, BUT RTM IS NOT
DISPLAYING DATA, AND/OR
DBSELECT IS NOT STORING OR
ROUTING DATA.
Is DBSelect program started? If started, is data
collection running? The title bar of DBSelect
should indicate the data collection status
(running or stopped). If the title bar says that
DBSelect is stopped or does not indicate status,
check the SWF$.LOG to see if any messages
indicate why DBSelect stopped. The common
reasons are indicated by the following type
messages:
'08-18-94 15:44:13','F','PC1','PC1',
'DBSELECT Acknowledged Named pipe
broken, Memory low'
'08-18-94 15:44:13','F','PC1','PC1',
'DBSELECT shutting down too little disk
space'
'08-18-94 15:44:13','F','PC1','PC1',
'DBSELECT detected less than 3760128
bytes Free'
'08-18-94 15:44:13','S','PC1','CR10T','Send:
Data Advise.'
'08-18-94 15:44:14','S','PC1','PC1',
'DBSELECT Stopped'
These indicate either there was insufficient hard
disk space or that there was not enough
memory (these can be related). See Section
2.2 of the RTMS manual for specific OS/2
requirements.
DBSelect will also stop if the program receiving
data via the named pipe stops acknowledging
data. The following type messages will be
generated when this happens.
'08-18-94 15:30:00','S','PC1','PC1',
'DBSELECT DosWrite error on
Acknowledged named pipe 109'