Jump to content

Recommended Posts

Posted (edited)

I have a 2017 6.2L 8l90 4wd with max tow.

I experienced the clunking when taking off and stopping sometimes lurching forward.

They said that was normal operation as well and that it was learning my driving and would smooth out.

Wanted to ask how everyone else's 2017 truck is holding up with the 6.2l and 8speed .

 

Edited by 2017gmcsierraslt
Posted (edited)

DO NOT used DexOS2 0w-20 oil,  use 5w-30 or 10w-30. change it at 4000 miles

remove thermostat from trans if it has one,  

change engine t-stat to a 170

 

Edited by pokismoki
Posted

i also installed and Aux trans filter, 

 

be sure to use the correct oil filter for the engine, there are two versions, one is low pressure bypass and the other is higher pressure.  using the wrong one might damage the motor too

Posted

Thanks for the reply. I am using the 0w20 oil and I didn't know about the 2 different oil filters.

Is it the low or high pressure bypass we are supposed to use for the 6.2 liter?

Thanks again

 

Posted

2015 6.2 with 8l90 high country 150,000. Same issues with the trans. Clunking when shifting from park to reverse. Gears slamming when downshifting or slowing down. Almost like the trans does not know what gear it wants to be in. Once you get driving everything seems to get along and drive fine. But that initial startup and shift is violent lol. Had trans flushed and did absolutely nothing. Part of me wants to have new torque converter, steels and frictions put it in and the other side of me says just drive it till she won’t anymore. 
 

the life of a GM owner 

Posted (edited)

Thanks for the reply blbstack. 

I was considering doing upgrades to the transmission but the fluid change stopped the shudder and is shifting much smoother.

The 1st to 2nd clunk is rare now and seems to be normal. 

 

 

 

Edited by 2017gmcsierraslt
  • 1 month later...
Posted

I just picked up a 2017 Denali 6.2 with the 8L90 just over a month ago.  Noticed the same things on the shifting.  Delayed from Reverse to Drive, and Park to Reverse or Drive.  The clunking was noticeable too, but I'm new to the 8 speed and this body style (went from an 09 Tahoe 5.3 with 6 speed).  Just over a week and a half ago, the P0711 code came on for the trans fluid temp sensor.  Carried it to the dealer and thankfully I got an extended warranty.  They pulled the pan and found metal in there and said the torque converter was bad.  Now i'm waiting on them to source a new tranny and torque converter.  Been in the shop a week today.  Good times!

  • 8 months later...
Posted

Cocheese1128;

 

what was the outcome of the trans? Were they able to source parts or just a reman? Shop near me (central Michigan) couldn’t find any parts for the 8l90…

 

I’ve just dealt with the clunking and slamming, probably just ride it out until it no longer moves at this point. 

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined
  • Who's Online   5 Members, 0 Anonymous, 2,189 Guests (See full list)

  • Latest Articles

  • Posts

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

  • Popular Contributors

×
×
  • Create New...