Scope of this technical record
Step-by-step field-circuit workflow for F005 cases that need field supply, winding, feedback and CUD1 evidence separated.
Do not use run attempts as field proof. De-energize and verify the field and armature circuits before physical checks.
Workflow goal
The goal is to classify F005 as a field supply, field winding, field feedback, CUD1 interpretation, electronics-supply or modernization case. Each conclusion requires evidence; none should be assumed from the code alone.
Result package
A complete field package includes type code, fault value, motor field nameplate, field fuse state, field supply source, F+ / F- wiring, field current evidence, PMU/CUD1 stability and any recent cabinet work.
Field record checklist
- Fault value
- Field supply
- Field fuse
- Field winding
- Field feedback
- CUD1 stability
Technical basis and reference documents
This is an independent editorial technical reference. Original manufacturer documentation remains controlling for installation, repair and commissioning decisions.
Used to verify that 6RA70 fault work should preserve the fault value and separate CUD1 / power-interface evidence from field and armature circuit evidence.
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
F005 should be handled as a field-circuit evidence route. The case can involve the motor field winding, field fuse, field supply, field current feedback, field-weakening configuration, a field connector or a CUD1 / power-interface interpretation problem. It is not enough to reset the drive or replace the control board from the panel message alone.
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.
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.
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