Jump to content

Recommended Posts

Posted

Im surprised about the MPG posted, i expected better than that! certainly not enough to justify switching my 11 denali for a 14 denali 5,3! my 6.2 average 18 mpg gallon on highway, i thought it sucks but really not that bad after all!

Posted

Oh wait you have the jacked up white Silverado with 4.56 gears. That makes more sense now lol

 

Sent from my SCH-I535 using Tapatalk 2

 

 

Posted

Seen a lot of talk on here about MPG going south after the recall update, i noticed the same thing but after thinking about this some more maybe its just more of the cold weather bad MPG. I got my recall done early January about the same time as the temps have really falling off in most of the country. I drive the same drive everyday one way to work 15 miles. In the summer months I was getting 20 MPG all the time, once the colder fall months came around I was is getting about 18 MPG, now since it has been colder than hell (beginning of January) I'm only getting 16 MPG. Also with the temp never going above 20 around here for the last month, on my 15 mile trip the water temp won't hit the 210' mark until I am almost to the end of the trip. I really think the crappy MPG is just due to the extreme cold.

Posted

Im surprised about the MPG posted, i expected better than that! certainly not enough to justify switching my 11 denali for a 14 denali 5,3! my 6.2 average 18 mpg gallon on highway, i thought it sucks but really not that bad after all!

Take one for a test run and make the comparison the same way you check your current ride.

Posted

Take one for a test run and make the comparison the same way you check your current ride.

i did with a 14 slt 5,3, i saw 1-2MPG better. But way down on power!! The new Denali didnt got me all excited anyway. I think ill stick with my 10 denali for another year and then ill take another look.

Posted (edited)

Can't you request that they reset the system to the previous settings, i.e. undo the update (at least temporarily) and then see if the mileage improves? At least you would eliminate this as the root cuase if something else is causing it.

 

I have hard time understanding how can some small software update severely reduce the fuel economy unless someone really messed with the fuel mapping and ignition timing advance.

Edited by pm26
Posted

They had a recall on fuel pump calibration that why they had the first update 13330. Then the 14008 update fix remote start problem which caused the exhaust to over heat and the they cancelled the 13330 updated and replaced it with a new updated. I Asked my GM dealer about and they just go with what GM Tech tells them. I told them its my truck I would like a better understanding of these updates seeing that GM really not explaining them to much.

Posted

Can't you request that they reset the system to the previous settings, i.e. undo the update (at least temporarily) and then see if the mileage improves? At least you would eliminate this as the root cuase if something else is causing it.

 

I have hard time understanding how can some small software update severely reduce the fuel economy unless someone really messed with the fuel mapping and ignition timing advance.

Safety Hazard because of the fire from over heating. so they won't roll back the updates

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.

What dealership?

Posted

Oh wait you have the jacked up white Silverado with 4.56 gears. That makes more sense now lol Sent from my SCH-I535 using Tapatalk 2

 

 

Correct Sent from my iPhone using Tapatalk

I don't understand how you think you would be getting great fuel milelage with those mods you have?

Posted
They had a recall on fuel pump calibration that why they had the first update 13330. Then the 14008 update fix remote start problem which caused the exhaust to over heat and the they cancelled the 13330 updated and replaced it with a new updated. I Asked my GM dealer about and they just go with what GM Tech tells them. I told them its my truck I would like a better understanding of these updates seeing that GM really not explaining them to much.

 

The 14008 recall incorporated the 13330 recall into it. It's just software updates. It's kind of like when windows does one big service pack instead of installing a bunch of little software patches they do one big one...

 

Sent from my SCH-I535 using Tapatalk 2

 

 

Posted (edited)

I get the vapor thing, but it still doesn't explain why my 2012 Silverado got better gas mileage and I getting 18-19 in it summer and winter. And it switched from V8 to 4.

Sound everybody just wants to just to it GM word on it.

post-127624-0-04813500-1391412833_thumb.jpeg

post-127624-0-04813500-1391412833_thumb.jpeg

post-127624-0-04813500-1391412833_thumb.jpeg

post-127624-0-04813500-1391412833_thumb.jpeg

Edited by Ton J

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined
  • Who's Online   5 Members, 0 Anonymous, 1,931 Guests (See full list)


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