Agilent Technologies

Agilent E44xxB ESA VXIplug&play Instrument Driver Read Me

Agilent Technologies ESA-E and ESA-L Series Spectrum Analyzer
Universal Instrument Driver (UID)
Driver Revision A.03.00
Instrument Firmware Revision Supported: A.04.07
Powersuite: A.01.03
Option BAC CDMA: A.01.04
Option BAH GSM: A.01.03
8 August 2000

Revision History


A.03.00 8 August 2000 Shipment Release - Complete Driver

Instrument Firmware Revision Supported: A.04.07
Powersuite: A.01.03
Option BAC CDMA: A.01.04
Option BAH GSM: A.01.03

This driver adds support for:
cdmaOne Mode Setup
cdmaOne Radio Setup
cdmaOne Input Setup
cdmaOne Demod Setup
GSM Mode Setup
GSM Radio Setup
GSM Input Setup
GSM Trigger Setup
GSM Demod Setup
GSM Frequency Control
GSM Measurements
GSM Transmit Power (TXP)
GSM Power vs Time (PVT)
GSM Phase & Frequency Error (PFER)
GSM Output RF Spectrum (ORFS)
GSM Transmit Band Spurs (TSP)

Note 1: For the hpesa_GSM_ORFMeasureTrace function, Results
Type 3 may cause a system error with some firmware 
versions. See the online help for more information.

A.02.00 05 May 2000 Shipment Release - Complete Driver

Instrument Firmware Revision Supported: A.04.07

This driver adds support for Cdma1 Mode Setup &
Cdma1 Trigger Setup
Cdma1 Frequency control
Cdma1 Channel Power (CHP)
Cdma1 Modulation Accuracy (RHO)
Cdma1 Code Domain Power (CDP)
Cdma1 Close Spurs Power (CSP)
Cdma1 Spurs at Harmonics (SHP)

Note 1: hpesa_harmonicDistConfig and hpesa_harmonicDistConfigQuery 
functions have been updated to be compatible with ESA
firmware releases A.03.03 and above.

Note 2: The function hpesa_cdma1_CSPMeasure currently returns 
invalid measurement data when used with ESA instrument
firmware version A.04.07. This is a known problem with
the A.04.07 firmware implementation of the "MEAS:CSP1?" 
SCPI command. The difficulties with this command will be
fixed in a future instrument firmware revision. In the 
meantime, use the hpesa_cdma1CSPMeasureTrace function 
with results type 1 to view the unfiltered spur measurement

A.01.02 30 Jun 1999 Shipment Release - Complete Driver
Instrument Firmware Revision Supported: A.01.03
This driver adds support for Measurement types:
Adjacent Power (ACP)
Channel Power (CHP)
Occupied Bandwidth (OBW)
Emission Bandwidth (EBW)
Harmonic Distortion

A.01.01 11 Jun 1999 Shipment Release - Complete Driver

A.01.00 01 Jun 1999 Shipment Release - Complete Driver



1.0 Introduction

2.0 VTL/VISA Specific Information

2.1 Instrument Addresses

2.2 Language Specific Features

3.0 Using the Agilent Technologies ESA UID in Application Development 

3.1 Microsoft Visual C++ 5.0 (& higher) 
and Borland C++ 4.5 (& higher)

3.2 Microsoft Visual Basic 5.0 (& higher) 

3.3 LabWindows CVI/(R) 4.0.1 (& higher)

4.0 Known Defects
4.1 Functions that accept GSM constants may not handle these constants

5.0 Online Information


1.0 Introduction

The help file included with the Agilent Technologies ESA UID 
contains instrument and programming information. This readme 
file contains additional information concerning the driver.

The Agilent ESA Windows 95 and Windows NT drivers are 
actually a single 32-bit driver. All of the directory 
paths which follow assume Windows 95. For Windows NT, 
change references from win95 to WinNT. 

This Agilent ESA driver conforms to all portions of the 
VXIplug&play driver standard which are applicable to 
conventional GPIB. Two elements of the standard do not 
apply to the ESA since it is not a VXI instrument. 
First, there is no soft front panel, as the ESA can be 
controlled from its hardware front panel. Second, there 
is no knowledge base file, which is primarily a description 
of a VXI board.

This driver features:

1. Conformance with the VXIplug&play standard. The 
only exceptions are that it does not have a soft 
front panel or a knowledge base file.

2. It is built on top of, and uses the services provided 
by VISA. VISA supports GPIB and VXI protocols. The 
driver can be used with any GPIB card for which the 
manufacturer has provided a VISA DLL.

3. It includes a "Function Panel" (.fp) file which allows 
it to be used with visual programming environments 
such as Agilent VEE, LabWindows, and LabVIEW.

4. It includes a comprehensive on-line help file which 
complements the instrument manual. The help file 
presents application programming examples, a 
cross-reference between instrument commands and 
driver functions, and detailed documentation of each 
function, with examples.

5. Source is included so that the driver can be modified 
if desired. The source conforms to VXI Plug & Play 
standards. Modifications should only be done by 
people who are familiar with the VXIplug&play 

6. It includes a Visual Basic include file (.bas) which 
contains the function calls in Visual Basic syntax, so 
that driver functions can be called from Visual Basic. 
If you use Visual Basic with this driver, you should be 
familiar with C/C++ function declarations. In particular, 
care must be taken when working with C/C++ pointers.


2.0 VISA Specific Information

The following topics refer to instances when the driver is 
used with different versions of VISA.

2.1 Instrument Addresses

When using Agilent Technologies UID, instrument 
addresses must be all uppercase letters. Implementation of 
the addressing scheme is vendor specific and some 
vendors support mixed cases. However, for maximum 
portability, the instrument address should use uppercase 
characters only.

For example: use "GPIB0::18" instead of "gpib0::18"

2.2 Language Specific Features

Language Specific features are not supported with this 


3.0 Using the Agilent Technologies ESA UID in Application Development Environments 

For general instructions on using the driver with Agilent VEE, 
Microsoft Visual C++, Borland C++, Microsoft Visual Basic, 
LabVIEW, and LabWindows/CVI, see the online help file.

Additional notes:

3.1 Microsoft Visual C++ 5.0 (& higher) and 
Borland C++ 4.5 (& higher)

1. The driver uses Pascal calling conventions.
2. Do not build the driver in the directory in which 
it was installed.

3.2 Microsoft Visual Basic 5.0 (& higher) 

Refer to the Microsoft Visual BASIC manual for additional 
information on calling DLLs.

3.3 LabWindows CVI/(R) 4.0.1 (& higher)

The Agilent Technologies ESA driver is supplied as both a source code file 
and as a dynamic link library file (dll). There are 
several advantages to using the dll form of the driver. 
These include:

1. Transportability across different computer 
2. A higher level of support from Agilent for 
the compiled driver
3. Faster load time for your project

LabWindows/CVI (R) by default will attempt to load the 
source version of the instrument driver. To load the dll 
you must include the file hpesa.fp in your project. 
This file can be found in vxipnpwin95hpesa. Do not 
include hpesa.c in your project. You must also provide 
an include path for hpesa.h. This is done by adding 
vxipnpwin95include to the include paths (CVI Project 
Option menu).


4.0 Known Defects

There are no known defects in the Agilent ESA driver.


5.0 Online Information

The latest copy of this instrument driver and other Agilent instrument
drivers are available at the Agilent Technologies customer WWW site:

If you do not have Internet access, the drivers can be obtained by
contacting your country support organization. In the US, the phone
number is 800-452-4844. A list of contact information for other
countries is available on the Access Agilent Technologies website: (two zeros at the end)


LabWindows/CVI is a registered trademark of National 

© Agilent 2000-2006