07-15-2012 03:02 PM
I am using a GigE camera to capture an image and then check for a hole using IMAQ Find Circular Edge. Each time the camera receives a trigger the while loop processes and the results are displayed. If the trigger is delayed for more than about 5 seconds, I get Error 1074396154 (IMAQ Spoke - Image not large enough for the operation).
The loop should be waiting for the next image before processing, so I don't understand why the error is being generated. Any suggestions would be appreciated.
Solved! Go to Solution.
07-17-2012 12:53 PM
Would it be possible for you to post your code so we can see how your trigger is set up? In addition, what version of LabVIEW and IMAQ do you have installed on your computer?
07-17-2012 09:31 PM
I am using Labview 8.6 Pro and IMAQdx 3.2. The code waits for a hardware trigger wired directly to the camera, which starts the loop when received. There are two sets of ROI's, one which looks for holes and the other checks for intensity.
07-18-2012 04:01 PM
It seems like this error is occurring because you are trying to do the IMAQ processing on a space in memory that doesn't have image information. Could you try including a check to make sure that it isn't passing in a blank image to the Find Circular Edge.vi?
07-18-2012 07:30 PM
I am not really sure how to check your suggestion. However, the images appear after triggering until the trigger has a 5 second delay. Also, I noticed today that I require 2 trigger signals to capture an image. Any chance this is related to my problem?
Out of curiosity, what part of the image signal initiates the loop processing?
Thanks for the input,
07-20-2012 09:14 AM
Have you tried increasing your Timeout on your camera? The default value is 5 seconds and since you are seeing this behavior right at 5 seconds this maybe causing the problem. To increases the timeout open Measurement and Automation Explorer, select your camera, select Acquisition Attributes tab at the bottom, and increase Timeout to 10000 ms.
Acquiring from GigE Vision Cameras with Vision Acquisition Software - Part II (Figure 4)