[SilverII]

Does anyone know if we can disable the DRL LED on LCI e92 from dimming when turning on the headlights? I'd think it would look hot at night with the LED at full power around the projectors.

[dryicerx]

I was actually wondering the same thing, would be awesome if possible.

Doesn't appear to be an option on Neutrino45's spreadsheet, it just may have not been stumbled upon yet...

[tldoxmf87]

we need to figure this out..

[Toad335]

I searched through NFRM and found all of the following references to SL (the angel eyes?). A lot of them are also related to corner delete mod, so SL might be the turn signals...A couple sound promising, but I'm going to need someone with more coding experience/german to translate. The first two seem the most promising to me, as they refer to SL with high (FL) and low (AL) beams, and there are a number of options to choose = brightness??

The other one that sounds cool, though unrelated, is SIGNALBILD_SL. Has options for one or both lights. Wondering if this is like the Audi's that it turns off the AE when you are using your turn signal on one or both sides...

PWM_SL_V_BEI_AKTIVEN_AL
wert_01 value 01
wert_02 value 02
* wert_03 value 03
wert_04 value 04
wert_05 value 05
wert_06 value 06

PWM_SL_V_BEI_AKTIVEN_FL
wert_01 value 01
wert_02 value 02
* wert_03 value 03
wert_04 value 04
wert_05 value 05
wert_06 value 06

IGR_MIT_SL_AL
* nicht_aktiv not active
aktiv active

SL_PARKL_ABSCH_12H
nicht_aktiv not active
* aktiv active

SL_ABSCH_OHNE_ECE
nicht_aktiv not active
* aktiv active

OPTIONEN_SL_ABSCH_TFL_FLC
nicht_aktiv not active
* aktiv active

PWM_SL_V
wert_01 value 01
wert_02 value 02
* wert_03 value 03
wert_04 value 04
wert_05 value 05

NSW_FKT_SL
aktiv active
* nicht_aktiv not active

HECKKL_SL_LOGIK
aktiv active
* nicht_aktiv not active

PARKLICHT_MIT_SL_V
aktiv active
* nicht_aktiv not active

PO_RL_FKT_MIT_SL_V
* aktiv active
nicht_aktiv not active

SIGNALBILD_SL
* nicht_aktiv not active
sl_1
sl_2
sl_1_und_sl_2

SL_SCHALT_UMSCHALT_OPT
wert_00 value 00
wert_01 value 01
* wert_02 value 02
wert_03 value 03

[tldoxmf87]

Found a solution (not a coding solution though) in the forum..!
http://www.n54tech.com/forums/showthread.php?t=11714

[Toad335]

Originally Posted by tldoxmf87

Found a solution (not a coding solution though) in the forum..!
http://www.n54tech.com/forums/showthread.php?t=11714

I'm not into shorting wires on my harnesses. Would rather do it via coding. Must be possible, given the number of things that are...

[Toad335]

Anyone do any more playing around with this? I haven't had time.

[Toad335]

Wondering if anyone has found a solution yet.

[Elliott@DetailAddict]

The answer is in recoding using non-standard variables. (NETTODAT)

[matrix76]

I believe the reference to the AE's is RL (ringlight)

Information provide to me via another member,

Originally Posted by Knob

You should look for something like PWM_AN_SL_V_AL_1 or
PWM_ANSTEUERUNG_RL_BL_1 (RL = ringlight), it´s probably wert_02 or something, change it to wert_01... I don´t know if that works..

[Toad335]

Originally Posted by Grant@DetailAddict

The answer is in recoding using non-standard variables. (NETTODAT)

Do you have the detailed answer, or just know that it can be done using this method but don't actually know how?

[Elliott@DetailAddict]

Yes I do actually know how
Basically read your NFRM/FRM. Then take the NETTODAT file and make a copy to compare from.
Now change the AE wert_06 or whatever it is and change it to wert_01 and recode the car.
Now read the module again and compare this NETTODAT file to the last.
You'll find 2 bytes (values) that changed.
Then you change them:
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]
Save this NETTODAT and recode using the NETTODAT instead of the normal MAN file.
PM me if you'd like more help.
Be VERY careful upping the voltages.
Cheers

[matrix76]

Originally Posted by Grant@DetailAddict

Yes I do actually know how
Basically read your NFRM/FRM. Then take the NETTODAT file and make a copy to compare from.
Now change the AE wert_06 or whatever it is and change it to wert_01 and recode the car.
Now read the module again and compare this NETTODAT file to the last.
You'll find 2 bytes (values) that changed.
Then you change them:
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]
Save this NETTODAT and recode using the NETTODAT instead of the normal MAN file.
PM me if you'd like more help.
Be VERY careful upping the voltages.
Cheers

Can you confirm that this" PWM_ANSTEUERUNG_RL_BL_1" is the actaul file in question that the "wert" is changed or do you know the specific file in question?

[Elliott@DetailAddict]

Yes those are the angel eyes.

[Toad335]

Originally Posted by Grant@DetailAddict

Yes I do actually know how
Basically read your NFRM/FRM. Then take the NETTODAT file and make a copy to compare from.
Now change the AE wert_06 or whatever it is and change it to wert_01 and recode the car.
Now read the module again and compare this NETTODAT file to the last.
You'll find 2 bytes (values) that changed.
Then you change them:
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]
Save this NETTODAT and recode using the NETTODAT instead of the normal MAN file.
PM me if you'd like more help.
Be VERY careful upping the voltages.
Cheers

Very interesting! Thanks for sharing the detailed response. Now off to do a little comparing to see if I can figure this out.

[tldoxmf87]

This looks promising.
If someone can post if it really worked and a step by step guide, that would be great.
I get everything but am a little confused on 'Then you can change them: ... ... '.
Do we use the exact values listed on the post and ignore the 2 bytes that changed? Or is this something that would differ depending on values changed?

Also not really sure how to 'recode using the NETTODAT instead of the normal MAN file.'

[Elliott@DetailAddict]

The 2 bytes that change are just used to identify the string of numbers that show you it corresponds to the AE's.

Then replace the bytes that changed with the ones listed.

Then rather than using the FSW use "coapiCodeSqByNettoData".

[tldoxmf87]

Originally Posted by Grant@DetailAddict

The 2 bytes that change are just used to identify the string of numbers that show you it corresponds to the AE's.

Then replace the bytes that changed with the ones listed.

Then rather than using the FSW use "coapiCodeSqByNettoData".

Thanks! I'll try it later this week when I have time!

[Rotary Rasp]

Originally Posted by tldoxmf87

Thanks! I'll try it later this week when I have time!

did you get it to work?

[tldoxmf87]

No I tried but failed.. because I don't know how to compare the NETTODAT.
The NETTODAT has hundreds of values so I'm not sure if I have to be looking at everything one by one to compare them..
I might try later again.

[Rotary Rasp]

bummer

[GtiGyver]

Dude, use "beyond compare".

Originally Posted by tldoxmf87

No I tried but failed.. because I don't know how to compare the NETTODAT.
The NETTODAT has hundreds of values so I'm not sure if I have to be looking at everything one by one to compare them..
I might try later again.