Jump to content

Recommended Posts

Posted
I like the Z71. I been thinking about how to do that myself. How did you attach it? Got a better picture?
Thank you. It is just with the standard double sided tape that comes on the emblems. Fit perfectly between the grille bars and seems pretty secure with were the tape is contacting the grille.
75291faba0dfc75ea417a4736a43b3ea.jpg

Sent from my SAMSUNG-SM-G890A using Tapatalk

Posted
1 hour ago, Fix29 said:

Thank you. It is just with the standard double sided tape that comes on the emblems. Fit perfectly between the grille bars and seems pretty secure with were the tape is contacting the grille.
75291faba0dfc75ea417a4736a43b3ea.jpg

Sent from my SAMSUNG-SM-G890A using Tapatalk
 

Awesome! Thank you very much!

  • Like 1
Posted

Did the wireless charging mod to the indentation in the armrest. 

Just hope I remember the phone is sitting there before going into the console lol

 

Very simple mod and works great. 

  • Like 1
Posted

Hahaha I’ve done the James Bond ejector seat to my phone 2wice like that. It’s only happened at night tho. Haha


Sent from my iPhone using Tapatalk

  • Like 2
  • Haha 2
Posted

It wasn't today, but yesterday I swapped over from the OEM 17" rims on 255/70/17 General Grabber HTS  it came with

81232278_10114865756526603_8243867060958

 

 

to the OEM 18"  rims and some 255/7018 Bridgestone Dueler AT

81720326_10114913261052153_6781370171991

  • Like 2
Posted (edited)

I have my new heated steering wheel, I have  a part number of 23381964 for the new clock spring. I have a 2017 LTZ, does that part number seem correct? If not, what one do I need? My truck did not come stock with a heated steering wheel, I am doing the mod.

 

 

Edited by 6.2Midnight
Posted
On 12/28/2019 at 9:38 PM, doubeleive said:

not quite sure of the exact model it was installed by the previous owner, would there be a part number on it somewhere?

 

I don't believe so. The Competitor muffler is pretty short. Maybe 8-10" long. I would imagine the Progressive muffler is a bit larger. It's either really loud and aggressive(competitor) on the gas or it's fairly loud and not as aggressive sounding(progressive).

Posted
15 hours ago, HeySkippyDog said:

New Lund tri-fold tonneau. We'll see how it holds up.f324d2ea7885735227f758b80df1506d.jpg

Sent from my SM-J810F using Tapatalk
 

I have had the same Lund Genesis Elite tri-fold for about 5 years.  Bought it for my 09 Sierra and then moved it to my 17 Silverado and have had 0 issues with mine; absolutely love it..

Posted

Well I have been creeping on here long enough..... 

 

2017 CC SB Silverado LT 2WD.

 

Bought the truck back in July of 17.  

 

Mods:

20inch black and chrome replica wheels

Diode upgrade to BCM so that fogs come on anytime the parking lamps are on (can't remember the pins right off)

$200 6 inch running boards from Amazon

Removed rear lift blocks

Removed front lower valance

Replaced cargo and reverse bulbs with LED

Plasti-dipped all chrome badges to black

Lund Genesis Elite 95892 tonneau transferred from 09 Sierra. (Had to add some weather stripping to the front edge to get it sealed on the 17)

Carbon fiber vinyl applied to exterior bow ties

Truck 2019.jpg

  • Like 3
Posted
Well I have been creeping on here long enough..... 
 
2017 CC SB Silverado LT 2WD.
 
Bought the truck back in July of 17.  
 
Mods:
20inch black and chrome replica wheels
Diode upgrade to BCM so that fogs come on anytime the parking lamps are on (can't remember the pins right off)
$200 6 inch running boards from Amazon
Removed rear lift blocks
Removed front lower valance
Replaced cargo and reverse bulbs with LED
Plasti-dipped all chrome badges to black
Lund Genesis Elite 95892 tonneau transferred from 09 Sierra. (Had to add some weather stripping to the front edge to get it sealed on the 17)
Carbon fiber vinyl applied to exterior bow ties
1714685034_Truck2019.thumb.jpg.a137637a3af1558285bf2caa1f373fa7.jpg
I've been looking to see someone on here with the tahoe black chrome insert wheels. Looks fantastic man! Theyd be killer on a black LTZ with the chrome pack too. Much better than the all chrome 20s they come with factory.

Sent from my SM-N975U1 using Tapatalk

Posted
3 hours ago, cbrsilv15 said:

Hauled a bunch of drywall today. Ceilings suck....072433C3-65DE-4C5A-9D10-3EF319EC9034.thumb.jpeg.2edb90eb884b9a71c308162d27ca7d0b.jpeg

F05ED482-8D8F-4CE7-AB0D-CD3F3195B94D.jpeg

One of these days soon, I'll be doing something similar, redoing our laundry room, bottom 4' of one wall and the opposite side of the wall (in the hallway) are water wicked from a flood from an overflowing sink.

  • Like 1
Posted
18 hours ago, XtremeSPL said:

Well I have been creeping on here long enough..... 

 

2017 CC SB Silverado LT 2WD.

 

Bought the truck back in July of 17.  

 

Mods:

20inch black and chrome replica wheels

Diode upgrade to BCM so that fogs come on anytime the parking lamps are on (can't remember the pins right off)

$200 6 inch running boards from Amazon

Removed rear lift blocks

Removed front lower valance

Replaced cargo and reverse bulbs with LED

Plasti-dipped all chrome badges to black

Lund Genesis Elite 95892 tonneau transferred from 09 Sierra. (Had to add some weather stripping to the front edge to get it sealed on the 17)

Carbon fiber vinyl applied to exterior bow ties

Truck 2019.jpg

Are your tires stock size, and your only suspension mod the rear block removal? If so, could you post a straight on side view pic? I'm thinking about taking the block out of my 2016 Sierra. Even though I have 18's, the overall size is basically the same.

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

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