Scope of this technical record
Danfoss VLT 2900 DB1-DB4 Power and Gate-Driver Drawing Family for Danfoss VLT 2800 / VLT 2900. The page turns public fault terminology and the reviewed drawing evidence into a repair decision route rather than a generic fault-code summary.
This content is for qualified industrial-drive technicians. VFDs contain hazardous DC-link energy after isolation; the record organizes evidence and does not define live measurement procedures.
Technician demand and public supply gap
Technicians checking Danfoss VLT 2900 DB1-DB4 Power and Gate-Driver Drawing Family usually already have a stopped machine, a warning on the keypad or a drive that cannot be interrogated. General fault-code notes can often identify the meaning of the code, but it rarely connects the code to control-supply, driver, feedback and replacement-risk evidence in one path.
For Danfoss VLT 2800 / VLT 2900, the current supply of information is split among manuals, short fault-code lists, forum/video troubleshooting and repair-service pages. That partially satisfies the technician need, but it does not tell a repair buyer what evidence to collect before replacing a board or shipping a drive for service.
Evidence available from the owner-supplied drawings
The VLT 2900 DB drawing set exposes DC-link references, +12 V / -12 V / +18 V rails, HCNW2611 isolation, LM293 comparison and gate-signal families, which support pre-power checks after output faults.
This does not prove a module is failed. It supports a safer sequence: isolate the motor/cable first, then evaluate supply and driver consistency before fitting replacement power hardware.
Evidence boundary
| Evidence type | What it supports | What it does not prove alone |
|---|---|---|
| public manual/fault term | correct vocabulary and first diagnostic direction | which component has failed |
| reviewed schematic labels | functional board region and rail/driver path | universal compatibility across all revisions |
| field timing and isolation result | repair, replacement or retrofit decision | safe live testing by unqualified personnel |
How to use this page
Start with exact identity: drive type code, rating, displayed fault text, event timing and whether the motor/cable was connected. Then classify the case as supply, output/load, driver/feedback or lifecycle decision. This prevents a technician from replacing a control card for an external motor fault or a power module for a control-supply symptom.
The page is most useful when it turns a vague request into a structured technical package: what happened, when it happened, which external causes are ruled out, which drawing-supported region is implicated and what must be stable before replacement parts are installed.
Repair or replacement decision
Danfoss and VACON legacy drives may still be repairable, but old compact drives also raise retrofit questions. A successful page should not force every case toward component repair. It should tell the technician when a used board, a bench repair, an OEM-compatible replacement or a full retrofit is the better risk decision.
That is the site advantage: not competing with manuals by repeating alarms, but connecting demand to evidence that manuals and repair-service landing pages do not usually package together.
Field record checklist
- exact type code and rating
- displayed warning/alarm or no-display state
- event timing and reset behavior
- motor/cable/supply isolation result
- visible board identifier and damage evidence
- repair versus replacement constraint
Technical basis and reference documents
This is an independent editorial technical reference. Original manufacturer documentation remains controlling for installation, repair and commissioning decisions.
Reviewed VLT2800 CB1-CB3, VLT2900 DB1-DB4 and VACON NXL DB1-DB4 drawing records; original drawings are not redistributed.
Public source for VLT 2800 warning and alarm terminology including current limit, overcurrent and DC-link undervoltage context.
Public fault-code list showing DC-link undervoltage, current limit and related VLT 2800 alarm terminology.
Related technical records
The compact VLT reports Alarm 13 or Warning 13 when the motor is started, during acceleration, under load or immediately at PWM output.
The drive trips with Alarm 14 during start, immediately after reset, with the motor connected, or even when the motor has been disconnected for testing.
The VLT 2800 / 2900 reports Alarm 16 on start, immediately after output enable, after motor work, after cable changes or after a prior power-stage repair.
The drive trips on overcurrent during start, acceleration or under load.
The drive reports earth fault or trips when the output is energized.
The drive reports internal or output short-circuit and may trip immediately at run command.
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.
DB1 shows power-source and auxiliary rail evidence that supports undervoltage and post-repair rail-stability questions.
DB2-DB4 show isolated and buffered driver/feedback regions with rails and gate-signal families used when Alarm 13, 14 or 16 requires internal escalation.
Alarm 13 overcurrent or Alarm 14 earth fault on a VLT 2800 / 2900 compact drive during start, ramp, run or bench test.
Alarm 16 short circuit, repeat output-stage failure or post-repair uncertainty on compact Danfoss VLT 2900 hardware.
Warning/Alarm 13 or Alarm 14 during run command, acceleration or output energization.
Alarm 16 current short-circuit, repeat module failure or post-IGBT repair risk.
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