IMAQ Resample subvi causing exception error

[Riggy]

Hi all,

I'm using IMAQ V3.0 subvi IMAQ Resample in LabVIEW 7.0 to resize an image as part of a built application that runs independently on other machines about my worksite.

My probem is, basically, that the executable runs perfectly for many hours on the machines that it is installed on, then, at random and without warning, throws up the error:

LabVIEW: An exception occurred 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 "Image_Grab.vi" was stopped at node 0xAV of subVI "IMAQ Resample"

I looked in IMAQ Resample and it does call some external code, so I can't debug it to test for a problem.

Has anyone experienced this error before? Any advice on what it is I'm possibly doing wrong?

Included is Image_Grab.vi (saved as a library with included subVIs) that uses the IMAQ Resample subVI, as mentioned in the error box. It probably won't run though if you tried to run it, its called by other code and interacts with it too, but maybe if you see my code you might see a blatant problem with it

Thanks for reading this,

Richard.

[AdamB]

Hi Riggy,

Looking at what you are saying I would have to guess that there is something wrong with the accessing of the dll's.  Do you have a number of calls to this vi in your code?

What might be happening is that the calls are being made at the same time and this will cause a memory error.

You need to set up the particular call library Node function to be a reentrant.  (right click the function, select configure and to the right of function name select reentrant).  This may solve your problem.

Please try this and post back with your results

Thanx

AdamB

[Riggy]

Thanks for the advise,

It is true, I do call the IMAQ Resample subvi in more than one place within the code, but having followed your instructions I found that the function is already re-entrant. Thus the problem must lie elsewhere? I checked the vi itself and this is not reentrant, only the function inside the vi is reentrant. Would this matter?

Richard.

[AdamB]

Hi Riggy,

I'm getting my wires crossed here.

You need to take it off reentrant (sorry)

As of yet I can't find any other information in house and so I'm affraid that I might have to use the imortal line ("you might need to upgrade your software")

I'll keep looking and post back as soon as I have found anything.

p.s I can't see anything wrong with you code.

AdamB

[AdamB]

Hey Riggy,

Any luck getting the program to work?

Post back if you need some more help

AdamB

[Riggy]

Sorry for not responding, the issue became a low priority suddenly, I haven't had a chance to test this concept yet.

I promise as soon as it has been tried I will post back.

Thanks,

Richard.

[Riggy]

AdamB,

I have submitted the new revised code to the system and so far the test runs performed have been positive. That is, the error I experienced previously has since not reappeared. It may be a little early to assume it is fixed, more time may be required to be sure, but things are looking good 🙂

Thanks for you help!

Richard

[AdamB]

Great stuff,

Glad to hear it.  Just post back if it stops again.

Thanx

AdamB