Jump to content

Recommended Posts

Posted (edited)

Gents - the used market is just too nuts right now so I have switched to new trucks. Looking at a 21 Sierra Elevation with x31 or a 21 Silverado RST with z71.  I know basically same truck except looks. Both 5.3, gm is 10spd auto, chevy is 8spd auto.  Priced pretty close to each other.  

 

Thoughts on which one or is it really down to my looks preference?

 

Thanksimage.png.bdd62dd60bb1f507ddb39dbeb48d2e79.png  image.png.aa9bf9e76bccf92a4c3b7c7cdb0380b3.png

Edited by yzinger
added pics
Posted

I would go with the 10-speed over the 8-speed The look of the GMC is just better to me but that's all opinion of course. I don't know this for a fact but resale may also be slightly better on the GMC.

 

 

  • Like 1
Posted

thanks - i do sort of like the 10spd. The Sierra headlights remind me of an f150 eek,.

Posted

They are both beautiful trucks. Mainly comes down to your preference since they are basically the same package other than the tranny. But you are taking this from a AT4 owner [emoji23].

  • Like 1
Posted

I like them both. Have both in the family. I love my Chevy High Country but my stepfathers Sierra SLT is a bit quieter. But from experience I would go with the 10 spd over the 8 spd. 
good luck!

Posted

man i sort of agree. I like the RST looks better but I like the 10spd. Especially with the gearing in both at 3.23 (although thats not much higher than 3.42s)

 

I expect even the 8spd will be fairly snappy with those gears right?

Posted

I'm partial to the looks of the GMC myself (yes, I have an RST), and with the added benefit of the 10 spd, I'd be looking at the GMC (all else being equal).

Posted

I hope to go see them in person this afternoon. Tell me Jim - why do you like the GM better and also - can you speak to your 8spd RST - has it been good for you? Still lots of get up and go?

Posted

I was also looking at both, going back and forth and ended up getting a Black RST with the 6.2 and 10 speed transmission, I just didnt like the huge front end of the GMC

but the 10 speed is awesome.69137FC6-534B-4961-AC10-30C2BEDBEBF8.thumb.jpeg.a09f575ce21ad16a8890534d1175e699.jpeg

  • Like 1
Posted

To me this year has much better luxe. Also that 10 speed has been less problematic than the eight speed. Plus who doesn’t like to extra gears!

Posted

Any other options/ equipment differences between the two? Sounds like you’re leaning towards the Chevy. If the 10 speed is the only material difference, not sure you should let that sway you into a truck you don’t like as much.

 

I have the 10 speed and it’s flawless but my experiences with the 8 speed were good too. Drive both and see.

Posted

The Chevy looks like it was styled by a cross-eyed 7 year-old, while the GMC looks like it's the illegitimate love child of a Tundra and a Titan XD.  Fortunately you can't see either from the driver's seat.

 

Go with the 10 speed.

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   4 Members, 0 Anonymous, 2,136 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...