Talk:EtherNet/IP

Needs help
Introductory material: It may be necessary to separate marketing jargon from technical explanation. The very name "Ethernet/IP" is extremely misleading as it implies some relationship with the hardware standard Ethernet while IP is easily confused by beginners with the link layer of TCP/IP. Neither have any relevance since Ethernet/IP sits above the TCP layer. A short discussion of Event-driven programming would also help the unitiated to understand both how it works and how it may be classified. —Preceding unsigned comment added by 167.211.65.80 (talk) 20:06, 8 September 2008 (UTC)


 * Oh yes, please do. And add citations too. W Nowicki (talk) 23:35, 14 October 2011 (UTC)

"Multicast/broadcast communication over TCP" is nonsense
The article claims ENIP would enable "multicast/broadcast communication over TCP". This is nonsense. TCP is connection-based and can thus be used only for unicast communication. Truth is, ENIP enables multicast over UDP. ODVA: "For real-time messaging, EtherNet/IP also employs UDP over IP, which allows messages to be multicast to a group of destination addresses." ODVA --Dinarsad (talk) 06:36, 26 November 2013 (UTC)


 * I changed that statement from TCP to IP. ~KvnG 00:15, 30 November 2013 (UTC)
 * Thanks. --Dinarsad (talk) 14:42, 30 November 2013 (UTC)

Reference to CIP
I'm a little surprised that this article doesn't talk about CIP. Ethernet/IP is just a terribly named port of CIP to Ethernet that has been cleaned up a little over the years. I'm a Wikipedia newbie or I'd do this myself (I limit myself to talk pages for now). — Preceding unsigned comment added by 50.78.52.249 (talk) 22:00, 17 December 2013 (UTC)
 * Welcome to Wikipedia. Feel free to create an account and jump in and make some edits. I'll keep an eye on this page and refrain from biting. ~KvnG 20:18, 21 December 2013 (UTC)

Not hard real-time nor deterministic
Ethernet/IP is event driven and you can argue that it is soft real-time (it certainly isn't hard real-time), but it most certainly is not, in any way, deterministic. The wording in the description currently implies that it is quasi-deterministic and also implies its shortcomings come from the physical layer of Ethernet (which is completely false). The description should clarify the basic operation of the protocol and can certainly tout speed advantage over standard TCP/IP sockets and general repeatability. I feel it is misleading as it is now. 50.78.52.249 (talk) 22:25, 17 December 2013 (UTC)