[sid21177]

So I have a 2011 E90 with halogen lamps and AEs
I wanted to increase the AE brightness, and I read/was told that I would have to code via nettodat to achieve that.

I got the nettodat.trc for my NFRM module using the FSW PSW profile.
The hex values for PWM_SL_1_FKT_BL_TFL & PWM_SL_1_FKT_SL_TFL were showing as 10,00
I used NCS Dummy to update them to 0C,2C and create the nettodat.man file (A compare shows the change correctly)

I used the normal procedure for coding, except selecting coapiCodeSgByNettoData as the basic function (supplying nettodat.man as the value for the Nettodatenliste parameter)
The jobname was kept as SG_CODIEREN while executing the job, which completed successfully.

However, when I read back the NFRM module to confirm the changes, the nettodat.trc file shows the old values 10,00 for both keys.

What could I be doing wrong ??
I've used both the FSW PSW & revtor expertmode profiles and the result is the same.

Is it not sticking coz I have halogen headlamps ??
Please help

[Coding@DetailAddict]

Are you using stock AE bulbs? If you are using LUX or other LED's it won't work.

[sid21177]

Stock AE bulbs, no change to any hardware of the car.

The only thing i found different was that when I used the expert mode profile, I got a popup after selecting the NFRM ecu, it showed the CBD as FRM2_E89.C08, which I changed to FRM3_E89.C32 (the one that was being used while doing the standard MAN coding)

[cn555ic]

There is your problem. Don't use the expertmode. Also use the frm module after the one that changes at the end when you get the nettodAt file. Use the module name to edit

[sid21177]

Originally Posted by cn555ic

There is your problem. Don't use the expertmode. Also use the frm module after the one that changes at the end when you get the nettodAt file. Use the module name to edit

Ok, I did try the normal mode, and it didnt work as well
The module name changed from FRM2_E89.C08 to FRM3_E89.C32 when the nettodat file was created after reading the NFRM ecu.

So you're saying that when I get the popup after selecting the nettodat basic function, I should update the module name to FRM3_E89.C33 (or greater) ??

My DATEN folder does not have anything greater than .C32 though

[cn555ic]

Originally Posted by sid21177

Ok, I did try the normal mode, and it didnt work as well
The module name changed from FRM2_E89.C08 to FRM3_E89.C32 when the nettodat file was created after reading the NFRM ecu.

So you're saying that when I get the popup after selecting the nettodat basic function, I should update the module name to FRM3_E89.C33 (or greater) ??

My DATEN folder does not have anything greater than .C32 though

Hmmm then maybe you need the newest daten files as I dont think I have the C33 files either....If thats the case then you cannot code it in until you get the updated files for your FRM3

[sid21177]

Originally Posted by cn555ic

Hmmm then maybe you need the newest daten files as I dont think I have the C33 files either....If thats the case then you cannot code it in until you get the updated files for your FRM3

Ah ok.
If I update my daten files so that a version greater than C32 is available, wouldn't that version get picked by default ??, just like the latest version C32 is currently getting picked up

[sohcpunk]

Why were they set to 10,00? That means they are both off for full bright and dim.

[sid21177]

Originally Posted by sohcpunk

Why were they set to 10,00? That means they are both off for full bright and dim.

I have no idea, the keys were set to wert values, and when I looked thru NCS dummy they corresponded to 10,00.

They do come on though as DRLs & with the headlights.

[cn555ic]

You need spdaten V47 as I have V46 and I don't have that specific file. You must have the latest software from the dealer