Using Instruments - Keysightliterature.cdn.keysight.com/litweb/pdf/rfde2002c/pdf/rfd... · 2002. 7....

Using Instruments

September 2002

Notice

The information contained in this document is subject to change without notice.

Agilent Technologies makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Agilent Technologies shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.

Warranty

A copy of the specific warranty terms that apply to this software product is available upon request from your Agilent Technologies representative.

Restricted Rights Legend

Use, duplication or disclosure by the U. S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 for DoD agencies, and subparagraphs (c) (1) and (c) (2) of the Commercial Computer Software Restricted Rights clause at FAR 52.227-19 for other agencies.

Agilent Technologies395 Page Mill RoadPalo Alto, CA 94304 U.S.A.

Copyright © 1998-2002, Agilent Technologies. All Rights Reserved.

ii

Contents1 Using Instrument Interfaces

GPIB Interfaces .................................................................................................. 1-1Configuring the Driver for the GPIB Interface..................................................... 1-2

2 Instrument ServerInstallation Requirements ......................................................................................... 2-2Starting and Exiting the Instrument Server............................................................... 2-2Parts of the Instrument Server ................................................................................. 2-3Connecting to Instruments........................................................................................ 2-5Data Transfer Considerations ................................................................................... 2-6Reading from and Writing to Files ............................................................................ 2-6

Reading a File .................................................................................................... 2-9Writing to a File .................................................................................................. 2-10

Reading and Writing Network Analyzer Data ........................................................... 2-11Network Analyzer Data Formats......................................................................... 2-11Using the Agilent E8358A Network Analyzer .................................................... 2-12Using Agilent 87xx-Series Network Analyzers .................................................. 2-12Using Agilent 8752 Network Analyzers ............................................................. 2-13Using Agilent 8510 Network Analyzers ............................................................. 2-14Reading Instrument Data from a Network Analyzer ........................................... 2-15Writing Data to a Network Analyzer ................................................................... 2-16

Reading and Writing Spectrum Analyzer Data ......................................................... 2-17Reading Instrument Data from a Spectrum Analyzer......................................... 2-17Writing to a Spectrum Analyzer.......................................................................... 2-19

Reading and Writing Oscilloscope Data ................................................................... 2-20Reading Instrument Data from an Oscilloscope................................................. 2-21Using Agilent 541xxx-series Oscilloscopes ....................................................... 2-21Writing Advanced Design System Data to an Oscilloscope ............................... 2-23

Reading and Writing Microwave Transition Analyzer Data ....................................... 2-24Reading Instrument Data from an MTA .............................................................. 2-25Writing Data to an MTA ...................................................................................... 2-27

Specifying a Symbolic Interface Name..................................................................... 2-28Specifying a Transfer Timeout .................................................................................. 2-28Entering Comments into a Dataset........................................................................... 2-29

3 CITIfile Data Format ReferenceCITIfile Data Formats ............................................................................................... 3-1

Data Formats...................................................................................................... 3-1File and Operating System Formats................................................................... 3-2

CITIfile Definitions .................................................................................................... 3-2

iii

Package.............................................................................................................. 3-2Header................................................................................................................ 3-3Data Array .......................................................................................................... 3-3Keywords ............................................................................................................ 3-3

CITIfile Examples ..................................................................................................... 3-3Display Memory File........................................................................................... 3-3Agilent 8510 Data File ........................................................................................ 3-4Agilent 8510 3-Term Frequency List Cal Set File ............................................... 3-4

CITIfile Keyword Reference ...................................................................................... 3-6CITIfile Guidelines .................................................................................................... 3-9Converting Between Disk Formats ........................................................................... 3-10

HFS .................................................................................................................... 3-10DOS.................................................................................................................... 3-11

CITIfile Device-specific Definitions ........................................................................... 3-11Network Analyzer (#NA) Definitions ......................................................................... 3-11

Data Grouping .................................................................................................... 3-11Network Analyzer Keywords............................................................................... 3-11

Error Array Numbering ............................................................................................. 3-13Disk Filename Requirements ................................................................................... 3-14Agilent 8510 Series CITIfile ...................................................................................... 3-14Agilent 8700 Series CITIfile ...................................................................................... 3-15

4 Touchstone Data Format ReferenceSpecifying Units and Impedance .............................................................................. 4-1

Syntax ................................................................................................................ 4-1Example ............................................................................................................. 4-1

Entering Data Values................................................................................................ 4-2Example ............................................................................................................. 4-2

Noise Parameters ..................................................................................................... 4-3Example ............................................................................................................. 4-3

5 Command ReferenceFile Menu.................................................................................................................. 5

Close Window..................................................................................................... 5HP-IB Menu .............................................................................................................. 5

Symbolic Name .................................................................................................. 5Timeout .............................................................................................................. 5

Help Menu ................................................................................................................ 5What’s This?....................................................................................................... 5Topics and Index................................................................................................. 5Agilent EEsof Web Site ...................................................................................... 6About the Instrument Server .............................................................................. 6Read Instrument (Button) ................................................................................... 6

iv

Chapter 1: Using Instrument InterfacesThere are two different approaches to using instruments:

• Using the Instrument Server – for more information, refer to “Instrument Server” on page 2-1.

• Using the Instrument Components (ADS only) – for more information, refer to “Instrument Components” in the Signal Processing Components manual.

Note: Instrument connectivity is supported on the Windows® 2000, Windows NT® 4.0 and Windows XP platforms only. On Unix® platforms, instrument connectivity is not supported.

GPIB Interfaces

If you use GPIB interfaces, Advanced Design System supports the following GPIB hardware and software interface kits.

Note For the lastest information refer to this manual on our website at: http://www.agilent.com/find/eesof-docs.

Description Part Number

Agilent LAN/GPIB Gateway Interface/ SICL drivers E2050A/B w/ Opt AG6

Agilent LAN/GPIB Gateway Interface/ SICL drivers E5810A

Agilent USB/GPIB SICL/VISA drivers 82357A

Agilent GPIB PCI card / SICL drivers 82350A

Agilent GPIB EISA card / SICL drivers 82341C

National Instruments AT-GPIB/TNT card/NI-488.2M drivers 776836-01

National Instruments PCMCIA-GPIB card/NI-488.2M drivers 777332-02

National Instruments PCI-GPIB card/NI-488.2M/SICL drivers 777073-01

1-1

Using Instrument Interfaces

Configuring the Driver for the GPIB Interface

Your GPIB interface includes the software necessary for an application to use the facilities the interface provides. The software typically has two components:

• A kernel driver (also known as a device driver)

• An application interface DLL, which interfaces with the kernel driver

For Windows, the most recent version of the SICL drivers may be downloaded from the Agilent IO Libraries website located at:

http://www.agilent.com/find/iolib

The downloaded file is executable. To install the Agilent IO Libraries run this file and follow the installation instructions supplied with it.

After installation is complete, run the IO Config program by selecting Start > Programs > Agilent IO Libraries > IO Config from the Windows main screen. The following graphic illustrates the IO Config application.

1-2

To use a GPIB card installed locally on the PC, from the Available Interface Types field, select the relevent GPIB option (based on the Interface Description provided on the right hand side) and click Configure > OK. The default settings are correct.

To use a remote LAN/GPIB gateway, from the Available Interface Types field, select Lan Client (Lan Instruments) > Configure > OK. The default settings are correct.

Note If the Instrument Server reports it’s unable to find an interface, check to see if the system path contains either gpib-32.dll, sicl32.dll or both. If it does, check to see that the path you supplied is correct.

Setting Enviroment Variables

To set an Environment Variable:

• From the Windows NT main screen, choose Start > Settings > Control Panel > System > Environment and enter the variable name and value.

• From the Windows 2000 main screen, choose Start > Settings > Control Panel > System > Advanced > Environment Variables and enter the variable name and value.

For example:

Variable Value

PATH C:\WINNT\System32;

1-3

Using Instrument Interfaces

1-4

Chapter 2: Instrument ServerThe Instrument Server provides a way to read in data from sources such as a network analyzer or Touchstone file into a dataset. The Instrument Server also writes data from a dataset to an instrument or file.

Applications for using transferred data include:

• Reading measured instrument data into a dataset, and comparing measured data to simulation results in a data display.

• Reading data into a dataset for use with components, such as the VtDataset source, that can read data from a dataset.

• Writing S-parameters from a dataset to a specific file type. The S-parameter file can then be read by a component, such as a P2D amplifier.

• Transferring data between other simulation products such as Series IV, MDS, Agilent HFSS, or IC-CAP.

These are just a few examples, there are many other applications for transferring data between Advanced Design System and outside systems.

This chapter describes how to transfer measured data between datasets and files, network analyzers, spectrum analyzers, oscilloscopes, and the Agilent 70820A Microwave Transition Analyzer.

The Instrument Server can transfer data between many instrument models and file formats. A list of supported instruments appears at the start of each section.

Note Currently, instrument connectivity for the Instrument Server is only supported on the following platforms: Windows NT 4.0, Windows 2000, Windows XP. On UNIX platforms, the Instrument Server supports file translation capablities, however it does not support instrument connectivity.

2-1

Instrument Server

Installation Requirements

Note For details on the hardware and software installation, refer to “Using Instrument Interfaces” on page 1-1.

To use the Instrument Server, you must first perform the following installation steps:

• Install a GPIB card and software in your computer

• Run any installation procedures to set symbolic names, bus speed, et cetera.

• Set GPIB and Instrument Server configurations in Advanced Design System

Note As part of the interface card installation, a symbolic name is assigned to the card. When you install the card, make a note of this name, you will need it when you use the Instrument Server. For details on specifying a symbolic name, refer to “Specifying a Symbolic Interface Name” on page 2-28.

Starting and Exiting the Instrument ServerYou can start the Instrument Server from a Schematic window or a Data Display Window.

• From a Schematic window, choose, Window > File/Instrument Server. Or, click the Instrument Server icon.

• From a Data Display window, click the Instrument Server icon.

To exit the Instrument Server, choose File > Exit from the Instrument Server menu bar.

2-2 Installation Requirements

Parts of the Instrument ServerThe following illustration shows the default appearance of the Instrument Server user interface for a UNIX based system when the Instrument Server is started.

The layout of the interface and names of the various elements vary with the task being performed (read or write) and whether a file, network analyzer, spectrum analyzer, oscilloscope, or microwave transition analyzer is selected.

Note Instrument options are not available on UNIX.

This variation in the appearance of the Instrument Server user interface is evident in the following illustration, which shows the appearance of the interface when it is configured for instrument options on a Windows based system.

Menu bar

Availableand selecteddatasets

Availableand selectedvariables

Read sourcesand writedestinations

Instrumentandfile options

Parts of the Instrument Server 2-3

Instrument Server

The following are the more frequently used elements of the interface:

• The Menu bar displays the menus that are available in a data display window.

• Read and Write display lists of items that you can read from and write to. Depending on your selection, additional instrument and file options are displayed.

• Display Status Log activates the transfer of information to the Status Server. Any errors that occur during the data transfer or messages that indicate the progress of the transfer will appear in this window.

• Display Comments Dialog enables you to add comments to a dataset.

• The Dataset field list the datasets in the current project. The selected dataset or the name of a new dataset is displayed in the Dataset Name field.

• The Blocks field lists the blocks (variables) in the selected dataset. The selected block is displayed in the field below the list.

2-4 Parts of the Instrument Server

Connecting to InstrumentsSeveral interface bus choices must be specified when you transfer data to or from an instrument (Windows based systems only).

Data is transfered via the GPIB interface. (References to HP-IB in this text also refer to GPIB).

To configure the interface bus, do the following:

1. Choose HP-IB > Timeout. The HPIB Timeout dialog box appears.

2. Enter the amount of time, in seconds, allowed to transfer data and click OK.

When this time is exceeded, the communication between the instrument and computer is terminated. Do not specify an excessively long time because if the data transfer fails, it may be difficult to terminate the connection between the computer and the instrument until the time has expired. If you do not specify a time interval, a default value of 10 seconds is used.

3. Choose HP-IB > Symbolic Name. The HPIB Symbolic Name dialog box appears.

4. Enter the symbolic name of the interface card and click OK.

This name is required to transfer data via GPIB. For details on specifying a symbolic name, refer to “Specifying a Symbolic Interface Name” on page 2-28.

5. The HP-IB Address field enables you to the identify the instrument that you want to connect to by GPIB address.

The steps to complete these settings begin with “Specifying a Symbolic Interface Name” on page 2-28.

Connecting to Instruments 2-5

Instrument Server

Data Transfer ConsiderationsTo ensure successful data transfers, before initiating a transfer, be sure to:

• Specify a timeout duration which is sufficient to complete the data transfer from an instrument.

• Set the instrument to hold or single sweep mode. This is particularly important when retrieving averaged data from an instrument, or the data acquisition time for an instrument is relatively long.

• Do not change any settings on an instrument while a transfer is in progress.

• Not all instruments have the same memory or trace locations, so be sure to select a location that is valid for your instrument or an error will occur when you attempt to transfer data.

• You may need to perform several transfers in order to place data in a final format. For example, you may have S-parameters in a Touchstone file and want them in P2D format. You would read the S-parameters from the Touchstone file to a dataset, then write the data from the dataset and into a P2D file.

Reading from and Writing to FilesYou can transfer data between datasets and files that are in the following file formats:

• Touchstone

• CITIfile

• IC-CAP

• Measurement Data Interchange Format (MDIF)

You can transfer data from a file into a dataset, or vice versa. One application is to transfer data from a dataset to an MDIF file, for use with a specific type of component. For example, a file in P2D format (P2D is one of several MDIF formats) containing S-parameters can then be used by the P2D amplifier. Using the Instrument Server, you can write S-parameters from a dataset to a file in P2D format. Another application is reading Agilent IC-CAP data into a dataset to be used in conjunction with a component, such as a source, that can read data from a dataset.

There are some specific problems with the current version in writing and/or reading this data format. On the Agilent EEsof web site, refer to the Release Notes in Product

2-6 Data Transfer Considerations

Documentation and to Technical Support for more information and workarounds (www.agilent.com/find/eesof).

The following table lists available file types, a description of the file contents, and the component that uses the data. Be sure to review the notes at the end of the table. For details about each file format, refer to the Circuit Simulation manual.

Table 2-1. Available File Format Types

Format Description Usage

Touchstone (SnP) Format

SnP†,†† Small signal S, H, Y, Z, or G -parameters. May also include optional noise data (2 port data only). Where n is the number of ports from 1 to 99.

n-Port S-parameter file (SnP) components in the Data Items Library.

CITIfile Format

CITI††† A general data format supported by network analyzers. Capable of storing multiple packages of multi- dimensional data.

S#P #-Port S-parameter file components in the Data Items Library.

Agilent IC-CAP Formats

† When writing data from a dataset to a file, the variable names are limited to S,H,Y,Z or G, for example, S[1,1], S[1,2], G[1,1], G[1,2]. The variable name is used to determine the type of data.†† The first set of data in the dataset that matches the data type (name) will be output. It is not possible to arbitrarily select which data will be will be output.††† There are some specific problems with the current version in writing and/or reading this data format. On the Agilent EEsof web site, refer to the Release Notes in Product Documentation and to Technical Support for more information and workarounds (www.agilent.com/find/eesof).‡ You can read in IC-CAP data only.‡‡ Only simple, scaled expressions with numbers or variables and one operator (either +, -, *, or /) are supported for start, stop, step, and number of points parameters, for example, start= 1 GHZ or stop=icmax/10. ‡‡‡ This format is not yet fully supported.

The COD, FIR, LAS, and SPE formats were obsolete when ADS 1.0 was introduced and are not used by the application. The LIST2 and T2D formats are also obsolete.

Reading from and Writing to Files 2-7

Instrument Server

DUT, MDL,

SET‡,‡‡ Device under test (DUT), model (MDL), and setup (SET) files from the Hewlett Packard IC-CAP program. These files can contain Measured, Simulated, and/or Transformed data.

Once the data is read into a dataset, it can be used with any component (for example, a VtDataset source) that can read data from a dataset.

Table 2-1. Available File Format Types (continued)




2-8 Reading from and Writing to Files

MDIF Formats

DSCR Discrete (indexed) tabular and possibly statistical density data.

DAC

GCOMP†† Gain compression data Amplifier and Mixer items in the System - Amps & Mixers library.

GEN_MDIF Generalized multi-dimensional tables unifying other MDIF formats.

DAC

IMT†† Intermodulation product table of mixer intermodulation products between the LO and signal that relates the mixer IM output level to signal input level.

MixerIMT in the System - Amps & Mixers library.

MODEL_MDIF Nonlinear model parameters EEFET1, BJTAP, etc.

P2D†,†† Large-signal, power-dependent, 2-port S, H, Y, Z, or G -parameters.

AmplifierP2D item in the System - Amps & Mixers library.

PDF‡‡‡ User defined, piece-wise linear probability density function data.

With expressions in the Statistics tab.

S2D†,†† 2-port S, H, Y, Z, or G-parameters with gain compression and optional noise and intermodulation data.

Amplifier S2D, Amplifier, and Mixer items in the System - Amps & Mixers library.

S2PMDIF Multi-dimensional 2-port, S, Y, Z, H, G signal and optional 2-port noise parameter (Fmin, Gopt, Rn) data.

With S2PMDIF and DAC






Instrument Server

Reading a File

To read the contents of a file into a dataset:

1. From an open Instrument Server window, click READ.

2. Under Read From, click File.

3. Under File Format to Read From, select one of the following file formats:

• Touchstone

• MDIF

• CITIfile

• ICCAP

4. For MDIF files, choose the appropriate file subtype fromMDIF Sub File.

SDF††,††† Time-domain voltage data file in 89440 file format.

TimeFile item in Timed Sources and OutFile item in Sinks library.

SPW†† Time-domain voltage data file in Cadence Alta Group SPW format

TimeFile item in Timed Sources and OutFile item in Sinks library.

TIM†† Time-domain data TimeFile item in Timed Sources and OutFile item in Sinks library.





2-10 Reading from and Writing to Files

5. Under File Name, type in the filename if the file is in the project. If it is not, click Browse to locate and select the file.

6. Click Display Status Log to view any messages and errors that may occur during the transfer.

7. Click Display Comments Dialog to add comments to a dataset. For instructions, refer to “Entering Comments into a Dataset” on page 2-29.

8. The data from the selected file will be written to a dataset. Enter a name in the Dataset Name field or select from the existing datasets in the Datasets list. If you choose a dataset from the list, any data that is already stored in the dataset will not be saved and will be overwritten with new data.

9. Click Read File to send the file contents to the dataset.

Note The source file must not use any ADS reserved variables. Use of such a file can produce misleading results.

Writing to a File

To write data to a file:

1. From an open Instrument Server window, click WRITE.

2. Under Write To, click File.

3. Under File Format to Write To, select one of the following file formats:

• Touchstone

• MDIF

• CITIfile

4. Under File Name, type in the filename you want to write to. It will be saved in the project directory. If you want to save the file in a different location, click Browse to select a location.


6. Click Display Comments Dialog to view comments in a dataset. For instructions, refer to “Entering Comments into a Dataset” on page 2-29.


Instrument Server

7. The source of the data can be any project dataset. Select an existing dataset from the Datasets list.

8. Click Write to File to send the data to the file.

Reading and Writing Network Analyzer DataData can be transferred to and from the following network analyzers.

Network Analyzer Data Formats

The network analyzer stores measurements as raw, corrected, or formatted data, depending on the settings of the network analyzer:

Table 2-2. Network Analyzer Data

Model Number Description

Agilent E8358A 300 kHz - 9 GHz VNA †

†Instrument Server does not support writing data to the analyzer waveform memory.

Agilent 8510B/C High Performance uW VNA

Agilent 8712X 300kHz - 1.3 GHz Low Cost (Trans, Refl) RF VNA

Agilent 8714X 300kHz - 3 GHz Low Cost (Trans, Refl) RF VNA

Agilent 8719X 50 MHz – 13.5 GHz VNA

Agilent 8720X 50 MHz – 20 GHz VNA

Agilent 8722X 50 MHz – 40 GHz VNA

Agilent 8752X 300kHz - 6 GHz Reflection Transmission VNA

Agilent 8753X 30kHz-6 GHz High Performance RF VNA

Agilent 8702X 300 kHz - 6 GHz Mod Freq Lightwave Component Analyzer

Agilent 8703X 130 MHz - 20 Ghz Mod Freq Lightwave Component Analyzer

Wiltron 360 High Performance uW VNA

Agilent E880X 300 kHz - 9 GHz Performance Network Analyzer†

Agilent E835X 300 kHz - 9 GHz Performance Network Analyzer †

Agilent N338X 300 kHz - 9 GHz Performance Network Analyzer†, ††

††Instrument Server will only support reading S parameters from ports 1 and 2.

Agilent E836X 45 MHz - 50 GHz Performance Network Analyzer†

2-12 Reading and Writing Network Analyzer Data

• Raw data are the values measured at the detector, with no correction or alteration.

• Corrected data are the values measured at the detector, plus correction data applied.

• Formatted data is corrected data plus any averaging, smoothing, or other processes that can be applied with network analyzer.

Most Agilent Analyzers have two channels, each having its own set of raw, corrected and formatted data arrays. For all analyzers except the 8712 and 8714 the instrument server accesses the data in channel 1 only.

Using the Agilent E8358A Network Analyzer

The instrument server has the ability to interface with the Agilent E8358A network analyzer. The instrument server reads from the Channel 1 data arrays. There are three NWA data formats to choose from.

• Formatted Transfer the data in the analyzer’s Formatted data array to the dataset.

• Corrected Transfer the data in the analyzer’s Corrected data array to the dataset.

• Raw Transfer the data in the analyzer’s Raw data array to the dataset. Raw data for all four S parameters is available regardless of whether a full 2-port-calibration is in effect.

Data is always stored in the dataset variable as complex real imaginary pairs of the requested S parameters.

The instrument server will expect the data in the dataset to be complex.

Using Agilent 87xx-Series Network Analyzers

The instrument server reads from and writes to the Channel 1 data arrays. The data of interest in channel 1 does not have to be currently displayed to be read. If averaging is ON, the instrument server will put the instrument in HOLD mode before reading the data. Therefore make sure that the instrument has sufficiently averaged the data before reading the array.

In Read Mode there are three NWA data formats to choose from.

Reading and Writing Network Analyzer Data 2-13

Instrument Server





In Write Mode there are two NWA Data Locations to choose from.

• Memory Transfer complex data from the selected dataset variable to the Channel 1 Memory array.

• Raw Transfer complex data from the selected dataset variable to the Channel 1 Raw data array. If a full 2-port-calibration is in effect, any of the four S-parameters can be written to the 4 available raw data arrays. If a full 2-port-calibration is not in effect, S11 data must be selected in order to write to the single Raw data array available.

The instrument server will expects the data in the dataset to be complex.

Using Agilent 8752 Network Analyzers

Only S11 (reflection) and S21 (transmission) data can be read from or written to an Agilent 8752 network analyzer. This network analyzer only makes reflection and transmission measurements, and reading or writing data for other parameters produces unpredictable results.

Before data is written into a raw data array in the Agilent 8752 network analyzer, the error correction that is built into the instrument must be turned off. This is not necessary if data is written into memory in the instrument.

To turn off error correction in the Agilent 8752, follow these steps:

1. Press the menu key SYSTEM.

2. Press the function key SERVICE.

3. Press the function key SERVICE MODES.

4. Press the function key MORE.


5. Press the function key FREQ RESP to turn off the calibration.

When this has been complete, you can write data into the raw data array in an Agilent 8752 network analyzer.

Note Be sure to turn on error correction before making additional measurements with the network analyzer.

Using Agilent 8510 Network Analyzers

The instrument server reads from and writes to the Channel 1 data arrays. The data of interest in channel 1 does not have to be currently displayed to be read. If averaging is ON, the instrument server will put the instrument in HOLD mode before reading the data. Therefore make sure that the instrument has sufficiently averaged the data before reading the array.

In Read mode there are three NWA data formats to choose from.





In Write mode there are two NWA data locations to choose from.

• Memory Transfer complex data from the selected dataset variable to the Channel 1 Corrected data array.

• Raw Transfer complex data from the selected dataset variable to the Channel 1 Raw data array. If a full 2-port-calibration is in effect, any of the four S-parameters may be written to the 4 available raw data arrays. If a full 2-port-calibration is not in effect, S11 data must be selected in order to write to the single Raw data array available.

The instrument server will expects the data in the dataset to be complex.


Instrument Server

Reading Instrument Data from a Network Analyzer

To read measured data from a network analyzer:

1. Configure the network analyzer by setting the stimulus, calibration, and other parameters.


3. Under Read From, click Network Analyzer.

4. Under NWA Data Format, select one of the following formats:

• Raw

• Corrected

• Formatted

5. Under Read Network Analyzer Data, select the S-parameters that you want to use as the data source. You can select one set of the S-parameters or create an S-matrix of all S parameters.

Note For PNA’s that have more than two ports, the Instrument Server will only support reading S parameters from ports 1 and 2. Specifically, the Instrument Server will read: S11, S12, S21, and S22 (selecting “All S parameters&quto” will read S11, S12, S21, and S22).

6. Type the network analyzer address in the HP-IB Address field.

7. Select HP-IB > Symbolic Name and enter a symbolic interface name. For more information, refer to “Specifying a Symbolic Interface Name” on page 2-28.

8. If you want the data transfer to include a timeout, select HP-IB > Timeout. For more information, refer to “Specifying a Transfer Timeout” on page 2-28.



11. Enter a name in the Dataset Name field, or select an existing dataset from the Datasets list.


12. Enter a unique block name in the Enter Unique Block Name field. The instrument data will be stored in this block name.

Note You can select an existing block from the Blocks list, but you must edit the selected block name in the Enter Unique Block Name field so that it is unique.

13. Click Read Instrument to send the measured instrument data to the dataset.

Writing Data to a Network Analyzer

Data in a dataset can be written to the network analyzer raw data array or memory array. The memory array can only hold one parameter.

If data is to be written to the Channel 1 Raw data array, and a full 2-port-calibration is in effect, any of the four S parameters may be written to the 4 available raw data arrays. If a full 2-port-calibration is not in effect, S11 data must be selected in order to write to the single Raw data array available.

Note For the PNA family of network analyzers, including the E855x, E880x, E836x, N388x families, the Instrument Server does not support writing to the analyzer waveform memory.

To write to a network analyzer:


2. Under Write To, click Network Analyzer.

3. Under NWA Data Location, select the network analyzer data locations to identify where you want to send the data.

4. Under Write Network Analyzer Data, select the type of S-parameters that you intend to send to the analyzer.

5. Type the network analyzer address in the HP-IB Address field.


7. If you want the data transfer to include a timeout, select HP-IB > Timeout. For more information refer to “Specifying a Transfer Timeout” on page 2-28.


Instrument Server


9. The source of the data can be any block in a project dataset. The data in the dataset block must be complex data. Select from the list of existing datasets and blocks.

10. Enter a unique block name in the Enter Name from Block List field.

Note You can select an existing block from the Blocks list, but you must edit the selected block name in the Enter Name from Block List field so that it is unique.

11. Click Write To Instrument to send the data to the specified network analyzer location.

Reading and Writing Spectrum Analyzer DataData can be read from and written to a wide range of Hewlett-Packard spectrum analyzers. Supported spectrum analyzers are listed below.

Reading Instrument Data from a Spectrum Analyzer

When data is read into a dataset, the location specified as the source of the data (trace A, B, or C) is read immediately without the selected trace being put into view mode. When reading data from a spectrum analyzer, keep in mind the following:

• The 856X series of analyzers do not have a Trace C.

Table 2-3. Spectrum Analyzer Data

Model Number Features

Agilent 70000 Modular Analyzers (MMS)

Agilent 8566B 100 Hz–22 GHz

Agilent 8567A 10 kHz–1500 MHz

Agilent 8568B 100 Hz–1500 MHz

Agilent 859XX Portable Economy Analyzer Series

Agilent 856XX Portable Mil Spec Analyzer Series

2-18 Reading and Writing Spectrum Analyzer Data

• The instrument server doesn’t wait for the trace to complete before the data is read.

• For traces with long sweep times, make sure the instrument has completed one sweep of the desired spectrum before reading the data.

• No peak search is performed before the data is transferred.

• Data is read in exactly as it appears on the screen.

• The data written to the dataset variable has the amplitude units of the analyzer at the time the data was read.

To read data from a spectrum analyzer:


2. Under Read From, click Spectrum Analyzer.

3. Under Read Spectrum Analyzer Trace, select the trace you want to use as the data source.

4. Type the spectrum analyzer address in the HP-IB Address field.


6. If you want the data transfer to include a timeout, select HP-IB > Timeout. For more information refer to “Specifying a Transfer Timeout” on page 2-28.




10. Enter a unique block name in the Enter Unique Block Name field.

Note You can select from the list of existing blocks in the Blocks list, but you must edit the selected block name in the Enter Unique Block Name field so that it is unique. The instrument data will be stored in this block.


Reading and Writing Spectrum Analyzer Data 2-19

Instrument Server

Writing to a Spectrum Analyzer

Existing data in the instrument memory to which data is being written is overwritten, and the dataset data is displayed as if it were measured data. Since dataset data is deleted from the instrument when another measurement is made, the instrument server places the instrument in single sweep mode to prevent the dataset data from being overwritten. Dataset data is deleted from the instrument when another measurement is made.

When data is written into the spectrum analyzer, the frequency range, number of points, and other stimulus values in the instrument are not changed. Interpolation is used (if necessary) to display the dataset data at the frequency points given by the current spectrum analyzer settings. There must be some overlap between the frequency range of the dataset and the analyzer’s current frequency range. The spectrum analyzer does not extrapolate. Data values for all frequencies above or below the frequencies in the dataset appear as zero.

The instrument server searches the selected dataset variable for an attribute labeled “Amplitude Units”. If it is not found, the instrument server prompts the user for the unit value of the dataset variable data. The dataset variable data must be real data, complex data will result in an error.

To write to a spectrum analyzer:


2. Under Write To, click Spectrum Analyzer.

3. Under Write to Spectrum Analyzer Trace, select the trace where you intend to send the data.

4. Type the spectrum analyzer address in the HP-IB Address field.





2-20 Reading and Writing Spectrum Analyzer Data

9. The source of the data can be any block in a project dataset. Enter a name in the Dataset Name field, or select a dataset from the Dataset list.

10. Enter a unique block name in the Enter Name from Block List field. The instrument data will be stored in this block.


11. Click Write To Instrument to send the dataset or block to the spectrum analyzer trace.

Reading and Writing Oscilloscope DataData can be read from and written to a wide range of Agilent oscilloscopes. Supported oscilloscopes are listed below.

Table 2-4. Oscilloscope Data

Model Number Features

Agilent 54100A 1 GHz rep BW, 2-channel.

Agilent 54100D Agilent 54100A with dual trigger.

Agilent 54110D Agilent 54100D with color CRT and PaintJet output.

Agilent 54111D 500 MHz Rep BW, 250 MHz 1-shot, 2-channel dual trigger.

Agilent 54120T 20 GHz rep BW, 4-channel.

Agilent 54123T 34 GHz rep BW, 4-channel.

Agilent 54124T 50 GHz, 4-channel.

Agilent 54720D 2 GHz, 8 GSample/sec Modular Oscilloscope (using Agilent 5471x and 5472x plug-ins)

Agilent 54750A 20 GHz Sampling Modular Oscilloscope (using Agilent 5475x plug-ins)

Agilent 86100A 50 GHz DCA (digital communications analyzer)

Agilent 86100B 50 GHz high speed DCA (digital communications analyzer)

Reading and Writing Oscilloscope Data 2-21

Instrument Server

Reading Instrument Data from an Oscilloscope

Not all channels or memory locations exist on all supported oscilloscopes. Requesting data from a nonexistent channel results in an error message and no data is transferred.

Table 2-5 summarizes the memory locations from which data can be read in various Agilent oscilloscopes.

It may take a long time to read some extreme cases of averaged data. It is not uncommon for it to take 10 to 15 minutes to accumulate 500 points of data averaged 2048 times. If such a trace is desired, store the trace in memory first, then read the data directly from memory.

Also note that the Agilent 54111D oscilloscope stores 8192 points of data in waveform memories 1 through 4 even though only 512 of these points are displayed at any one time. The result is that even if only two periods appear on the display, reading the memory will take as long as is needed to read points for 16 periods.

Using Agilent 541xxx-series Oscilloscopes

When reading data from an active channel, all Agilent 541xxx-series and Agilent 547xx-series oscilloscopes first digitize the data into a waveform memory.

Table 2-5. Oscilloscope Memory Locations

Oscilloscope Memory1 Memory2

Memory3 Memory4

Memory5Memory6

Memory5 through Memory8

All † ‡ •Agilent 54120T • •Agilent 54123T • •Agilent 54110D • •Agilent 54111D • • •

Agilent 547xx ‡ • • •† All instruments except Agilent 54100A/D oscilloscopes with firmware revisions earlier than March 1986. In these earlier oscilloscopes, data is read from Channel 1 or 2 only.‡ Memory5 = fcn1, Memory6 = fcn2.

2-22 Reading and Writing Oscilloscope Data

Table 2-6 traces the flow of the data in each oscilloscope.

To read data from an oscilloscope:


2. Under Read From, click Oscilloscope.

3. Under Read Oscilloscope Data, select the channel or memory location that you want to use as the data source.

4. Type the oscilloscope address in the HP-IB Address field.






Table 2-6. Oscilloscope Data Flow

Agilent54100A/D †

Agilent 54110D

Agilent 54111D

Agilent5412xx

Agilent547xx

Where channel 1 is stored

Internal memory

Memory 1 Memory 1 or Memory 5 ‡

Memory 1 Internal memory


Internal memory

Memory 2 Memory 2 or Memory 6 ‡






† Agilent 54100A/D oscilloscopes with firmware revisions later than March 1986 behave like Agilent 54110D oscilloscopes.‡ The Agilent 54111D oscilloscope digitizes real-time traces from channels 1 and 2 into Memory 1 and Memory 2. It digitizes averaged traces from these two channels into Memory 5 and Memory 6.

Reading and Writing Oscilloscope Data 2-23

Instrument Server

10. Enter a unique block name in the Enter Unique Block Name field. The instrument data will be stored in this block.

Note You can select an existing block from the Blocks list, but you must edit the selected block name in the Enter Unique Block Name field so that it is unique.


Writing Advanced Design System Data to an Oscilloscope

Not all memory locations are on all supported oscilloscopes. Writing data to a nonexistent channel aborts the process with an error message and no data changes.

Table 2-7 summarizes the memory locations that are available for writing data in various Agilent oscilloscopes.

When data is written into the oscilloscope, the time range, number of points, and other stimulus values in the waveform memory are not changed. Interpolation is used (if necessary) to display the dataset data at the time points given by the current oscilloscope settings. This means that the desired time/div, volts/div, delay, and other settings must be adjusted on an active channel and then stored in memory.

The oscilloscope does not extrapolate. Data values for all times above or below the frequencies in the dataset appear as zero.

To write to an oscilloscope:

Table 2-7. Oscilloscope Memory Locations

Oscilloscope Memory1 Memory2

Memory3 Memory4

Memory5 through Memory8

ALL •Agilent 54120T • •Agilent 54123T • •Agilent 54110D • •Agilent 54111D • • •Agilent 547xx • •

2-24 Reading and Writing Oscilloscope Data


2. Under Write To, click Oscilloscope.

3. Under Write To Oscilloscope Memory, select the memory location where you intend to send the data.

4. Type the oscilloscope address in the HP-IB Address field.





9. The source of the data can be any block in a project dataset. Enter a name in the Dataset field, or select a dataset from the Datasets list.



11. Click Write To Instrument to send the dataset or block to the specified oscilloscope memory location.

Reading and Writing Microwave Transition Analyzer DataData can be read from and written to the Agilent 70820A Microwave Transition Analyzer (MTA).

Reading and Writing Microwave Transition Analyzer Data 2-25

Instrument Server

Reading Instrument Data from an MTA

You can read MTA data from a trace, memory, or a table. Data can be in the following format. The data read from a trace or memory location is formatted by the following Read MTA data selections.

• Formatted The format of the data depends on the instrument’s current Domain setting, which dictates how the trace data is to be displayed. Basically, this is a What You See Is What you Get mode. The dependent data returned may be in Complex(real, imaginary), Real, Imag, Magnitude, Phase, or Complex(magnitude, phase) formats. The independent data can be either frequency or time.

• Complex versus time The dependent data returned will be complex data, and the independent data will be time. It doesn’t matter what is currently being displayed on the screen. The measured data will be transformed as necessary to output complex data vs. time. For instance, if the instrument is currently displaying magnitude data vs. frequency, an inverse FFT is performed so the independent data is time, and the dependent data will be complex(real, imaginary).

• Complex versus frequency The dependent data returned will be complex data, and the independent data will be frequency. It doesn’t matter what is currently being displayed on the screen. The measured data will be transformed as necessary to output complex data vs. frequency. For instance, if the instrument is currently displaying real data vs. time, a FFT is performed so the independent data is frequency, and the dependent data will be complex(real, imaginary).

If data is to be read from the MTA table, the instrument server checks to see if there is more than 1 signal in the signal list. If there is more than 1 signal in the list, the instrument server will prompt the user for the signal of interest. The magnitude data is changed to absolute amplitude values if it is originally relative. When the transfer is started, the transition analyzer is put into hold mode if it is not in this mode already. Then the data is read. This makes it possible to set up a trace, put the instrument in hold mode, and then read the data. After the data has been read, the transition analyzer is returned to its original sweep mode.

Details on transition analyzer domains appear under the description of the waveform subsystem in the Agilent 70820A Transition Analyzer Remote Programming Manual.

To read data from an MTA:

2-26 Reading and Writing Microwave Transition Analyzer Data


2. Under Read From, click Microwave Transition Analyzer.

3. Under Read MTA Trace, select one of the MTA Trace Formats:

• Trace 1-4: a displayed MTA trace

• Memory 1-4: an MTA memory location

• Table: If there is more than one signal in the signal list, the instrument server will prompt the user for the signal of interest. The structure of the table is retained. For example, a table may contain the magnitude and phase values of a fundamental frequency and each of its harmonics. The data is transferred to the dataset in the same order.

4. Under Read MTA Data, select one of the MTA Data Formats:

• Formatted

• Complex vs. Time

• Complex vs. Frequency

5. Type the microwave transition analyzer address in the HP-IB Address field.






11. Enter a unique block name in the Enter Unique Block Name field. The instrument data will be stored in this block.

Note You can select an existing block from the Blocks list, but you must edit the selected name in the Enter Unique Block Name field so that it is unique.

Reading and Writing Microwave Transition Analyzer Data 2-27

Instrument Server


Writing Data to an MTA

Any data that in the instrument memory location that you select to write to will be overwritten with the dataset data. The frequency range, number of points, and other stimulus values in the instrument are reset to fit the trace being written.

To write to an MTA:


2. Under Write To, click Microwave Transition Analyzer.

3. Under Write to MTA Memory, select the memory location where you intend to send the data.

4. Under Write MTA Data, select one of the MTA data types:

• Frequency Domain Data as a function of frequency

• Time Domain Complex data as a function of time

5. Type the microwave transition analyzer address in the HP-IB Address field.





10. The source of the data can be any block in a project dataset. Enter a name in the Dataset Name field, or select a dataset from the Datasets list.



2-28 Reading and Writing Microwave Transition Analyzer Data

12. Click Write To Instrument to send the dataset or block to the specified MTA memory location.

Specifying a Symbolic Interface NameThe symbolic interface name is the name assigned to the interface card when the card is installed. This name can be redefined at any time and is required by the Instrument Server to transfer data to or from an instrument. For the E2050 Lan/GPIB gateway box, the symbolic name is of the form:

lan[IP_address]:hp-ib_name

To enter the symbolic name:

1. From the menu bar choose HP-IB > Symbolic Name.

2. The HP-IB Symbolic Name dialog box appears. Type the name into the field in the dialog box.

3. Click OK.

Example:

If an E2050 Lan/GPIB gateway box with an IP address of 18.9.134.213 is to be addressed, the symbolic name is:

lan[18.9.134.213]:hpib that is, lan[IP_address] : hp-ib_name

Refer to the documentation for the E2050 for details on changing the hp-ib_name.

Note Interface cards for the PC are often bundled with a diagnostics program. If the diagnostics software is installed, you can run it to identify the card name. UNIX platforms are not supported.

Specifying a Transfer TimeoutA transfer timeout specifies the length of time allowed to transfer data. When the time is exceeded, the instrument and computer are disconnected. You should always set the timeout option before a data transfer to ensure the connection between the instrument and Advanced Design System can be terminated.

To set a timeout:

Specifying a Symbolic Interface Name 2-29

Instrument Server

1. From the menu bar choose HP-IB > Timeout.

2. The HP-IB Timeout dialog box appears. Type the amount of time you want to allow to elapse, in seconds, before the timeout occurs.

3. Click OK.

Note The optimum transfer time depends on the hardware speed and the amount of data to be transferred. If you transferring data from an instrument and are averaging data, transferring a large amount of data, or have a long sweep time, put the instrument in hold or single sweep mode or change the timeout setting to an appropriate value before attempting to transfer data.

Entering Comments into a DatasetYou can enter comments into a dataset. Comments such as the origin of the data can be useful to identify the contents of the dataset.

To enter comments:

1. Click Display Comments Dialog.

2. Type in comments that you want to add to the dataset. The comments are entered into a comments field of the dataset.

3. Click OK to add the comments to the dataset.

2-30 Entering Comments into a Dataset

Chapter 3: CITIfile Data Format ReferenceThis chapter gives an overview of the CITIfile format, definitions of key terms, and file examples. It also includes:

• Keyword reference

• File guidelines

• Instructions for converting between disk formats

• Device-specific definitions

• Filename requirements

CITIfile Data FormatsCITIfile is a standardized data format that is used for exchanging data between different computers and instruments. CITIfile stands for Common Instrumentation Transfer and Interchange file format.

This standard is a group effort between instrument designers and designers of computer-aided design programs. As much as possible, CITIfile meets current needs for data transfer, and it is designed to be expandable so it can meet future needs.

CITIfile defines how the data inside an ASCII package is formatted. Since it is not tied to any particular disk or transfer format, it can be used with any operating system, such as DOS or UNIX, with any disk format, such as DOS or HFS, or with any transfer mechanism, such as by disk, LAN, or GPIB.

By careful implementation of the standard, instruments and software packages using CITIfile are able to load and work with data created on another instrument or computer. It is possible, for example, for a network analyzer to directly load and display data measured on a scalar analyzer, or for a software package running on a computer to read data measured on the network analyzer.

Data Formats

There are two main types of data formats: binary and ASCII. CITIfile uses the ASCII text format. Although this format does require more space than binary format, ASCII data is a transportable, standard type of format which is supported by all operating systems. In addition, the ASCII format is accepted by most text editors. This allows

CITIfile Data Formats 3-1

CITIfile Data Format Reference

files to be created, examined, and edited easily, making CITIfile easier to test and debug.

File and Operating System Formats

CITIfile is a data storage convention designed to be independent of the operating system, and therefore may be implemented by any file system. However, transfer between file systems may sometimes be necessary. You can use any software that has the ability to transfer ASCII files between systems to transfer CITIfile data. For more information, see “Converting Between Disk Formats” on page 3-10.

The descriptions and examples shown here demonstrate how CITIfile may be used to store and transfer both measurement information and data. The use of a single, common format allows data to be easily moved between instruments and computers.

CITIfile DefinitionsThis section defines the following terms: package, header, data array, and keyword.

Package

A typical CITIfile package is divided into two parts:

• The header is made up of keywords and setup information.

• The data usually consists of one or more arrays of data.

The following example shows the basic structure of a CITIfile package:

When stored in a file there may be more than one CITIfile package. With the Agilent 8510 network analyzer, for example, storing a memory all will save all eight of the memories held in the instrument. This results in a single file that contains eight CITIfile packages.

CITIFILE A.01.00NAME MEMORYVAR FREQ MAG 3DATA S RIBEGIN-3.54545E-2,-1.38601E-30.23491E-3,-1.39883E-32.00382E-3,-1.40022E-3END

Header

Data

3-2 CITIfile Definitions

Header

The header section contains information about the data that will follow. It may also include information about the setup of the instrument that measured the data. The CITIfile header shown in the first example has the minimum of information necessary; no instrument setup information was included.

Data Array

An array is numeric data that is arranged with one data element per line. A CITIfile package may contain more than one array of data. Arrays of data start after the BEGIN keyword, and the END keyword follows the last data element in an array.

A CITIfile package does not necessarily need to include data arrays. For instance, CITIfile could be used to store the current state of an instrument. In that case the keywords VAR, BEGIN, and END would not be required.

Keywords

Keywords are always the first word on a new line. They are always one continuous word without embedded spaces. A listing of all the keywords used in version A.01.00 of CITIfile is shown in “CITIfile Keyword Reference” on page 3-6.

CITIfile ExamplesThe following are examples of CITIfile packages.

Display Memory File

This example shows an Agilent 8510 display memory file. The file contains no frequency information. Some instruments do not keep frequency information for display memory data, so this information is not included in the CITIfile package.

Note that instrument-specific information (#NA = network analyzer information) is also stored in this file.

CITIFILE A.01.00#NA VERSION HP8510B.05.00NAME MEMORY#NA REGISTER 1VAR FREQ MAG 5

CITIfile Examples 3-3


DATA S RIBEGIN-1.31189E-3,-1.47980E-3-3.67867E-3,-0.67782E-3-3.43990E-3,0.58746E-3-2.70664E-4,-9.76175E-40.65892E-4,-9.61571E-4END

Agilent 8510 Data File

This example shows an Agilent 8510 data file, a package created from the data register of an Agilent 8510 network analyzer. In this case, 10 points of real and imaginary data was stored, and frequency information was recorded in a segment list table.

CITIFILE A.01.00#NA VERSION HP8510B.05.00NAME DATA#NA REGISTER 1VAR FREQ MAG 10DATA S[1,1] RISEG_LIST_BEGINSEG 1000000000 4000000000 10SEG_LIST_ENDBEGIN0.86303E-1,-8.98651E-18.97491E-1,3.06915E-1-4.96887E-1,7.87323E-1-5.65338E-1,-7.05291E-18.94287E-1,-4.25537E-11.77551E-1,8.96606E-1-9.35028E-1,-1.10504E-13.69079E-1,-9.13787E-17.80120E-1,5.37841E-1-7.78350E-1,5.72082E-1END

Agilent 8510 3-Term Frequency List Cal Set File

This example shows an Agilent 8510 3-term frequency list cal set file. It shows how CITIfile may be used to store instrument setup information. In the case of an Agilent

3-4 CITIfile Examples

8510 cal set, a limited instrument state is needed in order to return the instrument to the same state that it was in when the calibration was done.

Three arrays of error correction data are defined by using three DATA statements. Some instruments require these arrays be in the proper order, from E[1] to E[3]. In general, CITIfile implementations should strive to handle data arrays that are arranged in any order.

CITIFILE A.01.00#NA VERSION HP8510B.05.00NAME CAL_SET#NA REGISTER 1VAR FREQ MAG 4DATA E[1] RIDATA E[2] RIDATA E[3] RI#NA SWEEP_TIME 9.999987E-2#NA POWER1 1.0E1#NA POWER2 1.0E1#NA PARAMS 2#NA CAL_TYPE 3#NA POWER_SLOPE 0.0E0#NA SLOPE_MODE 0#NA TRIM_SWEEP 0#NA SWEEP_MODE 4#NA LOWPASS_FLAG -1#NA FREQ_INFO 1#NA SPAN 1000000000 3000000000 4#NA DUPLICATES 0#NA ARB_SEG 1000000000 1000000000 1#NA ARB_SEG 2000000000 3000000000 3VAR_LIST_BEGIN1000000000200000000025000000003000000000VAR_LIST_ENDBEGIN1.12134E-3,1.73103E-34.23145E-3,-5.36775E-3-0.56815E-3,5.32650E-3-1.85942E-3,-4.07981E-3ENDBEGIN2.03895E-2,-0.82674E-2-4.21371E-2,-0.24871E-20.21038E-2,-3.06778E-2

CITIfile Examples 3-5


1.20315E-2,5.99861E-2ENDBEGIN4.45404E-1,4.31518E-18.34777E-1,-1.33056E-1-7.09137E-1,5.58410E-14.84252E-1,-8.07098E-1END

When an instrument's frequency list mode is used, as it was in this example, a list of frequencies is stored in the file after the VAR_LIST_BEGIN statement. The unsorted frequency list segments used by this instrument to create the VAR_LIST_BEGIN data are defined in the #NA ARB_SEG statements.

CITIfile Keyword ReferenceTable 3-1 lists keywords, definitions, and examples.

3-6 CITIfile Keyword Reference

Table 3-1. CITIfile Keyword Reference

Keyword Example and Explanation

CITIFILE Example: CITIFILE A.01.00Identifies the file as a CITIfile and indicates the revision level of the file. The CITIFILE keyword and revision code must precede any other keywords.

The CITIFILE keyword at the beginning of the package assures the device reading the file that the data that follows is in the CITIfile format.The revision number allows for future extensions of the CITIfile standard.

The revision code shown here following the CITIFILE keyword indicates that the machine writing this file is using the A.01.00 version of CITIfile as defined here. Any future extensions of CITIfile will increment the revision code.

NAME Example: NAME CAL_SET

Sets the current CITIfile package name. The package name should be a single word with no embedded spaces. Some standard package names:

RAW_DATA: Uncorrected data.

DATA: Data that has been error corrected. When only a single data array exists, it should be named DATA.

CAL_SET: Coefficients used for error correction.

CAL_KIT: Description of the standards used.

DELAY_TABLE: Delay coefficients for calibration.

VAR Example: VAR FREQ MAG 201

Defines the name of the independent variable (FREQ); the format of values in a VAR_LIST_BEGIN table (MAG) if used; and the number of data points (201).

CONSTANT Example: CONSTANTname value

Lets you record values that do not change when the independent variable changes.

CITIfile Keyword Reference 3-7


# Example: #NA POWER1 1.0E1

Lets you define variables specific to a particular type of device. The pound sign (#) tells the device reading the file that the following variable is for a particular device.The device identifier shown here (NA) indicates that the information is for a network analyzer. This convention lets you define new devices without fear of conflict with keywords for previously defined devices. The device identifier can be any number of characters.

SEG_LIST_BEGIN Indicates that a list of segments for the independent variable follows.

Segment Format: segment type start stop number of points

The current implementation supports only a signal segment. If you use more than one segment, use the VAR_LIST_BEGIN construct. CITIfile revision A.01.00 supports only the SEG (linear segment) segment type.

SEG_LIST_END Sets the end of a list of independent variable segments.

VAR_LIST_BEGIN Indicates that a list of the values for the independent variable (declared in the VAR statement) follows. Only the MAG format is supported in revision A.01.00.

VAR_LIST_END Sets the end of a list of values for the independent variable.

DATA Example: DATA S[1,1] RI

Defines the name of an array of data that will be read later in the current CITIfile package, and the format that the data will be in. Multiple arrays of data are supported by using standard array indexing as shown above. CITIfile revision A.01.00 supports only the RI (real and imaginary) format, and a maximum of two array indexes.

Commonly used array names include:S - S-parameterE - Error TermVoltage - VoltageVOLTAGE_RATIO - A ratio of two voltages (A/R)

Table 3-1. CITIfile Keyword Reference (continued)

Keyword Example and Explanation

3-8 CITIfile Keyword Reference

CITIfile GuidelinesThe general guidelines aid in making CITIfiles universally transportable are:

• Line Length The length of a line within a CITIfile package should not exceed 80 characters. This allows instruments which may have limited RAM to define a reasonable input buffer length.

• Keywords Keywords are always at the beginning of a new line. The end of a line is as defined by the file system or transfer mechanism being used.

• Unrecognized Keywords When reading a CITIfile, unrecognized keywords should be ignored. There are two reasons for this:

• Ignoring unknown keywords allows new keywords to be added, without affecting an older program or instrument that might not use the new keywords. The older instrument or program can still use the rest of the data in the CITIfile as it did before. Ignoring unknown keywords allows “backwards compatibility” to be maintained.

• Keywords intended for other instruments or devices can be added to the same file without affecting the reading of the data.

• Adding New Devices Individual users are allowed to create their own device keywords through the # (user-defined device) mechanism (see list of keywords for more information). Individual users should not add keywords to CITIfiles without using the # notation, as this could make their files incompatible with current or future CITIfile implementations.

• File Names Some instruments or programs identify a particular type of file by characters that are added before or after the file name. Creating a file with a particular prefix or ending is not a problem. However in general an instrument or program should not require any such characters when reading a file. This allows any file, no matter what the filename, to be read into the instrument or computer. Requiring special filename prefixes and endings makes the exchange of data between different instruments and computers much more difficult.

CITIfile Guidelines 3-9


Converting Between Disk FormatsMost current Agilent instruments use disks formatted in the Logical Interchange Format (LIF). Some instruments also use DOS-formatted disks. CITIfiles created on one file system (LIF, DOS, HFS, etc.) may be transferred to other file systems.

HFS

Several LIF and DOS utilities are available for HP-UX workstations. The HP-UX utilities lifcp and doscp can transfer CITIfiles to and from LIF and DOS disks. Using lifcp and doscp are similar; using lifcp is described below. Several other LIF and DOS utilities are also available. Consult the manuals for these utilities for more detailed information. Listing the contents of a LIF disk when using HP-UX would be similar to the following example:

lifls /dev/rdsk/1s0.0

The device name used will depend on how your system was configured. Copying a CITIfile named DD_FILED1 from a LIF disk to HFS would be similar to the following example:

lifcp /dev/rdsk/1s0.0:DD_FILED1 DD_FILED1

To copy a standard HFS ASCII file to a LIF disk:

lifcp DD_FILED1 /dev/rdsk/1s0.0:DD_FILED1

When used on an HFS disk, The HP-UX program RMB/UX (Rocky Mountain BASIC for HP-UX) has the ability to write a CITIfile in either as a standard HFS ASCII file, or as a LIF volume file. The LIF volume file is the default. This type of file is not directly readable when using the HP-UX operating system, and the copy commands listed above will not work correctly.

BASIC program writers are encouraged to detect when writing to an HFS disk, and to use the standard HFS format. The program examples CITIWRITE and CITIDOALL show how this can be done. However CITIfiles stored in the LIF volume format can still be transferred to LIF disks, or converted to standard HFS files. To copy a LIF volume file named DD_FILED stored on an HFS disk and move it to a LIF disk:

lifcp DD_FILED1:WS_FILE /dev/rdsk/1s0.0:DD_FILED1

To copy the LIF volume file DD_FILED1 to a standard HFS file named NEWFILE:

lifcp DD_FILED1:WS_FILE NEWFILE

3-10 Converting Between Disk Formats

DOS

Utilities are available for DOS machines that enable them to transfer files to and from a LIF formatted disk. Many of these programs are menu-driven, and are available from the following companies: Hewlett-Packard, Oswego, Meadow Soft Works, and Innovative Software Systems.

CITIfile Device-specific DefinitionsCITIfile is a generic definition of a data storage format for any type of computer or instrument. However each type of device may need to define certain conventions for itself. This section describes the device-specific keywords and conventions for current implementations.

Network Analyzer (#NA) Definitions

Data Grouping

Data arrays of the same type, obtained during a single measurement operation, are stored in a single CITIfile package. For example, all error correction arrays are stored in the same CITIfile package, and all parameters acquired during an s-parameter measurement operation are stored in the same CITIfile package.

A CITIfile package is as described in the main CITIfile documentation: the CITIFILE keyword, followed by a header section, usually followed by one or more arrays of data.

Note There are some specific problems with the current version in writing and/or reading this data format. On the Agilent EEsof web site, refer to the Release Notes in Product Documentation and to Technical Support for more information and workarounds (www.agilent.com/find/eesof).

Network Analyzer Keywords

The definition of CITIfile allows for statements that are specific to a certain type of device. Table 3-2 lists the currently defined commands for the #NA network analyzer) keyword.

CITIfile Device-specific Definitions 3-11


Table 3-2. Network Analyzer Keywords

Statement Explanation

#NA ARB_SEG x y p A list segment, as entered by the user. xx = start value y = stop value p = number of points.

#NA REGISTER nn Register in instrument that the current data package was stored in. nn = number of register.

#NA SWEEP_TIME tt The sweep time of the analyzer. tt = time in seconds.

#NA POWER1 pp Power level of signal source #1. pp = power in dBm.

#NA POWER2 pp Power level of signal source #2. pp = power in dBm.

#NA PARAMS aa Bitmap of valid parameters for a calibration. Bit positions 1-8 represent the following: Bit #1 = S11 Bit #2 = S21 Bit #3 = S12 Bit #4 = S22 Bit #5 = user1 Bit #6 = user2 Bit #7 = user3 Bit #8 = user4A bit equal to one means that the calibration is valid for that parameter; a zero means that the calibration is not valid for that parameter. Bit #0 is the least significant bit.

NA# CAL_TYPE cc The type of calibration used: 1 = response calibration. 2 = response and isolation calibration. 3 = one-port calibration on port 1 4 = one-port calibration on port 2 5 = two-port calibration (includes one-path full & TRL)

NA# POWER_SLOPE ss Change in power versus frequency. ss = dBm/GHz

NA# SLOPE_MODE mm On/off flag for power slope. mm = 0 = off mm = 1 = on

3-12 Network Analyzer (#NA) Definitions

Error Array NumberingCurrent network analyzer implementations use between one and twelve error coefficient arrays in order to perform error correction. The CAL_TYPE keyword description in “Network Analyzer (#NA) Definitions” on page 3-11 lists the currently defined calibration types. Table 3-3 defines the meanings of each coefficient array with respect to the error model used.

NA# TRIM_SWEEP tt Linearity adjustment value for swept sources.

NA# SWEEP_MODE ss Type of sweep done to make measurement. 0 = swept 1 = stepped 2 = single-point 3 = fast CW 4 = list

NA# LOWPASS_FLAG ff Low-pass time domain flag. ff = 0 = low-pass time domain enabled. ff = 1 = low-pass time domain disabled.

NA# FREQ_INFO ii The frequency information flag. ii = 0 = frequency information displayed on instrument screen. ii = 1 = frequency information not displayed on instrument screen.

NA# DUPLICATES dd Delete duplicates flag. Determines if points listed more than once should be measured more than once. dd = 0 = points listed more than once are measured as many times as they are listed. dd = 1 = points are measured only once.

NA# SPAN xx yy pp The sweep parameters: xx = start value yy = stop value pp = number of points

NA# IF_BW gg The IF bandwidth setting of the receiver. gg = IF bandwidth in Hertz.

Table 3-2. Network Analyzer Keywords (continued)

Statement Explanation

Error Array Numbering 3-13


Disk Filename RequirementsSome instruments or programs identify a particular type of file by characters that are added before or after the file name. In general an instrument or program should not require any such characters when reading a file.

There exist CITIfile implementations which do have file naming restrictions. This section explains how to work around these restrictions.

Agilent 8510 Series CITIfileThe Agilent 8510 checks the first three letters of the filename to determine what is stored in the file. Table 3-4 lists the file prefixes for an Agilent 8510 CITIfile.

Table 3-3. Error Array Numbering

ErrorArrayName

FrequencyResponse

Response &Isolation

All1-Port

All2-Port

E1 Er or Et Ed or Ex Ed Edf

E2 — Er or Et Es Esf

E3 — — Er Erf

E4 — — — Exf

E5 — — — Elf

E6 — — — Etf

E7 —- —- — Edr

E8 — — —- Esr

E9 — — — Err

E10 — — — Exr

E11 -— -— — Elr

E12 — — -— Etr

3-14 Disk Filename Requirements

DD_MYDATA is an example of a file name for a file that contains one array of corrected data.

The current Agilent 8510 CITIfile implementation is unable to read files unless they have the prefixes above. It is expected that a future Agilent 8510 revision will remove this restriction.

Agilent 8700 Series CITIfileStoring a data file from an Agilent 8700-series analyzer in CITIfile format requires that you choose the SAVE USING ASCII option.

The Agilent 8700 series of instruments check the last two characters of the filename to determine what is stored in the file. Table 3-5 lists the file endings for an Agilent 8700 CITIfile.

Table 3-4. Agilent 8510 Series CITIfile Prefixes

File Prefix File Contents Notes

RD_ Raw Data Raw (uncorrected data array(s).

DD_ Data Data Error corrected data array(s)

FD_ Formatted Data Corrected & formatted data array.

DM_ Display Memory File holds one memory.

MA_ Display Memory All Holds all memories in 8510.

CS_ Cal Set One set of calibration data.

CA Cal Set All All sets of calibration data.

DT_ Delay Table One delay table.

Table 3-5. Agilent 8700 Series CITIfile Suffixes

Last 2 Charsof File Name File Contents Notes

Rx Raw Data x = 1 = channel 1.x = 5 for channel 2.

Dx Data Data x = channel number.

Fx Formatted Data

x = channel number.

Agilent 8700 Series CITIfile 3-15


FILE1D1 is an example of a file name for a file that contains corrected data for channel #1. FILE1R5 is a filename for raw data arrays from channel #2. MYFILE2C is an example of a name for a file that contains a cal set used by channel #2, with 12 arrays of data (hexadecimal C).

To load data from disk into an Agilent 8700-series instrument, there must be a matching instrument state file to go with the data that is being loaded. Consult the Agilent 8700-series documentation for more information.

Mx Display Memory

x = channel number.

xy Cal Set x = channel number.y = number of error coefficient arrays in the file. y is displayed in hexadecimal.

Table 3-5. Agilent 8700 Series CITIfile Suffixes

Last 2 Charsof File Name File Contents Notes

3-16 Agilent 8700 Series CITIfile

Chapter 4: Touchstone Data Format ReferenceTouchstone data files are ASCII text files in which data appears line by line, one line per data point, in increasing order of frequency. Each line of data consists of a frequency value and one or more pairs of values for the magnitude and phase of each S-parameter at that frequency.Values are separated by one or more spaces. Comments are preceded by an exclamation mark (!). Comments can appear on separate lines, or after the data on any line or lines. Extra spaces are ignored.

Specifying Units and ImpedanceThe first uncommented line in the file must be a specification line. The next uncommented line is the first data line.

Specification lines begin with the number symbol (#) followed by a space. Then these parameters are specified, in this order:

• Frequency unit (GHz, MHz, KHz, or Hz)

• Parameter type (S)

• Data format, as magnitude-angle (MA), dB-angle (DB), or real-imaginary (RI)

• Nnormalizing impedance (R n, where n=ohms)

Syntax

The syntax for specifying units and impedance is shown below.

[#] [GHz MHz KHz, Hz] [S] [MA DB RI] [R n]

Example

This is a typical specification line:

# MHZ S MA R 50

Frequency values are in MHz (MHz), the data is S-parameter data (S), the data format is magnitude and angle (MA), and the impedance is 50 ohms (R 50).

Specifying Units and Impedance 4-1

Touchstone Data Format Reference

Entering Data ValuesData values appear on each line, in this order:

• Frequency In these examples, frequency appears as f. In the data file, frequency must be in the units that are used in the stimulus control element on the circuit page where the data is used.

• Magnitude In these examples, magnitude is expressed as m.

• Phase In these examples, phase is expressed as p. Phase is always given in degrees.

One-port data is entered on one line, with three values for each point:

f m(S11) p(S11)

Two-port data is entered on one line, with nine values for each point:

f m(S11) p(S11) m(S21) p(S21) m(S12) p(S12) m(S22) p(S22)

Three-port data is entered on three lines, with 19 values for each point:

f m(S11) p(S11) m(S12) p(S12) m(S13) p(S13m(S21) p(S21) m(S22) p(S22) m(S23) p(S23)m(S31) p(S31) m(S32) p(S32) m(S33) p(S33)

Four-port data is entered on four lines, with 33 values for each point:

f m(S11) p(S11) m(S12) p(S12) m(S13) p(S13) m(S14) p(S14)m(S21) p(S21) m(S22) p(S22) m(S23) p(S23) m(S24) p(S24)m(S31) p(S31) m(S32) p(S32) m(S33) p(S33) m(S34) p(S34) m(S41) p(S41) m(S42) p(S42) m(S43) p(S43) m(S44) p(S44)

Example

In this example, 2-port S-parameter data is specified.

! Two-port S-Parameter Data # MHz S MA R 500 .1 20 2 -20 .01 -20 .1 -30100 .1 20 2 -20 .01 -20 .1 -30200 .2 -40 4 -30 .02 -30 .15 -35300 .3 -60 5 -40 .02 -30 .2 -50

4-2 Entering Data Values

Noise ParametersNoise parameters can be included in Touchstone format 2-port data files. Noise data follows the S-parameter data and consists of a row of noise parameters at a particular frequency.

Each line of a noise parameter has the following five entries:

x1 x2 x3 x4 x5

where

Example

This is an example of a data file with noise data:

! NEC710

# GHZ S MA R 502 .95 -26 3.57 157 .04 76 .66 -1422 .60 -144 1.30 40 .14 40 .56 -85! NOISE PARAMETERS4 .7 .64 69 .3818 2.7 .46 -33 .40

x1 = Frequency in units. Assumed to be GHz unless otherwise noted in a units line. The first point of noise data must have a frequency less than the frequency of the last S-parameter frequency.

x2 = Minimum noise figure in dB

x3 = Magnitude of the reflection coefficient to realize the minimum noise figure (MA)

x4 = Phase in degrees of the reflection coefficient (MA)

x5 = Normalized effective noise resistance. The system simulator requires this parameter to meet physical requirements. If the user-supplied x5 value is less than allowed for this requirement, then the system simulator will force this x5 value to the lowest physical limit.

Noise Parameters 4-3

Touchstone Data Format Reference

4-4 Noise Parameters

Chapter 5: Command Reference

File Menu

Close Window

Closes the instrument server window.

HP-IB Menu

Note Only available on Windows based systems.

Symbolic Name

Specifies the symbolic interface name assigned to the interface bus card.

Timeout

Specifies the maximum length of time allowed to transfer data. Instruments disconnect after this time has elapsed.

Help Menu

What’s This?

Displays context-sensitive help for a menu, command, button, or control that is selected subsequently.

Topics and Index

Provides access to a brief list of topics for each product area, as well as access to an index of topics in all product areas.

File Menu 5-5

Command Reference

Agilent EEsof Web Site

Launches the browser (Netscape by default) defined in Options > Preferences > Web Browser in the Advanced Design System Main window, provided the path for the browser has been established.

About the Instrument Server

Displays version, copyright, and technical support information. Provides a direct link to the Agilent EEsof web site.

Read Instrument (Button)

Sends the measured instrument data to the dataset.

5-6 Help Menu

Index
CCITIfiles
about, 3-1and network analyzers, 3-11and the instrument server, 2-6data arrays, 3-3data format, 3-2filename requirements, 3-14for data, 2-6guidelines, 3-9header, 3-3keyword reference, 3-6keywords, 3-3package, 3-2

commentsentering in a dataset, 2-29

communication timeouts, specifying, 2-5

Ddata

and files, 2-6and MTAs, 2-24and network analyzers, 2-11and oscilloscopes, 2-20and spectrum analyzers, 2-17in Touchstone files, 4-2

data arraysin CITIfiles, 3-3

data communicationand timeouts, 2-28

data conversionof CITIfiles, 3-10

data filesand the instrument server, 2-6

data formatsfor network analyzers, 2-11

data transfersand files, 2-6and MTAs, 2-24, 2-25and network analyzers, 2-11and oscilloscopes, 2-20and spectrum analyzers, 2-17considerations, 2-6

datasetsand comments, 2-29

DOS formatfor CITIfiles, 3-11

Eexamples

CITIfile packages, 3-3

Ffiles

and the instrument server, 2-6reading, 2-9supported formats, 2-6writing, 2-10

GGPIB

address, 2-5timeouts, 2-28

GPIB cardsand symbolic names, 2-2, 2-5

Hheaders

in CITIfiles, 3-3HFS format, 3-10HP 8510 network analyzers

writing data to, 2-14HP 8703 network analyzers

reading data from, 2-12HP 8720 network analyzers



reading data from, 2-12

IIC-CAP files

as sources of data, 2-6instrument server

and data transfers, 2-6and files, 2-6and GPIB addresses, 2-5and MTAs, 2-24and oscilloscopes, 2-20and spectrum analyzers, 2-17

Index-1

and symbolic names, 2-5and timeouts, 2-5, 2-28connecting to instruments, 2-5elements, 2-3entering comments, 2-29exiting, 2-2reading files, 2-9reading MTA data, 2-25reading network analyzer data, 2-15reading oscilloscope data, 2-21reading spectrum analyzer data, 2-17starting, 2-2writing to a file, 2-10writing to an MTA, 2-27writing to network analyzers, 2-16writing to oscilloscopes, 2-23writing to spectrum analyzers, 2-19

instrumentsand instrument server connections, 2-5and timeouts, 2-5considerations, 2-6MTAs, 2-24network analyzers, 2-11oscilloscopes, 2-20spectrum analyzers, 2-17

interfacesusing instrument, 1-1

Kkeywords

CITIfile, 3-3reference, 3-6

MMDIF files

reading and writing, 2-6microwave transition analyzers

and data transfers, 2-24MTAs

reading data from, 2-25writing data to, 2-27

Nnaming CITIfiles, 3-14network analyzers

and the instrument server, 2-11data formats, 2-11error correction, 3-13

filename requirements, 3-14reading data from, 2-15writing data to, 2-16

noise parametersin Touchstone format, 4-3

Ooscilloscopes

about HP 541xxx series, 2-21and data transfers, 2-20reading data from, 2-21supported, 2-20writing data to, 2-23

Ppackages

CITIfile, 3-2

Rreading data

from a file, 2-9from a microwave transition analyzer, 2-25from a network analyzer, 2-15from a spectrum analyzer, 2-17from an oscilloscope, 2-21from oscilloscopes, 2-22

Sspecifications

of CITIfiles, 3-9of Touchstone files, 4-1

specifying a symbolic interface name, 2-28spectrum analyzers

and data transfers, 2-17reading data from, 2-17supported, 2-11, 2-17writing data to, 2-19

startingthe instrument server, 2-2

supported instrumentsoscilloscopes, 2-20spectrum analyzers, 2-11, 2-17

symbolic names, specifying, 2-2, 2-5, 2-28

Ttimeouts

specifying, 2-28timeouts, specifying, 2-5

Index-2

Touchstonefiles, 2-6

Touchstone dataentering data, 4-2impedance, 4-1noise parameters, 4-3units, 4-1

transferring dataconsiderations, 2-6

Wwriting data

to a microwave transition analyzer, 2-27to a network analyzer, 2-16to a spectrum analyzer, 2-19to an oscilloscope, 2-23to oscilloscopes, 2-23

Index-3

Index-4

Using Instruments - Keysightliterature.cdn.keysight.com/litweb/pdf/rfde2002c/pdf/rfd... · 2002. 7....

Documents

Transcript of Using Instruments - Keysightliterature.cdn.keysight.com/litweb/pdf/rfde2002c/pdf/rfd... · 2002. 7....