Diagnostic workflow

590P MISSING PULSE Firing-Path Diagnostic Workflow

Entry symptom: MISSING PULSE appears, armature current is uneven, or torque is absent even though enable and command evidence are present.

Step-by-step thyristor firing workflow10 min read

Scope of this technical record

Workflow for converting a 590P MISSING PULSE report into line-reference, connector, firing-output, gate path, bridge and retrofit evidence.

Safety boundary

Do not perform live bridge or gate measurements without qualified procedures and appropriate equipment. Preserve evidence instead of repeated resets under load.

590P missing-pulse workflow route

1Capture timing
2Check line
3Inspect firing plugs
4Trace gate pulse
5Repair / retrofit

The workflow turns a missing-pulse text into line, connector, gate and bridge evidence.

590P MISSING PULSE workflow

Parker 590P MISSING PULSE workflow capture timing check line inspect firing plugs trace gate pulse repair retrofit
The workflow turns a firing alarm into line, connector, gate and bridge evidence.

Workflow sequence

The sequence keeps a firing-path fault from becoming an automatic SCR bridge replacement.

590P MISSING PULSE workflow

StepEvidenceDecision
1590P / 591P configuration and regenerative statusKnow which bridge group can be involved
2Trip timing: enable, motoring load, regeneration or recent repairSeparate line/contact/firing/bridge conditions
3Input phases, fuses, contactor and line referenceClear external line-reference causes
4Firing plug, harness and gate wiring photosFind connector and wiring faults before bridge decisions
5Firing output or waveform evidenceSeparate missing command from non-conducting SCR
6Board and bridge labelsChoose repair, donor board, bridge repair or retrofit

Evidence that improves a support answer

A support request that includes only “MISSING PULSE” forces a generic answer. The request becomes useful when it includes load condition, regenerative status, recent work, firing connector photographs and whether any current waveform or fault capture exists.

  • Line condition at the drive
  • Regenerative/non-regenerative status
  • Firing connector and harness photos
  • Bridge and control-board labels
  • Current waveform or trip capture
  • Recent repair history

Field record checklist

  • Hardware status
  • Trip timing
  • Line/reference proof
  • Firing connector proof
  • Bridge labels
  • Retrofit constraints

Technical basis and reference documents

This is an independent editorial technical reference. Original manufacturer documentation remains controlling for installation, repair and commissioning decisions.

Parker 590+ Series Digital DC Drives product manualParker Hannifin / SSD Drives

Primary product manual context for 590+ digital DC drive fault handling, safety boundaries and field/firing evidence routes.

Parker 590+ DRV Field Fail procedureParker manual extract via ManualsLib

Shows FIELD FAILED routing through field volts, external jumper positions, FL1/FL2 connection and wiring tightness before the drive is treated as failed.

Parker / Eurotherm 590 missing-pulse field caseEng-Tips forum

A field technician case showing the real case behaviour behind mature SSD 590 Missing Pulse faults and current-waveform evidence requests.

Parker DC590 Field Fail support noteParker Vietnam support

Public support note connecting FIELD FAIL to field motor wiring, field fuses, field resistance checks and hardware repair boundary.

Linked records

Evidence intake

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
Prepare request →