Jump to content

Recommended Posts

Posted (edited)

I guess diode must not have been making contact. Works great now took me a few tries and a few bent up diodes but I got it. Also diode placement is the same on 2018 jumped 10 and 18.

 

Thanks guys.:thumbs:

Edited by 2018deepocean
  • Like 1
  • 1 month later...
Posted

Looking for some help, tried searching this thread but search doesn't do well with short search terms (like DRL).

 

I have a 2018 Sierra with LED headlights, if that matters.  I want to have my fogs on all the time, so when DRLs are on, when parking lights are on, and when both low and high beams are on.  I did the BRN10-BRN22 diode, so I have everything but when DRLs are on.  I was looking at the pinout and it looks like I can go to pin 23 (out of park)?  I assume that would turn the fogs on when the vehicle is on and out of park?  Does that work, is there a better option?  I was also thinking pin 7 (right front DRL control), but would that turn the fog lights off when I turn my right turn signal on?

  • 2 weeks later...
Posted

Hey guys - recently bought a 2016 Sierra Denali and joined the forum. Stumbled upon this thread while clicking around. I always gain so much from these forums, so I thought I'd give back in my first post. Here is a simple solution I made to have the fog lights automatically turn on with the day time running lights - did this with my previous truck as well (2008 Cadillac Escalade). I bought a diode and used some 14 gauge wire I had laying around. I wrapped 14 gauge wire to each end of the diode and sealed it with marine grade shrink wrap (waterproof). I then got into the engine bay fuse box and pulled the fuses for the fog lights (#49) and day time running lights (#28 or #29 - can be either, only need one). When I put the fuses back in I wedged the wire in one of the slots for the fuse connector, one end of the diode/wire goes in the fog light fuse and the other goes in the DRL fuse. Keep in mind the diode is directional (only allows current one way), so if it doesn't work at first just flip the wire around. Now anytime your DRL's are on, the fog lights will automatically come on. No need to push the fog light button. The fog lights also stay on when you turn on your brights. I attached a photo of my set up, it was taken standing over the driver side fender looking at the fuse box. Ask any questions if you got em!

2016 Sierra 1500 Fog Light Mod Diagram.JPG

Posted
On 7/28/2018 at 5:38 PM, 02SOMWS6 said:

Looking for some help, tried searching this thread but search doesn't do well with short search terms (like DRL).

 

I have a 2018 Sierra with LED headlights, if that matters.  I want to have my fogs on all the time, so when DRLs are on, when parking lights are on, and when both low and high beams are on.  I did the BRN10-BRN22 diode, so I have everything but when DRLs are on.  I was looking at the pinout and it looks like I can go to pin 23 (out of park)?  I assume that would turn the fogs on when the vehicle is on and out of park?  Does that work, is there a better option?  I was also thinking pin 7 (right front DRL control), but would that turn the fog lights off when I turn my right turn signal on?

Look at my previous post, I think this takes care of your issue.

  • 2 weeks later...
Posted

Did this mod today, chose to do the 10/22 option. Really like it, can still turn on fogs prior to auto headlights activating, but if i start the truck at night the fogs  come on with the auto headlights and stay on with highbeams.

Posted
13 hours ago, Speedy308 said:

Did this mod today, chose to do the 10/22 option. Really like it, can still turn on fogs prior to auto headlights activating, but if i start the truck at night the fogs  come on with the auto headlights and stay on with highbeams.

were did you get the diode from ???? Thanks

  • Like 1
Posted
were did you get the diode from ???? Thanks

You can get them from Amazon. 1N4004


Sent from my iPhone using Tapatalk
Posted
37 minutes ago, pgamboa said:


You can get them from Amazon. 1N4004


Sent from my iPhone using Tapatalk

Thank You Phil .

Posted
were did you get the diode from ???? Thanks


Yup off amazon. Have 98 left over.


Sent from my iPhone using Tapatalk
Posted
On 8/16/2018 at 12:36 AM, Speedy308 said:

Did this mod today, chose to do the 10/22 option. Really like it, can still turn on fogs prior to auto headlights activating, but if i start the truck at night the fogs  come on with the auto headlights and stay on with highbeams.

I think you're doing what I wan to do.  Fogs do not come on with DRL, come on with headlights, stay on with high beams?  Correct?

  • Like 2
Posted
I think you're doing what I wan to do.  Fogs do not come on with DRL, come on with headlights, stay on with high beams?  Correct?

Yep. This is the intended operation here.


Sent from my iPhone using Tapatalk
  • Like 2
Posted
9 minutes ago, Darmichar said:

I think you're doing what I wan to do.  Fogs do not come on with DRL, come on with headlights, stay on with high beams?  Correct?

 Correct, come on with remote start as well. 

 

  • Like 1
Posted (edited)
6 minutes ago, pgamboa said:


Yep. This is the intended operation here.


Sent from my iPhone using Tapatalk

I was just starting to wade through the 45 pages, perhaps you can save me the trouble.  Which pin does the stripe on the diode 'face', 10 or 22?

 

*Edit* ...and I'm assuming it's still the same on an '18?  Just traded my '14 in last night.

Edited by Darmichar
  • Like 3

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