OBD coded angel eyes and digital speed gauge

DimSum · 02-28-2011, 07:34 PM

I've done the voltage change in the Angel Eyes! It is much brighter indeed!

The_DDub · 03-01-2011, 08:00 AM

Quote:

Originally Posted by DimSum

I've done the voltage change in the Angel Eyes! It is much brighter indeed!

Hey DimSum, what module and option is it in? I'd like to bump my AE voltage up as well.

xxxjecxxx · 03-01-2011, 10:29 AM

for the digital speed and changing voltage for AE there is a post around here with more information than one can consume in a day...

The_DDub · 03-01-2011, 10:47 AM

Quote:

Originally Posted by xxxjecxxx

for the digital speed and changing voltage for AE there is a post around here with more information than one can consume in a day...

Too true, also your awesome thread is full of help me with my computer not being recognized by the cable so useful info gets buried and lost pretty quickly. I checked the spreadsheet copy and it doesn't show the FRM/NFRM value, at least not as of yesterday.

rubdom · 03-01-2011, 02:51 PM

Quote:

Originally Posted by The_DDub

Too true, also your awesome thread is full of help me with my computer not being recognized by the cable so useful info gets buried and lost pretty quickly. I checked the spreadsheet copy and it doesn't show the FRM/NFRM value, at least not as of yesterday.

Agreed! I have been following that thread from day 1 and I don't know where this info is. Can anyone help with this or update the spreadsheet?

anthoj · 04-28-2011, 12:19 AM

Quote:

Originally Posted by rubdom

Agreed! I have been following that thread from day 1 and I don't know where this info is. Can anyone help with this or update the spreadsheet?

+1

xxxjecxxx · 04-28-2011, 07:45 AM

this was posted by onebadmofo

Coding non-standard values and voltages through nettodat.trc

This is my first draft of the guide. I will update it as-we-go.

So how can you shove data you want into the NCS if it's not letting you?
We try to outsmart it.

Our example is my car, 2007 E92 335i.
I have this value

PWM_ANSTEUERUNG_RL_BL_1
wert_06

These are my front (1) "ring lights" (RL).

1. We read the FRM and set nettodat.trc file aside.
2. We change the value from wert_06 to wert_01 and code the car (Not necessarily wert_01, just any other value from stock)
3. Read the FRM again and compare the two nettodat.trc files.
4. Look for two bytes that are different. Here are the possible voltages

00 10 // [0,0V]
55 05 // [5,95V]
DD 05 // [6,6V]
21 06 // [6,9V]
10 09 // [10,2V]
F4 09 // [11,2V]
D7 0A // [12,2V]
49 0B // [12,7V]
8D 0B // [13,0V]
BB 0B // [13,2V]
FF 0B // [13,5V]
2C 0C // [13,7V]
38 0E // [16,0V]

and so on, here's formula to calculate your own values

http://dl.dropbox.com/u/417229/PWM.jpg

5. Basic function - coapiCodeSqByNettoData .
6. If everything is fine the value will DISAPPEAR from the trace files now. The only way to see it again is to code blank MAN file which will revert everything back to stock in the FRM module.

Now you need to understand that the bulbs, wiring, housings or the FRM itself were never designed with 16 volts in mind. Be very careful!

You can do it with every damn string in the trace files, that's how the VIM was defeated I believe.

02-28-2011, 07:34 PM	#23
DimSum Banned 230 Rep 2,740 Posts Drives: SLOW Join Date: May 2008 Location: LITTLEBIMMER.COM iTrader: (10)	I've done the voltage change in the Angel Eyes! It is much brighter indeed!
	Appreciate 0 Quote

03-01-2011, 10:29 AM	#25
xxxjecxxx Banned 245 Rep 966 Posts Drives: F30 335i M sport Join Date: Aug 2009 Location: Orlando, FL iTrader: (1) Garage List 2013 BMW 335i [0.00] 2006 BMW 325i [0.00]	for the digital speed and changing voltage for AE there is a post around here with more information than one can consume in a day...
	Appreciate 0 Quote

04-28-2011, 07:45 AM	#29
xxxjecxxx Banned 245 Rep 966 Posts Drives: F30 335i M sport Join Date: Aug 2009 Location: Orlando, FL iTrader: (1) Garage List 2013 BMW 335i [0.00] 2006 BMW 325i [0.00]	this was posted by onebadmofo Coding non-standard values and voltages through nettodat.trc This is my first draft of the guide. I will update it as-we-go. So how can you shove data you want into the NCS if it's not letting you? We try to outsmart it. Our example is my car, 2007 E92 335i. I have this value PWM_ANSTEUERUNG_RL_BL_1 wert_06 These are my front (1) "ring lights" (RL). 1. We read the FRM and set nettodat.trc file aside. 2. We change the value from wert_06 to wert_01 and code the car (Not necessarily wert_01, just any other value from stock) 3. Read the FRM again and compare the two nettodat.trc files. 4. Look for two bytes that are different. Here are the possible voltages 00 10 // [0,0V] 55 05 // [5,95V] DD 05 // [6,6V] 21 06 // [6,9V] 10 09 // [10,2V] F4 09 // [11,2V] D7 0A // [12,2V] 49 0B // [12,7V] 8D 0B // [13,0V] BB 0B // [13,2V] FF 0B // [13,5V] 2C 0C // [13,7V] 38 0E // [16,0V] and so on, here's formula to calculate your own values http://dl.dropbox.com/u/417229/PWM.jpg 5. Basic function - coapiCodeSqByNettoData . 6. If everything is fine the value will DISAPPEAR from the trace files now. The only way to see it again is to code blank MAN file which will revert everything back to stock in the FRM module. Now you need to understand that the bulbs, wiring, housings or the FRM itself were never designed with 16 volts in mind. Be very careful! You can do it with every damn string in the trace files, that's how the VIM was defeated I believe.
	Appreciate 0 Quote