Brake energy and DC-link protection evidence record

Danfoss VLT Brake Chopper / Braking Resistor Evidence Record

Documents whether regenerated energy is being dissipated through a correctly installed brake path or whether the case belongs to ramp tuning, resistor sizing, thermal protection, brake transistor or DC-link sensing repair.

Board and hardware evidence checklist9 min read

Scope of this technical record

Evidence record for Danfoss VLT brake-chopper, brake-transistor and braking-resistor decisions where overvoltage during deceleration must be separated from line voltage, ramp, load inertia and thermal installation issues.

Safety boundary

This record is not an instruction to probe live brake circuits. Brake hardware and DC-link nodes must be treated as high-energy areas and handled only after qualified isolation and discharge verification.

Danfoss brake evidence request route

1Type code
2Trip timing
3Resistor
4Thermal
5Repair decision

The record prevents a vague overvoltage request from becoming a wrong resistor or premature board repair.

Danfoss VLT brake evidence record

Danfoss VLT brake evidence record type code trip timing resistor thermal contact cabinet heat repair decision
The evidence image shows what must be documented before resistor, chopper or board advice is useful.

What this evidence record prevents

A deceleration-overvoltage case can generate three bad requests: sell me any braking resistor, repair the board without load evidence, or replace the drive because it trips during stop. This record prevents those shortcuts by forcing the physical brake path and the machine duty into the same support package.

The goal is to decide whether the case needs parameter/ramp work, a correctly specified brake resistor, thermal relocation, brake-chopper repair, or DC-link sensing investigation.

Photographs and measurements that matter

Useful photos show the drive type code, brake terminals, resistor label, resistor mounting, thermal-contact wiring and the cabinet airflow route. Useful measurements include input voltage and resistor ohms after safe isolation. The report should also state whether the resistor is inside the cabinet or mounted externally, because heat management changes the decision.

  • Drive type code, frame and voltage class
  • Brake terminal wiring and option identity
  • Resistor label, ohms and duty rating if available
  • Thermal contact wiring and current state
  • Cabinet heat, airflow and resistor placement
  • Trip timing before and after ramp change

Repair versus redesign boundary

If the resistor is wrong, disconnected or overheated, the repair path stays outside the drive until the brake package is corrected. If the hardware is correctly specified and installed but the drive never commands braking, the case can move toward brake-chopper or control evidence. If the stop requirement exceeds the drive/brake package capability, the right answer may be system redesign rather than component replacement.

Field record checklist

  • Type code / frame / voltage class
  • Alarm 7 or overvoltage timing
  • Brake resistor and option evidence
  • Input and ramp evidence
  • Thermal and cabinet placement evidence
  • Previous brake 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.

Danfoss AC drives service tips — Alarm 7 DC-link overvoltageDanfoss

Defines Alarm 7 / DC-link overvoltage checks around input phase-to-phase voltage and regenerative voltage from the motor end.

Danfoss VLT AutomationDrive FC 301/302 Programming GuideDanfoss

Describes brake-resistor function as absorbing brake power generated in regenerative braking and supports the brake-energy route used here.

Danfoss article — Brake resistors, external is betterDanfoss

Explains why external brake-resistor placement can improve heat handling, duty-cycle selection and braking-energy dissipation.

Linked circuit records

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 →