First I would like to say: "Thank you so much for adding this feature!"
Before, with my foot off the throttle my TPS reading would drift between -1 and 1% making it very jerky when I lifted the throttle. Now it is smoother than ever.
However I would like to make a suggestion in the name of safety. Please make the text boxes for Min and Max read-only, and change the label of the Set button to "Read". Additionally you might want to throw up a warning dialog if the user hits the Min Read and Max Read button without changing the actual throttle position between button presses. And perhaps make the "Defaults" button actually load the defaults.
I thought that I could "Set" the range myself. I typed in 1 and 101 because that's often what my TPS reads at those positions. When I hit the "Set" buttons I expected it to apply this values. Instead it changed the numbers I entered for Min and Max to 1.2% and 60% respectively. At first I thought this was a bug in the program, then I thought maybe it actually did set the values I typed, but it reads back and displays the raw behind-the-scenes scale factor. So I went for a test drive like this. I tried to accelerate in 1st gear, but when the throttle was pressed more than 60% the TPS readng rolled over to 0% and it cut fuel. It jerked the car, which caused my foot to move slightly, which caused it to read 100% and it lurched forward, which caused me to move my foot and it really freaked me out because I was out on the road when this was happening. I pulled over and hit the Defaults button, which didn't actually reset my car to the defaults, it just entered 0 and 100 in the boxes and since it didn't apply anything I figured I needed to hit Set again, which reset it to 1.2% and 60% again. I thought "Oh crap, I've driven somewhere and I can't even reset it back to the defaults!"
Eventually by accident I figured out how this worked, but it took me a while, and it was very scary to be in traffic without a working gas pedal.
The documentation states: "If you generate TPS error codes then you have incorrect adjustments entered." This further confirmed my wrong assumption about being able to enter the numbers manually.
I hope these changes can make it into the next revision; I would hate for this to happen to anyone else!
