Thread: Default Labview Dashboard and Windriver Example Help
View Single Post
  #7   Spotlight this post!  
Unread 22-01-2009, 15:17
heydowns's Avatar
heydowns heydowns is offline
Registered User
AKA: Jeff Downs
FRC #1511 (Rolling Thunder)
Team Role: Mentor
  
Join Date: Jan 2006
Rookie Year: 2005
Location: Ra-Cha-Cha
Posts: 142
heydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond reputeheydowns has a reputation beyond repute
Re: Default Labview Dashboard and Windriver Example Help
Yeah we fill in all the dashboard packet data by querying DigitalModule, AnalogModule directly. It saves having to query all the driver classes in different ways, and also provides access to some things that you can't get through some of the driver classes.

The limitation comes in when you want to get DigitalOutputs and a few others. For those, we had to change WPILib to add access methods or expose the FPGA handle such that we could query it directly for the necessary information.

I don't know how to check for updated LabView, sorry. Maybe someone else can chime in on that.