Bug located within driver for Agilent scopes agx2k3k

[Stephen.Schwahn]

Hey John,

Using the same settings, I still am unable to reproduce the error. I simply am not able to force a timeout error on the reads. I rememebr having that happen earlier today, and it felt to me like when I phsically ran the instrument, the error would cease to exist. I managed to see the same set of errors in the same place when I forgot to wire in the channel configuration (or manually changed it during execution), but given the VI that you provided, it worked very well for me. (I came up from a hard reboot and ran the code). 

Did you run any form of configurations before you ran this code? Or did you start fresh as well? If so, this is likely something that needs to be looked at, as it would vary between series.

Regards,

Stephen Schwahn

Instrument Drivers

National Instruments,

[Stephen.Schwahn]

John,

Finally, can we have your firmware version and interface mode? This way, I can set up a test to see if I can duplicate the issue and correct it.

Regards,

Stephen Schwahn

Instrument Drivers

National Instruments

[jto2]

Stephen,

I tried rebooting computer and scope and running the code fresh out the gate. Same results however. 

My current firmware version is: 02.10.201222200 and I'm connected tom the computer via USB.

I wasn't able to find the version you have (3.25), but I was able to find this one, which is (2.35) and was released 06-24-2013. It's the same as the most recent 3000 series firmware update I could find.

Before upgrading I will wait to see if you can duplicate the error I have with my current version. I looked through the release notes of the firmware updates and did not see anything regarding this current issue, however.

Thanks,

John

[hailin]

Hi john,

Just wondering have you met any problem with agx2k3k IVI driver?

Thanks,

Hailin

[jto2]

Hailin,

No, I'm not having problems with those drivers. They control the scope ok, including in averaging mode, which is where I'm having trouble with the Agilient 2000 3000 X-Series VISA drivers.

There are 2 no essential issues with the agx2k3k that I've come across with my scope (Agilent DSO-X-2004A). Mostly dealing with accessing the waveform measurements.

1. I can ask the scope to fetch measurements from my signal, like: frequency, Voltage pk-pk, etc., but I cannot make them ask the oscilloscope to display those measurements on the oscilloscope screen. There is a button on the front panel of the scope that allows me to view measurements along the side bar of the screeen. The Agilent 2000 3000 X-Series has a Configure Measurement Type VI that allows me to set the scope screen to display the measurements.

2. My scope has 4 different types of RMS voltage measurements it can do (DC, DC full screen, AC, AC full screen), but the IVI drivers (agx2k3k) only allow me fetch the DC RMS measurement. 

Besides that they seem to work ok. I've had an easier time with the VISA drivers, besides my problem with running the scope in averaging mode.

- John

[jto2]

I've narrowed the issue down a little bit. The 3000 and 4000 series scopes have selectable input impedances, and my 2000 series doesn't (it's fixed at 1Mohm, no option for 50 Ohm). 

So, the -220 Parameter error I was getting only occurs when I set the impedance to 50 Ohm, because my scope can't do that.

With the impedance fixed at 1 MOhm, I can run in Normal, Peak Detect, and High Res modes, but still not Averaging mode. That error is the same as posted in the earlier IO Trace file, even after I updated the firmware to its latest version 2.35.

- John

[Stephen.Schwahn]

Everyone,

For non-4k X-Series in average acquisition modes, you will need to make the change ":WAV:POIN:MODE NORM" instead of "WAV:POIN:MODE RAW" for a temporary workaround. We are working on a fix for this issue that will allow a more dynamic setting based on scope types.

Best regards,

Stephen Schwahn

Instrument Drivers

National Instruments

[stfung]

Stephen,

Has there been an update on this issue with the driver? I am running into some problems  with acquisition of averaged waveforms from a DSOX-2002A.

Thank you,

Stephanie

[hailin]

Hi Stephanie,

We have an update on this issue with the driver. You can download here.