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

Why Direct Migration from PCS 7 V7.0 to V9.0 is Blocked and How to Execute It via V8.0

Why Direct Migration from PCS 7 V7.0 to V9.0 is Blocked and How to Execute It via V8.0

Direct software migration from SIMATIC PCS 7 V7.0 to PCS 7 V9.0 is fundamentally blocked because the underlying software and database architectures underwent multiple generational transformations across intermediate releases. Siemens does not publish a "V7.0 to V9.0" manual because the WinCC Project Migrator, Microsoft SQL Server database schemas, and the CFC compiler cannot bridge more than one major architectural boundary in a single step. To upgrade a V7.0 project to V9.0, you must execute a two-stage migration: first migrate the V7.0 project to PCS 7 V8.0 (or V8.2) in an intermediate staging environment, compile and verify the databases, and then migrate that intermediate project to PCS 7 V9.0.

Table of Contents

The Generational Divide Between PCS 7 V7.0 and V9.0

Engineers searching Siemens documentation frequently discover manuals titled Software Update with Migration from V8.0 to V9.0, but find no single manual covering V7.0 to V9.0:
- PCS 7 V7.0 (2007): Built on Microsoft Windows XP SP2 / Server 2003, STEP 7 V5.4, WinCC V6.2, Microsoft SQL Server 2005, and classic PCS 7 Standard Library.
- PCS 7 V9.0 (2017): Built on Microsoft Windows 10 Enterprise (64-bit) / Server 2016, STEP 7 V5.6, WinCC V7.4 SP1, Microsoft SQL Server 2014 SP2, and the Advanced Process Library (APL).
- The Direct Jump Barrier: The WinCC Migrator in V9.0 requires a minimum source version of WinCC V7.2 or V7.3. It cannot parse WinCC V6.2 project tables directly.

Database Conversion Roadblocks: Sybase, SQL 2005, and SQL 2014

The technological constraint preventing direct migration lies in database engine evolution:

System LayerPCS 7 V7.0 BaselineIntermediate Stage (PCS 7 V8.0 / V8.2)Target Stage (PCS 7 V9.0)OS Relational DatabaseMicrosoft SQL Server 2005Microsoft SQL Server 2008 R2 / 2014Microsoft SQL Server 2014 SP2Operating SystemWindows XP Professional (32-bit)Windows 7 SP1 (64-bit)Windows 10 Enterprise LTSC (64-bit)CFC Internal FormatCFC V7.0 binary schemaCFC V8.0 / V8.2 extended tablesCFC V9.0 modern object dictionaryGraphic EngineClassic GDI / Sybase Dbf driversEarly WPF/Vector integrationNative hardware acceleration / Modern APL

Direct conversion fails because Microsoft SQL Server cannot attach or convert database files skipping multiple major SQL release generations simultaneously.

The Two-Stage Staging Strategy: V7.0 to V8.0 to V9.0

To execute the upgrade reliably, establish an isolated staging environment:

[PCS 7 V7.0 SP1/SP2/SP3] (Windows XP)
         │
         ▼ (Stage 1 Migration: WinCC V6.2 to V7.2/V7.4 Migrator)
[PCS 7 V8.0 SP2 or V8.2 SP1] (Windows 7 SP1 Staging VM)
         │
         ▼ (Stage 2 Migration: V8.x to V9.0 Migrator & APL Adaptation)
[PCS 7 V9.0 SP1/SP3] (Windows 10 LTSC Target Environment)

By staging the database transformation in PCS 7 V8.0 or V8.2, project tables, graphic scripts, and CFC run sequences are modernized safely before reaching V9.0.

Method: Step-by-Step Staging and Database Transformation

Follow this sequential procedure across the three operating environments:

Step 1: Project Preparation in PCS 7 V7.0

  1. Open the multiproject in SIMATIC Manager under Windows XP.
  2. Select File -> Save As..., enable With Reorganization (Slow), and save to clean storage.
  3. Open all CFC charts and verify zero compiler errors.
  4. Close all editors and create a full project archive (.zip).

Step 2: Intermediate Conversion in PCS 7 V8.0 / V8.2

  1. Deploy a virtual machine with Windows 7 SP1 (64-bit) and PCS 7 V8.0 SP2 or V8.2 SP1.
  2. Open SIMATIC Manager and retrieve the V7.0 archive.
  3. Allow STEP 7 to execute automatic database format conversion.
  4. Open the WinCC OS project: the WinCC Project Migrator launches automatically:
    - It upgrades WinCC V6.2 database structures to SQL Server 2008/2014.
    - Verify the migration log for 0 fatal errors.
  5. In SIMATIC Manager, open CFC, update block types, and run Chart -> Compile -> Charts as Program (Entire Scope).
  6. Open WinCC Explorer, run the OS Project Editor, and execute a full OS Compile.
  7. Save the project with reorganization and create a new archive.

Step 3: Final Modernization in PCS 7 V9.0

  1. Transfer the V8.x archive to the permanent PCS 7 V9.0 engineering station (Windows 10 LTSC).
  2. Restore the project in SIMATIC Manager.
  3. Open the WinCC OS project to allow the V9.0 Migrator to complete final table formatting.
  4. In SIMATIC Manager, update block types in the Master Data Library and synchronize charts.
  5. Run the OS Project Editor with V9.0 basic data templates.
  6. Perform full compilations of both AS and OS projects.

Verification

To confirm that the two-stage migration was successful:
- Open SIMATIC Manager: confirm that the multiproject opens cleanly with zero missing software package alerts.
- Check compiler diagnostics: verify that AS charts compile with 0 Errors and the OS compile finishes with 0 Errors.
- Launch WinCC Runtime: confirm that process pictures load, historical trend controls function, and alarms from the AS populate the alarm banner.
- Verify communication: test controller online connection via NetPro to confirm S7 named communication channels are active.

Limitations and Operational Precautions

  • Do Not Attempt In-Place Software Overwrites: Never attempt to install PCS 7 V8.0 over V7.0 or V9.0 over V8.0 on the same physical Windows installation. Operating system requirements differ completely; always use clean, dedicated virtual machines.
  • Standard Library vs. APL: Migrating a project without updating blocks keeps legacy Standard Library blocks in place. While PCS 7 V9.0 supports running legacy blocks in compatibility mode, planning a progressive conversion to APL is strongly advised.
  • Hardware Replacement Window: CPU 400 controllers running very early firmware revisions (pre-V5.0) cannot communicate with PCS 7 V9.0 and must be upgraded or replaced with CPU 410-5H.

Engineer FAQ

Why didn't Siemens create a direct converter from V7.0 to V9.0?

The architectural leap between WinCC V6.2 (SQL 2005) and WinCC V7.4 (SQL 2014) involves hundreds of table schema alterations. Supporting a direct converter across multiple major releases introduces massive regression risk compared to a proven intermediate staging step.

Where can I obtain temporary installation media for PCS 7 V8.0 or V8.2?

Siemens Technical Support provides temporary migration media to licensed customers upon opening an official Support Request (SR) detailing an active plant upgrade project.

What happens to customized C-scripts during the two-stage migration?

The WinCC Migrator checks C-script syntax. Obsolete internal functions from WinCC V6.2 are flagged in the migration log (Migration.log) and must be updated to modern WinCC ODK APIs.

Will running batches in SIMATIC BATCH survive this migration?

No. All active batch orders must be closed out in the V7.0 system before taking the final engineering backup. Historical batch logs can be archived using the BATCH historical backup utility.

Technical References

  • Siemens Industry Online Support: SIMATIC PCS 7 Software Update with Migration from V8.0 to V9.0.
  • Siemens Industry Online Support: SIMATIC PCS 7 Software Update with Migration from V7.0 to V8.0.
  • SIOS Entry 109742323: PCS 7 Compendium Part A - Configuration Guidelines (Section: Lifecycle and Migration).
  • SIOS Entry 109809264: SIMATIC Process Control System PCS 7 Released Modules.

Related Articles

Related Tags

  • Migration
  • PCS 7 V7.0
  • PCS 7 V8.0
  • PCS 7 V9.0
  • WinCC Migrator
  • SQL Server
  • Industrial Automation
20 respuestas