MCB
Member
I recently made a post about a customer's job site that supposedly RSLinx Ethernet/IP would fault the PLCs as stated by the customer. After making a return visit this week to actually test the PLCs, I found the actual problems. The PLCs never faulted. They continue to run just fine.
They have Eaton Cutler Hammer SVX9000 VFDs with an Eaton Multiprotocol Ethernet Module part number OptCI.
There are 3 PLCs in the plant. Each PLC cabinet has a PanelView Plus display. And up in the one building is a PC running RSView that enables you to see the entire plant. This PC is where my problems are at:
RSView works perfectly and the plant runs just fine... In RSLinx, it is configured to use the Ethernet/IP driver.
The problem arises when they want to add tags to the PLC programs from that computer, or say they open RSLinx and expand the tree on that of the Ethernet/IP driver. As soon as you do that, all 3 VFDs lose communication with the PLCs, and all of the alarms go off on the system.
The only way to recover from that is to power cycle the drives (they lock on their current speed, but will not communicate with the PLCs.) But this is a separate issue.
So anytime RSWho tries to browse that subnet in Ethernet/IP and find all of the devices on it, the VFDs lose communication.
Now, if I just use the plain Ethernet driver, and enter all of the IP addresses that way, there is no problem. It does not cause the VFDs to go offline.
I am just trying to find a solution here as to why the Ethernet/IP driver is causing this problem.
If I cannot find a solution there, I can go with just the Ethernet driver, but then RSView will have to be reconfigured to do so.
They have Eaton Cutler Hammer SVX9000 VFDs with an Eaton Multiprotocol Ethernet Module part number OptCI.
There are 3 PLCs in the plant. Each PLC cabinet has a PanelView Plus display. And up in the one building is a PC running RSView that enables you to see the entire plant. This PC is where my problems are at:
RSView works perfectly and the plant runs just fine... In RSLinx, it is configured to use the Ethernet/IP driver.
The problem arises when they want to add tags to the PLC programs from that computer, or say they open RSLinx and expand the tree on that of the Ethernet/IP driver. As soon as you do that, all 3 VFDs lose communication with the PLCs, and all of the alarms go off on the system.
The only way to recover from that is to power cycle the drives (they lock on their current speed, but will not communicate with the PLCs.) But this is a separate issue.
So anytime RSWho tries to browse that subnet in Ethernet/IP and find all of the devices on it, the VFDs lose communication.
Now, if I just use the plain Ethernet driver, and enter all of the IP addresses that way, there is no problem. It does not cause the VFDs to go offline.
I am just trying to find a solution here as to why the Ethernet/IP driver is causing this problem.
If I cannot find a solution there, I can go with just the Ethernet driver, but then RSView will have to be reconfigured to do so.
Last edited: