Recovering from 'Connection Aborted DB61 Not Downloaded' and Restoring Delta Downloads in PCS 7

A download failure in SIMATIC PCS 7 reporting that the connection to the CPU was aborted (e.g., 'DB61 not downloaded') occurs when physical communication breaks or buffer timeouts occur while transferring compiled blocks to the controller. Once a block transfer is interrupted, the compiler invalidates the controller's consistency footprint, graying out the 'Changes only' download option and demanding a complete download. To recover without an unscheduled plant shutdown, engineers must evaluate whether an archived project backup matches the controller's online memory signature or execute targeted block downloads before committing to a full STOP download.

Root Causes of Interrupted AS Downloads

During a Continuous Function Chart (CFC) program download (PLC -> Download -> Changes only), the Engineering Station (ES) transfers modified S7 blocks (data blocks, function blocks, organization blocks) sequentially over the Industrial Ethernet plant bus. If communication drops during transmission, the download aborts with an explicit error:

The connection to the CPU was aborted. DB61 not downloaded.

The underlying causes of mid-download communication loss include:

Physical Cable or Switch Dropout: A loose RJ45 connector, damaged patch lead, or industrial switch port reset during block transmission.
CPU Communication Buffer Saturation: If the controller's reserved PG communication resources are exhausted by concurrent SIMATIC PDM sessions, WinCC OS servers, or multiple engineering stations, the CPU's S7 communication stack times out.
CP 443-1 Backplane Overload: High cyclic I/O traffic across a communication processor (CP 443-1) causing packet dropping during heavy block writes.
Target Data Block Memory Collision: Attempting to download a dynamic instance data block (DB61) whose structure expanded beyond available contiguous controller work memory.

Why Delta Download ('Changes Only') Becomes Grayed Out

Following an interrupted download, attempting a second download reveals that Download Changes is disabled (grayed out), leaving only Entire program selectable:

The Consistency Footprint: PCS 7 embeds a cryptographic timestamp and consistency checksum between the offline CFC database and the online controller memory.
The Broken Transaction: The controller received part of the compiled blocks (e.g., DB1 through DB60), but failed on DB61. The controller's online program is now in an inconsistent, split state where some blocks expect new memory offsets while others run old structures.
Compiler Safety Interlock: To prevent erratic controller execution, memory corruption, or plant safety trips, the PCS 7 compiler disables delta downloading whenever the online state does not match the known offline compile signature.

Step-by-Step Recovery and Consistency Restoration

When the plant is actively running and an AS STOP is prohibited, follow this recovery methodology:

Step 1: Re-Establish Communication and Inspect Diagnostics

Verify physical Ethernet cabling and switch port link LEDs.
In SIMATIC Manager, select the CPU and press Ctrl + D to open Module Information.
Inspect the Diagnostic Buffer:
* Look for events timestamped with the download abort (e.g., Communication error, Connection terminated by partner, or Memory bottleneck).
* Confirm that the CPU remains in RUN mode.

Step 2: Compare Online and Offline Block Checksums

In SIMATIC Manager, select the Blocks folder of the affected AS project.
Select Options -> Compare Blocks....
Compare the Offline Block Folder against the Online CPU.
Identify which specific blocks differ:
* If only a few data blocks (like DB61) are missing or mismatched, the controller's core runtime logic may still be executing safely.

Step 3: Utilize a Pre-Change Project Backup

If you created a project archive (File -> Archive) immediately prior to modifying CFC connections:
* Retrieve the backup to a temporary folder (File -> Retrieve).
* Open the retrieved project in SIMATIC Manager.
* Check if the retrieved project's compile timestamp matches the online CPU state.
* If the timestamps align, you can re-establish delta download synchronization from the backup.

Step 4: Targeted S7 Block Download (Advanced Workaround)

If the aborted block was a standard data block or non-structural instance:
* Open the offline Blocks folder in SIMATIC Manager.
* Select the specific block cited in the error (DB61).
* Select PLC -> Download to manually transfer the single missing block to the CPU.
* If successful, open CFC, compile changes, and test whether the delta download option is re-enabled.

Evaluating S7 Block Checksums and Online/Offline Comparisons

When comparing blocks, pay close attention to structural signatures:

If the offline compilation modified block interfaces (adding pins to function blocks), the instance data blocks change size. Downloading mismatched DBs manually can cause the CPU to call OB121 (Programming Error) or OB122 (I/O Access Error).
Ensure error organization blocks (OB80, OB82, OB85, OB86, OB121, OB122) are present in the CPU to prevent unexpected transitions to STOP.

Verification

Confirm system recovery and download capabilities:

Delta Download Availability Check:
* Open the CFC editor.
* Select PLC -> Download.
* Confirm whether Changes only is selectable (not grayed out).
Diagnostic Buffer Health Check:
* In STEP 7, verify that the CPU diagnostic buffer contains zero active communication errors or unbuffered peripheral access faults.
Live Chart Status:
* Switch CFC to Test Mode; confirm that dynamic monitoring functions normally across modified charts.

Limitations and Operational Precautions

Complete Download May Require AS STOP: If the compiler strictly enforces a full download ("Entire program"), downloading to a single-station CPU will require transitioning the CPU to STOP, halting the plant process. Schedule this during an approved maintenance window.
Redundant System Advantage: In a fault-tolerant AS 410-5H Redundant system, an interrupted download can be recovered by failing over between subsystems and downloading changes sequentially without stopping the process.
Always Archive Before Downloading: Always execute a quick project archive or backup before initiating online delta downloads on operational plants.

Engineer FAQ

What causes the error 'The connection to the CPU was aborted. DB61 not downloaded'?
An unexpected communication drop, network cable fault, communication buffer saturation, or CPU timeout interrupted the transfer of compiled blocks.
Why is 'Download Changes' grayed out after an aborted download?
The compiler detected that the online CPU program was left in an inconsistent state, requiring a full download to restore database integrity.
Can I restore delta download capability without stopping the PLC?
If you have a backup made immediately before the change, you may be able to re-align compile timestamps, or manually download the single missing DB.
What happens to the running plant when a download aborts halfway?
The CPU continues running the blocks already in memory; if a modified block calls a missing DB, the CPU executes error OBs (like OB121) or drops to STOP if OBs are missing.
Does S7-400 require an overall reset (MRES) after an aborted download?
No, an MRES is not required unless the CPU work memory is completely fragmented or locked by corrupted system data blocks.
Which organization block prevents CPU STOP during a missing DB call?
OB121 (Programming Error Organization Block) intercepts missing DB or range errors, preventing the CPU from stopping.
Can I cancel an ongoing CFC download safely?
Canceling a download mid-transfer almost always results in an inconsistent online program and disables subsequent delta downloads.
How do I check if my offline project matches the online CPU?
Use the 'Options -> Compare Blocks' utility in SIMATIC Manager to execute an offline/online block comparison.
Does this problem occur on redundant AS 410-5H systems?
Redundant systems are far more resilient; if a download fails, changes can be rolled back to the partner CPU without stopping the plant.
What is stored inside DB61?
DB61 is typically an instance data block generated automatically by the CFC compiler for a specific function block (e.g., valve, motor, or interlock).

Technical References

Siemens Industry Online Support (SIOS) Portal: Why is it no longer possible to download changes to the target system in PCS 7? (Entry ID: 22258957).
SIMATIC CFC for S7 / PCS 7 Manual - Compiling and Downloading Programs, Siemens AG.
SIMATIC S7-400 CPU Diagnostic and Fault Handling Guide, Siemens AG.

Related Tags

PCS 7, CFC, Download Error, Delta Download, DB61, S7-400, Consistency Check, Troubleshooting

Recovering from 'Connection Aborted DB61 Not Downloaded' and Restoring Delta Downloads in PCS 7