Scope of this technical record
Evidence record for VLT 2900 power-board, gate-driver and current-feedback cases before repair or replacement decisions.
Do not energize a suspected power board until output short and driver-channel evidence is known.
VLT 2900 DB1-DB4 evidence route
The record links output alarms to driver and board evidence.
Power-board evidence to collect
The DB1-DB4 evidence package should connect the first trip, motor/cable proof, static output checks, driver supply, current-feedback behavior and previous repair history.
That evidence decides whether the compact drive is a board repair, donor-board case, replacement-drive case or a field wiring problem.
Field record checklist
- Type code
- DB1-DB4 label
- Alarm number
- Motor/cable proof
- Static output check
- Driver evidence
- Current-feedback behavior
- Repair history
Technical basis and reference documents
This is an independent editorial technical reference. Original manufacturer documentation remains controlling for installation, repair and commissioning decisions.
Confirms Alarm 13 overcurrent, Alarm 14 earth fault, Alarm 16 current short circuit, input-phase and DC-link alarm boundaries used to structure the first service routes.
Documents VLT 2800 warning and alarm text including Alarm 13 peak current, Alarm 14 ground fault, Alarm 15 switch-mode supply and Alarm 16 short-circuit cautions.
Provides practical Alarm 14 separation between motor/cabling evidence and drive-side current-sensor evidence, including no-motor current observations and manual-initialization caution.
Linked circuit records
Energy path for compact Danfoss cases where DC-link undervoltage, display instability or power-board suspicion must be separated from input fuses, rectifier, DC link and auxiliary supply behavior.
Output-stage route for Alarm 13, Alarm 14 and Alarm 16 cases after external motor, cable and terminal evidence has been collected. The route connects gate-drive channels, driver supply, current feedback and output module decisions.
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