Resolving LOGO! 8 Ladder .lld Import Failure in Soft Comfort v8
Siemens LOGO! Soft Comfort V8.x restricts the import of *.lld (LAD) programs when the project is opened in Network Project Mode. Only *.lsc (FBD) programs can be imported or created. The default editor preference set under Tools → Options → General only governs the editing view; it does not override the import filter. This article documents the underlying constraint, the supported editor/file matrix, and the field-proven workaround that converts the LAD program to FBD, saves it as *.lsc, and then imports it into the target 0BA8 device node in the project tree.
Problem Summary
When working with a Siemens LOGO! 0BA8 (LOGO! 8) base module inside LOGO! Soft Comfort V8.x on Windows 7 Professional, an existing ladder diagram stored as *.lld cannot be imported directly. The Import dialog filters out *.lld files and only shows *.lsc. The user has already configured the default editor to Ladder under Tools → Options → General, yet the import behavior does not change because the option controls the editing view, not the file-type acceptance of the Import action.
Symptoms observed in the field:
-
Import dialog lists only
*.lscfiles. The*.lldladder program does not appear even when All files (*.*) is selected, and double-clicking the file opens a separate instance rather than importing. -
Right-click → Import on a 0BA8 device node is greyed out for
*.lldsource programs. - Project tree shows a new device node for the 0BA8 but the circuit program slot remains empty after the attempted import.
- Setting the default editor to Ladder has no effect on import. The Tools → Options → General → Default editor setting governs only how a brand-new or freshly opened program is displayed in the diagram editor window.
Root Cause: Network Project Mode Import Restriction
LOGO! Soft Comfort V8.x supports two distinct top-level workspace modes:
- Diagram Mode (single-program editor) — both LAD and FBD are first-class program representations. Users can create, open, save, and convert between them freely.
-
Network Project Mode (multi-device project tree) — the project tree may contain multiple LOGO! base modules and expansion nodes. Within this mode, only FBD-based programs (
*.lsc) may be imported or newly authored. LAD is not a supported representation for imported or newly created circuit programs in this mode.
This restriction is enforced at the project-tree level and is independent of the user's editor preference. The internal circuit-program model used by the network project stores blocks in a format that mirrors the LOGO! 0BA8 firmware's FBD program representation. LAD files (*.lld) are essentially LAD-native serializations that do not map one-to-one onto this FBD-centric internal model without an explicit conversion step.
The conversion button labeled "Convert to FBD" in the diagram editor performs the necessary translation. Once executed, the program can be saved as *.lsc and subsequently imported into a network project device node.
LOGO! Soft Comfort v8 Editor Modes Compared
| Attribute | Diagram Mode | Network Project Mode |
|---|---|---|
| Use case | Single circuit program development, conversion, and direct download | Multi-device projects, Ethernet topology, remote download via IP |
| Create LAD program | Yes | No |
| Create FBD program | Yes | Yes |
Import *.lld (LAD) |
Yes (opens directly) | No — filtered out |
Import *.lsc (FBD) |
Yes | Yes |
| Convert LAD → FBD | Yes (button in toolbar) | N/A — LAD not present |
| Convert FBD → LAD | Yes (only in diagram mode) | Not supported in network projects |
| Multiple LOGO! base modules | No — one device per workspace | Yes — device tree with base + expansion |
| Ethernet/IP download | Single target only | Yes — download per device node |
| Default editor setting (Tools → Options) effect | Affects newly opened/created programs | Does not enable LAD import |
File Type and Editor Compatibility Matrix
| Source Program | Extension | Diagram Mode | Network Project Import | Notes |
|---|---|---|---|---|
| Ladder program | *.lld |
Open, edit, save, convert to FBD | Blocked — must convert to *.lsc first |
Cannot be edited as LAD inside a network project |
| Function Block Diagram program | *.lsc |
Open, edit, save, convert to LAD | Allowed | Native representation inside network projects |
| UDF (User-Defined Function) library |
*.lma / *.lmp
|
Manage via Tools menu | Reachable via FBD block library | Macros; not directly imported as a circuit program |
| Network project | *.lnp |
Read-only / project-level | Native file format | Authored in network project mode only |
| Archive (zipped project) |
*.zip / *.lna
|
Extract then open | Extract then open in network mode | Used for project sharing and version control handoff |
Prerequisites
Before running the conversion workflow, confirm the following on the engineering workstation:
- LOGO! Soft Comfort V8.x installed. Versions V8.0, V8.1, V8.2, and V8.3 are all known to exhibit the same network-project LAD import restriction. Verify version via Help → About.
- Supported OS. Windows 7 Professional SP1, Windows 8.1, Windows 10 (1809+), or Windows 11. LOGO! Soft Comfort V8.0 was the last official build tested against Windows 7; V8.2 and V8.3 require Windows 10 or later.
-
Source program on disk. The
*.lldladder program must be in a folder writable by the engineering user; the conversion step writes a new*.lscto the same path by default. -
Project file location. The target
*.lnpnetwork project must be located on a local drive (not a network share) for reliable file-locking during import. -
User permissions. Write access to the project folder and the
*.lldsource folder.
Optional but recommended:
- A spare LOGO! 0BA8 on the bench, programmed via Ethernet for end-to-end verification (PC → switch → LOGO! 0BA8).
- Backup copy of the source
*.lldfile in a separate folder, since the "Convert to FBD" operation is non-destructive but the file may be resaved with format metadata changes.
Step-by-Step Conversion and Import Workflow
The end-to-end procedure is split into two phases: (A) Diagram-mode conversion of the LAD file to FBD, and (B) Network-project import of the resulting *.lsc.
Phase A — Convert .lld to .lsc in Diagram Mode
- Launch LOGO! Soft Comfort V8.x and ensure the application opens in Diagram Mode. If the workspace currently shows a network project tree with multiple devices, close it (File → Close Project) so the application returns to the single-program editor.
-
Open the source
*.lldfile via File → Open or by dragging the file onto the workspace. The diagram editor renders the program in LAD view. Verify visually that all rungs loaded correctly before converting. - Convert to FBD. Click the toolbar button labeled "Convert to FBD". In V8.0 the icon is a two-block arrow (LAD → FBD). The dialog Do you want to convert the program from Ladder Diagram to Function Block Diagram? appears. Click Yes.
-
Inspect the converted program. Soft Comfort regenerates the circuit as FBD blocks. Confirm that:
- All normally-open / normally-closed contacts are present.
- All coils (Q outputs, memory flags M, jump labels) are connected.
- Timers, counters, analog blocks, and any UDFs are present and parameterized.
- No blocks show an exclamation mark indicating unresolved references.
-
Save as
*.lsc. Use File → Save As and select LOGO! Program (*.lsc) as the file type. Pick a filename that clearly indicates the FBD variant, e.g.pump_seq_v3_FBD.lsc. Confirm the save.
Phase B — Import .lsc into the Network Project
-
Open or create the network project. In LOGO! Soft Comfort, choose File → New Project (or Open Project for an existing
*.lnp). The workspace switches to Network Project Mode with a device tree on the left. - Add or select the target 0BA8 device node. Right-click the project root and choose Add Device → LOGO! 0BA8, or expand an existing device to expose its circuit program slot.
-
Import the FBD program. Right-click the target device's Circuit Program node and choose Import. The file-open dialog appears filtered to
*.lsc. Navigate to the converted file and confirm. - Confirm the program appears in the device node's circuit program. The program is stored as FBD and is no longer convertible to LAD inside the network project.
-
Save the network project with File → Save (or Ctrl+S). Soft Comfort writes the updated
*.lnpand associated*.lscpayloads. - Download to the LOGO! 0BA8. Right-click the device and choose Download → PC ↔ LOGO!. Confirm the Ethernet connection (or use USB cable) and complete the transfer.
Network Project Mode Import Walkthrough (Inline SVG)
The decision flow below summarizes the import path taken by Soft Comfort V8.x when a network project is open and a user attempts to load a program onto a 0BA8 device node.
Verification
After completing the import, verify that the program is functionally identical to the source *.lld by running the following checks in order.
- Block-count parity. Compare the number of blocks in the original LAD (rungs × contacts/coils + blocks) against the FBD result. A discrepancy greater than 5% typically indicates a failed conversion of a UDF or an analog block.
- Tag and address audit. Open Tools → Reference Data in the FBD program. Confirm that all I/O (I1–I24, Q1–Q16, AI1–AI8, AQ1–AQ2), flags (M1–M27), and shift-register bits (S1.1–S4.8) match the source LAD reference.
- Simulation run. Use Tools → Simulation to start the LOGO! Soft Comfort simulator. Toggle each input used in the program and confirm the expected output, timer, or counter behavior. Soft Comfort's simulator uses the same runtime model as the 0BA8 firmware, so functional drift between modes is rare.
- Online test against hardware. Connect the PC to the LOGO! 0BA8 via Ethernet and select Online → Start Online Test. Soft Comfort displays live I/O state. Manually exercise inputs and compare against the simulated results.
- Download and cold-start. Perform a final download with PC → LOGO!. Power-cycle the 0BA8 to confirm the program is non-volatile and boots into RUN. The LOGO! display should show the configured text message and the green RUN LED should be steady.
*.lld as the documentation master. Use the FBD version strictly for network project integration and hardware download. This avoids round-tripping FBD → LAD → FBD, which can re-encode comments and minor rung metadata.
Troubleshooting Matrix
| Symptom | Likely Cause | Action |
|---|---|---|
Import dialog shows only *.lsc
|
Network Project Mode active; LAD import filtered | Convert *.lld in Diagram Mode first, then re-import |
| "Convert to FBD" button greyed out | Program already in FBD, or no program loaded | Open the *.lld file in Diagram Mode, then re-check the button state |
Converted *.lsc missing UDF instances |
UDF library not registered on the engineering PC | Install the matching *.lma UDF under Tools → UDF Library, then reopen and reconvert |
| Block count drops after conversion | Empty rungs or disconnected sub-circuits in the LAD source | Open the original *.lld in Diagram Mode; check for orphan contacts/coils; reconvert |
| Default editor set to LAD but view still FBD after import | Network project mode forces FBD view for imported programs | Accept FBD view; use the standalone *.lld master for LAD documentation |
| Download fails with "Wrong firmware version" | Target LOGO! 0BA8 firmware older than the program's minimum version | Check program properties for the minimum 0BA8 firmware; update LOGO! via SD card or upgrade module |
| Ethernet download stalls at 0% | PC and 0BA8 on different subnets, or firewall blocking UDP/69-style discovery | Verify both nodes share subnet; allow Soft Comfort through Windows Firewall; retry |
| Program on LOGO! does not match PC after download | Old program still in module; PC → LOGO! transferred only the circuit but not the parameters | Use PC ↔ LOGO! in Online Test to sync parameters, or perform a full overwrite download |
Edge Cases and Caveats
UDF and Macro Preservation
User-Defined Functions (*.lma) and macros used inside the LAD source must be installed on the engineering PC before the conversion step. If a UDF is referenced by block name but not present in the local library, the converter may emit a placeholder block that lacks the macro's internal logic. Always re-install the UDF library set that accompanied the source program before converting.
Comment and Text-Message Loss
Inline rung comments in LAD are stored as block-property text in FBD. The conversion preserves comment strings but visually relocates them onto block properties dialogs. The "Show comment" toggle in the FBD view does not show legacy LAD-style inline notes. Use the Comment tab in the block's properties dialog to re-verify and reformat documentation after conversion.
Analog Threshold and Hysteresis
Analog comparator and threshold blocks retain their parameter set across conversion, but the gain/offset scaling constants are stored with full precision only when the target 0BA8 firmware is ES 02 or later. On early ES 01 firmware, the conversion may quantize the constants to the nearest displayable value. Verify analog behavior in simulation before relying on it.
Network Project Save Format
Network projects saved by Soft Comfort V8.x are not forward-compatible with LOGO!Soft Comfort V7. The internal *.lnp format changed. If a mixed-version team is involved, store the FBD *.lsc separately and re-create the network project on the older V7 workstation if a V8 import is not feasible.
Multiple 0BA8 Devices in One Project
When several 0BA8 nodes are present, each must hold its own FBD program. Importing the same *.lsc into multiple devices works, but the project file size grows linearly. For projects with more than four 0BA8 nodes, prefer splitting into separate network projects and linking via Ethernet routing rather than a single monolithic project.
Clock and Timer Block Parameter Rounding
On conversion, timer preset values are preserved exactly. The "Convert to FBD" path does not resample the time base. Edge cases where the original LAD file used non-standard 10 ms time bases (the legacy LOGO! 5/6 base) are remapped to the LOGO! 8 native 10 ms base. Verify any timing-critical ladder logic after conversion, especially where the legacy base was 100 ms or 1 s.
Field Notes and Best Practices
-
Always keep a master
*.lld. Treat the LAD file as the canonical, human-readable documentation of the control logic. The FBD*.lscinside the network project is a derived artifact for runtime deployment. -
Name files semantically. Use suffixes like
_LAD.lldand_FBD.lscto keep variants unambiguous in version control and on shared drives. - Set Tools → Options → General → Default editor to LAD for users who primarily author in LAD. Remember that this only affects newly created or standalone-opened programs — it does not enable LAD inside a network project.
- Validate in simulation first. Run the FBD program in the LOGO! Soft Comfort simulator with a representative input sequence before downloading to hardware. The simulator is cycle-accurate with the 0BA8 firmware and catches conversion drift quickly.
- Use Ethernet for download to 0BA8. USB download is supported but slower and locks the LOGO! display into a transfer mode. Ethernet keeps the HMI usable during PC ↔ LOGO! sync.
-
Back up the network project before bulk import. Right-click the project root and choose Archive to produce a
*.lnasnapshot. This is the only way to roll back a corrupted*.lnpafter an import failure. -
Document the conversion in the project log. A short note in the project README listing which devices were imported from which LAD master helps future maintenance engineers reverse the mapping if the original
*.lldis updated.
Standards and Documentation References
The conversion behavior described above is consistent with the LOGO! 0BA8 system manual and the LOGO! Soft Comfort V8.x online help. Confirm firmware-specific limits against the official Siemens documentation before commissioning:
- LOGO! 0BA8 System Manual (Siemens Industry Online Support, entry ID 109751634)
- LOGO! Soft Comfort V8.0 Online Help and Function Manual
- Siemens LOGO! Product Family Overview
- Siemens Industry Online Support — LOGO! Downloads and Firmware
Why does LOGO! Soft Comfort v8 only import .lsc files in network projects?
The network project mode stores circuit programs in the 0BA8 firmware's native FBD representation. The Import filter is therefore restricted to *.lsc. LAD (*.lld) is supported in standalone Diagram Mode only, where you can open the file and click the "Convert to FBD" button to produce a compatible *.lsc for re-import.
Does setting Tools → Options → General → Default editor to Ladder enable .lld import?
No. That setting only controls the editing view for newly opened or newly created programs in Diagram Mode. It does not change the Import dialog filter inside a network project, and it does not permit LAD editing once a program is imported into a network project.
Can I convert an imported FBD back to LAD inside a network project?
No. The "Convert to LAD" capability is not available in network project mode. Maintain the canonical *.lld master outside the project and re-derive *.lsc files when logic changes.
What happens to comments and rung notes when I convert .lld to .lsc?
Comment text is preserved on the FBD block properties, but inline LAD-style rung notes are not rendered inline in the FBD view. Open each block's properties dialog after conversion to confirm that all comments survived and are still attached to the correct logical element.
How do I roll back a failed import in a network project?
Right-click the project root and choose Archive to produce a *.lna before performing bulk imports. If an import corrupts the *.lnp, close Soft Comfort, locate the archive, and restore the project from the *.lna. Without an archive, the previous state is not recoverable.