ABB fault record

3220 / DC UNDERVOLT: Intermediate DC Circuit Undervoltage

The drive trips on DC UNDERVOLT / 3220, may not become ready, or may trip when load or line conditions pull the DC link below the permitted level.

Deep search-intent fault page11 min read

Scope of this technical record

ABB DC UNDERVOLT / 3220 routing for users deciding whether a low DC-link fault is caused by incoming supply, phase loss, fuses, contactor/precharge, rectifier bridge, bus measurement or weak control supply behaviour.

Safety boundary

Undervoltage on the display does not mean the DC link is safe. Treat the drive as energized until isolation and discharge verification are complete.

ABB 3220 DC undervoltage route

1Input phases
2Fuses / contactor
3Precharge
4DC link
5Measurement path

Follow the energy path to the DC bus before blaming capacitors or boards.

ABB 3220 DC undervoltage image

ABB DC UNDERVOLT 3220 input fuse precharge DC link route diagram
The image follows the bus-energy path so the page does not become a generic capacitor or board replacement suggestion.

Searcher intent coverage

3220 searchers need the energy path proven from input terminals to DC link before capacitor or board decisions.

Observed situationDecision neededEvidence that satisfies the search
Fault at power-upLine/fuse/contactor/prechargeInput phase measurements and bus-rise observation
Fault at run commandSupply sag or charge collapseDC-link trend and contactor behaviour
IntermittentLoose input or weak DC-link pathEvent timing, thermal pattern and terminal evidence

What 3220 users are trying to decide

A 3220 search usually means the drive will not become ready, trips during start, or drops out when the machine loads the line. The useful page must separate three conditions: the drive never builds a correct DC bus, the bus builds but collapses under load, or the drive is reporting bus trouble because of precharge/measurement/control-supply behaviour.

Official and public fault descriptions point to insufficient intermediate-circuit DC voltage, often from missing supply phase, blown fuse or rectifier-bridge fault. That is only the beginning. In the field, the page must force measurement at the drive terminals, not at an upstream assumption, then move through fuses, contactors, precharge, rectifier and DC-link evidence.

3220 timing map

When 3220 appearsLikely first boundaryEvidence to record
Immediately on power-upMissing phase, fuse, input contactor, precharge pathThree-phase voltage at drive terminals, fuse continuity, contactor state
After relay clicking / weak displayPrecharge, control supply, DC-link build-up problemDisplay stability, relay behaviour, qualified DC-link measurement
Only when motor startsLine sag, weak supply, load-related bus collapseTerminal voltage under start, DC-link trend, load condition
After recent repairWrong wiring, loose terminals, missed rectifier/precharge damageBefore/after photos, torque marks, rectifier/static checks
Intermittent in productionContactor, phase loss, utility sag, loose connectionEvent timing, upstream logs, thermal/vibration evidence

Field checking order that avoids wasted parts

Start with the supply at the drive input terminals. A measurement upstream of a fuse, disconnect, contactor or terminal block does not prove what the rectifier sees. Record all three phase-to-phase values and whether they remain stable during the start or load event.

Next inspect fuses, line contactor, terminals and precharge behaviour. A drive that clicks, flashes, weakly displays or repeatedly attempts to charge is not the same as a drive with a stable bus that trips only when loaded. If the DC link is low with all input evidence normal, rectifier bridge, precharge resistor/relay, bus capacitor condition and voltage-detection path become legitimate boundaries.

Your repair sources add a practical warning: low-voltage or weak-output symptoms can be caused by ageing electrolytics, rectifier/open-phase conditions and driver/control supply faults. Do not replace a keypad or main board before proving the main power chain.

3220 evidence table

EvidenceSupports external/input routeSupports internal drive route
One missing phase at drive terminalsYes: supply/fuse/contactor/wiringNo board conclusion yet
All phases correct but DC bus does not chargeInput route weakerRectifier/precharge/DC-link measurement route stronger
Bus charges then collapses at startSupply sag or load issue possibleCapacitor/precharge/rectifier under-load issue possible
Weak or cycling control displayCould be line/precharge instabilityControl supply or capacitor ageing route possible
Blown input fuse repeatsUpstream short or rectifier path likelyInternal rectifier/precharge fault must be checked

What to capture before repair or replacement

A useful 3220 request includes full type code, voltage class, input measurements at the drive terminals, fuse status, contactor/precharge behaviour, whether the bus ever reaches expected value and whether the trip occurs before or after a run command. If someone already replaced a fuse or rectifier, include that history because repeat fuse failures change the boundary.

Do not clear the history and replace parts first. In undervoltage cases, the pattern of supply, contactor and bus behaviour is the diagnostic asset. Without it, a repair shop may only be able to say “test required”, not which path is most likely.

Stop conditions for 3220

ConditionReasonNext action
No qualified DC-link measurement procedureDC bus remains hazardous even during undervoltage faultsDo not open; request qualified service
Missing phase or blown fuse not correctedDrive-side diagnosis is prematureCorrect input boundary first
Fuse blows again after replacementPossible rectifier/precharge/internal shortStop repeated energizing and collect static evidence
Bus voltage collapses under loadCould damage parts during repeat startsRecord load and supply trend before another run

Field record checklist

  • Full ABB type code, voltage class and supply configuration
  • Exact 3220 text/code and when it appears
  • Input phase-to-phase measurements at drive terminals
  • Fuse, contactor, disconnect and precharge behaviour
  • Qualified DC-link evidence and display/relay behaviour
  • Recent fuse, rectifier, capacitor or board replacement history

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

Formal ABB wording for DC UNDERVOLT as intermediate circuit voltage below limit.

ABB ACS800 3220 field discussionClick2Electro forum

Public fault description links 3220 to missing phase, blown fuse or rectifier bridge fault.

Diagnostic workflow