Quote:
Originally Posted by Mark McLeod
Don't modify library code.
There's certainly no reason to breakout the DevRef.
You are feeding the motor settings into the drve vi's now.
Modify them before you feed them in.
The default teleop.vi takes a joystick axes value and wires it into the Arcade Drive vi.
Put your new code between the Joystick axes and the Drive vi of your choice.
|
but, again, how do we do this for holonomic drive? there's a lot of trig performed on the joystick inputs before it gets out to the motor set VI in the holonomic drive VI -- breaking out the devref would give us direct access to the transform VI ref for each motor, which would let us do scaling like this. it seems like the only other option, barring rewriting the holonomic drive VI, would be to do all that math inversed on the axis values we're giving it -- and at that point we may as well just write our own drive VI.
in the mean time, i'll double check for any mechanical/electrical issues on our old bots (e.g. mis-set coast/break jumpers) with my team, because it seems like this really isn't a very common issue at all.