EtherNet/IP
ODVA's adaptation of CIP to standard Ethernet and TCP/IP, used for cyclic I/O, controller-to-controller data, and configuration traffic.
The network analogy
CIP carried in ordinary TCP and UDP: explicit messages are request/reply over TCP, and cyclic I/O is a UDP stream, unicast or multicast.
Why it matters for wireless
Cyclic I/O rides UDP on a fixed interval, so the radio's job is to deliver each packet before the connection timer runs out, not just eventually.
ODVA says EtherNet/IP uses CIP for its upper layers and runs on standard, unmodified Ethernet. Devices accept explicit messaging over TCP on port 0xAF12 (44818)1 and exchange I/O over UDP on port 0x08AE (2222), unicast or multicast. I/O connections run at a configured RPI and time out after a multiple of it.
ODVA concedes that Ethernet has its roots in the office and gets its determinism from switched, full-duplex links. A radio channel is a commonly shared medium, which is the difference the wireless design has to absorb.
About this page
Built from 3 sources: 3 protocol owners and alliances. Researched and drafted with AI assistance, then reviewed and approved by Ben Rutter on . How pages are made
- First published
- Last updated
Cite this page
Plain
Ben Rutter. "EtherNet/IP." OT Wireless, published October 5, 2026. https://otwireless.com/glossary/ethernet-ip/
APA 7
Rutter, B. (2026, October 5). EtherNet/IP. OT Wireless. https://otwireless.com/glossary/ethernet-ip/
BibTeX
@misc{rutter2026ethernetip,
author = {Rutter, Ben},
title = {{EtherNet/IP}},
year = {2026},
howpublished = {\url{https://otwireless.com/glossary/ethernet-ip/}},
organization = {OT Wireless},
}