Jump to content

I have a 5.3 and a 6.2 what do I keep

dillpickle
 Share

Recommended Posts

dillpickle Enthusiast

dillpickle

Posted
Posted

I am currently in the process of preparing for a swap I  have a 6.2(L92) with about 190k miles, it has some issues with idling and throttle response, my guess is something with the oil dealing with the VVT/AFM and probably bearings.

I am needing to remove the AFM and VVT for my swap anyway which is about $1000 alone ontop of whatever fixes I might need or maybe not if VVT and AFM are my sole issues.

 

I have a 5.3 with about 184k miles on it, I'm not exactly sure how well it runs atm since the radiator is destroyed. 

 

I'm looking to hopefully achieve 500hp while being a street daily/weekend car. I'd love to get a supercharger but I cannot justify the 5 figure price tag.

realistically I don't need any more power than the 300hp from the 5.3 however its my dream car and I might as well get some more power. The 5.3 has the 4l60e where as the 6.2 will have a 6l80e which will cost around $7000, or $8000 if I want the 650hp rating

CamGTP Senior Enthusiast

CamGTP

Posted
Posted

So what is your actual question??

 

What engine are you going to use?

 

Also a stock rebuilt 6L80e with a good torque converter will handle 500-600hp all day long with a good tune. Spending 7-8K on a built up transmission is kind of a waste. If you put in good clutches and stuff in the 6L80e, that's all it needs in a car.

dillpickle Enthusiast

dillpickle

Posted
  • Author
Posted
1 hour ago, CamGTP said:

So what is your actual question??

 

What engine are you going to use?

 

Also a stock rebuilt 6L80e with a good torque converter will handle 500-600hp all day long with a good tune. Spending 7-8K on a built up transmission is kind of a waste. If you put in good clutches and stuff in the 6L80e, that's all it needs in a car.

is it even possible to get a 5.3 up to 450-500hp while being a daily driver? The 6.2 will need probably thousands in repairs who knows.

 

And for the transmission the base kit price is $6,350 and $7,600 for the 650hp upgrade which includes a billet TC

CamGTP Senior Enthusiast

CamGTP

Posted
Posted (edited)

Yes a 5.3 can make that much power at the crank but it will take a rowdy camshaft and some headwork to make that power but the downside is that it wouldn't be as friendly to tune and drive. A stock 5.3 is putting down maybe 280-300hp to the rear tire, making another 100hp is going to take some work.

 

A 6.2 is such a better starting point. It would only take a camshaft, some long tubes and a good tune to be making roughly 500 crank horsepower.

 

And $6.350 for a base kit 6L80e is absurd. You could buy a brand new 6L80e from the GM dealer, toss in a billet converter and be way better off. It will hold the power no problem. There are guys making 600+ crank horsepower on factory transmission in trucks with  magnuson supechargers. The trucks are way harder on transmissions than cars.

 

Also put it this way, a stock 6L90e behind a CTS-V that makes 650hp from the factory can hold the power. Buying a built up 6L80e that can handle 650hp per their rating for nearly $8,000 sounds kinda dumb.

Edited by CamGTP
  • Like 2
dillpickle Enthusiast

dillpickle

Posted
  • Author
Posted
40 minutes ago, CamGTP said:

Yes a 5.3 can make that much power at the crank but it will take a rowdy camshaft and some headwork to make that power but the downside is that it wouldn't be as friendly to tune and drive. A stock 5.3 is putting down maybe 280-300hp to the rear tire, making another 100hp is going to take some work.

 

A 6.2 is such a better starting point. It would only take a camshaft, some long tubes and a good tune to be making roughly 500 crank horsepower.

 

And $6.350 for a base kit 6L80e is absurd. You could buy a brand new 6L80e from the GM dealer, toss in a billet converter and be way better off. It will hold the power no problem. There are guys making 600+ crank horsepower on factory transmission in trucks with  magnuson supechargers. The trucks are way harder on transmissions than cars.

 

Also put it this way, a stock 6L90e behind a CTS-V that makes 650hp from the factory can hold the power. Buying a built up 6L80e that can handle 650hp per their rating for nearly $8,000 sounds kinda dumb.

well I guess I'll tear apart the 6.2 once I have room after I sell my 2017 silverado for 10k. hopefully the damage isn't too bad

 

as for the 6l80e, that includes a standalone transmission controller, T-case Adapter, 27 spline output shaft and probably more stuff. $1250 increases the power rating to 650hp and comes standard with a multi-disc billet TC

KARNUT Senior Enthusiast

KARNUT

Posted
Posted

I would approach it a little differently. You already have a 6.2 truck. I would do a rebuild eliminate the cylinder deactivation. I match the cam a good set of headers and tune it. Maybe add E-85 if it’s plentiful in your area.  I’d gear it. Eliminating the nannies and gearing it would really hit the seat of the pants. Without hurting reliability. The nannies really affect the seat of the pants feel. 

CamGTP Senior Enthusiast

CamGTP

Posted
Posted

What kind of vehicle is this going in that needs a separate transmission controller??

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   3 Members, 0 Anonymous, 1,633 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...