Delta Download Feasibility After Upgrading PCS 7 from SP1 to SP3

Performing an online delta download ('Download Changes only') to an automation station after upgrading SIMATIC PCS 7 from SP1 to SP3 is generally not permitted if the Service Pack updates standard library blocks, module drivers, or system function calls. Upgrading across Service Packs alters internal block interfaces, data structures, and the Basis Library, which enforces an 'Entire program' compilation and download with the CPU in STOP mode. Delta download is only feasible if you deliberately choose not to update the block types in the S7 program and omit module driver regeneration.

Executive Summary

Operating facilities often seek to install SIMATIC PCS 7 Service Packs—such as advancing from V9.0 SP1 to V9.0 SP3—to benefit from software stability patches and security fixes without halting continuous chemical or refining processes. When engineers attempt to compile and download after updating their Engineering Station, the compiler frequently disables 'Changes only' and demands an entire program download in STOP. This article details the boundary conditions governing online delta downloads during Service Pack upgrades, the role of library block versions, and strategies for phased migration.

Architecture and Fundamental Mechanics

Service Pack Upgrade Architecture and Delta Download Mechanics:

Online Delta Download Requirements (Download Changes only):
The CPU can remain in RUN mode during download only if all block interface definitions (inputs, outputs, static variables) remain 100% identical between offline charts and online CPU memory.
If any block type interface changes, CFC invalidates the existing DB instance structures and requires a cold restart.
What Changes Between SP1 and SP3:
Basis Library & APL: Siemens regularly modifies internal diagnostic structures, maintenance states (MS), or system interfaces between Service Packs.
Module Driver Rules: Driver generation algorithms are updated to support newer hardware firmware, regenerating @ system charts.
The Two Upgrade Methodologies:
1. Software Update with Utilization of New Functions: Full library update, block type updates, module driver regeneration. Strictly requires CPU STOP.
2. Software Update without Utilization of New Functions: Updates only the engineering tools (SIMATIC Manager, CFC editor), leaving the project's Master Data Library and block types untouched at SP1. Delta downloads remain possible, but new SP3 library features cannot be used.

Step-by-Step Implementation Procedure

Evaluating and Executing an SP1 to SP3 Update Strategy:

Determine Process Downtime Availability:
- If a planned plant outage is scheduled: Choose 'Update with utilization of new functions' (recommended for long-term support).
- If the plant must run continuously: Choose 'Update without utilization of new functions'.
Workflow for Zero-Downtime Maintenance (No Library Update):
- Install PCS 7 SP3 software on the Engineering Station.
- Open the existing project; do not update the Master Data Library blocks.
- Do not run 'Options -> Charts -> Update Block Types'.
- When compiling CFC, select Compile -> Scope: Changes only.
- In the download dialog, verify that Download -> Scope: Changes only is selectable.
Workflow for Full Upgrade (With Plant Outage):
- Copy updated APL and Basis Library blocks from SP3 into the Master Data Library.
- Run 'Update Block Types' across all S7 programs.
- Compile CFC with 'Generate module drivers' (Entire program).
- Put CPU into STOP mode -> download Entire program -> restart CPU in RUN.

Verification

To verify download feasibility:
1. In the CFC editor, click Chart -> Compile -> Charts as Program; select 'Changes only'. Verify compilation completes without forced full-compile warnings.
2. Click Target System -> Download; verify that the 'Changes only' radio button is enabled and not grayed out.
3. If 'Changes only' is grayed out, inspect the compilation log to identify which block interfaces changed.

Limitations and Operational Precautions

Operational precautions:
- Never force a block type update on a running production controller without verified downtime.
- For redundant S7-400H systems, certain minor library updates can be performed using the 'Update in RUN' (H-CiR / Redundant firmware update) procedure, but major Service Pack block modifications still carry risks of bumpless transition failure.
- Always back up the multiproject archive (.zip) prior to opening it on an upgraded ES.

Engineer FAQ

Can I download changes only after installing a PCS 7 Service Pack?

Only if you do not update the block types in your project library; updating block types forces an Entire program download in STOP mode.

Why is 'Changes only' grayed out after my compile?

Because a block interface (input, output, or static memory) was modified or added, altering the memory allocation of instance data blocks in the CPU.

What is the difference between an update with and without new functions?

'With new functions' updates all block algorithms and faceplates to the new SP release; 'without new functions' keeps older blocks to preserve online delta download capability.

Can redundant S7-400H controllers be upgraded without stopping the plant?

Yes, through the specialized 'Software Update in RUN' procedure, provided specific H-CiR rules are followed.

Does upgrading from SP1 to SP3 require new software licenses?

Service Packs within the same major release (e.g., V9.0 SP1 to SP3) are typically free updates covered under the existing major license.

Technical References

Related Tags

Delta Download
Service Pack Upgrade
CFC Compile
Update Block Types
CPU STOP

20 respuestas

Delta Download Feasibility After Upgrading PCS 7 from SP1 to SP3