| DTC Data Sheet | |
| System | Network |
| Standard | Manufacturer Specific |
| Fault type | Communication Loss |
| Official meaning | Lost communication with tilt & telescopic module |
| Definition source | Lexus factory description · Autel MaxiSys Ultra & EV |
U1115 means your Lexus ES lost communication with the tilt and telescopic steering column module. Most owners notice the steering wheel may not move to the saved position. In some cases, the memory functions act up or stop working. According to Lexus factory diagnostic data, this code indicates “Lost communication with tilt & telescopic module.” That definition matters because a U-code does not prove a bad module. It proves the network did not deliver expected messages. Your next step is to confirm if the tilt/telescope module went offline, or if power, ground, or network wiring dropped out.
Decode any Lexus ES VIN — free recalls, specs & safety ratings — free VIN decoder with NHTSA data
U1115 Quick Answer
U1115 on Lexus means the vehicle’s network stopped receiving messages from the tilt & telescopic module. Diagnose power, ground, and network integrity to that module before replacing any parts.
What Does U1115 Mean?
Official meaning (Lexus): Lost communication with tilt & telescopic module. In plain terms, at least one other control module in the Lexus ES expected to “hear from” the steering column tilt/telescope controller. It did not receive those updates for a period long enough to set a fault. That usually shows up as inoperative tilt/telescope movement, memory recall issues, or an intermittent “dead” steering column adjustment.
What the vehicle actually checks: The setting module monitors message presence on the in-vehicle network. It looks for a valid ID and updates within a timing window. Why that matters: loss of messages can come from several sources. The tilt/telescope module may lose power or ground, a connector may loosen, or the network line may open, short, or suffer high resistance. Diagnosis must determine whether the module failed, or the vehicle simply could not communicate with it.
Theory of Operation
Under normal operation, the tilt & telescopic module controls motors and position sensing for steering column movement. It also exchanges data with other Lexus modules. Those modules may include a main body controller, a gateway, and memory seat or personalization logic. The network carries commands, position status, and confirmation messages.
U1115 sets when the expected network communication stops. A power or ground drop will take the tilt/telescope module offline. A network wiring fault can isolate the module even when it still powers up. Intermittent faults often appear during column movement because motor load, harness flex, and connector strain peak at that moment.
Symptoms
U1115 often shows up as a scan-tool communication issue first, then a steering column function complaint.
- Scan tool Tilt/telescope module does not respond, disappears from the ECU list, or drops out intermittently during a health check.
- Column adjust Tilt and telescopic movement inoperative, works only in one direction, or works intermittently.
- Memory recall Steering wheel does not return to stored driver position, or recall stops mid-travel.
- Entry/exit Easy-exit steering movement does not operate, or operates only sometimes.
- Intermittent reset Function returns after a key cycle, then fails again after driving or after adjustment.
- Related warnings Additional network or body-related U-codes appear in multiple modules.
- Noise/no movement Switch commands register, but motors do not run and no actuator sound occurs.
Common Causes
- Tilt & telescopic module power supply fault: A blown fuse, faulty relay, or poor power feed stops the module from powering up, so other Lexus modules log a lost-communication DTC.
- High-resistance ground at the seat/column ground point: Corrosion or a loose fastener increases voltage drop under load and makes the module reset, which breaks network messages.
- Connector fretting or moisture intrusion at the module: Light corrosion and pin tension loss create intermittent opens that drop the module off the network during vibration or temperature changes.
- Harness damage in a moving area: A pinched or chafed harness near the steering column or under-dash routing can open the network or power/ground circuits when the column moves.
- Network circuit open or short (CAN/LIN, platform-dependent): An open, short-to-ground, or short-to-power on the communication lines prevents the tilt/telescope module from exchanging messages.
- Network connector/junction issue: A loose junction connector, splice, or gateway-related connection increases resistance and disrupts communication to the tilt/telescope module.
- Aftermarket device interference: Remote start, alarm, or added electronics can load the network or disturb power feeds, causing intermittent module dropouts.
- Module internal fault: Internal logic or driver faults can stop the module from transmitting even with correct power, ground, and network integrity.
Diagnosis Steps
You need a capable scan tool with a Lexus network scan, DTC detail, and data list access. Use a DVOM for voltage-drop testing under load. A back-probe kit, terminal tension tools, and basic wiring repair supplies help. Service information matters here because Lexus network architecture and the module’s bus type vary by platform.
- Run a full network scan and confirm U1115 in all reporting modules. Record DTC status as pending or confirmed/stored. Save freeze frame for each reporting module. Focus on ignition state, vehicle speed, battery voltage, and any companion U-codes.
- Before any meter work at the module, check power distribution. Inspect and test related fuses and any seat/column or ECU-IG feeds that could power the tilt & telescopic module. Use a test light or loaded fuse check, not continuity alone. Verify whether the tilt/telescope module appears in the scan tool’s ECU list.
- If the scan tool cannot see the tilt/telescope module, attempt a direct “health check” again with ignition ON. Note which modules drop out together. Group dropouts often point to a shared power feed, shared ground, or a network branch issue.
- Verify module power and ground under load. Keep the circuit operating by commanding tilt/telescope movement if the scan tool supports active tests, or by turning ignition ON and waking the network. Measure voltage drop on the power feed and ground path. Accept less than 0.1V drop on the ground side with the circuit loaded.
- Inspect the tilt & telescopic module connector and nearby harness routing. Look for backed-out pins, water tracks, green corrosion, and terminal spread. Pay attention to harness sections that flex with steering column movement or tilt/telescope travel.
- Perform a wiggle test while watching live network status and DTC counters. Use a scan tool snapshot you trigger manually during the wiggle test. Freeze frame shows conditions when the DTC set. A snapshot captures the moment an intermittent dropout happens during your test.
- Identify the communication protocol for this module in service information (CAN, LIN, or gateway-routed network). Then test the communication circuits for opens and shorts. With ignition ON, check for proper network bias presence. Ignition OFF readings do not provide a valid reference for communication line bias.
- If you suspect an open, isolate sections of the harness and junctions. Check continuity end-to-end only after you unload and disconnect the correct endpoints. Then re-check the same path with a loaded test when possible. High resistance can pass continuity but fail under load.
- If the tilt/telescope module appears on the network but U1115 still sets, look for message-related companion codes. Check for low system voltage, wake-up issues, or gateway codes that could interrupt message routing. Also verify that the module stays awake and does not reset during commanded movement.
- Clear DTCs and perform a confirmation drive cycle. Re-run the network scan and verify U1115 does not return as pending or confirmed. If the monitor behaves like a Type B logic on this platform, expect that a confirmed code may require the fault on two consecutive trips. A hard power/ground fault usually returns immediately on key-on.
Professional tip: If U1115 appears in multiple modules, treat it as a network symptom first. Prove the tilt/telescope module has stable power and a low-drop ground under load. Next prove the communication lines stay intact during column movement. Only after those tests pass should you consider a module fault or programming-related action.
Need network wiring diagrams and module connector views?
Communication stop and network faults require module connector pinouts, bus wiring routes, and power/ground diagrams. A repair manual helps you trace the exact circuit path before replacing any ECU.
Possible Fixes
- Restore power feed integrity: Replace the failed fuse or relay only after you find and correct the underlying cause of the overload or poor connection.
- Clean and secure the ground point: Remove corrosion, tighten the ground fastener, and verify low voltage drop with the circuit loaded.
- Repair connector and terminal issues: Replace damaged terminals, restore pin tension, and correct moisture intrusion sources to prevent repeat dropouts.
- Repair harness damage: Fix chafed, pinched, or stretched wiring and re-route to prevent column movement from stressing the harness.
- Correct network circuit faults: Repair opens or shorts on the module’s communication lines and verify stable communication with ignition ON.
- Remove or correct aftermarket interference: Isolate added electronics from shared power or network circuits and confirm the module stays online.
- Replace and program the tilt & telescopic module: Do this only after you verify power, ground, and network circuits test good and the module still drops off the network.
Can I Still Drive With U1115?
You can usually drive a Lexus ES with U1115, because this code targets a body network function. U1115 means the network lost communication with the tilt and telescopic module. That module mainly controls steering column position and memory movement. The car will still start, steer, and brake normally in most cases. Expect the column to stop moving, stop saving memory positions, or refuse to auto-move on entry and exit. Treat it differently if the steering column locks in an unsafe position or moves unexpectedly. In that case, park the vehicle and diagnose it before further driving. Also avoid repeated key cycles and constant memory switch use, because those actions can trigger more network traffic and reveal an intermittent fault.
How Serious Is This Code?
U1115 ranges from an inconvenience to a real safety concern, depending on the symptom. When the column simply will not tilt or telescope, the risk stays low. You lose comfort features and memory functions. Risk increases if the column position changes on its own, binds, or fails to release from a previously stored position. Driver control can suffer if the wheel sits too close, too far, or blocks gauge visibility. This code does not confirm a failed module. Per SAE J2012 guidance, a U-code points to a suspected network trouble area. The message stays intentionally general, so you must identify the actual root cause. Focus on communication basics first: power, ground, connector integrity, and the relevant network line integrity for the tilt and telescopic module.
Common Misdiagnoses
Technicians often replace the tilt and telescopic module because the scan tool shows “lost communication.” That move wastes money when the real fault sits in power, ground, or the network path to the module. Another common miss involves chasing a mechanical column binding issue. A jammed column can exist, but it does not automatically create a communication DTC. People also ignore the freeze frame and network health snapshot, then they miss a low-voltage event that took multiple modules offline. Some shops back-probe the wrong connector. Lexus connectors and splice packs can look similar. Confirm the correct module connector by service information, then prove power and ground under load. Finally, many clear codes too early. They erase network history that helps isolate an intermittent open or high resistance.
Most Likely Fix
The most common confirmed repair direction for U1115 on a Lexus ES involves restoring a stable electrical supply and network connection to the tilt and telescopic module. Start with the basics you can prove: clean and tighten the module connector, correct terminal tension, and repair any harness damage near the column where movement flexes wiring. Next, verify low resistance grounds and solid power feeds under load, not just with an unloaded meter reading. If the scan tool cannot connect to the tilt and telescopic module after those checks, isolate the network segment and look for an open, short, or poor splice. Consider module replacement only after you prove correct powers, grounds, and network integrity at the module connector. Plan for initialization and configuration with Toyota Techstream if replacement becomes necessary.
Repair Costs
Network and communication fault repairs vary by root cause — wiring/connectors are often the source, but module-level repairs or replacements can be significantly more expensive.
| Repair Type | Estimated Cost |
|---|---|
| Basic DIY inspection (battery, fuses, connectors) | $0 – $50 |
| Professional diagnosis | $100 – $200 |
| Wiring / connector / ground repair | $80 – $400+ |
| Module replacement / programming | $300 – $1500+ |
Definition source: Lexus factory description · Autel MaxiSys Ultra & EV. Diagnostic guidance is based on factory-defined fault logic for this code.
Key Takeaways
- Meaning: U1115 on Lexus indicates lost communication with the tilt and telescopic module.
- Impact: The issue usually affects steering column movement and memory, not basic drivability.
- Root cause approach: Prove power, ground, and network integrity before suspecting a module.
- Intermittents: Column movement and harness flex often trigger opens or high resistance.
- Verification: Confirm the fix with multiple key cycles and conditions that reproduce the fault.
FAQ
Can my scan tool still talk to the tilt and telescopic module with U1115 set?
Sometimes yes, and that detail matters. If the scan tool communicates with the tilt/telescopic module, the fault often involves intermittent network dropouts, power glitches, or brief bus errors. If the scan tool cannot communicate, prioritize checking module power, ground, and the network lines at the module connector before replacing anything.
What quick checks should I do before removing trim or the steering column covers?
First, run a full vehicle DTC scan and note any low-voltage or network codes in other modules. Next, confirm the steering column moves at all and whether memory recall works. Then check fuses related to body electronics and seating/column memory. If symptoms change with key cycles, suspect an intermittent connection.
How do I confirm the repair is complete for an intermittent communication loss?
Do not rely on “no codes right now.” Recreate the conditions that triggered the fault, such as column movement, memory recall, and entry/exit operation. Then drive and perform several key cycles to stress the network. Enable criteria vary by Lexus platform, so use service information to confirm when the communication monitor runs.
If I replace the tilt and telescopic module, will it need programming or initialization?
Yes in many Lexus applications. Expect configuration, initialization, and sometimes calibration steps after module replacement. Toyota Techstream typically handles these functions. Plan to verify memory settings, column limits, and any related body functions after installation. Do not install a module and assume it will self-configure without scan tool work.
Could this be caused by a weak battery or charging issue?
Yes, and it is common. A weak battery, poor battery connections, or unstable charging voltage can drop a body module offline for a moment. That event can set U1115 even though the module works later. Check battery condition and cable integrity first, then review scan data for voltage-related history across multiple modules.
