Manual Change Supplement
Agilent 86100A
Introduction
Introduction
This supplement contains corrections for the 86100A manuals that are listed in the following 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 extension) 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 commands 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 instrument:
• 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 using 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 Register. The execution of the remote script is halted and therefore the *OPC query should be used judiciously. 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 circumstances, 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 computer 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 instrument:
• 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 using 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 Register. The execution of the remote script is halted and therefore the *OPC query should be used judiciously. 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 circumstances, 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 computer 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 ongoing 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 incremental 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 available 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 <filename> 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 calibration 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 calibration 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
Channel Command s
The values that always return “0” are used to make the returned format compatible with
the Agilent 83480A and 54750A.
Channel Commands
Page 12-4 Change the FDEScription? query description to read:
Query This query return s the number of filte rs and a brief description of each filter for channels
with one or more internal low-pass filters.
Change the returned format to read:
Returned Format [:CHANnel<N>:FDEScription]<n><filter1_description>,<filter2_description>,<filter3_description>,
Page 12-5 Change the FSElect com ma nd and <fi lter_number> descripti ons to read:
Command This command selects which fi lt er is contr oll ed by on /of f fo r cha nn els w ith mo re than one
<filter_number> The filter number is an integer from 1 to 4. In the Channel dialog box, filter number 1 is
Returned Format [:CHANnel<N>:FSELect]{FILT<filter_number>}<NL>
<filter4_description><NL>
filter selection.
the first filter listed in the
Change the returned format to read:
Filter box.
Page 12-6 Change the :CHANnel<N>:OFFSet command description to read:
This command sets the voltage that is represented at the c e nter of the display fo r the
selected channel. Offset parameters are probe and vertical scale dependent.
For TDR and TDT applications, when the TDR stimulus is set to differential or common
mode, the instrume n t will change offset to magn if y o ff set. This command is used to set
the magnify of fset as well as t he offset.
Page 12-6 Change the :CHANnel<N>:PROBe? query description to read:
Query CHANnel<N>:PROBe?
When the TDR stimulus is set to differential or common mode, the instrument will change
offset to magnify offs et. This command is use d to set the magnify offs et as well as the offset .
Page 12-8 Change the :CHANnel<N>:SCAL e com ma nd de scription to read:
This command sets the vertical scale, or units per division, of the selected channel. This
command is the same as the front-panel channel scale.
For TDR and TDT applications, when the TDR stimulus is set to differential or common
mode, the instrument will change scale to magnify scale. This command is used to set the
magnify scale as well as th e scale.
Page 12-9 Add the followin g no te to the :CHANnel<N>:TDRSkew co m m a nd description:
Note
This command is enabled only if a stimulus is currently active and if the module has differential capability.
13
Clock Recovery Commands
Page 12-10 Change the :CHANnelN:WAVelength command to read:
Command :CHANnel<N>:WAVelength {WAVelength1 | WAVelength2 | USER}
Change the :CHANnelN:WAVelength query to read:
Query :CHANnel<N>:WAVelength?
The query returns the currentl y selected wavel ength for the channel.
Returned Format [:CHANnel<N>:WAVelength] {WAV1 | WAV2 | USER}<NL>
Clock Recovery Commands
Page 13-3 Change the :CRECovery{1|3}:LOCKed? query description to read:
The query returns the locked or triggered status of the clock recovery module.
Locked or triggered status returns 1, unlocked or trigger loss sta tus returns 0. When a
clock rate is selected, unlocked status indicates clock recovery cannot be established and
trigger output to the mainframe is disabled. In bypass mode (TOD) status is always 0 and
trigger output to the mainframe is not disabled.
Page 13-3 Change the :CRECovery{1|3}:RATE command to read:
Command :CRECovery{1 |3}:RATE {TOData | R155 | R622 | R1062 | R1250 | R2125 | R2488 | R2500 | R2666 | R9953 |
R10664}
This command sets the c lock recovery module data rate based on mo du le slot position:
left slot (1), right slot (3). The rates are: Trigger On Data (TOData), Rate 155, Rate 622,
Rate 1062, Rate 1250, Rate 2125, Rate 2488, Rate 2500, Rate 2666, Rate 9953, and Rate
10664 in Mb/s.
Rate parameters are nominal and reflect front panel la be l s and not actual data rates.
Data Rates vs. Model
Rate
Parameter
TOData — XXXXX
R155 155.52 X X X X X
R622 622.08 X X X X X
R1062 1062.50 X X
R1250 1250.00 X X X
R2125 2125.00 X X
R2488 2488.32 X X X X X
R2500 2500.00 X X X
Note
After setting a rate, locked or triggered status should be verified before executing any signal dependent
GPIB commands, such as autoscale, or any measurements. This is required to allow the module/instrument enough time to establish a trigger. This can be achieved by querying locked status until locked or
generating an event on the module lock.
As noted in the table below, not all modules suppor t the sam e rates.
Module Model Number
Rate (Mb/s)
83491 83492 83493 83494
83494
Option 106
14
Data Rates vs. Model
Disk Commands
Rate
Parameter
R2666 2666.06 X
R9953 9953.28 X
R10664 10664.23 X
Rate (Mb/s)
Module Model Number
83491 83492 83493 83494
83494
Option 106
Example This example sets the module in the right slot to a data rate of 2488 Mb/s.
10 OUTPUT 707;":CRECOVERY3:RATE R2488"
20 END
Query :CRECovery{1 | 3}:RATE?
This query return s the current data rate of the clock reco v e ry module in the specified
module position.
Returned Format [:CRECovery{1 | 3}:RATE] {TOData | R155 | R622 | R1062 | R1250 | R2125 | R2488 | R2500 | R2666 | R9953 |
R10664}<NL>
Example The following example checks the current data rate of the module in the left slot and
places the result in the string variable, Rate$. Then the program prints the contents of the
variable to the controller’s screen .
10 DIM Rate$[50]
20 OUTPUT 707;":CRECOVERY1:RATE?"
30 ENTER 707;Rate$
40 PRINT Rate$
50 END
Page 13-5 Add the following table to the :CREC o v e ry{1|3}:SPRes ent? query descr iption:
Signal Present Return Status vs. Receiver Number
Module Model
83491 0 0
a
83492
83493 0 1/0
83494 0 1/0
83494 Option 106 0 1/0
a. Only one receiver at a time can have a signal present.
Receiver 1
Short Wavelength
1/0 1/0
Receiver 2
Long Wavelength
Disk Commands
Page 14-2 Change the DISK subsystem commands introductory description to incl ude :
The DISK subsystem commands perform the disk operations as defined in the Disk menu.
This allows storage and retrieval of waveforms and setups, remote screen captures, as
well as formatting the disk.
Page 14-3 Change the :DISK:DELete c o mma nd description and the example to read:
15
Display Commands
This command deletes a file from the disk. If no path is specified, it searches for the file
using the present working direc to ry. An error is disp la y ed on the analyzer sc reen if the
requested file do es not exist. The file “C:\User Files ” cannot be deleted.
Example 10 OUTPUT 707;":DISK:CDIRECTORY SETUPS"
20 OUTPUT 707;":DISK:DELETE ""FILE1.SET"""
30 END
Page 14-6 Add the followin g c ommand:
SIMage
Note
This command operates only on files and directories on “A:\”, under “C:\User Files”, or on any mapped
network drive.
Command :DISK:SIMage "<filename>"
This command remotely captures images of the screen.
<filename> 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 filename field encodes the network path of 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 Direct ory ...
“Test1.gif” C:\User Files\Screen Images\
“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.
The following graphics formats are available by specifying a file extension: PCX files
(.pcx), EPS files (.eps), Postscript files (.ps), JPEG files (.jpg), TIFF files (.tif), and GIF
files (.gif).
Display Commands
Page 15-4 Change the :DISPlay:DATA ? query to read:
Query :DISPlay:DATA? [<format>[,<screen_mode> [,<inversion>]]]
The query returns information about the captured data. If no options to the query are
specified, the default selections are PCX file type, SCReen mode, and inversion set to
NORMal.
<format> The file format: BMP | PCX | EPS | PS | GIF | TIF | JPG.
<screen_mode> The display setting: SCReen | GRATicule.
<inversion> The inversion of the disp layed file: NORMal | INVer t | MO No c hr ome.
Returned Format [:DISPlay:DATA] <binary_block_data><NL>
16
Function Commands
<binary_block_data> Data in the IEEE 488.2 definite block form at.
Function Commands
Page 16-3 Change the :FUNCtion<N>:DISP lay command to re a d :
Command :FUNCtion<N>:DISPlay {{ON | 1} | {OFF | 0}}
Page 16-4 Change the :FUNCtion<N>? que ry <o pe rator> description and the exam pl e to re ad:
<operator> Active math operation for the selec ted function: IN Vert, MAGNify, MAXimum, MINim um,
SUBT ra ct, or VERSus.
10 :SYST:HEAD ON
20 :FUNC1:SUBTRACT CHAN1,CHAN2
30 :FUNC1? !returns :FUNC1:SUBTRACT CHAN1,CHAN2
40 :SYST:HEAD OFF
50 :FUNC1? !returns CHAN1,CHAN2
Page 16-4 Add the followin g no te to the :FUNCtion< N>:HORizontal co mmand descriptio n:
Note
This command applies only to the Magnify and Versus operators.
Page 16-5 Add the following not e to the :FUNCtion<N>:HORizontal:POSition command description:
Note
This command applies only to the Magnify and Versus operators.
Change the :FUNCtion<N>:HOR izontal:POSition query and th e example to read:
Query :FUNCtion<N>:HORizontal:POSition?
The query returns the current time value at center screen of the selected function.
Note
This query returns the current time value only when the respective function display is ON.
Example This example places the current horizon ta l po si tion setting for functi on 2 in the numeric
variable, Value, then prints the contents to the computer's screen.
10 OUTPUT 707;":SYSTEM:HEADER OFF" !Response headers off
20 OUTPUT 707;":FUNCTION2:DISPLAY ON"
30 OUTPUT 707;":FUNCTION2:HORIZONTAL:POSITION?"
40 ENTER 707;Value
50 PRINT Value
60 END
Page 16-5 Add the followin g no te to the :FUNCtion< N > :HORizontal:RA NGe command description:
Note
This command applies only to the Magnify and Versus operators.
17
Function Commands
Change the :FUNCtion<N>:HORizontal:RANGe query and the example to read:
Query :FUNCtion<N>:HORizontal:RANGe?
The query returns the current time range setting of the specified function.
Note
This query returns the current time range setting of the specified function only when the respective
function display is ON.
Example This example places the curren t ho rizo nta l ra nge se tt ing of f unct ion 2 in the n um eric vari -
able, Value, then prints the contents to the computer's screen.
10 OUTPUT 707;":SYSTEM:HEADER OFF" !Response headers off
20 OUTPUT 707;":FUNCTION2:DISPLAY ON"
30 OUTPUT 707;":FUNCTION2:HORIZONTAL:RANGE?"
40 ENTER 707;Value
50 PRINT Value
60 END
Page 16-7 Add the followin g c o m m a nds:
MAXimum
Command :FUNCtion<N>:MAXimum <operand>
This command defines a function that computes the maximum value of the operand waveform in each time bucket.
<N> An integer, 1–4, represen ti ng the selected function.
<operand> {CHANnel<n> | FUNCtion<n> | WMEMory<n> | <float_value>}
<n> An integer from 1 to 4.
MINimum
Command :FUNCtion<N>:MINimum <operand>
This command defines a function that computes the minimum va lue of each time bucket
for the defined operand’s waveform.
<N> An integer, 1–4, represen ti ng the selected function.
<operand> {CHANnel<n> | FUNCtion<n> | WMEMory<n> | <float_value>}
<n> An integer from 1 to 4.
Page 16-7 Change the :FUNCtion<N>:OF FSet query and the example.
Query :FUNCtion<N>:OFFSet?
The query returns the current offset value for the selected function .
Note
This query returns the current offset value of the specified function only when the respective function
display is ON.
Example This example places the current setting for offset on function 2 in the numeric variable,
Value, then prints the result to the computer's screen.
10 OUTPUT 707;":SYSTEM:HEADER OFF" !Response headers off
20 OUTPUT 707;":FUNCTION2:DISPLAY ON"
18
Function Commands
30 OUTPUT 707;":FUNCTION2:OFFSET?"
40 ENTER 707;Value
50 PRINT Value
60 END
Page 16-8 Change the :FU NCtion<N>:R ANGe query and the example t o read:
Query :FUNCtion<N>:RANGe?
The query returns the current full scale range setting for the specified function.
Note
This query returns the current full scale range setting of the specified function only when the respective
function display is ON.
Example This example places the current range setting for function 2 in the numeric variable
“Value,” then prints the contents to the computer screen.
10 OUTPUT 707;":SYSTEM:HEADER OFF" !Response headers off
20 OUTPUT 707;":FUNCTION2:DISPLAY ON"
30 OUTPUT 707;":FUNCTION2:RANGE?"
40 ENTER 707;Value
50 PRINT Value
60 END
Page 16-11 Change the :FU NCtion<N>:V ER Tical:OFFSet query a n d the example to read:
Query :FUNCtion<N>:VERTical:OFFset?
The query returns the current offset value of the selected function.
Note
This query returns the current offset value of the specified function only when the respective function
display is ON.
Example This example places the current offset setting for function 2 in the numeric variable,
Value, then prints the contents to the com puter's screen.
10 OUTPUT 707;":SYSTEM:HEADER OFF" !Response headers off
20 OUTPUT 707;":FUNCTION2:DISPLAY ON"
30 OUTPUT 707;":FUNCTION2:VERTICAL:OFFSET?"
40 ENTER 707;Value
50 PRINT Value
60 END
Page 16-11 Change the :FUNCtion<N>:VERTical:RANGe query and the example to read:
Query :FUNCtion<N>:VERTical:RANGe?
The query returns the current range set t ing of the specified function.
Note
This query returns the current range setting of the specified function only when the respective function
display is ON.
Example This example place s the c urrent vertical ran ge setting of function 2 in the numeric vari-
able, Value, then prints the contents to the compu ter screen.
10 OUTPUT 707;":SYSTEM:HEADER OFF" !Response headers off
19
Histogram Commands
20 OUTPUT 707;":FUNCTION2:DISPLAY ON"
30 OUTPUT 707;":FUNCTION2:VERTICAL:RANGE?"
40 ENTER 707;Value
50 PRINT Value
60 END
Histogram Commands
Page 18-5 Add the followin g c ommand:
WINDow:BORDer
Command :HISTogram:WINDow:BORDer {ON | OFF}
This command turns the histogram window border on or off.
Example The following example enables the display of the hist ogram window border.
10 OUTPUT 707;”:HISTOGRAM:WIND O W: BORDER ON”
20 END
Query :HISTogram:WINDow:BORDer?
The query returns the current histogram window bo rd er setting.
Returned Format [:HISTogram:WINDow:BORDer] {ON | OFF}<NL>
Limit Test Commands
Page 19-3 Change the following returned format for :LTESt:FAIL:
Returned Format [:LTESt:FAIL] {INSIDELIMITS| OUTSIDELIMITS| ALWAYSFAIL| NEVERFAIL}<NL>
Page 19-6 Add the following note to the :LTESt:RUNTil FAILur es command description:
Note
To run for a number of waveforms or samples, refer to ACQuire:RUNTil command.
Page 19-7 Add the following note to the :LTESt:Source command descript ion:
Note
As a measurement is activated, the associated measurement limit test is programmed according to
default values expressed by the following script:
:LTESt:SOURce <n>
:LTESt:FAIL OUTSIde
:LTESt:LLIMIt -10
:LTESt:ULIMIt 10
:LTESt:MNFound FAIL
:LTESt:RUNTil FAILUres, 1
Before a measurement limit test is initiated, you must make the necessary adjustments to the default
values otherwise these values will be used during the limit test.
Page 19-7 Change the :LTESt:SSCReen <filename> description to read:
20
Limit Test Commands
<filename> An ASCII string enclosed in quotations marks. If no filename is specified, a filename will
be assigned. The default filename is MeasLimitScreenX.bmp, where X is an incremental
number assigned by the instrum e nt.
Note
The save screen options established by the commands L TESt:SS CReen DISK, LTESt:SSCReen:AREA, and
LTESt: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
L TES t:SSCReen DISK command. If th e 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 MeasLimitScreenX.bmp, where X is an incremental 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\Screen Images\
“A:test2.pcx” A:\
“\\computer-ID\d$\test3.bmp” File sav ed in drive D: of computer “computer-ID”, pro v ided all permissions are
set properly.
“E:test4.eps” Fi le s aved in the instrume nt’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 available by specifying a file extension: PCX files (.pcx), EPS files (.eps), Postscript files (.ps),
JPEG (.jpg), TIFF (.tif) and GIF files (.gif).
Page 19-9 Add the followin g no te to the :LTESt:SSUMmary <filename> descript i o n:
Note
If the summary of consecutive limit tests is to be stored in separate files, omit the <filename> parameter. Limit test summaries will be stored in files named MeasLimitSummaryX.sum, where X is an incremental number assigned by the instrument.
Change the <filename> example to read:
Example The following exam ple saves the summa ry to a disk file named TEST.sum.
10 OUTPUT 707;”:LTEST:SSUMMARY DISK,TEST”
20 END
Change the returned format example to read:
Returned Format The follow in g exa m p le returns the current destination for the summary and prints the
results to the controller’s screen.
10 DIM SUMM$[50]
20 OUTPUT 707;”:LTEST:SSUMMARY?”
30 ENTER 707;SUMM$
40 PRINT SUMM$
21
Marker Commands
50 END
Page 19-10 Add the following note to the :LTESt:SWAVeform <filename> description:
Note
If the selected waveforms of consecutive limit tests are to be stored in individual files, omit the <filename> parameter. The waveforms will be stored in the default format (INTERNAL) using the default
naming scheme.
Page 19-11 Change the SWAVeform:RESet command and example to read:
Command :LTESt:WAVEform:RESet
Example 10 OUTPUT 707;”:LTESt:SWAVeform:RESet”
Marker Commands
Page 20-3 Remove the following command:
REFerence
Command :MARKer:REFerence {TRIGger | REFPlane}
Page 20-7 Change the following command to read:
XUNITs
Change the :MARKer:XUNITs command description to read:
This command sets the units for horizontal display in TDR and TDT applications. the units
may be in seconds or meters relative to the reference plane. The marker mode must be
TDRTDT to use this feature.
Page 20-10 Change the following command to read:
YUNITs
Mask Test Commands
Page 21-10 Add the following note to the :MTESt:RUNTil command de scription:
Note
To run for a number of waveforms or samples, refer to ACQuire:RUNTil command.
Page 21-16 Change the :MTESt:SSCReen <f il ename> description to read:
<filename> An ASCII string enclosed in quotations marks. If no filename is specified, a filename will
be assigned. The default filename is MaskLimitScreenX.bmp, where X is an incremental
number assign ed by the instrument.
22
Mask Test Commands
Note
The save screen options established by the commands MTESt:SSCReen DISK, MTESt:SSCReen:AREA,
and MTESt: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
MTESt: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 MaskLimitScreenX.bmp, where X is an incremental 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 Dir ectory...
“Test1.gif” C:\User Files\Screen Images\
“A:test2.pcx” A:\
“\\computer-ID\d$\test3.bmp” File saved in drive D: of computer “computer-ID”, provided all permi ssions are
set properly.
“E:test4.eps” File saved in the instr u m e nt’s drive E:, that could be mappe d to a ny 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 available by specifying a file extension: PCX files (.pcx), EPS files (.eps), Postscript files (.ps),
JPEG (.jpg), TIFF (.tif), and GIF files (.gif).
Page 21-18 Add the followin g no te to the :MTESt:SSUMmary <filen a m e> description:
Note
If the summary of consecutive limit tests is to be stored in separate files, omit the <filename> parameter. Limit test summaries will be stored in files named MaskLimitSummaryX.sum, where X is an incremental number assigned by the instrument.
Change the <filename> example to read:
Example The following exam ple saves the summa ry to a disk file named TEST.sum.
10 OUTPUT 707;”:MTEST:SSUMMARY DISK,TEST”
20 END
Change the returned format example to read:
Returned Format The follow in g exa m p le returns the current destination for the summary and prints the
results to the controller’s screen.
10 DIM SUMM$[50]
20 OUTPUT 707;”:MTEST:SSUMMARY?”
30 ENTER 707;SUMM$
40 PRINT SUMM$
50 END
Page 21-19 Add the followin g note to the :MTESt:SWAVeform <filena m e> description:
23
Measure Commands
Note
If the selected waveforms of consecutive limit tests are to be stored in individual files, omit the <filename> parameter. The waveforms will be stored in the default format (INTERNAL) using the default
naming scheme.
Measure Commands
Page 22-9 Add the followin g c ommand:
CGRade:CRATio
Command :MEASure:CGRade:CRATio <format>
This command measures the contrast ratio of the RZ (Return-to-Zero) eye diagram on the
color graded display. The dark level or dc offset of the input channel must have been previously calibrated. See “ERATio:STARt CHANnel<N>” to perform a dark level calibrat i o n.
Mode Eye mode only. Also ensure that the eye type is set to RZ. See “MEASure:DEFine”.
<format> {RATio | DECibel | PERCent}
Example The following example measures the contra st ratio.
10 OUTPUT 707;”:MEASURE:CGRADE:CRATIO PERCENT”
20 END
Query :MEASure:CGRade:CRATio? <format>
This query returns the contra st ra tio of the color gra ded display.
Returned Format [:MEASure:CGRade:CRATio]<value>[,<result_state>]<NL>
<value> The contrast ratio.
<result_state> If SENDvalid is ON, the result state is returned with the measurement result. Refer to
“MEASure:RESults?” for a list of the result states.
Example The following example places the c urrent contrast ratio in the numeric v a riable, Value,
then prints the contents of the variable of the controller screen.
10 OUTPUT 707;”:SYSTEM:HEADER OFF” !Response headers off
20 OUTPUT 707;”:MEASURE:CGRADE:CRATIO? PERCENT”
30 ENTER 707;Value
40 PRINT Value
50 END
Page 22-9 Change the :MEASure:CGRade:CROSsing mode description to read:
Mode Eye mode only. Also ensure that the eye type is set to NRZ. See “MEASure:DEFine”.
Page 22-10 Change the :MEASure:CGRade:DCDistortion mode description to read:
Mode Eye mode only. Also ensure that the eye type is set to NRZ. See “MEASure:DEFine”.
Page 22-11 Add the followin g co m mand:
CGRade:DCYCle
Command :MEASure:CGRade:DCYCle
This command measures the duty cycl e o f the RZ (Return-to-Zero) eye diagram on the
color graded display.
24
Measure Command s
Mode Eye mode only. Also ensure that the eye type is set to RZ. See “MEASure:DEFine”.
Example The following example measures the duty cycle of the color graded display.
10 OUTPUT 707;”:MEASURE:CGRADE:DCYCle”
20 END
Query :MEASure:CGRade:DCYCle?
This query returns the duty cycl e of the color graded di splay.
Returned Format [:MEASure:CGRade:DCYCle]<value>[,<result_state>]<NL>
<value> The duty cycle.
<result_state> If SENDvalid is ON, the result state is returned with the measurement result. Refer to
“MEASure:RESults?” for a list of the result states.
Example The following example places the c ur rent duty cycle in the numeric variabl e, Value, then
prints the contents of the variable of the controller screen.
10 OUTPUT 707;”:SYSTEM:HEADER OFF” !Response headers off
20 OUTPUT 707;”:MEASure:CGRade:DCYCle?”
30 ENTER 707;Value
40 PRINT Value
50 END
Page 22-11 Change the :MEASure:CGRade:EHEight mode and query descriptio ns to read:
Mode Eye mode only.
Query :MEASure:CGRade:EHEight? [{RATio | DECibel}]
The query returns the eye height of the col or g ra d e display. RATio sets th e eye height in
amplitude units. DECibel sets the eye height in DB units.
Page 22-11 Change the :MEASure:CGRade:ERATio mode description to read:
Mode Eye mode only.
Page 22-12 Change the :MEASure:CGRade:ESN mode description to read:
Mode Eye mode only.
Page 22-13 Change the :MEASure:CGRade:EWIDth mode description to read:
Mode Eye mode only.
Page 22-14 Add the followin g co m mand:
CGRade:OFACtor
Command :MEASure:CGRade:OFACtor
This command measures the opening factor of the RZ (R e t urn-to-Zero) eye di a gram on
the color graded disp lay.
Mode Eye mode only. Also ensure that the eye type is set to RZ. See “MEASure:DEFine”.
Example The following example measures the opening factor of the color graded display.
10 OUTPUT 707;”:MEASure:CGRade:OFACtor”
20 END
Query :MEASure:CGRade:OFACtor?
This query re turns the openin g fa c t or of the color gra d ed display.
Returned Format [:MEASure:CGRade:OFACtor]<value>[,<result_state>]<NL>
25
Measure Commands
<value> The opening factor.
<result_state> If SENDvalid is ON, the result state is returned with the measurement result. Refer to
“MEASure:RESults?” for a list of the result states.
Example The following example places the current opening factor in the numeric variable, Value,
then prints the contents of the variable of the controller screen.
10 OUTPUT 707;”:SYSTEM:HEADER OFF” !Response headers off
20 OUTPUT 707;”:MEASure:CGRade:OFACtor?”
30 ENTER 707;Value
40 PRINT Value
50 END
Page 22-15 Add the followin g co m mand:
CGRade:PWIDth
Command :MEASure:CGRade:PWIDth
This command measures the pulse width of the eye diagram on the color graded display.
Mode Eye mode only.
Example The following exam ple measures the pulse width of the color graded display.
10 OUTPUT 707;”:MEASure:CGRade:PWIDth”
20 END
Query :MEASure:CGRade:PWIDth?
This query returns the pulse width of the color graded display.
Returned Format [:MEASure:CGRade:PWIDth]<value>[,<result_state>]<NL>
<value> The pulse width.
<result_state> If SENDvalid is ON, the result state is returned with the measurement results. Refer to
“MEASure:RESults?” for a list of result states.
Example The following example places the current pulse width in the numeric variable, Value, then
prints the contents of the variable of the controller screen.
10 OUTPUT 707;”:SYSTEM:HEADER OFF” !Response headers off
20 OUTPUT 707;”:MEASure:CGRade:PWIDth?”
30 ENTER 707;Value
40 PRINT Value
50 END
Page 22-16 Change the :MEASure:DEFine command to read:
Command :MEASure:DEFine <meas_spec>
This command sets up the definition fo r me a surements by spec ifying the delta time,
threshold, or top-base values. Changing these values may affect other measure commands. The follow in g ta ble identifies the relationships bet w een user-DEFined values and
other MEASure commands.
<meas_spec> {THResholds,TOPBase,EWINdow,CGRade,DELTatime}
:MEASure:DEFine Interactions
MEASure Commands THResholds TOPBase EWINdow CGRade DELTatime
RISEtime x x
FALLtime x x
PERiod x x
FREQuency x x
26
Measure Command s
:MEASure:DEFine Interactions (Co ntinued)
MEASure Commands THResholds TOPBase EWINdow CGRade DELTatime
VTOP x
VBASe x
VAMPlitude x
PWIDth x x
NWIDth x x
OVERshoot x x
DUTycycle x x
DELTatime x x
VRMS x x
PREShoot x x
VLOWer x x
VMIDdle x x
VUPPer x x
VAVerage x x
VARea x x
DELTatime x x x
CGRade:CRATio x x
CGRade:CROSsing x x
CGRade:DCDistortion x x
CGRade:DUTYCycle x x
CGRade:ERATio x
CGRade:EHEight x
CGRade:ESN x
CGRade:OFACtor x
CGRade:OLEVel x
CGRade:PWIDth x
CGRade:ZLEVel x
Command :MEASure:DEFine THResholds,{{STANdard} | {PERCent,<upper_pct>,<middle_pct>,<lower_pct>} |
{UNITs,<upper_volts>,<middle_volts>,<lower_volts>}}
<upper_pct>
An integer,
–25 to 125.
<middle_pct>
<lower_pct>
<upper_units>
A real number specifying amplitude units.
<middle_units>
<lower_units>
Command :MEASure:DEFine TOPBase,{{STANdard} |{<top_volts>,<base_volts>}}
<top_volts>
A real number specifying voltage.
<base_volts>
Command :MEASure:DEFine EWINdow,<ewind1pct>,<ewind2pct>
<ewind1pct>
<ewind2pct>
A real number, 0 to 100, specifying an eye wi nd ow as a percentage of th e bit period unit
interval.
Command :MEASure:DEFine CGRade {RZ | NRZ}
This command defines the eye type.
Command :MEASure:DEFine DELTatime, <start edge_direction>,<start edge_number>,<start edge_position>,<stop
edge_direction>,<stop edge_number>,<stop edge_direction>
This command is used to set up edge parameters for delta time m eas ure ment.
<edge_direction> {RISing | FALLing | EITHer}
27
Measure Commands
<edge_number> An integer, from 1 to 20.
<edge_position> {UPPer | MIDDle | LOWer}
Query :MEASure:DEFine? DELTatime
Query :MEASure:DEFine? {EWINdow | THResholds | TOPBase | CGRade | DELTatime}
Returned Format [:MEASure:DEFine] CGRade,<signal_type><NL>
[:MEASure:DEFine] THResholds {{STANdard} | {PERcent,<upper_pct>,<middle_pct>,<lower_pct>} |
{VOLTage, <upper_volts>,<middle_volts>,<lower_volts>}}<NL>
[:MEASure:DEFine] TOPBase {{STANdard} |{<top_volts>,<base_volts>}}<NL>
[:MEASure:DEFine] CGRade {{RZ | NRZ}}
[:MEASure:DEFine] DELTatime, {{<start edge_direction>,<start edge_number>,<start edge_position>,<stop
edge_direction>,<stop edge_number>,<stop edge_direction>}}<NL>
Use the Suffix Multiplier Instead
Using "mV" or "V" following the numeric value for the voltage value will cause Error 138-Suffix not
allowed. Instead, use the convention for the suffix multiplier as described in Chapter 3, “Message Communication and System Functions”.
Example This example returns the current setup for the measurement thresholds to the string vari-
able, Setup$, then prints the contents of the variable to the computer's screen.
10 DIM Setup$[50] !Dimension variable
20 OUTPUT 707;":MEASURE:DEFINE? THRESHOLDS"
30 ENTER 707; Setup$
40 PRINT Setup$
50 END
Page 22-18 Add the followin g co m mand:
DELTatime
Command :MEASure:DELTatime [<source>[,<source>]]
This command meas ures th e time del ay betw een two edges . If no so urce is specifi ed, the n
the sources specified using the :MEASure:SOURce command are used. If only one source
is specified , the n the edges used f or c o m puting delta time belong to that source. If two
sources are specified, then the first edge used in computing to delta time belongs to the
first source and the second edge belongs to the second source.
<source> {CHANnel<number> | FUNCtion<number> | WMEMory<number>}
<number> An integer, from 1 to 4.
Example The following example measures the delta time between channel 1 and channel 2.
10 OUTPUT 707;”:MEASURE:DELTATIME CHANNEL1,CHANNEL2”
20 END
Query :MEASure:DELTatime? [<source>[,<source>]]
The query returns the measured de lta time value.
Returned Format [:MEASure:DELTatime] <value> [,<result_state>]<NL>
<value> Delta time from the first specified edge on one source to the next specified edge on
another source.
<result_state> If SENDVALID is ON, the result state is returned with the measureme nt result. Refer to
the Result States table in the Measure chapter for a list of the result states.
28
Measure Command s
Example The following example places the current value of delta time in the numeric variable,
Value, then prints the contents of the variab le to the controller’s screen. This example
assumes the source was set using MEASure:SOURce.
10 OUTPUT 707;”:SYSTEM:HEADER OFF” !Response headers off
20 OUTPUT 707;”:MEASURE:DELTATIME?”
30 ENTER 707;Value
40 PRINT Value
50 END
T urn Off Headers
When receiving numeric data into numeric variables, turn off the headers. Otherwise, the headers may
cause misinterpretation of returned data.
Page 22-21 Remove the :MEASure:DUTYcycle [<source>] mode description.
Change the <source> and <N> descript ions to read:
<source> {CHANnel<N> | FUNCtion<N> | WMEMo ry < N>}
<N> For channels: Value is dependent on the type of plug-in and its location in the instrument.
For functions: 1 or 2. For waveform memories (WMEMORY): 1, 2, 3, or 4.
Page 22-26 Add the followin g query:
HISTogram:PPOSition?
Query :MEASure:HISTogram:PPOSition? [<source>]
This query return s the p ositi on of t he great est peak of the h istogra m. If t here i s more than
one peak, then it returns the position of the first peak from the lower boundary of the histogram window for vertical axis histograms. Otherwise, in the case of horizontal axis histograms, it returns the position of the first peak from the leftmost boundary of the
histogram window. The optional parameter MEASure:SOURce com m and can b e us ed to
specify the source for the measurement. This query can only be applied to histogram data,
therefore the histogram must be turned on in order to use this query.
<source> {HISTogram}
Returned Format [:MEASure:HISTogram:PPOSition] <value>[,<result_state>]<NL>
<value> The value of the greatest peak of the histogram.
<result_state> If SENDvalid is ON, the res ult s tat e is ret urn ed wi th th e meas ure men t resu lt . Refe r to the
MEASure:RESults command for a list of the result states.
Example 10 OUTPUT 707;”:MEAS UR E:HISTOGRAM:PPOSITION? HI STOGRAM”
20 ENTER 707;HMaxVal
30 PRINT HMaxVal
40 END
Page 22-31 Add the followin g no te to the MEASure:RESults? quer y de sc ription:
Note
In some cases, remote results on statistical measurements may display incorrect ASCII mapping, such
as a ç symbol in lieu of
Page 22-36 Add the following note to the MEASure:TE DGe ? que ry description:
Σ (sigma).
29
Measure Commands
Note
TEDGe is measured for a value less than or equal to 20. A value greater than 20 returns data out of
range.
Page22-37 Add the fol lowing command:
TMAX
Command :MEASure:TMAX [<source>]
This command measures the first time at which the first maximum voltage of the source
waveform occurred. The source is specified with the MEASure:SOURce command or with
the optional parameter following the TMAX command.
<source> {CHANnel<number> | FUNCtion<number> | WMEMory<number>}
<number> An integer, from 1 to 4.
Query :MEASure:TMAX? [<source>]
The query returns the time at which the first maximum voltage occurred.
Returned Format [:MEASure:TMAX] <time>[,<result_state>]<NL>
<time> Time at which the first maximum voltage occurred.
<result_state> If SENDVALID is ON, the result state is returned with the measureme nt result. Refer to
the MEASure:RESults? section for a list of the result states.
Example The following example returns the time at which the first maximum voltage occurred to
the numeric variable, Time, then prints the contents of the variable to the controller’s
screen.
10 OUTPUT 707;”:SYSTEM:HEADER OFF” !Response headers off
20 OUTPUT 707;”:MEASURE:TMAX?”
30 ENTER 707;Time
40 PRINT Time
50 END
Tur n Off Headers
When receiving numeric data into numeric variables, turn off the headers. Otherwise, the headers may
cause misinterpretation of returned data.
Page 22-37 Add the followin g co m mand:
TMIN
Command :MEASure:TMIN [<source>]
This command measures the first time at which the first minimum voltage of the source
waveform occurred. The source is specified with the MEASure:SOURce command or with
the optional parameter following the TMIN command.
<source> {CHANnel<number> | FUNCtion<number> | WMEMory<number>}
<number> An integer, from 1 to 4.
Query :MEASure:TMIN? [<source>]
The query returns the time at which the first minimum voltage occurred.
Returned Format [:MEASure:TMIN] <time>[,<result_state>]<NL>
<time> Time at which the first minimum voltage o cc u rred.
30
TDR/TDT Commands
<result_state> If SENDVALID is ON, the result state is return ed wi th the measurement result. Refer to
the MEASure:RESults? section for a list of the result states.
Example The following example returns the time at which the first min imum voltage occurred to
the numeric variable, Time, then prints the contents of the variable to the controller’s
screen.
10 OUTPUT 707;”:SYSTEM:HEADER OFF” !Response headers off
20 OUTPUT 707;”:MEASURE:TMIN?”
30 ENTER 707;Time
40 PRINT Time
50 END
Turn Off Headers
When receiving numeric data into numeric variables, turn off the headers. Otherwise, the headers may
cause misinterpretation of returned data.
Page 22-39 Add the followin g co m mand:
VAVerage
Command :MEASure:VAVerage {CYCLe | DISPlay} [,<source>]
This command calculates the average voltage over the displayed waveform. The source is
specified with the MEASure:SOURce command or with the optional parameter following
the VAVerage command.
CYCLe The CYCLe parameter instructs the average measurement to measure the average voltage
across the first period of th e display.
DISPlay The DISPlay pa ra meter ins tru cts the aver age meas ureme nt to meas ure all the da ta on the
display.
<source> {CHANnel<number> | FUNCtion<number> | WMEMory<number>}
<number> An integer, from 1 to 4.
Example The following example calculates the average voltage over the displayed waveform.
10 OUTPUT 707;”:MEASURE:VAVERAGE DISPL AY”
20 END
Query :MEASure:VAVerage? {CYCLe | DISPlay}, [<source>]
The query returns the calculated average voltage of the specified source.
Returned Format [:MEASure:VAVerage] <value> [,<result_state>]<NL>
<value> T he calculate d aver ag e voltag e.
<result_state> If SENDVALID is ON, the result state is return ed wi th the measurement result. Refer to
the MEASure:RESults? section for a list of the result states.
Example 10 OUTPUT 707;”:SYSTEM:HEADER OFF” !Response headers off
20 OUTPUT 707;”:MEASURE:VAVERAGE? DISPLAY”
30 ENTER 707;Average
40 PRINT Average
50 END
TDR/TDT Commands
Page 23-3 Change the :TDR{2 | 4}:PREset command description to read:
31
TDR/TDT Commands
This command performs an automatic set up of the instrument for TDR or TDT measurements, based on the stimulus. Th is command does the following:
• Turn on TDR channels.
• If the stimulus is set to EXT ernal (see the STIMulus command in this chapter), turn off chan-
nel 1 or 3 and turn on channel 2 or 4.
• If the TDT destinations are not shown, turn on the TDT destination channels. (See the TDTDest command in this chapter).
• Set the timebase to 500 ps/div and positions the incident edge on screen.
• Turn on averaging and set best flatness (see the ACQuire subsystem).
• For all channels that are on:
• Set the attenuation units to ratio.
• Set the attenuation to 1:1.
• Set the bandwidth to low (12.4 GHz). (Set high for external stimulus .)
• Set the units to volts.
• Set the channel scale to 100 mV/div.
• Set the channel offset to 200 mV or –200 mV for diff er ential stimulus.
Page 23-4 Change the :TDR { 2 | 4} :R ESPonse{1 | 2 | 3 | 4} {OFF | ON | DIFFerential | C OMMonmode}
command description to read:
This command turn s o n or of f a TDR or TDT normaliz ed response.
The RESPonse <n> refers to the stimulus channel used to produce a response waveform,
while the resp on s e w a v e f orms are numbered based on the destination channel. F o r TD R
commands, the response waveform numbers and RESPonse <n> refer to the same waveforms. This is not the case for TDT related commands.
Page 23-5 Change the :TDR{2 | 4}:RESPons e {1 | 2 | 3 | 4}:CALibrate command descripti o n to re ad:
This command begins a TDR or TDT normalization and reference plane calibration. Which
calibration is do ne (T DR o r TDT) depends on the setting of the TDRTDT control. See
“RESPonse:TDRTDT” on page 23-11.
The RESPonse <n> refers to the stimulus channel used to produce a response waveform,
while the resp on s e w a v e f orms are numbered based on the destination channel. F o r TD R
commands, the response waveform numbers and RESPonse <n> refer to the same waveforms. This is not the case for TDT related commands.
Page 23-5 Change the :TDR{2 | 4 }:RESPonse{1 | 2 | 3 | 4}:CALibra t e:CANCel command description to
read:
This command activates the cance l softkey during a TDR or TDT normaliz ati on and refer-
ence plane calibration.
This command is retained for backward comp ati bil it y with the 83480/54750. The pre-
ferred command is :CALibrate:CANCel.
The RESPonse <n> refers to the stimulus channel used to produce a response waveform,
while the resp on s e w a v e f orms are numbered based on the destination channel. F o r TD R
commands, the response waveform numbers and RESPonse <n> refer to the same waveforms. This is not the case for TDT related commands.
Page 23-6 Change the :TDR{2 | 4}:RESPonse{1 | 2 | 3 | 4}:CALibrate:CONTinue command description
to read:
32
TDR/TDT Commands
This command activates the continue softkey during a TDR or TDT normalization and reference plane calibration.
This command is retained for backward compatibility with the 83480/54750. The preferred command is :CALibrate:CONTinue.
The RESPonse <n> refers to the stimulus channel used to produce a response waveform,
while the resp onse waveforms are nu m be red based on the destination chann el . F or TDR
commands, the respon se wa veform numbers and RESPonse <n> refer to the same waveforms. This is not the case for TDT related commands.
Page 23-6 Change the :TDR{2 | 4}:RESPonse {1 | 2 | 3 | 4}:H O Riz ontal {AUTO | MANual} command
description to read:
This command specifies whether the TDR/TDT response should automatically track the
source channel’s horizontal scale (AUTO), or a user-defined scale specified wi th t he HORizontal:POSItion and HORizontal:RANGe commands (MANual). AUTO is the usual setting.
Note
The keyword TSOurce may also be used. This command is compatible with the Agilent 83480/54750
and is equivalent to AUTO.
The RESPonse <n> refers to the stimulus channel used to produce a response waveform,
while the resp onse waveforms are nu m be red based on the destination chann el . F or TDR
commands, the respon se wa veform numbers and RESPonse <n> refer to the same waveforms. This is not the case for TDT related commands.
Page 23-7 Change the :TDR{2 | 4}:RESPonse{1 | 2 | 3 | 4}:HORizontal:POSition <position> command
description to read:
This command specifies the horizontal position of the TDR/TDT response when horizontal
tracking is set to man ual. The position is always reference d to center screen.
The RESPonse <n> refers to the stimulus channel used to produce a response waveform,
while the resp onse waveforms are nu m be red based on the destination chann el . F or TDR
commands, the respon se wa veform numbers and RESPonse <n> refer to the same waveforms. This is not the case for TDT related commands.
Page 23-8 Change the :TDR{2 | 4}:RESPonse{1 | 2 | 3 | 4}:HORizontal:RANGe <range> command
description to read:
This command specifies the range of the TDR/TDT response when the horizontal tracking
is set to manual.
The RESPonse <n> refers to the stimulus channel used to produce a response waveform,
while the resp onse waveforms are nu m be red based on the destination chann el . F or TDR
commands, the respon se wa veform numbers and RESPonse <n> refer to the same waveforms. This is not the case for TDT related commands.
Page 23-9 Change the :T DR { 2 | 4 } :R ESPonse{1 | 2 | 3 | 4} :R ISetime <risetime> comma nd description
to read:
This command se ts the risetime fo r the no rmalized respo nse. The risetim e setting is lim-
ited by the timebase settings and the record length. The normalize response function
allows you to change th e risetime of the normalized step.
33
TDR/TDT Commands
The RESPonse <n> refers to the stimulus channel used to produce a response waveform,
while the resp on s e w a v e f orms are numbered based on the destination channel. F o r TD R
commands, the response waveform numbers and RESPonse <n> refer to the same waveforms. This is not the case for TDT related commands.
Page 23-11 Change the :TDR{2 | 4}:RESPonse{1 | 2 | 3 | 4}:TDRTDT {TDR | TDT} command description
and the example to read:
This command controls th e b ehavior of other :TDR{2| 4:RESPonse commands and que-
ries. A response waveform is fully specified by the TDRTDT setting, as well as by the stimulus value that is part of a “TDR{2 | 4}:RESPonse” command.
The RESPonse <n> refers to the stimulus channel used to produce a response waveform,
while the resp on s e w a v e f orms are numbered based on the destination channel. F o r TD R
commands, the response waveform numbers and RESPonse <n> refer to the same waveforms. This is not the case for TDT related commands.
Example To turn on Response 1 waveform as TDR with stimulus = Chan1:
:TDR2:RESPonse1:TDRTDT to TDR
Set
Set :TDR2:RESPonse1 to NORM
To turn on Respo nse 2 waveform as TD T with stimulus = Chan1:
Set
:TDR2:RESPonse1:TDTDest to Chan2
Set :TDR2:RESPonse1:TDRTDT to TDT
Set :TDR2:RESPonse1 to ON
Page 23-11 Change the :TDR{2 | 4}:RES Ponse{1 | 2 | 3 | 4}:TDTDes t {NONE | CHAN nel<nu mber>} co m-
mand description to read:
This command selects a destination channel for a normalization measurement.
The RESPonse <n> refers to the stimulus channel used to produce a response waveform,
while the resp on s e w a v e f orms are numbered based on the destination channel. F o r TD R
commands, the response waveform numbers and RESPonse <n> refer to the same waveforms. This is not the case for TDT related commands.
For differential and common mode stimuli, the TDT destination is implied as follows:
• The TDT destination for channel 1 is channel 3.
• The TDT destination for channel 2 is channel 4.
• The TDT destination for channel 3 is channel 1.
• The TDT destination for channel 4 is channel 2.
A channel is valid as a TDT destination if it meets the following criteria:
• Must be an electrical channel.
• Must not have an active TDR stimul us.
• Must not be the destin ation of another TDT measurem e nt.
• Must not be the destin ati on of a TDR measurement (external sti m ul us only).
You must select a va lid TDT destination before setting the TDRTDT control to TDT.
Page 23-12 Change the :TDR{2 | 4}:RESPonse{1 | 2 | 3 | 4} :VERTical {AUTO | MANual} command
description to read:
This command specifies whether the TDR/TDT response should automatically track the
source channel’s vertical scale (AUTO), or use a user-defined scale specified with the
VERTical:OFFSet and VERTical:RANGe commands (MANual). AUTO is the usual setting.
34
TDR/TDT Commands
Note
The keyword TSOurce may also be used. This command is compatible with the Agilent 83480/54750
and is equivalent to AUTO.
The RESPonse <n> refers to the stimulus channel used to produce a response waveform,
while the resp onse waveforms are nu m be red based on the destination chann el . F or TDR
commands, the respon se wa veform numbers and RESPonse <n> refer to the same waveforms. This is not the case for TDT related commands.
Page 23-13 Change the :TDR{2 | 4}:RESPonse{1 | 2 | 3 | 4}:VERTical:OFFSet <offset_value> command
description to read:
This command sets the vertical position of the specified response when vertical tracking is
set to MANual. The po sition is always referenced to ce nt er screen.
The RESPonse <n> refers to the stimulus channel used to produce a response waveform,
while the resp onse waveforms are nu m be red based on the destination chann el . F or TDR
commands, the respon se wa veform numbers and RESPonse <n> refer to the same waveforms. This is not the case for TDT related commands.
Change the <offset_value> description to read:
<offset_value> Offset value in volts depending on the current channel UNITs. Suffix UNITs are ignored;
only the scalar part is used (m in mv).
Page 23-14 Change the :TDR{2 | 4}:RESPo nse{1 | 2 | 3 | 4}:VERTical:RANGe <range _ v a lue> command
description to read:
This command specifies the vertical range of the TDR/TDT response when the vertical
tracking mode is set to MANual.
The RESPonse <n> refers to the stimulus channel used to produce a response waveform,
while the resp onse waveforms are nu m be red based on the destination chann el . F or TDR
commands, the respon se wa veform numbers and RESPonse <n> refer to the same waveforms. This is not the case for TDT related commands.
Change the <range_va lue> description to read:
<range_value> Vertical range in volts depending on the current UNITs setting and suffix supplied. (The
suffix does not set the UNITs; it is ignored.)
Page 23-15 Change the :T DR {2 | 4}:STIMulus{OFF | ON | ON1 | O N2 | ON1AND2 | DIFFe rential |
COMMonmode | EXTernal | ON3 | ON4 | ON3AND4} command description to read:
This command turns the TDR/TDT stimulus on or off. This command is set before starting
normalization to specify type of normalization or reference plane calibration to perform.
• The stimulus may be OFF, ON, or EXTernal.
• In slots 1 and 2, the stimulus may be OFF, ON1, ON2, ON1AND2, EXTernal, DIFFerential, or
COMMonmode.
• In slots 3 and 4, the stimulus may be OFF, ON3, ON4, ON3AND4, EXTernal, DIFFerential, or
COMMonmode.
ON,ON1,ON2,
EXTernal
Change the ON, ON1, ON3 mode description to read:
Tu rn on the channel 1 or channel 3 pulse generator for single-e nded TDR or TDT mea-
surements.
35
Error Messages
Error Messages
Page 29-7 Add the following error messag e de sc riptions to Table 29-1:
-224 Illegal parameter value Used where exact value, from a list of possibles, was expected.
-241 Hardware missing Indicates that a legal program command or query could not be executed
because of missing device hardware; for example, an option was not
installed, or current module does no t ha ve har dware to support
command or query. Definition of what constitutes missing hardware is
completely device-specific or module-specific.
36
© Copyright Agilent Technologies Company 2001
All Rights Reserved. Reproduction, adaptation, or translation
without prior written permission
is prohibited, except as allowed
under copyright laws.
Agilent Part No. 8610 0-90034
Printed in USA
July 2001
Agilent Technologies Company
Lightwave Division
3910 Brickway Boulevard
Santa Rosa, CA 95403, USA
Notice.
The information contained in this
document is subject to change
without notice. Companies,
names, and data used in examples herein are fictitious unless
otherwise noted. 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.
Restricte d Ri ghts 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.
Loading...