Making the Dashboard more relevant to drivers?

FIRST General Forum
1

I am on programming and my team is moving toward driver practice and I want to how to know what data to put on and what data to remove from the dashboard. Definitely much of the space will be cameras, but how do I know what data will be useful during the match? Should I leave excess data for mid-match debugging, or keep it clean to make it easier to read?

1 Like
2

Whiteboard the ideas with your drive team - so list down on 1 side all the functionality/“data” that you guys have available and leave a blank column on the other side of the whiteboard blank. Then walk through with your drive team how they want the dashboard to be organized. Any new ‘data’ that hasn’t been completed go into the blank column but sketch them out still on the dashboard. Then that’s your driving manual which you can then distribute to everyone who might want to give their inputs (especially previous year’s drive team members - even those that might have graduated).

1 Like
3

Great question. Drive team feedback on what they want is the way to go. As drive coach, I only want the match timer in large font.

4

To add to the above, have them test-drive it. This is likely going to be an iterative process, and don’t be surprised if (when) it changes over the season (or during an event). The drive team are your “customers” or “users” in this case. (the same statement also applies to driver controls / what buttons do what)

For debugging/tuning purposes, note you can have multiple tabs in Shuffleboard, or different dashboards on different computers. E.g. in your shop, you can be running Glass on a second laptop showing all the debug data you’re interested in, but have a very simple Shuffleboard display on your DS laptop.

5

+1 on brainstorming with your drive team

For driver practice, you may want a lot more data than you will keep for competitions. But it really depends on what you are looking to fine tune.

I would include:

  • battery status
  • motor temperature (if you are using motors that report this)
  • motor speed for any items that you are still tuning like shooter, intake, etc.
  • Any outputs from your vision system that are relevant to your tuning (range to target, target pose, etc.)
  • position of mechanisms (encoder or motor counts converted to appropriate units) for things like the climber
  • pneumatic system pressure (if you have a pneumatic system and a pressure sensor)
1 Like
6

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.