Prometha™ Installation
750-441
11
8.2 - Hawk Connection
In the event of a problem with the Hawk control system connection:
• Confirm gateway Ethernet cable is plugged into the top Ethernet port of the gateway.
• Confirm PLC Ethernet cable is plugged into the Hawk PLC or an Ethernet switch on the Hawk network. Do
not plug the Ethernet cable into the 1769-SM2 module in the Hawk PLC I/O rack or, for older Hawks, the
1761-NET-ENI module.
• Confirm the offline Hawk control panel is powered up. Pay close attention to the PLC and Ethernet switch,
if applicable, to ensure they are also powered up in the panel.
• Confirm IP addresses match. The Hawk PLC IP address displayed on the portable monitor must be consis-
tent with IP address displayed on HMI (on the base rail). If mismatched, change the PLC IP address to
match (refer to Hawk O&M manual) or call C-B IoT support at the number listed on the portable monitor
for assistance.
• Confirm there is no gateway IP conflict on the Hawk network. The gateway IP address is listed (2) and
there shouldn’t be any other devices on the network with the same IP address. If there are, unplug the net-
work cable from the gateway device and call C-B IoT support with the preferred gateway IP address for
gateway IP address reassignment.
• Confirm the cables are good: use a network cable tester (Ideal LinkMaster 62-200), to test the Hawk net-
work cabling. A failed test could indicate either a damaged cable or an improperly terminated RJ45 con-
nector. Damaged cables that fail the network cable test will need replacing. Ensure that any incorrectly
terminated RJ45 connectors are reterminated following the T-568B wiring standard. Refer to illustration in
Wiring Diagrams section above for the T-568B pinout diagram.
• Confirm the CAT5e Ethernet cable does not exceed 328 ft in length. Cables beyond this length will not
maintain proper connection.
To Next Page
Loading...
Need help?
General
