Edge Gateway Lab, Part 1: Why Does This Beckhoff Controller Have Nine Ethernet Ports?
A practical look at a Beckhoff controller as a multi-network industrial edge platform.
A PLC with an unusual amount of networking
Figure 1. Beckhoff controller with nine front-panel Ethernet ports.
I recently picked up the Beckhoff controller shown above. My first reaction was straightforward: what kind of conventional PLC needs nine Ethernet ports? Once I powered it up, however, the hardware started to make more sense. The platform has generous Ethernet connectivity, CPU capacity, and memory for an industrial controller.
Figure 2. Windows Device Manager shows one Intel I219 interface and eight Intel I210 Gigabit Ethernet interfaces.
Figure 3. The test system running Windows 10 Enterprise LTSC on Beckhoff hardware.
The edge-gateway use case
Beckhoff describes the platform as suitable not only for a wide range of automation tasks, but also for use as an IoT gateway or edge controller.
Viewed as a conventional PLC, nine Ethernet ports seem excessive. Viewed as a compact industrial server positioned between multiple networks, the design makes much more sense. The same machine can run control and data acquisition, connect legacy equipment while normalizing and forwarding data to newer systems, and host services such as a web-based HMI, MQTT, logging, or remote-maintenance tools.
A colleague was using this type of hardware to test an industrial gateway application, which is a logical use case. A gateway does not really live on one network; it sits between several networks and moves data across those boundaries.
Why RT Linux changes the picture
That leads to the next question: how many purpose-built industrial gateways would you choose to run on Windows? The current-generation product information lists support for TwinCAT/BSD and Beckhoff RT Linux. That is much closer to what I would expect from an industrial edge platform.
To me, Beckhoff's move toward RT Linux reflects a broader trend. Industrial control is gradually adopting software-defined architectures, containers, and virtualization. Over time, the TwinCAT runtime may become one core service on an IPC, while the same platform also runs data acquisition, protocol conversion, visualization, remote support, machine vision, and AI workloads. The industrial PC of the future may be less of a “computer that runs a PLC” and more of a unified industrial computing platform for control, data, and edge applications.
Planned lab sequence
Since I already have the hardware, I am going to put it through a proper bench evaluation. The plan is:
1. Install Beckhoff RT Linux and verify that the operating system boots and runs correctly.
2. Validate the basic platform functions—storage, display output, and SSH—and confirm that all nine Ethernet ports can be detected, mapped, configured, documented, and maintained.
3. Bring up the TwinCAT runtime.
4. Integrate Node-RED and FUXA to build a small end-to-end industrial edge-gateway demonstration.
Figure 4. Lab hardware and Beckhoff components prepared for the gateway test. Figure 5. Beckhoff RT Linux documentation used for the next stage of the evaluation.
