Why PROFINET IRT, not just RT?

Standard PROFINET RT runs on a best-effort cycle of 1 ms and is fine for I/O, valve manifolds, and most frequency inverters. PROFINET IRT (Isochronous Real-Time), however, reserves a dedicated time slice inside the bus cycle so that the drive setpoints and actual values are exchanged in a tightly bounded phase. For a Siemens S7-1500 CPU 1515-2 PN or 1517-3 PN driving SINAMICS S120 via PROFIdrive profile 4, IRT is the only way to achieve the <1 µs jitter required by cam discs, flying shear, and electronic line shafting on a packaging line.

Before you touch TIA Portal, validate three things on the plant floor: managed industrial Ethernet switches (SCALANCE XC-200 or XR-500 family), CAT6A cabling within the 100 m segment limit, and a clear star or line topology that the IRT planner can accept.

Step 1 — Build the Hardware Topology First

Open TIA Portal V18, create a new S7-1500 station, and drag the CPU 1515-2 PN into Device view. The two PN ports (X1, X2) are your IRT-capable interfaces; reserve X1 for the IRT sync domain and X2 for diagnostics on a separate subnet. Import the SINAMICS S120 GSDML file (STARTER or Startdrive ships the latest) before you add drives — this ensures the PROFIdrive telegrams (Standard Telegram 3, Siemens Telegram 105, or 111 for servo) are recognized.

Wire the topology in the Topology Editor: every port, every cable, every switch must be present. IRT refuses to download if there is even one unknown link in the path between the controller and the drive.

Step 2 — Configure the IRT Domain and Sync Interval

Right-click the PROFINET interface → Properties → Real-Time Settings. Set the Send clock to 500 µs (or 250 µs if the drives and switch support it). The Reduction Ratio then defines how many send-clock cycles make up one IRT phase; start with a ratio of 1:1 for the sync master and accept the auto-derived phase offset. Enable "Synchronize the PN interface with the CPU clock" so the OB91 (Synchronous Cycle) interrupts fire predictably.

Assign the IO controller as the Sync Master. All other PROFINET nodes become Sync Slaves. If you mix SCALANCE switches, ensure the "Cut-through" forwarding mode is enabled on the IRT ports; store-and-forward adds jitter that defeats the IRT budget.

Step 3 — Map PROFIdrive Telegrams and Axis Telegrams

In the S120 drive object's Device view, add the telegram(s) you will use. For a typical servo axis, Standard Telegram 5 plus the supplementary Siemens Telegram 111 gives you torque, speed, and position in one frame. In the PLC's Technology Objects (TO-Axis), reference the same telegram so the cyclic data matches. A mismatch here is the single most common cause of F08501 (PROFIdrive fault) during commissioning.

Step 4 — Verify with the Topology and Trace Tools

Before running motion, open the Online → Topology view and confirm every node reports IRT capability. Then use the Trace tool to record the OB91 phase jitter — a healthy IRT network stays below 1 µs of jitter at the sync slave. If jitter spikes, check for broadcast storms, unmanaged switches, or duplex mismatches.

Common Commissioning Pitfalls to Avoid

• Incomplete topology: A single unknown link blocks the IRT download. Wire every port, cable, and switch in the Topology Editor.
• Telegram mismatch: Different telegrams on the drive and TO-Axis trigger F08501. Reference the same telegram on both sides.
• Unmanaged or store-and-forward switches: These inject jitter that breaks the IRT budget. Use SCALANCE managed switches with cut-through forwarding.
• GSDML/firmware version skew: Always match the GSDML version to the drive firmware before adding devices.
• Skipping the jitter trace: Never run a mechanical trial before confirming <1 µs jitter at the sync slave.