LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How to display data at a slower rate than it is being acquired?

Thanks for the example. I think it'll work for what I want. I tried using it as a SubVI and passing data in a loop as that is how my data will be (it'll be through shift register), I am having trouble. I have attached what I am trying to do. And the values are not updated as the user changes the value.
0 Kudos
Message 11 of 16
(949 Views)

For this particular case, if you want a sub-vi, then the code's architecture needs to change.  You could make the code work using the original code, but it would be messy and not the better way to do it.

 

Have a look at the attached VI's.

 

I did modify the original code but preferred not showing a bad example.  That is why these are named [3].

 

R

 

 

Download All
Message 12 of 16
(937 Views)

I'm going all the way back to the initial question and then stepping back a bit to see the forest for the trees.

 

If you display at a slower rate than you acquire, then you are displaying *less* data than you acquire.  It will be *lossy*.  And having a lossy display is often not a bad thing at all -- I for one do it regularly.

 

So once you explicitly decide to have a lossy display, a lot of your data handling gets simpler.  You can decimate by averaging to reduce the amount of data being slung around.  And you can use a Notifer instead of a Queue to do the slinging, so you won't start running out of memory if your "consumer" loop stops consuming.

 

I don't have LV handy here to look at the vi's being posted.  Just wanted to chime in with some "big picture" comments.

 

-Kevin P.

ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.
Message 13 of 16
(928 Views)

Hi Kevin,

 

I agree with you that there may be better techniques to implement a solution.  However, there were not many details ( or specifications) given about the overall functionality, requirements or constraints.  It is an unfortunate side effect at this forum where many people ask for help without offering enough details in order to offer a precise example.  😞  So we try to guess at what they are trying to do based on the available information. 

 

The example does keep track of all data but only displays the last set in the waveform chart. 

 

R

Message Edited by JoeLabView on 09-10-2008 12:14 PM
Message 14 of 16
(926 Views)

I think this is what I wanted.  I didn't want any loss of data.  I'll implement it my larger VI and hope it will work.

 

Thanks very much for your help. 

0 Kudos
Message 15 of 16
(906 Views)

I made a small mistake in one of the vi's.  Here is the corrected version.

 

R

 

 

Message 16 of 16
(889 Views)