Jump to content

Recommended Posts

Posted (edited)

Better than my gmt900 5.3 V8. Never been one for the smaller motors in full size trucks but this thing exceeds all my expectations for a V6.

Edited by corwest
  • Like 1
Posted

Better than my gmt900 5.3 V8. Never been one for the smaller motors in full size trucks but this thing exceeds all my expectations for a V6.

That's good to hear. Bad thing is about the forums is you read about an issue and then you might start looking for it. I am on my third Harley and stopped reading the boards because those make all kinds of noises...lol. Just looking to see how people felt about it. I know when I got into a 2014 and drove it I was very impressed but waited a year bought a 2015. My last V8 was a 2007 f150. I am also impressed with this engine,

Posted (edited)

Couldn't be more true. Most people who speak poorly of things on forums go searching for a place to speak that way. It's very rare you find people who are completely satisfied who go looking for a place to tell people how happy they are. Of course this motor is not a V8 and of course it isn't as powerful as one but it is lightyears ahead of what I pictured for a V6 in a half ton and for that it gets my vote.

Edited by corwest
  • Like 3
Posted

I've got about 26,000 miles on my 4.3 and have been very pleased with the performance and towing so far that I have done with it.

 

I wouldn't pay much more for the 5.3, however I do regret not getting the 6.2L, that motor is BEAST

Posted

I had a 2014 4.3l 4WD LT Z71 Silverado with the All Star pack last year and think it's a good engine, but I did have one problem with it.

 

I tow a 2500lb boat at least weekly for half the year. The engine has enough power to easily tow that much weight, but there is no external transmission oil cooler on that model. I asked the dealer I bought it from to install one, and they refused, stating there was no part for it and that they did not recommend I add an aftermarket part.

 

I couldn't get what I wanted so I bought a 2015 5.3l LT Z71 Sierra with Value Pack with an external cooler. Probably overkill for something that likely wouldn't have been a problem, but I lost a year of miles on the truck, added a year of payments at $12/mo higher, so it wasn't a big deal.

 

Other than the transmission cooler, I liked the 4.3l a lot. It drove a lot like my three previous 5.3l Silverados, and even very close on the towing. That's amazing for a NA V6 in my opinion, I'm more impressed by this than the Ecoboost.

 

From what I can tell the 4.3l gets 1-2mpg better than the 5.3l.

  • Like 1
Posted

Well I test drove one right when they hit the lot in 2014, regular cab, and I couldn't believe it, I couldn't believe it was a v6. I waited a year and found a double cab, I don't haul a lot, I just have always drove trucks and dint need a 4x4. I wanted a WT, didn't want all the bells and whistles... Heck I was upset I couldn't get crank windows. But what I want and had to have was the G80 locker, two sand bags in the back and snow is no problem this truck is straight up awesome.

 

This engine is very nice, I couldn't be happier with the engines power gas mileage. I have had no remorse buying this truck...

  • Thanks 1
Posted

I've got 19500 or so on mine, its a 4x4 with a 3.42 rear end and I'm very pleased with it.

  • Like 1
Posted

I have 14000 on mine best 4.3 I have ever owned very pleased

  • Like 1
Posted

7000 miles on mine. Love everything. Really want to try towing with it. Just don't want to go overboard. Would like to trailer my Mustang to the track with it and maybe a travel trailer see how it does

Also if anyone has real world figures on level kit and larger tires, I'm interested in mall crawling

Posted

16000 miles on mine. Have towed between 3000-3500 and it did it very well. Worst tank of gas has been 15.3 (towing in western Maryland mountains) and my best has been 22 (running 75 going to Disney). For everyday driving not much difference between it and my brothers 14 CC 5.3. When he steps on his thats the difference. Not enough for me to worry about though...

  • Like 2
Posted

16000 miles on mine. Have towed between 3000-3500 and it did it very well. Worst tank of gas has been 15.3 (towing in western Maryland mountains) and my best has been 22 (running 75 going to Disney). For everyday driving not much difference between it and my brothers 14 CC 5.3. When he steps on his thats the difference. Not enough for me to worry about though...

I had the 4.3l with 4wd/3.42 gears Xcab last year, now have the 5.3l with 4wd/3.42 gears Xcab and agree with what you say.

 

In normal driving, the 4.3 and 5.3 drive largely the same. The difference is when you put the pedal on the floor because that's when you tap into the extra horsepower and torque.

 

The 4.3l with 3.42 gears is only 1/2 second slower 0-60mph than the 5.3l with the standard 3.08 gears, the 4.3l moves the truck around very well.

  • Like 2
  • Thanks 1
Posted

16000 miles on mine. Have towed between 3000-3500 and it did it very well. Worst tank of gas has been 15.3 (towing in western Maryland mountains) and my best has been 22 (running 75 going to Disney). For everyday driving not much difference between it and my brothers 14 CC 5.3. When he steps on his thats the difference. Not enough for me to worry about though...

My car weighs about 3400 lbs I figure 1,000 for the trailer. And I'm looking at 20 ft pull behinds. Roughly 3500-4200 dry weight I wonder if I'm expecting to much or not
Posted

My car weighs about 3400 lbs I figure 1,000 for the trailer. And I'm looking at 20 ft pull behinds. Roughly 3500-4200 dry weight I wonder if I'm expecting to much or not

I know my truck 4x4 double cab 3:42's had no problem pulling what I put behind it. I was able to maintain 67 mph going up mountains right at 3800 rpm. I could've gained speed if I wanted to. Truthfully I would have zero problems pulling 6000 pounds. I would take it slower so I could stop easier. This new 4.3, while not a V8, is a very solid performer. You will be just fine with that weight!

  • 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
  • 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,640 Guests (See full list)


  • Latest Articles

  • Posts

    • 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. 😄
    • 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
    • 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?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...