Jump to content

Recommended Posts

Posted

I did these a few weeks back ...

22in OEM Caddy Wheels and black out the gold Bowties on the center caps

rear clearance lamps

TonnoPro Hardfold Cover

GM Splash Guards color matched

Have a link to those rear lights?

 

 

Sent from my iPhone using Tapatalk

  • Like 1
Posted

You must have the non-GM rear floor liner. Lol. I'm getting more and more turned off by the GM liners I have. Like the dual USB add-on. Also like that it's 2amp output. Where did you source it from?

 

 

Sent from my iPhone using Tapatalk

Thanks. Got it from wish.com. It's the Husky liner, love how it goes up against the console like that.

 

Sent from my SM-G930V using Tapatalk

Posted

finally got to herculine the pocket flares i bought last year and install them. Once installed the stance was way to skinny so I went and got 2 inch spacers from rough country and installed. Next step, tomorrow pulling the front bumper valence / wind thing off.

IMG 3591

IMG 3590

IMG 3589


i think she looks like a 90s R/C truck or a matchbox truck now. LOVE IT. Especially with the Add a leaf making me not level anymore!

Posted

i love mine.. sure cleans up that engine compartment!.. plus sounds nice

Sounds great. When you stab the long skinny pedal you can definitely hear it sucking air.

  • Like 1
Posted

finally got to herculine the pocket flares i bought last year and install them. Once installed the stance was way to skinny so I went and got 2 inch spacers from rough country and installed. Next step, tomorrow pulling the front bumper valence / wind thing off.

 

 

 

 

i think she looks like a 90s R/C truck or a matchbox truck now. LOVE IT. Especially with the Add a leaf making me not level anymore!

If those spacers are aluminum I'd be worry about them breaking.

 

Sent from my SM-G930V using Tapatalk

Posted

Not today but a couple days ago, someone failed to stop and pulled out right in front of me going 50 mph. So much for a nice new truck.

 

61BA864F-89B9-4EE3-A081-359939E60281_zps

Posted

Not today but a couple days ago, someone failed to stop and pulled out right in front of me going 50 mph. So much for a nice new truck.

 

61BA864F-89B9-4EE3-A081-359939E60281_zps

Where is the thumb's down button. That sucks. Sorry to hear that!

 

 

Sent from my iPhone using Tapatalk

Posted

Not today but a couple days ago, someone failed to stop and pulled out right in front of me going 50 mph. So much for a nice new truck.

 

61BA864F-89B9-4EE3-A081-359939E60281_zps

Damn that sucks! If it's not totaled go after anticipated depreciation so you don't lose your ass in value.

 

Sent from my SM-G930V using Tapatalk

  • Like 2
Posted (edited)

Have a link to those rear lights?

Sent from my iPhone using Tapatalk

Here you go..its a OEM part, I like to use them when possiable. GM part # 15248604 ...picked it new up off eBay.

post-164772-0-91604600-1487954622_thumb.png

post-164772-0-91604600-1487954622_thumb.png

post-164772-0-91604600-1487954622_thumb.png

post-164772-0-91604600-1487954622_thumb.png

Edited by Bmz72
  • Like 1
Posted

Not today but a couple days ago, someone failed to stop and pulled out right in front of me going 50 mph. So much for a nice new truck. 61BA864F-89B9-4EE3-A081-359939E60281_zps

Sorry man!

Posted

Nice! Did you install the mud guards yourself? I am looking to add some and torn between Weathertech, Husky, and color matched GM ones.

Sent from my iPhone using Tapatalk

I was torn also, but I think the fit and look on the GM ones are much cleaner looking. I saw some post of guys complaining of rub/wear marks where dirt builds up. So I mocked the mounting area and then installed some 3m paint film where ever they might touch. Skipped the nutsert, and used double sided tape and 1 screw at the top after resealing the hole with touch up. They are going no where!

  • Like 1
Posted

Did this after work today. Added the dual USB plug on the left, tapped into the factory plug on the right. Panel popped off with a gentle but firm pull. Took all of 20 minutes. Don't know why it didn't come like this from the factory...98ed154aee2210df943e04f8bb317301.jpg61a3db1877dc3a7af3f66ef06f335a5f.jpg

Sent from my SM-G930V using Tapatalk

Hey is there any other usable wiring/power behind that panel? I been thinking of adding this to give my son usb's and installing rear heated seat grids . Just trying to decide what to do with the extra hvac knobs ...maybe lighting controls or something ?

It's from a Tahoe/Yukon and they have the harness also.

post-164772-0-29203300-1487956115_thumb.png

post-164772-0-29203300-1487956115_thumb.png

post-164772-0-29203300-1487956115_thumb.png

post-164772-0-29203300-1487956115_thumb.png

Posted

Hey is there any other usable wiring/power behind that panel? I been thinking of adding this to give my son usb's and installing rear heated seat grids . Just trying to decide what to do with the extra hvac knobs ...maybe lighting controls or something ?

It's from a Tahoe/Yukon and they have the harness also.

That one looks different, not 100% sure it would fit. The only other harness I saw was the one going up into the console itself. I didn't check those wires though.

 

Sent from my SM-G930V using Tapatalk

  • 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

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