Showing results for 
Search instead for 
Did you mean: 

Timing issue with parallel timed loops

- while running only the acquisition loop: 10-15 %

- while running both loops in parallel: 18-32 %

in both case, all cores seem to be active

0 Kudos
Message 11 of 15

The reason for the slow down is a race condition on the image buffer.

See attached example for correct handling of the image buffer.



CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
0 Kudos
Message 12 of 15

I cannot opn the example since I have LabVIEW 2009!

0 Kudos
Message 13 of 15



I converted the VI to version 2009.

Cédric | NI Belgium
0 Kudos
Message 14 of 15

Hello Cedric,


Thanks for the effort. First of all, for this particular application I cannot capture a sequence of images just one after another since I need to analyze each frame and output some analog signals based on each image. This means that I still have to capture images within the producer loop. However I tried the example proposed by Norbert and it is obviously NOT the solution because as you know the "IMAQ copy" is computationally expensive and it slows down the iteration time of the producer loop by 8 ms, whilst I am hoping for 1 ms!!!

0 Kudos
Message 15 of 15