|
|
|
|
|
|
BMW Garage | BMW Meets | Register | Today's Posts | Search |
|
BMW 3-Series (E90 E92) Forum
>
Nettodat Coding not working - what could be wrong ??
|
|
10-11-2012, 05:46 PM | #1 |
Private First Class
18
Rep 192
Posts
Drives: 2011 328i AW/ 2013 128i AW
Join Date: Jun 2012
Location: Phoenix, AZ
|
Nettodat Coding not working - what could be wrong ??
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 |
10-12-2012, 01:18 AM | #3 |
Private First Class
18
Rep 192
Posts
Drives: 2011 328i AW/ 2013 128i AW
Join Date: Jun 2012
Location: Phoenix, AZ
|
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) |
Appreciate
0
|
10-12-2012, 10:36 AM | #5 | |
Private First Class
18
Rep 192
Posts
Drives: 2011 328i AW/ 2013 128i AW
Join Date: Jun 2012
Location: Phoenix, AZ
|
Quote:
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 |
|
Appreciate
0
|
10-12-2012, 12:50 PM | #6 | |
441
Rep 18,331
Posts |
Quote:
|
|
Appreciate
0
|
10-12-2012, 02:58 PM | #7 | |
Private First Class
18
Rep 192
Posts
Drives: 2011 328i AW/ 2013 128i AW
Join Date: Jun 2012
Location: Phoenix, AZ
|
Quote:
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 |
|
Appreciate
0
|
10-12-2012, 09:09 PM | #9 |
Private First Class
18
Rep 192
Posts
Drives: 2011 328i AW/ 2013 128i AW
Join Date: Jun 2012
Location: Phoenix, AZ
|
|
Appreciate
0
|
Bookmarks |
|
|