So, who has a custom dashboard?

[Radical Pi]

I'm curious to see how many teams have been able to successfully get their own customized dashboard working.

So far, the Classmate side of the dashboard for our team is almost 100% done. From C++ the code works in theory. I was able to send some static data as a test but our debug code has never tried sending live data to the dashboard (and won't until competition now). Camera feed works like a charm though. Our drivers absolutely love it (and it really helps with aiming)!

I'll try to get a picture of it up when I can

[Alan Anderson]

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).

[EHaskins]

Our dashboard is written in C#/WPF, and it's talking to Java.

Other than a few issues due to poor documentation it has been relativily painless.

[Tanner]

Right now we've just got a few important things to make sure nothing is broken (which is always good to check for). Might add a overheard view of the view for drivers to make sure that the autonomous switches are in the right place.

The dashboard is really nice for some debugging stuff as well, just so you don't have to pull up the programming computer to check one teeny thing.

-Tanner

[ideasrule]

We have a custom dashboard. It's the only thing that made a live camera feed possible.

[sloteera]

Our dashboard just shows the camera image, an feedback for "ball in position to kick" and three possibles range for the kick!!

At the moment it's work very well!

We'll make a USB network using and "USB bridged cable" between Classmate and an Laptop to expand the camera image, but we don't try it yet!!

PS: we're using LV!

[Ziaholic]

We have a custom dashboard and a programmer that's diving into some more of the advanced features like animating shapes and creating custom indicators.

One thing that we haven't figured out completely yet is if it is possible to access the Teleop Elapsed Time without sending it from the 'bot. We're going to use this data to flash an indicator when we are approaching the final 20 seconds of the match.

Do I have to send that time from the 'bot, or is it already available via some local Dashboard/DriverStation variable that we haven't found yet?

[umangv620]

tried to make a custom dashboard, but got so confused on how to. i looked up some videos on frcmastery.com but they jump around from one series to the next, so i didnt get it.

[PIDman]

Ours isn't really custom, we just tweaked it a bit. We have an indicator to convert psi into kicking distance, it's really neat.

[pSYeNCe]

We have a (non-tested) custom dashboard for extra feedback, mostly. I wish I had more time with the robot, I would customize it a lot more than I did... Ah well. There's always the practice day before competition!

[PranavSathy]

We have a custom dashboard in C#, and it reciees packets via TCP/IP to display certain values like voltage, it shows a live camera feed AND it even records whatever images we got after a certain record packet is sent. It also has audio playback capability to play cool music during certian points of the match like a victory and game over music.

Below is the picture of our dashboard at startup

[Robototes2412]

can someone please send me a link to the protocol notes that FRC/WPI used to make the dashboard? I want to make my own dashboard in python/pyGtk, I am programming the robot in java.

[Boydean]

As of Tuesday we do not have a dashboard. But between now and Palmetto we could very easy have one(maybe even required).

Originally Posted by Alan Anderson

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 really like this idea, I'll be really looking into making this happen on our dashboard.

[apalrd]

I just finished writing the Killer Bees dashboard. I made the camera as large as possible with the small screen (full dashboard height at same aspect ratio),gave status information about the robot, made the background black, and grouped all of the controls into the cells of honeycomb. All of the text is 33pt yellow, default font. All of the indicator lights are brightly colored (purple, pink, yellow, blue, and green for on and red and black for off) so the drivers can see. Since we don't like to look down at the controls, the indicators are primarily aimed at the coach. For a final touch, I replaced the Timeout in camera communication message with the logo on honeybomb with a white background, with "Timeout in Camera" on the bottom. (I then put this program on the Classmate, which resides in a silver briefcase with honeycomb and our logo on it).

I like the idea of the tabbed dashboard. However, when that raw data is necessary, I am usually editing the code, so I can just probe stuff.

[Brandon_L]

It would be cool to record the camera feed from the matches, how can you do that with the default dashboard?