I'm getting an Error -1073807300

[Kunal]

I'm getting the following error while running a vi, called Integration testing 1.vi, which has 5 sub vi's. These vi's are instrument drivers for instruments such as HP34401A, HP53132A. The following error shows up while running the integration vi:

Error -1073807300 occurred ar VISA Open in HP34401A Initialize.vi->hp34401a-getting started.vi->Integration Testing 1.vi

Possible reasons:
VISA: (Hes 0xBFFF003C) Insufficient system resources to perform necessary memory allocation.

When the error says Insufficent system resources does it mean on the hard drive. Would I have to delete any files then?

I have no clue how to go about this one.
Any help is appreciated,
Thanks,

Kunal.

[Rob Cole]

I have run into a similar situation when using instrument VIs that other people have written. The problem came when the VI uses "Open VISA" without setting the "Duplicate Session" input to true. Setting "Duplicate Session" fixed the problems I was having.

I assumed that it was because 2 different VIs were attempting to open communications to the GPIB card at the same time.

You might also want to check that each instrument works on the GPIB seperately (not all connected or turned on at once).

I hope your difficulty is as easy to fix.

Rob

[Kunal]

Hi,
I'm relatively new to LabVIEW and was wondering how do I set the input to Duplicate Visa Session to true. Also I couldnt find any Duplicate VISA session, though I did find a VISA session. I'm using instrument drivers provided by NI-LabVIEW like HP3301A Getting Started.vi and HP5313xA Example.vi, these work alrite seperately but show the error metioned above.
Thanks,
Kunal.

[Rob Cole]

You have to go inside the VI that you are using to run the instrument. If you look at the Error X happened in the first VI in the list is "VISA Open". You need to follow the chain of VI's from the last one in the list to the first (the "VISA Open") and wire a TRUE constant into the "Duplicate VISA Session" input to the "VISA Open". Then save everything. Hopefully, this will solve your problem.

Rob

[Kunal]

Hi Rob, I'm still confused how to approach this problem. Whenever I tried wiring a constant to the VISA session at the Open Visa, the wire broke (i.e bad connection) and when I found a Dup Visa Session in the Config.vi, I did the same thing, tried wiring the Duplicate Visa Session with a True boolean Constant, the same thing happened, i.e bad connection.
I've attached the vi I'm using. If you can take a look at it and tell me how to approach further, I'll be very glad.
Sorry for the inconvinence caused.
Thanks,
Kunal.

[Rob Cole]

Okay, I will work on this when I get the chance. I took a quick look and had some trouble with my version of LabVIEW (6.0.2) finding some of the sub VIs that you are using. But I think the big problem here is that I haven't worked in LabVIEW 5 for a couple of years now. Have you fired the question off to NI support? They could probably tell you more. The email support from NI.com is free and they usually answer my questions within 24 hours.

Rob

[Dan_Mondrik]

Kunal:

I do not know the cause of the error, but perhaps you should try debugging this at a lower level than the instrument driver. For one, try the VISA Interactive Control utility. With NI-VISA 2.01 (I think you have that version) it is at Start>>Programs>>VXIpnp. On Unix platforms it is in something like: /opt/vxipnp/sun/NIvisa/NIvisaic.

VISAIC will first find all resources available - is the resource string you are using listed there? If so, double-click it and a session window should open. If this fails in the same way as the instrument driver, then perhaps the problem is with VISA. If this succeeds, try sending *IDN?\n with viWrite and getting the response with viRead. If this succeeds, the problem might be with the instrument driver.

Dan Mondrik
Se
nior Software Engineer, NI-VISA
National Instruments

[Kunal]

Hi Dan, I used VISAIC and found the list of the resources available. Then I opened the window session of HP-34401A Multileter and sent the *IDN?\n with viWRITE and the following response was given in the viREAD:
HEWLETT-PACKARD,34401A,0,9-5-2\n
So does that mean there is a problem with the instrument driver. It works fine when I use it alone, but when I use a couple of drivers together. It shows the error mentioned above.
Also I'm attaching the instrument driver file. Could you please take a look at it and let me know if theres any problem.
I'm using WIN 98 platform and LabVIEW 5.

Thanks,
Kunal.