RoboDS Android 2015 Driverstation

[gixxy]

As a developer for the Cross Platform DriverStation.js we too have been working to reverse engineer the 2015 protocol, not that we have made it too far...

What we DO have is here: https://github.com/gluxon/node-drive.../2015-Protocol

[raystubbs]

Originally Posted by gixxy

As a developer for the Cross Platform DriverStation.js we too have been working to reverse engineer the 2015 protocol, not that we have made it too far...

What we DO have is here: https://github.com/gluxon/node-drive.../2015-Protocol

I don't have my notes with me right now but here is what comes after your general packet data, according to my memory:

The rest of the data is divided into joystick structures, each structure has the following:

1 byte: Size, in bytes, of the joystick structure
1 byte: Unknown, according to my memory it has always been 12, 0x0c in hex.
1 byte: 'a' the number of axis' available on the joystick.
'a' bytes: The values of each of the axis'.
1 byte: 'b' the number of buttons on the joystick.
'b'/8 rounded up, bytes: The state of every button, one per bit, button 1 is far right and button 'b' is far left.
3 bytes: Unknown, always seems to be 01-ff-ff.

The data for any other joysticks follows.

This may be slightly wrong, I do not have a perfect memory but I think this is mostly correct. If you want details or clarifications then contact me and I'll find my notes. If you find anything new with the 'Connection Packet' structure please let me know, thanks.