Manual revision 001
Section 6: Troubleshooting
SBE 39
plus
-IM
81
Section 6: Troubleshooting
This section reviews common problems in operating the SBE 39
plus
-IM, and
provides the most common causes and solutions.
Problem 1: Unable to Communicate with 39plus-IM
If
#iiOutputExecutedTag=N
, the
S>
prompt indicates that communications
between the IMM or SIM and computer have been established. Before
proceeding with troubleshooting, attempt to establish communications again
by selecting
Connect
in the Communications menu in SeatermIM.
Cause/Solution 1
: If communicating via IM telemetry, the I/O cable
connection to the computer may be loose. Check the cabling between the IMM
or SIM and computer for a loose connection.
Cause/Solution 2
: If communicating via the internal USB connector, the USB
cable connection to the computer may be loose. Check the cabling between the
39
plus
-IM and computer for a loose connection.
Cause/Solution 3
: The instrument type and/or its communication settings may
not have been entered correctly in SeatermIM. Verify the settings in the
Configure Communications dialog box (Communications menu ->
Configure
).
The settings should match those on the instrument Configuration Sheet.
Cause/Solution 4
: The I/O cable between the IMM or SIM and computer may
not be the correct one. The I/O cable supplied with the IMM or SIM permits
connection to standard 9-pin RS-232 interfaces.
Cause/Solution 5
: The modem core in the 39
plus
-IM (and/or the ICC, if
applicable) may have a gap, be misaligned, or be damaged. See
Application
Note 85: Handling of Ferrite Core in Instruments with Inductive Modem
Telemetry
for details on inspecting the modem core and proper installation of
the 39
plus
-IM and the ICC (if applicable) on the cable.
Problem 2: No Data Recorded
Cause/Solution 1
: The memory may be full; once the memory is full, no
further data will be recorded. Verify that the memory is not full using
#iiDS
(
free = 0
or
1
if memory is full). Sea-Bird recommends that you upload all
previous data before beginning another deployment. Once the data is
uploaded, send
#InitLogging
to reset the memory. After the memory is reset,
#iiGetSD
or
#iiDS
will show
samplenumber = 0
.