Resolving F06200, A06205, F06210 on Parallel SINAMICS S120 ALM

Problem Overview

Intermittent startup faults on parallel SINAMICS S120 Active Line Modules (ALM) controlled by a single Control Unit CU320 are among the most challenging diagnostics in high-power drives. The classic case is a 3 × 1200 kW, 690 V ALM rack in parallel — each line module fronted by its own Active Interface Module (AIM) — which develops an inconsistent set of infeed faults during precharge or within the first second of pulse enable. The fault set typically includes F06200 (Infeed: one or several line phases failed), A06205 (Infeed: voltage dip in at least one line phase), F06210 (Infeed: summation current too high), and occasionally F05051 (Drive: line contactor feedback signal). The faults appear in the precharge-to-closing transition, succeed on retry, and disappear after the 24 V electronics supply is removed and re-applied for at least an hour. This signature — cyclical recurrence, dependence on thermal state, and successful individual module start — almost always points to one of three causes: a marginal VSM/PLL synchronization mismatch, a transient DC-link ground fault, or a current-sensor/channel consistency problem internal to one of the three line modules.

This technical reference walks through the diagnostic logic the SINAMICS S120 List Manual (LH1) defines for each fault, the parameter adjustments that reveal the root cause without power cycling, and the practical inspection order that resolves intermittent F06200/A06205/F06210 in a 3-parallel AIM+ALM configuration. Parameter numbers follow the SINAMICS S120 List Manual parameter mapping. Refer to the SINAMICS S120 Function Manual (FH1) for functional descriptions of the line synchronization and active line filter control loops.

System Configuration: 3 × 1200 kW AIM+ALM on a Single CU320

The system under analysis is a SINAMICS S120 Chassis line-up in which three Active Line Modules are connected in parallel on a common DC bus, each preceded by its own Active Interface Module. The drive object hierarchy under a single CU320 is:

• Drive Object 1: Active Line Module 1 (p0107 = 11)
• Drive Object 2: Active Line Module 2 (p0107 = 11)
• Drive Object 3: Active Line Module 3 (p0107 = 11)
• Drive Objects 4–N: Motor Modules (downstream inverters)

For 690 V / 1200 kW class, the relevant SINAMICS S120 Chassis units are from the 6SL3310-1GE series (ALM, see the SINAMICS S120 Chassis Power Units Manual) and 6SL3300-7TE series (AIM). Each ALM is rated for a continuous line current of approximately 1080 A at the 1200 kW / 690 V frame; three in parallel produce 3240 A of line current. The line-side apparent power is:

S = √3 × V_LL × I_L = √3 × 690 V × 3240 A ≈ 3.87 MVA

The common DC-link is regulated to approximately 1130 V (≈ 1.41 × 690 × 1.04, including 4% line overvoltage allowance). The AIM integrates the line filter, precharge circuit, and Voltage Sensing Module (VSM10) interface. An external VSM10 module (catalog 6SL3055-0AA00-5AA3) is required to provide the line voltage feedback used for the active line filter regulation and PLL synchronization. Refer to the SINAMICS S120 Getting Started and the SINAMICS S120 Commissioning Manual for canonical commissioning flow.

Three elements in this configuration define startup behavior:

1. VSM10 phase assignment (L1, L2, L3) versus the ALM power connections. A swap — even on one phase — causes the PLL to fail immediately on power-up because the line angle cannot be reconstructed.
2. Precharge path. Each AIM contains its own precharge resistors and contactor; the line contactor (KM1) feedback is monitored via digital inputs on the CIM and reported as F05051 if the contactor closes after a timeout or fails to open.
3. DC-link current summing path. Parallel ALMs share a common DC bus and a current-balancing network; a phase-loss in one of the three units produces a current imbalance that, if not averaged, manifests as F06210.

Fault Code Reference and Cause Mapping

Each fault in the cluster has a distinct meaning and a distinct line in the SINAMICS S120 List Manual fault cause table. Treat them as a chain, not as alternatives.

The fault progression in the field case is: line voltage momentarily out of spec (A06205) → PLL loss or phase-loss detect (F06200) → summation current spikes during the asymmetric transition (F06210) → contactor feedback anomaly if the KM1 drops during the event (F05051). The reverse progression is also possible if the root cause is a contactor/connector problem rather than a line-quality issue.

Root Cause Analysis: Why the Faults Are Intermittent

The diagnostic clue is the operating envelope, not the fault text. Three envelope characteristics narrow the root cause:

1. All three ALMs start individually without fault. This rules out a single power-unit hardware defect that would trip deterministically on every start. It points to a system-level coupling effect: shared DC-link, shared VSM, shared grounding, or a marginal interface connector.
2. Success depends on previous thermal state. The 1-hour cool-down and electronics-reset cure suggests a thermal-mechanical issue (expansion, cold solder joint, capacitor charge migration) rather than a hard short. Tighten the suspect: connector backplane pins, VSM terminal screws, DRIVE-CLiQ connectors, and the DC-link busbar torque.
3. Parallel-mode failures only. The pattern repeats only when all three ALM are ramped together. A PLL issue with one ALM's VSM would also appear individually. A current-sensor imbalance would appear in all parallel operations. The leading candidates are therefore: (a) VSM phase assignment (system-level, all 3 ALMs see it through the master VSM), (b) DC-link ground fault that is loaded by the parallel current, (c) contactor/connector wear on the KM1 line side that fails under inrush.

VSM10 and PLL Synchronization Diagnostics

The VSM10 (6SL3055-0AA00-5AA3) feeds the ALM control the three line voltages used for: (1) PLL synchronization to the grid angle, (2) line-voltage feedforward in the active line filter current controller, and (3) the symmetry check that produces F06200. A wrong VSM phase assignment produces a deterministic, immediate F06200; a loose VSM terminal produces an intermittent, thermal-dependent F06200. Distinguish the two with the parameter set below.

If the three r346x values are within 5% of r0025 and p3472–p3474 match the physical wiring, the VSM is not the cause. If one phase deviates by 10–20%, retorque the VSM terminals (typical torque 2.5 Nm on Phoenix-style spring or 4 Nm on screw-type) and re-test. If a phase is missing entirely (r346x = 0), check the VSM fuse (0.5 A fast-blow on the VSM10 input board) and the wiring from the line side to the VSM terminal block.

DC-Link Summation Current and Ground Fault Analysis

F06210 originates in the ALM firmware's instantaneous current balancing. In a healthy 3-phase system, the vector sum of three balanced phase currents is zero. The firmware computes the scalar sum |I_u| + |I_v| + |I_w| and compares to a derived threshold. Three conditions can produce a non-zero scalar sum:

1. Real current measurement error in one ALM (DCCT sensor drift, connector, ribbon cable, or current-sensor supply failure). Disconnect one ALM at a time by switching off its DRIVE-CLiQ and observe whether F06210 disappears; the suspect ALM is the one that, when removed, returns the rack to normal.
2. DC-link ground fault on the load side or the busbar. A ground fault draws current through the DC-link capacitors, and that current is reflected into the line-side scalar sum. Use an insulation monitor (Bender IR155, Eaton (formerly DOLD) IL5880, or similar) on the DC-link to localize.
3. Precharge failure. If the precharge contactor in one AIM closes late or partially, the DC-link rises asymmetrically. The three ALMs see different DC-link voltages and respond with different line currents for the same PWM state.

The ground fault threshold is set in p0287 (infeed ground fault threshold) and p0289 (ground fault delay). For a 1080 A ALM, the default ground fault detection threshold is approximately 5% of rated infeed current — that is, ≈ 54 A DC-link leakage before the firmware generates the alarm. For a 3-parallel rack at 3240 A, set p0287 to 0.03 (3%) to detect 97 A leakage events, but be aware that a too-tight threshold produces nuisance trips during DC-link charge transients.

Parameter Configuration for Infeed Monitoring

The following parameter set is the working minimum for an F06200/A06205/F06210 cluster diagnosis. Adjust p3491 only when validating a known-good system; do not raise it as a workaround because it delays the fault reaction and can mask a real PLL loss.

For parallel ALM startup, the firmware uses p0120 to define the number of power unit data sets and p0125 to activate the parallel mode. Verify all three drive objects report identical p0220, p0221, p0223 values; if one differs, the DRIVE-CLiQ connection or the CIM firmware is the suspect.

Hardware Inspection Procedure

Hardware inspection should follow the SINAMICS S120 Chassis Power Units Manual torque and inspection schedule. Items in bold are the high-probability causes for this fault cluster.

1. Torque-check the VSM10 terminal block (0.8 Nm on the Phoenix spring-cage variant; 1.2 Nm on the screw variant). A loose VSM terminal produces exactly the sporadic F06200 described here, and the cure is torque, not firmware.
2. Inspect the DRIVE-CLiQ connectors on the CIM, on the CU320, and on the VSM10. A partially engaged DRIVE-CLiQ connector produces intermittent topology loss and parameter mismatch errors that the firmware misclassifies as F06200.
3. Measure the DC-link resistance to ground with the system de-energized and the DC-link discharged. Use a megohmmeter at 500 V (for the 1130 V DC-link) to ground. Healthy: > 1 MΩ. Suspect: 100 kΩ – 1 MΩ. Failed: < 100 kΩ.
4. Inspect the KM1 main contactor for contact wear, burned poles, and low coil voltage. Use the contactor feedback wiring diagram in the cabinet manual. Replace if the contact resistance exceeds 50 mΩ per pole at 100 A DC test.
5. Check the line fuses at each AIM. Use a fuse tester (Bussmann FBT or equivalent). A high-resistance fuse produces exactly the line-voltage dip pattern that triggers A06205/F06200.
6. Verify the commutation reactor in each AIM (the L1, L2, L3 filter inductors). Measure the inductance at 100 Hz, 1 A; it should be within ±10% of nameplate (typically 0.18–0.4 mH for 1200 kW / 690 V class). A shorted turn in one inductor produces the exact A06205/F06200 pattern under parallel load.
7. Check the ribbon cable from the CIM to the power unit. A partially engaged ribbon cable produces F06210 by corrupting the current-sensor signal. Inspect for pin damage, oxidation, and correct locking.
8. Verify the 24 V power supply to the CU320, the CIMs, and the VSM10 holds at 24.0 V ±0.5 V under full load. A droop of 0.5 V on the 24 V bus during contactor closure produces both F05051 and the A06205 cluster.

Firmware and Control Board Considerations

Firmware version 2.6.2 on the CIM+IPD control interface board (CIM = Control Interface Module, IPD = Infeed Power module Detection) is an early-generation SINAMICS S120 firmware branch. The current production firmware is in the V5.x line. Two firmware-related actions are warranted before declaring a hardware fault:

1. Check Siemens Product Support for the specific firmware 2.6.2 hotfixes. The S120 firmware branch has had several updates that specifically address parallel ALM behavior, PLL behavior with VSM10, and DC-link summation current thresholds. Search the Siemens support database for the exact firmware version of the CIM and the CU320.
2. Update the CU320 firmware to the matching production line for the hardware version. Do not mix CIM firmware versions across the 3 ALMs — the parallel-mode current-sharing algorithm requires identical firmware on all three drive objects.

A common scenario in field service is a partial firmware update: the CU320 was updated but one or two CIMs were left at 2.6.2. The mixed-firmware state produces exactly the symptoms described: occasional PLL loss, summation current spike, and a fault pattern that is not deterministic. Use STARTER or the SIMOTION SCOUT (depending on the higher-level controller) to verify all three CIMs are at the same firmware version and that the firmware matches the CU320's expected feature set.

If a firmware update is not feasible, the next-best action is to use p3491 (infeed line filter monitoring time) to extend the line monitoring window from 4 ms to 10 ms as a diagnostic tool only. This does not fix the root cause but it converts an immediate-trip fault into a captured-log condition that records r0089, r0078, and r0066 at the moment of the trip. Capture the trip data, then restore p3491 to 4 ms before re-commissioning for production.

Step-by-Step Diagnostic Procedure

The procedure below resolves the F06200 / A06205 / F06210 cluster for 3-parallel AIM+ALM systems. It is ordered by cost and time: hardware checks first, parameter validation second, firmware last.

1. Capture the alarm buffer at the moment of fault. Use STARTER to read r0945 (fault code), r0949 (fault value), and r2123 (alarm value). The fault value r0949 for F06200 identifies the line phase that failed; for A06205 the r2123 value gives the actual line voltage at the dip.
2. Verify the line supply with a power-quality analyzer (Fluke 435, Dranetz HDPQ, or Hioki PW3198) for at least one full operating cycle. Look for: (a) voltage unbalance > 2%, (b) individual phase dip > 10% lasting > 10 ms, (c) harmonic distortion (THD) > 5%, (d) flicker Pst > 1.0. Any of these will trip A06205 and F06200 in a 690 V class ALM.
3. Isolate the ALM rack from the load. Open the DC-link contactor or pull the DRIVE-CLiQ to the Motor Modules. Re-attempt a start. If the ALMs start cleanly without F06210, the cause is load-side (motor cable ground fault, Motor Module IGBT failure, or downstream 24 V droop). Continue diagnosis on the load.
4. Start each ALM individually in turn, with the other two DRIVE-CLiQ ports disabled. If all three start individually, the issue is parallel-mode-specific (current sharing, VSM assignment, or shared DC-link). Continue.
5. Check the VSM10 phase assignment with r3472, r3473, r3474. Compare with the physical wiring diagram. Verify r3460, r3461, r3462 against r0025. If mismatch, retorque and re-test.
6. Measure the DC-link to ground with a megohmmeter. If below 1 MΩ, isolate the busbar and re-measure the load side versus the line side to localize the ground fault.
7. Inspect the commutation reactor and fuses in each AIM per the hardware inspection list above.
8. Verify the line contactor feedback at the CIM digital inputs. The KM1 auxiliary contact must close within p0860 (default 100 ms) of the close command; if not, F05051 precedes the infeed faults.
9. Check the 24 V power supply to the CU320, all three CIMs, and the VSM10 under full load. A 0.5 V droop is enough to corrupt the VSM ADC and produce intermittent A06205.
10. Compare firmware versions across the three CIMs. Mixed versions cause parallel-mode instability.

Verification and Commissioning

After the root cause is identified and corrected, re-commission the rack with the following checks recorded in the project folder:

1. All three ALMs start and run in parallel without fault for at least 30 minutes at 50% load, then 30 minutes at 100% load. Monitor r0089 and r0078 on all three drive objects; the current-sharing error between ALMs should be within ±5%.
2. DC-link voltage holds at the configured setpoint ± 2% under steady-state load. The default for 690 V line is 1130 V DC-link; verify r0085 (DC-link voltage actual) is within tolerance.
3. Line current per ALM is within ±5% of the expected 1080 A at full load (3 × 1080 = 3240 A total). Asymmetry above 5% indicates a current sensor drift in one ALM.
4. Line voltage at the AIM input is within IEC 61800-2 Class A tolerance: 690 V ± 10% steady-state, ± 15% transient for < 10 ms.
5. KM1 contactor feedback closes within p0860 (100–250 ms) and opens within the same window on stop. Verify the digital input state in r0722 (CU320 digital inputs status).

If any of the above fails, the rack is not yet ready for production. Re-enter the diagnostic procedure at the step that produced the first failure.