Last Updated: October 2026

PROFINET IRT TSN describes the shift from PROFINET’s hardware-scheduled isochronous real-time (IRT, Conformance Class C) toward PROFINET over Time-Sensitive Networking (Conformance Class D). IRT still works and remains in the specification, while TSN moves the same determinism onto standard IEEE 802.1 mechanisms such as time synchronization, scheduled traffic and frame preemption, running on multi-vendor switches instead of PROFINET-specific ASICs.

The standards picture has firmed up since the original article was written. According to the IEEE 802.1 TSN pages, IEC/IEEE 60802 (the TSN profile for industrial automation) is listed as a published standard dated 29 June 2026. PROFIBUS and PROFINET International (PI) states that PROFINET specification V2.4, which integrates TSN as an additional Layer 2 technology, is published, and that RT and IRT stay in the specification. The OPC Foundation reports the OPC UA FX 1.00 specification as a staged release, with Part 81 and Part 84 at release-candidate level as of March 2026.

This refresh adds an answer-first summary, an updated FAQ and a list of primary sources. Treat dates, product-support horizons and certification details in the original text below as of its April 2026 writing, and confirm them with PI and your vendors before committing a design. For related reading, see IEC/IEEE 60802 TSN profile decisions for industrial networks, OPC UA FX field exchange reference architecture and OPC UA protocol: complete technical guide. The original article follows unchanged.

PROFINET IRT and TSN: Real-Time Industrial Ethernet Deep Dive

PROFINET is the most widely deployed real-time industrial Ethernet protocol, trusted in over 30 million devices on factory floors worldwide. It delivers sub-millisecond cycle times through proprietary isochronous real-time (IRT) scheduling, but the protocol now faces a critical convergence: IEEE 802.1 Time-Sensitive Networking (TSN) is standardizing what PROFINET pioneered, forcing a strategic choice between legacy hardware lock-in and standards-based determinism. This deep dive unpacks three PROFINET conformance classes (RT, IRT, TSN), the hardware-switched scheduling that makes sub-microsecond jitter possible, and exactly why the next generation of factory automation runs on Ethernet standards, not vendor-specific extensions.

Architecture at a glance

PROFINET IRT and TSN: Real-Time Industrial Ethernet Deep Dive — architecture diagram — Architecture diagram — PROFINET IRT and TSN: Real-Time Industrial Ethernet Deep Dive

What PROFINET Is and Why It’s a Factory-Floor Default

PROFINET is a layer-2 and layer-3 industrial protocol that emerged in the early 2000s from the PROFIBUS organization (now part of PI—PROFIBUS & PROFINET International). It maps field devices (sensors, actuators, motor drives, programmable logic controllers) onto standard Ethernet MAC and IP frames, but crucially does not tolerate the variable latency and jitter that TCP/IP introduces. A synchronous motor control loop—burning hot a 1 millisecond cycle time—cannot tolerate a 10 ms packet arriving late; PROFINET guarantees it won’t, by enforcing layer-2 determinism.

PROFINET succeeds because it is pragmatically standards-based: it reuses Ethernet cabling, switches, and NIC hardware, lowering adoption friction against legacy protocols like PROFIBUS (serial) or CANopen (real-time CAN). Yet it is also proprietary in the places it matters most—the three conformance classes impose specific scheduling disciplines that no generic Ethernet switch can enforce without PROFINET-aware firmware.

Today, PROFINET controls over 350 million I/O nodes globally, with industrial deployments spanning automotive assembly lines (cycle times 5–100 ms), precision CNC machining (sub-1 ms), and coordinated robot cells (10–50 µs). Its dominance is not accident. The protocol trades single-vendor extensibility for interoperability across a certified ecosystem.

PROFINET Conformance Classes: CC-A, CC-B, CC-C, and CC-D

PROFINET defines four conformance classes, each with distinct real-time guarantees, hardware requirements, and topology constraints. Understanding these is essential to architecture decisions.

Figure 1: PROFINET conformance classes comparison. CC-A (non-real-time) handles acyclic communication; CC-B/C (soft and hard real-time) enforce microsecond-level scheduling; CC-D (TSN-based) converges on IEEE standards.

CC-A (Non-Real-Time, Acyclic)

CC-A is ordinary IP over Ethernet. No scheduling, no jitter guarantees. Appropriate for configuration uploads, diagnostics, and non-critical data fetch (temperature telemetry every 5 seconds). Latencies are variable: 10–100 ms. No special switch firmware required.

CC-B (Soft Real-Time, ~1 ms)

CC-B (“RT”—real-time) enforces periodic communication cycles at 1 ms or longer through software-based scheduling on device CPUs and switches. A PROFINET switch classifies RT frames by MAC multicast address and priority tags (802.1p), buffering and forwarding them ahead of NRT traffic. No deterministic sub-millisecond jitter guarantee; cycle time skew of 100–500 µs is acceptable for soft-synchronous applications like pressure monitoring, temperature control feedback, and human-machine interface updates.

Topology: ring-resilient (media redundancy protocol, MRP), any standard Ethernet switch with PROFINET-aware firmware.

Cycle time: 250 µs to 100 ms (typical: 1–10 ms).

Jitter: ±500 µs typical.

CC-C (Hard Real-Time, <1 ms Isochronous)

CC-C is where PROFINET becomes a proprietary beast: isochronous real-time (IRT). IRT reserves dedicated time slots on every switch port and NIC, creating a synchronous schedule that repeats every IRT period (typically 125–500 µs). No frame collisions, no buffering, no interrupts: the Ethernet link operates like a TDM (time-division multiplex) trunk line.

This requires:
– IRT-aware switches (Siemens S7-1200/1500, Phoenix Contact, Hirschfeld, etc.)—firmware reserves per-port bandwidth.
– IRT-capable NICs on devices (dedicated DMA engine, hardware timestamping).
– Synchronization via PROFINET sync frames (sub-µs precision PTP variant, proprietary).
– Strict topology: line or tree; no loops (STP disabled).

Cycle time: 125–500 µs (30 Hz to 8 kHz cycles).

Jitter: <100 ns typical; sub-microsecond in certified systems.

Use case: servo drive coordination, precision spindle control, coordinated multi-axis motion, high-speed distributed safety systems.

CC-D (TSN-Based Deterministic Ethernet)

CC-D abandons proprietary scheduling in favor of IEC/IEEE 60802 Time-Sensitive Networking (TSN) profile. Instead of PROFINET-specific firmware, CC-D uses standard IEEE 802.1 mechanisms:

Time-Aware Scheduler (Qbv): hardware gate control—a switch port can be programmed to open/close on a microsecond-granular schedule.
Frame Preemption (Qbu): allows high-priority frames to interrupt and resume lower-priority traffic mid-frame, reducing worst-case latency.
Precise Timing (802.1AS-2020 PTP): GPS-synchronized clocks across the network to nanosecond precision.
Stream Reservation (802.1Qcc / YANG model): management plane tells the network “I need 50 Mbps, <100 µs latency, <10 ns jitter”—the switch computes the schedule and responds with a reservation status.

Figure 2: TSN shapers (Qbv time-aware, Qbu frame preemption, Qav credit) replace PROFINET’s proprietary IRT switching with standards-certified determinism. Vertical slice shows per-port gate schedule; shaded regions are reserved for high-priority cyclic traffic.

Cycle time: 125 µs to 100 ms (same as IRT, now standardized).

Jitter: <100 ns, certified across multi-vendor equipment.

Advantage: hardware from any IEEE 802.1 TSN-certified vendor (not PROFINET-only); upgrade path for existing sites; regulatory alignment.

PROFINET IRT Isochronous Scheduling: The Engine Room

The reason PROFINET dominates high-speed motion control is its scheduling discipline. Here’s how a PROFINET IRT network works at layer 2.

Figure 3: IRT cycle time decomposition. Every 500 µs (example), the PROFINET schedule repeats: IRT phase (reserved slots for servo/spindle), sync frame, NRT/RT phase (acyclic + soft real-time), then idle.

Every IRT switch port maintains a time division multiplexing (TDM) schedule, regenerated in firmware every IRT period (typically 125, 250, 500 µs). The schedule has three phases:

Phase 1: IRT Reserved Slots

The first 80–90% of the cycle is allocated to IRT devices. Each device knows its transmit slot in advance (slot offset, duration, destination MAC). No arbitration; no collision detection. The switch cross-fabric forwards IRT frames deterministically—no buffering, no queue—to designated output ports in under 100 ns.

Example: A servo drive knows “I transmit at T+12 µs for 4 µs on port 3.” The switch will see that frame and output it on port 5 at T+18 µs (wire propagation + switch latency). Guaranteed.

Phase 2: NRT/RT Phase

The remaining 10–20% of the cycle handles acyclic (file upload, parameter changes) and soft-real-time (sensor polling, status updates) traffic. Standard FIFO queuing applies; buffering is allowed. Latency here is variable but bounded (worst-case < next IRT slot).

Phase 3: Synchronization

Every cycle, one device (the “sync master”) issues a PROFINET sync frame carrying a high-precision timestamp (locked to 802.1AS-2020 PTP or internal quartz). Every IRT device timestamps its reception and adjusts local clock via a phase-locked loop (PLL)—typically a proportional-integral servo that corrects ±100 ns drifts. Sub-microsecond network-wide synchronization emerges without explicit time sources.

Why Sub-µs Jitter?

The jitter budget comes entirely from deterministic sources:

Switch forwarding latency: 100 ±10 ns (fixed, measured).
NIC DMA jitter: 50 ±5 ns (hardware predictable).
Ethernet propagation: negligible at switch-to-switch distances (10 m ≈ 50 ns).
Clock correction drift: <10 ns RMS over steady state.

The absence of packet loss, buffer contention, and CPU context switches (IRT bypasses the OS, lives in NIC hardware or real-time firmware) is what makes these numbers possible.

Contrast with TSN: TSN achieves the same through centralized scheduling. A TSN manager (usually a controller or orchestration platform) computes the full network schedule offline, sends it to switches and NICs via YANG/netconf, and ensures no two streams are ever allowed to transmit in overlapping time windows. IRT is implicitly scheduled (hardcoded per-device in engineering tools); TSN is explicitly scheduled (runtime dynamic).

PROFINET over TSN (IEC/IEEE 60802): The Convergence

As of 2024, the PROFINET organization, IEEE 802.1 Working Group, and IEC have ratified IEC/IEEE 60802 Part 1: TSN PROFINET profile. This is the formal standard for running PROFINET on standards-based TSN infrastructure, not proprietary IRT switches.

Architecture Shift

Aspect	PROFINET IRT	PROFINET over TSN
Scheduling	Implicit, per-device firmware	Explicit, centralized manager
Hardware	PROFINET-certified switches only	Any IEEE 802.1 TSN-certified switch
Sync protocol	PROFINET-specific	802.1AS-2020 PTP
Stream reservation	Offline, hardcoded	Runtime, YANG/NETCONF (802.1Qcc)
Preemption	None (reserved slots)	Optional frame preemption (Qbu)
Multi-vendor	Limited (PROFINET alliance)	Full (IEEE 802.1 certified)

TSN Components in PROFINET over TSN

Time-Aware Scheduler (802.1Qbv): Each switch port has a schedule gate—a set of time windows when specific traffic classes are allowed. The manager computes a global schedule ensuring no oversubscription:

Port 1 schedule (125 µs cycle):
  [0–25 µs]   Gate 0 open (IRT servo frames)
  [25–80 µs]  Gate 1 open (RT soft-real-time)
  [80–125 µs] Gate 2 open (NRT best-effort)

Hardware enforces this in the MAC: a frame arriving at T+30 µs on a class intended for Gate 0 is buffered until the next cycle.

Frame Preemption (802.1Qbu): Allows a high-priority frame to interrupt a low-priority frame mid-transmission. Without preemption, a 1500-byte Ethernet frame at 1 Gbps blocks for 12 µs; with preemption, it yields after 64 bytes (512 ns), minimizing latency tail.

Cyclic Queuing and Forwarding (802.1Qch): Ensures frames traverse the network in a repeating time pattern—generalization of PROFINET’s IRT slots to multi-hop topologies.

Enablement Timeline

2024–2025: Intel, NVIDIA, Bosch Rexroth, Phoenix Contact, Hirschfeld release first TSN-PROFINET switches and gateways.
2025–2026: PROFINET device vendors (drives, controllers, I/O modules) ship TSN stacks; Siemens, Beckhoff add TSN support to engineering tools.
2027+: TSN expected to displace proprietary IRT in greenfield designs; legacy IRT remains for backward compatibility.

Topology, Redundancy, and Fault Tolerance

PROFINET IRT is topology-constrained: line or tree only; no rings, no loops. This is because TDM slots assume fixed paths. Redundancy is limited to:

Media Redundancy Protocol (MRP): two parallel line segments with automatic ring-opening on link failure (10 ms recovery).
Spare devices: Firmware can activate standby drives/controllers on detection of primary failure.

TSN relaxes this somewhat through FRER (Frame Replication and Elimination): the manager can duplicate high-priority frames to N paths; endpoints discard duplicates. Recovery is faster (sub-millisecond) but at the cost of higher network load.

Diagnostic complexity increases. IRT jitter is visible in cycle-time histograms; TSN schedule violations hide in gate-open/close logs and may not surfaced in real-time, requiring post-mortem trace analysis.

Trade-Offs, Gotchas, and Migration Challenges

Hardware Lock-In

PROFINET IRT devices (switches, NICs, drives) are certified against a proprietary stack. Swapping a Siemens switch for a Hirschfeld switch requires re-engineering and re-certification of timing. Vendors charge premium margins on IRT hardware. Upgrading a 20-year-old cell is economically painful.

TSN, by contrast, is commoditizing. Any vendor building an 802.1 TSN switch (Broadcom, Marvell, Microchip) can mark it compliant with the PROFINET profile. This lowers hardware costs by 30–40% but introduces a new risk: interoperability testing. Just because two vendors claim IEEE 802.1 compliance doesn’t mean their schedule managers will negotiate a reservation correctly.

Jitter Measurement Gotcha

PROFINET IRT jitter is network jitter—measured end-to-end (device A transmit to device B receive). TSN jitter is schedule jitter—deviation from programmed gate timing. A TSN schedule might be perfect (0 ns deviation) but the actual device transmission jitter still depends on the NIC driver and CPU interrupt latency. Don’t assume TSN eliminates device jitter; it eliminates network jitter.

Clock Synchronization Dependency

Both IRT and TSN rely on precise network-wide clocks. PROFINET uses a proprietary PTP variant; TSN uses IEEE 802.1AS-2020 (a stricter subset of PTP). If GPS is unavailable (underground factory, RF-poor facility), both protocols need a local grandmaster—a device running high-stability quartz or disciplined oscillator. Failure of the grandmaster causes clock divergence; divergence over 100 ns becomes visible as motion jitter in servo loops (≤1 mm at 1 m/s axis velocity).

Migration Complexity

Migrating a brownfield site from IRT to TSN involves:

Replace all PROFINET switches with TSN switches (lead time: 12–24 months for custom industrial hardware).
Upgrade NICs and drive firmware (firmware updates are free; hardware retrofit for older drives is expensive).
Deploy a TSN schedule manager (Siemens TIACloud Controller, Phoenix Contact Managed Switch Manager, or open-source Openvswitch + ONOS).
Re-engineer the network topology (may need to split rings into trees or mesh, depending on manager capability).
Re-test and re-certify all motion sequences.

For a large automotive plant (500+ devices across 50 cells), this is a 2–3 year program.

Practical Recommendations

Choose PROFINET IRT if:
– You are in a brownfield site with existing PROFINET infrastructure and no need for third-party hardware interop.
– Cycle times are <500 µs and you prioritize simplicity (implicit scheduling is easier to debug than centralized schedules).
– Your integrator has deep IRT expertise and strong vendor relationships.

Choose PROFINET over TSN if:
– You are designing greenfield or replacing aging infrastructure.
– You want to source switches and NICs from commodity vendors; your budget prioritizes CapEx over integrator hours.
– You plan to integrate non-PROFINET devices (IP cameras, monitoring systems) on the same network.
– Your site lacks 24/7 on-premise IT support; centralized scheduling is more amenable to remote management and trace logging.

Hybrid approach (recommended for most large sites):
– Core cells (motion, safety-critical) run PROFINET IRT.
– Auxiliary systems (material handling, diagnostics, OEE collection) run PROFINET over TSN or pure IP/OPC UA.
– Use a gateway device (Siemens IE/PB Link, Phoenix Contact switch) to bridge IRT and TSN domains.

Action checklist:
– Audit current network: cycle times, jitter distribution, device count, vendor landscape.
– Baseline hardware age; identify end-of-life risk (IRT switches older than 10 years are reaching EOL).
– If greenfield >50 devices: design for TSN. If brownfield <200 devices: stay IRT. If brownfield >500 devices: plan a multi-year TSN migration.
– Invest in a network performance monitoring tool (Siemens Diagnostic Suite, EtherCAT Master Trace, or open-source network analyzer) to capture baseline jitter and schedule compliance.

FAQ

What is the difference between PROFINET RT and IRT?

PROFINET RT (CC-B) relies on software scheduling on device CPUs and switch firmware to enforce ~1 ms cycle times with ±500 µs jitter. PROFINET IRT (CC-C) reserves dedicated time slots on switch hardware and NICs, achieving <1 ms cycles with <100 ns jitter. RT is cheaper and simpler; IRT is deterministic and supports high-speed motion.

Is PROFINET moving to TSN?

Yes. The PROFINET organization endorsed the IEC/IEEE 60802 TSN profile in 2024. New sites should assume PROFINET over TSN; existing IRT sites are supported for backward compatibility until ~2035, but vendors are ending support for legacy IRT hardware.

What cycle time does PROFINET IRT achieve?

IRT supports cycles from 125 µs to 100 ms. Typical motion control uses 125–500 µs (high-speed servo, spindle); typical I/O polling uses 5–10 ms. The absolute minimum is limited by switch forwarding latency (~100 ns) plus device processing; 125 µs is practical on modern hardware.

Can PROFINET run on standard Ethernet switches?

Not IRT. IRT requires PROFINET-certified switches with dedicated firmware. Standard Ethernet switches can run PROFINET RT (CC-B) or CC-D (TSN), but not CC-C (IRT) because they lack the hardware-reserved time-slot mechanism. TSN-capable switches (IEEE 802.1 certified) can run PROFINET over TSN (CC-D) once the PROFINET schedule manager is deployed.

What is PROFINET over TSN?

PROFINET over TSN (CC-D, IEC/IEEE 60802 profile) replaces PROFINET’s proprietary IRT scheduling with standards-based IEEE 802.1 Time-Sensitive Networking (Qbv time-aware shaper, Qbu frame preemption, 802.1AS-2020 PTP). It achieves sub-microsecond jitter using any IEEE 802.1 TSN-certified switch, not PROFINET-specific hardware. It is the future of PROFINET.

Schema Markup (JSON-LD)

{
  "@context": "https://schema.org",
  "@type": "TechArticle",
  "headline": "PROFINET IRT and TSN: Real-Time Industrial Ethernet Deep Dive",
  "description": "PROFINET RT vs IRT vs TSN — deterministic industrial Ethernet architecture, sub-microsecond cycle times, topology rules, and how TSN is reshaping PROFINET beyond 2026.",
  "image": "/wp-content/uploads/2026/04/profinet-irt-tsn-real-time-industrial-ethernet-guide-hero.jpg",
  "author": {
    "@type": "Person",
    "name": "Riju"
  },
  "publisher": {
    "@type": "Organization",
    "name": "iotdigitaltwinplm.com",
    "logo": {
      "@type": "ImageObject",
      "url": "https://iotdigitaltwinplm.com/logo.png"
    }
  },
  "datePublished": "2026-04-23T10:00:00+05:30",
  "dateModified": "2026-04-23T10:00:00+05:30",
  "mainEntityOfPage": "https://iotdigitaltwinplm.com/industrial-iot/profinet-irt-tsn-real-time-industrial-ethernet-guide/",
  "proficiencyLevel": "Expert",
  "estimatedReadingTime": "PT15M",
  "keywords": ["PROFINET", "IRT", "TSN", "Time-Sensitive Networking", "Industrial Ethernet", "Real-Time", "Deterministic", "IEEE 802.1"]
}

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is the difference between PROFINET RT and IRT?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "PROFINET RT (CC-B) relies on software scheduling on device CPUs and switch firmware to enforce ~1 ms cycle times with ±500 µs jitter. PROFINET IRT (CC-C) reserves dedicated time slots on switch hardware and NICs, achieving <1 ms cycles with <100 ns jitter."
      }
    },
    {
      "@type": "Question",
      "name": "Is PROFINET moving to TSN?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. The PROFINET organization endorsed the IEC/IEEE 60802 TSN profile in 2024. New sites should assume PROFINET over TSN; existing IRT sites are supported for backward compatibility until ~2035."
      }
    },
    {
      "@type": "Question",
      "name": "What cycle time does PROFINET IRT achieve?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "IRT supports cycles from 125 µs to 100 ms. Typical motion control uses 125–500 µs (high-speed servo, spindle); typical I/O polling uses 5–10 ms."
      }
    },
    {
      "@type": "Question",
      "name": "Can PROFINET run on standard Ethernet switches?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Not IRT. IRT requires PROFINET-certified switches with dedicated firmware. Standard Ethernet switches can run PROFINET RT (CC-B) or CC-D (TSN), but not CC-C (IRT)."
      }
    },
    {
      "@type": "Question",
      "name": "What is PROFINET over TSN?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "PROFINET over TSN (CC-D, IEC/IEEE 60802 profile) replaces PROFINET's proprietary IRT scheduling with standards-based IEEE 802.1 Time-Sensitive Networking. It achieves sub-microsecond jitter using any IEEE 802.1 TSN-certified switch."
      }
    }
  ]
}

Frequently Asked Questions

Is IEC/IEEE 60802 finished, and does it replace PROFINET IRT?

The IEEE 802.1 TSN pages list IEC/IEEE 60802 as a published standard dated 29 June 2026. It defines TSN profiles for industrial automation by selecting features, options, defaults and procedures for bridges, end stations and LANs. It does not replace PROFINET IRT by itself. It is a Layer 2 network profile, and PROFINET over TSN is how PROFINET uses that layer. IRT remains in the PROFINET specification, so existing CC-C installations are not invalidated by the standard.

What is PROFINET over TSN, and what is Conformance Class D?

PI describes PROFINET over TSN as adding TSN as an additional Layer 2 technology to PROFINET, delivered in specification V2.4. Conformance Class D is the class that summarizes PROFINET over TSN. PI says manufacturers can add CC-D to existing devices as an extra function or build new devices with CC-D only. The aim is to keep the IRT strengths (time accuracy, reproducibility, bandwidth reservation, diagnostics) while using standard hardware instead of IRT-specific switch silicon.

Do RT and IRT disappear now that TSN is available?

No. PI states that RT and IRT remain part of the PROFINET specification, and that PROFINET over TSN is intended to cover both IRT and RT application areas. In practice, that means brownfield lines keep running CC-B and CC-C, and new designs can choose CC-D where the switches, controllers and engineering tools support it. Any specific end-of-support dates quoted for legacy IRT hardware should be confirmed with each vendor, since they are product decisions and not part of the PROFINET specification.

Can I run PROFINET over TSN on any TSN switch?

Not automatically. A switch must implement the IEEE 802.1 functions the profile requires, such as time synchronization and scheduled traffic, and the PROFINET device or controller must support CC-D with its configuration model. Treat “TSN-capable” as a starting point and check the vendor’s stated conformance to IEC/IEEE 60802 and PROFINET CC-D. Standard unmanaged Ethernet switches do not provide the scheduling needed for IRT-class determinism, though they can carry non-real-time traffic and, within limits, RT traffic.

How does OPC UA FX relate to PROFINET over TSN?

They address different layers of the stack. OPC UA FX is the OPC Foundation’s field-level exchange framework for controller-to-controller and controller-to-device communication, and it is designed to run over TSN-capable Ethernet. The OPC Foundation’s March 2026 update describes a staged UAFX 1.00 release, with Part 81 and Part 84 at release-candidate level, and TSN-based real-time prototyping still being planned. PROFINET over TSN and OPC UA FX can therefore share the same TSN network infrastructure, which is the point of a converged profile.

Should a new plant choose IRT or PROFINET over TSN today?

It depends on the installed base and the supply chain. If your controllers, drives and I/O all offer CC-D and your engineering tool supports TSN configuration, a TSN-based design avoids dependence on PROFINET-specific switch hardware and aligns with a published IEC/IEEE standard. If you need proven motion control with a mixed brownfield fleet, IRT remains a mature, fully specified option. Run a pilot cell, measure cycle time and jitter on your own hardware, and compare results before standardizing on either approach.

Sources for This Refresh

IEEE 802.1, “IEC/IEEE 60802 TSN Profile for Industrial Automation” (listed as published standard, 29 June 2026). https://1.ieee802.org/tsn/iec-ieee-60802/
PROFIBUS and PROFINET International, “PROFINET over TSN” (specification V2.4, Conformance Class D). https://www.profibus.com/technology/industrie-40/profinet-over-tsn
OPC Foundation, “Field Level Communications Corner, March 2026” (UAFX 1.00 staged release). https://opcconnect.opcfoundation.org/2026/03/field-level-communications-corner-march-2026/
OPC Foundation, OPC UA FX specification overview. https://opcconnect.opcfoundation.org/?p=3956

By Riju – about