U025900 indicates the IPB (Intelligent Integrated Braking System/Intelligent Power Braking System) failed to receive a valid message or heartbeat signal from the VCU (Vehicle Control Unit) via the powertrain CAN bus within the calibrated time window (typically 100-200ms) — Atto 3
U025900 indicates the IPB (Intelligent Integrated Braking System/Intelligent Power Braking System) failed to receive a valid message or heartbeat signal from the VCU (Vehicle Control Unit) via the powertrain CAN bus within the calibrated time window (typically 100-200ms).
In the BYD DM-i hybrid architecture, the VCU acts as the primary vehicle controller.
It calculates the regenerative braking torque request in real time and sends it to the IPB.
The IPB then coordinates the distribution ratio between electric motor braking and hydraulic braking based on this request.
Upon a communication timeout, the IPB determines it has lost communication with the VCU and enters fail-safe/limp-home mode.
The IPB forcibly cancels regenerative braking and retains only basic hydraulic brake assist (vacuum or electric assist, depending on the IPB type) while triggering an ABS/ESC system fault warning.
This U-category communication fault indicates a network or physical layer connection anomaly rather than a functional failure of the braking actuators.
However, it severely impacts regenerative braking efficiency and braking coordination.
- 1VCU power supply system fault: Causes include a blown VCU constant power fuse (usually EF17/EF18 or a high-current fuse above 30A in the front compartment fuse box), burnt relay contacts, a poor power circuit connection, or a loose ground wire. These faults cause the VCU to restart intermittently or freeze, preventing continuous CAN message transmission.
- 2Powertrain CAN bus physical layer fault: Open or short circuit in the CAN_H and CAN_L lines between the VCU and IPB (shorted together or shorted to power/ground), excessive contact resistance (backed-out connector pins, water ingress, oxidation), or abnormal terminating resistance (120Ω in parallel should be 60Ω) causing signal reflection.
- 3VCU software fault or hardware damage: Damaged VCU internal CAN transceiver chip, MCU crash (program runaway), abnormal Watchdog reset, or software bug causing abnormal message transmission cycle.
- 4IPB receiving fault: A damaged internal IPB CAN receiving module, abnormal software parsing, or an IPB power supply/ground fault prevents the IPB from correctly receiving VCU messages (although the IPB logs the fault code, the root cause may be the IPB itself).
- 5Network interference or bus congestion: Other nodes on the powertrain CAN bus (e.g., BMS, MCU, OBC) malfunction and transmit error frames, causing excessive bus load and delaying or dropping VCU messages.
- 1Fault confirmation and freeze frame analysis: Use the VDS2000/VDS3000 diagnostic tool to read the complete fault codes and freeze frame data. Record the vehicle speed, SOC, gear position, and brake pedal status at the time of the fault. Determine if the fault is intermittent or current. Check for other U01xx series communication fault codes.
- 2VCU power supply and ground check: Check the VCU constant power fuses (e.g., EF15/EF16 30A) and IGN supply fuse in the front compartment power distribution box. Measure the voltage drop across the fuses (should be <0.1V). Check the tightening torque of the VCU ground bolt (usually located on the front left side member or firewall) (standard: 10-12N·m). Measure the supply voltage at the VCU connector pins (should be 9-16V, fluctuation <0.5V).
- 3CAN bus physical layer check: Disconnect the battery negative terminal and measure the resistance between OBD connector pin 6 (CAN_H) and pin 14 (CAN_L). The standard value is approximately 60Ω (two 120Ω terminating resistors in parallel). Power on the vehicle and measure the CAN_H voltage to ground (2.5-3.5V) and CAN_L voltage to ground (1.5-2.5V). The differential voltage should be between 0.2V and 2.5V. Use an oscilloscope to observe the CAN waveform and check for distortion or error frames.
- 4Wiring harness and connector inspection: Inspect the IPB wiring harness connector (located near the brake master cylinder, prone to moisture) and the VCU wiring harness connector (located in the front compartment or behind the glove box) for backed-out pins, spread terminals, water corrosion (green rust), and harness damage. Check the front compartment wiring harness for chafing against metal body edges, especially at the firewall pass-through.
- 5Network topology isolation test: Disconnect the other powertrain CAN nodes (BMS, MCU, OBC, etc.) one by one, except the VCU and IPB. Observe if the fault clears to rule out interference from other modules. Use CANoe or a BYD dedicated network analyzer to capture bus messages and verify the VCU periodically sends brake request messages (ID is typically 0x1xx or 0x2xx series, depending on the platform).
- 6Software update and configuration: If wiring is normal, update the VCU software to the latest version (e.g., V2.x versions released after 2023 fix the early communication timeout bug). Verify the VCU and IPB CAN baud rate (typically 500kbps) and network address configurations are correct.
- 7Component Replacement and Matching: If the above steps fail, first replace the VCU assembly (perform online anti-theft matching and parameter configuration). If the fault persists, replace the IPB assembly (bleed the brake lines and calibrate the system). After replacement, perform a network communication test and verify the fault code does not return.
Intermittent brake warning light during high-speed driving in Song PLUS DM-i
IPB communication timeout after accident repair
Software version mismatch caused multiple communication failures
VCU main board CAN transceiver chip failure
IPB internal communication module fault