Jump to content

Recommended Posts

Posted (edited)

What make is that bar Todd? Any specs? Looks like a spot configured beam for high speed driving?

I think I found seller from another member who got one. It is 32 inch, 13500 lms spot/flood combo. It was like $90. I replaced his switch with a halo switch. I have been real happy with it.

52172d0c5d749f3e087455bbc6af7413.jpg

 

Eyourlife 32" 13500LM Led Off Road Led Light Bar Flood/Spot Combo Beam- 3W Led-180W White by Eyourlife http://www.amazon.com/dp/B00D8RYHHE/ref=cm_sw_r_udp_awd_7e9oub0KW7MDA

 

Let me know if link doesn't work.

Edited by Toddfather
Posted

32 inch

32e27d5239d3cee6bb91771894fda8cf.jpgdd6730dc643bd91a397c944ac2b75a09.jpg

 

High beem and fogs 084f1fd3e38bdbcd8da29f289ce3fca3.jpg

Now with light bar

20c21e0c794873658da395b8b511bdd2.jpg

Can you snap some pictures during the day of the bar? Want to do this on mine. If you wouldn't mind posting a picture with the bar on and one with it off looking straight at the bar. Thanks!

Posted

c9351ffe1bb2a36835efc23a2ca5fd87.jpg

Thank you! Also how is it on distant shine? I already have LED pods for my fogs and a 20" bar that does pretty good for flood and decent for Spot. But I still don't have much distant light.

 

 

Sent from my iPad using Tapatalk

Posted

My distance is pretty good. I may aim it one notch higher though. Still puts light well ahead of me. I can see reflections a few 100 yards up.

  • Like 1
Posted

Here is an AC Auto 32" led light bar i got off amazon for 90$ that's turned out great behind my 2014 silverado ltz grill. There's not much of an opening in the grill space of the ltz like some of the other models but i was pleasantly surprised how much light it puts out. I have another light bar on the way and i might try to double stack another. Easy install. Just bolted right to the V frame and the light bar just rest against my grill. yCAaSEA.jpg

 

jM3d5jR.jpg

  • Like 2
Posted

Just read on another forum someone doing a wireless connector and using one of his home link buttons to turn on and off the led light bar

Posted

Just read on another forum someone doing a wireless connector and using one of his home link buttons to turn on and off the led light bar

Pls post a link to that. I wouldn't mind doing that if I set up a new bar and rewire my old bar to do the same. And would be nice for some AUX reverse lights

  • Like 1
Posted

Dang, I just drilled holes in my console for my switches last night. I should have checked up on this thread first, that remote would have been sweet.

Posted

Would it be possible to wire up the remote to another brand of light bar? Say a rigid industries one?

Posted (edited)

Someone with a 1500 needs to get that and see if it'll work! I don't see why not. But someone should try it. Wouldn't mind getting that with some spot lights.

 

EDIT:

 

Nevermind! They have one for the 2015 1500. So I'm sure it would carry over to the 2014 1500

 

http://trexbillet.com/cart/index.php?main_page=product_info&products_id=1961

Edited by Mike1220
  • 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

    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...