what is controlnet?

ControlNet is a deterministic industrial communication network designed for time-critical I/O, controller-to-controller communication and industrial automation systems. It uses CIP — Common Industrial Protocol at its upper layers and belongs to the same CIP network family as DeviceNet and EtherNet/IP.
In simple terms: ControlNet allows a PLC to exchange data with remote I/O, other controllers, drives and automation devices at predictable time intervals. Its key advantage is not simply raw speed, but its ability to reserve communication time and network bandwidth for important control data.
How does ControlNet work?
ControlNet uses a time-controlled media-access mechanism known as CTDMA — Concurrent Time Domain Multiple Access. Instead of allowing time-critical messages to compete unpredictably for access to the network, ControlNet divides communication into repeating time intervals.
These intervals are called NUT — Network Update Time. Within each NUT, network time is divided into a scheduled section for deterministic control data and an unscheduled section for configuration, programming, diagnostics and other less time-critical messages.
This architecture made ControlNet particularly useful for remote I/O, controller interlocks and other applications where predictable data delivery was more important than simply having the highest possible network bandwidth.
What is NUT — Network Update Time?
Network Update Time is the repeating communication cycle used by ControlNet. It establishes the basic time interval in which scheduled network communication is organized.
ControlNet systems can typically use NUT values from approximately 2 ms to 100 ms, depending on the controller and network configuration.
A smaller NUT provides more frequent scheduled update opportunities, but it can also reduce the amount of data that can be scheduled in each cycle. Network timing therefore needs to be designed around the actual I/O load and update requirements rather than simply selecting the smallest possible value.
What are Scheduled and Unscheduled communication?
Scheduled traffic is network communication for which time and bandwidth have been reserved in advance. Typical examples include remote I/O data, controller interlocks and time-sensitive process values.
Unscheduled traffic is used for operations such as controller programming, diagnostics, device configuration and other messages that do not require the same deterministic timing.
Separating these traffic types helps prevent engineering or diagnostic messages from unexpectedly delaying critical I/O communication. This is one of the key differences between ControlNet and a general-purpose shared network.
What speed does ControlNet use?
ControlNet operates at a fixed data rate of 5 Mbit/s. Unlike DeviceNet, there is no choice between 125, 250 and 500 kbit/s.
Five megabits per second is not considered high bandwidth compared with modern Ethernet. The historical strength of ControlNet is its deterministic scheduling and predictable control communication, not higher raw speed than Ethernet.
Which cable does ControlNet use?
Classic ControlNet installations commonly use 75 Ω RG-6 quad-shield coaxial cable. Devices connect to the coax trunk through dedicated passive ControlNet taps.
Standard IP20 coax installations commonly use BNC connectors. Ruggedized installations can use TNC-style connections, and fiber-optic repeaters can be used where longer distance, electrical isolation or immunity to electromagnetic interference is required.
ControlNet should therefore not be confused with Ethernet. The classic ControlNet trunk does not use standard Ethernet twisted-pair ports or Ethernet switching.
How is ControlNet terminated?
A coaxial ControlNet segment requires a 75 Ω termination resistor at each physical end of the trunk segment. These resistors reduce signal reflections at the ends of the coaxial cable.
Termination is not installed at every device. Each permanent node normally connects through a ControlNet tap, while the two terminators remain at the ends of the segment.
When intermittent network errors occur, incorrect or missing terminators, damaged RG-6 cable, poor BNC connections and faulty taps should be among the first physical-layer checks.
How far can a ControlNet coax segment run?
The permitted coaxial segment length depends on the number of taps installed on that segment.
With only two taps, standard RG-6 ControlNet coax can reach approximately 1000 m — 3280 ft.
As additional taps are installed, the allowable cable length decreases. With the classic maximum of 48 taps on one coax segment, the permitted standard RG-6 trunk length is approximately 250 m — 820 ft.
Repeaters and fiber links can be used to create larger networks from multiple physical segments. For this reason, neither “ControlNet is limited to 250 m” nor “ControlNet always supports 1000 m” is correct without considering the segment layout.
How many nodes can ControlNet support?
ControlNet supports up to 99 network nodes. Each device must have a unique ControlNet node address.
A single coaxial segment has a lower physical tap limit, traditionally up to 48 taps. Repeaters can connect additional segments while still forming one ControlNet link.
Duplicate node addresses can prevent correct network operation, so node addressing should always be checked when replacing or commissioning a ControlNet module.
Does ControlNet use IP addresses or TCP/UDP ports?
No. ControlNet is not an Ethernet/TCP/IP network. Normal ControlNet communication therefore does not identify devices using IP addresses or TCP/UDP port numbers.
ControlNet devices are identified through their network node addresses. This is fundamentally different from EtherNet/IP, which uses Ethernet and IP networking.
A ControlNet module may have other service or backplane interfaces depending on the product, but those should not be confused with the physical ControlNet network itself.
What is the difference between ControlNet and Ethernet?
Older descriptions sometimes claim that ControlNet is faster than Ethernet. That is no longer technically meaningful. ControlNet operates at 5 Mbit/s, while modern Ethernet commonly operates at 100 Mbit/s, 1 Gbit/s or much higher speeds.
The more useful distinction is network architecture. ControlNet was specifically designed around deterministic scheduled control traffic. Ethernet is a general networking technology that has evolved into the dominant physical infrastructure for both information systems and industrial automation.
Modern industrial Ethernet systems can also support real-time automation using switched networks, traffic prioritization, synchronization and industrial application protocols. Ethernet is therefore not limited to office or home networks.
What is the relationship between ControlNet and EtherNet/IP?
ControlNet and EtherNet/IP share CIP — Common Industrial Protocol at their upper layers. This gives them related object, connection and producer-consumer communication concepts.
Their physical and data-link networks are different. ControlNet uses its dedicated 5 Mbit/s CTDMA network, while EtherNet/IP uses standard Ethernet together with IP-based networking technologies.
The common CIP architecture made it possible to integrate older ControlNet systems with newer EtherNet/IP architectures through suitable controllers, bridges and gateways.
What is the difference between ControlNet and DeviceNet?
ControlNet and DeviceNet are both members of the CIP family, but they were designed for different levels of an automation system.
DeviceNet is a CAN-based field-level network operating at 125, 250 or 500 kbit/s. It has traditionally connected sensors, actuators, remote I/O and smaller field devices and can also distribute 24 VDC network power to suitable equipment.
ControlNet operates at 5 Mbit/s and was designed for deterministic controller-level communication, larger I/O systems and peer-to-peer interlocks.
The difference should therefore not be reduced to “ControlNet is fast and DeviceNet is slow.” Their physical technologies, network roles and installation architectures are different.
Does ControlNet support redundant media?
Yes. ControlNet can support redundant network media on compatible hardware. The same network can be provided through two independent physical channels, commonly referred to as channels A and B.
If one physical media path fails, compatible redundant-media devices can continue communicating through the remaining path. This can improve availability in process and production applications where a single cable failure would otherwise stop communication.
Redundant communication media does not automatically make the entire machine or process fault tolerant. Controller power, I/O modules, power supplies and other single points of failure still need to be considered separately.
Does ControlNet provide cybersecurity?
ControlNet's deterministic timing and media redundancy should not be confused with cybersecurity. Predictable communication does not mean that ordinary ControlNet traffic is encrypted or cryptographically authenticated.
The classic ControlNet network should therefore not be described as having an automatic security feature comparable to modern authentication, encryption or firewall technologies.
Legacy ControlNet systems should be protected through appropriate industrial network segmentation, controlled engineering access, physical security and secure gateway design where they interface with Ethernet or enterprise networks.
Where is ControlNet used?
ControlNet has been widely used in large remote-I/O systems, process plants, manufacturing lines, material-handling systems, packaging equipment and controller-to-controller communication.
A typical installation may connect a controller to distributed I/O racks, motor drives, instrumentation and other controllers over the same deterministic network.
An HMI, engineering station or SCADA system can also access ControlNet-connected control systems through appropriate communication modules or bridges.
Is ControlNet still used today?
Yes. EtherNet/IP is much more common in new projects, but a substantial installed base of ControlNet systems remains in operating industrial plants.
ControlNet also remains part of ODVA's current CIP specification library. As of April 2026, the ControlNet Adaptation of CIP is listed as Volume 4, Version 1.9.
Modernization from ControlNet to EtherNet/IP is common, but a working ControlNet installation should not be replaced solely because the network is older. Spare-parts availability, production downtime, controller platform, engineering effort and lifecycle cost all need to be considered.
Why does ControlNet communication fail?
Troubleshooting should begin with the physical network. Inspect the coax cable, BNC connections, taps and the 75 Ω terminators at both ends of each segment.
Next verify node addresses. Every node must have a unique address, and duplicate addresses can prevent normal communication.
If the physical layer is healthy, inspect the NUT configuration, scheduled network configuration, keeper status and I/O connections. Adding or changing scheduled I/O can require the ControlNet network schedule to be updated.
If unscheduled programming messages work but scheduled I/O does not, the problem may be related to network scheduling rather than the coax cable itself.
Practical ControlNet troubleshooting checklist
1. Are 75 Ω terminators installed at both physical ends of the coax segment?
2. Are the BNC connectors, taps and RG-6 trunk cable in good condition?
3. Does every network device have a unique ControlNet node address?
4. Are tap count and cable length within the permitted segment limits?
5. If redundant media is used, are both channels healthy?
6. Is the configured NUT appropriate for the scheduled I/O load?
7. Was the network schedule updated after changes to scheduled I/O?
8. What do the diagnostic indicators on the controller, adapter and ControlNet modules show?
Related Industrial Communication Guides
Industrial Communication · Ethernet · EtherNet/IP
Related Automation Pages
PLCs · HMI Panels · SCADA · AC Drives and VFDs · Sensors