[dimitrev]

Hey guys,

I've been trying to get my interior lighting (with lights package) to go a little brighter as it is barely visible at this point with the dimmer on max (the instrument lights are ok, but the actual orange interior lights from the lights package are very dim). I changed U_POTI_DIMM_MIN from wert 2 to wert 1 (1V to 1.098V - hardly much of a bump) and U_POTI_DIMM_DELTA the same (3V vs 3.294), together adding up to a miserly almost 0.4V bump. It is a tiny bit better, but only if I'm looking hard. So I decided to dip my feet into custom values coding via nettodat.trc.

I'm ok until the very end of the process (I have my custom value added, and have a NATTODAT.MAN file exported from NCS Dummy) but when I get to the coapiCodeSgByNettoData bit, I notice that it selects the wrong daten files. The first time I was not paying much attention and flashed like that, it completed without errors, but all that happened was that the U_POTI_DIMM_MIN value was just erased from the next FSW_PSW.TRC I read out (and obviously no change to the lighting). I coded it back with a backup, and tried again and that's when I noticed what was happening:

I have an LM2 with the latest part number (manufactured in 2013), but the car is from 2005 (i'm guessing this is somewhere at the root of my issue). For this LM2 the normal daten files that it gets coded with are these:
LM2_E6X.C35, A_E60LM2.IPO, LM_AHL_2.PRG, but when I go to basic functions and try to code with the NETTODATA.MAN file I can see the listed ones are: LM_E60.C0B, A_E60LM2.IPO, LM60.PRG and in the CBD Name field on the coapiCodeSgByNettoData dialogue box I see LM_E60.C0B is prefilled.

Anyone got any ideas as to why this is happening and how to resolve this (my guess is that it may be something to do with the VO and/or the production date of the car, and thus it is trying to code it as if it has the old LM1 still inside- but i'm not sure how to check that).

Thanks in advance!