Jump to content

'03 Suburban Fuel Pump/tank ?s

CDR242

By CDR242
in Ask A GM Technician

Recommended Posts

CDR242 New Member

CDR242

Posted
Posted

This may seem redundant, but this is my first post and I didn't see another post with the exact same issues, so, here goes:

 

Vehicle:

2003 Suburban, 6.0L, 4x4, QuadraSteer, 3/4 Ton, 68K miles

 

Issues:

1. Ran out of gas with 1/8 of a tank left (per gauge). The idiot light didn't come on (the light worked the last time my son op-checked it - prior to this event). Verified that there was still about 5 gallons in the tank when it "ran out of gas."

2. Since the event, it takes a long time to get the last 5 gallons of gas in the truck when I fill up.

 

When I discussed the issue with the dealer, they advised that:

a. I needed a new fuel pump ($600 + labor) :thumbs:

b. The vehicle has two fuel pumps, one is for a 5 gallon reserve.

c. The reason that it takes so long to get the last 5 gallons in the tank is that the reserve pump isn't pumping the fuel back into the reserve portion of the tank - this didn't make any sense - how does it come out of the reserve portion of the tank if the pump is out? If it was gravity feed, then why did I run out of gas with 5 gallons left?

 

Questions (in addition to the issue above):

- Does the truck have two fuel tanks?

- Does it have two fuel pumps?

- Are the two pumps in one module?

- Is there a less expensive repair option?

- Did the pick up tube simply fall off and the dealer's assessment is incorrect?

- Why does it take so long to get the last five gallons of gas in?

 

Thanks!

L29er Senior Enthusiast

L29er

Posted
Posted

I had heard of a system like that on the GM 1ton cab and chassis trucks that worked like that, not too sure (or have never heard of the system on your model) but another thing that is common is for the breather at the top rear of the tank getting plugged up, it is easily removed and cleanable, it usually is the casue of most of the slow fueling problems i`ve dealt with... a time ago. BUT this is for slow filling at any tank level, so i may be just just be blowing wasted air..... :thumbs:

bill190 Enthusiast

bill190

Posted
Posted

I would crawl under the vehicle and look to see if there were two tanks or not. Then I would look in the factory service manual to see how it worked (best "owners manual" there is). Then go from there.

 

If you don't have a service manual set (4 books) and don't want to buy one, maybe you could look under the vehicle and see something obvious to check?

 

Like maybe there are two tanks and a connecting hose and one hose is pinched? Or things of that nature. Wouldn't need a service manual for that.

Archived

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

Go to topic listing

  • Latest Articles

  • Posts

    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      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
    • davester
      Replacement Radiator

      By davester · Posted

      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...