IMAQdx capturing at 30 FPS even though camera set to higher FPS

[ibutter]

Then it runs at ~60 FPS

[cbutcher]

---

@Gregory wrote:

What if you check that the buffer number has changed before calculating the frame rate and updating your image indicator?

---

In LabVIEW 2017 there's even a shiny new VIM to check if a value changed 🙂

If you don't have 2017, it's just an uninitialised shift register with a first call or equals node output and a variant through. You could swap the variant for the integer number.

[zou]

Take a look this post:

http://forums.ni.com/t5/Machine-Vision/Max-continuous-fps-using-imaq-and-LabVIEW/m-p/3617516#M49506

I was able to reach 2k+ frames/sec using the tricks in above post without using real time os.

You can also increase the read thread priority, increase application priority and write to disk using low level write function instead of imaq function.

You might be better helped in the Vision forum.

[cbutcher]

Except her/his loop is capable of running all the contained code at ~300 fps, and (s)he only needs 120. The problem presumably doesn't relate to speeding up the loop.

[Gregory]

---

@ibutter wrote:

Then it runs at ~60 FPS

---

Just to confirm, you implemented it the way that CButcher outlined, and kept "wait for next buffer" set to False?

[ibutter]

Confirmed. Wait for buffer set to false, and I tried both a shift register style not-equal check, and the new "is value changed.vim" approach.

Also, I'm a he, @cbutcher to save you the extra typing

[ibutter]

Just tried other FPS values

MAX Acq setting FPS / labview grab FPS

20 / 20

50 / 50

60 / 60

80 / chaotic 80

100 / less chaotic 100

110 / flipping between 55 & 110

120 / 60 

In each of these cases the buffer numbers are incrementing by 1, so perhaps that's being set by the grab, rather than the push to buffer that the camera does?

100 may actually be sufficient for my needs, but it would be great to get up to 120

[udka]

-Can you provide code in LV16 by saving to previous version?

-How you are calculating FPS?

-What is the resulting and Acquisition frame rate in MAX when try to grab?

-Can you confirm you have connected to USB 3.0 port? you can also verify by checking the USB Connection Speed(Should be Super speed) parameter in Camera Information subset in MAX.

-Are you connecting camera to PC directly or via any USB hub?

-What is the USB controller make model?

-Try the Grab and Attributes Setup example in Example finder and check what is the frame rate you are getting.

-What do you mean by chaotic? Do you miss any buffers(Images)?

-What is the PC Configuration(OS, RAM)?

[preekar]

Hello,

I have been facing similar issue in capturing a sequence of images. I have acquired images at a rate higher than 120fps through flycap..but labVIEW is capping out at 30fps (the default setting on flycap is 160fps). Unfortunately I am not able to open the file you have shared because I have an earlier version (2015) and the labview software is identifying the shared file as 2017 version.  I was wondering how to increase the frame per seconds (if you have found it). I am uploading the vi used. 

I also went inside IMAQdx Configure Acquisition and changed the number of buffers to 50 (getting inspired from https://www.ptgrey.com/KB/10827) . That did not help at all. 

[G-IV]

Hi preekar,

Would you mind posting this in the Machine Vision community (http://forums.ni.com/t5/Machine-Vision/bd-p/200).

They are probably going to want to know more details about your camera (specifically, what model camera are you using?) before they can offer any  help, so be sure that you post that information along with your question.

Thanks!

George B.

Applications Engineer

National Instruments

Gor