The smart building of today requires connectivity to thousands of field devices — temperature sensors, humidity monitors, CO₂ detectors, occupancy sensors, energy meters, door contacts, motorised valves, lighting controls, and water leak detectors. Every one of these devices needs two things: a data connection to the building management system and power to operate. Providing both via four-pair Cat6A cabling to each individual sensor is economically absurd — 90% of the cable cost and installation labour goes toward bandwidth and power capacity that these tiny devices will never use.
Single-Pair Ethernet (SPE) was designed specifically for this problem. 10 Mbps over two conductors to 1,000 metres is sufficient for every data acquisition device in a building. PoDL (Power over Data Line) over those same two conductors provides up to 52W — far more than any sensor or actuator requires. And the cable itself — a thin, light two-conductor twisted pair — costs 55–70% less than Cat6A per metre and takes up a fraction of the conduit space.
SPE Standards Variants Comparison
| Standard | Speed | Max Distance | Topology | PoDL | Typical Application |
|---|---|---|---|---|---|
| 10BASE-T1S (IEEE 802.3cg) | 10 Mbps | 25 m | Multidrop bus (up to 8 nodes) | Yes | Automotive, industrial bus segments |
| 10BASE-T1L (IEEE 802.3cg) | 10 Mbps | 1,000 m | Point-to-point | Yes (52W) | Building IoT sensors, BMS field devices |
| 100BASE-T1 (IEEE 802.3bw) | 100 Mbps | 15 m | Point-to-point | Limited | Automotive in-vehicle networks |
| 1000BASE-T1 (IEEE 802.3bp) | 1 Gbps | 40 m | Point-to-point | No | Automotive backbone, short industrial |
| APL (Advanced Physical Layer) | 10 Mbps | 1,000 m | Point-to-point (ATEX variant) | Yes (IEC certified) | Oil & gas, chemical, ATEX Zone 1/2 |
SPE for Building IoT: Technical Design
- IEC 63171-6 SPE connector: Standardised IP20 and IP67 SPE connector — compact, keyed, and polarity-safe. Different from RJ45 — all devices must carry IEC 63171-6 connectors for SPE connectivity
- PoDL power classes: Class 10 (= 10W PD), Class 13 (= 26W), Class 14 (= 52W at PSE) — configurable per port on SPE PSE switches, with power negotiation between PSE and PD devices per IEEE 802.3cg
- BACnet/IP over SPE: Building automation protocols (BACnet, MODBUS TCP, PROFINET, OPC UA) run directly over 10BASE-T1L IP links — no gateway required. SPE switch aggregates all sensor IP addresses to the BMS over standard Ethernet uplink
- Cable specification for 1000m: AWG 24–26 twisted pair, shielded (STP) recommended for 1000m runs in buildings with high EMI (near VSD drives, fluorescent lighting). Unshielded acceptable in low-EMI environments up to 500m
- Fieldbus replacement path: For existing BACnet MS/TP or Modbus RS-485 installations, SPE gateway devices (Moxa, HMS Networks) bridge legacy fieldbus segments to SPE/IP — enabling phased migration without full device replacement
- SPE switch infrastructure: SPE PSE switches (Siemens SCALANCE XC, Moxa EDS-P series, Hirschmann) aggregate multiple SPE device connections to standard PoE Ethernet uplink — fitting in standard IDF cabinets alongside the Cat6A infrastructure
SPE Replacing Every Fieldbus: The All-IP Smart Building Sensor Network
SPE is poised to replace remaining proprietary fieldbus protocols (PROFIBUS, Modbus RS-485, BACnet MS/TP, KNX TP) in building automation by 2030 — consolidating the entire building sensor and actuator network onto a single IP-based physical layer standard. As SPE-native chipsets drop below $0.30 per device port in volume production, every temperature sensor, occupancy detector, door contact, and energy meter will be directly IP-addressed over SPE with no gateway or protocol conversion required. The building's IP network extends to every physical point in the building envelope. Smart city programmes in India (Smart Cities Mission) that are deploying city-wide IoT sensor networks at unprecedented scale will find SPE the most economical wired medium for sensor connectivity beyond the limitations of wireless (reliability, battery life, penetration) and conventional Ethernet (cost at IoT device scale).