09-26-2013 04:37 PM
Hello,
I'm working on converting a program from Labview 8 to 2010. I can't use the Legacy drivers because I'm using Windows 7-64 bit, so I'm reconfiguring the IMAQ vi's to IMAQdx vi's. I replaced the vi's and ran the program and I get the following error:
Error -1074396120 occured at IMAQ Linear Averages
Not an Image
Possible reasons:
IMAQ Vision: (Hex 0xBFF60428) Not an Image
The program takes camera's through firewire and then does some processing. I can't show the processing so I can't post the full code, but I can post the section about acquiring the Camera Images, where I believe the error comes from. Attached is the Labview 8 version and then the Labview 10 work. Any help would be appreciated!
Thanks
09-27-2013 10:57 AM
Hi,
Unfortunately, it looks like the problem may reside in the processing portion of your code. This error can occur if you are sending a 32bit image to a function that requires an 8bit image. There is also an issue that can arise with the extract color planes VI that could be causing the problem. Here's a KB discussing the issue:
Why Do I Get Error -1074396120 "Not an Image" When Using IMAQ ExtractColorPlanes?
It's really tough to say where the error is without seeing your code. I recommend looking at the article and also using some debugging tools such as Highlighted Execution to see which VI is causing the error.
09-27-2013 02:27 PM
Thanks, Eric
I updated my code and was able to get an image out of one camera, but I was unable to obtain an image from the second camera. I'm not sure what the issue is since both cameras are acquired using the same code. Attached is a screenshot showing a highlight execution and where the error occurs.
Thanks for any help at all,
Sal
09-27-2013 03:02 PM
Sorry, the last image had a mistake this is the correct screenshot:
09-30-2013 12:10 PM
Hi Saln1,
I took a look at the screenshot you posted, and it looks like the error is being caused by an issue with the settings of a Region Of Interest. Are you working with an ROI in your program? Maybe there's one set up in MAX for that specific camera, so that when the grab is configured and loaded in LabVIEW, it attempts to load the invalid ROI, which causes the error.