Home / DTC / U059F — Invalid Data Received From NOX Sensor “B”

U059F — Invalid Data Received From NOX Sensor “B”

Detailed page for trouble code U059F.

33,028codes
59brands
10,567generic
22,461specific
Reset
Code

U059F

HYUNDAI U — Network/User

Invalid Data Received From NOX Sensor “B”

Views: UK: 10 EN: 46 RU: 15
AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • NOx sensor B failure (internal fault or contamination)
  • Open, shorted, corroded or damaged wiring/connectors between sensor and control module
  • Poor power or ground to the sensor (heater or signal reference)
  • Heater circuit failure preventing proper sensor operation
  • Exhaust leaks or aftertreatment damage affecting sensor readings
  • CAN/CAN-FD or LIN bus communication faults or module software error

Symptoms

  • Check Engine / MIL illuminated with U059F stored
  • Possible additional NOx/aftertreatment related DTCs
  • Reduced aftertreatment performance, failed emissions test, or regeneration issues (diesel/SCR systems)
  • Possible store of other network communication codes
  • Engine runs normally in many cases (symptom may be limited to emissions/regeneration behavior)

What to check

  • Read and record freeze frame data and all stored codes (including pending and history)
  • Inspect sensor B wiring harness and connector for damage, corrosion, looseness or water ingress
  • Check for related codes (heater circuit, CAN bus, other NOx sensors)
  • Visually inspect exhaust and aftertreatment hardware for damage or leaks near sensor B
  • Backprobe sensor connector and measure reference voltage, signal and heater power/ground
  • Perform wiggle test on harness while monitoring live data for intermittent changes

Signal parameters

  • Typical NOx sensor signal: low-voltage analog output expected within manufacturer-specific range (examples often 0–1.0 V or 0–5.0 V depending on design) — consult vehicle spec
  • Heater circuit supply: usually battery voltage when active; expected DC supply 10–14 V with good continuity
  • Heater resistance (room temp, typical example): ~5–100 ohms depending on sensor design — check manufacturer spec
  • Expected signal behavior: sensor voltage/current should change when exhaust composition changes (load, throttle, rich/lean events). Exact ranges are manufacturer-specific — refer to service data

Diagnostic algorithm

  1. Read all DTCs and freeze frame; note any related NOx, heater, or communication codes.
  2. Visually inspect NOx sensor B connector and harness for damage, corrosion, water, or heat damage. Repair as needed.
  3. With ignition on (engine off), verify sensor heater supply and ground at the connector (compare to vehicle wiring diagram).
  4. Measure heater resistance at the sensor terminals (spec per manufacturer). If infinite or out of spec, suspect heater open/short and replace sensor.
  5. Backprobe signal pin with engine running; observe live NOx sensor data while inducing exhaust richness/lean conditions (throttle changes) — signal should vary. If frozen or out-of-range, suspect sensor or wiring.
  6. Check continuity and resistance between sensor ground/signal and ECM connector; repair open/shorts. Perform wiggle test to find intermittent faults.
  7. Inspect CAN/LIN bus integrity and related modules if communication-type failure suspected; check termination and voltages.
  8. If wiring and power/ground are good but signal remains invalid, replace NOx sensor B and clear codes. Retest and verify at operating temperature.
  9. If replacement does not clear code or failure returns, consider ECM/aftertreatment controller fault or require dealer-level reprogramming/advanced diagnostics.

Likely causes

  • Failed NOx sensor B (most common)
  • Damaged/shorted signal or ground wire to ECM
  • Failed heater circuit in the sensor preventing proper operation
  • Connector corrosion or poor mating at sensor/ECM
  • Intermittent CAN/communication fault or module software error

Fault status

⚠️ Status
Invalid data received from NOx sensor ‘B’ — sensor signal or communication is outside expected parameters or not being received by control module.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 1.0-2.5 hours

Similar codes

Your experience will help others
+100 karma for a short comment :)
Send to email