[Radical Pi]

Originally Posted by apalrd

If it lost comm, I could tell fairly quickly because the image would go away

do you mean no more new images would be incoming? On our Dashboard the image just froze on the last one before comms were lost (same with targeting data)

Liked:

• Soft Reboot button (small bug - it throws an error if you try to use it while E-Stopped but still reboots)
• Status of DS side I/O - used it many times in debugging
• Live camera images
• Enable/Disable hotkeys
• Dashboard programming - As a C++ programmer that knows a bit of LabVIEW the dashboard packer was fairly easy to figure out, however a bit more documentation on this would have been nice.

Would have been nice:

• NetConsole built in - I wish there was an easy way to run it on the driver account (I had to remove the task manager block and run it from there). Perhaps the text box on the Diagnostics window could be a smaller window version of it that could pop out to the current netconsole window
• Fix for updater troubles - minor enough not to put into "Didn't like", but a small annoyance. Would have liked to see a quick fix once it was reported.
• When in the Driver account, the wireless and ethernet enable/disable hotkeys don't work. It would be nice to be able to switch between wireless and wired on the fly without having to switch accounts

Didn't like:

• Cypress board problems - I feel like this was a bit of negligence in testing. I don't see how with all of the beta teams running it the bug never popped up and got fixed.
• FMS Lock - I didn't even know this existed until we got to competition. Also an FTA at one of our completions claimed we wouldn't be able to connect while FMS lock was on, however we had done fine in matches before with it still on (hotkeys worked even though the lock was on, so I only was clearing it when we needed to run autonomous).
• USB e-stop button - In cases of control lag the e-stop was ALWAYS slower to react than the hotkey disable (spacebar), so our e-stop was never really touched.
• E-Stop bypass delay - is the 20 second wait to bypass the USB e-stop button really necessary?

Other notes:

• I saw a bug at philly during practice rounds where a team on our alliance had to e-stop during the first match. The e-stop crashed their DS and forced a reboot of the classmate (had to run the match without them)
  
• If we are getting new DS computers next year, please send one with a better ethernet port. Us (and many other teams) had a broken tab on the port that prevented the cable from completely latching in to the port. Our solutions was to duct tape an "extension cord" to the classmate.
  
• When connecting the classmate to the team router wirelessly, the enet link light will stay red even though everything is working and all the other lights are normal. Just a small cosmetic fix

EDIT: added a few more things