U0195 — Data Bus: Subscription Entertainment Receiver Module – No Communication #
Note: The description of DTC U0195 may differ depending on the vehicle manufacturer. Always refer to OEM documentation for your specific model.
Known variations:
- “Lost Communication With Satellite Radio Receiver” (Ford)
- “No Communication With Entertainment Control Module” (GM, Volvo)
- “Entertainment Subscription Receiver Module Communication Fault” (Jaguar/Land Rover)
- “CAN Communication With Audio/Video Control Module Lost” (Toyota/Lexus)
U0195 — Code Summary #
The U0195 diagnostic trouble code (DTC) indicates that the vehicle’s control modules have lost communication with the Subscription Entertainment Receiver Module. This module is typically responsible for handling subscription-based media services, such as satellite radio or streaming entertainment. The code is triggered when the main data network, known as the CAN (Controller Area Network) bus, fails to exchange messages with the entertainment receiver module for a predetermined period. This loss of communication can affect in-car audio, infotainment, or telematics functionality. While U-codes are often considered “network” codes, they signal potential wiring, module, or network faults that may impact more than just entertainment features. Prompt diagnosis helps prevent cascading issues with other control modules.
Frequent Symptoms for Code U0195 #
Most drivers notice this fault through changes in the infotainment system. Since the Subscription Entertainment Receiver Module controls subscription media, you may experience partial or complete loss of these services. The main symptoms include:
- No audio from satellite or subscription-based radio
- Infotainment screen displaying errors or unavailable services
- Warning light or message: “Entertainment System Not Available”
- Inability to access or change subscription channels
- Other modules temporarily losing communication or reporting faults
Probable Causes for Code U0195 #
The most common root causes of U0195 are related to wiring or power issues but can also involve module failure or network disruptions. Here is a ranked list, from most to least frequent:
- Open, shorted, or corroded wiring/connectors in the CAN bus circuit leading to the entertainment receiver module
- Blown fuse or lost power/ground at the subscription entertainment receiver module
- Faulty Subscription Entertainment Receiver Module itself (internal failure or software corruption)
- Network congestion or interference (other modules overloading the CAN bus)
- Loose or disconnected harness after repairs or upgrades
Step-by-Step Diagnosis for Code U0195 #
Accurate troubleshooting of U0195 requires a logical, step-by-step approach. Here’s how a technician (or advanced DIYer) should proceed:
- 1. Verify code presence: Use a professional scan tool to check for U0195 and any related U-codes. Record freeze frame data if available.
- 2. Inspect power/ground: Locate the entertainment receiver module, check all related fuses, and test for correct power and ground supply with a multimeter.
- 3. Check CAN wiring: Visually inspect the CAN High and CAN Low wires for damage, corrosion, or loose connectors between the main harness and the module.
- 4. Perform module communication test: Using the scan tool, attempt to directly communicate with the subscription entertainment receiver module. A “no response” situation confirms a network or module fault.
- 5. Perform a wiggle test: Gently flex wiring harnesses while monitoring code status—an intermittent fault often points to wiring or connector issues.
- 6. Test with known good module (if possible): Swap in a working module to rule out hardware failure.
Possible Repairs for Code U0195 #
After pinpointing the root cause, repairs for U0195 may include:
- Repair or replace damaged CAN bus wiring/connectors to the entertainment module
- Replace blown fuses or restore power/ground supply to the module
- Replace or reprogram the Subscription Entertainment Receiver Module (sometimes requires OEM-level tools)
- Secure or reconnect loose harnesses, especially after recent dashboard or audio work
- Clear DTCs and perform a system reset to confirm repair effectiveness
Can You Drive With Code U0195? #
Yes, in most cases you can continue to drive with code U0195. This code typically affects only the entertainment or infotainment features, not critical engine or safety systems. However, if you notice additional warning lights or your vehicle’s communication network shows more widespread issues, have it diagnosed promptly. Loss of communication with other modules can eventually lead to more severe problems if left unchecked.
Vehicles Most Commonly Affected by U0195 #
While U0195 can occur on any vehicle equipped with a subscription-based entertainment system, it is more frequently seen on:
- Ford/Lincoln (SYNC and SiriusXM systems)
- General Motors (Chevrolet, GMC, Cadillac, Buick with OnStar or XM Radio)
- Volvo (Sensus Connect infotainment)
- Jaguar/Land Rover
- Toyota/Lexus (with advanced infotainment packages)
- Some Volkswagen/Audi models (with satellite radio modules)
Common Mistakes & Best Practices for U0195 #
Misdiagnosing U0195 is easy without a methodical approach. Here are frequent errors and the best ways to avoid them:
- Assuming the module is faulty without checking power, ground, and CAN wiring first
- Replacing fuses without investigating why they blew
- Ignoring intermittent communication faults—these often mean loose or corroded connectors
- Overlooking recent work (radio upgrades, dashboard repairs) that may have disturbed wiring
- Not clearing codes and verifying system operation after repairs
U0195 Express FAQ #
Q1: Will this code drain my battery or cause other electrical issues?
A1: U0195 itself doesn’t drain the battery, but if the module keeps trying to reconnect or there is a CAN network problem, it could lead to higher standby current. Always check for battery drain if you notice repeated dead batteries.
Q2: Can I reset this code by disconnecting the battery?
A2: Disconnecting the battery may clear the code temporarily, but unless the root cause (wiring, power loss, or module fault) is addressed, the code will likely return.




