LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW Freezes

Hello all,
 
I have a fairly simple VI which takes multiple text files containing wavelength/flux values and I plot them according to spectral flux, spectral flux curve peaks, and the integrated area under each spectral flux curve.  I use a tab for Red, Green, Blue, and Combined; each section containing multiple arrays and multiple graphs.  I've written VIs that have been much more complex than this one but whenever I go into the Combined section to change the plot settings (markers, line, color, thickness) LabVIEW moves very slowly and the memory usage continues to build from 40k all the way up to 70k until I have any activity.  After that I try to edit another plot setting and the memory usage builds again from 70k to 100k and so on...
 
Perhaps the amount of graphs or arrays could cause this huge memory build up, but even so if this were true I am baffled as to why.  Maybe it is my computer, but it seems to be working properly with every other application.  Maybe something within one of my loops or loop counts causes a never ending cycle of data? 
 
Any help would be greatly appreciated,
 
Attached is the VI and an example of the text document.
 
Thanks,

Message Edited by Steve.Briggs on 03-29-2007 03:21 PM

Download All
0 Kudos
Message 1 of 2
(2,466 Views)
Hello Steve,
If I understand you correctly, when you view all of your plots in the Combined tab, you experience a significant increase in processor usage. If I am correct in this assumption then I would say this behavior is typical. If your front panel is having to update several graphic items with every iteration of your program then the processor is having to work that much harder to complete those display updates on time. I imagine that when you are viewing one plot at a time, the processor usage remains at bay.
One way you might attempt to "pace" your processor is to introduce some timing vi's into your program, if you haven't already done so. I would suggest you use Wait Until Next Multiple in order to allow the processor enough time to complete the entire iteration with some time to spare to update other system applications.
Hope this helps.
Cheers,
Emilie Kopp | Applications Engineer | National Instruments
0 Kudos
Message 2 of 2
(2,432 Views)