51
50
TROUBLESHOOTING GUIDE
If troubles occur with the
HI504903
device, follow the be-
low guidelines.
INTERFACE CONFIGURATION
•
One (or more)
HI142
datalogger(s) is (are) not recognized
by
HI504903
interface during interface configuration with
provided application software
HI504903SW
on “test device”
procedure.
Possible causes
Configuration parameters for serial com-
munication between
HI504903
and
HI142
datalogger are not correct.
Mains power supply missing on
HI142
datalogger.
Wiring not correctly performed.
Solutions
Check if the
HI142
serial number parameter
for serial communication set with
HI504903SW
application software matches with the one of
the datalogger.
Provide the mains power supply to
HI142
datalogger.
Check if
HI142
datalogger is correctly con-
nected to the
HI504903
supervisor.
•
During local interface configuration attempt the
HI504903SW
software can not connect to the
HI504903
interface.
Possible causes
Wiring not correctly performed.
HI504903
interface is busy (a remote
PC communication or remote interface
configuration is already in place, inter-
face is performing the polling procedure
for a not responding device, etc.).
HI504903
is in power failure status.
HI504903
interface is turned off.
Solutions
Check if the
HI920010
cable is correctly con-
nected to the RS232 serial port on the PC and
to the auxiliary serial port on the
HI504903
interface.
Try to connect later.
Restore mains power supply or wait for power
supply comes back.
Turn on the
HI504903
interface.
ERRORS PRIORITY
HI504903
is provided with some selftest procedures and
related “visual” LED indications when some of these tests
failed, in order to make the user understand the interface
related problem (see “Fault conditions and selftest proce-
dures” section).
Only two LEDs (green and red LEDs for SMS sending enable/
disable) are available to give information to the user about
active errors, and no more than one can be shown at the
same time. For this reason every error type has an associated
priority level, as described in the following table:
Error type
Priority level
Power failure
4
EEPROM data corruption
3
Cellular error
2
Battery test failure
1
If more than one fault condition occurs simultaneously, then
errors with lower priority level are masked by error with high
one: only error indication with higher priority will be visible
by the user.
