forscan \ Glarefree headlight question

[swoop1156]

Assuming I could also test this out though I have no fog lights on my switch, but it still is functional on/off.

 

[Copp5]

My ‘23 R does this exact same thing with AG enabled and fogs on.

My previous ‘22 Raptor did not do this with fogs on, which seems weird to me.

Granted, I have not enabled ‘Bambi mode’ on my R, but it seems you have and it hasn’t changed anything. Wonder what’s different on the R’s vs the other Gen 3s?

I shut bambi mode off on mine and they work as intended, shuts fogs (the ones on headlight switch) on and off as the lights ramp up. But I can run the aux 1 fog lights with no issue. So I ordered a harness from @Specialtyperformanceparts to put all 4 fogs on the aux 1 switch, Thinking I should be able to get it all to work that way. Don't want to give up the AG much better feature, especially on the rural roads.

 

[GT4ME]

I shut bambi mode off on mine and they work as intended, shuts fogs (the ones on headlight switch) on and off as the lights ramp up. But I can run the aux 1 fog lights with no issue. So I ordered a harness from @Specialtyperformanceparts to put all 4 fogs on the aux 1 switch, Thinking I should be able to get it all to work that way. Don't want to give up the AG much better feature, especially on the rural roads.

So turning Bambi mode off has the headlights gradually turning on and off again as they should (while turning off the main headlight switch fogs)? I do not have Bambi mode enabled and am encountering a more abrupt on/off of my high beams rather than the gradual on/off.

 

[Copp5]

So turning Bambi mode off has the headlights gradually turning on and off again as they should (while turning off the main headlight switch fogs)? I do not have Bambi mode enabled and am encountering a more abrupt on/off of my high beams rather than the gradual on/off.

My first go around with it I had bambi mode activated from the start. I wanted to be able to run all fogs and AG at the same time, but I noticed with bambi mode it then made the AG system act up like in the 2 videos I posted. This is my first go around with forscan so I might not be the most helpful, but this is what I experienced

Bambi mode ON-
w/ fogs ON = abrupt change, w/ fogs OFF = gradual change.

Bambi mode OFF-
AG automatically kills the HS fogs as the lights ramp up , but I can run the aux 1 fogs full time without issue.

It seems something about the system doesn't like the fogs on the HS (at least with mine).

double and triple check values, make sure you RESET the APIM after changes.

 

[GT4ME]

My first go around with it I had bambi mode activated from the start. I wanted to be able to run all fogs and AG at the same time, but I noticed with bambi mode it then made the AG system act up like in the 2 videos I posted. This is my first go around with forscan so I might not be the most helpful, but this is what I experienced

Bambi mode ON-
w/ fogs ON = abrupt change, w/ fogs OFF = gradual change.

Bambi mode OFF-
AG automatically kills the HS fogs as the lights ramp up , but I can run the aux 1 fogs full time without issue.

It seems something about the system doesn't like the fogs on the HS (at least with mine).

double and triple check values, make sure you RESET the APIM after changes.

I misspoke, I did have Bambi mode enabled - disabling it gave me the results you’re seeing as well.

Must’ve been falling asleep while coding in my mods the other week.

 

[spack]

Do gen2's support glare free through Forscan, or is this only gen3 hardware?

 

[JakeMate]

Did this change last night. Seems to be working although I am getting a message at startup about Checking the Headlight system. A quick question about the last line of code below with the 'HCM 734-01-04 xx56 D1--'. I believe mine read 'A1D1', not 'D1--'. With that said, I only changed the '56' in that line of code and nothing in the 'D1' portion. Is that correct? Am I supposed to change mine to '0056 D1D1' or '0056 D1--' with the 2 dashes?? Just need help with that last line of code.

You can see the DTC error in the last image. I tried clearing it but it stays.

 

[socal raptor]

I have a 24 Raptor R and been trying to do this mod. I was successful with my 22, but HCM 734-01-04 does not exist on my 24. It stops at 734-01-02. I have a "white auto" sign not green, but I can see glare free in the menu. I have a feeling the 24 glare free settings are different. When I try to change 734-01-01 and 734-01-02 I get an error every time of "writing blocks failed - incompatible configuration"

edit* adding on to this. When I make a change to certain modules and write it, everything looks and saves correctly, but when I go back to the module it reverts back to the original. This is happening with the SCCM for for glare free both with the as built and not

 

[aFallenTree]

I have a 24 Raptor R and been trying to do this mod. I was successful with my 22, but HCM 734-01-04 does not exist on my 24. It stops at 734-01-02. I have a "white auto" sign not green, but I can see glare free in the menu. I have a feeling the 24 glare free settings are different. When I try to change 734-01-01 and 734-01-02 I get an error every time of "writing blocks failed - incompatible configuration"

edit* adding on to this. When I make a change to certain modules and write it, everything looks and saves correctly, but when I go back to the module it reverts back to the original. This is happening with the SCCM for for glare free both with the as built and not

I’ve also noticed this on my 24’. Haven’t had time to dig into it further or reach out to forscan to work with them on it. Keep us updated if you make a breakthrough.

 

[cwh]

I have a 24 Raptor R and been trying to do this mod. I was successful with my 22, but HCM 734-01-04 does not exist on my 24. It stops at 734-01-02. I have a "white auto" sign not green, but I can see glare free in the menu. I have a feeling the 24 glare free settings are different. When I try to change 734-01-01 and 734-01-02 I get an error every time of "writing blocks failed - incompatible configuration"

edit* adding on to this. When I make a change to certain modules and write it, everything looks and saves correctly, but when I go back to the module it reverts back to the original. This is happening with the SCCM for for glare free both with the as built and not

I read in another forum that the 24’s don’t have glare free option. Be curious if they are wrong and you figured this out.