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

Migrating PCS 7 Multiprojects Across Major Releases: WinCC Project Migrator and Convert Project Data

Migrating PCS 7 Multiprojects Across Major Releases: WinCC Project Migrator and Convert Project Data

When migrating a SIMATIC PCS 7 multiproject from V7.0 SP3 / V7.1 SP4 through V8.0 SP2 to V8.1 SP1, the WinCC Project Migrator does not trigger automatically between V8.0 and V8.1 because both versions share the same core Microsoft SQL Server database structure. To update graphic pictures, custom C-scripts, and faceplates in WinCC V7.3 (PCS 7 V8.1), you must open WinCC Explorer and manually execute 'Tools > Convert Project Data', selecting 'Pictures and Faceplates' and 'Global Script' with language set to English (USA). Additionally, legacy faceplate calls such as PCS7_openfaceplate must be updated to APL_OpenFaceplate.

Table of Contents

Executive Summary

Migrating legacy SIMATIC PCS 7 systems across multiple major releases—such as upgrading from PCS 7 V7.0 SP3 or V7.1 SP4 to V8.1 SP1—requires a structured, intermediate migration path to preserve engineering data, CFC charts, OS projects, and custom scripts. While transitioning from V7.x to V8.0 triggers the automatic WinCC Project Migrator to convert the Microsoft SQL Server database schema, moving from V8.0 SP2 to V8.1 SP1 often bypasses the migrator. This behavior leaves graphics files, faceplates, and project functions (.fct) unconverted, resulting in runtime script failures when opening faceplates. This article details the database transition mechanics, explains why automatic migration is bypassed, and outlines the mandatory manual conversion steps.

Multi-Version Migration Architecture: V7.0 to V8.1 SP1

Siemens PCS 7 migration rules do not permit direct project opening across multiple major generations without intermediate conversion stages. Upgrading an installed plant from V7.0 SP3 to V8.1 SP1 requires two intermediate steps:

  1. Stage 1: V7.0 SP3 to V7.1 SP4: Updates basic library blocks, STEP 7 database formats, and WinCC V6.2 to V7.0 SP3.
  2. Stage 2: V7.1 SP4 to V8.0 SP2: Converts classic engineering data to support the Advanced Process Library (APL) and migrates WinCC database formats from SQL Server 2005 to SQL Server 2008 R2.
  3. Stage 3: V8.0 SP2 to V8.1 SP1: Introduces WinCC V7.3 (SQL Server 2014) and modernized APL faceplate structures.

Why WinCC Project Migrator Skips Between V8.0 and V8.1

The WinCC Project Migrator is designed to execute only when the underlying WinCC database table schema versions differ fundamentally. In WinCC V7.2 (PCS 7 V8.0 SP2) and WinCC V7.3 (PCS 7 V8.1 SP1), the core configuration database structure (*.mdf / *.ldf) is backward compatible, leading the Migrator tool to report that the project 'does not require migration'.

However, internal graphic object structures (*.pdl), faceplate types (*.fpt), and compiled C-scripts (Global Script) require recompilation against the V7.3 graphics engine. When the automated migrator does not trigger, these files remain in their legacy binary format, causing runtime script crashes and rendering errors.

Legacy Faceplate Scripting and APL API Changes

A common failure during V7.x to V8.x migration is the breakdown of custom project functions and navigation buttons. In classic PCS 7 libraries, opening a faceplate relied on internal C-functions such as PCS7_openfaceplate(...) or direct calls to the Faceplate Designer (@screen).

In PCS 7 V8.1, the APL utilizes APL_OpenFaceplate(...) and standardized tag prefixing mechanisms (@PCS7_ prefix). Custom scripts that call obsolete V7 functions fail to compile or throw access violation errors in runtime. Engineers must run the OS Project Editor and update project-specific script calls to match the modernized APL calling conventions.

Migration Matrix and Database Evolution Across PCS 7 Releases

The following table details the intermediate software platforms, underlying database versions, and required migration actions:

Migration HopSource VersionTarget VersionUnderlying WinCC & SQL VersionMandatory Migration MechanismHop 1PCS 7 V7.0 SP3PCS 7 V7.1 SP4WinCC V6.2 SP3 to V7.0 SP3 (SQL 2005)Automatic WinCC Project MigratorHop 2PCS 7 V7.1 SP4PCS 7 V8.0 SP2WinCC V7.0 SP3 to V7.2 (SQL 2008 R2)Automatic WinCC Project Migrator + OS Project EditorHop 3PCS 7 V8.0 SP2PCS 7 V8.1 SP1WinCC V7.2 to V7.3 (SQL 2014)Manual 'Convert Project Data' + OS Project EditorCFC UpdateClassic CFCModernized CFCSTEP 7 V5.4 to V5.5 SP4Options > Block Types > New Version + Full CompileFaceplatesClassic PDLAPL Modernized PDLWinCC Graphic Designer 7.3Tools > Convert Project Data (Pictures & Faceplates)

Step-by-Step Multiproject Migration Procedure

Method 1: Converting Graphic Pictures and Global Scripts in WinCC V7.3

  1. Open the migrated OS project in WinCC Explorer on the PCS 7 V8.1 SP1 Engineering Station.
  2. Navigate to the menu bar and select Tools > Convert Project Data.
  3. In the conversion dialog, select the checkboxes for Pictures and Faceplates and Global Script.
  4. In the language selection drop-down, select English (USA) regardless of the target runtime language.
  5. Click OK and allow the batch conversion tool to recompile all .pdl, .fpt, and .fct files.

Method 2: Running the OS Project Editor and Updating Block Icons

  1. In WinCC Explorer, double-click OS Project Editor.
  2. Under the Complete configuration tab, select the appropriate monitor resolution and layout.
  3. Click OK to regenerate standard system pictures (@screen.pdl, @overview1.pdl, @alarmline.pdl).
  4. In SIMATIC Manager, select the OS project and choose Options > Plant Hierarchy > Create/Update Block Icons.
  5. Perform a full compilation of the OS and test runtime activation.

Verification

To verify successful project migration and script compatibility:

  1. Script Syntax Check: In WinCC Explorer, open Global Script > C-Editor. Select Options > Compile All Scripts and confirm 0 compilation errors.
  2. Faceplate Activation: Activate WinCC Runtime. Click on multiple technological block icons (e.g., valves, motors, PID controllers). Confirm that standard and custom faceplates open immediately without script errors.
  3. Diagnostic Log Review: Open the diagnostic folder C:\Program Files (x86)\Siemens\WinCC\Diagnostics\ and inspect WinCC_Sys_01.log and PDLCS.log. Verify that no Call of undefined function or SQL Error entries appear.

Limitations and Operational Precautions

  • Language Selection in Conversion: When running 'Convert Project Data', always select English (USA). Running conversion with a non-English language setting can cause corrupted static text strings in multilingual projects.
  • Direct Migration Prohibition: Never attempt to open a PCS 7 V7.0 project directly in PCS 7 V8.1. Doing so permanently corrupts the internal cross-reference and CFC database structures.
  • Backup Discipline: Create an uncompressed archive (.zip) of the multiproject at each intermediate milestone before proceeding to the subsequent version hop.

Engineer FAQ

Why does WinCC Project Migrator state that my V8.0 project does not need migration in V8.1?

Because WinCC V7.2 and V7.3 share compatible SQL Server database tables. The Migrator updates SQL schemas, not picture binary formats, which requires the manual 'Convert Project Data' utility.

Can I migrate a PCS 7 multiproject with customized C-scripts without rewriting code?

Standard C-scripts migrate successfully, but scripts that invoke internal, undocumented Siemens faceplate APIs (such as PCS7_openfaceplate) must be adapted to modern APL functions.

Is it necessary to compile AS connections after upgrading to V8.1 SP1?

Yes. Upgrading WinCC drivers requires compiling the OS with the 'Tags and Messages' and 'SFC Visualization' options selected to rebuild communication mappings.

Technical References

Related Articles

Related Tags

  • https://industrialautomation.net/search?query=simatic-pcs7
  • https://industrialautomation.net/search?query=migration
  • https://industrialautomation.net/search?query=wincc
  • https://industrialautomation.net/search?query=os-project-editor
6 respuestas