|
|
|
|
|
|
BMW Garage | BMW Meets | Register | Today's Posts | Search |
|
BMW 3-Series (E90 E92) Forum
>
OBD coded angel eyes and digital speed gauge
|
|
03-01-2011, 08:00 AM | #24 |
Mmmm torque
19
Rep 318
Posts
Drives: Like a Boss, hard and fast
Join Date: Jun 2010
Location: Livermore, CA
|
Hey DimSum, what module and option is it in? I'd like to bump my AE voltage up as well.
__________________
Monaco Blue E90 328i with Nav, Sport, Premium and Comfort Access packages, 6FL with iPod cable
SAE spec Depo with HIDs and HID fogs Depo AE replacement Album |
Appreciate
0
|
03-01-2011, 10:29 AM | #25 |
Banned
245
Rep 966
Posts
Drives: F30 335i M sport
Join Date: Aug 2009
Location: Orlando, FL
|
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
|
03-01-2011, 10:47 AM | #26 |
Mmmm torque
19
Rep 318
Posts
Drives: Like a Boss, hard and fast
Join Date: Jun 2010
Location: Livermore, CA
|
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.
__________________
Monaco Blue E90 328i with Nav, Sport, Premium and Comfort Access packages, 6FL with iPod cable
SAE spec Depo with HIDs and HID fogs Depo AE replacement Album |
Appreciate
0
|
03-01-2011, 02:51 PM | #27 |
Private First Class
8
Rep 117
Posts |
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?
|
Appreciate
0
|
04-28-2011, 12:19 AM | #28 |
Lieutenant
43
Rep 437
Posts
Drives: 2011 E92 335i AW
Join Date: Jan 2010
Location: Earth
|
|
Appreciate
0
|
04-28-2011, 07:45 AM | #29 |
Banned
245
Rep 966
Posts
Drives: F30 335i M sport
Join Date: Aug 2009
Location: Orlando, FL
|
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
|
Bookmarks |
|
|