Closed GoogleCodeExporter closed 8 years ago
Original comment by jonie4
on 15 Feb 2013 at 11:09
Some suggestions:
- Probably should save the SmartDashboard config file somewhere, so that we
have a backup in case someone changes the config and we want to restore it.
Tip: the location of the save file can be found in File->Preferences.
- May want to turn on logging in SmartDashboard. See File->Preferences. This
might be useful for post-match analysis, although might take up a lot of data.
- Consider info that would be useful to driver/operator, and also some debug
info. Perhaps place driver/operator info on the upper part of the screen, in
large font; and debug info in the lower part of the screen in small/normal font.
Some suggestions for items to add to the display:
- Live camera feed
- Shooter voltage
- Connection indicator
- Software version
- Command scheduler
- Tape servo position?
- Limit switch values (if any)
Original comment by jtec...@gmail.com
on 19 Feb 2013 at 9:15
Also:
- Whether the shooter is enabled
Original comment by jtec...@gmail.com
on 20 Feb 2013 at 7:11
Original comment by jtec...@gmail.com
on 23 Feb 2013 at 10:16
I've added a branch in git called SmartDashboard, which initially contains no
files. This branch can be used to record history of the SmartDashboard
configuration on the driver station netbook, should you choose to use it.
This provides a couple benefits:
- We can restore the dashboard configuration if it gets deleted or messed up.
- We can share the dashboard config with other computers, for development, etc.
Original comment by jtec...@gmail.com
on 26 Feb 2013 at 5:29
I made the SmartDashboard look nicer than it did before. Also I updated the
SmartDashboard.
Original comment by jarr...@corr.org
on 10 Mar 2013 at 11:10
I put SmartDashboard in the SmartDashboard branch on our Git repository.
Original comment by jarr...@corr.org
on 10 Mar 2013 at 11:23
Original comment by jtec...@gmail.com
on 15 Mar 2013 at 9:30
Original comment by jarr...@corr.org
on 30 Mar 2013 at 11:37
Original issue reported on code.google.com by
jtec...@gmail.com
on 15 Feb 2013 at 4:49