Latest Agilent MSO drivers not returning all waveforms

[tonysutton\]

HI

The firmware version is 01.00.2011011301

Files I have been using attached - updated as per thread

Thanks for the help

Tony

[Charles.Tac]

Hi Tony,

The package you uploaded seems work well on my instrument (ver. 01.10.2011042700 MSO-X 3024A ). I just added some VIs into the example "Acquire Waveform Continuously.vi". Wish the change would work for you. 🙂

Yours,

Charles

[jjp377]

Hi Tony,

There also seems to be a newer firmware version for the X-2000 series

Upgrading to the firmware might help - one of the enhancements according to the documentation include waveform Math functions.

[tonysutton\]

Thanks Charles and JJP

I have changed firmware to latest and tried both the files I have used before and Charles's new file and both give different errors.

The error message for my original files (with Charlse's earlier uploaded files included) is now:

Possible reason(s):

Instrument reports:
-224,"Illegal parameter value"
+0,"No error"

Complete call chain:
     Agilent 2000 3000 X-Series.lvlib:Error Query.vi
     Agilent 2000 3000 X-Series.lvlib:Autosetup.vi
     Agilent 2000 3000 X-Series Acquire Waveform Continuously no Reset.vi

For Charles's latest uplaoded file, I saw your FFT data still on screen when opening it, but when I ran it the scope settings changed and the FFT display changed significantly (all noise componnets gone)  and gave an error:

Possible reason(s):

Instrument reports:
-221,"Settings conflict"
+0,"No error"

Complete call chain:
     Agilent 2000 3000 X-Series.lvlib:Error Query.vi
     Agilent 2000 3000 X-Series.lvlib:Read Waveforms (Single).vi
     Agilent 2000 3000 X-Series Acquire Waveform Continuously.vi

Very frustrating!

Thanks

Tony

[jjp377]

Hi Tony,

We can work on creating a debug VI to try to capture more information, since we cannot reproduce the issue with the MSO-X 3024A we are working with now.

[jjp377]

Hi Tony,

Here is the test VI for the MSO-X 2000 scope.  Please run the VI and follow the intructions indicated in the front panel.

[tonysutton\]

Thanks

I ran the code as detailed on the screen and the two attached files show what was on the scope screen before I ran the vi, what was on the vi after run and what the scope screen looks like after the vi is run.

I didn't recieve any error message this time, so we could be getting there.

[Charles.Tac]

Oh, that's really a good news!

Notices that there is still a little bit different between the "before" and "after" scope screen image. The reason looks like they had different parameters settings for the FFT waveform (See fig 1).

Would you please try to change the input value of Vertical Scale and Vertical Offset parameters for "Configure Math Function Characteristic.vi" in the test VI (see fig 2). Whis that would change the position of FFT waveform to center of screen. 🙂

----------------

Fig 1

Fig 2

[tonysutton\]

Hi Charles

The debug program from JJP is the only program that runs with math channel and is different to the other programs. It does not show the offsets as you have them in your image. I opend "Configure Math Function Characteristic.vi" from the block diagram and changed the vertical offset to -66 on the front panel and it had no effect other than resetting my -66 back to 0 when i ran the main program.

I then enterred -66 on the front panel and ran just the "Configure Math Function Characteristic.vi" and it returned the scope display to how it should be. Partial result!! (no display on software of course)

Running the main vi always returns the vertical setting back to 0

Could someone please make the vi read the scope settings and use them when writing to the scope - or more logically, not alter the scope settings at all. Why does it write to the scope to change the settings???? I only want the PC to display what is on the scope and see no reason to write scale settings to it.

Could the changes made in the debug program be added to the original driver package with several example apps please?

Thanks for sticking with this

Tony

[Charles.Tac]

Hi Tony,

What you have tried are very very close to the correct solution.

As your requirement is to fetch the scope displayed FFT waveform. I made a little bit modification on JJP's debug VI. 

1. Forbidden instrument reset in Initialize.vi or a reset will clear all your previous settings on instrument.

2. Remove math channel configurations. Since you have manually configure the scope to MATH measurement. Not only these VIs are duplicate to the manual setting, but also the incorrect parameter input will even lead to a partial FFT waveform.

 Please try the VI in the attachment after manually setting the instrument to MATH mode and the acceptable FFT waveform is displayed.

Thank you for your patient in this thread. 🙂

Yours,

Charles