DC-drive current feedback / control-board evidence package

Parker 590P Armature Current-Feedback Evidence Record

Collects the proof needed to decide whether OVER I TRIP is caused by real armature current, bad tuning/calibration, ACCT / feedback plug trouble, burden/scaling electronics, control-board A/D feedback failure or a downstream power-stage condition.

Board and repair evidence record8 min read

Scope of this technical record

Evidence package for repair shops or maintenance engineers deciding whether a 590P OVER I TRIP is a motor/load issue, current-feedback fault, control-board repair, bridge issue or retrofit candidate.

Safety boundary

The evidence record is for documentation before repair decisions. It does not authorise live board probing or bypassing protection.

590P current-feedback evidence package

1Type code
2Trip timing
3Current proof
4Feedback photos
5Decision

The evidence package turns an OVER I TRIP request into repair, donor-board or retrofit advice.

590P current-feedback evidence record

Parker 590P current feedback evidence record type code trip timing field proof current proof feedback connector photos
The evidence record shows what a repair request needs before parts or retrofit advice is reliable.

What to send with an OVER I TRIP repair request

A useful request includes enough information to distinguish a real current event from a false-current report. The minimum package is drive identity, motor identity, trip timing, field state, autotune/calibration history, current display at trip, any external current evidence and photographs of feedback connectors and board labels.

This evidence prevents three expensive mistakes: replacing a good control board, replacing a good bridge, or reinstalling the repaired drive into the same motor/load fault that caused the trip.

OVER I TRIP evidence package

Evidence itemWhy it mattersDecision supported
Type code and current ratingConfirms drive hardware and scalingRepair or donor match
Regenerative statusSeparates bridge groups and operating quadrantBridge/firing route
Trip timingShows whether fault is setup, load or feedbackWorkflow entry point
Field and speed-feedback proofCurrent-loop behaviour depends on bothSafe torque route
Autotune/calibration notesShows setup historyParameter correction versus hardware repair
ACCT / feedback connector photosFinds disturbed feedback hardwareFeedback-board route
Displayed versus measured currentSplits real current from false feedbackMotor/load versus control board

Field record checklist

  • Drive label
  • Motor label
  • Trip photo
  • Autotune/calibration history
  • Field proof
  • Current evidence
  • Board/connector photos
  • Repair or retrofit target

Technical basis and reference documents

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

590 DRV Digital DC Drive Product ManualParker / SSD Drives

Official source for OVER I TRIP: armature current above calibration value; possible causes include missing autotune, incorrect calibration and unstable current loop.

590+ Series Digital DC Drives Product ManualParker / Eurotherm SSD Drives

Official source for 590+ safety boundaries, permanent earthing, field/armature context and parameterised DC-drive operation.

590 Series DC Digital Converter Product Manual HA467078Parker SSD Drives

Official converter reference describing current-feedback related trip protection and the importance of feedback hardware in external-stack cases.

590P / 591P reviewed drawing referencesIndustrialDriveData reviewed technical source

Internal reviewed drawings used only as functional evidence for supply, feedback, burden, firing and bridge path mapping; original drawings are not redistributed.

Linked circuit 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 →