Jump to content

Recommended Posts

Posted

Add me to the list of shakers. Live in rural Iowa but just took it to Califonria, as soon as I hit the interstate above 75 the vibration started. I still had 3500 miles to go! The worst was at 82. Took it to the dealer today. They told me they had to wait to hear from GM??

Posted

Update,

 

Received my truck back from the dealership last week Friday with half the problem resolved. Dealership put almost 300 miles of testing within 20+ days of them working on it. GM engineer found the exhaust manifold was causing the vibration issue. They replaced the parts and now I am vibration free as long as I am driving in 6 cylinders. The moment it goes into 4 cylinders the vibration is back at the specific speeds of complaints. Dealership says that GM knows this is an issue and is working on a resolution but he does not have a time frame for the fix. I asked if they can disable the feature and he said that it’s a possible solution but cannot disable it until GM makes it official. I will update the post when I get a resolution for the 4 cylinder issue or if the vibration comes back in 6 cylinder mode.

  • Like 1
Posted

I have vibration but its pretty intense at 70mph.. to the point of where stuff rattles in my cupholders.. i think my driveshaft isnt balanced or something odd... gonna take it to the dealer soon.

Posted

Well, I had mentioned that I was done dealing with all of GM's BullSh*t, particularly after they told me that it was "normal operation" and they they wouldn't do anything. The lawfirm I had contacted called me back today, and they ARE interested in taking the class action case, they have already gotten some "experts" to look into ALL of the issues, I gave them a little more information, and they said that either one of their "upper level partners" or the "experts" will be contacting me in the next few weeks regarding the overall case.



Here we go, the ball is finally rolling


(if anyone wants to/ is willing to speak to them, please pm me your Name, Email, and Phone)


  • Like 1
Posted

Well just picked the truck up after 2 more weeks in the shop. They replaced the torque converter and said yep it's all fixed got 20mins up the road and the same s*** started again at this point I am done I am taking it back tomm and requesting a buy back I guess we shall see how it goes. Only 1400 miles on it bought it June 6th and has been in the shop since June 26 3 times for a total of over 30 days.

Posted

Well just picked the truck up after 2 more weeks in the shop. They replaced the torque converter and said yep it's all fixed got 20mins up the road and the same s*** started again at this point I am done I am taking it back tomm and requesting a buy back I guess we shall see how it goes. Only 1400 miles on it bought it June 6th and has been in the shop since June 26 3 times for a total of over 30 days.

ouch man

Posted

I finally found another dealership that is willing to really look at the truck. I have a GMC but taking it to a Chevy dealer that's 50 miles away. The Service Advisor was very quick to acknowledge that there are issues with the 2014s. I think I'm going to use this thread and make a checklist of all the things to look at. LOL. I drop off the truck tomorrow night.

 

I'm kind of curious to see how many other people following this thread have the 5.3 8cyl and are experiencing the same vibration issue.

 

 

Sent from my iPad using Tapatalk

Posted

I finally found another dealership that is willing to really look at the truck. I have a GMC but taking it to a Chevy dealer that's 50 miles away. The Service Advisor was very quick to acknowledge that there are issues with the 2014s. I think I'm going to use this thread and make a checklist of all the things to look at. LOL. I drop off the truck tomorrow night.

 

I'm kind of curious to see how many other people following this thread have the 5.3 8cyl and are experiencing the same vibration issue.

 

 

Sent from my iPad using Tapatalk

there is another thread for the same topic over 360 pages

  • Like 1
Posted

Yeah, I've been reading through that thread as well. I knew I should've gotten the 8cyl. Lol

 

 

Sent from my iPad using Tapatalk

welcome to my world

  • Like 1
Posted

I have a 5.3, but currently have a v6 for a loaner. The AFM vibe that comes from the v6 is entirely different than the vibe I get on my 5.3. The AFM vibe on the v6 is in the steering wheel and column. The vibe on my 5.3 appears to be coming from the rear of the truck and causing the center console to shake at 40mph and 75-80mph. The steering wheel on the 5.3 is solid in and out of AFM (for me anyway). The only thing I can feel is a slight surge when going into and out of AFM on the 5.3.

Posted

I have a 5.3, but currently have a v6 for a loaner. The AFM vibe that comes from the v6 is entirely different than the vibe I get on my 5.3. The AFM vibe on the v6 is in the steering wheel and column. The vibe on my 5.3 appears to be coming from the rear of the truck and causing the center console to shake at 40mph and 75-80mph. The steering wheel on the 5.3 is solid in and out of AFM (for me anyway). The only thing I can feel is a slight surge when going into and out of AFM on the 5.3

I have the same vibe but from 70-80. Have you noticed the vibe to be much worse during colder weather? Where I'm at the temp swings 35 degrees from when I go to work to when I come home, vibration is less severe in the afternoon .

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

    • Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...