C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

Version Compatibility Constraints Between WinCC OS Clients and Servers in SIMATIC PCS 7

Version Compatibility Constraints Between WinCC OS Clients and Servers in SIMATIC PCS 7

In SIMATIC PCS 7 and WinCC, an OS Client running a newer version (such as PCS 7 V8.x on Windows 7) cannot connect to or operate with an OS Server running an older version (such as PCS 7 V7.1 SP3 on Windows Server 2003). Standard rich OS Clients strictly require identical WinCC software versions, service packs, and update levels as the OS Server because internal DCOM RPC interfaces, project database schemas (SQL Server 2005 vs 2008 R2), and runtime communication protocols are version-locked. To upgrade client hardware to Windows 7 without altering the V7.1 server, run PCS 7 V7.1 in a virtualized Windows XP/7 compatible environment, deploy WinCC Web Navigator clients, or execute a coordinated plant-wide upgrade.

Table of Contents

Executive Summary

Industrial lifecycle management often faces asymmetric hardware obsolescence: commercial desktop workstations hosting operator interfaces (OS Clients) fail or require replacement with modern Windows 7 PCs long before plant management approves the capital expense and planned downtime necessary to modernize central OS Servers running legacy operating systems (such as Windows Server 2003 with PCS 7 V7.1 SP3). Plant engineers frequently inquire whether newly procured PCS 7 V8.x OS Clients can connect directly across the Terminal Bus to an existing PCS 7 V7.1 OS Server. In SIMATIC PCS 7, the answer is an absolute no. Understanding the architectural dependencies that mandate version parity allows engineering teams to deploy compliant bridge solutions.

The Principle of Strict Version Parity in WinCC Client-Server Architectures

WinCC multi-client architectures enforce strict software alignment:

  • Rich Client Architecture: Unlike thin web browsers, a standard WinCC OS Client executes local instances of the WinCC runtime graphics engine (PDLRuntimeSystem), alarm manager, and tag logging channels.
  • Version Parity Mandate: Siemens documentation explicitly mandates: 'An OS client and OS server must always run the identical version of WinCC and PCS 7'. Mixing a V8.x client with a V7.x server is rejected at the protocol level during project loading.

Why Rich OS Clients Cannot Cross Version Boundaries

Connecting across major versions fails due to three unbridgeable software barriers:

  • SQL Server Database Engine Incompatibility: PCS 7 V7.1 utilizes Microsoft SQL Server 2005 (32-bit). PCS 7 V8.x utilizes Microsoft SQL Server 2008 R2 SP2 (64-bit). The WinCC client communication stack directly queries server database views that exhibit structural schema differences across versions.
  • DCOM RPC Serialization: Inter-station function calls (such as alarm acknowledgments and script triggers) use compiled COM/DCOM interfaces whose class GUIDs and memory argument structures change between major PCS 7 releases.
  • Server Data Package (*.pck) Parsing: An OS Client loads binary Server Data Packages generated by the OS Server. A V8.x client cannot parse the legacy format of a V7.1 package.

Database Schema and DCOM Protocol Divergence

Even minor service pack discrepancies can cause instabilities:

  • A PCS 7 V7.1 SP3 client connecting to a V7.1 SP2 server may experience intermittent script aborts.
  • Crossing a major boundary (V7 to V8) prevents the client from even opening the server's start picture (@Screen.pdl).

WinCC Client-Server Interoperability Matrix

The following table summarizes client-server compatibility rules in SIMATIC PCS 7:

OS Client VersionOS Server VersionConnection Supported?Failure Mode / SymptomTechnical Root CausePCS 7 V8.x (Win 7)PCS 7 V7.1 (Server 2003)NO (Strictly Unsupported)Project load aborts; cannot open PDLsSQL Server & DCOM class mismatch.PCS 7 V7.1 (Win XP)PCS 7 V8.x (Server 2008)NO (Strictly Unsupported)Server rejects client connectionProtocol version incompatible.PCS 7 V7.1 SP3PCS 7 V7.1 SP3YES (Fully Supported)Normal operational runtimeExact version and SP parity.WinCC Web Navigator V8WinCC Web Server V7.1Partial (Compatibility Mode)Web rendering only (Not rich client)Web server encapsulates protocol.

Migration and Coexistence Strategies for Mixed-OS Plants

When new Windows 7 PC hardware must be introduced into a legacy V7.1 plant environment, engineers have three viable strategies:

  1. Virtualized Client Environment: Install virtualization software (VMware Workstation or ESXi) on the new Windows 7 PC. Run a virtualized guest instance of Windows XP SP3 with PCS 7 V7.1 SP3 OS Client, preserving exact version parity over the virtual NIC.
  2. WinCC Web Navigator Thin Clients: Deploy WinCC Web Navigator on the V7.1 server; operator workstations on Windows 7 access process pictures via Internet Explorer web sessions.
  3. Coordinated Full-Plant Upgrade: Upgrade the OS Server pairs and OS Clients concurrently to PCS 7 V8.1 during a planned outage.

Verification

To verify software version consistency across the plant:

  1. Installed Software Audit: On every OS Server and OS Client, open SIMATIC Manager and select Help > About > Installed Software > Display.
  2. Version Parity Check: Confirm that SIMATIC WinCC and SIMATIC PCS 7 report identical version, Service Pack, and Update levels (e.g. V7.1 SP3 Upd4) across all stations.
  3. Simatic Shell Validation: In Windows Explorer on the client, open Simatic Shell. Confirm that the server is reachable and project files can be selected without format warnings.

Limitations and Operational Precautions

  • Never Force Connection via Registry Hacks: Attempting to bypass version checks by modifying Windows registry keys destroys project database integrity.
  • License Entitlements: Ensure client licenses match the installed software version in Automation License Manager; a V8.0 license cannot license a legacy V7.1 installation without appropriate backward-compatible entitlements.
  • Procurement Disclaimer: When ordering replacement PC hardware for legacy plants, consult with an authorized Siemens distributor to ensure the hardware platform supports the required legacy operating systems and driver sets.

Engineer FAQ

Can a PCS 7 V8.0 client connect to a PCS 7 V8.1 server?

No. Even within the V8 generation, V8.0 and V8.1 use different WinCC releases (WinCC V7.2 vs V7.3) and cannot be mixed.

Can OpenPCS 7 bridge two different PCS 7 versions?

Yes, OpenPCS 7 exposes standard OPC DA/HDA/A&E interfaces; an external OPC client can read data from both V7 and V8 systems simultaneously.

Does Siemens support running PCS 7 V7.1 in Windows 7 'XP Mode'?

Windows 7 XP Mode is a desktop virtualization feature not certified by Siemens for continuous 24/7 industrial production; deploy certified VMware solutions instead.

Technical References

Related Articles

Related Tags

  • https://industrialautomation.net/search?query=simatic-pcs7
  • https://industrialautomation.net/search?query=wincc
  • https://industrialautomation.net/search?query=compatibility
  • https://industrialautomation.net/search?query=client-server
6 respuestas