Custom Controller Info

[Greg McKaskle]

Seeing as how the cRIO can decode a jpeg with 80,000 pixels in a 20ms control period, it can certainly do a few derivatives. But directly to the issue. Try just plotting the axis value and determine if it is a line, a curve, or other. Also, do you have any documentation on the controller? It isn't uncommon for a supplier to have developer level documents on their site that describe the SW interface or the configurations available.

The initialize value on analysis blocks should receive one True, and then Falses. It is often wired with either a (first run) block or the i==0 expression based on a loop in the program. Depending on the joystick graph, you can probably just use discrete math -- subtract the previous value to get the delta, and then normalize the delta between -1 and 1. I'd assume that the joystick simply adds a scaled value to an accumulated value. Note that this will glitch when/if the DS packet to the robot is dropped.

If you want to post some VIs and screenshots showing how the controller behaves, someone may have other ideas.

Greg McKaskle

[Mark McLeod]

The Space Navigator might serve you better as a positional control than a joystick replacement. Since it's a 3D mouse intended to control a point in space you might use it to control the absolute position of the robot on the field, or of a multi-degree-of-freedom manipulator.

Output is really a measure of torque translated to a moving point in 3D space. Twist/pull/lean harder and the point translates or moves faster.
Have you used the 3Dconnexion control panel to reduce the speed of each axis as much as possible?