Migrating SIMATIC NET SOFTNET-PB DP to Windows 7: CP Card and Version Selection Guide

1. Problem Overview

Many long-running industrial PC applications were built on Windows XP and Siemens SIMATIC NET PC software. With Microsoft retiring Windows XP extended support, these systems must migrate to Windows 7 (or later). The migration is rarely a drop-in replacement: SIMATIC NET version compatibility, supported PROFIBUS CP cards, and the PC-internal configuration (XDB/PC station) all change between versions.

This reference documents the field-validated path for migrating a VB.NET / .NET application using SIMATIC NET SOFTNET-PB DP 2008 (V7.1) with a CP 5611 PROFIBUS master on Windows XP to Windows 7. It captures the version matrix, supported CP cards, configuration import (XDB) workflow, and known incompatibility cases that affect the SOFTNET-PB DP product line through SIMATIC NET V17 SP1.

2. Reference System Architecture

The source system follows the classic single-master PC-to-PLC PROFIBUS DP topology:

• Application layer: VB.NET (Microsoft Visual Studio .NET), calls SIMATIC NET OPC / DP base services via the SIMATIC NET PC software.
• Protocol layer: PROFIBUS DP, DP-V0/V1 master class 2.
• PC hardware: Windows XP SP3 workstation, PCI slot occupied by a Siemens CP 5611 PROFIBUS interface.
• PLC side: SIMATIC S7-200, configured as DP slave (EM 277 DP slave module or CPU with integrated DP port, depending on the original wiring).
• Software stack: SIMATIC NET SOFTNET-PB DP 2008 (release V7.1), including the PC station configuration tool and the DP base services DLLs accessed by the VB.NET application.

3. SIMATIC NET SOFTNET-PB DP Version Compatibility Matrix

Siemens has released multiple generations of SOFTNET-PB DP since V7.1. Each generation changed its approved list of PROFIBUS CP cards, the underlying driver model, and the supported Windows operating systems. The table below is the field-relevant subset for a Windows XP → Windows 7 migration path.

Sources: Siemens Industry Online Support entry "Sales and delivery release of SIMATIC NET PC Software V17 SP1" confirms that "The products SOFTNET-PB S7 V17 … have not been approved with the modules CP 5611 A2 and CP 5621. The modules CP 5612, CP 5622 and CP 5711 are …" approved.

4. CP Card Selection Strategy

The CP card selection is coupled to the SIMATIC NET version. Three viable Windows 7 strategies are field-proven:

4.1 Strategy A — Minimum Disruption: SIMATIC NET V8.2 + CP 5612

This is the lowest-risk path because V8.2 retains NCM PC, the XDB import/export workflow, and the V7.1-style DP base service API. The CP 5612 is a PCI card that replaced CP 5611 in production, uses the same Siemens DP base driver architecture, and is approved across V8.2 through V14. Field feedback from the support case described in the field report converged on this exact combination: SOFTNET-PB DP 8.2 with CP 5612.

• PCI bus (5 V). Requires a workstation with at least one free PCI slot. Most Windows 7 industrial PCs of the era (e.g., Siemens SIMATIC IPC547, IPC627, IPC847) still include PCI slots.
• If the target PC is PCI Express only, use the CP 5622 (PCIe x1) instead — it is the PCIe successor of CP 5612.
• If the target PC is a laptop / mobile maintenance station, use the CP 5711 (USB 2.0 PROFIBUS adapter). CP 5711 is approved from V8.2 onward.

4.2 Strategy B — Latest Long-Term: SIMATIC NET V12+ + CP 5622

If the application will be redeployed for many years and the workstation hardware supports PCIe, jump straight to SIMATIC NET V12 (or V13 / V14 if a SIMATIC NET DVD is available) with a CP 5622. This requires:

• Switching from NCM PC configuration (used by V7.1) to the new PC station in STEP 7 / TIA Portal.
• Re-importing the XDB file (exported from V7.1 NCM PC) into the new PC station project.
• Rebuilding any references to the old DP base service DLL names if they changed between V7.1 and V12.

The advantage is forward compatibility through V17 SP1, which still approves CP 5622.

4.3 Strategy C — Hardware-First Migration: Keep V7.1, Replace PC First

If hardware refresh is the immediate priority and the application cannot yet be re-validated, deploy SIMATIC NET V7.1 SPx onto Windows 7 only if Siemens has published a compatibility hotfix for that combination. Note that V7.1 was originally qualified for Windows XP; an out-of-the-box install on Windows 7 is not a supported configuration. This strategy is not recommended for new deployments.

5. CP Card Hardware Comparison

6. Windows 7 Installation Prerequisites

Before installing SIMATIC NET on a Windows 7 system, verify the following prerequisites:

1. Edition: Windows 7 Professional, Enterprise, or Ultimate (32-bit for SIMATIC NET ≤ V12; 64-bit supported from V12 SP1 onward, full support from V13).
2. Service Pack: Windows 7 SP1 installed; latest Windows updates applied.
3. User account: Log in with administrator privileges during install; the SIMATIC NET installer registers DP base services, OPC DA servers, and a kernel-mode DP driver that requires elevation.
4. .NET Framework: .NET 3.5 SP1 (default on Win7) for VB.NET applications using COM interop to the SIMATIC NET OPC automation interface; .NET 4.x if the application was rebuilt with a newer Visual Studio.
5. Free slot: One PCI slot for CP 5612 or one PCIe x1 slot for CP 5622; one USB 2.0 port for CP 5711.
6. Driver signature: Windows 7 x64 enforces driver signature enforcement. Confirm the target SIMATIC NET version supplies signed drivers for the chosen CP. CP 5612 / CP 5622 drivers from SIMATIC NET V8.2 onward are signed for Windows 7 x64.
7. Disable UAC prompt for DP services: Configure the SIMATIC NET "Configuration Console" service and the "SIMATIC NET DP" service to start automatically (delayed start) so the VB.NET application does not block on a UAC elevation prompt at first run.

7. Step-by-Step Migration Procedure

The following sequence is the minimal-change migration path: SIMATIC NET V8.2 + CP 5612 + Windows 7. It preserves the existing VB.NET application's DP base service calls.

7.1 Pre-Migration on the Old XP System

1. Open the SIMATIC NET NCM PC configuration (Start → SIMATIC → SIMATIC NET → NCM PC).
2. Open the existing PC station project. Verify the CP 5611 is online (green check) and the DP master is in OPERATE state.
3. From the menu, choose PC station → Export and save the project to an XDB file (e.g., PB_DPV1.xdb). The XDB captures the CP slot assignment, DP master parameters (baud rate, bus profile, FDL address), and the configured slave list.
4. Copy the application's deployment folder, the XDB file, and any DP slave GSD files (e.g., SIEM089D.GSD) to portable media.
5. Document the CP 5611's slot, the DP master's PROFIBUS address (default = 1), the highest station address (HSA, default = 126), and the bus baud rate (e.g., 1.5 Mbps, 12 Mbps).

7.2 Hardware Migration

1. Power down the XP workstation. Remove the CP 5611 PCI card.
2. Move the CP 5611 to the Windows 7 workstation's free PCI slot. (Optional — keep as a cold spare if a CP 5612 is the new primary.)
3. Install the new CP 5612 (or CP 5622) into a free PCI / PCIe slot of the Windows 7 workstation.
4. Connect the PROFIBUS cable to the new CP's 9-pin D-sub PROFIBUS connector. The pinout (pin 3 = B-line, pin 8 = A-line) is identical between CP 5611 and CP 5612 — no cable rework required.
5. Verify termination: PROFIBUS DP segments must be terminated at both ends. If the CP is at a segment end, enable the termination switch on the CP 5612 (slider on the rear bracket).

7.3 SIMATIC NET V8.2 Installation on Windows 7

1. Insert the SIMATIC NET V8.2 DVD (or mount the ISO). Right-click Setup.exe → Run as administrator.
2. Accept the license agreement. Choose Custom installation.
3. Select the components: SOFTNET-PB DP, PC station configuration (NCM PC), OPC server (DP) if the VB.NET application uses the OPC DA automation interface.
4. When prompted for the CP card, select CP 5612 (or whatever CP you installed).
5. Complete the install and reboot.
6. Open SIMATIC NET → Commissioning → Configuration Console. Confirm the CP 5612 is listed and shows "Running".

7.4 Import the Existing PC Station Project

1. Launch NCM PC on Windows 7.
2. Create a new PC station project with the new CP 5612.
3. From the menu, choose PC station → Import and select the PB_DPV1.xdb file from the XP system. NCM PC reads the CP slot, DP master parameters, and slave list from the XDB.
4. Re-assign the DP master to the new CP 5612's index if necessary. Save the project.
5. From NCM PC, choose PC station → Download to target. The configuration is pushed to the running SIMATIC NET configuration.

Per the Siemens SIMATIC NET support note "SIMATIC NET PC software update": "When installing a SIMATIC NET PC software update, you will need to reload the configuration and project configuration. You can import the XDB file, for example, …". This is exactly the XDB import workflow used in step 7.4.

7.5 Verify the DP Master Comes Up

1. Open SIMATIC NET → Commissioning → DP Diagnostics or the OPC Scout.
2. Confirm the CP 5612 reaches the OPERATE state.
3. Confirm the configured S7-200 slave appears with its PROFIBUS address and reports data exchange OK.
4. Launch the VB.NET application. Confirm that it opens the DP base / OPC connection without error and that live process data exchanges with the S7-200.

8. Configuration Import — Why XDB Re-Loading Is Mandatory

The XDB (XML Data Block) is the on-disk representation of the PC station's bus configuration. After a SIMATIC NET PC software update — including a major version change such as V7.1 → V8.2 or V12 → V17 SP1 — the running configuration must be reloaded. Simply reinstalling the software does not transfer the CP / DP master settings into the new runtime.

Best practice for any SIMATIC NET PC software upgrade:

1. Export the existing PC station to XDB before uninstalling the old version.
2. Uninstall the old SIMATIC NET version.
3. Install the new SIMATIC NET version.
4. Import the XDB into the new PC station project.
5. Download the configuration to the running services.
6. Reboot and verify with DP diagnostics.

9. DP Base Service / OPC API Considerations for VB.NET

The VB.NET application interacts with SIMATIC NET through one of two routes. Both survive a V7.1 → V8.2 migration without code changes; migrating to V12+ requires verification.

9.1 COM / OPC DA Automation Interface

Classic OPC DA access via the Siemens "OPC.SimaticNET" automation wrapper. This interface has remained compatible from V6.x through V17 SP1. The ProgID OPC.SimaticNET and the IIDs have not changed for PROFIBUS DP. The VB.NET call site looks like:

Dim opcServer As New OPCAutomation.OPCServer
opcServer.Connect("OPC.SimaticNET")
Dim tags As OPCAutomation.OPCItem
opcServer.OPCGroups.Add("DPGroup")
group.OPCItems.AddItem("S7:[S7-200]DB1,BYTE0", 1)

If the application uses this path, the Windows 7 migration is largely transparent: re-install the SIMATIC NET OPC server, re-import the XDB, run the application.

9.2 Native DP Base Service DLL (e.g., dplib.dll / dpapi32.dll)

The SIMATIC NET DP base service DLLs expose the low-level DP-V0/V1 functions (dp_init, dp_read_slv, dp_write_slv, dp_slv_event) used by some custom .NET wrappers. These DLLs ship with the SOFTNET-PB DP component and have stable calling conventions from V7.1 through V17 SP1. The VB.NET application must use P-Invoke (DllImport) against the version-specific DLL name. Confirm the DLL name and the export table after upgrade; the function signatures are stable, but the DLL filename occasionally changes between major releases.

9.3 PROFINET OPC UA (Not Applicable Here)

If the application is migrated to OPC UA later, the SIMATIC NET OPC UA server is included from V13 onward. OPC UA is not required for the PROFIBUS DP path described in this reference.

10. Operating System Upgrade Path Beyond Windows 7

Windows 7 mainstream support ended January 2015; extended support ended January 2020. If you intend to skip Windows 7 and migrate directly to Windows 10, the table below shows the version that pairs with the CP card already discussed.

11. Troubleshooting Matrix

12. Commissioning Verification Checklist

• CP 5612 visible in Windows Device Manager under "SIMATIC NET".
• SIMATIC NET Configuration Console shows CP 5612 in state Running.
• NCM PC opens the imported XDB and the CP slot / DP master parameters are correct.
• Configuration downloaded to the runtime; DP master state = OPERATE.
• Configured S7-200 DP slave appears in DP diagnostics with data exchange OK.
• OPC Scout (or equivalent test client) browses the configured items and returns valid values.
• VB.NET application launches without COMException on Connect, and cyclic read / write of process values completes within the configured poll interval.
• Disconnection of the PROFIBUS cable produces a deterministic diagnostic event in the application (no unhandled exception).

13. Field-Proven Migration Summary

The combination chosen in the field report — SOFTNET-PB DP V8.2 + CP 5612 — is the lowest-risk Windows 7 migration path because it preserves the NCM PC configuration workflow, the XDB export/import mechanism, and the OPC / DP base API surface that the existing VB.NET application depends on. For longer-term deployments, promote to SIMATIC NET V14 / V16 / V17 SP1 with CP 5622 (PCIe) or CP 5711 (USB) while keeping the same XDB-derived PC station configuration. In every case, the legacy CP 5611 must be replaced; it cannot be carried forward into V12 or V17 SP1 environments.

FAQ