Toggle Side Panel

Shopping Cart

No products in the basket.

Shopping Cart

No products in the basket.

Close search
Home / DTC / U1123 — SCP (J1850) invalid or missing data for odometer

U1123 — SCP (J1850) invalid or missing data for odometer

Detailed page for trouble code U1123.

34,405codes
59brands
11,914generic
22,491specific
All codes P-codes (Powertrain) B-codes (Body) C-codes (Chassis) U-codes (Network/User) Tesla Alerts
Reset
Code

U1123

LAND ROVER U — Network/User

SCP (J1850) invalid or missing data for odometer

Brand: LAND ROVER
Type: U — Network/User
AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Faulty instrument cluster (odometer data source)
  • Faulty gateway/BCM or other sending module
  • Open, shorted or corroded wiring/connectors on the J1850/SCP bus
  • Low or unstable battery/vehicle voltage
  • Software/firmware mismatch or missing calibration in a module
  • Aftermarket device (alarm, radio, tracker) interfering with the bus

Symptoms

  • Odometer blank, incorrect, or not updating
  • Service reminders or interval functions incorrect
  • Other modules reporting odometer-related faults or erroneous mileage
  • Possible MIL or stored communication-related U-codes
  • Intermittent features tied to vehicle distance (e.g., service lamps) not working correctly

What to check

  • Connect a factory-level scan tool; read U1123 and any related U- or B- codes and freeze frame data
  • Verify battery voltage with ignition on and engine off (should be stable and within spec)
  • Inspect instrument cluster, gateway/BCM and relevant harness connectors for corrosion, bent pins, or water
  • Check for aftermarket devices connected to wiring or bus and remove/disable for test
  • Confirm module software/flash levels and compare to latest Technical Service Bulletins (TSBs)
  • Perform a visual check of J1850/SCP wiring for chafing, open or pinched areas

Signal parameters

  • Odometer message transmitted over SCP (J1850) network — should appear at regular intervals while key is ON
  • Message format and ID are manufacturer-specific; verify expected message ID with factory data
  • Physical bus uses single-wire J1850 levels; check for proper voltage swings and absence of constant short to Vb or ground
  • If available, use a scope or factory bus diagnostic tool to confirm message timing and signal integrity

Diagnostic algorithm

  1. Record freeze frame and all stored codes. Note whether code is permanent or intermittent. Attempt to reproduce condition.
  2. Check and restore battery voltage to specification. Clear codes and see if U1123 returns.
  3. Inspect connectors and harnesses at instrument cluster, BCM/gateway and any modules that send odometer data. Repair any damage or corrosion.
  4. Use a scan tool to monitor SCP/J1850 traffic. Identify if odometer message is present and valid. If message absent, determine which module should be sending it.
  5. If traffic is present but corrupted, use an oscilloscope to examine bus waveform for noise, short, or open conditions. Repair wiring faults as needed.
  6. If a specific module is not responding or is the confirmed sender and wiring is good, attempt reflash or software update per factory procedure. If update unavailable or unsuccessful, consider module replacement and ensure proper programming/coding after replacement.
  7. After repairs, clear codes, verify odometer operation, and perform a road test or extended key-on verification to confirm the fault does not return.

Likely causes

  • Damaged connector or corroded pins at instrument cluster or gateway
  • Failed instrument cluster electronics
  • No power or poor ground to a module that supplies odometer data
  • Noise or short on the J1850/SCP communication line
  • Module requiring software update or reprogramming after replacement

Fault status

⚠️ Status
SCP (J1850) invalid or missing odometer data — communication or sender module fault. Check instrument cluster, gateway and J1850/SCP bus integrity.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 1.0-3.0 hours

Similar codes

U0100 U0073 U1121 U1124 P0500
320

Browse 320 LAND ROVER manuals: repair procedures, diagnostics, wiring diagrams, component locations, service data and Labor Times by year, model and trim.

LAND ROVER

Your experience will help others
+100 karma for a short comment :)
Keep it short and practical. Up to 500 characters.
Send to email
Code

U1123

MITSUBISHI U — Network/User

PDC(CAN message)

Brand: MITSUBISHI
Type: U — Network/User
AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Faulty instrument cluster (odometer data source)
  • Faulty gateway/BCM or other sending module
  • Open, shorted or corroded wiring/connectors on the J1850/SCP bus
  • Low or unstable battery/vehicle voltage
  • Software/firmware mismatch or missing calibration in a module
  • Aftermarket device (alarm, radio, tracker) interfering with the bus

Symptoms

  • Odometer blank, incorrect, or not updating
  • Service reminders or interval functions incorrect
  • Other modules reporting odometer-related faults or erroneous mileage
  • Possible MIL or stored communication-related U-codes
  • Intermittent features tied to vehicle distance (e.g., service lamps) not working correctly

What to check

  • Connect a factory-level scan tool; read U1123 and any related U- or B- codes and freeze frame data
  • Verify battery voltage with ignition on and engine off (should be stable and within spec)
  • Inspect instrument cluster, gateway/BCM and relevant harness connectors for corrosion, bent pins, or water
  • Check for aftermarket devices connected to wiring or bus and remove/disable for test
  • Confirm module software/flash levels and compare to latest Technical Service Bulletins (TSBs)
  • Perform a visual check of J1850/SCP wiring for chafing, open or pinched areas

Signal parameters

  • Odometer message transmitted over SCP (J1850) network — should appear at regular intervals while key is ON
  • Message format and ID are manufacturer-specific; verify expected message ID with factory data
  • Physical bus uses single-wire J1850 levels; check for proper voltage swings and absence of constant short to Vb or ground
  • If available, use a scope or factory bus diagnostic tool to confirm message timing and signal integrity

Diagnostic algorithm

  1. Record freeze frame and all stored codes. Note whether code is permanent or intermittent. Attempt to reproduce condition.
  2. Check and restore battery voltage to specification. Clear codes and see if U1123 returns.
  3. Inspect connectors and harnesses at instrument cluster, BCM/gateway and any modules that send odometer data. Repair any damage or corrosion.
  4. Use a scan tool to monitor SCP/J1850 traffic. Identify if odometer message is present and valid. If message absent, determine which module should be sending it.
  5. If traffic is present but corrupted, use an oscilloscope to examine bus waveform for noise, short, or open conditions. Repair wiring faults as needed.
  6. If a specific module is not responding or is the confirmed sender and wiring is good, attempt reflash or software update per factory procedure. If update unavailable or unsuccessful, consider module replacement and ensure proper programming/coding after replacement.
  7. After repairs, clear codes, verify odometer operation, and perform a road test or extended key-on verification to confirm the fault does not return.

Likely causes

  • Damaged connector or corroded pins at instrument cluster or gateway
  • Failed instrument cluster electronics
  • No power or poor ground to a module that supplies odometer data
  • Noise or short on the J1850/SCP communication line
  • Module requiring software update or reprogramming after replacement

Fault status

⚠️ Status
SCP (J1850) invalid or missing odometer data — communication or sender module fault. Check instrument cluster, gateway and J1850/SCP bus integrity.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 1.0-3.0 hours

Similar codes

U0100 U0073 U1121 U1124 P0500
406

Browse 406 MITSUBISHI manuals: repair procedures, diagnostics, wiring diagrams, component locations, service data and Labor Times by year, model and trim.

MITSUBISHI

Your experience will help others
+100 karma for a short comment :)
Keep it short and practical. Up to 500 characters.
Send to email
Code

U1123

Other U — Network/User

SCP (J1850) Invalid or Missing Data for Odometer

Brand: Other
Type: U — Network/User
AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Faulty instrument cluster (odometer data source)
  • Faulty gateway/BCM or other sending module
  • Open, shorted or corroded wiring/connectors on the J1850/SCP bus
  • Low or unstable battery/vehicle voltage
  • Software/firmware mismatch or missing calibration in a module
  • Aftermarket device (alarm, radio, tracker) interfering with the bus

Symptoms

  • Odometer blank, incorrect, or not updating
  • Service reminders or interval functions incorrect
  • Other modules reporting odometer-related faults or erroneous mileage
  • Possible MIL or stored communication-related U-codes
  • Intermittent features tied to vehicle distance (e.g., service lamps) not working correctly

What to check

  • Connect a factory-level scan tool; read U1123 and any related U- or B- codes and freeze frame data
  • Verify battery voltage with ignition on and engine off (should be stable and within spec)
  • Inspect instrument cluster, gateway/BCM and relevant harness connectors for corrosion, bent pins, or water
  • Check for aftermarket devices connected to wiring or bus and remove/disable for test
  • Confirm module software/flash levels and compare to latest Technical Service Bulletins (TSBs)
  • Perform a visual check of J1850/SCP wiring for chafing, open or pinched areas

Signal parameters

  • Odometer message transmitted over SCP (J1850) network — should appear at regular intervals while key is ON
  • Message format and ID are manufacturer-specific; verify expected message ID with factory data
  • Physical bus uses single-wire J1850 levels; check for proper voltage swings and absence of constant short to Vb or ground
  • If available, use a scope or factory bus diagnostic tool to confirm message timing and signal integrity

Diagnostic algorithm

  1. Record freeze frame and all stored codes. Note whether code is permanent or intermittent. Attempt to reproduce condition.
  2. Check and restore battery voltage to specification. Clear codes and see if U1123 returns.
  3. Inspect connectors and harnesses at instrument cluster, BCM/gateway and any modules that send odometer data. Repair any damage or corrosion.
  4. Use a scan tool to monitor SCP/J1850 traffic. Identify if odometer message is present and valid. If message absent, determine which module should be sending it.
  5. If traffic is present but corrupted, use an oscilloscope to examine bus waveform for noise, short, or open conditions. Repair wiring faults as needed.
  6. If a specific module is not responding or is the confirmed sender and wiring is good, attempt reflash or software update per factory procedure. If update unavailable or unsuccessful, consider module replacement and ensure proper programming/coding after replacement.
  7. After repairs, clear codes, verify odometer operation, and perform a road test or extended key-on verification to confirm the fault does not return.

Likely causes

  • Damaged connector or corroded pins at instrument cluster or gateway
  • Failed instrument cluster electronics
  • No power or poor ground to a module that supplies odometer data
  • Noise or short on the J1850/SCP communication line
  • Module requiring software update or reprogramming after replacement

Fault status

⚠️ Status
SCP (J1850) invalid or missing odometer data — communication or sender module fault. Check instrument cluster, gateway and J1850/SCP bus integrity.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 1.0-3.0 hours

Similar codes

U0100 U0073 U1121 U1124 P0500
8,038

The library contains 8,038 repair and diagnostic manuals. Choose a brand to open the full manual tree by year, model and trim.

ALFA ROMEO
89
AUDI
1,160
BMW
479
CHEVROLET
356
DAEWOO
75
FIAT
26
GENESIS
207
HUMMER
138
HYUNDAI
371
ISUZU
86
LAND ROVER
320
LEXUS
280
LINCOLN
166
MERCEDES-BENZ
856
MERCURY
296
MITSUBISHI
406
PORSCHE
136
TESLA
58
TOYOTA
2,042
TRIUMPH
131
VOLKSWAGEN
139
VOLVO
221
Your experience will help others
+100 karma for a short comment :)
Keep it short and practical. Up to 500 characters.
Send to email

Report

Harassment or bullying behavior
Contains mature or sensitive content
Contains misleading or false information
Contains abusive or derogatory content
Contains spam, fake content or potential malware

Block Member?

Please confirm you want to block this member.

You will no longer be able to:

  • See blocked member's posts
  • Mention this member in posts
  • Invite this member to groups
  • Message this member
  • Add this member as a connection

Please note: This action will also remove this member from your connections and send a report to the site admin. Please allow a few minutes for this process to complete.

Report

You have already reported this .