Jump to content

Foglights On With High Beams

Spurshot
 Share

Recommended Posts

  • Replies 796
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

Spurshot
Spurshot

2014 SIERRA SLT FOG LIGHTS WITH HIGH BEAM HEADLIGHTS MODIFICATION This mod will let you use the fog lights on low beam same as factory. On and off with the fog light button. When the fog ligh

Spurshot
Spurshot

This was on the Duramax forum. I believe it is for a GMT 900. But the principles are likely applicable to a K2. Use this information cautiously. ------------------------------------------------------

Spurshot
Spurshot

OK, After struggling thru the schematics and online mods of past models all evening, I figured it out. This is for a Sierra and should be the same for the Silverado. It involves pushing one Diode in

Posted Images

Amuro Enthusiast

Amuro

Posted
Posted

Thank you!

 

The diode that goes into Pin #22 (Dark blue) comes from Pin #10 (two slots below). Pin #10 (can't be seen) should he a Brown Solid wire.

 

 

Sent from my iPhone using Tapatalk

  • Like 2
pgamboa Senior Enthusiast

pgamboa

Posted
Posted (edited)

So it's #10-#22 regardless of the wire color right?

 

I would take EXTRA precautions if the wire color doesn't match. After reviewing the BCM Connector Pin for 2014-2017, I found some variances. Especially with 2014.

 

For Example: Looking at JUST the Brown X5 Connector between the years:

 

2014: Shows a 25-Pin Connector (2015-2017 Show a 26-Pin Connector)

Pin #10 - Shows a Brown Wire, Circuit 5077 - Low Reference (10 Series Except MEX)

Pin #18 - Shows a Tan Wire, Circuit 28 - Horn Relay Control (Except MEX)

Pin #22 - Shows "NOT USED"

 

It looks like for 2014, I cannot locate a Fog Lamp Relay Control circuit on this Brown Connector (X5) but it shows that there is one on the Black X4 Connector - Pin #11 - Dark Green/White Stripe: Circuit 1317 - Fog Lamp Relay Control.

 

2015: Shows a 26-Pin Connector:

Pin #10 - Shows a Brown/White Stripe Wire - Circuit 1317 - Fog Lamp Relay Control

Pin #18 - Shows a Brown/Violet Stripe Wire - Circuit 1969 - Headlamp High Beam Control

Pin #22 - Shows a Dark Blue Wire - Circuit 45 - Park Lamp Relay Control

 

2016: Shows a 26-Pin Connector:

Pin #10 - Shows a Brown Wire - Circuit 1317 - Fog Lamp Relay Control

Pin #18 - Shows a Brown/Violet Stripe Wire - Circuit 1969 - Headlamp High Beam Control

Pin #22 - Shows a Dark Blue Wire - Circuit 45 - Park Lamp Relay Control

 

2017: Shows a 26-Pin Connector:

Pin #10 - Shows a Brown Wire - Circuit 1317 - Fog Lamp Relay Control

Pin #18 - Shows a Brown/Violet Stripe Wire - Circuit 1969 - Headlamp High Beam Control

Pin #22 - Shows a Dark Blue Wire - Circuit 45 - Park Lamp Relay Control

 

So - If you are unsure, I would be double/triple checking before inserting a diode in the BCM.

Edited by pgamboa
  • Like 3
bndawgs Senior Enthusiast

bndawgs

Posted
Posted

Alright, now I'm curious. Let me go out and get a pic of my brown plug. I swore it was yellow yesterday. But I could also still be seeing red after the Cowboys blew it on Sunday. :mad:

  • Like 3
rzr New Member

rzr

Posted
Posted

I DID THE 10-18 OPTION WAS A BREEZE,I'AM NOT A MECHANIC,I BELIEVE IT'S ALL IN THE PREP WORK I FOUND ON THIS FORUM-USED EMERY CLOTH TO GET A NEEDLE SHARP POINT ON THE WIRE&PUT ELECTRICAL GREASE ON THE POINTS-PULLED THE THE COVER OFF THE BOX NEXT TO IT TO GET EXTRA WORKING ROOM-PULLED THE BROWN PLUG OUT TO HOLD IN YOUR HAND USE A SMALL 45 DEGREE BEND NEEDLE NOSE PLIERS ONE DIODE ONE TRY 15 MINUTES MAX.

  • Like 1
MonkeyMouth Enthusiast

MonkeyMouth

Posted
Posted

I DID THE 10-18 OPTION WAS A BREEZE,I'AM NOT A MECHANIC,I BELIEVE IT'S ALL IN THE PREP WORK I FOUND ON THIS FORUM-USED EMERY CLOTH TO GET A NEEDLE SHARP POINT ON THE WIRE&PUT ELECTRICAL GREASE ON THE POINTS-PULLED THE THE COVER OFF THE BOX NEXT TO IT TO GET EXTRA WORKING ROOM-PULLED THE BROWN PLUG OUT TO HOLD IN YOUR HAND USE A SMALL 45 DEGREE BEND NEEDLE NOSE PLIERS ONE DIODE ONE TRY 15 MINUTES MAX.

 

WHY ARE WE YELLING :confused:

  • Haha 1
Ricks Munn Enthusiast

Ricks Munn

Posted
Posted (edited)

Just did the 10-18 jump to run my fogs with my highs and I also did the 26brown to 26pink jump to tie my cargo lights into my reverse lights so they come on when in reverse or when the vehicle is unlocked with the key fob. Probably shouldn't have bought 100 diodes though.

IMG 0564

IMG 0566

IMG 0568

Edited by Ricks Munn
  • Like 2
pgamboa Senior Enthusiast

pgamboa

Posted
Posted

Just did the 10-18 jump to run my fogs with my highs and I also did the 26brown to 26pink jump to tie my cargo lights into my reverse lights so they come on when in reverse or when the vehicle is unlocked with the key fob. Probably shouldn't have bought 100 diodes though.

In the earlier posts of this thread, someone started a chain and paid it forward. Basically, using the diodes he needed, then mailing the rest to another member. That member would use what he needed then paid it forward. It was really cool and how I got a couple.

 

 

Sent from my iPhone using Tapatalk

  • Like 2
paauto Enthusiast

paauto

Posted
Posted

Newbe here and I'm looking to do the 10-18 jump for the fogs and the 26-26 for the reverse lights. I've seen the pictures of both but for the fogs I'm confused. I thought the stripe on a diode was to go toward the flow of current - which would be the fog light (10) wire. Let me know. Thanks.

  • Like 1
pgamboa Senior Enthusiast

pgamboa

Posted
Posted (edited)

Newbe here and I'm looking to do the 10-18 jump for the fogs and the 26-26 for the reverse lights. I've seen the pictures of both but for the fogs I'm confused. I thought the stripe on a diode was to go toward the flow of current - which would be the fog light (10) wire. Let me know. Thanks.

I said the same thing when I started learning more about diodes and how the flow of current is one way, then looking at the pics, I had the same questions. Since it works as intended, they are left that way. I was gonna post the same question in hopes of some electrical engineers can explain. I also learned that the circuits we are jumping are switched ground circuits and not actual positive supply voltage.

 

 

Sent from my iPhone using Tapatalk

Edited by pgamboa
  • Like 1
paauto Enthusiast

paauto

Posted
Posted

Thanks PGamboa - will hook em up this weekend as per the pics in forum. Looking forward to it.

  • Like 1
Grjfer Enthusiast

Grjfer

Posted
Posted

I did the 26/26 jumper with a piece of thermostat wire. Working fine so far.

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