From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

IMAQdx GetImage2.vi and CalculateFramePerSecond.vi - low frame rate

Solved!
Go to solution

Hi everyone,

 

Part of my VI deals with image acquisition. The implementation was taken from the example NI-IMAQdx "Grab and Attributes Setup". I've been trying to understand what the issue could be from the manuals, but no good so far. 

 

I have a continuous acquisition configured for 10 buffers as below:

 

T1.PNG

 

The Buffer Number Out from the GetImage2 VI seems to output a frame rate that is much faster than 10fps. When I use the CalculateFramesPerSecond.vi,  it says I am acquiring approx. 25fps but only processing 10fps. This 25fps seems to be how fast the Buffer Number Out is counting. I don't quite understand the difference between the two outputs.

 

Since the Image Out port from GetImage2 is the one that goes ahead to the part where I process the images, I don't understand if I am actually getting 25fps or 10fps during processing.

 

Furthermore, I don't really understand the slower count "ActualBufferNumber" that is 'attached' to the event structure and goes into GetImage2. I've tried removing this connection, but the fps behaviour continued to be the same apparently.

 

Yuri94_0-1588866667515.png

 

Perhaps I've misunderstood how buffering works in a Grab setup like this. Any explanation will be helpful!

 

Thanks a lot!

 

0 Kudos
Message 1 of 2
(2,124 Views)
Solution
Accepted by topic author Yuri94

Hi folks,

 

I've found the issue.

 

The whole loop was within a structure updating only every 100ms. After I changed it to update every 20ms, both the processed and acquired frame rates matched.

 

Yuri94_0-1588869931368.png

 

 

Cheers,

 

Yuri

0 Kudos
Message 2 of 2
(2,093 Views)