CTI 2572-A, Installation And Operation Manual

Page: 73 / 130

CTI 2572-A Installation and Operation Guide V1.3 65
8.4. Communications Problems
If the module operational (properly started up) but it will not respond to network clients, refer to the
table below for help in diagnosing the cause.
Symptom Probable Cause Corrective Action
Cable between the module and Ethernet
hub/switch is not connected. Plug the opposite cable end into the
hub or switch.
The Link Status (LS) LED is
Off
The cable is faulty or the RJ45 connector is
improperly wired. Test cable and replace if faulty.
OR
Substitute a cable known to be
good.
Defective Ethernet Hub or Switch Ensure power is applied to the
hub/switch.
Determine whether other devices
are using the hub/switch
successfully.
There is no traffic on the network segment.
If you are attempting to access the module
via the network, you should observe the
Ethernet RCV LED flash intermittently.
NOTE: On most active networks, you will
see some traffic on the local segment, even
though that traffic is not directed to the
module.
Ensure that the Ethernet hub/switch
is connected to the network.
Using a PC attached to the local
network, send a PING to the
module IP address. If you observe
the Ethernet RCV LED flash, the
physical connection is OK.
The Link Status (LS) LED is
on. Ethernet Receive (RCV)
LED does not flash.
If you are using a switch, the switch may be
blocking the port for the particular IP
address.
NOTE: This can occur when you change
the port to which the module is connected.
Cycle power to the switch, if
possible.
OR
Wait for up to 5 minutes, for the port
to dynamically reassign the port.
The IP Address/Subnet Mask of the client
PC does not match the local network.
NOTE: This might occur is you are using a
laptop normally used for other purposes.
Observe the reply to the PING. If
you receive a reply such as
“Network Unreachable” , the PC IP
address does not match.
Determine the IP setting of the PC
by typing IPCONFIG in the
Command Prompt window. Ensure
that both the IP address and Subnet
Mask are correct.
Attempt to PING the module
using a PC attached to the
local network is
unsuccessful. Physical
network connections are
OK.
The module IP address/Subnet Mask is
improperly set. Using the CTIDiag program,
connect to the module serial port
and open a serial port connection.
Using the “Set Network
Parameters” command, read the IP
address from the module EEPROM.
Then see following troubleshooting
activities
Module IP address is
improperly set. Using PLC Incorrect data has been entered in the Start
Network Server command block. Review the command block entries.
Ensure that the conversion to