Siemens LOGO! Web Editor: Fix Invalid Name in SD Card Error

Siemens LOGO! Web Editor: Fix "Invalid Name in SD Card" Download Error

Siemens LOGO! 8 base modules with an integrated Ethernet interface expose a built-in web server that displays custom dashboards generated by the LOGO! Web Editor (LWE). When the project name in the LWE does not match the directory name already present on the micro SD card — or does not match the active LOGO!Soft Comfort (LSC) program name — the LWE V1.0.1 download routine aborts with Download Failed! Invalid name in SD Card. This article documents the conditions that trigger the error on a 6ED1 052-1MD08-0BA0, the diagnostic path that confirms the SD card itself is healthy, and a complete step-by-step procedure to restore a working web project without re-flashing the base module.

1. Problem Overview

Engineers using the LOGO! Web Editor V1.0.1 to push custom web dashboards to a LOGO! 8.3 base module (order number 6ED1 052-1MD08-0BA0) report the following reproducible failure mode:

• The first download of a web project succeeds and the dashboard appears correctly on the device's web server.
• After modifying the project in LWE — most notably renaming the web project — every subsequent download attempt fails with the dialog Download Failed! Invalid name in SD Card.
• Replacing the micro SD card with a freshly formatted card does not resolve the problem.
• Creating a new LWE project from scratch with a different name reproduces the error.
• The LOGO! on-board diagnostic path Main menu → Diagnostics → Hardware → SD card reports OK with no hardware fault.

The condition is reproducible, is independent of the SD card vendor, capacity class, or file system used (provided the card is FAT16/FAT32 formatted as required by the LOGO! 8 platform), and is not resolved by re-installing LOGO!Soft Comfort. The cause is project-name binding inside the LWE V1.0.1 downloader, not the physical media.

2. Affected Hardware and Software

The 6ED1 052-1MD08-0BA0 belongs to the LOGO! 8.3 family (also referred to as LOGO! 8 FS4). It is a 24 V DC powered base module with an integrated display, eight digital inputs, four digital outputs, four analog inputs (two of which can be reconfigured as digital inputs 1B/2B), an Ethernet interface, and a micro SD card slot. The module is the first line of LOGO! devices that fully supports custom web projects produced by the LWE plug-in.

3. Base Module Specifications Reference

The following specification data for the 6ED1 052-1MD08-0BA0 is taken from the official LOGO! 8.3 system manual and is included here so that engineers can confirm they are working with the affected hardware revision.

4. Root Cause Analysis

When the LWE project is first downloaded to the LOGO!, the tool writes a self-contained directory tree onto the SD card. The root directory of that tree uses the LWE project name as its identifier. Internally, the LOGO! web server then serves the dashboard from that path. The LSC program is stored in a sibling directory whose name matches the LSC project. The web server correlates the LWE and LSC programs by directory name on the card; if the names diverge, the association cannot be resolved.

Three conditions have been observed to trigger the V1.0.1 "Invalid name in SD Card" dialog:

1. Project name drift after the first download. The LWE project is renamed between successive downloads. The previously written folder on the SD card is not removed, and the new project name cannot be bound to a clean directory. The downloader refuses the transfer to protect the existing directory from being orphaned.
2. Mismatch between the LWE project name and the LSC project name on the SD card. The base module writes the active LSC program to the SD card using the LSC project name. The web server correlates the LWE and LSC programs by directory name. When the two names diverge, the web server cannot associate the LWE assets with the running LSC logic, and the download is refused with the "Invalid name in SD Card" message.
3. Stale residual directory from a previous project. Renaming an LWE project — or copying a project from another installation — leaves behind a folder whose name is the old project name. The LWE V1.0.1 downloader validates the SD card tree before writing, and any pre-existing directory with a different name produces the error.

The on-board diagnostic path Main menu → Diagnostics → Hardware → SD card only checks the physical state of the card (presence, file system, write-protect, and free space). It does not validate the project-name consistency. A clean OK result therefore rules out a hardware defect and points to a project-naming conflict.

5. Diagnostic Procedure

Run the following checks in order before applying the resolution. Each step is non-destructive and can be performed on a running system.

1. Check the SD card in the LOGO! on-board menu. Navigate to Main menu → Diagnostics → Hardware → SD card. A status of OK confirms the card is present, formatted correctly, and writable. A status of NO CARD, WRITE-PROTECTED, or FILE SYSTEM ERROR indicates a physical issue that must be resolved before continuing.
2. Read the active LSC program name from the LOGO!. On the base module display, open Program → Card → Program name and note the exact string. The string is the LSC project name and is also the root directory on the SD card under which the web project must be stored.
3. List the SD card contents on a PC. Power down the LOGO!, remove the micro SD card, and read it with a card reader. The root of the card should contain a folder whose name matches the active LSC program. Inside that folder you will find logo.bin (the LSC program image) and, if a web project has been deployed, a sub-folder with the LWE project name.
4. Compare the LWE project name with the SD card sub-folder name. In the LWE, open Project → Properties (or File → Properties depending on the LWE build) and record the project name. Compare it to the sub-folder name on the SD card. Any mismatch is the trigger for the error.
5. Compare the LWE project name with the active LSC project name. Open the matching LSC project in LOGO!Soft Comfort and record the project name from File → Project Properties. If this name differs from the LWE project name, the download will fail.
6. Capture the LWE build number. Open Help → About in the LWE plug-in and record the exact build string. This is required if a Siemens support request is opened.

6. Resolution: Step-by-Step Procedure

The fix is to align the three identifiers — the LWE project name, the LSC project name, and the SD card folder name — before re-issuing the download. Use the procedure that matches your situation.

6.1 Quick fix: rename the LWE project to match the LSC project

1. In the LOGO! Web Editor, open the project that is failing to download.
2. Select File → Save As and assign the new name to exactly match the LSC project name recorded in step 2 of the diagnostic procedure. Match the case, underscores, hyphens, and any numerical suffix.
3. Confirm that no other project, image, or asset references the old LWE project name.
4. Click the Download to LOGO! button (the icon with the arrow pointing down to a card). The progress bar should complete without the "Invalid name in SD Card" dialog.
5. After the download, leave the LOGO! powered for at least 10 seconds so that the internal name index is flushed to non-volatile memory.

6.2 Clean-room fix: clear the SD card and re-deploy both projects

1. Back up the active LSC program: in LSC, File → Save As to a local .lsc file on the PC.
2. Back up the LWE project: in LWE, File → Save As to a local .lwe file on the PC.
3. Power down the LOGO! and remove the micro SD card.
4. Insert the card into a PC. Format the card with FAT16 or FAT32 (allocation size 4096 bytes is recommended). Delete any residual \<old name>\ folders that remain from previous projects, including the ~SD_Config.dir index file.
5. Re-insert the card into the LOGO! base module.
6. Open the LSC project. Use Tools → PC → LOGO! (or Tools → Transfer → PC → LOGO!) to download the program. Note the exact project name from the Program name display on the base module.
7. Open the LWE project. File → Save As the LWE project using a name identical to the LSC project name (including underscores, hyphens, and case).
8. In the LWE, click Download to LOGO!. The transfer should complete and the dashboard should appear at http://<logo-ip>.

6.3 Block format check after the project names are aligned

After the download succeeds, verify that the integer variables exposed by the dashboard are interpreted correctly. In the LWE, each variable must be bound to a memory marker or I/O address using the Signed block format whenever the underlying value can be negative (e.g. AI1 scaled to °C, counters that wrap, or any signed arithmetic result). Selecting Unsigned for a signed variable will display garbage values in the dashboard even though the download completes without error. This is a common secondary fault discovered only after the "Invalid name" error is cleared.

7. Verification

1. Open a browser and navigate to the LOGO!'s IP address. The custom dashboard should load without HTTP 404 errors.
2. Click on each dashboard widget. The values should match the values shown on the base module display or in LSC's online view (press F5 to start online mode).
3. Force a value change in the LOGO! (e.g. toggle an input or set a memory marker). The dashboard should update within one polling cycle (default 2 seconds; configurable in the LWE project properties).
4. Power-cycle the LOGO! base module. The dashboard should reload automatically when the web server comes back up. If it does not, the SD card folder binding has not been flushed — re-run the resolution in section 6.
5. Repeat the LWE download a second time. The transfer should succeed without prompting the "Invalid name" dialog, confirming the SD card directory is now in a consistent state.

8. SD Card Folder Structure Reference

The SD card layout for a LOGO! 8.FS4 base module with an active web project follows a strict convention. Use the table below to validate the on-card tree before and after an LWE download.

The base module performs a case-sensitive comparison of <LSC_project_name> and <LWE_project_name> against the on-card directory names. Any difference — including trailing spaces, non-ASCII characters, or BOM markers embedded by certain text editors — produces the "Invalid name in SD Card" rejection. If the LWE project has been opened and re-saved by an external HTML editor, ensure that the file is re-saved as UTF-8 without BOM before re-deploying.

9. Firmware and Software Compatibility Matrix

The 6ED1 052-1MD08-0BA0 ships with FS4 firmware from the factory. The LWE V1.0.1 is bundled with LOGO!Soft Comfort V8.3 or later and is the recommended version for this hardware. Earlier LWE V1.0.0 builds are supported on FS3 but do not include the strict name-binding check, which is why the error appears only after the upgrade to V1.0.1.

10. Troubleshooting Matrix

11. Prevention and Best Practices

• Lock the project names. Once a web project is deployed, keep the LWE project name identical to the LSC project name. Treat the two names as a single identifier and document them in the project header in both tools.
• Use Save As with the same name when porting projects. Migrating a dashboard from one LOGO! to another is a common trigger for the error. Always create the new LWE project with File → Save As and explicitly type the destination LSC project name.
• Avoid renaming after first deployment. Renaming an existing LWE project on the PC side does not update the on-card directory. The cleanest workflow is to deploy a new project, never to rename an existing one.
• Format the SD card between project migrations. When transferring a project to a different LOGO!, re-format the card on a PC to wipe residual project folders and the ~SD_Config.dir index. A clean FAT16/FAT32 partition is a prerequisite for a clean LWE deployment.
• Use Siemens 6ED1 056-1BA00-0AA0 cards for critical deployments. Third-party cards are supported but the Siemens-branded cards have been qualified against the LOGO! diagnostic path and minimise the risk of intermittent file-system errors. The 2 GB capacity is sufficient for any LWE project that fits in the on-card program space.
• Tag every LWE download in a change log. Record the LWE project name, LSC project name, LWE build number, SD card serial, and the base module's IP address and firmware version. The change log turns a future "Invalid name" failure into a five-minute fix.
• Keep LSC and LWE on the same release train. Mixing LSC V8.2 with LWE V1.0.1, or LSC V8.4 with a base module still on FS3, is a frequent cause of subtle name-binding errors. Upgrade LSC, the LWE plug-in, and the base module firmware as a set.
• Keep the LWE project UTF-8 without BOM. External HTML editors that insert a BOM at the start of the file can produce name comparison failures that surface as the same "Invalid name" dialog. Re-save the project as plain UTF-8 before deploying.

12. Escalation Path

If the procedure in section 6 does not clear the error, escalate as follows:

1. Collect the LSC project (.lsc), the LWE project (.lwe), a screen capture of the on-board Diagnostics → Hardware → SD card menu, and a directory listing of the SD card root.
2. Open a Siemens support request at the Siemens Industry Online Support portal and attach the four files.
3. Reference the LWE V1.0.1 build number from Help → About in the LWE plug-in and the base module's order number (6ED1 052-1MD08-0BA0) and firmware version (FS4 / FS5 / FS6).
4. Siemens Technical Support can request a remote pull of the on-card directory listing and confirm whether a stray folder with the old name is still present. The escalation typically takes 2-5 business days for a name-binding defect.