Spectrum Analyzer

[underdog]

Hi.
I've got a problem when trying to automate Agilent 44XX Spectrum Analyzer.
First of all it's running O'kwith Highlight Execution(the Bulb).
I succesfuly passed previous measurement and Setup Spectrum to current measurement properly. But when I do Peak search I get incorrect value (noise floor value). I tryed to put simple delay in SA sequence (packed in subVI with Visa & Error) it doesn't work ????
I've used this drivers before & it worked O'k in other parts of programs.
Thank you in advance.

[TongY]

So the exact same code runs file with Highlight Execution turned on? And you can measurem the current peak correctly? If this is the case, what is the difference between your desired value and the "wrong" value?

You said the usinga smal delay didn't work, what kind of error did you receive, a timeout? If the only difference between working and nonworking condition are the execution speed, maybe the data was read in too fast.

[underdog]

Hi & thank you for responce.
Actualy the wrong value I get was noise level value (-40dBm in my case) instead of expected +27dBm, that I get in Highlight Execution.

In fact the delay wasn't so small, I increased it up to 3sec. It just wasn't executed & no error was received.
If the data was read in too fast, how can I prevent this?

[TongY]

It looks like this issue definitely has something to do with timing. You may need a longer delay for your code to be executed, if your measurement started before the data is actually ready, you will probably receive the wrong vale.

To introduce a delay before the acquisition starts, you can insert a single sequence structure in your code that has a "wait" in there, I would use a bigger value than 3 seconds since Highlight Execution is delays the program much longer than 3 seconds.

[underdog]

Well I do use a sequence strucutre before the command.
The delay time isn't the issue, because I can't see it running at all.
From Agilent support I understood that FW upgrade may solve the problem. I'll try 🙂

[JLS]

Hello,

Great, give that a try and repost if you continue to have problems!

Thanks,

JLS

[basyarie]

Dear senior NI users,

I am a new member of this discussion forum, and also new user of LabVIEW, would like to ask everyone who knows well about LabVIEW programming in particular building an application to analyze and control the spectrum analyzer output as required.

In my case, now I am facing the problem to make the program. Here, I explain my designed system:
The system consists of one spectrum analyzer (Anritsu MS-2663B or Agilent E4403B), laptop,GPIB-USB-HS cable, and receiving antenna which is connected to RF input connection.
I want to retrieve and control the data (received power of antenna) using LabVIEW v.8.0.1
I have installed each analyzer driver (both of MS-266x family and E4403B --GPIB purpose--) to the laptop.
Unfortunately, I am new user in such kind of programming (usually with text-based programming), so I would like to askeverybody who knows about it.
My questions:
1. How can I start to make a program? Is it possible to control spectrum anlyzer using GPIB-USB-HS cable? How about serial cable?
2. Is there any sample program for such applications?

Thanks a lot.
Cheers,

[BerkO]

Hello Basyarie,

Welcome to the NI discussion forum.  In the future, please create a new thread for a new question so that we can keep track of things better.

As for your question, you can find information on how to use instrument drivers here.

All of our certified drivers contain examples which demonstrate the basic operation of the instruments. You can refer to the examples and easily modify them to acquire the desired measurement.

Both of the drivers that you need only support GPIB. If the instrument that you have has serial interface you would have to modify the Initialize VI to set the VISA serial settings to match the settings of your instrument.  I would recommend using GPIB over serial since VISA takes care of GPIB communcation completely without you needing to change settings.

I hope it helps. Please post any furter questions under a new thread. Thank you! Good luck.

[basyarie]

Dear Mr. Berk,

Thanks a lot for the beginning advice.
As for your advices, I already tried both of Agilent and Anritsu spect. analyzer. I 've been using LabVIEW v.8.2 with Japanese language.
Once installing the driver by automatic find instrument driver menu, I safely installed the driver of Agilent E440x family, but unfortunately I didn't find the driver for Anritsu (MS2663B) by finder menu. So, I tried searching on the NI instrument driver website and I found  it in the package of ms266578 for MS266x family via third party, namely Anritsu homepage.
Then, because the driver in .zip file, I extracted it on the  C:\Program Files\National Instruments\LabVIEW 8.2\ms2663.lib

I would share my test results both of them using example .vi file.
A. Agilent E4403B (f= 9kHz until 3 GHz)
- configuration: Analyzer, laptop (windows xp), GPIB-USB-HS cable (autodetect driver).
- tested file: Agilent ESA PSA Series Acquire Trace.vi (see front panel in attachment file)
- result: GPIB number was detected as 18, and Analyzer display showed in "remote mode (indicated by letter R on the display)", with start and stop frequency were displayed well.
- error message:
  --> on the analyzer display: undefined header
  --> on the labVIEW: same with specific report (see deatils in the attachment)

I don't know what is the function of such .vi example. But, in my thought this program just to trace frequency and show it on the output display panel.

B. Anritsu MS2663B (f=9 kHz - 8.1 GHz)
- configuration: same as above.
- tested file: MS266578 example.vi (I didn't attach it) for tracing start and stop frequency and show it on the front panel.
- result: Analyzer display showed nothing change.
- error message: Error -1073807304, in this place is generated(in japanese): VISAwrite-in/MS266578 Freq-amp Log-Lin range.vi->MS266578 Example.vi

It seems error in "query" to Analyzer.

I would be grateful hearing your advices again.

regards,
basyarie

[basyarie]

This is attachment, because I had problem to upload it.