Insufficient system resources error

[REash]

OK, changing that driver helped some, it now gets to the 5th loop, instead of the 3rd.  It is now getting stuck again on the agn330xa driver.

Same "insufficient resources..." error....

[Dennis_Knutson]

I guess the next step would be to replace all of those initalize functions you call in the middle of the test. I have no idea why that could cause a problem with recent versions of VISA. I just created a small program with a VISA Open in a for loop and no VISA Close. I ran it 10,000 times with no problem.

[REash]

Yes, I have just removed the unnecessary initialize driver VIs, and am running the program again now.

We'll see what this does.

If this doesn't work, I'm not sure what to do next.

[napview]

I told you exactly what happened in your program if you still do not want to have the same fatal error. Here it is again: have a visa close for each visa open per instrument, preferably before and after the last loop (which means that no visa open for the same instrument per loop, no need to), similar to labwindow or any other programming languages (for, end loop).

It is a very simple solution but due to the nature of graphical programming, you can get easily off track of the logical structure of the nested loops.

[Dennis_Knutson]

Napview,

That used to be essential back in the days of 5.1/6.0 as you mentioned but has been fixed with newer releases of VISA. It is still good programming practice to do a close for every open but the good folks at NI fixed the problem as far as I can tell.

[REash]

Napview, yes, that is what I just did by removing the unnecessary initialize VIs.  The ratio of VISA Opens to VISA Closes should be 1:1 now, or something very close to it.

Dennis, you don't think this is going to help at all, then?

Message Edited by REash on 12-08-2006 12:45 PM

[napview]

How many loops you have for the same instrument(s)? Let's say that you have a power supply to sweep 3 times as the most outer loop, then you should have only one visa open (or initialize if you call it that) BEFORE that same loop, then a visa close AFTER that same loop. Now the second loop has a signal generator to sweep 60 times then just apply the same structure. To make it have more compact looking diagram, you can wire all those vi reference and error out to those visa close after the last loop, just be SURE to disable index of those wires through each loops. This way you can have as many loops for many instruments as possible without getting that nasty error.  

[REash]

napview, I just said that's how my program is right now.  The VISA Opens to VISA Closes is about a 1:1 ratio....

And what do you mean by "...disable index of those wires..."??

Did you read what Dennis just said, too??

[napview]

Can you send me all initialize VIs in your programs?

[REash]

Napview,

The two that have been causing problems thus far are for the Agilent N3301A Electronic Load, and for the Xantrex XFR Power Supply.  They can be found in the Instrument Driver Network.

Dennis,

The program went through all 6 loops this time.  But one thing I forgot to mention is that the program will do these 6 loops 2 more times, for a total of 3.  We are testing 6 units in a temperature chamber, at 3 different temperatures.  So it performs the same set of tests for all 6 units, switching through the connections to them with a matrix of relays, changes the temperature setting of the chamber, dwells there for 90 minutes, then starts the same sequence of tests again.  It then repeats this for a third temperature.  So right now it is dwelling on the second temperature for its 90 minute wait, allowing the units time to reach temperature.  So I still need to make it through those 6 loops two more times.  So removing those extra initialize VIs did help out a lot.  We'll see how the rest of this run turns out.  It will be a while until this run is done though.  I'll let you know.

Ryan

Message Edited by REash on 12-08-2006 02:06 PM