View Single Post
  #2   Spotlight this post!  
Unread 04-02-2006, 10:53
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,563
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: Labview Video Tutorial? Dashboard

Quote:
Originally Posted by chakorules
We are using EasyC this year, so none of the default OI information is being sent to the controller, unless we create those varibles. But I can't tell by looking at the block diagram view how the "varibles" are called or accessed in Labview. I see the LEDs panel that was created in Dashboard (labview) version, but I can't find that in the block diagram, nor make a relationship of if that graphic is assigned to a varible which is updated by a packet or protocol stream somehow.
Have you read the "Labview Dashboard Documentation.pdf" included with the labview app? The driver is already written, you just need to modify the display file (although both have to run).

Each variable passed through the dashboard port gets stuffed into a different "frame" (I'm not sure the real labview term as I just started using it last week). See my attachement initial.gif to see where you change the frames. Clicking the down arrow gives you a list like in choosing.gif. Between the two "frames" you can choose from every variable sent over the dashboard port. Each variable is brought to the edge of the "frame" and you add whatever display stuff you want within the frame and connect it to the edge. So, rather then placing your HMI element and clicking on it and choosing your variable, you place the HMI element in the correct "frame" for your variable and draw a wire connecting it to the dge.

It would be worthwhile to read IFI's dashboard documentation included with the IFI dashboard viewer to see what gets sent by the IFI default code, which was what labview was designed to display. I don't know what EasyC does by default, but it would probably be easier with labview if you copied the IFI format.



I did my first modification to the battery display. I used some simple addition and multiplication to convert the battery from a 0-255 range to volts. Then I branched to adding graphs for other variables. That's as far as I've gotten though, but it's been really easy so far.
Attached Thumbnails
Click image for larger version

Name:	initial.gif
Views:	830
Size:	46.3 KB
ID:	3943  Click image for larger version

Name:	choosing.gif
Views:	349
Size:	40.1 KB
ID:	3944  

Last edited by Joe Ross : 04-02-2006 at 11:01.
Reply With Quote