Jagd,
Ok, let me explain the problem with a digital throttle a bit more as I experienced it. Anyone who feels that I am mistaken, please jump in.
As sprint pointed out, the throttle has to be moved slowly or the signals gets lost between your throttle and your motherboard. What this means basically is that the motherboard cannot handle the amount of signals transmitted by the throttle. (this is my explanation to the behavior) So, if you move it too fast, the more the chance that the signal gets eaten up and gets lost. So, Sprint knows this and suggested that it has to be moved slowly so that the motherboard can accept the inputs without loss.
What I suggested to you, if you still prefer to use digital throttle, is to add extra steps. For example, on AW, there were 15 steps to reach 100% throttle. As you will notice from what I sent you, I programmed 9 extra steps. Why did I do this? The extra steps will make sure that even if I moved the throttle fast, I can reach full throttle or complete chop when I need it.
For this reason, I preferred the analog throttle, because I do not need to worry about extra steps. All I needed to worry about is think about how to overcome the views setup, which is different from AW.
I did program my configuration so it is like AW with analog coolie hat. (there is a small draw back to it, but I got used to the behavior of my machine)
Soooo, kindly let me know how things turn out for you.