DC-link / braking / thermal evidence record

Unidrive Braking and Thermal Evidence Record

Captures Over Volts and O.ht/O.ht1 evidence around DC bus, braking resistor, chopper, fan, heatsink and load duty.

Board and evidence record8 min read

Scope of this technical record

Defines the Unidrive evidence package for braking, Over Volts, O.ht and thermal/cooling cases.

Safety boundary

Brake resistors and heatsinks can be hot; DC-bus discharge must be verified before access.

Unidrive braking/thermal evidence route

1Load
2Brake resistor
3Chopper
4Fan / heatsink
5Thermal timing

The evidence record connects Over Volts and O.ht to application and hardware boundaries.

Unidrive braking thermal evidence image

Unidrive braking thermal evidence route load brake resistor chopper fan heatsink and thermal timing
The image connects Over Volts and thermal trips to machine energy and cooling hardware.

Evidence package

The record should show load type, stop/decel profile, brake resistor and wiring, chopper evidence, cooling fan/heatsink state, ambient conditions and whether the trip is cold or hot-load related.

  • Load and stop profile
  • Brake resistor value/wiring
  • Brake chopper evidence
  • Fan and heatsink condition
  • Cold/hot trip timing

Repair boundary

A braking/thermal case moves to board repair only after load, resistor, chopper, fan and heatsink evidence is reconciled. Otherwise the first action may be application or cooling correction, not electronics replacement.

Field record checklist

  • Load energy
  • Brake hardware
  • Chopper evidence
  • Cooling evidence
  • Thermal timing

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

Public trip-code context for Over Volts and thermal events.

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 →