Jump to content

Recommended Posts

Posted
2 hours ago, Chad2815 said:

I would try the easy stuff first. Change fluid, and flash the tranny. Could also be numerous other things like leaf springs, or rear end play. If you have to change the torque converter then your tranny will be out or pulled back from the engine. Then you might be able to check crankshaft play. The easiest way to check this is with the engine on a stand. I hope it’s not your crank. Good luck!

Posted

Crazy stuff....I have had the flush numerous times for the vibrations but the downshift from third to second is new. I just wanted to post so others knew, that was news to me. I am still under warranty but I am sorta exhausted with the process. Thanks for the input though.

Posted (edited)

i just got tuned by black bear, and all down shift clunking is gone. what a difference on shifting, engine, etc. totally new truck. 

what my point is, tuning can fix the clunks. the way GM has programmed these trucks is asinine. too many up shifts to quick, constant lugging, wanting to increase fuel economy to gov regulations. i dont think its setup correctly/synchronized correctly with tranny and engine setpoints. 

but hey, im not an engineer. 

 

30k miles. my warranty is up in 2 months anyway. 

Edited by Jgreen2193
Posted
57 minutes ago, Jgreen2193 said:

i just got tuned by black bear, and all down shift clunking is gone. what a difference on shifting, engine, etc. totally new truck. 

what my point is, tuning can fix the clunks. the way GM has programmed these trucks is asinine. too many up shifts to quick, constant lugging, wanting to increase fuel economy to gov regulations. i dont think its setup correctly/synchronized correctly with tranny and engine setpoints. 

but hey, im not an engineer. 

 

30k miles. my warranty is up in 2 months anyway. 

You have the 8 speed? Last I heard nobody could tune an eight speed, well I know you can send off your ECM and have it swapped but I’m talking as is factory tuned.

Posted (edited)
23 minutes ago, Chad2815 said:

You have the 8 speed? Last I heard nobody could tune an eight speed, well I know you can send off your ECM and have it swapped but I’m talking as is factory tuned.

6 speed

didnt know they had 8 speeds in 2014's...you might want to update your signature, and post more clearly what tranny your talking about in the original post, you  may have some better results ?

i doubt you have a crank issue...that would be the final step, but its most likely the gm parameters in how the tranny shifts, as i said above, i have 0 clunks now with my 6 speed after my tune. its butter. 

hasnt the 8 speeds always shifted like ****** and had more problems than the 6's?

tuning might be your only way out, or going to a different brand truck. 

 

goodluck

Edited by Jgreen2193
Posted
On 8/30/2020 at 12:42 PM, Chad2815 said:

You have the 8 speed? Last I heard nobody could tune an eight speed, well I know you can send off your ECM and have it swapped but I’m talking as is factory tuned.

Do you have a 2017 Denali 8 speed? It can be tuned, just costs a bit more than the 15-16's. But yeah factory GM tuning on the 8L90 is garbage. There are many contributing factors to the clunkiness (in my opinion and experience)

 

1. The trans tune sucks all around. Primarily the TCC lockup schedule. 

2. Driver demand settings make transitions from light throttle to zero throttle abrupt. 

3. The 6.2 has zero cam ****** until .14g cylinder airmass. 

 

These three areas are big contributors to the poor driveability of the 6.2/8 speed. 

Posted

Yeah I have the 6.2/ 8 speed. Mine clunks but not every time, I was more posting that article so everyone knew not just complaining about mine. I would like to find a place that could tune it but its great WOT and 90 percent of the time, just when slowing down the clunk has started for mine. I have 44,000 miles, also makes a

loud clunk when I go from Drive to Reverse but again, thats just life with these trucks. Just thought I would share what I came across while doing research.

Posted (edited)

I have a 2017 Sierra Denali 6.2L / 8-sp. # yrs and about 35,000 miles (3 yrs old , original owner) and I never experience a clunk going from  drive to reverse.   I can't ever recall any down shift clunks at all ever.  Sometimes when driving real slow after cold start it will shift hard from 1st to 2nd but that typically occurs at 5mpg and only when I barely have any pressure on the gas pedal, just crawling along.  Live by the lake shore so I often just take in the scenery leaving home. 

 

PS - I had the ATF changed over to AMSOIL 2.5 yrs ago at about 10,000 miles more or less. .

Edited by elcamino

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

    • 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?
    • I went to the county a few years back to dispute my property taxes. To do that I hired an appraiser and a lawyer. The County Assessor wished to argue that the homes in my neighborhood the appraiser used were all 'distressed properties" and not representative of the "Market Average".    My response was," Of the 50 homes in our subdivision 43 of them were "distressed properties" under bank foreclosure and as such "Distressed IS the market". Lawyer about choked on his coffee and handed the Assessor the 'receipts'.    I won that case on the evidence provided by the Lawyer and the Appraiser.    We have the same thing going on here. My statements were based on the GOVERNMENTS NATIONAL DATA and yours on local markets in areas of your interest. They are both correct....   Thing is, this divergence was based on NATIONAL and not on LOCAL. I think you even understand that. But like you said, we are both stubborn and hardheaded.    I do not see any advantage to disengagement.  But that said we can step back to compose ourselves. 
    • Trust me I appreciate the comments and concerns. It's what I was looking for to help me evaluate the situation and what I want to do. I have decided to move forward with the BORA hubcentric slip on 3/8" (.375") with the extended lugs nuts. Fedex says they should be here Monday :). Meanwhile, the dealer got the remote start and Patriot spray in bed liner done over the last couple of days. Also, I installed an inline stop/start eliminator today. Starts back up in what whatever mode you shut it off in, so you don't have to hit the button every time you fire up.
    • $2.20 E-85 down from $2.59 Around $3.80 for regular and about $5 on average for Premium.  Propane $3.99 a gallon. 
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...