Jump to content

Recommended Posts

Posted

I put on the one without the lights. If it starts to come off I'll have to replace it with the lighted on.

 

Are those on all the time or only when the parking lights are on?

 

Sent from my Pixel 2 using Tapatalk

 

 

 

 

Posted (edited)
6 hours ago, ShamrockShooter said:

I put on the one without the lights. If it starts to come off I'll have to replace it with the lighted on.

 

Are those on all the time or only when the parking lights are on?

 

Sent from my Pixel 2 using Tapatalk

 

 

 

 

Right now it’s only with the parking lights on or when I put the fog lights on as well. You can wire to always be on if you connect to one of the yellow wires if you look back to my wiring picture. 
Just be careful about local laws if you choose always on. Though, some states require amber clearance lights for vehicles over 80 inches wide and the 2019 1500 just happens to come in at 81.2, so you should be safe. 

Edited by Suprmario
Posted
On 7/12/2019 at 7:27 PM, Suprmario said:

Went for it myself....might not be for everyone, but I like it..

 

548DCBE5-438E-4C80-85A6-0FD7F939E603.jpeg

71F5E45C-B3F6-4DE0-85FC-BB00B422F372.jpeg

Got a side picture?  how much does it stick up?   Thanks

  • Like 1
Posted
1 hour ago, Suprmario said:

Not much...side shot and view from the cab...barely visible

C26470C9-00D3-4BB7-BF8E-681F43BC0E57.jpeg

432D6067-F6AE-4F8F-AD30-B3AF7CB5D3FC.jpeg

Thanks.  I like it... 

  • 1 month later...
Posted

Just put mind on my Trail Boss. People that look at it says it looks like factory installed product. The wires were a little tight. Thanks for the post on the colors of wires. That saved me some time.

Posted
8 hours ago, Eddie Duffie said:

Just put mind on my Trail Boss. People that look at it says it looks like factory installed product. The wires were a little tight. Thanks for the post on the colors of wires. That saved me some time.

Glad to hear the pics were useful. A lot of people online tell me it’s just copying the raptor, but this looks so slick coming the road when you see it lit up in person and I have come across other 19 Silverado owners who ordered one right after seeing mine. 

  • 5 months later...
Posted

Sorry to revive an old topic, but was thinking about ordering one and had a question. As wired into the parking lights, these will not be on at night when headlights are on? Are they too bright to run at night?

Posted

They will be on at night anytime you put your fog lights on.. Some other ways to wire them so they can be on 100% of the time... I bought my about 1 month ago and still need to install it on my 2020 TB..

Posted

How are they holding up to snow and ice ?  Water and ice cascade right down the hood, I’d think you’d get a bunch of ice underneath that thing.   I like the lights tho, was thinking of placing some in the grill till I saw this.

i know some people are adverse to more lights, but I’m all for additional visibility especially in bad weather.  

Posted

See, I don’t mind the looks but AVS missed it on this one. It looks like there is plenty of room to add white lights in there as well. If they had that available as a lightbar of sorts plus the marker lights I would go for it.

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

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • 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
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...