Agilent 86100A Programming Manual

Manual Change Supplement

Agilent 86100A

Introduction

Introduction

This supplement contains corrections for the 86100A manuals that are listed in the follow­ing table. This information was not available at the time that these manuals were printed.
The corrections include errata and changes due to product redesign.

Note

The information in this supplement applies to instruments that have software version 2.0 or
higher.

Manuals Affected by this Change Supplement

Manual Part Number

Programmer’s Guide 86100-90017

2

Programmer’s Guide

Introduction

Page 1-12 Change the following file name extensions table and descriptions:

Ta ble 1-1. File Name Extensions

File Type File Name Extension

Screen image .bmp, .eps, .gif, .pcx, .ps, .jpg, .tif

If you do not specify an extension when storing a file, or specify an incorrect extension, it
will be corrected automatically according to the following rules:

Programmer’s Guide

• No extension specified: add the extension for the file type.

• Extension doe s not match file type: retain the filename (including the cu rrent exten­sion) and add the appropriate ext ension.

Y ou do no t nee d to use an ext ensio n when loa ding a fil e if you us e the opt ional destin ation
parameter. For example, :DISK:LOAD "STM1_OC3",SMASK will automatically add .msk to
the file name.

Note

For .gif and .tif file formats, this instrument uses LZW compression/decompression licensed
under U.S. patent No 4,558,302 and foreign counterparts. End user should not modify, copy, or
distribute LZW compression/decompression capability.

For .jpg file format, this instrument uses the .jpg software written by the Independent JPEG
Group.

Page 1-13 Change the following default file locations table:

Ta ble 1-3. Default File Locations (Storing Files)

File Type Default Location

Mask C:\Scope\masks (standard masks)

C:\User Files\masks (user-defined masks)

Page 1-18 Add the following not e to the DIGITIZE command description:

3

Introduction

Note

The execution of the DIGITIZE command is subordinate to the status of ongoing limit tests. (See com­mands ACQuire:RUNTil , MTEST:RUNTil, and LTEST.) The DIGITIZE command will not capture data if the
stop condition for a limit test has been met.

4

Status Reporting

Page 4-5 Change the following status reporting bit definitions table:

Ta ble 4-1. Status Reporting Bit Definition

Bit Description Definition

UNLK UNloCKed Indicates that an unlocked or trigger loss condition has occurr ed i n the

Clock Recovery Module.

LOCK LOCKed Indicates that a locked or trigger capture condition has occurred in the

Clock Recovery Module.

Page 4-14 Clock Recovery Event Register (CRER)

Change the Bit 0 (UNLK) and Bit 1 (LOCK) descriptions to read:
Bit 0 (UNLK) of the Clock Recovery Event Register is set when Clock Recovery module

becomes unlocked or trigger l oss ha s occurred for the 83494A family of module s.
Bit 1 (LOCK) of the Clock Recovery Event Register is set when Clock Recovery module

becomes locked or a trigger capture has occurred for the 83494A family of modules.

Status Reporting

Programming Conventions

Pages 5-6 to 5-8 Change the following command trees:

5

Programming Conve ntions

Command Trees

Figure 5-2. Command Tree

6

Programming Conventions

Command Tree (Continued)

7

Programming Conve ntions

Command Tree (Continued)

8

Command Tree (Continued)

Common Commands

Common Commands

Page 7-9 Add the followin g no te to the *OPC (Operation Complete ) c ommand:

Note

Three commands are available for the synchronization between remote command scripts and the instru­ment:

• The *OPC command: This command sets a bit in the Standard Event Status Register when all pendi ng
device operations have finished. It is useful to verify the completion of commands that could take a
variable amount of time or commands executed in parallel with other commands, such as PRINt, and
the limit test commands (ACQuire:RUNtil, MTEST:RUNtil, and LTEST). It does not stop the execution
of the remote script.

• The *OPC query: This query allows synchronization between the computer and the instrument by us­ing the message available (MAV) bit in the Status Byte, or by reading the output queue. Unlike the
*OPC command, the *OPC query does not affect the OPC event bit in the Standard Event Status Reg­ister. The execution of the remote script is halted and therefore the *OPC query should be used judi­ciously. For example, the command “:MTEST:RUNtil FSAMPLES,100’; *OPC?” will lock the remote
interface until 100 failed samples are detected, which could take a very long tim e. Under these cir­cumstances, the user must send a device clear or power down to re-start the instrument.

• The *WAI command: This command is similar to the *OPC? query as it will also block the execution
of the remote script until all pending operations are finished. It is particularly useful if the host com­puter is connected to two or more instruments. This command will not block the GPIB bus, al lowing
the computer to continue issuing commands to the instrument not executing the *WAI command.

Page 7-20 Add the following not e to the *WAI (Wait-to-C ontinue) command:

9

Root Level Commands

Note

Three commands are available for the synchronization between remote command s c ripts and the instru­ment:

• The *OPC command: This command sets a bit in the Standard Event Status Register when all pendi ng
device operations have finished. It is useful to verify the completion of commands that could take a
variable amount of time or commands executed in parallel with other commands, such as PRINt, and
the limit test commands (ACQuire:RUNtil, MTEST:RUNtil, and LTEST). It does not stop the execution
of the remote script.

• The *OPC query: This query allows synchronization between the computer and the instrument by us­ing the message available (MAV) bit in the Status Byte, or by reading the output queue. Unlike the
*OPC command, the *OPC query does not affect the OPC event bit in the Standard Event Status Reg­ister. The execution of the remote script is halted and therefore the *OPC query should be used judi­ciously. For example, the command “:MTEST:RUNtil FSAMPLES,100’; *OPC?” will lock the remote
interface until 100 failed samples are detected, which could take a very long tim e. Under these cir­cumstances, the user must send a device clear or power down to re-start the instrument.

• The *WAI command: This command is similar to the *OPC? query as it will also block the execution
of the remote script until all pending operations are finished. It is particularly useful if the host com­puter is connected to two or more instruments. This command will not block the GPIB bus, al lowing
the computer to continue issuing commands to the instrument not executing the *WAI command.

Root Level Commands

Page 8-7 Change the CRER? query, Bit 0 (UNLK), and Bit 1 (LOCK) descriptions to read:

This query returns the current value of the Clock Recovery Event Register as a decimal
number and also clears this register. Refer to the “:CRECovery:SPResent?” query in Cha p ­ter 13 for more detailed information on receiver one and receiver two.

Bit 0 (UNLK) of the Clock Recovery Event Register is set when the clock recovery module
becomes unlocked or trigger l oss ha s occurred for the 83494A family of module s.

Bit 1 (LOCK) of the Clock Recovery Event Register is set when the clock recovery module
becomes locked or a trigger capture has occurred for the 83494A family of modules.

Page 8-8 Add the followin g note to the :DIGitiz e co m m a nd description:

Note

As with the RUN command, the DIGitize command will not be executed if the stop condition for an ongo­ing limit test has been satisfied. The stop condition is specified by commands ACQuire:RUNTil ,
MTEST:RUNTil, or L TES T.

Page 8-13 Change the :PRINt example to rea d:

Example This example outputs a copy of the screen to a printer or a disk file. See *OPC (Operation

Complete) command for synchronization of PRINT operations.

10 OUTPUT 707;":PRINT"
20 END

Page 8-13 Add the followin g note to the :Run comm a nd:

10

Acquire Commands

Note

The execution of the RUN command is subordinate to the status of ongoing limit tests. (see commands
ACQuire:RUNTil, MTEST:RUNTil, and LTEST). The .RUN command will not start data acquisiton if the
stop condition for a limit test has been met.

Page 8-15 Change the STORe:WAVeform command to read:

Command :STORe:WAVEform {CHANnel<N> | FUNCtion<N> | WMEMory<N> | RESPonse<N>},{WMEMory<N>}

Acquire Commands

Page 10-6 Change the :AC Quire:SSCReen <f ilename> descr iption to read:

<filename> An ASCII string enclosed in quotation marks. If no filename is specified, a default filename

is assigned. This fil ename w ill be AcqLimitScreenX.bmp, where X is an incremental num-
ber assigned by the instrument.

Note

The save screen options established by the commands ACQuire:SSCReen DISK,
ACQuire:SSCReen:AREA, and ACQuire:SSCReen:IMAG are stored in the instrument’s memory and will
be employed in consecutive save screen operations, until changed by the user. This includes the
<filename> parameter for the ACQuire:SSCReen DISK command. If the results of consecutive limit tests
must be stored in different files, omit the <filename> parameter and use the default filename instead.
Each screen image will be saved in a different file named AcqLimitScreenX.bmp, where X is an incre­mental number assigned by the instrument.

The filename field encodes the network path and the directory in which the file will be
saved, as well as the file format that will be used. The following is a list of valid filenames.

Valid Filenames

Filename File Saved in Directory...

“Test1.gif” C:\User Files\Scre en Ima ges \
“A:test2.pcx” A:\
“\\computer-ID\d$\test3.bmp” File saved in drive D: of computer “computer-ID”, provided all permissions are

set properly.

“E:test4.eps” File saved in the instrument’s drive E:, that could be mapped to any disk in the

network.

If a filename is specified without a path, the default path will be C:\User Files\screen
images. The default file type is a bitmap (.bmp). The following graphics formats are avail­able by specifying a file extension: PCX files (.pcx), EPS files (.eps), Postscript files (.ps),
JPEG files (.jpg), TIFF files (.tif), and GIF files (.gif).

Page 10-9 Add the followin g no te to the :ACQuire :SWAVeform <filename> descriptio n:

11

Calibration Commands

Note

If the selected waveforms of consecutive limit tests are to be stored in individual files, omit the <file­name> parameter. The waveforms will be stored in the default format (INTERNAL) using the default
naming scheme.

Calibration Commands

Page 11-7 Add the followin g c ommand:

MODule:LRESistance

Command :CALibrate:MODule:LRESistance <resistance_value>

This command sets the load resista nc e value used during vertical calibration of a TDR
module. The accur a c y of the calibration is improved by specifyin g th e exa c t resistance
value of the load that is connected to the TDR module during the calibration process.

<resistance_value> The resistance of the load from 47 to 53 ohm. The defaul t value is the targ et value of

50 ohm.

Example This example sets the load resistance value to 49.9 ohms.

10 OUTPUT 707;":CALIBRATE:MODULE:LRESISTANCE 49.9"
20 END

Query :CALibrate:MODule:LRESistance?

The query returns the resistanc e value in ohms for the load used during v e rtical calibra­tion of a TDR module.

Returned Format [:CALibrate:MODule:LRESistance] <resistance_value><NL>

Page 11-9 Change the :CALibrate:MODule:STATus?{LMODu le | RMODule} query description to read:

This query re turns the status o f the vertical calibration (ele c trical channels) and optica l
calibration (optical channels) as either CALIBRATED or UNCALIBRATED. It will return
UNKNOWN if th e m o dule does not have ca libration cap a b ility. Queries to modules with
two electrical channels (including TDR modules) will return the status of vertical calibra­tion only.

Change the returned format to read:

Returned Format [:CALibrate:MODule:STATus] {<status vertical calibration>,<status optical calibration> | CALIBRATED |

Page 11-11 Change the :CALibrate:SKEW <skew_valu e> description to read:

<skew_value> A real number, 0 s to 100

Page 11-12 Change the :CALibrate:STATus? query description and <status> description to read:

<status> <Mainframe/Horizontal Status>,

UNCALIBRATED | UNKNOWN} <NL>

µs

This query returns the calibration status of the analyzer. These are nine comma-separated
integers, with 1 o r 0 . A "1" indicates calibrated; a "0" ind ic a t es uncalibrated. T his matches
the status in the C a li bration dialog box in the Calibra te menu.

<Channel1 Vertical>, 0,
<Channel2 Vertical>, 0,
<Channel3 Vertical>,0,
<Channel4 Vertical>, 0

12