View Single Post
  #15   Spotlight this post!  
Unread 21-01-2010, 03:12
jhersh jhersh is offline
National Instruments
AKA: Joe Hershberger
FRC #2468 (Appreciate)
Team Role: Mentor
 
Join Date: May 2008
Rookie Year: 1997
Location: Austin, TX
Posts: 1,006
jhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond repute
Re: Dashboard-Driver Station Help Please

Quote:
Originally Posted by Abrakadabra View Post
Check out the WPI Robotic's Library User's Guide on page 51 - "Sending data to the dashboard". (Best bet is to follow the hyperlink from the PDF's table of contents, because someone forgot to put page numbers in the thing ). There is a two-column table on the next page that describes two different LabView data "clusters" - these are essentially the documentation for the data packages that the C++ example code is building up in preparation for sending it to the DS Dashboard that was written (of course) in LabView.
This structure is only an example, though. It's true that it does match the default data structures in the Dashboard that is generated when you create a new Dashboard project in LabVIEW, but there is nothing blessed about that format. Delete anything you don't want and make space for data that will actually help you to debug or to drive.

It's meant to get you to a good starting point with some examples... not to mandate that you use that data format, cause quite frankly, the data is too low level to be terribly useful (certainly in a driving situation) and reading all that data from the FPGA wastes lots of processor time. The fact that this was intended to be replaced by you with relevant data is even more evident since the real data isn't populated!

Sorry it was confusing and that you guys had different expectations. This part is supposed to be highly customized.

I have a feeling people would like it even less if it was all just a blank slate giving you no idea how to handle interesting data types, but at least their expectations would be fitting.
Reply With Quote