LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Message "An exception occurred within..."

I've been working on the project and received this message "An exception occurred within the external code called by a Call Library Node. This might have corrupted LV's memory. Save any work to a new location and start LV." "VI <> was stopped at node 0xAC of subVI "IMAQ ROIToMask"".

I took the advice restarted the vi but same message pop up again. I've always do a daily backups of my current work and the same message appeared for vi from previous few days but those that dated further back a week or more are working.

As my vi is already alraedy very bulky at the moment, debugging without a clue would be an impossible task. Can anyone provide some idea how I can solve this problem?
0 Kudos
Message 1 of 11
(4,744 Views)
The Call Library Node is a VI that allows you to call code written in another language. Apparently, the VI "IMAQ ROIToMask.VI" is calling a DLL and has some problem with it. It's possible that your previous VIs don't have this VI and so they work. I've never worked with IMAQ so I can't check it, but I would suggest that you start by isolating that VI and running it separately. If it still causes trouble then this is probably a bad install. Try doing a repair install on IMAQ and if that doesn't help try uninstalling and reinstalling. If that doesn't help, see if someone else can run the VI. By the way, there's a cool tool in the tools menu called compare VIs and it does just that - you give it two VIs and it tells you all the differences between them. You can use it to see how your old VIs are different from your new VIs.

___________________
Try to take over the world!
0 Kudos
Message 2 of 11
(4,739 Views)
I'm not sure if IMAQ ROIToMask is the origin to the problem cos the older vis also contain this subvi and still run without problem.

Just did a repair on IMAQ vision and had to restart my system still didn't help.

This is really frustrating. I've been on this vi for hours today and just before the error message I didn't even have any major changes on the vi. I've even tried to "rollback" such changes but didn't help.
0 Kudos
Message 3 of 11
(4,732 Views)
Just done more testing on the vi and the same error shows up on and off. So going back to the supposed source of error.. the IMAQ ROItToMask at node 0xAC, how do I find that node or the subvi? I'm asking because well my vi contains many ROIToMask subvi and it is also rather difficult to navigate and search for it on a complex code.
0 Kudos
Message 4 of 11
(4,722 Views)
Do what I suggested earlier. Try running that VI seperately to see if it causes any trouble. Also, you can go into and search for the Call Library Function VI and see which DLL it calls.

___________________
Try to take over the world!
0 Kudos
Message 5 of 11
(4,717 Views)
The subvi (ROIToMask) runs perfectly fine in my vi most of the time now and also running fine in other examples.

About the search for the Call Library Function VI to find the DLL it calls... I'm not really sure how to do it cos I'm not very familiar with it.

Since my program contains alot of image processing steps, the error occurs mostly when I picked a certain part of the same image for processing. Reason is still not clear.
0 Kudos
Message 6 of 11
(4,712 Views)
I think I just found out the reason for the error. It isn't the subvi but the data feed into the subvi that causes it.

The ROIToMask requires a ROI Dscriptor to be connected to it and the ROI Descriptors somehow screwed up before it reaches the subvi.
Message 7 of 11
(4,709 Views)
Hi,
I have the same problem. But I cannot solve this as Josh Monkey did because the only inputs taken from the main subVis are the Instrument handler and the Error Handler, all other paramters are constants from the driver that turned to controls and are taken out to the main Vi.

When I ran it alone it shows the same error.
When I used SCPI commands and VISA write (instead of the originally HP ESD drivers) it works ?!
When I use the HP driver INIT (initialization of ESD Signal Generator) in a prior task it accepts it. The VISA Instrument handling is ok in all further part of the program.

I attach the SubVi,
Is there something I am missing?
0 Kudos
Message 8 of 11
(4,641 Views)
Hello,

First, you need to attach the subVI's as well in order to take a look at the code in any detail; if you can do this I'll take a look! Second, if you can give a more detailed description of your problem it will make helping more efficient. In particular, you noted that communication using VISA and SCPI commands works... does this give you your desired functionality. Which resource of port are you communicating through (Serial, GPIB, etc.)? Does the HP driver you refer to use HP VISA? Are you have a problem with a dll call as the others in the stream you posted to discuss?

I won't ask further questions now, but any and all information about your system will likely provide insight into the solution!

Thank you,

Best Regards,

JLS
Best,
JLS
Sixclear
0 Kudos
Message 9 of 11
(4,617 Views)
Hello,
 
I have quite the same problem: I also get the message "An exception etc....... was stopped at Call Library Node 0x10C of SubVi "IMAQ ROIToMask".
My SubVi´s which contains ROIToMask all run seperate without any problems. The message only appears when I try to run the whole VI.
 
So is there any possibility to tell exactly what Node 0x10C is and where to find it or how to locate it?
 
Thanks,
 
Friede
0 Kudos
Message 10 of 11
(4,269 Views)