Jump to content

Recommended Posts

Posted

My brother has no complaints about his 5.3/8 speed/3.23 2019 SLT yet. As someone else noted, $0.20 CAD/litre ($0.60 USD/ gallon) more for premium makes the 6.2 unattractive if you don't have a need for the extra power (even if it's only recommended).

Posted
On 10/23/2019 at 11:01 AM, greatmizzou said:

?

 

I might be mixing my articles.   I think Im confused about comparing the 6.0HD engine with the 6.2 , and the comparisons to the 6.6HD gas to the 6.2.  I googled it to re read the article and found it.


As far as the 5.3 to the 6.2 it looks like the 6.2 beats it pretty soundly, just more $$$

 

 

he may have been thinking about an article that tfltruck did,  where they picked the 5.3 over the 6.2 for towing.  I don't remember their reasoning,  you would have to find the article...

Posted
22 hours ago, wizard4878 said:

he may have been thinking about an article that tfltruck did,  where they picked the 5.3 over the 6.2 for towing.  I don't remember their reasoning,  you would have to find the article...

Higher payload capacity allowing for a heavier tongue weight, maybe? 

Posted (edited)
1 hour ago, Cpl_Punishment said:

Higher payload capacity allowing for a heavier tongue weight, maybe? 

I think it had something to do with weight or weight distribution,  I'll see if I can find it

 

So I found it,  they are testing a 5.3 with the 8 speed and a 6.2 with the 10.  In this video neither truck was maxed out, and it was about the fact that the 5.3 was lighter weight therefore having a better payload capacity and 30lbs greater tongue weight.

I guess I didn't realize that the 6.2 was that much heavier than the 5.3, and of course the 10 speed is heavier than the 8 speed

Edited by wizard4878
found more info
  • Like 1
Posted

I have had a 2004, 2014 and 2017 with a 5.3 and was very happy. I recently purchased a 2020 with the 6.2 and love it. I'm not saying the 5.3 is bad but this 6.2 is just better in my opinion. Everyone has to decide what is best for them but I won't go back to a 5.3 now. 

  • Like 3
Posted

I test drove a couple of trucks with the 6.2, and it felt like a race engine. Phenomenal power, but I really dont need it. The reason i bought the 5.3 was it was cheaper and ran regular fuel. I will say if i did it again, i would have bought the 6.2 just because. Maybe my next truck.

  • Like 1
Posted

I've got my 18 1LE Camaro to enjoy a 6.2   -  my 19 Silverado is just a daily commuter / Home Depot project hauler.    So I have no problems with the 5.3 it does what I need, it has A/c and heat and xm radio Haha!

 

 

  • 3 months later...
Posted

If you opted for the 6.2L, that's great. MY Sierra SLT X31 with 5.3L is transformed by GM's new 10 speed auto. This transmission

really puts out the power where you need it with that wonderful 5.3L.  I wouldn't change a thing

  • Like 1
Posted

The GM trucks wanted more than the cost for the 6.2 to get that engine. The Texas editions and SLEs didn’t offer that engine. I wasn’t willing to pay 7-10k more to get it. Especially when I spent most of my life cruising the HWY.


Sent from my iPhone using Tapatalk

Posted

I am picking up my new 2020 LT Trail Boss with a 5.3l engine this Friday. I would have absolutely ordered the 6.2l engine, but I couldn't find any in the trim I wanted. Most of the trucks available on the lot are 5.3l with the short beds. I was able to find a standard bed which i really wanted but not the 6.2l.

 

I drove my buddy's 18 Chevy LT with the 5.3l and it felt quick. I'm coming from a 2012 Ram with the Hemi and the Chevy seemed to be pretty close to speed. I had nothing but issues with the Ram (lifters/cam) and a ton of electrical issues, so I'm hoping for a lot more luck with the Chevy!

 

I'm really stoked to be getting the truck and I know I will be happy with the 5.3l.

  • Like 2
Posted

I'm coming from a 2016 Tacoma TRD OffRoad with a really pokey V6 to my new 2020 LT TrailBoss with the 5.3L. I'm really enjoying the power and I have zero complaints so far. Now it doesn't compare to the EcoBoost in my old 2012 F150 in terms of speed and acceleration, but I'm older now and I just don't feel the need to race other vehicles on the street. Plus fuel economy and the loss of power when accelerating once I got past 100K miles really didn't do that truck any favors. Hence the purchase of my old Taco.

 

Anyways, this 5.3 is plenty fast for me. And if I feel the need for speed, I still have my 2020 Lexus RX350 F-Sport, which oddly enough uses the same engine as my old Taco (2GR-FKS). However my RX was way faster than my old truck. Just goes to show how important your transmission and shift-points are.

Posted
17 hours ago, Garys007 said:

I am picking up my new 2020 LT Trail Boss with a 5.3l engine this Friday. I would have absolutely ordered the 6.2l engine, but I couldn't find any in the trim I wanted. Most of the trucks available on the lot are 5.3l with the short beds. I was able to find a standard bed which i really wanted but not the 6.2l.

 

I drove my buddy's 18 Chevy LT with the 5.3l and it felt quick. I'm coming from a 2012 Ram with the Hemi and the Chevy seemed to be pretty close to speed. I had nothing but issues with the Ram (lifters/cam) and a ton of electrical issues, so I'm hoping for a lot more luck with the Chevy!

 

I'm really stoked to be getting the truck and I know I will be happy with the 5.3l.

Congrats on the new TB! Most likely your truck has the 10-speed transmission, which really helps make the 5.3L feel stronger than it probably is. Most of us with 2019+ 5.3Ls on here have notice that it feels much snappier than the previous 5.3L powertrain combos. 

 

I'm putting a GM Performance Exhaust and CAI on my 5.3L next week. I've never felt the 5.3L to be sleepy or sluggish at all, but I'm pumped for the little boost the exhaust and intake will give to it. I decided to spend $2K on this vs. trading my truck in for a 6.2L. I think it's a good compromise that I'll be happy with. 

Posted
On 4/8/2020 at 9:06 AM, franktrusty said:

I just purchased a Sierra crew 5.3 SLT. Wanted black, and only 6.2  was white. I drove the 6.2 first, and the 5.3 second. I really couldn't tell a difference between the two. I figured something changes maybe computer wise after some miles are put on them. I had a black Silverado Z71 RST 6.2 ordered with a build date of first week of April, and it was never going to be built... But I sure like all the features this truck came with....

Screenshot_2020-04-06-10-02-07-1.png

 

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
  • 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   6 Members, 0 Anonymous, 1,554 Guests (See full list)


  • Latest Articles

  • Posts

    • 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.
    • 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.
    • 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?
    • I went to the county a few years back to dispute my property taxes. To do that I hired an appraiser and a lawyer. The County Assessor wished to argue that the homes in my neighborhood the appraiser used were all 'distressed properties" and not representative of the "Market Average".    My response was," Of the 50 homes in our subdivision 43 of them were "distressed properties" under bank foreclosure and as such "Distressed IS the market". Lawyer about choked on his coffee and handed the Assessor the 'receipts'.    I won that case on the evidence provided by the Lawyer and the Appraiser.    We have the same thing going on here. My statements were based on the GOVERNMENTS NATIONAL DATA and yours on local markets in areas of your interest. They are both correct....   Thing is, this divergence was based on NATIONAL and not on LOCAL. I think you even understand that. But like you said, we are both stubborn and hardheaded.    I do not see any advantage to disengagement.  But that said we can step back to compose ourselves. 
    • Trust me I appreciate the comments and concerns. It's what I was looking for to help me evaluate the situation and what I want to do. I have decided to move forward with the BORA hubcentric slip on 3/8" (.375") with the extended lugs nuts. Fedex says they should be here Monday :). Meanwhile, the dealer got the remote start and Patriot spray in bed liner done over the last couple of days. Also, I installed an inline stop/start eliminator today. Starts back up in what whatever mode you shut it off in, so you don't have to hit the button every time you fire up.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...