Toggle Side Panel

Shopping Cart

No products in the basket.

Shopping Cart

No products in the basket.

Close search
Home / DTC / U1190 — No receive fault detect signal

U1190 — No receive fault detect signal

Detailed page for trouble code U1190.

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

U1190

MITSUBISHI U — Network/User

No receive fault detect signal

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

Causes

  • Open or short in CAN/communication bus wiring
  • Disconnected or corroded connector at the affected module
  • Faulty or powered-down control module that should send the signal
  • Blown fuse or lost power/ground to the sending or receiving module
  • Poor termination or excessive bus resistance/noise on the communication network
  • Software/firmware mismatch or module not initialized after replacement

Symptoms

  • Malfunction Indicator Lamp (MIL) or warning lamp illuminated
  • Affected systems controlled by the missing message may be inoperative or revert to limp mode
  • Intermittent or permanent loss of function for related systems (e.g., ABS, transmission, climate, depending on module)
  • Multiple communication-related DTCs present
  • Vehicle may fail initial system checks or show module “not responding” in a scan tool

What to check

  • Read and record all stored and pending DTCs and freeze frame data with a capable scan tool
  • Note which module(s) are reporting loss of signal and whether any modules are not responding to the scanner
  • Verify battery voltage (should be within spec) and check relevant fuses and power/ground feeds for the affected module(s)
  • Visually inspect connectors and wiring for damage, corrosion, or disengagement at the sending and receiving modules
  • Check for other U-codes that indicate bus-wide problems (multiple modules)
  • Measure CAN bus termination resistance across CAN_H and CAN_L with ignition off (≈60 Ω typical with two 120 Ω terminators)

Signal parameters

  • Bus type: vehicle communication bus (typically CAN, ISO 11898)
  • Typical idle voltages: CAN_H ≈ 2.5 V, CAN_L ≈ 2.5 V (recessive)
  • Dominant state voltages: CAN_H ≈ 3.5 V, CAN_L ≈ 1.5 V (differential ≈2.0 V)
  • Typical data rates: commonly 250 kbps or 500 kbps depending on network (verify vehicle spec)
  • Expected: regular message frames from the sending module — absence or irregular timing indicates fault

Diagnostic algorithm

  1. Connect a diagnostic scan tool and record all U- and P-codes and module responses; identify which module’s fault-detect message is missing.
  2. Verify battery voltage and check related fuses and relays for the sending and receiving modules; repair/replace any blown fuses or faulty relays.
  3. Visually inspect connectors and wiring at both the sending and receiving modules for damage, corrosion, or poor seating; repair or reconnect as needed.
  4. Check power and ground circuits at the sending module: confirm proper voltage with ignition on and a good ground return.
  5. Measure CAN_H to CAN_L resistance with ignition off; expect around 60 Ω (two 120 Ω terminators). If open or far from expected, trace/repair wiring or terminators.
  6. With the ignition on and engine running if required, monitor CAN_H and CAN_L with an oscilloscope or high-speed data logger to confirm valid differential signals and message frames from the sending module.
  7. If messages are missing or corrupted, perform a wiggle test on harnesses and connectors while monitoring for changes; repair any intermittent wiring faults.
  8. If wiring and power/ground are good but the module still does not send messages, try to communicate directly with the suspected sending module using the scan tool. If it does not respond, consider replacing or reflashing the module per manufacturer procedures.
  9. After repairs, clear codes and road-test to verify the fault does not return. If multiple modules are affected, investigate shared power/ground or bus-level faults.

Likely causes

  • Loose or corroded connector at the sending module
  • Blown fuse or missing supply/ground to the sending module
  • CAN bus wiring damaged (pinched, chafed, rodent damage)
  • Sending module failed or is in sleep/off state
  • Bus termination resistor open or short causing communication failure

Fault status

⚠️ Status
No receive fault-detect signal: the control module did not receive the expected communication/message from another module. Indicates a communication/network, wiring, power/ground, or module fault.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 1.0-3.0 hours

Similar codes

U0100 U0073 U1000 U0115 U0121
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

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 .