Jump to content

Recommended Posts

Posted

Update on 2014 Crew Cab SLT Z71 4x4 5.3 engine 3.42 rear end. It seems to be improving slightly as I get a few miles on it. I took it to OHIO last week and ran one tank of E-85 plus ran in 4wd auto over 1/2 the time (forgot to switch it no dash indicator light you know) so I think that may have been what caused the lower mileage on the first 1000 miles or so. Here si what I have 25 50 and last 400

its from updates 13330 and then 14008

Posted

Once you get the update you lose 50% of mileage. I went 22 to 16 now am getting 14 and dealership to me today GM aware of the problem and doesn't have a fix. and that's not counting the other problems am having. 50,000.00 truck and they just want me to just seat and deal with it.

 

This is exactly what the hell happened to me, no joke when from 16-18 to 11-13 after my freaking updates. I'm going in Saturday for my rear window recall and I am going to raise hell.

Posted (edited)

This 6.2L is getting better gas mileage than my 2007 5.3!!!!! All this with less than 100 miles on the clock and 3.42 gears! By the time this thing gets broke in I'll have to leave my gas cap off 'cause it'll be MAKIN' GAS. :D:D (This ALL stop & go, in-town driving).

 

140129.jpg

Edited by LTZTom
Posted

its from updates 13330 and then 14008

what are these updates?? I picked my truck up on Jan 17 and they said they had already done the catching on fire reprogram. Is that one of these updates?

Posted

They did recall for back glass. Then upper center console fell because the clips where not holding. My right front glass makes noise they put doubleside tape on it because there is nothing holding the molding in place. Updates where for the fuel pump. GM is aware of problem and alot more other issues but cant fix them.

 

Why u think they haven't responded to my thread yet they already looked up my name in the files and found my truck and seen how many times its been into the dealership.

Posted

 

This is exactly what the hell happened to me, no joke when from 16-18 to 11-13 after my freaking updates. I'm going in Saturday for my rear window recall and I am going to raise hell.

 

Let me know what you find out. I too am getting pathetic mpg. About the same as you. Don't get me wrong, I'm not expecting anything phenomenal, but this is still below what these trucks should be getting I think. And if the recall fix makes it worse then I definitely want to know.

Posted

I have 1k on her Ipone onstar app says 19 average 12 miles each way mix, med lead foot. No interstate yet

Posted (edited)

2014 Silverado

I have had mine into dealership 4 times and yesterday they final told that GM is aware of problems and they have no fix and unless more customers complain they wont address it. And I got my truck in Oct and just 3500 miles. And drive the same route everyday. My camaro gets better gas mileage at 20 mpg.

Edited by Ton J
Posted (edited)

OK boys I have been taking a few short interstate trips around town and have been babying the truck with no jack rabbit takeoffs and no passing slow moving vehicles at WTO as usual. Here is what I have now on fuel mileage. Yes my rear bumper is in danger of being dented when driving like granny but I think this proves that if you drive easy you can achieve very good fuel mileage even on a Crew Cab Z71 4x4 with 5.3 and 3,42 rear axle BAMMMMMMMMMMMMMM [attachment=34119:IMAG0928.jpg and no it is not all down hill LOL just normal driving on interstate in moderate hilly middle TN not exceeding 70 mph most of the time and actually (against my nature) allowing the truck too slow a bit when going up hills. Give it a try and see what you come up with I never really paid it much attention before but putting the display in the 25 mile average setting and watching the effect of how I drive on the average fuel mileage it is quite a learning experience. I call it feathering the gas pedal LOL. I still cannot resist releasing the beast at least every 10 or 12 miles when some arsehole is riding the bumper but still I am getting what I think are impressive results.

Edited by Dnt
Posted

I drove from Little Rock to Texarkana which is good little drive with full tank gas today best I got driving the speed limit was 15.5 mpg. Way below spec still. I my 2012 was getting 18 mpg. I didnt buy it to baby it and its not doing what GM advertise at all.

Posted

I did have the recall done on my 4.3 and no difference in MPG here.

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