Industries / Industrial equipment and services / IoT and industrial automation / Industrial controls and PLCs
Networks
Controller networks carry inputs, outputs and commands between a controller and its sensors, drives and other controllers, on a timetable the machine depends on.
5
Milestones achieved, from 1994 to 2026.
1
To watch for: announced, not yet confirmed outside.
2
Open deliverables. Nobody has shipped them.
The road
AchievedWatch forOpen
Achieved
1994
A factory network from cars
Allen-Bradley introduced DeviceNet in 1994 to connect its PLCs, distributed inputs and outputs and motor control centres, building it on CAN, the serial bus that Bosch had developed for cars, Manufacturing AUTOMATION reported in 2011. In HMS Networks' 2026 count, DeviceNet, CC-Link and CAN/CANopen each make up 1 to 2% of newly installed factory nodes.
Credit
Allen-Bradley
2006
A data storm stops pumps
On 19 August 2006 operators at Unit 3 of the Tennessee Valley Authority's Browns Ferry nuclear plant in Alabama shut the reactor down by hand after the controllers of both reactor recirculation pumps stopped responding. The US Nuclear Regulatory Commission blamed "excessive traffic" on the plant's control-system Ethernet network, apparently from a malfunctioning PLC on the same network, and the plant added firewalls in front of its controllers.
LessonA controller on a shared network can be stopped by another device's traffic, so each needs a limit on what reaches it.
Credit
TVA; the NRC, in Information Notice 2007-15
2014
Devices tested under traffic
Certification of PROFINET devices by PROFIBUS & PROFINET International (PI) includes a netload test, which floods a device with network traffic under common conditions and rates its robustness in classes. Softing reported in January 2014 that its PROFINET implementation had passed Class III, the highest. PI later renamed the test "Netload Robustness for Security" and in 2022 extended it to Ethernet-APL at 10 Mbit/s.
Credit
PROFIBUS & PROFINET International
2023
Sparkplug becomes a standard
Sparkplug sets out how controllers and edge devices publish data over MQTT, a lightweight publish-and-subscribe messaging protocol, with "birth and death certificates" that tell a listener whether a device's data is current. It became an Eclipse Foundation project in 2019, and in November 2023 ISO and IEC published version 3.0 as ISO/IEC 20237, the first Eclipse specification to become an international standard.
Credit
the Eclipse Sparkplug Working Group; ISO/IEC JTC 1
2026
Ethernet takes four in five
HMS Networks, a Swedish maker of network gateways, estimates in its 2026 study that Industrial Ethernet made up 79% of newly installed factory nodes, up from 34% in its first study in 2015. PROFINET, EtherNet/IP and EtherCAT together held about three-quarters of the wired market, at 30%, 25% and 20%; older fieldbuses fell to 14% of new nodes, and PI's own figures show new PROFIBUS nodes falling from 1.1 million in 2024 to 1.0 million in 2025.
Credit
HMS Networks, which measured it
Watch for
One network to the drive
OPC UA FX (Field eXchange) extends OPC UA so that controllers, drives and input and output modules from different makers exchange data directly and on a fixed schedule, using time-sensitive networking. B&R, ABB's machine automation division, says its PLCs and industrial PCs already support FX controller-to-controller (C2C) communication, and that its ACOPOS M4 is "one of the first servo drives in the world" built natively on OPC UA FX. In June 2026 the OPC Foundation said the controller-to-device (C2D) specification was still being prepared as a release candidate, with a multi-vendor demonstration planned for the SPS trade fair in Nuremberg in November 2026.
Achieved whenthe C2D specification is released and an outside party reports drives and I/O from at least three makers running a machine on it.
Claimed by
B&R, November 2025; OPC Foundation, June 2026
Open
01
Flood tests, model by model
A repeat of the 2018 flood tests on controllers sold today, with every model named, the traffic rates in frames per second at which its outputs slow or stop or its connections drop, how long it takes to recover, and whether its program survives, measured the same way for every model and rerun when new firmware ships.
The briefCredit · unclaimed02
From fieldbus capture to config
A tool that listens passively to a running PROFIBUS DP or DeviceNet network on a bench, lists every device and the data it exchanges, and writes a draft configuration for the replacement Ethernet network (PROFINET or EtherNet/IP), checked by running the bench network both ways.
The briefCredit · unclaimed
Open 01 · the brief
Flood tests, model by model
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
A repeat of the 2018 flood tests on controllers sold today, with every model named, the traffic rates in frames per second at which its outputs slow or stop or its connections drop, how long it takes to recover, and whether its program survives, measured the same way for every model and rerun when new firmware ships.
Why it is still open
The 2018 study covered 16 devices from six makers with the firmware of that year, and one of its authors, Matthias Niedermaier, said that researchers "only have a few devices and cannot investigate the huge amount of PLCs." PROFINET's netload test rates devices only by class, as part of certification, and its guideline is open to PI members only.
Built with what exists
current and second-hand PLCs and remote I/O on a bench, with no machinery connected; the method published by the 2018 authors; open-source traffic generators such as hping3, Ostinato or Cisco's TRex; a managed switch with a mirror port; Wireshark to record traffic; a logic analyzer on an output toggled every cycle.
First step
Connect one current PLC to a switch, toggle an output every cycle, raise broadcast traffic in steps of 1,000 frames per second and record the rate at which the toggle slows or stops.
Done looks like
At least 20 models from at least six makers, all on sale in 2026, each with the broadcast, multicast and unicast rates at which outputs stop or connections drop, the recovery time and whether the program survived, with the test scripts and raw timings published.
Open 02 · the brief
From fieldbus capture to config
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
A tool that listens passively to a running PROFIBUS DP or DeviceNet network on a bench, lists every device and the data it exchanges, and writes a draft configuration for the replacement Ethernet network (PROFINET or EtherNet/IP), checked by running the bench network both ways.
Why it is still open
PI's guidance for existing plants is a step-wise move in which proxies keep PROFIBUS devices running behind a PROFINET gateway, and searches found migration tools that start from an existing project file, not from the traffic on the bus. The base waiting to move is large: older fieldbuses still made up 14% of new nodes in 2026, and PI counted 1.0 million new PROFIBUS nodes in 2025.
Built with what exists
a PROFIBUS or CAN capture interface; makers' device description files (GSD for PROFIBUS, GSDML for PROFINET, EDS for DeviceNet and EtherNet/IP); AI models to match captured data to device manuals; second-hand fieldbus devices for the bench.
First step
Capture a three-device PROFIBUS DP network on the bench and produce a list of each device's address, its GSD identity and the bytes it sends and receives each cycle.
Done looks like
For five bench networks of at least ten devices each, the tool's draft configuration matches the hand-built one on every device and data item, or the differences are listed and explained.