How can I resolve "Query Interrupted" on 51st data point with a queue length of 50 for an Agilent 34401A?

[Aticris]

Hi,

I have a script used in our educational labs here. I am by no means a pro at Labview or its setup, however I believe I have narrowed down our problem some. The point of our LabView program is to create a Bode plot based upon measurement readings given from a Agilent 34401A DMM.

After the 50th data reading, the Agilent 34401A gives a "Query Interrupted" error. Upon looking around in the "Measurement and Automation Explorer", I found that the queue length of the 34401A is set at 50. Also, the SubVI for reading the measurement has "Data Storage" set to ON, and every time I turn it off it comes right back on as soon as the program starts.

The catch is, this program worked perfectly on the exact same computer last semester (Fall). Since then, we have updated the ELVIS software on here as well as the NI libraries. However, reverting back to the older versions has not helped at all. We have an Agilent 34401A DMM, 33120A Fn Gen, 54624A O-scope on a GBIB PCI interface card and an NI Elvis hooked into the same computer. Also, LabView 7.1 with default libraries (currently) and NI Elvis 3.2. Latest 34401A drivers are in the NI Library folder as well.

Thanks in advance!

[JLS]

Hello,

I have a few questions which may clarify the issue:

1. Is this an error you see on the instrument itself or do you see it in LabVIEW?
2. Are you using a Plug and Play Driver, an IVI driver, or simply programming using NI-VISA in LabVIEW?
3. Can you reproduce this error with a very simple program, such as doing just an initialize and then read 51 times?

As for the data storage setting on the 34401a, it is likely being programmatically set by your LabVIEW application, which would explain why you see it reset all the time when you check in Measuerement and Automation Explorer (MAX). If you set the Data Storage to off in the subVI you mention, does that prevent it from appearing otherwise in MAX?

In any event, I actually have access to an HP34401a so if you'd like to attach a simple program which replicates the problem and only accesses the HP34401a, I can take a look at here and see if there is anything we can do programmatically to fix it!

Thank you,

Best Regards,

JLS