Jump to content

Recommended Posts

Posted

Hi Guys,

 

I just bought a new 2017 Silverado and noticed the digital fuel gauge not showing full...I thought I'd wait until I hit a certain mileage to see if the engine needed to calibrate itself, but this is not the case.

 

GM customer service said "it's normal and just a display..." But my wife has a 2013 Equinox and her digital image depletes as the fuel depletes (works as it should), so GM customer service has to be wrong here.

 

Any guidance would help greatly! ?

 

Attached is a photo I took immediately after fill up.

 

Cheers Gents

IMG_20170623_071701465.jpg

Posted (edited)

Pretty sure gm Is actually right here. That screen is meant to show mileage to empty not act as an actual fuel gauge.  I don’t recall the level changing on mine either but I have a 2015

Edited by paumat
Posted (edited)

My Aunt was a service manager for 20 years for GM and she just told me it could be the sensor or cluster itself.

 

Again...doesn't make sense if my wife's Equinox reads correctly.

Edited by jsanford01
Posted

It is just an image on the screen, does not function. Did not move on my 14 or the 16 I have now.

Posted (edited)

The gas pump thing on the DIC?  They are all at that same spot, on every single 4.2" color cluster on these trucks.  2014 and up, Silverado, Colorado, Sierra, Canyon, Tahoe, Suburban, Escalade, Yukon, and anything else that uses that cluster display.  Its NOT a representation of the fuel level in the truck. 

Edited by newdude
Posted

Not sure where in that image you expect it to show full. Maybe you can be a little more specific and draw a red circle around the area.

My wife has a 2013 Equinox 2LT, what digital image are you talking about? It's a simple monochrome display between the gauges that doesn't even display fuel level.

Posted

This doesn't make sense. Even under the image shows 2 circles...one as empty and one as full. But even this doesn't denote anything. If the image doesn't show fuel depletion, there is no point in having this.

 

I'll try and dissect further.

 

Thanks guys

Posted
This doesn't make sense. Even under the image shows 2 circles...one as empty and one as full. But even this doesn't denote anything. If the image doesn't show fuel depletion, there is no point in having this.
 
I'll try and dissect further.
 
Thanks guys



It’s just a graphic image. Not functional. Silly sure, but broken no


Sent from my iPhone using Tapatalk
  • Like 1
Posted

The blue color in the gas pump is not meant to be a dynamic guage (think battery icon on your phone).

It is simply a static picture of a gas pump that they chose to color that way. Its exactly the same in my 2015.

Posted

Ok. Thanks guys. I can rest assured now haha

 

I was thinking it was a fuse or sensor.

 

????

 

 

Posted

I just filled my tank up and my range says 220 miles ☹️.


Sent from my iPhone using Tapatalk

  • 3 years later...
Posted
34 minutes ago, Jessiejames said:

My fuel range did not go over 274 with a completely full tank in a 2017 suburban. Any help on this issue?

Welcome to the site.

 

More information may help, what was your average MPG on the last tank? If very low the truck uses that to calculate and estimate for the new tank of gas. Higher average on the last tank will yield more miles on the next.

  • Like 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Latest Articles

  • Posts

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • 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
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...