Jump to content

Recommended Posts

  • 3 weeks later...
Posted

didnt read all 31 pages,so maybe its in there... but is there a way to get the FL to come on with the key and stay on with the DRL / LB / HB?... basically on all the time.

 

Oh ya..its my first post here..

Posted

didnt read all 31 pages,so maybe its in there... but is there a way to get the FL to come on with the key and stay on with the DRL / LB / HB?... basically on all the time.

 

Oh ya..its my first post here..

I know my Camaro with the RS package uses the fog lights as DRL lights. But once your headlights turn on you can't have your dog lights on anymore. Same goes if you flash your high beams.

 

But I bought a plug and play harness that allows you to keep your dogs in all the time. There is no switch to turn them on and off but I guess it's better than nothing. And now they stay on with my headlights and if I put the high beams on as well.

 

Hope this helps and maybe someone else will chime in with there experience. Maybe someone makes a similar harness for our trucks.

Posted (edited)

didnt read all 31 pages,so maybe its in there... but is there a way to get the FL to come on with the key and stay on with the DRL / LB / HB?... basically on all the time.

 

Oh ya..its my first post here..

The first page goes into that. The 85 pin pin between what is on and what you want to feed to be on will do that.

It is really worth taking the time to read thru the posts. It will help you understand how and why the resistors are placed where they go and how that makes the functions occur that you desire.

 

Sent from my XT1254 using Tapatalk

Edited by TxDoc
  • Like 1
Posted

thx for the help..found what i need on PG4..the 10-22 jump should be what i am looking for. Fogs on with my DRLs and on HIGHS

Posted (edited)

First post here, but I've been lurking for a while.

 

I'm a new GMC Sierra owner -- bought a 2015 SLT Crew Cab 4WD two weeks ago and am loving it! I'm coming from a Wrangler Unlimited that I modded heavily so the mod bug obviously has bitten me once again.

 

I'm wanting to do this mod and I'm curious if anyone by chance has any diodes they have still laying around that I could have? I have a 100 pack in my Amazon cart but that's overkill if there unused ones out there.

 

Thanks

Edited by kramer2k
Posted

First post here, but I've been lurking for a while.

 

I'm a new GMC Sierra owner -- bought a 2015 SLT Crew Cab 4WD two weeks ago and am loving it! I'm coming from a Wrangler Unlimited that I modded heavily so the mod bug obviously has bitten me once again.

 

I'm wanting to do this mod and I'm curious if anyone by chance has any diodes they have still laying around that I could have? I have a 100 pack in my Amazon cart but that's overkill if there unused ones out there.

 

Thanks

 

I've got a couple. PM me your address and will put in an envelope tomorrow.

  • Like 2
Posted

I've got a couple. PM me your address and will put in an envelope tomorrow.

Awesome! Thanks so much! PM on the way.

  • Like 2
Posted

In my 2003 Avalanche, this is what I did for the All On High. I also opted to have my running lights come on with my fog lights. Will this work with the 2017 system, if not, what will I need to do to keep everything on when I either flash or turn on my highs, and have the DRL's come on when I turn on my fogs?

 

As a side note, we replace the white DRL lights with Amber so we know who all is from the site. But, our DRL's come on when we put the truck in drive only.

 

 

Here is the link:

http://www.chevyavalanchefanclub.com/cafcna/index.php/topic,60928.0.html

  • 1 month later...
Posted

I want this! How?

 

Sent from my SCH-I545 using Tapatalk

 

My company, same one that developed this:

 

 

wanting some info on this but cant figure out how to PM you

  • 2 weeks later...
Posted

Hizzle3500,

 

Here is the link to what you are looking for. I have spoke to them before about having my remote make the windows go up, pay good attention to their hours of operation, they are very specific about it. I want to do the radio mod and the windows as well...

 

http://www.whiteautoandmedia.com/

  • Like 1
Posted

Back on subject, has anyone tried the #10 & #18 on a 2017 Silverado 1500 yet? If so, are all six lights one when you turn on the high beams? That would be High, Low, and Fog...

  • Like 1
Posted

Back on subject, has anyone tried the #10 & #18 on a 2017 Silverado 1500 yet? If so, are all six lights one when you turn on the high beams? That would be High, Low, and Fog...

 

 

With the 16's and 17's, there would only be 4 lights on at any one time with the fogs, whether it be low or high.

 

But I know what you're trying to ask.

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined
  • Who's Online   3 Members, 0 Anonymous, 1,633 Guests (See full list)


  • Latest Articles

  • Posts

    • Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • 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?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...