MCB
Member
I had an interesting problem at a customer's site today.
He has RSLinx Classic Professional version 2.50.00.20, and is using the Ethernet/IP driver to communicate with the PLCs. He is also using the Ethernet driver with individual IP addresses to talk to the different VFDs, which are from 192.168.0.30 though 192.168.0.38 (Both drivers configured are, however, on the same subnet. The Ethernet/IP driver configured to browse a remote subnet at 192.168.0.20, subnet 255.255.255.0)
In RSWho, if you were to simply just expand the tree that is the Ethernet/IP driver, all PLCs (there are 3 CompactLogix PLCs) on that subnet will completely lock up, as that is what I was told. He would then have to go power cycle the PLCs to get them to come back online.
Then after they power cycled the PLCs, they were able to see it in that RSLinx tree, and be able to get online. Say they would make changes to the program live in RSLogix5000 by adding a new tag. Then that would cause all of the PLCs on the network to lock up again, and be restored only after power cycling them.
I personally have not witnessed the PLCs crashing like that, and could not experiment today while I was there....
However, with my laptop running RSLinx Classic Gateway version 2.54.00.11, I was able to get online just fine. However, I used just the plain Ethernet driver, and added the IP addresses myself. I was also able to get online using RSLogix5000 with the processor with no problems.
I was unable to experiment with other drivers on the customer's PC today, as we were afraid of again crashing the PLCs...
The PLCs are all CompactLogix L32E.
So my question is: Is it the Ethernet/IP driver in RSLinx on the customer's computer causing the problem? Or is there something else configured improperly in my scenario above?
Thanks,
Mike B.
He has RSLinx Classic Professional version 2.50.00.20, and is using the Ethernet/IP driver to communicate with the PLCs. He is also using the Ethernet driver with individual IP addresses to talk to the different VFDs, which are from 192.168.0.30 though 192.168.0.38 (Both drivers configured are, however, on the same subnet. The Ethernet/IP driver configured to browse a remote subnet at 192.168.0.20, subnet 255.255.255.0)
In RSWho, if you were to simply just expand the tree that is the Ethernet/IP driver, all PLCs (there are 3 CompactLogix PLCs) on that subnet will completely lock up, as that is what I was told. He would then have to go power cycle the PLCs to get them to come back online.
Then after they power cycled the PLCs, they were able to see it in that RSLinx tree, and be able to get online. Say they would make changes to the program live in RSLogix5000 by adding a new tag. Then that would cause all of the PLCs on the network to lock up again, and be restored only after power cycling them.
I personally have not witnessed the PLCs crashing like that, and could not experiment today while I was there....
However, with my laptop running RSLinx Classic Gateway version 2.54.00.11, I was able to get online just fine. However, I used just the plain Ethernet driver, and added the IP addresses myself. I was also able to get online using RSLogix5000 with the processor with no problems.
I was unable to experiment with other drivers on the customer's PC today, as we were afraid of again crashing the PLCs...
The PLCs are all CompactLogix L32E.
So my question is: Is it the Ethernet/IP driver in RSLinx on the customer's computer causing the problem? Or is there something else configured improperly in my scenario above?
Thanks,
Mike B.