Ethernet IP on Compact / Controllogix Vs. SLC 5/05

Tim Ganz

Member
Join Date
Dec 2010
Location
Dallas, Texas
Posts
685
Can someone help me understand in detail the differences and limitations between Ethernet IP on a Compact / Controllogix Controller and Ethernet IP on a SLC 5/05 controller please.
 
It’s really not so much as the difference between a Logix controller and a SLC but rather a difference between two different protocols, Ethernet/IP TCP and Ethernet/IP UDP. The Logix processors will do both and the SLC’s and MicroLogix will only do TCP.
Ethernet/IP UDP also known as “Produce/Consume” and/or “Implicit messaging” is a continuous connection where one device “produces” the data and the other device “consumes” it. It’s considered “real time” data and doesn’t require anything in the ladder logic (no message instructions) to operate.
Ethernet/IP TCP also known as “explicit messaging” is a process where one device uses a message instruction to exchange data with another device. A connection is opened and established, the data is exchanged and the connection is closed.
UDP is faster and because you don’t have to write message instructions is more popular than TCP however it is very sensitive to the health of the connection and isn’t “wireless friendly” meaning while you can do it wirelessly you have to be careful.
TCP is slower (by milliseconds not seconds) and requires writing message instructions but it is far more robust especially when (if) you go wireless.
 
It’s really not so much as the difference between a Logix controller and a SLC but rather a difference between two different protocols, Ethernet/IP TCP and Ethernet/IP UDP. The Logix processors will do both and the SLC’s and MicroLogix will only do TCP.
Ethernet/IP UDP also known as “Produce/Consume” and/or “Implicit messaging” is a continuous connection where one device “produces” the data and the other device “consumes” it. It’s considered “real time” data and doesn’t require anything in the ladder logic (no message instructions) to operate.
Ethernet/IP TCP also known as “explicit messaging” is a process where one device uses a message instruction to exchange data with another device. A connection is opened and established, the data is exchanged and the connection is closed.
UDP is faster and because you don’t have to write message instructions is more popular than TCP however it is very sensitive to the health of the connection and isn’t “wireless friendly” meaning while you can do it wirelessly you have to be careful.
TCP is slower (by milliseconds not seconds) and requires writing message instructions but it is far more robust especially when (if) you go wireless.

That makes a lot more sense now. I think I have a good grasp on it now. Thanks for the help Firejo I greatly appreciate it.
 

Similar Topics

It may look as a stupid question but I have to confirm (Put my head on the table to being cut if i'm wrong...just an image) that my micrologix...
Replies
1
Views
4,167
I have a CompactLogix 5280 a I am trying to figure out which of the Ethernet ports are A and B. Not finding it in the manual and this is a new...
Replies
2
Views
1,189
Here is me again with a question that I am suspecting the answer is NO I have a 1769-L33ER that already has some Ethernet/IP devices attached...
Replies
12
Views
4,334
Dear all Can any one guide me for mapping in compact logix in RS Logix 5000 which I will be using MOXA MB Gate 5105 for converting Ethernet IP to...
Replies
1
Views
1,526
Hi all, Im having issues connecting a CompactLogix L33ER using Ethernet to a ProTalk P2 callout unit. From everything I found online I seem to...
Replies
0
Views
942
Back
Top Bottom