[Swan217]

Originally Posted by Alan Anderson

What will you do with it at that point? The cRIO doesn't have a keyboard, so it's not expecting any keyboard commands.
I don't have any idea what you want to use a joystick-to-keyboard translation for. If what you want to do were possible, can you describe how you would use it? Give an example of what the operator would do, and what the result would be.

What I want is to make the joysticks tell the computer that I'm pressing a key instead. For a simplified example, Pinball in Windows accepts keyboard inputs, so if I push the joystick right, the case loop outputs "Right Arrow" to the user32.dll, simulating the pressing of the key "<-" For a robotics application, you could open up a text file and have the program give you a history of the directions you gave to the robot. If you pushed the joystick right for 5 iterations, the case loop outputs "RRRRR"

Of course, this is all irrelevant to my question, which is:
How can I intercept the joystick input and send the value to a VI running on the computer? Looking at my second attachment, which is essentially the arcade drive with its input wires cut, how do I make the "Joystick Get Axis" tell the VI on the computer I'm running (NOT on the cRIO) what the values from the Joystick are?

Once again, this is NOT competition-related. I'm simply deploying the modified arcade drive example to the cRIO. What needs to take the place of "X in / X out" on the example to make this work?