Jump to content

Recommended Posts

Posted (edited)

2014 LT Z71 with 4.3.

 

When the cylinder deactivation kicks in and the truck switches into V4 mode, it has a very noticeable vibration or shake.  Not unlike driving on a washboard road.  This is not a wheel balance / driveline issue, it's definitely when the cylinders are deactivated and it's pretty much like a light switch.  Anytime, any speed, the truck is in V4 it's shaking.  ENgine is totally smooth in V6 mode with all cylinders firing.

 

I know I got the crap motor, but did Chevy really do this poor of a job balancing in the V6 (and therefore this vibration is normal) or is something wrong?

 

I did search pretty extensively and can't find ANY reference to this, which I thought was really odd.  If it was normal I'm sure I would have read a ton about it, or at least found one or two people whose engines grenaded right after this.

 

DIsclaimer: I "inherited" the truck from my dad, who swears it never had any vibration, but I felt it driving the truck home from his house for the first time.  My dad also doesn't know how to put gas in his own car, and is the sort of person who goes into a dealership and says, "I would like one car, please."

 

Thanks,

Darel

Edited by Darel Matthews
add
Posted (edited)

 

I own a 2015 4.3 V6. Has 144,003 miles on it. Flawless miles. AFM works seamlessly. Gets great gas mileage. In point of fact everything works perfectly. Still on original brakes. First set of tires lasted 125,000 miles... only two sets of wipers. A $5 pinion seal and a $15 starter shield. That's my entire seven years of abnormal maintenance.

 

Unless a deer or a distracted driver takes her out.....solid as a rock and lov'n it. 

 

IMG_0253.JPG.249353198ed5bf0315ed3b52e7b758c4.JPG

 

 

 

 

Edited by Grumpy Bear
Posted

Uh-oh.  Any ideas where I should start to look for the source of the vibration?  The cylinder deactivation on my '07 is like yours, invisible and seamless, but that's the 5.3 and I thought maybe the inherent balance was different.  Thanks.

Posted

OK, oddly enough I found a few references to guys with similar issues.  To provide some more info if anyone's experienced this, the shaking occurs the entire time the truck is running in V4 mode, NOT as it transitions in and out of it (as most of the other guys seem to have indicated).  The entire time the truck is in V4 mode, it feels like it's driving on a washboard road at all speeds and under all driving conditions.  V6 ins perfect.

 

Also seeing a couple of references to GM firing the parts cannon at this.  So it's not unknown, but it also doesn't sound like in seven years there's a confirmed fix?  

 

Also please don't suggest one of those chips that eliminates the V4 mode.  That's a bandaid, not a fix.  You're just hiding the problem then.  Also I love the gas mileage this truck gets, I'm comfortably getting 21 mpg and loving it.  

Posted

You might try this question in the "Ask the GM Technician" in the "Technical and Advanced" forum.

You could also give a shout out to "newdude'. A Tech who has seen nearly everything....

If this happens to enough units it will have generated a TSB. 

Parts canons get fired when the tech has not read or does not know about the TSB or if one has not yet been generated. 

  • 4 years later...
Posted

I have 2018 Silverado 4.3V6. When transmission goes from V6 to V4 I get excessive vibration. On cold start I get chatter from engine then puff of black smoke out tailpipe. Also when I’m in V4 mode truck is vibrating when I go back in V6 it stops. Dealer told me normal operation. Bull crap. 

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

    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...