Aftermarket Headlights - Wiring & Issues (Group Help)

[airline tech]

OK, I just verified a theory I had. I went out and pulled the tapped power from fuse #19 and switch in auto ignition off, connected it to the positive battery post. I got a startup sequence both sides, headlights out after sequence and DRLs on bright. So the tapped power powers the headlight sequence and the DRLs on bright.

Did same test, with switch in park ignition off, DRLs come on in dim (parking mode). Got same results, when connecting tapped lead to battery, except, DRLs stayed on dim (parking mode).

It appears that when there is power on the parking wire it keeps the DRLs in the dim parking mode. This would make sense, as anytime the lights are on the parking lights are also. Also, because I have my parking lights on as part of my DRL setting, when I take my truck out of park my DRLs dim down.

You know - sometimes you can look so deep into an issue and overlook a SIMPLE way to pinpoint down - what specific circuit is triggering the (Start=Up) sequence to NOT WORK.


So, you have a simple way to play with Switch Position and Forscan.
1. We know that with you setting - Forscan to (Dedicated DRL)
This moves the DRL circuit to (Dedicated DRL - which changes the circuit from)
Low Beams (Bi-Powered) - DRL (Dim) & (Low Beam - Bright) when Low Beam is activated the Park Lights are also triggered (ON)
to
Park Light (Bi-Powered) - (DRL-Bright) and all other lights (OFF)
When you transition (OUT of Park) - The DRL-Dims and your Fogs trigger (ON) as your (DRL Light) Option.

In a (Normal) set-up the initial (DRL-Bright) In Park is (Not-Normal) and when transitioning out of (Park) should be the trigger for the DRL to come on & Bright

The DRL - Bright @ Truck Start and still in (Park) is due to the Tapped Power, By-Passing the BCM Control, when you transition out of park - the BCM takes over control (of the park lamp circuit)
and since you have (+Fogs) as DRL's - it considers this the same as (Low Beams) being on and changes the Light Output from DRL Bright - To DRL Dim (Park Lights) or it caused by the (Setting - (Include Park Lights) as DRL's

The main question is:
With that - TEST, and you place the (Headlamp Switch) in (Headlamps) and then touch the (Battery) source - Does the Start-Up - Sequence - Trigger?
as If I understand - The Start-Up sequence will (Trigger) with the Headlamp Switch in (AUTO) and (Park Lamps) --- Correct?

If this is CORRECT, then we can (isolate) it to the (Headlamp- Low Beam) circuit causing the Morimoto to pick up (They have already been powered) so the Start-Up sequence has already been completed (even though) they have not.

If this is the case, then we just need to (Wiretap) Pin #6 in the harness and then reset the Forscan (Settings) up as they would be set for (Lariat) LED's and then play with the Forscan settings from there and it may possibly be a scenario to set them up as the - Canadian Trucks.

I have the complete list of (As-Built) data relating to the exterior lights for:
US Version (Halo to LED) Change (Factory Lighting)
based on that
I have all the (As-Built) changes for a 22 US Version to a 22 Canada Version (Lariat)
So, I can see (all changes) that were made for the (Sept 2021) Canada Mandate change to the DRL (Laws)
The UNKNOWN is for this LAW CHANGE - and a Canadian Owner will need to chime in here.
I know that the law made it so:
1. The DRL Lights are to be (ON) in any switch position and they must include the Park Lights (Meaning the Tail Lamps)
Any switch position (Includes) OFF - Park Lamps - Auto
The Auto Headlamps (Will Still Function) normally and the DRL Lighting will (DIM) as the Headlights will be (ON)

2. The Canada Version - also DISABLES the IPC selection inputs in the (BCM)
This is for DRL Lighting - In the IPC Menu
So, all this is doing within the BCM is telling the BCM - DRL's are always active outside of (Auto) position. Where the US Version - they are only active in (AUTO) and you have the option to (Turn-Off) the (Auto-DRL)

There are others but I wanted to see (As-Built) data and wanted to know what was being changed when you - De-Select - DRL Lighting in the IPC Menu

BCM:
726-16-02: Feature Configuration - DRL By Auto-Lamp Person 1-4
726-16-02: Feature Configuration - DRL by Auto-Lamp Vehicle

726-16-02 - 0101-0101-014A - (US Version)
726-16-02 - 0202-0202-024F - (Canada Version)

For the Person 1-4 Setting - x2x2-x2x2-xxxx
0=Disabled - 1=Enabled 2=Inop

For the DRL by Vehicle Setting - xxxx-xxxx-x2xx
0=Disabled - 1=Enabled 2=Inop

My Test Results:
With the IPC Selection (DRL-Lighting) Selected this line reads -- 0101-0101-014A
With the IPC Selection (DRL-Lighting) DE-Selected this line reads - 0101-0101-0049
So, by having the IPC screen - this is exactly how you are telling the BCM to turn the function (OFF or Disable)
Note the by Person - Does Not Change as this is still a (ALLOWED) by person change to change it back to (Enabled)
So, Canada version sets this as (INOP)
and they take it a step further and completely (Disable) the IPC selection screen from even showing in the menu.

Plus: They change (1) other setting regarding (DRL-Auto-Lamps) Control in the BCM
and that is:

721-21-01 - Feature List to BCM (DRL) By Auto-Lamp Initial Value

721-21-01 - 1401-0001-0166 - (US Version)
721-21-01 - 1401-0001-0267 - (Canada Version)
xxxx-xxxx-x2xx
0=Disabled - 1=Enabled 2=Inop
It is not (CLEAR) for this line, but I believe that this line is the (Primary Line) that allows control (By-Person) for the 726-16-02 (Line) as it allows that line to be (Customized) by the IPC Menu.

and the IPC (DRL-Lighting) option in the IPC Menu is Disabled for the Canada Trucks

IPC: 720-02-01

720-02-01 - 4DE5-343D-1EEB - (US Version)
720-02-01 - 4DA5-345D-1ECB - (Canada Version)

IPC Menu: xxAx-xxxx-xxxx
E=Enabled A=Disabled

IPC Menu: xxxx-xx5x-xxxx
5=Canada 3=USA

I do not know what (Specific) change it would make by changing the (Country Code) as to what programming it actually does, but the other to Enable or Disable setting will alter if the screen is viewable.

Again, there are some other changes made (Between US & Canada) I will be posting those shortly.

But I can see the changes, but I have (1) unanswered question and that is for a Canada Truck and the Factory Settings on all 2022 and 2023 (after the Law Change) and these settings changed between a 2019 compare & 2022 to comply with that Law Chage.

Do the Canada Trucks have the DRL Lights (ON) at engine start and in (PARK) or is the (DRL- Still Activated) out of Park, as I am unclear on this, as I know they have taken away the DRL only on in (Auto) and also the ability for customer control.

This is a very important (question) as this would take away the need for a (Tapped Power) source and give full control over to the BCM as @ engine start the (DRL Lighting) circuit would trigger (ON) and give you the start-up sequence- just like the (Tapped Power) Source is.
but with the Canada trucks having a Factory LED installed, and the DRL being triggered (ON) at engine start - (In the Dark) would the - Start-Up Sequence (always work) or would it provide the same result as you currently have.

So, the other half of this question - relies on the outcome of the test results of @Big Blue
With the Headlamps (ON) and you touch the power to the battery - how does the Start-Up sequence function.
and a secondary test would be (In the Dark) in (Auto) and the BCM has already turned on the Low Beams - and then touch battery with that tapped power - do you get the same results
Inoperative - Start-Up Sequence or Partially Working (Left Side-Only) Start-Up Sequence.
As, if I am clear on your test results thus far - In (AUTO) & (Park Lamps) the Start-Up Sequence will trigger every time when you touch the battery with the tapped source.

Sponsored

 

[airline tech]

And just a FYI Information:
The reason for - Parking Lights (ONLY) during remote start is this setting:

BCM:
726-41-02 - Remote Start Lighting Control (Park Lights- ON)
726-41-02 - 0101-0101-0074 - xxxx-xxx1-xxxx
0=Disabled - 1=Enabled

This is how the factory BCM is set for remote start (Exterior Lighting) Control and why the parking lights are the only lights lit.

 

[airline tech]

I plan on doing some more - T-Shooting next week.
I want to play with -Forscan (With my Factory LED's)
And I want to try to get the exact power match as the Tapped Source.

So, I need to find (In Daylight)
What setting will trigger the (Parking Lights-ON-DIM) at start-up and in (Park) & (Auto)
as this would be the same as (Remote Start) Lighting and then switch to (Bright) when out of park.
or
What setting will trigger the (Parking Lights/DRL - ON-Bright) at start up and in (Park) & (Auto) and stay (Bright) out of Park.

and then Retest - this in the Dark when the Headlights are triggered (ON)
At least from the Factory Side, I can see what is happening and BCM Control, this MAY provide some guidance in getting the Morimoto's to function without issues but removing the Tapped source from Fused to Wire Tap.

This would be a way - to test how the Canada Trucks are set, as I am unsure if they are set to be on (In Park) or are they still (Gear Dependent) and out of Park Position.
As my thinking is - if we can get the (Park Lights) to come on in Park either (DRL-Bright) or (Parking-DIM) this would provide the (same) power pulse as the Tapped Power source is.
I am confident it will work it's just finding the right setting to get the lights to trigger the (Start-Up) sequence (Every-Start) both Day & Night.

My REASONING for moving the Fused Tapped Power source to Wire Tapped.
1. The BCM is not providing the Power, so as far as the BCM is concerned the DRL & Parking lights are (OFF)

2. When the BCM - closes the circuit (to power Parking Lights), since there is already power on the parking lights - They DIM

3. When the BCM - Triggers the (Headlights) on - (Auto) - the programming is to also power the (Parking Lights - In DIM) and to turn off the (PIN#6) power feed which with a LED DRL is the same light source - So with power on Pin#5 - the BCM is providing (Park Light-Power) and the when (DRL Power is applied to Pin#6) - Pin #5 power drops.
Since (Pin#6) has been By-Passed with a (switched) power source, the BCM has lost full control on when to (Apply & Remove) Power from the (DRL) Lighting Circuit (PIN#6)
This loss of control I believe is what is causing the issues with the (Start-Up) sequence.

One way to test my theory without actually (Wire Tapping) the circuit is to Back-Probe pin #6 on the harness connector and then use a jumper from that to the (Fuse) Tap wire.
They make Back-Probe leads but a Sewing (T-PIN) will work, just ensure you are sliding down the side of the wire vs piercing it.
and as long as you have set Forscan up to have (Dedicated-DRL) then the BCM will be sending power to PIN#6.

From here (It will require) the Truck in (Daylight) and (Auto) and out of (Park), I like to set the Parking Brake and place in (Neutral) and chock the tires as extra precaution when I am testing.
From Here:
It just the matter of finding the setting to get the (Parking or DRL) circuit to trigger on at engine start and in (PARK)
Which is the test (T-Shoot) that still needs to be complied with.

 

[Big Blue]

Did some more testing today. Pulled tapped power again and shorted to plus battery terminal this time switch in headlight position, ignition off. I got no startup sequence. Tried again with switch in Auto, got a startup sequence both sides headlights came on after sequence completed. Seems having headlights on will block the startup sequence. Also, seems like power on the parking curcuit does not block the sequence, but does control DRL brightness.

Second phase: Reinstalled tapped power lead to fuse #19 position. Switch in Auto Position, turned ignition to on (assy) position, did not start. Got startup sequence both sides.

Next, started truck, all lights go out. When truck started lights came back on with what seemed to be a significant delay of the drivers side light behind the passenger side.

I know this is not the normal way to start the truck so started the truck numerous times without the pause in the on position. Had varying delay of the drives side after the passenger side.

My thoughts on this are this the drop out of power during the start event stops the startup sequence from happening. Then when the power returns, the passenger light coming on stops the sequence from happening on the passenger side but the driver side delay allows the sequence to start locking out the headlight until it completes. The question is what is causing this delay and why does it vary? Does it have something to do with the CANBUS variability during the start sequence or something else?

 

[jdjeff]

Did some more testing today. Pulled tapped power again and shorted to plus battery terminal this time switch in headlight position, ignition off. I got no startup sequence. Tried again with switch in Auto, got a startup sequence both sides headlights came on after sequence completed. Seems having headlights on will block the startup sequence. Also, seems like power on the parking curcuit does not block the sequence, but does control DRL brightness.

Second phase: Reinstalled tapped power lead to fuse #19 position. Switch in Auto Position, turned ignition to on (assy) position, did not start. Got startup sequence both sides.

Next, started truck, all lights go out. When truck started lights came back on with what seemed to be a significant delay of the drivers side light behind the passenger side.

I know this is not the normal way to start the truck so started the truck numerous times without the pause in the on position. Had varying delay of the drives side after the passenger side.

My thoughts on this are this the drop out of power during the start event stops the startup sequence from happening. Then when the power returns, the passenger light coming on stops the sequence from happening on the passenger side but the driver side delay allows the sequence to start locking out the headlight until it completes. The question is what is causing this delay and why does it vary? Does it have something to do with the CANBUS variability during the start sequence or something else?

Yah...I'm about to really do nothing about all this. Doesn't that make me mad?

 

[airline tech]

Did some more testing today. Pulled tapped power again and shorted to plus battery terminal this time switch in headlight position, ignition off. I got no startup sequence. Tried again with switch in Auto, got a startup sequence both sides headlights came on after sequence completed. Seems having headlights on will block the startup sequence. Also, seems like power on the parking curcuit does not block the sequence, but does control DRL brightness.

Second phase: Reinstalled tapped power lead to fuse #19 position. Switch in Auto Position, turned ignition to on (assy) position, did not start. Got startup sequence both sides.

Next, started truck, all lights go out. When truck started lights came back on with what seemed to be a significant delay of the drivers side light behind the passenger side.

I know this is not the normal way to start the truck so started the truck numerous times without the pause in the on position. Had varying delay of the drives side after the passenger side.

My thoughts on this are this the drop out of power during the start event stops the startup sequence from happening. Then when the power returns, the passenger light coming on stops the sequence from happening on the passenger side but the driver side delay allows the sequence to start locking out the headlight until it completes. The question is what is causing this delay and why does it vary? Does it have something to do with the CANBUS variability during the start sequence or something else?

I still think it's the Tapped Power source - reaching the Drivers Side (1st) the Headlight Star-Up Sequence relays in the Headlights are being double powered, Fuse Tapped Source and the BCM at the same time.
You have the (Tapped Power Source) attempting to power the (Low Beam) circuit for a brief moment and at the same time the BCM is applying power to the Low Beam Circuit.
This is why I would like to see - what the outcome would be to let the BCM have full control, as your results so far - The BCM does not like the Tapped Power.

Since we know that the DRL / Parking Circuit is the Trigger, my hunch is that (In the Dark) the initial engine start will trigger the start-up sequence on both lights.
and
Then there would be no start-up sequence in (daylight) at engine start - (UNLESS) we can find the setting to get the Park/DRL to light up (IN PARK)
Otherwise, the start-up sequence will trigger when you move out of park and the DRL triggers.

The big factor here what specific wire (Internal) to the headlight is feeding the relay to get the start-up sequence to trigger - Is it the DRL or Parking or since it is a shared circuit and with you having the (park lights) set as DRL (Include Park Lights) may trigger the start-up sequence, so either circuit can possibly trigger it.

 

[airline tech]

I have been thinking about this, and I believe I know what is happening, and it may confirm that it is the (Tapped Power) source. It will explain the delay as well on the Left Light.

I think the (Start-Up) sequence is actually triggering and working, it's just the (BCM) Power hides it (The Pulse-Ramp Up) for all 3 lights.
The (Left) 2 internal headlight relay gets tripped up, and the (Start-Up) splits the light sequence in half, the Left light triggers (AFTER) the right light finishes.
2 Separate power sources coming in at different times, it needs to be on a single source.
To confirm Time the (Start-Up) Sequence, does it match the (Left) side delay.

The above makes the most logical sense on this issue, the BCM power being applied and hiding the (Start-Up) sequence, and you have a shared circuit between the 2 lights (Tapped) the (Tapped-Power) trigger for the left light is not seen until after the (right) side finishes the sequence.
Again - (2) power sources coming in at the same time but a slight delay in the precise timing causing the issue.

Since we have somewhat (Confirmed) that the (DRL) power is the trigger for the start-up, then we need to (Wiretap) the source and then find a way to get power output from the BCM on Pin#6 with the transmission in (Park) in both (Night) & (Day) and also determine if power being applied to the (Park Lights) Pin #5 will it also trigger the (Sequence)
Meaning (Does the Trigger Relay) require the (Bright) voltage signal from Pin#6 or will any voltage from the DRL/Park lamp circuit trigger it, tying in Pin#5.

As an alternative it may be possible to wiretap Pin #5 or a combo of both Pin#5 & Pin#6, this way either circuit receiving a (initial) power pulse would trigger the start-up sequence.
So, at (Night) the park lamp circuit will trigger as the park lamps come on with the headlights.

So, the issue would be in (daylight) the start-up sequence would not trigger until you move out of park and Pin #6 (DRL) power is applied.
So, if we can find a way, to get either (Park) or (DRL) power in park @ anytime the engine is running then we can get the start-up sequence to always trigger.

So, this will take some more playing except move the fuse tapped source to wiretap.
and
Playing with (Forscan) and just sitting in park with the engine running get the (DRL) to light bright, just like it does with the (Tapped) source.

 

[jdjeff]

I have been thinking about this, and I believe I know what is happening, and it may confirm that it is the (Tapped Power) source. It will explain the delay as well on the Left Light.

I think the (Start-Up) sequence is actually triggering and working, it's just the (BCM) Power hides it (The Pulse-Ramp Up) for all 3 lights.
The (Left) 2 internal headlight relay gets tripped up, and the (Start-Up) splits the light sequence in half, the Left light triggers (AFTER) the right light finishes.
2 Separate power sources coming in at different times, it needs to be on a single source.
To confirm Time the (Start-Up) Sequence, does it match the (Left) side delay.

The above makes the most logical sense on this issue, the BCM power being applied and hiding the (Start-Up) sequence, and you have a shared circuit between the 2 lights (Tapped) the (Tapped-Power) trigger for the left light is not seen until after the (right) side finishes the sequence.
Again - (2) power sources coming in at the same time but a slight delay in the precise timing causing the issue.

Since we have somewhat (Confirmed) that the (DRL) power is the trigger for the start-up, then we need to (Wiretap) the source and then find a way to get power output from the BCM on Pin#6 with the transmission in (Park) in both (Night) & (Day) and also determine if power being applied to the (Park Lights) Pin #5 will it also trigger the (Sequence)
Meaning (Does the Trigger Relay) require the (Bright) voltage signal from Pin#6 or will any voltage from the DRL/Park lamp circuit trigger it, tying in Pin#5.

As an alternative it may be possible to wiretap Pin #5 or a combo of both Pin#5 & Pin#6, this way either circuit receiving a (initial) power pulse would trigger the start-up sequence.
So, at (Night) the park lamp circuit will trigger as the park lamps come on with the headlights.

So, the issue would be in (daylight) the start-up sequence would not trigger until you move out of park and Pin #6 (DRL) power is applied.
So, if we can find a way, to get either (Park) or (DRL) power in park @ anytime the engine is running then we can get the start-up sequence to always trigger.

So, this will take some more playing except move the fuse tapped source to wiretap.
and
Playing with (Forscan) and just sitting in park with the engine running get the (DRL) to light bright, just like it does with the (Tapped) source.

Still following along here. I appreciate the work you're doing. What I'm not sure about is if you want me to try something over on my end..

 

[airline tech]

I have an idea:

Since I cannot find any specific (As Built) setting to get the Parking Lights and or DRL Lights to be triggered (ON) at engine start and in (Park) on paper anyways, as I would have to just try different settings on my own (Testing)
There is (1) exception (Remote Start) has an optional (As Built) setting to have the Parking Lights (ON) in the remote start operation.
The only settings I can find are (Include Park Lights) as DRL's, and then the Canada settings to force DRL's (ON) in all headlight switch settings (except Headlight position)
I think that even by switching to the Canada settings the (DRL) trigger will still be activated (Out of Park)

My thought would be keeping the (Tapped) power source but move where it's tapped from.
So, this would be (Direct - Power) from the Battery and using a (Wire Tap) to the park Lamp circuit as the Trigger.

So, install a 4-Pin relay.
1. Run a (10-Amp) fused wire from the Battery to (Relay - Pin#30)
2. Wire Tap (Pin#5) of either headlight harness to (Relay - Pin #86)
3. Run a wire to Body Ground from (Relay - Pin #85)
4. Hook up the Morimoto - Harness Tap to (Relay - Pin#87)

So, you are still using a Fused Tapped source but instead of (DRL Input Power) coming from a (Switched Power -via the Run/Start Relay) which switches with ignition (ON/OFF)
We would be using the Park Light circuit as the trigger.

1. The unknown is (How would this react) with the (Door Lock / Door Open) feedback on the circuit.
You may have to disable this feature, I am talking about when you cycle the Door Locks or open the door, the exterior lights (Flashing) as visual feedback.
It may be (a) the start-up sequence will complete or (b) it will not power long enough to finish
Hopefully this would add the ability of (Triggering) the startup sequence just by locking the doors or opening to doors.

2. When the truck is started - (Day) No-Start up sequence, until you move out of park and with (Include Park Lamps) as DRL's the (Start-Up) Sequence would trigger when the Park Lamps trigger on. (The unknown is - Bright or Dim?)

3. When the truck is started at (Night) the Start-Up sequence should trigger when the Park Lights trigger on (This hopefully will correct) the timing of the start-up sequence due to the fact that at night the Park Lights & Low Beams will trigger on at the same time, and the internal relay in the lights should delay the headlights from coming (ON) until after the start up sequence has completed.

4. You would be able to trigger the start-up sequence just by moving the headlight switch to Headlights or Parking Lights

This would be an alternative in finding a way to get the (DRL Lights) to be on (In-Park) and you are letting the BCM control via (Park Light) power when the relay closes.
I think this is the viable solution and I think it will work as the issue now is the fact that you have 2 separate power sources coming in and the BCM is winning the race providing the power and getting the headlights on (Hiding) the start-up sequence and by letting the BCM control the switched power (when the BCM actually triggers the Park Lights -ON) you have a evenly timed Start-Up sequence trigger.
So, you are still using the recommend way to power the DRL by the Fuse Tapped source you are just moving (when) the source has power and actually using the BCM to control it vs (NOW) the BCM has no control of that power and anytime Power is applied to (Pin#5) of the Park Lamp circuit the (Start-Up) sequence should trigger off of the added relay and apply power to the (DRL Harness) or if the pin was there (Pin#6) DRL Circuit

 

[Big Blue]

I have an idea:

Since I cannot find any specific (As Built) setting to get the Parking Lights and or DRL Lights to be triggered (ON) at engine start and in (Park) on paper anyways, as I would have to just try different settings on my own (Testing)
There is (1) exception (Remote Start) has an optional (As Built) setting to have the Parking Lights (ON) in the remote start operation.
The only settings I can find are (Include Park Lights) as DRL's, and then the Canada settings to force DRL's (ON) in all headlight switch settings (except Headlight position)
I think that even by switching to the Canada settings the (DRL) trigger will still be activated (Out of Park)

My thought would be keeping the (Tapped) power source but move where it's tapped from.
So, this would be (Direct - Power) from the Battery and using a (Wire Tap) to the park Lamp circuit as the Trigger.

So, install a 4-Pin relay.
1. Run a (10-Amp) fused wire from the Battery to (Relay - Pin#30)
2. Wire Tap (Pin#5) of either headlight harness to (Relay - Pin #86)
3. Run a wire to Body Ground from (Relay - Pin #85)
4. Hook up the Morimoto - Harness Tap to (Relay - Pin#87)

So, you are still using a Fused Tapped source but instead of (DRL Input Power) coming from a (Switched Power -via the Run/Start Relay) which switches with ignition (ON/OFF)
We would be using the Park Light circuit as the trigger.

1. The unknown is (How would this react) with the (Door Lock / Door Open) feedback on the circuit.
You may have to disable this feature, I am talking about when you cycle the Door Locks or open the door, the exterior lights (Flashing) as visual feedback.
It may be (a) the start-up sequence will complete or (b) it will not power long enough to finish
Hopefully this would add the ability of (Triggering) the startup sequence just by locking the doors or opening to doors.

2. When the truck is started - (Day) No-Start up sequence, until you move out of park and with (Include Park Lamps) as DRL's the (Start-Up) Sequence would trigger when the Park Lamps trigger on. (The unknown is - Bright or Dim?)

3. When the truck is started at (Night) the Start-Up sequence should trigger when the Park Lights trigger on (This hopefully will correct) the timing of the start-up sequence due to the fact that at night the Park Lights & Low Beams will trigger on at the same time, and the internal relay in the lights should delay the headlights from coming (ON) until after the start up sequence has completed.

4. You would be able to trigger the start-up sequence just by moving the headlight switch to Headlights or Parking Lights

This would be an alternative in finding a way to get the (DRL Lights) to be on (In-Park) and you are letting the BCM control via (Park Light) power when the relay closes.
I think this is the viable solution and I think it will work as the issue now is the fact that you have 2 separate power sources coming in and the BCM is winning the race providing the power and getting the headlights on (Hiding) the start-up sequence and by letting the BCM control the switched power (when the BCM actually triggers the Park Lights -ON) you have a evenly timed Start-Up sequence trigger.
So, you are still using the recommend way to power the DRL by the Fuse Tapped source you are just moving (when) the source has power and actually using the BCM to control it vs (NOW) the BCM has no control of that power and anytime Power is applied to (Pin#5) of the Park Lamp circuit the (Start-Up) sequence should trigger off of the added relay and apply power to the (DRL Harness) or if the pin was there (Pin#6) DRL Circuit

If you are still trying to solve the problem with that @jdjeff is having I think you are confusing what is actually causing it. You keep looking at the tapped power. And, you seem obsessed with making them work like your OEM LED lights, which they are not. They were designed to work with no Asbuilt changes on both LED and Halogen equipped truck. Hence the need to separate out the DRL control. The fact that they included the startup sequence, including the Bi-LED projectors complicated the system. They maybe did not take the Auto-Light system fully into account.

I'll let you in on my theory from my testing with my lights.
First, I find that the trigger for the startup sequence is the power up of the tapped power. It also powers the sequence and takes control of the projectors until the sequence completes. This happens regardless of light switch position, except when headlights are on, as long as the ignition is off. Tested by pulling fuse tap out and jumping fuse tap to positive battery terminal. This indicates that even with parking lights on the sequence is initiated. This also happens if you turn the ignition switch to on and do not start the truck. Only difference with the parking lights on is the DRL bars come on dim. With the headlights on you get no startup sequence, only the DRL bars on dim. This happens with starting the truck with the light switch in any position but Auto, and the truck in dark mode. My conclusion is that any power to the low beams disables/blocks the startup sequence. The only thing the parking light power seems to affect is the brightness of the DRL bars.

So with the truck in light mode the Startup sequence works as designed in any light switch position except the Headlight position, as even in Auto the headlights are not on.

The issue that @jdjeff and I am having appears to happen only when the light switch is in Auto and the truck is in dark mode, calling for lights. The randomness of either getting, or not getting, a startup sequence on one or both lights seems to be do to the momentary dropping of the headlight and tapped power during the cranking cycle and any delay in the lights coming back on and blocking the startup sequence. The difference be that the left and right headlights are powered by separate circuits for some reason.

Again this is my theory from my personal crude testing. as for the issue I have no plans to change anything with my lights and live with them as is, installed per manufacturers instructions. I didn't even know it exited until @jdjeff brought it up. In fact I haven't really paid much attention to the startup sequence at all until now, kind of hard to see from the drives seat. If I knew how, I'd probably disable it. As long as it didn't require removing the lights to do.

 

[airline tech]

I am using your findings and (Symptoms) @Big Blue and @jdjeff issues (symptoms) of the Start-Up sequence not working all the time.
Mainly your findings on when you take the Tap and place it on the battery and your noted - (DELAY) on the LH Headlight anytime (The Headlights) are (ON)
I believe that instead of being blocked (Its actually happening) but with the BCM already commanding the (Headlight-ON) the Tapped- Power is cycling the (Start-Up) but it is HIDDEN.

I am using the Following as my basis of what is happening:
@Big Blue Test Results

"Iny playing I did have a couple instances of the passenger side not occurring while the driver side did. I also had sometimes where neither had the sequence with the headlights in the on position."

"Did some more testing today. Pulled tapped power again and shorted to plus battery terminal this time switch in headlight position, ignition off. I got no startup sequence. Tried again with switch in Auto, got a startup sequence both sides headlights came on after sequence completed. Seems having headlights on will block the startup sequence. Also, seems like power on the parking curcuit does not block the sequence, but does control DRL brightness."

"Next, started truck, all lights go out. When truck started lights came back on with what seemed to be a significant delay of the drivers side light behind the passenger side."

"My thoughts on this are this the drop out of power during the start event stops the startup sequence from happening. Then when the power returns, the passenger light coming on stops the sequence from happening on the passenger side but the driver side delay allows the sequence to start locking out the headlight until it completes. The question is what is causing this delay and why does it vary? Does it have something to do with the CANBUS variability during the start sequence or something else? "


My Theory:
The Start-Up is not being BLOCKED, its (HIDDEN) as the BCM already has the lights (ON)
You both are experiencing a (DELAY) on (Start-Up) sequence any time the (Headlights are ON)
The last sentence of your findings asks the question:

"The question is what is causing this delay and why does it vary? Does it have something to do with the CANBUS variability during the start sequence or something else? "

I am answering that question, and I believe the cause of it is from the exact (Tapped Source) is coming off (Relay-Power) the BCM is (Direct Power) and the Headlights are being commanded (ON) before the (Relay-Powered) Tap can reach the Headlight.
So, when the (Relay-Power) reaches the Headlight - The Headlights are already on
Each of those Headlights have a (Relay) inside of them that (wants) a tapped power source that will trigger (Coil-Side) control to (INIATE) the start-up sequence.
With (BOTH) of those (Relays) being on the same (SHARED) power source they get out of sequence. (This is the DELAY)

"Tried again with switch in Auto, got a startup sequence both sides headlights came on after sequence completed. Seems having headlights on will block the startup sequence."

Excerpt from above: This result tells me that in (AUTO) it will (show-visually) display the Start-Up sequence as you are providing the (Tapped-Switched) power with the Headlights (OFF) & when you have the Headlight Switch (Headlight) the Headlights are already (ON) and the Star-Up sequence is (HIIDDEN) not (BLOCKED)

Fact and Proven:
The DRL control (Input) signal is what triggers the Start-Up sequence, this is proven by @Big Blue and for a (Factory- LED) Headlamp housing is Pinned For, thus my initial reasoning as the Halo's & Aftermarkets) are not. The REASON for the Aftermarkets to want Tapped Power

Fact:
Halogen (OEM) - Headlamps are NOT wired for (PIN#6) DRL Control the exact same as the aftermarkets. (Morimoto at this point -CONFIRMED)

Fact:
The only way to get power on (PIN#6) Dedicated DRL circuit is with (FORSCAN) and PROGRAMMING the BCM open that power output this is the (Dedicated DRL) Setting in Forscan it allows Power Output on Pin #6 to power a Dedicated DRL Circuit (LED LIGHTBAR) this moves the DRL power from (LOW BEAM) Pin #2 to Pin #6
When you De-Select the (DRL-Lighting) in the IPC - it's not doing anything but removing the DRL (Output) on Pin #2 (Disabling) the Power Cut (50%) on the Low Beam circuit
This is ONLY & IF you have not changed any BCM programming and are still set up with BCM Control as (Halogen) Headlights, this is the REASON the AFTERMAKETS have you (DE-SELECT) that IPC Menu setting.

If you have changed the BCM settings to Factory LED, and have (ONLY) the BCM to control the DRL's then (De-Selecting) the DRL Lighting turns off Power to Pin#6 instead of (Pin#2)
So, with a Tapped power source & changing the - BCM to Dedicate DRL, the IPC Menu screen will be only affecting the Park Lamp circuit as the BCM has no control of Power for Pin#6, but will affect the (extra's) (+Fogs / +Park Lights)

Fact:
The reason for the (Aftermarkets) to have you (De-Select) the DRL Lighting in the IPC, is to (TURN-OFF) the DRL circuit to the (Low Beams) as that is what the BCM is programmed to do.
Without - BCM Reprogramming of Pin#6 Power, which is also negated as the Headlight Assembly is not wired for (Directly) from the BCM (Tapped Source - Addition)

Fact:
The BCM cannot see (DRL) Lighting is (ON) as you have by-passed its control of it.
via (Tapped-Power) again (Pin#6) Power

Fact:
The Aftermarkets - Do NOT want to sell a product that requires a BCM programming change for them to work - Hense the (Tapped-Power) source.
On a (Bench) and a battery source for Power, this logic works flawlessly, what was (OVERLOOKED) in the operation aspect of the (Start-Up) sequence and what will happen if you (add) another power source on the circuit. (That-ADDED source is the BCM) taking over control of the (Low Beam Power)

Fact:
This is the CONFLICT in (Double) powering the Headlight from 2 separate sources
THIS is the reason for ME pushing to DUMP that Tapped Power
So, with (ZERO) programming changes and removing the (Tapped-Power) the DRL's will never work.

So, this brings us to a crossroad, The BEST WAY to (Bring Power) onto the DRL Circuit

1. Keep it as (IS) and Fuse Tap - Fuse #19
a. This is proven to be an issue, works fine until the BCM pushes power out to the Headlights (Pin#2) Low Beam Circuit.

2. Wire Tap (Pin#6) on the Harmes, anytime the BCM provides power to (Pin#6) the DRL's will light up.
a. This creates an issue with the (Start-Up) sequence function, it will only power when you take the truck out of park and its (Daylight)
b. FIND a (BCM) Programming setting that will allow power output on (Pin#6) when the truck is in (Park) with both (DAY) & (NIGHT) scenarios.
This will simulate - the Fused Tapped - Power
The issue, in the As-Bult files, I do not see any settings that will provide that (power) need.

3. My Theory of (Finding) an alternate (Taped-Power) source and let the (BCM) itself provide the power source.
a. Wire Tap (Pin#5) on the harness side of the connector (Either LEFT or RIGHT) with most of the complaints occurring on the (LEFT) I would try the (RIGHT) first
b, by using the (Park) Lamp circuit as the (Relay) trigger, anytime power is applied to the (Park Lamp) circuit will (Power) the (DRL- Tapped) power source (Pin#6) in the headlight wiring.
c, so this is (STILL) a Tapped Power source but you are (ELIMIMINATING) the (Ignition-Run/Start) relay bringing the power in and using the (BCM) itself to provide the power via the (Park Lamp) circuit.
d. This will cure (I Think) the Start-Up sequence not being seen at (Dark)
e. However, in (Day) the startup sequence will only function when you come out of (PARK)
so, a small caveat - you lose the sequence at start-up in (Day) operation only
f. In (Night/Dark) - operation the (Park-Lamp) powering up will close the added relay and provide the (Start-Up) sequence as the Park Lamps & Low Beams will be commanded on at the (Same Time)
Vs
BCM Powering First and winning the Race throwing the Headlight Relays (Out of Sequence)

I hope this makes sense, and since I do not have aftermarkets, I cannot actually test this out.
I am only going off of - the issues you both have and your findings in your test results thus far.
I am 90% positive that the timing of the (Tapped-Power) source is the cause and thinking that moving it (when its actually applied) will cure the issue and unless I can find the (HIDDEN) BCM As-Built data file that will (power-out) Pin #6 at engine start.
The adding of a relay on the (Park-Lamp) circuit as a (Coil-Side) trigger to close the relay and (Power Pin#6) will be the most logical option
Again - UNTESTED but in theory makes the most sense, as we are talking about (Milliseconds) in Time

So, at this point - Since I have NOT found a (Power Out of Pin#6) solution at engine start so far.
Then YES, it REQUIRES a TAPPED POWER source, and we only need to (Augment) or (Change) when the Tapped Power is (ACTUALLY APPLIED)
That (TIMING) is the cause of the Start-Up Sequence being (Hidden or Delayed)
If I can find a (BCM-Change) that (WILL -POWER) Pin #6 at every engine start and (In-Park)
then the (Tapped) Power source can be removed, and this will let the BCM provide full control.
I do not see that happening from the As-Built settings, so this will have to be a (Play) with Forscan and make changes (and note) if I can get the DRL Circuit to Light Up (Bright) with the Truck in (Park) using only the (BCM-Power Output) from Pin#6 as my Factory LED's have Pin#6 this would be easily noted.
We can then use that (Information) - (Setting-Needed) and transpose that to Wire Tap (Pin#6) in the Factory Harness and (Send that) Tapped source onto the (Aftermarket) Headlamp Assembly.
Again - This will only work if I can find a way to get the (WANTED) Power Output from Pin#6 Engine Running in (PARK) & Day & Night Operation
The Aftermarkets (WILL) function the same as Factory LED including the (ADDED) special effects
(Start-Up Sequence) and (Sequential Turns) if we can achieve this power output (CHANGE)

Since it APPEARS that this is NOT an achievable outcome, then we need to move the (Timing) of when the Tapped Power actually comes in, which is the issue (The Timing) of the Tapped Power,

 

[Big Blue]

I am using your findings and (Symptoms) @Big Blue and @jdjeff issues (symptoms) of the Start-Up sequence not working all the time.
Mainly your findings on when you take the Tap and place it on the battery and your noted - (DELAY) on the LH Headlight anytime (The Headlights) are (ON)
I believe that instead of being blocked (Its actually happening) but with the BCM already commanding the (Headlight-ON) the Tapped- Power is cycling the (Start-Up) but it is HIDDEN.

I am using the Following as my basis of what is happening:
@Big Blue Test Results

"Iny playing I did have a couple instances of the passenger side not occurring while the driver side did. I also had sometimes where neither had the sequence with the headlights in the on position."

"Did some more testing today. Pulled tapped power again and shorted to plus battery terminal this time switch in headlight position, ignition off. I got no startup sequence. Tried again with switch in Auto, got a startup sequence both sides headlights came on after sequence completed. Seems having headlights on will block the startup sequence. Also, seems like power on the parking curcuit does not block the sequence, but does control DRL brightness."

"Next, started truck, all lights go out. When truck started lights came back on with what seemed to be a significant delay of the drivers side light behind the passenger side."

"My thoughts on this are this the drop out of power during the start event stops the startup sequence from happening. Then when the power returns, the passenger light coming on stops the sequence from happening on the passenger side but the driver side delay allows the sequence to start locking out the headlight until it completes. The question is what is causing this delay and why does it vary? Does it have something to do with the CANBUS variability during the start sequence or something else? "


My Theory:
The Start-Up is not being BLOCKED, its (HIDDEN) as the BCM already has the lights (ON)
You both are experiencing a (DELAY) on (Start-Up) sequence any time the (Headlights are ON)
The last sentence of your findings asks the question:

"The question is what is causing this delay and why does it vary? Does it have something to do with the CANBUS variability during the start sequence or something else? "

I am answering that question, and I believe the cause of it is from the exact (Tapped Source) is coming off (Relay-Power) the BCM is (Direct Power) and the Headlights are being commanded (ON) before the (Relay-Powered) Tap can reach the Headlight.
So, when the (Relay-Power) reaches the Headlight - The Headlights are already on
Each of those Headlights have a (Relay) inside of them that (wants) a tapped power source that will trigger (Coil-Side) control to (INIATE) the start-up sequence.
With (BOTH) of those (Relays) being on the same (SHARED) power source they get out of sequence. (This is the DELAY)

"Tried again with switch in Auto, got a startup sequence both sides headlights came on after sequence completed. Seems having headlights on will block the startup sequence."

Excerpt from above: This result tells me that in (AUTO) it will (show-visually) display the Start-Up sequence as you are providing the (Tapped-Switched) power with the Headlights (OFF) & when you have the Headlight Switch (Headlight) the Headlights are already (ON) and the Star-Up sequence is (HIIDDEN) not (BLOCKED)

Fact and Proven:
The DRL control (Input) signal is what triggers the Start-Up sequence, this is proven by @Big Blue and for a (Factory- LED) Headlamp housing is Pinned For, thus my initial reasoning as the Halo's & Aftermarkets) are not. The REASON for the Aftermarkets to want Tapped Power

Fact:
Halogen (OEM) - Headlamps are NOT wired for (PIN#6) DRL Control the exact same as the aftermarkets. (Morimoto at this point -CONFIRMED)

Fact:
The only way to get power on (PIN#6) Dedicated DRL circuit is with (FORSCAN) and PROGRAMMING the BCM open that power output this is the (Dedicated DRL) Setting in Forscan it allows Power Output on Pin #6 to power a Dedicated DRL Circuit (LED LIGHTBAR) this moves the DRL power from (LOW BEAM) Pin #2 to Pin #6
When you De-Select the (DRL-Lighting) in the IPC - it's not doing anything but removing the DRL (Output) on Pin #2 (Disabling) the Power Cut (50%) on the Low Beam circuit
This is ONLY & IF you have not changed any BCM programming and are still set up with BCM Control as (Halogen) Headlights, this is the REASON the AFTERMAKETS have you (DE-SELECT) that IPC Menu setting.

If you have changed the BCM settings to Factory LED, and have (ONLY) the BCM to control the DRL's then (De-Selecting) the DRL Lighting turns off Power to Pin#6 instead of (Pin#2)
So, with a Tapped power source & changing the - BCM to Dedicate DRL, the IPC Menu screen will be only affecting the Park Lamp circuit as the BCM has no control of Power for Pin#6, but will affect the (extra's) (+Fogs / +Park Lights)

Fact:
The reason for the (Aftermarkets) to have you (De-Select) the DRL Lighting in the IPC, is to (TURN-OFF) the DRL circuit to the (Low Beams) as that is what the BCM is programmed to do.
Without - BCM Reprogramming of Pin#6 Power, which is also negated as the Headlight Assembly is not wired for (Directly) from the BCM (Tapped Source - Addition)

Fact:
The BCM cannot see (DRL) Lighting is (ON) as you have by-passed its control of it.
via (Tapped-Power) again (Pin#6) Power

Fact:
The Aftermarkets - Do NOT want to sell a product that requires a BCM programming change for them to work - Hense the (Tapped-Power) source.
On a (Bench) and a battery source for Power, this logic works flawlessly, what was (OVERLOOKED) in the operation aspect of the (Start-Up) sequence and what will happen if you (add) another power source on the circuit. (That-ADDED source is the BCM) taking over control of the (Low Beam Power)

Fact:
This is the CONFLICT in (Double) powering the Headlight from 2 separate sources
THIS is the reason for ME pushing to DUMP that Tapped Power
So, with (ZERO) programming changes and removing the (Tapped-Power) the DRL's will never work.

So, this brings us to a crossroad, The BEST WAY to (Bring Power) onto the DRL Circuit

1. Keep it as (IS) and Fuse Tap - Fuse #19
a. This is proven to be an issue, works fine until the BCM pushes power out to the Headlights (Pin#2) Low Beam Circuit.

2. Wire Tap (Pin#6) on the Harmes, anytime the BCM provides power to (Pin#6) the DRL's will light up.
a. This creates an issue with the (Start-Up) sequence function, it will only power when you take the truck out of park and its (Daylight)
b. FIND a (BCM) Programming setting that will allow power output on (Pin#6) when the truck is in (Park) with both (DAY) & (NIGHT) scenarios.
This will simulate - the Fused Tapped - Power
The issue, in the As-Bult files, I do not see any settings that will provide that (power) need.

3. My Theory of (Finding) an alternate (Taped-Power) source and let the (BCM) itself provide the power source.
a. Wire Tap (Pin#5) on the harness side of the connector (Either LEFT or RIGHT) with most of the complaints occurring on the (LEFT) I would try the (RIGHT) first
b, by using the (Park) Lamp circuit as the (Relay) trigger, anytime power is applied to the (Park Lamp) circuit will (Power) the (DRL- Tapped) power source (Pin#6) in the headlight wiring.
c, so this is (STILL) a Tapped Power source but you are (ELIMIMINATING) the (Ignition-Run/Start) relay bringing the power in and using the (BCM) itself to provide the power via the (Park Lamp) circuit.
d. This will cure (I Think) the Start-Up sequence not being seen at (Dark)
e. However, in (Day) the startup sequence will only function when you come out of (PARK)
so, a small caveat - you lose the sequence at start-up in (Day) operation only
f. In (Night/Dark) - operation the (Park-Lamp) powering up will close the added relay and provide the (Start-Up) sequence as the Park Lamps & Low Beams will be commanded on at the (Same Time)
Vs
BCM Powering First and winning the Race throwing the Headlight Relays (Out of Sequence)

I hope this makes sense, and since I do not have aftermarkets, I cannot actually test this out.
I am only going off of - the issues you both have and your findings in your test results thus far.
I am 90% positive that the timing of the (Tapped-Power) source is the cause and thinking that moving it (when its actually applied) will cure the issue and unless I can find the (HIDDEN) BCM As-Built data file that will (power-out) Pin #6 at engine start.
The adding of a relay on the (Park-Lamp) circuit as a (Coil-Side) trigger to close the relay and (Power Pin#6) will be the most logical option
Again - UNTESTED but in theory makes the most sense, as we are talking about (Milliseconds) in Time

So, at this point - Since I have NOT found a (Power Out of Pin#6) solution at engine start so far.
Then YES, it REQUIRES a TAPPED POWER source, and we only need to (Augment) or (Change) when the Tapped Power is (ACTUALLY APPLIED)
That (TIMING) is the cause of the Start-Up Sequence being (Hidden or Delayed)
If I can find a (BCM-Change) that (WILL -POWER) Pin #6 at every engine start and (In-Park)
then the (Tapped) Power source can be removed, and this will let the BCM provide full control.
I do not see that happening from the As-Built settings, so this will have to be a (Play) with Forscan and make changes (and note) if I can get the DRL Circuit to Light Up (Bright) with the Truck in (Park) using only the (BCM-Power Output) from Pin#6 as my Factory LED's have Pin#6 this would be easily noted.
We can then use that (Information) - (Setting-Needed) and transpose that to Wire Tap (Pin#6) in the Factory Harness and (Send that) Tapped source onto the (Aftermarket) Headlamp Assembly.
Again - This will only work if I can find a way to get the (WANTED) Power Output from Pin#6 Engine Running in (PARK) & Day & Night Operation
The Aftermarkets (WILL) function the same as Factory LED including the (ADDED) special effects
(Start-Up Sequence) and (Sequential Turns) if we can achieve this power output (CHANGE)

Since it APPEARS that this is NOT an achievable outcome, then we need to move the (Timing) of when the Tapped Power actually comes in, which is the issue (The Timing) of the Tapped Power,

First I believe the headlight power IS blocking the startup sequence. This is because the sequence happens with just the parking lights on. Also the sequence is just the sequential cycling of individual shutters between high and low beams. If you disable the tapped power the headlights will function normally with the exception of no startup sequence and no bright DRL bars. Parking lights and sequential turns still work.

Oh did I mention that the startup sequence lasts 5-6 seconds.

 

[airline tech]

Be it (Hidden) or (Blocked) I feel it's a timing issue of when the (Tapped Power) is introduced and I am making suggestions here to possibly fix that issue, Will it WORK - IDK, but clearly the current wire set-up is NOT working as the lights are intended to function and I THINK that this is the answer (change when that power comes in) worst case scenario it does not work and produces the exact same outcome as the Fuse #19 source.
This does 2 things, it gives (some control) back to the BCM on when to power and eliminates the external power (introduction) into the light, this way the only way for the (DRL) circuit to be powered the (Park Lamp) circuit must be activated (ON)
The DRL (Power) tap only needs to see a (12-Volt) source, let the BCM control that power and see how it reacts. I have a hunch - it will provide a better functional result.
I could be - WRONG, but with the current set-up not working, I feel this MAY cure the issues.
I wish I had a Morimoto to test my theory.


Here is a simple diagram of what I am talking about
You are still using a (Tapped Power) source and a RELAY, but you are letting the BCM dictate when the power is applied and that is when the BCM turns on the power on Pin#5 (Park Lamp) power.
This should cure the issue of (Improper) Timing from the current wired setup where the (Run/Start) Relay is in control and letting Fuse #19 power after it closes.
With the BCM being direct power - its beating the transition of the (Run/Start) relay getting closed and also the BCM (Can Bus) Data transmission on (Ign Switch) Position (ISP-R)

By moving that (Input) feed (Power-Trigger) to the (Park Lamp) circuit, I THINK that this will provide a (BETTER TIMED) - Power Trigger for the DRL (Start-Up) Sequence

 

[Big Blue]

Here is a simple diagram of what I am talking about
You are still using a (Tapped Power) source and a RELAY, but you are letting the BCM dictate when the power is applied and that is when the BCM turns on the power on Pin#5 (Park Lamp) power.
This should cure the issue of (Improper) Timing from the current wired setup where the (Run/Start) Relay is in control and letting Fuse #19 power after it closes.
With the BCM being direct power - its beating the transition of the (Run/Start) relay getting closed and also the BCM (Can Bus) Data transmission on (Ign Switch) Position (ISP-R)

By moving that (Input) feed (Power-Trigger) to the (Park Lamp) circuit, I THINK that this will provide a (BETTER TIMED) - Power Trigger for the DRL (Start-Up) Sequence

View attachment 229643

OK, if I read you right you are letting the parking lights control a always on power source. Am I correct?

If so, you are going to get a startup sequence anytime the parking lights activate. This will be when you lock/unlock the doors or open any door, just turn on the parking lights on. This thing likes to turn the parking lights on for everything. Not the way I want my headlights to work! I don't want to have to have to add any components and do any extra wiring to make this work, a simple Forscan changes maybe.

As I said before, I really don't have a problem with how they work now, except for the startup issues in dark mode. The DRLs being dim during the day is not and issue to me. It was my choice because I wanted the taillights on with the DRLs.

 

[airline tech]

I also watched the (Headlight Revolution) video
The Start-Up Sequence is this:
DRL - Lit Bright
Headlight Trigger -(Turn ON)- (OB to IB) in 3 phases in Dim
Headlights Pulse - (IB to OB) in 3-Phases to Bright
Headlights Pulse - (OB to IB) in 3 -Phases to Dim
Headlight Trigger -(IB to OB) in 3-Phases to Off

So be it (HIDDEN) or (BLOCKED) when the Headlights are commanded on by BCM we need to find a alternate solution to getting the (DRL-Bright) to activate the Start-Up sequence before the BCM takes control.
This is my reasoning of moving when the (DRL-Power) comes in as a possible solution to the issue.
This theory can only be tested by (adding) a relay into the circuit and letting Park Lamp Power do it.
So YES, the DRL input - must be powered to begin (start) the sequence, if we let the (Park Lamp) input be the trigger it just (MAY) start the sequence up and the end result will (END) with the headlight's on in (DARK)
as for your testing this far has been using (Park Lamps) gets the (Start-Up) sequence to work, but if you go to (Headlamp) position or (Auto) position in the dark, the BCM has already powered the Headlights.

By using the (Park Lamps) Powering as the trigger, may let the (Start-Up) sequence happen before the BCM can take control and turn on the lights.
It is a BATTLE of which RELAY wins the RACE to power the headlight.
Bug's Bunny (The BCM) is winning the race, and we need to slow him down and introduce the (Tortoise) short cut in powering the lights first.

Again, this is all THEORY BASED, but if I had these lights, I would try everything possible to fix the issue, being that this issue is discovered (AFTER) the Time-Consuming install of them.
With Morimoto NOT PROVIDING support for this issue it takes some deep thought on how to fix the issue that they are ignoring and just say (send us the Headlights) for replacement.
I am a Troubleshooter by Trade and this issue can be fixed I believe it's just going to take some time to find the correct way to cure it (By Trial & Error)

You have provided me with some valuable info, and I am looking at this issue from a (power supply) aspect as it is looking like the (As-Built) BCM changes will not provide the power I am looking to have and when it comes in.
I am looking at (alternatives) to changing when & how that power is applied from the actual wiring harness as a possible solution.
Will it make any difference? IDK, but it would be worth a try, no harm to the lights just a small investment in a (relay) and (some wire) and about 30-Minutes to wire it up and mount the relay.

But with Relay (In-Hand) before I would actually Wire-Tap wire #5, I would Back-Probe) the connector first and tap power from that, then proceed with testing to outcome on (Back-Probing) both sides Left & Right to see if there is any time delay (In that circuit) which side will provide the result I want (if it matters) the best.
If successful then do the actual Wire Tap of Pin #5

Sponsored