- Joined
- Oct 7, 2021
- Threads
- 6
- Messages
- 131
- Reaction score
- 101
- Location
- Jalisco, Mexico
- Vehicle(s)
- 2022 Maverick 2.0 AWD
- Engine
- 2.0L EcoBoost
- Thread starter
- #1
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):
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.
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
Last edited: