Used Nettodat coding to fix HID foglights

Bendercle · 05-07-2012, 06:46 PM

First off, thanks to Grant and Rotary Rasp. For those who are not aware there was this thread a while back that showed people how to mess with the NETTODAT.TRC file in order to code in specific voltages that the regular trace file does not allow. People were using it primarily for different Angel Eyes setups. I experimented with it in my own car but didn't really get anywhere.

Fast forward to today I met up with someone having issues with their HID fog light kit. After coding out all the bulb checks per usual the driver's side would still go out after about a minute if the engine was running.

I zeroed in on the line PWM_ANSTEURUNG_NSW as a possible source of the problem. Using NCS Dummy I determined that there were 3 possible values (wert_01, wert_02, wert_03), but 2 lines. Before I started messing with it it was:

PWM_ANSTEURUNG_NSW
wert_02
wert_03

I then tried changing those 2 lines in every possible combination, to no avail. Only thing I managed to change was to get both fog lights to turn off after a minute instead of just one.

Then I remembered the NETTODAT coding. Just like with the angel eyes, I wrote 2 different trace files back with different values for PWM_ANSTEURUNG_NSW and figured out which 2 bits were different using Beyond Compare. Sure enough, they matched up with the voltages in this handy chart. I then started coding in specific voltages, starting from the minimum 5.95V and incrementing upwards. What I saw with the lower voltages was, the fog lights would flicker constantly and not power on fully at all. When I reached 13.0V they behaved like they were before, going out after 1 minute. Then 13.2V, bam, they stayed on! My theory is that the bulbs required higher than what I'm guessing is the stock fog light voltage, 13.0V, and since they weren't getting enough juice they shut off. So in the end everyone was happy and I felt like a badass for getting this through experimentation and experience instead of the usual "copy pasta stuff from the spreadsheet". I do have to thank Rotary Rasp and Grant for the knowledge to accomplish this though, and I leave this story here hoping maybe someone will find it useful.

Elliott@DetailAddict · 05-07-2012, 07:17 PM

Great job! No need to thank... we're here to help!

Bendercle · 05-07-2012, 08:48 PM

Quote:

Originally Posted by cn555ic

I am a bit confused. Everytime I load up the ncsdummy with Nettodat trace file I don't get the numerical values to edit but I get exactly what is in the regular trace file. What am I doing wrong here

I just open Nettodat.trc in Notepad... the old fashioned, stare at a wall of numbers, eyes bleeding way.

VTECaddict · 05-07-2012, 09:35 PM

Thanks for experimenting! This will help a lot of people with 06 and early 07 cars that have been having problems with HID fogs.

Bendercle · 05-07-2012, 09:36 PM

Quote:

Originally Posted by cn555ic

Can you post the NETTODAT trace files values that you edited and the orginal ones with the edited ones in bold if you can...Thanks man I would appreciate this

I could but I'm doubtful it's going to be the exact same place... it's from a 2006 early FRM, pretty risky to just change a Nettodat bit based on someone else's file. What part is giving you trouble doing it with your own?

cn555ic · 05-07-2012, 11:25 PM

Quote:

Originally Posted by Bendercle

I could but I'm doubtful it's going to be the exact same place... it's from a 2006 early FRM, pretty risky to just change a Nettodat bit based on someone else's file. What part is giving you trouble doing it with your own?

Nothing wrong with mine just wanted to see what values you changed. I am not using the data but just curious to see what happened in your case to the NETTODAT trace file

Mark_h · 05-08-2012, 08:58 AM

This is exactly what I was looking for in my thread. Thanks! I'll give it a try later this week.

Mark_h · 05-08-2012, 05:14 PM

Fixed my issues, thanks!

Bendercle · 05-08-2012, 05:45 PM

Quote:

Originally Posted by Mark_h

Fixed my issues, thanks!

Awesome, wasn't expecting anyone to find this useful so quickly!

Volasko · 01-13-2013, 09:15 PM

Everytime I try and change the PWM_ANSTEURUNG_NSW values to something different than 02 & 03 it never seems to actually code the different values? I change the values to something different (eg 01 & 02) and recode the car but after it reads the file and I pull the FRM module again the values are still 02 & 03?!?!

The first time I though I just did something wrong when I couldn't see a difference in the Nettodat files, but after doing it 3-4 times there must have been something up...

Anyone know whats going on? I just coded a bunch of stuff successfully and this has got me stumped.

DESI4life10 · 01-13-2013, 10:26 PM

I suggest you use the "ncs dummy" program to do nettodata coding. Much easier to use in my opinion

Volasko · 01-26-2013, 05:18 PM

Using NCS Dummy's trace editor I figured out what my problem was; there are only two different ways to code the PWM_ANSTEUERUNG_NSW (OP Forgot an E) values; wert_02 & wert_03 OR wert_1. If you try and code 1 & 3 for example it doesn't actually write, this is why I wasn't seeing a difference in my Nettodat file.

Once I got past this I was able to coded my car with the new NETTODAT file with the higher voltages. Problem is that it still doesn't fix the issue I am having, only the driver side fog is coming on?!?!?

From reading the OP's original problem I though my aftermarket Xenon fogs where picky with the voltage going to them. I had tested both fog lights on the driver side and they worked. Anyone know else have this problem? The whole reason I learned how to code was so I could get this to work and now I am officially out of ideas?

AWDBooSTIn90 · 01-23-2015, 03:55 PM

So i had this problem in my 07 coupe 335i. With an early build date (09/2006). I have FRM.

DDM 35w h8 kit in fog lights. They worked great. BUT as soon as i start the engine. They shut off and flicker.

So i followed everything above. I was able to change my voltage from 12.7 which is what its set at from the factory. But it 12.7vdc thats pwm.

So i thought. Ok set it to a higher voltage. I code it through the NETTODAT file. Didnt work.

The key to this working is setting the value to 16 volts. Because what it does is instead of trying to set the voltage using pwm. The ecu sends full voltage available at all times.

Problem fixed.

Now you still have to code out bulb errors, but thats a given.

2088 MSP · 08-24-2016, 04:02 PM

necrobump.

i have a 04/07 with NFRM, and cant seem to find pwm_ansteuerung_nsw at all in my NFRM module. what gives?

Ninja EDIT: pwm ansteuerung is the group name. and then you go hunting for the pwm_nsw for fogs, or which ever bulb ur working on.

SUPER NINJA EDIT: here is teh solution: http://www.e90post.com/forums/showpo...1&postcount=35

05-07-2012, 06:46 PM	#1
Bendercle Banned 17 Rep 263 Posts Drives: 2007 335xi 6MT Join Date: Jan 2012 Location: North Shore MA iTrader: (3)	Used Nettodat coding to fix HID foglights First off, thanks to Grant and Rotary Rasp. For those who are not aware there was this thread a while back that showed people how to mess with the NETTODAT.TRC file in order to code in specific voltages that the regular trace file does not allow. People were using it primarily for different Angel Eyes setups. I experimented with it in my own car but didn't really get anywhere. Fast forward to today I met up with someone having issues with their HID fog light kit. After coding out all the bulb checks per usual the driver's side would still go out after about a minute if the engine was running. I zeroed in on the line PWM_ANSTEURUNG_NSW as a possible source of the problem. Using NCS Dummy I determined that there were 3 possible values (wert_01, wert_02, wert_03), but 2 lines. Before I started messing with it it was: PWM_ANSTEURUNG_NSW wert_02 wert_03 I then tried changing those 2 lines in every possible combination, to no avail. Only thing I managed to change was to get both fog lights to turn off after a minute instead of just one. Then I remembered the NETTODAT coding. Just like with the angel eyes, I wrote 2 different trace files back with different values for PWM_ANSTEURUNG_NSW and figured out which 2 bits were different using Beyond Compare. Sure enough, they matched up with the voltages in this handy chart. I then started coding in specific voltages, starting from the minimum 5.95V and incrementing upwards. What I saw with the lower voltages was, the fog lights would flicker constantly and not power on fully at all. When I reached 13.0V they behaved like they were before, going out after 1 minute. Then 13.2V, bam, they stayed on! My theory is that the bulbs required higher than what I'm guessing is the stock fog light voltage, 13.0V, and since they weren't getting enough juice they shut off. So in the end everyone was happy and I felt like a badass for getting this through experimentation and experience instead of the usual "copy pasta stuff from the spreadsheet". I do have to thank Rotary Rasp and Grant for the knowledge to accomplish this though, and I leave this story here hoping maybe someone will find it useful.
	Appreciate 0 Tweet Quote

05-07-2012, 07:17 PM	#2
Elliott@DetailAddict Brigadier General 309 Rep 4,370 Posts Drives: E90 Join Date: May 2011 Location: Santa Clara, CA iTrader: (0)	Great job! No need to thank... we're here to help!
	Appreciate 0 Quote

05-07-2012, 09:35 PM	#4
VTECaddict Where'd my VTEC go? 487 Rep 6,066 Posts Drives: 06 330i 6MT Join Date: Mar 2009 Location: Seattle, WA iTrader: (4)	Thanks for experimenting! This will help a lot of people with 06 and early 07 cars that have been having problems with HID fogs. __________________ AW/Terra \| ZSP \| ZPP \| ZCW \| iDrive \| CA Mods: BC BR coilovers \| Blacklines \| M-tech rear \| dual exhaust \| M3 steering wheel \| BMW SSK \| ZHP shift knob \| High-kick CF spoiler \| NBT Retrofit M3 front control arms \| M3 rear guide rods \| Manzo rear toe and camber links \| Monroe rear shock mounts \| Varrstoen ES1 19x9.5+20 Front, 19x11+25 rear
	Appreciate 0 Quote

05-08-2012, 08:58 AM	#7
Mark_h New Member 4 Rep 28 Posts Drives: BSM e90 Join Date: Dec 2011 Location: St. Paul, MN iTrader: (0)	This is exactly what I was looking for in my thread. Thanks! I'll give it a try later this week.
	Appreciate 0 Quote

05-08-2012, 05:14 PM	#8
Mark_h New Member 4 Rep 28 Posts Drives: BSM e90 Join Date: Dec 2011 Location: St. Paul, MN iTrader: (0)	Fixed my issues, thanks!
	Appreciate 0 Quote

01-13-2013, 09:15 PM	#10
Volasko Colonel 726 Rep 2,610 Posts Drives: 06 330i E90, 18 530xe G30 Join Date: Dec 2010 Location: Toronto iTrader: (2) Garage List 2018 BMW 530e M Sport [9.00] 2006 BMW E90 330i [8.28]	Everytime I try and change the PWM_ANSTEURUNG_NSW values to something different than 02 & 03 it never seems to actually code the different values? I change the values to something different (eg 01 & 02) and recode the car but after it reads the file and I pull the FRM module again the values are still 02 & 03?!?! The first time I though I just did something wrong when I couldn't see a difference in the Nettodat files, but after doing it 3-4 times there must have been something up... Anyone know whats going on? I just coded a bunch of stuff successfully and this has got me stumped.
	Appreciate 0 Quote

01-13-2013, 10:26 PM	#11
DESI4life10 Banned 203 Rep 3,328 Posts Drives: Coding: Desi4life10@gmail.com Join Date: Oct 2008 Location: West of Toronto, Canada iTrader: (18)	I suggest you use the "ncs dummy" program to do nettodata coding. Much easier to use in my opinion
	Appreciate 0 Quote

01-26-2013, 05:18 PM	#12
Volasko Colonel 726 Rep 2,610 Posts Drives: 06 330i E90, 18 530xe G30 Join Date: Dec 2010 Location: Toronto iTrader: (2) Garage List 2018 BMW 530e M Sport [9.00] 2006 BMW E90 330i [8.28]	Using NCS Dummy's trace editor I figured out what my problem was; there are only two different ways to code the PWM_ANSTEUERUNG_NSW (OP Forgot an E) values; wert_02 & wert_03 OR wert_1. If you try and code 1 & 3 for example it doesn't actually write, this is why I wasn't seeing a difference in my Nettodat file. Once I got past this I was able to coded my car with the new NETTODAT file with the higher voltages. Problem is that it still doesn't fix the issue I am having, only the driver side fog is coming on?!?!? From reading the OP's original problem I though my aftermarket Xenon fogs where picky with the voltage going to them. I had tested both fog lights on the driver side and they worked. Anyone know else have this problem? The whole reason I learned how to code was so I could get this to work and now I am officially out of ideas?
	Appreciate 0 Quote

01-23-2015, 03:55 PM	#13
AWDBooSTIn90 Nomore 158 Rep 793 Posts Drives: 335i Coupe 6MT N54 Join Date: Feb 2014 Location: Long Island iTrader: (1)	So i had this problem in my 07 coupe 335i. With an early build date (09/2006). I have FRM. DDM 35w h8 kit in fog lights. They worked great. BUT as soon as i start the engine. They shut off and flicker. So i followed everything above. I was able to change my voltage from 12.7 which is what its set at from the factory. But it 12.7vdc thats pwm. So i thought. Ok set it to a higher voltage. I code it through the NETTODAT file. Didnt work. The key to this working is setting the value to 16 volts. Because what it does is instead of trying to set the voltage using pwm. The ecu sends full voltage available at all times. Problem fixed. Now you still have to code out bulb errors, but thats a given.
	Appreciate 0 Quote

08-24-2016, 04:02 PM	#14
2088 MSP Private 5 Rep 67 Posts Drives: 07 e90 335i Join Date: Feb 2015 Location: Tallahassee, FL iTrader: (2)	necrobump. i have a 04/07 with NFRM, and cant seem to find pwm_ansteuerung_nsw at all in my NFRM module. what gives? Ninja EDIT: pwm ansteuerung is the group name. and then you go hunting for the pwm_nsw for fogs, or which ever bulb ur working on. SUPER NINJA EDIT: here is teh solution: http://www.e90post.com/forums/showpo...1&postcount=35 Last edited by 2088 MSP; 08-24-2016 at 09:33 PM..
	Appreciate 0 Quote