Scope of this technical record
Model-level record for SIMOREG 6RA70 DC MASTER evidence collection before optimization, feedback, CUD1, power-interface or modernization decisions.
Qualified personnel only. Verify safe state of line, armature, field and electronics circuits before access.
A 6RA70 repair package must include commissioning context
For a 6RA70, the board label alone is not enough. A useful service package includes motor armature data, field data, feedback source, parameter set, optimization state, fault value and the timing of the machine event.
This matters because a feedback or parameter problem can imitate a failed controller, while a weak field or armature-circuit issue can make optimization and current-loop behavior appear inconsistent.
Evidence before donor CUD1 or modernization
A donor CUD1 can restore a dead converter only if the parameter set, feedback scaling and field / armature assumptions match the machine. If those are unknown, the safe service decision may be parameter recovery or modernization rather than board swapping.
Field record checklist
- Type code
- Software / PMU status
- Parameter backup
- Motor data
- Field data
- Feedback source
- Fault history
- Board labels
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.
Related technical 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.
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