Jump to content

Foglights Auto On

gabbygenier
 Share

Recommended Posts

Lamby66 Enthusiast

Lamby66

Posted
Posted

The fog light switch is in fact a momentary contact switch which pulls the BCM fog light control to ground. I will ponder this later but I think this should not be too hard but might need two more relays or a flip-flop

 

Sent from my SM-G930V using Tapatalk

  • Replies 100
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

jimmyboy8301
jimmyboy8301

SMH    Sent from my iPhone using Tapatalk

duquephart
duquephart

Why would you want them to come on every time? Fog lights are intended for a specific use and, under normal circumstances, are seldom needed.

Sierra706
Sierra706

If you want to see any real visibility improvement, turn off your headlights and use only the fogs. They will project useful light without the blinding effect of the low or high beams. I've found that

Lamby66 Enthusiast

Lamby66

Posted
Posted

I think the big problem with this circuit (at least in my configuration) would be any toggle of the fog light switch would then tell the BCM the fog lights are on and disable the high beams. If I used a flip flop the fog lights would not always be in sync with the BCM and would cause issues with the high beams.

 

If the op explains better what he wants I can make this but ideally the fog light control would need to be removed from the BCM entirely (cut wire) and is NOT something I am willing to do

 

Sent from my SM-G930V using Tapatalk

gabbygenier Enthusiast

gabbygenier

Posted
  • Author
Posted

Hey Lamby

 

Sorry, been a busy week and didn't have time to investigate the fog light switch but looks like you've already figured it out.

 

What I'm looking for is for the fog lights to turn on when the lights come on, so the low beams, but also be able to turn them off if i want to. Essentially the simple diode would work but then i can't turn the fogs off if i want to

 

I'm not worried about the fog lights being on or off with the high beams so that part isn't a must if its too hard to do.

arcasey Enthusiast

arcasey

Posted
Posted

Unless I'm mistaken, you can do the diode trick to have the fog lights on with high beams. The circuit that gets controlled with the fog light switch would need to break the fog light circuit down stream from the diode and the switch in order to have control of the fog lights and still maintain auto on.

 

Lamby, would it actually cause problems with the BCM if the fog lights are out of sync? The high beam switch should work no matter what state the fog lights are in because all it should control is the head lights. The BCM is only disabling the fog lights based on the Head light state (high or low beam). Then, if a user wants the fog lights to run with the high beams then all they need to do is the diode trick.

 

At least that's my line of thinking and I am by no means an expert.

Coby7 Senior Enthusiast

Coby7

Posted
Posted (edited)

 

What I'm looking for is for the fog lights to turn on when the lights come on, so the low beams, but also be able to turn them off if i want to. Essentially the simple diode would work but then i can't turn the fogs off if i want to

 

 

Why would you need to turn them off once they're on? I did the simple diodes to low beam and DRLs and I'm happy with that, never feel the need to turn them off. They still turn ''OFF'' with high beams though.

Edited by Coby7
gabbygenier Enthusiast

gabbygenier

Posted
  • Author
Posted

Why would you need to turn them off once they're on? I did the simple diodes to low beam and DRLs and I'm happy with that, never feel the need to turn them off. They still turn ''OFF'' with high beams though.

Why not is the question?

 

I'd like to have the fog light switch still work as it should from factory.

 

Just my preference.

Lamby66 Enthusiast

Lamby66

Posted
Posted

I started to work on a concept that would then use a latching relay that would be triggered by the foglight button to kill the fog lights. The problem with my circuit so far is that it does not reset until the power removed... it might work as long as the lights and bcm are in "sequence".. I will have to ponder more.

 

Sent from my SM-G930V using Tapatalk

Lamby66 Enthusiast

Lamby66

Posted
Posted

I will have to test this, but not on my truck as mine is already modified as I see best, but I think this will work for what you want... if you don't care about the fog lights with the high beams it gets MUCH easier

 

.c9f93f14f483355f770637decbbac538.jpg

 

I will make a cleaner drawing in a little bit

 

Sent from my SM-G930V using Tapatalk

Lamby66 Enthusiast

Lamby66

Posted
Posted

Here is a drawing that makes more sense.

 

When you turn on your headlights, or auto headlights turn on, K1 will energize pulling the wiper to the normally open circuit tied to ground.

 

The output of K1 feeds the normally closed position of A side of K2 via a 1004 diode. (This normally closed location also is the point you tie the high beams is needed)

 

The wiper of K2 A feeds the foglight control relay (x5-pin 10) where a low would turn on the lights.

 

When you press the foglight button the first time you will then energize relay K2 connecting wiper B to the normally open circuit which is tied to ground. This completes a loop latching the relay to the energized position. Which will disconnect the A side wiper from the previously active K1... HOWEVER since X5 pin 10 is switched by BOTH the relay K2 AND the BCM, the low signal at X1 PIN 15 will make the BCM turn on the fog lights (and the dash icon which was off until this point).

 

Since K2 is latched it will not be de energized until the truck is turned off but is no longer needed. Each press of the fog light button after the first will then change the state of the fog lights via the BCM as designed by GM.

 

when the truck is restarted both relays are deenergized until they are needed again.

 

This "should" be exactly what you want.

 

Again I am not going to tie this into my BCM but it should work perfect based on the logic that I am already using for my circuit (just adds an interrupt circuit)

 

Sent from my SM-G930V using Tapatalk

Coby7 Senior Enthusiast

Coby7

Posted
Posted

Or maybe simpler just have a relay turn the fog lights on when either of them turn on and then disengage with an RC constant.

 

2017-03-28%2017.21.13_zps5ir5rrfg.jpg

Lamby66 Enthusiast

Lamby66

Posted
Posted

Coby, the low beam is a logic high and needs to be inverted. I am not sure what the tank circuit does in your drawing.

 

Sent from my SM-G930V using Tapatalk

Lamby66 Enthusiast

Lamby66

Posted
Posted

Ohhhh I see what you did there. The tank circuits bleeds down the relay so the momentary contact can trigger the output of the relay. Very nice. Is there a logic low low beam pulse somewhere in the BCM inputs?

 

Sent from my SM-G930V using Tapatalk

Lamby66 Enthusiast

Lamby66

Posted
Posted

Coby, I forgot.. if you do it your way it will disable the auto dimming high beam function (if equiped) the high beams will not automatically turn on if the BCM senses the fog lights are on. That is why I went the way I did.

 

Sent from my SM-G930V using Tapatalk

Coby7 Senior Enthusiast

Coby7

Posted
Posted (edited)

Didn't know he had auto dimming!!! My 11 has negative from BCM going to lows and DRL relay, so I will mind my own business on this one. I tried.

Edited by Coby7

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
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts

  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined

  • Who's Online   4 Members, 0 Anonymous, 2,121 Guests (See full list)

  • Latest Articles

  • Posts

    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      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
    • davester
      Replacement Radiator

      By davester · Posted

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