BitAlyzer and BERTScope technologies are registered with the
U.S. Patent and Trademark Office, U.S. Patent Nos. 5,414,713;
6,636,994; 6,728,311; and other pending patents.
2011 Tektronix
This manual is copyrighted and all rights are reserved. No portion of this document may
be reproduced or transmitted in any form or by any means, electronic or mechanical,
including photocopying and recording, for any purpose without the express written
permission of Tektronix.
Products of Tektronix are covered by U.S. and foreign patents and/or pending patents.
Information available on request.
BitAlyzer and BERTScope are registered trademarks of Tektronix.
This Remote Control Guide is applicable to the following Tektronix products:
BitAlyzer BA1500, BA1600 Bit Error Rate Test Analyzers
BERTScope BSA 85C, BSA125C, BSA260C Signal Integrity Analyzers
BERTScope BSA 85CPG, BSA125CPG, BSA260CPG Pattern Generators
Table of Contents
Theory of Operation ........................................................................................................................... 1
Setting Up Remote Control ................................................................................................................. 2
Remote Control Protocol .................................................................................................................... 2
Detector Data Input ............................................................................................................................................ 48
Detector Symbol Filtering ................................................................................................................................... 50
Basic BER ............................................................................................................................................................. 62
Physical Layer Test .................................................................................................................................. 87
Eye: Data Collecting .......................................................................................................................................... 115
BER Contour ...................................................................................................................................................... 124
BER Contour Optical Mode ............................................................................................................................... 129
Mask Test .......................................................................................................................................................... 153
System View .......................................................................................................................................... 172
System Event Log .................................................................................................................................. 174
Status Queries ....................................................................................................................................... 176
Common Commands ............................................................................................................................ 179
File Transfer .......................................................................................................................................... 180
Error Messages and Codes .................................................................................................................... 182
Index ............................................................................................................................................. 183
ii
BitAlyzer Remote Control
Theory of Operation
BitAlyzer/BERTScope remote control enables operation of bit error analysis and physical layer tests via
an IEEE-488 GPIB communications connection. Remote control is implemented using a text-oriented
command protocol described in the following pages of this document. These commands set and query
the system parameters of the Analyzer and operate the instrument in live error analysis and off-line
playback of previously recorded error data.
The text-oriented commands follow a basic three-part structure, consisting of one word identifying the
major feature being addressed, another word identifying a specific operation or parameter within that
feature, followed by optional parameters.
The Analyzer receives and operates on each command immediately. Command execution sets a status
variable that may be queried by the user to determine if the previous command was successful.
Alternatively, a mode can be selected in which these statuses are automatically returned after each
command execution.
It is most useful to have an understanding of the basic principles of BitAlyzer Error Location Analysis
before undertaking remote control programming. There is a high degree of similarity between the
BitAlyzer Analyzer graphical user interface and the remote control command protocol.
This document describes how to interface with the Analyzer using the IEEE-488 connection. The
Analyzer is an IEEE-488 bus peripheral only; it is not an IEEE-488 bus controller and cannot produce SRQ
signals.
Remote Control setup is accessed in the System view:
View > System > Tools > Remote > IEEE Address
Enter the unique address in the GPIB Address field.
For more technical assistance in programming your remote control applications, please contact
Tektronix. We are glad to help.
1
Setting Up Remote Control
Touch Remote on the System view to launch the RemoteClient program. Touch the Disconnect to
enable the IEEE Address button (this may take a few seconds). Touch IEEE Address.
You should now see the GPIB Configuration dialog. The Primary GPIB Address should be set to ‘3’.
Remote Control Protocol
Command Description
Remote control communications are exchanged as ASCII strings over a LAN telnet (TCP port 23) between
the host computer and the Analyzer. Select a communications port to be used for access to the
instrument's remote control operations. If the port is set to NONE, then remote control is disabled.
The input values of commands are checked against the same ranges as the user interface. If an input is
received that is outside of this legal range, the input will be clipped and recorded in the status queue.
It is recommended that you request the status of a command by sending “SYSTem:ERRor?” after each
command. Besides telling you what has happened with the command, this will also synchronize
command transmission and handling.
Command Syntax
Most commands have both a “long version” and “short version,” indicated by capitalized versus
lowercase letters. For example: GENerator:PATTern? can be typed out exactly as shown, or as
GEN:PATT? The capital letters and the colon (:) are required; the lowercase letters are optional. The
actual use of capital and lowercase letters is not significant – commands are not case-sensitive.
Remote Control Command Lines are defined as ASCII text strings ending with "\r" or "\n".
Every Command Line consists of two parts, a Command and <Setup Data> that are separated by a space
and defined as ASCII texts.
<Setup Data> can be Double, Integer, or Boolean numbers, a file’s absolute pathname, a special word, or
a Data Type. For a Boolean data type, the input can be 1 (ON) or 0 (OFF). The returned response will be
either 1 for true or 0 for false. A question-mark character (?) is added at the end of a command, without
a space, to create a Query.
2
When command setup data uses a string as a parameter, the string should be enclosed in double-quotes
(“string”). Filenames always require the absolute path, enclosed within double-quotes.
For every Command processed, an error code will be returned. If the command has a question mark (a
Query), the setup information is also returned. A list of these codes is included below:
Error Codes Error Messages
0 "NO ERROR" "TOO MANY PARAMETERS"
-350 "Queue Overflow" "UNRECOGNIZED COMMAND"
-10 File transfer error "WRONG PARAMETER TYPE"
-20 System error or event "TOO LITTLE PARAMETERS"
-30 Command error; see list of error messages "WRONG PARAMETER FORMAT"
-40 No software option "WRONG PARAMETER NUMBER"
"WRONG ACTION-ONLY"
"WRONG QUERY-ONLY"
"REQUESTED <QUERY PARAMETER> IS NOT SUPPORTED
ON THE PLATFORM"
Communications Timeouts
Most commands issued to the Analyzer are processed quickly and return within milliseconds. A handful
of commands require considerable processing and take longer, including:
Detector Delay Calibration – 8 sec. (approximately) Generator Delay Calibration – 7 sec. Detector Auto-Align – 5 sec. Generator Data Signal Enabling (BERTScope only) – 7 sec. Run State Enable (Physical Layer Tests that perform initial auto-align) – 6 sec.
As a result, programming the communications architecture with a two-second timeout for most
commands, and a 10-second timeout for the commands listed above is one approach. Another approach
is to set all communications timeouts to be 10 seconds. Of course, commands that don’t require this
much time will not be affected by the longer timeout, and this ensures that all commands can complete
without triggering communications timeouts.
3
VIEW Generator
GEN:DOP:ENAB 0
; Turn off DataP
GEN:DON:ENAB 0
; Turn off DataN
GEN:COP:ENAB 0
; Turn off ClockP
GEN:CON:ENAB 0
; Turn off ClockN
GEN:PATT PN7
; Use a HW 2^7-1 pattern. Load in
; Generator
DET:PATT PN7
; Same pattern loaded into Detector
VIEW Detector
DET:AREN 0
; Auto Resync mode off
; voltage which Gen ClkP will be
; set to AC coupled after the DC
; termination voltage setting
DET:CINP:TAC
DET:DIMP:IMOD
DIFF
; Detector is expecting differential
; data (both inputs)
DET:DINP:TVOL 0
; Detector is going to terminate
; inputs to 0 mV DC
; Don’t care about threshold voltage.
; Auto align will find and set
Sample Remote Programming
Remote Command Usage: BERTScope operation
Cabling Setup:
Cable the Generator ClockP out to the Detector Clock In Cable the Generator DataP out to the Detector DataP In Cable the Generator DataN out to the Detector DataN In
NOTE: Data cables must be the same length
Misc: Assume that data outputs are already set for 50-ohm output impedance.
View Generator
Turn off Generator Amps
Rev. March 2005
PN7 pattern to both Generator and Detector
View Detector
General Detector settings
Set Detector to custom levels. Clock, then Data
4
VIEW Generator
GEN:ICL
9953000000
; Set internal synthesizer to 9.953 GHz
GEN:CSEL INT
; Gate the internal synthesizer to
; the Generator (not an ext syn)
GEN:COP:TVOL 0
; 0 mV Termination for ClockP
GEN:COP:SLOF 0
; 0 mV Offset for ClockP
GEN:COP:SLAM
1000
; 1000 mV (1 V) Amplitude for ClockP
GEN:DOUT:LPNS 1
; Link DataP & DataN. Only set
; conditions for one, other follows
GEN:DOP:TVOL 0
; 0 mV Termination for DataP
GEN:DOP:SLOF 0
; 0 mV Offset for DataP
GEN:DOP:SLAM
1000
; 1000 mV (1 V) Amplitude for DataP
GEN:COP:ENAB 1
; Enable ClockP output
GEN:DOP:ENAB 1
; Enable DataP output
GEN:DON:ENAB 1
; Enable DataN output
Loop Until = 1
GEN:COP:ENAB?
; Is Generator ClockP Enabled yet?
Wait 0.25
Repeat
Loop Until = 1
GEN:DOP:ENAB?
; Is Detector DataP Enabled yet?
Wait 0.25
Repeat
Loop Until = 1
GEN:DON:ENAB?
; Is Detector DataN Enabled yet?
Wait 0.25
Repeat
GEN:PCAL
; Initiate Generator Delay Calibration.
Wait Until reply
; Takes awhile (10 seconds?)
RSTATE?
Repeat
DET:PCAL
; Initiate a Detector Delay Calibration.
Wait Until reply
; Takes awhile (10 seconds?)
RSTATE?
Repeat
Finish setting up the Generator. Set frequency, set output amp conditions
Turn outputs on, and query their “on” status—they can take up to 3 seconds to turn on
Calibrate Generator and Detector Delay paths for this frequency at this time and temperature
5
DET:PDC
; Initiate an Auto Align.
Wait Until reply
; Takes awhile
RSTATE?
Repeat
DET:DCS?
; Was Auto Align successful?
; Result = 1 if successful
DET:ISYNC?
; Should be sync’d
; Result = 1 if sync’d
DET:DCAM?
; What is the data amplitude in mV?
; Should be about 2 V pp (differential —
; adds the amplitudes of the two
; two out-of-phase inputs)
DET:DCHM?
: What is the data offset voltage
; in mV? Should be about 0 V DC
DET:DCW?
: What is the width of the eye?
; Should be inverse of frequency
DET:RUIN 20
; Sets the run interval for 20 seconds
RSTATE 1
; Runs the detector for the set time
; above (20 seconds)
Wait Until Reply
RSTATE?
; Are we done with the 20-second run
; yet?
Repeat
DET:BITS?
; How many bits passed during the
; 20-second run? Should be about 20
; seconds x 9.953 Gb/s
DET:ERR?
; And how many errors in those 20
; seconds?
Now, Auto Align the Detector (“Perform Data Centering”)
Auto Align is completed, and Detector is ready to run (error-free if cabled back-to-back)
But, first, query some results from the Auto Align:
Run bits through the detector for 20 seconds.
Running has stopped. Did errors accumulate along the way? (If you want errors to accumulate,
slightly unscrew the data cables during run time, and watch the GUI in Detector view.)
6
VIEW JITTER
; Switch to Jitter Peak View
RSTATE 1
; Toggle Run state
Wait Until Reply
; Toggling Run state to 1 does an auto align,
; which will take approximately 5 seconds
JITT:TST?
; Query Jitter Peak Status
If OK Proceed
Else Take necessary action
JITT:IVALUE?
Query Invalid value
JITT:TJIT?
Query to retrieve Total Jitter
Run test until Total Jitter value is not the invalid value returned earlier
RSTATE 0
; Stop test once we have valid value
Remote Command Usage: Run a test and read back measurements
Example: Run Jitter Peak analysis and obtain the Total Jitter result.
Assumption: Detector is in sync
Rev. September 2009
7
Returns:
< 1 >
Needs delay recalibration.
< 0 >
Does not need delay recalibration.
Params:
<EXTernal>
External clock reference
<INTernal>
Internal clock reference
Returns:
< EXTernal | INTernal >
Params:
<INTernal>
Generator uses the internal clock synthesizer
<EXTernal>
Generator uses the external clock
Returns:
< INTernal | EXTernal >
Params:
<numeric>
Set Generator data delay in fs.
Returns:
< numeric >
Command Listing
Generator
DELAY:GENRecal?
DELAY:GENR?
Retrieve the information that indicates whether Generator delay needs recalibration. Query only. Note:
Since monitoring for these calibrations is suspended while Physical Layer tests are running, using this
command under those circumstances may not return an accurate result.
Set or retrieve the Generator data delay in femto-seconds.
8
Params:
<numeric>
Generator data delay.
BitAlyzer: When the BitAlyzer is operating within range [1 to 981 MHz],
Data Delay is within range [0 to 33,000 ps]. Input out of range will be
clipped and recorded in the status queue.
When the BitAlyzer is operating within range [982 to 1,500 MHz], Data
Delay is within range [0 to 5,000 ps].
BERTScope: When the BERTScope is operating within range [500 to
1,000 MHz], Data Delay is within range [0 to 32,000 ps]. Input out of range
will be clipped and recorded in the status queue.
When the BERTScope is operating within range [1,100 to 12,500 MHz], Data
Delay is within range [0 to 3,000 ps].
Returns:
< numeric >
Params:
<bool>
On = 1, Off = 0
Returns:
< 1 >
Data inversion is on
< 0 >
Data inversion is off
Returns:
< numeric >
Generator data rate in bits/sec. “0” means No Clock.
Params:
<SWITCHRISE>
Switch momentarily to the other page on rising edge
<SWITCHFALL>
Switch momentarily to the other page on falling edge
Set or retrieve the Generator External Page Select mode.
9
Returns:
< 1 >
Generator is in Full Rate Clock mode
< 0 >
Generator is in Half Rate Clock mode
Params:
<numeric>
Generator internal clock synthesizer frequency in Hz
BitAlyzer BA1500: Range [1 to 1,500,000]
BitAlyzer BA1600: Range [1 to 1,600,000]
BERTScope 7500: Range [100,000,000 to 7,500,000,000]
BERTScope BSA125C: Range [100,000,000 to 12,500,000,000]
BERTScope BSA175C: Range [500,000,000 to 17,500,000,000]
Input out of range will be clipped and recorded in the status queue.
Returns:
< numeric >
Params:
<numeric>
Generator’s Frequency Offset in PPM. Range [-500 to +500]
Set or retrieve Generator’s Reference Out frequency in Hz.
GENerator:SYNFM:PRESent?
GEN:SYNFM:PRES?
Retrieve whether SynFM module is present. Query only.
Generator — Data Generator
GENerator:ISERror
GEN:ISER
Inject a single error. Action only.
GENerator:LUPFilename?
GEN:LUPF?
Retrieve user pattern file that has been loaded to the Generator. Query only.
13
Params:
<PN7 | PN11 | PN15 |
PN20 | PN23 | PN31>
Generator pseudo-random pattern data type. PN11 pattern is
available only on the BERTScope.
<USTart>
User pattern (See GEN:UPLoad to load a user pattern file)
<UCYCle>
User pattern cycle
<ALLZERO>
All-zeros pattern
<PASSthrough>
When corresponding option is purchased, Detector Pass-Through
mode outputs whatever the Detector has just received. Available
only on BERTScope Si models.
Set or retrieve the Generator data type. PRBS-11 is available only on BERTScope instruments. The
‘Passthrough’ type is available only on BERTScope Si 8500C, 17500C, and 25000C models.
Set or retrieve whether the Generator tracks the Detector when loading a user pattern. If the tracking is
true, the command GEN:UPL <“filename”> loads the user pattern into both the Generator and Detector.
GENerator:UPWLen?
GEN:UPWL?
Retrieve the word count from the Generator RAM. Query only.
Set or retrieve the SSC modulation deviation. Argument range is different for first generation hardware
(Option SSC) and second generation (Option XSSC).
16
Params:
<bool>
On = 1, Off = 0
Returns:
< 1 >
SSC is enabled
< 0 >
SSC is disabled
Params:
<numeric>
SSC modulation frequency in Hz.
Option SSC: Range [25,000 to 35,000]
Option XSSC: Range [20,000 to 160,000]. Note that modulation deviation is
Set or retrieve the SSC modulation frequency. Argument range is different for first generation hardware
(Option SSC) and second generation (Option XSSC).
Set or retrieve the termination voltage of the Generator Clock input.
GENerator:CLocKOPTimize
GEN:CLKOPT
BitAlyzer only. Initiates procedure for optimizing the location of the Generator external clock input
threshold. May take seconds to complete. Locates the mid-point of the clock envelope. Action only.
GENerator:CLocKOPTimizeResult?
GEN:CLKOPTR?
BitAlyzer only. Returns the located threshold in millivolts. If optimization fails, returns -99999999 as a
sentinel value. Query only.
Set or retrieve whether the Generator Data+/– outputs are linked. May require some delay to complete.
30
Params:
<numeric>
Generator Trigger offset
BitAlyzer: In 32-bit words. Range [0 to (Pattern Size – 1)] for all the PRBS
patterns. For others, the range is [0 to 0]. Input out of range will be clipped
and recorded in the status queue.
BERTScope: In 128-bit words. Range [0 to (Pattern Size – 1)] for all the PRBS
patterns. For others, the range is [0 to 0]. Input out of range will be clipped
and recorded in the status queue.
Returns:
< numeric >
Params:
<PCYCle>
Generator Trigger out method is pattern cycle
<CLOCk>
BitAlyzer: Generator Trigger out method is a divided-down clock/64
BERTScope: Generator trigger out method is a divided-down clock/256
Set or retrieve the Generator Error Inject mode. May require some delay to complete.
GENerator:IBER?
GEN:IBER?
Retrieve the injected BER of the Generator. Query only.
GSM – Generator Stress Module – Stressed Eye
All GSM commands apply only to the BERTScope family of analyzers. Before using the GSM commands,
send GSM:STRess:ENABle 1 to enable all stress features (see GSM:STRess below).
Set or retrieve whether the entire global stress feature is enabled. The entire stress feature includes
jitter insertion of sinusoidal jitter (SJ), external sinusoidal jitter (EXSJ), random jitter (RJ), PRBS jitter
(BUJ) and external high frequency jitter (EXHF).
There are commands to enable each individual stress insertion, such as GSM:SJitter:ENABle; however,
unless the Stress Feature is enabled using this command, those individual jitter insertion enabling
commands do not enable any jitter insertion. For example, if one sent a “GSM:SJ:ENAB 1” without
enabling the stress feature (query “GSM:STR:ENAB?” returns 0), the system merely caches the SJ Enable
value. The next time “GSM:STR:ENAB 1” is sent, the SJ is then enabled. After the stress feature is
enabled, one can still enable or disable individual types of jitter insertion by sending the corresponding
ENABle command.
This command corresponds to the Clock control’s “Jitter Insertion Enabled” menu item in the Generator
view.
39
Params:
<numeric>
Valid ranges: 0.001:1 to 1000:1 or –60 dB to +60 dB
Returns:
< numeric >
Params:
<DECIBEL>
BERTScope interprets and displays the Detector's Data Input Attenuation
Factor in dB. (Example:20 dB)
<RATIO>
BERTScope interprets and displays the Detector's Data Input Attenuation
Factor as a ratio. (Example:20:1)
Returns:
< DECIBEL | RATIO >
Params:
<bool>
On = 1, Off = 0
Returns:
< 1 >
Detector Blank is inverted
< 0 >
Detector Blank is not inverted
Params:
<numeric>
Bit Rate Multiplier, a numeric value. Range [1 to 8]. A value of –1 calculates the
Bit Rate Multiplier value automatically.
BERTScope only. Set or retrieve the Detector's Data Input Attenuation Factor. Note: The format used for
parameter and return value is determined by the current attenuation factor mode setting. See
DET:ATTENFM below.
Detector Data delay.
BitAlyzer: When operating within the range [1 to 981 MHz], Detector Data
Delay is within a range [0 to 33,000 ps]. Input out of range will be clipped
and recorded in the status queue.
When operating within the range [982 to 1,500 MHz], the Detector Data
Delay is within a range [0 to 5,000 ps].
BERTScope: When the BERTScope is operating within the range [500 to
1,000 MHz], the Detector Data Delay is within a range [0 to 32,000 ps]. Input
out of range will be clipped and recorded in the status queue.
When the BERTScope is operating within the range [1,100 to 12,500 MHz],
the Detector Data Delay is within a range [0 to 3,000 ps].
Set or retrieve the data delay of the Detector (in picoseconds).
DELAY:DETRecal?
DELAY:DETR?
Retrieve the information that indicates whether Detector delay needs recalibration. Query only.
Note: Since monitoring for these calibrations is suspended while Physical Layer tests are running, using
this command under those circumstances may not return an accurate result.
Set or retrieve the Detector capture length. The action causes the machine to capture the input number
of words into the Detector. The query returns the amount of captured RAM in words.
DETector:ISYNc?
DET:ISYN?
Retrieve whether the Detector is in sync. Query only.
DETector:LUPFilename?
DET:LUPF?
Retrieve user pattern file that has been loaded to the Detector. Query only.
DETector:NALArm?
DET:NALA?
Retrieve the negative input protection alarm. Query only.
DETector:PALArm?
DET:PALA?
Retrieve the positive input protection alarm state. Query only.
44
Params:
<PN7 | PN11 | PN15 | PN15
| PN20 | PN23 | PN31>
Pseudo-random data types:
PRBS-7, PRBS-11, PRBS-15, PRBS-20, PRBS-23, PRBS-31.
<USTart>
User pattern (See GEN:UPLoad to load a user pattern file.)
Set or retrieve the termination voltage of the Detector Clock input. May require some delay to
complete.
DETector:CLocKOPTimize
DET:CLKOPT
BitAlyzer only. Initiates procedure for optimizing the location of the Detector Clock input threshold.
Locates mid-point of clock envelope. May take seconds to complete. Action only.
DETector:CLocKOPTResult?
DET:CLKOPTR?
BitAlyzer only. Returns the located threshold in millivolts. If optimization fails, returns -99999999 as a
sentinel value. Query only.
Set or retrieve the Detector's Data Input Attenuation Factor. Note: The format used for parameter and
return value is determined by the current attenuation factor mode setting.
48
Params:
<DECIBEL>
BERTScope interprets and displays the Detector's Data Input Attenuation
Factor in dB. (Example:20 dB)
<RATIO>
BERTScope interprets and displays the Detector's Data Input Attenuation
Factor as a ratio. (Example:20:1)
Set or retrieve the termination AC of the Detector Data input. May require some delay to complete. This
command is available only on the BitAlyzer platform.
Set or retrieve whether Detector Symbol Filtering option is enabled (the corresponding option must be
purchased). Available only on BERTScope 17.5G and 26G analyzers.
DETector:SYMbolFILtering:PRESET <USB3 | SATA | PCIE | PCIESWITCH | SASALIGN | SASPRIMITIVES>
DET:SYMFIL:PRESET <USB3 | SATA | PCIE | PCIESWITCH>
Sets Detector Symbol Filtering according to a preset. The presets are equivalent to setting the symbols
as shown below. Available only on BERTScope 17.5G and 26G analyzers. Action only.
Set or retrieve symbol sequence for Detector Symbol Filtering. User can specify up to four symbols to be
filtered. Available only on BERTScope 17.5G and 26G analyzers. Usage examples:
Set or retrieve the “Resync on end” setting of the Detector Blank input.
51
Params:
<numeric>
Detector Trigger offset.
BitAlyzer: in 32-bit words. Range [0 to (Pattern Size –1) if the detected pattern
is one of the PRBS patterns. For other patterns, the range is [0 to 0]. Input out
of range will be clipped and recorded in the status queue.
BERTScope: in 128-bit words. Range [0 to (Pattern Size –1)] if the detected
pattern is one of the PRBS patterns. For others, the range is [0 to 0]. Input out
of range will be clipped and recorded in the status queue.
Returns:
< numeric >
Params:
<PCYCle>
Detector Trigger out method is pattern cycle
<CLOCk>
BitAlyzer: Detector trigger out method is clock/64
BERTScope: Detector trigger out method is clock/256
Set or retrieve the Detector’s results update interval.
Detector Convenience
DETector:PDARkcalibration
DET:PDAR
Perform Dark Calibration. Action only. May require some delay to complete.
DETector:PDCenter
DET:PDC
Perform Data Centering. This command is equivalent to the ‘Auto Align’ function on the local control
interface. Action only. May require some delay to complete.
DETector:MRESync
DET:MRES
Perform manual resync. Action only.
Detector Auto Align Results
DETector:DCAMv?
DET:DCAM?
Retrieve the data center amplitude in mV. Query only.
DETector:DCHMv?
DET:DCHM?
Retrieve the data center height in mV. Query only.
DETector:DCSuccess?
DET:DCS?
Retrieve whether Detector Data Centering (Auto Align) succeeds or not. Query only.
54
Params:
<ELEC>
BERTScope operates in Electrical mode
<OPTIC>
BERTScope operates in Optical mode
Returns:
< ELEC | OPTIC >
DETector:DCTime?
DET:DCT?
Retrieve the data center time. Query only.
DETector:DCUinterval?
DET:DCU?
Retrieve the data center unit interval. Query only.
DETector:DCUMv?
DET:DCUM?
Retrieve the data center Ua in mV. Query only.
DETector:DCWidth?
DET:DCW?
Retrieve the data center width. Query only.
DETector:IVALue?
DET:IVAL?
Retrieve the illegal value. Query only. Before data centering is successful, all the result queries will
return this illegal value. The user can read the value to know what it is.
Detector Optical Mode
Note: In Electrical mode, values are displayed in mV or percent of amplitude. In Optical mode, choose
between W or dBm.
Retrieve Total Bit Count, Total Error Count, and Total Squelched Count. Query only.
EANalysis:BBER:TBERate?
EAN:BBER:TBER?
Retrieve Total Error Rate. Query only.
EANalysis:BBER:TCOunt?
EAN:BBER:TCO?
Retrieve Total Bit Count. Query only.
EANalysis:BBER:TERRors?
EAN:BBER:TERR?
Retrieve Total Errors. Query only.
63
Params:
<int>
Bin Map Start value. Range [0 to 998]
<int>
Bin Map End value. Range [1 to 32,767]
Returns:
< int, int >
Params:
<BLANking>
Select Blank signal as the boundary
<MARKer>
Select Marker signal as the boundary
<PATTern>
Select Pattern Cycle as the boundary
<USERquantity>
Select a user-specified quantity of bits as the boundary
Returns:
< BLANking | MARKer | PATTern | USERquantity >
EANalysis:BBER:TSCOunt?
EAN:BBER:TSCO?
Retrieve Total Squelched Count. Query only.
Block Errors
EANalysis:BLOCk:ACENter
EAN:BLOC:ACEN
Auto Center Block Errors view. Action only.
EANalysis:BLOCk:BCOunt?
EAN:BLOC:BCO?
Retrieve Block Errors chart Bin Count. Query only.
EANalysis:BLOCk:BDATa?
EAN:BLOC:BDAT?
Retrieve Block Errors binary Bin Data. Query only. The binary query should return #1nnbbb...b where:
1 is a number from 1 to 9 (tells number of digits for block length)
nn is the block length (number of bytes to follow)
b is a byte of binary data
Retrieve Burst Length binary Bin Data. Query only. The binary query should return #1nnbbb...b
where: 1 is a number from 1 to 9 (tells number of digits for block length)
nn is the block length (number of bytes to follow)
b is a byte of binary data
Enable/disable vertical cursors on Burst Length view.
Correlation
EANalysis:CORRelation:ACENter
EAN:CORR:ACEN
Auto Center Correlation View. Action only.
EANalysis:CORRelation:BCOunt?
EAN:CORR:BCO?
Retrieve Correlation Bin Count. Query only.
EANalysis:CORRelation:BDATa?
EAN:CORR:BDAT?
Retrieve Correlation binary Bin Data. Query only. The binary query should return #1nnbbb...b,
where: 1 is a number from 1 to 9 (tells number of digits for block length)
nn is the block length (number of bytes to follow)
b is a byte of binary data
Retrieve Pattern Sensitivity Bin Count. Query only.
EANalysis:PSENsitivity:BDATa?
EAN:PSEN:BDAT?
Retrieve binary Pattern Sensitivity Bin Data. Query only. The binary query should return #1nnbbb...b
where: 1 is a number from 1 to 9 (tells number of digits for block length)
nn is the block length (number of bytes to follow)
b is a byte of binary data
Set or retrieve the Eye Jitter P-P measurement value format.
90
Params:
<TIME>
Value displayed in ps
<%UI>
Value displayed in %UI
Returns:
< TIME | %UI >
Params:
<UW>
Value displayed in μW
<DBM>
Value displayed in dBm
Returns:
< UW | DBM >
Params:
<UW>
Value displayed in μW
<DBM>
Value displayed in dBm
Returns:
< UW | DBM >
Params:
<numeric>
The threshold value in mV or μW that defines the level at which the 80/20 or
90/10 rising or falling edge crosses to set the Rising or Falling Level Crossing in
ps. Limits vary depending on the signal, and must be between the 80/20 or
90/10 points on the rising or falling edges, depending on the edge mode
configuration.
Eye Sample Depth in bits. Range [2,000 to 10,000,000]. Input out of range will
be clipped and recorded in the status queue.
A value of –1 runs the Eye diagram in the ‘Auto’ mode with a sample depth of
10,000 bits.
Returns:
< numeric >
Params:
<“filename”>
CSV file to be saved. Filename in double quotes, include full path
Params:
<numeric>
Eye center time offset in ps. The range of the input is the same as described in
the numeric keypad if you click the volt Center button in the Eye view. Range
[0 to 33,000]
Returns:
< numeric >
Params:
<numeric>
Eye time extent in ps. Range [200 to 33,000]. Input out of range will be
clipped and recorded in the status queue.
Returns:
< numeric >
Params:
<numeric>
Eye time offset in ps. Range [–16,500 to +16,500]. Input out of range will be
clipped and recorded in the status queue.