[pikcachu]

what are your values for:

IHKA 3003 MEMORY_UMLUFT
IHKA 3003 MEMORY_OFF

mine are aktive and nitch_aktiv...

when i set Memory_off to aktive the car will always start with the fan turned off no matter where i left it.... and didn't like it so i put it back to nitch_aktiv

I also see grayed out the auxiliary comfort ventilation but i can set the timers...

[lichenlt]

Originally Posted by pikcachu

Do you have any KAFAS or FLA ecu on your list ?

Looks like I don't have FLA but do have KAFAS2. Is that the same as KAFAS?

[pikcachu]

ya KAFAS2 is the same thing....

see if you can find DFL anywhere in that CAFD

[lichenlt]

Originally Posted by pikcachu

what are your values for:

IHKA 3003 MEMORY_UMLUFT
IHKA 3003 MEMORY_OFF

mine are aktive and nitch_aktiv...

when i set Memory_off to aktive the car will always start with the fan turned off no matter where i left it.... and didn't like it so i put it back to nitch_aktiv

I also see grayed out the auxiliary comfort ventilation but i can set the timers...

I have both set to aktiv, but I'm not concerned about the fan turning on when I start the car, I'm concerned about it turning off when I shut off the engine. It did not do that before coding, so I guess I'll turn it back to nitch_aktiv and see if it stops doing that.

[pikcachu]

what you can do is to remove 5AP from your VO and VO code FEM_BODY and KAFAS2
That's how the car would have come from factory if it hadn't had the 5AP decoded....

there is a catch... when you VO code you will lose all your custom coding on that module... but now your VO won't have 5AP so if your dealer ever updates your car with new version, you will still have the anti-dazle as it's VO coded and VO codes remain...

but if you just do FDL code then if dealer updates your software then all custom coding is gone...

That's why it's always better to do all VO coding first and then FDL coding ... else VO coding will erase any FDL coding...

hope i didn't confuse you too much

[pikcachu]

Originally Posted by lichenlt

I have both set to aktiv, but I'm not concerned about the fan turning on when I start the car, I'm concerned about it turning off when I shut off the engine. It did not do that before coding, so I guess I'll turn it back to nitch_aktiv and see if it stops doing that.

well that's what i'm saying Memoery_off aktive will always make the car start with the whole ventilation turned off.... nomater if you left it on or off before starting....


my car came with it nitch_aktive originally, set it to aktive but didn't like that behavior so set it back to nitch_aktive...

haven't tried changing the air recirculating setting yet which is set to aktive now...

[pikcachu]

another thing i want to try is this:

ICM 3000 C_Wunschgeschw_min_kmh
ICM 3000 C_Wunschgeschw_min_mph

to allow cruise control below 25mph

[lichenlt]

Originally Posted by pikcachu

what you can do is to remove 5AP from your VO and VO code FEM_BODY and KAFAS2
That's how the car would have come from factory if it hadn't had the 5AP decoded....

there is a catch... when you VO code you will lose all your custom coding on that module... but now your VO won't have 5AP so if your dealer ever updates your car with new version, you will still have the anti-dazle as it's VO coded and VO codes remain...

but if you just do FDL code then if dealer updates your software then all custom coding is gone...

That's why it's always better to do all VO coding first and then FDL coding ... else VO coding will erase any FDL coding...

hope i didn't confuse you too much

No you didn't. Thanks for explaining this to me. I appreciate it.

so when I do VO coding 5AP, I should remove 8S4 as well right? just to make the variable light distribution permanent?

[pikcachu]

ya... basically you will modify your FA and remove 5AP and 8S4, save it, write the new FA to your car, then read the FA from your car and VO code whatever module you want (in this case FEM and KAFAS2) the new changes to apply too...

now all FDL coding will be erased and the car will be just like it came out of factory with the new options specified in the FA...

after that ... FDL code any custom coding you had before that got erased
and make sure you don't ever click "Code default values"

also you can save the .ncd before and after so you can compare what where the changes done by VO coding afterwards

[lichenlt]

Originally Posted by lichenlt

I think 68mph is a little high as the upper bound of second tier light pattern, can it be changed to like 50 or 55mph?

Originally Posted by pikcachu

probably this C_AFS_E_V_LO in FEM_BODY

Have you tried to change this? What are the options in the drop down list? The speed would be in Hex value of kph, right? How do I convert it to mph?

[pikcachu]

haven't tried... ya HEX in kph

http://hextodecimal.com/index.php?hex=6e = 110 kph = 68 mph

https://www.google.com/?gws_rd=ssl#q=110kmh+to+mph

[lichenlt]

I removed 5AP and 8S4 and VO coded both FEM_BODY and KAFAS2

The HBA seemed to be working but I couldn't really tell because there was too much traffic. However, HBA briefly turned on even when there was a car in front of me, which happened both on local street and on freeway. I didn't catch if it was just the one on the right or both, but it wouldn't matter to the driver in front me. People will think that I'm flashing them. It's dangerous.

VLD is now working perfectly. The change of light pattern when the speed exceeds 30mph is very obvious now. I see the left low beam moving to the center but couldn't tell if it swiveled vertically as well.

I also did C_AFS_E_V_LO and it turns out there are four other entries similar to this. The description says they are lower speed threshold for light distribution E, E1, E2, E3. I don't know why there's only lower threshold but no higher threshold, but I changed the one that has the equivalent speed of 68mph to 50mph. However, there's already one entry that has this value. Not sure how the computer deals with two same thresholds. Again, on my test drive I couldn't tell if the light distribution pattern changed above 50mph because it wasn't dark enough.

[pikcachu]

i think there is no upper threshold cause it's just 155 by default

you might have to play around with some other entries...to see which one is the one affecting the VLD for highway speed

[lichenlt]

The auto unlock when engine off is only working on driver's door. I think there's another entry that needs to be changed in order to unlock the passenger door.

[lichenlt]

I didn't find MAPPING_TAGFAHRL_V_R_PWM_LEVEL_1 for DRL

Instead, I found these,
MAPPING_TAGFAHRL_V_R_PWM_STANDARD
MAPPING_TAGFAHRL_V_R_PWM_REDUCED
MAPPING_TAGFAHRL_V_R_PWM_REAR
and similarly for the Left side. I changed all of them to 100%. No idea if the brightness actually changed.

[pikcachu]

Originally Posted by lichenlt

The auto unlock when engine off is only working on driver's door. I think there's another entry that needs to be changed in order to unlock the passenger door.

i don't think there is another entry... i think you need to go to idrive - settings - doors - and check to unlock all doors instead of just driver only that you do it

[pikcachu]

Originally Posted by lichenlt

I didn't find MAPPING_TAGFAHRL_V_R_PWM_LEVEL_1 for DRL

Instead, I found these,
MAPPING_TAGFAHRL_V_R_PWM_STANDARD
MAPPING_TAGFAHRL_V_R_PWM_REDUCED
MAPPING_TAGFAHRL_V_R_PWM_REAR
and similarly for the Left side. I changed all of them to 100%. No idea if the brightness actually changed.

Halos with DLR are always 100%
what's not 100% is halos with low beams...

just coded it yesterday...

FEM_BODY 3062 MAPPING_STANDL_V_L_PWM_LEVEL_STANDARD 8% = 08 100% = 64
FEM_BODY 3062 MAPPING_STANDL_V_R_PWM_LEVEL_STANDARD 8% = 08 100% = 64
FEM_BODY 3062 MAPPING_PARKL_V_L_PWM_1_LEFT 8% = 08 100% = 64
FEM_BODY 3062 MAPPING_PARKL_V_R_PWM_2_RIGHT 8% = 08 100% = 64

weird was that just changing the first made the all halos go 100% but did the other 3 just in case...
I think PARK are for when the blinkers are on...

to be able to check this you should turn DRL off on the lighting settings so you can actually see the difference if it's not dark enough the the DRL to be off...

So set DRL to off and put light switch 1 step from off to running lights and compare before the coding... it's really noticable..... halos should be as bright as when DRL is on and also the same when low beams are on

[pikcachu]

Also coded to be able to see full messages while driving...

Display full messages while driving Unknown HU_NBT 3000 OFFICE_MESSAGES_SPEEDLOCK_CONDITION handbrake_or_gearbox_p none

updated cheat sheet

[HX_Guy]

Pikcachu: Did you do any testing with the PDC/camera stuff? I see it on your cheat sheet and I tried it but it doesnt' seem to work. I can activate the rear camera while driving but it only works for 1 second and then shuts off again. My values were not 0F like you sheet says but I changed them to FF and the description changed to UNKNOWN.

I assume the coding is supposed to allow you to view the rear view camera at any speed?

Did I miss one of the settings maybe?

[pikcachu]

0F is the default value...

Did you do all of these?
REM 3203 V_SCHWELLE_2 werte = 0F werte = FF
REM 3203 D_SCHWELLE_2 werte = 0F werte = FF
REM 3203 V_SCHWELLE_1 werte = 0F werte = FF
REM 3203 D_SCHWELLE_1 werte = 0F werte = FF

one is distance limit and the other is speed limit.... distance and speed are set to 255 meters and kmh respectively...

so camera will shut off after 255m

I think if you set it to 00 it will stay on forever... but I don't want to have to press the pdc button everytime to disable after i come out of reverse for example so left it at FF = 255 m

[pikcachu]

Thing is that if you are on the freeway at 80mph 255m about 800 feet will go pretty fast

[HX_Guy]

That's the thing, my default value was not 0F expect for one of them. My defaults were:

V_SCHWELLE_2 werte = 0F
D_SCHWELLE_2 werte = 0A
V_SCHWELLE_1 werte = 24
D_SCHWELLE_1 werte = 32