From Saturday, Nov 23rd 7:00 PM CST - Sunday, Nov 24th 7:45 AM CST, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Saturday, Nov 23rd 7:00 PM CST - Sunday, Nov 24th 7:45 AM CST, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
12-14-2017 02:17 PM
Thanks for all the help and suggestions Ryan. Here is the final product that could be made better with a few minor tweaks.
The sample rate and duration of collection would be user inputs so determining a divisibility factor would make the elapsed time and timer more accurate. Do you have any general recommendations of what I should keep the # samples per channel in the range of? We would collect anything from 1-2048 Hz so it is a wide range.
12-14-2017 02:21 PM
Well, if you are going to have variable rates then the #samples/channel should be adaptable as well. You could do some tests to see how long is acceptable for the update process, down to a lower levels of the rates, for 1, 2, etc, you can probably read the same number of samples as the rate as that is not very fast. As it progresses upwards you could aim for around the same dt with the number of samples, etc.
12-14-2017 02:24 PM
Yes the constants were wired in just for testing and proof but I will be changing those to user controls. Other than this, was the code implemented correctly based on your feedback?