Why PCS 7 CFC Charts Cannot Be Downgraded Between Service Packs and How to Realign Engineering Versions
SIMATIC PCS 7 and STEP 7 Continuous Function Charts (CFC) cannot be downgraded or converted from a newer Service Pack (such as PCS 7 V9.0 SP3) to an older Service Pack (such as V9.0 SP1). When a project or chart is opened, modified, or compiled in PCS 7 V9.0 SP3, the internal CFC database schema and object container descriptors are permanently upgraded to match the newer CFC compiler version (s7cfc*.dll). Opening these charts on an older engineering station results in fatal version rejection dialogs. To realign engineering environments, upgrade the older ES stations to match the field PG's Service Pack—which does not require new license purchases within the same main version—or reconstruct the logic using exported SCL sources or XML exchange files.
Table of Contents
- Database Architecture of PCS 7 CFC Charts and Version Compatibility
- Service Pack Upgrades vs. Hotfix / Update Compatibility
- Symptoms of Database Incompatibility Across Service Packs
- Method: Standardized Procedures to Realign Engineering Stations
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Database Architecture of PCS 7 CFC Charts and Version Compatibility
In SIMATIC PCS 7, an S7 program does not store CFC charts as raw text or flat graphics files. Instead, each chart is a relational object database embedded within the STEP 7 project directory under the chart container:
- Object Schema: Every block instance, parameter connection, textual link, and run sequence entry is tracked in binary database tables.
- One-Way Upgrading: When an engineering station running a newer Service Pack opens an older chart, STEP 7 automatically executes an internal database migration, updating table structures, internal pointers, and compiler metadata.
- No Backward Converter: Siemens does not provide a reverse database transformation utility. The older CFC software lacks the schema definitions, class IDs, and serialization parsers introduced in the newer Service Pack.
Service Pack Upgrades vs. Hotfix / Update Compatibility
Understanding Siemens' versioning hierarchy explains why some project exchanges succeed while others fail:
Symptoms of Database Incompatibility Across Service Packs
Attempting to open an SP3 chart on a station running SP1 triggers explicit system alerts:
* STEP 7 Missing Package Error: The project contains objects of the software package 'CFC' of version V9.0 SP3 which cannot be edited with the installed version V9.0 SP1.
* Object Access Lock: In SIMATIC Manager, the CFC charts appear with a yellow padlock or generic question mark icon, and double-clicking returns: Cannot open object. Version mismatch.
* Compilation Block: Executing a project compilation from the plant hierarchy aborts immediately, citing mismatched software component versions.
Method: Standardized Procedures to Realign Engineering Stations
When encountering this version discrepancy between a field programming device (PG) and central engineering stations (ES), implement one of two approved engineering approaches:
Approach A (Recommended): Upgrade the Engineering Stations to SP3
Because Service Packs do not require new software license purchases within the same main version of PCS 7 (a license for PCS 7 V9.0 covers V9.0, V9.0 SP1, V9.0 SP2, and V9.0 SP3):
1. Download the official SIMATIC PCS 7 V9.0 SP3 Update Package from Siemens Industry Online Support (SIOS).
2. Create full disk image backups of your engineering stations.
3. Install PCS 7 V9.0 SP3 on all ES client and server stations to match the field PG.
4. Open the project in SIMATIC Manager. All stations can now open, edit, compile, and download charts transparently.
Approach B: Logic Reconstruction via Source Code and XML Export
If strict site change-freeze policies prevent updating the ES clients immediately, port logic manually without transferring binary chart files:
1. Export SCL Sources:
- If custom algorithmic logic was written in SCL, export the source file from the PG (Sources -> Export Source...).
- SCL source text is version-independent ASCII/Unicode text.
- Import the .SCL source on the SP1 station and compile it into a local block.
2. Re-create Chart Interconnections:
- On the SP1 station, manually instantiate the required blocks into a fresh SP1 CFC chart.
- Use the SP3 chart on the field PG as a visual reference for signal routing.
3. Utilize Plant Automation Accelerator (PAA) / CAx XML Exchange:
- If the facility utilizes Siemens PAA or standard XML engineering exchange tools, export the technological hierarchy to XML.
- Import the XML file on the SP1 station to reconstruct chart structures automatically.
Verification
To verify that software versions are unified and charts function without conflict:
- Open SIMATIC Manager on all engineering stations and select Help -> About -> Installed Software -> Display.
- Verify that every station displays an identical version string for CFC (e.g., CFC V9.0 + SP3).
- Open the modified CFC chart on the ES client: confirm that the chart opens without warning dialogs, blocks render properly, and signal lines display live values in online Test Mode.
- Perform a consistency check: right-click the Chart folder and select Check Block Types / Clean Up.... Confirm zero database errors.
Limitations and Operational Precautions
- Never Attempt Manual Hex / Registry Modification: Editing binary chart database files (
*.s7p,*.dbf) or altering registry entries to bypass version checks corrupts the project database irreversibly. - CPU Online Download Restrictions: If a chart compiled in SP3 is downloaded to an AS controller, an older ES running SP1 cannot perform change downloads or upload the station from the CPU.
- Master Data Library Alignment: When upgrading to SP3, ensure that the Master Data Library (MDL) block types are also updated to prevent type-version conflicts during project compilation.
Engineer FAQ
Can I copy blocks from an SP3 chart and paste them into an SP1 chart?
No. Windows clipboard operations between different CFC Service Pack versions carry the internal SP3 metadata, causing the SP1 CFC editor to reject the paste operation with a version error.
Do I have to purchase new Siemens automation licenses to upgrade from SP1 to SP3?
No. Standard SIMATIC PCS 7 and STEP 7 licenses are version-specific to the main release (V9.0). Service Packs (SP1, SP2, SP3) and cumulative Updates (Upd) are free software enhancements that run under the existing V9.0 license.
What should field service engineers do before modifying customer charts on a field PG?
Always verify the customer's exact installed PCS 7 version and Service Pack before opening or modifying project files. Always create a date-stamped archive (.zip) of the project before connecting the field PG to prevent accidental one-way database upgrades.
Can an S7 project backup made in SP3 be restored in SP1?
The archive utility in SIMATIC Manager will extract the files, but SIMATIC Manager will prevent opening the project or displaying the charts once extracted, displaying a software package version mismatch.
Technical References
- Siemens Industry Online Support: SIMATIC PCS 7 V9.0 SP3 Delivery Release and Software Compatibility.
- SIOS Entry 109742323: PCS 7 Compendium Part A - Configuration Guidelines (Section: Software Upgrades and Compatibility).
- SIOS Entry 109809264: SIMATIC Process Control System PCS 7 Released Modules.
- Siemens Manual: SIMATIC CFC for S7 Engineering and System Administration.
Related Articles
- How to Locate and Apply the Official Migration Procedure for PCS 7 V9.1 SP2
- How to Upgrade SIMATIC PCS 7 V9.1 SP1 to V9.1 SP2 and License Requirements
- How to Resolve PCS 7 CFC Compilation Warnings and Prevent CPU Download Faults
Related Tags
- CFC
- PCS 7
- Service Pack
- Compatibility
- Engineering Station
- STEP 7
- Industrial Automation