From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
07-26-2007 01:50 PM
07-26-2007 02:09 PM
07-26-2007 02:28 PM
I'm sifting through the results for Time DIO (thanks for the quick suggestion). In the meantime, here are the two versions of the program. From what I've seen distant professional colleagues do, it should be fairly straightforward
07-27-2007 06:41 PM
Hi Gordon,
I am not sure how your wind speed is being correlated to your data. Is there a more simple example which can exhibit the same problem – without using DAQ. (since your DAQ is software timed, this should be easy to simulate). I may also suggest doing a producer consumer loop instead of shared variables. An example of this can be found here: File >> New >> Producer/Consumer (under VI >> From Template >> Frameworks >> Design Pattern). The fact that your variable is being updated every 4 seconds only means that is what you are seeing. The variable will be updated at the rate of the DAQmx acquire, and (I suspect) that data is being overwritten and lost since your variable can only hold one number. This is why I suggested a producer/consumer queue previously, as it is a first in first out (FIFO) and as long as it is big enough, you will not loose data.