U0573

Code

Generic U — Network/User

Invalid Data Received from Vehicle Motion Control Module B

Brand: Generic

Type: U — Network/User

Views: UK: 19 EN: 26 RU: 16

AI status

Completed

ready

Completed 100%

Page language: EN

Causes

Corrupted or out-of-spec CAN/LIN messages from Vehicle Motion Control Module B
Faulty VMCM B hardware or internal software error
Intermittent or permanent CAN bus wiring fault (short, open, high resistance)
Poor power or ground supply to VMCM B
Connector corrosion, water intrusion or physical damage at VMCM B or intermediate junctions
Incompatible or incorrect software/calibration (mismatched module programming)

Symptoms

Malfunction Indicator Lamp (MIL) or multiple warning lights (ABS, ESC, TCS) illuminated
Loss or degradation of vehicle stability control/traction control functions
Erratic or missing vehicle motion data in scan tool (speed, yaw, wheel speed inconsistent)
Associated modules report related U-codes or reduced functionality
Occasional or permanent limp-home behavior from stability/drive systems

What to check

Read and record all U-codes and related codes from every control module with a capable scan tool
View freeze frame and data stream for VMCM B and downstream modules to identify when/what data is invalid
Visually inspect VMCM B connector(s), wiring harness, and nearby grounds for damage, corrosion or moisture
Check battery voltage and charging system; test while trying to reproduce the fault
Verify presence of VMCM B on the network (module addresses and PID list) with scan tool
Check for inconsistent software part numbers or recent programming history

Signal parameters

CAN message ID: VMCM_B (manufacturer-specific) — presence/frequency: expected periodic message (e.g., 10–100 Hz)
Vehicle speed — units km/h or mph; expected steady increase/decrease consistent with wheel speeds
Wheel speed (each wheel) — expected 0–vehicle speed; inconsistent or out-of-range values indicate bad data
Yaw rate — units deg/s; should be within expected vehicle motion ranges and consistent with steering angle
Lateral acceleration — units g; should correlate with yaw and wheel speed
Message counter/sequence number — should increment predictably; repeated or out-of-sequence values indicate corruption

Diagnostic algorithm

Connect a professional scan tool and record all U-codes, freeze frame, and live data streams from VMCM B and related modules (ABS, ECU, IPC).
Clear codes and attempt to reproduce. Note whether U0573 returns immediately, intermittently, or after specific events (start, drive, cornering).
Confirm VMCM B is present on the bus and responding to diagnostic requests (module ID, software/calibration part numbers).
Monitor relevant VMCM_B CAN messages and parameters (vehicle speed, wheel speeds, yaw, msg counter, checksum). Identify which fields are invalid.
Inspect VMCM B connectors, pins and harness for damage, corrosion, bent pins or moisture. Repair any physical defects and retest.
Verify power and ground to VMCM B: measure battery voltage at the module connector while attempting to reproduce the fault. Repair poor connections or grounds.

Likely causes

VMCM B failed self-check and is transmitting invalid message content or CRC
Loose/dirty connector pins at VMCM B or common ground point
CAN high or CAN low short to voltage/ground or missing bus termination resistor
Low battery or unstable supply during module wakeup or reflash
Aftermarket device or recent module replacement with incorrect coding/software

Fault status

⚠️ Status

Invalid Data Received from Vehicle Motion Control Module B — module messages flagged as malformed, out-of-range, or failing checksum/validation on the vehicle network.

🟡 Repair difficulty: Medium

⏱️ Diagnostic time: 1.0-2.5 hours