Jump to content

Recommended Posts

Posted

the above was what I'm referring to, but since it's just a cosmetic upgrade I would bet the 16's will also have it.

 

 

And you know this for a fact ? You know exactly what was changed on the 2016s correct ? You are 100% confident that the ONLY changes were cosmetic.

Posted

Well i just got this back from GM customer service on here, unfortunately they were as useless as I feared.

 

"Again, we truly apologize for the ongoing displeasure. After extensive review with the dealership and our internal resources, it's been determined your truck is operating as designed at this time. We recognize this isn't the resolution you were seeking; however, please know we've exhausted all available resources on our end at this time. If you'd like to accept our accessories certificate offer, we're more than happy to get it processed for you. Feel free to reach out in the future if you have further questions."

I still need a third visit to lemon law this truck, but I don't want to. I'd lose about $3500 from the xpel, painted bumpers, line-x and i'm quite fond of her minus the vibes. I might try a driveshaft shop for shits and giggles to see if they can balance the drive shaft and effect it at all. I didn't beat cancer to have a new truck handle like this, and be treated like this grrrrrrr :rant:

Posted

Dropped mine off again today. See what comes of it. My service writer and the service manager are very patient with me and understand my frustration.

 

Another thing, since this is my second attempt, should I let them know I will pursue a buyback or lemon law it after the third and final failed attempt?

Posted

I thought the 6 speed was standard on the 2016 while the 8 speed was only available in the upper trim levels with the 5.3 engine?

Posted

I thought the 6 speed was standard on the 2016 while the 8 speed was only available in the upper trim levels with the 5.3 engine?

You know what, I think you're right
Posted

Well it will be interesting to see what comes of the 2016's once they start hitting the streets in the next few days. So lets see what facts come out instead of just speculating what changes might or might not have been made for this issue. It's not like they would come out and say they resolved the vibration issue for 2016 as that would be admitting that there is a vibration issue and they don't seem willing to admit that so far.

 

 

Jesse, let me know when you are around, i need to get that TPS sensor back.

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

    • Batteries don’t always show signs of a few years ago my vehicle started fine in the morning and took me to work. After work the battery was completely dead and I needed a jump. No, I didn’t leave anything on and the battery was only a couple months old. It was replaced under warranty. 
    • AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • If his battery was that bad I would think it would have been showing signs before this that were ignored. Stinks that it happened the way it did in rush hour traffic, but this seems like a pretty fringe scenario. I don't mind it that bad and never turn it off. The only slight annoyance for me is the slight delay between brake to gas, but I have gotten used to it and figure if it can save a little gas why not.
    • That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.
    • It was all part of the tiny bit of fuel savings it goes towards what was mandated by the government. Much like cylinder deactivation. That was relaxed by the recent administration. All that doesn’t help the individual buyer. But as a whole helps the manufacturer to try to reach the previous ridiculous past mileage per gallon mandate. So yes it was mandated and added cost to the vehicle. 
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...