DC-drive feedback option / sensor / control-input evidence package

Parker 590P Speed Feedback / Encoder Evidence Record

Collects the proof needed to decide whether a SPEED FBK / ENCODER problem is caused by armature-voltage feedback limits, tach or encoder wiring, feedback polarity, Microtach fibre/receiver, field weakening, option-card hardware or a control-board feedback input.

Evidence request record8 min read

Scope of this technical record

Support request package for 590P / 591P speed-feedback, encoder, tachometer and armature-voltage feedback problems.

Safety boundary

This page defines documentation requirements; it is not an instruction to perform unsafe live testing.

590P speed-feedback evidence package

1Type code
2Feedback mode
3Sensor proof
4Field state
5Decision

The record converts a vague encoder alarm into repair, upgrade or retrofit evidence.

590P speed-feedback evidence record

Parker 590P speed feedback evidence record type code feedback mode sensor proof field state repair decision
The evidence record shows what a support request needs before repair, upgrade or retrofit advice is reliable.

What makes the request actionable

A speed-feedback request becomes actionable when it identifies the drive, the configured feedback source, the actual feedback hardware, the event timing and the field / speed range context. Without that information, the same alarm can point to several unrelated service routes.

The evidence package is also useful for repair planning. It tells whether the likely output is a sensor repair, option-card match, control-board repair, feedback upgrade, donor-unit case or retrofit.

  • Complete 590P / 591P type code and regenerative status
  • Selected speed-feedback source and installed feedback option
  • Sensor type, nameplate, wiring and coupling evidence
  • Field weakening status, base speed and top speed
  • Diagnostic feedback value, armature volts and speed demand at fault time
  • Photos of feedback card, connectors, tach/encoder and recent repair work

Field record checklist

  • Reject vague 'encoder alarm' requests until feedback mode and hardware are identified.
  • Ask for both electrical and mechanical feedback evidence.
  • Route the result to repair, feedback upgrade or retrofit only after evidence review.

Technical basis and reference documents

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

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

Official source for 590+ safety, feedback selection and parameter context for speed feedback applications.

590 DRV Digital DC Drive Product ManualParker / SSD Drives

Official source noting that speed feedback can be armature voltage, analog tachometer, wire-ended encoder or Microtach feedback.

DC590+ Series DC Drive Technical Application NotesParker Electromechanical

Explains speed-feedback alarm behaviour, armature-voltage feedback limitations and field-weakening effects.

590P / 591P reviewed drawing referencesIndustrialDriveData reviewed technical source

Internal reviewed drawing references used only for functional 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 →