ProSoft Technology 5201-MNET-101S - Manual (Page 57)

IEC-101 Slave ♦ ProLinx Communication Gateway Diagnostics and Troubleshooting
IEC 60870-5-101 v3 Slave (Firmware version 3.xx) Protocol Manual
ProSoft Technology, Inc. Page 57 of 159
August 6, 2010
4 Diagnostics and Troubleshooting
In This Chapter
 LED Indicators ....................................................................................... 57
 Using ProSoft Configuration Builder (PCB) for Diagnostics................... 59
There are two ways to troubleshoot ProLinx Gateways:

Using the LEDs located on the front of the gateway
 Using the Debug port that provides a view into the gateway's internal
database.
4.1 LED Indicators
LEDs provide visual indications of potential problems. The following LEDs are
found on all ProLinx gateways.
4.1.1 Base Gateway LEDs
LED State Description
Power Off Power is not connected to the power terminals or source is insufficient
to properly power the gateway (minimum required is 800mA at 24 Vdc)
Green Solid Power is connected to the power terminals.
Fault Off Normal operation.
Red Solid A critical error has occurred. Program executable has failed or has
been user-terminated and is no longer running. Press Reset p/b or
cycle power to clear error. If not, use the Debug procedures described
later in this manual.
Cfg Off Normal operation.
Amber Solid The unit is in configuration mode. The configuration file is currently
being downloaded or, after power-up, is being read, the unit is
implementing the configuration values, and initializing the hardware.
This will occur during power cycle, or after pressing the reset button. It
also occurs after a cold/warm boot command is received.
Err Off Normal operation.
Flashing An error condition has been detected and is occurring on one of the
application ports. Check configuration and troubleshoot for
communication errors.
Solid Red This error flag is cleared at the start of each command attempt
(Master/Client) or on each receipt of data (slave/adapter/server); so, if
this condition exists, it indicates a large number of errors are occurring
in the application (due to bad configuration) or on one or more ports
(network communication failures).