Migrating Siemens CP5412a2 ISA to CP56xx PCI Profibus Cards

Industrial PC fleets that survived on ISA-bus Profibus masters are reaching the end of their service life. The Siemens CP5412a2 (A2) ISA card was discontinued years ago when the industry pivoted to PCI, and any attempt to retain a legacy ISA controller inside a modern desktop-class workstation is a non-starter: current chipsets do not expose the ISA bus, the BIOS no longer offers ISA IRQ/DMA resources, and modern 64-bit operating systems will not enumerate the slot. This article documents the field-proven migration path from the CP5412a2 (ISA) to the CP5611, CP5613, and CP5614 PCI/PCIe Profibus master cards, including Softnet configuration, WinCC integration, and the specific failure modes operators encounter when they try to keep a Profibus DP slave configuration under WinCC.

The procedures below were assembled from commissioning experience upgrading Step 5 control rooms where the original COM PROFIBUS configuration, GSD files, and master-slave topologies had to be preserved while the host hardware moved forward by two or three PC generations. Hardware selection, software version pinning, and Windows OS support boundaries are addressed in the order they actually bite a migration project.

1. Migration Overview and Scope

The migration typically affects four domains:

1. Physical layer — replacement of the ISA card with a PCI card.
2. Driver layer — installation of Softnet (S7-DP/Softnet, Softnet-PB) on the new host.
3. Configuration layer — porting the COM PROFIBUS or STEP 7 master configuration (master/slave numbers, baud rate, GSD-derived slave parameters).
4. HMI/SCADA layer — restoring the WinCC channel connection between the new master card and the SCADA tags.

Each layer has independent failure modes. The most common complaint on forums and in field reports — that the new PCI card "won't support the slave configuration" — almost always traces to either (a) the wrong Softnet edition or version, or (b) the wrong protocol family selected in the master configuration. Profibus DP (the older DP master) and Profibus FMS expose different configuration tools, and only FMS supports the master-side configuration layout that STEP 5-era projects were written against.

2. Hardware Selection: CP5611 vs CP5613 vs CP5614

Siemens produced three practical drop-in PCI replacements for the CP5412a2. All three expose a 9-pin D-sub Profibus connector and present the same logical interface to Softnet; they differ in onboard intelligence and protocol capability.

Recommendation: For Step 5 host replacement where the original configuration must be preserved, the CP5613 is the sweet spot. The onboard processor eliminates PC-side CPU spikes during DP cycle interrupts, which is critical on virtualized or modern multi-core hosts where the legacy Softnet driver was not written with modern scheduler behavior in mind. The CP5614 is required if the existing SCADA configuration uses FMS master functions or if a parallel PG (programming) connection must run simultaneously with the SCADA channel — see Siemens Industry Online Support for the latest compatibility matrix before ordering.

3. Host Computer Selection and BIOS Configuration

Because the migration involves replacing the host PC, plan the new machine around the card's constraints, not the other way around. Three rules govern the host:

1. OS: Windows XP Professional SP1 only (English, MUI not supported by Softnet). Do not install SP2 or later service packs.
2. CPU: Single-core Pentium-class or equivalent. Multi-core is supported but disable hyper-threading in BIOS for predictable interrupt timing.
3. Slot: A standard 32-bit, 33 MHz PCI slot. PCIe is supported only via a tested bridge; do not assume PCIe-native enumeration will work.

Before swapping the host, verify the new machine can complete POST reliably. If the workstation fails to POST after the migration, isolate the failure using the layered diagnostic approach documented in Dell Knowledge Base: How to Fix No POST Startup Failure — power supply, hard reset, peripherals, beep codes, and memory reseat. A system that intermittently fails POST with the CP56xx installed almost always has a PCI slot power or IRQ assignment problem, not a card failure.

BIOS settings to lock down before installing Softnet:

• PnP OS: Disabled (force BIOS-assigned IRQ).
• ACPI Suspend: Disabled.
• APIC: Enabled but verify Softnet IRQ is in the range 5, 9, 10, or 11.
• Plug & Play OS: No.

4. Softnet Installation: License vs Bundled CD

The CP56xx cards ship with a CD containing a time-limited trial of Softnet. Field experience is unanimous: do not use the bundled CD. The trial license either expires mid-project (typical: 14 days) or is pinned to a Softnet version that has known bugs in master configuration parsing.

Order a licensed Softnet package separately. The licensed version:

• Includes the current Softnet-PB driver set (CP5611/5613/5614).
• Carries a perpetual license tied to the host's Microsoft Host SID.
• Bundles the current PG/PC interface configuration tool.
• Supports simultaneous PG (programming) and OP (operator) access modes.

Install order:

1. Power off, install the CP5613/CP5614 in a free PCI slot, attach Profibus segment.
2. Boot Windows XP SP1.
3. Detect new hardware; cancel Windows' default driver prompt.
4. Insert licensed Softnet CD. Run Setup.exe as Administrator.
5. Select CP5613/CP5614 Profibus as the access point.
6. Restart. Verify card appears in Set PG/PC Interface with no warning icons.

5. COM PROFIBUS Configuration: DP vs FMS

The original failure reported during the migration was: "the newer boards (Profibus & DP) don't support the slave configuration." The root cause is a confusion between two distinct protocol families that share the same physical layer:

• Profibus DP (Decentralized Periphery): cyclic I/O exchange; slave configuration done via GSD import in STEP 7 or COM PROFIBUS; the master configuration is compiled into a binary blob downloaded to the master card.
• Profibus FMS (Fieldbus Message Specification): acyclic, variable-length messaging; master and slave relationships are configured through FMS-specific tools and expose a different API to SCADA packages like WinCC.

The CP5611/CP5613/CP5614 cards physically support both protocols, but the master configuration tool differs. If the legacy STEP 5 project was written against the FMS profile, importing it into a DP-only master configuration in COM PROFIBUS will silently drop the slave descriptors — which is exactly the "won't support the slave configuration" symptom operators describe.

5.1 Decision path: Is your STEP 5 project DP or FMS?

1. Open the legacy *.pb or *.fms file in COM PROFIBUS.
2. If the file uses FDL bindings or FMS services, the project is FMS-based.
3. If the file references GSD files for ET200, S7-300, or third-party slaves, it is DP-based.
4. Hybrid projects are common in retrofits; treat each subnet independently.

5.2 Reconfiguring for FMS Compatibility

If the legacy project is FMS-based and the new SCADA is WinCC 5.1 or later, the resolution documented in the original commissioning report is:

1. Upgrade WinCC from 4.01 to 5.1 (or later, within the Softnet support window).
2. In WinCC, select the Profibus FMS channel instead of Profibus DP.
3. Re-import the FMS master configuration. The slave descriptors are preserved.
4. Verify tag polling from WinCC to each FMS station before bringing the segment online.

6. WinCC to CP5614 Channel Configuration

Once the card and Softnet are installed, the WinCC channel must be pointed at the new access point. The default install leaves the channel pointing at the CP5412a2's symbolic access point name (S7ONLINE or CP5412A2(PROFIBUS)), which the new Softnet install may not recreate identically.

Procedure:

1. Open Set PG/PC Interface from the Windows Control Panel.
2. Confirm CP5614(PROFIBUS) exists and is the active access point. If not, add it and assign the Softnet driver.
3. In WinCC Explorer, open the Tag Management editor.
4. Select the Profibus channel driver. Right-click → System Parameters.
5. Verify the Logical Device Name matches the Softnet access point.
6. Compile the WinCC project. Watch for warnings on unresolved logical device names.

6.1 Common Communication Errors

7. Master / Slave Numbering and GSD Handling

Slave station numbers are not auto-assigned by the new card; they are read from the imported master configuration. During migration:

1. Document every slave's Profibus address (1–126) before powering down the legacy host.
2. Export the master configuration from the legacy COM PROFIBUS session as .pb.
3. Verify all referenced GSD files exist on the new host at \Siemens\COMPB\GSD\. Missing GSDs cause slaves to silently default to empty module lists.
4. Re-import the configuration on the new host. Recompile and download to the CP5614.
5. Power up slaves in address order. Verify each appears in the diagnostic view with green status.

8. Verification Procedure

Run the following verification steps in order before declaring the migration complete:

1. Hardware presence: Device Manager shows CP5613/CP5614 with no yellow bang. Softnet driver loaded.
2. Set PG/PC Interface: Diagnostics tab shows bus statistics (0 bus errors after 60 seconds idle).
3. Master configuration download: COM PROFIBUS reports Configuration Active on the card.
4. Slave enumeration: All configured slaves appear in the online view with status Data Exchange.
5. WinCC channel: Tag Management shows all process tags with green status indicators.
6. Forced tag test: Force a digital output from WinCC; confirm the corresponding input on the slave toggles.
7. Sustained run: Leave the system running 24 hours with diagnostic logging enabled. Review logs for any burst errors.

9. Troubleshooting Matrix

10. Performance and Timing Considerations

The Profibus DP cycle time is bounded by the slowest slave's min T_sdr plus bus propagation. A CP5613 with the onboard ASIC can sustain 12 Mbaud with cycle times below 1 ms for typical 16-byte I/O segments. The CP5611, lacking the ASIC, sees effective throughput degrade above 1.5 Mbaud when more than 8 slaves are present.

Master-side timing on the CP5613:

• Token rotation time (TTR): auto-negotiated; do not manually override.
• Slot time (T_sl): 1,000 bit-times at 12 Mbaud (~83 µs).
• Min slave response time (min T_sdr): 11 bit-times.

For WinCC tag updates, poll interval should not exceed the DP cycle time × 3, otherwise the SCADA layer introduces its own latency on top of the bus jitter. In typical retrofits this means a 500 ms WinCC poll at 12 Mbaud with a 5 ms DP cycle.

11. Documentation and References to Capture

Before signing off any migration, archive:

• Softnet license certificate and Host SID binding.
• COM PROFIBUS master configuration file (.pb or .fms).
• All GSD files referenced, with revision numbers.
• WinCC project backup including Tag Management export.
• Set PG/PC Interface screenshot showing active access point.
• 24-hour diagnostic log from Profibus Diagnostics tool.

12. Extended Notes for Field Engineers

A few field-proven caveats that do not appear in the official Siemens documentation but consistently surface during commissioning:

1. Host SID binding is hardware-bound. Replacing the motherboard invalidates the Softnet license. Siemens Customer Support can re-host a license once per year per seat at no charge in many regions.
2. Profibus segment termination must be powered at all times when slaves are present. An unterminated cable during slave commissioning will surface as intermittent diagnostic timeouts that look like card failures.
3. Virtualization is not supported. Running the CP5614 inside a VM with PCI passthrough will install but will fail under load. Run the SCADA host on bare metal.
4. Backup operator consoles. Retain one working CP5412a2-equipped PC in the spares locker for at least six months after cutover; cold-starting an entire segment from zero is significantly harder than swapping a known-good master.

FAQ