Jump to content

Engine swap

emtnm
 Share

Recommended Posts

emtnm Enthusiast

emtnm

Posted
Posted

I know I might get some flack for this but here it goes. I am thinking about taking out my 8.1 and swapping it for a 5.3. Just wondering if the wiring, or computers need to be changed. I’m mainly considering doing this because of fuel mileage and needing to find an oil leak that might be causing the engine to knock really bad. Any info that can be provided would be greatly appreciated. 

shakenfake Senior Enthusiast

shakenfake

Posted
Posted

You do not want a 5.3 in a 2500 truck.

 

You would have to change the wiring. I believe that the 8.1 computer will work with a 5.3 but I cannot remember

emtnm Enthusiast

emtnm

Posted
  • Author
Posted (edited)

Why would going to the 5.3 be a bad idea? What about going to the 6.0?

Edited by emtnm
David89GMC Enthusiast

David89GMC

Posted
Posted

Why would an oil leak cause the engine to knock?

You won't like the 5.3 if you ever try to tow anything.

Just how can you justify the expense? How many YEARS of ga$ $aving$ will the 5.3 $$$wap have over just keeping the 8.1? That's an expensive swap.

If you're able to swap the 8.1 for a 5.3 and handle the technical issues, why can't you just coax more fuel mileage from the 8.1?

A smaller engine will have to work harder than a large engine, so the 5.3 mileage won't be nearly what you expect.

 

Get a good programmer and adjust the parameters until your 8.1 mileage gets better.

davester Senior Enthusiast

davester

Posted
Posted (edited)

Just to follow up with your original idea, you need the engine, transmission, transfer case, wiring harnesses at least for the engine, transmission, and to the bcm (unless you like diffing the wiring diagram and repinning/wiring stuff, ecm at least, custom fab a driveshaft, possibly the front one as well, instrument panel (it's programmed different between gas and diesel), if the two trucks have different option packages, that is more work to either transplant or get it going.

 

And that's it you transplant in the 6.0/4l80e

 

Edit:

 

Oh yeah, I believe the radiator, shrouds and metal piece (forget the name of it) that goes across the front of the truck holding the radiator are all different as well.

Edited by davester
shakenfake Senior Enthusiast

shakenfake

Posted
Posted

6.0 would be a great idea. I would do that. Skip the programmer though, you are not going to get any real mileage out of it.

 

@davester This is a gasser to gasser swap not a diesel to gasser swap. Half that stuff you just brought up does not need to be touched at all lol

davester Senior Enthusiast

davester

Posted
Posted

ok, you don't need to do the engine harness, bcm, ip.  Still need to change all the driveline parts, and rewiring the transmission harness.

emtnm Enthusiast

emtnm

Posted
  • Author
Posted
51 minutes ago, davester said:

ok, you don't need to do the engine harness, bcm, ip.  Still need to change all the driveline parts, and rewiring the transmission harness.

Are you talking all driveline part, ie: differentials and rear axle?

shakenfake Senior Enthusiast

shakenfake

Posted
Posted

You would only need to do that if it came with an Allison.

Also I don't think the original engine harness works with an LS. The 8.1 is not an LS and therefore has different connectors.

davester Senior Enthusiast

davester

Posted
Posted

The 8.1 comes with an Allison.  You don't need to replace the front/rear diff, but the driveshaft will be a different length and you probably would need some adapter u-joints.

davester Senior Enthusiast

davester

Posted
Posted

From brief googling, it should bolt up to the allison, so that would cut down a lot of work.  You'd have to sort out flexplate/starter/engine mounts and then clearance around the front of the engine (as the engine is a little shorter, you still want the fan in the shroud to pull air through the radiators).  And you may want to regear it as the 6.0 will be happier with 4.10's vs I think the 8.1 normally gets 3.73.

emtnm Enthusiast

emtnm

Posted
  • Author
Posted

Thank you all for your help. I will be coming back and asking more questions as the time for the swap comes near (if the wife actually lets me). 

shakenfake Senior Enthusiast

shakenfake

Posted
Posted
On 8/9/2022 at 9:39 PM, davester said:

The 8.1 comes with an Allison.  You don't need to replace the front/rear diff, but the driveshaft will be a different length and you probably would need some adapter u-joints.

Not all 8.1s came with an Allison. The did come with a 4L80 as well.

 

The Allison has it's own TCM, trying to tie that into the PCM may be tricky

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...