DTC U058508 indicates abnormal CAN communication data between the IPB (Intelligent Integrated Braking System) and the TCU (Transmission Control Unit) — Atto 8
DTC U058508 indicates abnormal CAN communication data between the IPB (Intelligent Integrated Braking System) and the TCU (Transmission Control Unit).
Specifically, the TCU data frames received by the IPB contain checksum errors, implausible data logic, or communication timeouts.
This fault affects critical data exchange between the powertrain and braking systems.
The TCU cannot provide the IPB with accurate gear state, torque request, motor speed, or vehicle speed signals, preventing the braking system from coordinating the switching logic between energy recovery and hydraulic braking.
Potential causes include corrupted internal TCU EEPROM data, CAN bus physical layer interference, logic errors resulting from an abnormal TCU power supply, or parsing errors at the IPB receiver.
When triggered, this fault may limit vehicle power output, disable the energy recovery function, and illuminate the ABS/ESC warning light.
In severe cases, the vehicle enters Limp Home Mode.
- 1TCU internal program runaway or corrupted EEPROM data causes an abnormal frame structure or checksum error in the transmitted CAN signal.
- 2Intermittent short circuit, open circuit, or excessive contact resistance in the CAN-H/CAN-L wiring harness between the TCU and IPB, especially at the firewall, high-temperature areas of the engine compartment, or chassis wiring harness bends.
- 3Unstable voltage in the TCU power supply circuit (constant B+ or IGN power), or oxidized or loose ground points (such as G303/G304), causes abnormal TCU operating timing.
- 4IPB (Intelligent Integrated Braking System) internal CAN receiving module fault, incorrectly identifying normal TCU data as abnormal.
- 5Aftermarket equipment (such as a dashcam or navigation module) connected in parallel to the CAN bus, or electromagnetic interference from the high-voltage system causing communication data distortion.
- 1Use the BYD VDS2000 diagnostic tool to read all DTCs. Check for accompanying communication faults such as U059508 (MG communication fault). Verify freeze frame data at the time of the fault, such as vehicle speed and gear position.
- 2Check TCU power supply fuses F1/9 (constant power) and F2/2 (IGN power). Measure the voltage at TCU connector pin 1 (B+) and pin 2 (IGN). Verify the voltage is within 11–14 V and fluctuates less than 0.5 V.
- 3Measure the resistance between the TCU ground wire (pin 3) and body ground; it must be less than 1Ω. Inspect ground points G303 and G304 for oxidation or looseness.
- 4Disconnect the TCU and IPB connectors. Measure the circuit resistance between CAN-H (pin 6) and CAN-L (pin 7). Standard value: 60 Ω (including terminating resistor). Check the wiring harness for wear and signs of water ingress.
- 5Use an oscilloscope to monitor the CAN waveform at the TCU terminal. The standard dominant level is CAN-H 3.5V/CAN-L 1.5V, and the recessive level is 2.5V. Check for waveform distortion or noise interference.
- 6Check the TCU and IPB connector sealing rings for aging and the pins for green corrosion. If necessary, clean with electrical contact cleaner and apply conductive grease.
- 7Perform the TCU and IPB software upgrade procedure. Early software versions on some 2020-2021 BYD Song DM and Qin DM models have communication protocol compatibility issues.
- 8If all above checks are normal, replace the TCU control unit assembly and complete online programming and immobilizer matching.
Song Plus DM-i: TCU data abnormality caused braking system warning
Qin Pro DM: TCU program error causing abnormal communication data
Water ingress in Song DM TCU connector caused data communication error