Resolving S7-300 Backup Empty Program Blocks in STEP 7 V5.x

1. Problem Statement

An S7-300 backup archive (typically a *.s7p project, or a compressed *.zip / *.arj wrapper of a STEP 7 V5.x project) is opened in SIMATIC Manager and the project tree displays the Hardware and NetPro / Network sub-objects, but the S7 Program > Blocks container is empty. No OB1, no FCs, no FBs, no DBs are listed, even though the CPU type is correctly identified (e.g. CPU 315-2 PN/DP, 6ES7 315-2EH14-0AB0).

This is one of the most common support cases on the Siemens Industry Online Support portal for the SIMATIC S7-300 family (see the documented thread at S7-300 backup blocks not showing - SiePortal). The root cause is almost never a single fault; it is one of a known set of conditions that must be ruled out in sequence before the project is declared unrecoverable.

2. Common Symptoms

Across the documented support cases the symptom set is consistent:

• SIMATIC Manager opens the *.s7p file without errors.
• Project > Station > Hardware shows the configured rack, CPU order number, and signal modules.
• Project > Station > CPU > S7 Program > Blocks opens, but the right-hand detail pane is blank.
• No warning dialog at project-open time — or a dialog reporting "missing software components" is dismissed before being read in full.
• Selecting Options > Block Consistency Check returns "No blocks found" within a few seconds.
• If the user attempts PLC > Download or PLC > Upload to PG, the online/offline mismatch immediately overwrites the empty offline tree with the online content of the connected CPU (or fails if the CPU is password-protected).

3. Root Cause Categories

Five conditions account for almost every reported case. They are listed in descending order of frequency in the SiePortal thread and in Siemens' own backup documentation (Backup options for S7 CPUs - TIA documentation).

4. Diagnostic Workflow

Follow this sequence before changing any tool installation. Each step is non-destructive.

1. Confirm the file is a SIMATIC Manager archive and not a TIA Portal export. Right-click the file → Properties. A valid V5.x backup is a *.s7p file that internally points to a *.zip or *.arj container. A TIA Portal export produces *.zap17 / *.zap20 and cannot be opened in SIMATIC Manager.
2. Re-open the project and read every dialog completely. STEP 7 reports the missing block-type FBs / DBs by name. Write down each FB/DB number — these identify the optional package you must install (see Section 5).
3. Open the project folder on disk with Windows Explorer (default: %USERPROFILE%\Documents\Siemens\Automation\<ProjectName>\ after the Retrieve operation). Check that the S7PROG\BLOCKS subfolder physically exists and contains *.AWL / *.SCL files. If only SystemData.s7p is present, the archive is incomplete (Cause #4).
4. Check the CPU order number by double-clicking Hardware → HW Config. If the order number contains an F in the firmware position (e.g. 6ES7 3xx-xxxF-xAB0), F-block handling applies (Cause #2).
5. Try a direct online upload if a PG is available. Connect via MPI / PROFIBUS (PC Adapter USB A2, 6GK1 571-1AA00) or PROFINET (TCP/IP, port 102) and execute PLC > Upload Station to PG. The online view of Online > Accessible Nodes will display the actual block list, even when the offline tree is empty.

5. Solution Path 1 — Missing Software Packages

This is the most common cause and the one that matches the original report directly (the user reported WinCC missing initially; STEP 7 raises the same dialog for library FBs).

STEP 7 V5.x ships with a number of optional software packages. Each is referenced by a block type and by the corresponding library *.s7l / *.s7s source. If the package is not installed, SIMATIC Manager displays the offending blocks in the open-time dialog and then omits them from the offline tree, so the Blocks container appears empty even though the .AWL files exist on disk.

Procedure:

1. Note the block numbers from the open-time warning dialog.
2. Start the STEP 7 V5.5 Setup in Modify mode (Start > SIMATIC > STEP 7 > Setup > Modify / Upgrade).
3. Enable the matching optional package; if the source media is missing, contact Siemens support with the order number of the block (e.g. "FB 242 is referenced; we need the Modbus Master library V3.2").
4. Reboot, then re-open the project. The Blocks container should populate immediately. The originally missing FB/DB symbols are now resolved through the installed library.

6. Solution Path 2 — F-Blocks and Distributed Safety

The thread title in the source contains the typo "fblocks". If this is not a typo — i.e. the project targets an S7-300 F-CPU (e.g. 6ES7 315-6FF01-0AB0, 6ES7 317-6FF00-0AB0, 6ES7 318-6FF00-0AB0, or any CPU of the S7-300F family) — then the program contains F-runtime groups, F-FBs, and F-DBs that cannot be uploaded to a PG. Siemens documents this behaviour explicitly: F-block code is generated by the Distributed Safety or F-Configuration Pack F-Compiler and is intentionally non-extractable.

Procedure:

1. Install SIMATIC S7 Distributed Safety V5.4 SPx (catalog: 6ES7 833-1FC02-0YA5) on top of STEP 7 V5.5 SPx. Re-run Setup in Modify mode and add the option.
2. Open the project in SIMATIC Manager. The Safety Administration editor will appear under CPU > S7 Program alongside the standard Blocks folder.
3. F-blocks are present but appear under a dedicated F-runtime group; standard OB 35 (or other cyclic OB) calls the F-CALL block that drives the F-runtime group. The empty Blocks folder in the standard tree is normal for F-CPU projects.
4. If Distributed Safety is not installed, you will not be able to view or modify the F-program — and you should not be able to do so per Siemens' safety integrity policy. The original F-source must be supplied by the OEM (Cause #4).

7. Solution Path 3 — Know-How Protection

STEP 7 V5.x supports S7-Block Privacy (formerly Know-how protection) at block level. When enabled, the block compiles to bytecode in the offline *.AWL file but the source is encrypted. Opening such a project in SIMATIC Manager shows the block icon with a small padlock overlay; if all blocks in the Blocks folder are know-how protected and the password is not supplied, the entire container can appear empty depending on the SIMATIC Manager service pack and view filter.

Diagnostic / recovery procedure:

1. Open the project and switch to the Details view of the Blocks folder (right-click → View > Details). If a list of FBxxx / DBxxx entries appears with a padlock column, know-how protection is active.
2. Open each block → the editor prompts "Block has know-how protection. Enter password:". Enter the password supplied by the OEM.
3. If the password is not known, no standard tool can decrypt the block. The only legitimate path is to obtain the original S7-Project source from the machine supplier (Cause #4).
4. If a live CPU is available, a know-how-protected block can be uploaded in executed form using PLC > Upload to PG, but only the block interface and runtime instance DBs arrive — the STL / SCL source is not recovered.

8. Solution Path 4 — Incomplete OEM Archive

The most likely cause in the original report is that the machine installer supplied a partial backup. STEP 7 V5.x lets an OEM export only the Hardware + NetPro + System Data subset by selecting only those nodes before File > Archive. The result is a project that opens cleanly, displays the rack and PROFIBUS / PROFINET topology, and contains no program.

Verification:

1. Open Windows Explorer at the extracted project root.
2. Confirm the presence of the directory \S7PROG\BLOCKS\. A complete project contains files such as OB1.AWL, FC1.AWL, DB1.AWL, plus SYMBOLS.SEQ and the SystemData.s7p shortcut.
3. If \S7PROG\BLOCKS\ is missing or contains only SystemData.s7p, the archive is incomplete.

Recovery options:

1. Request a re-export from the OEM. Ask for File > Archive > User-defined scope > Entire project with the "With S7-Program" option ticked. The resulting *.s7p file is typically 2-10 MB for a mid-size S7-300 application.
2. If a live CPU is available, perform a PLC > Upload Station to PG directly. This is the only way to recover the program when the supplier cannot be reached (see Section 9).
3. As a last resort, check the MMC (Micro Memory Card) that ships with the CPU. The card itself contains a SIMATIC.MMC image with the entire program; reading it with a Siemens field PG (or a third-party MMC programmer supporting the SIMATIC.MMC FAT-16 partition) gives you the original offline tree.

9. Solution Path 5 — Direct Upload from CPU 315-2 PN/DP

If the physical CPU is accessible, an online upload is the fastest path to a complete program. The CPU 315-2 PN/DP (6ES7 315-2EH14-0AB0) supports both PROFINET and PROFIBUS / MPI for PG communication.

Procedure:

1. Open SIMATIC Manager, choose PLC > Upload Station to PG.
2. In the Select Node Address dialog, browse to the target CPU over the chosen interface.
3. Confirm the upload. The complete offline tree is rebuilt, including all FBs / FCs / DBs / OBs / SDBs that are not know-how-protected and not F-blocks.
4. After upload, open Options > Block Consistency Check to confirm that all interface calls resolve.

If the CPU prompts for a password, the program is either:

• CPU password protected (set in HW Config → CPU properties → Protection). Contact the OEM for the password or perform a CPU memory reset to clear it (this also erases the program — only acceptable when the backup is the source of truth).
• Know-how protected at block level (see Section 7).

10. Verification Procedure

After applying any of the solutions above, validate the project as follows:

1. Open SIMATIC Manager and re-load the project. The Blocks folder must list at least OB 1, OB 100 (warm restart), and any FC/FB/DB referenced in the documentation.
2. Double-click OB 1. The editor (STL / LAD / FBD) must open without the "Block has no source / object" error.
3. Run Options > Block Consistency Check. All blocks should report OK. A count of Errors: 0, Warnings: 0 is the expected result.
4. Compile the hardware (Station > Save and Compile) and confirm the System Data matches the expected rack layout.
5. If the CPU is available, compare online vs. offline via PLC > Compare. A consistent result confirms the recovered program is the running one.

11. Preventive Measures

To prevent recurrence:

• Always request two copies of the project backup from the OEM: the offline archive (*.s7p) and a complete read-out of the CPU's MMC image.
• Ask the OEM to document the STEP 7 version and optional packages used to compile the project. Keep a copy of the same install media in a versioned archive (e.g. STEP 7 V5.5 SP4 + Distributed Safety V5.4 SP5 + WinCC flexible 2008 SP5).
• Use File > Archive > Entire Project for every backup. Avoid the "User-defined scope" option unless intentional.
• Maintain a project-level README.TXT with the CPU order number, FW version, password list (kept in a separate secure location), and the list of optional packages.
• For F-CPU projects, request both the S7-Project source and the signed F-signature audit log — these are required for any future safety re-certification.

12. Field-Proven Diagnostic Matrix

FAQ