Jump to content

2015 1500 5.3 6L80 Swap to 8L90

MrRosado

By MrRosado
in Engines & Drivetrain

 Share

Recommended Posts

MrRosado New Member

MrRosado

Posted
  • Author
Posted
On 2/12/2020 at 7:57 PM, flyingfool said:

Richard Wardell will tell you how to do it, he's on youtube, so you'll have to track him down to get his shop phone number. 

 

I got in touch with Richard and swap would require a new ECU wiring harness on top of the harness for the TCU, and a laundry list of other minor tweaks and modifications. Long story short can it be done yes, is it worth it no. At this point I think when the time comes I will just have the 6L80 rebuilt with parts that address the known issues and weaknesses of the 6L80.  

tmo Enthusiast

tmo

Posted
Posted

They started putting the new 10 speed in the later Tahoe’s, Escalades and Suburbans. Wonder if that would be better than the 8 speed?

flyingfool Senior Enthusiast

flyingfool

Posted
Posted
1 hour ago, truckguy82 said:

If that’s all it is, anybody who doesn’t tune their 8l90 is missing out big time

 

It’s awesome in the camaro.

not sure any trans after 2016 is reprogrammable , software is under lock down

CamGTP Senior Enthusiast

CamGTP

Posted
Posted

2017, 2018, 2019's and maybe the 2020 camaro TCM's can be programmed, it's on the HP Tuners website.

 

It requires an unlock service plus the credits to do it. Note this is only of the 8 and 10 speed transmission. 6 speed TCM's do not require this service.

 

The 2019's are for the camaro/corvette, surburban/yukons that are still running the E92 computers. The T1 trucks have nothing for the TCM's yet.

  • Like 1
  • Thanks 1
  • 9 months later...
flyingfool Senior Enthusiast

flyingfool

Posted
Posted
On 12/5/2020 at 1:14 PM, TrkNrrs said:

I bought everything for this swap

 

8l90 trans

matching electronic transfer case

2017 8L90 cooler line set

L83 and 8L90 engine/trans harness

8l90 tcm

 

But I want to know if I can get get a flexplate and torque converter from a gen 3 Ctsv to work for me? If anyone has a definitive answer..

 

** nevermind finally found the part number for ctsv flexplate**

 

Will be reprogramming the bcm and gauge cluster as well when it goes in, will let you all know what’s up when it’s in

start another thread on this when you begin.

  • 4 years later...
1vicious_gmc New Member

1vicious_gmc

Posted
Posted
On 2/18/2020 at 10:08 AM, MrRosado said:

I got in touch with Richard and swap would require a new ECU wiring harness on top of the harness for the TCU, and a laundry list of other minor tweaks and modifications. Long story short can it be done yes, is it worth it no. At this point I think when the time comes I will just have the 6L80 rebuilt with parts that address the known issues and weaknesses of the 6L80.  

Do you happen to have the list of what all was needed to get this done?

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
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      I hope to high heaven this is wrong. My Chevy farm trucks frame is lasting way longer than a newer Nissan Titan XD I got for a steal, and it only pulls trailers. A decade younger and it's frame is already way rustier than the waxed Chevy I drive across longs and ditches. Also, hasn't Ford been having tones of troubles with rusted frames? 
    • Coastie05
      2027 GMC Sierra: Official Discussion

      By Coastie05 · Posted

      Batteries don’t always show signs of a few years ago my vehicle started fine in the morning and took me to work. After work the battery was completely dead and I needed a jump. No, I didn’t leave anything on and the battery was only a couple months old. It was replaced under warranty. 
    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • NDKoze
      2027 GMC Sierra: Official Discussion

      By NDKoze · Posted

      If his battery was that bad I would think it would have been showing signs before this that were ignored. Stinks that it happened the way it did in rush hour traffic, but this seems like a pretty fringe scenario. I don't mind it that bad and never turn it off. The only slight annoyance for me is the slight delay between brake to gas, but I have gotten used to it and figure if it can save a little gas why not.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...