Jump to content

Recommended Posts

Posted

Does anyone have a picture of a white RST with black emblems in place of the chrome? If possible one with a Duramax as well?

 

I'm looking at spending some of my Reward points on the emblem package for my 2020 RST with the 3.0.

Posted
Just now, Carbon said:

I just bought the black duramax ones for the hood. Installing this weekend.

Shoot up a picture when you get them installed. I'd be interested in seeing them. I'm debating on getting the whole badge package (non-Z71) and changing all my chrome ones to black. I'm not sure about all the chrome badges when everything else is either black or painted white.

Posted

Will do. My plan is to do the tailgate next. ebay has some nice red and black RST badges available. The Z71 I cannot find in gloss black and may get deleted but undecided. 

 

Will post up on the duramax. I may also have some pics in my phone of other trucks, will look

 

Posted
Just now, Carbon said:

Will do. My plan is to do the tailgate next. ebay has some nice red and black RST badges available. The Z71 I cannot find in gloss black and may get deleted but undecided. 

 

Will post up on the duramax. I may also have some pics in my phone of other trucks, will look

 

The RST is the only one in the GM package I don't like since it is all black. I may look at eBay for a red/black RST emblem.

Posted

That definitely looks better. Hopefully, they are not too hard to put back on after removing the OEM ones. Luckily I just got the truck so hopefully they are not too bad to remove.

Posted (edited)
4 minutes ago, mjonesjr84 said:

Thanks. I found a couple that I'm watching. I'm going to get the other black ones changed out first and then maybe get one like that.

Black looks sooooo much better.  

 

The silver metallic is mine

20200920_185724.jpg

20201024_172100.jpg

20201010_211433.jpg

Edited by fsuboy75
Posted
Just now, mjonesjr84 said:

Agreed @fsuboy75. I just don't understand why they use the chrome emblems when that is the only chrome on a RST. SMH

Exactly why I went all black.  I couldn't stand some black and some chrome!    

Posted
54 minutes ago, Carbon said:

Will do. My plan is to do the tailgate next. ebay has some nice red and black RST badges available. The Z71 I cannot find in gloss black and may get deleted but undecided. 

 

 

 

I can't find gloss black Z71 emblems either.  I've ordered two sets, thinking second one was gloss.  It was same.  I may spray paint them gloss black and maybe add a gloss clear.  It doesn't really look that bad.  The only time it looks awkward is in my garage under fluorescent light, the 6.2 on hood is super shiny and the Z71 is not.  I also am debating just removing the chrome Z71.  

Posted
3 minutes ago, SILVER SLED said:

I can't find gloss black Z71 emblems either.  I've ordered two sets, thinking second one was gloss.  It was same.  I may spray paint them gloss black and maybe add a gloss clear.  It doesn't really look that bad.  The only time it looks awkward is in my garage under fluorescent light, the 6.2 on hood is super shiny and the Z71 is not.  I also am debating just removing the chrome Z71.  

Spray it gloss black and clear coat it.    Looks better with than without.  

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
  • Latest Articles

  • Posts

    • 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.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...