sdb
Member
I have a ControlLogix system using ControlNet to connect to the remote I/O. I am using 1756-CNBR modules with redundant media in both the CPU and remote racks. The system is a redundant system using the 1756-RM modules. The CPUs are 1756-L63 with firmware 16.57. I have 13 remote I/O racks. Due to the bandwidth of the CNBR modules I am using 3 of them in each of the CPU racks for a total of 19 CNBRs.
My concern is troubleshooting broken connections. Let's say I pull the "B" cable from the bottom of a CNBR module. The "B" LED on every CNBR module flashes red, not just the one with the pulled cable. The "A" LEDs all stay green and comms remain intact, as expected. It does not matter if I pull the cable from the active keeper or inactive keeper. Same thing happens if I break the trunk cable anywhere along its path. Is this normal? It sure makes finding the broken connection a difficult task.
I am in the process of creating a communications overview screen that will show the status of each CNBR on the network. I can ascertain the status of the LEDs using MSG instructions but showing 19 red LEDs on the screen won't help the technicians pinpoint the problem.
Is there another way to isolate the faulty connection and display it on the HMI?
My concern is troubleshooting broken connections. Let's say I pull the "B" cable from the bottom of a CNBR module. The "B" LED on every CNBR module flashes red, not just the one with the pulled cable. The "A" LEDs all stay green and comms remain intact, as expected. It does not matter if I pull the cable from the active keeper or inactive keeper. Same thing happens if I break the trunk cable anywhere along its path. Is this normal? It sure makes finding the broken connection a difficult task.
I am in the process of creating a communications overview screen that will show the status of each CNBR on the network. I can ascertain the status of the LEDs using MSG instructions but showing 19 red LEDs on the screen won't help the technicians pinpoint the problem.
Is there another way to isolate the faulty connection and display it on the HMI?