check code

[Ziaholic]

You need to feed the Tank Drive with the default joystick inputs, unless overridden by the trigger. Your figure looks only half-fixed.

My attached pic doesn't directly apply to you, but if you look closely you can see where we used button 1 (trigger) to modify the throttle input. When the case is FALSE, we pass the normal value thru, but when the case is TRUE (i.e. the trigger is pulled), we override with a constant.

For us, the constant is 1.0 ... but if you want half power, then put a 0.5 in there and you've got it. (and we're doing our override to Axis3(Throttle), you'd want to do your case statement over the Y-Axis wires between the Joystick GET and the TankDrive VI.

G/L!

[Vikesrock]

Originally Posted by Ziaholic

You need to feed the Tank Drive with the default joystick inputs, unless overridden by the trigger. Your figure looks only half-fixed.

The picture shows one true case and one false case (presumably to show an example of each case to assure things are coded properly)

[Ziaholic]

KK ... sorry ... after re-looking at the pic in post #3, I can see what they're showing now ... My example does the uncluster outside of the case ... but essentially they're the same ... assuming that the other cases look like the ones that they're showing.

Hmmm.

Could it be that instead of writing "0.5" as the motor inputs when the trigger is pulled, they'd rather take the actual "Y" value, and cut it in half? If that's the case, then they should move the uncluster to the outside of the case statement, run both cases straight through, then modify the TRUE case with a MULTIPLY block with a 0.5 constant.