check code

[zip100]

wanted to both joysticks pressed for half speed. So does the second pic look okay.

[Vikesrock]

Originally Posted by zip100

wanted to both joysticks pressed for half speed. So does the second pic look okay.

Yes, if you want each joystick and button #1 to control each side separately I believe the fixed code is correct.

[zip100]

so i do not have to put in axis (y) in the true, only in the false. Also only one end is go9ng to the case structure of the constant. Does that look okay.

[Vikesrock]

Correct, when the button is pressed (true case) you want the motor to run at a constant speed so you do not need the joystick value.

The constant originates in the case so it only goes out, no need for anything to come in.

[zip100]

Thank you for the help, will test out tomorrow and reply on how it went.

[Vikesrock]

If you need additional assistance and would like something more real-time, you can use the AIM, MSN, or Yahoo Messenger info in my profile or contact me on Gtalk (My gmail address is the same as my username here).

I'm not sure if I'm heading out to our shop tomorrow or not, so I may or may not be available by the above methods tomorrow afternoon/evening.

[zip100]

I tried the revised code but it shows error on build process of a broken vi.
Can I get a second opinion? Also the Ethernet cable going from the classmate will not click into the Ethernet port of the classmate it just falls out. Anyone else having these problems

[Vikesrock]

Originally Posted by zip100

I tried the revised code but it shows error on build process of a broken vi.

Could be the floating multiply block on the left side of the picture.

You can click the broken grey arrow at the top of the block diagram and it will pull up a list of errors. Double clicking on an error in the list will highlight the offending VI.

[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.