Jump to content

Recommended Posts

Posted (edited)

I wanted to start a new thread. I have searched the internet over and over. I have not been successful in finding a build that is close to what I am doing. I have a bunch of goodies for the 2021 Silverado 1500 RST 3.0 Diesel setting in my garage. I am starting my build today however I wanted a start-to-finish post on here to help others that might be thinking the same thing. 
 

My shopping list: (so far) 

 

RC 3.5-inch lift kit (Front strut spacers and Rear N3 shocks) 

RC Air spring kit 

RC EXO winch mount

RC 12000-lb Synthetic rope Pro Series winch 

RC LED grille light kit 

 

RDS Transfer tank 55 gallon 

Armordillo CR1 Tire Carrier

Bed Fender well toolbox (Undercover brand) 

GM OEM Upfitter switches 

 

N-FAB Wheel-to-wheel running boards 


Fuel Flame 20x10 -18 offset 

Nitto Trail grappler 35x12.50

 

Black badges 

20% window tint side (this was done by a shop) 

Front window tinter 50% all the way with a 5% brow on the top windshield. 

 

I think I have this all correct. I am starting my build today and since I am doing this all on my own, for the install, I won't have time to do a step-by-step install. Again, I wanted people to see a build that can be done on your own. I am not a mechanic but your everyday guy. You can do this too. 

 

I forgot to take a picture before I changed badges and tinted windows however here is a photo of my identical truck before I started. This will take me about two to three weeks to complete. So stay tuned and I will add pics as I go along. 

 

Stock truck .jpg

Edited by RST from TN
correction of description
  • Like 1
Posted (edited)

Alright, day 4 of my slow build... Today I have finished the NFABS, 3.5 RC lift, and the Airbags RC are installed as well. Not pictured is the wheel well toolbox, it is an Undercover brand BTW, with the new locks to keep it from being stolen. Badges are replaced from chrome to black along with the windows that have been tinted in addition to the front windshield with 50% all the way down and 5% brow across the top of the glass. 

 

Waiting on the winch mount from RC to come in which has now pushed it back to 7/14/2022 according to my order status. 

 

This weekend I am hoping my upfitter switches come in so that I can install the grille lights as well as the switches. 

 

Wheels and tires should be here by the end of the week. Right now, my truck has definitely missed leg day at the gym. 

Little done .jpg

Edited by RST from TN
correction of description
Posted
14 hours ago, RST from TN said:

Alright, day 4 of my slow build... Today I have finished the NFABS, 3.5 RC lift, and the Airbags RC are installed as well. Not pictured is the wheel well toolbox, it is an Undercover brand BTW, with the new locks to keep it from being stolen. Badges are replaced from chrome to black along with the windows that have been tinted in addition to the front windshield with 50% all the way down and 5% brow across the top of the glass. 

 

Waiting on the winch mount from RC to come in which has now pushed it back to 7/14/2022 according to my order status. 

 

This weekend I am hoping my upfitter switches come in so that I can install the grille lights as well as the switches. 

 

Wheels and tires should be here by the end of the week. Right now, my truck has definitely missed leg day at the gym. 

Little done .jpg

 

Can you post a measurement for the height of your fenders? I am looking to lift my truck a little more and was curious if this is higher than I already have.

Posted
On 7/6/2022 at 12:00 PM, mikewohlwend said:

 

Can you post a measurement for the height of your fenders? I am looking to lift my truck a little more and was curious if this is higher than I already have.

I plan on doing some more work today. I will get this for you. 

Posted
On 7/6/2022 at 12:00 PM, mikewohlwend said:

 

Can you post a measurement for the height of your fenders? I am looking to lift my truck a little more and was curious if this is higher than I already have.

I measured a little bit ago 41 in the front and 41.5 in rear. 

 

Posted
20 hours ago, RST from TN said:

I measured a little bit ago 41 in the front and 41.5 in rear. 

 

 

Thank you.  That's the same height my Trail Boss is sitting right now.

Posted
3 hours ago, mikewohlwend said:

 

Thank you.  That's the same height my Trail Boss is sitting right now.

You have already installed more lift than the factory, correct? 

Posted

Been a bit since I have updated. I currently have been doing work underneath the vehicle. Airbags, compressor, aux fuel tank connection etc...

 

Today I am putting in the Rough Country grill lights. 

Posted
On 7/10/2022 at 6:40 PM, RST from TN said:

I measured a little bit ago 41 in the front and 41.5 in rear. 

 

Measured from the ground or the bottom of the wheel?

Posted
On 7/17/2022 at 6:32 PM, Byrds8 said:

Measured from the ground or the bottom of the wheel?

From the ground

 

Posted (edited)

I am going to post this in three pics... 

3.5 Rough Country lift 

Fuel Vapor 20X10 -18MM offset 

Nitto Ridge Grappler 35x12.50 

 

Hard to see at first glance but the RC Grille lights are in also... Coming along. 

Lift .jpg

Edited by RST from TN
Posted (edited)

I cannot get this picture to post vertical. Sorry about that. 

 

Fuel Vapor 20X10 -18MM offset 

Nitto Ridge Grappler 35x12.50 

 

Side view .jpg

Edited by RST from TN
Posted

Again will not post vertical. 

 

Fuel Vapor 20X10 -18MM offset 

Nitto Ridge Grappler 35x12.50 

Tire size .jpg

Posted (edited)

I rubbed very little however it was enough to keep me from turning tight. When I got home, I took 30 minutes per side and removed the carpet plate, cut down the mudflap, and used a zip tie to hold back the carpet. Zero rubbing after that. 

Edited by RST from TN
correction of description

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,770
    Total Members
    8,960
    Most Online
    Paul8556
    Newest Member
    Paul8556
    Joined
  • Who's Online   4 Members, 0 Anonymous, 592 Guests (See full list)

  • Latest Articles

  • Posts

    • I hope to high heaven this is wrong. My Chevy farm trucks frame is lasting way longer than a newer Nissan Titan XD I got for a steal, and it only pulls trailers. A decade younger and it's frame is already way rustier than the waxed Chevy I drive across longs and ditches. Also, hasn't Ford been having tones of troubles with rusted frames? 
    • Batteries don’t always show signs of a few years ago my vehicle started fine in the morning and took me to work. After work the battery was completely dead and I needed a jump. No, I didn’t leave anything on and the battery was only a couple months old. It was replaced under warranty. 
    • AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • If his battery was that bad I would think it would have been showing signs before this that were ignored. Stinks that it happened the way it did in rush hour traffic, but this seems like a pretty fringe scenario. I don't mind it that bad and never turn it off. The only slight annoyance for me is the slight delay between brake to gas, but I have gotten used to it and figure if it can save a little gas why not.
    • That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...