Jump to content

Recommended Posts

Posted

I would love for GM to come out with an SS version. Maybe something based off the custom but with the 6.2 or better and with slightly lowered suspension and so forth. Anyone else think that would be sweet or buy one?

  • Like 1
  • Thanks 1
Posted (edited)

Most definitely with a Supercharged 6.2L with say 700HP.  😃👍

Edited by Steve-2019
  • Thanks 1
Posted

I had planned to buy a brand new truck at a certain arbitrary point in my life that wouldn't make sense to most, if they release a RCSB with the 6.2 it will be that or an SS. If they don't do those things I will never buy a new truck lol

  • Like 2
Posted

I am totally not a lifted truck guy. Never have liked them because of the hinderance on the performance side. If GM decided to release a new version of a supercrew SS truck with the stance of the 03-06 SS trucks.  I would place my order with them tomorrow.

 

Wish list:

 

22 with optional 24 inch wheels

ZL1 suspension (lowered)

paddle shifters with 10 spd 

dual quad tip exhaust with selectable exhaust features

different modes of driving (sport, track, wet/traction, snow)

selectable 2WD, 4WD, and AUTO 

Leather seats with suede inserts.....loved them in my SS Trailblazer 

 

 

 

 

 

  • Thanks 2
Posted
5 minutes ago, TNTSilverado said:

I am totally not a lifted truck guy. Never have liked them because of the hinderance on the performance side. If GM decided to release a new version of a supercrew SS truck with the stance of the 03-06 SS trucks.  I would place my order with them tomorrow.

 

Wish list:

 

22 with optional 24 inch wheels

ZL1 suspension (lowered)

paddle shifters with 10 spd 

dual quad tip exhaust with selectable exhaust features

different modes of driving (sport, track, wet/traction, snow)

selectable 2WD, 4WD, and AUTO 

Leather seats with suede inserts.....loved them in my SS Trailblazer 

 

 

 

 

 

Yes, I had an 06 TB SS and loved though seats as well not too mention the engine. 

  • Like 1
Posted

I got tired of waiting for an SS model so I sold my 03 SS that I bought new off the showroom floor, and bought my 19 High Country. I would definitely take a look at one if they came out with one.

Posted (edited)
1 minute ago, RAYS B4U said:

I got tired of waiting for an SS model so I sold my 03 SS that I bought new off the showroom floor, and bought my 19 High Country. I would definitely take a look at one if they came out with one.

Do you miss it?  I miss my SS Trailblazer. I know its not a truck but it towed my boat well and loved the lowered stance, and of course the Vette motor was fantastic  

Edited by TNTSilverado
Posted
9 minutes ago, TNTSilverado said:

Do you miss it?  I miss my SS Trailblazer. I know its not a truck but it towed my boat well and loved the lowered stance, and of course the Vette motor was fantastic  

I actually drove mine on pipelines when I went on training detail. It was tricky at times and did more walking than usual. I still had my Z-71 but I just loved driving that trailblazer. To answer the question as long as GM has cylinder deactivation I’m out. I believe GMs outside the box performance days are over. 

  • Like 1
Posted
4 hours ago, Low Elevation said:

I would love for GM to come out with an SS version. Maybe something based off the custom but with the 6.2 or better and with slightly lowered suspension and so forth. Anyone else think that would be sweet or buy one?

 

In a second!

 

I could see this as a starting point.

 

These trucks as a regular cab have a lot of potential!

 

 

5e716551ffde3bb3c6f44e6e1a907006.jpeg

20c4f4256866d4223f5b4999a2b285e2.jpeg

92e235fa622c0d3fb7db9a8862ecdf94.jpeg

f635b682b8cad5f75f6561b5038a9b02.jpeg

  • Like 1
Posted
On 5/3/2022 at 3:04 PM, Low Elevation said:

Heck I’d also be happy if they just offered the 6.2 as an option in a Custom.

You can get the Custom Trail Boss with the 6.2 engine.

 

I just hit the configurator on the chevrolet website, and under Custom Trail Boss I could select:

6.2L ECOTEC3 V8 ENGINE WITH 10-SPEED AUTOMATIC TRANSMISSION

 

If I would have ordered my Custom Trail Boss, instead of purchased off of the lot, I probably would have gotten the 6.2 instead of the L82 5.3 with the 6 speed that I have now.

Posted
3 hours ago, Railroad_Jim said:

You can get the Custom Trail Boss with the 6.2 engine.

 

I just hit the configurator on the chevrolet website, and under Custom Trail Boss I could select:

6.2L ECOTEC3 V8 ENGINE WITH 10-SPEED AUTOMATIC TRANSMISSION

 

If I would have ordered my Custom Trail Boss, instead of purchased off of the lot, I probably would have gotten the 6.2 instead of the L82 5.3 with the 6 speed that I have now.

Ya but it’s lifted and bigger tires. Hinders performance. We as “SS” guys want a leveled or slightly lowered truck that Handles more like a street car/truck than a “Hummer”.  
 

 

  • Haha 1
Posted

Yeah I wasn’t aware you could get that with the custom TB but still not my cup of tea. Something likes this is more what I would like them to offer.

image.jpeg.40a432059b2a3365db76d15cdf4f6e4a.jpeg

  • Like 1
  • Thanks 1
Posted
2 minutes ago, Low Elevation said:

Yeah I wasn’t aware you could get that with the custom TB but still not my cup of tea. Something likes this is more what I would like them to offer.

image.jpeg.40a432059b2a3365db76d15cdf4f6e4a.jpeg

That’s a badass looking truck!  

  • Like 1
Posted

I've seen a guy rolling around in my county in a custom T-1 regular cab short bed. Traffic jammed me up and he got away  before I could catch up to him.....lowered 6-7 inches on some massive tires and wheels but not laying frame. It's got a great stance ! He appeared from behind other vehicles quietly and disappeared just about the time I realized what it was.

 

Probably totally useless as a truck but the ear to ear grin on his face spoke volumes !

 

I think I actually drooled a little as he went by ......

  • 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,694 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...