Jump to content

Recommended Posts

Posted (edited)

I also did this on the 2023. I use Testors model car paint. I'm sure Rustoleum would work, too. I would like to do something similar to the Duramax lettering. I think that should be vinyl. 20250518_072921.thumb.jpg.a433153890dca1fb9009174d0a747a16.jpg

Edited by Jus Cruisin
  • Like 2
Posted (edited)

I swapped everything to the equivalent of "Dark Essentials".  I tried Plastidip but too many small corners and crevices and I couldn't get a good finish.  My purchases:

 

GM 86539780 - Black Emblem Kit (Includes (2) Silverado fender badges, (2) Duramax and (2) 6.2L badges, and the tailgate "Silverado" and "LTZ" badges.  - $75 on eBay

 

(2)"Texas Edition" Emblems in Black - $13 on eBay (my truck is Texas Edition)

 

GM 84434790 - Combo black bowtie package for grille and multipro tailgate for 19 -22 pre-refresh - $49 on eBay

GM 84432695 - Black Z71 Emblems - $36 on Amazon

 

If you are doing this yourself, also highly recommend a heat gun and an eraser wheel.  It makes removing and cleaning the areas around the old logos MUCH easier. 

 

Very happy with the outcome:

 

 

 

 

 

 

image0 (10).jpeg

image0 (11).jpeg

Edited by parthery
  • 2 weeks later...
Posted

Here's another that I'm working with tvd vinyl to produce. I've sent them tracings and measurements. I received a prototype to test yesterday. I think it's fine. I emailed them pictures this morning. They are floating on soapy water (temporary) 20250605_171432.thumb.jpg.efa24482b73cdf6b5dddaf9bac614ff5.jpg20250606_072630.thumb.jpg.06baca46da4af7430e7884c7a4d5fd2d.jpgin the pictures as they are orange and I will end up with red. 

  • Like 1
Posted

Anyone have any ideas on how to get this back to red? the "5.3" was red and now its so faded its almost silver. 

0.thumb.jpg.5c779bab455ec4fa7e0c04c090203b2e.jpg

Posted
2 hours ago, bluemonstercali said:

Anyone have any ideas on how to get this back to red? the "5.3" was red and now its so faded its almost silver. 

0.thumb.jpg.5c779bab455ec4fa7e0c04c090203b2e.jpg

See the first post if they are indented. 

  • 3 weeks later...
Posted
On 5/24/2025 at 7:01 PM, Jus Cruisin said:

My second 10 minute mod. Installed the jumper cables to run amber drl's. Screenshot_20250524_185412_Ring.thumb.jpg.5cd59219129c1c3a561395c4e2d4ba0d.jpg

Did you use the Venom Trucks kit?

Posted
24 minutes ago, Carver60 said:

Did you use the Venom Trucks kit?

Yes. I had it on my 2023 GMC and swapped it to the 2025. 

Posted

My next 10 minute mod is going to be the gen5diy kit to add a switch for the cargo lights in the bed.  One of the things I really miss from my F150.  $44 and it should be here by the weekend.

  • Thanks 1
  • 3 weeks later...
Posted

Bed light switch is in.  Kit was $46 from gen5diy.com and I picked up an $8 surface mount switch on Amazon.  

 

Might have taken a bit longer than 10 minutes but not too much longer :)

54687612945_b9a56419e7_b.jpg

  • Thanks 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
  • 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...