Jump to content

Swapping an L86(6.2) into a 5.3 (L83)

Gavin Faulkner

By Gavin Faulkner
in Engines & Drivetrain

 Share

Recommended Posts

Gavin Faulkner Enthusiast

Gavin Faulkner

Posted
Posted

Hey everyone,

I just completely blew my motor up yesterday in my 2015 Silverado 5.3 w 6L80. I am wondering what it takes to swap the 6.2 into my truck. as far as harnessed and what not. id love any input i can get. 

Thanks 

BC0573E4-C003-45A6-85FC-854A32710F62.jpeg

  • Sad 1
CamGTP Senior Enthusiast

CamGTP

Posted
Posted

If you buy a 2014-2015 6.2 engine it's basically plug and play with the harness, nothing is really different. The later years after 2016 I believe run a different high pressure fuel pump so the connector is different.

 

The rest is tuning.

  • Like 1
  • Thanks 1
  • 7 months later...
gat0r Enthusiast

gat0r

Posted
Posted

just in case, for others on this topic....

 

Fuel pump control module harness

2014-16 are 4 pin and the 2017+ are 3 pin

  • 1 year later...
AztekxBeast New Member

AztekxBeast

Posted
Posted
On 11/2/2023 at 10:19 PM, gat0r said:

just in case, for others on this topic....

 

Fuel pump control module harness

2014-16 are 4 pin and the 2017+ are 3 pin

Do you know if there is a way to swap that part of the harness out or to change from 4 to 3 vice versa? I have a 2014 with 5.3 looking to swap to 6.2 and I have seen more later model 6.2s in DFW.

AztekxBeast New Member

AztekxBeast

Posted
Posted

From the research I have found I am happy that I can continue to use the 4L80e that I have lol. It was rebuilt in march so I have like 1-2k miles on it. From what I can see my only concern is the fuel pin connectors between newer models if I can't find a decent motor thats in my year range for direct bolt up. I didn't plan on doing a full rebuilt just the cams and heads to get rid of that nasty AFM. I was also given full bolt on exhaust from my cousin so that as well but I do want something reliable that will last me years to come for sure. 

 

Motor mounts for the 6.2 from 5.3 are also direct bolt ons and placement?

  • 3 months later...
mayutt Enthusiast

mayutt

Posted
Posted

I drive a 2014 Sierra 1500 SLT with an L83. It has over 220K and still runs great, but I'm starting to research an engine swap as I intend to re-engine and keep driving it when this one goes.

 

I see the L86 is a direct form/fit/function minus some tuning...my question is regarding the Flex Fuel sensor. Since my truck is factory Flex Fuel, will it be fine to run the L86 on ethanol too (if I install a rebuilt L86 vice L83)?

  • 1 month later...
M1ck3y Senior Enthusiast

M1ck3y

Posted
Posted
On 3/25/2025 at 7:17 AM, mayutt said:

I drive a 2014 Sierra 1500 SLT with an L83. It has over 220K and still runs great, but I'm starting to research an engine swap as I intend to re-engine and keep driving it when this one goes.

 

I see the L86 is a direct form/fit/function minus some tuning...my question is regarding the Flex Fuel sensor. Since my truck is factory Flex Fuel, will it be fine to run the L86 on ethanol too (if I install a rebuilt L86 vice L83)?


yes the l86 can run on e85 but it has to be turned on in the tune. 

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

    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      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
    • davester
      Replacement Radiator

      By davester · Posted

      And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • davester
      Turning radius

      By davester · Posted

      Just don't turn the steering wheel as much?
    • Snowcamo
      Replacement Radiator

      By Snowcamo · Posted

      Rockauto bud. I pass local stores for parts.   Findya something online. 

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...