![hilscher netTAP NT 50 Series User Manual Download Page 38](http://html1.mh-extra.com/html/hilscher/nettap-nt-50-series/nettap-nt-50-series_user-manual_2134827038.webp)
Troubleshooting
38/86
netTAP NT 50 | Gateway Devices
DOC091202UM09EN | Revision 9 | English | 2013-02 | Released | Public
© Hilscher, 2010-2013
7 Troubleshooting
Two methods for troubleshooting exist:
•
The visual analysis of the LED conditions of the device
•
The analysis via the Ethernet port along with the configuration tool
SYCON.net.
The following overview describes the error conditions that may be detected
by a visual check of the LEDs.
In order to find the correct position of the LEDs please follow the chapter
Control Elements from page 24. The numbers in the
column LED state is referencing the position number in the device drawing.
LED state
Remedy
No LED is on
The device is not powered or the device has a malfunction and needs re-
placement.
SYS LED
flashes
yellow/green at 1 Hz
After a power cycle the device has not found a valid firmware and remains in
bootloader mode. The device has to be send back to the manufacturer for
repair.
SYS LED
is permanet
yellow
The device has a malfunction and needs replacement.
SYS LED
flashes
yellow
after Power On
The device has not found a firmware. The device has to be send back to the
manufacturer for repair.
SYS LED
is permanet
green,
APL LED
on
red flashing
or red on
The device is well initialized. Further analysis is possible with the LED
APL. Follow the chapter
on page 40.
APL LED
flashing
green
The communication via port X2 or/and port X3 is not in data exchange mode.
See chapter
Table 33: NT 50 Troubleshooting
The device is operational just in case the illustrated error conditions do not
met. Further protocol specific error diagnostics via the LEDs is possible by
reading on the chapter “LEDs”
In deep diagnostics is possible at any time via the Ethernet diagnostic port
of the device and a PC with the software SYCON.net.
In case of trouble you should make sure that you have downloaded a cor-
rect signal mapping to the device via SYCON.net
For some protocols it is necessary to synchronize data via a handshake be-
tween the gateway and the superordinated PLC. Please make sure that the
handshake mechanism is kept.