Autotune / current calibration / loop stability

Parker 590P Current-Loop Autotune and Calibration Path

Separates OVER I TRIP caused by a real current event from an unstable current loop, incorrect calibration, wrong motor data, failed autotune or manual tuning that leaves the loop unstable.

Current-loop setup and stability record9 min read

Scope of this technical record

Calibration, autotune and current-loop stability path for OVER I TRIP cases after commissioning, motor replacement, parameter copy, board exchange or manual tuning.

Safety boundary

Do not use tuning changes to hide a hardware fault. The path assumes qualified commissioning procedures and safe machine conditions.

590P current-loop calibration path

1Rating match
2Calibration
3Autotune
4Loop stability
5Trip threshold

Autotune and calibration evidence must be reconciled before hardware is condemned.

590P current-loop autotune and calibration path

Parker 590P current loop calibration path motor rating current calibration autotune loop stability feedback plausibility
The setup image shows where calibration and autotune fit before a board is blamed.

The setup path behind a current trip

Parker documentation ties OVER I TRIP not only to current magnitude but also to missing autotune, incorrect calibration and unstable current loop conditions. That means a page that only talks about motor overload is incomplete for a technician working on a 590P.

The setup path starts with whether the drive rating, armature current calibration, motor data, field data and speed-feedback mode match the installed machine. It then checks whether autotune was completed on the actual motor and whether manual tuning or copied parameters left the current loop unstable.

Calibration and loop-stability evidence

EvidenceWhy it mattersPossible action
Drive and motor current ratingWrong scaling can move the trip boundaryCorrect rating and calibration data
Autotune resultThe drive must identify current-loop behaviourRepeat autotune after hardware/motor changes
Manual tuning historyHigh gain or poor compensation can trip during current build-upReturn to documented tuning route
Parameter copy sourceA parameter set from another machine may not fitCompare motor, feedback and field configuration
Feedback plausibilityBad hardware can make tuning impossibleFix feedback before retuning
Machine loadingReal load current can mask a setup problemTest with controlled, documented load conditions

Field record checklist

  • Motor nameplate
  • Drive rating
  • Calibration values
  • Autotune pass/fail
  • Parameter source
  • Feedback mode
  • Load condition

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.

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 →