NCS Dummy - Taking the expert out of NCS Expert

[AlKiz]

AlKiz: The solution is in the error message: Make sure chassis and module match those of the trace file. You should select the module displayed by NCS Expert AFTER reading the trace file. For more information, see chapter 6.1 of the NCS Dummy user manual.

I do select AFTER reading the trace file. Error.
I did select BEFORE reading the trace file. Error.
SP-Daten 2.50.2 FULL.
I read instruction, but not understand this error.

Thank you.

- - - Updated - - -

I have TeamViewer. Can you look?

[revtor]

AlKiz: What happens if you let NCS Dummy detect the module using the "Filter" > "Filter Modules by Trace File..."? More information about filtering by trace files in the NCS Dummy user manual chapter 3.6.

If you can't get it to work, can you (7-)zip the "NCSEXPER\DATEN\E70\" folder and mail it to me () along with the "FSW_PSW.TRC" and (if possible) the "NETTODAT.TRC" trace files?

[AlKiz]

If you can't get it to work, can you (7-)zip the "NCSEXPER\DATEN\E70\" folder and mail it to me () along with the "FSW_PSW.TRC" and (if possible) the "NETTODAT.TRC" trace files?

e70.zip+TRC mail to you. NETTODAT after 9.11.13, if will need

Thank you.

[AlKiz]

i did mail e70.zip and FSW_PSW.TRC. NETTODAT.TRC will mail after 9.11.13, if need.

Thank you.

- - - Updated - - -

Thanks, revtor. All is well.

[Luke Stutz]

i have gotten the trace files for every moduale on my car. loaded my aibag module trace file and it worked great but with every other file i try to load with ncs dummy i get this error.

[ ] 12:25:17 NCS Dummy 0.6.0.1 log cleared.
[E] 12:25:23 An error occurred while reading "C:\NCS TRACE FILES\ASC\E36-ASCT.C05-FSW_PSW.TRC": Unresolved function keyword "WARNUNG_TEMPERATUR". Make sure chassis and module match those of the trace file.
[ ] 12:25:33 Loaded module "BC5.C25" with 10 functions and 1 unoccupied block.
[E] 12:25:33 An error occurred while reading "C:\NCS TRACE FILES\BCV\E36-BC5.C25-FSW_PSW.TRC": Unresolved function keyword "WARNUNG_TEMPERATUR". Make sure chassis and module match those of the trace file.
[ ] 12:25:41 Loaded module "EWS.C02" with 8 functions and 1 unoccupied block.
[E] 12:25:41 An error occurred while reading "C:\NCS TRACE FILES\EWS\E36-EWS.C02-FSW_PSW.TRC": Unresolved function keyword "WARNUNG_TEMPERATUR". Make sure chassis and module match those of the trace file.
[ ] 12:25:49 Loaded module "GM4.C03" with 48 functions and 5 unoccupied blocks.
[E] 12:25:49 An error occurred while reading "C:\NCS TRACE FILES\GM4\E36-GM4.C03-FSW_PSW.TRC": Unresolved function keyword "WARNUNG_TEMPERATUR". Make sure chassis and module match those of the trace file.
[ ] 12:26:00 Loaded module "FGR2.C04" with 2 functions and 2 properties.
[E] 12:26:00 An error occurred while reading "C:\NCS TRACE FILES\GR2\E36-FGR2.C04-FSW_PSW.TRC": Unresolved function keyword "WARNUNG_TEMPERATUR". Make sure chassis and module match those of the trace file.
[ ] 12:26:12 Loaded module "IHKA_E36.C01" with 15 functions and 3 unoccupied blocks.
[E] 12:26:12 An error occurred while reading "C:\NCS TRACE FILES\IHA\E36-IHKA_E36.C01-FSW_PSW.TRC": Unresolved function keyword "WARNUNG_TEMPERATUR". Make sure chassis and module match those of the trace file.
[ ] 12:26:23 Loaded module "KMB_E36.C27" with 54 functions with 2 multiword functions, 84 properties with 7 arrays and 9 unoccupied blocks.
[E] 12:26:23 An error occurred while reading "C:\NCS TRACE FILES\KMB\E36-KMB_E36.C27-FSW_PSW.TRC": Unresolved function keyword "WARNUNG_TEMPERATUR". Make sure chassis and module match those of the trace file.

Any help would be greatly appreciated!!!

[revtor]

Luke Stutz: Same issue as the poster above you: your trace files are not valid! You should be aware that NCS Expert uses the "FSW_PSW.TRC" trace file as temporary file for many actions, so most of the time the file does not contain valid module traces!

Carefully follow the instructions in "Reading FSW_PSW.TRC and NETTODAT.TRC trace files" (user manual chapter 6.1) to create proper trace files.

[Luke Stutz]

ok ill give it another shot. i didnt know if i was doing something wrong or what....

FIGURED IT OUT MAKE SURE THE JOBNAME SAYS --> "CODIERDATEN_LESEN" NOT---->>>> "CODIERINDEX_LESEN"


LOOKING THROUGH MY ASCT.C05 IT COMES WITH THIS SCREEN SHOT


I TAKE IT I CANNOT DISABLE THE ASCT USING NCS DUMMY???

[MParallel]

Yes that sure looks like to be the case. You can select the engine model and tranmission, but you can't deactivate it. At least not through this file, if another ASC coding file is available.

[wyccka]

Dear revtor, please take a look:

[E] 00:06:39 An error occurred while reading "FSW_PSW.TRC": Inconsistent data between parameter keywords "e39_man_lwr" and "e39_aut_lwr" in function "EHC_KENNFELD". Make sure chassis and module match those of the trace file.

Module: EHC.C06

Where could be a problem ?

FSW_PSW.TRC.TXT
NETTODAT.TRC.TXT

[revtor]

wyccka: Bizarre issue. Your "FSW_PSW.TRC" trace file is:

EHC_KENNFELD
	e39_man_lwr
	e39_aut_lwr
	e39_man_lwr_mit_offset
	e39_aut_lwr_mit_offset
	e39_ab_sensor
	e53_ab_sensor
OFFSET_HI_LI
	ab_sensor
OFFSET_HI_RE
	ab_sensor

Nothing is wrong with functions "OFFSET_HI_LI" and "OFFSET_HI_RE", but something weird is going on with "EHC_KENNFELD". It has multiple parameters selected. Well, that by itself is not strange - multiple parameters for a function just means that the data for each parameter is the same. The problem is that the data is not the same!

e39_man_lwr            : 9F,06,0A,06,01,43,01,43,80,00,28,1E,04,B0,03,84,0E,10,01,B8,27,00,00,00,3C,FF,F1,00,0E,E6,91,19,6E,05,32,1E,19,0A,F0,19,13,0A,5A,5A,64,00,00,00,00,B2,4B,7D,DC,03,12,C0,00,32,0E,10,03,00,14,00,00,00,00,00,00,00,00,00,00,00,E0,DB,14,56,3A,14,14,03,03,84,2B,48,1E,66,00,00,00,00,00,00,00,00,00,00,00,28
e39_aut_lwr            : A0,06,0A,06,01,43,01,43,C0,00,28,1E,04,B0,03,84,0E,10,01,B8,27,00,00,00,7D,FF,F1,00,0E,E6,91,19,6E,05,32,1E,19,0A,F0,19,13,0A,5A,5A,64,00,00,00,00,B2,4B,7D,DC,03,12,C0,00,32,0E,10,03,00,14,00,00,00,00,00,00,00,00,00,00,00,E0,D9,14,56,3A,14,14,03,03,84,2B,48,1E,1E,00,00,00,00,00,00,00,00,00,00,00,DE
e39_man_lwr_mit_offset : A1,06,0A,06,01,43,01,43,80,08,28,1E,04,B0,03,84,0E,10,01,B8,27,00,00,00,46,FF,F1,00,0E,E6,91,19,6E,05,32,1E,19,0A,F0,19,13,0A,5A,5A,64,00,00,00,00,B2,4B,7D,DC,03,12,C0,00,32,0E,10,03,00,14,00,00,00,00,00,00,00,00,00,00,00,E0,DB,14,56,3A,14,14,03,03,84,2B,48,1E,66,00,00,00,00,00,00,00,00,00,00,00,28
e39_aut_lwr_mit_offset : A2,06,0A,06,01,43,01,43,C0,08,28,1E,04,B0,03,84,0E,10,01,B8,27,00,00,00,87,FF,F1,00,0E,E6,91,19,6E,05,32,1E,19,0A,F0,19,13,0A,5A,5A,64,00,00,00,00,B2,4B,7D,DC,03,12,C0,00,32,0E,10,03,00,14,00,00,00,00,00,00,00,00,00,00,00,E0,D9,14,56,3A,14,14,03,03,84,2B,48,1E,1E,00,00,00,00,00,00,00,00,00,00,00,DE
e39_ab_sensor          : B5,06,0A,06,00,BA,00,BA,00,00,28,1E,04,B0,03,84,0E,10,01,B8,27,00,00,00,BE,FF,F1,00,0E,E6,91,19,6E,05,32,1E,19,0A,F0,19,13,0A,3C,7D,64,00,00,00,00,B7,4B,7D,DC,03,12,C0,00,32,0E,10,00,00,14,00,00,00,00,00,00,00,00,00,00,00,DD,ED,12,56,3A,14,14,03,03,84,2B,48,1E,1E,00,00,00,00,00,00,00,00,00,00,00,F0
e53_ab_sensor          : B6,06,0A,06,00,BA,00,BA,00,00,28,00,04,B0,03,84,0E,10,01,B8,27,00,00,00,A1,FF,F1,00,0E,E6,91,19,6E,05,32,1E,19,0A,F0,19,13,0A,3C,7D,64,00,00,00,00,B7,4B,7D,DC,03,12,C0,00,32,0E,10,00,00,14,00,00,00,00,00,00,00,00,00,00,00,DD,ED,12,56,3A,14,14,03,03,84,2B,48,1E,1E,00,00,00,00,00,00,00,00,00,00,00,F0

As you can see, the first byte is already different between each parameter keyword!

Let's have a look at the "NETTODAT.TRC" file because that file represents what NCS Expert actually read from the module's coding memory:

B 000000A0,0002,77,9F

That is somewhat unexpectedly... Nowhere is a trace of the large binary blob of function "EHC_KENNFELD". The two data bytes present (77h and 9Fh) stand for "OFFSET_HI_LI/ab_sensor" and "OFFSET_HI_RE/ab_sensor" (easy to verify with NCS Dummy). In other words; NCS Expert did not read the memory space of function "EHC_KENNFELD" (addresses 0h - 64h). Again, this by itself is not strange - many modules have gaps. The problem is that NCS Expert generated fake (and definitely wrong) data for a function it did not read! I have never seen this before...

Try re-reading the module. Maybe you did not create the "FSW_PSW.TRC" trace file properly?

[wyccka]

FSW_PSW.TRC was generated in proper way. This is not the first time i see this in ncs/ncs dummy.

E39 owners - can anyone verify this ?

[revtor]

Bizarre... All I can say is that NCS Dummy is definitely right here. The FSW/PSW trace file is not valid.

[xdjbx]

Hi,
same problem here:
it says:
[E] 20:02:08 An error occurred while reading "C:\NCSEXPER\WORK\FSW_PSW.TRC": Unresolved function keyword "CC_ID_AKTIV_01". Make sure chassis and module match those of the trace file.

[revtor]

xdjbx: That's not the same error message wyccka gets.

To everyone: Can the users who get "unresolved function keyword" errors please first read chapter 6.1 of the NCS Dummy user manual before posting here? This error message is almost always the result of not following the instructions.

[xdjbx]

xdjbx: That's not the same error message wyccka gets.

To everyone: Can the users who get "unresolved function keyword" errors please first read chapter 6.1 of the NCS Dummy user manual before posting here? This error message is almost always the result of not following the instructions.

Hi,
Thanks. but this is not working as described.

I'm stuck at Step 9 (because there are no modules listed) so "The middle groupbox now shows the available modules" is not correct for me.

But:
I was able to read and code the FRM-Module with nettodat.trc file.

complete Log:
[ ] 17:53:51 NCS Dummy 0.6.0.1 launched.
[ ] 17:53:52 Loaded 14757 translations by revtor, IcemanBHE, joako, lolo, rdl, StefanL, rondo and LPCapital.
[ ] 17:53:54 Loaded NCS Expert DATEN folder "C:\NCSEXPER\DATEN\" with 21 chassis.
[ ] 17:53:56 Loaded chassis "R56" (R55, R56, R57, R58, R59, R60 and R61) with 138 modules.
[ ] 17:54:50 Loaded module "FRM3_R56.C35" with 803 functions and 86 unoccupied blocks.
[ ] 17:54:51 Loaded trace file "NETTODAT-R56-Mini.TRC" with 803 functions, 86 unoccupied blocks and 2 custom parameters.
[ ] 17:59:27 Exported nettodata trace to "NETTODAT.MAN".
[E] 18:04:58 An error occurred while reading "C:\NCSEXPER\WORK\NETTODAT_CAS.TRC": Unresolved data in trace file. Make sure chassis and module match those of the trace file.
[ ] 18:05:10 Loaded module "CAS3.C09" with 264 functions, 8 properties with 2 arrays and 41 unoccupied blocks.
[ ] 18:05:11 Loaded trace file "NETTODAT_CAS.TRC" with 264 functions, 8 properties with 2 arrays and 41 unoccupied blocks.
[ ] 18:09:45 Loaded trace file "NETTODAT.TRC" with 264 functions, 8 properties with 2 arrays and 41 unoccupied blocks.
[ ] 18:11:19 Loaded module "CAS3.C09" with 264 functions, 8 properties with 2 arrays and 41 unoccupied blocks.
[ ] 18:11:20 Loaded trace file "NETTODAT.TRC" with 264 functions, 8 properties with 2 arrays and 41 unoccupied blocks.
[E] 18:11:26 An error occurred while reading "C:\NCSEXPER\WORK\FSW_PSW.TRC": Unresolved function keyword "CC_ID_AKTIV_01". Make sure chassis and module match those of the trace file.


any suggestions?
Thanks

[revtor]

xdjbx: That's strange. The instructions were written for NCS Expert 3. Maybe there are subtle differences with NCS Expert 4 (apart from the language of course) but I cannot verify this at the moment. Anyway, regardless of whether the modules are shown in the middle groupbox at the end of step 9, what happens if you continue following the instructions? The modules shown at the end of step 9 are not important. NCS Dummy needs the one shown in step 17... Oh and just to make sure you are working with a good profile, can you repeat the steps with the NCS Dummy profile for NCS Expert 4?

[wyccka]

Had similar situation with kombi module. Kombi showed error about incomplete coding. Cleared error and wualia, ncs dummy became happy.

[bhudda28]

Hello Revtor. I am trying to use your program to disable cold and warm monitoring of my high and low beam headlights. I have been through all of the modules of my 2007 e83 and the closest I have come to locating the functionality is in the ALSZ file. When I load this trace file and choose module in first screenshot I get options for every light except headlights. When I choose module from second screenshot I see high and low beams but cannot edit. Any advice on what I am doing wrong? I was thinking maybe I have to disassemble module from first screenshot and add functionality for high and low beams. Do you know if this is correct?

[revtor]

I am trying to use your program to disable cold and warm monitoring of my high and low beam headlights. I have been through all of the modules of my 2007 e83 and the closest I have come to locating the functionality is in the ALSZ file. When I load this trace file and choose module in first screenshot I get options for every light except headlights. When I choose module from second screenshot I see high and low beams but cannot edit. Any advice on what I am doing wrong? I was thinking maybe I have to disassemble module from first screenshot and add functionality for high and low beams. Do you know if this is correct?

The reason you cannot edit when selecting the "LSZ.C37" module is in the NCS Dummy log: "Make sure chassis and module match those of the trace file". You cannot load a trace file with a different module just because its contents are more to your liking. It doesn't make sense for NCS Dummy to allow you to edit the trace file in this situation - the result would never work anyways. A trace file is only valid for the module it was generated for...

So I'm afraid you are stuck with "LM2_E83.C05". I had a quick look at that module description file and, indeed, it does not have references to the high and low beams. The module description file does however have a lot of "<UNOCCUPIED>" blocks in the "Light monitoring" group. Unoccupied blocks often hint at hidden functionality - especially when the data values are not 0. Looking at the file I would say there's a very good chance the cold and hot monitoring of the high and low beams is present in one of the unoccupied blocks. The only problem is that without documentation it will be quite difficult to figure out where exactly.

If you don't mind trial and error you can convert the unoccupied blocks in address range 00000100 to 0000011E (= "Light monitoring" group) to regular functions with "nicht_aktiv" (data value 00) and "aktiv" (same data value as the unoccupied block) using the NCS Dummy disassembly and assembly functionality. Judging by the cold and hot monitoring that is present in the file it seems "nicht_aktiv" is always 00. Since the cold and hot monitoring of your high and low beams is currently enabled, you can probably ignore all unoccupied blocks that have data value 00. Make sure to read chapter 4.1.1 in the NCS Dummy user manual and familiarize yourself with the syntax - it's very easy to make mistakes by manually editing the disassembled module description files. Once the file has been modified and reassembled, read a new trace file from the module with NCS Expert, open in NCS Dummy and then experiment with setting the freshly added functions to "nicht_aktiv" and recode the car. Doing each function one by one is probably the best approach but it may take quite some time, so perhaps you could start with setting all new functions to "nicht_aktiv" at once and see whether the cold and hot monitoring is gone. From there on you can fine tune to find the exact functions.

[bhudda28]

The reason you cannot edit when selecting the "LSZ.C37" module is in the NCS Dummy log: "Make sure chassis and module match those of the trace file". You cannot load a trace file with a different module just because its contents are more to your liking. It doesn't make sense for NCS Dummy to allow you to edit the trace file in this situation - the result would never work anyways. A trace file is only valid for the module it was generated for...

So I'm afraid you are stuck with "LM2_E83.C05". I had a quick look at that module description file and, indeed, it does not have references to the high and low beams. The module description file does however have a lot of "<UNOCCUPIED>" blocks in the "Light monitoring" group. Unoccupied blocks often hint at hidden functionality - especially when the data values are not 0. Looking at the file I would say there's a very good chance the cold and hot monitoring of the high and low beams is present in one of the unoccupied blocks. The only problem is that without documentation it will be quite difficult to figure out where exactly.

If you don't mind trial and error you can convert the unoccupied blocks in address range 00000100 to 0000011E (= "Light monitoring" group) to regular functions with "nicht_aktiv" (data value 00) and "aktiv" (same data value as the unoccupied block) using the NCS Dummy disassembly and assembly functionality. Judging by the cold and hot monitoring that is present in the file it seems "nicht_aktiv" is always 00. Since the cold and hot monitoring of your high and low beams is currently enabled, you can probably ignore all unoccupied blocks that have data value 00. Make sure to read chapter 4.1.1 in the NCS Dummy user manual and familiarize yourself with the syntax - it's very easy to make mistakes by manually editing the disassembled module description files. Once the file has been modified and reassembled, read a new trace file from the module with NCS Expert, open in NCS Dummy and then experiment with setting the freshly added functions to "nicht_aktiv" and recode the car. Doing each function one by one is probably the best approach but it may take quite some time, so perhaps you could start with setting all new functions to "nicht_aktiv" at once and see whether the cold and hot monitoring is gone. From there on you can fine tune to find the exact functions.

Ok...thank you so much for the reply. I will be out of town for a couple of weeks but will try again when I return and I will definitely report back on success or failure. I know from personal experience that info on this topic specifically for X3 models is hard to find and the info may be useful for some forum members current and future. Until then thanks again.

[bhudda28]

The reason you cannot edit when selecting the "LSZ.C37" module is in the NCS Dummy log: "Make sure chassis and module match those of the trace file". You cannot load a trace file with a different module just because its contents are more to your liking. It doesn't make sense for NCS Dummy to allow you to edit the trace file in this situation - the result would never work anyways. A trace file is only valid for the module it was generated for...

So I'm afraid you are stuck with "LM2_E83.C05". I had a quick look at that module description file and, indeed, it does not have references to the high and low beams. The module description file does however have a lot of "<UNOCCUPIED>" blocks in the "Light monitoring" group. Unoccupied blocks often hint at hidden functionality - especially when the data values are not 0. Looking at the file I would say there's a very good chance the cold and hot monitoring of the high and low beams is present in one of the unoccupied blocks. The only problem is that without documentation it will be quite difficult to figure out where exactly.

If you don't mind trial and error you can convert the unoccupied blocks in address range 00000100 to 0000011E (= "Light monitoring" group) to regular functions with "nicht_aktiv" (data value 00) and "aktiv" (same data value as the unoccupied block) using the NCS Dummy disassembly and assembly functionality. Judging by the cold and hot monitoring that is present in the file it seems "nicht_aktiv" is always 00. Since the cold and hot monitoring of your high and low beams is currently enabled, you can probably ignore all unoccupied blocks that have data value 00. Make sure to read chapter 4.1.1 in the NCS Dummy user manual and familiarize yourself with the syntax - it's very easy to make mistakes by manually editing the disassembled module description files. Once the file has been modified and reassembled, read a new trace file from the module with NCS Expert, open in NCS Dummy and then experiment with setting the freshly added functions to "nicht_aktiv" and recode the car. Doing each function one by one is probably the best approach but it may take quite some time, so perhaps you could start with setting all new functions to "nicht_aktiv" at once and see whether the cold and hot monitoring is gone. From there on you can fine tune to find the exact functions.

Success... I was able to disable the headlight warning light from the dashboard although not the way I had originally planned. I thought I would share my experience since as I was commenting earlier, info regarding the E83 seems to be scarce. First let me say that a couple of days after my original post my TPMS light came on the dash. I tried resetting with no luck so I took the car to the dealer and they did a reset and the light would not stay off so they wanted me to make an appointment for a thorough analysis which I am sure would mean at the least a couple of hundred dollars plus labor if only one sensor needed replacing.

In going back through the trace files for my car i found I could manipulate in your program all options in KMB_E85_.C08 which was located in the AKMB module. Using this module was super easy. I loaded it into NCSDummy and made the changes for both the headlight warning light and to disable the TPMS warning light. I changed the following:

To disable headlight warning:

CC_LAMPEN - CHECK CONTROL NOTIFICATION FOR LIGHTS to "nicht_aktiv"

To disable TPMS (did not need to removes fuses or pull modules as mentioned in other forums):

KBUS_RDC - K-BUS TIRE PRESSURE CONTROL (RDC) to "nicht_aktiv"

AKUSTIK_RDC - TIRE PRESSURE CONTROL (RDC) WARNING GONG to "nicht_aktiv"

CAN_RDC - CAN-BUS TIRE PRESSURE CONTROL (RDC) to "nicht_aktiv"

RDC_AUSFALL_KBUS (??not sure of translation but has to do with RDC) to "nicht_aktiv"

RDC_AUSFALL_BLINKEN (??not sure of translation but maybe the blink function) to "nicht_aktiv"

I coded the headlight warning first by itself. The other five changes I coded in at the same time. Again, all of this was in KMB_E85_.C08. The whole process took maybe 5 min with ignition switch turned to second position. The only thing that I am not totally happy with is that the CC_LAMPEN code turns off my warning for all bulbs that may be out instead of just the headlights. For this reason I will continue to explore the suggestions you made in you earlier reply. I will report back as I find out more. Other than that, I am completely happy with the results. I just have to make a note to visually check for bulbs out and check my tire pressure once in a while. Thanks again for the recommendations and for a great program.

[Sigil7]

Hey bhudda, I'm in the same boat as you. E83 LCI, trying to disable cold/warm checks but can only see the LM module and not the LSZ. I may also try disassembling the modules once I do some more studying. Will post any updates I find if I do.

Question for revtor (or anyone else that can answer): When I do a 'Process Car' through NCS Expert, the trace file I get shows options present from both modules - that is, I see options from both the LM and LSZ modules. Am I correct in thinking this trace is for a 'theoretical' E83 that covers all modules for the lifespan of the platform? Or is there an actual LSZ module in the car that I just can't get access to through NCS Expert?

[radlaw]

Why do so many people want to disable their warm/cold bulb monitoring feature??? One would think this is an advantageous feature without any down side. What am I missing?

[revtor]

Question for revtor (or anyone else that can answer): When I do a 'Process Car' through NCS Expert, the trace file I get shows options present from both modules - that is, I see options from both the LM and LSZ modules. Am I correct in thinking this trace is for a 'theoretical' E83 that covers all modules for the lifespan of the platform? Or is there an actual LSZ module in the car that I just can't get access to through NCS Expert?

NCS Expert uses "FSW_PSW.TRC" as temporary file for many actions, so most of the time it contains data that does not apply to your car. Only when following the instructions (like in chapter 6 of the NCS Dummy user manual) you will end up with a valid trace file.

Why do so many people want to disable their warm/cold bulb monitoring feature??? One would think this is an advantageous feature without any down side. What am I missing?

Naturally the hot/cold monitoring is an advantage, but it does not always work as desired. Some people may want to "upgrade" their lighting from traditional light bulbs to LEDs and/or xenon lights. The hot/monitoring works by measuring currents, but there is a fundamental difference in current behavior between incandescent light bulbs, LEDs and xenon lights. That means if the light module does not have support for these other light types, the hot/cold monitoring will falsely detect bulb failures. Even when the module does have support for LEDs or xenon lights, using aftermarket lights may cause bulb failure warnings because the current thresholds are tuned for the OEM parts.

[metoo]

Hi, when I am clicking wth right click on "Speedlock_X_KMH_MIN" there isn't the "button" Add parameter. Only "Copy Keyword name" stands there.

https://www.dropbox.com/s/0wut8l2i9pobsqo/ncs-dummy.png

Anybody knows what I am doing wrong?

Thanks