Resolving Empty Workspace After Upload from Siemens LOGO! 8

Resolving Empty Workspace After Upload from Siemens LOGO! 8

A recurring field issue with the Siemens LOGO! 8 programmable logic relay is the appearance of a completely blank diagram workspace in LOGO!Soft Comfort (LSC) immediately after the operator clicks Upload. The transfer progress bar completes, the software reports success, and yet the FBD/LAD editor shows zero blocks, zero I/O references, and an empty canvas. This article provides an engineering-grade troubleshooting path covering firmware/LSC version compatibility, password protection, project metadata, and memory integrity.

1. Problem Context and Typical Symptom Chain

When an engineer performs a PC → LOGO! Upload (also called Read from device or PC → LOGO!) using LSC, the expected behavior is the recreation of the FBD/LAD diagram stored in the controller's non-volatile memory. The four failure paths that most frequently produce a blank workspace are:

1. Empty user program slot — no circuit diagram is actually saved to LOGO! (only the boot project area is empty).
2. LOGO!Soft Comfort major version mismatch — LSC V8.0 cannot decode a project written by a V8.2/V8.3 firmware block.
3. Password-protected program — the upload succeeds in terms of file transfer but the diagram payload is encrypted/blanked.
4. Corrupted RAM cache or stale .lsc file — LSC opens a previously cached empty project over the freshly uploaded content.

The prompt to save the program on close is misleading: it triggers because LSC treats any in-memory session as a dirty project, regardless of whether blocks were placed or not. It is not an indicator that data was actually loaded.

2. Siemens LOGO! 8 Hardware Family Reference

Correct diagnosis begins with identifying the exact hardware platform. The LOGO! 8 family has evolved through several hardware revisions, each requiring its own firmware and LSC pairing.

The full MLFB (Siemens order number) is printed on the side label of every base module. Capture it as the first diagnostic step. Hardware generations prior to BA0 (i.e., LOGO! 6ED1052-0xxx — the LOGO! 7/0BA6/0BA7 era) use a different program container format and will produce exactly the symptom described if read with LOGO! 8 LSC.

3. LOGO!Soft Comfort Version Compatibility Matrix

LOGO!Soft Comfort encodes program blocks using a version-specific binary schema. Each new firmware release introduces block IDs (e.g., new analog function blocks, UDFs, and data log features) that older LSC builds cannot parse. Reading a newer firmware project with older LSC yields either an error dialog or a silently empty workspace.

4. Root Cause Analysis

4.1 Cause A — Empty User Program Stored on the Device

If the LOGO! was never programmed (or was cleared via Clear Program on the on-board display with cursor keys), the upload will succeed but return an empty project object. LSC shows a blank canvas with default 4 inputs and 4 outputs visible, but no interconnections.

Verification: navigate to Tools → Transfer → LOGO! → Diagnostics. The Used memory field will read 0 blocks / 0 bytes. If this is the case, the controller is genuinely empty — the upload worked correctly; the device just has no program to give you.

4.2 Cause B — Firmware / LSC Version Mismatch

If the LOGO! carries firmware newer than LSC supports (for example, an 8.3 BK0 unit being read by LSC V8.1), the upload may complete silently but the diagram is dropped during deserialization. The visible indication is:

• Empty FBD workspace.
• No warning dialog from LSC.
• Title bar shows default project name (Untitled1) rather than the on-device project name.

Always cross-check the firmware version reported under Diagnostics against the LSC build under Help → About.

4.3 Cause C — Password Protection

LOGO! programs can be assigned a program password (Tools → Protect, option Program password, alphanumeric, up to 10 characters). When set:

• The on-device user program is encrypted at rest in flash.
• Uploading without entering the password returns an empty workspace (the file transfer handshake completes, but the encrypted payload is discarded by LSC).
• The on-board display will show a lock icon and prompt for the password before allowing program changes locally.

This is the most common cause when the device is clearly running a program (LED activity) yet nothing appears in LSC after upload.

4.4 Cause D — Ethernet Connection Mode

With LOGO! 8.1 and later (BB0/BK0/BT0/BJ0/BM0) using Ethernet, the wrong transfer channel selection can produce the symptom. LSC may report transfer successful while uploading metadata only:

• Selection of Remote connection via Ethernet without an active network link routes the upload to a non-existent target.
• If the wrong IP address is configured in Tools → Options → Ethernet, LSC can connect to a different LOGO! on the LAN and receive that device's (empty) program.

Confirm via Tools → Transfer → Ethernet Connections that the IP and subnet match the target hardware. Ping the IP from a Windows command prompt first:

4.5 Cause E — Stale Local Cache

If a previous session left an .lsc project open, LSC may auto-load the empty template instead of the freshly uploaded content. Test by closing LSC entirely (no auto-recovery), restarting, and immediately performing the upload without first opening any local file.

5. Step-by-Step Diagnostic Workflow

1. Capture hardware identity. Read the MLFB on the LOGO! side label (e.g., 6ED1052-1MD00-0BA0). Note the hardware series.
2. Capture firmware version. On the device, navigate menu → Diagnostics → FW or use LSC Tools → Transfer → LOGO! → Diagnostics. Typical firmware strings: FS: 01 / FW: V1.09.04.
3. Capture LSC version. Help → About. Compare against the LOGO! firmware compatibility matrix above.
4. Establish clean connection. Restart LSC with no project loaded. Use Tools → Transfer → LOGO! → Ethernet Connections or the serial/USB cable dialog. Confirm IP/serial parameters.
5. Test transfer channel. Use Tools → Transfer → LOGO! → Test Connection. Successful response: Connection OK, FW Vx.xx.xx.
6. Execute upload. Tools → Transfer → PC → LOGO! (NOTE: this command writes from PC to LOGO!; the correct upload command is LOGO! → PC, found in the same menu). Confirm the direction dialog carefully.
7. Check memory contents. After upload, navigate to Tools → Transfer → LOGO! → Diagnostics and inspect User program: 0 / 850 blocks free.
8. Verify password state. On the LOGO! display, press ESC repeatedly and observe if the lock icon appears next to the program name.

6. Resolution Procedures

6.1 If the Program is Genuinely Empty

No correction is required on the controller side. The application does not have a stored circuit diagram. You can:

• Reprogram from a known-good backup using Tools → Transfer → PC → LOGO! (Download).
• Build a new program and download.

To create a backup of the current empty state (rarely useful), use File → Save As with a descriptive name such as LOGO_BA0_empty.lsc.

6.2 If Firmware is Newer than LSC

1. Update LOGO!Soft Comfort to the latest available version from the Siemens Industry Online Support portal. The current release is V8.4, available as a free download.
2. Perform the upload again. Newer LSC will deserialize the program correctly.
3. If updating LSC is not possible, downgrade the LOGO! firmware only if a compatible older image is available — Siemens does not officially support firmware downgrade on 8.x platforms.

6.3 If a Program Password is Set

1. On the LOGO! device, navigate menu → Program → Password.
2. Enter the password via the on-board cursor keys.
3. Return to LSC and execute LOGO! → PC upload again. LSC will prompt Enter password on the upload dialog. Enter the same password; the encrypted payload will be decrypted and the workspace will populate.

6.4 If Wrong Ethernet Target

1. Open Tools → Options → Ethernet Connections.
2. Remove all saved targets.
3. Add the correct target IP. The default IP of a new LOGO! 8.1+ is 192.168.0.10 / 255.255.255.0.
4. Use Test to confirm round-trip before uploading.

6.5 If Local Cache Is Corrupt

1. Close LSC.
2. Delete or rename the auto-recovery folder: %APPDATA%\Siemens\LOGO!Soft Comfort V8.x\AutoRecover.
3. Relaunch LSC. Perform upload without opening any prior project.

7. Cross-Check: Distinguishing a Real Empty Program from a Transfer Failure

Use the following matrix to definitively classify the issue:

If the diagnostics dialog reports a non-zero block count yet the workspace is empty, the cause is either password protection or a version mismatch — not an empty program.

8. Verification Procedure

After applying a fix, verify with the following sequence:

1. Re-initiate LOGO! → PC upload.
2. Inspect the FBD editor for at least one function block, comment block, or analog block in the diagram.
3. Compare Tools → Compare (or third-party diff) against the last known-good archive if one exists.
4. Switch LSC to Online → Run/Stop and verify I/O state updates in real time — this confirms the loaded diagram is functionally identical to what is executing.
5. Save the recovered project as recovered_<MLFB>_<date>.lsc for change-control archiving.

9. Preventive Best Practices

• Maintain a single source of truth. Always archive the .lsc project (not just screenshots) in version control with the MLFB and firmware version annotated in the project comment block.
• Pin LSC versions. In multi-vendor environments, pin a specific LSC build (e.g., V8.4.0) and use it across the engineering team. Avoid ad-hoc upgrades that introduce compatibility drift.
• Document passwords separately. Store the program password in a controlled location, never embedded in the project file comment, since LSC project files can be transmitted unencrypted.
• Label hardware. Apply a physical label with MLFB and firmware version to the LOGO! enclosure so a future engineer can identify the hardware generation without powering the device.
• Use SD card backup. For LOGO! 8.2 and later with microSD slot, schedule periodic Card → LOGO! backups. The .bin image on the SD card can be read on any PC without LSC.

10. When to Escalate

If the diagnostics dialog reports the firmware is non-zero memory, the on-board program executes correctly (LED activity confirms I/O changes), the password is known and entered, and the LSC version supports the firmware, but the workspace remains blank, escalate to Siemens Technical Support with the following package:

• MLFB, hardware series, firmware string from diagnostics.
• LSC build and Windows version.
• Connection type (Ethernet / serial) with a packet capture (Wireshark on TCP port 10005 — LOGO! Ethernet transfer port).
• Project archive .lsc if any blocks can be exported locally.

This configuration enables the support engineer to reproduce the environment with the exact binary protocol version.

11. Related Symptoms Worth Checking

Engineers encountering the blank-workspace symptom should also verify the following related conditions, which often co-occur: