Jump to content

6.6 gas swap

Chebbyfan
 Share

Recommended Posts

Chebbyfan Enthusiast

Chebbyfan

Posted
Posted

I've been reading alot lately about the performance of the 6.6 gas motors in the new trucks.  I love my truck, and only wish it would have more power for get up and go.  I drive my truck the way I want, and sometimes thats faster than most.  I would have a 6.2 half ton, but my enclosed trailer is more than a half ton could pull comfortably.

 

I have seen a few 6.6 gas motors showing up in salvage yards already, and I believe there is even one on ebay for sale right now.  I wonder what it would take to swap in place of a 6.0?  I really don't know much about them except they are a direct inject motor (I think) but my truck is a 15 and shouldn't be that far off on electronics I wouldn't think.

  • Like 1
silveradosid Senior Enthusiast

silveradosid

Posted
Posted (edited)

if this would work i would do it. the problem is the new ecms are locked and you would need the calibrations of the 6.6

Edited by silveradosid
CamGTP Senior Enthusiast

CamGTP

Posted
Posted

The 6.6 is direct injection. Your truck could never run that, not even with a computer swap because you can't tune it.

 

It's easier to swap in a port injection 6.2 or just mod your 6.0 to gain more power. Knowing someone that can tune your truck is the key, the E78 computers are pretty difficult computer to tune for someone that hasn't done a lot of them.

SILVER SLED Senior Enthusiast

SILVER SLED

Posted
Posted

Why not just get an aftermarket stroker crank and a good “towing” camshaft for your current 6.0, or get a junkyard 6.0 and get it built with a stroker crank, cam... then swap it. 

  • Like 1
kenny_r Enthusiast

kenny_r

Posted
Posted

I also pondered this swap....would be cool if it worked but sounds like it won’t.lol

 

 

Edit only because I can’t fit a larger truck in the garage.......way to go gm for making an even larger truck [emoji849]

Chebbyfan Enthusiast

Chebbyfan

Posted
  • Author
Posted

I could mod my current 6.0, and probly will in the future.  It just sounded like it would be cool to do a swap with that new 6.6.  I had mine tuned and it runs rather well, but I still want more out of it.  Probly a cam swap in the future and see if that gets me what I want for awhile, 😏 

i82much Enthusiast

i82much

Posted
Posted

i would like to hear more about 6.0 iron block vvt stroker builds in l96 or ly6 trucks.  is feasible without a lot of other changes?  or do you need injectors, fuel pump, other items besides the engine itself?   i would want a stock idle, keep vvt and torque management, just basically a larger version of the factory l96.

kenny_r Enthusiast

kenny_r

Posted
Posted
i would like to hear more about 6.0 iron block vvt stroker builds in l96 or ly6 trucks.  is feasible without a lot of other changes?  or do you need injectors, fuel pump, other items besides the engine itself?   i would want a stock idle, keep vvt and torque management, just basically a larger version of the factory l96.

Yea that be sweet, idk if I mentioned it in another thread but keeping a basically stock L96, but boring out to 6.2 or 6.6. Would be interested in seeing those numbers if anyone has done something like that
  • Like 1
i82much Enthusiast

i82much

Posted
Posted
27 minutes ago, kenny_r said:


Yea that be sweet, idk if I mentioned it in another thread but keeping a basically stock L96, but boring out to 6.2 or 6.6. Would be interested in seeing those numbers if anyone has done something like that

i don’t know that the ls engines will take the big overbores like some of the older engines, but i have seen stroker kits and curious what other modifications are necessary to run one, besides the obvious internal engine work.  basically, what do you need besides the stroked long block?

  • Like 1

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

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts

  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined

  • Who's Online   4 Members, 0 Anonymous, 1,691 Guests (See full list)

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

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

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...