Jump to content

Recommended Posts

Posted
On 4/26/2020 at 8:15 PM, truck_newbie said:

Black denali grille installed with fog light bezel painted black. I wanted a black AT4 grille but there doesn't seem to be one available that supports the front camera. Anyways, i think it looks sharp.

 Deadpool would approve of the theme ?.

black_grille_1.thumb.jpg.ff62e1835fe1c7d7891ccddda0563a4d.jpg

black_grille_2.thumb.jpg.218b208d24019d7d66878bd7bf6efccf.jpg

black_grille_3.thumb.jpg.02f8f7f122b6803ab457cee1d981135c.jpg

Hey did you have to get the fog light bezel painted or did you buy it in gloss black

  • Like 1
Posted
17 hours ago, Gerstein1989 said:

Hey did you have to get the fog light bezel painted or did you buy it in gloss black

Got it painted gloss black. I was going to wrap it but the wrap experienced some shipping delays so ended up getting it painted. At the time of purchase, there weren't any aftermarket bezels available. Believe me, I already checked. If you don't need it done immediately, aftermarket bezels will probably show up at some point as they did for the grille. 

Posted
4 hours ago, truck_newbie said:

Got it painted gloss black. I was going to wrap it but the wrap experienced some shipping delays so ended up getting it painted. At the time of purchase, there weren't any aftermarket bezels available. Believe me, I already checked. If you don't need it done immediately, aftermarket bezels will probably show up at some point as they did for the grille. 

thanks. with the new grill has the angle of the camera changed at all. I noticed his higher up as opposed to the factory at4 grill

Posted
1 hour ago, Gerstein1989 said:

thanks. with the new grill has the angle of the camera changed at all. I noticed his higher up as opposed to the factory at4 grill

I haven't noticed any camera issues but i haven't really paid close attention to it. It seems to work fine, no distortion observed. 

Posted

Just got the shoes put on.

20x9 +1 offset. Wanted to stay conservative this time around. Had 10 wides with a -24 on 35's on my last truck and it was getting a bit annoying. Currently running the stock tires to get a bit of use out of them. I'll get some new rubber in the fall before the winter.

 

 

20200508_181010.jpg

Posted
1 hour ago, Trza said:

Just got the shoes put on.

20x9 +1 offset. Wanted to stay conservative this time around. Had 10 wides with a -24 on 35's on my last truck and it was getting a bit annoying. Currently running the stock tires to get a bit of use out of them. I'll get some new rubber in the fall before the winter.

 

 

20200508_181010.jpg

Very nice.  I’m looking at that exact wheel but don’t know if I should go +1 or +20.  Can you take down the side shots to see how far outside fender?  Thanks.

Posted (edited)
1 hour ago, Parb said:

Very nice.  I’m looking at that exact wheel but don’t know if I should go +1 or +20.  Can you take down the side shots to see how far outside fender?  Thanks.

Here you go. I would do the +1, there wouldn't be much of a difference from stock with the +20. There's a ton of room from the tire to the upper control arm. I could have easily went with the 20x10...but the offsets are a bit much in that width.

 

 

 

 

 

20200508_203641.jpg

Edited by Trza
Posted
1 hour ago, Trza said:

Here you go. I would do the +1, there wouldn't be much of a difference from stock with the +20. There's a ton of room from the tire to the upper control arm. I could have easily went with the 20x10...but the offsets are a bit much in that width.

 

 

 

 

 

20200508_203641.jpg

Very nice.  Thanks.  I think that would be perfect for me with some 33x11.50x20 ridge grapplers.

 

Posted
26 minutes ago, Parb said:

Very nice.  Thanks.  I think that would be perfect for me with some 33x11.50x20 ridge grapplers.

 

Are you leveled? Lifted? I've got a 2 inch level. Let me know how the truck rides with the Nitto's in that size. I am contemplating sizing up, but don't want to lose the comfortable ride.

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