The brake monitoring system has detected a fault condition in one or more axis holding brakes, indicating the brake has failed to engage properly, has insufficient holding torque, or the monitoring circuit cannot verify correct operation. This is a critical safety fault that prevents robot operation because axes cannot be safely held in position during power-off or emergency stop conditions, creating a drop hazard.
KUKA RobotSystemIntermediate
KRC0132
KUKA Robot KRC0132 - Brake Defective
Brake Defective
The brake monitoring system has detected a fault condition in one or more axis holding brakes, indicating the brake has failed to engage properly, has insufficient holding torque, or the monitoring circuit cannot verify correct operation. This is a critical safety fault that prevents robot operation because axes cannot be safely held in position during power-off or emergency stop conditions, creating a drop hazard.
Common Causes
Worn or contaminated brake friction pads and surfaces resulting in insufficient holding torque to meet monitoring threshold, typically occurring after 100,000+ brake cycles or exposure to oil contamination
Brake coil electrical failure including open winding, short circuit, or degraded resistance outside specification range detected by monitoring circuit during engagement test
24VDC brake power supply fault or voltage drop on brake release circuit preventing proper electromagnetic release, caused by failing power supply module or wiring issues
Mechanical brake adjustment out of specification with excessive air gap between brake disc and friction surfaces, often due to pad wear or incorrect reassembly after maintenance
Faulty brake monitoring switch or resolver feedback circuit in motor preventing controller from verifying brake engagement through position drift detection algorithm
Troubleshooting Steps
1Step 1: Identify which axis triggered the alarm from fault message or smartPAD display, mechanically secure robot with chain blocks or support stands before any brake system work to prevent axis drop
2Step 2: With robot powered down and LOTO applied, manually verify brake operation by attempting to move axis by hand with brake released (power on, drives enabled) versus engaged (power off), confirm positive holding
3Step 3: Measure brake coil resistance at motor connector or KPP brake output terminals using multimeter, compare to specifications in motor documentation (typically 80-150 ohms), check for open or short conditions
4Step 4: With power restored in T1 mode, access Service Brake Test function to perform automated brake engagement test, monitor results for specific axis failure indication and holding torque measurement
5Step 5: If brake resistance is correct but alarm persists, measure 24VDC brake release voltage at motor connector during enabled state, verify clean 24VDC present and check wiring continuity from KPP brake outputs X401-X406
6Step 6: Remove motor cover and inspect brake assembly for pad wear (minimum thickness 1.5-2.0mm), contamination, or mechanical damage, replace brake pads and perform air gap adjustment per service manual procedure, or replace complete motor if internal brake mechanism or monitoring components are faulty
Seeing Multiple Alarms?
Seeing another alarm with this one? Enter the code.
Get machine-aware diagnosis
AxisMD logs alarms against your actual machines, tracks patterns, and gives AI context your manual doesn't have.