Machine Vision

cancel
Showing results for 
Search instead for 
Did you mean: 

Error during running vision program

Hello,
I am working on IMAQ vision program. While running the program error message appeared as below:
 
" LabVIEW: An exception occured within the external code called by a Call Library Node. This might have corrupted LabVIEW's memory. Save any work to a new location and restart LabVIEW.
VI "Mecron_2007(Color).vi" was stopped at node 0x70 of subVI "IMAQ Match Color Pattern"
 
What should I do to avoid the above error? 
0 Kudos
Message 1 of 5
(3,835 Views)
The error you are seeing typically comes when the user tries to reference a variable in a method incorrectly from LabVIEW when using a call library node function.  These are buried in the IMAQ VIs at the lowest level.  The following discussion forum link talks about a similar situation that may help you. 
 
The error could be coming from several problems:
 
1) The installation of NI IMAQ of Vision is corrupt
- If the development files have been corrupted on your PC, it is possible that every now and then when a function is referenced, it will fail.  Try re-installing the lastest versions of your software.
 
2) Bad RAM
- The corrupted memory could also be bad RAM in your system.  Try running the program on a seperate PC or with only one RAM stick that you have tested and know to be good.
 
3) References in your code
- It is possible that your code is not closing a reference correctly or you are using a call library node function at another place in your program.  Verify that you close references properly and that no other DLLs are being called improperly.
0 Kudos
Message 2 of 5
(3,809 Views)
hart -

If you're still having this problem and could attach the VI, that would be very helpful.  These sorts of errors shouldn't show up in normal use of NI Vision and I'd love to see what's going on.

Greg Stoll
Vision R&D
National Instruments
Greg Stoll
LabVIEW R&D
0 Kudos
Message 3 of 5
(3,805 Views)

Dear Greg,

Here is my VI.

Thanks.

0 Kudos
Message 4 of 5
(3,780 Views)
hart -

Thanks for the VI!  Unfortunately, it has a lot of subVIs that I don't have on my system.  You can either save it as an .llb or try to eliminate extraneous subVIs to see what the smallest case is that still gets that error - this would help a lot in diagnosis, and it's what I'll be doing anyway Smiley Happy

Greg Stoll
Vision R&D
National Instruments
Greg Stoll
LabVIEW R&D
0 Kudos
Message 5 of 5
(3,767 Views)