Insufficient system resources error

[REash]

I'll give that a try.

I use that same initialize driver many times prior to that point in my program, and remember, this is on the third loop through that the error is occurring.

Do you have any idea why that driver VI would be working fine up until that particular point in my program?

And why would I be getting that same error with the initialization VI for that other instrument, the agn330xa that I first was having that problems with, that my first post was based on?

I'm still going to let my program keep running until I see what NI-Spy catches.  Then I'll try changing that Xantrex driver tomorrow.

What is the problem with having the "Old VISA Open" in there?  Is there known problems with that being in drivers?

Thanks,

Ryan

[REash]

I ran NI-Spy and it caught the error, but I don't know if there's really anything to learn from the file.

If you think there's any value in looking at it, I can post it if you'd like.

I'll try changing that driver file tomorrow.

Dennis, if you could, please check back tomorrow to see if I still need help!

Thanks!

Ryan

[Dennis_Knutson]

Go ahead and post the file and let me know what happens after you change the VI.

[Weiyuan]

I don't know if your program should be 20MB.  If not, try to clear the graphs.  search "reduce vi file size" for more info.

[napview]

I used to have that annoying problem back with 5.0 to 6.1 until I knew exactly what happened when looking at a colleague's routine. You must have a visa close before getting out of last loop that is just after the visa open. This would cause an overflow in GPIB buffer everytime the same visa reference is passed but was closed prematurely without re-openning it. However this may not be true enough but I noticed this behavior occurred no matter which labview or visa version, "old" or "new" visa open was used. 

[REash]

Dennis, here is the NI-Spy file.

I'm about to change the XFR driver VI now.

[Dennis_Knutson]

I see a whole lot of viOpen for GPIB0::4 but the only viClose I see is at the very end. Are you sure you have a close for it? If you have a loop and are opening the instrument each time in the loop, then you should also be closing it in the loop. There's no reason to open it inside a loop though. Doing it once at the very beginning of the program is enough.

[REash]

What you are seeing there is all within one test sequence of my program.  I re-initialize the instrument a few times in each test to clear out the instrument settings when performing a new step of the test, but I close the VISA session at the end of the test.  Does it hurt anything to re-initialize it as often as I do?  I probably don't need it as often, but can that cause problems?  I do close the VISA sessions after each test...

My test program is running right now to see if changing that driver VI helped at all.

Message Edited by REash on 12-08-2006 10:09 AM

[Dennis_Knutson]

The intialize function calls VISA Open each time it's called and optionally reads the id and does a reset. You should only be doing this once. If you need to do a reset, call the reset function by itself.

[REash]

Yes, but would that cause an error like I'm getting?  An error that doesn't occur until after the program is running for a while...