LabVIEW
How to change tunnel mode
Solved!
What about Jeff's solution? Does that throw away 99 samples? And how do you know when you're throwing away data? I see 100 points when I execute the VI so where's the missing data? I'm having a hard time conceptualizing this 
@altenbach wrote:
@JÞB wrote:
Bill, You missed the Plot visability checkbox
Also, what would happen if you would replace the array of 3 NaNs with a scalar NaN? 😄
(A scalar NaN would make the code much more maintainable. Currently, if he would add another signal, a seemingly unrelated change would need to be done in the lower left corner...)
Yeah, I started straghtening out the cases and noticed the to dbl whoops, never got back to optimizing the select. There was a lot of BD clean-up and Bill had just posted
For readability would probably put the NaN in the nested loop and let the optomizer move it for me (with comment that such was intended)
@rhupd wrote:
What about Jeff's solution? Does that throw away 99 samples? And how do you know when you're throwing away data? I see 100 points when I execute the VI so where's the missing data? I'm having a hard time conceptualizing this
Jeff is not throwing away data. Notice that he configured the From DDT to output an array?
@rhupd wrote:
Ok, so the attached file is my final result.
You don't need to transpose (explicit and in the chart indicator) and you only need a single FOR loop. See attached.
@rhupd wrote:
I'm currently working on fixing the time and date but other than that, it does exactly what it's supposed to.
Note that the time will be questionable, because you sent entire arrays to the chart, instead of single, equally spaced points. You need to match up the loop time, the number of points, and "dt" in the actual data correctly.
@rhupd wrote:
and everything in the array is displayed so there's no loss of data. Is that right?
Sometime the array data is replaced with NaN, so ther original data IS lost.
Well, if we are going there..... (Timing) we need to get off the Express.vi teat (Nearly as evil as the DDT Data type but sometimes helpful) and use some real vis and a waveform data type
And I still like the plot visibility checkbox in this code
EDIT Obviously the loop timing shoud match the simulated signal time (Its late- and the default is produce 1 second of data)
@rhupd wrote:
@altenbach: why don't I need to transpose? What're the advantages of not doing that?
Less code is simpler and easier to maintain.
@rhupd wrote:
Note that the time will be questionable, because you sent entire arrays to the chart, instead of single, equally spaced points. You need to match up the loop time, the number of points, and "dt" in the actual data correctly.
Can you please explain the above? How would I send single, equally spaced points as opposed to an entire array?
You acquire a certain number of points at a certain rate, apendd all point to a chart at once, and then wait for the next iteration. During the wait, not data is being acquired. This will make the actual points on the chart nonlinear with time.
You probably shoud do continuous hardware timed acquisition and do the processing in parallel, reading the buffer at regular intervals.
rhupd wrote:I want to save the original data so is there a way to save it while using NaN?
Yes, branch the acquired data and save it. only process the data for the chart further.
