Bringing single-pair Ethernet for constrained devices to the industrial network edge means solving a different problem from connecting a controller or high-performance drive. In-cabinet devices such as push buttons, indicators and contactors must fit tight cost, size and power budgets. At the same time, manufacturers want to reduce hardwiring and connect more devices to a common Ethernet-based architecture.
A 2020 ODVA Industry Conference paper proposed an approach built around IEEE 802.3cg 10BASE-T1S and a simplified EtherNet/IP communication profile. Its central idea is to combine multidrop Ethernet with power distribution and streamlined device communications, making networked pilot devices more practical without assuming they need the features of larger industrial nodes.
Why bring Ethernet into the control cabinet?
Industrial Ethernet has expanded across automation systems, but many field devices still rely on point-to-point wiring or separate fieldbus and sensor networks. For cabinet components, hardwiring can mean substantial control-power wiring, lengthy commissioning and more effort when troubleshooting or changing equipment. A hardwired device may also provide little network data for monitoring or analysis.
A harmonized Ethernet and IP-based network can reduce reliance on application-level gateways and simplify integration with existing network infrastructure. It can also create a more consistent basis for device management and connectivity to higher-level systems. Those benefits depend, however, on making the edge device economical and straightforward to install—not merely giving it a conventional Ethernet port.
What 10BASE-T1S brings to constrained devices
IEEE 802.3cg-2019 introduced two 10 Mbit/s single-pair Ethernet physical-layer options. 10BASE-T1L targets longer-reach applications, while 10BASE-T1S addresses shorter-reach, lower-cost applications, including multidrop networks. The T1S multidrop option can support a shared link up to 25 metres, with PHY-level Collision Avoidance (PLCA) providing a deterministic method for managing access to the medium.
For in-cabinet devices, the appeal is not maximum bandwidth. It is the potential to connect multiple nodes over a shared medium while keeping device electronics small and low power. The paper identifies 10 Mbit/s, half-duplex communication and a constrained Ethernet stack as a possible fit for pilot devices with modest communication requirements and limited memory.
The proposed cabinet architecture uses a multi-conductor cable rather than treating the Ethernet signal pair as the only wiring needed. The described cable allocates conductors for:
- One pair for the 10BASE-T1S signal.
- One pair for network power to device communication electronics.
- One pair for switched or control power for loads such as contactor coils.
- One select-line conductor intended to support sequential network servicing and discovery of the linear node topology.
A gateway connects the multidrop segment to a controller and supplies network and switched power. If the gateway cannot provide enough switched power for connected loads, the concept uses a supplemental power tap. Separating network power from switched power helps address the different needs of communication circuitry and output loads within the proposed arrangement.
Simplifying EtherNet/IP for constrained nodes
Physical-layer changes alone do not make a device suitable for a tight hardware budget. The paper also describes a proposed constrained EtherNet/IP profile that reduces communication-stack requirements. Instead of requiring the full set of EtherNet/IP transports, a UDP-only profile would transmit CIP messages over UDP, avoiding TCP connections and encapsulation sessions.
The profile concept retains selected communication functions while minimizing implementation overhead. The paper describes support for unconnected messaging and Class 1 communications, alongside a reduced implementation of base device objects and optional features. Capability discovery would let a device report its supported EtherNet/IP transport profile through identity-related information, helping network tools distinguish constrained devices from devices using the full transport profile.
Security was also part of the proposal. Because UDP-only communications do not use TCP, the paper proposed optional DTLS-only support for CIP communications in a CIP Security context. These details describe work and concepts presented in 2020; they should not be read as a statement that every proposed profile or implementation is part of a current specification.
Design trade-offs for integrators and device makers
The engineering challenge is balancing installation simplicity with the constraints of small devices. A common, keyed connector and shared cable could reduce wiring effort, while the additional power and select-line conductors mean the media is more than a conventional two-conductor Ethernet cable. System designers need to consider how the cable, connector, power distribution and topology work together.
Device electronics also influence cost and package size. The paper compares three PHY integration approaches: a PHY with an MII interface, a PHY with an SPI interface and integrated MAC-related functions, or a PHY and microcontroller combined in one chip. The MII approach can require more signal connections and a more capable microcontroller; SPI was identified as a preferred direction for constrained devices. A single-chip option could reduce package size, but it must provide an appropriate balance of processing, memory and security features.
For system integrators, the practical questions include:
- Can the device meet its power and thermal limits on the intended segment?
- How will network power and switched power be supplied and extended?
- Does the cable and connector arrangement suit the cabinet layout and installation process?
- How will devices be discovered, commissioned and maintained?
- Which communication and security functions are required for the application?
Conclusion: a path from hardwiring to networked edge devices
Single-pair Ethernet for constrained devices is best understood as a system design challenge, not simply a new cable choice. The 10BASE-T1S multidrop PHY provides a potential communications foundation; a purpose-designed media and power arrangement addresses cabinet wiring; and a reduced EtherNet/IP profile aims to fit limited device resources.
For automation engineers and plant decision-makers, the practical implication is a possible way to network small cabinet components without requiring every node to implement a full-featured Ethernet stack. Whether that approach suits a given application depends on its power needs, device cost, installation requirements, topology and communication profile. Evaluating those elements together is essential to realizing the intended reduction in hardwiring and commissioning complexity.