Scope of this technical record
Workflow for converting a 590P FIELD FAIL report into configuration, field-circuit, field-supply, feedback and repair-boundary evidence.
Do not bypass field protection. Use lockout, discharge verification and qualified test procedures before working on field or armature circuits.
590P field-fail workflow route
The workflow stops unsafe armature testing until field evidence is stable.
590P FIELD FAIL workflow
Workflow sequence
The sequence is designed to prevent a field-circuit problem from being mis-sold as a control-board failure.
590P FIELD FAIL workflow
| Step | Evidence | Decision |
|---|---|---|
| 1 | Drive type code, motor nameplate and field rating | Confirm the field circuit is required and correctly configured |
| 2 | Fault timing and field-enable state | Separate parameter/configuration issue from hardware issue |
| 3 | Field fuses, FL1/FL2 supply and F+/F- wiring | Prove external field path |
| 4 | Field voltage and field current relationship | Split missing supply from open field |
| 5 | Feedback condition after field is proven | Escalate to field feedback or control board only if justified |
| 6 | Repair history and parts availability | Choose repair, donor hardware or retrofit |
Stop conditions
The workflow stops whenever the field identity, field circuit or motor type is uncertain. It also stops if a technician wants to keep testing armature current while the field state remains unproven. That is not a useful diagnostic route; it is a risk route.
- Unknown motor field type
- Open field circuit
- No safe field measurement
- Drive repeatedly reset under armature demand
- No photos of field terminals or board labels
Field record checklist
- Type code
- Motor field data
- Field-enable state
- Fuses and terminals
- Voltage/current evidence
- Repair goal
Technical basis and reference documents
This is an independent editorial technical reference. Original manufacturer documentation remains controlling for installation, repair and commissioning decisions.
Primary product manual context for 590+ digital DC drive fault handling, safety boundaries and field/firing evidence routes.
Shows FIELD FAILED routing through field volts, external jumper positions, FL1/FL2 connection and wiring tightness before the drive is treated as failed.
A field technician case showing the real case behaviour behind mature SSD 590 Missing Pulse faults and current-waveform evidence requests.
Public support note connecting FIELD FAIL to field motor wiring, field fuses, field resistance checks and hardware repair boundary.
Linked records
FIELD FAIL is a field circuit evidence problem before it is a control-board claim. The first split is permanent-magnet motor / disabled field setting versus wound-field motor; then external field wiring, fuses, FL1/FL2 supply, field bridge/regulator and field-current feedback must be separated.
Routes FIELD FAIL through field-enable configuration, FL1/FL2 field supply, fuses, field bridge/regulator, F+ / F- motor field wiring, field-current feedback and the board-level boundary.
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