Configuring Siemens CP5624 with WinAC RTX F: TIA Setup

David Krause13 min read
ProfibusSiemensTutorial / How-to
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

Overview: CP5624 as PROFIBUS Interface for WinAC RTX F

The Siemens CP 5624 (6GK1562-4AA00) is a PCI Express PROFIBUS communication processor that supports DP-Master and DP-Slave operation at 9.6 kbit/s through 12 Mbit/s. It can be inserted into a SIMATIC WinAC RTX F station as the PROFIBUS interface and, in current TIA Portal versions, the controller is allowed to use the CP 5624 as its sole DP-Master for downstream PROFIBUS-DP slaves such as ET 200S stations and PROFIBUS-capable drives such as the Fuji Frenic-Mega inverter family.

WinAC RTX F is a software-based fail-safe controller that runs on top of the Venturcom RTX (Real-Time eXtension) real-time subsystem under Windows. The fail-safe (F) variant adds a second F-runtime (F-CPU) and the PROFIsafe protocol on PROFIBUS-DP, which is the reason the CP 5624 is being assigned to the WinAC station rather than to the host PC's general Windows networking stack.

This tutorial covers the supported configuration path: WinAC RTX F V4.6 in TIA Portal V13 SP1 (or later) using CP 5624 as DP Master. The example slaves are an ET 200S distributed I/O station and a Fuji Frenic-Mega inverter on the same PROFIBUS segment.

Important: The CP 5624 is supported by WinAC RTX F as DP Master only in this configuration. The CP 5623 (PCI variant) is functionally similar but uses a different PCI bus; the assignment procedure in TIA Portal is identical. Always confirm the firmware of the CP 5624 and the installed version of the SIMATIC NET PC software before commissioning.

Hardware and Software Prerequisites

Component Requirement Notes
PC platform Siemens-certified IPC or industrial PC with free PCI Express x1 slot WinAC RTX (F) 2010 manual recommends an exclusive, non-shared PCI/PCIe interrupt for the communication module
CP 5624 6GK1562-4AA00 (PCIe x1, PROFIBUS DP, 12 Mbit/s) PROFIBUS-DP master and slave support, DP-V0/V1/V2
WinAC RTX F 6ES7671-1RC08-... (V4.6) or later Includes F-runtime for PROFIsafe
RTX runtime Venturcom / IntervalZero RTX matching the WinAC version Install before WinAC RTX F
SIMATIC NET PC Version matching the CP 5624 firmware and WinAC RTX F version Installs CP 5624 Windows driver and diagnostic
TIA Portal V13 SP1 minimum, V14/V15/V16/V17/V18 recommended The "Interface Assignment" property is first available in V13 SP1
PROFIBUS cable Siemens PROFIBUS FC cable, terminated at both ends Use 9-pin D-sub on CP 5624 with PROFIBUS connector with terminating resistor

Before opening TIA Portal, verify in SIMATIC NET Commissioning that the CP 5624 is visible as a PROFIBUS interface, that the firmware revision is detected, and that the PCIe interrupt is not shared. The WinAC RTX (F) 2010 manual explicitly calls out the requirement for an exclusive (non-shared) interrupt for PCI/PCIe-based communication modules. The CP 5624 with WinAC RTX F behaves like a CP 1604 / CP 1616 from an interrupt perspective - shared interrupts can lead to sporadic F-runtime stop events.

TIA Portal Version Requirements

The "Interface Assignment" property on the CP 5624 in the device view is the mechanism that binds the PROFIBUS channel to the WinAC RTX F controller. According to Siemens Support, this property is not present in TIA Portal V13 and is first implemented in V13 SP1. A field-engineered workaround in V13 was to use the CP 5624's DP-Master system directly in OB61 without an explicit assignment - this only worked because the WinAC F-runtime picked up the master's slot implicitly, and it is not a supported configuration in production.

TIA Portal version Interface Assignment visible? DP-Master operation with WinAC RTX F V4.6
V13 No Implicit (OB61) only - not recommended
V13 SP1 Yes Supported as DP Master
V14 / V14 SP1 Yes Supported as DP Master
V15 / V15.1 / V16 / V17 / V18 Yes Supported as DP Master
If only V13 is available, upgrade to V13 SP1 or later before attempting the interface assignment. Siemens officially supports DP-Master operation of the CP 5624 with WinAC RTX F V4.6 in TIA Portal V13 SP1 and newer.

Step-by-Step: Creating the WinAC RTX F Project

  1. Create a new project in TIA Portal V13 SP1 (or newer). Choose Create new project → PC Systems rather than a generic PLC project, because WinAC RTX F is a PC-based controller.
  2. Insert the SIMATIC Controller Application: in the project tree, right-click the new PC station → Insert new device → SIMATIC Controller Application → WinAC RTX F V4.6. The catalog entry exposes the F-capable software controller and its F-runtime.
  3. Verify the catalog entry: confirm that the inserted controller is the F variant. The device name and version should read SIMATIC WinAC RTX F V4.6. A non-F WinAC RTX will be shown without the F-runtime and will not allow PROFIsafe programs.
  4. Open the Device view of the PC station. The WinAC RTX F controller now occupies the controller slot. The PCI slots of the host PC are still empty - this is where the CP 5624 will be inserted.

Step-by-Step: Inserting and Assigning the CP 5624

  1. In the Device view, open the hardware catalog and navigate to Communication modules → PROFIBUS → CP 5624.
  2. Drag the CP 5624 into an empty PCI Express slot of the PC station. The module appears in the rack overview with its PROFIBUS interface port.
  3. Select the CP 5624 in the device view. The Properties pane opens on the right side.
  4. In the Properties pane, expand Interface Assignment. This dialog only appears in TIA Portal V13 SP1 or later. Set the assignment so that the CP 5624 is bound to the WinAC RTX F controller (not to the host PC or to a non-existent application). The dropdown lists all controller-type slots in the PC station; pick the WinAC RTX F V4.6 instance.
  5. Confirm that the PROFIBUS interface of the CP 5624 is now shown with a green link icon pointing to the WinAC RTX F. If the link icon is red or absent, the assignment has not been made and the master will not run.
Tip: When the assignment is correct, the CP 5624 is no longer free for Windows applications such as SIMATIC Manager or HMI panels. Attempting to use the same CP 5624 from a PC application will fail with a "bus access conflict" error.

Configuring the DP Master System

With the CP 5624 assigned to WinAC RTX F, configure the DP-Master system on the CP 5624's PROFIBUS port:

  1. Right-click the PROFIBUS interface of the CP 5624 and select Add master system. A new DP-Master system line appears below the CP 5624.
  2. Open the master system properties and set the PROFIBUS address of the CP 5624 (default 2, range 1-126, master address 1-7 reserved for host/master class 1).
  3. Set the baud rate to the highest rate the entire segment supports. Standard DP baud rates are 9.6 kbit/s, 19.2 kbit/s, 45.45 kbit/s, 93.75 kbit/s, 187.5 kbit/s, 500 kbit/s, 1.5 Mbit/s, 3 Mbit/s, 6 Mbit/s, and 12 Mbit/s. For ET 200S plus Fuji Frenic-Mega on a single short segment, 1.5 Mbit/s is typical.
  4. Configure the bus profile to DP (not Universal). The WinAC RTX F controller is the master, and standard DP slaves are expected.

Connecting DP Slaves: ET 200S and Fuji Frenic-Mega

Once the master system exists, drop the DP slaves into it from the hardware catalog.

ET 200S Slave

  1. Open the hardware catalog and navigate to Distributed I/O → ET 200S → Interface modules → IM151-1 Standard (or the variant matching the field hardware).
  2. Drag the IM 151-1 onto the DP-Master system. A new slave station appears with the next free PROFIBUS address.
  3. Assign a fixed PROFIBUS address (for example 3) and configure the address to match the DIP switch setting on the physical IM 151-1 module.
  4. Insert the required I/O modules (digital input, digital output, analog modules) into the slots of the IM 151-1 station in the same order as they are physically clipped onto the backplane.
  5. If a PROFIsafe F-module is present (e.g. 4/8 F-DI, 4 F-DO), it is added as an F-module slot and later assigned a PROFIsafe address (F-source address 1, F-destination address assigned automatically by the F-runtime).

Fuji Frenic-Mega Inverter as DP Slave

The Fuji Frenic-Mega family (FRENIC-MEGA series) supports PROFIBUS-DP via the optional PROFIBUS-DP communication card (OPC-PRB / OPC-PR1 / similar, depending on the inverter series and release). In TIA Portal, the GSD file provided by Fuji is imported first:

  1. Install the Fuji GSD file (e.g. FUJI0A1F.GSD or the current release) into TIA Portal: Options → Manage general station description files (GSD).
  2. After the import, the Fuji inverter appears in the hardware catalog under Other field devices → PROFIBUS-DP → Drives → Fuji Electric → FRENIC-MEGA.
  3. Drag the inverter onto the master system and assign PROFIBUS address 4 (or as set on the card's DIP switches).
  4. Map the process data slots: typically PPO type 1 (4 PKW words + 2 PZD words) or PPO type 3 (0 PKW + 2 PZD) for cyclic control word / status word / setpoint / actual speed. If the inverter is non-safety, it operates on standard DP; for PROFIsafe safe stop, a separate safety module path is required.

PROFIsafe and OB61 Considerations

WinAC RTX F uses OB61 (synchronization to the PROFIsafe slot) to run the F-runtime in lock-step with the PROFIBUS cycle. With CP 5624 as the master, the OB61 must be configured to match the master system cycle, typically 10 ms or 20 ms:

  • Open WinAC RTX F → Properties → F-runtime → F-OB and verify that OB61 is selected as the F-OB.
  • Confirm the OB61 phase / priority matches the F-application generation in the safety program.
  • Assign each F-module a unique PROFIsafe F-destination address (1..65534). WinAC RTX F automatically assigns the F-source address; the default is 1 for the first F-CPU.

If a CP 5624 is used in TIA Portal V13 (no Interface Assignment) with WinAC RTX F, the F-runtime still uses the CP 5624 master system for OB61 implicitly. This is a useful diagnostic path to test the F-runtime in isolation, but it should not be shipped to production.

Configuration Example: Topology Diagram

Industrial PC WinAC RTX F V4.6 CP 5624 (PCIe) (Interface Assignment) PROFIBUS 12 Mbit/s max ET 200S Addr 3 (IM151-1) Fuji Frenic-Mega Addr 4, PPO type 1 Terminator ON

Verification and Commissioning

After the configuration is downloaded, validate end-to-end operation:

  1. Compile the PC station - any "Interface Assignment missing" or "CP 5624 not assigned to a controller" error must be resolved before download.
  2. Download the project to the target PC. The WinAC RTX F starts the F-runtime, and the CP 5624 should light its PROFIBUS activity LED.
  3. Open Online → Accessible nodes in TIA Portal and confirm the ET 200S and Fuji inverter appear with the expected PROFIBUS addresses.
  4. Use the SIMATIC NET Commissioning tool or the CP 5624 diagnostic page to confirm DP state = Operate and check bus statistics (repeat counts, slave diagnostics).
  5. For PROFIsafe, sign in to the F-CPU with the safety password and check the standard F-runtime log for "F-communication established" messages for every F-destination address.
  6. Run a test program that toggles a non-safety digital output on the ET 200S, monitors it in the I/O monitor, and writes a setpoint word to the Frenic-Mega to verify the PZD round trip.

Troubleshooting Matrix

Symptom Likely Root Cause Corrective Action
CP 5624 not visible in TIA Portal hardware catalog SIMATIC NET PC or hardware support package not installed for the TIA version Install the matching HSP for CP 5624 in TIA Portal Options → Manage HSP
"Interface Assignment" property is missing TIA Portal V13 (no SP) Upgrade to V13 SP1 or later
CP 5624 cannot be assigned to WinAC RTX F WinAC RTX F V4.6 not inserted, or non-F variant inserted Re-insert the F variant from the catalog; the assignment list shows only F-capable controllers
Master system present, OB61 does not run Interface Assignment not made; F-OB configuration wrong Re-do the assignment; verify OB61 selected in F-runtime properties
Slaves do not appear online PROFIBUS address mismatch, missing termination, GSD not imported (Fuji) Verify DIP switches on the slaves, terminate both ends, re-install Fuji GSD
CP 5624 reports shared interrupt BIOS / chipset shares the PCIe interrupt with another device Reserve an exclusive interrupt in the BIOS; WinAC RTX (F) 2010 manual calls this out for CP 1604/CP 1616, same rule applies to CP 5624
Sporadic F-stop with no bus errors RTX version mismatch with WinAC RTX F build Re-install RTX matching the WinAC version; confirm the SIMATIC NET PC version
Fuji Frenic-Mega does not respond to PZD writes Wrong PPO type, or PKW slot mapped to write-disabled area Set the inverter to PPO type 1 or 3 as supported by the card; clear PKW if unused

Reference Documentation

For additional context, consult the official Siemens documentation for the WinAC RTX (F) 2010 platform and the S7-1200 / general TIA Portal communication reference. The WinAC RTX (F) 2010 manual covers the interrupt and PCI/PCIe slot assignment rules for CP 1604, CP 1616, and Intel PRO/1000 GT, which apply in principle to the CP 5624 as a PCIe PROFIBUS module. The TIA Portal S7-1200 manual collection includes a configuration example for a SIMATIC communication processor (CM 1241) that follows the same device-configuration paradigm as the CP 5624 in WinAC RTX F.

Field Notes and Best Practices

  • Always upgrade to TIA Portal V13 SP1 or newer before commissioning a CP 5624 + WinAC RTX F pairing; V13 cannot perform the interface assignment, and the implicit OB61 path is not a production-grade configuration.
  • Use the same TIA Portal version on the engineering station as the one used to install the WinAC RTX F runtime on the target PC. Mismatched versions can cause project-compatibility errors during download.
  • Keep the PCIe slot for the CP 5624 in a position with an exclusive interrupt. The WinAC RTX (F) 2010 manual highlights this rule for CP 1604/CP 1616; the CP 5624 has the same real-time requirement on PROFIBUS-DP.
  • Document the F-destination address map of every F-slave. PROFIsafe communication diagnostics are unusable without a known F-destination table.
  • For non-safety drives such as a Fuji Frenic-Mega without a PROFIsafe option, the drive is configured as a standard DP slave on the same master system. Do not mix PROFIsafe and non-PROFIsafe logic in the same F-channel.

Can the CP 5624 be used as a DP Slave with WinAC RTX F?

No. Siemens only supports the CP 5624 with WinAC RTX F as a DP Master in this configuration. If a DP-Slave role is required, the CP 5624 must be moved to a different application on the same PC or replaced with a CP 5623 / CP 5613 / CP 5614 in the standard SIMATIC NET stack, not the WinAC RTX F controller.

Which TIA Portal version is required for the Interface Assignment?

Use TIA Portal V13 SP1 or later. V13 (no SP) does not expose the Interface Assignment property on the CP 5624, and only an implicit OB61 path is possible - this is not officially supported for production.

Which WinAC RTX F version is verified with CP 5624?

WinAC RTX F V4.6 is the version confirmed in the field engineering case. Newer WinAC RTX F versions in TIA Portal V14 / V15 / V16 / V17 / V18 continue to support the CP 5624 as DP Master, but always cross-check the release notes of the WinAC version against the SIMATIC NET PC version installed on the target.

Can the same CP 5624 be shared with a Windows HMI or PC application?

No. Once the CP 5624 is bound to the WinAC RTX F via the Interface Assignment, it is exclusive to the controller. PC applications such as HMI panels or SIMATIC Manager will report a bus access conflict if they try to open the same PROFIBUS interface.

How is the Fuji Frenic-Mega integrated over PROFIBUS?

Install the Fuji GSD file (for example FUJI0A1F.GSD) in TIA Portal, drag the FRENIC-MEGA drive from the catalog into the CP 5624 master system, set the PROFIBUS address to match the DIP switches on the Fuji PROFIBUS option card, and configure the cyclic PZD slots (PPO type 1 or 3). No PROFIsafe addressing is required for the drive itself unless a separate safe-stop module is added.

Back to blog