Order processing time 24h
Free shipping !
Support service 24/7
100% Secure Payment
Free shipping !
Support service 24/7
100% Secure Payment
View Categories

5 min read

U1090 — SCP (J1850) Invalid or Missing Data for Non-Legislated Diagnostics #

The code description may vary depending on the vehicle manufacturer (OEM). Below are known description variations for U1090:

  • Ford: SCP (J1850) Invalid or Missing Data for Non-Legislated Diagnostics
  • General Motors (GM): Loss of Communication with Non-Legislated Diagnostic Module
  • Chrysler: No Communication with Non-Legislated Diagnostic Device
  • Mazda: Invalid Data Received from Non-Emissions Diagnostic Module

Summary of Code U1090 #

The U1090 diagnostic trouble code (DTC) signals a communication issue within the vehicle’s data network, specifically related to non-legislated diagnostic modules—those not required by emissions laws but still essential for vehicle operation. On most OEM vehicles, this code means that a message expected from a specific module was either incomplete, corrupted, or never arrived. The “SCP” stands for Standard Corporate Protocol, a Ford term for the J1850 communication standard, which is used by several manufacturers to allow modules (computers) to share information. When data is missing or incorrect, it can disrupt diagnostics, affect module functionality, and sometimes cause drivability issues or warning lights. This code does not directly indicate a faulty sensor, but rather points to network or module communication problems.

Common Symptoms for U1090 #

Drivers or technicians may notice a range of symptoms when the U1090 code is present. Sometimes, the effects are subtle or intermittent, while in other cases, they can impact vehicle operation more noticeably. Typical symptoms include:

  • Warning lights on the dashboard, such as the check engine light or service vehicle soon indicator
  • Loss of communication with specific modules during diagnostic scans
  • Intermittent operation of certain features (e.g., climate control, ABS, or instrument cluster functions)
  • Failure of remote or auxiliary systems to respond as expected
  • Possible drivability issues if the affected module communicates with critical control units

Most Likely Causes for U1090 #

The U1090 code is generally triggered by communication breakdowns on the vehicle’s data bus. These can result from wiring issues, module malfunctions, or connector problems. The most frequent causes, ranked by likelihood, are:

  1. Loose, corroded, or damaged wiring/connectors in the J1850/SCP communication network
  2. Failure or intermittent operation of a non-legislated diagnostic module (e.g., body control module, instrument cluster)
  3. Faulty network termination resistors, which regulate signal integrity on the data bus
  4. Incorrect aftermarket device installation that disrupts network traffic
  5. Shorts to power or ground within the communication circuit

Step-by-Step Diagnostic for U1090 #

A careful, methodical approach is essential for diagnosing U1090. Here’s a recommended step-by-step process:

  • 1. Scan all modules with a professional scan tool to check for related or additional communication codes.
  • 2. Identify affected modules by noting which devices are not communicating or reporting invalid data.
  • 3. Inspect wiring and connectors at the affected module(s) and along the data bus for corrosion, loose pins, or physical damage.
  • 4. Check for aftermarket equipment (e.g., remote starters, alarm systems) that may be spliced into network wiring.
  • 5. Test network resistance across the J1850/SCP lines to verify proper termination (usually around 60 ohms for J1850 networks).
  • 6. If possible, substitute or reprogram the suspected faulty module following OEM procedures.
  • 7. Clear codes and recheck for U1090 after repairs to confirm resolution.

Possible Repairs for U1090 #

Repairs should be directly guided by the diagnostic findings. The most common solutions include:

  • Repairing or replacing damaged wiring/connectors in the network circuit
  • Replacing a failed non-legislated diagnostic module if proven faulty
  • Removing or correcting aftermarket equipment causing network interruptions
  • Repairing grounds or power supplies to affected modules
  • Replacing termination resistors if resistance is out of specification
  • Updating or reprogramming module software per OEM technical service bulletins

Is It Safe to Drive With Code U1090? #

It depends on the affected module. In most cases, the vehicle may continue to operate with limited functionality if U1090 is present, especially if the module is not emission- or safety-critical. However, if key features such as ABS, power steering, or instrument displays are impacted, it is not recommended to drive until repairs are made. Persistent communication faults can also lead to other system malfunctions over time.

Vehicles Most Commonly Affected by U1090 #

While U1090 can occur on any vehicle using the J1850/SCP protocol, it is most often found on certain OEM models from the late 1990s to mid-2000s. The following vehicles are more frequently associated with this code:

  • Ford F-Series (F-150, F-250, F-350)
  • Ford Explorer, Expedition
  • Lincoln Navigator
  • Mercury Mountaineer
  • Chevrolet Silverado (older models)
  • GMC Sierra (older models)
  • Chrysler Town & Country, Dodge Caravan (early 2000s)
  • Mazda B-Series (J1850-equipped)

Common Mistakes & Best Practices for U1090 #

Proper diagnosis and repair of U1090 requires careful attention to detail and good diagnostic habits. Avoid these common mistakes:

  • Overlooking wiring and connector issues in favor of immediate module replacement
  • Ignoring the presence of aftermarket devices on the network
  • Not checking for related DTCs in other modules, missing broader network issues
  • Skipping OEM service information or technical bulletins related to the code
  • Failing to verify repairs by rescanning and testing all relevant systems

U1090 FAQ #

Here are quick answers to common questions about the U1090 code:

  • Q: Will U1090 clear itself if the problem goes away?
    A: Sometimes, but not always. Many modules require a manual clear with a scan tool after the underlying issue is repaired. If the problem is intermittent, the code may return.
  • Q: Can a weak battery cause U1090?
    A: Yes. Low system voltage can disrupt module communication, especially during startup or if the battery is failing. Always verify battery and charging system health during diagnosis.
  • Q: Does U1090 affect emissions testing?
    A: Not directly, since it references non-legislated (non-emissions) modules. However, if other emissions-related modules are affected or cannot communicate, the vehicle may not pass inspection.