22 troubleshooting, Q: a – In-Situ TROLL 9500 Operators Manual User Manual

Page 148

Advertising
background image

143

Multi-Parameter

Water Quality TROLL

®

TROLL 9500 Operator’s Manual

0095110 rev. 007 01/09

22 TROUBLESHOOTING

Q:

A:

The MP TROLL 9500 rolled out of the back of my truck
and hit the ground pretty hard. It still talks. Is it OK to
use?

The instrument is pretty rugged, and can survive a few
drops and rolls. We hope the restrictor was on to protect
the sensors! First, check the joint between the body and the
restrictor. It should appear smooth and tight to preserve the
integrity of the water seal. Next, remove the restrictor and
insure the pressure sensor is snug against the sensor block.
Push it firmly into the sensor block if you see a gap. If the
temperature sensor is bent, straighten it gently but firmly by
hand (no tools, please).

If the instrument is dropped repeatedly on the nose cone,
check for damage to the batteries.

TROUBLESHOOTING CONNECTIONS

Problem: Win-Situ or Pocket-Situ cannot “find” (connect to) the MP

TROLL 9500. Error 6146 may be displayed.

Probable Cause: Wrong COM port selected, loose cable connec-

tions, device is taking a measurement as part of a test, batteries
are low, elastomer is worn

Suggested Remedy: Check the following:

s

power

s

necessary to “sneak” in between test data points.

Problem: Readings are in the wrong units

Probable Cause: Default units are being used

Suggested Remedy: Select the desired units on the Win-Situ Op-

tions menu, or select the Home site in Pocket-Situ and tap Setup in
the command bar

Problem: Pocket-Situ hangs

Suggested Remedy: Reset the PDA; see your PDA documentation

for details on hard and soft reset

TROUBLESHOOTING DATA COLLECTION (TESTS)

Problem: Test ABENDed (came to an “ABnormal END”)

Probable Cause: Device lost power or ran out of memory

Suggested Remedy: None; indication of ABEND in software cannot

be reversed. but data collected up until the time the test ABENDed
is likely to be fine

Check clock, check memory free, check device power

Problem: Scheduled test did not start

Probable Cause: Incorrect device clock, full memory, power removed

at time of first scheduled data point

Suggested Remedy: Synchronize device clock and reschedule test;

insure device has sufficient battery power and free memory; insure
device is powered at time of first scheduled data point

Advertising
This manual is related to the following products: