Resolving Siemens 6SE70 Fault F29: Current Transducer Diagnosis

1. Overview of the 6SE70 Drive Family

The SIMOVERT MASTERDRIVES 6SE70 series is a field-proven DC-link voltage-source inverter platform used for both DC-AC (inverter) and AC-AC (converter) configurations. The drive is built around three cooperating hardware blocks:

• CUVC – the Control Unit (Voltage / Control) carrying the MCU, parameter memory, and operator panel interface.
• IVI – the current/voltage interface card that digitizes the CT feedback and DC-link voltage.
• Power Section – the IGBT stack, DC-link capacitors, and the three external current transducers (one per phase) mounted on the AC busbars.

Each phase current transducer is fed from a floating ±24 V supply derived inside the IVI card and routed through a multi-conductor harness back to the transducer head. The transducer's analogue output is a bipolar current or voltage proportional to the line current, fed back into the IVI for ADC conversion. When the control voltage is applied but the inverter is not enabled, the firmware runs a self-check of these sensing channels. A non-zero reading at this stage trips Fault F29.

2. F29 Fault Definition and Trigger Conditions

Fault F29 is logged by the 6SE70 firmware immediately after control-voltage (24 V electronics) power-up. The compendium classifies it as a "measured value sensing error." The drive performs a plausibility check on the three phase current feedback signals while the gating is inhibited and the line contactor (if present) is open. Under these conditions, the only signal that should be present is the residual offset of the transducer + IVI signal chain.

If any phase feedback exceeds the plausibility window, the firmware latches F29 and the drive refuses to start. The fault can appear:

• Immediately at switch-on (typical of a shorted transducer output stage or wiring fault).
• Within 1–10 minutes of switch-on (typical of a transducer that drifts warm, or of a marginal ±24 V supply that collapses under load).

A critical symptom: the fault is not induced by the CUVC. Exchanging the CUVC has been shown in the field to leave the fault unchanged, which is the first signal that the failure lies in the transducer chain, not the controller.

3. Fault Value r949 / r0949 Decoding

The fault is qualified by the supplementary fault value stored in parameter r949 (also referenced in later firmware revisions as r0949). The value is a bitmask that points the engineer at the offending phase or channel.

Field cases consistently fall into the r949 = 2, 3, or 4 range. When r949 = 3 is reported, the failure is not necessarily two bad transducers. It is more commonly a shared supply problem – a collapsed +24 V or −24 V rail that drags down two of the three transducers simultaneously.

4. Current Transducer Hardware Architecture

The 6SE70 family uses closed-loop (compensated) or open-loop Hall-effect current transducers mounted on the AC input or output busbars depending on configuration (AC-AC converter, DC-AC inverter, or AFE active front end). Each transducer:

1. Requires a floating ±24 V bipolar supply (typically ±24 V ±10 %, ripple < 100 mV).
2. Draws a quiescent current in the 30–60 mA range per rail (closed-loop types up to 100 mA).
3. Returns a current-mode or voltage-mode analogue signal (0 V at 0 A nominal, ±4 V or 4–20 mA at full scale) to the IVI card.

Wiring is a three-wire bundle per transducer: +24 V, −24 V, and signal (with shield/drain on a separate conductor). The three bundles from L1, L2, and L3 transducers are collected into a multi-core harness that lands on a PCB behind the electronics box, where the supply rails are distributed. The wire colour code used in the field report identifies the L2 harness conductors as pink, grey, and white (verify against the wiring diagram for the specific frame size).

5. Symptom Chain: F11 Followed by F29

A diagnostic signature observed on multiple field cases is the F11 → F29 sequence. When the offending transducer is reconnected after a successful measurement, the drive may first trip F11 (an overcurrent or measurement plausibility fault on the IVI side), and on acknowledgement then re-latch F29. This is because:

1. The IVI ADC sees a large transient offset as the transducer output stage settles.
2. The IVI latches F11 because the instantaneous current reading exceeds plausibility.
3. Once acknowledged, the self-check on the next start-up still fails because the transducer's drift behaviour is intrinsic to the device – not a one-shot transient.

The F11-then-F29 pair is a strong fingerprint of a hardware defect in the transducer itself, as opposed to a wiring-only fault that would clear on reconnect.

6. Diagnostic Procedure: Step-by-Step Isolation

Use this sequence to isolate the fault to either the transducer, the wiring harness, or the IVI card.

6.1 Confirm the Fault Value

1. Apply control voltage only (line contactor open, gating inhibited).
2. Read r949 (or r0949) on the PMU or via DriveMonitor / SIMOVIS.
3. Note whether the fault appears immediately or after a warm-up delay.

6.2 Exchange the CUVC as a Sanity Check (Optional)

If a known-good CUVC of the same firmware version is available, swap it. The fault should persist if the CUVC is not the root cause. In multiple field reports, exchanging the CUVC has not changed the F29 behaviour – this rules the controller out and is the first definitive step.

6.3 Disconnect Each Transducer in Turn

1. Lock out control voltage and confirm zero energy on the harness.
2. Disconnect the harness connector at the IVI board for the phase indicated by r949 (start with L1, then L2, then L3).
3. Restore control voltage and observe the PMU / fault buffer.
4. If F29 clears with one transducer disconnected, that transducer's signal path is the suspect – either the transducer itself, the wiring harness, or the IVI input channel.

6.4 Measure the ±24 V Supply at the Transducer Head

With the harness connected to the IVI and control voltage applied, measure +24 V to −24 V, +24 V to 0 V (analogue ground), and −24 V to 0 V at the transducer terminals.

Field readings of +0.8 V and −4.6 V on the L2 transducer (with the other two phases showing normal ±24 V) confirm a hard failure in the L2 transducer's internal regulator. The reading "moves with the device" – when the transducer is unplugged, the IVI supply returns to nominal ±24 V, isolating the load to that one device.

6.5 Cross-Check with Parameter r832

Parameter r832 displays the instantaneous measured phase currents in engineering units (A). With the inverter not enabled, the DC-link is not charged, and the line current is zero. Healthy readings are < 1 A on all three phases.

In the field case, r832 reported ~60 A on L1 and L3 with the DC-link uncharged – a clearly invalid combination that the firmware uses to latch F29. If r832 shows > 5 A on any phase with the inverter disabled, the corresponding sensing channel has an offset error.

7. Decision Matrix: Transducer, Harness, or IVI

8. Replacement Procedure

1. Lock out and tag the line supply. Wait for the DC-link to discharge to < 50 V (verify with a meter at the DC-link test points).
2. Remove the failed transducer from its busbar mount. Note the orientation arrow – most closed-loop transducers are directional.
3. Match the replacement by:
   • Primary current rating (equal to or one frame above the drive's rated output current).
   • Turns ratio (e.g., 1:1000, 1:2000, 1:3000 – verify with the frame-specific parts list).
   • Supply voltage (must be ±24 V bipolar unless the drive uses a ±15 V variant).
   • Output type (voltage mode or current mode – must match IVI input configuration).
4. Reconnect the three-wire harness (pink / grey / white for L2 in the example) and tighten the connector.
5. Restore control voltage. Verify F29 is absent and that r832 reads < 1 A on all phases with the inverter disabled.
6. Close the line contactor and run the drive in a no-load commissioning test, watching r832 for symmetry across the three phases.

9. Verification and Commissioning Checks

After replacement, perform the following verification sequence:

1. Standstill self-check – with gating inhibited, r832 must read < 1 A on all three phases. Any reading > 5 A indicates residual offset, often from a wiring shield not properly terminated at the IVI end.
2. ±24 V supply check – measure the supply at each transducer head; all three must read within ±5 % of nominal, and within 50 mV of each other.
3. No-load ramp – ramp the speed reference slowly to 10 %, 25 %, 50 %, and 100 % of nominal. Confirm r832 tracks the reference symmetrically across L1, L2, L3 within ±2 %.
4. Fault buffer clear – clear the fault history and confirm no new F29 entries are written during a 30-minute soak at zero speed.
5. Firmware / parameter integrity – confirm parameters P70 and P71 (motor and pulse encoder configuration) are correct, as the firmware uses these in conjunction with the current sensing plausibility check.

10. Related Faults and Cross-References

F29 is one of a family of measured-value plausibility faults. Knowing the neighbours helps in differential diagnosis:

For AFE (Active Front End) configurations using the same 6SE70 platform, the same F029 fault code applies. The same diagnostic flow holds, with the transducer set being on the line side rather than the motor side. The transducer failure mode, the r949 decode, and the F11-then-F029 chain are all observed in AFE units as well.

11. Spares and Preventive Recommendations

• Keep at least one spare transducer per phase current rating in the cabinet, with the wiring harness pre-built to a known-good connector pinout.
• Periodically (every 12–24 months) measure the ±24 V supply at each transducer head during a routine outage. Drift of more than 0.5 V across the three phases is a leading indicator of an imminent F29.
• On drives more than 10 years old, consider replacing all three transducers in a planned outage – they age as a cohort and the second failure often follows the first by months.
• Verify the harness shield is terminated at the IVI end only (single-point ground). Floating or double-ended shield termination is a common source of common-mode noise that can also trigger F29 in borderline cases.

12. FAQ