Scope of this technical record
Series-level route for SIMOREG 6RA70 DC MASTER service cases involving field supply, armature current, no-display electronics, optimization runs, speed feedback and donor-board decisions.
Qualified DC-drive personnel only. A SIMOREG DC drive includes hazardous line, armature and field circuits. Isolate, lock out and verify safe state before internal checks or board removal.
SIMOREG 6RA70 optimization and feedback route
Use the symptom to choose the first route
A 6RA70 service case should not start by changing a CUD1 board. The first route depends on what the machine shows: field failure, armature current trip, dead electronics, failed optimization, unstable speed feedback or a parameter-memory problem after a board change.
The series hub now keeps those routes separate. Field and armature problems are power-circuit evidence routes; no-display cases start with electronics supply; F050 and F051 need commissioning and memory evidence; speed instability needs feedback proof before controller tuning.
First route selector
| Observed case | Start with | Do not jump directly to |
|---|---|---|
| F005 field circuit | Field supply, field fuse, field winding and feedback | CUD1 replacement |
| F030 / armature current | Armature fuse, load, field proof and firing path | Thyristor bridge replacement |
| No display / PMU dark | Electronics supply and CUD1 boot evidence | Fault-code lookup |
| F050 during optimization | Run type, fault value, motor data, current-loop preparation and load state | Speed controller tuning |
| F051 / optimization refused | Parameter access, permanent memory and donor-board context | Power-stage repair |
| Unstable tachometer / encoder | Feedback source, polarity, scaling, wiring and coupling | Controller gain changes |
Why optimization faults need service evidence
Optimization runs deliberately move the converter through commissioning states. A failed run can be caused by motor data, current-loop preparation, field proof, load torque, feedback scaling or memory state. Treat the fault value and the run type as service evidence, not as a simple replacement instruction.
For older machines, the largest risk is losing the original parameter context. Before any donor CUD1 or restored parameter set is used, preserve type code, motor data, feedback source and the existing parameter state whenever possible.
Field record checklist
- 6RA70 type code
- CUD1 / PMU state
- P051 / P052 run type
- Fault value
- Motor armature and field data
- Feedback source
- Parameter backup
- Machine load / brake state
Technical basis and reference documents
This is an independent editorial technical reference. Original manufacturer documentation remains controlling for installation, repair and commissioning decisions.
OEM troubleshooting reference for 6RA70 fault values, tachometer checks, CUD1 / power-interface context and optimization-run faults.
Base operating and commissioning context for SIMOREG DC-MASTER converters, parameterization and speed-sensing setup.
Model records
6RA70 DC MASTER converters supply a DC motor armature and field from a three-phase AC supply. Service decisions usually need the fault value, parameter set, optimization-run state, selected feedback source, field architecture, armature circuit, CUD1 control electronics and power-interface / firing path to be separated.
6RA70 DC MASTER converters supply a DC motor armature and field from a three-phase AC supply. Service decisions usually need the fault value, the selected operating state, the field architecture, the armature circuit, CUD1 control electronics and the power-interface / firing path to be separated.
Fault records
The SIMOREG 6RA70 reports F050 during a selected optimization run, often while commissioning, after a motor change, after parameter restoration or during speed-controller / current-controller tuning work.
The drive refuses or cannot complete an optimization run because parameter write access, operating state, memory handling, commissioning sequence or setup conditions are not ready.
The 6RA70 becomes unstable, overspeeds, hunts, fails speed optimization, reports speed-feedback-related behavior, or runs differently after tachometer, encoder, motor or CUD1 work.
The 6RA70 reports F005 during enable, run-up or field build-up, or the DC motor field chain cannot be confirmed even though the armature converter electronics appear alive.
The 6RA70 reports F030 during current build-up, load application, reversing, acceleration, or after mechanical or armature-circuit disturbance.
The SIMOREG PMU or operator interface is dark, resets, shows unreliable status, or the converter cannot preserve a useful diagnostic state after power-up.
Board and assembly records
Collects the evidence needed before changing speed-feedback hardware, rerunning optimization, installing donor CUD1 hardware or modernizing a SIMOREG 6RA70 DC drive.
Collects the evidence needed before CUD1, power-interface, thyristor firing or donor-converter decisions on SIMOREG 6RA70 field, armature-current and no-display cases.
Circuit and diagnostic records
Maps F050-style optimization failures through selected run type, commissioning order, motor data, armature current build-up, field proof, load isolation and feedback credibility before a control-board decision.
Separates speed-feedback instability into selected feedback source, analog tachometer polarity and voltage, encoder pulse evidence, wiring, shielding, mechanical coupling and CUD1 feedback input boundaries.
Maps F051-style optimization setup problems and donor-board cases through parameter access, permanent memory, parameter backup, PMU access, electronics stability and CUD1 replacement evidence.
Routes F005 cases from the selected motor field and field supply through fuses, F+ / F- wiring, field-current feedback and CUD1 interpretation before a control or interface board is blamed.
Maps F030 and current build-up failures through armature fuse, contactor, motor armature circuit, thyristor bridge, firing path, current feedback and field proof before power-interface decisions.
Separates a no-display or reset-loop 6RA70 case into cabinet supply, electronics supply, CUD1 boot state, PMU/interface path, downstream loading and power-interface loading evidence.
SIMOREG 6RA70 fails, refuses or interrupts an optimization run during commissioning, motor replacement, parameter restore or feedback work.
The DC motor hunts, overspeeds, fails speed optimization, shows unreliable actual speed or behaves differently after tachometer, encoder, motor or control-board work.
The 6RA70 cannot save commissioning data, refuses optimization, has unknown parameters after a board change, or arrives with a donor CUD1 / power-interface history.
SIMOREG 6RA70 reports F005 or cannot prove the selected DC motor field circuit.
6RA70 reports F030, trips on armature current build-up, or indicates commutation / current behavior that cannot be explained from the panel alone.
The PMU/operator interface is dark, flickers, resets, or the converter cannot provide stable diagnostic access.
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