View Single Post
  #25   Spotlight this post!  
Unread 05-03-2010, 23:19
Joshuaal2000 Joshuaal2000 is offline
Registered User
FRC #0131
 
Join Date: Mar 2010
Location: Manchester
Posts: 4
Joshuaal2000 is an unknown quantity at this point
Re: So, who has a custom dashboard?

For my team, I am Using the Demo Dashboard as a base, but I have completely modified it to only contain info that our drivers want during the match, such as two bars to compare our what our drivers set for our kicking distance, to that of what the robot is currently set to kick at. This makes it simple for the drivers to see when the Kicker is in the correct position. We have Booleans for certain necessary features. We also display What state our Autonomous and Kicker state machines are currently in, Using enumerations from our C code.

Quote:
Originally Posted by Alan Anderson View Post
Our custom Dashboard works great. We're using LabVIEW on the robot, so it was easy to make the data match up.

One wrinkle we added was to split the display into two tabs. One is for use during a match and the other has a lot of diagnostic information (like raw encoder counts and other sensor input).
I have also done this to my dashboard, but in a different fashion. Using Data sent from the robot, we have made an autonomous and a teleop tabs plus a developer tab for debugging. During the match, the tabs switch from auto to teleop instantaneously when the state of the game changes with no manual control needed. This allows us to display different data during each part of the match, and allows us to keep our auto tab uncluttered so we can have larger text and inidcators, so that the driving team can view it from their starting position. The developer page requires manual opening to view.