Gate driver and inverter output stage

ABB ACS800 AGDR Gate-Driver to IGBT Output-Stage Path

This path separates control/interface command, AGDR driver health, isolated driver supply, gate output, IGBT phase-leg condition and motor-output evidence after an ACS800 SHORT CIRC event.

Gate-driver circuit path11 min read

Scope of this technical record

Use this path to map ACS800 control/interface command, AGDR driver hardware, IGBT phase legs and output-stage protection evidence after a SHORT CIRC event.

Safety boundary

This is an evidence path for qualified personnel, not a live test instruction. Do not access AGDR or IGBT hardware until the drive is isolated and discharged.

ACS800 AGDR gate-driver route

1Interface
2Driver supply
3AGDR
4IGBT
5Phase output

The driver path is checked before trusting another power module.

The driver path sits between interface command and power switching

AGDR hardware belongs to the boundary between inverter-interface command and IGBT switching. In a 2340 case, the driver may be healthy and reporting a real power-stage problem, damaged by a failed IGBT, or the initiating cause of a repeat module failure.

The useful service record links the AGDR assembly to a physical output module, phase leg, connector path and failure history. It should not treat the driver as an isolated board name.

AGDR path checkpoints

CheckpointEvidenceWhy it matters
Interface commandINT/AINT relationshipSeparates command path from driver path
AGDR identityLabel, revision, connector positionPrevents wrong assembly selection
Driver channelAffected phase/leg relationshipLinks fault evidence to hardware area
IGBT relationshipModule label and static evidenceSeparates driver damage from module damage
Output pathCable and motor proofProtects replacement hardware

What a driver record must not claim

A driver record must not claim that 2340 always means AGDR failure. It also must not claim that a good-looking driver is safe after a destructive output event. The service position depends on external proof, static bridge evidence, driver-channel evidence and repair history together.

If a previous repair changed the module but not the driver, or changed the driver but not the original external route, the next event should be handled as a repeat-failure investigation.

Field record checklist

  • AGDR label
  • Connector positions
  • Phase/leg clue
  • IGBT module label
  • Driver damage
  • Output path proof
  • Prior repairs

Technical basis and reference documents

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

ACS800 Standard Control Program Firmware ManualABB Library

OEM basis for ACS800 SHORT CIRC 2340, PPCC LINK 5210, FAULTED INT INFO and INT SC INFO context.

ACS800 hardware manualABB Library

OEM basis for hazardous-drive safety, cabinet structure, power-module and control/interface hardware context.

ACS800 SHORT CIRC field-service discussionPLCtalk

Public field discussion showing why 2340 cases can involve AGDR/module evidence, vibration, dust and repeat-failure conditions.

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 →