View Single Post
  #9   Spotlight this post!  
Unread 01-10-2012, 11:55
Joe Ross's Avatar Unsung FIRST Hero
Joe Ross Joe Ross is offline
Registered User
FRC #0330 (Beachbots)
Team Role: Engineer
 
Join Date: Jun 2001
Rookie Year: 1997
Location: Los Angeles, CA
Posts: 8,562
Joe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond repute
Re: Creating a Dashboard

Quote:
Originally Posted by phynix View Post
Thanks to everyone! I would prefer to go with the option that has the least amount of work involved, and produces acceptable results--so I think we might just use LabView. Thanks Alan/Rapture for suggesting that--I wasn't sure if they were compatible with each other. I don't have much experience building a dashboard (Though I would assume it's all pre-packaged in the 'Build Dashboard Project' option in LabView; I'm sure it won't be too hard to extend the ready-made code). Are there any finer points to deal with connecting to such a dashboard in C++? And would I just use the functions provided in the Dashboard class? The Dashboard.AddType() functions (in Dashboard.h)? I guess Labview will have similar options for reading, and writing back.

However, what functions would I use for listening to the Dashboard from the CRio?

Once again, thanks!
There's no built-in FIRST-specific method to communicate from a LabVIEW dashboard to the robot, unlike from the robot to the dashboard. You can do it through UDP or TCP sockets.

If two way communication is important, I would suggest starting with the SmartDashboard, which supports two way communication natively. I think that managing the datatype using the Dashboard class to communicate with the LabVIEW dashboard is a pain, but that isn't necessary with SmartDashboard.
Reply With Quote