Jump to content

Recommended Posts

Posted

With the harness from Gen5DIY, is it correct that you would need to manually turn on the fog lamps while on low beam in order that they fogs would be on when activating the high beam lights?

Posted

If anyone needs diodes i have 42 left over can send out to whoever needs some. PM your address, im taking a batch to the PO in a cpl hours 1pm (mountain). Anything after will be sent out on Monday

  • Like 1
  • 2 weeks later...
Posted (edited)

Does this work on 2016?

 

Anyone perform this on 2016?

 

We're the cable colors/locations different?

 

And issues with the BCM or electrical?

Edited by SierraMyst
Posted

I literally just created an account to thank you all for the help. I can't even describe how easy this was to do... I have some of those smz vled headlights on back order so I'll post an updated picture then, but this is how it looks now... And I dig it

post-160038-0-59245000-1467795682_thumb.jpg

post-160038-0-59245000-1467795682_thumb.jpg

post-160038-0-59245000-1467795682_thumb.jpg

post-160038-0-59245000-1467795682_thumb.jpg

  • Like 1
Posted

Does this work on 2016?

 

Anyone perform this on 2016?

 

We're the cable colors/locations different?

 

And issues with the BCM or electrical?

 

I just did the 10-22 on my 2016 Silverado LT and it works perfectly. The fog light wire at pin 10 was brown and the parking light wire at pin 22 was blue. The locations are exactly the same as previously mentioned in this thread. As far as the issues with the BCM, I would remove the diode whenever having the truck at the dealership to avoid any complications that people were having.

  • Like 3
  • 3 weeks later...
Posted (edited)

Does this work on 2016?

 

Anyone perform this on 2016?

 

We're the cable colors/locations different?

 

And issues with the BCM or electrical?

Edited by stealthhtm
Posted

cant get the damn thing in the #10 slot!! I bent 5-6 trying. maybe the diodes im using suck. anyone got a link to ones that worked?

Posted

cant get the damn thing in the #10 slot!! I bent 5-6 trying. maybe the diodes im using suck. anyone got a link to ones that worked?

So did you get it to work?

Posted

unfortunately not

I read one post where the person used some wire cutters on the diode and cut the wire on an angle which put sort of a pointed end on the wire which made it easier to insert into the plug.

  • Like 1
Posted

You guys having difficulty inserting the diode may want to try sharpening the lead with a file or snipping it on a steep angle like mentioned above. Also, try moving around the socket/pin to another side. These sockets/pins can be pulled over to one side or another. Another thing to look at is the gauge (diameter) of the lead on the diode. Some are smaller than others. I don't think the diode size is critical in our application. Buy a smaller one.

  • Like 2
  • 3 weeks later...
Posted

I have been performing this mod since whenever fog lights started going off when you turned on the high beams.

 

I would like to say that I was the originator of this mod as I used to sell diodes with instructions at local car and truck meets, swap meets and over the counter at my parts counterman job.

 

It's good to see someone started posting this online - it's probably one of the coolest mods you can do to a Chevy Truck.

Posted

I have been performing this mod since whenever fog lights started going off when you turned on the high beams.

 

I would like to say that I was the originator of this mod as I used to sell diodes with instructions at local car and truck meets, swap meets and over the counter at my parts counterman job.

 

It's good to see someone started posting this online - it's probably one of the coolest mods you can do to a Chevy Truck.

can this be done with a resistor instead of a diode? used all my diodes and have a bunch of resistors lying around

Posted (edited)

can this be done with a resistor instead of a diode? used all my diodes and have a bunch of resistors lying around

NO!

 

Think of a resistor as a flow restrictor orifice and a diode as a one way check valve.

Edited by spurshot
  • 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

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • Paid $2.72 for E85 today.
    • 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
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...