Scope of this technical record
590P FIELD FAIL route for technicians separating field-enable configuration, external field wiring, field fuses, FL1/FL2 supply, field bridge/regulator and field-current feedback before replacing control hardware.
Do not run a wound-field DC motor armature without a proven field. Isolate line, armature and field circuits before measuring resistance or inspecting field wiring.
590P FIELD FAIL route
FIELD FAIL is routed through configuration and field circuit evidence before control-board repair.
FIELD FAIL is not one fault
FIELD FAIL means the drive cannot prove the field condition it expects. That may be a real open field winding, a missing field supply, incorrect jumper or field-enable configuration, failed field fuses, loose F+ / F- wiring, a field bridge/regulator fault, or a feedback problem that reports zero field current when current is actually present.
The worst diagnostic shortcut is to treat FIELD FAIL as a control-board failure before confirming the motor type and field circuit. A permanent-magnet motor or externally excited motor may require different field assumptions, while a shunt-wound motor must never be driven without controlled field evidence.
Decision table for field evidence
Use the timing and measured field condition to decide where the next inspection belongs.
FIELD FAIL triage
| Observed evidence | Most likely boundary | Next service decision |
|---|---|---|
| FIELD FAIL immediately after enabling field | Configuration, field-enable, FL1/FL2 supply or field fuse | Do not open control board until field supply input is proven |
| Field voltage missing at expected terminals | Supply jumper, fuse, wiring or field regulator input | Document terminal identity and upstream supply path |
| Field voltage present but current absent | Open winding, field wiring or high-resistance terminal | Prove external field circuit before drive repair |
| Field current present but drive still reports fail | Field-current feedback or detection path | Escalate to field feedback/control board evidence |
| FIELD FAIL after recent motor or wiring work | Terminal identity or field wiring error | Photograph and verify field route before powering again |
Repair boundary
If field wiring, fuses and field supply are proven but feedback remains impossible, a board-level investigation becomes reasonable. That does not mean replacing the first board visible in the cabinet. The service request should identify the power frame, board labels, field path, fault timing and whether a 591P regenerative arrangement is present.
For old DC systems, the service decision is often repair versus retrofit. FIELD FAIL with proven field supply but no stable feedback may support board repair; repeated failures, missing parts or unsafe field wiring may point toward a planned DC-drive retrofit. The page should make that decision evidence-led rather than sales-led.
- Stop if motor field type is unknown
- Stop if field continuity cannot be proven safely
- Stop if armature testing is proposed before field evidence
- Escalate only after field supply and feedback evidence are separated
Field record checklist
- Motor field type
- Field-enable setting
- FL1/FL2 and F+/F- photos
- Field fuses
- Measured field condition
- 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.
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.
Diagnostic workflow
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