Code U0573 indicates that a control module on the vehicle's communication network is receiving invalid or implausible data from the Vehicle Motion Control Module B. This is a network communication fault, not a specific mechanical or sensor failure. It means the data being sent by the motion control module is corrupted, out of range, or missing expected parameters.
The reporting module itself may be failing internally, producing corrupted or invalid data on the network. This is the most common root cause when wiring and connections are verified good.
Damaged, corroded, loose, or shorted wiring and connectors between the motion control module and the network can distort data signals, causing the receiving module to flag invalid data.
Termination resistance problems, bus line short or open circuits, or interference from another failing module on the same network can corrupt messages and trigger this code.
If a module was recently replaced or reprogrammed with incorrect software, the data format or content may not match what the receiving module expects, setting a U-code.
Insufficient or unstable voltage to the motion control module can cause it to transmit erroneous data or drop messages intermittently.
A failure inside the receiving control module's communication circuitry is possible but rare. This should only be considered after all wiring, network, and the reporting module have been ruled out.
No. This code is almost never caused by the PCM or ECM. It points to a problem with the Vehicle Motion Control Module B or the communication network. Replacing the PCM is typically incorrect and will not fix the underlying issue.
It depends on symptoms. If stability or motion control systems are affected, handling characteristics may change. Have the vehicle diagnosed promptly, especially if warning lights for traction or stability are illuminated.
It can be either. Wiring, connectors, and CAN bus integrity should be checked first because they are more common and less expensive to address. If those check out, the motion control module itself is the more likely culprit.
Sometimes. If the code appeared after a module replacement or reprogramming, a software or calibration mismatch may be the cause. Checking for and applying the correct software is a valid diagnostic step before replacing hardware.