OBD-II fault code

U047E: Invalid Data Received From Restraints System Sensor N

What it means

A receiving module detected implausible data from restraints system sensor N (satellite crash sensor). Acceleration profile values fail plausibility checks against other crash sensors and are rejected.

At a glance

  • Usually lights the warning light of the system that lost communication

How it works

Restraints system sensor N is identified here as a satellite crash sensor that reports acceleration data to the restraint system. A receiving module sets U047E when sensor N's acceleration profile fails plausibility checks against other crash sensors and is rejected.

Common causes

Most likely first.

  1. Module internal fault or sensor input drift
  2. Software version mismatch after replacement
  3. Gateway module routing CAN messages incorrectly

Symptoms

  • Multiple warning lights may illuminate
  • Affected modules may go into limp mode or shut down
  • Specific functions inoperative depending on module
  • Diagnostic tools may show communication faults

How to diagnose it

  1. Use an SRS-capable scan tool to record which module set U047E, related crash-sensor or communication codes, and any available event data before clearing codes.
  2. Check service information for sensor N's specified location and compare its reported data and status with the other crash sensors on the scan tool.
  3. With the ignition off and following the manufacturer's SRS safety precautions, inspect sensor N's mounting area, connector, and harness for damage, corrosion, looseness, or evidence of impact or repair.
  4. Check sensor N's power, ground, and network connections against the wiring diagram and manufacturer's specification.
  5. If the vehicle recently had a restraint module or sensor replaced, verify the installed component and software configuration against manufacturer service information before condemning a module.
  6. If sensor N's data still conflicts with the other crash sensors, follow the manufacturer's SRS diagnostic procedure to isolate a sensor, restraint module, or network routing fault.

Common fixes

  • Repair a damaged, loose, or corroded sensor N connector or wiring.
  • Correct sensor N's mounting or restore its power, ground, or network connection as specified by the manufacturer.
  • Install the correct manufacturer-approved software configuration after a documented replacement mismatch.
  • Replace sensor N or repair the restraint module or network only after the manufacturer's diagnostic procedure identifies the fault.

Can I keep driving?

The restraint system may not be able to use sensor N's crash data, so airbags or related protections may be impaired. Arrange prompt SRS diagnosis and avoid disturbing the sensor or its wiring; do not rely on the affected restraints in a crash.

A code shows where the control module detected a fault, not always which part failed. Check the causes in order and confirm with a test before replacing parts. Have several codes? Check them together

This is a generic code: it means the same on every make. The car’s maker may add more detail in its own service information.

Codes for the same component

Nearby codes