Thanks yet again
I'll forward the RPM stuff to our coach. The reason we were thinking about it is to keep the same RPM rather than a percentage of the motor speed (which would change as the battery dies)
As for the case and select vi's, I think I understand what you mean. And for the situation I mentioned about slower movement, I should just be able to use a case structure.
Would you happen to have a picture of an example Select Vi?
We had a huge issue today. Spent a good half hour to an hour trying to figure it out and still never got anywhere, AND apparently last year's programmer never could figure it out either. We have a window motor (for our shooter) that I programmed simply:
Button x: if true, set motor output to 0.4 / if false, set motor output to 0
Button y: if true, set motor output to -0.4 / if false, set motor output to 0
I used case structures for both and copy/pasted the first one made and just added the (-) sign.
However the issue is that only one of the two Case Structures will work! Say (ex) initially, Case A is +0.4 and Case B is -0.4. Case A will move the motor but Case B won't do anything at all. Then I switched the signs and Case A will move the motor the other way, but Case B still wont do anything. Switching buttons didnt make a difference. If I delete Case A, THEN Case B works, since there's no other Case in its way.
I tried it both with one and with two RefNumRegistry Get vi's but that didnt make a difference either.
Pics of the cases attached. The FALSE sides are identical to the TRUE sides, except the number is 0 instead of +/-0.4