[gaby1367]

there are many faults to our dashboard heres some:
• Hot plugging joysticks is not supported. If you plug in a joystick after the DS has already booted,
it will not be recognized. The workaround is to always have joysticks plugged in.
• The DS only supports joysticks that use the standard HID interface. This means that if a joystick
requires special drivers on windows, it won't work with the DS. Unfortunately, this means the
XBOX 360 controller won't work.
• There is no API for displaying data on the DS LCD (like the UserMode byte from previous
years). This is planned, but not implemented yet.
• Occasionally the DS will send bad joystick data before the joystick has been moved the first
time. The workaround is to always make sure the robot is disabled when first starting up, and
move the joysticks before enabling for the first time. (This problem will be fixed soon!)
• When a joystick is unplugged, the DS continues sending the last valid joystick value. The
workaround is to not unplug joysticks while running.
• Occasionally, communication will lag by about 2 seconds. The workaround is to unplug any
Ethernet cable for a second, then plug it back in.
• Occasionally, communication will stop between the DS and the cRIO. One way to notice this the
robot will stay disabled when you enable. The battery voltage on the DS display will also not
update. The workaround is to unplug power to the DS and then let it reboot.