Resolving SINAMICS F30052 EEPROM Data Error on Basic Line Module

Resolving SINAMICS F30052 EEPROM Data Error on the Basic Line Module

1. Problem Overview

The Basic Line Module 6SL3130-1TE31-0AA0 is a 10 kW unregulated rectifier / feed unit in the SINAMICS S120 Booksize family. It supplies the DC link for motor modules and is paired with a Control Unit (CU320-2, CU310-2, or an integrated S210 controller). During commissioning or after a control-voltage interruption, the unit may refuse to leave the start-up state and the drive object (DO) of the BLM raises:

• Fault code: F30052
• Message text: EEPROM data error
• Reaction: OFF2 (the BLM's pre-charge contactor is opened, the DC link is not enabled)
• Acknowledge: POWER ON (the fault cannot be cleared with standard acknowledge; a control-voltage reset is required after the corrective action)
• Fault value r0949: 0 (most often observed on first occurrence; sub-index pointers appear in later attempts to access the EEPROM)

The fault is functionally identical to the message documented for the SINAMICS S210 / SIMOTICS S-1FK2 drive family (Siemens support ID 109771824), because the SINAMICS firmware uses a common power-unit interface and a common EEPROM read path across the S120, S210, G120, and similar SINAMICS platforms.

2. Affected Hardware and Part Numbers

The fault applies to any SINAMICS power module that contains the dual-memory identification circuit. Practical part numbers where the fault has been observed in the field:

Inside every active and basic line module, the power unit carries two memories on a small PCB stacked to the IGBT power board:

3. Fault Code F30052 Definition

Per the official SINAMICS S210 / SIMOTICS S-1FK2 list of fault and warning messages, the definition is fixed across firmware versions and is the same message class carried over into the S120 Booksize platform:

Source: Siemens Support entry 109771824 - SINAMICS S210 / SIMOTICS S-1FK2, F30052 EEPROM data error.

The same fault class is published in the SINAMICS S120/S150 List Manual (LH1) section "Faults and warnings - Power unit", where r0949 = 0 indicates the firmware could not even decode a sub-index; r0949 > 0 indicates the sub-record index where the checksum or CRC mismatch was detected.

4. Memory Architecture Inside the BLM

The Basic Line Module contains three functional blocks in the data path used for identification:

1. Power unit (IGBT/diode power board). Holds the 24C16W EEPROM and the 25P80V serial flash. Data written here is the only source of truth for the BLM's electrical personality (calibration, current sensor scaling, IGBT gate timing, firmware identification string, serial number, MLFB, hardware revision).
2. CPU / control board. A small microcontroller reads the two memories in sequence during power-up. The 24C16W is read first; if its checksum is valid, the 25P80V is read and a CRC comparison is performed. If both pass, the BLM enters normal operation. If either fails, the firmware issues F30052 and parks the DO in start-up.
3. Control Unit / drive controller. On S120 platforms, the external Control Unit (CU320-2, CU310-2) can re-write the on-board memories only when the BLM is in a special service state. On S210, the controller is integrated and uses the same service path.

The EEPROM and the flash are connected to the CPU board via a small flex or pin header that is often covered by a protective compound. This is the mechanical detail that catches first-time technicians: the 24C16W on the IGBT power board exists and may read correctly with a clip-on I2C programmer, but the fault is generated by the on-board CPU's own read cycle, not by a tool reading the memory externally.

5. Root Cause Analysis

F30052 is not a single failure mode. Each of the following conditions can produce the fault, and each requires a different corrective action:

The most common production-floor scenario is a 24 V interruption during a firmware update. A second common case is module swap without re-loading the Power Stack Data; in that case r0949 is non-zero and the operator sees an additional F01300 / F30001 / F30002 class fault on top of F30052.

6. Diagnostic Procedure

Follow this sequence before any repair decision is made. All steps assume the BLM is in a safe state, the line voltage is locked out, and the 24 V control supply can be cycled.

1. Capture r0949 and the fault buffer. From the active Control Unit (S120) or from the S210 web server / Startdrive, read r0945, r0946, r0947, r0948, r0949 for the BLM DO. The 32-bit fault value breaks down as 0xmmiisscc where mm=module, ii=record index, ss=sub-record, cc=CRC status. A pure 0 means "no sub-record decoded".
2. Read r2125 and r0944. r2125 holds the alarm history, r0944 holds the buffer counter. Multiple consecutive F30052 entries with the same r0949 confirm a deterministic storage corruption, not a contact issue.
3. Power-cycle the 24 V control supply three times. Wait at least 30 s between cycles so the on-board CPU runs its full read sequence. If the fault clears, log the event and update the maintenance record; if it persists, proceed.
4. Re-load firmware with STARTER / Startdrive. Connect to the Control Unit, place the BLM DO online, and use "Load firmware to drive object" with the matching firmware version from the Siemens support download portal. The tool will attempt to refresh the on-board memories; monitor r3996 for a successful transfer.
5. If the firmware load does not clear the fault, escalate to Power Stack Data reload. This is a Siemens-authorized service action. The technician uses the Siemens Service Tool (SST) or a regional service laptop with the right service account to push the correct Power Stack Data image into the 25P80V serial flash and the 24C16W EEPROM.
6. Read the on-board memories externally (optional, for documentation only). Using a clip-on I2C/SPI programmer and the BLM top cover removed, dump both memories. Compare the 25P80V image to a known-good image of the same MLFB. This data is useful for root-cause reporting but is not a substitute for the SST-based re-flash, because the on-board CPU's read sequence is what the firmware will trust.

7. Power Stack Data and Memory Roles

Each SINAMICS power module carries a record called the Power Stack Data (PSD). The PSD contains:

• MLFB and serial number
• Hardware and software revision of the power board
• Calibration constants for current sensors and DC-link voltage divider
• IGBT gate-drive timing and derating tables
• Checksum / CRC values for both the 24C16W EEPROM and the 25P80V flash

The Control Unit uses the PSD to recognize the connected power module, to set the correct current and voltage limits, and to enable the correct thermal model. If the PSD is missing or invalid, the firmware cannot pass the "module identification" gate and the drive object stays in start-up, surfacing F30052.

On the 6SL3130-1TE31-0AA0 Booksize BLM, the PSD layout is:

The 25P80V is the authoritative copy. The 24C16W acts as a fast-read header so the firmware can decide early whether to proceed with the full SPI read. If the 24C16W is readable from outside but the BLM still raises F30052, the corruption is almost always in the 25P80V image or in the on-board CPU's read path.

8. Corrective Action Options

There are three legitimate paths. Pick based on the situation:

1. Authorized re-flash (preferred). Siemens service uses the Service Tool to load the correct PSD into the 25P80V and 24C16W. The BLM stays in the cabinet. Typical turnaround is on-site, in less than an hour once the service engineer is on site with the right account and a 24 V supply.
2. Module replacement (fallback). When the 24C16W is electrically damaged (ESD, over-voltage on 24 V) or when the on-board CPU's read path is faulty, the only correct action is to replace the BLM. A replacement BLM is delivered with the PSD already loaded, but the Control Unit will still run a verification read at first power-up.
3. Firmware re-load from STARTER / Startdrive (recovery attempt). If the corruption is on a record that STARTER can rewrite, a controlled firmware load through the standard tool can recover the BLM. This is the same path used for routine updates and it writes the PSD image again. It is the cheapest option when it works.

Any attempt to swap the 24C16W EEPROM with a hand-written image sourced from a different unit of the same MLFB is not a sanctioned procedure. The PSD is calibrated to the specific power board's current sensors; a wrong PSD will either re-trigger F30052 or, worse, allow operation with wrong current limits, which is a safety hazard.

9. Step-by-Step Repair Workflow

1. Lock out and tag out. Open the line contactor, verify zero voltage on the line side with a CAT IV meter, and disconnect the 24 V control supply to the BLM.
2. Wait for DC-link discharge. The S120 Booksize BLM has internal discharge resistors; wait the time printed on the front label (typically 5 min for the 10 kW unit) before opening the cabinet.
3. Document the fault buffer. From the Control Unit's web server or Startdrive, save the diagnostic buffer of the BLM DO. Record r0945-r0949 for every F30052 entry. This file is required for the service report.
4. Attempt firmware re-load. With the BLM in start-up, connect STARTER or Startdrive to the Control Unit. Use the firmware loader to push the firmware version that matches the rest of the cabinet. Do not interrupt the write. A green "load successful" and a re-read of the fault buffer should show F30052 cleared.
5. If the firmware re-load does not clear F30052, request Siemens service. Provide the service engineer with: the cabinet serial, the BLM MLFB and serial, the firmware version on the Control Unit, the diagnostic buffer export, and the r0949 value at first occurrence.
6. Authorized re-flash. The Siemens service engineer connects with the Service Tool, identifies the BLM, selects the matching PSD from the secure Siemens image database, and writes it to the 25P80V and 24C16W. The tool verifies the CRC after each block.
7. Functional test. Run the pre-charge, close the line contactor, verify the DC-link voltage reaches the expected value (for 400 V line, DC link is approximately 540-600 V no-load; for 480 V line, 650-720 V no-load; for the 6SL3130-1TE31-0AA0 the rated DC link is 600 V at 400 V line). Verify the BLM status word shows "Run" and that F30052 is no longer present in the buffer.
8. Restore production. Enable the connected motor modules and run the system back to process.

10. Verification and Commissioning

After the corrective action, the following checks confirm a clean repair:

11. Related Fault Codes

F30052 is one of a family of EEPROM / power-unit identification faults. Knowing the neighbours speeds up diagnosis:

12. Field-Proven Notes and Safety

• Never trust an external read of the 24C16W. The fault originates in the on-board CPU's read of the 25P80V flash. A clip-on I2C read of the EEPROM is useful for root-cause documentation only.
• Do not hot-plug the 24 V supply. A clean power-up is required for the firmware to finish its identification sequence. A marginal 24 V supply that dips below 21 V during the 25P80V read can re-trigger F30052 on a unit that was just re-flashed.
• Match firmware versions. A PSD written by an older firmware version is rejected by a newer firmware, and vice versa. Always re-load the PSD with the firmware version installed on the Control Unit.
• Document the MLFB before swapping. The PSD is keyed to the MLFB on the nameplate. When you replace a BLM, capture the nameplate data and the firmware version. The new unit is delivered with a generic PSD that STARTER / Startdrive will overwrite with the correct image after the first online connection.
• Service availability. Where local Siemens service is not available, contact the regional Siemens support organization through the official portal at support.industry.siemens.com to schedule a re-flash visit. Third-party tooling cannot replace the authorized PSD image database.
• Safety on the G-120 variant. The same fault on a SINAMICS G-120 (CU240E-2 + PM240) follows the same root-cause and corrective-action pattern. The PM240 Power Module is the field-replaceable part, and the PSD is written into the PM240's internal EEPROM from the Control Unit at first power-up.

13. Frequently Asked Questions