Jump to content

Fog lights not working

Jricharc
 Share

Recommended Posts

Jricharc Enthusiast

Jricharc

Posted
Posted

So I’ve had my truck almost three weeks now and since it’s getting dark earlier now I noticed my fog lights aren’t working at all.  The light on the dash comes on but they don’t turn on.  When I first bought it I noticed that one of the leds next the third brake lights was out, these wouldn’t be correlated in any way would they?  I’m going to make an appointment to have it looked at tomorrow.  

Jricharc Enthusiast

Jricharc

Posted
  • Author
Posted

No they were factory installed, and I haven’t checked that yet. I will take a look today.

Jricharc Enthusiast

Jricharc

Posted
  • Author
Posted

So it's at the dealership and they told me the switch is sending power but the lights arent getting power so they are thinking it's the BCM or something between the switch and the lights. They are keeping it over night to see what they can figure out...

Jonnytc New Member

Jonnytc

Posted
Posted

Have almost the same issue as my custom trail boss has been in and out of the dealership over the past three months.  My situation is a little different, as my truck didn’t have fog light when I picked it up.  I put my fog lights on my custom thru the Chevy parts department (obviously with the parts they ordered) a few weeks after I owned it.  The majority of the time the indicator light comes on but the fog lights do not.  Luckily my dealer has been very accommodating but it is a hassle in general.  The fog lights turn on every once in a while but they are completely unreliable.  The truck is back at dealer now for the 4th time regarding this issue but due to the strike, they only recently received the Module and new fog light kit that they are going to replace everything and start over.  

Hopefully my truck is ready today or Monday but if I have any answer to this mystery I will post it here.   

Jricharc Enthusiast

Jricharc

Posted
  • Author
Posted

So they finally tracked down my issue, one of the pins somewhere in the bumper had backed out casing the issue. They reseated the pin and they are now functioning.  

  • 2 years later...
Jamrok123 New Member

Jamrok123

Posted
Posted

I have a 2021 trailboss custom. I had the dealership install their OEM foglights and program them. The foglights only work when you unlock the truck and the switch does nothing. Any ideas what the issue could be?

 

 

 

 

 

 

redwngr Senior Enthusiast

redwngr

Posted
Posted

If the BCM can command them 'on' with the unlock routine, then it would seem it's  not getting the 'on' request from the button/switch. 

 

Presumably the installer/programmer checked that they were working.

How have you had it?

 

Maybe switch is disconnected from harness?

Pin pushed out?

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

  • Latest Articles

  • Posts

    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

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

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...