Industrial AC drive / VFD diagnostic framework

Cross-Brand VFD Fault Triage

A search-led diagnostic track for high-frequency VFD symptoms: no display, overcurrent at startup, DC bus overvoltage during deceleration, ground-fault trips, output phase-loss indications and repeated IGBT module failures after repair.

Field-triage framework8 min read

Scope of this technical record

Cross-brand VFD Fault Triage organizes common AC drive symptoms into safe diagnostic boundaries for qualified maintenance and repair personnel.

Safety boundary

This framework is not a live-repair procedure. Industrial VFDs contain hazardous input, DC-link and output-stage energy; isolation, discharge verification and qualified site procedure are mandatory.

Why cross-brand VFD symptoms need a database path

Many service searches start with a symptom rather than a complete model number: no display, overcurrent at startup, DC bus overvoltage during deceleration, ground fault on run or repeated IGBT failure after repair. The wording varies by manufacturer, but the diagnostic boundary is often similar enough to create a structured first-pass route.

The value of this track is not to replace the OEM manual. It prevents the most expensive early mistake: jumping from a visible alarm to a replacement board or module before line supply, precharge, DC-link energy, control power, motor cable, braking hardware and gate-driver evidence are separated.

Symptom-to-boundary map

The first question is not which component failed. The first question is which boundary must be proven. A dark keypad points to input, DC-link and auxiliary supply evidence; an instant overcurrent trip points to output cable, load, parameters, driver and current sensing; a deceleration overvoltage points to regenerated energy and braking capacity.

Cross-brand VFD triage map

SymptomFirst diagnostic boundaryCommon mistake to avoid
No displayInput / precharge / DC link / SMPSReplacing the keypad before supply evidence
Overcurrent at startupMotor cable / load / driver / current feedbackResetting repeatedly into a damaged bridge
DC bus overvoltage on stopRamp / braking / regeneration / bus feedbackShortening decel without braking capacity
Ground fault at runMotor insulation / cable / output accessoriesMegger testing through drive electronics
Repeated IGBT failureGate drive / isolated supply / snubber / loadInstalling a second module without driver checks

How to use this record for service requests

A useful request should include the exact model, input voltage class, frame size, fault text, when the trip occurs, whether the motor was connected, any previous repair, photos of labels and visible board identifiers. Without those details, a generic symptom stays generic and cannot become a high-confidence model record.

This track also creates internal links from generic symptoms into brand-specific pages. When a user later provides an ABB ACS800, Siemens MASTERDRIVES, Parker 590P, Yaskawa A1000 or Schneider ATV unit, the generic route can be narrowed into a manufacturer-specific fault page.

Field record checklist

  • Complete drive manufacturer and model number
  • Input voltage class and approximate power/frame size
  • Exact fault code or keypad wording
  • When the symptom appears: power-up, enable, acceleration, deceleration or load
  • Motor/cable connected or disconnected status under approved procedure
  • Photos of nameplate, control board, power board and visible damage
  • Any recent module, capacitor, fan, board or parameter repair

Technical basis and reference documents

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

IndustrialDriveData cross-brand diagnostic frameworkIndustrialDriveData

Internal database framework derived from common industrial AC drive architecture and field-triage patterns.

Model records

Fault records

Circuit and diagnostic records

Circuit
VFD input rectifier, precharge and DC-link path

Routes incoming three-phase supply through protection, rectification, precharge and DC-link storage before the inverter stage is allowed to run.

Open →
Circuit
VFD auxiliary SMPS and control-power path

Maps the auxiliary supply route that powers the CPU, keypad, I/O, relay logic, fan control and often isolated driver supplies.

Open →
Circuit
VFD IGBT gate-driver and output-stage path

Connects PWM command, isolated driver supply, gate components, short-circuit protection and the output bridge to overcurrent and repeat-module-failure symptoms.

Open →
Circuit
VFD braking chopper and DC-bus discharge path

Routes excess DC-link energy into braking hardware or controlled overvoltage management during deceleration and overhauling-load events.

Open →
Circuit
VFD motor cable and ground-fault path

Separates motor insulation, cable leakage, terminal contamination, output filters and internal sensing when a drive trips only after output voltage is applied.

Open →
Workflow
VFD no-display control-power workflow

Drive line power is present, but the keypad is dark, flashing or repeatedly restarting.

Open →
Workflow
VFD precharge and DC-link workflow

Drive reports undervoltage/precharge fault, blows input fuses or shows no-display symptoms with uncertain DC-link charging.

Open →
Workflow
VFD overcurrent-at-startup workflow

Overcurrent trip appears immediately at run command, during acceleration or before stable speed is reached.

Open →
Workflow
VFD DC-bus overvoltage during deceleration workflow

Drive trips on DC bus overvoltage when stopping, lowering, braking or reducing speed.

Open →
Workflow
VFD ground-fault and motor-cable workflow

Ground fault, earth fault or leakage trip occurs when output voltage is applied.

Open →
Workflow
VFD repeated IGBT/IPM failure workflow

Replacement IGBT, IPM or output module fails again during power-up, enable or early load testing.

Open →