jdbrandt
Lifetime Supporting Member
Well, I came across this gem in some Rockwell documentation today:
You cannot bridge EtherNet/IP I/O across networks. I/O modules must be configured in either a local chassis or a remote chassis. You cannot go through a gateway chassis to control I/O even though, in some circumstances, RSLogix 5000 software accepts such a configuration in the I/O Configuration folder.
Now, I suppose, it all depends on your definition of a 'gateway chassis', but there is a specific reason this is interesting.
I have a PLC (192.168.1.2) with a real gateway/router at (192.168.1.1), and lost of EIP I/O in the 192.168.1.xxx...all that works.
We are doing MSGing across this router, with success, to the other network.
I'd like to access an Ethernet/IP I/O device on another network, through the (192.168.1.1) gateway/router, and it doesn't work.
If I connect the device to the local network, and re-address it in the 192.168.1.xxx range (like the already-working local I/O), it works...which shows me the device is happy.
If I connect the device (reset to its address on the 'other' network, directly to the gateway's external network port, it still doesn't work...proving that its not a network infrastructure problem on the other network.
So, the real question for plcs.net is: Does all this sound right? More importantly, What is so different about a router/gateway accessed address, versus an address on the local network, that does not allow Ethernet/IP (for I/O) to work?
You cannot bridge EtherNet/IP I/O across networks. I/O modules must be configured in either a local chassis or a remote chassis. You cannot go through a gateway chassis to control I/O even though, in some circumstances, RSLogix 5000 software accepts such a configuration in the I/O Configuration folder.
Now, I suppose, it all depends on your definition of a 'gateway chassis', but there is a specific reason this is interesting.
I have a PLC (192.168.1.2) with a real gateway/router at (192.168.1.1), and lost of EIP I/O in the 192.168.1.xxx...all that works.
We are doing MSGing across this router, with success, to the other network.
I'd like to access an Ethernet/IP I/O device on another network, through the (192.168.1.1) gateway/router, and it doesn't work.
If I connect the device to the local network, and re-address it in the 192.168.1.xxx range (like the already-working local I/O), it works...which shows me the device is happy.
If I connect the device (reset to its address on the 'other' network, directly to the gateway's external network port, it still doesn't work...proving that its not a network infrastructure problem on the other network.
So, the real question for plcs.net is: Does all this sound right? More importantly, What is so different about a router/gateway accessed address, versus an address on the local network, that does not allow Ethernet/IP (for I/O) to work?