Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC 62026-1 Controller-Device Interface (CDI) General Requirements for LV Switchgear
Standard: IEC 62026-1 | Edition: 3.0 (2019) | Scope: Low-voltage switchgear and controlgear — Controller-device interfaces
💡 Core Value: IEC 62026-1 establishes the foundational requirements for controller-device interfaces (CDIs) in industrial automation. It provides a unified framework for AS-Interface, DeviceNet, CompoNet, and other fieldbus protocols, ensuring plug-and-play interoperability between controllers and field devices from different manufacturers — an essential enabler for Industry 4.0 and smart manufacturing.
1. Understanding Controller-Device Interfaces (CDIs)
IEC 62026-1 defines the general requirements for interfaces connecting programmable logic controllers (PLCs) to field devices such as sensors, actuators, contactors, circuit breakers, and motor starters within low-voltage switchgear and controlgear systems. A Controller-Device Interface (CDI) encompasses the physical layer, data link layer, and application layer specifications needed to enable deterministic communication between automation controllers and distributed I/O devices.
The standard is organized into multiple parts, each addressing a specific CDI protocol: Part 1 (General Requirements), Part 2 (AS-Interface), Part 3 (DeviceNet), Part 5 (Smart Distributed System — SDS), Part 6 (Seriplex), and Part 7 (CompoNet). Each sub-protocol offers distinct characteristics in terms of topology, data rate, message structure, and application suitability, allowing system designers to select the optimal network architecture for their specific use case.
🔧 Engineering Insight: When selecting a CDI protocol, evaluate node count, data payload size, real-time constraints, and environmental conditions. AS-Interface excels in bit-level sensor/actuator networks with up to 62 slaves and deterministic polling cycles under 5 ms. DeviceNet suits object-oriented, data-intensive applications with up to 64 nodes at 500 kbps. CompoNet handles high-density I/O scenarios with up to 384 nodes per segment.
2. AS-Interface Protocol Architecture and Implementation
AS-Interface (Actuator Sensor Interface), standardized as IEC 62026-2, is one of the most widely deployed fieldbus protocols at the sensor/actuator level. Its key innovation is a two-wire, unshielded cable that simultaneously carries both data and power (30 V DC, up to 8 A), dramatically simplifying field wiring. Each AS-i segment supports up to 62 slave devices, with the master performing cyclic polling for deterministic data exchange. The complete scan cycle for 62 slaves takes approximately 5 ms.
The AS-i telegram structure is remarkably lightweight: the master transmits 4 data bits (plus 4 parameter/control bits), and each slave responds with 4 data bits, resulting in a total telegram length of only 14 bits (including start, control, data, and stop bits). This minimalist design delivers exceptional real-time performance. From an engineering standpoint, AS-i networks support hot-swapping, automatic addressing, and IP67-rated field modules, making them highly suitable for harsh industrial environments with distributed I/O requirements.
⚠️ Common Misconception: Many engineers assume AS-i handles only discrete on/off signals. In reality, AS-i 3.0 supports analog data transmission (up to 16 bits per slave) and safety-related communication (AS-i Safety at Work, certified to SIL 3). Always verify master and slave version compatibility when integrating analog or safety modules.
| Parameter | AS-Interface | DeviceNet | CompoNet |
|---|---|---|---|
| Max. Nodes | 62 | 64 | 384 |
| Data Rate | 167 kbps | 125/250/500 kbps | 93.75 kbps — 4 Mbps |
| Max. Distance | 100 m (300 m with repeaters) | 500 m (@125 kbps) | 30 — 800 m (rate-dependent) |
| Physical Medium | 2-wire (data + power) | 5-wire (CAN_H/CAN_L/V+/V-/shield) | 4-wire (signal pair + power pair) |
| Data Exchange | Master polling | Multi-master / CAN arbitration | Master polling + STN |
| Typical Application | Sensors/actuators | Complex devices/drives | High-speed/density I/O |
3. DeviceNet and Industrial Network Integration
DeviceNet, specified in IEC 62026-3, is built on CAN (Controller Area Network) technology and supports object-oriented, multi-master communication. Unlike AS-Interface’s bit-level simplicity, DeviceNet offers both explicit messaging (connection-oriented, non-cyclic) and implicit messaging (cyclic I/O data transfer), making it suitable for applications ranging from simple discrete control to complex drive configuration and condition monitoring.
The Device Profile mechanism is central to DeviceNet interoperability. Every compliant device implements a standardized object model specific to its device type, including identity objects, connection objects, and parameter objects. This standardized model allows同类 devices from different manufacturers (e.g., variable-frequency drives, pneumatic valve manifolds, smart sensors) to be configured and monitored through a unified interface, significantly reducing integration effort.
Critical engineering considerations for DeviceNet installation include: proper termination resistors (120 Ω), stub length control, and power budget calculation. Trunk line length depends on data rate: up to 500 m at 125 kbps but only 100 m at 500 kbps. Power supply planning must account for each node’s current consumption and cable voltage drop; intermediate power tap modules may be necessary for large networks.
🔥 Critical Risk: The most common DeviceNet failures stem from missing or incorrect termination resistors, reversed power polarity, and CAN bus common-mode voltage exceeding the -2 V to +7 V range. Perform network health verification during commissioning using a DeviceNet analyzer tool (e.g., Rockwell NetTAX) to validate signal quality and bus timing.
4. Engineering Selection and Design Recommendations
Selecting the optimal CDI protocol requires multi-dimensional evaluation: (1) Node scale — small distributed I/O (<62 nodes) favors AS-Interface; high-density scenarios call for CompoNet; (2) Data payload — bit-level discrete signals suit AS-i, while byte-oriented complex data favors DeviceNet or CompoNet; (3) Real-time determinism — AS-i offers strictly deterministic polling cycles ideal for time-critical control, whereas DeviceNet’s CAN arbitration introduces non-deterministic latency under high bus load; (4) Environmental conditions — AS-i’s two-wire design provides significant wiring and maintenance advantages in IP67-rated installations.
For applications requiring functional safety (e.g., emergency stop, light curtain monitoring), consider CDI protocols with integrated safety communication. AS-Interface Safety at Work is TUV-certified to SIL 3; DeviceNet Safety also supports SIL 3 functional safety communication. Safety-related data is transmitted via the “black channel” principle, adding safety CRCs and timing monitoring on top of standard communication protocols.
❓ How does IEC 62026-1 relate to IEC 61158 (industrial communication networks)?
IEC 61158 is the umbrella standard for industrial communication networks covering the full protocol stack from physical to application layers. IEC 62026 series focuses specifically on controller-device interfaces within low-voltage switchgear and controlgear, addressing the device-level (sensor/actuator) layer. IEC 62026 complements IEC 61158 by providing domain-specific requirements for industrial automation’s lowest network tier.
❓ What is the maximum cable length for AS-i power supply?
Standard AS-i segments are limited to 100 m using 1.5 mm² cable. With repeaters/extenders, this extends to 300 m. For longer distances, AS-i fiber optic couplers or DSL remote extension solutions can reach several kilometers. Voltage drop is a critical concern: a 30 V supply at full load (8 A) may drop below 24 V at 100 m; use redundant power feeding or increase cable cross-section for large installations.
❓ What are CompoNet’s key advantages over DeviceNet?
CompoNet (IEC 62026-7) is optimized for high-density I/O: up to 384 nodes per segment (6x DeviceNet’s capacity), supports multiple topologies via STN and RTN architecture, and achieves cycle times below 1 ms. However, CompoNet’s device ecosystem is significantly smaller than DeviceNet’s — verify compatibility for intelligent devices such as drives and servo controllers before selection.
❓ Can AS-Interface and DeviceNet coexist in the same facility?
Yes, through gateways/couplers. A typical architecture uses a PLC on DeviceNet connecting multiple AS-i gateways, each managing an AS-i segment. AS-i data is mapped to DeviceNet implicit I/O messages at the gateway, making AS-i slaves appear as virtual devices on the DeviceNet bus. This hierarchical architecture is widely deployed in automotive manufacturing and material handling systems.
