U1137 — SCP (J1850) Invalid or Missing Data for Telltales #

Note: The code description may differ depending on the vehicle manufacturer.

• U1137: SCP (J1850) Invalid or Missing Data for Telltales (Ford, Lincoln, Mercury)
• U1137: CAN Data Bus: Signal Error (Mazda)
• U1137: Telltale Data Communication Error (Chrysler, Jeep, Dodge)
• U1137: Network Communication Error – Telltale Data (General Motors – GM)

Summary of code U1137 #

The U1137 diagnostic trouble code (DTC) is related to issues in the vehicle’s communication network—specifically the Standard Corporate Protocol (SCP) J1850 bus. This code signals that the data required to control or display dashboard warning lights (called telltales) is invalid, missing, or not received as expected by a critical module, like the instrument cluster. Automakers use different terms for “telltales,” but they generally refer to the dashboard indicators that alert you to system statuses or warnings. When this code appears, it usually points to a communication fault between modules, a wiring problem, or a malfunctioning control unit. Addressing U1137 promptly helps ensure that important warning lights continue to function, keeping the driver informed of potential safety or mechanical issues.

Frequent Symptoms for code U1137 #

When U1137 is set, you might notice odd or inconsistent behavior from your dashboard warning lights. Sometimes, one or more telltale indicators may not illuminate when they should, or they may stay on even after the issue is resolved. In other cases, a cluster of warning lights could flicker sporadically, causing confusion or concern. Intermittent loss of data to the cluster may also result in a temporary “dead” or unresponsive dashboard. Other vehicle features relying on network data, such as the odometer or trip computer, may also be affected.

• Warning lights (telltales) do not illuminate when expected
• Warning lights remain on after resolving the original fault
• Flickering or erratic dashboard indicators
• Instrument cluster may become unresponsive or “dead”
• Other dashboard functions (odometer/trip computer) may fail
• Intermittent chimes or warning sounds

Probable Causes for code U1137 #

The U1137 code is generally triggered by issues affecting data communication across the vehicle’s SCP (J1850) network. The root cause can range from simple wiring problems to faulty electronic control modules. Addressing the most common causes first can save time and resources during diagnosis.

1. Loose, corroded, or damaged SCP (J1850) wiring or connectors
2. Faulty instrument cluster (IC) or other receiving module
3. Failed or malfunctioning transmitting module (such as BCM, PCM, or ABS module)
4. Poor ground or power supply to involved modules
5. Aftermarket device interfering with network communication
6. Internal short or open circuit within network wiring

Step-by-step Diagnosis for code U1137 #

Diagnosing U1137 requires methodical troubleshooting, as communication errors can be elusive and sometimes intermittent. Use a systematic approach, starting with the simplest and most likely faults before considering more complex possibilities. A scan tool capable of reading network data and module status is essential for efficient diagnosis.

• 1. Confirm the code. Use a scan tool to verify U1137 is active and note if other network-related codes are present.
• 2. Review freeze-frame data. Check when the code was set and under what conditions.
• 3. Inspect all related wiring. Visually examine the SCP (J1850) network wiring and connectors for looseness, corrosion, or damage, especially between the instrument cluster and other modules.
• 4. Check power and grounds. Ensure all involved modules have proper power supply and ground connections.
• 5. Disconnect aftermarket accessories. Remove or isolate any non-OEM electronics that could disrupt the network.
• 6. Use a wiring diagram. Trace the communication circuit and test for continuity or shorts with a multimeter.
• 7. Module cross-check. Use the scan tool to check if all required modules are communicating on the network.
• 8. Swap or substitute modules (if available and safe) to confirm module faults.
• 9. Clear codes and retest. After repairs or component swaps, clear DTCs and verify if U1137 returns.

Possible Repairs for code U1137 #

The repair for U1137 should target the root cause identified during diagnosis. Most solutions involve restoring reliable communication on the network or replacing a failed module. Sometimes even a simple wiring fix can restore normal function.

• Repair or replace damaged, corroded, or loose SCP (J1850) wiring and connectors
• Clean and tighten ground points and module connectors
• Replace a faulty instrument cluster or other affected module (body control module, powertrain control module, ABS module, etc.)
• Remove or properly integrate interfering aftermarket devices
• Fix internal wiring shorts or open circuits
• Update module software (if recommended and available from OEM)

Can you drive with code U1137? #

Limited—Caution Advised: While some vehicles may appear to operate normally with the U1137 code present, driving with this code is not recommended for long periods. The main risk is that you may not receive critical warning signals—like check engine, ABS, or airbag lights—if telltale data is missing or invalid. In some cases, safety systems may not notify you of a developing problem. Prompt diagnosis and repair are essential for ensuring you remain informed and safe on the road.

Vehicles Most Commonly Affected by code U1137 #

This code appears most often on vehicles manufactured by Ford Motor Company (including Ford, Lincoln, and Mercury brands), but it can also occur on other vehicles using the SCP (J1850) network. Chrysler, Jeep, Dodge, Mazda, and certain GM models have also reported this code, particularly in vehicles built from the late 1990s through the mid-2000s.

• Ford F-Series (F-150, F-250, etc.)
• Ford Explorer and Expedition
• Lincoln Navigator and Town Car
• Mercury Mountaineer
• Chrysler 300 / PT Cruiser
• Jeep Grand Cherokee, Wrangler
• Dodge Ram, Dakota
• Mazda Tribute
• GM light trucks (selected models, late 90s–early 2000s)

Common Mistakes & Best Practices for code U1137 #

Misdiagnosing U1137 can lead to unnecessary module replacements and wasted expense. It’s vital to check the basics—wiring, power, and grounds—before condemning expensive components. Network communication issues can be intermittent and are often made worse by overlooked connector or harness problems.

• Skipping basic wiring and connector inspections
• Overlooking ground and power supply issues to modules
• Replacing instrument cluster or modules prematurely
• Failing to check for aftermarket accessories interfering with the network
• Ignoring related network DTCs that may provide clues
• Using generic scan tools that can’t see all network modules

Express FAQ for code U1137 #

Here are quick answers to the most common questions about U1137:

• Q: Will U1137 cause my car to break down?
  A: Generally, no. U1137 usually doesn’t cause the engine to stall or the car to become undriveable. However, it can prevent you from being alerted to critical problems, so it should not be ignored.
• Q: Can I reset the code myself?
  A: You can clear U1137 with a scan tool, but unless the underlying problem is fixed, the code will likely return. Always address the root cause for a lasting solution.
• Q: Is this a common code?
  A: U1137 is relatively common on certain Ford and Chrysler vehicles where network aging or minor wiring faults are present.