Config Preset

[SyPol*]

Hi, Polestar user here. Regarding the Pixel lights (106) and AHBL (109) in NA, I change both settings to make it work, but as you know 2  dtc (one for each beam) remain log as "unknow configuration" for AHB if we want to keep the auto function "on" in cluster while returning to car after a shut down. I was wondering if it could be possible to get and install the europeen program and coding and get rid of those false errors using the Config Preset option in Orbit ?  I'm asking because on my  first service of the car at 32k km the mecanic notice those "funny" error and ask me to book another appointment to look at it but knowing what it was I didn't  of course.    The other thing is that for the first time since update P2.4 (now on P2.12) I have to recode (thank's Orbit) all my preferences back to the car.

Thank's !

[LtYoung]

I think the HCML and HCMR codes are set because the modules don't like being addressed as Type 2 while they are Type 1, despite no issues with functionality. Imo the only way to get rid of the DTC is to install euro-spec HCMs

[Power6]

The HCMs and the software between the "Type A" and "Type B" headlights, that I have seen, are the same. The difference is the headlamp units, hence the config item 106 is how the HCMs know what type of headlamp unit to expect.

The "memory" behavior of the AHB function is tied directly to that same config item 106. To be clear, you do not need to change item 106! You can simply change item 109 to enable AHB3 for your Pixel lights. 106 is a "trick" to change to the wrong lights type, in order to enable the memory behavior.

(This is sort of the "reason" why config exists at all! Volvo can build one set of hardware/software in a module, that supports many different hardware configurations)

[Dave]

The HCMs and the software between the "Type A" and "Type B" headlights, that I have seen, are the same. The difference is the headlamp units, hence the config item 106 is how the HCMs know what type of headlamp unit to expect.

The "memory" behavior of the AHB function is tied directly to that same config item 106. To be clear, you do not need to change item 106! You can simply change item 109 to enable AHB3 for your Pixel lights. 106 is a "trick" to change to the wrong lights type, in order to enable the memory behavior.

(This is sort of the "reason" why config exists at all! Volvo can build one set of hardware/software in a module, that supports many different hardware configurations)

Hello,

will resetting HCM and then writing the 106 ROW config get rid of error from the module?

will be changing some settings today.

Thanks!