|
Re: Problem programming buttons
Out team did the same thing - used T/F case structures each having a motor set. It mostly worked at .6 and the others would just move the motor in small increments. After thinking about it we came up with the same conclusion as above - all non pressed buttons are F and setting the motor to 0 while the pressed one is setting it to .6 for example. I'm not sure why .6 seems to work for us and many others that tried this method. My guess is that is has something to do with PWM, the motor frequency, and the DS communication packet delivery.
We moved to using cascaded select statements and it works fine.
|