DC-link / braking / regeneration

Unidrive DC Bus and Braking Path

Routes Over Volts evidence through line voltage, DC bus, load regeneration, deceleration ramp, brake resistor, brake chopper and feedback-induced instability.

Circuit-path evidence record9 min read

Scope of this technical record

Maps Unidrive DC-bus and braking evidence for Over Volts, regenerative load and brake-resistor/chopper decisions.

Safety boundary

DC-bus and brake resistor circuits are hazardous. Verify isolation, discharge and load state before access.

Unidrive DC-bus/braking path

1Load energy
2Ramp
3DC bus
4Chopper
5Resistor

The path connects Over Volts to regenerative energy and braking hardware.

Unidrive DC-bus braking path image

Unidrive DC bus braking path load energy ramp chopper resistor and bus feedback
The image links Over Volts to regenerated energy and braking hardware.

DC bus as an energy balance

The DC bus rises when regenerated or incoming energy exceeds what the drive can store or dissipate. On hoists and winders, this is often a machine-energy route before a hardware route.

Braking path table

The route connects mechanical energy to electrical evidence.

Unidrive DC bus/braking path

NodeEvidenceMeaning
Load/inertiaOverhauling or fast stopEnergy source
Ramp/profileToo aggressive decelControl demand
Brake resistorOpen/wrong value/overheatedDissipation fault
Brake chopperNo switching or shorted deviceHardware boundary
Bus feedbackIncredible or noisy readingSensing boundary

Field record checklist

  • Load energy
  • Ramp profile
  • Brake resistor
  • Chopper
  • Bus feedback

Technical basis and reference documents

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

Unidrive SP trip-code referenceDrives and Automation

Reference for Over Volts and DC-bus trip context.

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 →