NI Frame Grabber and Camera Link Image Acquisition Slower Than Expected

Updated Sep 23, 2022

Reported In


  • Frame Grabber Device



Issue Details

I am using triggered acquisition with a Camera Link camera and a NI frame grabber. It seems to be working fine at low trigger rates. However, when I increase the trigger rate past a certain point, the acquired frames per second drops to approximately half of the trigger rate. What is causing this?


This can be caused by triggering the camera and the frame grabber simultaneously.

Typically you will only need to trigger the camera or the frame grabber. Here are the two recommended ways of triggering your system:

Triggering the Camera Only

When only triggering the camera, the frame grabber continuously tries to acquire images. Whenever you trigger the camera, the camera exposes an image and sends it to the frame grabber, which receives the data. When the FVAL line goes high, the frame grabber reads this data as a new image. 
You can typically use Measurement & Automation Explorer or the camera's configuration software to set the camera's triggered mode. You should not need to modify the image acquisition code in LabVIEW.

Triggering the Frame Grabber Only

When triggering only the frame grabber, the camera will operate in free-run mode. The camera will constantly collect and send images to the frame grabber. When the frame grabber is triggered, it waits until the next time the FVAL line goes high and then reads the next image from the camera. When all of the image data has been sent from the camera, the FVAL line will go low and the frame grabber will wait until triggered again. While waiting for the next trigger, the frame grabber will not respond to the FVAL line.
To configure the trigger in LabVIEW, use the IMAQ Configure Trigger VI.