Error -1074396120 - Labview quits

[elkim]

I am using a scritp made in Vison Assistant to do some pattern recognition. When I connect the script to the camera, after some minutes of working fine I got this:

Error -1074396120 occurred at IMAQ Convert Real World to Pixel   Not an image.

And Labview quit suddenly after acknowledge the error.

I understand that after some time there will be no image to process. I am wondering how can I solve the problem even knowing that sometime I can not have image to process. I am attaching the vi's used.

[ChristopheC]

Hi,

fiducialx.vi is broken. Is that the case on your machine? Can you please let us know which version of Vision Development Module / Vision Assistant you're using.

Thanks.

-Christophe

[elkim]

I am using Labview 8.6 and Vission Assistant 8.6.

fiducialx.vi is working on my machine.

[Joel Khan]

Hey all,

I was able to fix the fiducialx.vi to get it to run for testing. This broken wire was probably due to a change from 8.6 to 2010. The error  -1074396120 is in relation to a IMAQ VI not recieving a proper image reference. It is documented in this knowledge base. In other words, you need to read in an image have have the reference to this image, this image needs to be calibrated, and then it can be fed into IMAQ Convert Real World to Pixel.

This screenshot depicts some changes you might want to make at the start of your program. 

Hope this all helps.

<Joel Khan | Applications Engineering | National Instruments | Rice University BSEE> 

[elkim]

Thanks for your answer. I am already doing that in patt4.vi which is the main vi and it is calling fiducialx.vi.

Maybe I haven't explained well. The program is doing what it is suppose to do (it means it is doing pattern recognition well) , except that after sometime labview suddenly exits and I have to restarted labview again.

[Joel Khan]

Elkim,

I need to be able to reproduce your error on a NI machine in order to get R&D to look into this. I have not found any documentation describing your Error in relation to LabVIEW crashes, therefore, the behavior you are experiencing is unusual. Are you able to pinpoint what is crashing labview? It would help to keep good records of the labview crash log files: Knowledge Base.

What kind of hardware are you using; both NI and 3ed party? Also, it would help in the reproduction process to have all the VIs.

<Joel Khan | Applications Engineering | National Instruments | Rice University BSEE>