Jump to content

Recommended Posts

Posted

 

 

no need to actually remove anything on the harness, but it does help to unplug the actual connector to make it easier to work with. Once you have it in a spot you can see better, all you have to do is jump the two wires with the diode.

 

Also on that note

 

12 diodes left....

 

What kind of fog lights are you running? I think I'll change out the bulbs in my fogs.

Posted

 

What kind of fog lights are you running? I think I'll change out the bulbs in my fogs.

 

stock bulbs right now

Posted

Just a heads up i replaced my fog bulbs with LEDs, the static in the radio when lights were on is crazy. i had my truck in the dealer for the radio issue and they removed my LEDs and put in factory bulbs. static went away (but the reception issue is still there) . Dealer said the problem was solved. Sent an email service manager 2 days later telling him the reception issue is still present.

Posted

My Baja Designs SII LED lights don't cause any additional static on my XM, AM or FM.

Posted

Did this mod yesterday and it worked like a charm. Very clever. Thanks for sharing!

 

Sent from my SCH-I545 using Tapatalk

Posted

Guys-

Been ready all of these replys, and was thinking about the following.

 

What about instead of running 2 diodes, (one to high beam, one to low beam), instead you run one to the parking lights. That away when those turn on the fog lights would then turn on. Thus not needing the 2nd diode, or having to turn them on ever again. Let me know if I am off base as I will be trying to complete this mod this weekend.

  • Like 1
Posted

Guys-

Been ready all of these replys, and was thinking about the following.

 

What about instead of running 2 diodes, (one to high beam, one to low beam), instead you run one to the parking lights. That away when those turn on the fog lights would then turn on. Thus not needing the 2nd diode, or having to turn them on ever again. Let me know if I am off base as I will be trying to complete this mod this weekend.

 

The original mod in this thread has one diode from the high beam signal (-) to the fog light signal (-). Not two diodes. But, clearly, you can do all kinds of circuits with the concept as long as you understand the OEM logic and you ensure you're hooking like signals (not positive to negative, etc.). Just read the schematics.

Posted

OK, well did the modification tonight. Instead of going to the High Beam, I went and ran my Diode into the 22 slot, which is the parking light signal. I tried the lights and everything functioned perfect. Lights on with Low Beams, High Beams, and when switched to parking lights they stayed on as well. All I can say is best 0.50 cent mod ever!!!!

  • Like 6
Posted

OK, well did the modification tonight. Instead of going to the High Beam, I went and ran my Diode into the 22 slot, which is the parking light signal. I tried the lights and everything functioned perfect. Lights on with Low Beams, High Beams, and when switched to parking lights they stayed on as well. All I can say is best 0.50 cent mod ever!!!!

That's great. My particular goal was to use the fog circuit to tie in my LED wide beam driving lights and be able to use them with high or low beam. I cannot have them on anytime the low beam is on since they are too bright for oncoming traffic. I got that done and ended up with the fog circuit being lit anytime the high beams are on and the fog circuit shuts off when dimming the high beams. Very slick when an oncoming car pops over a rise in road and you need to dim all the lights.

Posted

Out of curiosity. I wonder what would happen if the left front and right from drl supplied vtage pins were removed from the connector? Would someone lose the pwm signal going to there drls? In my cAse the lowbeam lights?

Posted

OK, well did the modification tonight. Instead of going to the High Beam, I went and ran my Diode into the 22 slot, which is the parking light signal. I tried the lights and everything functioned perfect. Lights on with Low Beams, High Beams, and when switched to parking lights they stayed on as well. All I can say is best 0.50 cent mod ever!!!!

 

Wait so by doing the jump to slot 22 the fogs come on automatically with your low beams? And stays on with high beams as well?

Posted

Thanks guys. Once I get the diodes from Dave, I'm going to do this mod.

 

I think I'm going with suggestion #2 though. I'm going to jump from #10 (fog lamps) to #22 (parking lamps). I want my fog lights on anytime my parking lights are on. Perfect.

 

Thanks for the info guys.

  • Like 2
Posted

 

Wait so by doing the jump to slot 22 the fogs come on automatically with your low beams? And stays on with high beams as well?

yes that is correct. i just did this mod right now. and the fogs do turn on with the parking lamps, and stay lit with the low beams and high beams aswell.

  • Like 3
Posted

on a side note. i went outside to go verify the wires for pin 7 on X4 and X5 connectors and strangely enough i found out that they do no exist. now this is on a 2014 silverado, maybe the wires would exist on a GMC being that they have a dedicated DRL module? any GMC guys care to confirm this for me?

  • Like 1

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

    • As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?
    • I went to the county a few years back to dispute my property taxes. To do that I hired an appraiser and a lawyer. The County Assessor wished to argue that the homes in my neighborhood the appraiser used were all 'distressed properties" and not representative of the "Market Average".    My response was," Of the 50 homes in our subdivision 43 of them were "distressed properties" under bank foreclosure and as such "Distressed IS the market". Lawyer about choked on his coffee and handed the Assessor the 'receipts'.    I won that case on the evidence provided by the Lawyer and the Appraiser.    We have the same thing going on here. My statements were based on the GOVERNMENTS NATIONAL DATA and yours on local markets in areas of your interest. They are both correct....   Thing is, this divergence was based on NATIONAL and not on LOCAL. I think you even understand that. But like you said, we are both stubborn and hardheaded.    I do not see any advantage to disengagement.  But that said we can step back to compose ourselves. 
    • Trust me I appreciate the comments and concerns. It's what I was looking for to help me evaluate the situation and what I want to do. I have decided to move forward with the BORA hubcentric slip on 3/8" (.375") with the extended lugs nuts. Fedex says they should be here Monday :). Meanwhile, the dealer got the remote start and Patriot spray in bed liner done over the last couple of days. Also, I installed an inline stop/start eliminator today. Starts back up in what whatever mode you shut it off in, so you don't have to hit the button every time you fire up.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...