Resolving SINAMICS S210 PROFINET IRT Compile Errors on SCALANCE X500

The SINAMICS S210 servo drive system communicates with the SIMATIC S7-1500 controller over PROFINET, and the default configuration forces the drive onto a PROFINET IRT (Isochronous Real-Time) subnet. The SCALANCE X-500 family of managed Layer 3 switches, including the SCALANCE XT524-8C (MLFB 6GK5 248-0GS00-2AR2 / 6GK5 248-0GS00-2AR2 regional variants such as 6GK 524-8GS00-2AR2), provides PROFINET RT support but does not advertise IRT capability with the cut-through latency class required by SIMATIC S210 technology objects. The result is an HW Config compile error, a topology alarm, and a non-fatal but unacceptable commissioning state. This article documents the root cause, the affected firmware and hardware revisions, the diagnostic workflow, and three engineering-valid solution paths.

1. Problem Description

A typical installation that produces the compile error looks like this:

• SIMATIC S7-1500 CPU (e.g. 1515-2 PN, 1516-3 PN/DP, 1517-3 PN/DP, 1518-4 PN/DP) with a PROFINET X1 or X2 interface assigned to the drive subnet.
• One or more SINAMICS S210 servo converters, e.g. 6SL3210-5HB10-1UF0 / 6SL3210-5HB10-2UF0 / 6SL3210-5HB10-4UF0 (1-axis, 1/2/4 A rated).
• SCALANCE X-500 managed switch, in the case study the SCALANCE XT524-8C (6GK 524-8GS00-2AR2) with 4 GE + 4 combo ports.
• TIA Portal V17 / V18 / V19 with the SINAMICS S210 HSP (Hardware Support Package) installed.

When the user places the S210 in the Devices & Networks view, assigns it to the CPU's PROFINET subnet, and clicks Compile > Hardware (only), the following class is reported:

1. "The PROFINET IO device SINAMICS S210 requires PROFINET IRT on the connected subnet."
2. "The PROFINET IO device SINAMICS S210 requires a sync domain that includes a PROFINET IO controller and PROFINET IO device with the same IRT option."
3. "The PROFINET IO device SINAMICS S210 is connected to a switch that does not support the required IRT option."
4. Depending on topology editor state: "A port partner was not assigned in the topology view."

The drive port is shown with a yellow warning, the sync domain remains in RT class, and the IO cycle is reported at 128 ms (X500 default sync) instead of the S210 mandated 1 ms / 250 µs / 500 µs / 2 ms isochronous cycle.

2. Why SINAMICS S210 Forces PROFINET IRT

The S210 is part of the SINAMICS S210 converter family paired with 1FK2 / 1FS2 servomotors. It implements the PROFINET profile PROFIdrive (PN) V4.2 with extended PROFIsafe and isochronous mode. Siemens deliberately ties the drive to IRT for the following reasons:

• Closed-loop control determinism. The S7-1500's TO (e.g. TO_SpeedAxis, TO_PositioningAxis, TO_SynchronousAxis) and the S210's internal current/velocity controller need a fixed, jitter-bounded bus cycle. IRT with cut-through switching delivers end-to-end jitter well below 1 µs; RT only guarantees best-effort and lets store-and-forward latency grow with load.
• Telegram 105 dependency. Standard Telegram 105 (and its 2-position variant Telegram 106) for servo axes transmits setpoints, actual values, encoder raw data, and the DSC (Dynamic Servo Control) fine interpolation. The 32-byte payload, the 1-ms cycle, and the fine-grained ramp generators are only declared as supported under IRT in the device description.
• Technology module requirement. TIA Portal's technology object (TO) for the S210 is delivered as a "technology module" in HW Config. The TO's Isochronous Mode property is hard-coded to Yes (IRT) by the HSP and cannot be demoted to RT.

Even when the user manually selects Telegram 102 (8-byte standard drive telegram) the S210 will still default the device to IO Device IRT in the device properties, because the drive's GSDML-PNIRTVx.y.z.xml is only released for IRT operation. Only by deleting the technology module and the servo-grade telegram can the device be coerced into RT operation, and even then the cycle time will drift above the 1 ms target.

3. SCALANCE X-500 Series: Capabilities and Limits

The SCALANCE X-500 line is Siemens' high-end managed Industrial Ethernet platform. It is positioned as the central routing/switching node for plant networks and supports Layer 3 functions (OSPF, VRRP, static routing) plus PROFINET RT with QoS and priority tagging (PROFINET Class 1, 2, 3 / VLAN priority 6/7). The series includes:

None of the X-500 platform members implement the IRT forwarding plane, the FSU (Frame Slotted Update) scheduler, or the dynamic frame packing required by PROFINET IRT Class 2 / 3. They are correct choices for routing the plant's standard TCP/IP traffic, video, MQTT, and PROFINET RT devices such as ET 200SP in RT mode, but they cannot be inserted into a drive-grade IRT sync domain. The Mouser product brief confirms the X-500 family positioning as "demanding network tasks and … central component of large Industrial Ethernet networks", which is the management plane use case, not the motion-control plane.

4. IRT-Capable SCALANCE Switches: The Alternative Set

Siemens offers dedicated IRT-capable switches in three lines. Use one of these in the path between the S7-1500 PROFINET port and the S210. The X-500 stays in place as the plant backbone if needed; it just cannot sit inline with the S210 sync domain.

IRT "High Performance" is the only IRT option TIA Portal accepts for S210; "IRT" (non-High Performance) is a weaker option used by older S7-300 / S7-400 motion projects and is rejected by the S210's GSDML with the same error class.

5. Root Cause Analysis

The HW Config compile error has a single, deterministic root cause:

1. Drive demands IRT. The S210 HSP / GSDML lists only IRT for the default Telegram 105 configuration and for every technology object. The S7-1500 IRT property on its PROFINET port is therefore forced to IRT High Performance as soon as the S210 is added.
2. Switch cannot speak IRT. The SCALANCE X-500 (XT524-8C and the rest of the X-500 family) supports PROFINET RT and PROFINET prioritization but is not an IRT node. TIA Portal's topology check (in the Devices & Networks > Topology view) flags the port partner as not IRT-capable.
3. Sync domain becomes invalid. When a non-IRT node is part of an IRT sync domain, the entire sync domain falls back to RT and the IRT option is downgraded. The S210's TO then detects the IRT requirement mismatch and reports an alarm ("IRT not available on subnet") at run time even if the compile is forced through.

The behavior observed with the ET200SP on the same X-500 switch is correct and expected: ET200SP in RT mode (the default for distributed I/O) is fully compatible with the X-500's RT forwarding plane. The mismatch is drive-specific, not a global switch defect.

6. Diagnostic Workflow

Run this checklist before changing hardware to confirm the issue is switch-related and not, e.g., a wrong HSP or a sync master conflict.

1. Confirm drive subnet IRT class. In TIA Portal, open the CPU's PROFINET interface and read Properties > PROFINET interface > Real-time settings > Send clock. It must be 1 ms (or 0.5 ms / 2 ms with reduced sub-cycle). 128 ms is the RT fallback the user reported and is the smoking gun.
2. Read the S210 device properties. S210 > Properties > PROFINET interface > Real-time settings: IRT option = IRT High Performance. If this is missing, the HSP is outdated.
3. Inspect the sync domain. Devices & Networks > Sync domains shows the IRT domain members. With the X-500 in line, the S210 is shown as RT, which proves the downgrading.
4. Check topology editor. In the topology view, the X-500's port objects do not show IRT-capable; they show RT only. This is the structural reason for the error.
5. Read the device diagnostics buffer. On the live S210 (web server or Starter / Startdrive commissioning tool), the diagnostic buffer reports the F01900 / F08501 family of events when IRT is missing.
6. Cross-verify with ET200SP. Drop an ET200SP into the same subnet in TIA Portal. It will compile in RT with the X-500 without error. This confirms the X-500's RT capability is intact and isolates the problem to the drive's IRT requirement.

7. Solution Path A — Replace the In-Line Switch with an IRT-Capable SCALANCE

This is the recommended path when the S210 must use Telegram 105 with a S7-1500 technology object. The X-500 stays in the plant backbone, but the S210 sync domain is split off onto a dedicated IRT switch that is line-of-sight to the CPU PROFINET port.

1. Insert the IRT switch. Add a SCALANCE X-200 IRT, XC-200 IRT, or XF-200 IRT device from the hardware catalog directly into the S7-1500 PROFINET subnet. The X-500 stays in the parallel plant network, not in the S210 sync domain.
2. Wire CPU port to IRT switch. Connect the S7-1500 PROFINET X1 (or X2, depending on slot mapping) to a fixed-port of the IRT-capable switch, e.g. port 1 of an X204-2 IRT. Mark the cable in the topology editor with the correct cable length and signal delay.
3. Wire S210 to the IRT switch. Connect the S210 PROFINET port X150 P1 or P2 to a second port of the IRT switch.
4. Re-run compile. Compile > Hardware (only). The send clock should now collapse to 1 ms and the IRT option is IRT High Performance.
5. Download and verify. Download the project, go online with the S210 in Startdrive, and confirm Diagnostics > Communication > PROFINET status shows IRT active.

8. Solution Path B — Reconfigure Telegram and Drop the Technology Object

If the X-500 must remain in line for cost or topology reasons, the drive can be coerced onto PROFINET RT by removing the S210-specific telegrams and the technology object. The drive then runs in a profile that does not require isochronous mode, with the S7-1500 doing the position control in Standard Telegram 1 / Standard Telegram 102 at a relaxed cycle.

1. Delete the technology module. In Devices & Networks, right-click the S210's technology slot and choose Delete. This removes the TO binding and the S210 will fall back to drive-internal control.
2. Change the telegram. S210 > Properties > PROFINET interface > Telegram configuration. Replace Telegram 105 with Telegram 1 (speed setpoint, 4-byte) or Telegram 102 (8-byte). Telegram 102 is a common middle ground that still allows a S7-1500 standard axis without TO scoping.
3. Accept IRT downgrade. TIA Portal will warn that the subnet IRT option is being downgraded. Acknowledge the warning, then verify the X-500's RT plane can sustain the chosen send clock (typically 4 ms to 8 ms for non-isochronous RT).
4. Re-run compile. Compile should now succeed with the X-500 in line. The S210 will, however, lose its 1-ms isochronous profile; this is the explicit trade-off.

9. Solution Path C — Mixed Topology: S210 on IRT island, RT devices on X-500

When the cabinet has both motion axes (S210) and distributed I/O (ET 200SP / ET 200MP / HMI panels), split the PROFINET network into two subnets sharing a single physical S7-1500 CPU:

• Subnet 1 (IRT). S7-1500 PROFINET X1 → SCALANCE XC-200 IRT → SINAMICS S210. Telegram 105, technology object, 1 ms.
• Subnet 2 (RT). S7-1500 PROFINET X2 (second PN port) → SCALANCE X-500 (XT524-8C) → ET 200SP RT, HMI, third-party RT drives. No isochronous requirements.

This pattern is the most common in real cell designs. The X-500 handles plant-class traffic; the IRT switch handles motion. Both ports are aggregated by the S7-1500 CPU. The CPU's PROFINET interface X1 and X2 each carry their own sync domain; the sync domains do not share an IRT scheduler.

10. TIA Portal Configuration Steps (Path A, step-by-step)

Tested with TIA Portal V18 Update 2, SINAMICS S210 HSP V18, and S7-1500 CPU 1515-2 PN.

1. Open the project. Confirm the SINAMICS S210 HSP and the SCALANCE XC-200 IRT HSP are installed (Options > Support Packages).
2. In the project tree, drag a SCALANCE XC-200 IRT (e.g. 6GK5 206-2BS00-2NA2) onto the Devices & Networks canvas. Place it next to the S7-1500.
3. Drag the SINAMICS S210 onto the same canvas.
4. Use Connect to draw a PROFINET subnet from the S7-1500 PROFINET port X1 through the SCALANCE XC-200 IRT to the S210 PROFINET port. Use the topology view to add the S7-1500, the SCALANCE IRT, and the S210 to the same Sync Domain 1.
5. Set the S7-1500 PROFINET port to IRT High Performance, send clock 1 ms, and check Synchronize to equidistant.
6. Set the SCALANCE IRT to IRT High Performance. The IRT switch accepts the sync-master role automatically because the CPU is the sync master.
7. Set the S210 to IRT High Performance, Telegram 105, DSC enabled, encoder 1 = motor encoder, encoder 2 = external (or disable external).
8. Add a TO TO_PositioningAxis on the S7-1500, link the TO to the S210 telegram.
9. Compile the hardware. Expected result: no errors, send clock 1 ms, sync domain valid.
10. Download HW Config and the TO configuration. Go online with the S210 in Startdrive to validate.

11. Verification Checklist

Run this checklist after any of the three solution paths:

12. Field-Proven Caveats and Edge Cases

• Second PROFINET port of the S7-1500. When both X1 and X2 carry IRT drives, both ports must be IRT High Performance and both sync domains must be independent. The X-500 is acceptable on a second, non-IRT subnet of the same CPU.
• Cable length and signal delay. Even on an IRT switch, port-to-port cable lengths must be entered in the topology editor. Long copper links (over 100 m) at 100 Mbit/s may force a longer send clock. Consider fiber SC ports on the XC206-2SFP IRT for the CPU uplink when the cabinet-to-cabinet distance exceeds 80 m.
• Firmware versions. SCALANCE XC-200 IRT requires firmware V2.0 or later for full TIA Portal V18 / V19 IRT support. SCALANCE X-200 IRT family (X204-2 IRT) requires firmware V4.4 or later for S210 compatibility. Always update to the latest firmware from the Siemens Industry Online Support portal before commissioning.
• Web server access on the X-500. The X-500 will still respond to web, SSH, and PROFINET discovery even when the S210 on its RT-only path is failing. Do not interpret a reachable X-500 as evidence that the network is good.
• MC (Motion Control) licensing. The S7-1500 TO for the S210 requires a Motion Control runtime license. Even with a perfectly tuned IRT network, a missing license will block the axis without a network alarm. Verify licensing before chasing topology errors.
• PROFIsafe and PROFIenergy. The S210 supports PROFIsafe over the same IRT port. Adding a PROFIsafe slot does not change the IRT requirement; the switch requirement stands.
• Third-party PROFINET drives. A non-Siemens PROFINET drive may declare RT only and will work on the X-500. Do not generalize from third-party RT devices to the S210's IRT requirement.

13. Related Siemens References

The original diagnostics and the IRT option requirements for SINAMICS S210 are documented in the S210 function manuals, the S7-1500 motion control function manual, and the SCALANCE X-500 / XC-200 IRT operating instructions on Siemens Industry Online Support. Always cross-check the HSP readme, the GSDML revision, and the SCALANCE firmware release notes before commissioning a new motion cell.

14. FAQ