Building a Sensor Dashboard with Node-RED and MQTT
Read more...
Single Pair Ethernet brings Ethernet links to sensors over one balanced copper pair. Plan the rollout around the link that fits the installation. The SPE System Alliance describes long point-to-point 10BASE-T1L links and short shared 10BASE-T1S segments; both operate at 10 Mbit/s, but they solve different wiring problems (SPE System Architecture, 2025).
An SPE label starts the specification. Before ordering equipment, define the topology, application protocol, power arrangement, cable channel and acceptance tests. This guide turns those choices into a pilot plan. For the wider communication-stack decision, see our IIoT protocols comparison.
TL;DR: Choose SPE by the channel you need. The SPE System Alliance describes 10BASE-T1L links up to 1,000 m under specified conditions, while T1S supports short shared segments. Qualify cable, power and application compatibility separately. Prove one representative installation before repeating the design across a sensor network.
SPE changes the Ethernet connection toward the field; it does not select the application protocol. The SPE System Alliance separates physical-layer choices from the protocols they carry, including its 10 Mbit/s options. The rollout must preserve compatibility above the link and meet the channel requirements below it (architecture whitepaper, sections 3–4).
Write the requirement in layers. Name the industrial protocol the controller and sensor must support. Then name the Ethernet PHY, the power interface, the connector arrangement and the channel limits. Avoid a purchase description that says only “SPE compatible.” The supplier then has to infer the intended installation.
Our PROFINET versus EtherNet/IP guide addresses a separate choice in that specification. Selecting one of those application environments does not remove the need to select the physical link.
A useful procurement check is to ask two questions separately: “Will these ports communicate?” and “Will this sensor work in our control application?” Record an answer for each. Treat the pair as an acceptance requirement, rather than accepting a demonstration of connectivity as the whole result.
Choose 10BASE-T1L for a long point-to-point channel; consider T1S when a short shared segment fits the design. The SPE System Alliance gives T1L a reach up to 1,000 m and describes a T1S baseline of at least eight nodes across 25 m. Those T1S figures are not universal maxima (architecture whitepaper, sections 3–4).
| Option | Connection arrangement | Figure to interpret carefully | Design question |
|---|---|---|---|
| 10BASE-T1L | Point-to-point | Up to 1,000 m under specified channel conditions | Does the complete channel meet the chosen equipment's requirements? |
| 10BASE-T1S multidrop | Shared half-duplex segment | 10 Mbit/s shared; baseline support for at least eight nodes over 25 m | Does the selected implementation support the intended nodes, wiring and traffic? |
| Ethernet-APL | Process-specific switched connections using T1L | Spurs up to 200 m; unpowered trunks up to 1,000 m per segment | Do port profiles, power and installation conditions match? |
The APL figures come from the Ethernet-APL Engineering Guideline, version 1.11. Powered trunk length depends on load and cable design. Keep trunk and spur limits attached to their own switched segments; do not add them into the allowable length of one passive cable run.
Choose the link arrangement before specifying cable lengths, node counts or equipment; the SPE family includes different physical topologies.
For T1S, Physical Layer Collision Avoidance (PLCA) coordinates transmission opportunities among nodes. The IEEE development draft describes a coordinator beacon and opportunities associated with node identities; a node without data can yield its turn (IEEE 802.3cg D0.3 draft, 2017, clause 148). This historical draft explains the mechanism; use the applicable final standard and product documentation for a deployment specification.
For a shared segment, include the intended traffic in the pilot. Ask the supplier to document its supported configuration and demonstrate the application under that configuration. Do not translate a physical-layer feature into an application-cycle promise without evidence from the proposed system.
Cable reuse needs qualification. For APL, the Engineering Guideline specifies characteristic impedance of 100 Ω ±20% across 100 kHz–20 MHz and describes examination of existing cabling. That is a channel requirement, not permission to accept any pair because it previously carried a sensor signal (Engineering Guideline, section 4.1.4).
Keep those numerical criteria within their APL scope. Other SPE designs need the requirements applicable to their own PHY and installation. Use the cable record, actual route and equipment documentation to choose the measurements. Include intermediate connections in the assessment rather than evaluating only a new sample of bulk cable.
Specify connectors separately. The SPE System Alliance discusses connector variants under IEC 63171 and cable specifications under IEC 61156. A connector's housing description alone does not specify the complete interface (architecture whitepaper, section 3).
Ask for the exact mating interface, pin assignment, environmental rating, power rating and supported PHY at each end. Include patch leads and adapters in that record. For the related installation discipline, our sensor cable shielding and grounding guide provides further context.
Consider a hypothetical pilot with an installed cable route and a proposed SPE sensor. Make cable acceptance a separate decision from sensor acceptance. If the cable fails its checks, the pilot has answered a wiring question; it has not established whether the proposed sensor and control application work together. That separation makes the result easier to act on.
Specify power independently of the 10 Mbit/s data link. The SPE System Alliance describes Power over Data Line (PoDL) arrangements with suitable sourcing and powered-device circuitry, including detection and classification mechanisms that differ from conventional PoE. The power interfaces are not interchangeable merely because both carry Ethernet (architecture whitepaper, section 5).
For procurement, request a matched source-and-device power specification. Record the supply conditions, required device power, allowed cable resistance and the manufacturer's limits for the proposed channel. Avoid accepting a maximum power headline without the conditions under which the device receives that power.
Our active versus passive PoE injector guide covers conventional PoE decisions. Keep that equipment category distinct from a PoDL purchasing requirement.
Ethernet-APL needs its own treatment. The Engineering Guideline defines port profiles and power provisions for process installations, including intrinsically safe applications. Generic T1L support does not establish hazardous-area suitability. Match equipment and installation requirements to the actual application (Engineering Guideline, sections 4.3–4.6).
For a powered APL trunk, the guideline lists checking field-switch voltage against the minimum operating voltage plus reserve as an optional basic check. We recommend recording that measurement in the pilot. This is an editorial acceptance recommendation, not a claim that the guideline mandates every optional test.
Use a written acceptance record. The APL Engineering Guideline organizes acceptance into three stages: visual inspection, cable measurements and a basic functional check before control-system commissioning. Its tables distinguish recommended and optional checks. For other SPE installations, adapt the structure to the selected equipment's documented requirements (Engineering Guideline, chapter 7).
Keep physical inspection, channel measurements and application acceptance visible as separate results in the rollout record.
Use the following as a proposed pilot worksheet, rather than a substitute for the applicable installation specification:
Make the pilot deliverable a repeatable specification. A second installer should be able to identify the permitted channel, assemble the approved components and apply the same acceptance criteria. If the record depends on an undocumented setting or an unexplained adapter, resolve that dependency before buying the next batch.
SPE is a family of Ethernet physical-layer options using one balanced copper pair. The SPE System Alliance describes 10 Mbit/s T1L and T1S options with different topologies. Specify the physical link separately from the industrial application protocol, power interface and connector system (architecture whitepaper).
10BASE-T1L supports point-to-point links up to 1,000 m under the specified channel conditions, according to the SPE System Alliance. That figure is not a guarantee for an arbitrary installed pair. Qualify the complete channel and check power delivery separately before accepting a long sensor link (architecture whitepaper).
Ethernet-APL is a process-automation application of 10BASE-T1L with defined port, power and installation provisions. Its Engineering Guideline allows spurs up to 200 m. Generic SPE equipment does not acquire hazardous-area suitability merely by using the same underlying PHY; the applicable equipment and installation requirements still govern (Engineering Guideline).
No. In a 10BASE-T1S multidrop segment, nodes share the 10 Mbit/s medium. The SPE System Alliance describes baseline support for at least eight nodes over 25 m, with compliant implementations able to exceed those figures. Evaluate the selected devices and application traffic together rather than multiplying bandwidth by node count (architecture whitepaper).