Resolving Step 7 V5.5 Error 30:547 on S7-300 CPU315-2DP

1. Problem Overview

Engineers using SIMATIC STEP 7 V5.5 with an S7-300 CPU 315-2DP (typical MLFB 6ES7315-2AF03-0AB0, 6ES7315-2AH14-0AB0, or 6ES7315-2EH14-0AB0) frequently report a symptom cluster in which the initial project download succeeds, but any subsequent partial download of a modified FC, FB, or OB fails. The classic manifestation is:

• Full project download (PLC → Download User Program to Memory Card) works the first time.
• Subsequent edits to FCs/FBs/OBs cannot be selectively downloaded to the CPU.
• STEP 7 raises the dialog: "Monitor (30:547) – The offline block is different from the associated block on the CPU. The program can therefore not be monitored."
• The download icon in the FC/FB/OB tree is greyed out (inactive).
• Switching the project Type from PCS 7 back to STEP 7 revives download capability.

The error string is a STEP 7 internal diagnostic code (event ID 30:547) that ties to the Online/Offline Consistency Check of the S7-300/400 online interface. The same condition appears with CPU 312, 314, 315-2DP, 315-2 PN/DP, 317-2DP, 318-2DP, 319-3 PN/DP, and ET 200S IM 151-7 CPU when the offline block container, the system data, or the project framework has been re-organized in a way STEP 7's online monitor cannot reconcile.

2. Engineering Context: CPU 315-2DP and STEP 7 V5.5

Reference: Siemens S7-300 CPU 315-2DP operating instructions and the STEP 7 V5.5 SP5 programming and operating manual.

3. Root Cause Analysis

Event 30:547 is a STEP 7 online-monitor self-check failure, not a CPU fault. It occurs whenever the block container visible in the offline project cannot be paired one-to-one with the block container in the CPU's load memory. The most frequent triggers on CPU 315-2DP are:

1. Project type set to PCS 7. When the offline S7 project is created from a PCS 7 template (or its Object Properties → Type field is "PCS 7"), the block headers and the symbolic table carry PCS 7-specific extensions. The CPU's online interface compares the block signature and refuses the partial download, because the runtime will treat the blocks as belonging to a different control system class.
2. Offline/online timestamp or CRC drift. The S7-300 stores the time stamp, checksum (CRC), and author / family / name in the block header. If the offline block was edited in a different STEP 7 instance, copied from another station, or saved with a different CPU firmware revision, the CRC diverges and the monitor path throws 30:547.
3. CPU in RUN (not RUN-P) with key removed. RUN-P enables program changes from PG; RUN locks them out. On a partially-out-of-sync container, STEP 7 silently disables the download icon.
4. Load memory fragmentation. After several partial downloads and deletes, residual holes in MMC load memory prevent the new block image from being staged. Compress is required.
5. System data (SDB) inconsistency. Hardware configuration edited while online or pulled from an unrelated station. SDBs are the largest online objects and dominate the consistency check.
6. Know-how-protected or encrypted blocks (S7-Block Privacy, KM-attribute). Without the matching source the partial download is blocked.

4. Preconditions Before Changing Anything

• PG/PC interface set to PC Adapter (MPI) / CP5611 / CP5711 / IE-PG matching the cable. (See STEP 7 V5.5 manual, section "Setting the PG/PC Interface".)
• Project offline archive saved: File → Archive → User project.
• CPU firmware status read: Online → Accessible Nodes → Module Information → Diagnostic Buffer.
• MMC write-protect slider unchecked; spare MMC on hand (e.g. 6ES7953-8LF20-0AA0 4 MB).

5. Step-by-Step Resolution

5.1 Verify and correct the project type

1. In SIMATIC Manager, right-click the S7 Program (or the Station) → Object Properties.
2. Open the Type tab.
3. If it reads "PCS 7 Project" or "PCS 7 Vxx Library", change to "STEP 7 Project".
4. Click OK, close the project, and re-open it.
5. Compile the S7 program: Program → Compile All (Ctrl+F9).
6. Retry the FC/FB partial download. The download icon should now be active.

5.2 Set the CPU mode key correctly

1. Turn the key switch on the CPU 315-2DP door to RUN-P. The status LED shows "RUN" steady and "DC5V" on.
2. From the PG, Online → Accessible Nodes → [CPU315-2DP] and confirm the mode reads RUN-P.
3. If the CPU lacks a key switch (rare for the -2DP family) or the key has been removed, you must stop the process and use STOP.

5.3 Bring CPU to STOP and download

1. Select Online → Stop CPU (or move the key to STOP).
2. Confirm the dialog: "CPU changes to STOP — output of outputs deactivated".
3. Re-select the modified FC/FB/OB, right-click → Download (or click the toolbar download button).
4. Confirm "Do you want to load the block ... and overwrite the existing block?" with OK.
5. Switch back to RUN-P when the field is safe.

5.4 Compress CPU load memory

If the download still fails after the project type fix and the mode-key check, the load memory may be fragmented. Compression rebuilds a contiguous image and is the Siemens-blessed recovery path.

1. Online → Accessible Nodes → [CPU315-2DP] → Module Information.
2. Open the Memory tab.
3. Click Compress.
4. Confirm with OK. The CPU enters STOP briefly, compacts, then returns to its prior mode (RUN-P only if compress from RUN-P is permitted by the active project setting).
5. Re-attempt the partial download.

5.5 Re-align offline and online blocks

1. In SIMATIC Manager, open the Blocks container offline.
2. Switch to the online view: View → Online (or Online → Online View).
3. Compare the two containers block by block. Any block present online but missing offline is a "ghost" block; any offline block whose time stamp does not match online will show a small red marker.
4. For each mismatch: right-click the offline block → Delete and accept the prompt to remove it from the project, or right-click the online block → Upload to PG to pull the current CPU-side version into the offline project.
5. Recompile (Program → Compile All) and re-download.

5.6 Reset CPU and reload (last resort)

1. Turn key to STOP.
2. Hold key in MRES for ~3 s until the STOP LED blinks, release.
3. Within 3 s, turn the key back to MRES until STOP LED lights steady.
4. CPU is reset; all RAM and (if MMC absent) load memory cleared. On a 315-2DP an MMC remains; reset clears working memory only.
5. PLC → Download User Program to Memory Card (full project) to repopulate.
6. Verify with Monitor / Modify on a known tag.

6. Verification Checklist

7. Extended Diagnostics

7.1 Read the diagnostic buffer (event IDs)

Open CPU → Module Information → Diagnostic Buffer. Common events surrounding 30:547:

Full list: STEP 7 V5.5 Manual, Appendix A — Diagnostic Events.

7.2 Reference data and cross-reference

If 30:547 recurs after a sequence of edits, generate reference data and look for unresolved or multiply-assigned symbols.

1. Options → Reference Data → Generate.
2. Open Program Information → Cross References.
3. Search for any block flagged "Block is inconsistent / Block does not exist / Address used several times".
4. Re-instantiate the multi-instanced FBs from a single source FB; never paste FB headers across projects.

7.3 PC Adapter / cable sanity

Intermittent PG/PC interface faults can corrupt the partial download in flight and surface later as 30:547 on the next attempt.

• USB-to-MPI/PC Adapter (6ES7972-0CB20-0XA0): driver SIMATIC PC Adapter USB V2.0 (current build 2.x). Verify in Device Manager that the COM port enumerates.
• For TCP/IP routes, use the S7-300 Accessible Nodes only when the CP (e.g. CP343-1) is online and a valid IP is set; otherwise the CPU's online view may be served stale data from a previous session.
• Set the PG/PC interface first, then open the project — the wrong interface binding silently disables per-block download.

8. Cross-Platform Notes

9. Common Pitfalls

• Editing offline project while the CPU is online in RUN without RUN-P: edits look correct in the editor, but the download command is gated by the key position and silently drops.
• Mixing block versions across stations by copy/paste: the block CRC inherits the source CPU. Always regenerate source blocks from the original STEP 7 source, not the binary copy.
• Long block names (> 8 chars in family/author fields) on legacy 6ES7315-2AF03/AF04 may trigger inconsistency with newer PG tools; trim to 8 chars and reset timestamp via recompile.
• MMC write protection: SIMATIC MMC has a yellow slider; leaving it in the "protected" position blocks every download.
• Out-of-date GSD files for PROFIBUS slaves: the SDB generated for the DP master may differ from what is loaded in the CPU, surfacing as 30:547 on the SDB container.
• Reinstalling STEP 7 over a non-English MUI: project type defaults to PCS 7 if a PCS 7 option pack was once installed; reverting does not always strip the project type until the manual fix in § 5.1.

10. When to Migrate to TIA Portal

STEP 7 V5.5 reached end of lifecycle in 2020; SIMATIC Manager and the classic S7-300 CPUs remain supported but no new patches are issued. If 30:547 keeps reappearing after compression and full re-download, the path of least resistance is migration:

1. Use the TIA Portal migration tool: Project → Migrate project → STEP 7 V5.x.
2. Re-compile the S7-300 program for the new target (CPU 315-2DP → CPU 315-2 PN/DP, MLFB 6ES7315-2EH14-0AB0, or S7-1500 ET 200S equivalent).
3. Validate the program with the S7-PLCSIM in TIA before live cutover.

Reference: STEP 7 V5.5 manual archive and SIMATIC S7-300 to TIA Portal migration guide.

11. Safety and Operational Notes

12. Quick Reference Matrix

13. Frequently Asked Questions