Diagnostic workflow

Siemens SIMOREG 6RA70 F030 Armature Firing and Current Diagnostic Workflow

Entry symptom: 6RA70 reports F030, trips on armature current build-up, or indicates commutation / current behavior that cannot be explained from the panel alone.

Diagnostic workflow9 min read

Scope of this technical record

Armature-current and firing route for F030 cases where the external armature path, field proof, thyristor bridge and current feedback need separation.

Safety boundary

Stop if the armature fuse, contactor, motor armature path or field condition is unknown. Repeated power attempts can damage the bridge or motor.

Workflow goal

F030 diagnosis should end with a service boundary: load/motor, armature fuse or contactor, field condition, thyristor bridge, firing-pulse path, current feedback, CUD1/power interface or modernization. The route is designed to avoid guessing at the board level.

Result package

The useful package includes trip timing, armature fuse status, contactor and motor evidence, field proof, bridge condition, firing connector evidence, current feedback credibility and any previous board or bridge work.

Field record checklist

  • Trip timing
  • Armature fuse
  • Field proof
  • Bridge condition
  • Firing evidence
  • Current feedback

Technical basis and reference documents

This is an independent editorial technical reference. Original manufacturer documentation remains controlling for installation, repair and commissioning decisions.

FAQ for 6RA70 DC MASTER and SIMOREG CM fault diagnosticsSiemens Industry Support

Used to verify that 6RA70 fault work should preserve the fault value and separate CUD1 / power-interface evidence from field and armature circuit evidence.

SIMOREG 6RA70 Series operating instructions and system overviewSiemens

Used to confirm the 6RA70 architecture as a three-phase AC supplied DC converter for armature and field circuits, with hazardous service boundaries around power and control electronics.

Linked records

Evidence intake

Turn this record into a qualified service request

A repair decision is much more reliable when the request includes the exact identity of the drive, the first fault evidence and the machine condition when the symptom appeared.

  • Complete drive type code / MLFB or nameplate model
  • Fault code, fault value and first event before reset
  • When the event appears: power-up, enable, ramp, run, decel or stop
  • Motor/cable connected or isolated during the symptom
  • Visible board, option-card, module and connector identifiers
  • Previous repair history, replacement parts and repeat-failure pattern
Prepare request →