Jump to content

Recommended Posts

Posted

I am looking to wire my Baja Designs Lightbar to my high beams.  I know that its not legal to drive like this on the road so I plan to have a switch between the high beam wire and the relay to shut it off if needed.  I have seen that people have done this but I cant figure out how/where people are getting power from the high beams.  There are two high beam fuses in the box but they are tiny and I cant find an add a fuse solution.  I would prefer not to tap into the wiring but if thats the only option where are you all doing it?

 

The S8 light bar also as the amber driving light portion that I am likely going to delete because I dont want it to be powered on when the truck isnt powered on.  Beaming that I plan on having the high beams trigger the relay I dont think this is easily possible.  If anyone has any ideas there as well that would be great.  Thanks in advance for any advice.

Posted

Ok, I did this with my two spot and my wide beam light install on my AT4. Keep in mind this is how I did it knowing I will be changing it around in the future. If you want to use a switch to toggle the lights on and off you’ll need two relays to do it right. If you want them always on with high beam you can get away with 1 relay.

Switch relay (relay 1)
High beam relay (relay 2)


Step 1- you need two SPST relays. 86 on both will be grounded, 30 on the switch relay (relay 1) will need to be fused directly from the battery at an amperage high enough for your light bar. Mine is 15 amps.


Step 2-switch relay (relay 1).First I ran a ‘zip’ wire (two wires bonded together) through the firewall and into the truck. These two connect to a regular toggle switch that I have floating around cause I didn’t want to drill a hole. If you have a lighted switch you will need a ground wire as well. 18 gauge is plenty for this. This switch allows me to turn the light bars on or off. (Only trips on with high beams with the 2nd relay). 12 volt into the switch is one of the wires, fused at 3 amps directly from the battery. The wire going out goes to 85 on the relay.

Step 3-switch relay out to high beam relay(relay2). 87 from relay 1 goes to 30 of relay 2. This basically sees the switch on trigger and allows it to activate the second relay which will use the high beam trigger.

Step 4- high beam relay (relay 2). I tapped into the high beam right at the harness going into the headlight. It was just easier for me. I metered and verified the correct wire and used a solder with heat shrink style “butt”connector to tap it. This is the signal wire to trip the high beam relay. It will go to 85 on the high beam relay.

Step 5- 87 on the high beam relay (relay 2) will
Be the 12 volt output that will power your light bar.

Using relays this way keeps your light bar from drawing too much amperage from the factory high beam wire so it doesn’t mess with the computer. The switch will allow the system to be on or off. Works nicely with the auto high beam as well if your truck is equipped.

  • Like 1
Posted
7 minutes ago, jflan23 said:

Ok, I did this with my two spot and my wide beam light install on my AT4. Keep in mind this is how I did it knowing I will be changing it around in the future. If you want to use a switch to toggle the lights on and off you’ll need two relays to do it right. If you want them always on with high beam you can get away with 1 relay.

Switch relay (relay 1)
High beam relay (relay 2)


Step 1- you need two SPST relays. 86 on both will be grounded, 30 on the switch relay (relay 1) will need to be fused directly from the battery at an amperage high enough for your light bar. Mine is 15 amps.


Step 2-switch relay (relay 1).First I ran a ‘zip’ wire (two wires bonded together) through the firewall and into the truck. These two connect to a regular toggle switch that I have floating around cause I didn’t want to drill a hole. If you have a lighted switch you will need a ground wire as well. 18 gauge is plenty for this. This switch allows me to turn the light bars on or off. (Only trips on with high beams with the 2nd relay). 12 volt into the switch is one of the wires, fused at 3 amps directly from the battery. The wire going out goes to 85 on the relay.

Step 3-switch relay out to high beam relay(relay2). 87 from relay 1 goes to 30 of relay 2. This basically sees the switch on trigger and allows it to activate the second relay which will use the high beam trigger.

Step 4- high beam relay (relay 2). I tapped into the high beam right at the harness going into the headlight. It was just easier for me. I metered and verified the correct wire and used a solder with heat shrink style “butt”connector to tap it. This is the signal wire to trip the high beam relay. It will go to 85 on the high beam relay.

Step 5- 87 on the high beam relay (relay 2) will
Be the 12 volt output that will power your light bar.

Using relays this way keeps your light bar from drawing too much amperage from the factory high beam wire so it doesn’t mess with the computer. The switch will allow the system to be on or off. Works nicely with the auto high beam as well if your truck is equipped.

Wow that was quick and thorough.  Thanks a ton.  You dont happen to have an image of where you tapped into the high beam harness do you?  I am assuming the engine compartments and wiring are fairly close between the AT4 and Trailboss LT.

Posted
Wow that was quick and thorough.  Thanks a ton.  You dont happen to have an image of where you tapped into the high beam harness do you?  I am assuming the engine compartments and wiring are fairly close between the AT4 and Trailboss LT.

I don’t have a photo, it’s wrapped in tape now lol. If I recall correctly I grabbed the harness right at the headlight. I believe the harness goes through a grommet before plugging into the headlight. Granted the gmc headlights are a bit different but I assume it’s somewhat close. Regardless there will be a high beam wire going into the headlight housing, you’ll have to verify which one first but it’ll be there.
Posted
1 hour ago, jflan23 said:


I don’t have a photo, it’s wrapped in tape now lol. If I recall correctly I grabbed the harness right at the headlight. I believe the harness goes through a grommet before plugging into the headlight. Granted the gmc headlights are a bit different but I assume it’s somewhat close. Regardless there will be a high beam wire going into the headlight housing, you’ll have to verify which one first but it’ll be there.

Do you have a picture of the LED bar placement day and night?  I have an AT4 and ive been thinking about installing a bar as well.  Thanks

Posted
Do you have a picture of the LED bar placement day and night?  I have an AT4 and ive been thinking about installing a bar as well.  Thanks

258daa4c9bf20037fe4bf91887890d60.jpg


I don’t have a night pic. I basically cut the plastic valence above the bumper in two pieces and put the lights in the middle. Two are spots the center is wide angle.
Posted
1 hour ago, jflan23 said:


258daa4c9bf20037fe4bf91887890d60.jpg


I don’t have a night pic. I basically cut the plastic valence above the bumper in two pieces and put the lights in the middle. Two are spots the center is wide angle.

Wow, that looks really good.  I'm too scared to go cutting to my bumpers, but that looks like its from the factory!

  • 1 year later...
Posted

So I finally got around to doing this.  Thank you Jflan for getting me 90% of the way there.  Ended up setting up a relay so that light bar is only powered when the truck is on.  I then set up a relay so that my high beams trigger the light bar to come on.  Because youre not supposed to drive on road with light bars I also added a switch on this relay so that I can have my high beams without the light bar on.

 

Both relays are triggered from the fuse box inside the engine compartment.  I just used simple add a fuses for this.  High beams fuse for the light bar relay and the parking lights for the whole system relay.  I slotted the cover so that I can get the wires out of the box. The fuse box covers are cheap if I want to return it to stock.

 

I would prefer to find a fuse in there that is acc power on and not necessarily tied to my parking lights.  I would like to keep this so that it can be easily returned to OEM without tapping into wires (I would prefer to use these add-a-fuses).  Issue is that during the daylight with my headlights in auto the parking lights toggle off which kills the whole system.

 

Does anyone know a fuse in this box that its acc power on?

Posted
On 12/28/2021 at 7:15 PM, Josef said:

So I finally got around to doing this.  Thank you Jflan for getting me 90% of the way there.  Ended up setting up a relay so that light bar is only powered when the truck is on.  I then set up a relay so that my high beams trigger the light bar to come on.  Because youre not supposed to drive on road with light bars I also added a switch on this relay so that I can have my high beams without the light bar on.

 

Both relays are triggered from the fuse box inside the engine compartment.  I just used simple add a fuses for this.  High beams fuse for the light bar relay and the parking lights for the whole system relay.  I slotted the cover so that I can get the wires out of the box. The fuse box covers are cheap if I want to return it to stock.

 

I would prefer to find a fuse in there that is acc power on and not necessarily tied to my parking lights.  I would like to keep this so that it can be easily returned to OEM without tapping into wires (I would prefer to use these add-a-fuses).  Issue is that during the daylight with my headlights in auto the parking lights toggle off which kills the whole system.

 

Does anyone know a fuse in this box that its acc power on?

Headlight fuse #4. It receives power when the truck is turned on but does not turn on the headlight (headlight function is controlled elsewhere).

  • 2 weeks later...
Posted (edited)

Using fuse #4 I get an error when I put my left turn signal on when the headlights are off during the day.  It’s strange because that fuse is labeled right headlamp and I don’t get the error when I have the right turn signal on. 
 

edit:  nevermind I believe that this error is unrelated to the light bar install. 

Edited by Josef
Update
Posted

Just to circle back on this.  I believe the #4 fuse should work just fine for keyed acc power.  The issue that I had was related to a loose ground wire on a canopy install.

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