[SOLVED!] Adjust auto headlight ON delay

[PanchoBarrancas]

UPDATE October 12 2024: SOLVED!

Thanks to user Dynamo, who has found the solution:

Try
726-11-05
5xxx

For my case (but it was in another bit position and before writing here I checked the Maverick spreadsheet), it was 3 by default (and as I can see different AB from different MY22-24 Maverick it's the same - 3)
I tried from 0 to 5 and only five helped me. I put the lamp selector in Auto, cover sensor by my hand, and whoa 1-2 sec - the headlight turned automatically

I have tested this on my truck and it works flawlessly, see video below:

Original post:

Hi, I'm mildly annoyed by the auto headlights taking 15 seconds to turn on when going into a tunnel or parking garage. I know, I have a perfectly functional hand to operate the dial but with a light sensor I might as well tweak it to be faster

Trouble is, I found there is no option in easy mode in the BdyCM in Forscan for that, and after researching the forscan forums and F150 spredsheets everybody says location 726-26-01 is for configuring a slow (15 sencond) or fast (2 second) delay for the light sensor. Quoted from this spreadsheet for the 2020 F-150 (which I found here):

726-26-01	x*xx	xxxx	xxxx	Ambient Light Sensor Present Cfg	0=Not Present, 1=Present
726-26-01	xxx*	xxxx	xxxx	Ambient Light Sensor Type Cfg	0=Slow_FNA (Autolamp Only), 1=Fast_ROW (Autolamp Sunload) Slow_FNA=15 seconds delay turning on headlamps when dark. Fast_ROW=2 seconds delay turning on headlamps when dark.

Problem is, the maverick comes by default with the value set to sensor not present. Weird, as it is obviously there and working just fine. The fact that it is also set to slow_fna is pretty much irrelevant considering the previous point.

Trying to set the sensor present to 1, setting the sensor tyoe to Fast_ROW, or both to present and fast at the same time, results in a failure to write due to incompatible config. Seems like this is completely diferent in the mav.

Any ideas? Has anybody been able to decode the maverick-specific forscan settings?

P.S. I already messed with the Autolamp Delay setting, it doesnt affect the time to auto-ON.

Sponsored

 

[MavRio]

Hi, I'm mildly annoyed by the auto headlights taking 15 seconds to turn on when going into a tunnel or parking garage. I know, I have a perfectly functional hand to operate the dial but with a light sensor I might as well tweak it to be faster

Trouble is, I found there is no option in easy mode in the BdyCM in Forscan for that, and after researching the forscan forums and F150 spredsheets everybody says location 726-26-01 is for configuring a slow (15 sencond) or fast (2 second) delay for the light sensor. Quoted from this spreadsheet for the 2020 F-150 (which I found here):

726-26-01	x*xx	xxxx	xxxx	Ambient Light Sensor Present Cfg	0=Not Present, 1=Present
726-26-01	xxx*	xxxx	xxxx	Ambient Light Sensor Type Cfg	0=Slow_FNA (Autolamp Only), 1=Fast_ROW (Autolamp Sunload) Slow_FNA=15 seconds delay turning on headlamps when dark. Fast_ROW=2 seconds delay turning on headlamps when dark.

Problem is, the maverick comes by default with the value set to sensor not present. Weird, as it is obviously there and working just fine. The fact that it is also set to slow_fna is pretty much irrelevant considering the previous point.

Trying to set the sensor present to 1, setting the sensor tyoe to Fast_ROW, or both to present and fast at the same time, results in a failure to write due to incompatible config. Seems like this is completely diferent in the mav.

Any ideas? Has anybody been able to decode the maverick-specific forscan settings?

P.S. I already messed with the Autolamp Delay setting, it doesnt affect the time to auto-ON.

Man, I’m in the same dilemma. I’ve changed the autolamp settings in the BdyCM. But nothing happened.
I talked to the dealer since the settings available in the dash don’t work as well. It seems a software bug. I have an appointment with the dealer service next week. I will share here if I find the solution.

 

[EONR24]

 

[PanchoBarrancas]

Ohhh, so that actually works?
Sorry, I'm not sure if I understand the instructions for 726-14-01, so in the 2 asterisks positions I need to input the milliseconds converted to hex?

 

[EONR24]

Ohhh, so that actually works?
Sorry, I'm not sure if I understand the instructions for 726-14-01, so in the 2 asterisks positions I need to input the milliseconds converted to hex?

I have not tested it. Let me try to link a hex to number value converter and look at the other fords that have this figured out. I can also give this a test in my garage probably as it is dark enough to kick on the headlights.

 

[PanchoBarrancas]

Actually these pictures below match more what you are looking for than the first pictures I posted.

I would guess this is the change you should make based on these pictures and the f150 threads.

726-11-05
1xxx
Change the First digit to a 1. (it should be 0 from the factory)

726-11-04
xxxx-Dxxx-xxxx
It should be D from the factory.

Thanks, I'll try it tomorrow, I use a big ole 3 D-cell maglite with an LED bulb as my artificial sun inside my garage lol.

 

[EONR24]

Hey there is a setting the cluster under vehicle settings and under lighting that adjusts auto headlight delay. No need to use forscan.

 

[PanchoBarrancas]

Hey there is a setting the cluster under vehicle settings and under lighting that adjusts auto headlight delay. No need to use forscan.

That's for the delay to turn them off after you lock the truck, not for when you get into a long tunnel and have to wait 15 seconds for the lights to come on.

 

[EONR24]

That's for the delay to turn them off after you lock the truck, not for when you get into a long tunnel and have to wait 15 seconds for the lights to come on.

ah I see!

 

[PanchoBarrancas]

Hey there

Thanks, I'll try it tomorrow, I use a big ole 3 D-cell maglite with an LED bulb as my artificial sun inside my garage lol.

Hello again, I couldn't really do the tests before, now I've made these changes and nothing changed lol, I rolled back the BCM to the previous as-built data just in case.

Where did you get your list of possible codes? Is it possible to learn tis power? Lol I'd be willing to experiment with different things on my own and report back if I succeed for you to add to your forscan masterlist

 

[EONR24]

Hey there

Hello again, I couldn't really do the tests before, now I've made these changes and nothing changed lol, I rolled back the BCM to the previous as-built data just in case.

Where did you get your list of possible codes? Is it possible to learn tis power? Lol I'd be willing to experiment with different things on my own and report back if I succeed for you to add to your forscan masterlist

LIVNITUP SPEADSHEET

I have been using this spreadsheet to try to decode information and figure out forscan mods. Ill look through it again and try to find where this delay is stored in the BCM

 

[PanchoBarrancas]

LIVNITUP SPEADSHEET

I have been using this spreadsheet to try to decode information and figure out forscan mods. Ill look through it again and try to find where this delay is stored in the BCM

Thank you, I'll take a peek and report anything I find.

 

[EONR24]

 

[EONR24]

 

[EONR24]

Sponsored