[Frenk]

does it only blink 3 times on the cluster or also flash 3 quick time turn signal bulb ?

[taranonline]

Can someone please make a detailed diy on this please..

[justa3series]

No need for detailed DIY, you need to read and use the tools available to you. NCSdummy is amazing and will help you find the value then you need to change it.

[Rotary Rasp]

Originally Posted by Frenk

does it only blink 3 times on the cluster or also flash 3 quick time turn signal bulb ?

The dash mimics the turn signals. I get five flashes on my dash.

[taranonline]

Detailed DIY for dummies please.

[Kalud]

OP you are awesome, was looking for this for a long time, thanks for posting!

[taranonline]

can somebody please put instructions on how to get this done. please

[srwatters]

Originally Posted by justa3series

No need for detailed DIY, you need to read and use the tools available to you. NCSdummy is amazing and will help you find the value then you need to change it.

While this is true, it perhaps isn't really obvious that you need to use the code via NETTODAT option. NCSdummy does a great job of listing out all the options, but even with the latest version is isn't clear that you need to change the value, then write the module trace data back different from normal option coding (sg_codieren with FSW PSW MAN). The option is MIND_ANZ_ZYKL_TIPP_BLK. The parameter needs to be custom added with the data being the number of blinks you want (I used 4). From there you can export the trace data as a NETTODAT.MAN file and write it back to the module using the job coapiCodeSgByNettoData. It's all explained in the NCSdummy thread "Taking the expert out of NCS expert".

Good luck!

[ZZZZ]

Originally Posted by srwatters

While this is true, it perhaps isn't really obvious that you need to use the code via NETTODAT option. NCSdummy does a great job of listing out all the options, but even with the latest version is isn't clear that you need to change the value, then write the module trace data back different from normal option coding (sg_codieren with FSW PSW MAN). The option is MIND_ANZ_ZYKL_TIPP_BLK. The parameter needs to be custom added with the data being the number of blinks you want (I used 4). From there you can export the trace data as a NETTODAT.MAN file and write it back to the module using the job coapiCodeSgByNettoData. It's all explained in the NCSdummy thread "Taking the expert out of NCS expert".

Good luck!

Been experimenting with this program and the most useful feature is the english translations on what those options mean. I haven't been able to change my triple blink yet, having a tough time with the NETTODAT part as it's a bit different from regular modules. Where do I find this 'code via NETTODAT' option? I don't see it in NCS Dummy?


From the regular modules I managed to get my doors to lock when driving off, changed to 15km/h. (this isn't an option in the cluster on my pre Sept-05 build e90), get my key to unlock all 4 doors with one push, auto-unlock doors when engine stopped, add a speed-limit warning on the dashboard at 120km/h.

For some reason my modules don't have an option to disable the seatbelt chimes, that's on my to-do list as well.

Great program, still not completely dummy-proof, but much easier than NCS Expert.

[scanboy]

if this

Originally Posted by srwatters

0x27 = xxx0 01xx = 1
0x2f = xxx0 11xx = 3
0xbb = xxx1 10xx = 6

is true, maybe we should leave the other bits untouch i.e:

001x xx11 where xxx is the number of blinks.

1 = 0x27
2 = 0x2b
3 = 0x2f
4 = 0x33
5 = 0x37
6 = 0x3b
7 = 0x3f

Safer this way ?
To put 0xbb instead of 0x3b would actually change values of other (who konws what) settings, I wouldn't do 0xbb.

my 2 cents (in case not everyone realize that).
Thanks op & srwatters for the info.

[srwatters]

Originally Posted by scanboy

if this



is true, maybe we should leave the other bits untouch i.e:

001x xx11 where xxx is the number of blinks.

1 = 0x27
2 = 0x2b
3 = 0x2f
4 = 0x33
5 = 0x37
6 = 0x3b
7 = 0x3f

Safer this way ?
To put 0xbb instead of 0x3b would actually change values of other (who konws what) settings, I wouldn't do 0xbb.

my 2 cents (in case not everyone realize that).
Thanks op & srwatters for the info.

The examples were given with values from someone specific vehicle. I would suggest that you use NCSdummy and edit the values from your specific NETTODAT trace changing only the specific 3 bits. That should work all the time.

[taranonline]

Got it done!!!!!!

BB = six worked great.

[Rotary Rasp]

For those who need a better explanation of how to accomplish this...

You need to scan the NETTODAT file once with the triple blink disabled within the gauge cluster (or idrive) and once again with it enabled. Then use beyond compare to scan the two NETTODAT files and find the value that has changed. That value is the HEX value you need to modify to increase the blink count.

Once you've changed it from XX to 37 (or whatever), save the NETTODAT file as NETTODAT.MAN and recode the car using the codeNETTODAT command.

Hope this helps.

[scanboy]

Originally Posted by srwatters

The examples were given with values from someone specific vehicle. I would suggest that you use NCSdummy and edit the values from your specific NETTODAT trace changing only the specific 3 bits. That should work all the time.

Thanks for clearing that up, make sense.

[scanboy]

Ok, I just did this, works when I test it right after coding, but as soon as I change something, it went back to 3 blinks, is that how it's suppose to work? I wasn't even changing the blinker setting, I was changing something else. ?!?!

[Elliott@DetailAddict]

Originally Posted by scanboy

Ok, I just did this, works when I test it right after coding, but as soon as I change something, it went back to 3 blinks, is that how it's suppose to work? I wasn't even changing the blinker setting, I was changing something else. ?!?!

That's the issue with the way this works. You can never toggle it off then on or you lose it.

[DESI4life10]

Originally Posted by Grant@DetailAddict

That's the issue with the way this works. You can never toggle it off then on or you lose it.

+1...with Grant

As soon as you use the bc stalk to change it to 1, you will lose this feature.

[scanboy]

Seriously? I mean I was just playing with the auto light sensertivity settings as I also just coded that, then it went away. That means I can't change anything with the stalk after the blinker change? That sucks! But I'm glad there's a way to change the number of blinks. Not complaining just making sure that's the way it works

[moreno1]

Good info to know :-)
thx

[Rotary Rasp]

Originally Posted by Rotary Rasp

No. And if you change it on the BC or iDrive it will revert back to stock. So it's best not to mess with those functions.

I told you guys that in the beginning......


It's not really a problem. How often to you feel the need to turn it on and off? You can still change everything except the triple tune signal option. Set it and forget it.

[taranonline]

today my coding got reset? happened to any of you guys.. I didnt change any setting from stalk menu.

[scanboy]

Originally Posted by taranonline

today my coding got reset? happened to any of you guys.. I didnt change any setting from stalk menu.

mine is still working, haven't touch the stalk menu.