|
Re: recording data
We experimented with this a few years ago and found there are many ways within LV to capture or log data. Many of them can interfere with the operation of your code, slowing it down / making it non-deterministic.
We landed on the TDMS file as it is very fast, efficient storage (binary files), and is easy to post process with Excel (the file maintains meta data and there are interfaces designed for Excel). This is also what NI would recommend, I believe, for data logging. We routinely collect data for performance analysis during competition as well as addressing developmental issues during code design.
Data logging has given us good analytical capability, and provides for some great teaching moments with interested students. It has been key to resolving what I call the "What just happened?" scenario.
Along with TDMS, good design will require something like the Producer/Consumer architecture with real-time FIFOs for communicating between loops. It's worthwhile to read up on these concepts if you're not already familiar with them.
I'll see if I can post an example.
|