Quick Answer
U0109 describes lost communication with fuel pump control module in the documented application. It does not prove a failed fuel pump, fuel-pump module or ECM. Save the original scan, confirm VIN scope and use the matched approved network scan, fuel-system wiring diagram and voltage-drop/communication tests before choosing a repair.
1What Does the U0109 Code Mean?
For the documented application, U0109 concerns lost communication with fuel pump control module. Confirm the vehicle, reporting module and full wording before using this guide. The full fault record determines the test branch.
U0109 identifies missing communication with a fuel-pump control module from the reporting controller. The cause can be module power, connector seating, a data-bus fault, gateway state, software or the module itself; it is not a pump replacement command. PIC4740F is a useful warning against reading the code literally. In its listed Cadillac automatic-transmission applications, the symptom group includes no crank, hard shifting and several warning telltales, and the first prescribed branch is the transmission connector X1. A loose terminal or chafed bracket can interrupt network communication and leave a fuel-pump module code in another controller. Only after the communication path is proven should fuel-pressure, pump command and controller output be interpreted. Do not transfer the X1 location, terminal test or model list to another VIN.
The fuel-pump label can distract from PIC4740F’s first branch at transmission connector X1; use that order only when the application matches.
GM PIC4740F covers specified Cadillac automatic-transmission vehicles with no-crank, warning and hard-shift symptoms. Its DTC table includes U0109 and directs inspection of transmission connector X1 terminals and harness condition. Confirm application before using this path.
The fuel-pump label can mislead diagnosis when the bulletin’s first branch is a transmission connector or network problem. Keep no-crank, fuel-pressure and communication evidence separate. No-crank or stalling has a higher safety priority than an ordinary stored code. Preserve the original state and avoid repeated starter operation if fuel, wiring or burning-odor concerns exist. The repair is complete only when the communication report, start/fuel-control symptom and required module verification agree.
Save the full module wording and suffix before clearing; they can change the test path.
Separate U0109 from adjacent fault families
| Code | General description | Key distinction |
|---|---|---|
| U0109 | Lost Communication with Fuel Pump Control Module | This guide’s documented application; retain the full suffix. |
| U0121 | Lost communication with ABS controller | A communication or network condition is different from a particular sensor or actuator fault. |
| P0562 | System voltage low | Check a documented shared-supply issue without assuming it caused every stored code. |
Record the complete U0109 description. The suffix, reporting module and companion faults can change the diagnostic path. Use the manufacturer's full wording and test procedure for the exact vehicle.
2U0109 Symptoms and Likely Causes
Record U0109 symptoms and fault status; symptoms alone cannot identify a failed part.
Check whether companion faults share a proven cause.
Record the exact warning, when it appeared and whether it changes with the monitored function. It is evidence to investigate, not proof of a failed part.
Compare the saved report with supported live data and operating conditions. A displayed value can be stale, invalid or unavailable without identifying the cause.
Preserve the service history and inspect the disturbed branch first, while keeping timing as a clue rather than proof.
Save every module’s codes and status. A related communication, voltage, warning or performance code can change the diagnostic order.
Practical cause-checking order
- Power, ground, connector or wake-state problem affecting the fuel-pump control module communication path: Unseated or damaged transmission connector X1 terminal
- Open, shorted, corroded, chafed or water-damaged wiring in the monitored path: Harness chafing, open/short, poor retention or water/corrosion
- A target, mechanical, tire or signal relationship problem where the monitor evaluates a physical input: Fuel-pump controller power, ground, wake or CAN loss
- Gateway, network, configuration, calibration or software condition that changes the reported result: Gateway/ECM/TCM state producing receiver-side U0109
- Internal sensor, controller or assembly fault only after the external branches pass: Fuel-pump controller or pump fault after communication and pressure tests
Did U0109 appear after recent fuel-pump, transmission, connector, harness, battery or module work? Recheck the documented connections, parts and setup steps affected by that work. Record battery and software history; a post-repair code does not prove the new part is defective.
3How Serious Is U0109, and Can You Drive?
Fuel/powertrain communication warning — assess starting and stalling. Follow the owner manual and current warnings. U0109 cannot establish a safe driving distance or prove that assistance is available. Stop safely if the engine stalls, will not crank or start, fuel delivery is unsafe, or the owner manual requires stopping; obtain qualified inspection or towing.
Record warning messages, operating conditions and service history. Do not induce wheel slip, emergency braking or a handling event on public roads. A red stop warning or abnormal control overrides any verification plan.
Stop and arrange a tow if the engine stalls, will not crank or start, fuel delivery is unsafe, or the owner manual requires stopping.
Do not work under an unsupported vehicle or bypass a safety interlock. Follow OEM shutdown, access and support instructions. A scan result is not a safety certificate.
4How to Diagnose U0109 in the Right Order
-
Identify the application and preserve evidence
Save the complete U0109 record, reporting module, status, network state, freeze frame, no-crank/stall symptoms and companion codes before clearing.
-
Inspect the relevant physical and electrical path
Confirm GM PIC4740F scope: listed Cadillac automatic-transmission models; its path includes no crank, warnings and hard shifting, not a universal fuel-pump diagnosis.
-
Confirm architecture and prerequisites
Follow the bulletin order: inspect transmission connector X1 terminals, disconnect and carefully tug each wire, then check the specified harness securing-bracket/chafing area.
-
Separate signal, network or system behavior
Prove fuel-pump controller feed/ground and network path with the VIN diagram after safe access; never jump the pump or controller directly to battery/ground.
-
Prove the repair path before parts
Establish whether ECM/TCM and fuel-pump controller communicate, then separate connector/network loss from fuel-pressure or pump-output evidence.
-
Verify the original condition after repair
Repair the demonstrated X1 terminal/harness, feed, network, software or fuel-control branch and verify crank/start, fuel control and module communication.
Specifications are vehicle-specific. Use the exact VIN specifications, approved test points and required operating state. No generic value or drive cycle can replace the applicable procedure. Manufacturer examples here do not establish specifications for other applications.
5U0109 Repairs and Cost Planning
A U0109 repair must address the demonstrated failure. Do not replace an assembly from the code alone.
Recheck installation and required setup after repair. U0109 does not measure fuel pressure; keep no-crank, network availability and pump-output evidence separate. No-crank or stalling has a higher safety priority than an ordinary stored code. Preserve the original state and avoid repeated starter operation if fuel, wiring or burning-odor concerns exist. The repair is complete only when the communication report, start/fuel-control symptom and required module verification agree.
Ask the shop to name the failed branch and the measurement supporting each proposed repair.
Authorize diagnosis before parts while the cause remains uncertain.
| Possible path | Quote basis |
|---|---|
| Repair the demonstrated power, ground, connector or network path serving the fuel-pump control module communication path | VIN-specific quote |
| Correct the proven mechanical, target, tire, mounting, centering or installation condition where applicable | VIN-specific quote |
| Restore configuration, software, calibration or required setup only through the VIN-specific procedure | VIN-specific quote |
| Replace the isolated sensor, controller or assembly only after external evidence and the OEM test support that path | VIN-specific quote |
These are alternative repair paths, not prices to add together. Request a VIN-specific quote separating diagnosis, parts, labor, fluids, taxes, required setup and verification. Ask which failed test supports the proposed repair and whether warranty coverage applies.
6Using iCarsoft CR Ultra P for U0109
On a supported vehicle, iCarsoft CR Ultra P can save accessible faults, available freeze frame, live data and diagnostic reports. Preserve the U0109 evidence before clearing.
Compare the saved and final module records. Scan data supports diagnosis but does not replace the OEM reference, physical measurement or safety-system functional check.

Preserve the fuel-pump control module communication path evidence
iCarsoft CR Ultra P
Review supported codes and relevant live data together. Confirm the exact VIN, controller access, PIDs and any requested active test with iCarsoft before purchase; generic product capabilities do not guarantee a U0109-specific function.
Check current CR Ultra P price and availabilityCheck CR Ultra P compatibility by VINThe official product page describes supported full-system diagnostics, available live data, freeze frame and diagnostic reports; exact controller coverage and active tests depend on the VIN and software. Confirm the requested function by VIN before purchase. Follow OEM prerequisites and stop for abnormal operation.
Know the measurement boundary. Scan data describes ECU-provided information; it does not directly prove the physical condition of the fuel-pump control module communication path. Where required, use approved network scan, fuel-system wiring diagram and voltage-drop/communication tests and compare reported values with the relevant measured evidence.
7Verify the U0109 Repair
After repair, verify installation, clearance and required setup. Save the final findings and clear only erasable records as instructed. Battery disconnection is not a repair.
Run the manufacturer's applicable verification conditions in a safe workshop or route. Compare the original operating state with current data for the fuel-pump control module communication path, and check current and pending faults in related modules. A clean start or idle period does not prove the repair; use the OEM functional check for the affected system.
Compare the original and final fault status. Record the functional-check result and whether the original event returned.
If U0109 returns, compare its suffix, status, failure order and operating conditions with the saved baseline before replacing another part. Revisit the failed branch and inspect anything disturbed. Confirm the prescribed affected-system functional verification separately from code clearing.
Verification follows the system involved. After saving the original evidence, use the OEM procedure to clear erasable records, complete any required calibration or functional check, and compare the final module status with the original warning and fault conditions.
8Related Fuel-Pump Control Module Communication Path Code Guides
Compare the related monitor families below. Shared symptoms or components do not make their repair procedures interchangeable.
9U0109 Frequently Asked Questions
Does U0109 prove the named component is bad?
No. U0109 describes lost communication with fuel pump control module, not a confirmed part. It also does not prove a failed fuel pump, fuel-pump module or ECM. Use the manufacturer’s test sequence to distinguish the relevant branch before replacing parts.
What should I check first for U0109?
Save every module's codes and freeze frame before clearing. Confirm the full definition, suffix and VIN architecture. Then inspect recent fuel-pump, transmission, connector, harness, battery or module work, connectors and shared supplies. Those facts determine whether the next test needs approved network scan, fuel-system wiring diagram and voltage-drop/communication tests or a manufacturer-specific functional procedure.
Can I drive with the U0109 code?
Fuel/powertrain communication warning — assess starting and stalling. Follow the owner manual and current warnings. U0109 cannot establish a safe driving distance or prove that assistance is available. Stop safely if the engine stalls, will not crank or start, fuel delivery is unsafe, or the owner manual requires stopping; obtain qualified inspection or towing.
Why did U0109 return after a part was replaced?
Connector repair and code clearing are incomplete until the original start/fuel-control symptom and module communication are verified.
What should a U0109 repair estimate include?
Ask for the failed-test evidence and a VIN-specific breakdown of diagnosis, parts, labor, taxes, required setup and verification. A code alone cannot establish the repair price.
Can CR Ultra P diagnose and clear U0109?
On a supported vehicle, CR Ultra P can organize available faults, freeze frame, live data and reports, and can clear erasable records after repair. Confirm exact ECU coverage. It cannot replace the OEM functional procedure or physical measurements for the fuel-pump control module communication path.
Technical and cost references
- GM PIC4740F — No Crank - Multiple Warning Telltales On - Trans Shifts Hard. NHTSA-hosted GM application bulletin; specified Cadillac automatic-transmission vehicles.
Product information: Official iCarsoft CR Ultra P page.
Editorial note: General diagnostic education, not a substitute for the owner's manual, current VIN-specific service information or professional inspection. Test limits, procedures, coverage and costs vary. Related articles provide context; apply only the specifications and repair procedures that match the vehicle. No universal failure rate, repair price or outcome is implied.