Jump to content

Recommended Posts

Posted

Curious if this inhibits the auto high beam...or does it function as it should except all the lights are on now?

Posted
8 minutes ago, mikeay said:

Curious if this inhibits the auto high beam...or does it function as it should except all the lights are on now?

As for Fogs/HIGHs, the intellibeam system works fine on my truck.  I know that if the fogs are ON with lows (manually), the intellibeam system will not work.  Have not seen anything from anyone that's done the Fogs/Lows mod.

  • Thanks 1
Posted
1 minute ago, Ravenkeeper said:

As for Fogs/HIGHs, the intellibeam system works fine on my truck.  I know that if the fogs are ON with lows (manually), the intellibeam system will not work.  Have not seen anything from anyone that's done the Fogs/Lows mod.

Thanks a lot for the info. That's exactly what I wanted to know.

  • 2 weeks later...
Posted (edited)

Thank you for all this information everyone!

 

Just wanted to share my experience with this mod:

 

Step 1:  I did the diode thing to make FOG and High beams on at same time (which was super easy and works like a champ) Thanks again to the original poster!

 

Because I also installed High powered xhp 70 CREE lights into my high beam and low beam housings I was having the typical DRL issues (headlight would turn off when put into drive) this also occurred randomly after installing canbus thingy as well (my guess is that these mechanisms are not 100 percent reliable). so I decided to make a more reliable setup, one that wouldn't have a possibility of turning my headlights off randomly with no way of getting them back on while I am already driving.

 

Step 2:  I re-routed my fog wires to the low beam housing

 

Step 3: I re-routed my low beam wires to the fog light housing

 

so my DRL are now my fogs (just aimed them up a little bit from where they are set from the factory for increased visibility during the day)

 

to turn on my low beams I just hit the fog button on the dash (results in lows and fogs being on)

flip the high beam switch on - and all 3 lights are on regardless if the lows were on before the flip or not.

flip the high beams off -results in the lights reverting back to whatever was on before the high beams were switched on 1. lows plus fogs or 2. just fogs ( now my DRL)

 

Sorry if this has already all been said have to admit I didn't read all 50 pages. 

 

 

This was done on a Canadian 2015 Silverado LT

 

 

Edited by jdirt
add truck model
  • 1 month later...
Posted

So... if work arounds aren't you're thing... you can do it the OEM way now ;)

 

 

  • 1 month later...
Posted

Hate to revive a thread that seems to have been covered thoroughly but I've got a problem. I feel like I've followed the previous posts exactly, diode correct way, right pins for the high beam fog as well as 3rd brake light with backup but neither work, attached is what I'm looking at, point out what's the problem? Thanks.

20190908_203423.jpg

Posted
18 hours ago, Florida_Dawg14 said:

Hate to revive a thread that seems to have been covered thoroughly but I've got a problem. I feel like I've followed the previous posts exactly, diode correct way, right pins for the high beam fog as well as 3rd brake light with backup but neither work, attached is what I'm looking at, point out what's the problem? Thanks.

20190908_203423.jpg

Your reverse/cargo jumper is correct for cargo lights on while in reverse.  Maybe push your leads in a little further?  What diodes did you use, 1N4004?

 

HOWEVER, your fogs on with HIGHs appears to be completely incorrect.  Your striped end it in BRN24, mine is in BRN18 (next row up), and I can't tell where the other end is pinned, but mine is in BRN10. 

 

The attached picture if from my '15 LTZ.  My '18 is similar, other than the third diode in the GREY block, because my '18 comes setup to have the puddle lights on when any of the doors are open.

3 BCM Mods.jpg

Posted
6 hours ago, Ravenkeeper said:

Your reverse/cargo jumper is correct for cargo lights on while in reverse.  Maybe push your leads in a little further?  What diodes did you use, 1N4004?

 

HOWEVER, your fogs on with HIGHs appears to be completely incorrect.  Your striped end it in BRN24, mine is in BRN18 (next row up), and I can't tell where the other end is pinned, but mine is in BRN10. 

 

The attached picture if from my '15 LTZ.  My '18 is similar, other than the third diode in the GREY block, because my '18 comes setup to have the puddle lights on when any of the doors are open.

3 BCM Mods.jpg

Yes I'm using the 1N4004. I corrected the fogs/highs but no dice replaced the diode too. Got the cargo/reverse working for just a min buttt then they went out again. I feel like the wire isn't getting a good connection in the pin, pushed as far as they'd go just doesn't feel "secure." Going to try them again tomorrow. Thanks again.

  • Like 1
  • Thanks 1
Posted
16 hours ago, Florida_Dawg14 said:

Yes I'm using the 1N4004. I corrected the fogs/highs but no dice replaced the diode too. Got the cargo/reverse working for just a min buttt then they went out again. I feel like the wire isn't getting a good connection in the pin, pushed as far as they'd go just doesn't feel "secure." Going to try them again tomorrow. Thanks again.

I took my smallest phillips jewelers screwdriver and pushed it in to make way for the diode leads, so that it was "easier" to push them in the needed length for good contact.

  • 4 weeks later...
Posted
On 7/25/2019 at 5:01 PM, GTPprix said:

So... if work arounds aren't you're thing... you can do it the OEM way now ?

 

 

What is the OEM way?

Posted
On 10/5/2019 at 4:34 AM, RickLB said:

What is the OEM way?

Pull your BCM out, send it off to be reprogrammed, sent back to you, and reinstall.

Posted
On 6/11/2019 at 10:10 PM, Ravenkeeper said:

As for Fogs/HIGHs, the intellibeam system works fine on my truck.  I know that if the fogs are ON with lows (manually), the intellibeam system will not work.  Have not seen anything from anyone that's done the Fogs/Lows mod.

 

I believe Gen5DIY has a harness for fog on anytime the lights are on.

  • 1 month later...
Posted
On 10/15/2019 at 9:09 PM, Megawolf said:

 

I believe Gen5DIY has a harness for fog on anytime the lights are on.

but.. that's a $100 harness and we're all talking about $0.95 diodes... so there's that..

 

 

 

..on a side note, why not just run a diode from the HIGH BEAMS to the LOW BEAMS so that when you turned the high beams on (and the BCM shuts off the low beams in the process) the BCM is overridden and keeps the LOWs on while the HIGHs are on.. (?)

Posted
2 hours ago, rbrjr1 said:

but.. that's a $100 harness and we're all talking about $0.95 diodes... so there's that..

 

 

 

..on a side note, why not just run a diode from the HIGH BEAMS to the LOW BEAMS so that when you turned the high beams on (and the BCM shuts off the low beams in the process) the BCM is overridden and keeps the LOWs on while the HIGHs are on.. (?)

On my '15 Silverado, the lows stayed ON with the highs, before the diode mod.

 

Pre-MOD:

228145401_HI-LOPre-Mod.thumb.png.0e87149714b6231c7e8b1cb33f44f309.png

 

Post-MOD:

346314891_HI-LOPost-Mod.thumb.png.6267ab7d6162d1b1b9ca415c4e8fb9b7.png

  • 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

    • 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.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...