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

Evaluating Cross-Version Compatibility Between PCS 7 V8.2 OS Clients and PCS 7 V9.0 OS Servers

Evaluating Cross-Version Compatibility Between PCS 7 V8.2 OS Clients and PCS 7 V9.0 OS Servers

Connecting an OS Client running SIMATIC PCS 7 V8.2 SP1 to an OS Server running PCS 7 V9.0 SP1 is strictly unsupported by Siemens for continuous production operation. PCS 7 V9.0 introduces WinCC V7.4 SP1/V7.5 underlying architectures, updated SQL Server database schemas, revised Server Data (.pck) package formats, and modernized Advanced Process Library (APL) faceplate scripts that cannot be processed by an older V8.2 client runtime. Attempting cross-version client-server operation results in broken faceplate rendering, script execution errors, alarm logging failures, and client disconnection. While Siemens permits a temporary mixed-version state strictly during phased plant migrations while stations are actively being upgraded, both OS servers and clients must be brought to the identical PCS 7 version before resuming normal plant control.

Table of Contents

Executive Summary

In large-scale industrial manufacturing and continuous processing facilities governed by SIMATIC PCS 7, plant modernization and software updates represent significant engineering undertakings. Plant managers and automation engineers frequently evaluate phased upgrade strategies, seeking to minimize production downtime by upgrading central OS servers first while temporarily retaining existing OS clients on their legacy software baseline (such as connecting PCS 7 V8.2 SP1 clients to newly upgraded PCS 7 V9.0 SP1 servers).

However, Siemens engineering guidelines and release readmes strictly forbid running heterogeneous, mixed-version client-server architectures during steady-state production. Major PCS 7 version transitions introduce fundamental structural changes across the SCADA framework, including updated Microsoft SQL Server versions, modified tag and alarm database schemas, revised server package (.pck) specifications, and updated Advanced Process Library (APL) C/VBScript routines. This guide details the architectural incompatibilities between PCS 7 V8.2 and V9.0, explains the operational risks of cross-version deployment, outlines the narrow boundary conditions under which temporary mixed operation is permitted during phased migrations, and details the verified upgrade path.

Architecture and Fundamental Mechanics

The client-server architecture in SIMATIC PCS 7 is built upon tightly coupled communication protocols, shared database schemas, and exported server packages:
1. Server Data Packages (.pck): An OS Client accesses server process data, alarms, and historical archives by loading the server package generated on the OS Server during compilation. The internal binary and XML structure of .pck files is version-dependent. A PCS 7 V8.2 client attempting to parse a V9.0 server package encounters deserialization errors and unrecognized structural attributes, leading to failed tag resolution.
2. Underlying WinCC and SQL Server Platforms:
* PCS 7 V8.2: Built on WinCC V7.4 and Microsoft SQL Server 2014 (SP1/SP2).
* PCS 7 V9.0: Built on WinCC V7.4 SP1 (or V7.5 in later service packs) and Microsoft SQL Server 2016.
* The internal RPC interfaces, database view formats, and security tokens utilized for alarm synchronization and historical tag queries differ significantly between SQL Server 2014 and 2016, preventing reliable cross-version data exchange.
3. APL Faceplate and Scripting Discrepancies: PCS 7 V9.0 delivers modernized APL libraries featuring new block attributes, updated status double-words (Status3, Status4), and modified internal C-scripts (@pg_*.pdl). When an operator on a V8.2 client attempts to open a faceplate hosted on a V9.0 server, the older client lacks the required runtime script functions, causing the faceplate to fail to render, display blank parameter fields, or crash the local graphics runtime (PDLRT.exe).
4. Phased Migration Exception: Siemens documentation permits mixed-version operation ONLY as a transient intermediate state during an active software update sequence, provided that operator control is strictly managed and stations are upgraded sequentially within the shortest possible maintenance window.

Step-by-Step Implementation Procedure

Step 1: Review Siemens Compatibility Matrix and Upgrade Documentation

  1. Access the online Siemens Compatibility Tool for Automation and Drive Technology.
  2. Enter SIMATIC PCS 7 V8.2 SP1 and SIMATIC PCS 7 V9.0 SP1 into the tool to review official support statements.
  3. Confirm that continuous cross-version client-server operation is documented as unsupported.

Step 2: Establish a Phased Migration Plan

  1. Rather than attempting a permanent mixed-version architecture, plan a phased upgrade window where OS Servers and OS Clients are updated sequentially.
  2. If plant availability requires continuous monitoring, upgrade one OS Server of a redundant pair first, followed by the second OS Server, and immediately upgrade OS Clients station-by-station.
  3. Consult an authorized Siemens distributor or the Siemens Industry Mall to acquire the necessary PCS 7 V9.0 upgrade license packages (including OS Software Upgrade packages for Servers and Clients).

Step 3: Upgrade OS Client Hardware and Operating System

  1. Check the operating system compatibility: PCS 7 V8.2 supported Windows 7 (32/64-bit), whereas PCS 7 V9.0 mandates Windows 10 Enterprise (64-bit) or Windows 7 SP1 64-bit (with specific update requirements).
  2. Back up all local client configuration files and license keys via Automation License Manager.
  3. Install the certified Windows operating system and required service packs on the client hardware.

Step 4: Install SIMATIC PCS 7 V9.0 on the OS Client

  1. Mount the PCS 7 V9.0 installation media on the client workstation.
  2. Run Setup.exe and select the OS Client installation profile.
  3. Complete the installation, install all required PCS 7 V9.0 updates (matching the server service pack and update level), and restart the machine.
  4. Transfer the upgraded PCS 7 V9.0 OS Client runtime license from ALM.

Step 5: Assign Server Packages and Validate Client Runtime

  1. In SIMATIC Manager on the ES, open the OS Client project.
  2. In WinCC Explorer, right-click Server Data and select Assign.
  3. Assign the updated PCS 7 V9.0 server package exported by the upgraded OS Server.
  4. Download the OS Client project from the ES to the physical client station.
  5. Activate WinCC Runtime on the client station and confirm seamless process communication.

Verification

  1. On the upgraded PCS 7 V9.0 client station, open WinCC Runtime.
  2. Verify that all process pictures load without script warnings or missing picture object badges.
  3. Open multiple APL faceplates (motors, valves, analog monitors): confirm that live process values, setpoints, and status indicators display correctly.
  4. Issue operator commands from the client (e.g., start/stop motor, adjust setpoint) and confirm that commands execute immediately on the AS.
  5. In WinCC Explorer on the OS Server, open Tools > Status of the System and verify that all connected clients report status 'Connected' on identical software release levels.

Limitations and Operational Precautions

  1. Siemens Customer Support will reject incident tickets regarding communication errors, faceplate script faults, or archive failures if the system is operating in a permanent mixed V8.2/V9.0 state.
  2. Server data packages (.pck) must be re-exported and reassigned whenever the server is compiled; mismatched package versions cause client runtime initialization failure.
  3. Operating system differences (Windows 7 vs. Windows 10) introduce terminal bus security and network authentication barriers if not aligned in SIMATIC Shell.
  4. Redundant OS servers must NEVER run mixed major versions; redundancy synchronization will immediately abort.

Engineer FAQ

Can an OS Client V8.2 connect to a V9.0 server temporarily during an outage?

Yes. During a planned phased software update, a temporary connection may function for basic monitoring, but it is not guaranteed or supported for sustained process control.

Why do APL faceplates fail when connecting across versions?

APL blocks in PCS 7 V9.0 utilize extended internal status tags and updated C-scripts that do not exist on a PCS 7 V8.2 client installation, causing graphics errors and script aborts.

Can redundant OS servers run different PCS 7 versions?

No. Redundant OS servers must run identical software versions, service packs, and update levels. Server redundancy pairing will fail immediately if versions differ.

What licenses are required to upgrade an OS Client from V8.2 to V9.0?

An OS Client software upgrade package is required. Final license quantities and order numbers must be confirmed with an authorized Siemens distributor or the Siemens Industry Mall.

Where can I find official compatibility statements between PCS 7 releases?

Official compatibility tables are published in the Siemens Kompatibilitäts-Tool (Compatibility Tool) available on the Siemens Industry Online Support portal.

Technical References

Related Articles

Related Tags

  • PCS 7 V8.2
  • PCS 7 V9.0
  • OS Client
  • OS Server
  • Compatibility
20 respuestas