Jump to content

1996 c1500 fuel guage

griepp06
 Share

Recommended Posts

griepp06 Enthusiast

griepp06

Posted
Posted

So I just bought a 1996 5.7 fuel injection c1500 that needs some work as the check engine light is on but that I will take care of thats my next project. My main concern is that when the tank is empty it says 1/2 full on the guage and when full it says way past fullon the gauge. Please advise weather to pull the bed off and replace something inside the tank or if its the gauge or something else completely.

thx1138v2 Enthusiast

thx1138v2

Posted
Posted

Here's something to be aware of if that truck had 2 different size gas tanks: I put a new pump/sending unit in my '94 and the auto parts guy asked me if I wanted the HV model or the non-HV model. I asked him what the difference was and he didn't know. So I got the "HV" model and it doesn't read correctly. It's not as bad as what you described but it's still annoying. I later found out that truck had 2 possible fuel tanks and the HV designated the (H)igh (V)olume tank - the larger of the two.

griepp06 Enthusiast

griepp06

Posted
  • Author
Posted

okay so i think i have the smaller of the two options but am unsure. im going to take the bed off so i can see the top of the tank and get access to the sending unit and replace it and makse sure that i get the reight one depending on the size tank. what were the two sizes in gallons?

thx1138v2 Enthusiast

thx1138v2

Posted
Posted

Shortbed trucks were equipped with 25 gallon tanks; longbed trucks were equipped with either a 25 gallon or 34 gallon tank. Mine was a 25 gallon tank because I have a short bed. The better way to tell is how much it holds when the gauge is near empty.

griepp06 Enthusiast

griepp06

Posted
  • Author
Posted

Well I have a short bed so I guess that means I have the smaller tank and a non HV 

thx1138v2 Enthusiast

thx1138v2

Posted
Posted

Now the question is which version of the sending unit do you have? It would make sense that it is the HV sending unit. It may have been replaced before you got the truck so the only way to tell is to pull the bed off and then remove the pump/sending unit.

LDM Enthusiast

LDM

Posted
Posted

Don't just assume it is the sending unit in the tank.  The gauges on these trucks often stop working or get outside of spec.  My brother has a 97 K1500 and we had to replace the tank and fuel pump due to failure, which still didn't fix the issue withe gas gauge randomly jumping all over the place.  Turned out to be a bad air core motor in the gauge, which was fixed after I swapped out the entire cluster due to the RPM motor and speedo failing.  You used to be able to get the motors on ebay for a decent price and fix the cluster but the last time I looked they were pretty expensive.  You may want to see if you can find a replacement cluster in a junk yard first, they are much easier to replace than the fuel tank/pump.

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