Jump to content

Fueling Up Issues

BLACK DEATH

Recommended Posts

BLACK DEATH Enthusiast

BLACK DEATH

Posted
Posted

I just got the truck and last time i filled up there were issues as it took forever to fuel up as it kept clicking the nozzle as if it were full. Well it finally let me fill up with out any issues. Well yesterday I go to fuel up again and i had to go very slow filling up and it took about 10 minutes to fill up. Its like the fuel going in is not releasing the air in the tank. I can hear air coming out from the filler tube and the fuel will start to fill to the top. Now I know it is empty as I put 20 gallons in it and drove 220 miles from last fill up so it was not full. Wheres this issue at? I did a search but came up empty. 04 2500 6.0 2wd ecsb

JoJoJim Enthusiast

JoJoJim

Posted
Posted

I have had the same thing happen but have found if I pull the nozzle out just a little and get it about the right place the problem goes away. I assume with nozzle in too far there is not enough air flow getting through.

Kodiak450 Senior Enthusiast

Kodiak450

Posted
Posted

Does this problem occur on a specific gas station pump? Or in general at every pump? I never had any issues like this in my 03, I have heard of pumps taking a long time to fill up because of problems with them (meaning not having to do anything with your truck).

BLACK DEATH Enthusiast

BLACK DEATH

Posted
  • Author
Posted

Its not the gas stations pumps output, guys. Its when your filling your truck and the nozzle will click as if the tank is full. It does it all the time. I have to barely squeeze the trigger to put fuel into the tank for me to fill up my tank. Its like it is not venting the air out from the tank. However much fuel gets put in is about how much air must be removed, correct? Its got to be a vent clogged somewhere or someother issue somewhere in this fuel tank.

steiny93 Enthusiast

steiny93

Posted
Posted

my 2500hd does it once in a while, wifes 06 denali does it all the time

 

under warranty we were back and forth with the denali, dealership printed out a tsb during the last visit

basically the gas pumps have sped up and the truck doesn't handle it well

 

we've just adjusted our fuel stops to ones in town that we know, getting annoying on a road trip as it can be crap shoot

Kodiak450 Senior Enthusiast

Kodiak450

Posted
Posted
I've found that pumps at Speedway are incredibly slow. But pumps at BP seem to be almost twice as fast.

 

BP does seem to have better, faster pumps. I fill up at Sunoco, BP, Hess, Exxon, Shell and Valero and exclusively boycott all Citgo's. Now that I think of it, I do remember recalling a couple of times at an Exxon the pump keep stopping as if the tank was full, but that was only at a certain station and it hasn't done that for awhile now at the same station. Out of all these stations, I really prefer Sunoco's fuel as it feels like my truck has more pep to it when running on Sunoco's 89 or higher.

plowking Enthusiast

plowking

Posted
Posted

I think the new pumps capture the fumes and send it back to the underground tank,Tank truck takes fumes back to the refinery. It could be this system is upsetting the truck at fillup. If you leave nozzle loose,the fumes will be released into atmosphere. I have same problems at some stations,fine at others. plowking

Archived

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

Go to topic listing

  • Latest Articles

  • Posts

    • 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.
    • davester
      Turning radius

      By davester · Posted

      Just don't turn the steering wheel as much?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...