Ethernet-APL vs Ethernet-SPE: Power Classes, PoDL, and What IEC TS 63444 Edition 2 Changed

Somewhere in a vendor deck right now, a slide uses “Ethernet-APL” and “Single Pair Ethernet” as if they were two products competing for the same DIN rail. They are not. The Ethernet-APL vs Ethernet-SPE question has a clean answer that most marketing material fails to give: APL is a profile of single-pair Ethernet built for hazardous process areas, and SPE is the wider family that APL belongs to. Getting this wrong costs real money, because the two profiles make opposite choices about how power reaches a field device — and those choices decide your cable lengths, your Ex certification path, and whether a 3 W analyser can sit on that segment at all. The confusion got worse in 2026, when the governing documents were retitled to cover both.

What this covers: the clause-level difference between the two profiles, the power class tables that actually constrain instrument design, what IEC TS 63444 Edition 2.0 changed in June 2026, and a decision matrix built on hazardous-area rating, distance, and power budget rather than on “which is better”.

Context and Background

Process plants have been running 4–20 mA loops since the 1950s and digital fieldbuses — HART, FOUNDATION Fieldbus H1, PROFIBUS PA — since the 1990s. All of them share a constraint that plant engineers stopped noticing because it was always true: a field instrument in a hazardous area gets its power and its data over the same two wires, and the amount of energy allowed on those wires is capped by explosion-protection rules rather than by anything electrical.

That constraint is why a HART transmitter runs on roughly 3.5 mA of headroom and why FOUNDATION Fieldbus H1 tops out at 31.25 kbit/s. It is also why the industry spent two decades bridging fieldbus segments into Ethernet at a gateway, with all the protocol translation, device-description mismatches, and diagnostic loss that implies.

IEEE 802.3cg-2019 broke the deadlock by standardising 10BASE-T1L: full-duplex 10 Mbit/s over one balanced pair, over cable runs up to a kilometre. That clause now lives as Clause 146 of IEEE Std 802.3-2022. The same project also produced 10BASE-T1S for short multidrop segments, and Clause 104 of the base standard already defined Power over Data Lines (PoDL) for single-pair links.

Two industry efforts then built on top of that PHY, and this is exactly where the naming trouble starts. Ethernet-APL — the Advanced Physical Layer — was developed by FieldComm Group, ODVA, OPC Foundation and PROFIBUS & PROFINET International to carry 10BASE-T1L into Zone 0 and Division 1 process areas with intrinsic safety. Ethernet-SPE is the newer, non-intrinsically-safe profile of the same PHY aimed at factory and building automation. Both are specified in the same IEC document. Neither replaces the other, and our Ethernet-APL reference architecture for process automation walks through what an APL deployment looks like end to end.

Ethernet-APL Is a Profile of SPE, Not a Rival to It

Ethernet-APL and Ethernet-SPE are both profiles of IEEE 802.3 single-pair Ethernet running the same 10BASE-T1L PHY. APL adds 2-WISE intrinsic safety per IEC TS 60079-47 and a trunk-and-spur power scheme for hazardous areas. Ethernet-SPE keeps standard Clause 104 PoDL and targets non-hazardous factory and building automation. Both are specified in IEC TS 63444.

Figure 1: Where the two profiles sit in the IEEE 802.3 single-pair Ethernet family tree.

The diagram traces the lineage that vendor decks usually flatten. IEEE 802.3 defines several single-pair PHYs — 10BASE-T1S for short multidrop runs, 10BASE-T1L for long process runs, and the faster 100BASE-T1 and 1000BASE-T1 variants that arrived from the automotive world. Ethernet-APL and Ethernet-SPE both sit under 10BASE-T1L specifically. They diverge at the power layer, not the data layer, and that divergence is the entire story.

The clause-level distinction that settles the argument

The introduction to IEC TS 63444 Edition 2.0 states the difference in one sentence that is worth reading twice. Ethernet-APL “references and extends” Clause 146 and replaces Clause 104 with an alternate power method. Ethernet-SPE, by contrast, “references and extends” both Clause 146 and Clause 104.

That is the whole distinction, expressed normatively. APL does not use PoDL. It uses what the IEEE 802.3 power ad-hoc community calls engineered power: a fixed, pre-classified source port whose voltage and current envelope is declared up front, matched at design time against a load port with a compatible declared envelope. There is no runtime negotiation because negotiation is a liability when the energy budget is an explosion-protection parameter.

Ethernet-SPE keeps PoDL, including the Serial Communication Classification Protocol handshake in which a powered device signals its class before the source applies full voltage. That handshake is fine in a non-hazardous cabinet. It is precisely what a 2-WISE assessor does not want to certify in a Zone 0 spur, because the assessment has to hold for every transient state of the link, not just steady state.

Four classification axes, not one

A second thing the marketing material flattens: an APL port is described by four orthogonal classifications, and only one of them is about watts. IEC TS 63444 Edition 2.0 defines them in Clause 5.2 as segment class, port class, power class, and intrinsically safe protection class.

Segment class says whether the segment is a trunk (T) or a spur (S), which in turn drives the permitted cable length. Port class describes the powering behaviour — power source, power load, cascade, or unpowered. Power class gives the electrical envelope. Intrinsically safe protection class states the Ex level of protection the port supports.

The important consequence is that these are checked independently. A permitted power-class combination does not imply a permitted intrinsic-safety combination. The Engineering Guideline is blunt about this: permitted port class combinations “do not imply that every combination is also permitted from an intrinsically safe viewpoint”, and that has to be verified separately under 2-WISE. Teams that read only the power table and skip the Ex check are the ones who discover the problem during commissioning.

Trunk and spur are APL vocabulary, and SPE does not have them

Ethernet-APL defines a two-tier topology. A trunk connects an APL power switch to a field switch, or a field switch to another field switch, at up to 1,000 m per segment. A spur connects a single field device to a field switch, at up to 200 m. Only one field device may hang on a spur — APL is not multidrop, despite the fieldbus cabling it reuses.

The two tiers also run the PHY differently. Trunk segments use the 2.4 Vpp operating mode of 10BASE-T1L; spur segments use the 1.0 Vpp mode. The lower amplitude on the spur is not an oversight. It is part of the energy limitation that makes a spur certifiable for a hazardous area at all.

Ethernet-SPE has no trunk or spur concept. Its unit of design is the “Ethernet-SPE transmission channel”: two SPE ports at either end of one shielded single pair, with power sourcing equipment at one end and a powered device at the other. That is a flat, point-to-point model borrowed straight from PoDL. Anyone who has designed a deterministic OPC UA over TSN architecture will recognise the difference in planning effort immediately: APL asks for a power-tree calculation, SPE asks for a per-link budget.

What Actually Changed in 2026

Two documents moved this year, and they moved in lockstep because one feeds the other.

IEC TS 63444 Edition 2.0, dated 2026-06. The retitle alone tells the story. Edition 1.0 (2023-11) was called “Industrial networks – Ethernet-APL port profile specification”. Edition 2.0 is “Industrial networks – Ethernet-APL port profile / Ethernet-SPE profile specification”. It cancels and replaces Edition 1.0, and its foreword lists exactly three significant technical changes: a new power class for Ethernet-APL, the addition of Ethernet-SPE, and a clarification of the usability of Ethernet-APL in non-hazardous locations.

That third item matters more than it reads. It closes a recurring procurement argument — whether APL hardware may be specified in a safe area purely for its cable reach and its single-pair economics, without any Ex justification. The answer is now explicit rather than inferred.

The joint SDO port specification. The four co-owning organisations also released an updated port specification covering both profiles. Its content is confirmed: the SPE power concept was expanded to include PoDL, applicable power classes and connectors were defined for SPE, and Ethernet-APL Power Class B was formalised at up to 1.16 W per device.

One caveat, stated plainly because getting version numbers wrong is how reference pages lose trust. Secondary reporting describes this as “APL/SPE Port Specification Revision 3.1”, approved and released on 1 September 2026. FieldComm Group’s own live specifications page, however, lists the current document as Ethernet-APL/Ethernet-SPE Profile Specification (FCG TS10186) Rev. 2.1. The substance is corroborated by FieldComm Group’s own press release and by ARC Advisory Group’s coverage; the revision number is not. Treat “3.1” as reported and check FCG TS10186 in the FieldComm library before you cite a revision in a specification document of your own.

Figure 2: How power classes cascade from the APL power switch down to the instrument, and where Power Class B lands.

Figure 2 shows why the new class exists. The APL power switch feeds a trunk in one of two classes. Class 3 delivers a minimum of 57.5 W at the source (46 V at 1.25 A); Class 4 raises that to 92 W (46 V at 2 A). After the volt drop across up to a kilometre of trunk cable, a field switch on Class 3 sees a minimum of 36 W at 28.8 V, and on Class 4 sees 57.6 W. That budget is then split between the switch’s own electronics and every spur hanging off it.

Power Class B filled a gap that had been sitting in the tables for years

Here is the detail that makes the 2026 change interesting rather than routine. Power Class B was named in the Ethernet-APL Engineering Guideline long before it was specified. The guideline’s prose says “power classes A, B and C are primarily intended to be used for intrinsically safe rated spur ports”, but its power-class table lists only A, C, 3 and 4 as source classes. B was a reserved slot with a letter and no numbers.

The published spur classes are narrow. Class A source ports supply 15 V DC and a minimum of 0.54 W, which becomes 0.5 W at the load after 200 m of AWG18 spur cable. Class C supplies 15 V DC and a minimum of 1.1 W, landing at 1.0 W at the load. Filling in B at 1.16 W at the device closes a real gap between “half a watt” and “a watt”, and it does so on the device side of the cable rather than the source side.

Class	Segment	Source envelope	Power at the load	Typical use
A	Spur	15 V DC, 0.54 W min	0.5 W	Ex ia two-wire transmitters, Zone 0/1
B	Spur	Specified in IEC TS 63444 Ed 2.0	up to 1.16 W	Higher-draw IS instruments
C	Spur	15 V DC, 1.1 W min	1.0 W	Ex ic instruments, Zone 2
3	Trunk	50 V max, 46 V min, 1.25 A, 57.5 W min	36 W at 28.8 V	Small field-switch counts
4	Trunk	50 V max, 46 V min, 2 A, 92 W min	57.6 W at 28.8 V	Dense spur fan-out

The Class A and C figures, and the trunk figures, come from Pepperl+Fuchs’ presentation to the IEEE 802.3 power distribution ad-hoc. The presentation is candid about the internal cost: a Class A field device consumes roughly 1 W inside the field switch because of resistive current limiting, and a Class C device costs 1.2–1.3 W with electronic limiting. Eight spurs is therefore a far bigger ask on the trunk budget than eight times 0.5 W suggests.

Ethernet-SPE inherits the PoDL class ladder instead

Ethernet-SPE does not use A/B/C/3/4 at all. It uses the PoDL power classes, and IEC TS 63444 Edition 2.0 confirms the range: its tables cover “classes 10 to 15” for PSE, power interface and PD, with an informative annex giving DC loop resistance and cable length calculations for those same classes across AWG13 to AWG24.

Classes 10 to 12 operate at a nominal 24 V system voltage; classes 13 to 15 operate at 50–58 V. Vendor documentation puts the maximum PD power at roughly 1.2 W, 3.4 W and 8.4 W for classes 10–12, and roughly 7.7 W, 20 W and up to 52 W for classes 13–15. Treat those wattages as supplier-reported rather than quoted from IEEE normative text — the class grouping is confirmed by the IEC document, the individual figures are not.

The asymmetry is the point. The top of the APL ladder is 1.16 W at a field device. The top of the SPE ladder is roughly fifty times that. Nothing about SPE’s electronics is superior; SPE simply is not carrying an explosion-protection obligation.

Why Intrinsic Safety Caps the Watts

Intrinsic safety is not a component rating. It is a statement about the whole circuit: under any credible fault, the circuit cannot release enough energy — thermally or as a spark — to ignite the surrounding atmosphere. The relevant physics is the minimum ignition energy of the gas group, which for IIC atmospheres such as hydrogen or acetylene is in the tens of microjoules.

Two energy stores matter. Capacitance in the field device can dump its charge into a fault in microseconds. Inductance in the cable can sustain an arc when a circuit opens. Classical intrinsic safety handles this with entity parameters — the source declares Uo, Io, Po, Co and Lo; the load declares Ui, Ii, Pi, Ci and Li; and the installer proves each source parameter bounds its load counterpart, with cable capacitance and inductance subtracted from the budget.

Figure 3: Runtime power-up on a 2-WISE spur, and the design-time protection-level roll-up that has to accompany it.

What 2-WISE changed about that arithmetic

Doing entity-parameter arithmetic per instrument, per cable, per installation is tedious and error-prone. 2-WISE — the 2-Wire Intrinsically Safe Ethernet concept in IEC TS 60079-47:2021 — replaces per-pair arithmetic with pre-agreed envelopes. A 2-WISE port declares a protection class; a 2-WISE segment is intrinsically safe if it comprises one 2-WISE source port, one 2-WISE load port, and at most two 2-WISE auxiliary devices.

The roll-up rule is deliberately pessimistic, and it trips people up. The level of protection for the segment is set by the port with the lowest level. Put an Ex ia field device on a field-switch port rated Ex ic and the segment is Ex ic — which disqualifies it for Zone 0. Buying the better instrument does not upgrade the segment.

The runtime sequence in Figure 3 shows why an APL source port cannot just apply voltage and hope. When the device’s input capacitance charges, it pulls an inrush current with a characteristic shape. IEC TS 63444 classifies these as current step and current spike events, with defined limits on peak current and on the charge transferred during a spike. The source port has to remain inside its declared envelope throughout, not only in steady state. That is a much harder guarantee than PoDL’s classification handshake, and it is why APL’s power ceiling is where it is.

What the budget buys in a real instrument

Translate the numbers into hardware and the design pressure becomes obvious. A Class A spur gives a field device 0.5 W at the terminals. At a typical 9 V rail that is about 55 mA for everything: the 10BASE-T1L PHY, the MAC, the microcontroller running the protocol stack, the sensor front end, and the local display if the spec demands one.

A 10BASE-T1L PHY in 1.0 Vpp mode is the single largest fixed cost in that budget. What remains has to cover a sensor bridge, an ADC, and a stack that may be PROFINET, EtherNet/IP, or HART-IP. The Pepperl+Fuchs presentation names the long-term goal explicitly: bring field-device consumption down from 500 mW to about 250 mW, which “requires more power-efficient MCUs to be developed first”.

This is why the three canonical instrument classes behave so differently on APL:

• A pressure or temperature transmitter fits inside Class A. It is a low-duty-cycle measurement with modest analogue front-end requirements, and vendors have shipped these since 2023.
• A valve positioner does not. It needs enough power to drive a pneumatic stage, so it either takes a Class C spur or takes its actuation energy from a separate supply and uses APL only for data.
• A gas chromatograph or process analyser is out of reach entirely. Column heaters and detectors are multi-watt loads. Those instruments live in Zone 2 or a purged enclosure and take Ethernet-SPE, conventional PoE, or a local supply.

Power Class B at 1.16 W does not move a positioner or an analyser into range. It moves the marginal instrument — the multivariable transmitter, the radar level device with more signal processing — from “needs a Class C port and an Ex ic segment” to something that may stay intrinsically safe. That is a narrow win, but a commercially real one.

Choosing Between Them: The Decision Matrix

The choice is not a preference. It is a sequence of hard gates, and the first gate is almost always the area classification on the plant drawing.

Figure 4: The decision sequence — hazardous-area rating first, then power, then distance.

Criterion	Ethernet-APL	Ethernet-SPE
Hazardous-area rating	Zone 0/1/2 and Div 1/2 via 2-WISE; Ex ia, ib and ic protection levels	None inherent; needs a separate Ex method such as Ex d or purging
Power method	Engineered power, pre-classified, replaces Clause 104	Clause 104 PoDL as amended by IEEE 802.3dd-2022
Power at the device	0.5 W (Class A), 1.0 W (Class C), up to 1.16 W (Class B)	Roughly 1.2 W to 52 W depending on PoDL class 10–15
Topology	Trunk and spur, one device per spur, cascade ports for daisy chain	Point-to-point transmission channel
Distance	Trunk to 1,000 m, spur to 200 m, cable categories I–IV	Governed by PoDL loop-resistance budget for the chosen class
Connectors	M12 and M8 A-coded, terminal blocks; M8 not for IS circuits	M8, M12, M12 hybrid and IP20 per IEC 63171:2025
Segment loading	Max 2 auxiliary devices; 4 inline connections on a spur, 10 on a trunk	Auxiliary devices permitted, per the SPE channel definition
Brownfield cable reuse	Designed for it — reuses fieldbus Type A cable	Possible, but no equivalent re-qualification framework

Cable length is a data limit and a power limit at once

Both profiles impose two separate length constraints that engineers routinely conflate. The signal-integrity limit comes from the cable category. IEC TS 63444 defines APL categories I to IV with maximum trunk lengths of 250, 500, 750 and 1,000 m and maximum spur lengths of 50, 100, 150 and 200 m. Those figures derive from insertion loss, return loss and coupling attenuation limits over 0.1–20 MHz.

The power limit is separate and usually binds first. On a powered trunk, the achievable distance depends on the power switch output voltage, the number of field switches, the total field-device load, the conductor cross-section, and the cable temperature. Worked examples in the Engineering Guideline show roughly 600 m to the first field switch on 1.5 mm² (16 AWG) trunk cable, extending to around 700 m on 2.5 mm² (14 AWG), for the same load.

Ethernet-SPE faces the same physics through a different door. Its informative annex tabulates DC loop resistance per power class against wire gauges from AWG13 to AWG24 and derives the permitted length. A class 15 link at 52 W over AWG24 is a very short link.

The migration question nobody asks early enough

Most APL projects are brownfield. The cabling case is genuinely strong: APL’s reference cable is fieldbus Type A cable, MAU types 1 and 3 per IEC 61158-2 — the same cable already pulled for PROFIBUS PA and FOUNDATION Fieldbus H1. Existing runs can be re-qualified rather than replaced, using the insertion-loss examination in ISO/IEC 11801-3, with a 0.2 correction factor applied to spur cables to reflect the shorter maximum length.

The topology case is weaker, and this is the trap. PROFIBUS PA and FF H1 are multidrop: many instruments share one segment. APL is not. Every field device needs its own spur back to a field switch. A 32-device PA segment does not become one APL segment; it becomes two 16-port field switches and thirty-two home runs. If the existing cable is a multidrop bus rather than a home-run star with junction boxes, the reuse argument mostly evaporates.

Budget for that when you cost the migration, and while you are there, revisit your zone and conduit model — flattening fieldbus into routable Ethernet changes the attack surface, which our walk-through of IEC 62443 zones and conduits covers in detail.

Trade-offs, Gotchas, and What Goes Wrong

The version numbers are genuinely inconsistent right now. As noted above, secondary sources describe an “APL/SPE Port Specification Revision 3.1” released 1 September 2026, while FieldComm Group’s live specification index lists FCG TS10186 Rev. 2.1. Cite the IEC TS 63444 edition and date in contractual documents; it is unambiguous and it is the version that certification bodies will read.

Power-class compatibility is not symmetric. A Class C source port may feed a Class A or Class C load, but a Class A source may only feed a Class A load. Specifying field switches with Class A spur ports to save cost locks out every Class C instrument on that switch for the life of the installation. Switch ports are the long-lived asset; instruments turn over faster.

The protection-level roll-up punishes mixed procurement. Segment protection is set by the weakest port. Plants that buy instruments and field switches on separate purchase orders, years apart, routinely end up with Ex ia instruments on Ex ic ports and a segment that cannot serve Zone 0.

The field switch consumes its own budget. Trunk power arrives at the field switch, and the switch’s electronics take a share before any spur is fed. With resistive current limiting, a single Class A spur costs roughly 1 W inside the switch to deliver 0.5 W outside it. A sixteen-port switch at full load is not an 8 W device.

Auxiliary devices are counted, not ignored. An APL segment permits at most two auxiliary devices — a surge protector is the common one — and each counts as an inline connection. Spurs allow four inline connections total; trunks allow ten. Junction boxes added during construction eat that allowance quickly, and the failure mode is intermittent link loss rather than a clean error.

Standards status is not product status. Edition 2.0 published in June 2026 and the joint port specification followed. Silicon, certified switches and certified instruments for Ethernet-SPE and for APL Power Class B follow on their own schedules. Conformance test specifications exist — FieldComm Group publishes separate EMC, data and power test specifications for APL — but a registered product list is the only evidence that matters for a procurement deadline.

100BASE-T1L is coming, and it is not here. The SDOs have stated that adding 100 Mbit/s two-wire operation is in progress, along with integration into IEC 61158-100. Designing a plant network on the assumption that a tenfold bandwidth increase lands on your schedule is speculation, not planning.

Practical Recommendations

Start with the area classification drawing, not the datasheet. If the instrument sits in a zone that demands intrinsic safety, the decision is already made and the only remaining question is which APL power class the device fits. If it does not, Ethernet-SPE with PoDL is almost always the cheaper and more flexible answer, and it will carry an order of magnitude more power.

Specify field-switch spur ports one class above what today’s instruments need. The switch outlives the instruments. Paying for Class C ports you do not yet use is cheap insurance against a Class A port blocking an upgrade in 2031.

Do the trunk power calculation before you fix switch locations, not after. The volt-drop limit binds before the insertion-loss limit on most powered trunks, and moving a field switch after the cable trays are installed is expensive.

A working checklist for the next segment you design:

• Record the zone or division and the required protection level (ia, ib, ic) for every device on the segment.
• Confirm the protection-level roll-up: the lowest-rated port sets the segment rating.
• Check the power-class pairing against the source/load compatibility table, then check intrinsic safety separately under 2-WISE.
• Size the trunk from total field-switch load, conductor cross-section, and worst-case cable temperature — not from the category length alone.
• Count auxiliary devices and inline connections per segment against the 2/4 and 2/10 limits.
• Re-qualify reused fieldbus cable per ISO/IEC 11801-3, applying the 0.2 spur correction factor.
• Produce the 2-WISE descriptive system document for each segment; IEC TS 60079-47 requires it.
• Verify certification against the vendor’s registered-product listing, not a datasheet claim.

Frequently Asked Questions

Is Ethernet-APL the same as Single Pair Ethernet?

No. Single Pair Ethernet is the family of IEEE 802.3 physical layers that carry Ethernet over one balanced pair, including 10BASE-T1S, 10BASE-T1L, 100BASE-T1 and 1000BASE-T1. Ethernet-APL is a specific profile of 10BASE-T1L that adds intrinsic safety under 2-WISE (IEC TS 60079-47) plus a trunk-and-spur power scheme for process plants. Every APL link is an SPE link, but most SPE links are not APL.

What is Ethernet-APL Power Class B?

Power Class B is the spur power class formalised in IEC TS 63444 Edition 2.0, supporting field devices drawing up to 1.16 W. It sits between the long-established Class A (0.5 W at the load) and Class C (1.0 W at the load). The letter B appeared in earlier APL guideline prose without electrical values attached; the 2026 edition supplied the numbers. It is aimed at intrinsically safe instruments that were marginal on the older classes.

Does Ethernet-APL use PoDL?

No, and this is the sharpest technical difference between the profiles. IEC TS 63444 states that Ethernet-APL replaces IEEE 802.3 Clause 104 (PoDL) with an alternate power method, while Ethernet-SPE references and extends Clause 104. APL uses pre-classified engineered power with design-time port matching, because a runtime negotiation handshake is difficult to certify when every transient state has to stay inside an explosion-protection envelope.

How far can an Ethernet-APL cable run?

A trunk segment runs up to 1,000 m and a spur up to 200 m, but only with cable category IV. Categories I, II and III cap trunks at 250, 500 and 750 m and spurs at 50, 100 and 150 m. On a powered trunk the practical limit is usually shorter still, because voltage drop binds before insertion loss. Guideline worked examples show roughly 600 m on 16 AWG trunk cable under realistic load.

What changed in IEC TS 63444 Edition 2.0?

Edition 2.0, dated June 2026, cancels and replaces Edition 1.0 from November 2023 and was retitled to cover both profiles. Its foreword lists three significant technical changes: a new power class for Ethernet-APL, the addition of Ethernet-SPE, and clarification of the usability of Ethernet-APL in non-hazardous locations. That last point confirms APL hardware may be specified in safe areas purely for reach and cabling economics.

Can I reuse my PROFIBUS PA or FOUNDATION Fieldbus cable for APL?

Often yes for the cable itself — APL’s reference cable is fieldbus Type A, MAU types 1 and 3 per IEC 61158-2 — provided it passes re-qualification under ISO/IEC 11801-3 with the 0.2 correction factor applied to spurs. The topology is the real obstacle. PA and H1 are multidrop; APL allows exactly one field device per spur. A shared 32-device segment becomes 32 home runs plus field switches.

Further Reading

• Ethernet-APL reference architecture for process automation — the full deployment picture, from power switch to controller.
• PROFINET vs EtherCAT vs OPC UA FX over TSN — which protocol rides on top of the physical layer you just chose.
• The IEC/IEEE 60802 TSN profile for industrial automation — determinism above the APL trunk.
• IEC 62443 zones and conduits for industrial control systems — what routable Ethernet at the field level does to your security model.
• IEC TS 63444:2026 at the IEC Webstore — the primary normative source for both profiles.
• FieldComm Group Ethernet-APL specifications index — current revision numbers for the joint port and test specifications.

By Riju — about