Changing data sent from driver station to CRIO

[mjcoss]

I have a USB device connected to the driver station. It's a HID device and while it did require that I install the driver to get the Classmate to really see the device, after installing the driver, the driver station display showed the device, and part of it is working like a joystick but ultimately I need to extend the data that is being sent by some amount. Not a lot of extra data but some. Or do we have to try and get the driver station software to see our extra data as joystick like event?

The data collection and packetization is clearly happening on the Classmate, and is then sent to the CRIO, which processes the packets.

I see in the library code a call to getCommonControlData(), but cant find the source code.

It looks to me like you'd need to modify both the code on the driver station and on the CRIO.

Is this possible? Permissible under the rules? Where would I find the source code that implements this?

Thanks

[heydowns]

Originally Posted by mjcoss

Is this possible? Permissible under the rules? Where would I find the source code that implements this?

I doubt that any modifications to the driver station software would be legal. The DS software, the FIRST-oriented cRIO network routines, and the network protocol that tie them together are standard for all teams to keep the playing field level.

Can you provide information on the device you are having trouble with? Manufacturer, model number, and what aspects of the device are not being recognized by the driver's station software?
Someone may be able to help out in reaching your desired goal.

[mjcoss]

The device is a logitech G13 keypad. It has a thumb joystick, and a number of scriptable/programmable keys. The joystick is picked up so I can get X/Y axis information, but the keys are silent. I assume that the DS code is collecting the joystick information, and packaging it up into the packets that it sends to the CRIO. Further that the data collection is only looking for "joystick" like devices and maps the collected data into a joystick structure. The issue is that getting the keypad to pretend that pressing a key is equivalent to a joystick buttons doesn't quite work, I can make it pretend to be a mouse button but no luck so far with getting the DS to see the key press events. I found a joystick emulator, but that clearly will be outside the rules in that it would require a separate application to be run is driver mode to provide the emulation.

Ultimately, I'd like to customize the data sent to the CRIO while leaving the majority of the framework intact.