U1109 – Lost communication with LIN steering wheel controls (Dodge)

U1109 means your Dodge Charger may lose steering wheel button functions, or they may work only sometimes. You can see radio, cruise, or menu controls drop out with no other warning. According to Dodge factory diagnostic data, this code indicates lost communication with the LIN steering wheel controls. In plain terms, one module stopped hearing the steering wheel switch messages it expects. The vehicle can still drive, but the missing inputs can affect convenience and, on some setups, cruise control operation. This is a manufacturer-specific Dodge network code, so the exact module roles and routing can vary by platform.

U1109 Quick Answer

U1109 sets when the vehicle stops receiving valid LIN network messages from the steering wheel control switch circuitry. Diagnose the LIN circuit, clockspring path, and module power/grounds before replacing any switch or module.

What Does U1109 Mean?

Official definition: “Lost communication with LIN steering wheel controls.” In practice, the module that supervises steering wheel switch inputs no longer sees button data on the LIN bus. That loss makes the vehicle ignore steering wheel button presses or behave intermittently.

What the module checks: the supervising controller monitors LIN traffic for expected activity and valid framing from the steering wheel control node. Why it matters for diagnosis: the DTC does not prove a bad switch. It only proves the network messages stopped. You must confirm whether the LIN wire path, clockspring connection, node power/ground, or the receiving module caused the dropout.

Theory of Operation

On many Dodge platforms, the steering wheel switch assembly communicates on a LIN bus. LIN uses a single communication line plus power and ground. The steering wheel buttons act like a node that reports button states to a supervising module, which then commands other functions.

U1109 sets when the supervising module stops seeing expected LIN communication. A wiring open, a short to power or ground, high resistance in the clockspring path, or a missing power/ground to the switch node can silence the bus. A module reset or poor connector fit can also interrupt messages long enough to trigger the code.

Symptoms

U1109 usually shows up as a steering wheel control complaint first, then a network fault on the scan tool.

• Scan tool shows U1109 stored, and the steering wheel control node may not report or may appear intermittently
• Steering wheel buttons stop working for radio, EVIC/menu, or hands-free features depending on build
• Cruise control buttons work intermittently or not at all on vehicles that route those inputs through the LIN controls
• Intermittent operation returns after a key cycle, then fails again while driving
• Other U-codes appear related to lost communication or bus faults in modules that rely on switch inputs
• Noises or feel from the steering column wiring after tilt adjustment, followed by control dropout
• Cluster behavior shows missing menu navigation inputs even though other vehicle functions operate normally

Common Causes

• Open circuit on the LIN communication wire: A break in the LIN line stops the steering wheel control node from exchanging messages, so the module logs a communication loss.
• Short to ground on the LIN circuit: A grounded LIN wire holds the bus low and blocks valid data transitions, which makes the network appear offline.
• Short to power on the LIN circuit: A powered LIN wire holds the bus high and prevents proper biasing and signaling, so the controller stops hearing the steering wheel controls.
• High resistance in clock spring or column harness path: Added resistance distorts the LIN waveform and causes intermittent dropouts, especially while turning the wheel.
• Poor power feed or ground to the steering wheel control node: Low supply voltage or a weak ground resets the node or forces it offline, which looks like lost communication.
• Corrosion or terminal tension issues at column or module connectors: Spread pins and oxidized terminals create intermittent opens that mimic a failed module.
• Aftermarket accessory wiring tied into steering wheel or column circuits: Added loads and poor splices can inject noise or create shorts that collapse LIN communication.
• Network gateway/module software or configuration mismatch: A module that expects a different LIN node ID or message set can flag U1109 even when wiring looks intact.

Diagnosis Steps

Tools you need include a scan tool that can run a full network scan and read body/chassis DTCs, a DVOM for voltage-drop testing, and basic back-probing tools. A two-channel oscilloscope helps on LIN faults, but you can still prove many issues with smart checks. Use Dodge service information to confirm connector locations and which module stores U1109.

1. Confirm U1109 and record scan data before clearing anything. Save freeze frame for ignition state, vehicle speed, system voltage, and any related network DTCs. Compare stored versus pending codes, since a pending U-code often points to an intermittent drop. Remember the difference between freeze frame and a scan-tool snapshot. Freeze frame captured conditions when U1109 set, while a snapshot can catch the dropout during a steering input test.
2. Run a complete network scan and note which modules respond. Verify the module that reports U1109 appears on the scan list, since a missing reporting module changes the direction. Check for companion codes for steering wheel switches, clockspring, or other “lost communication” U-codes. If multiple modules report LIN-related loss, treat it as a shared power, ground, or bus problem.
3. Check fuses and power distribution feeds for the steering column and body systems before probing any module connector. Use a test light or loaded voltage check, not continuity alone. Pay attention to fuses that feed the column electronics and any interior junction block circuits. A fuse that looks good can fail under load or have poor terminal contact.
4. Verify power and ground integrity under load at the module or node involved. Perform voltage-drop tests with the circuit operating. Target less than 0.1V drop on the ground path while the node is powered. Load the circuit by operating steering wheel controls and turning on related functions if available. A clean continuity check can still hide a high-resistance connection.
5. Inspect the steering column and wheel-related harness routing. Look for pinch points, chafing, and evidence of past repairs. Focus on the clock spring area and the column tilt or telescoping zones. Wiggle-test the harness while watching the scan tool for steering wheel control status changes and new pending codes.
6. Disconnect and inspect the relevant connectors for terminal fit and corrosion. Check for pushed-out pins, spread terminals, and moisture tracks. Confirm terminal tension with a proper test probe, not an oversized meter lead. Reseat connectors and retest, since poor contact often creates U1109 without any visible damage.
7. Test the LIN circuit for shorts and opens using a structured approach. With ignition OFF, check for a short to ground and a short to power on the LIN wire using resistance checks against ground and B+. Then switch ignition ON for bias checks, because LIN bias only exists when the circuit powers up. Do not use ignition-OFF voltage readings as a reference for a communication line.
8. Verify LIN activity with a scope if available. With ignition ON, look for a stable biased line with data pulses during switch operation. If the line stays stuck high or low, isolate the fault by unplugging the suspected LIN node and rechecking the bus at the master side. A restored waveform after unplugging a node points to a shorted node or a shorted section of harness past that connector.
9. Use scan tool data to confirm the steering wheel control node status where supported. Many Dodge platforms show switch state, LIN status, or “node present” indicators in body or steering-related modules. Compare switch response with the fault setting event. If U1109 sets only while turning the wheel, prioritize the clock spring and column wiring path.
10. After repairs, clear DTCs and perform a verification drive. Repeat the same conditions seen in freeze frame. Also capture a scan-tool snapshot during steering inputs to confirm stability during the exact moment the concern used to occur. Confirm U1109 stays out as a pending and a stored code across at least one complete drive cycle.

Professional tip: If U1109 returns immediately at key-on, treat it as a hard fault on the LIN circuit or node power and ground. If it returns only after steering input, suspect a mechanical-harness interaction like a clock spring or column harness strain. Prove that pattern with a snapshot and a controlled wiggle test before you condemn any module.

Possible Fixes

• Repair open or short in the LIN wire: Restore harness integrity, then verify LIN activity and that U1109 does not return.
• Clean and tighten affected connectors: Correct terminal tension and remove corrosion at column and module connectors, then recheck for intermittent dropouts.
• Restore proper power and ground to the steering wheel control node: Repair fuse feed issues, loose grounds, or high-resistance splices proven by voltage-drop testing.
• Repair or replace the clock spring only after circuit proof: Replace it only when tests show the LIN line or power path fails through the clock spring during wheel rotation.
• Remove or correct aftermarket wiring faults: Eliminate improper taps and splices that load or short the LIN circuit, then confirm stable communication.
• Perform module configuration or software update when verified: Address verified setup mismatches only after the network and wiring pass all checks.

Can I Still Drive With U1109?

You can usually drive a 2007 Dodge Charger with U1109 if the vehicle drives normally. This code points to lost communication on the LIN network for the steering wheel controls. Most of the time, the failure disables buttons like radio, menu, or cruise switches. It does not usually stall the engine. Treat it differently if other network codes stack up, the cluster acts erratic, or multiple modules drop offline. Those patterns suggest a broader power, ground, or network fault. In that case, limit driving and diagnose it now. If cruise functions act unpredictably, stop using cruise until you confirm stable switch data.

How Serious Is This Code?

U1109 ranges from nuisance to a real safety concern, depending on what the lost LIN communication takes down. If only the steering wheel audio and menu buttons quit, the impact stays low. If cruise control switches also ride on that LIN path, you lose cruise or get intermittent inputs. That becomes a safety issue in traffic. The code also matters more when it appears with other U-codes, low-voltage codes, or ignition-run power feed faults. Dodge network diagnostics follow SAE J2012 guidance. The message names a suspected area, not a failed part. Prove the network and power integrity before you replace anything.

Common Misdiagnoses

Technicians often replace the clock spring or steering wheel switch pack first because the symptoms match. That wastes money when the real fault sits in power, ground, or a LIN splice. Another common miss involves battery voltage and charging issues. Low system voltage can drop LIN communication and set U1109. Some techs also ignore the scan tool’s module list. If multiple modules show “not communicating,” focus on shared feeds and grounds first. Finally, many skip connector drag tests at the column. A loose terminal can pass a quick visual check and still open under steering tilt movement.

Most Likely Fix

The most frequently confirmed repair directions for Dodge U1109 involve restoring clean connections and stable power at the steering column network path. Start with the steering column and clock spring related connectors. Verify terminal tension, corrosion, and harness strain during tilt and telescoping. Next, confirm solid module power and ground under load, not just with a static voltage check. If those tests pass, then isolate the LIN circuit for opens, shorts, or high resistance between the steering wheel controls and the receiving module. Only after you prove the circuit fault should you consider component replacement.

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.

Last updated: March 31, 2026