Jump to content

Gas Gauge Whacky - CEL On/Off

Gooseslayer717

Recommended Posts

Gooseslayer717 Enthusiast

Gooseslayer717

Posted
Posted

i have a 2011 sierra 1500 z71 ext cab.

I had once noticed my fuel gauge go empty then was acting odd and ran a cleaner with next fill up and the problem went away.

Now about 5-6 months later it happened again. The gauge goes from normal to empty. then will slowly come back up, or will jump back up, then can read correctly, then falls back to empty.

The gauge reading empty will put CEL on. The gauge will work again while CEL is on, then it will go down, slowly come up etc...

Each time i have filled up since it started recently, it was either at empty or had been going back and fourth. first fill up of 10 gallons and it seemed to be working again normally. CEL light went off, and gauge read fine.

2 days later its acting up. CEL comes back on.

I fill up again, and all is normal. Now again few days later and CEL comes out. gauge works sometimes and will move extremely slow back to the correct spot.

I havent gotten under to do diagnostics but i wasnt sure if anyone knew if it was a problem with a float device, or ground wire, sensor?
I have researched and i would imagine ground wire but seems sensors are often bad too.

Thanks for any input 

Gooseslayer717 Enthusiast

Gooseslayer717

Posted
  • Author
Posted

That's what i am thinking.

I also noticed that when its the tank is full but its showing empty. The Gas tank light will be on (showing empty) and the flick off while still showing empty.

Does the float cause CEL light to engage? I read about Sensors and grounds being the main cause.

Did you fix the float? Was it hard?

Gooseslayer717 Enthusiast

Gooseslayer717

Posted
  • Author
Posted
19 hours ago, riverbanks said:

Sounds like you're connection at tank, did you get the code read?

P0463 Fuel level Sensor.

Its odd because sometimes it jumps up to normal level, then falls back down.

Itll slowly go up over the drive then just drop.

It will give me the Low Fuel level warning, then clear itself without needing me to hit the DIC.

It will clear the CEL itself after driving after refilling.

 

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