View Single Post
  #5   Spotlight this post!  
Unread 31-01-2014, 14:15
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: How do Dashboard Projects Work

You are getting good advice from the above posts. If they don't address your questions, please follow up with more specific questions.

For a high level description. The templates have the targets properties and build scripts set for you. The robot project runs on the robot or in some situations on a simulated robot. The dashboard always runs on a laptop.

The driver station, which also runs on the laptop, will attempt to run your dashboard. It has selectors for Default, LV, Java, etc. These simply choose different paths and EXE names to launch and again match the templates.

Communication between DS and dashboard and robot and dashboard is supported, and the templates include some of it already. For example, the DS sends robot mode and voltage via the UDP protocol. Additionally, the robot and dashboard are both running SmartDashboard client/server code and share named variables with the icons in the SD palette.

Greg McKaskle
Reply With Quote