User Manual
PLUS System Manual System Installation 53
Proprietary Information: Do not disclose unless authorized under a Nondisclosure Agreement and the Partner Agreement.
2.7 Troubleshooting Reader Communications
For cases where the Visualizer is unable to see data from the Readers, follow the troubleshooting
procedure below.
Check that discovery packets are being received from the Readers. Under the Reader List View,
determine if the Last Comms timer is exceeding ten seconds for the Reader(s) in question. If the
timer is resetting to zero after ten seconds, the Visualizer is receiving Reader data, but the Reader is
not seeing Tag packets. Follow the procedure below for the Reader Connectivity but No Tag
Traffic case. If the timer is exceeding ten seconds without resetting, follow the procedure for the No
Reader Connectivity case.
Figure 2-51: Reader List View
2.7.1 No Reader Connectivity
1) Make sure that duplicate instances of the Visualizer application are not running.
2) Check the Ethernet cable connection bewteen the server and Ethernet switch. Typically, the
Ethernet connector will have one LED for link status and one LED for activity. A steady green
LED generally indicates Ethernet connectivity to the next device, and a flashing yellow LED
indicates Ethernet traffic is present. Replace the cable if it is in question.
3) Check the Ethernet cable connection between the Ethernet switch and the SDP. Verify that the
Switch is powered, a valid connection exists, and traffic is present.
4) Check that the Reader is powered, and the Ethernet link status light on the Reader is steady. The
Ethernet activity light should blink each time a Tag packet is received, or once every ten seconds
as a discovery packet is transmitted.
5) Check that the NIC card on the server has been configured with the correct IP address. This IP
address should correspond to the Location Engine IP address configured on each Reader.
6) Check that the Visualizer IP address is set properly under the Settings, Set Data Input… menu.
7) Check that traffic from the Readers is not blocked by the server firewall.
Open a command window (Figure 2-52). Check that there is not another process conflicting with
the location software on port 11000 using the command
netstat –a –p UDP –n –o (Figure 2-53).
8) Check communications to the Reader by typing ping <IP address>.