Jump to content

Rear fuel pump not working on my '02?


Recommended Posts

Posted

So the gas gauge on my '02 Yukon XL 2500 6.0L has been acting a bit funky lately, once I get below ~9/16 of a tank the needle starts to drop like a rock. The last time I went below 1/2 tank it went from ~7/16 of a tank to ~1/4 of a tank in <15 miles, when I hit the gas station it only took on 22 gallons of fuel instead of the expected 30 gallons.

 

I looked all over the left rear frame rail for the rear pump relay and connection to see if I could test the resistance of the pump or jumper it to see if I could get it to cycle, but I couldn't find the connection or the relay. Am I looking in the right spot, or does anyone have a picture of what it should look like?

 

Both my work's scan tool and the mechanic's only read the gas gauge's reading from the dash, they can't seem to pull individual tank values, is that only available on later vehicles?

 

Is there any other way to test it other than bring along a bunch of gas cans and drive it until it stalls?

Posted

So the gas gauge on my '02 Yukon XL 2500 6.0L has been acting a bit funky lately, once I get below ~9/16 of a tank the needle starts to drop like a rock. The last time I went below 1/2 tank it went from ~7/16 of a tank to ~1/4 of a tank in <15 miles, when I hit the gas station it only took on 22 gallons of fuel instead of the expected 30 gallons.

 

I looked all over the left rear frame rail for the rear pump relay and connection to see if I could test the resistance of the pump or jumper it to see if I could get it to cycle, but I couldn't find the connection or the relay. Am I looking in the right spot, or does anyone have a picture of what it should look like?

 

Both my work's scan tool and the mechanic's only read the gas gauge's reading from the dash, they can't seem to pull individual tank values, is that only available on later vehicles?

 

Is there any other way to test it other than bring along a bunch of gas cans and drive it until it stalls?

 

I think the only connection is on top of tank ( fuel pump/filter in tank ) old age ???????

Posted

My understanding of the wiring is the relay under the hood powers the front pump and provides power to a second relay (located towards the rear of the vehicle) controlled by the computer. The rear pump should have a relay somewhere since the computer can't provide enough power to make the pump run.

Posted

Simplest thing first. Get a new stepper motor in the dash, They are cheap and much easier than fooling with the rest. Fill your tank up, get new motor installed ( or do it yourself if you can solder and de solder) and then sync it to full with key on, and give it a try. this is a common problem with the gauge motors

Posted

If the stepper was bad, wouldn't I see a difference between the scan tool's output and the gauge? The gauge appeared to move to the proper positions when I commanded them (0, 100, etc).

Posted

If the stepper was bad, wouldn't I see a difference between the scan tool's output and the gauge? The gauge appeared to move to the proper positions when I commanded them (0, 100, etc).

If your motor has never been updated, its the cheapest and easiest thing to try first . When they mess up, they dont always mess up

Archived

This topic is now archived and is closed to further replies.

  • Latest Articles

  • Posts

    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • 2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...