Keysight Technologies J-BERT M8020A Programming Manual
  1. Manuals
  2. Brands
  3. Keysight Technologies Manuals
  4. Control Unit
  5. J-BERT M8020A
  6. Programming manual

Keysight Technologies J-BERT M8020A Programming Manual

M8000 series of ber test solutions
Hide thumbs Also See for J-BERT M8020A:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
Table of Contents

Advertisement

Quick Links

See also: Configuration Manual , Installation Manual
Keysight M8000 Series of BER
Test Solutions
J-BERT M8020A High-Performance BERT
M8030A Multi-Channel BERT
M8040A High-Performance BERT
Programming
Guide

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the J-BERT M8020A and is the answer not in the manual?

Questions and answers

Related Manuals for Keysight Technologies J-BERT M8020A

Summary of Contents for Keysight Technologies J-BERT M8020A

  • Page 1 Keysight M8000 Series of BER Test Solutions J-BERT M8020A High-Performance BERT M8030A Multi-Channel BERT M8040A High-Performance BERT Programming Guide...
  • Page 2 TAL OR CONSEQUENTIAL DAMAGES IN agreement and written consent from license set forth therein, does not require CONNECTION WITH THE FURNISHING, Keysight Technologies as governed by or permit, among other things, that Key- USE, OR PERFORMANCE OF THIS DOCU- United States and international copyright...

  • Page 3: Safety Summary

    Failure to comply with these precautions or with specific warnings or operating instructions in the product manuals violates safety standards of design, manufacture and intended use of the instrument. Keysight Technologies assumes no liability for the customer's failure to comply with these requirements. Product manuals are provided with your instrument on CD-ROM and/or in printed form.

  • Page 4: Safety Symbols

    Safety Symbols Table 1 Safety Symbol Symbol Description Indicates warning or caution. If you see this symbol on a product, you must refer to the manuals for specific Warning or Caution information to avoid personal injury or damage to the product. Frame or chassis ground terminal.

  • Page 5: Compliance And Environmental Information

    Compliance and Environmental Information Table 2 Compliance and Environmental Information Safety Symbol Description This product complies with WEEE Directive (2002/96/EC) marking requirements. The affixed label indicates that you must not discard this electrical/electronic product in domestic household waste. Product Category: With reference to the equipment types in WEEE Directive Annex I, this product is classed as a “Monitoring and Control instrumentation”...

  • Page 7: Table Of Contents

    Contents Safety Summary Safety Symbols Compliance and Environmental Information 1 Programming Basics Modular Configuration M8020A Modular Configuration M8030A Modular Configuration M8040A Modular Configuration Using Identifiers Location Identifiers Group Name Identifiers Measurement Name Identifiers PLUGin Subsystem 2 Recommended Programming Techniques Output Protection Pattern Generator Output Termination Output Protection Algorithm Controlling the Output Levels...
  • Page 8 Contents Read ing the M8020A/M8030A/M8040A’s Status Reading the M8020A/M8030A/M8040A’s Status - Concepts M8020A/M8030A/M8040A Status Reporting Structure Working with Patterns Symbol Coding Descriptions Symbol Sequences Creating Pattern Sequences Sequence Editor Pattern Sequence Building Blocks Sequencer Triggers Block Branching Link Training Events Block Controls Coding Configuration Link Training Configuration...
  • Page 9 Contents BER Example N4903B BER Example M8020A BER Example M8070A Jitter Tolerance Measurement CSV Output 4 SCPI Command Language SCPI Command Language - Introduction SCPI Common Commands SCPI Instrument Control Commands IEEE 488.2 Mandatory Commands Overlapped and Sequential Commands Data Types Important Points about SCPI Important Points about SCPI - Concepts Send ing Commands to the M8020A/M8030A/M8040A...
  • Page 10 Contents STATus Subsystem :STATus:QUEStionable Subnode :STATus:OPERation Subnode :STATus:INSTrument Subnode TRIGger Subsystem Source Subsystem [:SOURce]:PULSe Subnode [:SOURce]:VOLTage Subnode [:SOURce]:JITTer Subnode [:SOURce]:JITTer:HFRequency Subnode [:SOURce]:JITTer:HFRequency:PERiodic Subnode [:SOURce]:JITTer:HFRequency:BUNCorrelate Subnode [:SOURce]:JITTer:HFRequency:RANDom Subnode [:SOURce]:JITTer:HFRequency:SPECtrally Subnode [:SOURce]:JITTer:LFRequency Subnode [:SOURce]:JITTer:LFRequency:PERiodic Subnode [:SOURce]:JITTer:LFRequency:RSSClocking Subnode [:SOURce]:JITTer:SWEep Subnode [:SOURce]:SSCLocking Subnode [:SOURce]:INTerference Subnode [:SOURce]:INTerference:RANDom Subnode [:SOURce]:INTerference:SINUsoidal Subnode [:SOURce]:CONFigure Subnode...
  • Page 11 Contents SENSe Subsystem CLOCk Subsystem N71000 Subsystem FETCh Subsystem MMEMory Subsystem PLUGin Subsystem :PLUGin:ERATio Subnode :PLUGin:OTIMing Subnode :PLUGin:OTIMing:FETCh Subnode :PLUGin:OLEVel Subnode :PLUGin:OLEVel:ACQuisition Subnode :PLUGin:OLEVel:EVALuation Subnode :PLUGin:OLEVel:FETCh Subnode :PLUGin:OLEVel:FETCh:LEVel Subnode :PLUGin:OLEVel:FETCh:NOISe Subnode :PLUGin:OLEVel:FETCh:QLEVel Subnode :PLUGin:OLEVel:SHOW Subnode :PLUGin:OLEVel:RUN Subnode :PLUGin:JTOLerance Subnode :PLUGin:EDIagram Subnode :PLUGin:EDIagram:ACQuisition Subnode :PLUGin:EDIagram:EVALuation Subnode :PLUGin:EDIagram:FETCh[:RESult] Subnode...
  • Page 12 Contents SYSTem Subsystem DATA Subsystem :DATA:PATTern Subnode :DATA:SEQuence Subnode :DATA:SYNC Subnode :DATA:LINecoding Subnode Index Keysight M8070A Programming Guide...

  • Page 13: Programming Basics

    Keysight M8070A System Software for M8000 Series of BER Test Solutions Programming Guide Programming Basics / 14 Modular Configuration / 21 Using Identifiers / 23 PLUGin Subsystem...

  • Page 14: Modular Configuration

    M8051A high-performance BERT generator-analyzer 8/16 Gb/s • M8061A multiplexer 2:1 with de-emphasis 32 Gb/s • M8062A 32Gb/s Front-end for J-BERT M8020A High-Performance BERT The M8020A modules must be installed in the M9505A 5-slot chassis. The M8030A instrument supports the following modules.
  • Page 15 Programming Basics 1 or 2-channel System Configuration The 1 or 2-channel configuration is a single channel system (a second channel can be added with license) consisting of the 5-slot M9505A AXIe Chassis and an M8041A module. The M8041A occupies three slots. A maximum of two M8020A modules can be installed in a 5-slot chassis.
  • Page 16 Programming Basics Figure 2 M8020A configuration for 16 Gb/s BERT for up to 4 channels 1-channel, 32 Gb/s (Pattern Generator Only) A typical configuration using the M8061A 32 Gb/s multiplexer with de-emphasis consists of the 5-slot M9505A AXIe Chassis, an M8041A module, and an M8061A module.

  • Page 17: M8030A Modular Configuration

    Programming Basics 1-channel, 32 Gb/s (Pattern Generator only or full BERT) A typical configuration for an M8020A 32 Gb/s full BERT consists of the 5-slot M9505A AXIe Chassis, an M8041A module, and an M8062A module. The M8041A occupies three slots and the M8062A occupies two slots. Figure 4 M8020A configuration for 32 Gb/s BERT M8030A Modular Configuration...
  • Page 18 Programming Basics Slot Number Module # 10-11 M8051A module # 12-13 M8051A module # 14 M8192A multi-channel synchronization module, mandatory Figure 5 on page -18 shows an example of modules arrangement in the M9514A AXIe 14-slot chassis. Figure 5 Example of M8030A module arrangement Keysight M8070A Programming Guide...

  • Page 19: M8040A Modular Configuration

    Programming Basics M8040A Modular Configuration The M8040A is a modular test solution which simplifies accurate receiver characterization of devices operating up to 32 and 64 GBaud with NRZ and PAM-4. It supports the following modules. • M8045A pattern generator • M8046A analyzer •...
  • Page 20 Programming Basics M8046A Analyzer Module The M8046A module occupies single slot of the 5-slot M9505A AXIe chassis. The following figure illustrates an M8045A module with M8046A module installed in an M9505A AXIe chassis. M8046A Module Figure 7 M8045A and M8046A configuration M8057A Remote Head The M8057A remote head is an external box which can be connected to each channel of M8045A module, using the matched pair of cables.

  • Page 21: Using Identifiers

    Programming Basics Using Identifiers There are three different types of Identifiers: • Location • Group Name • Measurement Name Location Identifiers When an instrument has several output channels with identical capabilities or a subset of capabilities and has more than one module, the selection of which module/channel to use is done using its location identifier.

  • Page 22: Group Name Identifiers

    Programming Basics Group Name Identifiers Group name identifiers are used to affect a group of inputs or outputs using a single SCPI command. That is, all properties belonging to these identifiers can be addressed simultaneously using the group name. The following SCPI command shows the syntax for creating a group name then adding the desired location identifiers.

  • Page 23: Plugin Subsystem

    Programming Basics PLUGin Subsystem The M8020A/M8030A/M8040A platform supports a plugin interface. C# assemblies which implement certain interfaces are recognized by the software and integrated into the M8070A GUI and instrument software. Error ratio, Output Timing and Jitter Tolerance measurements are examples of the plugin concept.

  • Page 25: Recommended Programming Techniques

    Keysight M8070A System Software for M8000 Series of BER Test Solutions Programming Guide Recommended Programming Techniques / 26 Output Protection / 27 Controlling the Output Levels / 28 Allowing the M8020A/M8030A/M8040A to Settle / 29 Reading the M8020A/M8030A/M8040A’s Status / 36 Working with Patterns / 43 Creating Pattern Sequences...

  • Page 26: Output Protection

    Recommended Programming Techniques Output Protection Pattern Generator Output Termination The pattern generator's output ports must be terminated with 50 Ω if they are not connected. Termination of output ports improves the test performance. Refer also to the M8020A/M8030A/M8040A Getting Started Guide for NOTE information on terminating the M8061A outputs to ensure proper performance.

  • Page 27: Controlling The Output Levels

    Recommended Programming Techniques Controlling the Output Levels Controlling the Output Levels - Concepts When the output levels are changed at the M8020A/M8030A/M8040A data and clock output ports, four parameters are changed: • high • • amptl • offs The M8020A/M8030A groups these parameters into "pairs" (V ampl offs ).

  • Page 28: Allowing The M8020A/M8030A/M8040A To Settle

    Recommended Programming Techniques Allowing the M8020A/M8030A/M8040A to Settle Allowing the M8020A/M8030A/M8040A to Settle - Concepts When patterns are sent to the pattern generator or error detector, the M8020A/M8030A/M8040A requires some time to settle. The following topics explain how the instruments react to pattern changes. How Pattern Changes Affect the Pattern Generator The M8020A/M8030A/M8040A requires some time to change the patterns at the pattern generator and error detector.

  • Page 29: Reading The M8020A/M8030A/M8040A's Status

    Recommended Programming Techniques Reading the M8020A/M8030A/M8040A’s Status Reading the M8020A/M8030A/M8040A’s Status - Concepts The M8020A/M8030A/M8040A has a set of status registers that you can use to monitor the status of the hardware, software and any running tests. Overview of Registers Specifically, it has the following registers: •...
  • Page 30 Recommended Programming Techniques M8020A/M8030A/M8040A Status System Structure The M8020A/M8030A/M8040A's status system is comprised of multiple registers that are arranged in a hierarchical order. The lower-level status registers propagate their data to the higher-level registers in the data structures by means of summary bits. The Status Byte register is at the top of the hierarchy and contains general status information for the M8020A/M8030A/M8040A's events and conditions.
  • Page 31 Recommended Programming Techniques This register is read by the CONDition? SCPI commands. Transition Filters: A positive transition filter allows an event to be reported when a condition changes from false to true. A negative transition filter allows an event to be reported when a condition changes from true to false.

  • Page 32: M8020A/M8030A/M8040A Status Reporting Structure

    Recommended Programming Techniques M8020A/M8030A/M8040A Status Reporting Structure Figure 10 on page -32 shows the M8020A/M8030A/M8040A’s status reporting structure. Figure 10 Status reporting structure Keysight M8070A Programming Guide...
  • Page 33 Recommended Programming Techniques Status Byte The Status Byte is the summary register to which the other registers report. Each reporting register is assigned a bit in the Status Byte Register. The bits in the Status Byte byte have the following meaning: Table 4 Status byte descriptions Mnemonic...
  • Page 34 Recommended Programming Techniques Standard Event Status Register The Standard Event Status register provides general-purpose information about the instrument. It sets bit 5 in the Status Byte. Table 5 Standard event status register descriptions Mnemonic Description Operation Complete Operation Complete bit. It is set in response to the *OPC command, but only if the instrument has completed all its pending operations.
  • Page 35 Recommended Programming Techniques Questionable Status Register The Questionable Status Register indicates that a currently running process is of questionable quality. The output of this register sets bit 3 of the Status Byte. Table 6 Questionable status register descriptions Mnemonic Description 0 - 8 Not used INSTrument...

  • Page 36: Working With Patterns

    Recommended Programming Techniques Working with Patterns Patterns can be accessed with a program and are stored in three different areas: Local to current setting (“current:”) Shared between settings (“shared:”) Factory supplied standard patterns (“factory:”). These patterns are read only and cannot be modified. Below these root nodes is a folder structure using ‘/’...

  • Page 37: Symbol Coding Descriptions

    Recommended Programming Techniques Symbol Coding Descriptions Bit Coding To encode a bit coded (binary) symbol 1, 2, or 3 bits are needed. This depends on the use of mask and squelch. Table 8 Plain bit coding without using mask or squelch Bit Offset/Range Bit (range) Name Description...
  • Page 38 Recommended Programming Techniques Table 12 Error is used Bit Offset/Range Bit (range) Name Description Data Data bit Error Error (ignored on DataOut, ignored on DataIn) Keysight M8070A Programming Guide...
  • Page 39 Recommended Programming Techniques 8b10b Coding To encode an 8b10b symbol 16 bits (2 bytes) are used. Table 13 8b10b coding Bit Offset/Range Bit (range) Name Description Data Symbol data 0 = D-character, 1 = K-character Reserved for future use. Must be set to 0 Mask Mask (if present, ignored on DataOut)
  • Page 40 Recommended Programming Techniques 128/130 Coding To encode 128/130 symbol 144 bits (18 bytes) are used. Table 15 128/130 coding Bit Offset/Range Bit (range) Name Description Framing Framing bits 129:2 Data Data Mask Mask (if present, ignored on DataOut) Squelch Squelch (if present, ignored on DataIn) Reset Scrambler Reset scrambler (ignored on DataIn)
  • Page 41 Recommended Programming Techniques 128/132 Coding To encode a 128/132 symbol 144 bits (18 bytes) are used. Table 16 128/132 coding Bit Offset/Range Bit (range) Name Cod ing-128/132 content Framing Framing bits 131:4 Data Data Mask Mask (if present, ignored on DataOut) Squelch Squelch (if present, ignored on DataIn)

  • Page 42: Symbol Sequences

    Recommended Programming Techniques Symbol Sequences When combining symbols to a sequence of symbols they are filled in one after the other without any gaps. For the non-bit codings that use multiple bytes, the symbols naturally start again on a byte boundary. For the bit codings (binary) they start at the next available bit.

  • Page 43: Creating Pattern Sequences

    Recommended Programming Techniques Figure 13 Example 3: 8b10b coding Creating Pattern Sequences A pattern sequence is configured using a language. The pattern sequence language is based on XML. Sequence Editor Pattern sequences are created and edited using the Sequence Editor in the M8070A software interface as shown in Figure 14 on page -43.
  • Page 44 Recommended Programming Techniques A default “Generator” and “Analyzer” sequence are configured in the Sequence Editor as shown in Figure 14 on page -43. You can edit these sequences or create new ones. As a pattern sequence is being configured, the corresponding XML elements are generated and can be viewed in the XML editor by clicking on the <Xml>...

  • Page 45: Pattern Sequence Building Blocks

    Recommended Programming Techniques Figure 17 Sequence settings Pattern Sequence Building Blocks Minimal Sequence A minimalistic sequence looks like the following: <?xml version="1.0" encoding="utf-16"?> <sequenceDefinition xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.agilent.com/schemas/M8000/DataSequence"> </sequenceDefinition> This sequence generates a 0 signal to all assigned locations. Description To specify a description for the sequence, insert the following: <description>Default 2^7-1 PRBS Sequence</description>...
  • Page 46 Recommended Programming Techniques Symbol Width To specify the symbol encoding this sequence works with, insert the following: <symbolWidth>1</symbolWidth> Available symbol widths are: 1: this is for bit coded symbols 10: this is for 8b/10b coded and bit coded symbols 130: for 128/130 coded and bit coded symbols 132: for 128/132 coded and bit coded symbols Pattern Generation Granularity Pattern generation has granularity.
  • Page 47 Recommended Programming Techniques Blocks and Loops The basic building blocks of a sequence are blocks and loops. A block is the basic unit of a sequence. Here patterns are assigned to locations or branches and are specified to other blocks. A block transitions to the next as a default action.
  • Page 48 Recommended Programming Techniques Length Attribute The length attribute specifies the “length” of the block in number of bits. The enabled attribute allows the block to be temporarily disabled (ignored). If omitted, the default is enabled. <block length="1" enabled="1"></block> Synchronization and Loop Block A special combination of sync and loop is available for achieving synchronization: <syncAndLoopBlock...

  • Page 49: Sequencer Triggers

    Recommended Programming Techniques Sequencer Triggers Trigger output pulses can be generated and controlled from sequence blocks. These pulses are sent to the front panel TRIG OUT connectors. This requires that the trigger mode be set to sequencer controlled. The following describes how to change the trigger mode. In the M8070A software interface, select System >...

  • Page 50: Block Branching

    Recommended Programming Techniques Triggering Based on Specific Bit Sequence The following is an example of a trigger pulse generated based on a specific PRBS bit sequence: <trigger> <pulseOnPrbsMatch width="32" matchPattern="0000000" polynomial="2^7-1" seed="127" invert="0"/> </trigger> All attributes can be omitted. The width defaults to 32. The match pattern defaults to all 0’s or all 1’s depending on the invert attribute.

  • Page 51: Link Training Events

    Recommended Programming Techniques It is also possible to specify a reaction based on a static level or a transition. Using the “event” attribute, you can select “low”, “high”, “positiveEdge” and “negativeEdge”. In the M8070A software interface, select Patterns > Sequence Ed itor. Under the Block Branches settings, change Transition to Positive, Negative, Static High, or Static Low.

  • Page 52: Coding Configuration

    Recommended Programming Techniques CtrlOutA can only be used if it is not currently being used by the global NOTE block controls. Global Block Controls Global block controls are used to set up global routing of signals. Signals can be routed to the CTRL OUT A front panel connector only. One common use could be for generating a pulse on CTRL OUT A whenever an error on the M1.DataIn1 or M1.DataIn2 of the corresponding module occurs:...
  • Page 53 Recommended Programming Techniques After specifying a filler primative, various aspects of the (de)scrambler can be configured with the <scrambler> node. With the polynomial attribute the USB/PCIe or SATA polynomial can be selected. The reset value for the scrambler and the reset value for the scrambler after a hold sequence can be configured with the resetValue and resetValueAfterHold attribute.
  • Page 54 Recommended Programming Techniques PCIe 1/2 <codingConfigurations> <b8b10> <fillerPrimitive symbol1="K28.5" symbol2="K28.0"/> <fillerPrimitive symbol1="K28.0"/> <scrambler> <resetPrimitive symbol1="K28.5"/> </scrambler> </b8b10> </codingConfigurations> SATA <codingConfigurations> <b8b10> <fillerPrimitive symbol1="K28.5" symbol2="D10.2" symbol3="D10.2" symbol4="D27.3"/> <fillerPrimitive symbol1="K28.0"/> <scrambler polynomial="SATA" resetValue="61686" resetValueAfterHold="30349"> <resetPrimitive symbol1="K28.3" symbol2="D21.5" symbol3="D23.1" symbol4="D23.1"/> <holdPrimitive symbol1="K28.3" symbol2="*" symbol3="*" symbol4="*"/>...
  • Page 55 Recommended Programming Techniques MIPI Phy <codingConfigurations> <b8b10> <fillerPrimitive symbol1="K28.1"/> </b8b10> </codingConfigurations> <codingConfigurations> <b8b10> <fillerPrimitive symbol1="K28.5" symbol2="D10.2" symbol3="D10.2" symbol4="D27.3"/> <fillerPrimitive symbol1="K28.5" symbol2="D7.0" symbol3="D7.0" symbol4="D7.0"/> <fillerPrimitive symbol1="K28.5" symbol2="D1.3" symbol3="D1.3" symbol4="D1.3"/> <fillerPrimitive symbol1="K28.5" symbol2="D27.3" symbol3="D27.3" symbol4="D27.3"/> </b8b10> </codingConfigurations> Keysight M8070A Programming Guide...

  • Page 56: Link Training Configuration

    Recommended Programming Techniques Link Training Configuration Link Training Configuration describes the parameters controlling the LTSSM (Link Training and Status State Machine). In the first release it is only defined and implemented for PCI Express 3.0. This is done with the <linkTrainingConfigurations>...
  • Page 57 Recommended Programming Techniques Name Possible Values Default Value Description Used for DUT Type DUT Preset -6 dB Reserved This is the preset hint being Add-in Card Hint -7 dB sent by the BERT to the DUT -8 dB during phase 0 of the link -9 dB equalization procedure.

  • Page 58: Downloading Pattern Sequence To Hardware

    Recommended Programming Techniques Downloading Pattern Sequence to Hardware Once a sequence has been configured, it is downloaded to the hardware using the download button in the Sequence Editor shown in Figure 19 page -58. When the sequence has been downloaded, this button turns green.
  • Page 59 Keysight M8070A System Software for M8000 Series of BER Test Solutions Programming Guide Programming Examples / 60 Introduction / 60 Initializing the Connection / 62 SJ Example / 68 PJ Example / 74 Sampling Point Alignment Example / 78 BER Example / 83 M8070A Jitter Tolerance Measurement CSV Output...

  • Page 60: Programming Examples

    Programming Examples Introduction This chapter provides programming examples for setting up some of the most common functions including: • Initialization • • • Sampling point alignment • If you have programmed the N4903B, examples are provided for comparison to the M8020A. This will facilitate code conversion from the N4903B to the M8020A.

  • Page 61: M8020A Initialization

    Programming Examples M8020A Initialization using System; using System.Collections.Generic; using System.Linq; using System.Text; namespace baseInstrument.instruments class M8020A : BERT private string m_PG_channel = "'M1.DataOut1'"; private string m_ED_channel = "'M1.DataIn1'"; private string m_system = "'M1.ClkGen'"; double m_ED_clk = 16.0e9; double m_PG_clk = 16.0e9; double m_prevBER = 0.0;...

  • Page 62: Sj Example

    Programming Examples SJ Example N4903B SJ Example #region SJ public override bool getSJEnabled() // SOUR8:SIN? if ((int.Parse(this.Query(":SOUR8:SIN?"))) == 1) return true; else return false; public override double getSJFreq() // SOUR8:SIN:FREQ? return double.Parse(this.Query(":SOUR8:SIN:FREQ?")); public override double getSJFreqMax() // SOUR8:SIN:FREQ? MAX return double.Parse(this.Query(":SOUR8:SIN:FREQ? MAX")); public override double getSJFreqMin() // SOUR8:PER:FREQ? MIN return double.Parse(this.Query(":SOUR8:SIN:FREQ? MIN"));...
  • Page 63 Programming Examples public override List<string> setSJFreq(double SJFreq) // SOUR8:SIN:FREQ string strValue = ""; if ((this.getSJFreqMax() > SJFreq) && (this.getSJFreqMin() <= SJFreq)) strValue = SJFreq.ToString(); else strValue = this.getSJFreq().ToString(); return this.Send(":SOUR8:SIN:FREQ " + strValue); public override double getSJAmp() // SOUR8:SIN:LEV? return double.Parse(this.Query(":SOUR8:SIN:LEV?")); public override double getSJAmpMax() // SOUR8:SIN:LEV? MAX return double.Parse(this.Query(":SOUR8:SIN:LEV? MAX"));...

  • Page 64: M8020A Sj Example

    Programming Examples M8020A SJ Example #region SJ - implemented for M8020A public override bool getSJEnabled() // M8020A string str = ""; str = this.Query(":SOUR:JITT:LFR:PER:STAT? " + m_PG_channel); if (str.IndexOf("1") != -1) return true; else return false; public override double getSJFreq() // M8020A string retString = "";...
  • Page 65 Programming Examples public override double getSJFreqMin() // M8020A string retString = ""; double val = 0.0; retString = this.Query(":SOUR:JITT:LFR:PER:FREQ? " + m_PG_channel + ",MIN"); val = double.Parse(retString); return val; public override List<string> setSJEnabled(bool b) // M8020A string strValue = ""; if (b) strValue = "ON";...
  • Page 66 Programming Examples public override double getSJAmp() // M8020A string retString = ""; string unit = ""; double val = 0.0; unit = this.Query(":SOUR:JITT:LFR:UNIT? " + m_PG_channel); this.Send(":SOUR:JITT:LFR:UNIT " + m_PG_channel + ",UINT"); retString = this.Query(":SOUR:JITT:LFR:PER:AMPL? " + m_PG_channel); this.Send(":SOUR:JITT:LFR:UNIT " + m_PG_channel + "," + unit); val = double.Parse(retString);...
  • Page 67 Programming Examples public override double getSJAmpMin() // M8020A string retString = ""; string unit = ""; double val = 0.0; unit = this.Query(":SOUR:JITT:LFR:UNIT? " + m_PG_channel); this.Send(":SOUR:JITT:LFR:UNIT " + m_PG_channel + ",UINT"); retString = this.Query(":SOUR:JITT:LFR:PER:AMPL? " + m_PG_channel + ",MIN"); this.Send(":SOUR:JITT:LFR:UNIT "...

  • Page 68: Pj Example

    Programming Examples PJ Example N4903B PJ Example #region PJ public override bool getPJEnabled() // SOUR8:PER? if ((int.Parse(this.Query(":SOUR8:PER?"))) == 1) return true; else return false; public override double getPJFreq() // SOUR8:PER:FREQ? return double.Parse(this.Query(":SOUR8:PER:FREQ?")); public override double getPJFreqMax() // SOUR8:PER:FREQ? MIN MAX return double.Parse(this.Query(":SOUR8:PER:FREQ? MAX"));...
  • Page 69 Programming Examples public override List<string> setPJFreq(double PJFreq) // SOUR8:PER:FREQ string strValue = ""; if ((this.getPJFreqMax() > PJFreq) && (this.getPJFreqMin() <= PJFreq)) strValue = PJFreq.ToString(); else if (this.getPJFreqMax() < PJFreq) strValue = this.getPJFreqMax().ToString(); else if (this.getPJFreqMin() > PJFreq) strValue = this.getPJFreqMin().ToString(); else strValue = this.getPJFreq().ToString();...

  • Page 70: M8020A Pj Example

    Programming Examples M8020A PJ Example #region PJ - as PJ1 implemented for M8020A public override bool getPJEnabled() // M80820A - checked string str = ""; str = this.Query(":SOUR:JITT:HFR:PER1:STAT? " + m_PG_channel); if (str.IndexOf("1") != -1) return true; else return false; public override double getPJFreq() // M8020A - checked string retString = "";...
  • Page 71 Programming Examples public override double getPJFreqMin() // M8020A - checked string retString = ""; double val = 0.0; retString = this.Query(":SOUR:JITT:HFR:PER1:FREQ? " + m_PG_channel + ",MIN"); val = double.Parse(retString); return val; public override List<string> setPJEnabled(bool b) // M8020A - checked string strValue = "";...
  • Page 72 Programming Examples public override double getPJAmp() // M8020A - checked string retString = ""; string unit = ""; double val = 0.0; unit = this.Query(":SOUR:JITT:HFR:UNIT? " + m_PG_channel); this.Send(":SOUR:JITT:HFR:UNIT " + m_PG_channel + ",UINT"); retString = this.Query(":SOUR:JITT:HFR:PER1:AMPL? " + m_PG_channel); this.Send(":SOUR:JITT:HFR:UNIT "...
  • Page 73 Programming Examples public override List<string> setPJAmp(double PJAmp) // M8020A - checked string strValue = ""; string unit = ""; double amp = 0.0; if (m_PG_channel == "'MUX'") PJAmp /= 2.0; if ((this.getPJAmpMax() > PJAmp) && (this.getPJAmpMin() <= PJAmp)) amp = PJAmp; else amp = this.getPJAmp();...

  • Page 74: Sampling Point Alignment Example

    Programming Examples Sampling Point Alignment Example N4903B Sampling Point Alignment Example public bool checkN900() return m_N4900; # region Sampling Point Alignment public override string autoAlign() string result = ""; this.Send(":SENS1:EYE:ALIGN:AUTO 1"); this.opc(); result = this.Query(":SENS1:EYE:ALIGN:AUTO?"); } while ((result != "CS_ABORTED") && (result != "CS_FAILED") && (result != "CS_SUCCESSFUL")); return result;...
  • Page 75 Programming Examples public override List<string> sync() return this.Send(":SENS1:SYNC 1"); # endregion #region sampling point public override List<string> setSamplingPointDelay(double x) return this.Send(":INP1:DEL " + x.ToString()); public override double getSamplingPointDelay() string str = ""; double delay = 0.0; str = this.Query(":INP1:DEL?"); delay = double.Parse(str); return delay;...

  • Page 76: M8020A Sampling Point Alignment Example

    Programming Examples M8020A Sampling Point Alignment Example public override string autoAlign() string result = ""; * do result = this.Query(":STATus:OPERation:RUN:EVENt?"); while ((int.Parse(result) % 2) == 0); this.Send(":INP:ALIG:EYE:AUTO " + m_ED_channel); this.opc(); result = this.Query(":INP:ALIG:EYE:RES:DEL? " + m_ED_channel); } while (result == ""); return result;...
  • Page 77 Programming Examples public override string thresholdCenter() string result = ""; this.Send(":INP:ALIG:EYE:ACEN " + m_ED_channel); this.opc(); result = this.Query(":INP:ALIG:EYE:RES:THR? " + m_ED_channel); } while (result == ""); return result; public override List<string> sync() return this.Send(":DATA:SYNC " + m_ED_channel); # endregion #region sampling point - implemented for M8020A public override List<string>...

  • Page 78: Ber Example

    Programming Examples BER Example N4903B BER Example # region ber private double m_N4900_BitCount = 0.0; private double m_N4900_ErrorCount = 0.0; public override List<string> resetBERCounter() m_N4900_BitCount = 0.0; m_N4900_ErrorCount = 0.0; return this.startBERAcc(); public override List<string> setBERCounterResults() this.stopBERAcc(); this.startBERAcc(); double errors = 0.0; double bits = 0.0;...

  • Page 79: M8020A Ber Example

    Programming Examples M8020A BER Example private double m_prevAccBER_M8020 = 0.0; private double m_prevAccBitCount_M8020 = 0.0; private double m_prevAccErrorCount_M8020 = 0.0; public override List<string> startBERAcc() // M8020A List<string> errorStr = new List<string>(); errorStr = this.ErrorQ(); return errorStr; public override List<string> stopBERAcc() // M8020A - error counters can't be stopped yet List<string>...
  • Page 80 Programming Examples public override double getInstantaneousBER() // M8020A double accumulatedBER = 0.0; List<double> result = new List<double>(); result = this.getBERAccResults(); accumulatedBER = result[2]; return accumulatedBER; public override List<string> setBERCounterResults() // M8020A List<double> berResults = new List<double>(); List<double> bitCounter = new List<double>(); double bitCount = 0.0;...
  • Page 81 Programming Examples resultStr = this.Query(":FETC:BCO? " + m_ED_channel); // timestamp index = resultStr.IndexOf(","); valStr = resultStr.Substring(1, index - 1); timeStamp = double.Parse(valStr); resultStr = resultStr.Substring(index + 1, resultStr.Length - index - 1); // identifier index = resultStr.IndexOf(","); valStr = resultStr.Substring(0, index); identifier = valStr;...
  • Page 82 Programming Examples If the M8070A software is running on Windows 8 or 8.1, the VXI-11 NOTE protocol is not supported. Example: “SCPI Access (VXI-11): TCPIP0::localhost::inst0::INSTR” does not work on Windows 8 or 8.1. In this case, the HiSLIP protocol should be used as shown below: “SCPI Access (HiSLIP): TCPIP0::localhost::hislip0::INSTR”...

  • Page 83: M8070A Jitter Tolerance Measurement Csv Output

    Programming Examples M8070A Jitter Tolerance Measurement CSV Output The following python script generates the results from all open jitter tolerance measurements to different CSV files. This script can be easily modified to generate the output of the highest-passing point at each jitter modulation frequency value measured.
  • Page 84 Programming Examples # iterate over the data # first element ([0]) is a module identifier, discard # items are then grouped in bundles of six, per header above # we need to insert a comma or LF after each item, depending on pos for idx,data in enumerate(results): if (idx==0): # do nothing, this is the module identifier...
  • Page 85 Keysight M8070A System Software for M8000 Series of BER Test Solutions Programming Guide SCPI Command Language / 86 SCPI Command Language - Introduction / 89 Important Points about SCPI / 93 Sending Commands to the M8020A/M8030A/M8040A / 94 Command Line Arguments / 95 Communication...

  • Page 86: Scpi Command Language

    SCPI Command Language SCPI Command Language - Introduction The Serial BERT is compatible with the standard language for remote control of instruments. Standard Commands for Programmable Instruments (SCPI) is the universal programming language for instrument control. SCPI can be subdivided into the following command sets: •...

  • Page 87: Ieee 488.2 Mandatory Commands

    SCPI Command Language IEEE 488.2 Mandatory Commands In order to comply with the SCPI model as described in IEEE 488.2, the Serial BERT implements certain mandatory commands. Other commands are implemented optionally. For more detail on the IEEE 488.2 mandatory and optional commands, see IEEE Commands - Reference on page 100.

  • Page 88: Data Types

    SCPI Command Language • *OPC? The *OPC? query returns the ASCII character "1" in the Output Queue when the No Operation Pending flag is TRUE. At the same time, it also sets the Message Available (MAV) bit in the Status Byte Register. The *OPC? will not allow further execution of commands or queries until the No Operation Pending flag is true, or receipt of a Device Clear (dcas) message, or a power on.

  • Page 89: Important Points About Scpi

    SCPI Command Language Definite Length Arbitrary Block Data Block data is used when a large quantity of related data is being returned. A definite length block is suitable for sending blocks of 8-bit binary information when the length is known beforehand. An indefinite length block is suitable for sending blocks of 8-bit binary information when the length is not known beforehand or when computing the length beforehand is undesirable.
  • Page 90 SCPI Command Language For more details on the instrument model, see STATus Subsystem page 110. Command Syntax Commands may be up to twelve characters long. A short-form version is also available which has a preferred length of four characters or less. In this document the long-form and short-form versions are shown as a single word with the short-form being shown in upper-case letters.
  • Page 91 SCPI Command Language Query Responses It is possible to interrogate the individual settings and status of a device using query commands. Retrieving data is a two-stage operation. The query command is sent from the controller using the OUTPUT statement and the data is read from the device using the ENTER statement.
  • Page 92 SCPI Command Language SCPI Command Structure Example The SCPI command structure can be best examined by means of an example. For example, the command to set the pattern generator's output amplitude is: [:SOURce]:VOLTage[:AMPLitude] ‘M1.DataOut1’,1.11 The structure of this command can be illustrated as follows: [:SOURce] This is the top layer of the command structure and identifies the source...

  • Page 93: Sending Commands To The M8020A/M8030A/M8040A

    SCPI Command Language With the optional commands removed: :VOLT ‘M1.DataOut1’,1.11 The long form is the most descriptive form of programming commands in SCPI. Sending Commands to the M8020A/M8030A/M8040A Sending Commands to the M8020A/M8030A/M8040A - Overview A command is invalid and will be rejected if: •...

  • Page 94: Command Line Arguments

    SCPI Command Language Command Line Arguments (See Communication on page 95 for details about /Socket, /Telnet, /Inst, /AutoID, /NoAutoID, /FallBack). Table 19 Command line arguments Argument Description /AutoId Start in auto ID mode (this is the default) [optional] /NoAutoId Do not start in auto ID mode - use communication parameters from command line [optional] /FallBack...

  • Page 95: Communication

    SCPI Command Language Communication Depending on the command line arguments /Socket, /Telnet, /Inst, /AutoID, /NoAutoID, /FallBack, the M8070A software starts several servers to handle SCPI commands. (Refer to the table above.) /Socket, /Telnet, /Inst: If -1, don't start the respective servers “Defaults: Socket port: 5025 (e.g.
  • Page 96 SCPI Command Language Note: Ports may already be in use by Windows or other applications, so they are not available for M8195A. /NoAutoID: Do not automatically select ports and number for the connections, use the values specified with /Socket, /Telnet, /Inst or their respective default values instead.

  • Page 97: Scpi Command Reference

    Keysight M8070A System Software for M8000 Series of BER Test Solutions Programming Guide SCPI Command Reference / 98 Subsystems / 100 IEEE Commands - Reference / 106 SCPI Standard Commands / 107 Miscellaneous Commands / 108 Command Syntax to Find Min/Max Values / 109 Location and Module Mapping - Reference / 110...

  • Page 98: Subsystems

    SCPI Command Reference Subsystems The SCPI commands are divided into subsystems, which reflect the various functionality of the instrument. The following figure shows where the port-related subsystems are located. Table 20 Subsystems Subsystem Description STATus The STATus subsystem reports the current system condition, when an event changes and sets transition filter states to report when a passing event occurs.
  • Page 99 SCPI Command Reference Subsystem Description PLUGin The PLUGin subsystem is a plugin interface for integrating C# assemblies into the M8070A user interface and instrument software. SYSTem The SYSTem subsystem is used for general system functions. DATA The DATA subsystem is used to select patterns, define symbol parameters, define sequence blocks and loops and synchronize the pattern.

  • Page 100: Ieee Commands - Reference

    SCPI Command Reference IEEE Commands - Reference Mandatory Commands The following mandatory IEEE 488.2 commands are implemented: Table 21 IEEE commands Name Description under *CLS *CLS on page 101 *CAL? *CAL? on page 101 *LRN? *LRN? on page 101 *ESE[?] *ESE[?] on page 101 *ESR?
  • Page 101 SCPI Command Reference *CLS Syntax *CLS Description This command clears all status register structures in a device. These registers include: • OPERation Status Register structure • QUEStionable Status Register structure The corresponding enable registers are unaffected. *CAL? Syntax *CAL? Description This command returns calibration data.
  • Page 102 SCPI Command Reference *IDN? Syntax *IDN? Description The IDeNtification query (*IDN?) response semantics are organized into four fields, separated by commas. The field definitions are as follows: Table 22 IDN field definitions Field Value Manufacturer Agilent Technologies Model M80xx Serial number MYxxxxxxxx Firmware level X.x.x.xxx...
  • Page 103 SCPI Command Reference *OPT? Syntax *OPT? Description The *OPT? query returns the installed options for each installed module. If no options are installed, only the model number(s) of the installed module(s) are returned. Example *OPT? (M1-M8041A c08,c16)(M2-M8061A,004,008) *RCL Syntax *RCL Description The *RCL command recalls a predefined read only instrument state setting.
  • Page 104 SCPI Command Reference *SRE[?] Syntax *SRE[?] <NRf> Description The Service Request Enable Command (*SRE) sets the Service Request Enable Register. This acts as a mask on the Status Byte, defining when the instrument can issue a service request. For a service request to be issued, the summary bit in the Status Byte must match the bit in the Service Request Enable Register.
  • Page 105 SCPI Command Reference *WAI Syntax *WAI Description The *WAI commands allows no further execution of commands or queries until the No Operation Pending flag is true, or receipt of a Device Clear (dcas) message, or a power on. The *WAI command can be used for overlapped commands. It stops the program execution until any pending overlapped commands have finished.

  • Page 106: Scpi Standard Commands

    SCPI Command Reference SCPI Standard Commands The following SCPI standard commands are implemented: Table 23 SCPI standard commands Name Description under :SYSTem:ERRor[:NEXT]? :SYSTem:ERRor[:NEXT]? on page 106 :SYSTem:HELP:HEADers? :SYSTem:HELP:HEADers? on page 106 :SYSTem:VERSion? :SYSTem:VERSion? on page 106 :SYSTem:ERRor[:NEXT]? Syntax :SYSTem:ERRor[:NEXT]? Description Queries and at the same time deletes the oldest entry in the error queue.

  • Page 107: Miscellaneous Commands

    SCPI Command Reference Miscellaneous Commands The following miscellaneous commands are implemented: Table 24 Miscellaneous commands Name Description under :TEST:RESults? :TEST:RESults? on page 107 :TEST:RESults? Syntax :TEST:RESults? .Description This command returns the results of self test. Keysight M8070A Programming Guide...

  • Page 108: Command Syntax To Find Min/Max Values

    SCPI Command Reference Command Syntax to Find Min/Max Values The following example illustrates the syntax to find min/max values for any system parameter: In the below example, “Voltage Amplitude” is the parameter for which min/max values are to be found. :SOURce:VOLTage:AMPLitude? Syntax for :SOURce:VOLTage:AMPLitude? ‘identifier’, <MIN/MAX>...

  • Page 109: Location And Module Mapping - Reference

    SCPI Command Reference Location and Module Mapping - Reference The following table lists locations and their respective modules. Table 25 Location wise mapping of modules Location Module Data Out M8041A,M8051A, M8061A, M8062A, M8195A and M8045A Data In M8041A,M8051A, M8061A, M8062A and M8046A System M8041A Clk Gen...

  • Page 110: Status Subsystem

    SCPI Command Reference STATus Subsystem This subsystem has the following SCPI structure: This subsystem has the following commands and subnodes: Table 26 Name Description under Subnodes :STATus:QUEStionable Subnode :QUEStionable on page 111 :STATus:OPERation Subnode :OPERation on page 121 :STATus:INSTrument Subnode INSTrument on page 125 Keysight M8070A Programming Guide...

  • Page 111: Status:questionable Subnode

    SCPI Command Reference :STATus:QUEStionable Subnode This subnode has the following SCPI structure: This subnode has the following commands: Table 27 Name Description under :STATus:QUEStionable:CONDition? :CONDition? on page 113 :STATus:QUEStionable:ENABle[?] :ENABle[?] on page 113 :STATus:QUEStionable[:EVENt]? [:EVENt]? on page 113 Keysight M8070A Programming Guide...
  • Page 112 SCPI Command Reference Name Description under :STATus:QUEStionable:NTRansition[?] :NTRansition[?] on page 114 :STATus:QUEStionable:PTRansition[?] :PTRansition[?] on page 115 :STATus:QUEStionable:INSTrument :INSTrument[?] on page 115 :STATus:QUEStionable:INSTrument:CONDition? :INSTrument:CONDition? on page 116 :STATus:QUEStionable:INSTrument:ENABle[?] :INSTrument:ENABle[?] page 116 :STATus:QUEStionable:INSTrument[:EVENt]? :INSTrument[:EVENt]? page 116 :STATus:QUEStionable:INSTrument:NTRansition :INSTrument:NTRansition[?] on page 116 :STATus:QUEStionable:INSTrument:PTRansition :INSTrument:PTRansition[?] on page 117 :STATus:QUEStionable:PROTection...
  • Page 113 SCPI Command Reference Name Description under :STATus:QUEStionable:SYMBol[:EVENt]? :SYMBol[:EVENt]? page 119 :STATus:QUEStionable:SYMBol:NTRansition[?] :SYMBol:NTRansition[?] on page 119 :STATus:QUEStionable:SYMBol:PTRansition[?] :SYMBol:PTRansition[?] on page 120 :STATus:QUEStionable:CONDition? Syntax :STATus:QUEStionable:CONDition? Description This command query returns the contents of the condition register of the Questionable Status Register structure. :STATus:QUEStionable:ENABle[?] Syntax :STATus:QUEStionable:ENABle <NRf>...
  • Page 114 SCPI Command Reference :STATus:QUEStionable:NTRansition[?] Syntax :STATus:QUEStionable:NTRansition <NRf> :STATus:QUEStionable:NTRansition? Input <NRf>: Set transition filter state. Parameters Description This command sets the transition filter state in the Questionable Status Register structure. The query returns the weighted value of the bits that are set to pass negative transitions in the transition filter. Keysight M8070A Programming Guide...
  • Page 115 SCPI Command Reference :STATus:QUEStionable:PTRansition[?] Syntax :STATus:QUEStionable:PTRansition <NRf> :STATus:QUEStionable:PTRansition? Input <NRf>: Set transition filter state. Parameters Description This command sets the transition filter state in the Questionable Status Register structure. This is the default setting of the instrument. The query returns the weighted value of the bits that are set to pass positive transitions in the transition filter.
  • Page 116 SCPI Command Reference :STATus:QUEStionable:INSTrument:CONDition? Syntax :STATus:QUEStionable:INSTrument:CONDition? Description This command returns the contents of the condition register of the Questionable Status Register (bit 9), which reflects the state of the instrument. :STATus:QUEStionable:INSTrument:ENABle[?] Syntax :STATus:QUEStionable:INSTrument:ENABle <NRf> :STATus:QUEStionable:INSTrument:ENABle? Description This command sets the bits in the event enable register that can generate a summary bit used for the instrument state.
  • Page 117 SCPI Command Reference :STATus:QUEStionable:INSTrument:PTRansition[?] Syntax :STATus:QUEStionable:INSTrument:PTRansition[?] <NRf> Input <NRf>: Set transition filter state. Parameters Description This command sets the transition filter state in the Questionable Status Register structure. The query returns the weighted value of the bits that are set to pass positive transitions in the transition filter. :STATus:QUEStionable:PROTection The summary bit of this register set is reflected in bit 11 of the Questionable Status Register.
  • Page 118 SCPI Command Reference :STATus:QUEStionable:PROTection[:EVENt]? Syntax :STATus:QUEStionable:PROTection[:EVENt]? Description This command queries the contents of the Questionable Status event register. :STATus:QUEStionable:PROTection:NTRansition[?] Syntax :STATus:QUEStionable:PROTection:NTRansition <NRf> :STATus:QUEStionable:PROTection:NTRansition? Input <NRf>: Set transition filter state. Parameters Description This command sets the transition filter state in the Questionable Status Register structure.
  • Page 119 SCPI Command Reference Bit 0 - SymbolAlignmentLoss Indicates whether the error detector(s) has experienced a symbol alignment loss. :STATus:QUEStionable:SYMBol:CONDition? Syntax :STATus:QUEStionable:SYMBol:CONDition? Description This query returns the contents of the condition register of the Questionable Status Register (bit 12) to detect a symbol alignment loss. :STATus:QUEStionable:SYMBol:ENABle[?] Syntax :STATus:QUEStionable:SYMBol:ENABle <NRf>...
  • Page 120 SCPI Command Reference :STATus:QUEStionable:SYMBol:PTRansition[?] Syntax :STATus:QUEStionable:SYMBol:PTRansition <NRf> :STATus:QUEStionable:SYMBol:PTRansition? Input <NRf>: Set transition filter state. Parameters Description This command sets the transition filter state in the Questionable Status Register structure. The query returns the weighted value of the bits that are set to pass positive transitions in the transition filter. Keysight M8070A Programming Guide...

  • Page 121: Status:operation Subnode

    SCPI Command Reference :STATus:OPERation Subnode This subnode has the following SCPI structure: Table 28 Name Description under :STATus:OPERation:CONDition? :CONDition? on page 122 :STATus:OPERation:ENABle[?] :ENABle[?] on page 122 :STATus:OPERation[:EVENt]? [:EVENt]? on page 122 :STATus:OPERation:NTRansition[?] :NTRansition[?] on page 122 :STATus:OPERation:PTRansition[?] :PTRansition[?] on page 123 :STATus:OPERation:RUN :RUN on page 123...
  • Page 122 SCPI Command Reference :STATus:OPERation:CONDition? Syntax :STATus:OPERation:CONDition? Description This query returns the contents of the condition register of the Operation Status Register structure. :STATus:OPERation:ENABle[?] Syntax :STATus:OPERation:ENABle <NRf> :STATus:OPERation:ENABle? Input <NRf>: Set enable mask. Parameters Description This command sets the enable mask in the Operation Status Register structure, which allows true conditions in the event register to be reported in the summary bit.
  • Page 123 SCPI Command Reference :STATus:OPERation:PTRansition[?] Syntax :STATus:OPERation:PTRansition <NRf> :STATus:OPERation:PTRansition? Input <NRf>: Set transition filter state. Parameters Description This command sets the transition filter state in the Operation Status Register structure. This is the default setting of the instrument. The query returns the weighted value of the bits that are set to pass positive transitions in the transition filter.
  • Page 124 SCPI Command Reference :STATus:OPERation:RUN:ENABle[?] Syntax :STATus:OPERation:RUN:ENABle <NRf> :STATus:OPERation:RUN:ENABle? Description This command sets the bits in the event enable register that can generate a summary bit used to determine if the hardware is functioning properly. The query returns the weighted value of the bits that are set in the event enable register.

  • Page 125: Status:instrument Subnode

    SCPI Command Reference :STATus:INSTrument Subnode The :STATus:INSTrument commands return the ‘current’ value/condition of several predefined device states. These commands are a set of SCPI queries which return true (1) or false (0). This subnode has the following SCPI structure: This subnode has the following commands: Table 29 Name Description under...
  • Page 126 SCPI Command Reference :STATus:INSTrument:CLOSs? Syntax :STATus:INSTrument:CLOSs? ‘identifier’ Input ‘identifier’: 'M*.DataIn1' or 'M*.DataIn2' or 'M*.DataOut1' or 'M*.DataOut2' Parameters or ‘M1.System’ Return Range Description This query indicates if the clock has been lost. A true (1) indicates a clock loss. Example :STAT:INST:CLOS? ‘M1.DataIn1’ :STATus:INSTrument:DLOSs? Syntax :STATus:INSTrument:DLOSs? ‘identifier’...
  • Page 127 SCPI Command Reference :STATus:INSTrument:SALoss? Syntax :STATus:INSTrument:SALoss? ‘identifier’ Input ‘identifier’: 'M*.DataIn1' or 'M*.DataIn2' or ‘M1.System’ Parameters Return Range Description This query indicates if the symbol alignment has been lost. A true (1) indicates a symbol alignment loss. Example :STAT:INST:SAL? ‘M1.DataIn1’ :STATus:INSTrument:ERRor? Syntax :STATus:INSTrument:ERRor? ‘identifier’...
  • Page 128 SCPI Command Reference :STATus:INSTrument:RCINput? Syntax :STATus:INSTrument:RCINput? ‘identifier’ Input ‘identifier’: ‘M1.ClkGen’ Parameters Return Range Description This query indicates the input state of the reference clock. Example :STAT:INST:RCIN? ‘M1.ClkGen’ :STATus:INSTrument:RUN? Syntax :STATus:INSTrument:RUN? ‘identifier’ Input ‘identifier’: 'M*.DataIn1' or 'M*.DataIn2' or ‘M1.System’ Parameters Return Range Description This query indicates if the input is operating properly.

  • Page 129: Trigger Subsystem

    SCPI Command Reference TRIGger Subsystem The TRIGger subsystem selects the trigger mode at the TRIG OUT port. This subsystem has the following SCPI structure: Table 30 Name Description under :TRIGger[:SOURce][?] [:SOURce] on page 130 :TRIGger[:SOURce]:FREQuency? [:SOURce]:FREQuency? on page 131 :TRIGger:INTernal[:SOURce][?] :INTernal[:SOURce][?] on page 131 :TRIGger:REFerence[:FREQuency][?]...
  • Page 130 SCPI Command Reference Name Description under :TRIGger:CMULtiplier:FREQuency:DETect :CMULtiplier:FREQuency[?] page 135 :TRIGger:CMULtiplier:FREQuency:DETect :CMULtiplier:FREQuency:DETect page 135 :TRIGger:CMULtiplier:FREQuency:MULTipli :CMULtiplier:FREQuency:MULTipli er[?] er[?] on page 133 :TRIGger:CMULtiplier:FREQuency:DIVider[? :CMULtiplier:FREQuency:DIVider[ on page 134 :TRIGger:CMULtiplier:FREQuency[?] :CMULtiplier:FREQuency[?] page 134 :TRIGger:CMULtiplier:FREQuency:DETect :CMULtiplier:FREQuency:DETect page 135 :TRIGger[:SOURce][?] Syntax :TRIGger[:SOURce] ‘identifier’, INTernal|REFerence|DIRect|CMULtiplier :TRIGger[:SOURce]? ‘identifier’ Input ‘identifier’: M1.ClkGen Parameters...
  • Page 131 SCPI Command Reference :TRIGger[:SOURce]:FREQuency? Syntax :TRIGger[:SOURce]:FREQuency? ‘identifier’ Input ‘identifier’: ‘M1.TrigOut’ Parameters Description This query returns the effective frequency of the trigger out clock signal. This parameter is only active if the subrate clock operating mode is selected. The mentioned frequency value depends upon the system frequency &...
  • Page 132 SCPI Command Reference :TRIGger:REFerence[:FREQuency][?] Syntax :TRIGger:REFerence[:FREQuency] ‘identifier’, <REF10|REF100> :TRIGger:REFerence[:FREQuency]? ‘identifier’ Input ‘identifier’: ‘M1.ClkGen’ Parameters <REF10|REF100>: Set external reference clock to 10 MHz or 100 MHz. Return Range REF10|REF100 Description In the REFerence mode two different expected external reference clocks can be specified: 10 MHz / 100 MHz. This SCPI is applicable for M8041A and M8045A.
  • Page 133 SCPI Command Reference :TRIGger:DIRect[:FREQuency]:DETect Syntax :TRIGger:DIRect[:FREQuency]:DETect ‘identifier’ Input ‘identifier’: ‘M1.ClkGen’ Parameters Description The externally provided clock on the REF CLK IN port is measured once and used as the new system frequency (data rate), as required. This SCPI is applicable for M8041A and M8045A. Example :TRIG:DIR:DET ‘M1.ClkGen’...
  • Page 134 SCPI Command Reference Description This command specifies the external reference clock frequency multiplier. This SCPI is applicable for M8041A and M8045A. Example :TRIG:CMUL:FREQ:MULT ‘M1.ClkGen’,3 :TRIGger:CMULtiplier:FREQuency:DIVider[?] Syntax :TRIGger:CMULtiplier:FREQuency:DIVider ‘identifier’, <NRf> :TRIGger:CMULtiplier:FREQuency:DIVider? ‘identifier’ Input ‘identifier’: ‘M1.ClkGen’ Parameters <NRf>: Specify divider value. Return Range 1 to 63;...
  • Page 135 SCPI Command Reference :TRIGger:CMULtiplier:FREQuency:DETect Syntax TRIGger:CMULtiplier:FREQuency:DETect ‘identifier’ Input ‘identifier’: ‘M1.ClkGen’ Parameters Description The external provided clock at the REF CLK IN port is measured once and will be multiplied/divided for calculating the system frequency (data rate). This SCPI is applicable for M8041A and M8045A. Example :TRIG:CMUL:FREQ:DET ‘M1.ClkGen’...

  • Page 136: Source Subsystem

    SCPI Command Reference Source Subsystem The SOURce subsystem controls output signals (for example, for setting frequency and levels). This subsystem has the following SCPI structure: [:SOURce] :FREQuecy :PERiod[?] :DRATe :MEMoryCONFigure[:VALue][?] :PULSe :VOLTage :JITTer :HFRequency :PERiodic(*)[?] :BUNCorrelate :RANDom :SPECtrally :LFRequency :PERiodic :RSSClocking :SWEep :SSCLocking...

  • Page 137: [:Source]:Pulse Subnode

    SCPI Command Reference This subsystem has the following commands and subnodes: Table 31 Name Description under [:SOURce]:FREQuency[?] :FREQuency[?] on page 137 [:SOURce]:PERiod[?] :PERiod[?] on page 138 [:SOURce]:DRATe[?] :DRATe[?] on page 138 [:SOURce]:MEMory:CONFigure[:VALue][?] :MEMory:CONFigure[:VALue][?] on page 139 Subnodes [:SOURce]:PULSe Subnode :PULse on page 141 [:SOURce]:VOLTage Subnode :VOLTage...
  • Page 138 SCPI Command Reference Description Sets the frequency of the synthesizer in the M8020A/M8030A/M8040A. Acceptable units include kHz, MHz, GHz and exponents (for example, 10E9 is the same as 10 GHz). This SCPI is applicable for M8041A, M8195A, M8062A, M8196A and M8045A.
  • Page 139 SCPI Command Reference Description This command/query sets/gets the data rate. This SCPI is applicable for M8062A. Example :DRAT 'M2.ClkGen', 10e9 [:SOURce]:MEMory:CONFigure[:VALue][?] Syntax [:SOURce]:MEMory:CONFigure ‘identifier’, <SINGle | DUAL | FOUR | RANDom | SINusoidal> [:SOURce]:MEMory:CONFigure? ‘identifier’ Input ‘identifier’: ‘M1’ Parameters SINGle | DUAL | FOUR | RANDom | SINusoidal Case 1 - The following description is applicable when the four channel license has been purchased: •...
  • Page 140 SCPI Command Reference Case 2 - The following description is applicable when the two channel license has been purchased: • SINGle: DataOut1 will be sourced from extended memory and DataOut4 will be sourced from module internal memory. The data rate range in this mode is 256 Mb/s …...
  • Page 141 SCPI Command Reference [:SOURce]:PULSe Subnode This subnode has the following SCPI structure: [:SOURce] :PULSe :FILTer :TYPE[?] :ROFFfactor[?] :DELay[?] :TRANsition :FIXed[?] [:LEADing][?] This subnode has the following commands: Table 32 Name Description under [:SOURce]:PULSe:FILTer:TYPE[?] :PULSe:FILTer:TYPE[?] on page 141 [:SOURce]:PULSe:ROFFfactor[?] :PULSe:ROFFfactor[?] on page 142 [:SOURce]:PULSe:DELay[?] :PULSe:DELay[?] on page 142...
  • Page 142 SCPI Command Reference Return Range GAUS | RCOS Description This command specifies filter type used on the waveform. Depending upon the specific waveform used, the waveform gets properties like transition time or bandwidth limits. This query returns the present setting. This SCPI is applicable for M8196A.
  • Page 143 SCPI Command Reference Description This command sets the time from the start of the period to the first edge of the pulse. Acceptable units include ps, ns and exponents (for example, 25E-9 is the same as 25 ns). This SCPI is applicable for M8041A, M8051A, M8195A, M8062A and M8045A.
  • Page 144 SCPI Command Reference Description Use this command to set/read the transition time of the data output stream. The fundamental units for transition time is seconds. This SCPI is applicable for M8195A. Example :PULS:TRAN 'M1.DataOut2',15e-12 :PULS:TRAN? 'M1.DataOut2' It is not possible to define rise and fall times separately. In other words, NOTE the rise and fall time will be in the same range.
  • Page 145 SCPI Command Reference [:SOURce]:VOLTage Subnode This subnode has the following SCPI structure: This subnode has the following commands: Table 33 Name Description under [:SOURce]:VOLTage[:AMPLitude][?] [:AMPLitude][?] page 146 [:SOURce]:VOLTage:OFFSet[?] :OFFSet[?] on page 146 [:SOURce]:VOLTage:HIGH[?] :HIGH[?] on page 147 [:SOURce]:VOLTage:LOW[?] :LOW[?] on page 147 [:SOURce]:VOLTage:RANGe[:SELect][?] :RANGe[:SELect][?] page 148...
  • Page 146 SCPI Command Reference [:SOURce]:VOLTage[:AMPLitude][?] Syntax [:SOURce]:VOLTage[:AMPLitude] ‘identifier’, <NRf> [:SOURce]:VOLTage[:AMPLitude]? ‘identifier’ Input ‘identifier’: 'M1.ClkOut', 'M1.TrigOut', 'M1.SysOutA', 'M1.SysOutB', Parameters 'M*.DataOut1', 'M*.DataOut2', 'M*.DataOut3', 'M*.DataOut4', ‘M*.DataOut’, or 'M*.CtrlOutA' <NRf>: Set peak to peak voltage amplitude. Return Range <NRf> Description This command sets the peak to peak value of an output signal in Volts addressed by an identifier.
  • Page 147 SCPI Command Reference [:SOURce]:VOLTage:HIGH[?] Syntax [:SOURce]:VOLTage:HIGH ‘identifier’, <NRf> [:SOURce]:VOLTage:HIGH? ‘identifier’ Input ‘identifier’: 'M1.ClkOut', 'M1.TrigOut', 'M1.SysOutA', 'M1.SysOutB', Parameters 'M*.DataOut1', 'M*.DataOut2', 'M*.DataOut3', 'M*.DataOut4', ‘M*.DataOut’, or 'M*.CtrlOutA' <NRf>: Set upper voltage level. Return Range <NRf> Description This command sets the upper voltage level of an output signal in Volts addressed by an identifier.
  • Page 148 SCPI Command Reference [:SOURce]:VOLTage:RANGe[:SELect][?] Syntax [:SOURce]:VOLTage:RANGE[:SELect] ‘identifier’, <R1|R2|R3|R4|R5|R6|R7|R8> [:SOURce]:VOLTage:RANGE[:SELect]? ‘identifier’ Input ‘identifier’: 'M*.DataOut1', 'M*.DataOut2', or 'M*.DataOut' Parameters <R1|R2|R3|R4|R5|R6|R7|R8>: Select amplitude ranges. Return Range R1|R2|R3|R4|R5|R6|R7|R8 Description Amplitude ranges guarantee a glitch free change of the amplitude value within a specified range. The upper and lower limits of these ranges are specified in the data sheet.
  • Page 149 SCPI Command Reference [:SOURce]:JITTer Subnode This subnode has the following SCPI structure: [:SOURce] :JITTer [:GLOBal] [:STATe][?] :CONFigure [:DELay][?] :HMODe[?] :HFRequency … :LFRequency … This subnode has the following commands: Table 34 Name Description under [:SOURce]:JITTer[:GLOBal][:STATe][?] [:GLOBal][:STATe][?] page 150 [:SOURce]:JITTer:CONFigure[:DELay][?] :CONFigure[:DELay][?] page 150 [:SOURce]:JITTer:CONFigure:HMODe[?] :CONFigure:HMODe[?]...
  • Page 150 SCPI Command Reference [:SOURce]:JITTer[:GLOBal][:STATe][?] Syntax [:SOURce]:JITTer[:GLOBal][:STATe] ‘identifier’, <ON|OFF|1|0> [:SOURce]:JITTer[:GLOBal][:STATe]? ‘identifier’ Input ‘identifier’: 'M1.System' Parameters <ON|OFF|1|0>: Enable/disable global state. Return Range Description This command enables or disables global jitter. It is a global SCPI; working for all modules. Example :JITT:STAT ‘M1.System’, off [:SOURce]:JITTer:CONFigure[:DELay][?] Syntax [:SOURce]:JITTer:CONFigure[:DELay] ‘identifier’, <NRf>...
  • Page 151 SCPI Command Reference Description Sets the High Jitter Injection Mode of the corresponding output. This SCPI is applicable for M8062A. Example JITT:CONF:HMOD 'M2.DataOut', OFF Keysight M8070A Programming Guide...

  • Page 152: [:Source]:Jitter:hfrequency:buncorrelate Subnode

    SCPI Command Reference [:SOURce]:JITTer:HFRequency Subnode This subnode has the following SCPI structure: This subnode has the following commands: Table 35 Name Description under [:SOURce]:JITTer:HFRequency:UNIT[?] :UNIT[?] page 153 [:SOURce]:JITTer:HFRequency:EXTernal[:S :EXTernal[:STATe][?] TATe][?] on page 153 [:SOURce]:JITTer:HFRequency:PMMode[?] :PMMode[?] on page 154 [:SOURce]:JITTer:HFRequency:PERiodic(*)[: :PERiodic(*)[?] STATe][?] on page 155 [:SOURce]:JITTer:HFRequency:BUNCorrela...

  • Page 153: [:Source]:Jitter:hfrequency:random Subnode

    SCPI Command Reference Name Description under [:SOURce]:JITTer:HFRequency:RANDom :RANDom Subnode on page 162 [:SOURce]:JITTer:HFRequency:SPECtrally :SPECtrally Subnode on page 166 [:SOURce]:JITTer:HFRequency:UNIT[?] Syntax [:SOURce]:JITTer:HFRequency:UNIT ‘identifier’, <UINTerval|TIME> [:SOURce]:JITTer:HFRequency:UNIT? ‘identifier’ Input ‘identifier’: 'M*.DataOut1', 'M*.DataOut2', or 'M*.DataOut' Parameters <UINTerval|TIME>: Specify jitter parameter units. Return Range UINT|TIME Description Specifies whether the jitter parameters are to be specified/returned in seconds (TIME) or unit intervals (UINTerval).
  • Page 154 SCPI Command Reference [:SOURce]:JITTer:HFRequency:PMMode[?] Syntax [:SOURce]:JITTer:HFRequency:PMMode ‘identifier’, <UI|TIME> [:SOURce]:JITTer:HFRequency:PMMode? ‘identifier’ Input ‘identifier’: 'M*.DataOut1' or 'M*.DataOut2' Parameters <UI|TIME>: Specify unit interval or time. Return Range UI|TIME Description The internal delay line is optimized for either ‘UI’ (1UI; the maximum of the delay line is not used) or for ‘TIME’...
  • Page 155 SCPI Command Reference [:SOURce]:JITTer:HFRequency:PERiodic Subnode This subnode has the following SCPI structure: This subnode has the following commands: Table 36 Name Description under [:SOURce]:JITTer:HFRequency:PERiodic(*)[: [:STATe][?] STATe][?] on page 155 [:SOURce]:JITTer:HFRequency:PERiodic(*): :AMPLitude[?] AMPLitude[?] on page 156 URce]:JITTer:HFRequency:PERiodic(*):FRE :FREQuency[?] Quency[?] on page 157 [:SOURce]:JITTer:HFRequency:PERiodic(*)[:STATe][?] Syntax [:SOURce]:JITTer:HFRequency:PERiodic(*)[:STATe] ‘identifier’,...
  • Page 156 SCPI Command Reference The “(*)” suffix specifies which of the two periodic sources (1 or 2) for the specified channel to use. If a suffix is not specified, the suffix 1 is assumed. This SCPI is applicable for M8041A, M8051A, M8061A, M8062A and M8045A.
  • Page 157 SCPI Command Reference URce]:JITTer:HFRequency:PERiodic(*):FREQuency[?] Syntax [:SOURce]:JITTer:HFRequency:PERiodic(*):FREQuency ‘identifier’, <NRf> [:SOURce]:JITTer:HFRequency:PERiodic(*):FREQuency? ‘identifier’ Input ‘identifier’: 'M*.DataOut1' or 'M*.DataOut2', or 'M*.DataOut' Parameters <NRf>: Set periodic jitter frequency. Return Range 1 kHz to 500 MHz Description This command sets the frequency of the periodic jitter for the specified output.
  • Page 158 SCPI Command Reference [:SOURce]:JITTer:HFRequency:BUNCorrelate Subnode This subnode has the following SCPI structure: [:SOURce] :JITTer :HFRequency :BUNCorrelate [:STATe][?] :AMPLitude[?] :DRATe[?] :FILTer [:SELect][?] :PRBSequence [:SELect][?] This subnode has the following commands: Table 37 Name Description under [:SOURce]:JITTer:HFRequency:BUNCorrela [:STATe][?] te[:STATe][?] on page 159 [:SOURce]:JITTer:HFRequency:BUNCorrela :AMPLitude[?] te:AMPLitude[?]...
  • Page 159 SCPI Command Reference [:SOURce]:JITTer:HFRequency:BUNCorrelate[:STATe][?] Syntax [:SOURce]:JITTer:HFRequency:BUNCorrelate[:STATe] ‘identifier’ <ON|OFF|1|0> [:SOURce]:JITTer:HFRequency:BUNCorrelate[:STATe]? ‘identifier’ Input ‘identifier’: 'M*.DataOut1', 'M*.DataOut2', ‘M1.ClkOut’, or 'M*.DataOut' Parameters <ON|OFF|1|0>: Enable/disable bounded uncorrelated jitter. Return Range Description Enables/disables the generation of bounded uncorrelated jitter at the specified output. This SCPI is applicable for M8041A, M8051A, M8061A, M8062A and M8045A.
  • Page 160 SCPI Command Reference [:SOURce]:JITTer:HFRequency:BUNCorrelate:DRATe[?] Syntax [:SOURce]:JITTer:HFRequency:BUNCorrelate:DRATe ‘identifier’ <RATE625|RATE1250|RATE2500> [:SOURce]:JITTer:HFRequency:BUNCorrelate:DRATe? ‘identifier’ Input ‘identifier’: 'M*.DataOut1', 'M*.DataOut2', or 'M*.DataOut' Parameters <RATE625|RATE1250|RATE2500>: Set the bounded uncorrelated PRBS data rate. Return Range RATE625|RATE1250|RATE2500 Description This command sets the bounded uncorrelated PRBS data rate to 625 MBps, 1250 MBps, or 2500 MBps.
  • Page 161 SCPI Command Reference [:SOURce]:JITTer:HFRequency:BUNCorrelate:PRBSequence[:SELect][?] Syntax [:SOURce]:JITTer:HFRequency:BUNCorrelate:PRBSequence[:SELect] ‘identifier’, <PRBS7|PRBS8|PRBS9|PRBS10|PRBS11|PRBS15|PRBS23|PRBS31 [:SOURce]:JITTer:HFRequency:BUNCorrelate:PRBSequence[:SELect]? ‘identifier’ Input ‘identifier’: 'M*.DataOut1', 'M*.DataOut2', or 'M*.DataOut’ Parameters <PRBS7|PRBS8|PRBS9|PRBS10|PRBS11|PRBS15|PRBS23|PRBS31>: Select the PRBS polynomial. Return Range PRBS7|PRBS8|PRBS9|PRBS10|PRBS11|PRBS15|PRBS23|PRBS31 Description This command selects polynomial of the PRBS for bounded uncorrelated jitter source. This query returns the current setting. This SCPI is applicable for M8041A, M8051A, M8061A, M8062A and M8045A.
  • Page 162 SCPI Command Reference [:SOURce]:JITTer:HFRequency:RANDom Subnode This subnode has the following SCPI structure: [:SOURce] :JITTer :HFRequency :RANDom [:STATe][?] :AMPLitude [?] :FILTer [:LPASs][?] :VALue[?] :HPASs[?] :VALue[?] This subnode has the following commands: Table 38 Name Description under [:SOURce]:JITTer:HFRequency:RANDom[:S [:STATe][?] TATe][?] on page 163 [:SOURce]:JITTer:HFRequency:RANDom:A :AMPLitude[?] MPLitude[?]...
  • Page 163 SCPI Command Reference [:SOURce]:JITTer:HFRequency:RANDom[:STATe][?] Syntax [:SOURce]:JITTer:HFRequency:RANDom[:STATe] ‘identifier’ <ON|OFF|1|0> [:SOURce]:JITTer:HFRequency:RANDom[:STATe]? ‘identifier’ Input ‘identifier’: 'M*.DataOut1', 'M*.DataOut2', ‘M1.ClkOut’, or 'M*.DataOut' Parameters <ON|OFF|1|0>: Enable/disable random jitter source. Return Range Description This command enables/disables the generation of random jitter. This SCPI is applicable for M8041A, M8051A, M8061A, M8062A and M8045A.
  • Page 164 SCPI Command Reference Input ‘identifier’: 'M*.DataOut1', 'M*.DataOut2', or ‘M*.DataOut’ Parameters <OFF|LP100|LP500>: Enable/disable low-pass filter. Return Range OFF|LP100|LP500 Description This command enables/disables the low-pass filter for random jitter. LP100 enables a 100 MHz low-pass filter; LP500 enables a 500 MHz low-pass filter. This query returns the current settings.
  • Page 165 SCPI Command Reference Input ‘identifier’: 'M*.DataOut1' or 'M*.DataOut2', or ‘M*.DataOut’ Parameters <OFF|HP10>: Enable/disable high-pass filter. Return Range OFF|HP10 Description This command enables/disables the high-pass filter for random jitter. HP10 enables a 10 MHz high-pass filter. This query returns the current settings. This SCPI is applicable for M8041A, M8051A, M8061A, M8062A and M8045A.
  • Page 166 SCPI Command Reference [:SOURce]:JITTer:HFRequency:SPECtrally Subnode Spectrally distributed random jitter is composed of two jitter sources: low frequency jitter and high frequency jitter. It is characterized by the amplitudes of the low and the high frequency jitter part. This subnode has the following SCPI structure: This subnode has the following commands: Table 39 Name...
  • Page 167 SCPI Command Reference [:SOURce]:JITTer:HFRequency:SPECtrally[:STATe][?] Syntax [:SOURce]:JITTer:HFRequency:SPECtrally[:STATe] ‘identifier’ <ON|OFF|1|0> [:SOURce]:JITTer:HFRequency:SPECtrally[:STATe]? ‘identifier’ Input ‘identifier’: 'M*.DataOut1', 'M*.DataOut2', ‘M1.ClkOut’, or ‘M*.DataOut’ Parameters <ON|OFF|1|0>: Enable/disable spectrally distributed jitter. Return Range Description This command enables/disables the generation of spectrally distributed random jitter. This SCPI is applicable for M8041A, M8051A, M8061A and M8062A. Example :JITT:HFR:SPEC ‘M2.DataOut2’, off [:SOURce]:JITTer:HFRequency:SPECtrally:AMPLitude(*)[?]...
  • Page 168 SCPI Command Reference [:SOURce]:JITTer:HFRequency:SPECtrally:FILTer[:LPASs][:STATe][?] Syntax [:SOURce]:JITTer:HFRequency:SPECtrally:FILTer[:LPASs] [:STATe] ‘identifier’ <ON|OFF|1|0> [:SOURce]:JITTer:HFRequency:SPECtrally:FILTer[:LPASs] [:STATe]? ‘identifier’ Input ‘identifier’: 'M*.DataOut1' or 'M*.DataOut2' Parameters <ON|OFF|1|0>: Enable/disable low-pass filter. Return Range Description Enables/disables the 100 MHz low-pass filter for spectrally distributed random jitter. This SCPI is applicable for M8041A, M8051A, M8061A and M8062A. Example :JITT:HFR:SPEC:FILT ‘M2.DataOut2’, off Keysight M8070A Programming Guide...

  • Page 169: [:Source]:Jitter:lfrequency Subnode

    SCPI Command Reference [:SOURce]:JITTer:LFRequency Subnode This subnode has the following SCPI structure: This subnode has the following commands: Table 40 Name Description under [:SOURce]:JITTer:LFRequency:UNIT[?] :UNIT[?] page 170 [:SOURce]:JITTer:LFRequency:PERiodic :PERiodic Subnode on page 171 [:SOURce]:JITTer:LFRequency:RSSClocking :RSSClocking Subnode on page 173 Keysight M8070A Programming Guide...
  • Page 170 SCPI Command Reference [:SOURce]:JITTer:LFRequency:UNIT[?] Syntax [:SOURce]:JITTer:LFRequency:UNIT ‘identifier’, <UINTerval|TIME> [:SOURce]:JITTer:LFRequency:UNIT? ‘identifier’ Input ‘identifier’: 'M1.ClkOut', 'M*.DataOut1', 'M*.DataOut2', or 'M*.DataOut' Parameters <UINTerval|TIME>: Specify jitter parameter units. Return Range UINT|TIME Description Specifies whether the jitter parameters are to be specified/returned in seconds (TIME) or unit intervals (UINTerval). This SCPI is applicable for M8041A, M8051A, M8061A, M8062A and M8045A.
  • Page 171 SCPI Command Reference [:SOURce]:JITTer:LFRequency:PERiodic Subnode This subnode has the following SCPI structure: This subnode has the following commands: Table 41 Name Description under [:SOURce]:JITTer:LFRequency:PERiodic[:ST [:STATe][?] ATe][?] on page 171 [:SOURce]:JITTer:LFRequency:PERiodic:AM :AMPLitude[?] PLitude[?] on page 172 [:SOURce]:JITTer:LFRequency:PERiodic:FR :FREQuency[?] EQuency[?] on page 172 [:SOURce]:JITTer:LFRequency:PERiodic[:STATe][?] Syntax [:SOURce]:JITTer:LFRequency:PERiodic[:STATe] ‘identifier’, <ON|OFF|1|0>...
  • Page 172 SCPI Command Reference Description This command enables/disables the low frequency periodic jitter source. This SCPI is applicable for M8041A, M8051A, M8061A, M8062A and M8045A. Example :JITT:LFR:PER ‘M1.ClkOut’, off [:SOURce]:JITTer:LFRequency:PERiodic:AMPLitude[?] Syntax [:SOURce]:JITTer:LFRequency:PERiodic:AMPLitude ‘identifier’, <NRf> [:SOURce]:JITTer:LFRequency:PERiodic:AMPLitude? ‘identifier’ Input ‘identifier’: 'M*.DataOut1', 'M*.DataOut2', M1.ClkOut’, or ‘M*.DataOut’ Parameters <NRf>: Set periodic low frequency jitter amplitude.

  • Page 173: [:Source]:Jitter:lfrequency:rssclocking Subnode

    SCPI Command Reference [:SOURce]:JITTer:LFRequency:RSSClocking Subnode This subnode has the following SCPI structure: This subnode has the following commands: Table 42 Name Description under [:SOURce]:JITTer:LFRequency:RSSClocking [:STATe][?] [:STATe][?] on page 173 [:SOURce]:JITTer:LFRequency:RSSClocking :AMPLitude[?] :AMPLitude[?] on page 174 [:SOURce]:JITTer:LFRequency:RSSClocking :FREQuency[?] :FREQuency[?] on page 174 [:SOURce]:JITTer:LFRequency:RSSClocking[:STATe][?] Syntax [:SOURce]:JITTer:LFRequency:RSSClocking[:STATe] ‘identifier’,...
  • Page 174 SCPI Command Reference [:SOURce]:JITTer:LFRequency:RSSClocking:AMPLitude[?] Syntax [:SOURce]:JITTer:LFRequency:RSSClocking:AMPLitude ‘identifier’, <NRf> [:SOURce]:JITTer:LFRequency:RSSClocking:AMPLitude? ‘identifier’ Input ‘identifier’: 'M*.DataOut1', 'M*.DataOut2', M1.ClkOut’, or ‘M*.DataOut’ Parameters <NRf>: Set residual spread spectrum clocking amplitude. Return Range Description This command sets the amplitude of the residual spread spectrum clocking (rSSC). The units are set using the [:SOURce]:JITTer:LFRequency:UNIT command.

  • Page 175: [:Source]:Jitter:sweep Subnode

    SCPI Command Reference [:SOURce]:JITTer:SWEep Subnode This subnode has the following SCPI structure: [:SOURce] :JITTer :SWEep [:STATe][?] :FREQuency :STARt[?] :STOP[?] :TIME[?] :STEP :DISTance[?] [:VALue]? :AMPLitude :MODE[?] [:VALue]? :PLOT :INPut? [:VALue]? :DATA :FILE[?] This subnode has the following commands: Table 43 Name Description under [:SOURce]:JITTer:SWEep[:STATe][?] [:STATe][?]...
  • Page 176 SCPI Command Reference Name Description under [:SOURce]:JITTer:SWEep:STEP:[VALue][?] :STEP:[VALue][?] on page 178 [:SOURce]:JITTer:SWEep:STEP:DISTance[?] :STEP:DISTance[?] on page 179 [:SOURce]:JITTer:SWEep:AMPLitude[:VALu :AMPLitude[:VALue]? on page 179 [:SOURce]:JITTer:SWEep:AMPLitude:MOD :AMPLitude:MODE[?] E[?] on page 179 [:SOURce]:JITTer:SWEep:AMPLitude[:VALu :AMPLitude:[VALue]? on page 179 [:SOURce]:JITTer:SWEep:PLOT[:VALue]? :PLOT[:VALue]? page 180 [:SOURce]:JITTer:SWEep:PLOT:INPut? :PLOT:INPut? page 180 [:SOURce]:JITTer:SWEep:DATA:FILE[?] :DATA:FILE[?] page 181...
  • Page 177 SCPI Command Reference [:SOURce]:JITTer:SWEep[:STATe][?] Syntax [:SOURce]:JITTer:SWEep[:STATe] ‘identifier’, <ON|OFF|1|0> [:SOURce]:JITTer:SWEep[:STATe]? ‘identifier’ Input ‘identifier’: 'M*.DataOut1' or 'M*.DataOut2' Parameters <ON|OFF|1|0>: Enable/disable periodic jitter sweep. Return Range Description This command enables/disables the jitter sweep. This SCPI is applicable for M8041A, M8051A and M8045A. Example :JITT:SWE ‘M1.DataOut2’, on [:SOURce]:JITTer:SWEep:FREQuency:STARt[?] Syntax...
  • Page 178 SCPI Command Reference Description This command defines the stop frequency of the jitter sweep. The stop frequency must be higher than the start frequency and the range should be in accordance with the waveform. Acceptable units include Hz, kHz, MHz, GHz and exponents (for example, 1E3 is the same as 1,000 Hz). This SCPI is applicable for M8041A, M8051A and M8045A.
  • Page 179 SCPI Command Reference [:SOURce]:JITTer:SWEep:STEP:DISTance[?] Syntax [:SOURce]:JITTer:SWEep:STEP :DISTance ‘identifier’, <EQUidistant|AUTOmatic> [:SOURce]:JITTer:SWEep:STEP :DISTance? ‘identifier’ Input ‘identifier’: 'M*.DataOut1' or 'M*.DataOut2' Parameters <EQUidistan|AUTOmatic>: Specify log equidistant or frequency steps. Return Range EQU|AUTO Description The command defines whether the frequency steps are log equidistant (EQUidistant) along the periodic jitter curve or a frequency step matches a corner frequency on the jitter curve.
  • Page 180 SCPI Command Reference Input ‘identifier’: 'M*.DataOut1' or 'M*.DataOut2' Parameters <CONStant|VARiable>: Specify constant or user defined jitter level. Return Range CONS|VAR Description The command defines whether a sweep is defined with CONStant jitter level (amplitude) or with the user defined VARiable jitter level (amplitude). This SCPI is applicable for M8041A, M8051A and M8045A.
  • Page 181 SCPI Command Reference [:SOURce]:JITTer:SWEep:DATA:FILE[?] Syntax [:SOURce]:JITTer:SWEep:DATA:FILE ‘identifier’ <“FileName”> [:SOURce]:JITTer:SWEep:DATA:FILE? ‘identifier’ Input ‘identifier’: 'M*.DataOut1' or 'M*.DataOut2' Parameters <“FileName”>: Specify path to a data file. Description Every point of the periodic jitter sweep curve can be specified by a group of 2 value pairs Frequency, JitterLevel, Frequency, JitterLevel, etc.This command specifies the location of the file to be loaded within the workspace.

  • Page 182: [:Source]:Ssclocking Subnode

    SCPI Command Reference [:SOURce]:SSCLocking Subnode Spread Spectrum Clocking (SSCL) is used for reducing the peak electromagnetic radiation. The clock out signal and data out stream are modulated with a repetitive low-frequency waveform. This subnode has the following SCPI structure: [:SOURce] :SSCLocking [:STATe][?] :GLOBal[:STATe][?]...
  • Page 183 SCPI Command Reference [:SOURce]:SSCLocking[:STATe][?] Syntax [:SOURce]:SSCLocking[:STATe] ‘identifier’, <ON|OFF|1|0> [:SOURce]:SSCLocking[:STATe]? ‘identifier’ Input ‘identifier’: 'M1.ClkGen' Parameters <ON|OFF|1|0>: Enable/disable spread spectrum clocking. Return Range Description This command enables/disables spread spectrum clocking (SSC) state. The SSC mode can be only enabled if Global SSC state is activated. This SCPI is applicable for M8041A, M8195A, M8196A and M8045A.
  • Page 184 SCPI Command Reference [:SOURce]:SSCLocking:DEViation[?] Syntax [:SOURce]:SSCLocking:DEViation ‘identifier’, <NRf> [:SOURce]:SSCLocking:DEViation? ‘identifier’ Input ‘identifier’: 'M1.ClkGen' Parameters <NRf>: Set spread spectrum clocking deviation. Return Range 0% to 1% Description This command sets the spread spectrum clocking (SSC) deviation in percent. The effective deviation is ±0.5% (or 1% peak-to-peak). This SCPI is applicable for M8041A, M8195A, M8196A and M8045A.
  • Page 185 SCPI Command Reference Example The below mentioned SCPI command sets the method used to modulate clock frequency and data to ‘DOWN’ for M8041A/M8045A: :SSCL:TYPE ‘M1.ClkGen’, DOWN The below mentioned SCPI command queries the method used to modulate clock frequency and data for M8041A/M8045A: :SSCL:TYPE? ‘M1.ClkGen’...
  • Page 186 SCPI Command Reference This SCPI is applicable for M8041A and M8045A. Example :SSCL:SHAP ‘M1.ClkGen’,“Factory/Sinusoidal.txt” [:SOURce]:SSCLocking:FREQuency[?] Syntax [:SOURce]:SSCLocking:FREQuency ‘identifier’, <NRf> [:SOURce]:SSCLocking:FREQuency? ‘identifier’ Input ‘identifier’: ‘M1.ClkGen’ Parameters <NRf>: Set spread spectrum clocking frequency. Return Range 100 Hz to 200 kHz Description This command sets the spread spectrum clocking (SSC) frequency in hertz.

  • Page 187: [:Source]:Interference Subnode

    SCPI Command Reference [:SOURce]:INTerference Subnode This subnode has the following SCPI structure: [:SOURce] :INTerference [:LEVel] :HFRequency[:SOURce] :LFRequency[:SOURce] :CMODe [:STATe][?] :AMPLitude[?] :SOURce[?] :GAIN[?] :DMODe [:STATe][?] :AMPLitude[?] :SOURce[?] :GAIN[?] :ISYMbol [:STATe][?] :MODE[?] :FREQuency{1:2}[?] :ILOSs{1:2}[?] :PRESet[?] Keysight M8070A Programming Guide...
  • Page 188 SCPI Command Reference This subnode has the following commands: Table 45 Name Description under [:SOURce]:INTerference[:LEVel]:HFRequenc [:LEVel]:HFRequency[:SOURce][?] y[:SOURce][?] on page 189 [:SOURce]:INTerference[:LEVel]:LFRequenc [:LEVel]:LFRequency[:SOURce][?] y[:SOURce][?] on page 189 [:SOURce]:INTerference[:LEVel]:CMODe[:ST [:LEVel]:CMODe[:STATe][?] ATe][?] on page 190 [:SOURce]:INTerference[:LEVel]:CMODe:A [:LEVel]:CMODe:AMPLitude[?] MPLitude[?] on page 190 [:SOURce]:INTerference[:LEVel]:CMODe:SO [:LEVel]:CMODe:SOURce[?] URce[?] on page 191 [:SOURce]:INTerference[:LEVel]:CMODe:GA...

  • Page 189: [:Source]:Interference[:Level]:Hfrequency[:Source][?]

    SCPI Command Reference [:SOURce]:INTerference[:LEVel]:HFRequency[:SOURce][?] Syntax [:SOURce]:INTerference[:LEVel]:HFRequency[:SOURce] ‘identifier’, <NRf> [:SOURce]:INTerference[:LEVel]:HFRequency[:SOURce]? ‘identifier’ Input ‘identifier’: ‘M*.DATAOUT1’ or ‘M*.DataOut2’ Parameters <NRf>: Set frequency of HF generator. Return Range 1 GHz to 6 GHz Description This command sets the frequency of the high frequency generator. Acceptable units include MHz, GHz and exponents (for example, 2E9 is the same as 2 GHz).

  • Page 190: [:Source]:Interference[:Level]:Cmode[:State][?]

    SCPI Command Reference [:SOURce]:INTerference[:LEVel]:CMODe[:STATe][?] Syntax [:SOURce]:INTerference[:LEVel]:CMODe[:STATe] ‘identifier’, <0|1|ON|OFF> [:SOURce]:INTerference[:LEVel]:CMODe[:STATe]? ‘identifier’ Input ‘identifier’: ‘M*.DATAOUT1’, ‘M*.DataOut2’, or ‘M*.DataOut’ Parameters <0|1|ON|OFF>: Turn common mode interference on/off. Return Range Description This command turns common mode interference on/off. This SCPI is applicable for M8041A, M8051A, M8061A and M8062A. Example :INT:CMOD ‘M2.DataOut1’, on [:SOURce]:INTerference[:LEVel]:CMODe:AMPLitude[?]...

  • Page 191: [:Source]:Interference[:Level]:Cmode:source[?]

    SCPI Command Reference [:SOURce]:INTerference[:LEVel]:CMODe:SOURce[?] Syntax [:SOURce]:INTerference[:LEVel]:CMODe:SOURce ‘identifier’, <HFRequency|LFRequency> [:SOURce]:INTerference[:LEVel]:CMODe:SOURce? ‘identifier’ Input ‘identifier’: ‘M*.DATAOUT1’ or ‘M*.DataOut2’ Parameters <HFRequency|LFRequency>: Select HF or LF generator. Return Range HFR|LFR Description This command selects the high frequency or low frequency generator type for common mode interference. This SCPI is applicable for M8041A and M8051A.

  • Page 192: [:Source]:Interference[:Level]:Dmode[:State][?]

    SCPI Command Reference [:SOURce]:INTerference[:LEVel]:DMODe[:STATe][?] Syntax [:SOURce]:INTerference[:LEVel]:DMODe[:STATe] ‘identifier’, <ON|OFF> [:SOURce]:INTerference[:LEVel]:DMODe[:STATe]? ‘identifier’ Input ‘identifier’: ‘M*.DATAOUT’, ‘M*.DATAOUT1’, or ‘M*.DataOut2’ Parameters <ON|OFF>: Turn differential mode interference on/off. Return Range ON|OFF Description This command turns differential mode interference on/off. This SCPI is applicable for M8041A, M8051A, M8061A and M8062A. Example :INT:DMOD ‘M2.DataOut1’, on [:SOURce]:INTerference[:LEVel]:DMODe:AMPLitude[?]...

  • Page 193: [:Source]:Interference[:Level]:Dmode:source[?]

    SCPI Command Reference [:SOURce]:INTerference[:LEVel]:DMODe:SOURce[?] Syntax [:SOURce]:INTerference[:LEVel]:DMODe:SOURce ‘identifier’, <HFRequency|LFRequency> [:SOURce]:INTerference[:LEVel]:DMODe:SOURce? ‘identifier’ Input ‘identifier’: ‘M*.DATAOUT1’ or ‘M*.DataOut2’ Parameters <HFRequency|LFRequency>: Select HF or LF generator. Return Range HFR|LFR Description This command selects the high frequency or low frequency generator type for differential mode interference. This SCPI is applicable for M8041A and M8051A.

  • Page 194: [:Source]:Interference:isymbol:mode[?]

    SCPI Command Reference Description This command enables/disables the inter symbol interference state. This SCPI is applicable for M8041A, M8051A and M8062A. Example :SOUR:INT:ISYM 'M2.DataOut1', ON [:SOURce]:INTerference:ISYMbol:MODE[?] Syntax [:SOURce]:INTerference:ISYMbol:MODE 'Identifier', <PONE | PTWO> [:SOURce]:INTerference:ISYMbol:MODE? 'Identifier' Input Identifier: 'M*.DataOut1', 'M*.DataOut2', or 'M*.DataOut' Parameters Description This command allows the user to adjust inter symbol interface trace via...

  • Page 195: [:Source]:Interference:isymbol:iloss{1:2

    SCPI Command Reference [:SOURce]:INTerference:ISYMbol:ILOSs{1:2}[?] Syntax [:SOURce]:INTerference:ISYMbol:ILOSs1 'Identifier', <NRf> [:SOURce]:INTerference:ISYMbol:ILOSs2 'Identifier', <NRf> [:SOURce]:INTerference:ISYMbol:ILOSs1? 'Identifier' [:SOURce]:INTerference:ISYMbol:ILOSs2? 'Identifier' Input Identifier: 'M*.DataOut', 'M*.DataOut1', or 'M*.DataOut2' Parameters Description This command sets the insertion loss at one or two discrete user definable frequencies, f1 and f2 of the inter symbol interference (ISI) trace. This SCPI is applicable for M8041A, M8051A, or M8062A.
  • Page 196 SCPI Command Reference The following table describes the list of presets for selected standards and traces. Table 46 Preset List for Selected Standards and Traces (For M8041A and M8051A) SCPI Name f1/GHz L1/dB f2/GHz L2/dB PCIe3 Short -3.0 -9.6 PCIe3 Long -5.6 -17.9...
  • Page 197 SCPI Command Reference Table 47 Preset List for Selected Standards and Traces (For M8062A) SCPI Name f1/GHz L1/dB f2/GHz L2/dB CEI-28G-VSR -3.5 CEI-28G-VSR CEI-28G-VSR 100GbE 12.89 -10.25 CEI-28G-VSR 32GFC 14.025 -10.25 M8048A 7.7” -4.4 M8048A 9.4” M8048A 11.1” -1.9 -6.7 M8048A 12.8”...

  • Page 198: [:Source]:Interference:random Subnode

    SCPI Command Reference [:SOURce]:INTerference:RANDom Subnode This subnode has the following SCPI structure: [:SOURce] :INTerference :RANDom :HFRequency[?] :LFRequency[?] :CREStfactor[?] :UNIT[?] This subnode has the following commands: Table 48 Name Description under [:SOURce]:INTerference:RANDom:HFReque [:SOURce]:INTerference::RANDom ncy[?] :HFRequency[?] on page 199 [:SOURce]:INTerference:RANDom:LFReque [:SOURce]:INTerference:RANDom: ncy[?] LFRequency[?] on page 199 [:SOURce]:INTerference:RANDom:CREStfa...
  • Page 199 SCPI Command Reference [:SOURce]:INTerference:RANDom:HFRequency[?] Syntax [:SOURce]:INTerference:RANDom:HFRequency ‘identifier’, <NRf> [:SOURce]:INTerference:RANDom:HFRequency? ‘identifier’ Input ‘identifier’: ‘M*.DATAOUT1’ or ‘M*.DataOut2’ Parameters <NRf>: Set random interference high frequency Description This command sets the random interference high frequency in Hz. This SCPI is applicable for M8195A and M8196A. Example :INT:RAND:HFR ‘M2.DataOut1’, 1.0e9 [:SOURce]:INTerference:RANDom:LFRequency[?]...
  • Page 200 SCPI Command Reference [:SOURce]:INTerference:RANDom:CREStfactor:UNIT[?] Syntax [:SOURce]:INTerference:RANDom:CREStfactor:UNIT[?] ‘identifier’, < LINear | LOGarithmic > [:SOURce]:INTerference:RANDom:CREStfactor:UNIT? ‘identifier’ Input ‘identifier’: ‘M*.DATAOUT1’ or ‘M*.DataOut2’ Parameters < LINear | LOGarithmic > Description This command sets the random interference crest factor unit type. Following unit types are allowed: •...

  • Page 201: [:Source]:Interference:sinusoidal Subnode

    SCPI Command Reference [:SOURce]:INTerference:SINUsoidal Subnode This subnode controls the configuration when AWG is used as sinusoidal interference source. It has the following SCPI structure: [:SOURce] :INTerference :SINusoidal :FRQuency[?] This subnode has the following command: [:SOURce]:INTerference:SINusoidal:FREQuency[?] Syntax [:SOURce]:INTerference:SINusoidal:FREQuency ‘Identifier’, <NRf> [:SOURce]:INTerference:SINusoidal:FREQuency? ‘identifier’ Input ‘identifier’: 'M*.DataOut1' or 'M*.DataOut2' Parameters...

  • Page 202: [:Source]:Configure Subnode

    SCPI Command Reference [:SOURce]:CONFigure Subnode This subnode has the following SCPI structure: This subnode has the following command: [:SOURce]:CONFigure:MINTegration[?] Syntax [:SOURce]:CONFigure:MINTegration ‘identifier’,<NONe|MUX|DMUX|BOTH>[<data-location>[<visa-resource>]] [:SOURce]:CONFigure:MINTegration? ‘identifier’ Input ‘identifier’: ‘M*.MuxMode’ Parameters <NONe|MUX|DMUX|BOTH>: Select mux/demux module. <data-location>: (Optional) Specify location of data module. If omitted or an empty string is specified, the first suitable module is chosen automatically.

  • Page 203: Output Subsystem

    SCPI Command Reference OUTPut Subsystem The OUTPut subsystem controls the output ports of the pattern generator. This subsystem has the following SCPI structure: :OUTPut :GLOBal [:STATe][?] [:STATe][?] :CONFig :SOURce[?] :DRATe? :POLarity[?] :TVOLtage[?] :TCONfig[?] :COUPling[?] :DIVider[?] :FREQuency :DIVider[?] :CALibration :SKEW[?] :EIDLe [:STATe][?] :DATA :XOVer[?]...

  • Page 204: Output:deemphasis Subnode

    SCPI Command Reference This subsystem has the following commands and subnodes: Table 49 Name Description under :OUTPut:GLOBal[:STATe][?] :GLOBal[:STATe][?] on page 205 :OUTPut[:STATe][?] [:STATe][?] on page 205 :OUTPut:CONFig:SOURce[?] :CONFig:SOURce[?] on page 205 :OUTPut:DRATe? :DRATe? on page 206 :OUTPut:POLarity[?] :POLarity[?] on page 206 :OUTPut:TVOLtage[?] :TVOLtage[?] on page 206...
  • Page 205 SCPI Command Reference :OUTPut:GLOBal[:STATe][?] Syntax :OUTPut:GLOBal[:STATe] ‘identifier’, <ON|OFF|1|0> :OUTPut:GLOBal][:STATe]? ‘identifier’ Input ‘identifier’: 'M1.System' Parameters <ON|OFF|1|0>: Enable/disable global state. Return Range Description This command sets global output state to ON or OFF. This command works for all modules, as it is a Global command. Example :OUTP:GLOB ‘M1.System’, off :OUTPut[:STATe][?]...
  • Page 206 SCPI Command Reference Description This command selects the signal source for the instrument’s output. This is only valid for certain clock outputs. This query returns the present state. This SCPI is supported by M8045A. Example :OUTP:CONF:SOUR ‘M1.ClkOut1’,CLE :OUTPut:DRATe? Syntax :OUTPut:DRATe? ‘identifier’ Input ‘identifier’: 'M*.DataOut1', 'M*.DataOut2', 'M*.DataOut', or ‘M1.ClkOut’...
  • Page 207 SCPI Command Reference Input ‘identifier’: 'M1.ClkOut', 'M1.TrigOut', 'M*.DataOut1', 'M*.DataOut2', or Parameters 'M*.DataOut' <NRf>: Specify external termination voltage. Return Range <NRf> Description This command specifies the external termination voltage. The default is 0 V (ground). Acceptable units include mV, V and exponents (for example, 700E-3 is the same as 700 mV).
  • Page 208 SCPI Command Reference Description This command selects DC or AC output coupling. This SCPI is applicable for M8041A, M8051A, M8061A, M8062A and M8045A. Example :OUTP:COUP ‘M1.DataOut1’, DC :OUTPut:DIVider[?] Syntax :OUTPut:DIVider ‘identifier’, <DIV1...DIV640> :OUTPut:DIVider? ‘identifier’ Input ‘identifier’: ‘M1.ClkOut’, ‘M1.ClkOut1’, ‘M1.ClkOut2’ Parameters Specify a divider: DIV1 | DIV2 | DIV4 | DIV8 | DIV10 | DIV16 | DIV20 | DIV24 | DIV30 | DIV32 | DIV40 | DIV48 | DIV50 | DIV60 | DIV64 | DIV66 | DIV80 | DIV96 | DIV100 | DIV120 | DIV128 | DIV132 | DIV160 | DIV192 | DIV200 |...
  • Page 209 SCPI Command Reference :OUTPut:FREQuency:DIVider[?] Syntax :OUTPut:FREQuency:DIVider ‘identifier’, <NRf> :OUTPut:FREQuency:DIVider? ‘identifier’ Input ‘identifier’: 'M*.ClnClkOut’ Parameters Return Range <NRf> Description This command divides the frequency at clean clock out (Cln Clk Out) on an M8062A module. This SCPI is applicable for M8062A. Example :OUTPut:FREQuency:DIVider ‘M2.ClnClkout’, 2 :OUTPut:CALibration:SKEW[?]...
  • Page 210 SCPI Command Reference Return Range OFF|IDLE|EXT Description This command enables/disables the electrical idle feature for the Data Output. The state can be OFF, IDLE or EXTernal. This SCPI is applicable for M8061A and M8062A. Example :OUTP:EIDL ‘M2.DataOut’, EXT :OUTPut:DATA:XOVer[?] Syntax :OUTPut:DATA:XOVer ‘identifier’, <NRf>...
  • Page 211 SCPI Command Reference :OUTPut:DATA:F2Jitter:STATe[?] Syntax :OUTPut:DATA:F2Jitter:STATe ‘identifier’, <ON|OFF|1|0> :OUTPut:DATA:F2JitterSTATe? ‘identifier’ Input ‘identifier’: 'M*.DataOut1', 'M*.DataOut2', or 'M*.DataOut' Parameters Return Range ON|OFF|1|0 Description This command enables/disables f/2 jitter at the output. Enabling this command, causes stop of full clock group (all pattern generator channels and CLK/TRIG).
  • Page 212 SCPI Command Reference :OUTPut:DEEMphasis Subnode The M8070A provides an eight tap de-emphasis signal. Seven of these taps can be specified: two pre-cursors and five post-cursors. The resulting main cursor is calculated. The taps can be programmed remotely in two different ways. Firstly, all the tap values can be set by one command.
  • Page 213 SCPI Command Reference This subnode has the following commands: Table 50 Name Description under :OUTPut:DEEMphasis:UNIT[?] :UNIT[?] on page 214 :OUTPut:DEEMphasis:PRESet[?] :PRESet[?] on page 214 :OUTPut:DEEMphasis:PRESet:ENABle[?] :PRESet:ENABle[?] page 215 :OUTPut:DEEMphasis:SELect:PRESet[?] :SELect:PRESet[?] page 215 :OUTPut:DEEMphasis:PRECursor(*)[?] :PRECursor{1:2}[?] page 217 :OUTPut:DEEMphasis:POSTcursor(*)[?] :POSTcursor{1:5}[?] page 217 :OUTPut:DEEMphasis:CONFigure:SIGN(*)[?] :CONFigure:SIGN[?] on page 218...
  • Page 214 SCPI Command Reference :OUTPut:DEEMphasis:UNIT[?] Syntax :OUTPut:DEEMphasis:UNIT ‘identifier’, <DB|PCT> :OUTPut:DEEMphasis:UNIT? ‘identifier’ Input ‘identifier’: 'M*.DataOut1', 'M*.DataOut2', or 'M*.DataOut' Parameters <DB|PCT>: Select dB or percent as the unit. Return Range DB|PCT Description This command defines the tap value unit: dB or PCT (PerCenT). This command should not be sent in one PM (SCPI - Program Message) with the following de-emphasis commands: •...
  • Page 215 SCPI Command Reference addressed by a register index of 0 up to 30. The values in the list specify the register index and taps in the following order: <RegNr><Pre2>,<Pre1>,<Post1>,<Post2>,< Post3>,< Post4>,< Post5> Supported preset values for M8041A and M8051A are 0 - 30 and for M8061A and M8062A, 0 is the only preset value.
  • Page 216 SCPI Command Reference register. The :PRECursor and :POSTCursor commands change the tap values only in that preselected preset register. There are 31 preset registers available addressed by a register index of 0 up to 30. This command should not be sent in one PM (SCPI - Program Message) with the following de-emphasis commands: •...
  • Page 217 SCPI Command Reference :OUTPut:DEEMphasis:PRECursor(*)[?] Syntax :OUTPut:DEEMphasis:PRECursor(*) ‘identifier’, <NRf> :OUTPut:DEEMphasis:PRECursor(*)? ‘identifier’ Input ‘identifier’: 'M*.DataOut1' or 'M*.DataOut2' Parameters <NRf>: Set selected pre-cursor value. Return Range PRECursor1: -12.04 dB to 12.04 dB | 25% to 400% PRECursor2: -6.02 dB to 6.02 dB | 50% to 200% Description This command programs the pre-cursor value of the currently selected pre-cursor (pre-cursor 1 or pre-cursor 2).
  • Page 218 SCPI Command Reference :OUTPut:DEEMphasis:CONFigure:SIGN(*)[?] Syntax :OUTPut:DEEMphasis:CONFigure:SIGN(*) ‘identifier’, <enum>, <enum>, <enum>, <enum>, <enum>, <enum>, <enum> :OUTPut:DEEMphasis:CONFigure:SIGN(*)? ‘identifier’ Input ‘identifier’: 'M*.DataOut1' or 'M*.DataOut2' Parameters <enum>: Specify positive/negative tap value sign for each tap. Return Range POS|NEG (returned for each tap) Description A list of “POSitive”s and “NEGative”s specify the sign of the corresponding tap.
  • Page 219 SCPI Command Reference :OUTPut:DEEMphasis:CURSor:MAGNitude(0|1|2|3|4|5|6|7)[?] Syntax :OUTPut:DEEMphasis:CURSor:MAGNitude(0|1|2|3|4|5|6|7) 'Identifier',<NRf> :OUTPut:DEEMphasis:CURSor:MAGNitude(0|1|2|3|4|5|6|7)? ‘identifier’ Input ‘identifier’: 'M*.DataOut1' or 'M*.DataOut2' Parameters Return Range <NRf> Description This command sets the cursor magnitude as a signed value. The suffix selects the cursor to be addressed. The number of available cursors depends on the product number.
  • Page 220 SCPI Command Reference :OUTPut:DEEMphasis:CURSor:MAIN:AUTO[?] Syntax :OUTPut:DEEMphasis:CURSor:MAIN:AUTO 'Identifier',<ON|OFF|1|0> :OUTPut:DEEMphasis:CURSor:MAIN:AUTO? ‘identifier’ Input ‘identifier’: 'M*.DataOut1' or 'M*.DataOut2' Parameters Return Range ON|OFF|1|0 Description This command controls whether the main cursor magnitude shall be calculated automatically in order to maintain the overall peak to peak amplitude constant, or whether the main cursor magnitude can be controlled manually.
  • Page 221 SCPI Command Reference :OUTPut:DEEMphasis:CURSor:MAIN:SUFFix? Syntax :OUTPut:DEEMphasis:CURSor:MAIN:SUFFix? 'Identifier' Input ‘identifier’: 'M*.DataOut1' or 'M*.DataOut2' Parameters Return Value Description This query returns the main cursor’s suffix. This SCPI is supported by M8045A. Example :OUTP:DEEM:CURS:MAIN:SUFF? 'M1.DataOut1' :OUTPut:EINSertion Subnode This subnode has the following SCPI structure: This subnode has the following commands: Table 51 Name...
  • Page 222 SCPI Command Reference :OUTPut:EINSertion[:STATe][?] Syntax :OUTPut:EINSertion[:STATe] ‘identifier’, <ON|OFF|1|0> :OUTPut:EINSertion[:STATe]? ‘identifier’ Input ‘identifier’: 'M*.DataOut1', 'M*.DataOut2', or 'M*.DataOut' Parameters <ON|OFF|1|0>: Switch error insertion output on or off. Return Range Description This command switches the error insertion feature on or off for the specified output.
  • Page 223 SCPI Command Reference :OUTPut:EINSertion:MODE[?] Syntax :OUTPut:EINSertion:MODE ‘identifier’, <ERFSpacing|...|SINB> :OUTPut:EINSertion:MODE? ‘identifier’ Input ‘identifier’: 'M*.DataOut1', 'M*.DataOut2', or 'M*.DataOut' Parameters <ERFSpacing|...|SINB>: Specify the error insertion mode. Return Range <ERFSpacing|...|SINB> Description This command is used to specify the error insertion mode as follows: ERFSpacing: Generates errors with a predetermined bit error rate (fixed spacing).
  • Page 224 SCPI Command Reference :OUTPut:EINSertion:DISParity Syntax :OUTPut:EINSertion:DISParity ‘identifier’ Input ‘identifier’: 'M*.DataOut1' or 'M*.DataOut2' Parameters Description This command generates a single disparity error (only valid for 8b/10b operating mode) on the specified output. This SCPI is applicable for M8041A, M8051A and M8045A. Example :OUTP:EINS:DISP ‘M1.DataOut2’...

  • Page 225: Output:trigger Subnode

    SCPI Command Reference :OUTPut:TRIGger Subnode This subnode has the following SCPI structure: This subnode has the following commands: Table 52 Name Description under :OUTPut:TRIGger:MODE[?] :MODE[?] on page 226 :OUTPut:TRIGger:DIVider[?] :DIVider[?] on page 226 Keysight M8070A Programming Guide...
  • Page 226 SCPI Command Reference :OUTPut:TRIGger:MODE[?] Syntax :OUTPut:TRIGger:MODE ‘identifier’, <CLOCk|SEQuencer> :OUTPut:TRIGger:MODE? ‘identifier’ Input ‘identifier’: 'M1.TrigOut' Parameters <CLOCk|SEQuencer>: Set the operating mode of the trigger out. Return Range CLOC|SEQ Description This command sets the operating mode of the trigger out (TRIG OUT) either to subrate clock or sequencer controlled mode. This SCPI is applicable for M8041A and M8045A.

  • Page 227: Output:dembedding Subnode

    SCPI Command Reference :OUTPut:DEMBedding Subnode This subnode has the following SCPI structure: :OUTPut :DEMBedding [:SCABle] [:STATe][?] :SPARameter [:STATe][?] :PROFile[?] :IPORt[?] :OPORt[?] This subnode has the following commands: Table 53 Name Description under :OUTPut:DEMBedding:SCABle:STATe[?] :SCABle:STATe[?] page 228 :OUTPut:DEMBedding:SPARameter:STATe[ SPARameter:STATe[?] on page 228 :OUTPut:DEMBedding:SPARameter:PROFil :SPARameter:PROFile[?] e[?]...
  • Page 228 SCPI Command Reference :OUTPut:DEMBedding:SCABle:STATe[?] Syntax :OUTPut:DEMBedding[:SCABle][:STATe] ‘identifier’, <OFF | ON | 0 | 1> :OUTPut:DEMBedding[:SCABle][:STATe]? ‘identifier’ Input ‘identifier’:'M*.DataOut1’,‘M*.DataOut2’,‘M*.DataOut3’,or ‘M*.DataOut4’ Parameters OFF | ON | 0 | 1: Enables/disables standard cable compensation. Return Range Description This command switches on/off the standard cable compensation on the specified output.
  • Page 229 SCPI Command Reference This SCPI is applicable for M8195A and M8196A. Example :OUTP:DEMB:SPAR:PROF ‘M1.DataOut1’, ”factory/huber_suhner_cable.s2p” :OUTPut:DEMBedding:SPARameter:IPORt[?] Syntax :OUTPut:DEMBedding:SPARameter:IPORt ‘identifier’, <NRf> :OUTPut:DEMBedding:SPARameter:IPORt? ‘identifier’ Input ‘identifier’:'M*.DataOut1’,‘M*.DataOut2’,‘M*.DataOut3’,or ‘M*.DataOut4’ Parameters 1|2|3|4: Return Range 1|2|3|4; depends upon the selected S parameter file. Description This command selects the input port in the S-Parameter profile. The query return the present setting.

  • Page 230: Output:embedding Subnode

    SCPI Command Reference :OUTPut:EMBedding Subnode This subnode has the following SCPI structure: :OUTPut :EMBedding :SPARameter [:STATe][?] :PROFile[?] :IPORt[?] :OPORt[?] This subnode has the following commands: Table 54 Name Description under :OUTPut:EMBedding:SPARameter[:STATe][? :SPARameter[:STATe][?] on page 231 :OUTPut:EMBedding:SPARameter:PROFile[ :SPARameter:PROFile[?] on page 231 :OUTPut:EMBedding:SPARameter:IPORt[?] :SPARameter:IPORt[?] on page 231...
  • Page 231 SCPI Command Reference :OUTPut:EMBedding:SPARameter[:STATe][?] Syntax :OUTPut:EMBedding:SPARameter[:STATe] ‘identifier’, <OFF | ON | 0 | 1> :OUTPut:EMBedding:SPARameter[:STATe]? ‘identifier’ Input ‘identifier’:'M*.DataOut1’,‘M*.DataOut2’,‘M*.DataOut3’,or ‘M*.DataOut4’ Parameters OFF | ON | 0 | 1 Return Range Description This command Switches on/off the compensation via S-parameter file on the specified output.
  • Page 232 SCPI Command Reference This SCPI is applicable for M8195A and M8196A. Example :OUTP:EMB:SPAR:IPOR ‘M1.DataOut1’, 1 :OUTPut:EMBedding:SPARameter:OPORt[?] Syntax :OUTPut:EMBedding:SPARameter:OPORt ‘identifier’, <NRf> :OUTPut:EMBedding:SPARameter:OPORt ‘identifier’ Input ‘identifier’:'M*.DataOut1’,‘M*.DataOut2’,‘M*.DataOut3’,or ‘M*.DataOut4’ Parameters Description This command selects the output port in the S-Parameter profile. The query returns the present setting. This SCPI is applicable for M8195A and M8196A.

  • Page 233: Input Subsystem

    SCPI Command Reference INPut Subsystem The INPut subsystem controls the input ports of the analyzer. This subsystem has the following SCPI structure: :INPut :BRM[?] :DRATe? :DELay[?] :EQUalization [:PRESet][?] :LEVel[?] :POLarity[?] :CMVoltage[?] :DETect :THReshold[?] :TVOLtage[?] :TCONfig[?] :CMODe[?] :COUPling[?] :SENSitivity[?] [:VOLTage] :WINDow[?] [:NRZ]:THReshold[?] :PAM4[:SYMBol] :THReshold(1|2|3)[?]...

  • Page 234: Input:cdr Subnode

    SCPI Command Reference The subsystem has the following commands and subnodes: Table 55 Name Description under :INPut:DATA:BRMode[?] :BRM[?] on page 235 :INPut:DRATe? :DRATe? on page 236 :INPut:DELay[?] :DELay on page 236 :INPut:EQUalization[:PREset][?] :EQUalization[:PRESet] on page 236 :INPut:EQUalization:LEVel[?] :EQUalization:LEVel on page 238 :INPut:POLarity[?] :POLarity on page 238...
  • Page 235 SCPI Command Reference :INPut:DATA:BRMode[?] Syntax :INPut:DATA:BRMode ‘identifier’, < 0 | 1 | ON | OFF> :INPut:DATA:BRMode? ‘identifier’ Input ‘identifier’: 'M*.DataIn1' or 'M*.DataIn2' Parameters Range 0 | 1 | ON | OFF Description This command enables/disables the bit recovery mode. In BRM, the error detector does not expect any specific data.
  • Page 236 SCPI Command Reference :INPut:DRATe? Syntax :INPut:DRATe? ‘identifier’ Input ‘identifier’: 'M*.DataIn1', 'M*.DataIn2' or 'M*.DataIn' Parameters Description This query returns the data rate for the input channel. This SCPI is applicable for M8061A M8062A and M8046A. Example :INP:DRAT? 'M1.DataIn1' :INPut:DELay[?] Syntax :INPut:DELay ‘identifier’, <NRf> :INPut:DELay? ‘identifier’...
  • Page 237 SCPI Command Reference Return Range OFF | P1 | P2 | P3 | P4 | P5 | P6 | P7 | P8 | P9 | P10 Description This command is used to select from the following equalization presets: For M8041A and M8051A: •...
  • Page 238 SCPI Command Reference :INPut:EQUalization:LEVel[?] Syntax :INPut:EQUalization:LEVel 'Identifier', <NRf> :INPut:EQUalization:LEVel? 'Identifier', ‘identifier’: 'M*.DataIn' Input Parameters The specified number has a range from 0 – 15. Return Range 0 – 15 Description This command sets an equalization level in order to compensate the loss characteristic of an incoming pulse.
  • Page 239 SCPI Command Reference Return Range -1.0 V to 2.6 V; The range is dependent on other system parameters. See Command Syntax to Find Min/Max Values on page 108. Description This command is used to measure the common mode voltage of the selected data input by the module itself.
  • Page 240 SCPI Command Reference :INPut:TVOLtage[?] Syntax :INPut:TVOLtage ‘identifier’, <NRf> :INPut:TVOLtage? ‘identifier’ Input ‘identifier’:'M*.DataIn1', 'M*.DataIn2', or 'M2.ElectIdleIn' Parameters <NRf>: Specify receiver input termination voltage. Return Range -1 V to 2.9 V; The range is dependent on other system parameters. See Command Syntax to Find Min/Max Values on page 108.
  • Page 241 SCPI Command Reference :INPut:CMODe[?] Syntax :INPut:CMODe ‘identifier’, <SENormal|SEComplement|DIFFerential|SINGleended> :INPut:CMODe? ‘identifier’ Input ‘identifier’: 'M*.DataIn1', 'M*.DataIn2' or 'M*DataIn' Parameters <SENormal|SEComplement|DIFFerential|SINGleended>: Select compare mode. Return Range SEN|SEC|DIFF|SING Description This command defines the compare mode. This command defines which input (DATA or DATA\) is active. The following options are available: SENormal: Data stream is compared at Normal input;...
  • Page 242 SCPI Command Reference :INPut:COUPling[?] Syntax :INPut:COUPling ‘identifier’, <AC|DC> :INPut:COUPling? ‘identifier’ Input ‘identifier’: 'M*.DataIn1' or 'M*.DataIn2' Parameters <AC|DC>: Select input coupling. Return Range AC|DC Description This command selects DC or AC input coupling. This SCPI is applicable for M8041A and M8051A. Example :INP:COUP ‘M1.DataIn1’, DC :INPut:SENSitivity[?]...
  • Page 243 SCPI Command Reference This SCPI is supported by M8046A. Example :INP:WIND ‘M2.DataIn1’, 0.4 :INPut[:VOLTage][:NRZ]:THReshold[?] Syntax :INPut[:VOLTage][:NRZ]:THReshold ‘identifier’, <NRf> :INPut[:VOLTage][:NRZ]:THReshold? ‘identifier’ Input <identifier>: Any valid data input identifier. M*.DataIn1 or M*.DataIn2 Parameters Description The command specifies the threshold voltage of a RX input connector. This query returns the present setting.
  • Page 244 SCPI Command Reference Threshold Symbol Decides between symbol 0 and symbol 1. Decides between symbol 1 and symbol 2. Decides between symbol 2 and symbol 3. This query returns the present state. This SCPI is applicable for M8046A. It is best practice to configure the 3 decision thresholds in a combined command transaction (see the example) to minimize hardware re-configuration duration.
  • Page 245 SCPI Command Reference :INPut:CDR Subnode This subnode has the following SCPI structure: :INPut :CDR :LO RDer[?] :CTRL[?] [:STATe][?] :AUTO [?] :RELO ck :HIG HTD[?] O PTim ize :FIRSt :TDENsity[?] :LBANdwidth[?] :SECond :TDENsity[?] :LBANdwidth[?] :PEAKing[?] This subnode has the following commands: Table 56 Name Description under...
  • Page 246 SCPI Command Reference Name Description under :INPut:CDR:SECond:TDENsity[?] :SECond:TDENsity[?] on page 251 :INPut:CDR:SECond:LBANdwidth[?] :SECond:LBANd width[?] page 251 :INPut:CDR:SECond:PEAKing[?] :SECond:PEAKing[?] on page 252 Keysight M8070A Programming Guide...
  • Page 247 SCPI Command Reference :INPut:CDR:LORDer[?] Syntax :INPut:CDR:LORDer ‘identifier’, <FIRSt|SECond> :INPut:CDR[:STATe]? ‘identifier’ Input ‘identifier’: 'M*.DataIn1' or 'M*.DataIn2' Parameters <FIRSt|SECond>: Set the loop order of the CDR. Return Range FIRS|SEC Description This command determines the loop order of the CDR. Depending on this setting, defining the behavior of the CDR is done by different parameters.
  • Page 248 SCPI Command Reference :INPut:CDR[:STATe][?] Syntax :INPut:CDR[:STATe] ‘identifier’, <ON|OFF|1|0> :INPut:CDR[:STATe]? ‘identifier’ Input ‘identifier’: 'M*.DataIn1', 'M*.DataIn2' or 'M*DataIn' Parameters <ON|OFF|1|0>: Enable/disable the CDR. Return Range Description This command enables or disables CDR. This SCPI is applicable for M8041A, M8051A and M8046A. Example :INP:CDR ‘M1.DataIn1’, ON :INPut:CDR:AUTO[?] Syntax...
  • Page 249 SCPI Command Reference :INPut:CDR:RELOck Syntax :INPut:CDR:RELOck ‘identifier’ Input ‘identifier’: 'M*.DataIn' Parameters Description This command execute a full CDR relock. This SCPI is applicable for M8062A. Example :INPut:CDR:RELOck ‘M2.DataIn’ :INPut:CDR:HIGHTD[?] Syntax :INPut:CDR:HIGHTD ‘identifier’, <ON|OFF|1|0> :INPut:CDR:HIGHTD? ‘identifier’ Input ‘identifier’: 'M*.DataIn' Parameters <ON|OFF|1|0>: Set the High Transition Density state to ON or OFF. Return Range Description This command sets the High Transition Density state to ON or OFF.
  • Page 250 SCPI Command Reference :INPut:CDR:FIRSt:TDENsity[?] Syntax :INPut:CDR:FIRSt:TDENsity ‘identifier’, <NRf> :INPut:CDR:FIRSt:TDENsity? ‘identifier’ Input ‘identifier’: 'M*.DataIn1' or 'M*.DataIn2' Parameters <NRf>: Set first order transition density. Return Range 25% to 100% Description This command is used to set the first order transition density of the incoming signal from 25% to 100%.
  • Page 251 SCPI Command Reference :INPut:CDR:SECond:TDENsity[?] Syntax :INPut:CDR:SECond:TDENsity ‘identifier’, <NRf> :INPut:CDR:SECond:TDENsity? ‘identifier’ Input ‘identifier’: 'M*.DataIn1' or 'M*.DataIn2' Parameters <NRf>: Set second order transition density. Return Range 25% to 100% Description This command is used to set the second order transition density of the incoming signal from 10% to 100%.
  • Page 252 SCPI Command Reference :INPut:CDR:SECond:PEAKing[?] Syntax :INPut:CDR:SECond:PEAKing ‘identifier’, <NRf> :INPut:CDR:SECond:PEAKing? ‘identifier’ Input ‘identifier’: 'M*.DataIn1' or 'M*.DataIn2' Parameters <NRf>: Adjust second order peaking of the CDR. Return Range 0 dB to 3 dB Description This command adjusts the second order peaking of the CDR which is valid for the jitter transfer function.
  • Page 253 SCPI Command Reference :INPut:ALIGnment Subnode This subnode has the following SCPI structure: This subnode has the following commands: Table 57 Name Description under :INPut:ALIGnment:EYE[:AUTO] :EYE[:AUTO] on page 254 :INPut:ALIGnment:EYE:ACEN :EYE:ACENter on page 254 :INPut:ALIGnment:EYE:TCEN :EYE:TCENter on page 255 :INPut:ALIGnment:EYE:ABORt :EYE:ABORt on page 255 :INPut:ALIGnment:EYE:THReshold[?] :EYE:THReshold[?]...
  • Page 254 SCPI Command Reference Name Description under :INPut:ALIGnment:EYE:RESult:THReshold? :EYE:RESult:THReshold? on page 256 :INPut:ALIGnment:EYE:RESult:DELay? :EYE:RESult:DELay? page 257 :INPut:ALIGnment:EYE:RESult:POLarity? :EYE:RESult:POLarity? page 257 :INPut:ALIGnment:EYE[:AUTO] Syntax :INPut:ALIGnment:EYE[:AUTO] ‘identifier’ Input ‘identifier’: 'M*.DataIn1', 'M*.DataIn2' or M*DataIn Parameters Description This command starts an auto alignment. This SCPI is applicable for M8041A, M8051A, M8062A and M8046A. Example :INP:ALIG:EYE ‘M1.DataIn1’...
  • Page 255 SCPI Command Reference :INPut:ALIGnment:EYE:TCEN Syntax :INPut:ALIGnment:EYE:TCEN ‘identifier’ Input ‘identifier’: 'M*.DataIn1', 'M*.DataIn2' or M*DataIn Parameters Description This command initiates a search for the value of data/clock delay that puts the active clock edge in the center of the data eye, midway between the two relative delay points with a measured BER just in excess of the BER configured by the :EYE:THReshold command.
  • Page 256 SCPI Command Reference :INPut:ALIGnment:EYE:RESult[:HEIGht]? Syntax :INPut:ALIGnment:EYE:RESult[:HEIGht]? ‘identifier’ Input ‘identifier’: 'M*.DataIn1', 'M*.DataIn2' or M*DataIn Parameters Description This is a query command that searches for the value of data amplitude that puts the 0/1 threshold level midway between the upper and lower bounds at which the error ratio exceeds the threshold value set by the :INPut:ALIGnment:EYE:THReshold command.
  • Page 257 SCPI Command Reference :INPut:ALIGnment:EYE:RESult:DELay? Syntax :INPut:ALIGnment:EYE:RESult:DELay? ‘identifier’ Input ‘identifier’: 'M*.DataIn1', 'M*.DataIn2' or M*DataIn Parameters Description Returns the delay detected at the last alignment run. This SCPI is applicable for M8041A, M8051A, M8062A and M8046A. Example :INP:ALIG:EYE:RES:DEL? ‘M1.DataIn1’ :INPut:ALIGnment:EYE:RESult:POLarity? Syntax :INPut:ALIGnment:EYE:RESult:POLarity? ‘identifier’ Input ‘identifier’: 'M*.DataIn1', 'M*.DataIn2' or M*DataIn Parameters...

  • Page 258: Sense Subsystem

    SCPI Command Reference SENSe Subsystem The SENSe subsystem represents the analyzer's Data In port. This subsystem has the following commands: Table 58 Name Description under :SENSe:SRATe[?] :SENSe:SRATe[?] on page 258 :SENSe:SRATe[?] Syntax :SENSe:SRATe[?] <identifier>, <NRf> :SENSe:SRATe? <identifier> Input ‘identifier’: 'M*.DataIn' Parameters Description This command controls the symbol rate for the data input.

  • Page 259: Clock Subsystem

    SCPI Command Reference CLOCk Subsystem The CLOCk subsystem is used to detect clock source or to set the clock frequency applied to input or output channel. M8061A has only DataOut with Clock functional block, so the commands NOTE are only supported in the DataOut location and not in the DataIn location. This subsystem has the following SCPI structure: :CLOCk [:SOURce][?]...
  • Page 260 SCPI Command Reference :CLOCk[:SOURce][?] Syntax :CLOCk[:SOURce] ‘identifier’, <NRf> :CLOCk[:SOURce]? ‘identifier’ Input ‘identifier’: 'M*.DataOut' and ‘M*.DataIn’ Parameters <NRf>: CDR | CLK | SYS | AUXCLK | ECRevovery Return Range CDR | CLK | SYS | AUXCLK | ECR Description This command sets the source of the clock signal. It is supported by: •...
  • Page 261 SCPI Command Reference Description This command select the external clock recovery to be used when using the clock source ‘ECRecovery’ This query returns the present state. This SCPI is applicable for M8046A. Example :CLOCK:CREC:SEL"M2.DataIn","DCA1.Slot1" :CLOCk:FREQuency [?] Syntax CLOCk:FREQuency ‘Identifier', <NRf> CLOCk:FREQuency? ‘Identifier' Input ‘identifier’: 'M*.DataOut' or 'M*.DataIn'...
  • Page 262 SCPI Command Reference :CLOCk:TRACk[:STATe][?] Syntax :CLOCk:TRACk[:STATe] <identifier>, <ON|OFF|1|0> CLOCk:FREQuency? ‘Identifier' Input ‘identifier’: 'M*.DataIn' Parameters Description This command enables or disables the automatic system symbol rate tracking. When this is enabled, then the system symbol rate is used as the symbol rate of the addressed functional unit (e.g. DataIn). In this case, the required clock frequency will be determined automatically based on the selected frequency multiplier.

  • Page 263: N71000 Subsystem

    SCPI Command Reference N71000 Subsystem The N1000 subsystem is used to control external clock recovery instruments that are themselves controlled from within the FlexDCA N1000-Series System Software. The minimum required version of the FlexDCA N1000-Series System NOTE Software is A.05.61.23. It is possible to share one FlexDCA instance among multiple M8070A instances.
  • Page 264 SCPI Command Reference This subsystem has the following SCPI structure: :N1000 :EMODules :CONNect[?] :CRECovery :CLBandwidth[?] :CRATe [?] :LBWMode[?] :LOCKed? :LSELect [?] :AUTomatic[?] :ODRatio[?] :AUTO[?] :RDIVider[?] :RELock :SOURce[?] This subsystem has the following commands: Table 60 Name Description under :N1000:EMODules:SLOT:CONNect[?] :N1000:EMODules:SLOT:CONNec t[?] page 265 :N1000:CRECovery:CLBandwidth[?]...
  • Page 265 SCPI Command Reference Name Description under :N1000:CRECovery:ODRatio:AUTO[?] :N1000:CRECovery:ODRatio:AUT O[?] on page 266 page 269 :N1000:CRECovery:RDIVider[?] :N1000:CRECovery:RDIVider[?] on page 269 :N1000:CRECovery:RELock :N1000:CRECovery:RELock on page 269 :N1000:CRECovery:SOURce[?] :N1000:CRECovery:SOURce[?] on page 270 :N1000:EMODules:SLOT:CONNect[?] Syntax :N1000:EMODules:SLOT:CONNect <identifier>,{ON | OFF | 1 | 0} :N1000:EMODules:SLOT:CONNect? <identifier> Input ‘identifier’: ‘DCA*.SLOT*' Parameters...
  • Page 266 SCPI Command Reference :N1000:CRECovery:CLBandwidth[?] Syntax :N1000:CRECovery:CLBandwidth <identifier>,<bandwidth> :N1000:CRECovery:CLBandwidth? <identifier>, Input ‘identifier’: ‘DCA*.SLOT*' Parameters Description This command sets the fix loop bandwidth. This query returns the present state. This SCPI is applicable for M8046A. Example :N1000:CREC:CLB "DCA1.SLOT1",10e6 For detailed documentation, see :CRECovery{n}:CLBandwidth in the FlexDCA online help.
  • Page 267 SCPI Command Reference This query returns the present state. This SCPI is applicable for M8046A. Example :N1000:CREC:LBWM "DCA1.SLOT1",RDEP For detailed documentation, see :CRECovery{n}:LBWMode in the FlexDCA online help. :N1000:CRECovery:LOCKed? Syntax :N1000:CRECovery:LOCKed? <identifier> Input ‘identifier’: ‘DCA*.SLOT*' Parameters Description This query displays the clock recovery’s lock status. Response: 1 (for locked) or 0 (for unlocked) This SCPI is applicable for M8046A.
  • Page 268 SCPI Command Reference :N1000:CRECovery:LSELect:AUTomatic[?] Syntax :N1000:CRECovery:LSELect:AUTomatic <identifier>,{ON | OFF | 1 | 0} :N1000:CRECovery:LSELect:AUTomatic? <identifier> Input ‘identifier’: ‘DCA*.SLOT*' Parameters ON | OFF | 1 | 0 Description This command enables or disables automatic selection of the type 2 loop transition frequency. This query returns the present state.
  • Page 269 SCPI Command Reference :N1000:CRECovery:ODRatio:AUTO[?] Syntax :N1000:CRECovery:ODRatio:AUTO <identifier>,{ON | OFF | 1 | 0} :N1000:CRECovery:ODRatio:AUTO? <identifier> Input ‘identifier’: ‘DCA*.SLOT*' Parameters Description This command enables or disables automatic selection of the recovered clock’s output divide ratio. This query returns the present state. This SCPI is applicable for M8046A.
  • Page 270 SCPI Command Reference The re-lock operation can take quite some time. Especially when the NOTE clock recovery cannot lock to the received signal. Therefore, the VISA timeout shall be increased to well above 10 seconds to ensure that the controlling program is waiting long enough for the re-lock operation to finish.

  • Page 271: Fetch Subsystem

    SCPI Command Reference FETCh Subsystem The FETCh subsystem is used to query the error detector’s results. Commands for starting, stopping, resetting, etc. are found in the :PLUGin:ERATio subsystem. This subsystem has the following SCPI structure: This subsystem has the following commands: Table 61 Name Description under...
  • Page 272 SCPI Command Reference Timestamp: As timestamp the UNIX epoch time is used; it is defined as elapsed seconds, milliseconds etc. since 01.01.1970 UTC. Location: It’s a string referred to the place the bit counter are located. This parameter is important if a group name is used as ‘Identifier’. Counted1s: The number of received ones since start of accumulation period Counted0s: The number of received zeros since start of accumulation...
  • Page 273 SCPI Command Reference Additional Counters for PAM-4 line coding • Compared Symbols • Errored Symbols • Compared Symbol0 • Errored Symbol0 • Compared Symbol1 • Errored Symbol1 • Compared Symbol2 • Errored Symbol2 • Compared Symbol3 • Errored Symbol3 If this query is sent to a ‘group’ of inputs, the response will be expanded by additional sets of counted values.
  • Page 274 SCPI Command Reference :FETCh:IBERate? Syntax :FETCh:IBERate? ‘identifier’ Input ‘identifier’: 'M*.DataIn1' or 'M*.DataIn2' Parameters Description This query returns the instantaneous bit error rate measured by the addressed error detector. The response contains a timestamp, the location and the measured BER. (TimeStamp, “Location”, BER[, coding specific ratios]) Timestamp: As timestamp the Unix epoch time is used;...
  • Page 275 SCPI Command Reference As ‘Identifier’ a group name is also allowed. The response will be expanded by additional sets of values per error detector included in the group. Example :FETC:IBER? ‘M6.DataIn1’ Response: (1.266014336e9, “M6.DataIn1“, 1.2345e-1) :FETC:IBER? 'Lanes' Response: (1.266514336e9, “M1.DataIn1“, 1.2345e-1, “M1.DataIn2“, 0.0e0) Keysight M8070A Programming Guide...

  • Page 276: Mmemory Subsystem

    SCPI Command Reference MMEMory Subsystem All instrument states of the M8020A/M8030A instrument are stored in a “workspace”. There are two defined areas in a workspace. One area is named “Factory”. In this area you can find read only predefined settings and patterns.
  • Page 277 SCPI Command Reference This subsystem has the following commands: Table 62 Name Description under :MMEMory:WORKspace:SETTings[:USER]:C :WORKspace:SETTings:USER:CAT ATalog? alog? on page 278 :MMEMory:WORKspace:SETTings[:USER]:S :WORKspace:SETTings:USER:STO TORe on page 278 :MMEMory:WORKspace:SETTings[:USER]:R :WORKspace:SETTings:USER:REC ECall on page 278 :MMEMory:WORKspace:SETTings[:USER]: :WORKspace:SETTings:USER:DEL DELete on page 279 :MMEMory:WORKspace:SETTings:FACTory: :WORKspace:SETTings:FACTory:C CATalog? ATalog?

  • Page 278: Mmemory:workspace:settings[:User]:Catalog

    SCPI Command Reference :MMEMory:WORKspace:SETTings[:USER]:CATalog? Syntax :MMEMory:WORKspace:SETTings[:USER]:CATalog? Description This query returns a list of names currently stored in the “User” area. Example :MMEM:WORK:SETT:CAT? "PCI3_InitialTestSetting,DefaultSetting_1,DefaultSetting_2, DefaultSetting_3,DefaultSetting_4,PCI3/InitialTestA, PCI3/InitialTestB, PCI3_InitialTestSetting" :MMEMory:WORKspace:SETTings[:USER]:STORe Syntax :MMEMory:WORKspace:SETTings[:USER]:STORe “Path” Input “Path”: Specify name/path to store instrument state. Parameters Description This command stores the instrument state to the specified location.

  • Page 279: Mmemory:workspace:settings[:User]:Delete

    SCPI Command Reference :MMEMory:WORKspace:SETTings[:USER]:DELete Syntax :MMEMory:WORKspace:SETTings[:USER]:DELete “Path” Input “Path”: Specify location of stored instrument state. Parameters Description This command deletes the instrument state from the specified location. Example :MMEM:WORK:SETT:DEL “TestConfigurationSATA_1” :MMEM:WORK:SETT:DEL “SATA/TestConfiguration_1” :MMEM:WORK:SETT:DEL “SATA/TestConfiguration_2” :MMEMory:WORKspace:SETTings:FACTory:CATalog? Syntax :MMEMory:WORKspace:SETTings:FACTory:CATalog? Description This command creates a list of “predefined” setting names located in the “Factory”...

  • Page 280: Mmemory:workspace:import[:User]

    SCPI Command Reference :MMEMory:WORKspace:IMPort[:USER] Syntax MMEMory:WORKspace:IMPort[:USER] <ProfileType>,<"SourcePath">,<"RelativeTargetPath"> Input <ProfileType>: Specify jitter sweep or spread spectrum clocking profile Parameters type or SPProfile. <“SourcePath”>: Specify the absolute source path of file to be imported. <“RelativeTargetPath”>: Specify a current setting or a shared (common) storage location.

  • Page 281: Mmemory:workspace:import[:User]:Catalog

    SCPI Command Reference :MMEMory:WORKspace:IMPort[:USER]:CATalog? Syntax :MMEMory:WORKspace:IMPort[:USER]:CATalog? <ProfileType> Input <ProfileType>: Specify jitter sweep, spread spectrum clocking and spread Parameters spectrum profile type i.e. <JSPRofile | SSCProfile | SPProfile>. Description This query generates a list of imported files based on the profile type. Example :MMEM:WORK:IMP:CAT? jspr Returns:...

  • Page 282: Plugin Subsystem

    SCPI Command Reference PLUGin Subsystem The M8020A/M8030A/M8040A platform supports a plugin interface used to implement certain interfaces recognized by the software and integrated into the M8070A GUI and instrument software. Error Ratio, Output Timing, Jitter Tolerance, Output Level, Eye Diagram, Parameter Sweep and Pattern Capture measurements are examples of the plugin concept.

  • Page 283: Plugin:eratio Subnode

    SCPI Command Reference This subsystem has the following subnodes: Table 63 Name Description under :PLUGin:CATalog? :CATalog? on page 283 :RNODes[:LIST]? :PLUGin:ERATio Subnode :ERATio on page 284 :PLUGin:OTIMing Subnode :OTIMing on page 305 :PLUGin:OLEVel Subnode :OLEVel on page 335 :PLUGin:JTOLerance Subnode :JTOLerance on page 368 :PLUGin:EDIagram Subnode...
  • Page 284 SCPI Command Reference :PLUGin:ERATio Subnode This is the basic measurement for the bit error ratio, symbol error ratio and frame error ratio and is integrated with the M8070A software during the startup. The measurement comes with the set of acquisition and evaluation parameters which are used to configure the measurement run.
  • Page 285 SCPI Command Reference This subnode has the following SCPI structure: :PLUGin :ERATio :ACQuisition :ALOCation[?] :AEND[?] :COMPared[?] :DURation[?] :HISTory[?] :INTerval[?] :TCLevel[?] :TERatio[?] :TIME[?] :EVALuation :CERatio[?] :RVMode? :FETCh :DATA? [:DURation]? :PFResult? :CATalog? :DELete :NEW :RESet :STARt :STOP :SHOW:SGLegends :GRAPh? :RUN :HISTory [:STATe][?] :CLEar :LOG? :MESSage?
  • Page 286 SCPI Command Reference This subnode has the following commands: Table 64 Name Description under :PLUGin:ERATio:ACQuisition:ALOCation[?] :ACQuisition:ALOCation[?] on page 287 :PLUGin:ERATio:ACQuisition:AEND[?] :ACQuisition:AEND[?] page 288 :PLUGin:ERATio:ACQuisition:COMPared[?] :ACQuisition:COMPared[?] on page 289 :PLUGin:ERATio:ACQuisition:DURation[?] :ACQuisition:DURation[?] page 289 :PLUGin:ERATio:ACQuisition:HISTory[?] :ACQuisition:HISTory[?] page 290 :PLUGin:ERATio:ACQuisition:INTerval[?] :ACQuisition:INTerval[?] page 290 :PLUGin:ERATio:ACQuisition:TCLevel[?] :ACQuisition:TCLevel[?] page 291...
  • Page 287 SCPI Command Reference Name Description under :PLUGin:ERATio:RESet :RESet on page 298 :PLUGin:ERATio:STARt :STARt on page 298 :PLUGin:ERATio:STOP :STOP on page 300 :PLUGin:ERATio:SHOW:SGLegends :SHOW:SGLegends page 300 :PLUGin:ERATio:GRAPh? :GRAPh? on page 300 :PLUGin:ERATio:RUN:HISTory[:STATe][?] :RUN:HISTory[:STATe] page 302 :PLUGin:ERATio:RUN:HISTory:CLEar :RUN:HISTory:CLEar page 302 :PLUGin:ERATio:RUN:LOG? :RUN:LOG? on page 303 :PLUGin:ERATio:RUN:MESSage? :RUN:MESSage?
  • Page 288 SCPI Command Reference :PLUGin:ERATio:ACQuisition:AEND[?] Syntax :PLUGin:ERATio:ACQuisition:AEND ‘identifier’, <PFA|FDUR> :PLUGin:ERATio:ACQuisition:AEND? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters <PFA|FDUR>: Set accumulation end mode. Return Range PFA|FDUR Description This command sets the accumulation to end when a pass/fail (PFA) condition has been met or end after the full duration (FDUR) of the measurement for the addressed measurement name identifier.
  • Page 289 SCPI Command Reference :PLUGin:ERATio:ACQuisition:COMPared[?] Syntax :PLUGin:ERATio:ACQuisition:COMPared ‘identifier’, <NRf> :PLUGin:ERATio:ACQuisition:COMPared? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters <NRf>: IE+6 to IE+18 Return Range IE+6 to IE+18 Description This command sets the Number of Compared Bits for the addressed measurement name identifier. The query returns the current value. This SCPI is applicable for M8041A, M8051A, M8061A, M8062A and M8046A.
  • Page 290 SCPI Command Reference :PLUGin:ERATio:ACQuisition:HISTory[?] Syntax :PLUGin:ERATio:ACQuisition:HISTory ‘identifier’, <NRf> :PLUGin:ERATio:ACQuisition:HISTory? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters <NRf>: Set size of accumulation values. Return Range 1 to 100000 Description This command sets the size of accumulation values to be kept in memory for the addressed measurement name identifier.
  • Page 291 SCPI Command Reference :PLUGin:ERATio:ACQuisition:TCLevel[?] Syntax :PLUGin:ERATio:ACQuisition:TCLevel ‘identifier’, <NRf> :PLUGin:ERATio:ACQuisition:TCLevel? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters <NRf>: Set target confidence level. Return Range 0.1% to 99.9% Description This command sets the target confidence level when accumulation end is set to pass/fail (in percent) for the addressed measurement name identifier.
  • Page 292 SCPI Command Reference :PLUGin:ERATio:ACQuisition:TIME[?] Syntax :PLUGin:ERATio:ACQuisition:TIME ‘identifier’, <NRf> :PLUGin:ERATio:ACQuisition:TIME? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters <NRf>: Set accumulation fixed time. Return Range 1 s to 31.5E6 s Description This command sets the accumulation fixed time, when accumulation duration is set to FTIM (fixed time), for the addressed measurement name identifier.
  • Page 293 SCPI Command Reference :PLUGin:ERATio:SHOW:RVMode[?] Syntax :PLUGin:ERATio:SHOW:RVMode ‘identifier’, <DET|SUMM> :PLUGin:ERATio:SHOW:RVMode? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters <DET|SUMM>: Select measurement results view mode. Return Range DET|SUMM Description This command sets the measurement results view mode to detailed or summary when viewing the results using the :PLUGin:ERATio:FETCh:DATA? command.
  • Page 294 SCPI Command Reference :PLUGin:ERATio:FETCh:DATA? Syntax :PLUGin:ERATio:FETCh:DATA? ‘identifier’[,‘Location’] Input ‘identifier’: Specify the measurement name. Parameters [,‘Location’]: ‘M*.DATAOUT1’ or ‘M*.DataOut2’ (optional). Return Range ‘M*.DATAOUT1’ or ‘M*.DataOut2’ (data results) Description This command returns the raw data of the error ratio measurement for the addressed measurement name identifier and location identifier.
  • Page 295 SCPI Command Reference :PLUG:ERAT:FETC:DATA? ‘Error Ratio 1’,‘M1.DataIn1’ Return: ("M1.DataIn1",1420795894.76206,499999811,500000189,0,0,7692307,0, 0,0,0,0,0, ...) If the location is omitted from the above example e.g. if the query is :PLUG:ERAT:FETC:DATA? ‘Error Ratio 1’ then the query returns the comma separated list of all the analyzer location group participating in the measurement.
  • Page 296 SCPI Command Reference :PLUGin:ERATio:FETCh[:DURation]:PFResult? Syntax :PLUGin:ERATio:FETCh[:DURation]:PFResult? ‘identifier’[,‘Location’] Input ‘identifier’: Specify the measurement name. Parameters [,‘Location’]: Specify the location identifier (optional). Return Range <NR3> Description This command returns the results from the :PLUGin:ERATio:FETCh[:DURation]? query as well as four additional values of the specified measurement name and location identifier: •...
  • Page 297 SCPI Command Reference :PLUGin:ERATio:CATalog? Syntax :PLUGin:ERATio:CATalog? Description This command returns a list of all created error ratio measurement names currently available for measuring. This SCPI is applicable for M8041A, M8051A, M8061A, M8062A and M8046A. Example Assume the following is a list of created error ratio measurement names: :PLUG:ERAT:NEW ‘ERAT_1’...
  • Page 298 SCPI Command Reference :PLUGin:ERATio:DELete Syntax :PLUGin:ERATio:DELete ‘identifier’ Input ‘identifier’: Specify the measurement name to delete. Parameters Description This command deletes a previously created error ratio measurement addressed by the measurement name identifier. This SCPI is applicable for M8041A, M8051A, M8061A, M8062A and M8046A.
  • Page 299 SCPI Command Reference Example The following example starts an error ratio measurement addressed with the measurement name identifier called ‘MyMeasurement’: :PLUG:ERAT:STAR ‘MyMeasurement’ Keysight M8070A Programming Guide...
  • Page 300 SCPI Command Reference :PLUGin:ERATio:STOP Syntax :PLUGin:ERATio:STOP ‘identifier’ Input ‘identifier’: Specify the measurement name to stop. Parameters Description This command stops an error ratio measurement addressed by the measurement name identifier. This SCPI is applicable for M8041A, M8051A, M8061A, M8062A and M8046A.
  • Page 301 SCPI Command Reference [,<CURR | WHIT>]: Specify whether the user wants to capture in current theme or wants to capture in white background. [,<PNG>]: Specify the format of the image. The default format is PNG. [,1 | 0]: Specify whether to capture the graph with legends or not. [,’TabName’]: Specify the tab name on which the graph is supposed to be captured.
  • Page 302 SCPI Command Reference :PLUGin:ERATio:RUN:HISTory[:STATe][?] Syntax :PLUGin:ERATio:RUN:HISTory[:STATe] ‘identifier’ <0|1|ON|OFF> :PLUGin:ERATio:RUN:HISTory[:STATe]? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters Return Range 0|1|ON|OFF Description This command enables/disables the storage of error ratio measurement results addressed by the measurement name identifier. This query returns the current setting. This SCPI is applicable for M8041A, M8051A, M8061A, M8062A and M8046A.
  • Page 303 SCPI Command Reference :PLUGin:ERATio:RUN:LOG? Syntax :PLUGin:ERATio:RUN:LOG? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters Description This command returns logs for the addressed measurement. This SCPI is applicable for M8041A, M8051A, M8061A, M8062A and M8046A. Example The following example returns logs for the measurement name identifier called ‘MyMeasurement’: :PLUGin:ERATio:RUN:LOG? ‘MyMeasurement’...
  • Page 304 SCPI Command Reference :PLUGin:ERATio:RUN:PROGress? Syntax :PLUGin:ERATio:RUN:PROGress? ‘identifier’ Input ‘identifier’: Specify measurement name. Parameters Return Range 0.0 to 1.0 Description This query returns a number in the range of 0.0 to 1.0 to indicate the progress of an error ratio measurement addressed by the measurement name identifier.
  • Page 305 SCPI Command Reference :PLUGin:OTIMing Subnode This is the basic measurement for BER versus the sampling point delay, which is displayed as a “Bathtub” curve and is integrated with the M8070A software during the startup. The measurement comes with the set of acquisition and evaluation parameters which are used to configure the measurement run.
  • Page 306 SCPI Command Reference This subnode has the following SCPI structure: :PLUGin :OTIMing :ACQuisition :ALOCation[?] :DRESolution[?] :FTJBer[?] :OPTimization[?] :COMPared[?] :EBEnabled[?] :ERRored[?] :EVALuation :BERThresh[?] :MBJPartition[?] :ETJBer[?] :ERRType[?] :SHOW :SMPoints :UNIT :VSCale :SGLegends :CATalog? :DELete :NEW :RESet :STARt :STOP :BREak :STEP :CONTinue :GRAPh? :RUN :HISTory [:STATe][?]...
  • Page 307 SCPI Command Reference This subnode has the following commands: Table 65 Name Description under :PLUGin:OTIMing:ACQuisition:ALOCation[?] :ACQuisition:ALOCation[?] on page 308 :PLUGin:OTIMing:ACQuisition:DRESolution[ :ACQuisition:DRESolution[?] on page 309 :PLUGin:OTIMing:ACQuisition:FTJBer[?] :ACQuisition:FTJBer[?] page 309 :PLUGin:OTIMing:ACQuisition:OPTimization :ACQuisition:OPTimization[?] on page 310 :PLUGin:OTIMing:ACQuisition:COMPared[?] :ACQuisition:COMPared[?] on page 310 :PLUGin:OTIMing:ACQuisition:EBEnabled[?] :ACQuisition:EBEnabled[?] on page 311 :PLUGin:OTIMing:ACQuisition:ERRored[?] :ACQuisition:ERRored[?]...

  • Page 308: Plugin:otiming:fetch Subnode

    SCPI Command Reference Name Description under :PLUGin:OTIMing:NEW :NEW on page 316 :PLUGin:OTIMing:RESet :RESet on page 317 :PLUGin:OTIMing:STARt :STARt on page 317 :PLUGin:OTIMing:STOP :STOP on page 318 :PLUGin:OTIMing:BREak :BREak on page 318 :PLUGin:OTIMing:STEP :STEP on page 319 :PLUGin:OTIMing:CONTinue :CONTinue on page 320 :PLUGin:OTIMing:GRAPh? :GRAPh? on page 320...
  • Page 309 SCPI Command Reference The query returns the current location or group name identifier against which the measurement name identifier is configured for the data acquisition. This SCPI is applicable for M8041A, M8051A, M8062A and M8046A. Example :PLUG:OTIM:ACQ:ALOC ‘MyMeasurement’,“M1.DataIn1” :PLUGin:OTIMing:ACQuisition:DRESolution[?] Syntax :PLUGin:OTIMing:ACQuisition:DRESolution ‘identifier’, <NRf>...
  • Page 310 SCPI Command Reference :PLUGin:OTIMing:ACQuisition:OPTimization[?] Syntax :PLUGin:OTIMing:ACQuisition:OPTimization ‘identifier’, <FTJ|NONE> :PLUGin:OTIMing:ACQuisition:OPTimization? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters <FTJ|NONE>: Specify the sample delay optimization technique. Return Range FTJ|NONE Description This command specifies the sample delay optimization technique and associates it with a specific measurement name identifier. If NONE is selected then no optimization is performed.
  • Page 311 SCPI Command Reference :PLUGin:OTIMing:ACQuisition:EBEnabled[?] Syntax :PLUGin:OTIMing:ACQuisition:EBEnabled ‘identifier’, <OFF|ON|0|1> :PLUGin:OTIMing:ACQuisition:EBEnabled? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters <OFF|ON|0|1>: Disable/enable errored bits as criteria to move to the next measurement point. Return Range Description This command enables/disables the number of errored bits. This command also associates this parameter with a specific measurement name identifier.
  • Page 312 SCPI Command Reference :PLUGin:OTIMing:EVALuation:BERThresh[?] Syntax :PLUGin:OTIMing:EVALuation:BERThresh ‘identifier’, <NRf> :PLUGin:OTIMing:EVALuation:BERThresh? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters <NRf>: Specify the BER threshold value. Return Range 1E-15 to 1E-1 Description This command specifies the BER threshold value used to calculate the measurement parameters and associates it with a specific measurement name identifier.
  • Page 313 SCPI Command Reference :PLUGin:OTIMing:EVALuation:ETJBer[?] Syntax :PLUGin:OTIMing:EVALuation:ETJBer ‘identifier’, <EM6|...|EM12> :PLUGin:OTIMing:EVALuation:ETJBer? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters <EM6|...|EM12>: Specify the residual BER for total jitter estimation calculation. Return Range EM6 to EM12 Description This command specifies the residual BER for total jitter estimation calculation and associates it with a specific measurement name identifier.
  • Page 314 SCPI Command Reference :PLUGin:OTIMing:SHOW:SMPoints[?] Syntax :PLUGin:OTIMing:SHOW:SMPoints ‘identifier’, <OFF|ON|0|1> :PLUGin:OTIMing:SHOW:SMPoints? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters <OFF|ON|0|1>: Disable/enable viewing the measurement points. Return Range Description This command disables/enables viewing of the measurement points in the GUI and associates it with a specific measurement name identifier. A 0 or OFF value disables viewing and a 1 or ON value enables viewing of the measurement points.
  • Page 315 SCPI Command Reference :PLUGin:OTIMing:SHOW:VSCale[?] Syntax :PLUGin:OTIMing:SHOW:VSCale ‘identifier’, <LOG|LIN> :PLUGin:OTIMing:SHOW:VSCale? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters <LOG|LIN>: Specify the vertical axis scale. Return Range LOG|LIN Description This command specifies the vertical BER axis scale and associates it with a specific measurement name identifier.
  • Page 316 SCPI Command Reference Example Assume the following is a list of created output timing measurement names: :PLUG:OTIM:NEW ‘OTIM_1’ :PLUG:OTIM:NEW ‘OTIM_2’ :PLUG:OTIM:NEW ‘OTIM_3’ The command and returned list would look like the following: :PLUG:OTIM:CAT? “OTIM_1”,“OTIM_2”,“OTIM_3” :PLUGin:OTIMing:NEW Syntax :PLUGin:OTIMing:NEW ‘identifier’ Input ‘identifier’: Specify a new measurement name. Parameters Description This command creates a new output timing measurement name identifier.
  • Page 317 SCPI Command Reference :PLUGin:OTIMing:DELete Syntax :PLUGin:OTIMing:DELete ‘identifier’ Input ‘identifier’: Specify the measurement name to delete. Parameters Description This command deletes a previously created output timing measurement addressed by the measurement name identifier. This SCPI is applicable for M8041A, M8051A, M8062A and M8046A. Example The following example deletes an output timing measurement with the measurement name identifier called ‘MyOutputTiming’:...
  • Page 318 SCPI Command Reference :PLUGin:OTIMing:STOP Syntax :PLUGin:OTIMing:STOP ‘identifier’ Input ‘identifier’: Specify the measurement name to stop. Parameters Description This command stops an output timing measurement addressed by the measurement name identifier. This SCPI is applicable for M8041A, M8051A, M8062A and M8046A. Example The following example stops an output timing measurement with the measurement name identifier called ‘MyOutputTiming’:...
  • Page 319 SCPI Command Reference :PLUGin:OTIMing:STEP Syntax :PLUGin:OTIMing:STEP ‘identifier’ Input ‘identifier’: Specify the measurement name to step. Parameters Description This command allows you to step through an output timing measurement, addressed by the measurement name identifier, that was stopped using the BREak command. This SCPI is applicable for M8041A, M8051A, M8062A and M8046A.
  • Page 320 SCPI Command Reference :PLUGin:OTIMing:CONTinue Syntax :PLUGin:OTIMing:CONTinue ‘identifier’ Input ‘identifier’: Specify the measurement name to continue. Parameters Description This command allows you to continue an output timing measurement, addressed by the measurement name identifier, that was stopped using the BREak command. This SCPI is applicable for M8041A, M8051A, M8062A and M8046A.
  • Page 321 SCPI Command Reference :PLUGin:OTIMing:RUN:HISTory[:STATe][?] Syntax :PLUGin:OTIMing:RUN:HISTory[:STATe] ‘identifier’,<0|1|OFF|ON> :PLUGin:OTIMing:RUN:HISTory[:STATe]? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters Return Range Description This command enables/disables the storage of output timing measurement results addressed by the measurement name identifier. This query returns the current setting. This SCPI is applicable for M8041A, M8051A, M8062A and M8046A.
  • Page 322 SCPI Command Reference :PLUGin:OTIMing:RUN:LOG? Syntax :PLUGin:OTIMing:RUN:LOG? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters Description This command returns logs for the addressed measurement. This SCPI is applicable for M8041A, M8051A, M8062A and M8046A. Example This command returns logs for the measurement ‘MyMeasurement’. :PLUG:OTIM:RUN:LOG? ‘MyMeasurement’...
  • Page 323 SCPI Command Reference :PLUGin:OTIMing:RUN:PROGress? Syntax :PLUGin:OTIMing:RUN:PROGress? ‘identifier’ Input ‘identifier’: Specify measurement name. Parameters Return Range 0.0 to 1.0 Description This command returns a number in the range of 0.0 to 1.0 to indicate the progress of an output timing measurement addressed by the measurement name identifier.
  • Page 324 SCPI Command Reference :PLUGin:OTIMing:FETCh Subnode This subnode has the following SCPI structure: Keysight M8070A Programming Guide...
  • Page 325 SCPI Command Reference This subnode has the following commands: Table 66 Name Description under :PLUGin:OTIMing:FETCh:EDGE[:LEFT][:POI :EDGE[:LEFT][:POINts]? Nts]? on page 326 :PLUGin:OTIMing:FETCh:EDGE[:LEFT]:RSQ :EDGE[:LEFT]:RSQuare? uare? on page 326 :PLUGin:OTIMing:FETCh:EDGE:RIGHt[:POI :EDGE:RIGHt[:POINts]? Nts]? on page 327 :PLUGin:OTIMing:FETCh:EDGE:RIGHt:RSQ :EDGE:RIGHt:RSQuare? uare? on page 327 :PLUGin:OTIMing:FETCh[:JITTer][:TOTal]:DJ [:JITTer][:TOTal]:DJITTer? ITter? on page 328 :PLUGin:OTIMing:FETCh[:JITTer][:TOTal]:ES...

  • Page 326: Plugin:otiming:fetch:edge[:Left][:Points]

    SCPI Command Reference :PLUGin:OTIMing:FETCh:EDGE[:LEFT][:POINts]? Syntax :PLUGin:OTIMing:FETCh:EDGE[:LEFT][:POINts]? ‘identifier’[,‘Location’] Input ‘identifier’: Specify the measurement name. Parameters [‘Location’]: Specify location (optional). Return Range <NR3> Description This command returns the number of points that have been measured between the BER Threshold and the Min. BER for RJ/DJ separation threshold associated with a specific measurement name identifier.

  • Page 327: Plugin:otiming:fetch:edge:right

    SCPI Command Reference :PLUGin:OTIMing:FETCh:EDGE:RIGHt[:POINts]? Syntax :PLUGin:OTIMing:FETCh:EDGE:RIGHt[:POINts]? ‘identifier’[,‘Location’] Input ‘identifier’: Specify the measurement name. Parameters [‘Location’]: Specify location (optional). Return Range <NR3> Description This command returns the number of points that have been measured between the BER Threshold and the Min. BER for RJ/DJ separation threshold associated with a specific measurement name identifier.

  • Page 328: Plugin:otiming:fetch[:Jitter][:Total]:Djitter

    SCPI Command Reference :PLUGin:OTIMing:FETCh[:JITTer][:TOTal]:DJITter? Syntax :PLUGin:OTIMing:FETCh[:JITTer][:TOTal]:DJITter? ‘identifier’[,‘Location’] Input ‘identifier’: Specify the measurement name. Parameters [‘Location’]: Specify location (optional). Return Range <NR3> Description This command returns the total jitter component with non-Gaussian distribution (deterministic jitter) associated with a specific measurement name identifier. After transforming a contiguous range of measured points into Q space and performing a linear regression, it is calculated as the period minus the difference between the means of the two straight lines.

  • Page 329: Plugin:otiming:fetch[:Jitter][:Total]:Mean

    SCPI Command Reference :PLUGin:OTIMing:FETCh[:JITTer][:TOTal]:MEAN? Syntax :PLUGin:OTIMing:FETCh[:JITTer][:TOTal]:MEAN? ‘identifier’[,‘Location’] Input ‘identifier’: Specify the measurement name. Parameters [‘Location’]: Specify location (optional). Return Range <NR3> Description This command returns the mean value for total jitter associated with a specific measurement name identifier. This value is calculated as the weighted average of the left edge jitter histogram.

  • Page 330: Plugin:otiming:fetch[:Jitter][:Total][:Rmsquare]

    SCPI Command Reference :PLUGin:OTIMing:FETCh[:JITTer][:TOTal][:RMSquare]? Syntax :PLUGin:OTIMing:FETCh[:JITTer][:TOTal][:RMSquare]? ‘identifier’[,‘Location’] Input ‘identifier’: Specify the measurement name. Parameters [‘Location’]: Specify location (optional). Return Range <NR3> Description This command returns the average of the left and right jitter histogram root mean squared values associated with a specific measurement name identifier.

  • Page 331: Plugin:otiming:fetch[:Jitter][:Total]:Osdelay

    SCPI Command Reference :PLUGin:OTIMing:FETCh[:JITTer][:TOTal]:OSDelay? Syntax :PLUGin:OTIMing:FETCh[:JITTer][:TOTal]:OSDelay? ‘identifier’[,‘Location’] Input ‘identifier’: Specify the measurement name. Parameters [‘Location’]: Specify location (optional). Return Range <NR3> Description This command returns the average of the left (Ai) and right (Bi) bathtub/BER threshold intersections (optimum sample point delay) associated with a specific measurement name identifier.

  • Page 332: Plugin:otiming:fetch[:Jitter][:Total]:Uncertainty

    SCPI Command Reference :PLUGin:OTIMing:FETCh[:JITTer][:TOTal]:UNCertainty? Syntax :PLUGin:OTIMing:FETCh[:JITTer][:TOTal]:UNCertainty? ‘identifier’[,‘Location’] Input ‘identifier’: Specify the measurement name. Parameters [‘Location’]: Specify location (optional). Return Range <NR3> Description This command returns the total jitter uncertainty associated with a specific measurement name identifier. The returned value is only valid if the “Sample Delay Optimization”...

  • Page 333: Plugin:otiming:fetch:delay

    SCPI Command Reference One Bits, Compared Zero Bits, Errored One Bits, Errored Zero Bits, Sample Delay and Pass/Fail Results and are repeated in the same order for subsequent measured points. In the case of Sample Delay Optimization as "None" the pass/fail result for each measurement point is returned as "UNKNOWN".

  • Page 334: Plugin:otiming:fetch:frequency

    SCPI Command Reference :PLUGin:OTIMing:FETCh:FREQuency? Syntax :PLUGin:OTIMing:FETCh:FREQuency? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters Description This command returns the currently set frequency of the measurement. The frequency is set using the :SOURce:FREQuency command. This SCPI is applicable for M8041A, M8051A, M8062A and M8046A. Example :PLUG:OTIM:FETC:FREQ? ‘Output Timing 1’...

  • Page 335: Plugin:olevel Subnode

    SCPI Command Reference :PLUGin:OLEVel Subnode This is the basic measurement for BER versus sample threshold and is integrated with the M8070A software during the startup. The measurement comes with the set of Acquisition and Evaluation Parameters which are used to configure the measurement run. The Acquisition parameters can only be configured before the measurement starts (i.e.

  • Page 336: Plugin:olevel:acquisition Subnode

    SCPI Command Reference This subnode has the following commands and subnodes: Table 67 Name Description under :PLUGin:OLEVel:BREak :BREak[?] on page 337 :PLUGin:OLEVel:CATalog? :CATalog? on page 337 :PLUGin:OLEVel:CONTinue :CONTinue[?] on page 337 :PLUGin:OLEVel:DELete :DELete[?] on page 338 :PLUGin:OLEVel:NEW :NEW[?] on page 338 :PLUGin:OLEVel:RESet :RESet[?] on page 339...
  • Page 337 SCPI Command Reference :PLUGin:OLEVel:BREak Syntax :PLUGin:OLEVel:BREak ‘identifier’ Input ‘identifier’: Specify the measurement name to break/pause. Parameters Description This command breaks/pauses a measurement addressed by the measurement name identifier. This SCPI is applicable for M8041A, M8051A and M8062A. Example The following example breaks an output level measurement with the measurement name identifier called ‘MyMeasurement’: :PLUG:OLEV:BRE ‘MyMeasurement’...
  • Page 338 SCPI Command Reference :PLUGin:OLEVel:DELete Syntax :PLUGin:OLEVel:DELete ‘identifier’ Input ‘identifier’: Specify the measurement name to delete. Parameters Description This command deletes a previously created output level measurement addressed by the measurement name identifier. This SCPI is applicable for M8041A, M8051A and M8062A. Example The following example deletes an output level measurement addressed by the measurement name identifier called ‘MyMeasurement’:...
  • Page 339 SCPI Command Reference :PLUGin:OLEVel:RESet Syntax :PLUGin:OLEVel:RESet ‘identifier’ Input ‘identifier’: Specify the measurement name to reset. Parameters Description This command resets an output level measurement addressed by the measurement name identifier. This SCPI is applicable for M8041A, M8051A and M8062A. Example The following example resets an output level measurement addressed with the measurement name identifier called ‘MyMeasurement’: :PLUG:OLEV:RES ‘MyMeasurement’...
  • Page 340 SCPI Command Reference Example The following example triggers a single output level measurement step of the measurement addressed with the measurement name identifier called ‘MyMeasurement’: :PLUG:OLEV:STEP ‘MyMeasurement’ :PLUGin:OLEVel:STOP Syntax :PLUGin:OLEVel:STOP ‘identifier’ Input ‘identifier’: Specify the measurement name to stop. Parameters Description This command stops an output level measurement addressed by the measurement name identifier.
  • Page 341 SCPI Command Reference :PLUGin:OLEVel:ACQuisition Subnode This subnode has the following SCPI structure: :ACQuisition :ALOCation :COMPared :EBEnabled :ERRored :HILevel :LOWLevel :TRESolution This subnode has the following commands: Table 68 Name Description under :PLUGin:OLEVel:ACQuisition:ALOCation[?] :ALOCation[?] on page 342 :PLUGin:OLEVel:ACQuisition:COMPared[?] :COMPared[?] on page 342 :PLUGin:OLEVel:ACQuisition:EBEnabled[?] :EBEnabled[?] on page 343...
  • Page 342 SCPI Command Reference :PLUGin:OLEVel:ACQuisition:ALOCation[?] Syntax :PLUGin:OLEVel:ACQuisition:ALOCation 'Identifier', < location-string> :PLUGin:OLEVel:ACQuisition:ALOCation? 'Identifier' Input Identifier: 'MyMeasurement' Parameters Description This command sets the Location/Location Group string against which the Data Acquisition is performed. The query returns the current Location/Location group string against which measurement is configured for the Data Acquisition.
  • Page 343 SCPI Command Reference :PLUGin:OLEVel:ACQuisition:EBEnabled[?] Syntax :PLUGin:OLEVel:ACQuisition:EBEnabled[?] 'Identifier', <0 | 1 | ON | OFF> Input Identifier: 'MyMeasurement' Parameters Return Range Description If enabled then user can specify the number of errored bits additionally with number of compared bits in order to make them criteria together to move to the next measurement point.
  • Page 344 SCPI Command Reference :PLUGin:OLEVel:ACQuisition:HILevel[?] Syntax :PLUGin:OLEVel:ACQuisition:HILevel[?] 'Identifier', <NRf> Input Identifier: 'MyMeasurement' Parameters Return Range -5 V to 5 V Description This command allows the user to specify the sample threshold high level. The query returns current value of sample threshold high Level. This SCPI is applicable for M8041A, M8051A and M8062A.
  • Page 345 SCPI Command Reference :PLUGin:OLEVel:ACQuisition:TRESolution[?] Syntax :PLUGin:OLEVel:ACQuisition:TRESolution[?] 'Identifier', <NRf> Input Identifier: 'MyMeasurement' Parameters Return Range 1E-3 to 1 Description This command allows the user to specify the sample threshold resolution in terms of Volts. The query returns current value of sample threshold resolution in terms of Volts.
  • Page 346 SCPI Command Reference :PLUGin:OLEVel:EVALuation Subnode This subnode has the following SCPI structure: :EVALuation :BERThresh :MBQFactor This subnode has the following commands: Table 69 Name Description under :PLUGin:OLEVel:EVALuation:BERThresh[?] :BERThresh[?] on page 346 :PLUGin:OLEVel:EVALuation:MBQFactor[?] :MBQFactor[?] on page 347 :PLUGin:OLEVel:EVALuation:BERThresh[?] Syntax :PLUGin:OLEVel:EVALuation:BERThresh[?] 'Identifier', <NRf> Input Identifier: 'MyMeasurement' Parameters...
  • Page 347 SCPI Command Reference :PLUGin:OLEVel:EVALuation:MBQFactor[?] Syntax :PLUGin:OLEVel:EVALuation:MBQFactor[?] 'Identifier', <NRf> Input Identifier: 'MyMeasurement' Parameters Range 1e-15…1.0 Description This command allows the user to specify the Minimum BER for Q-factor caluclations. Please note that in order to be able to do Q-Factor calculations the specified BER Threshold value must be greater than the value specified by this command.

  • Page 348: Plugin:olevel:fetch:level Subnode

    SCPI Command Reference :PLUGin:OLEVel:FETCh Subnode This subnode has the following SCPI structure: :FETCh :DATA? :FREQuency? :LEVel … :NOISe … :QLEVel This subnode has the following commands and subnodes: Table 70 Name Description under :PLUGin:OLEVel:FETCh:DATA? :DATA? on page 349 :PLUGin:OLEVel:FETCh:FREQuency? :FREQuency? page 349 Subnode :PLUGin:OLEVel:FETCh:LEVel Subnode...
  • Page 349 SCPI Command Reference :PLUGin:OLEVel:FETCh:DATA? Syntax :PLUGin:OLEVel:FETCh:DATA? ‘identifier’[,‘Location’] Input ‘identifier’: Specify the measurement name. Parameters [,‘Location’]: ‘M*.DataIn1’ or ‘M*.DataIn2’ (optional). Description Return the raw data of the output level measurement. This SCPI is applicable for M8041A, M8051A and M8062A. Example A measurement run on location e.g 'M1.DataIn1' would return following results.
  • Page 350 SCPI Command Reference :PLUGin:OLEVel:FETCh:LEVel Subnode This subnode has the following SCPI structure: :LEVel :AMPlitude? :HIGH? :LOW? :MEAN? :THMargin? This subnode has the following commands: Table 71 Name Description under :PLUGin:OLEVel:FETCh:LEVel:AMPlitude? :AMPlitude? page 351 :PLUGin:OLEVel:FETCh:LEVel:HIGH? :HIGH? page 351 :PLUGin:OLEVel:FETCh:LEVel:LOW? :LOW? page 351 :PLUGin:OLEVel:FETCh:LEVel:MEAN? :MEAN? page 352...
  • Page 351 SCPI Command Reference :PLUGin:OLEVel:FETCh:LEVel:AMPlitude? Syntax :PLUGin:OLEVel:FETCh:LEVel:AMPlitude? ‘identifier’ [,‘Location’] Input ‘identifier’: Specify the measurement name. Parameters [,‘Location’]: ‘M*.DataIn1’ or ‘M*.DataIn2’ (optional). Description This command returns the value of amplitude calculated after a run. This SCPI is applicable for M8041A, M8051A and M8062A. Example :PLUGin:OLEVel:FETCh:LEVel:AMPlitude? ‘MyMeasurement’...
  • Page 352 SCPI Command Reference :PLUGin:OLEVel:FETCh:LEVel:MEAN? Syntax :PLUGin:OLEVel:FETCh:LEVel:MEAN? ‘identifier’ [,‘Location’] Input ‘identifier’: Specify the measurement name. Parameters [,‘Location’]: ‘M*.DataIn1’ or ‘M*.DataIn2’ (optional). Description This command returns the value of the mean level. This SCPI is applicable for M8041A, M8051A and M8062A. Example :PLUGin:OLEVel:FETCh:LEVel:MEAN? ‘MyMeasurement’...
  • Page 353 SCPI Command Reference :PLUGin:OLEVel:FETCh:NOISe Subnode This subnode has the following SCPI structure: :NOISe :PPEak? :HIGH :STDeviation? :LOW :STDeviation? :SNRatio :PPEak? :RMSquare? This subnode has the following commands: Table 72 Name Description under :PLUGin:OLEVel:FETCh:NOISe:PPEak? :PPEak? page 354 :PLUGin:OLEVel:FETCh:NOISe:HIGH:STDev :HIGH:STDeviation? iation? on page 354 :PLUGin:OLEVel:FETCh:NOISe:LOW:STDevi :LOW:STDeviation? ation?
  • Page 354 SCPI Command Reference :PLUGin:OLEVel:FETCh:NOISe:PPEak? Syntax :PLUGin:OLEVel:FETCh:NOISe:PPEak? ‘identifier’ [,‘Location’] Input ‘identifier’: Specify the measurement name. Parameters [,‘Location’]: ‘M*.DataIn1’ or ‘M*.DataIn2’ (optional). Description This command returns the value of the peak to peak noise level. This SCPI is applicable for M8041A, M8051A and M8062A. Example :PLUGin:OLEVel:FETCh:NOISe:PPEak? ‘MyMeasurement’...
  • Page 355 SCPI Command Reference :PLUGin:OLEVel:FETCh:NOISe:SNRatio:PPEak? Syntax :PLUGin:OLEVel:FETCh:NOISe:SNRatio:PPEak? ‘identifier’ [,‘Location’] Input ‘identifier’: Specify the measurement name. Parameters [,‘Location’]: ‘M*.DataIn1’ or ‘M*.DataIn2’ (optional). Description This command returns the peak to peak value of the signal to noise ratio. This SCPI is applicable for M8041A, M8051A and M8062A. Example :PLUGin:OLEVel:FETCh:NOISe:SNRatio:PPEak? ‘MyMeasurement’...
  • Page 356 SCPI Command Reference :PLUGin:OLEVel:FETCh:QLEVel Subnode This subnode has the following SCPI structure: :QLEVel :QFActor? :QOThreshold? :QRBer? :HIGH? :POINts? :RSQuare? :STDeviation? :LOW? :POINts? :RSQuare? :STDeviation? This subnode has the following commands: Table 73 Name Description under :PLUGin:OLEVel:FETCh:QLEVel:QFActor? :QFActor? page 357 :PLUGin:OLEVel:FETCh:QLEVel:HIGH? :HIGH? page 358 :PLUGin:OLEVel:FETCh:QLEVel:HIGH:POIN...
  • Page 357 SCPI Command Reference Name Description under :PLUGin:OLEVel:FETCh:QLEVel:LOW? :LOW? page 359 :PLUGin:OLEVel:FETCh:QLEVel:LOW:POINt :LOW:POINts? on page 360 :PLUGin:OLEVel:FETCh:QLEVel:LOW:RSQu :LOW:RSQuare? are? on page 360 :PLUGin:OLEVel:FETCh:QLEVel:LOW:STDev :LOW:STDeviation? iation? on page 360 :PLUGin:OLEVel:FETCh:QLEVel:QFActor? Syntax :PLUGin:OLEVel:FETCh:QLEVel:QFActor? ‘identifier’ [,‘Location’] Input ‘identifier’: Specify the measurement name. Parameters [,‘Location’]: ‘M*.DataIn1’ or ‘M*.DataIn2’ (optional). Description This command returns the value of the Q factor.
  • Page 358 SCPI Command Reference :PLUGin:OLEVel:FETCh:QLEVel:QRBer? Syntax :PLUGin:OLEVel:FETCh:QLEVel:QRBer? ‘identifier’ [,‘Location’] Input ‘identifier’: Specify the measurement name. Parameters [,‘Location’]: ‘M*.DataIn1’ or ‘M*.DataIn2’ (optional). Description This command returns the value of the Q Residual BER. This SCPI is applicable for M8041A, M8051A and M8062A. Example :PLUGin:OLEVel:FETCh:QLEVel:QRBer? ‘MyMeasurement’...
  • Page 359 SCPI Command Reference :PLUGin:OLEVel:FETCh:QLEVel:HIGH:RSQuare? Syntax :PLUGin:OLEVel:FETCh:QLEVel:HIGH:RSQuare? ‘identifier’ [,‘Location’] Input ‘identifier’: Specify the measurement name. Parameters [,‘Location’]: ‘M*.DataIn1’ or ‘M*.DataIn2’ (optional). Description This command returns the value of the Q High Level R This SCPI is applicable for M8041A, M8051A and M8062A. Example :PLUGin:OLEVel:FETCh:QLEVel:HIGH:RSQuare? ‘MyMeasurement’...
  • Page 360 SCPI Command Reference :PLUGin:OLEVel:FETCh:QLEVel:LOW:POINts? Syntax :PLUGin:OLEVel:FETCh:QLEVel:LOW:POINts? ‘identifier’ [,‘Location’] Input ‘identifier’: Specify the measurement name. Parameters [,‘Location’]: ‘M*.DataIn1’ or ‘M*.DataIn2’ (optional). Description This command returns the value of the Q Low Level Points. This SCPI is applicable for M8041A, M8051A and M8062A. Example :PLUGin:OLEVel:FETCh:QLEVel:LOW:POINts? ‘MyMeasurement’...

  • Page 361: Plugin:olevel:show Subnode

    SCPI Command Reference :PLUGin:OLEVel:SHOW Subnode This subnode has the following SCPI structure: :SHOW :SMPoints :GRAPhics :HSCale :SGLegends This subnode has the following commands: Table 74 Name Description under :PLUGin:OLEVel:SHOW:SMPoints[?] :SMPoints[?] page 362 :PLUGin:OLEVel:SHOW:GRAPhics[?] :GRAPhics[?] page 362 :PLUGin:OLEVel:SHOW:HSCale[?] :HSCale[?] on page 363 :PLUGin:OLEVel:SHOW:SGLegends[?] :SGLegends[?] page 363...
  • Page 362 SCPI Command Reference :PLUGin:OLEVel:SHOW:SMPoints[?] Syntax :PLUGin:OLEVel:SHOW:SMPoints[?] 'Identifier', <0|1|ON|OFF> Input Identifier: 'MyMeasurement' Parameters Description This command allows the user to control the GUI if he/she wants to visualize the measurement points of the measurement run. Value of 0 indicates that user does not want to visualize the measurement points and 1 indicates that user wants to visualize the measurement points.
  • Page 363 SCPI Command Reference :PLUGin:OLEVel:SHOW:HSCale[?] Syntax :PLUGin:OLEVel:SHOW:HSCale[?] 'Identifier', <LOG | LIN > Input Identifier: 'MyMeasurement' Parameters Description The command allows the user to specify the horizontal axis scale (i.e. BER scale) if BER versus Threshold graphics is visualized (see :PLUGin:OLEVel:SHOW:GRAPhics[?]), however if QBER versus threshold graphics is visualized then the Horizontal Axis Scale is always linear.

  • Page 364: Plugin:olevel:run Subnode

    SCPI Command Reference :PLUGin:OLEVel:RUN Subnode This subnode has the following SCPI structure: :RUN :MESSage? :PROGress? :STATus? :HISTory [:STATe][?] :CLEar :LOG? This subnode has the following commands: Table 75 Name Description under :PLUGin:OLEVel:RUN:MESSage? :MESSage? on page 365 :PLUGin:OLEVel:RUN:PROGress? :PROGress? on page 365 :PLUGin:OLEVel:RUN:STATus? :STATus? on page 365...
  • Page 365 SCPI Command Reference :PLUGin:OLEVel:RUN:MESSage? Syntax :PLUGin:OLEVel:RUN:MESSage? 'Identifier' Input Identifier: 'MyMeasurement' Parameters Description This command returns a string describing the state of an output level measurement addressed by the measurement name identifier. Possible states include NotStarted, Running, Suspended, Finished, Error, or Stopped.
  • Page 366 SCPI Command Reference This SCPI is applicable for M8041A, M8051A and M8062A. Example :PLUG:OLEV:RUN:STATus? 'MyMeasurement' :PLUGin:OLEVel:RUN:HISTory[:STATe][?] Syntax :PLUGin:OLEVel:RUN:HISTory[:STATe] 'Identifier', <0|1|OFF|ON> :PLUGin:OLEVel:RUN:HISTory[:STATe]? 'Identifier' Input Identifier: 'MyMeasurement' Parameters Return Range Description This command enables/disables the storage of output level measurement results addressed by the measurement name identifier. This query returns the current setting.
  • Page 367 SCPI Command Reference :PLUGin:OLEVel:RUN:LOG? Syntax :PLUGin:OLEVel:RUN:LOG? 'Identifier' Input Identifier: 'MyMeasurement' Parameters Description This command returns logs for the addressed measurement. This SCPI is applicable for M8041A, M8051A and M8062A. Example :PLUGin:OLEVel:RUN:LOG? 'MyMeasurement' Output: The format of log returned is in the following way: #XY Message Log where X denotes the length of digits for Y, Y denotes the number of characters in the log then followed by the log message.

  • Page 368: Plugin:jtolerance Subnode

    SCPI Command Reference :PLUGin:JTOLerance Subnode The jitter tolerance commands are used to determine the capacity of a serial data receiver to tolerate jitter. There are two modes: compliance or characterization. Jitter frequency is set at multiple test points. At each point, the jitter amplitude is modulated using various search algorithms to determine the level of jitter which causes the device to fail.
  • Page 369 SCPI Command Reference :BREak :CATalog? :CONTinue :NEW :DELete :RESet :STARt :STOP :STEP :RUN :HISTory [:STATe][?] :CLEar :LOG? :MESSage? :PROGress? [:STATus]? This subnode has the following commands: Table 76 Name Description under :PLUGin:JTOLerance:INSTruments:GENerat :INSTruments:GENerator[?] or[?] on page 372 :PLUGin:JTOLerance:INSTruments:ANALyz :INSTruments:ANALyzer[?] er[?] on page 372 :PLUGin:JTOLerance:BSETup:TBERatio[?] :BSETup:TBERatio[?]...
  • Page 370 SCPI Command Reference Name Description under :PLUGin:JTOLerance:MSETup:FREQuency: :MSETup:FREQuency:STOp[?] STOp[?] on page 376 :PLUGin:JTOLerance:MSETup:MTPoints[?] :MSETup:MTPoints[?] on page 376 :PLUGin:JTOLerance:MSETup:NPOints[?] :MSETup:NPOints[?] page 376 :PLUGin:JTOLerance:MSETup:MODE[?] :MSETup:MODE[?] page 377 :PLUGin:JTOLerance:MSETup:CMARgin[?] :MSETup:CMARgin[?] on page 377 :PLUGin:JTOLerance:MSETup:ALGorithm[?] :MSETup:ALGorithm[?] on page 379 :PLUGin:JTOLerance:MSETup:BINary:SSIZe :MSETup:BINary:SSIZe[?] on page 381 :PLUGin:JTOLerance:MSETup:LINear:SSIZe :MSETup:LINear:SSIZe[?] on page 382...
  • Page 371 SCPI Command Reference Name Description under :PLUGin:JTOLerance:DELete :DELete on page 389 :PLUGin:JTOLerance:RESet :RESet on page 389 :PLUGin:JTOLerance:STARt :STARt on page 390 :PLUGin:JTOLerance:STOP :STOP on page 390 :PLUGin:JTOLerance:STEP :STEP on page 390 :PLUGin:JTOLerance:GRAPh? :GRAPh? on page 384 :PLUGin:JTOLerance:RUN:HISTory[:STATe][ :RUN:HISTory[:STATe] on page 391 :PLUGin:JTOLerance:RUN:HISTory:CLEar :RUN:HISTory:CLEar page 391...
  • Page 372 SCPI Command Reference :PLUGin:JTOLerance:INSTruments:GENerator[?] Syntax :PLUGin:JTOLerance:INSTruments:GENerator ‘identifier’,<location-string> :PLUGin:JTOLerance:INSTruments:GENerator? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters <location-string>: Specify the location identifier or group name identifier. Return Range <location or group name> Description This command is used to select the pattern generator module/channel for the jitter tolerance measurement.
  • Page 373 SCPI Command Reference :PLUGin:JTOLerance:BSETup:TBERatio[?] Syntax :PLUGin:JTOLerance:BSETup:TBERatio ‘identifier’, <NRf> :PLUGin:JTOLerance:BSETup:TBERatio? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters <NRf>: Set the target BER. Return Range 1E-15 to 1E-1 Description This command is used to set the target BER of the measurement specified by the measurement name identifier.
  • Page 374 SCPI Command Reference :PLUGin:JTOLerance:BSETup:FRTime[?] Syntax :PLUGin:JTOLerance:BSETup:FRTime ‘identifier’, <NRf> :PLUGin:JTOLerance:BSETup:FRTime? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters <NRf>: Set the frequency relax time. Return Range 0 ms to 60 s Description This command is used to set the frequency relax time after a change in jitter modulation frequency for the measurement specified by the measurement name identifier.
  • Page 375 SCPI Command Reference :PLUGin:JTOLerance:MSETup:TEMPlate:FILE[?] Syntax :PLUGin:JTOLerance:MSETup:TEMPlate:FILE ‘identifier’, <filepath-string> :PLUGin:JTOLerance:MSETup:TEMPlate:FILE? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters <filepath-string>: Specify path/filename of template to load. Return Range Path/filename of current measurement template. Description This command is used to specify the path/filename of the measurement template to load for the measurement specified by the measurement name identifier.
  • Page 376 SCPI Command Reference :PLUGin:JTOLerance:MSETup:FREQuency:STOp[?] Syntax :PLUGin:JTOLerance:MSETup:FREQuency:STOp ‘identifier’, <NRf> :PLUGin:JTOLerance:MSETup:FREQuency:STOp? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters <NRf>: Set the stop frequency. Return Range 100 Hz to 500 MHz Description This command is used to set the stop (maximum) modulation frequency for the measurement specified by the measurement name identifier.
  • Page 377 SCPI Command Reference Description This command is used to set the number of measurement points for the measurement specified by the measurement name identifier. This SCPI is applicable for M8041A, M8051A, M8061A, M8062A and M8046A. Example :PLUG:JTOL:MSET:NPO ‘MyMeasurement’, 50 :PLUGin:JTOLerance:MSETup:MODE[?] Syntax :PLUGin:JTOLerance:MSETup:MODE ‘identifier’, <COMPliance|CHARacterize>...
  • Page 378 SCPI Command Reference Description This command is used to specify the compliance margin for the measurement specified by the measurement name identifier. The default is Compliance is used for checking that a device passes the minimum margin required for compliance to a standard. Characterization tests a device for tolerance to jitter to establish the pass/fail amplitude at each measurement point.
  • Page 379 SCPI Command Reference :PLUGin:JTOLerance:MSETup:ALGorithm[?] Syntax :PLUGin:JTOLerance:MSETup:ALGorithm ‘identifier’, <BINary|BDLInear|BULInear|DLINear|DLOGarithmic|ULINear| ULOGarithmic|ULL> :PLUGin:JTOLerance:MSETup:ALGorithm? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters <BINary|BDLInear|BULInear|DLINear|DLOGarithmic|ULINear| ULOGarithmic|ULL>: Specify the measurement algorithm. Return Range BINary|BDLinear|BULinear|DLINear|DLOGarithmic|ULINear|ULOGarithmic| Description This command is used to specify the measurement algorithm during characterization measurements for the measurement specified by the measurement name identifier.
  • Page 380 SCPI Command Reference This algorithm exits when the BER is measured below the measurement threshold BER, or if the last amplitude measurement point was at the minimum jitter value in the template. The jitter tolerance result at each jitter modulation frequency is the highest jitter amplitude at which the measurement was made below the threshold BER.
  • Page 381 SCPI Command Reference This algorithm exits when the BER is measured above the measurement threshold BER, or if the last amplitude measurement point was at the maximum jitter value determined by the template. Up Log + Linear: The Up Log + Linear search algorithm performs the same algorithm as Up Logarithmic, but in addition, it returns to the last passing amplitude and steps linearly up until it reaches a fail point.
  • Page 382 SCPI Command Reference :PLUGin:JTOLerance:MSETup:LINear:SSIZe[?] Syntax :PLUGin:JTOLerance:MSETup:LINear:SSIZe ‘identifier’, <NRf> :PLUGin:JTOLerance:MSETup:LINear:SSIZe? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters <NRf>: Set the step size. Return Range 5 mUI to 100 UI Description This command is used to set the step size for each step of the Up Linear and Down Linear algorithms for the measurement specified by the measurement name identifier.
  • Page 383 SCPI Command Reference :PLUGin:JTOLerance:MSETup:LOG:SSIZe[?] Syntax :PLUGin:JTOLerance:MSETup:LOG:SSIZe ‘identifier’, <NRf> :PLUGin:JTOLerance:MSETup:LOG:SSIZe? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters <NRf>: Set the step size. Return Range 0.1% to 50% Description This command is used to set the step size for each step of the Up Logarithmic and Down Logarithmic algorithms for the measurement specified by the measurement name identifier.
  • Page 384 SCPI Command Reference :PLUGin:JTOLerance:MSETup:CLAuto[?] Syntax :PLUGin:JTOLerance:MSETup:CLAuto ‘identifier’, <ON|OFF|1|0> :PLUGin:JTOLerance:MSETup:CLAuto? ‘identifier’ Input ‘identifier’: ‘Specify the measurement name. Parameters <ON|OFF|1|0>: Enable/disable auto loop bandwidth. Return Range Description This command sets the external CDR loop bandwidth selection during a Jitter Tolerance measurement. If AUTO state is ON, will set the CDR LBW based on the jitter frequency.
  • Page 385 SCPI Command Reference :PLUGin:JTOLerance:GRAPh:TLIMits[?] Syntax :PLUGin:JTOLerance:GRAPh:TLIMits ‘identifier’, <ON|OFF|1|0> :PLUGin:JTOLerance:GRAPh:TLIMits? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters <ON|OFF|1|0>: Enable/disable template limit lines. Return Range Description This command enables/disables the template limits in the graph for the measurement specified by the measurement name identifier. These limits show the search range amplitude (UI) during characterization defined using the template editor in the M8070A software interface.
  • Page 386 SCPI Command Reference :PLUGin:JTOLerance:GRAPh:CLIMits[?] Syntax :PLUGin:JTOLerance:GRAPh:CLIMits ‘identifier’, <ON|OFF|1|0> :PLUGin:JTOLerance:GRAPh:CLIMits? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters <ON|OFF|1|0>: Enable/disable compliance limits. Return Range Description This command enables/disables the compliance limits in the graph for the measurement specified by the measurement name identifier. These limits are defined using the template editor in the M8070A software interface.
  • Page 387 SCPI Command Reference :PLUGin:JTOLerance:BREak Syntax :PLUGin:JTOLerance:BREak ‘identifier’ Input ‘identifier’: Specify the measurement name to break/pause. Parameters Description This command breaks/pauses a measurement addressed by the measurement name identifier. This SCPI is applicable for M8041A, M8051A, M8061A, M8062A and M8046A. Example The following example breaks a jitter tolerance measurement with the measurement name identifier called ‘MyMeasurement’: :PLUG:JTOL:BRE ‘MyMeasurement’...
  • Page 388 SCPI Command Reference :PLUGin:JTOLerance:CONTinue Syntax :PLUGin:JTOLerance:CONTinue ‘identifier’ Input ‘identifier’: Specify the measurement name to continue. Parameters Description This command allows you to continue a jitter tolerance measurement, addressed by the measurement name identifier, that was stopped using the BREak command. This SCPI is applicable for M8041A, M8051A, M8061A, M8062A and M8046A.
  • Page 389 SCPI Command Reference :PLUGin:JTOLerance:DELete Syntax :PLUGin:JTOLerance:DELete ‘identifier’ Input ‘identifier’: Specify the measurement name to delete. Parameters Description This command deletes a previously created jitter tolerance measurement addressed by the measurement name identifier. This SCPI is applicable for M8041A, M8051A, M8061A, M8062A and M8046A.
  • Page 390 SCPI Command Reference :PLUGin:JTOLerance:STARt Syntax :PLUGin:JTOLerance:STARt ‘identifier’ Input ‘identifier’: Specify the measurement name to start. Parameters Description This command starts a jitter tolerance measurement addressed by the measurement name identifier. This SCPI is applicable for M8041A, M8051A, M8061A, M8062A and M8046A.
  • Page 391 SCPI Command Reference This SCPI is applicable for M8041A, M8051A, M8061A, M8062A and M8046A. Example The following example triggers a single jitter tolerance measurement step of the measurement addressed with the measurement name identifier called ‘MyMeasurement’: :PLUG:JTOL:STEP ‘MyMeasurement’ :PLUGin:JTOLerance:RUN:HISTory[:STATe][?] Syntax :PLUGin:JTOLerance:RUN:HISTory[:STATe] ‘identifier’,<0|1>...
  • Page 392 SCPI Command Reference :PLUGin:JTOLerance:RUN:LOG? Syntax :PLUGin:JTOLerance:RUN:LOG? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters Description This command returns logs for the addressed measurement. This SCPI is applicable for M8041A, M8051A, M8061A, M8062A and M8046A. Example The following example returns logs for the measurement name identifier called ‘MyMeasurement’: :PLUG:JTOL:RUN:LOG? ‘MyMeasurement’...
  • Page 393 SCPI Command Reference :PLUGin:JTOLerance:RUN:PROGress? Syntax :PLUGin:JTOLerance:RUN:PROGress? ‘identifier’ Input ‘identifier’: Specify measurement name. Parameters Return Range 0.0 to 1.0 Description This command returns a number in the range of 0.0 to 1.0 to indicate the progress of a jitter tolerance measurement addressed by the measurement name identifier.

  • Page 394: Plugin:ediagram Subnode

    SCPI Command Reference :PLUGin:EDIagram Subnode The M8070A system software provides quick design analysis with the eye diagram capability. The measurement allows a quick check for the DUT’s signal output and determines the signal quality. The eye contour lines display the measured eye at a deeper BER level, for accurate results. The eye diagram generates a three dimensional graph of the bit error rate (BER).

  • Page 395: Plugin:ediagram:acquisition Subnode

    SCPI Command Reference This subnode has the following commands and subnodes: Table 77 Name Description under :PLUGin:EDIagram:BREak :BREak on page 396 :PLUGin:EDIagram:CATalog? :CATalog? on page 396 :PLUGin:EDIagram:CONTinue :CONTinue on page 396 :PLUGin:EDIagram:DELete :DELete on page 397 :PLUGin:EDIagram:NEW :NEW on page 397 :PLUGin:EDIagram:RESet :RESet on page 398...
  • Page 396 SCPI Command Reference :PLUGin:EDIagram:BREak Syntax :PLUGin:EDIagram:BREak ‘identifier’ Input ‘identifier’: Specify the measurement name to break/pause. Parameters Description This command breaks/pauses a measurement addressed by the measurement name identifier. This SCPI is applicable for M8041A, M8051A and M8062A. Example The following example breaks an eye diagram measurement with the measurement name identifier called ‘MyMeasurement’: :PLUG:EDI:BRE ‘MyMeasurement’...
  • Page 397 SCPI Command Reference :PLUGin:EDIagram:DELete Syntax :PLUGin:EDIagram:DELete ‘identifier’ Input ‘identifier’: Specify the measurement name to delete. Parameters Description This command deletes a previously created eye diagram measurement addressed by the measurement name identifier. This SCPI is applicable for M8041A, M8051A and M8062A. Example The following example deletes an eye diagram measurement addressed by the measurement name identifier called ‘MyMeasurement’:...
  • Page 398 SCPI Command Reference :PLUGin:EDIagram:RESet Syntax :PLUGin:EDIagram:RESet ‘identifier’ Input ‘identifier’: Specify the measurement name to reset. Parameters Description This command resets an eye diagram measurement addressed by the measurement name identifier. This SCPI is applicable for M8041A, M8051A and M8062A. Example The following example resets an eye diagram measurement addressed with the measurement name identifier called ‘MyMeasurement’: :PLUG:EDI:RES ‘MyMeasurement’...
  • Page 399 SCPI Command Reference Example The following example triggers a single eye diagram measurement step of the measurement addressed with the measurement name identifier called ‘MyMeasurement’: :PLUG:EDI:STEP ‘MyMeasurement’ :PLUGin:EDIagram:STOP Syntax :PLUGin:EDIagram:STOP ‘identifier’ Input ‘identifier’: Specify the measurement name to stop. Parameters Description This command stops an eye diagram measurement addressed by the measurement name identifier.
  • Page 400 SCPI Command Reference :PLUGin:EDIagram:ACQuisition Subnode This subnode has the following SCPI structure: :ACQuisition :ALOCation[?] :NEYEs[?] :PERSistence[?] :TIME[?] This subnode has the following commands: Table 78 Name Description under :PLUGin:EDIagram:ACQuisition:ALOCation[?] :ALOCation[?] page 401 :PLUGin:EDIagram:ACQuisition:NEYEs[?] :NEYEs[?] page 401 :PLUGin:EDIagram:ACQuisition:PERSistence [?] :PERSistence[?] page 402 :PLUGin:EDIagram:ACQuisition:TIME[?] :TIME[?] on page 402...
  • Page 401 SCPI Command Reference :PLUGin:EDIagram:ACQuisition:ALOCation[?] Syntax :PLUGin:EDIagram:ACQuisition:ALOCation 'Identifier', < location-string> :PLUGin:EDIagram:ACQuisition:ALOCation? 'Identifier' Input Identifier: 'ParameterSweep1' Parameters <location-string>: ‘M*.DataIn*’ Description This command sets the location/location group string against which the data acquisition is performed. This query returns the current location/location group string against which measurement is configured for the data acquisition.
  • Page 402 SCPI Command Reference :PLUGin:EDIagram:ACQuisition:PERSistence[?] Syntax :PLUGin:EDIagram:ACQuisition:PERSistence 'Identifier', <INF | FTIM> :PLUGin:EDIagram:ACQuisition:PERSistence? 'Identifier', Input Identifier: 'MyMeasurement' Parameters Return Range INF | FTIM Description This command sets the criteria for persistence. Persistence could be infinite or fixed time. The query returns the current setting. This SCPI is applicable for M8041A, M8051A and M8062A.
  • Page 403 SCPI Command Reference :PLUGin:EDIagram:EVALuation Subnode This subnode has the following SCPI structure: :EVALuation :BERThresh[?] :BERThresh:THReshold[?] :TTIME[?] This subnode has the following commands: Table 79 Name Description under :PLUGin:EDIagram:EVALuation:BERThresh[ :BERThresh[?] on page 403 :PLUGin:EDIagram:EVALuation:BERThresh: :BERThresh:THReshold[?] THReshold[?] on page 404 :PLUGin:EDIagram:EVALuation:TTIMe[?] :TTIMe[?] page 404 :PLUGin:EDIagram:EVALuation:BERThresh[?] Syntax...
  • Page 404 SCPI Command Reference threshold is specified with the :PLUGin:EDIagram:EVALuation:BERThresh:THReshold[?] on page 404 command. The query returns either 0 errors (ZERR) or BER threshold (BTHR). This SCPI is applicable for M8041A, M8051A and M8062A. Example :PLUG:EDI:EVAL:BERT 'MyMeasurement', BTHR :PLUGin:EDIagram:EVALuation:BERThresh:THReshold[?] Syntax :PLUGin:EDIagram:EVALuation:BERThreshold 'Identifier', <NRf> :PLUGin:EDIagram:EVALuation:BERThreshold? 'Identifier' Input Identifier: 'MyMeasurement'...
  • Page 405 SCPI Command Reference :PLUGin:EDIagram:FETCh[:RESult] Subnode This subnode has the following SCPI structure: :FETCh [:RESult] :AMPLitude? :CVOLtage? :DCDistortion? :FALLtime? :HEIGht? :HILevel? :JPPeak? :JRMSquare? :LOLevel? :RISetime? :SCOunt? :SNRatio? :WIDTh? This subnode has the following commands and subnodes: Table 80 Name Description under :PLUGin:EDIagram:FETCh[:RESult]:AMPLitude? AMPLitude? page 406...
  • Page 406 SCPI Command Reference Name Description under :PLUGin:EDIagram:FETCh[:RESult]:HEIGht? :HEIGht? on page 408 :PLUGin:EDIagram:FETCh[:RESult]:HILevel? :HILevel? page 408 :PLUGin:EDIagram:FETCh[:RESult]:JPPeak? :JPPeak? page 408 :PLUGin:EDIagram:FETCh[:RESult]:JRMSquare? :JRMSquare? page 409 :PLUGin:EDIagram:FETCh[:RESult]:LOLevel? :LOLevel? page 409 :PLUGin:EDIagram:FETCh[:RESult]:RISetime? :RISetime? page 409 :PLUGin:EDIagram:FETCh[:RESult]:SCOunt? :SCOunt? page 410 :PLUGin:EDIagram:FETCh[:RESult]:SNRatio? :SNRatio? page 410 :PLUGin:EDIagram:FETCh[:RESult]:WIDTh? :WIDTh? on page 410 :PLUGin:EDIagram:FETCh[:RESult]:AMPLitude?
  • Page 407 SCPI Command Reference :PLUGin:EDIagram:FETCh[:RESult]:CVOLtage? Syntax :PLUGin:EDIagram:FETCh[:RESult]:CVOLtage? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters Description This command returns the cross voltage which is the measurement of the crossing point level in relation to the logic 1 level and logic 0 level. This SCPI is applicable for M8041A, M8051A and M8062A.
  • Page 408 SCPI Command Reference :PLUGin:EDIagram:FETCh[:RESult]:HEIGht? Syntax :PLUGin:EDIagram:FETCh[:RESult]:HEIGht? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters Description This command returns the value of the eye height which is a measurement of the vertical opening of an eye diagram. This opening is affected by the BER threshold that is set by the BER threshold command.
  • Page 409 SCPI Command Reference :PLUGin:EDIagram:FETCh[:RESult]:JRMSquare? Syntax :PLUGin:EDIagram:FETCh[:RESult]:JRMSquare? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters Description This command returns the Jitter Root-Mean Square value. It is the standard deviation of the normal distribution of random jitter. It is dependent on the BER Threshold. This SCPI is applicable for M8041A, M8051A and M8062A.
  • Page 410 SCPI Command Reference :PLUGin:EDIagram:FETCh[:RESult]:SCOunt? Syntax :PLUGin:EDIagram:FETCh[:RESult]:SCOunt? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters Description This command returns the sample count. This SCPI is applicable for M8041A, M8051A and M8062A. Example :PLUG:EDI:FETC:SCO? ‘MyMeasurement’ :PLUGin:EDIagram:FETCh[:RESult]:SNRatio? Syntax :PLUGin:EDIagram:FETCh[:RESult]:SNRatio? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters Description This command returns signal-to-noise ratio which is a measurement of the...

  • Page 411: Plugin:ediagram:run Subnode

    SCPI Command Reference :PLUGin:EDIagram:RUN Subnode This subnode has the following SCPI structure: :RUN :MESSage? :PROGress? :STATus? :HISTory [:STATe][?] :CLEar :LOG? This subnode has the following commands: Table 81 Name Description under :PLUGin:EDIagram:RUN:MESSage? :MESSage? page 412 :PLUGin:EDIagram:RUN:PROGress? :PROGress? page 412 :PLUGin:EDIagram:RUN:STATus? :STATus? on page 412 :PLUGin:EDIagram:RUN:HISTory[:STATe][?]...
  • Page 412 SCPI Command Reference :PLUGin:EDIagram:RUN:MESSage? Syntax :PLUGin:EDIagram:RUN:MESSage? 'Identifier' Input Identifier: 'MyMeasurement' Parameters Description This command returns a string describing the state of an eye diagram measurement addressed by the measurement name identifier. Possible states include Not Started, Running, Suspended, Finished, Error, or Stopped.
  • Page 413 SCPI Command Reference :PLUGin:EDIagram:RUN:HISTory[:STATe][?] Syntax :PLUGin:EDIagram:RUN:HISTory[:STATe] 'Identifier', <0|1|ON|OFF> :PLUGin:EDIagram:RUN:HISTory[:STATe]? 'Identifier' Input Identifier: 'MyMeasurement' Parameters Return Range Description This command enables/disables the storage of eye diagram measurement results addressed by the measurement name identifier. This query returns the current setting. This SCPI is applicable for M8041A, M8051A and M8062A. Example :PLUG:EDI:RUN:HIST 'MyMeasurement', 1 :PLUGin:EDIagram:RUN:HISTory:CLEar...

  • Page 414: Plugin:ediagram:show Subnode

    SCPI Command Reference characters in the log then followed by the log message. For example: #10 means, there is 1 digit after 1 and there is 0 character in the log. #2492 means, there are 3 digits after 2 and there are 492 characters in the log message.
  • Page 415 SCPI Command Reference :PLUGin:EDIagram:SHOW:CONTour[?] Syntax :PLUGin:EDIagram:SHOW:CONTour 'Identifier', <0|1|ON|OFF> :PLUGin:EDIagram:SHOW:CONTour? 'Identifier' Input Identifier: 'MyMeasurement' Parameters Return Range Description This command shows/hides the contour lines on the graph. This query returns the current setting. This SCPI is applicable for M8041A, M8051A and M8062A. Example :PLUG:EDI:SHOW:CONT 'MyMeasurement', 1 :PLUGin:EDIagram:SHOW:CONTour:LEGend[?]...
  • Page 416 SCPI Command Reference This query returns the current setting. This SCPI is applicable for M8041A, M8051A and M8062A. Example :PLUG:EDI:SHOW:UNIT 'MyMeasurement', UNIT :PLUGin:EDIagram:SHOW:WAVeform[?] Syntax :PLUGin:EDIagram:SHOW:WAVeform 'Identifier', <0|1|OFF|ON> :PLUGin:EDIagram:SHOW:WAVeform? 'Identifier' Input Identifier: 'MyMeasurement' Parameters <0|1|OFF|ON>: Show/hide waveform Return Range Description This command shows/hides the waveform. When this feature is enabled, the waveform is displayed together with the contour lines.
  • Page 417 SCPI Command Reference :PLUGin:EDIagram:SHOW:WAVeform:THReshold[?] Syntax :PLUGin:EDIagram:SHOW:WAVeform:THReshold 'Identifier', <NR3> :PLUGin:EDIagram:SHOW:WAVeform:THReshold? 'Identifier' Input Identifier: 'MyMeasurement' Parameters Return Range 1E-6 to 1E-1 Description This command sets the waveform BER threshold value. This query returns the current setting. This SCPI is applicable for M8041A, M8051A and M8062A Example :PLUG:EDI:SHOW:WAV:THR 'MyMeasurement', 1E-3 Keysight M8070A Programming Guide...

  • Page 418: Plugin:psweep Subnode

    SCPI Command Reference :PLUGin:PSWEep Subnode The Parameter Sweep plugin allows you to sweep the parameters of the selected location/location group to the desired analyzer in order to calculate BER. This is helpful in scenarios when a user wants to pick a property to sweep within a specified range with specified steps and measure BER with respect to that sweep.

  • Page 419: Plugin:psweep:acquisition Subnode

    SCPI Command Reference This subnode has the following commands and subnodes: Table 83 Name Description under :PLUGin:PSWEep:CATalog? :CATalog? on page 419 :PLUGin:PSWEep:DELete :DELete on page 420 :PLUGin:PSWEep:FETCh:DATA? FETCh:DATA? on page 420 :PLUGin:PSWEep:GRAPh? GRAPh? on page 421 :PLUGin:PSWEep:NEW :NEW on page 422 :PLUGin:PSWEep:RESet :RESet on page 423...

  • Page 420: Plugin:psweep:delete

    SCPI Command Reference :PLUG:PSWE:NEW ‘ParameterSweep3’ The command and returned list would look like the following: :PLUG:PSWE:CAT? “ParameterSweep1”,”ParameterSweep2”,”ParameterSweep3” :PLUGin:PSWEep:DELete Syntax :PLUGin:PSWEep:DELete ‘identifier’ Input ‘Identifier’: Specify the plugin name. For e.g. ‘ParameterSweep1’ Parameters Description This command deletes a previously created parameter sweep measurement addressed by the measurement name identifier.

  • Page 421: Plugin:psweep:graph

    SCPI Command Reference separated list for each measurement point are Sweep Value, Error Ratio, Compared Bits, Errored Bits, Errored Zero Ratio, Compared Zeros, Errored Zeros, Error One Ratio, Compared Ones and Errored Ones are repeated in the same order for subsequent measured points. If the location is omitted from the above example e.g.

  • Page 422: Plugin:psweep:new

    SCPI Command Reference :PLUGin:PSWEep:NEW Syntax :PLUGin:PSWEep:NEW ‘identifier’ Input ‘Identifier’: Specify the plugin name. For e.g. ‘ParameterSweep1’ Parameters Description This command creates a new parameter sweep measurement name identifier. This SCPI is applicable for M8041A, M8051A, M8061A, M8062A, M8045A and M8046A. Example The following example creates a parameter sweep measurement name identifier called ‘ParameterSweep1’:...

  • Page 423: Plugin:psweep:reset

    SCPI Command Reference :PLUGin:PSWEep:RESet Syntax :PLUGin:PSWEep:RESet ‘identifier’ Input ‘Identifier’: Specify the plugin name. For e.g. ‘ParameterSweep1’ Parameters Description This command resets a parameter sweep measurement addressed by the measurement name identifier. This SCPI is applicable for M8041A, M8051A, M8061A, M8062A, M8045A and M8046A.
  • Page 424 SCPI Command Reference Example The following example stops a parameter sweep measurement with the measurement name identifier called ‘ParameterSweep1’: :PLUG:PSWE:STOP ‘ParameterSweep1’ :PLUGin:PSWEep:ACQuisition Subnode This subnode has the following SCPI structure: :ACQuisition :ALOCation[?] :COMPared[?] :SFRom[?] :SLOCation[?] :SMODe[?] :SRTime[?] :STEP[?] :STO[?] :SWPArameter[?] Keysight M8070A Programming Guide...
  • Page 425 SCPI Command Reference This subnode has the following commands: Table 84 Name Description under :PLUGin:PSWEep:ACQuisition:ALOCation[?] :ALOCation[?] page 426 :PLUGin:PSWEep:ACQuisition:SLOCation[?] SLOCation[?] page 426 :PLUGin:PSWEep:ACQuisition:SWPArameter[?] :SWPArameter[?] page 427 :PLUGin:PSWEep:ACQuisition:SMODe[?] ::SMODe[?] page 427 :PLUGin:PSWEep:ACQuisition:SRTime[?] :SRTime[?] page 428 :PLUGin:PSWEep:ACQuisition:SFRom [?] :SFRom[?] page 428 :PLUGin:PSWEep:ACQuisition:STO[?] :STO[?] on page 428 :PLUGin:PSWEep:ACQuisition:STEP[?]...
  • Page 426 SCPI Command Reference :PLUGin:PSWEep:ACQuisition:ALOCation[?] Syntax :PLUGin:PSWEep:ACQuisition:ALOCation 'Identifier', <location-string> :PLUGin:PSWEep:ACQuisition:ALOCation? 'Identifier' Input ‘Identifier’: Specify the plugin name. For e.g. ‘ParameterSweep1’ Parameters <location-string>: ‘M*.DataIn*’ Description This command sets the location or location group string against which the data acquisition is performed. This query returns the current location or location group string against which measurement is configured for the data acquisition.
  • Page 427 SCPI Command Reference :PLUGin:PSWEep:ACQuisition:SWPArameter[?] Syntax :PLUGin:PSWEep:ACQuisition:SWPArameter 'Identifier', <Sweep-Parameter> :PLUGin:PSWEep:ACQuisition:SWPArameter? 'Identifier' Input ‘Identifier’: Specify the plugin name. For e.g. ‘ParameterSweep1’ Parameters <Sweep-Parameter>: Specify the sweep parameter present in current location or group. Description This command sets the sweep parameter to be swept amongst the list of other parameters present in current location or group.
  • Page 428 SCPI Command Reference :PLUGin:PSWEep:ACQuisition:SRTime[?] Syntax :PLUGin:PSWEep:ACQuisition:SRTime 'Identifier', <NRf> :PLUGin:PSWEep:ACQuisition:SRTime? 'Identifier' Input ‘Identifier’: Specify the plugin name. For e.g. ‘ParameterSweep1’ Parameters Description This command sets the relaxing time between the sweep before reading the BER. The relaxing time can be between 0 sec to 60 sec. This query returns the current set relaxing time.
  • Page 429 SCPI Command Reference Description This command sets the value till the sweep needs to be performed for that particular parameter. This query returns the current sweep value till the sweep is performed. This SCPI is applicable for M8041A, M8051A, M8061A, M8062A, M8045A and M8046A.
  • Page 430 SCPI Command Reference :PLUGin:PSWEep:RUN Subnode This subnode has the following SCPI structure: :RUN :MESSage? :PROGress? :STATus? :HISTory [:STATe][?] :CLEar :LOG? This subnode has the following commands: Table 85 Name Description under :PLUGin:PSWEep:RUN:MESSage? :MESSage? page 431 :PLUGin:PSWEep:RUN:PROGress? :PROGress? page 431 :PLUGin:PSWEep:RUN:STATus? :STATus? on page 431 :PLUGin:PSWEep:RUN:HISTory[:STATe][?]...
  • Page 431 SCPI Command Reference :PLUGin:PSWEep:RUN:MESSage? Syntax :PLUGin:PSWEep:RUN:MESSage? 'Identifier' Input ‘Identifier’: Specify the plugin name. For e.g. ‘ParameterSweep1’ Parameters Description This command returns a string describing the state of the parameter sweep addressed by the measurement name identifier. Possible states include; Not Started, Running, Suspended, Finished, Error, or Stopped. This SCPI is applicable for M8041A, M8051A, M8061A, M8062A, M8045A and M8046A.
  • Page 432 SCPI Command Reference the measurement is not running and a 1 indicates the measurement is running. This SCPI is applicable for M8041A, M8051A, M8061A, M8062A, M8045A and M8046A. Example :PLUG:PSWE:RUN:STAT? 'ParameterSweep1' :PLUGin:PSWEep:RUN:HISTory[:STATe][?] Syntax :PLUGin:PSWEep:RUN:HISTory[:STATe] 'Identifier', <0|1|ON|OFF> :PLUGin:PSWEep:RUN:HISTory[:STATe]? 'Identifier' Input ‘Identifier’: Specify the plugin name. For e.g. ‘ParameterSweep1’ Parameters Return Range Description...
  • Page 433 SCPI Command Reference :PLUGin:PSWEep:RUN:LOG? Syntax :PLUGin:PSWEep:RUN:LOG? 'Identifier' Input ‘Identifier’: Specify the plugin name. For e.g. ‘ParameterSweep1’ Parameters Description This command returns logs for the addressed measurement. This SCPI is applicable for M8041A, M8051A, M8061A, M8062A, M8045A and M8046A. Example :PLUG:PSWE:RUN:LOG? 'ParameterSweep1' The format of log returned is in the following way: #XY Message Log where X denotes the length of digits for Y, Y denotes the number of...
  • Page 434 SCPI Command Reference :PLUGin:PSWEep:SHOW Subnode This subnode has the following SCPI structure: :SHOW :SGLegends[?] :SMPoints[?] :VSCale[?] This subnode has the following commands: Table 86 Name Description under :PLUGin:PSWEep:SHOW:SGLegends[?] :SGLegends on page 434 :PLUGin:PSWEep:SHOW:SMPoints[?] :SMPoints on page 435 :PLUGin:PSWEep:SHOW:VSCale[?] :VSCale on page 435 :PLUGin:PSWEep:SHOW:SGLegends[?] Syntax :PLUGin:PSWEep:SHOW:SGLegends 'Identifier', <0|1|ON|OFF>...
  • Page 435 SCPI Command Reference :PLUGin:PSWEep:SHOW:SMPoints[?] Syntax :PLUGin:PSWEep:SHOW:SMPoints 'Identifier', <0|1|ON|OFF> :PLUGin:PSWEep:SHOW:SMPoints? 'Identifier' Input Identifier: Specify the plugin name. For e.g. 'ParameterSweep1' Parameters <OFF|ON|0|1>: Disable/enable viewing the measurement points. Return Range Description This command disables/enables viewing of the measurement points in the GUI and associates it with a specific measurement name identifier. A 0 or OFF value disables viewing and a 1 or ON value enables viewing of the measurement points.

  • Page 436: Plugin:ccapture Subnode

    SCPI Command Reference :PLUGin:CCAPture Subnode The M8020A/M8030A Analyzer captures the data received from the device under test. The captured data bits are displayed in the pattern capture pan in binary or 8b/10b symbol coding. The received data is compared with the expected data and the errored bits/symbols are highlighted.

  • Page 437: Plugin:ccapture:fetch Subnode

    SCPI Command Reference This subnode has the following commands and subnodes: Table 87 Name Description under :PLUGin:CCAPture:CATalog? :CATalog? on page 438 :PLUGin:CCAPture:DELete DELete[?] on page 439 :PLUGin:CCAPture:NEW NEW[?] on page 439 :PLUGin:JTOLerance:RESet RESet[?] on page 389 :PLUGin:CCAPture:STARt STARt[?] on page 440 :PLUGin:CCAPture:STOP STOP[?] on page 440...
  • Page 438 SCPI Command Reference :PLUGin:CCAPture:CATalog? Syntax :PLUGin:CCAPture:CATalog? Description This command returns a list of all created compare and capture measurement names currently available for measuring. This SCPI is applicable for M8041A and M8051A. Example Assume the following is a list of created compare and capture measurement names: :PLUG:CCAP:NEW ‘CCAP_1’...
  • Page 439 SCPI Command Reference :PLUGin:CCAPture:DELete Syntax :PLUGin:CCAPture:DELete ‘identifier’ Input ‘identifier’: Specify the measurement name to delete. Parameters Description This command deletes a previously created compare and capture measurement addressed by the measurement name identifier. This SCPI is applicable for M8041A and M8051A. Example The following example deletes a compare and capture measurement addressed by the measurement name identifier called ‘MyMeasurement’:...
  • Page 440 SCPI Command Reference :PLUGin:CCAPture:STARt Syntax :PLUGin:CCAPture:STARt ‘identifier’ Input identifier’: Specify the measurement name to start. Parameters Description This command starts a compare and capture measurement addressed by the measurement name identifier. This SCPI is applicable for M8041A and M8051A. Example The following example starts a compare and capture measurement addressed with the measurement name identifier called ‘MyMeasurement’: :PLUG:CCAP:STAR ‘MyMeasurement’...
  • Page 441 SCPI Command Reference [,<overwrite-flag>]: ON | OFF | 0 | 1 Optional flag is a boolean parameter which specifies if an existing pattern file should be overwritten or not. Description The currently uploaded pattern is stored into the specified file on the hard disk.
  • Page 442 SCPI Command Reference :PLUGin:CCAPture:SHOW:SYMBol[:PATTern][:VIEW][?] Syntax :PLUGin:CCAPture:SHOW:SYMBol:PATTern:VIEW 'identifier', ‘Mode’ :PLUGin:CCAPture:SHOW:SYMBol:PATTern:VIEW? 'identifier' Input ‘identifier’: Specify the measurement name. Parameters ‘Mode’: BIN|HEX|SYMBol Return Range BIN|HEX|SYMBol Description This command selects 8/10 bit pattern view mode viz. BIN|HEX|SYMBol. This SCPI is applicable for M8041A and M8051A. Example :PLUGin:CCAPture:SHOW:SYMBol:PATTern:VIEW 'MyMeasurement', BIN Keysight M8070A Programming Guide...
  • Page 443 SCPI Command Reference :PLUGin:CCAPture:FETCh Subnode This subnode has the following SCPI structure: :FETCh :ERRor :COUNt :PATTern :DATA :HOLDoff? :DEPTh? :ERRor :SYMBol :FIRSt? :LAST? :RUN [:STATus]? Keysight M8070A Programming Guide...
  • Page 444 SCPI Command Reference This subnode has the following commands: Table 88 Name Description under :PLUGin:CCAPture:FETCh:ERRor:COUNt? :ERRor:COUNt? on page 444 :PLUGin:CCAPture:FETCh:PATTern[:DATA :PATTern:DATA:HOLDoff? ]:HOLDoff? on page 445 :PLUGin:CCAPture:FETCh:PATTern[:DATA :PATTern:DATA:DEPTh? ]:DEPTh? on page 445 :PLUGin:CCAPture:FETCh:PATTern:ERRor :PATTern:ERRor:SYMBol:FIRSt? :SYMBol:FIRSt? on page 446 :PLUGin:CCAPture:FETCh:PATTern:ERRor :PATTern:ERRor:SYMBol:LAST? :SYMBol:LAST? on page 446 :PLUGin:CCAPture:FETCh:RUN[:STATus]? :RUN[:STATus]?
  • Page 445 SCPI Command Reference :PLUGin:CCAPture:FETCh:PATTern[:DATA]:HOLDoff? Syntax :PLUGin:CCAPture:FETCh:PATTern[:DATA]:HOLDoff? 'identifier' [,‘Location’] Input identifier: ‘Name of Measurement’ Parameters [,‘Location’]: ‘M*.DataIn1’ or ‘M*.DataIn2’ Description This command returns the actual holdoff i.e. number of data bits captured before the trigger event. Returned value of this query is only valid when capture measurement is finished.
  • Page 446 SCPI Command Reference :PLUGin:CCAPture:FETCh:PATTern:ERRor:SYMBol:FIRSt? Syntax :PLUGin:CCAPture:FETCh:PATTern:ERRor:SYMBol:FIRSt? 'identifier' [,‘Location’] Input identifier: ‘Name of Measurement’ Parameters [,‘Location’]: ‘M*.DataIn1’ or ‘M*.DataIn2’ Description This command fetches the first error symbol. This SCPI is applicable for M8041A and M8051A. Example :PLUGin:CCAPture:FETCh:PATTern:ERRor:SYMBol:FIRSt? 'MyMeasurement',‘M1.DataIn1’ Return: (“M1.DataIn1”, ...) :PLUGin:CCAPture:FETCh:PATTern:ERRor:SYMBol:LAST? Syntax :PLUGin:CCAPture:FETCh:PATTern:ERRor:SYMBol:LAST? 'identifier'...
  • Page 447 SCPI Command Reference :PLUGin:CCAPture:FETCh:RUN[:STATus]? Syntax :PLUGin:CCAPture:FETCh:RUN[:STATus]? 'identifier' [,‘Location’] Input identifier: ‘Name of Measurement’ Parameters [,‘Location’]: ‘M*.DataIn1’ or ‘M*.DataIn2’ Description This command returns the capture measurement status for each analyzer location. Returned value can be any of the following: STOP: Capture measurement is stopped or not currently running. No valid data is available in capture memory.
  • Page 448 SCPI Command Reference :PLUGin:CCAPture:ACQuisition Subnode This subnode has the following SCPI structure: :ACQuisition :ALOCation :DEPTh :HOLDoff :SOURce :SLOPe This subnode has the following commands: Table 89 Name Description under :PLUGin:CCAPture:ACQuisition:ALOCatio :ALOCation[?] n[?] on page 449 :PLUGin:CCAPture:ACQuisition:DEPTh[?] :DEPTh[?] on page 449 :PLUGin:CCAPture:ACQuisition:HOLDoff[ :HOLDoff[?] on page 449...
  • Page 449 SCPI Command Reference :PLUGin:CCAPture:ACQuisition:ALOCation[?] Syntax :PLUGin:CCAPture:ACQuisition:LOCation ‘identifier’,'Location' :PLUGin:CCAPture:ACQuisition:LOCation? ‘identifier’ Input identifier: ‘Name of Measurement’ Parameters ‘Location’: ‘M*.DataIn1’ or ‘M*.DataIn2’ Description Specified the location the compare & capture measurement cooperates with. Examples for a location are 'M1.DataIn1', 'M3.DataIn2',… or a name of an existing group of DataIns.
  • Page 450 SCPI Command Reference This SCPI is applicable for M8041A and M8051A. Example :PLUGin:CCAPture:ACQuisition:HOLDoff ‘My Measurement’, 1 :PLUGin:CCAPture:ACQuisition:SOURce[?] Syntax :PLUGin:CCAPture:ACQuisition:SOURce ‘identifier’,<CINA | CINB | ERRor I IMM> :PLUGin:CCAPture:ACQuisition:SOURce? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters <CINA | CINB | ERRor | IMM> Return Range CINA | CINB | ERRor | IMM Description...
  • Page 451 SCPI Command Reference :PLUGin:CCAPture:RUN Subnode This subnode has the following SCPI structure: :RUN :MESSage? :PROGress? :STATus? :LOG? This subnode has the following commands: Table 90 Name Description under :PLUGin:CCAPture:RUN:MESSage? :MESSage? page 452 :PLUGin:CCAPture:RUN:PROGress? :PROGress? page 452 :PLUGin:CCAPture:RUN:STATus? :STATus? page 453 :PLUGin:CCAPture:RUN:LOG? LOG? on page 453...
  • Page 452 SCPI Command Reference :PLUGin:CCAPture:RUN:MESSage? Syntax :PLUGin:CCAPture:RUN:MESSage? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters Description This command returns a string describing the state of the compare & capture measurement. Possible states include NotStarted, Running, Stopped and Triggered. This SCPI is applicable for M8041A and M8051A. Example The following example returns the state of a compare and capture measurement with the measurement name identifier called...
  • Page 453 SCPI Command Reference :PLUGin:CCAPture:RUN:STATus? Syntax :PLUGin:CCAPture:RUN:STATus? ‘identifier’ Input ‘identifier’: Specify the measurement name. Parameters Return Range Description This command returns the running status of the compare & capture measurement. A 0 indicates the measurement is not running and a 1 indicates the measurement is running.

  • Page 454: System Subsystem

    SCPI Command Reference SYSTem Subsystem The SYSTem subsystem is used for general system functions. This subsystem has the following SCPI structure: :SYSTem :INSTrument :RESet :GROup :DEFine :DELete :MEMBer? [:LIST]? :LTRaining [:LOG]? [:LOG] :CLEar :BLOCk :EQUalization [:STATus]? :INFormation [:INSTrument] :IDENtifier? :LOCations? :GROups :USER? :LICenses...
  • Page 455 SCPI Command Reference This subsystem has the following commands: Table 91 Name Description under :SYSTem:INSTrument:RESet :INSTrument:RESet on page 457 :SYSTem:INSTrument:GROup:DEFine :INSTrument:GROup:DEFine page 457 :SYSTem:INSTrument:GROup:DELete :INSTrument:GROup:DELete page 457 :SYSTem:INSTrument:GROup:MEMBer? :INSTrument:GROup:MEMBer? page 458 :SYSTem:INSTrument:GROup[:LIST]? :INSTrument:GROup[:LIST]? page 458 :SYSTem:INSTrument:LTRaining[:LOG]? :INSTrument:LTRaining[:LOG]? page 459 :SYSTem:INSTrument:LTRaining[:LOG]:CLE :INSTrument:LTRaining[:LOG]:CLEar on page 460 :SYSTem:INSTrument:LTRaining[:LOG]:BLO...
  • Page 456 SCPI Command Reference Name Description under :SYSTem:DCINterface[:PROGram]:UNLoad :DCINterface[:PROGram]:UNLoad on page 465 :SYSTem:DCINterface[:PROGram]:SELecte :DCINterface[:PROGram]:SELected? on page 466 :SYSTem:DCINterface:EXEcute[:INIT] :DCINterface:EXEcute[:INIT] page 466 :SYSTem:DCINterface:DEVice:CONNect[?] :DCINterface:DEVice:CONNect on page 467 :SYSTem:DCINterface:DEVice:MODE[?] :DCINterface:DEVice:MODE page 468 :SYSTem:DCINterface:LANE:MODE[?] :DCINterface:LANE:MODE page 469 :SYSTem:RESet[:ALL] :RESet[:ALL] on page 470 :SYSTem:RESet:INSTrument :RESet:INSTrument on page 470 Keysight M8070A Programming Guide...
  • Page 457 SCPI Command Reference :SYSTem:INSTrument:RESet Syntax :SYSTem:INSTrument:RESet Description This command resets the instrument state to its default values. This command does not influence the SCPI status system as *RST does. Example :SYST:INST:RES :SYSTem:INSTrument:GROup:DEFine Syntax :SYSTem:INSTrument:GROup:DEFine ’GroupName’,‘identifier’,‘identifier’,‘identifier’,‘...’ Input ‘GroupName’: Assign a name to this group of location identifiers. Parameters ‘identifier’: Define the group of location identifiers.
  • Page 458 SCPI Command Reference :SYSTem:INSTrument:GROup:MEMBer? Syntax :SYSTem:INSTrument:GROup:MEMBer? ‘GroupName’ Input ‘GroupName’: Specify group name. Parameters Description This command returns the comma separated list of member names contained within the specified group. Example :SYST:INST:GRO:MEMB? ‘Outputs’ “M1.DataOut1”,“M1.DataOut2” :SYSTem:INSTrument:GROup[:LIST]? Syntax :SYSTem:INSTrument:GROup[:LIST]? Description This command returns a comma separated list of all group names. Example :SYST:INST:GRO? “Outputs”...
  • Page 459 SCPI Command Reference :SYSTem:INSTrument:LTRaining[:LOG]? Syntax :SYSTem:INSTrument:LTRaining[:LOG]? Description This command returns accumulated Link Training logs for the selected DataOut locations in text format. Example :SYST:INST:LTR:LOG? Link Training Logging for M1.DataOut1 at 5/4/2015 12:42:36 PM State Execution Time Detect.Active 1.04864 ms Polling.Active 2.064992 ms Polling.Configuration 152.112 us...

  • Page 460: System:instrument:ltraining[:Log]:Clear

    SCPI Command Reference :SYSTem:INSTrument:LTRaining[:LOG]:CLEar Syntax :SYSTem:INSTrument:LTRaining[:LOG]:CLEar Description This command clears the Link Training logs. Example :SYST:INST:LTR:LOG:CLE :SYSTem:INSTrument:LTRaining[:LOG]:BLOCk? Syntax :SYSTem:INSTrument:LTRaining[:LOG]:BLOCk? Description The content of the log file is returned as definite block. (see :SYSTem:INSTrument:LTRaining[:LOG]?) Control character (e.g. Line Feed) are contained in the log file. This can interrupt the transfer to the host computer.

  • Page 461: System:instrument:ltraining:equalization[:Status]

    SCPI Command Reference :SYSTem:INSTrument:LTRaining:EQUalization[:STATus]? Syntax :SYSTem:INSTrument:LTRaining:EQUalization[:STATus]? ‘identifier’ Input ‘identifier:’ 'M*.DataOut1' or 'M*.DataOut2' Parameters Description This query returns the Dut transmitter equalization information from the link up block. The results are combined to an expression. An expression is comparable to a struct in a programming language. It’s a set of parameter of different types separated by a comma and enclosed by parenthesis.

  • Page 462: System:information[:Instrument]:Identifier

    SCPI Command Reference :SYSTem:INFormation[:INSTrument]:IDENtifier? Syntax :SYSTem:INFormation[:INSTrument]:IDENtifier? Description This command returns a list of all identifiers defined in the system. Example :SYST:INF:IDEN? (M1.System,M1.SysInA,M1.DataIn1,M1.SysInB,M1.DataIn2,M1.CtrlInA,M1 .CtrlInB,M1.DataOut2,M1.Simulation1,M1.DataOut1,M1.ClkOut,M1.Simul ation2,M1.ClkGen,M1.TrigOut,M1.SysOutA,M1.SysOutB,M1.CtrlOutA,M1. RefClkOut,M2.DataOut2,M2.CtrlOutA,M2.DataOut1,M2.DataIn1,M2.CtrlIn A,M2.DataIn2,M2.CtrlInB,M2.Simulation1,M2.Simulation2,M3.ClkOut,M3. DataIn2,M3.DataOut,M3.ElectIdleIn,M3.DataIn1,M3.MuxMode,M3.DataIn) :SYSTem:INFormation[:INSTrument]:LOCations? Syntax :SYSTem:INFormation[:INSTrument]:LOCations? Description This command returns a list of all locations defined in the system. Example :SYST:INF:LOC? (ClkGen,System,RefClkOut,TrigOut,SysOutA,SysOutB,CtrlOutA,SysInA,Sys...
  • Page 463 SCPI Command Reference SYSTem:INFormation:LICenses:HOST[:LIST]? Syntax SYSTem:INFormation:LICenses:HOST[:LIST]? Description This command lists the description of all the host licenses supported by the device. Example SYSTem:INFormation:LICenses:HOST[:LIST]? ((PCSERNO,AB99889386,("M8070A-CAL","CAL","1.0","System Software for M8000 Series, internal-use only, transportable perpetual license","Installed","Perpetual","12/31/9999 11:59:59 PM","clockgroup-wide")("M8070A-0TP","0TP","1.0","System Software for M8000 Series of BER Test Solutions, transportable, perpetual license","Not installed","Perpetual","12/31/9999 11:59:59 PM","clockgroup-wide")("M8070A-0NP","0NP","1.0","System Software for M8000 Series of BER Test Solutions, network/floating, perpetual...
  • Page 464 SCPI Command Reference :SYSTem:INFormation:LICenses:MODules[:LIST]? Syntax :SYSTem:INFormation:LICenses:MODules[:LIST]? Description This command lists the description of all the module licenses supported by the device. Example :SYSTem:INFormation:LICenses:MODules:LIST? :SYSTem:COMMunicate:TCPip:CONTrol? Syntax :SYSTem:COMMunicate:TCPip:CONTrol? Description This command implements SCPI over TCP with Control Connection. The Keysight Automation Advantage (AAA) standard requires that instruments that support SCPI also support SCPI traffic over TCP with a control connection.
  • Page 465 SCPI Command Reference :SYSTem:DCINterface[:PROGram]:LOAD Syntax :SYSTem:DCINterface[:PROGram]:LOAD “PathToPythonProgramFile” Description This commands loads the given Python script into the DUT control interface. This DUT control interface program can be used to read the bit error rate of an externally connected DUT and provide these to the M8070A software as if the counters are part of the instrument.
  • Page 466 SCPI Command Reference :SYSTem:DCINterface[:PROGram]:SELected? Syntax :SYSTem:DCINterface[:PROGram]:SELected? Description This query returns the DUT Control Interface script that is currently in use. If the DUT Control Interface is not using a script, an empty string is returned. Example :SYSTem:DCINterface:PROGram:SELected? :SYSTem:DCINterface:EXEcute[:INIT] Syntax :SYSTem:DCINterface:EXEcute[:INIT] ‘Location’[,“ArgumentsForInit”] Input ‘Location’: ‘*.Lane*’...
  • Page 467 SCPI Command Reference :SYSTem:DCINterface:DEVice:CONNect[?] Syntax :SYSTem:DCINterface:DEVice:CONNect ‘identifier’, <ON|OFF|1|0> :SYSTem:DCINterface:DEVice:CONNect ‘identifier’? Input ‘identifier’: “DCI.Control” Parameters Description This command relates to the DUT Control Interface hook functions DUT_connect and DUT_disconnect. When these functions are implemented by the currently used script (see syst:dcin:load), then this command is controlling the Connection parameter under the function Device for the Control location of the device under test.
  • Page 468 SCPI Command Reference :SYSTem:DCINterface:DEVice:MODE[?] Syntax :SYSTem:DCINterface:DEVice:MODE ‘identifier’, "mode" :SYSTem:DCINterface:DEVice:MODE? ‘identifier’ Input ‘identifier’: “DCI.Control” Parameters ‘mode’: Individual modes or configurations. Description This command relates to the DUT Control Interface hook functions DUT_getDeviceModes and DUT_setDeviceMode. When these functions are implemented by the currently used script (see syst:dcin:load), then this command is controlling the Mode parameter under the function Device for the Control location of the device under test.
  • Page 469 SCPI Command Reference :SYSTem:DCINterface:LANE:MODE[?] Syntax :SYSTem:DCINterface:LANE:MODE "Location", "mode" :SYSTem:DCINterface:LANE:MODE? "Location" Input ‘Location’: ‘*.Lane*’ Parameters ‘mode’: Individual modes or configurations. Description This command relates to the DUT Control Interface hook functions DUT_getLaneModes and DUT_setLaneMode. When these functions are implemented by the currently used script (see syst:dcin:load), then this command is controlling the Mode parameter under the function Lane for the given lane of the device under test.
  • Page 470 SCPI Command Reference :SYSTem:RESet[:ALL] Syntax :SYSTem:RESet[:ALL] [HARD | SOFT] Input [HARD | SOFT] Parameters Description This command resets the instrument. If SOFT is passed the instrument will load its default values and defined 'Groups' in the GUI will be untouched. If HARD is passed the instrument will load the factory setting and all 'Group' definitions will be cleared.

  • Page 471: Data Subsystem

    SCPI Command Reference DATA Subsystem The DATA subsystem is used to select patterns, define symbol parameters, define sequence blocks and loops and synchronize the pattern. This subsystem has the following SCPI structure: The subsystem has the following subnodes: Table 92 Name Description under :DATA:PATTern Subnode...
  • Page 472 SCPI Command Reference :DATA:PATTern Subnode For additional information about patterns, refer to Working with Patterns on page 36. This subnode has the following SCPI structure: This subnode has the following commands: Table 93 Name Description under :DATA:PATTern:USE[?] :USE[?] on page 473 :DATA:PATTern:IDATa[?] :IDATa[?] on page 474...
  • Page 473 SCPI Command Reference :DATA:PATTern:USE[?] Syntax :DATA:PATTern:USE <pattern-name>,<num-symbols>[,<symbol-coding> [,<mask-used>[,<squelch-used>,<error-used>]]] :DATA:PATTern:USE? <pattern-name> Input <pattern-name>: Name of the pattern. Name consists of root node Parameters (“factory:”, “shared:”, or “current:”) plus folder names separated by ‘/’ plus pattern name. <num-symbols>: Length of the pattern in number of symbols. <symbol- coding>: BIT|B8B10|B128B130|B128B132 for bit coding, 8b10b coding, 128/130 coding or 128/132 coding.
  • Page 474 SCPI Command Reference :DATA:PATTern:IDATa[?] Syntax :DATA:PATTern:IDATa <pattern-name>,<bit-offset>,<num-bits>,<data-block> :DATA:PATTern:IDATa? <pattern-name>,<bit-offset>,<num-bits> Input <pattern-name>: Name of the pattern. Name consists of root node Parameters (“shared:” or “current:”) plus folder names separated by ‘/’ plus pattern name. The “factory:” root node is not allowed here, as these patterns are read only and cannot be modified.
  • Page 475 SCPI Command Reference :DATA:PATTern:CATalog? Syntax :DATA:PATTern:CATalog? <pattern-path> Input <pattern-path>: Location of patterns. Parameters Description This command returns a list of patterns found at the specified path. Example :DATA:PATT:CAT? "factory:XAUI" “CJPAT_bit,CRPAT_b8b10,CRPAT_bit” :DATA:PATTern:CINFormation? Syntax :DATA:PATTern:CINFormation? <symbol-coding>[,<mask-used>[,<squelch-used>]] Input <symbol- coding>: BIT|B8B10|B128B130|B128B132 for bit coding, 8b10b Parameters coding, 128/130 coding or 128/132 coding.
  • Page 476 SCPI Command Reference :DATA:PATTern:DESCription[?] Syntax :DATA:PATTern:DESCription <pattern-name>,<description> :DATA:PATTern:DESCription? <pattern-name> Input <pattern-name>: Name of the pattern. Name consists of root node Parameters (“factory:”, “shared:”, or “current:”) plus folder names separated by ‘/’ plus pattern name; like “shared:SATA/LTDP_short_b8b10”. <description>: Enter a pattern description. Return Range <description>...
  • Page 477 SCPI Command Reference :DATA:PATTern:PACKed[?] Syntax :DATA:PATTern:PACKed <packing> :DATA:PATTern:PACKed? Input <packing>: Specify number of bits (1|4|8) that are encoded in a byte when Parameters using the :DATA:PATT:IDAT command or query. Return Range 1|4|8 Description This command specifies how many bits are encoded in a byte when using the :DATA:PATT:IDAT command or query.
  • Page 478 SCPI Command Reference <error-used> field requires version 1.0.1. Note that if <error-used> is 1, <mask-used> and <squelch-used> must both be 0. Also the coding must be BIT or B8B10. B128B130 and B128B132 are not supported. The next line describes the number of symbols, symbol coding, mask usage and squelch usage as described in :DATA:PATTern:USE command.
  • Page 479 SCPI Command Reference Data= 1010 N4903B J-BERT Patterns N4903B J-BERT patterns are always imported as bit coded patterns with no mask and no squelch. The B part of an alternate pattern will be imported as <pattern-name>B. The following is an example of an N4903B J-BERT pattern import: Example DATA:PATT:IMP "current:x","C:\N4903B\Pattern\xxx.ptrn"...
  • Page 480 SCPI Command Reference :DATA:SEQuence Subnode With this subsystem sequencing can be changed programmatically. For additional information, refer to Creating Pattern Sequences on page 43. This subnode has the following SCPI structure: :DATA :SEQuence :NEW :NAMes? :BIND[?] :VALue[?] :DELete :DALL :BREak :RESTart :IDENtifier :BLOCk?
  • Page 481 SCPI Command Reference Name Description under :DATA:SEQuence:RESTart :RESTart on page 484 :DATA:SEQuence:RESTart:IDENtifier :RESTart:IDENtifier page 485 :DATA:SEQuence:BLOCk? :BLOCk? on page 485 :DATA:SEQuence:BLOCk:IDENtifier? :BLOCk:IDENtifier page 485 :DATA:SEQuence:GRANularity? :GRANularity? on page 486 :DATA:SEQuence:GRANularity:IDENtifier? :GRANularity:IDENtifier? page 486 Keysight M8070A Programming Guide...
  • Page 482 SCPI Command Reference :DATA:SEQuence:NEW Syntax :DATA:SEQuence:NEW <sequence-name> Input <sequence-name>: Specify sequence name. Parameters Description This command is used to create a new sequence. Example :DATA:SEQ:NEW ‘MySequence’ :DATA:SEQuence:NAMes? Syntax :DATA:SEQuence:NAMes? Description This command returns the sequence names currently in use. Example :DATA:SEQ:NAM? “Generator”,“Analyzer”,“MySequence”...
  • Page 483 SCPI Command Reference :DATA:SEQuence:VALue[?] Syntax :DATA:SEQuence:VALue <sequence-name>,<sequence-string> :DATA:SEQuence:VALue? <sequence-name> Input <sequence-name>: Specify sequence name. Parameters <sequence-string>: Enter definite length block and pattern sequence XML string. Return Range <sequence-string> Description This command is used to enter a sequence string consisting of the pattern sequence parameters for the specified sequence name and download it to the hardware.
  • Page 484 SCPI Command Reference :DATA:SEQuence:DELete Syntax :DATA:SEQuence:DELete <sequence-name> Input <sequence-name>: Specify sequence name. Parameters Description This command deletes the specified sequence. Example :DATA:SEQ:DEL ‘MySequence’ :DATA:SEQuence:DALL Syntax :DATA:SEQuence:DALL Description This command deletes all sequences. This is a useful function if you do not want to use the reset sequence (“Generator”, “Analyzer”).
  • Page 485 SCPI Command Reference Example :DATA:SEQ:REST ‘EdSequence’ :DATA:SEQuence:RESTart:IDENtifier Syntax :DATA:SEQuence:RESTart:IDENtifier <identifier> Input <identifier>: 'M*.DataIn1', 'M*.DataIn2', 'M*.DataIn', 'M*.DataOut', Parameters 'M*.DataOut1' and 'M*.DataOut2' Description This command restarts the specified sequence (jumps to the first block). For example, this command is useful for ED sequences. Usually there is a synch block first and then a loop to compare the synchronized pattern.
  • Page 486 SCPI Command Reference :DATA:SEQuence:GRANularity? Syntax :DATA:SEQuence:GRANularity? <sequence-name> Input <sequence-name>: Specify sequence name, i.e., ‘Sequence1’ Parameters Description This query returns the granularity in bits of sequence. It changes with the symbol width. The following table shows the granularity for various symbol widths for different modules: Symbol Wid th Granularity...
  • Page 487 SCPI Command Reference :DATA:SYNC Subnode This subnode has the following SCPI structure: This subnode has the following commands: Table 95 Name Description under :DATA:SYNC[:ONCE] [:ONCE] on page 487 :DATA:SYNC:TYPE[?] :TYPE[?] on page 488 :DATA:SYNC:THReshold[?] :THReshold[?] on page 488 :DATA:SYNC[:ONCE] Syntax :DATA:SYNC[:ONCE] <identifier>...
  • Page 488 SCPI Command Reference :DATA:SYNC:TYPE[?] Syntax :DATA:SYNC:TYPE ‘identifier’, AUTO|MANual :DATA:SYNC:TYPE? ‘identifier’ Input <identifier>: 'M*.DataIn1', 'M*.DataIn2' or 'M*DataIn' Parameters AUTO|MANual: Enable/disable automatic resynchronization. Return Range AUTO|MAN Description This command enables/disables automatic resynchronization. This SCPI is applicable for M8041A, M8051A, M8062A and M8046A. Example :DATA:SYNC:TYPE ‘M1.DataIn1’, AUTO :DATA:SYNC:THReshold[?]...

  • Page 489: Data:linecoding Subnode

    SCPI Command Reference :DATA:LINecoding Subnode The :DATA:LINecoding subnode controls which line coding is being used when sending or receiving the digital data. This subnode has the following SCPI structure: :D A TA :LIN ecoding [:V A Lue][?] :P A M 4 :M A P P ing[?] :M A P P ing:C U S Tom [?] [:S Y M B ol]:LE V el(1|2)[?]...
  • Page 490 SCPI Command Reference :DATA:LINecoding[:VALue][?] Syntax :DATA:LINecoding[:VALue] ‘identifier’, NRZ | PAM4 :DATA:LINecoding[:VALue]? ‘identifier’ Input <identifier>: Any valid data output or data input identifier. M*.DataOut1, Parameters M*.DataOut2, M*.DataOut3, M*.DataOut4 and M*DataIn Description The command selects the line coding to be used. The availability of individual selections depends on the hardware capabilities.
  • Page 491 SCPI Command Reference :DATA:LINecoding:PAM4:MAPPing:CUSTom[?] Syntax :DATA:LINecoding:PAM4:MAPPing:CUSTom ‘identifier’, <”mapping definition”> :DATA:LINecoding:PAM4:MAPPing:CUSTom? ‘identifier’ Input <identifier>: Any valid data output or data input identifier. Parameters Description The command defines a custom bit sequence to symbol number mapping. The mapping defined with this command will be used when CUSTom is selected as the active mapping.
  • Page 492 SCPI Command Reference Range Symbol 1 Level: 1% to 65% Symbol 2 Level: 34% to 99% Description The command controls the PAM-4 level mappings. It can be used to adjust the actual output level that is being generated by a data output for a specific PAM-4 symbol.

  • Page 493: Index

    Index Symbols USB 3.0, :DATA:SYNC[:ONCE], condition register, Data Formats Configuration block data, *CLS, 32G BERT, 16, boolean, *ESE[?], Base, 15, 19, numeric, *ESR?, M8020A 32 Gb/s BERT, 16, string, *IDN?, M8030A multi-channel BERT, 17, download sequence, *OPC, 87, *OPC?, 88, M8041A with M8061A, *OPT?, *RCL,...
  • Page 494 Index *ESR?, :INPut:CDR:SECond:LBANdwidth M8045A Pattern Generator *IDN?, [?], Module, *OPC, :INPut:CDR:SECond:PEAKing[?], M8045A, M8046A and M8057A *OPC?, configuration, *OPT?, :INPut:CDR:SECond:TDENsity[?], M8046A Analyzer Module, *RCL, M8057A Remote Head, *RST, :INPut:CDR[:STATe][?], M8061A 32 Gb/s multiplexer with *SAV, :INPut:CMODe[?], de-emphasis, *SRE[?], :INPut:CMVoltage:DETect, M8192A multi-channel *STB?, :INPut:CMVoltage[?], synchronization module,...
  • Page 495 Index operation status, checking, :OUTPut:TVOLtage[?], :PLUGin:CCAPture:TRIGger:IMM Output Commands :OUTPut[:STATe][?], 205, ediate[:ONCE], :OUTPut:COUPling[?], output level behavior, Plugin Commands :OUTPut:DATA:F2Jitter[?], 210, output protection, :PLUGin:CATalog?, Plugin Compare Commands :OUTPut:DATA:XOVer[?], :PLUGin:CCAPture:RUN:LOG?, :OUTPut:DEEMphasis:CONFigure :SIGN(*)[?], 218, 219, 220, :PLUGin:CCAPture:RUN:MESSag pattern sequences, :OUTPut:DEEMphasis:POSTcurso pattern storage, r(*)[?], :PLUGin:CCAPture:RUN:PROGres patterns, changing, :OUTPut:DEEMphasis:PRECursor Plugin Capture Commands...
  • Page 496 Index :PLUGinERATio:RESet, :PLUGin:EDIagram:FETCh[:RESul :PLUGin:EDIagram:STARt, 398, :PLUGinERATio:RUN:HISTory:CL t]:HEIGht?, Ear, :PLUGin:EDIagram:FETCh[:RESul :PLUGin:EDIagram:STEP, :PLUGinERATio:RUN:HISTory[:ST t]:HILevel?, :PLUGin:EDIagram:STOP, 399, ATe], :PLUGin:EDIagram:FETCh[:RESul :PLUGinERATio:RUN:LOG?, t]:JPPeak?, :PLUGinEDIagram:RESet, 398, :PLUGinERATio:RUN:MESSage?, :PLUGin:EDIagram:FETCh[:RESul t]:JRMSquare?, plugin interface, :PLUGinERATio:RUN:PROGress?, :PLUGin:EDIagram:FETCh[:RESul Plugin Jitter Tolerance Commands t]:LOLevel?, :PLUGin:JTOLerance:BREak, :PLUGinERATio:RUN[:STATus]?, :PLUGin:EDIagram:FETCh[:RESul :PLUGin:JTOLerance:BSETup:AR 01, 304, 320, 340, t]:RISetime?, Time[?], :PLUGinERATio:STARt,...
  • Page 497 Index :PLUGin:JTOLerance:MSETup:FR :PLUGin:OLEVel:ACQuisition:LO :PLUGin:OLEVel:FETCh:QLEVel:L EQuency:STARt[?], WLevel[?], OW:POINts?, :PLUGin:JTOLerance:MSETup:FR :PLUGin:OLEVel:ACQuisition:TRE :PLUGin:OLEVel:FETCh:QLEVel:L EQuency:STOp[?], Solution[?], OW:RSQuare?, :PLUGin:JTOLerance:MSETup:LI :PLUGin:OLEVel:BREak, :PLUGin:OLEVel:FETCh:QLEVel:L Near:SSIZe[?], :PLUGin:OLEVel:CATalog?, OW:STDeviation?, :PLUGin:JTOLerance:MSETup:LO :PLUGin:OLEVel:CONTinue, :PLUGin:OLEVel:FETCh:QLEVel:L G:SSIZe[?], :PLUGin:OLEVel:DELete, OW?, :PLUGin:JTOLerance:MSETup:M :PLUGin:OLEVel:EVALuation:BER :PLUGin:OLEVel:FETCh:QLEVel:Q ODE[?], Thresh[?], FActor?, :PLUGin:JTOLerance:MSETup:MT :PLUGin:OLEVel:EVALuation:MB :PLUGin:OLEVel:FETCh:QLEVel:Q Points[?], QFactor[?], OThreshold?, :PLUGin:JTOLerance:MSETup:NP :PLUGin:OLEVel:FETCh:DATA?, :PLUGin:OLEVel:FETCh:QLEVel:Q Oints[?], RBer?, :PLUGin:JTOLerance:MSETup:TI...
  • Page 498 Index :PLUGin:OTIMing:ACQuisition:EB :PLUGin:OTIMing:FETCh[:JITTer][ Enabled[?], :TOTal]:MEAN?, :PLUGin:OTIMing:ACQuisition:ER :PLUGin:OTIMing:FETCh[:JITTer][ safety summary, Rored[?], :TOTal]:OSDelay?, SCPI :PLUGin:OTIMing:ACQuisition:FTJ :PLUGin:OTIMing:FETCh[:JITTer][ command keywords, Ber[?], :TOTal]:PMARgin?, command separators, :PLUGin:OTIMing:ACQuisition:OP :PLUGin:OTIMing:FETCh[:JITTer][ command structure, Timization[?], :TOTal]:PTPeak?, command syntax, :PLUGin:OTIMing:BREak, :PLUGin:OTIMing:FETCh[:JITTer][ common commands, :PLUGin:OTIMing:CATalog?, :TOTal]:RANDom[:RMSquare]? concepts, :PLUGin:OTIMing:CONTinue, consortium, :PLUGin:OTIMing:DELete, :PLUGin:OTIMing:FETCh[:JITTer][ instrument control :PLUGin:OTIMing:EVALuation:BE :TOTal]:UNCertainty?, commands,...
  • Page 499 Index [:SOURce]:INTerference:DMODe: [:SOURce]:JITTer:HFRequency:S [:SOURce]:JITTer[:GLOBal][:STAT AMPLitude[?], PECtrally[:STATe][?], e][?], [:SOURce]:INTerference:DMODe: [:SOURce]:JITTer:HFRequency:S [:SOURce]:PERiod[?], 138, 139, GAIN[?], 193, 194, PECtrallyƒILTer[:LPASs][:STAT [:SOURce]:INTerference:DMODe: e][?], [:SOURce]:PULSe:DELay[?], 142, SOURce[?], [:SOURce]:JITTer:HFRequency:U 143, [:SOURce]:INTerference:DMODe[: NIT[?], [:SOURce]:SSCLocking:DEViation STATe][?], [:SOURce]:JITTer:LFRequency:PE [?], [:SOURce]:INTerference:HFRequ Riodic:AMPLitude[?], [:SOURce]:SSCLocking:FREQuen ency[:SOURce][?], 189, 199, [:SOURce]:JITTer:LFRequency:PE cy[?], Riodic:FREQuency[?], [:SOURce]:SSCLocking:PROFile[? [:SOURce]:INTerference:LFReque [:SOURce]:JITTer:LFRequency:PE ncy[:SOURce][?], Riodic[:STATe][?],...
  • Page 500 Index :STATus:INSTrument:SALoss?, :STATus:QUEStionable:PROTectio :SYSTem:DCINterface:DEVice:M n:CONDition?, ODE, :STATus:INSTrument:SLOSs?, :STATus:QUEStionable:PROTectio :SYSTem:DCINterface:EXEcute[:I n:ENABle[?], NIT], :STATus:OPERation:CONDition?, :STATus:QUEStionable:PROTectio :SYSTem:DCINterface:LANE:MO n:NTRansition[?], :STATus:OPERation:ENABle[?], :STATus:QUEStionable:PROTectio :SYSTem:DCINterface[:PROGram n:PTRansition[?], ]:LOAD, :STATus:OPERation:NTRansition[ :STATus:QUEStionable:PROTectio :SYSTem:DCINterface[:PROGram n[:EVENt]?, ]:SELected?, :STATus:OPERation:PTRansition[? :STATus:QUEStionable:PTRansitio :SYSTem:DCINterface[:PROGram n[?], ]:UNLoad, :STATus:OPERation:RUN, :STATus:QUEStionable:SYMBol, :SYSTem:INFormation:LICenses: :STATus:OPERation:RUN:CONDiti HOST[:LIST]?, on?, :STATus:QUEStionable:SYMBol:C :SYSTem:INFormation:LICenses: :STATus:OPERation:RUN:ENABle[ ONDition?, MODules[:LIST]?, :STATus:QUEStionable:SYMBol:E :SYSTem:INFormation[:INSTrume...
  • Page 501 Index This, transition filters, Trigger Commands :TRIGger:CMULtiplier:FREQuency :DETect, :TRIGger:CMULtiplier:FREQuency :DIVider[?], :TRIGger:CMULtiplier:FREQuency :MULTiplier[?], :TRIGger:CMULtiplier:FREQuency [?], :TRIGger:CMULtiplier:LBWidth[?] :TRIGger:DIRect[:FREQuency]:DE Tect, :TRIGger:DIRect[:FREQuency][?], :TRIGger:INTernal[:SOURce][?], :TRIGger:REFerence[:FREQuency ][?], :TRIGger[:SOURce]:FREQuency?, :TRIGger[:SOURce][?], trigger, external device, trigger, sequencer, voltages, changing, XML, Keysight M8070A Programming Guide...
  • Page 502 This information is subject to change without notice. © Keysight Technologies 2017 Edition 9.1, August 2017 www.keysight.com...

This manual is also suitable for:

J-bert m8030aJ-bert m8040a

Table of Contents