How to Upgrade PCS 7 V7.0 WinCC to V8.1 Without Breaking Third-Party HMI Panels and OPC Interfaces

Upgrading a legacy PCS 7 V7.0 OS system running on Windows XP to a modern IPC827D with Windows 7 and PCS 7 V8.1 impacts third-party HMI panels (such as STAHL explosion-proof field terminals) communicating over OPC. While WinCC tag databases remain largely compatible when using 'migration without utilization of new functions', the upgrade introduces critical breaking barriers: Windows 7 enforces strict DCOM hardening that blocks legacy unauthenticated OPC DA calls, 32-bit third-party ActiveX controls cannot execute in 64-bit environments, and if block types are migrated to APL, modified tag structure prefixes will sever HMI tag links. To prevent communication disruption, maintain legacy tag structures, reconfigure Windows 7 DCOM security, and stage OPC communications through OpenPCS 7.

Multi-Version Upgrade Pathway: PCS 7 V7.0 to V8.1

Upgrading an industrial control system from SIMATIC PCS 7 V7.0 to PCS 7 V8.1 represents a transition across three major platform iterations and a fundamental shift from 32-bit Windows XP to 64-bit Windows 7 / Server 2008 R2.

The official Siemens migration pathway mandates executing sequential intermediate updates:
PCS 7 V7.0 -> PCS 7 V7.1 SP4 -> PCS 7 V8.0 SP2 -> PCS 7 V8.1 SP1
Attempting to open a PCS 7 V7.0 multi-project directly in PCS 7 V8.1 corrupts database headers and breaks AS-OS linkages. Furthermore, when replacing an obsolete PC station with a modern SIMATIC IPC827D, hardware drivers and CP communication cards (e.g., CP 1623 replacing legacy CP 1613) must be updated in HW Config.

Impact on Third-Party HMI Panels and Field Terminals (STAHL)

In hazardous chemical and oil refining areas, plants frequently deploy certified explosion-proof (Zone 1 / Zone 2) operator terminals (such as R. STAHL OpenHMI series) interfaced with the PCS 7 OS via OPC DA:

OPC DA Client Connectivity: The third-party HMI runs a local visualization client that queries process tags from the WinCC OS Server via OPC Data Access (OPC DA 2.05a or 3.0).
If the OS is Upgraded:
The WinCC OPC DA server binary changes from 32-bit WinCC V7.0 to modern WinCC V7.3.
If the STAHL panel relies on legacy WinCC client components installed on the panel, those client components must be updated to match the server version.
If the panel queries tags as an independent OPC client, the communication will survive, provided tag names and DCOM security remain identical.

DCOM Hardening and Network Security Transitions in Windows 7

The most common cause of complete communication failure after upgrading from Windows XP to Windows 7 is Microsoft DCOM security changes:

Windows XP Default: Highly permissive DCOM defaults allowed anonymous or unauthenticated RPC calls from third-party HMIs.
Windows 7 Hardening: Microsoft enforces strict RPC authentication (Kerberos or NTLMv2 with packet integrity).
Remediation via dcomcnfg:
1. On the new IPC827D, open dcomcnfg.exe.
2. Navigate to Component Services > Computers > My Computer > Properties > COM Security.
3. Under Access Permissions and Launch and Activation Permissions, click Edit Default and Edit Limits.
4. Ensure the group SIMATIC HMI, Everyone, and ANONYMOUS LOGON are granted Remote Access, Remote Launch, and Remote Activation.
5. In Windows Firewall, create inbound exceptions for TCP Port 135 and the WinCC OPC server executable (OPCServer.exe).

Tag Structure Preservation: Standard Library vs APL Migration

A pivotal architectural decision during migration is choosing whether to adopt the Advanced Process Library (APL):

Migration Without New Functions (Recommended for Legacy HMI Preservation):
Retains the classic PCS 7 Standard Library blocks in CFC.
Tag names in WinCC Tag Management remain 100% identical (e.g., TIC101.V, P101.QSTART).
The third-party STAHL HMI can continue polling the exact same tag addresses without requiring any screen or script modifications on the panel!
Migration With New Functions (APL Adoption):
Technological blocks are replaced with APL blocks (PIDConL, MotL).
Tag structures change to APL standards (e.g., TIC101.PV_Out.Value, P101.FbkRunOut.Value).
Adopting APL breaks all tag bindings on the third-party HMI, requiring a complete, labor-intensive reprogramming of every screen on the external panel.

Comparison of Migration Strategies: With vs Without New Functions

The table below compares the operational implications of the two migration strategies when interfacing third-party HMIs.

Migration StrategyAS Block UpgradesWinCC Tag StabilityThird-Party HMI ImpactOverall Commissioning RiskWithout New FunctionsRetains Standard Library100% UnchangedZero changes required on HMILow (Fast recovery)With New Functions (APL)Migrates to APLChanges to APL structuresEntire HMI database must be remappedHigh (Extended outage)

Verification

To confirm that third-party HMI communication is restored following the upgrade:
1. On the new IPC827D, verify that WinCC Runtime is active and the OPC DA server (OPCServer.exe) is running.
2. From the third-party STAHL HMI, ping the IP address of the IPC827D to confirm network connectivity across the terminal bus.
3. Open an OPC test client (such as Matrikon OPC Explorer or OPC Quick Client) on the third-party HMI: browse OPCServer.WinCC on the IPC827D.
4. Verify that tag browsing succeeds without Access Denied (0x80070005) DCOM errors.
5. Launch the third-party HMI runtime application: confirm that all faceplate values update dynamically and operator setpoint commands execute in the AS.

Limitations and Operational Precautions

Never attempt to perform an in-place operating system upgrade from Windows XP directly to Windows 7; perform a clean operating system installation on the new IPC827D hardware.
When procuring replacement IPC827D workstations, ensure the ordered MLFBs include the pre-installed SIMATIC PCS 7 software image and verified hardware communication processors.
Always maintain a complete, untouched ghost/image backup of the original Windows XP OS station and third-party HMI software prior to site cutover.
Validate final software licenses and options against the applicable Siemens catalog and authorized distributor quotation before deploying production upgrades.

Engineer FAQ

Will my STAHL HMI faceplates break if I upgrade the PCS 7 OS?

If you migrate 'without utilization of new functions', tag names remain identical, so the HMI faceplates will continue working once Windows 7 DCOM permissions are configured. If you migrate to APL, the tag structure changes completely, breaking all faceplate links on the third-party HMI.

Why does the third-party HMI report '0x80070005: Access Denied' when connecting via OPC?

This is a classic Windows DCOM security rejection. Windows 7 blocks remote unauthenticated OPC connections by default. You must configure dcomcnfg on the new Windows 7 station to permit Remote Access to ANONYMOUS LOGON and Everyone.

Can I use OpenPCS 7 instead of local WinCC OPC DA?

Yes. Deploying OpenPCS 7 provides a standardized, centralized OPC gateway that isolates the production OS server from third-party client traffic and supports modern OPC UA, eliminating DCOM security barriers.