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!

[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?

[apalrd]

There is a VI to save the images at a predetermined rate, to JPG files. Seems to work well.

[Brandon_L]

Originally Posted by apalrd

There is a VI to save the images at a predetermined rate, to JPG files. Seems to work well.

Ill look at it, but theres no way to do a video?

[Radical Pi]

Originally Posted by Brandon_L

Ill look at it, but theres no way to do a video?

There are quite a few programs that can convert a series of images into a video (ffmpeg comes to mind)

On that topic, I looked where the dashboard should be saving camera images and found only a single image back from when I was getting the camera to work. I checked the Dashboard and the code seems to be intact.

[byteit101]

Originally Posted by Radical Pi

There are quite a few programs that can convert a series of images into a video (ffmpeg comes to mind)

On that topic, I looked where the dashboard should be saving camera images and found only a single image back from when I was getting the camera to work. I checked the Dashboard and the code seems to be intact.

ah, ffmpeg! my favorite video editing program. I used images with timestamps to make it timed correctly, and got a nice video: http://thecatattack.org/media/Vid/#AsixM409 (Match 4 (from robot camera) is the best, at the end of auto, we are staring at our team, and you can watch the seconds count down, then we jump forward). we even had a "Cat-o-Vison" sign and played four of these in the pits (one got scrambled up later)

we are using our ZomB dashbaord (http://www.chiefdelphi.com/forums/sh...ad.php?t=82612) and right now I am adding the smashTCP video to it so we can stream video: http://www.chiefdelphi.com/forums/sh...ad.php?t=82422 (and my version doesn't need .net 4, It uses .net 2!)

[slavik262]

As many of you know, I'm currently in the process of making one. I've ran into a roadblock though. After working with the UI for several weeks, I went today to test the networking only to find that FIRST had completely changed the protocol around. If anybody could get me up-to-date documentation on the dashboard protocol, I would be extremely grateful.

[spartango]

While for competition we have a stable custom labview Dashboard(robot-side code is all Java), we've been experimenting with a java swing dashboard:

http://code.google.com/p/grtframewor...CDashboard.jar