Resolving the "Diagnostics Micro SD Card Detached" Error on Siemens LOGO! 8 (6ED1052-2MD08-0BA1)

The Siemens LOGO! 8 logic module (base variant 6ED1052-2MD08-0BA1) normally runs the user program from its internal non-volatile EEPROM and does not require a Micro SD card for ongoing operation. When the on-board display reports "Diagnostic Micro SD Card detached" and the controller drops into STOP, the message is a diagnostic hint, not a fatal hardware failure. In almost every case the controller can be brought back to RUN within a few minutes by reading the diagnostic message correctly, removing or replacing the Micro SD card, and verifying the program source.

This reference describes the architecture behind the Micro SD slot, the message semantics, the decision path the LOGO! 8 takes when a card is present, the menu navigation needed to inspect the diagnostic, and the field-proven recovery sequence. It is aimed at commissioning engineers, panel builders, and service technicians who encounter this message on a unit that previously ran without an SD card.

1. Problem Statement

The reported field symptom is reproducible across multiple LOGO! 8 base modules:

• Onboard display shows Diagnostic > Micro SD Card > detached.
• Status line of the LOGO! 8 turns red and the module enters STOP.
• Digital and analog outputs drop to their defined STOP-state values.
• Ethernet communication, Web server, and any remote I/O slaves may still respond, but the user program is not being scanned.
• The Micro SD slot flap on the front of the module is empty (no card visibly inserted).

Because the message is a "detached" indication but the user can see no card, the troubleshooting path is not obvious. The module is reporting either a card that has been removed, a card that is physically present but electrically unreadable (bent contact, partial insertion, foreign object), or an internal detection fault.

2. Affected Hardware and Firmware

The -0BA1 suffix on the 6ED1052-2 family indicates the first LOGO! 8 generation, which ships with the LOGO! 8 base firmware. The diagnostic menu structure described in this article is consistent across the LOGO! 8 / 8.2 / 8.3 firmware streams; the wording on the display is the same. Refer to the Siemens Industry Online Support portal for the current LOGO! 8 system manual, which documents the diagnostic text strings and the menu tree used here.

3. LOGO! 8 Micro SD Card Architecture

The LOGO! 8 base module exposes a single Micro SD slot on the front panel, hidden under a yellow protective flap. The card interface serves four distinct functions, and the LOGO! firmware prioritises them in a defined order at boot:

1. Boot program source – a file named LOGO.bin or LOGO.lsc in the card root.
2. Project archive / recipe storage – additional LSC files for transfer to other LOGO! devices.
3. Data logging – CSV files written when the Data Log function block is enabled.
4. Firmware update medium – special FWUPDATE.BIN for SD-based firmware upgrades.

The internal EEPROM is a separate physical memory. When the card slot is empty, the firmware always boots from EEPROM and the SD card diagnostic is reported as a passive warning (orange). When a card is detected, the firmware inspects its content; an empty card, a card with an unrecognised file system, or a card with an unparseable program triggers a different behaviour than a valid program-on-card. Understanding which of the four conditions applies is the first step in the recovery.

4. Decoding the Diagnostic Message

The on-board display uses a two-line status block for diagnostics. The exact lines and their meaning are:

Note that the diagnostic text is identical in the orange and the red cases. The colour of the status background and the RUN/STOP state of the module are the disambiguators. Always confirm both before acting.

5. Root Cause Analysis

Five root causes cover the vast majority of STOP incidents attributed to the SD card diagnostic:

5.1 Card physically present but invisible to the operator

The yellow front-flap does not lock the card; the spring mechanism can leave a card flush with the housing. Inspect with a flashlight. The card is typically a Micro SDHC of 2 to 32 GB.

5.2 Card inserted by third party

A commissioning engineer, integrator, or end-user may have inserted a card containing a different program, a partial copy, or an empty card. The LOGO! 8 attempts to load from the card, fails validation, and falls back to STOP.

5.3 Bent or contaminated contacts

The Micro SD spring carrier has eight contact pins. A bent pin can short the detect line to ground and confuse the firmware. Dust, oil, or solder debris from board rework can have the same effect. On a 0BA1 unit that has been on a panel for years, oxidation of the pins is also a candidate.

5.4 Incompatible card type

SDXC cards (64 GB and above) use exFAT, which the LOGO! 8 boot loader does not parse. Very small cards (< 256 MB) sometimes fail the geometry check. Industrial Micro SD cards from brands such as Swissbit, ATP, or Apacer are recommended for production; consumer SanDisk or Samsung cards are acceptable for bench work.

5.5 Card previously used as program source

If a project was last loaded from a card rather than the EEPROM, the LOGO! 8 expects to see that card on the next boot. Removing the card with the program on it is a deliberate "orphan" state that the firmware treats as a hard fault, not a warning.

6. Preconditions for the Diagnostic

Before opening the cabinet, gather the following items:

• Known-good Micro SD or Micro SDHC card, 2 GB to 32 GB, formatted as FAT32 with a single primary partition.
• PC with LOGO! Soft Comfort V8.x installed.
• Ethernet cable for direct connection to the LOGO! 8 (RJ45, point-to-point, no switch required).
• Phillips PH1 screwdriver if the module is in a sealed enclosure and the front flap is hard to access.
• Anti-static wrist strap; the LOGO! 8 base is ESD-sensitive on the SD card carrier.
• Camera or smartphone to record the diagnostic screen before any action.

Capture the on-board display exactly as it appears, then navigate through Menu → Diagnostics → Hardware → SD Card to confirm the message text. Photograph each submenu as you traverse it; this creates an audit trail if a Siemens support case is opened.

7. Step-by-Step Recovery Procedure

1. Power down safely. Place the connected machine in a safe state. The LOGO! 8 is a non-redundant controller; outputs will de-energise.
2. Open the yellow front flap. Press the flap gently toward the body of the module and lift. The spring carrier should be visible.
3. Inspect for an inserted card. Use a flashlight. If a card is present, depress it once to release the spring and remove it. If the slot is empty, proceed to step 5.
4. Inspect the spring carrier. Look at the eight contact pins under magnification. A bent pin will lean to one side. If a pin is bent, power down completely, gently straighten it with a non-magnetic tweezer, and re-seat a known-good card.
5. Insert a known-good card (FAT32, 2 to 32 GB). Push until the click is felt. The card should sit flush.
6. Power up the LOGO! 8. Watch the SD activity LED. It should flicker once on detection.
7. Navigate to the diagnostic menu. On the LOGO! display: ESC → Menu → Diagnostics → Hardware → SD Card. Confirm the line now reads OK instead of detached.
8. Return to RUN. Press ESC repeatedly until the status screen is shown. The background should be neutral or green, not red.
9. Re-transfer the program from LOGO! Soft Comfort to the LOGO! 8 internal EEPROM, even if the program was already there. This forces a clean re-load and clears any boot-time ambiguity about the program source.
10. Cycle power and verify the controller enters RUN without re-triggering the diagnostic.

8. Onboard Diagnostic Menu Navigation

The on-board menu of the LOGO! 8 base is operated with the six keys under the display. The diagnostic tree relevant to this fault is:

ESC -> Main Menu
  -> Diagnostics
       -> Hardware
            -> SD Card        <-- status line for this fault
            -> Ethernet
            -> Module Info
       -> Software
            -> Program
            -> Library
       -> System
            -> Clock
            -> Language

The Hardware → SD Card page shows the current state (OK, detached, write-protected, not supported) and, on most firmwares, the capacity of the detected card. If a capacity is shown but the message is still red, the firmware has detected the hardware but failed to mount the file system. Re-formatting the card on a PC as FAT32 is the corrective action.

9. Hardware Inspection Procedure

When the diagnostic persists after a known-good card is inserted, perform the following mechanical and electrical checks.

9.1 Visual inspection of the carrier

Remove power. With a 10x loupe, examine:

• The eight spring pins – all should be vertical and equidistant.
• The detect switch (a small leaf switch on the side of the slot).
• Any solder splash on the carrier PCB.

9.2 Continuity test

With the module unpowered and removed from the DIN rail, use a multimeter in continuity mode. Probe the SD card detect pin to ground; with no card inserted, the switch should be open (> 1 MΩ). With a card inserted, the resistance should drop to < 5 Ω. A short to ground (< 5 Ω with no card) indicates a bent pin or a foreign object.

9.3 ESD and contamination

Wipe the carrier with a clean, lint-free, isopropyl-alcohol-dampened swab. Allow two minutes for evaporation before inserting a card. Do not use acetone; it can craze the polycarbonate flap.

9.4 Carrier replacement

If the carrier is damaged, Siemens offers the slot as a service part. The carrier is soldered to the main board; replacement requires hot-air rework and is not a field repair in most jurisdictions. Escalate to a Siemens service partner for carrier swap.

10. Program Loading Priority Logic

The order in which the LOGO! 8 looks for a program at boot is, from highest to lowest priority:

1. Card-resident LOGO.bin with a valid header.
2. Card-resident LOGO.lsc project file.
3. Internal EEPROM (retained from the last download).

The card is always checked first. This is why a card containing a different program, an outdated program, or a corrupt file forces the LOGO! 8 into STOP even though the EEPROM still holds a valid, current project. The diagnostic message Micro SD Card detached in this case is the firmware reporting that the boot source it expected (the card) is no longer there, not that the EEPROM is empty.

To lock the LOGO! 8 to EEPROM-only boot, do not insert a card; the firmware falls back to EEPROM and continues to RUN. To force a card-only boot, write a new program to the card using LOGO! Soft Comfort and leave it in the slot; the next boot will source the project from the card.

11. Verification Procedure

After the recovery steps, perform the following sequence to confirm the fault is cleared:

1. With the controller in RUN, navigate to Diagnostics → Hardware → SD Card. Verify the line reads OK.
2. Toggle a digital output from the on-board menu (using the cursor keys to navigate to the I/O status page) and confirm the physical output follows.
3. From LOGO! Soft Comfort connected via Ethernet, perform an Online Test. The status indicators in the software should show the same input/output state as the physical module.
4. Power-cycle the LOGO! 8 three times, each cycle separated by 10 seconds. The module must enter RUN on each cycle without manual intervention.
5. Insert and remove the Micro SD card five times. Each insertion should be acknowledged by the SD activity LED; each removal should produce the detached line in orange, not red.
6. If a Data Log function block is used, verify that a CSV file is created on the card and updated at the configured interval.

If any step fails, return to Section 9 (Hardware Inspection) and re-check the carrier. If the fault persists, escalate to Siemens technical support with the photographs taken in Section 6.

12. Preventive Measures and Best Practices

13. Extended Diagnostic Reference

Related diagnostic messages on the LOGO! 8 base module that can be confused with the SD card fault:

The LOGO! 8 system manual is the authoritative reference for the complete diagnostic tree. Always cross-check the message text against the manual revision that matches the firmware version on the device, available from the Siemens Industry Online Support portal under product code 6ED1052.