Scope of this technical record
590P MISSING PULSE route for separating AC line reference, firing connector, pulse transformer or isolation path, SCR gate wiring, bridge conduction and armature current waveform evidence.
Thyristor firing and armature bridge circuits are line-connected high-energy circuits. Isolate and verify before connector, gate or bridge inspection. Do not repeatedly reset under load.
590P MISSING PULSE route
MISSING PULSE is a firing-evidence route; a bridge replacement is only justified after reference and connector evidence.
590P MISSING PULSE firing route
What a missing pulse really implies
MISSING PULSE is a firing evidence problem, not automatically a bad SCR stack. The message can be triggered by a missing line reference, a firing plug or harness problem, a pulse-transformer or isolation path issue, a gate-wire fault, an SCR bridge problem or current waveform evidence that the drive interprets as one absent firing group.
The real technician question is usually practical: can the installed bridge be trusted, or is the fault upstream in firing electronics and connectors? A good page must keep those possibilities separated because the cost and downtime of replacing a legacy DC power stack are high.
Timing and evidence split
Classify the trip by operating condition before touching the bridge.
MISSING PULSE decision points
| Trip condition | Likely first boundary | Service action |
|---|---|---|
| Trip after contactor closure or line disturbance | Line phase, fuse, contactor or reference input | Prove line/reference evidence first |
| Trip only when load current exceeds a threshold | Firing group, armature waveform or connector under current | Capture waveform or comparative current evidence |
| Trip after board or bridge replacement | Connector seating, gate wiring, wrong hardware or repair quality | Match board/frame labels before further power tests |
| No torque but command and field are present | Firing output, pulse transformer or SCR conduction | Trace firing path before replacing the bridge |
| Uneven current ripple | Missing firing group or current feedback distortion | Separate firing evidence from current-feedback fault |
When the bridge becomes suspect
The armature bridge becomes suspect only when line/reference, connectors, firing outputs and field condition are coherent but one firing group still fails to conduct correctly. In a regenerative drive, the motoring and regenerating bridge groups must be treated separately so a quadrant-specific symptom is not misread as a whole-drive failure.
The repair evidence should include the 590P/591P frame, regenerative status, firing connector photographs, gate-wire route, bridge markings and a description of when the trip appears. Without this, a support answer can only be generic. With it, the request can become a repair quote, donor board match or retrofit decision.
- Confirm regenerative versus non-regenerative hardware
- Preserve first-fault timing and current waveform if available
- Photograph firing plugs and gate wiring before disturbing them
- Do not replace the bridge until firing evidence has been separated
Field record checklist
- Regenerative status
- Trip timing
- Line/reference condition
- Firing plug photos
- Gate/bridge labels
- Current waveform evidence
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