Jump to content

Recommended Posts

Posted

Had my truck in yesterday and they said it is in the transmission and to bring it back next week. so a new transmission at 3k mikes valve body work at 25k and now a shutter that feels like the wheel is lose at 38k maybe they will just put another new transmission in it

Posted

Yeah but it's still a boring Crapota.

 

I'll take my good ol' boring, bulletproof, and oh so reliable 07' Crapota 4Runner any day of the week over that rolling POS 97' GMC Sierra I got rid of after owning it for 16 miserable years

  • Like 1
Posted (edited)

Yep, my girls 2013 Runner has been flawless after 60k miles.

 

My 2016 Sierra has numerous problems, some that can't be resolved yet...

Edited by wuznme
Posted

I think my build date is march of 2016. I have about 13k and change on the odometer. Bought the vehilcle as New with about 6,000 miles on it. Per the dealership the U-Joints were binding up in the same place on each rotation. I've had vibration issues since day one of purchase.

I think my build date is march of 2016. I have about 13k and change on the odometer. Bought the vehilcle as New with about 6,000 miles on it. Per the dealership the U-Joints were binding up in the same place on each rotation. I've had vibration issues since day one of purchase.

 

6.2 or 5.3?

Posted

After reading about this topic A LOT, I feel bad for those having to deal with this, but at the same time, I'm crossing my fingers that GM has rectified the issue for '17. I only have 4000 kms on my Sierra, but I have had zero vibration or shake issues.

  • Like 1
Posted

Going to pick up Sierra. Dealer replaced 3 tires. I'm skeptical that this fixed it

 

Wouldn't get your hopes up. Dealer has replaced 11 of my tires. No change in vibration.

Posted

Well picked it up. It's better but I don't think it's 100% gone. Maybe 50% better. I'm going to give it some time and see...?

Posted

Wouldn't get your hopes up. Dealer has replaced 11 of my tires. No change in vibration.

They didn't try anything else? Seems like they are just throwing tires at it without trying to diagnose issue

  • Like 1
Posted (edited)

Page 200!! And still no word from GM , not even a "we are aware and working to remedy". Every day I repete to my self, "my truck doesn't vibrate ,my truck doesn't vibrate, my truck doesn't vibrate". I rarely take it on the interstate. Who's going to be the first to start a class action lawsuit? :rant:

 

 

 

Once vibrator always a vibrator. And now we're on page 708?

Edited by scott19677
  • Like 1
Posted

I read about the new steering bushings in another thread.

 

Sent from my OnePlus 2 using Tapatalk

Posted

They didn't try anything else? Seems like they are just throwing tires at it without trying to diagnose issue

GM made me remove my leveling kit before they would send an engineer. I removed it and put in the shop. Engineer did the same shit and it's "in spec". No further claims to be warrantied.

Posted

GM made me remove my leveling kit before they would send an engineer. I removed it and put in the shop. Engineer did the same shit and it's "in spec". No further claims to be warrantied.

NO. WAY. I'm SOOOOO SURPRISED. lol, sorry had to

Posted

GM made me remove my leveling kit before they would send an engineer. I removed it and put in the shop. Engineer did the same shit and it's "in spec". No further claims to be warrantied.

Having a leveling kit doesn't get them off the hook. Blaming tires is an excuse. "In spec" is also an excuse. Aftermarket stuff doesn't allow them to skirt the warranty. They use this wording to turn you away. It's not like you turned the sheet metal inside out.

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