PCS 7 v7.0 SP3 OS Delta Download: Root Cause and Recovery

1. Problem Statement: OS Delta Download Suddenly Disabled

In a Siemens PCS 7 v7.0 SP3 plant with one OS Server, one OS Client, and one ES/OS client, an engineer adds the S7_m_c attribute to selected data blocks (DBs), creates a CFC, performs a full download of the AS program, executes an OS "Compile Changes" (Delta compile), edits one process picture in the Graphics Designer, and then discovers that the Download Changes to OS option is no longer available. The only offered alternative is a complete OS download, which requires leaving Runtime and would interrupt the running plant.

This is a recurring pain point on PCS 7 v7.0 SP3 ES/OS stations. The OS project silently invalidates its delta-loaded runtime database, and the engineer is forced to schedule a maintenance window for a full OS download that destroys the online tag database, archive configuration, and user administration.

2. Environment and Configuration Baseline

The following baseline is assumed for every diagnostic step in this article:

The OS Runtime database on the server contains structure tag instances that mirror every AS instance DB. When the engineer changes the definition of a type (or of an instance), the OS structure tag definition diverges from what the server is holding in memory, and PCS 7 marks the project as "full download required."

3. Root Cause Analysis

Two distinct, additive root causes trigger Delta Download loss in PCS 7 v7.0 SP3. Both must be checked during diagnosis.

3.1 Instance DB Attribute Modification (Fatal)

Each PCS 7 block type (e.g., MOT_SPEED, VALVE_ANA, PID_FB) defines a set of attributes on its instance DB. The OS project creates a corresponding structure tag per instance during the first full download. When an engineer changes attributes of an instance DB directly (not just shared DBs), the structure tag definition on the OS server no longer matches the AS image. PCS 7 invalidates the delta loader because recreating the tag without a full download is impossible without losing runtime data consistency.

3.2 Picture Tree Manager "Delta Save" Setting

In Graphics Designer > Tools > Picture Tree Manager > Options, the engineer must confirm two settings:

• Recalculate the group display hierarchy completely while saving — must be ENABLED if group display updates are required.
• Delta Save — must be ENABLED to allow OS online Delta Loading.

If Delta Save is disabled and full hierarchy recalculation is enabled, the OS project is saved in a form that does not support online delta loading. The Download Changes button is greyed out.

3.3 SIMATIC Shell Network Binding

If the ES cannot see the OS server's project path through the SIMATIC Shell, the ES reports that no changes can be transferred because the terminal-bus network card binding is wrong. The OS project appears "unreachable" and the engineer is incorrectly steered toward a full download.

4. Operations That Invalidate Delta Download on PCS 7 v7.0 SP3

The following OS engineering operations are known to force a full OS download (Delta Download will be unavailable afterwards):

The official Siemens knowledge base article — Which messages may appear in the "Download OS" dialog box? — enumerates the error strings that may be displayed when the WinCC application type is misconfigured. The most common text is:

The configured type of WinCC application in the PC station does not support downloading changes. Downloading changes is only possible for WinCC [OS Server / OS Client / OS Single Station].

When this string is present in the Download OS dialog, the PC station's WinCC application slot in SIMATIC Manager > PC Station > Configuration is the first place to inspect.

5. Diagnostic Workflow

Run the following checklist in order. Each step eliminates one possible cause:

1. Open WinCC Explorer on the ES and select OS Project Editor > Compile OS. Note whether the resulting log contains the string "No changes", "Changes were detected", or "A full download is required".
2. Inspect the AS cross-reference in SIMATIC Manager: Options > Cross References > Display. Verify that the modified DB is an instance DB (type > 0) and not a shared DB.
3. Open Picture Tree Manager > Options. Confirm Delta Save = ON and Recalculate group display hierarchy completely = ON.
4. Check SIMATIC Shell: in Windows Explorer, navigate to SIMATIC Shell, right-click the ES node, choose Object Properties > Settings, and ensure the terminal bus network card is highlighted. Click OK to re-bind.
5. Verify the WinCC application type in PC Station configuration: must be OS Server, OS Client, or OS Single Station. Anything else (e.g., WinCC Runtime, WinCC Standby) blocks delta download per the Siemens support article referenced above.
6. Confirm Runtime state on the ES: if OS Runtime was activated on the ES, the OS project is locked and delta download to the server is blocked. See Siemens Industry Online Support for the OS-RT-on-ES FAQ.

6. Recovery Without Full Download

If the diagnostic confirms the Delta Save option was disabled (root cause 3.2), the project can be recovered in minutes without a runtime shutdown:

1. In Graphics Designer on the ES, open Tools > Picture Tree Manager > Options.
2. Enable Delta Save.
3. Re-save the affected picture (File > Save).
4. Re-run OS Project Editor > Compile OS > Scope: Entire OS.
5. Verify in the log that "Online Delta Loading possible: Yes" appears.
6. Trigger Download Changes to OS from SIMATIC Manager.

If the root cause is the instance DB attribute modification (3.1), the only true recovery without a runtime shutdown is to revert the attribute on the AS, re-compile the AS program, and re-download to the AS. The OS side has not actually changed in memory, so the OS Runtime continues unaffected. Re-trigger an OS delta compile afterwards.

7. SIMATIC Shell Reconfiguration Procedure

If the ES cannot see the OS Server project path through SIMATIC Shell:

1. On the ES, open Windows Explorer.
2. Navigate to SIMATIC Shell (typically under My Computer or Desktop).
3. Right-click the ES node and choose Object Properties.
4. Open the Settings tab.
5. Select the network card used for the terminal bus (not the plant bus card).
6. Click OK to save and re-bind the terminal bus path.
7. Refresh the SIMATIC Shell view. The OS Server project folder should now be visible.

8. Preventive Engineering Practices

To minimize the probability of Delta Download loss during the project lifecycle:

• Centralize attribute changes. Modify block type attributes only in the master data library and propagate through CFC chart I/O where possible. Avoid touching attributes directly on instance DBs.
• Archive before changes. Before any OS-side edit, perform OS Project Editor > Archive. While not officially documented as restoring delta download, experienced PCS 7 engineers report that a recent archive improves delta save consistency.
• Lock Picture Tree Manager options. Use a project-wide configuration file to enforce Delta Save = ON. Document the option page in the project quality plan.
• Never run OS Runtime on the ES in a production project. Use OS Simulation mode for picture testing.
• Test on a stub OS first. Maintain a single-station test OS that mirrors the production OS Server configuration. Validate every AS attribute change against the stub OS before applying to the live server.
• Disable "Recalculate group display hierarchy completely" in routine picture edits. Only enable it for bulk plant-area restructurings.

9. Verification Checklist

After applying the corrective action, confirm each item:

10. Troubleshooting Matrix

11. Field-Proven Caveats

• Even when the engineer follows every preventive practice, PCS 7 v7.0 SP3 occasionally requires a full OS download after a CFC chart insert/delete cycle. This is not a defect — the AS image changes sufficiently that the OS structure tag set must be regenerated.
• On a redundant OS Server pair, the failure of one server's delta download does not affect the other. Plan the corrective edit on the standby server, fail over, and apply to the previously active server.
• On a single-OS-server plant, schedule at least one engineering maintenance window per quarter where a full OS download is permitted. Use this window to absorb any "Delta Download no longer possible" condition rather than tolerating a permanently degraded configuration.
• Do not promote a project from PCS 7 v7.0 SP3 to a newer PCS 7 release (e.g., V8.0 / V9.0) without re-baselining the block type library. Migration preserves the structure tag set, but new block attributes in the target version will force a one-time full OS download.

12. FAQ