Machine Vision

cancel
Showing results for 
Search instead for 
Did you mean: 

FIFO overflow

I have been using two Basler 504k high speed cameras connected to NI PCIe1429 boards.  The setup worked fine until last week when the cameras stopped working.  When checking in the Measurement and Automation explorer, an error message comes up saying: FIFO overflow caused acquistion to halt.  Part of the image is visible (about 150 lines).  When the camera is set to VGA output, the image is still not full size, but about 950 lines can be seen.
0 Kudos
Message 1 of 3
(3,501 Views)

Hi

I’m sorry to hear that your program stopped working.  Did anything in your system change?  Can you still get each camera to function separately? 

There are a few things that we can try.  First try upgrading your driver to the latest version of IMAQ.  You can also try reducing the frame rate.  Or change the window size.  There is also a discussion forum that discusses the error that you are seeing.   

If these steps don't help, then there are a few things that would be helpful to know.

1. What is the motherboard manufacturer, model, and BIOS revision (often shown quickly on system power-up might need to use a function key to keep it from flashing by too fast. Which key depends on the computer).  Several computers behave differently with the 1429 check this knowledge base to find out what computer you should use with the 1429e
2. What camera file are you using?  Who was the source of this camera file?
3. The Basler 504kc camera outputs in Bayer mode, correct? Are you doing the Bayer de-mosaicing in software? Is it being done as the image is acquired or as a post-processing step after all images are acquired?
4. Does the camera have a firmware version number?
5. For high speed cameras, we recommend choosing widths that result in multiple of 8 bytes because of the higher efficiency. So in the case of a 8-bit camera, this would mean multiples of 8 pixels. Is this how you have been testing?
6. Which widths have been tested, and what were the results?
7. What version of the IMAQ driver are you using?
8. Can you get the same behavior/error when you use one of our example VIs (Program Files\National Instruments\NI-IMAQ\Sample)?

Keep me posted

Have a great day

GG

0 Kudos
Message 2 of 3
(3,486 Views)

Updating the IMAQ software combined with changing the image width fixed the problem!

With the old software, we always had a timeout occur when the starting pixel was set to 0 and the width to 1280.  Now, it works fine with that setting but not with the previous one.  Seems odd, but it's working fine now!

Thanks a lot for the help,

Gunther

0 Kudos
Message 3 of 3
(3,471 Views)