01 P0084, P0085, and P0086: Exhaust valve control solenoid cir… • 02 Troubleshooting a Hard Brake Pedal: Causes and Solutions • 03 Manual Transmission Driving Techniques for Improved Fuel Ef… • 04 P0482 – Cooling Fan Relay 3 Fault: Engine Temperature Issues • 05 How to Avoid and Handle a Hydroplaning Vehicle: A Complete … • 06 How Technology Has Changed The Automotive Industry "Engines" • 07 iStop: The Revolutionary Brake-Activated Auto Stop-Start Sy… • 08 What Mechanics Check First When Fuel Usage Suddenly Spikes • 09 What Causes a Car Engine to Use More Water? • 10 The Benefits of Catalytic Converters in Vehicle Exhaust Sys… •

DTC codes / U05xx · Network communication / U059C

U059CInvalid Data Received From Drive Motor Control Module C

U059C is a vehicle network communication fault indicating that one electronic control unit received invalid or corrupted data from the drive motor control module C over the controller area network bus. The receiving module expected a valid data frame from the motor controller but detected missing, out-of-range, or checksum-failed information, so it flagged the message as invalid rather than acting on bad data.

SystemNetwork
Code typeGeneric (all makes)
SeverityMedium
Fix difficultyProfessional
AreaNetwork communication

Symptoms you may notice

  • Illumination of the malfunction indicator lamp, often with no other noticeable symptoms
  • Reduced power or limp-home mode if the invalid data affects torque commands or motor status
  • Intermittent hesitation, shudder, or abrupt loss of propulsion assist during acceleration
  • Instrument cluster warnings for hybrid or electric system faults, such as a service vehicle soon message
  • Failure of the vehicle to enter ready mode or start the drive system in some cases
  • Other modules storing communication or plausibility codes alongside U059C

Common causes, most likely first

  1. Corroded, loose, or damaged pins in the drive motor control module C harness connector
  2. Chafed or open wiring in the controller area network bus between the motor controller and the receiving module
  3. Failed or intermittent drive motor control module C internal circuitry affecting its transmitted data
  4. Low or unstable 12-volt supply or poor grounds shared by the motor controller and network modules
  5. Electromagnetic interference from degraded high-voltage cable shielding or nearby power electronics
  6. A software or calibration issue in the motor controller or receiving module causing message rejection
  7. Another module on the same bus transmitting malformed frames that disrupt communication

How to diagnose and fix it

  1. Scan all modules and record every stored code, then verify whether U059C is current or history and whether other communication codes point to a shared bus fault
  2. Inspect the drive motor control module C connector for corrosion, backed-out pins, and water intrusion, and clean or repair as needed
  3. Check the controller area network bus wiring for continuity, shorts to ground or power, and correct termination resistance at the diagnostic connector
  4. Measure battery voltage and the motor controller's power and ground circuits under load to rule out supply-related data corruption
  5. Inspect high-voltage cable routing and shielding for damage that could introduce interference into the network
  6. If wiring and power are sound, substitute a known-good drive motor control module C or perform a module reflash per the manufacturer's procedure
  7. Clear codes and road-test the vehicle through several drive cycles to confirm the fault does not return

Why invalid data is not always a bad module

  • A single stored U059C often results from a momentary voltage dip during cranking or a weak 12-volt battery, so load-test the battery before condemning the motor controller.
  • The receiving module, not the drive motor control module C, sets this code, so the fault may lie in the receiver's ability to process valid frames rather than in the motor controller itself.
  • Corrosion inside a connector that looks dry from the outside is a frequent culprit on vehicles exposed to road salt or repeated pressure washing.
  • Aftermarket accessories wired into the controller area network bus can introduce invalid frames that mimic a failing motor controller and should be disconnected during diagnosis.
  • A history-only U059C with no drivability complaint may never return after clearing, and unnecessary module replacement is a common and costly misdiagnosis.

Can I keep driving with U059C?

If the vehicle drives normally with only the warning light on, you can drive cautiously to a repair shop, but avoid heavy acceleration and long trips until the fault is diagnosed. If the vehicle enters limp mode, loses power, or fails to start the drive system, stop driving and arrange a tow to prevent a safety risk.

Tools that help

Tools we recommend are in the Auto Veteran shop on Amazon. As an Amazon Associate we earn from qualifying purchases.

Guidance is general and written for all OBD-II vehicles. Exact tests and values vary by model, so confirm the fault before replacing parts.

Running on fumes Free guides aren't free to make. Top up the tank. Any amount, one time. Fuel the Garage