Preventing Uncommanded AS STOP Download Requirements After Project Restoration in PCS 7

In SIMATIC PCS 7, an AS 410-5H controller unexpectedly requiring a full download in STOP after restoring an archived project is caused by timestamp and DB allocation desynchronization between offline charts and online controller memory. Even if no logic changes were intended, actions such as performing an AS Read Back followed by compilation, modifying symbol tables, or opening and saving hardware configurations alter internal offline compile timestamps and DB allocations. To recover online synchronization and download 'Changes only' without stopping the CPU, retrieve the exact verified archive created immediately after the last successful download, avoid compiling after read-back unless downloading changes, and ensure the offline project database has not undergone destructive block renumbering.

Executive Summary

In critical continuous operating facilities, an uncommanded requirement for an AS STOP download is a severe operational hazard. Automation engineers frequently encounter a dilemma: after restoring an uncorrupted project archive to perform routine offline review or minor tag modifications, SIMATIC Manager indicates that 'Changes only' download is disabled, forcing an AS STOP download. This condition occurs even when the engineer believes no functional changes were made. This technical article analyzes the exact timestamp, database consistency, and online/offline signature mechanics that govern PCS 7 download behavior and provides the mandatory operational workflows to maintain uninterrupted online RUN downloads.

Architecture and Fundamental Mechanics

The PCS 7 CFC and S7-400/CPU 410 download management system evaluates multiple structural signatures to determine whether an AS can accept delta changes in RUN:
1. Online/Offline Timestamp Signatures:
- When CFC charts are compiled, the compiler stamps the generated machine code and data blocks with an internal unique compilation timestamp (CompTime).
- During a download, this timestamp is written to the controller's system memory. When an engineer initiates 'Download Changes', the compiler compares the offline CompTime with the online CompTime.
2. The Read-Back / Compile Pitfall:
- Step 2 in common archive workflows involves 'AS Read Back' to capture operator control parameters (OCM values) from online DBs.
- If the engineer executes Compile Charts after the read-back, the compiler assigns a new compilation timestamp to the offline project.
- If this recompiled project is archived and then some offline modifications or test compiles are conducted, the link between the offline project and online CPU is severed. Restoring that archive without downloading immediately leaves the project out of sync.
3. Data Block (DB) Allocation and Renumbering:
- CFC dynamically assigns DB numbers to block instances. If an engineer opens the project offline and creates, moves, or deletes a block (or if project reorganization runs), the compiler may shift instance DB numbers.
- Once an instance DB number changes for an existing technological block, the CPU 410 refuses 'Changes only' and mandates a STOP download to prevent data corruption.
4. CPU 410-5H Type Change in RUN (TCiR) Limits:
- CPU 410-5H supports TCiR for library block interface modifications, but TCiR cannot reconcile mismatched project archives where block structures have diverged.

Step-by-Step Implementation Procedure

Establish Strict Project Archiving Governance:
a. Prior to any offline work, connect online to the controller: verify that 'Download -> Changes only' is enabled.
b. Execute Charts -> Read Back... to retrieve operator setpoints and tuning parameters.
c. Do not recompile charts after Read Back unless you immediately download those changes to the AS.
d. Immediately archive the multiproject (File -> Archive) and label it Plant_PROD_ExactOnline_<Date>. This is the reference production master.
Isolate Offline Sandbox Environments:
a. When offline testing or training is required, retrieve the archive to a dedicated test directory.
b. Never connect the offline test project to the production plant bus.
c. Do not perform block renumbering, symbol reorganization, or library block type imports in the master production project without a planned outage.
Diagnose Root Cause of Disabled 'Changes Only' Download:
a. In SIMATIC Manager, select the AS station.
b. Open CFC and select PLC -> Module Information -> Performance Data to inspect memory allocations.
c. Select Target System -> Compare Blocks: compare offline S7 program blocks with online CPU blocks.
d. Identify whether differences reside in timestamps alone or if instance DB numbers (DB 1000+) have shifted.
Recovering Synchronization Without Controller STOP:
a. If the project diverged due to accidental offline compilation or reorganization, delete the diverged project folder.
b. Retrieve the verified Plant_PROD_ExactOnline_<Date> production master archive.
c. Open CFC, connect online, and verify online monitoring works.
d. Execute a test compilation with 'Scope: Changes only'.
e. Attempt 'Target System -> Download -> Changes only': confirm the CPU accepts the delta download in RUN.
Managing Legitimate Logic Updates Safely:
a. Make required logic modifications directly in the synchronized production project.
b. Execute Chart -> Compile -> Changes only.
c. Execute PLC -> Download -> Changes only in RUN mode.

Verification

In CFC, open PLC -> Download: verify that the radio button 'Changes only' is active and selectable.
Execute 'Changes only' download: confirm the dialog displays 'The target system is in RUN mode. Do you want to continue?' and completes without forcing STOP.
Verify in Module Information that the AS remains in RUN mode throughout the download sequence.

Limitations and Operational Precautions

If block interface structures (inputs/outputs on existing FBs) were modified without utilizing Type Change in RUN (TCiR) rules, or if maximum DB numbers were exceeded, an AS STOP download is mathematically unavoidable.

Engineer FAQ

Why does compiling charts after an AS Read Back cause download issues?

Compiling creates a brand-new internal timestamp. If those recompiled charts are not immediately downloaded to the AS, the offline project diverges from the online CPU state.

What causes the 'Changes only' download option to be grayed out?

It is grayed out when the compiler detects that internal instance DB allocations have shifted, block numbers were reassigned, or the chart database was cleared.