Agilent ESA PSA configure acqusition vi error

[Ori_Idan]

I tried using the ESA PSA driver with LabVIEW 8.0

First I tried the configure vi to see that I am talking to the instrument, this works fine.

Then I tried the example "Agilent ESA PSA Series Acquire trance.vi" and got an error -113 undefined header.

Does someone have any idea what might cause this error?

--

Ori Idan

[nayer]

Hello Ori,

Undefined Header means the command is not supported by that instrument.  Here is a link to example programs and document for IM and FT for ESA and PSA series spec analyzer.

Good luck

NI-khil

[SunshineDesign]

Undefined header error does not mean the instrument command is not supported. It means that the instrument is in the wrong state for that command. I am finding a lot of errors and inappropiate grouping of functions in the ESA/PSA driver that do not work properly with the E4402B.

[Tanya_V]

What kind of problems are you seeing with this driver? Is there something that needs to be changed in the examples? If so, we would like to make the changes so the driver works correctly.

Thanks for the feedback!

[SunshineDesign]

Tanya I am glad you responded. I tried to work some changes to the driver last year and I was not able to find a responsible party (i.e. National or Agilent).to work the recommendations I have into the driver to fix the issues. I'd like to work with you to make a number of recommendations in terms of fixing some shortfalls in the driver and also change the command grouping that is current. The Undefined Header error is being thrown due to inappropiate command grouping and doing commands not appropiate for the state the instrument is in. I have worked extensively with the PSA and ESA not only in Spectrum Analyzer mode, but have also worked in the Modulation Measure mode and can make a significant number of suggestions to improve. Please feel free to contact me offline at my email SunshineDesign@cox.net (personal) or JCahak@DTWC.com (work) so we can follow thru on the suggestions. Thanks for replying on this and I look forward to working with you to address these issues and making a better driver. We have been considering rewriting this driver to fix the issues, but having National work it, keeping ownership and keeping the updates in the public domain is prefered. If you prefer to call my cell number is in the National database.

[Tanya_V]

We are definitely interested in your input in order to fix the driver. Could you send an email to instrument.drivers@ni.com? This will contact the person responsible for the fixing the drivers at National Instruments.

Thanks again for bringing this to our attention!