Troubleshooting SINAMICS G120 F01601 Startup Error After Power

1. Problem Overview

A SINAMICS G120 drive (in this case, 0.37 kW FSA frame) trips into a non-acknowledgeable fault state immediately after a controlled mains re-energization. The BOP-2/IOP shows F01601 (system startup error), and the drive does not auto-recover when the other units on the same supply come back online. The fault value cannot be cleared through a normal OFF1->ON command or by toggling the ON/OFF1 terminal. A full Control Unit (CU) power cycle is required to bring the drive back, and the same root cause has previously destroyed two higher-rated SINAMICS units on the same panel during brown-out / fluctuation events.

This is a post-mains-event failure mode. It is not a random hardware mortality issue, and it is almost always traceable to one of three families:

1. Loss or corruption of the internal handshake between the Control Unit (CU) and the Power Module (PM) during the inrush transient.
2. EMC / burst transients on the DC-link or 24 V supply rail that breach the CU boot-ROM's tolerance window.
3. Mechanical seating degradation of the CU-PM docking connector or the operator-panel ribbon, producing intermittent contact only when thermal/expansion cycles stress the joint during a cold re-start.

2. SINAMICS G120 Modular Architecture Reference

The G120 is a two-piece (or three-piece with operator panel) modular drive. Understanding which sub-assembly is reporting the fault is the first step in any F01601 investigation.

The CU and PM communicate over a high-speed internal serial interface (the docking connector at the rear of the CU, sometimes called the PM-IF). The CU cannot complete its boot if this interface fails to enumerate, and the firmware will raise a startup-error class fault - F01601 sits in this family.

Power range coverage for the SINAMICS G120 family extends from 0.55 kW to 250 kW (0.75 to 400 hp) as documented in the SINAMICS G120 product brochure. The 0.37 kW unit in the field case is the lower-edge variant and is identical in fault architecture to the rest of the family.

3. Understanding F01601 - System Startup Error

F01601 in the SINAMICS G120 fault list is classified as a Control Unit system startup error. It indicates that the CU's bootloader or main firmware image did not complete its initialization sequence after a power-on reset (POR). The drive transitions to a state where the inverter is inhibited, the relay outputs are de-energized, and the fault is non-acknowledgeable by a standard OFF1-ON cycle; only a hard power-down/power-up of the CU will clear it.

3.1 Fault value (r0949) and additional info (r2122)

Before clearing the fault, always read out and record:

• r0947[0...63] - Fault code (should read 1601 decimal / 0x0641).
• r0949[0...63] - Fault value. This is the most diagnostic parameter. It identifies the specific sub-routine that failed:

• r2122[0...63] - Additional fault information (complement to r0949).
• r2124[0...63] - Alarm text index, useful for cross-referencing to the Siemens List Manual.

4. Root Cause Analysis for Mains-Loss-Induced F01601

Four primary mechanisms are observed in field returns on the 0.37 kW to 7.5 kW range:

4.1 Inrush transients exceeding CU POR threshold

When a panel is re-energized, multiple drives and contactors draw inrush simultaneously. The resulting DC-bus voltage on the PM can overshoot or dip outside the CU's POR window for several tens of milliseconds. If the CU's internal supervisor sees a brown-out during the boot-loader stage, it raises F01601 to prevent the firmware from running on unstable rails.

4.2 EMC burst on the 24 V control supply

If the same 24 V DC rail feeds the CU terminals (1, 2 on most CU240 variants) and external relays, a high di/dt event on the panel mains (e.g., a DOL starter closing) can couple into the 24 V line. The CU's POR circuitry can interpret this as a corrupted boot signal.

4.3 Mechanical seating degradation

FSA-FSD frames dock the CU onto the PM with a high-density connector. Repeated thermal cycling (the case in the field report - drive had been running, was shut down, then started again) loosens the connector retention force. Under re-start, the contact resistance can spike, breaking the PM-IF link and triggering the F01601 startup error.

4.4 Corrupted parameter memory (EEPROM/SD)

An uncontrolled power-down during a parameter save (e.g., a copy-to-CU operation that was in progress when the mains was removed) can leave the parameter image inconsistent. The next boot will fail consistency checks and raise F01601.

5. Pre-Diagnostic Safety and Prerequisites

Prerequisites for the diagnostic procedure below:

• Locked-out and tagged-out mains supply to the affected panel (LOTO procedure complete).
• 5-minute capacitor discharge wait observed.
• STARTER V5.x, Startdrive V15+, or TIA Portal V15+ installed on a PC with a USB-to-MINI-USB or Ethernet cable to the CU's service port (X127 on CU230P-2 / CU240E-2 / CU250S-2).
• Drive's parameter backup (if available) from the most recent commissioning.
• Access to the G120 List Manual for firmware-specific r0949 decoding.

6. Step-by-Step Diagnostic Procedure

1. Capture the fault buffer before any reset attempt. Connect to the CU service port, go online, and read r0947, r0949, r2122, r2124 into a log. Note the firmware version (r0018) and the CU and PM article numbers (r0203, r0200).
2. Attempt a soft acknowledge. Issue a standard fault acknowledge on the CU (P2103 = 1, then trigger, or via the operator panel OK button). If F01601 does not clear, the fault is in the non-acknowledgeable class and a hardware reset is mandatory.
3. Power-cycle the CU only, not the PM. Where possible (panel with line contactor), drop the control 24 V to the CU and re-apply. If the drive recovers, the fault was an EMC/brown-out event on the 24 V rail.
4. Power-cycle the complete drive. Remove mains for at least 60 s (to ensure full DC-link discharge), then re-apply. If the drive recovers, log the incident and proceed to Section 7 (preventive).
5. Inspect the CU-PM docking connector. With mains isolated and capacitors discharged, remove the CU from the PM. Inspect both halves of the docking connector for:

• Bent or recessed pins (common after multiple re-seatings).
• Oxidation or arc-tracking on contact surfaces.
• Foreign debris (PCB dust from a panel that was drilled nearby).

6. Re-seat the CU with firm, even pressure. Confirm the two captive screws (or snap-latch on smaller frames) are fully engaged. Do not exceed the recommended torque on the screw-type retention (typical 0.8 Nm).
7. Power up and observe the boot sequence. On a healthy boot, the operator panel will cycle through the firmware version splash, the drive name, and settle on the operating screen within 3-5 s. A re-occurrence of F01601 with the same r0949 value indicates the docking connector is the dominant fault domain.
8. Check the SD card (if fitted). Remove the SD card and boot the drive from internal memory. If the drive boots clean, the SD card clone is corrupted and must be re-created from a known-good backup.
9. Verify internal supply rails. Using STARTER/Startdrive online, read r0025 (DC-link voltage) and the CU's internal 3.3 V/5 V rail monitors (firmware-version dependent; consult the List Manual). A sagging 3.3 V rail during boot points to a failing CU.
10. Decouple from shared panel loads. If the fault only re-occurs when the panel is brought up under load (e.g., DOL starters closing simultaneously), the panel sequence must be staged - see Section 10.

7. Recovery and Reset Procedures

7.1 Hard reset of the Control Unit

1. Open the line contactor / main breaker to the PM.
2. Wait 5 minutes for DC-link discharge.
3. Remove the 24 V supply to the CU (terminals 1 and 2) if it is fed from a separate rail.
4. Wait an additional 30 s.
5. Re-apply 24 V, then re-apply line voltage to the PM.

The CU will run a full Power-On Reset. The fault buffer is cleared on a successful boot.

7.2 Factory reset (only if F01601 persists after hard reset)

If the parameter image is suspected to be corrupted, perform a factory reset:

1. Set P0010 = 30 (factory settings).
2. Set P0970 = 1 (start factory reset).
3. Wait for the CU to complete the reset (approx. 20-30 s); the drive will reboot automatically.

7.3 Firmware reload

If the factory reset does not clear F01601, the CU's internal flash image is suspect. Use STARTER/Startdrive to push a fresh firmware image to the CU over the service port. Use only firmware versions that are officially released for the CU's article number; mismatched firmware can also raise F01601.

8. Verification Testing

After recovery, run the following verification before returning the drive to production:

1. No-fault run at zero speed. Issue ON, command 0 Hz, allow 2 minutes of operation. Confirm r0025 (DC-link) is within +/- 5% of nominal, and r0027 (output current) is at no-load value.
2. Step speed test. Command 10 Hz, 25 Hz, 50 Hz in sequence with 30 s dwell at each step. Confirm current stable and no fault buffer entries.
3. Mains-cycle test. Simulate the original failure mode: turn off the panel mains for 10 minutes, then restore. Verify the drive returns to a ready state without operator intervention.
4. Fault buffer readback. Connect online, read r0945 (fault code table - last 8 faults). Confirm r0945[7] (most recent) is 0.
5. Re-seat verification. If the docking connector was the root cause, perform a second mains-cycle test without disturbing the CU seating. If F01601 re-appears, replace the CU (and the PM, since repeated docking failures stress the PM-side connector as well).

9. Related Fault Codes and Escalation Matrix

The following faults are commonly seen together with F01601 on mains-loss events and can be used to refine the root-cause diagnosis:

Escalation trigger: If two drives on the same panel have been lost to F01601 / companion faults within the warranty window, the panel's mains quality, not the individual drive, is the root cause. Engage the panel builder / facility electrical engineer for a power-quality audit before installing the next replacement drive.

10. Preventive Measures and Power Quality

10.1 Line-side hardening

• Install a Siemens line reactor sized to the drive's kW rating on the input of each PM. For 0.37 kW, this is typically a 4EM6100-3CB00-class or equivalent compact reactor. This reduces the inrush di/dt the PM sees during simultaneous panel energization.
• Add a surge arrester (Type 2, 40 kA) to the panel incoming supply to clamp lightning-induced and switching transients.
• Stage the panel's mains-on sequence so that the drives are energized before (or at least simultaneously with, but not after) the DOL starters. A 100-200 ms time delay between contactor closures reduces the inrush overlap.

10.2 Control-side hardening

• Use a dedicated, regulated 24 V DC power supply (e.g., SITOP PSU100C) for the CU, isolated from the relay/contact coil rail.
• Add a TVS diode or varistor across the 24 V input to the CU if long cable runs expose it to inductive coupling.
• Verify cabinet PE bonding - chassis-to-PE resistance < 0.1 ohm, with star-point grounding to the supply PE.

10.3 Mechanical hardening

• On every scheduled maintenance, re-seat the CU and re-torque the retention screws.
• Apply a small amount of contact lubricant (e.g., Kontakt Chemie Kontakt 61) to the docking connector pins if the drive is in a high-vibration cabinet.

10.4 Power-quality audit

Install a power-quality logger (e.g., Siemens SENTRON PAC4200) at the panel incoming for at least one week of typical operation. Capture:

• Voltage sags (per SEMI F47 / ITIC curve - drives should ride through 200 ms sags down to 70% V_nominal).
• Impulsive transients (1-100 us range, > 500 V peak).
• Frequency deviation (nominal 50/60 Hz +/- 1%).

If the audit shows the panel is outside the ITIC envelope, corrective action on the upstream supply is the proper fix - not replacing the drives.

11. Specifications and Replacement Notes

For ordering a replacement CU or PM, use the article number from the unit's nameplate. Always order the latest firmware version compatible with the existing parameter set, or plan a full commissioning with a new parameter backup. The official SINAMICS G120 product page provides the current ordering-configurator links, and the G120 List Manual (separate document, accessible via Siemens Industry Online Support) is the authoritative source for the complete fault-code list including r0949 decoders for F01601.

12. FAQ