Jump to content

Recommended Posts

Posted

Hey folks! I'm new to the forum, and seeking some input from the folks who own these. 

My wife and I are looking to purchase a Suburban 2500, specifically a 2000 - 2006 model with 4wd. For the next 2 years, the truck will primarily be an "around town" truck, but will also be used to drive my grandparents and great grandfather to Connecticut to visit my mother. 

The reason we're looking into a 2500 is because we plan to purchase a camper in 2-3 years and take several cross country trips with it, and this will be our tow mule. The truck will also get used to tow other vehicles, firewood, and other remodeling projects around our property.

Short research has shown me the 6.0 is good for 10k towing, and the 8.1 is good for 12k. While I don't feel it's needed to purchase an 8.1, I want to get some feelers on any issues either engine has, and maybe some pointers on fuel economy expectations. 

The truck will be stock. No lift or leveling kits. Most aggressive tire I plan to run may be a Discover A/T, but more likely the H/T will fill my needs.

Towing wise, my F250 weighs 6700 pounds (it has a service body). It'll probably be the main culprit of being towed unless I buy another project. We're planning on a 24'-27' toy-hauler style camper that weighs 6k - 8k empty.

 

Any advice on the 6.0 or 8.1 (and their transmissions), pro or con, is appreciated!

Posted

Personally the occasional tow is perfectly fine for the 2500.  Low mileage will be your key factor.  I had a 05 gmc 2500 with the 6.0 and I pulled a 14 foot job trailer daily and the occasional 28 ' camper.  It pulled fine, as for gas mileage, it didnt seem to get any worse gas mileage full, or empty.  I dont know what sort of hills you have where you plan on towing, but that may well factor into your plans too.   I don't know anything about the 8.1.

Posted

You are going to get destroyed by MPG but they are great trucks. Single digits when towing most likely

Posted

Thanks! I realized this morning there is a 2500 forum, sorry for dropping this in the wrong place. All of the adds make the mobile website hard to navigate. 
 

We're fully expecting single digits while towing. Outside of towing, I was really hoping for 15-ish on the highway, but the nature of a 8.1 big-block makes that seem unlikely. I'm mainly curious how bad it'll be. 

Posted

Unless you are a serious person about limiting your weights when towing I feel you're better off with excess capability then having just enough to pull the weight you have Having said that, having more than you need is wasteful too, I mean you're gonna be drivin' around for a couple of years with a 8.1 carrying people, certainly over kill (for the present) unless you haul a lot more than planned around your property. I feel it's better to have more than you need than not enough and remember, things and plans change; you might get into some thing else hobby wise or other things can change.

Posted

Realize what you are asking a 16-22 year old truck to do for the next 5-6 years.  Can it still haul at maximum loads this old?  Do you plan to go through all the components and make them new again, new bushings, seals, etc.?  

 

I'd be more inclined to run a 2008-2013 2500 wagon.  Better mileage, newer, can haul just as much with 6-speed transmission even though they are rated for under 10K pounds.  They are towing beasts.

Posted

Yeah but it is a disgusting 08-14 2500. The worst GM interior literally ever. Luckily the 2500s have a decent front end but it doesn't take away from that disgusting inside.

Posted

I had a 2001 8.1 Suburban.  Yes it can pull just about anything you need to pull.  However, mpg was 10 mpg at best.  That is towing or not towing.  

Posted
On 10/24/2021 at 10:13 PM, shakenfake said:

Yeah but it is a disgusting 08-14 2500. The worst GM interior literally ever. Luckily the 2500s have a decent front end but it doesn't take away from that disgusting inside.

Boy, tell us what you really think about the interiors!  LOL

 

I like it!  hahaha

  • Like 1
  • Haha 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,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined
  • Who's Online   5 Members, 0 Anonymous, 2,134 Guests (See full list)

  • Latest Articles

  • Posts

    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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?
    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...