Instruction manual

APPENDIX A. TROUBLESHOOTING
A-5
Things to check include:
• Ensure that the correct COM port is
selected in the Net Description for the Base
MD9.
• Is the SC532 is powered up, i.e., plugged
in?
• Check each cable to be sure it is
connected properly.
• The cable connecting the computer and the
SC532 should not be a “Null Modem” cable
but should be standard serial RS232 cable.
• Swap cables if spares are available.
• Check that the base MD9 address is set to
255 with the switches.
• Power down the base MD9 by
disconnecting the 9-pin cable from the I/O
port. Disconnect the serial cable coming
from the computer to the SC532.
Reconnect the 9-pin cable to the base MD9.
Ensure that the SC532 is plugged in.
Reconnect the serial cable between the
computer and the SC532. Examine
communication again.
Once the base MD9 is communicating with the
computer, verify communication with the
remote(s). Here, the only clues are the network
health screen, the SWF$.LOG, and user's
observations. The SWF$.LOG will indicate
problems with messages like the following.
Again MD91 is the remote MD9-datalogger
station name. For this example the remote
MD9 Switches were set for ID = 1.
'08-24-94 14:28:41','W','PC1','MD91','MD9
dial operation failed (id = 1).'
'08-24-94 14:28:45','W','PC1','MD91','MD9
dial operation failed (id = 1).'
'08-24-94 14:28:48','W','PC1','MD91','MD9
dial operation failed (id = 1).'
'08-24-94 14:28:52','W','PC1','MD91','MD9
dial operation failed (id = 1).'
'08-24-94 14:28:52','F','PC1','MD91','Link
failed.'
Note that when the link does not work several
warnings precede a fault. This pattern repeats
each time the computer attempts
communication with the remote MD9 site.
Things to check include:
• Do the datalogger and DC112 have power?
Check 12 Volt supply for the datalogger.
The MD9 gets its power from pin 1 on the 9-
pin SERIAL I/O connector (5 Volts).
• Check the 9-pin cable connecting the MD9
to the datalogger. It should be straight
through, i.e., no line crossed. Check
connections at both ends. Try a spare 9-pin
cable if available.
• Check that each remote MD9 has a unique
address (ID).
• Check the coaxial cable between the base
MD9 and the remote. See MD9 manual for
details.
• Disconnect the 9-pin cable from the MD9.
Disconnect the coaxial cable from the MD9.
Reconnect the 9-pin cable then the coaxial
cable. Examine communications again.
• Occasional errors on MD9 networks.
Occasionally the computer may fail in its
attempt to communicate with or dial the
base MD9. The following type of warnings
and faults may occasionally be found in the
SWF$.LOG.
'08-24-94 14:29:06','W','PC1','MD91','MD9
dial operation failed (id = 1).'
'08-24-94 14:27:46','F','PC1','MD92','MD9
base failed to respond.'
'08-24-94
13:48:40','W','PC1','MD92','SerLine bad
signature on: COM1.'
This is normal, especially on an OS/2
computer with limited resources. As long
as data is being collected these messages
occasionally occurring are no reason for
concern. Failures are characterized by
repeated warnings and fault messages.