Managing Version Compatibility and Downward Incompatibility Between PCS 7 APL V9.0 SP1 and SP2

In SIMATIC PCS 7, software projects and block libraries are strictly downward incompatible. A project engineered or compiled with PCS 7 V9.0 SP2 Upd1 (APL V9.0 SP3 / Basis V9.0 SP3) cannot be moved to or compiled on an Engineering Station running PCS 7 V9.0 SP1. Newer service packs introduce expanded block interfaces, new feature bits, and updated structural data types that older compiler versions and libraries cannot interpret, causing fatal compilation errors and block interface conflicts. To resolve this, upgrade the target Engineering Station to match or exceed the authoring station's release level.

Executive Summary

In multi-engineer automation teams or distributed contracting arrangements, project archives frequently move between different engineering workstations. A common scenario arises when an automation engineer performs project development on an Engineering Station running SIMATIC PCS 7 V9.0 SP2 Upd1 (which incorporates Advanced Process Library V9.0 SP3 and Basis Library V9.0 SP3), and subsequently attempts to restore and open that project on another workstation running PCS 7 V9.0 SP1.

While engineers sometimes assume that sharing the same major version number ('V9.0') ensures seamless cross-station compatibility, attempting to open, modify, or compile a higher-service-pack project on a lower-service-pack station leads to severe project corruption. The older CFC compiler fails to recognize newer APL feature bits, pin structures, and system functions, generating fatal block interface errors and corrupting instance data blocks. This guide explains the technical reasons behind downward incompatibility in PCS 7 and outlines the mandatory upgrade rules required to maintain engineering integrity.

Architecture and Fundamental Mechanics

The internal architecture of SIMATIC PCS 7 libraries and CFC compilation enforces unidirectional version progression:

Structural Block Interface Expansion:
- Between PCS 7 V9.0 SP1 and V9.0 SP2 / SP3, Siemens released updates to both the Advanced Process Library (APL) and Basis Library.
- Newer releases add new input/output parameters, expand feature bit masks (e.g., introducing Feature.Bit4 or Feature2 definitions), and modify internal algorithmic function blocks (FBs).
- When an instance is placed in a CFC chart under SP2, its instance DB is compiled with the expanded parameter footprint.
The CFC Compiler Interface Validation Trap:
- When the project is opened on an ES running V9.0 SP1, the local Master Data Library and system catalogs contain only the older block signatures.
- When the engineer attempts to compile charts, s7tgtopx.exe detects an interface mismatch: the block instance in the chart expects pins and data structures that do not exist in the local library description.
- The compiler halts with: Block interface has changed or Unknown parameter. Forcing a compilation can overwrite instance DB structures, corrupting the project database.
Approved Unidirectional Migration Paradigms:
- PCS 7 officially supports moving projects ONLY forward (from lower versions to higher versions):
- Mode 1: Update with utilization of new functions (upgrading block types in the Master Data Library and updating instances).
- Mode 2: Update without utilization of new functions (retaining existing block versions under newer engineering software).
- Reverse migration (degrading a project) is completely unsupported and technically impossible without manual chart re-engineering.

Step-by-Step Implementation Procedure

Follow these steps to align engineering stations and prevent version corruption:

Audit Installed Software Versions on Both Stations:
- On both the authoring ES and the target ES, open SIMATIC Manager.
- Select 'Help > About... > Installed Software'.
- Click 'Display' and inspect the exact version strings for:
- SIMATIC PCS 7 (e.g., V9.0 SP1 vs V9.0 SP2 Upd1)
- PCS 7 Advanced Process Library
- PCS 7 Basis Library
- CFC and SFC
Upgrade the Target Engineering Station:
- Do NOT attempt to compile the SP2 project on the SP1 station.
- Obtain the official installation media for SIMATIC PCS 7 V9.0 SP2 and the corresponding Update Collections (e.g., UC03 or latest).
- Install the service pack and update collection on the target Engineering Station.
- Reboot the workstation.
Verify Library Version Parity:
- Open SIMATIC Manager on the newly upgraded station.
- Open the Master Data Library of the multiproject.
- Verify that the installed APL and Basis Library versions match the authoring workstation.
Recompile and Verify Consistency:
- Open the multiproject.
- Select 'Options > Charts > Check Consistency...'. Confirm zero block interface errors.
- Execute 'Chart > Compile > Charts as Program...' ('Changes only').
- Verify that compilation concludes with 0 Errors, 0 Warnings.

Verification

In SIMATIC Manager on the upgraded station, open CFC charts containing APL technological blocks (e.g., MotL, PIDConL): verify that block pins and headers display without yellow question marks or missing parameter banners.
Open an SFC chart or SFC Type: verify that state sequencers open and compile without syntax errors.
Perform a test delta compile: confirm that the compiler successfully generates machine code without raising block interface warnings.

Limitations and Operational Precautions

Never attempt to overwrite newer library blocks in a project with older library blocks; doing so creates broken pointer references that can force the CPU into STOP mode during runtime downloads. Engineering teams collaborating on the same multiproject must standardize on identical software service pack and update levels across all workstations. Software updates and version entitlements should be verified through an authorized Siemens distributor or the Siemens Industry Mall.

Engineer FAQ

Can a PCS 7 project engineered in V9.0 SP2 be opened in V9.0 SP1?

It can be opened, but compiling or modifying charts will cause fatal compilation errors due to missing block parameters and interface mismatches.

Why is downward compatibility not supported in PCS 7?

Because newer service packs add parameters, feature bits, and data structures to blocks that older software and compilers cannot recognize or compile.

What happens if I compile an SP2 project on an SP1 station?

The compiler aborts with 'Block interface has changed' or corrupts instance data blocks, potentially causing controller faults upon download.

How should engineering teams handle multiple workstations?

All engineering stations, OS servers, and clients must be updated to the identical PCS 7 service pack and update collection level.

Can I upgrade from SP1 to SP2 without changing controller runtime blocks?

Yes, using the migration option 'Update without utilization of new functions', which preserves existing block versions while updating the engineering tools.