View Single Post
      03-29-2018, 08:31 AM   #126
bbnks2
Colonel
1207
Rep
2,026
Posts

Drives: 135i N55
Join Date: Jan 2017
Location: NY

iTrader: (0)

Quote:
Originally Posted by bionicbelly View Post
I had that turned off during coding. I think. I will try to double check though.
Check Post #26. That is what used to happen to me on track with my 128 too. No codes but the car was basically in limp mode.

https://www.1addicts.com/forums/show...1&postcount=26

If you want to learn to do it yourself... the concept of what to do would be:

#1) read your DSC module using NCSExpert "Coderiden_Lessen" or something like that... I don't speak German.
#2) load the trace file that NCSExpert outputs into NCSDummy
#3) Manipulate the variables for each parameter in NCSDummy
#4) Export the changes you just made to the .MAN file type
#5) Go back to NCSExpert and change the job to "codierden" for coding (Pro Tip: the "profile" you use in NCSExpert must have write privileges enabled or the changes won't take affect)
#6) 15 seconds later your DSC module should be operating based on the new variables!

Plenty of youtube videos out there. It really is simple. If oyu know what you're doing, you don't even need NCSDummy, but having the description is nice and really helps reinforce understanding of what you're doing. I hope the above helps!

Last edited by bbnks2; 03-29-2018 at 08:39 AM..
Appreciate 1
ornicar136.00