Insufficient system resources error

[REash]

Quick question....I keep getting the following error after my LabVIEW 7.1 program has been running for a while:

"Error -1073807300 occurred at agn330xa Initialize With Options.vi
Possible reasons(s):
Driver Status:  (Hex 0xBFFF003C)   Primary Error:  (Hex 0xBFFF003C)  Insufficient system resources to perform
necessary memory allocation."

It varies on which instrument's driver it occurs on, but it alway seems to occur on the initialization VIs after my program
loops back through itself a few times.  This error causes me to close out LabVIEW completely before my program will run again.
I am closing out the VISA sessions after each of my tests for all instruments used in that test.

Any thoughts??

Thanks,
Ryan

[Dennis_Knutson]

The only driver I found for that instrument is an IVI one. Are all of your drivers IVI or is it just this one? When you do the close, are you just using a VISA Close or are you using the Close function in the driver? If you are using VISA Close, replace it with the driver close function.

Also, what version of VISA and the IVI Compliance Driver are you using?

[REash]

I am using the drivers' close functions for all instruments.  I have a few of each type of driver.  Like I said though, it's not just one set of instrument drivers that I'm getting the error on.  The other one I've been getting the error on a lot is for a Xantrex XFR Series Power Supply.

I am using VISA version 3.3, and the IVI Compliance Package 2.1.

[Dennis_Knutson]

We've only go a couple of testers with a single IVI controlled instrument and I'm pretty sure those are the versions being used. The latest versions are 4.0 vof VISA and 2.5 for the compliance package. You could try upgrading but I have no  idea if that would fix the problem. You could also post your program (or a small example) that demonstrates the problem. Maybe someone can see something in the code.

I'm pretty careful about closing IVI references but regular VISA ones haven't been a problem in a few years. It used to be that VISA Open would create a new refnum each time it was called, but now it just reuses a reference if one is already open.

Message Edited by Dennis Knutson on 12-07-2006 12:56 PM

[REash]

I will upgrade to VISA 4.0 and IVI 2.3 now (it says I need a new version of NI-Spy to go to 2.5).

I can't post the code, because it is much too large for posting.  It is around 20MB.

This is getting annoying because my program is complete and working fine, except for these errors, which are a

big killer.

Is there some way within LabVIEW to release all resources being used by all VISA instances?

I'll let you know if the upgrades help.

Message Edited by REash on 12-07-2006 02:18 PM

[REash]

The upgrade didn't help.  Still get the error.

Since my last change, the error is consistantly occurring at the exact same place every time, on the same driver VI, and on the same iteration through my program.

My program basically loops through the bulk of the program 6 times, and it is now on the third time through that it gets stuck on this error.  Before I put in the VIs to close the VISA sessions, it was always getting stuck on the second loop through.  So putting the VISA closes in helped.  What else more can I do??

Is there a way to allocate more resources for my program, or some way to free up more memory to use for it?

Any other thoughts at all would be helpful.

Message Edited by REash on 12-07-2006 04:27 PM

[Dennis_Knutson]

I don't think it's a resource problem that you can fix by adding more memory or anything like that but I don't know what could be causing the problem. What driver is doing it consistently now? Is it the IVI driver you mentioned before? If it is, I suppose it's possible that there is some sort of memory leak in the driver itself. That sort of thing might be difficult to find unless someone has both CVI and the instrument itself. You could turn on NISpy to see if you see something there.

[REash]

The VI driver doing it now is the initialization VI for the Xantrex XFR Power Supply I spoke of before.

[REash]

Could the size of my program itself be the problem here?

It doesn't seem like it would be, since the program is actually running...

I will try running NI-Spy to see what it sees when the error occurs.

[Dennis_Knutson]

I think I might have the solution. I downloaded the driver for that instrument and in the intialize function, there is Old VISA Open. You should replace this with the VISA Open on the Instrument I/O>VISA>VISA Advanced palette. When you do that, the wire to the string control 'Instr. Descriptor (GPIB::2::INSTR)' will be broken. The string control needs to be deleted and you need to right click on the VISA Session (for class) terminal and select Show Control. Go to the front panel and wire the VISA Session control to the upper left point on the connector pane.

This Old VISA Open shows up in drivers that have been converted from very old drivers. I've usually had the initialize fail to work at all with it in there. I hope this helps.