Resolving CFC Online-Offline Checksum Mismatches and Avoiding Full CPU Downloads in PCS 7

When retrieving an earlier project backup without modifying any CFC charts causes PCS 7 to report an online/offline timestamp mismatch and demand a full CPU download, the discrepancy is caused by internal database timestamp differences between the retrieved offline database and the online CPU work memory. In SIMATIC PCS 7, opening and saving Variable Tables (VAT), symbol tables, or Hardware Configuration updates the S7 Program timestamp, which invalidates online synchronization. To resolve this without an uncommanded CPU stop: 1. Perform an offline/online block comparison ('PLC -> Compare Blocks') to verify that actual block logic is identical; 2. Execute 'Chart -> Compile -> Changes only'; and 3. Perform a delta download ('Changes only') in RUN mode, which realigns the interface timestamps without stopping the controller.

Executive Summary

Maintaining strict synchronization between offline engineering archives and running automation controllers is paramount in SIMATIC PCS 7. A frequent and alarming operational dilemma arises when an engineer retrieves a verified project backup (e.g. from the previous week) to monitor a live production plant. Even though no functional modifications were made to the technological CFC charts, attempting to engage online test mode ('Glasses' icon) fails with a blocking prompt stating that the offline charts do not match the online program, demanding a complete download. Because an Entire Download forces the CPU into STOP, shutting down an active plant is unacceptable. This article analyzes the internal checksum and timestamp hierarchy of PCS 7, identifies the innocuous actions that trigger false mismatches, and outlines safe procedures to restore online monitoring.

Architecture and Fundamental Mechanics

S7-400 Block Checksum Hierarchy, Compilation Timestamps, and Delta Download Mechanics:

The Multi-Tier Timestamp and Checksum Model in PCS 7:
Every compiled block in an S7-400 CPU possesses two critical timestamps:
1. Code Time Stamp: Records when the executable machine code within the block was compiled.
2. Interface Time Stamp: Records when the block's input, output, or static interface was compiled.
In addition, the CFC chart container maintains a global Compilation Time Stamp and a unique cryptographic Download Checksum.
When an engineer clicks 'Test Mode' (Ctrl+F), the CFC editor queries the running CPU to verify that the offline chart checksum matches the CPU load memory checksum.
Why an Unchanged Retrieved Backup Triggers a Mismatch:
Scenario A: Download Occurred After Backup: If another engineer (or shift) executed even a minor delta download after the backup was created, the online CPU's internal download counter is ahead of the retrieved project, triggering an immediate mismatch.
Scenario B: Innocuous Offline Touch: Opening a Variable Table (VAT) and clicking Save, modifying comments in the Symbol Table, or executing 'Check Block Consistency' alters the offline S7 Program metadata timestamps, creating a divergence with the online CPU.
Scenario C: Master Data Library / CMT Synchronization: If Control Module Types (CMT) were synchronized, background instance attributes can be touched, updating chart revision headers.
How Delta Download Realigns Timestamps Without Stopping the CPU:
In SIMATIC PCS 7, the CFC compiler features sophisticated delta compilation: Chart -> Compile -> Changes only.
If the compiler detects that the underlying algorithms, DB structures, and technological logic have not changed, it generates a minimal delta package.
Performing PLC -> Download -> Changes only in RUN mode downloads the reconciled timestamp headers into the CPU work memory. The CPU remains 100% in RUN, process outputs are uninterrupted, and online CFC monitoring is instantly re-enabled.

Step-by-Step Implementation Procedure

Perform an Offline/Online Block Comparison in SIMATIC Manager:
* In SIMATIC Manager, select the Blocks folder under the S7 Program.
* Select PLC -> Compare Blocks....
* Choose to compare Offline blocks against Online blocks.
* Review the comparison result:
- If the result reports 'Only interface timestamps differ' or 'Only Code Timestamps differ' for a few coordination blocks, the core technological logic is identical.
- If major algorithmic blocks show logic discrepancies, the retrieved backup is NOT the active running version.
Attempt a Delta Compilation in CFC:
* Open any CFC chart in the project.
* Select Chart -> Compile -> Chart as Program....
* Select Changes only.
* Check Generate module drivers.
* Click OK.
* If the compiler completes with 0 errors and indicates delta compilation is possible, proceed to delta download.
Execute a Safe Delta Download in RUN Mode:
* In the CFC editor, select PLC -> Download....
* In the download scope dialog, select Changes only.
* Verify that the controller operating mode displays RUN.
* Confirm the download; STEP 7 transfers the updated block headers and timestamps into CPU memory without stopping the controller.
Fallback if Delta Download is Blocked:
* If PCS 7 reports that changes can only be loaded in STOP mode (because DB structures were shifted):
* DO NOT proceed with a download.
* Revert to finding the true latest engineering archive, or perform an upload from the running CPU into a separate temporary project to inspect the exact online state before planning a maintenance turnaround.

Verification

Following the successful delta download, open the target CFC chart.
Press Ctrl + F to engage Test Mode ('Glasses' icon).
Verify that online monitoring engages cleanly with green status frames and live process values.
Verify that the controller remained in RUN throughout the operation and no process disturbances occurred.

Limitations and Operational Precautions

Never attempt an 'Entire Program' download on a live production plant to resolve a timestamp mismatch, as full downloads force an immediate CPU STOP. If structural DB parameter offsets were altered between the backup and the running CPU, delta downloading is prohibited by the compiler to prevent memory overwrites; in such cases, only the matching archive can restore online monitoring.

Engineer FAQ

Why does CFC report an online/offline mismatch on an unmodified backup?

Because the backup was archived before the latest online download occurred, or minor actions (saving a VAT, editing symbols) altered offline timestamps.