
Quick answer
A VFD over‑current fault that appears only during acceleration usually indicates that the torque demand during the start‑up ramp exceeds what the drive‑motor system can deliver. The root cause is often a mechanical load that is higher than expected, an acceleration time that is too short, mismatched motor data, a brake that remains engaged, or a drive‑control setting that limits torque or current prematurely. Begin by confirming that steady‑state current is within the motor’s rated limits, then systematically examine the starting load, ramp profile, motor parameters, brake timing, and supply voltage before adjusting any current limits.
Problem / job
The drive trips on an over‑current fault each time the motor is commanded to accelerate from standstill to operating speed. Once the motor reaches speed, current returns to normal and the equipment runs without further interruption.
Evidence
Recorded VFD fault code, current and torque trends, speed command versus actual speed, DC‑bus voltage, configured acceleration time, motor name‑plate data, recent parameter changes, and any observable mechanical symptoms (binding, vibration, brake drag).
Decision
Separate excessive mechanical starting torque from aggressive ramp settings, incorrect motor data, brake or load problems, and drive‑control configuration errors. The correct remedy will address the underlying torque demand, not simply raise the current limit.
As‑found evidence capture
Save the VFD fault record and export the current, torque, command frequency, and actual speed traces for at least one failed start. Highlight the exact point in the acceleration ramp where the current spikes and the fault is logged. If possible, repeat the capture with the equipment unloaded or with a reduced material load to isolate the mechanical contribution.
All electrical work must follow site‑specific lock‑out/tag‑out (LOTO) procedures. Verify that the VFD and upstream breaker are isolated, confirm the absence of voltage with a calibrated tester, and ensure only qualified personnel perform any wiring or parameter changes. Document every change so the original configuration can be restored if needed.
Seven‑step diagnostic workflow
1. Verify that the fault is limited to acceleration
Run the motor at rated speed under normal load and confirm that current stays within the motor’s name‑plate rating. If over‑current persists at steady state, the problem is likely a sizing or continuous‑load issue rather than a start‑up condition.
2. Isolate the mechanical starting load
Inspect conveyors, crushers, mixers, or any driven equipment for material buildup, seized bearings, excessive belt tension, closed valves, or other conditions that increase torque at start‑up. Look for signs of binding such as abnormal noise, vibration, or resistance when the shaft is turned manually (after LOTO).
3. Review the configured acceleration time
Compare the programmed ramp (seconds or % of full speed) with the inertia of the driven equipment. An overly short ramp forces the drive to request peak torque early in the start, which can exceed the motor’s capability. Adjust the ramp only within the limits specified by the equipment OEM or the site’s process requirements.
4. Confirm motor name‑plate and autotune data
Check that the VFD’s motor data (rated voltage, current, frequency, pole count, and rated torque) match the actual motor name‑plate. Autotune values should be verified against the motor manufacturer’s data sheet. Incorrect data can cause the drive to limit torque prematurely.
5. Examine torque and current limit settings
Determine whether the drive reaches its programmed current limit before the motor can achieve the commanded speed. If the limit is being hit, investigate why torque demand is high—possible causes include mechanical binding, a brake that has not released, or an under‑sized motor for the application. Do not raise the limit until the underlying cause is identified.
6. Check brake, clutch, and interlock timing
For equipment equipped with mechanical brakes, verify that the brake release signal occurs early enough in the ramp. A brake that remains engaged for a fraction of a second can create a sudden torque surge and trigger an over‑current fault. Confirm that any interlocks (e.g., position switches) are functioning correctly and that feedback signals are accurate.
7. Validate the correction with repeatable starts
After addressing the suspected cause—whether by clearing material, adjusting the ramp, correcting motor data, or fixing brake timing—perform at least three controlled starts. Record the same parameters as in step 1 and ensure that the current trace remains below the fault threshold, the speed ramps smoothly, and no fault codes appear.
Evidence‑to‑decision matrix
| Evidence | Likely direction | Next check |
|---|---|---|
| Trip occurs at the same early point in every ramp | Ramp profile or starting load problem | Inspect mechanical load, compare acceleration time |
| Current spikes while actual speed barely increases | Binding, brake drag, or excessive inertia | Brake release timing, shaft freedom after LOTO |
| Fault appeared after a drive‑parameter change | Drive setup error | Review motor data, ramp, torque‑limit mode |
| Starts succeed when equipment is empty or lightly loaded | Process‑related starting load | Startup sequence, material condition, load‑reduction options |
| Current erratic and speed feedback unstable | Feedback or control loop issue | Encoder/sensor wiring, signal integrity, control tuning |
Return‑to‑service acceptance criteria
Accept the motor-drive system only after the plant-approved restart tests meet the applicable motor, VFD and driven-equipment OEM limits:
- Recorded acceleration current stays within the OEM-approved, time-dependent current and overload limits for the motor and VFD. A brief starting peak above the motor nameplate full-load current is not automatically a fault.
- Recorded torque demand remains within the applicable motor, drive and driven-equipment limits for the operating speed and duty.
- Acceleration completes as commanded without unexplained current-limit intervention or protective trips; assess any programmed current limiting against the approved drive configuration.
- Brake release (or clutch engagement) occurs before the torque peak, verified by the drive’s brake‑status feedback.
- Voltage at the VFD input remains within the OEM‑specified tolerance (verify against site power quality logs).
- No abnormal vibration, audible noise, or temperature rise is observed on the motor or driven equipment during the start‑up sequence.
Document the final parameter set, capture the current/torque trace for the last successful start, and retain the original fault record for future reference.
Common mistakes and repeat‑failure traps
- Raising the current limit as a first step. This masks the symptom without addressing the torque demand and can overload cables, motor windings, or the driven equipment.
- Lengthening the ramp to hide a mechanical fault. A longer ramp reduces peak torque demand but does not eliminate binding, seized bearings, or a brake that remains applied.
- Changing multiple drive parameters simultaneously. Simultaneous adjustments make root‑cause identification impossible and increase the risk of introducing new faults.
- Ignoring motor name‑plate data. Using generic or copied motor settings can cause the drive to apply inappropriate torque limits.
- Skipping lock‑out/tag‑out before mechanical inspection. Performing manual checks on a live motor can cause personal injury and damage to the drive.
- Failing to preserve the original fault trace. Without the baseline data, later troubleshooting may miss intermittent or evolving issues.
Adhering to a disciplined, step‑by‑step approach reduces the likelihood of recurring over‑current trips and extends the service life of both the VFD and the motor.
Related Infinity guides
Build a stronger cement maintenance library
The Infinity for Cement Organization technical package contains 900+ technical files. It is a one-time $249.99 purchase, with instant download immediately after payment and lifetime updates forever at no additional cost.
