Using a Keyboard on the Drivers Station

[Alan Anderson]

Originally Posted by MaxMax161

I looked over the rules again and I don't see anything that would stop you from using the built in LabVIEW stuff and not the WPI .VIs.

The built in LabVIEW stuff expects to be running on a computer with a keyboard, not on a cRIO. Unless I'm overlooking something fundamental, it won't give you the ability to read the Driver Station's keyboard from the robot.

[JesseK]

Hmm, we need to work on a keyboard-to-joystick API during this next offseason then. Pushing buttons on a joystick is ridiculous when COTS items like THIS would make year-to-year robotics much more intuitive. After all, many robots spend more time driving off of the field than on it (such as robot demos, etc).

[Alan Anderson]

Originally Posted by JesseK

Hmm, we need to work on a keyboard-to-joystick API during this next offseason then.

There are already several. They have been mentioned in other similar threads. Search the web for "virtual joystick" utilities.

[JesseK]

Thanks Alan. After looking into it, if the 'keyboard' mapped to 'joystick' functions that then went through the normal Driver's Station software (i.e. didn't try to go directly to the robot), I can't tell if that breaks <R75> or not since it's a 1:1 mapping and not a collation/redirection to the robot (similar to the way the HID drivers work).

I'll Q&A it.