View Single Post
  #2   Spotlight this post!  
Unread 09-05-2008, 08:16
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: Labview and Sensors

Sensors are usually supported in LV by adding a collection of subVIs that give you a higher level API. The API can vary, but will usually include a Configure, a Read, perhaps a Write, maybe even a session based Open and Close.

These subVIs are written on top of the I/O used to communicate with the sensor. If analog, the subVIs will use the analog driver icons, and they will scale values and do book keeping in their layer.

If the sensor is on a serial link, then the subVIs will use the serial driver icons to send and parse messages to the device, do book keeping, etc.

For the cRIO and FRC, most of the I/O will come in through the FPGA, and the fast computation will happen there as well. So, the low level subVI icons are already built. WPILib will then use those icons, add addressing and scaling, and return the sensor values.

If you want to play with sensors in LV before WPILib is available, you might want to open up the Example Finder in the help menu. Search for a sensor such as a thermistor or accelerometer, and poke around in the sample programs looking at what is done. You can also look at serial examples. Just keep in mind that most professionals aren't building FRC bots, and the sensors and devices they use may be quite different.

Greg McKaskle
Reply With Quote