LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

VI did not stop when I try to stop

Hello,

           My vi did not stop when I press stop button and also I need to restart my system in that case. I have one more doubt regarding "Unevenly spaced VI". I try to perform FFT on my data today with this VI but I found that is cause for this error and also my other FFT graphs are not updating continuously when I use  "Unevenly spaced VI" along with my another FFT operations. I also tried to remove and run the  "Unevenly spaced VI" and then it work good with updating continuously. Can any one help me what is the cause for this.

Download All
0 Kudos
Message 1 of 6
(2,956 Views)

Can you post the VI in LabVIEW 2009.

0 Kudos
Message 2 of 6
(2,946 Views)

Here it is..

0 Kudos
Message 3 of 6
(2,939 Views)

Hi Peter,

 

that error messages happens when LabVIEW is busy with cleaning up (like big memory chunks, loaded DLLs, even DAQmx calls).

 

Especially when problems with (external) DLLs occur you have to shutdown LabVIEW, sometimes even restart the computer...

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 4 of 6
(2,933 Views)

I am using LV2011 and I have small doubt that about "TSA periodogram VI". I have two parallel loops, one continuously acquired data from DAQ and plot the FFT by using TSA periodogram VI and another loop gets the data from my sound card and use the same VI to compute the FFT. Problems, DAQ loop graph is plotting the FFT data correctly as I expected and the sound card loop does not plot well and sometimes doesn't plot any thing. I checked all the settings for graph but had no luck so far.

Or I misunderstood the data cluster wire in DAQ loop and SOUNDcard loop. Is there any material, that explaining about wire colors here?

0 Kudos
Message 5 of 6
(2,900 Views)

I don't know what you have in the subVIs however the picture you psted shows that your loops are greedy loops. It is possible something in the subVIs will allow a context switch but nothing you have in the posted picture will. This means each loop will run as fast as possible and starve the CPU as well as possibly starve out the other loop. At a minimum put a Wait 0 in each loop. This will allow the LabVIEW scheduler to run and won't really impact your performance.



Mark Yedinak
Certified LabVIEW Architect
LabVIEW Champion

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
0 Kudos
Message 6 of 6
(2,879 Views)