Single-Pair Ethernet (SPE) is not a complete design specification simply because it uses one balanced copper pair.
Start by identifying the actual PHY and electrical link, then evaluate PoDL power delivery, topology, device and gateway roles, and the installation environment as separate approval questions.
The available evidence describes 802.3cg-2019, 100BASE-T1, 1000BASE-T1, selected automotive distance examples, PoDL, MICE classifications, and OT applications—but these sources do not form a universal SPE rate, distance, power, or topology table.
SPE link scoped for data only
- Power-delivery question
- Is PoDL supported by the actual PHY and device combination? Verify voltage, current, and class from separate evidence.
- Physical and environment boundary
- Check the single balanced pair, PHY, cable construction, and distance conditions; then compare the MICE environment classification separately.
SPE link including PoDL
- Power-delivery question
- Do not infer a power quantity or mandatory support from a statement that remote power is possible.
- Physical and environment boundary
- Validate data-link and power-delivery conditions separately. The cited material does not provide voltage, current, or pair-count values.
Industrial or building-automation OT boundary
- Power-delivery question
- Define the device, power-source role, gateway or switch role separately, then verify interoperability evidence.
- Physical and environment boundary
- The article associates industrial settings with MICE 2 and 3 and commercial settings with MICE 1; detailed limits require separate verification.
Answer first: define the system boundary before choosing cable
The first SPE design question is not “Which cable should we buy?” It is “What exactly are the endpoints, and how will data and power move between them?” Record at least four boundaries:
- Physical link: the actual PHY, balanced single-pair copper link, cable construction, connectors, and distance conditions.
- Power delivery: whether the link carries data only or also uses Power over Data Line (PoDL).
- Topology: whether the segment is point-to-point, or whether the selected PHY and implementation explicitly support a multidrop or branched arrangement.
- System and environmental roles: whether the installation is commercial or industrial, and whether each device is a sensor, actuator, switch, power source, or gateway.
SPE is not one speed or one wiring method. A Fluke Networks explanation identifies IEEE 802.3cg-2019 as a 10 Mb/s SPE standards family and describes 100BASE-T1 and 1000BASE-T1 as earlier automotive in-car communication standards. That is explanatory guidance, not a universal specification for every SPE implementation.
It does not establish one connector, topology, power method, distance, or cable construction for all SPE links.
Write the selected PHY and device combination in the design record rather than writing only “SPE supported.” Keep electrical host lanes, optical lanes or wavelengths, and aggregate system throughput out of this conclusion unless separate evidence addresses them. The supplied evidence concerns electrical single-pair copper links; it does not define optical lanes or host electrical lane counts.
Step 1: lock the scope of every rate and distance number
A numerical comparison is useful only when the interface or PHY appears next to the number. The supplied explanatory material supports the following limited descriptions:
IEEE 802.3cg-2019
- What the evidence says
- Described by Fluke Networks as a 10 Mb/s SPE standards family
- What it does not prove
- It does not establish a universal cable length, power method, or topology
100BASE-T1
- What the evidence says
- Described in an automotive in-car communication context
- What it does not prove
- It is not assigned a unique distance by the cited wording
1000BASE-T1
- What the evidence says
- Described in the same automotive context
- What it does not prove
- It is not assigned a unique distance by the cited wording
For the automotive 100BASE-T1/1000BASE-T1 applications discussed, Fluke Networks reports up to 40 m over a single shielded pair and up to 15 m over an unshielded pair. The supplied wording presents these distances together and does not independently assign 40 m or 15 m to a particular PHY.
Therefore, do not rewrite the evidence as “100BASE-T1 supports 40 m” or “1000BASE-T1 supports 15 m.” These are reported maximum distances under the article’s described cable and application conditions—not universal IEEE limits, minimums, or guarantees for every implementation.
For an actual design, match the PHY data sheet, link partners, cable construction, shielding, impedance, connectors, installation method, and required environment. A PAM4 label, a single-pair label, or a product class name does not by itself establish fiber count, optical lanes, host electrical lanes, or a mandatory pair allocation. Those subjects are not specified by the cited evidence.
Step 2: approve data transport and PoDL as separate requirements
An SPE data link does not automatically support PoDL. The Fluke Networks explanation says that SPE applications can deliver remote power through Power over Data Line and may reduce the need for separate power infrastructure. It does not provide a voltage, current, power class, allocation rule, protection condition, or guarantee that every PHY supports PoDL.
Use separate approval rows for the data and power functions:
- Data approval: Are the selected PHYs, link partners, cable, connectors, and distance compatible?
- PoDL capability: Does the actual PSE and PD combination support PoDL?
- Power capacity: Are voltage, current, class, and maximum load documented for that implementation?
- Operating behavior: What happens if the load exceeds the available allocation or a protection function operates?
“Remote power is possible” describes a capability in the applications discussed; it does not prove that a particular powered device will receive its required operating power. Identify the roles explicitly. Is the sensor the powered device? Is a switch, injector, or gateway the power source? Does the gateway handle only data aggregation, or also power delivery?
Do not create a power-budget table from a qualitative PoDL statement. The supplied evidence does not provide voltage, current, power, or physical pair-count values. A conceptual power-flow diagram can explain logical request and allocation relationships, but it cannot substitute for implementation documentation or measured electrical limits.
Step 3: decide topology from the PHY and implementation, not from the SPE label
Avoid both blanket statements: “SPE is point-to-point” and “SPE connects many devices on one cable.” The supported topology depends on the selected PHY, implementation, link partners, device roles, and management design.
The cited material names 802.3cg-2019, 100BASE-T1, and 1000BASE-T1 families and their application contexts, but it does not establish a universal device count, branch count, physical pair arrangement, or topology guarantee.
Draw the proposed topology in this order:
- Identify the data source and destination.
- Classify every endpoint as a PHY endpoint, switch, gateway, sensor, or actuator.
- Mark each link partner and each management boundary.
- If PoDL is present, show whether the data device and power source are the same device.
- If a branch or multidrop segment is required, confirm that the selected PHY and implementation documentation explicitly describe it.
The Ethernet Alliance presents SPE as relevant to operational-technology networks in building and industrial automation. It lists simplifying network design and operation and reducing the need to support and translate legacy network protocols among its stated benefits. These are system-level benefits, not proof of interoperability between arbitrary devices or proof that a gateway can be removed.
The practical decision is therefore implementation-specific: verify whether the selected devices share the required Ethernet and PHY behavior, and decide separately whether an OT-to-IT boundary, protocol translation, or gateway function remains necessary.
Step 4: evaluate the installation environment independently with MICE
A link can meet a data requirement and still be unsuitable for its installation environment. The Fluke Networks explanation defines MICE as four environmental dimensions:
- M: mechanical conditions such as flexing and vibration
- I: ingress conditions such as moisture
- C: climatic conditions such as temperature
- E: electromagnetic conditions such as noise
The same explanation associates MICE Level 1 with commercial environments and Levels 2 and 3 with industrial SPE environments. This is a classification context, not a supplied table of temperature, vibration, moisture, or electromagnetic limits. Do not infer a detailed operating limit from the level name alone.
Ask the following before approving the physical installation:
- Is the route in a commercial space, an industrial area, or near machinery?
- What mechanical movement, moisture, temperature variation, and electromagnetic noise are expected?
- Do the cable, connector, sealing method, and termination components have compatible environmental ratings?
- Will maintenance introduce repeated bending or movement?
- Do the selected PHY and cable documents address the same environmental conditions?
Fluke Networks also states that SPE was incorporated into the ISO/IEC 11801 cabling infrastructure series and reports that TIA released ANSI/TIA-568.5 as a commercial SPE component standard in 2022. It mentions additional industrial-cabling and intelligent-building standards activity.
These are standards-publication and development statements in a 2022 explanatory article; they do not by themselves prove that a particular field installation or component combination is compliant.
Hypothetical example: scoping a factory sensor link
This is a hypothetical example for illustrating the decision sequence, not a report of a tested installation.
Suppose a factory wants to connect a vibration sensor near production equipment to a control-room gateway over a single-pair link and also wants to use PoDL. The gateway connects upward to an Ethernet-based automation network.
A weak design statement would be: “This is industrial SPE, so select a 10 Mb/s PoDL cable.” That statement leaves the PHY, topology, power class, device roles, environmental conditions, and gateway boundary undefined.
A stronger review would proceed as follows:
- Identify the sensor and gateway PHYs and their actual link-partner requirements. If a 10BASE-T1S or 10BASE-T1L label appears, verify what the selected implementation supports rather than inferring topology or distance from the name.
- Identify the powered device and the power-sourcing device.
- Confirm PoDL support for the actual PHY, PSE, and PD combination, then obtain separate evidence for voltage, current, class, and maximum load.
- Check cable shielding, distance, terminations, vibration, moisture, temperature, and electromagnetic conditions using the relevant environmental framework.
- Define whether the gateway terminates the SPE segment, translates a legacy protocol, aggregates data, or simply provides an Ethernet boundary.
It would be unsupported to conclude automatically that “industrial” means MICE Level 3 or that “SPE” guarantees remote power. The cited evidence connects industrial contexts with MICE Levels 2 and 3 and describes PoDL as a possible capability, but it does not assign a level or power limit to this hypothetical device combination.
The Ethernet Alliance’s stated benefits—simpler OT network design and less legacy protocol translation—can be design objectives, but they do not replace interoperability evidence for the selected devices.
Evidence limits: distinguish standards work, guidance, data sheets, and roadmaps
Document status matters as much as technical content. The supplied IEEE page identifies IEEE P802.3dp as a task force or project concerning cabling restrictions for Single Pair Power over Ethernet and displays a last update of 14 April 2025. That supports a statement about standards-development activity.
It does not establish that the work was complete, ratified, or unchanged after that date. Later status and ratification are unverified in the supplied evidence.
The Fluke Networks article is explanatory vendor guidance dated 16 June 2022. It provides useful context for 802.3cg-2019, 100BASE-T1, 1000BASE-T1, MICE, PoDL, and cabling activity, but it is not the normative IEEE, ISO/IEC, or TIA text.
The Ethernet Alliance’s 2026 roadmap lists BASE-T1 among technologies for smarter industrial networks and discusses broader themes including TSN and converged connectivity. A roadmap is an outlook, not a ratified requirement. It does not define the PHY mode, rate, distance, power method, or adoption obligation of every BASE-T1 implementation.
Label evidence according to its scope:
- Standards-development page: confirms project scope and visible status, not final requirements.
- Explanatory guidance: clarifies terminology and application context, not universal limits.
- Implementation data sheet: establishes the documented behavior of a particular product or combination.
- Normative standard: supplies requirements only within its actual applicability.
- Roadmap: indicates direction and interest, not mandatory implementation behavior.
This classification prevents a work item from being treated as a finished standard, a vendor explanation from becoming a physical law, or a future-oriented roadmap from becoming a current design guarantee.
Final design gate: approve only what the evidence actually supports
Before approving an SPE deployment, verify each item below:
- The exact PHY and interface are identified.
- The stated rate is identified as a per-link nominal PHY rate rather than an aggregate system rate.
- Electrical single-pair copper links are distinguished from optical lanes and host electrical lanes.
- Every distance is tied to a named PHY, cable condition, and application context.
- Reported values such as 40 m and 15 m are not being treated as universal limits, minimums, or guarantees.
- PoDL support is confirmed for the actual implementation, with separate evidence for voltage, current, class, and load.
- PSE, PD, switch, gateway, sensor, and actuator roles are documented.
- The required point-to-point, multidrop, or branched topology is explicitly supported by the selected PHY and implementation.
- MICE mechanical, ingress, climatic, and electromagnetic conditions match the installation.
- Standards pages, explanatory articles, implementation documents, and roadmaps are not being treated as interchangeable evidence.
SPE may help simplify OT and building-automation connectivity, and BASE-T1 is included in the Ethernet Alliance’s stated outlook for smarter industrial networks. Those benefits and directions do not remove the need to scope the physical link, power path, topology, device roles, and environment separately.
The safe design sequence is to identify the PHY and link first, approve power independently, map the actual topology, verify environmental suitability, and attach each conclusion to evidence with the same scope as the claim.
Sources
Related reading
- Structured Cabling: A Practical Guide to Building a Reliable Ethernet Infrastructure
- What Is Ethernet? How Data Moves Across a Wired Network
- Power over Ethernet Explained: PoE Types, Watts, and Cabling
- How to Validate High-Power PoE: Requested Class, PSE Allocation, Demotion, and Acceptance Evidence
- How to Extend Ethernet Beyond 100 Meters: Fiber or an Intermediate Switch?
No comments:
Post a Comment