CP 5613 A2 Hardware Overview
The Siemens CP 5613 A2 is a PCI-bus communication processor for PCs and programming devices (PGs) that connects a host system to PROFIBUS DP and MPI networks. It is the direct PCI replacement for the legacy ISA-format CP 5611 A2, and it supersedes the original 5 V PCI CP 5613. The card is published in the CP 5613 A2 / CP 5614 A2 Operating Instructions with the following essential characteristics:
- PROFIBUS interface supporting 9.6 kbps through 12 Mbps (auto-detect).
- 32-bit, 33 MHz PCI target, 3.3 V / 5 V universal keyed edge connector.
- DPRAM dual-port memory on board for low-latency process data exchange with the host.
- Protocol support: PROFIBUS DP-V0, DP-V1, DP-V2, FDL, PG/OP, S7 communication, and FMS.
- Maximum of 124 DP slaves per segment when used as a Class 1 master.
- Maximum of 64 S7 connections (mixed PG/OP and S7) per CP.
- Isolation: 500 V functional isolation between PROFIBUS segment and PC chassis ground.
- Connector: 9-pin D-sub female (RS-485 PROFIBUS standard pinout per IEC 61158-2).
Two rotary switches on the bracket let the integrator set the PROFIBUS node address (0–126) when the card is not in PG mode. The CP 5613 A2 supports plug-and-play BIOS enumeration under Windows XP/2003 and explicit PnP enumeration under Windows 7 and later when paired with the matching SIMATIC NET PC software package.
DTM and FDT Framework Architecture
Device Type Managers (DTMs) are component-based drivers defined by the IEC 62453 / FDT 1.2 / FDT 2.0 specification. A DTM is loaded into an FDT frame application (also called the frame container) which orchestrates communication, parameterization, and diagnostics for the connected device. The architecture is layered:
- Frame application – PACTware, FieldCare, AssetCentre, PDM, or a vendor-specific container (e.g. SIMATIC PDM).
- Communication DTM (CommDTM) – Translates frame I/O requests into bus-specific calls (DP-V1, HART over RIO, etc.).
- Device DTM – Provides the device-specific GUI, parameter set, and diagnostics tree.
- Channel DTM – Optional multiplexer for gateways that fan out to multiple sub-buses (e.g. PROFIBUS to HART multiplexers).
The CP 5613 A2 occupies the CommDTM layer in this stack. Frame applications do not talk directly to the PCI hardware; they call the CommDTM interface, which in turn drives the SIMATIC NET driver stack (cp5613.sys, dpbase.lib, fdlbase.lib) exposed by the CP 5613 A2 firmware.
| Layer | Component for CP 5613 A2 | Provided by |
|---|---|---|
| Frame Application | PACTware 4.x / 5.x, FieldCare 2.x | End user / integrator |
| Communication DTM | Vendor-supplied CommDTM (e.g. T&H CommDTM PROFIBUS DP-V1) | Third-party DTM vendor |
| PC Driver Stack | SIMATIC NET PC Software >= V13 SP2 | Siemens |
| Hardware | CP 5613 A2 PCI card + firmware | Siemens |
Native Siemens DTM Availability for the CP 5613 A2
Siemens does not publish a Communication DTM for the CP 5613 A2 in the FDT Group certified catalog. The catalog enumerates Siemens DTMs only for PROFIBUS PA field instruments (flow meters, pressure transmitters, valve positioners, etc.) and for ET 200 remote I/O stations. Communication processors such as the CP 5613 A2, CP 5614 A2, CP 5622, and CP 5711 are absent because their lifecycle is managed by the SIMATIC NET PC software, not the FDT frame.
The PCI card is delivered with:
- A device driver package (CP 5613 A2 driver disk, part of the SIMATIC NET PC Software DVD).
- Configuration tools: Set PC/PG Interface and Station Configuration Editor.
- OPC DA / OPC UA server (SIMATIC NET OPC) – provides real-time data to SCADA without a DTM.
- SOAP / S7-API libraries (libnodave, Prodave, Snap7 over the S7 channel) – bypasses the DTM stack entirely.
For these reasons, plant integrators who need a CommDTM for the CP 5613 A2 must select a third-party FDT-compliant package or implement a custom DTM that wraps the SIMATIC NET API.
Compatible Third-Party Communication DTM Alternatives
Two commercial and one open-source path allow a CP 5613 A2 to be addressed from an FDT container.
Trebing & Himstedt CommDTM PROFIBUS DP-V1
The CommDTM PROFIBUS DP-V1 from Trebing & Himstedt Prozeßautomation supports the classic Siemens PC cards CP 5512, CP 5611, CP 5611 A2, and the Field PG with integrated CP 5611. Because the CP 5613 A2 registers itself to the SIMATIC NET device manager with the same CP5613.A2.1 device class ID and exposes a compatible DP-V1 service access point, the T&H CommDTM can usually bind to the CP 5613 A2 once a matching PC station configuration is loaded. Verify with T&H before commissioning critical loops; the package was originally qualified against the older CP 5611/CP 5611 A2.
Softing PROFIBUS CommDTM
Softing Industrial Automation ships PROFIBUS CommDTMs in the FG-200 PROFIBUS family. These DTMs are officially bound to Softing hardware (PROFIBUS PC cards and the FG-200 gateway) and do not include a CP 5613 A2 driver entry in the default catalog. Where the same PC hosts both a Softing card and a CP 5613 A2, the two networks are independent and cannot be bridged by a single DTM session.
Open-Source / Custom DTM
For laboratory use or air-gapped commissioning rigs, integrators can author a C#/.NET DTM (FDT 2.0 COM interface) that wraps the Siemens DP_BASE.LIB / FDL_BASE.LIB API exported by the SIMATIC NET runtime. Skeleton implementations are published in the FDT Group's DTM Style Guide; the integration risk is moderate and the long-term support cost is high, so reserve this path for proof-of-concept work.
| CommDTM Option | Officially supports CP 5613 A2 | FDT Versions | License Model |
|---|---|---|---|
| Siemens native CommDTM | No (none published) | — | — |
| T&H CommDTM PROFIBUS DP-V1 | Compatible on request | FDT 1.2 / 2.0 | Commercial, per seat |
| Softing FG-200 CommDTM | No (Softing hardware only) | FDT 1.2 / 2.0 | Commercial, per seat |
| Custom wrapper around DP_BASE.LIB | Yes (engineered) | FDT 2.0 | In-house development |
FMS-5613 Edition 2005 Software Stack
For FMS protocol, PG, and FDL access without a DTM, the FMS-5613 Edition 2005 package supplies a complete PC-side software suite. The PI Product Finder lists the following supported hardware:
- CP 5613 A2
- CP 5613 FO (fiber-optic variant)
- CP 5614 A2 (dual-channel)
The package bundles:
- FMS-5613 configuration utility for editing the local FMS station profile (VFD address, CR attributes, OD).
- FDL diagnostic trace with timestamped frame logging (essential when validating DP-V1 acyclic services).
- PG functions for routing S7 downloads through the CP 5613 A2 into MPI / DP networks.
- DLL export of the FMS and FDL primitives for C/C++ integration on Windows XP/2003.
SIMATIC_NET.DLL.Migration Path: CP 5611 / CP 5611 A2 to CP 5613 A2
The CP 5613 A2 is mechanically and electrically incompatible with the CP 5611 A2 (ISA bus) but is designed as a drop-in migration target at the application level. The migration is transparent if the PC station configuration is rebuilt with the new interface assignment in STEP 7 / TIA Portal:
- Open Set PC/PG Interface (
SIMATIC_NET::SetPgPcInterface) and select the CP 5613 A2 as the access point for S7ONLINE. - Re-import the PC station hardware catalog (HW Config > Options > Install HW Updates) so the CP 5613 A2 (6GK1 561-3AA02) is recognized.
- Copy the PROFIBUS subnet properties (baud rate, bus profile, highest station address = 126) from the retired CP 5611 A2 project to the new CP 5613 A2 object.
- Re-bind the OPC server channel: SIMATIC NET OPC Server > Station > CP 5613 A2. The tag database (.xml) is reused unchanged.
- Validate with Station Configuration Editor > Diagnostics – look for
CP 5613 A2 OK, master state = RUN, slave count = N.
| Parameter | CP 5611 A2 (legacy) | CP 5613 A2 (target) |
|---|---|---|
| Bus | ISA 16-bit | PCI 32-bit / 33 MHz |
| Max. baud | 12 Mbps | 12 Mbps |
| DP-V1 acyclic | Yes (firmware > V5.0) | Yes |
| Driver signature (modern OS) | Unsigned | Signed (Win 7+) |
| Power consumption | 5 V / 750 mA | 3.3 V / 600 mA + 5 V / 200 mA |
| Replacement MLFB | 6GK1 561-1AA01 / -2AA01 | 6GK1 561-3AA02 |
PROFIBUS PA vs DP Communication DTM Differences
FDT/DTM applications historically focused on PROFIBUS PA (process automation, IEC 61158-2, 31.25 kbps) because PA devices are parameterized through acyclic C2 services and benefit most from rich DTMs. PROFIBUS DP (factory automation, RS-485, up to 12 Mbps) is mostly configured at the master (PLC) side and only occasionally requires a CommDTM at the engineering station.
| Aspect | PROFIBUS PA | PROFIBUS DP |
|---|---|---|
| Physical layer | IEC 61158-2 (MBP), 31.25 kbps, bus-powered | RS-485, 9.6 kbps–12 Mbps |
| Coupling to PC card | Via DP/PA coupler or link | Direct (CP 5613 A2 native) |
| Typical DTM user | Instrumentation engineer | PLC / drive commissioning engineer |
| Cyclic service | MS0 / MS1 (C1) | MS0 / MS1 / MS2 (C1 / C2) |
| DTM catalog coverage | Very high (E+H, Yamatake, ABB, Siemens) | Low for masters, high for slave devices |
The CP 5613 A2 functions as a DP master on the segment. To use it as the entry point to a PA network, the PC must additionally host a DP/PA coupler (e.g. Siemens 6GK1 572-1AA00) or a Link/Coupler pair. The FDT frame sees the CP 5613 A2 as the C2 channel DTM and the PA devices as deviceDTMs behind the coupler.
Installing and Configuring a Communication DTM on the CP 5613 A2
Use this procedure to bring a CP 5613 A2 online in PACTware 5.x with the T&H CommDTM PROFIBUS DP-V1. Adapt the path for FieldCare or other FDT containers.
Prerequisites
- Windows 10 / Server 2016 or later, 64-bit.
- SIMATIC NET PC Software V15.1 or later (provides signed driver for CP 5613 A2).
- Set PC/PG Interface assigned to
CP5613.A2.1for the S7ONLINE access point. - PACTware 5.0.x with FDT 2.0 runtime.
- T&H CommDTM PROFIBUS DP-V1 (licensed dongle or soft-license).
Step-by-Step Configuration
- Install the CP 5613 A2 in a free PCI slot. Power the PC; verify the BIOS enumerates the card without resource conflicts (no yellow exclamation mark in Device Manager).
- Install SIMATIC NET PC Software. During setup select CP 5613 A2 / CP 5614 A2 driver and OPC Scout / S7 OPC.
- Open Set PC/PG Interface; set Access Point of the Application = S7ONLINE and Interface Parameter Assignment = CP5613.A2.1. Confirm baud rate = 1.5 Mbps (default).
- Open Station Configuration Editor. Click Add and select the CP 5613 A2 from the catalog. Save the configuration (
S7PCSTATION.cfg). - Install PACTware 5 and then the T&H CommDTM package. Reboot if the installer prompts for the FDT catalog refresh.
- Start PACTware. Right-click Device Catalog > Communication, choose Add Device, and select T&H CommDTM PROFIBUS DP-V1.
- Open the CommDTM's Connection page. Set Bus = PROFIBUS, Host = CP5613.A2.1, and Address = 0 (the PC's master address). Click Connect.
- Click Update Device Catalog to import all deviceDTMs visible on the bus.
- Add a deviceDTM (e.g. SITRANS P pressure transmitter). Right-click the device, select Parameterize > Online. The CommDTM routes the C2 read/write calls to the CP 5613 A2 driver.
- Verify the round trip: read a dynamic variable, observe the value updating at the configured refresh interval (typical 1 s for acyclic, 10 ms for cyclic with publisher subscription).
Driver, Firmware, and Compatibility Matrix
Use the matrix below to align the CP 5613 A2 hardware revision (MLFB 6GK1 561-3AA02) with the correct SIMATIC NET release and STEP 7 / TIA Portal version. Mixing releases on the same PC is not supported.
| SIMATIC NET Version | CP 5613 A2 Driver | STEP 7 / TIA Portal | Windows OS |
|---|---|---|---|
| V13 SP2 | Signed, DP-V1 | STEP 7 V5.5 SP4 / TIA V13 | Win 7 SP1, Server 2008 R2 |
| V14 SP1 | Signed, DP-V2 (isochronous) | TIA V14 SP1 | Win 8.1, Server 2012 R2 |
| V15.1 | Signed, OPC UA server | TIA V15.1 | Win 10 1809, Server 2016 |
| V16 | Signed, security hardened | TIA V16 | Win 10 1909+, Server 2019 |
| V18 | Signed, OPC UA Pub/Sub | TIA V18 | Win 10 21H2, Server 2022 |
The CP 5613 A2 firmware (DPRAM-resident microcontroller code) is updated automatically by the SIMATIC NET installer; there is no separate firmware image to flash. If the driver update fails, the card falls back to legacy mode and logs CP5613.A2.1: firmware down-rev, expected >= 5.2.4 in the Windows Event Viewer under System > Source = SIMATIC NET.
Troubleshooting Matrix
| Symptom | Probable Cause | Diagnostic Step | Corrective Action |
|---|---|---|---|
| CP 5613 A2 not visible in Set PC/PG Interface | Driver not installed or PCI enumeration failed | Device Manager → SIMATIC NET → CP 5613 A2 | Reinstall SIMATIC NET PC Software; reseat card |
| Station Configuration Editor shows "CP 5613 A2 not configured" | PC station name not bound | Right-click CP → Properties → Station name | Match station name in S7 project / OPC Scout |
CommDTM connect returns FDT_ERR_NO_BUS_CONNECTION
|
Acyclic channel not opened | FDL trace, check DP-V1 SAP list | Re-create PC station; restart SIMATIC NET service |
Initialization error with DP_BASE.LIB (LabWindows/CVI user) |
Conflicting access to the CP via two applications | Stop the SIMATIC NET service and retry | Use exclusive mode: only one consumer of the C2 channel |
| Event ID 7026 from SIMATIC NET service | Signed driver blocked on Windows 10 1607+ | Check bcdDevice / Hardware IDs | Enable test signing only for diagnostic; obtain current driver |
| Bus scan returns no slaves | Termination missing or wrong baud | Measure A-B voltage with terminating resistors enabled | Enable terminator at both ends; set master baud = bus baud |
| DP-V2 isochronous mode unstable | Bus cycle < 500 µs exceeds CP jitter | Station Configuration Editor → Diagnostics → jitter | Increase Ti / To by 50 µs increments |
Field-Proven Commissioning Notes
- When a custom application opens
DP_BASE.LIBdirectly (e.g. from a LabWindows/CVI test rig), the SIMATIC NET service must be stopped; otherwise the two consumers race for the C2 SAP and the second open returnsERROR_BUSY(Win32 error 170). - For DP-V1 acyclic traffic, the master and the FDT frame must agree on the slot assigned to the deviceDTM. The slot number is configured in HW Config under the slave's Properties > Parameter Assignment and must be unique per bus segment.
- If the bus has a mix of DP-V0 slaves that ignore MS1 acyclic calls, the FDT frame will time out on those nodes. Mask them out in the CommDTM scan list.
- The CP 5613 A2 is keyed for 3.3 V / 5 V universal PCI. It will not seat in a PCIe x1 slot without an active PCIe-to-PCI bridge. Plan the host PC accordingly when upgrading the engineering workstation.
- For OPC UA access without a DTM, configure the SIMATIC NET OPC UA server in Station Configuration Editor → OPC UA → Add Endpoint. This bypasses the FDT stack entirely and is the recommended path for new SCADA projects on TIA Portal V15+.
Does Siemens publish a DTM for the CP 5613 A2?
No. The FDT Group's certified DTM catalog lists Siemens DTMs only for PROFIBUS PA field instruments and ET 200 stations. The CP 5613 A2 is a communication processor and is configured through SIMATIC NET PC Software (V13 SP2 or later), not through a vendor DTM.
Which third-party CommDTM works with the CP 5613 A2?
The Trebing & Himstedt CommDTM PROFIBUS DP-V1 is the most widely deployed option and is compatible with the CP 5613 A2 when the PC station is bound to CP5613.A2.1. Softing CommDTMs are restricted to Softing hardware and do not bind to the CP 5613 A2.
Can FMS-5613 Edition 2005 still be used today?
Yes, but only on Windows XP / Server 2003 or inside an XP-Mode virtual machine on Windows 7. For modern hosts, migrate to SIMATIC NET PC Software V15 or later, which exposes the same FMS, FDL, and PG functions through the SIMATIC_NET.DLL API and supports the CP 5613 A2, CP 5613 FO, and CP 5614 A2.
What is the replacement for the CP 5611 A2?
The CP 5613 A2 (MLFB 6GK1 561-3AA02) is the official PCI replacement for the CP 5611 A2. It supports the same 12 Mbps baud rate and DP-V1 acyclic services, and the migration is transparent once the PC station is rebuilt in STEP 7 / TIA Portal with the new interface assignment for S7ONLINE.
How do I avoid ERROR_BUSY when opening DP_BASE.LIB alongside SIMATIC NET?
Stop the SIMATIC NET service (sc stop s7oiehsx64) before opening the CP 5613 A2 directly from a custom application. The C2 service access point is exclusive; simultaneous access from the OPC server and a custom DLL causes the second open to fail with Win32 error 170.