Wavetek ACTERN ANT20 series/ant20-3035/english/operating manual/_start.pdf operating manual

Page 1
Part 1
ANT-20, ANT-20E, ANT-20SE DominoCOM ANT-20
“Mainframe”
Remote Control Operating Manual SCPI Command List
Page 2
Page 3
Contents
1 ANT-20, ANT-20E, ANT-20SE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-1
1.1 General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-1
1.1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-1
1.1.2 Module selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-2
1.1.3 Monitor mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-3
1.1.4 LabWindows/CVI driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-3
1.2 GPIB Remote Control interface . . . . . . . . . . . . . . . . . . . . . .I-3
1.2.1 Items included. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-3
1.2.2 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-4
1.2.2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-4
1.2.2.2 Software installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-4
1.2.2.3 Hardware installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-7
1.2.3 Connecting to GPIB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-8
1.2.4 Device address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-8
1.2.5 Interface functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-9
1.2.5.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-9
1.2.5.2 Device Clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-9
1.3 V.24/V.28 (RS 232) Remote Control interface. . . . . . . . . . .I-9
1.3.1 Items included. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-9
1.3.2 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-9
1.3.2.1 Software installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-10
1.3.3 Connecting to V.24/V.28 (RS 232) . . . . . . . . . . . . . . . . . . . .I-11
1.3.4 Transmission parameters . . . . . . . . . . . . . . . . . . . . . . . . . . .I-13
1.3.5 Interface functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-14
1.3.5.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-14
1.3.5.2 Device Clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-14
2 DominoCOM ANT-20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-15
2.1 General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-15
2.1.1 Items included. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-15
2.1.2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-15
2.1.3 Changing the configuration . . . . . . . . . . . . . . . . . . . . . . . . . .I-15
2.1.4 ANT-20 mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-16
i
Page 4
2.1.5 Module selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-17
2.1.6 LabWindows/CVI driver . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-17
2.2 GPIB Remote Control interface. . . . . . . . . . . . . . . . . . . . .I-17
2.2.1 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-18
2.2.1.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-18
2.2.1.2 Configuration for GPIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-18
2.2.1.3 Hardware installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-18
2.2.2 Connecting to GPIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-19
2.2.3 Interface functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-19
2.2.3.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-19
2.2.3.2 Device Clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-20
2.3 V.24/V.28 (RS 232) Remote Control interface. . . . . . . . . .I-21
2.3.1 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-21
2.3.1.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-21
2.3.1.2 Configuration for V.24/V.28 (RS 232). . . . . . . . . . . . . . . . . .I-21
2.3.2 Connecting to V.24/V.28 (RS 232) . . . . . . . . . . . . . . . . . . . .I-22
2.3.3 Interface functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-24
2.3.3.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-24
2.3.3.2 Device Clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-24
3 TX/RX SCPI block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-25
4 Operating information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-26
5 Command hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-27
5.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-27
5.2 Command hierarchy (generator) . . . . . . . . . . . . . . . . . . . .I-27
5.3 Command hierarchy (receiver) . . . . . . . . . . . . . . . . . . . . .I-28
6 Programming examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-30
6.1 Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-30
6.2 Example 1 (PDH measurement). . . . . . . . . . . . . . . . . . . . .I-30
6.3 Example 2 (SDH C4 measurement). . . . . . . . . . . . . . . . . .I-31
6.4 Example 3 (SDH overhead) . . . . . . . . . . . . . . . . . . . . . . . .I-32
6.5 Example 4 (SDH overhead measurement) . . . . . . . . . . . .I-32
6.6 Example 5 (SONET STS1-SPE measurement) . . . . . . . . .I-33
ii
Page 5
6.7 Example 6
(SONET Transport overhead measurement) . . . . . . . . . .I-34
6.8 Example 7
(SONET DS1 ESF testing with LOF inserted) . . . . . . . . . .I-34
7 Release Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-36
7.1 New commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-36
7.2 Changed commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-38
Command reference
1 Common commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-1
*CAL?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-1
*CLS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-2
*ESE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-2
*ESE? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-3
*ESR? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-3
*IDN? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-4
*OPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-4
*OPC? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-5
*OPT? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-5
*RST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-5
*SRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-6
*SRE? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-6
*STB?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-7
*TST?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-7
*WAI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-7
2 SYSTEM subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-9
:SYST:DATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-9
:SYST:DATE? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-9
:SYST:ERR[:NEXT]? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-9
:SYST:TIME. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-10
:SYST:TIME?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-10
:SYST:VERS? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-10
3 STATUS subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-11
3.1 Status register structure. . . . . . . . . . . . . . . . . . . . . . . . . .R-11
3.2 STATUS commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-12
:STATus:OPERation register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-12
:STAT:OPER:COND? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-12
:STAT:OPER:ENAB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-13
:STAT:OPER:ENAB?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-13
:STAT:OPER[:EVEN]?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-13
iii
Page 6
:STAT:OPER:NTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-14
:STAT:OPER:NTR? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-14
:STAT:OPER:PTR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-14
:STAT:OPER:PTR?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-15
:STAT:PRES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-15
:STATus:QUEStionable register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-15
:STAT:QUES:COND?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-16
:STAT:QUES:ENAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-16
:STAT:QUES:ENAB? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-16
:STAT:QUES[:EVEN]? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-17
:STAT:QUES:NTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-17
:STAT:QUES:NTR? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-17
:STAT:QUES:PTR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-18
:STAT:QUES:PTR?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-18
:STAT:SEQ register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-18
:STAT:SEQ:COND? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-18
:STAT:SEQ:ENAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-19
:STAT:SEQ:ENAB? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-19
:STAT:SEQ[:EVEN]? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-19
:STAT:SEQ:NTR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-20
:STAT:SEQ:NTR?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-20
:STAT:SEQ:PTR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-20
:STAT:SEQ:PTR?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-21
4 TRIGGER 1 subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-23
:ABOR[1]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-23
:INIT[1][:IMM][:ALL]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-23
:TRIG[1][:SEQ]:SOUR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-24
:TRIG[1][:SEQ]:SOUR?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-24
:TRIG[1][:SEQ]:STIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-25
:TRIG[1][:SEQ]:STIM? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-25
5 TRIGGER 2 subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-27
:ABOR2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-27
:INIT2[:IMM][:ALL]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-28
:TRIG2[:SEQ]:LOG:OBYT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-28
:TRIG2[:SEQ]:LOG:OBYT?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-29
:TRIG2[:SEQ]:LOG:SOUR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-30
:TRIG2[:SEQ]:LOG:SOUR? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-30
:TRIG2[:SEQ]:LOG:TYPE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-31
:TRIG2[:SEQ]:LOG:TYPE?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-31
:TRIG2[:SEQ]:LOG:VAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-32
:TRIG2[:SEQ]:LOG:VAL? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-32
6 TRIGGER 3 subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-33
:ABOR3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-33
:INIT3[:IMM][:ALL]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-33
iv
Page 7
7 OUTPUT subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-35
:OUTP:CLOC[1]:DIV[:STAT] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-35
:OUTP:CLOC[1]:DIV[:STAT]? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-35
:OUTP:CLOC2[:STAT]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-36
:OUTP:CLOC2[:STAT]?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-36
:OUTP:CLOC3[:STAT]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-37
:OUTP:CLOC3[:STAT]?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-37
:OUTP[:TEL]:AUX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-38
:OUTP[:TEL]:AUX[:STAT] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-38
:OUTP[:TEL]:AUX[:STAT]? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-38
:OUTP[:TEL]:AUX:CODE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-38
:OUTP[:TEL]:AUX:CODE?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-39
:OUTP[:TEL]:AUX:TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-39
:OUTP[:TEL]:AUX:TYPE? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-39
:OUTP[:TEL]:IBUS:DCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-40
:OUTP[:TEL]:IBUS:DCC? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-40
:OUTP[:TEL]:LINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-41
:OUTP[:TEL]:LINE:CODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-41
:OUTP[:TEL]:LINE:CODE? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-41
:OUTP[:TEL]:LINE:ERR:CODE | BPV . . . . . . . . . . . . . . . . . . . . . . . . . . .R-42
:OUTP[:TEL]:LINE:ERR:CODE | BPV?. . . . . . . . . . . . . . . . . . . . . . . . . .R-42
:OUTP[:TEL]:LINE:LEV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-42
:OUTP[:TEL]:LINE:LEV? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-43
:OUTP[:TEL]:LINE:ROUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-43
:OUTP[:TEL]:LINE:ROUT? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-43
:OUTP[:TEL]:LINE:TYPE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-44
:OUTP[:TEL]:LINE:TYPE?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-44
:OUTP[:TEL]:NRZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-45
:OUTP[:TEL]:NRZ[:STAT] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-45
:OUTP[:TEL]:NRZ[:STAT]? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-45
:OUTP[:TEL]:OPT[1] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-46
:OUTP[:TEL]:OPT[1][:STAT] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-46
:OUTP[:TEL]:OPT[1][:STAT]? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-46
:OUTP[:TEL]:OPT[1]:WLEN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-47
:OUTP[:TEL]:OPT[1]:WLEN?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-47
:OUTP[:TEL]:OPT2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-48
:OUTP[:TEL]:OPT2[:STAT] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-48
:OUTP[:TEL]:OPT2[:STAT]? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-48
:OUTP[:TEL]:OPT2:PWL? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-48
:OUTP[:TEL]:OPT2:WLEN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-49
:OUTP[:TEL]:OPT2:WLEN?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-49
:OUTP[:TEL]:OPT3[:STAT] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-50
:OUTP[:TEL]:OPT3[:STAT]? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-50
:OUTP:TRIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-51
:OUTP:TRIG:SOUR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-51
:OUTP:TRIG:SOUR?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-51
:OUTP:TRIG[:STAT] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-52
:OUTP:TRIG[:STAT]? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-52
v
Page 8
8 SOURCE subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-53
:SOUR:CLOC:FOFF:OFFS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-53
:SOUR:CLOC:FOFF:OFFS?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-53
:SOUR:CLOC:FOFF[:STAT]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-53
:SOUR:CLOC:FOFF[:STAT]?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-54
:SOUR:CLOC:SOUR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-54
:SOUR:CLOC:SOUR? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-54
:SOUR:DATA[:TEL]:AAL1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-55
:SOUR:DATA[:TEL]:AAL1:CEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-55
:SOUR:DATA[:TEL]:AAL1:CEM? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-56
:SOUR:DATA[:TEL]:AAL1:ERR[:MODE] . . . . . . . . . . . . . . . . . . . . . . . . R-56
:SOUR:DATA[:TEL]:AAL1:ERR[:MODE]? . . . . . . . . . . . . . . . . . . . . . . . R-57
:SOUR:DATA[:TEL]:AAL1:ERR:RATE . . . . . . . . . . . . . . . . . . . . . . . . . . R-57
:SOUR:DATA[:TEL]:AAL1:ERR:RATE? . . . . . . . . . . . . . . . . . . . . . . . . . R-57
:SOUR:DATA[:TEL]:ATM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-58
:SOUR:DATA[:TEL]:ATM:ALAR:CLEN. . . . . . . . . . . . . . . . . . . . . . . . . . R-58
:SOUR:DATA[:TEL]:ATM:ALAR:CLEN?. . . . . . . . . . . . . . . . . . . . . . . . . R-58
:SOUR:DATA[:TEL]:ATM:ALAR[:MODE] . . . . . . . . . . . . . . . . . . . . . . . . R-59
:SOUR:DATA[:TEL]:ATM:ALAR[:MODE]? . . . . . . . . . . . . . . . . . . . . . . . R-60
:SOUR:DATA[:TEL]:ATM:DIST:BURS:BLO . . . . . . . . . . . . . . . . . . . . . . R-60
:SOUR:DATA[:TEL]:ATM:DIST:BURS:BLO? . . . . . . . . . . . . . . . . . . . . . R-60
:SOUR:DATA[:TEL]:ATM:DIST:BURS:BLEN . . . . . . . . . . . . . . . . . . . . . R-61
:SOUR:DATA[:TEL]:ATM:DIST:BURS:BLEN? . . . . . . . . . . . . . . . . . . . . R-61
:SOUR:DATA[:TEL]:ATM:DIST:BURS:BPER. . . . . . . . . . . . . . . . . . . . . R-61
:SOUR:DATA[:TEL]:ATM:DIST:BURS:BPER?. . . . . . . . . . . . . . . . . . . . R-62
:SOUR:DATA[:TEL]:ATM:DIST:CONS:LOAD. . . . . . . . . . . . . . . . . . . . . R-62
:SOUR:DATA[:TEL]:ATM:DIST:CONS:LOAD?. . . . . . . . . . . . . . . . . . . . R-63
:SOUR:DATA[:TEL]:ATM:DIST:CONS:RES. . . . . . . . . . . . . . . . . . . . . . R-63
:SOUR:DATA[:TEL]:ATM:DIST:CONS:RES?. . . . . . . . . . . . . . . . . . . . . R-63
:SOUR:DATA[:TEL]:ATM:DIST:EQU:CDIS . . . . . . . . . . . . . . . . . . . . . . R-64
:SOUR:DATA[:TEL]:ATM:DIST:EQU:CDIS? . . . . . . . . . . . . . . . . . . . . . R-64
:SOUR:DATA[:TEL]:ATM:DIST:EQU:RES . . . . . . . . . . . . . . . . . . . . . . . R-65
:SOUR:DATA[:TEL]:ATM:DIST:EQU:RES? . . . . . . . . . . . . . . . . . . . . . . R-65
:SOUR:DATA[:TEL]:ATM:DIST:STAT. . . . . . . . . . . . . . . . . . . . . . . . . . . R-66
:SOUR:DATA[:TEL]:ATM:DIST:STAT?. . . . . . . . . . . . . . . . . . . . . . . . . . R-66
:SOUR:DATA[:TEL]:ATM:DIST:TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . R-66
:SOUR:DATA[:TEL]:ATM:DIST:TYPE? . . . . . . . . . . . . . . . . . . . . . . . . . R-67
:SOUR:DATA[:TEL]:ATM:ERR:HEAD:CLEN . . . . . . . . . . . . . . . . . . . . . R-67
:SOUR:DATA[:TEL]:ATM:ERR:HEAD:CLEN? . . . . . . . . . . . . . . . . . . . . R-67
:SOUR:DATA[:TEL]:ATM:ERR:HEAD[:MODE]. . . . . . . . . . . . . . . . . . . . R-68
:SOUR:DATA[:TEL]:ATM:ERR:HEAD[:MODE]?. . . . . . . . . . . . . . . . . . . R-68
:SOUR:DATA[:TEL]:ATM:ERR:HEAD:RATE . . . . . . . . . . . . . . . . . . . . . R-69
:SOUR:DATA[:TEL]:ATM:ERR:HEAD:RATE? . . . . . . . . . . . . . . . . . . . . R-69
:SOUR:DATA[:TEL]:ATM:FILL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-69
:SOUR:DATA[:TEL]:ATM:FILL? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-70
:SOUR:DATA[:TEL]:ATM:HEAD:CLP. . . . . . . . . . . . . . . . . . . . . . . . . . . R-70
:SOUR:DATA[:TEL]:ATM:HEAD:CLP?. . . . . . . . . . . . . . . . . . . . . . . . . . R-70
vi
Page 9
:SOUR:DATA[:TEL]:ATM:HEAD:GFC . . . . . . . . . . . . . . . . . . . . . . . . . . .R-71
:SOUR:DATA[:TEL]:ATM:HEAD:GFC? . . . . . . . . . . . . . . . . . . . . . . . . . .R-71
:SOUR:DATA[:TEL]:ATM:HEAD:HEC? . . . . . . . . . . . . . . . . . . . . . . . . . .R-71
:SOUR:DATA[:TEL]:ATM:HEAD:PT . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-72
:SOUR:DATA[:TEL]:ATM:HEAD:PT? . . . . . . . . . . . . . . . . . . . . . . . . . . .R-72
:SOUR:DATA[:TEL]:ATM:HEAD:VCI. . . . . . . . . . . . . . . . . . . . . . . . . . . .R-72
:SOUR:DATA[:TEL]:ATM:HEAD:VCI?. . . . . . . . . . . . . . . . . . . . . . . . . . .R-73
:SOUR:DATA[:TEL]:ATM:HEAD:VPI. . . . . . . . . . . . . . . . . . . . . . . . . . . .R-73
:SOUR:DATA[:TEL]:ATM:HEAD:VPI?. . . . . . . . . . . . . . . . . . . . . . . . . . .R-73
:SOUR:DATA[:TEL]:ATM:NINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-74
:SOUR:DATA[:TEL]:ATM:NINT? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-74
:SOUR:DATA[:TEL]:ATM:PAYL:SCR . . . . . . . . . . . . . . . . . . . . . . . . . . .R-74
:SOUR:DATA[:TEL]:ATM:PAYL:SCR? . . . . . . . . . . . . . . . . . . . . . . . . . .R-75
:SOUR:DATA[:TEL]:ATM:PAYL:TYPE . . . . . . . . . . . . . . . . . . . . . . . . . .R-75
:SOUR:DATA[:TEL]:ATM:PAYL:TYPE? . . . . . . . . . . . . . . . . . . . . . . . . .R-75
:SOUR:DATA[:TEL]:ATM:SOUR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-76
:SOUR:DATA[:TEL]:ATM:SOUR? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-76
:SOUR:DATA[:TEL]:ATM:TRAF:BCH:FILL:LIM. . . . . . . . . . . . . . . . . . . .R-76
:SOUR:DATA[:TEL]:ATM:TRAF:BCH:FILL:LIM?. . . . . . . . . . . . . . . . . . .R-77
:SOUR:DATA[:TEL]:ATM:TRAF:BCH:HEAD:CLP. . . . . . . . . . . . . . . . . .R-77
:SOUR:DATA[:TEL]:ATM:TRAF:BCH:HEAD:CLP?. . . . . . . . . . . . . . . . .R-78
:SOUR:DATA[:TEL]:ATM:TRAF:BCH:HEAD:GFC . . . . . . . . . . . . . . . . .R-78
:SOUR:DATA[:TEL]:ATM:TRAF:BCH:HEAD:GFC? . . . . . . . . . . . . . . . .R-78
:SOUR:DATA[:TEL]:ATM:TRAF:BCH:HEAD:HEC? . . . . . . . . . . . . . . . .R-79
:SOUR:DATA[:TEL]:ATM:TRAF:BCH:HEAD:PT . . . . . . . . . . . . . . . . . . .R-79
:SOUR:DATA[:TEL]:ATM:TRAF:BCH:HEAD:PT? . . . . . . . . . . . . . . . . . .R-79
:SOUR:DATA[:TEL]:ATM:TRAF:BCH:HEAD:VCI . . . . . . . . . . . . . . . . . .R-80
:SOUR:DATA[:TEL]:ATM:TRAF:BCH:HEAD:VCI? . . . . . . . . . . . . . . . . .R-80
:SOUR:DATA[:TEL]:ATM:TRAF:BCH:HEAD:VPI . . . . . . . . . . . . . . . . . .R-81
:SOUR:DATA[:TEL]:ATM:TRAF:BCH:HEAD:VPI? . . . . . . . . . . . . . . . . .R-81
:SOUR:DATA[:TEL]:ATM:TRAF:BCH:PAYL . . . . . . . . . . . . . . . . . . . . . .R-82
:SOUR:DATA[:TEL]:ATM:TRAF:BCH:PAYL? . . . . . . . . . . . . . . . . . . . . .R-82
:SOUR:DATA[:TEL]:ATM:TRAF:BCH:STAT . . . . . . . . . . . . . . . . . . . . . .R-82
:SOUR:DATA[:TEL]:ATM:TRAF:BCH:STAT? . . . . . . . . . . . . . . . . . . . . .R-83
:SOUR:DATA[:TEL]:ATM:TRAF:BCH:TYPE . . . . . . . . . . . . . . . . . . . . . .R-83
:SOUR:DATA[:TEL]:ATM:TRAF:BCH:TYPE? . . . . . . . . . . . . . . . . . . . . .R-83
:SOUR:DATA[:TEL]:ATM:TRAF:BGEN:DATA. . . . . . . . . . . . . . . . . . . . .R-84
:SOUR:DATA[:TEL]:ATM:TRAF:BGEN:DATA?. . . . . . . . . . . . . . . . . . . .R-85
:SOUR:DATA[:TEL]:ATM:TRAF:BGEN:STAT. . . . . . . . . . . . . . . . . . . . .R-85
:SOUR:DATA[:TEL]:ATM:TRAF:BGEN:STAT?. . . . . . . . . . . . . . . . . . . .R-85
:SOUR:DATA[:TEL]:NEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-86
:SOUR:DATA[:TEL]:NEL? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-86
:SOUR:DATA[:TEL]:PAYL:ERR[:MODE]. . . . . . . . . . . . . . . . . . . . . . . . .R-86
:SOUR:DATA[:TEL]:PAYL:ERR[:MODE]?. . . . . . . . . . . . . . . . . . . . . . . .R-87
:SOUR:DATA[:TEL]:PAYL:ERR:RATE . . . . . . . . . . . . . . . . . . . . . . . . . .R-87
:SOUR:DATA[:TEL]:PAYL:ERR:RATE? . . . . . . . . . . . . . . . . . . . . . . . . .R-87
:SOUR:DATA[:TEL]:PAYL:PATT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-88
:SOUR:DATA[:TEL]:PAYL:PATT?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-89
vii
Page 10
:SOUR:DATA[:TEL]:PAYL:SOUR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-89
:SOUR:DATA[:TEL]:PAYL:SOUR?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-89
:SOUR:DATA[:TEL]:PAYL:UWOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-90
:SOUR:DATA[:TEL]:PAYL:UWOR? . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-90
:SOUR:DATA[:TEL]:PDH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-91
:SOUR:DATA[:TEL]:PDH:ALAR:FLEN . . . . . . . . . . . . . . . . . . . . . . . . . . R-91
:SOUR:DATA[:TEL]:PDH:ALAR:FLEN? . . . . . . . . . . . . . . . . . . . . . . . . . R-91
:SOUR:DATA[:TEL]:PDH:ALAR[:MODE] . . . . . . . . . . . . . . . . . . . . . . . . R-92
:SOUR:DATA[:TEL]:PDH:ALAR[:MODE]? . . . . . . . . . . . . . . . . . . . . . . . R-93
:SOUR:DATA[:TEL]:PDH:ALAR:SEQ. . . . . . . . . . . . . . . . . . . . . . . . . . . R-94
:SOUR:DATA[:TEL]:PDH:ALAR:SEQ?. . . . . . . . . . . . . . . . . . . . . . . . . . R-94
:SOUR:DATA[:TEL]:PDH:DS1:CHAN. . . . . . . . . . . . . . . . . . . . . . . . . . . R-95
:SOUR:DATA[:TEL]:PDH:DS1:CHAN?. . . . . . . . . . . . . . . . . . . . . . . . . . R-95
:SOUR:DATA[:TEL]:PDH:DS1:FRAM. . . . . . . . . . . . . . . . . . . . . . . . . . . R-96
:SOUR:DATA[:TEL]:PDH:DS1:FRAM?. . . . . . . . . . . . . . . . . . . . . . . . . . R-96
:SOUR:DATA[:TEL]:PDH:DS3:CHAN. . . . . . . . . . . . . . . . . . . . . . . . . . . R-97
:SOUR:DATA[:TEL]:PDH:DS3:CHAN?. . . . . . . . . . . . . . . . . . . . . . . . . . R-97
:SOUR:DATA[:TEL]:PDH:DS3:FEAC[:ALAR]. . . . . . . . . . . . . . . . . . . . . R-98
:SOUR:DATA[:TEL]:PDH:DS3:FEAC[:ALAR]?. . . . . . . . . . . . . . . . . . . . R-98
:SOUR:DATA[:TEL]:PDH:DS3:FEAC:LOOP[:TYPE] . . . . . . . . . . . . . . . R-99
:SOUR:DATA[:TEL]:PDH:DS3:FEAC:LOOP[:TYPE]? . . . . . . . . . . . . . . R-99
:SOUR:DATA[:TEL]:PDH:DS3:FEAC:LOOP:CODE. . . . . . . . . . . . . . . R-100
:SOUR:DATA[:TEL]:PDH:DS3:FEAC:LOOP:CODE?. . . . . . . . . . . . . . R-101
:SOUR:DATA[:TEL]:PDH:DS3:FRAM. . . . . . . . . . . . . . . . . . . . . . . . . . R-101
:SOUR:DATA[:TEL]:PDH:DS3:FRAM?. . . . . . . . . . . . . . . . . . . . . . . . . R-101
:SOUR:DATA[:TEL]:PDH:ERR[:MODE] . . . . . . . . . . . . . . . . . . . . . . . . R-102
:SOUR:DATA[:TEL]:PDH:ERR[:MODE]? . . . . . . . . . . . . . . . . . . . . . . . R-103
:SOUR:DATA[:TEL]:PDH:ERR:RATE. . . . . . . . . . . . . . . . . . . . . . . . . . R-103
:SOUR:DATA[:TEL]:PDH:ERR:RATE?. . . . . . . . . . . . . . . . . . . . . . . . . R-103
:SOUR:DATA[:TEL]:PDH:FRAM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-104
:SOUR:DATA[:TEL]:PDH:FRAM?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-104
:SOUR:DATA[:TEL]:PDH:M2:ABIT. . . . . . . . . . . . . . . . . . . . . . . . . . . . R-104
:SOUR:DATA[:TEL]:PDH:M2:ABIT?. . . . . . . . . . . . . . . . . . . . . . . . . . . R-105
:SOUR:DATA[:TEL]:PDH:M2:BNF . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-105
:SOUR:DATA[:TEL]:PDH:M2:BNF? . . . . . . . . . . . . . . . . . . . . . . . . . . . R-105
:SOUR:DATA[:TEL]:PDH:M2:CHAN. . . . . . . . . . . . . . . . . . . . . . . . . . . R-106
:SOUR:DATA[:TEL]:PDH:M2:CHAN?. . . . . . . . . . . . . . . . . . . . . . . . . . R-106
:SOUR:DATA[:TEL]:PDH:M2:FRAM. . . . . . . . . . . . . . . . . . . . . . . . . . . R-107
:SOUR:DATA[:TEL]:PDH:M2:FRAM?. . . . . . . . . . . . . . . . . . . . . . . . . . R-107
:SOUR:DATA[:TEL]:PDH:M2:SBIT. . . . . . . . . . . . . . . . . . . . . . . . . . . . R-108
:SOUR:DATA[:TEL]:PDH:M2:SBIT?. . . . . . . . . . . . . . . . . . . . . . . . . . . R-108
:SOUR:DATA[:TEL]:PDH:M2:TSL16 . . . . . . . . . . . . . . . . . . . . . . . . . . R-109
:SOUR:DATA[:TEL]:PDH:M2:TSL16? . . . . . . . . . . . . . . . . . . . . . . . . . R-109
:SOUR:DATA[:TEL]:PDH:M8:BDNB. . . . . . . . . . . . . . . . . . . . . . . . . . . R-110
:SOUR:DATA[:TEL]:PDH:M8:BDNB?. . . . . . . . . . . . . . . . . . . . . . . . . . R-110
:SOUR:DATA[:TEL]:PDH:M8:CHAN. . . . . . . . . . . . . . . . . . . . . . . . . . . R-111
:SOUR:DATA[:TEL]:PDH:M8:CHAN?. . . . . . . . . . . . . . . . . . . . . . . . . . R-111
viii
Page 11
:SOUR:DATA[:TEL]:PDH:M8:DNB . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-112
:SOUR:DATA[:TEL]:PDH:M8:DNB? . . . . . . . . . . . . . . . . . . . . . . . . . . .R-112
:SOUR:DATA[:TEL]:PDH:M34:BDNB . . . . . . . . . . . . . . . . . . . . . . . . . .R-113
:SOUR:DATA[:TEL]:PDH:M34:BDNB? . . . . . . . . . . . . . . . . . . . . . . . . .R-113
:SOUR:DATA[:TEL]:PDH:M34:CHAN . . . . . . . . . . . . . . . . . . . . . . . . . .R-114
:SOUR:DATA[:TEL]:PDH:M34:CHAN? . . . . . . . . . . . . . . . . . . . . . . . . .R-114
:SOUR:DATA[:TEL]:PDH:M34:DNB . . . . . . . . . . . . . . . . . . . . . . . . . . .R-115
:SOUR:DATA[:TEL]:PDH:M34:DNB? . . . . . . . . . . . . . . . . . . . . . . . . . .R-115
:SOUR:DATA[:TEL]:PDH:M34:FTYP. . . . . . . . . . . . . . . . . . . . . . . . . . .R-116
:SOUR:DATA[:TEL]:PDH:M34:FTYP?. . . . . . . . . . . . . . . . . . . . . . . . . .R-116
:SOUR:DATA[:TEL]:PDH:M34:G832:OVER:DATA . . . . . . . . . . . . . . . .R-117
:SOUR:DATA[:TEL]:PDH:M34:G832:OVER:DATA? . . . . . . . . . . . . . . .R-117
:SOUR:DATA[:TEL]:PDH:M34:G832:OVER:DATA:BLOC . . . . . . . . . .R-118
:SOUR:DATA[:TEL]:PDH:M34:G832:OVER:DATA:BLOC? . . . . . . . . .R-118
:SOUR:DATA[:TEL]:PDH:M34:G832:OVER:PRES. . . . . . . . . . . . . . . .R-119
:SOUR:DATA[:TEL]:PDH:M34:G832:OVER:TRAC. . . . . . . . . . . . . . . .R-120
:SOUR:DATA[:TEL]:PDH:M34:G832:OVER:TRAC?. . . . . . . . . . . . . . .R-120
:SOUR:DATA[:TEL]:PDH:M140:CHAN . . . . . . . . . . . . . . . . . . . . . . . . .R-121
:SOUR:DATA[:TEL]:PDH:M140:CHAN? . . . . . . . . . . . . . . . . . . . . . . . .R-121
:SOUR:DATA[:TEL]:PDH:M140:DNYY . . . . . . . . . . . . . . . . . . . . . . . . .R-122
:SOUR:DATA[:TEL]:PDH:M140:DNYY? . . . . . . . . . . . . . . . . . . . . . . . .R-122
:SOUR:DATA[:TEL]:PDH:M140:FTYP. . . . . . . . . . . . . . . . . . . . . . . . . .R-123
:SOUR:DATA[:TEL]:PDH:M140:FTYP?. . . . . . . . . . . . . . . . . . . . . . . . .R-123
:SOUR:DATA[:TEL]:PDH:M140:G832:OVER:DATA . . . . . . . . . . . . . . .R-124
:SOUR:DATA[:TEL]:PDH:M140:G832:OVER:DATA? . . . . . . . . . . . . . .R-124
:SOUR:DATA[:TEL]:PDH:M140:G832:OVER:DATA:BLOC . . . . . . . . .R-125
:SOUR:DATA[:TEL]:PDH:M140:G832:OVER:DATA:BLOC? . . . . . . . .R-126
:SOUR:DATA[:TEL]:PDH:M140:G832:OVER:PRES. . . . . . . . . . . . . . .R-126
:SOUR:DATA[:TEL]:PDH:M140:G832:OVER:TRAC. . . . . . . . . . . . . . .R-127
:SOUR:DATA[:TEL]:PDH:M140:G832:OVER:TRAC?. . . . . . . . . . . . . .R-127
:SOUR:DATA[:TEL]:PDH:PAYL:TYPE . . . . . . . . . . . . . . . . . . . . . . . . .R-128
:SOUR:DATA[:TEL]:PDH:PAYL:TYPE? . . . . . . . . . . . . . . . . . . . . . . . .R-128
:SOUR:DATA[:TEL]:PDH:RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-129
:SOUR:DATA[:TEL]:PDH:RATE? . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-130
:SOUR:DATA[:TEL]:PLCP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-131
:SOUR:DATA[:TEL]:PLCP:ALAR[:MODE]. . . . . . . . . . . . . . . . . . . . . . .R-131
:SOUR:DATA[:TEL]:PLCP:ALAR[:MODE]?. . . . . . . . . . . . . . . . . . . . . .R-131
:SOUR:DATA[:TEL]:PLCP:ALAR:FLEN . . . . . . . . . . . . . . . . . . . . . . . .R-132
:SOUR:DATA[:TEL]:PLCP:ALAR:FLEN? . . . . . . . . . . . . . . . . . . . . . . .R-132
:SOUR:DATA[:TEL]:PLCP:ERR[:MODE]. . . . . . . . . . . . . . . . . . . . . . . .R-133
:SOUR:DATA[:TEL]:PLCP:ERR[:MODE]?. . . . . . . . . . . . . . . . . . . . . . .R-133
:SOUR:DATA[:TEL]:PLCP:ERR:RATE . . . . . . . . . . . . . . . . . . . . . . . . .R-134
:SOUR:DATA[:TEL]:PLCP:ERR:RATE? . . . . . . . . . . . . . . . . . . . . . . . .R-134
:SOUR:DATA[:TEL]:SDH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-135
:SOUR:DATA[:TEL]:SDH:ALAR:FLEN . . . . . . . . . . . . . . . . . . . . . . . . .R-135
:SOUR:DATA[:TEL]:SDH:ALAR:FLEN? . . . . . . . . . . . . . . . . . . . . . . . .R-135
:SOUR:DATA[:TEL]:SDH:ALAR[:MODE]. . . . . . . . . . . . . . . . . . . . . . . .R-136
:SOUR:DATA[:TEL]:SDH:ALAR[:MODE]?. . . . . . . . . . . . . . . . . . . . . . .R-140
ix
Page 12
:SOUR:DATA[:TEL]:SDH:BPOV:DATA . . . . . . . . . . . . . . . . . . . . . . . . R-140
:SOUR:DATA[:TEL]:SDH:BPOV:DATA? . . . . . . . . . . . . . . . . . . . . . . . R-140
:SOUR:DATA[:TEL]:SDH:BPOV:DATA:BLOC . . . . . . . . . . . . . . . . . . . R-141
:SOUR:DATA[:TEL]:SDH:BPOV:DATA:BLOC? . . . . . . . . . . . . . . . . . . R-142
:SOUR:DATA[:TEL]:SDH:BPOV:HPTR . . . . . . . . . . . . . . . . . . . . . . . . R-142
:SOUR:DATA[:TEL]:SDH:BPOV:HPTR? . . . . . . . . . . . . . . . . . . . . . . . R-143
:SOUR:DATA[:TEL]:SDH:BPOV:PRES . . . . . . . . . . . . . . . . . . . . . . . . R-143
:SOUR:DATA[:TEL]:SDH:CHAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-144
:SOUR:DATA[:TEL]:SDH:CHAN?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-145
:SOUR:DATA[:TEL]:SDH:CONC:DPO2 . . . . . . . . . . . . . . . . . . . . . . . . R-146
:SOUR:DATA[:TEL]:SDH:CONC:DPO2? . . . . . . . . . . . . . . . . . . . . . . . R-146
:SOUR:DATA[:TEL]:SDH:CONC:DPO3 . . . . . . . . . . . . . . . . . . . . . . . . R-147
:SOUR:DATA[:TEL]:SDH:CONC:DPO3? . . . . . . . . . . . . . . . . . . . . . . . R-147
:SOUR:DATA[:TEL]:SDH:CONC:DPO4 . . . . . . . . . . . . . . . . . . . . . . . . R-148
:SOUR:DATA[:TEL]:SDH:CONC:DPO4? . . . . . . . . . . . . . . . . . . . . . . . R-148
:SOUR:DATA[:TEL]:SDH:CONC:POIN[:ACT] . . . . . . . . . . . . . . . . . . . R-149
:SOUR:DATA[:TEL]:SDH:CONC:POIN[:ACT]? . . . . . . . . . . . . . . . . . . R-149
:SOUR:DATA[:TEL]:SDH:CONC:POV2:DATA . . . . . . . . . . . . . . . . . . . R-150
:SOUR:DATA[:TEL]:SDH:CONC:POV2:DATA? . . . . . . . . . . . . . . . . . . R-150
:SOUR:DATA[:TEL]:SDH:CONC:POV2:DATA:BLOC . . . . . . . . . . . . . R-151
:SOUR:DATA[:TEL]:SDH:CONC:POV2:DATA:BLOC? . . . . . . . . . . . . R-151
:SOUR:DATA[:TEL]:SDH:CONC:POV2:MODE . . . . . . . . . . . . . . . . . . R-152
:SOUR:DATA[:TEL]:SDH:CONC:POV2:MODE? . . . . . . . . . . . . . . . . . R-152
:SOUR:DATA[:TEL]:SDH:CONC:POV2:PRES. . . . . . . . . . . . . . . . . . . R-153
:SOUR:DATA[:TEL]:SDH:CONC:POV3:DATA . . . . . . . . . . . . . . . . . . . R-154
:SOUR:DATA[:TEL]:SDH:CONC:POV3:DATA? . . . . . . . . . . . . . . . . . . R-154
:SOUR:DATA[:TEL]:SDH:CONC:POV3:DATA:BLOC . . . . . . . . . . . . . R-155
:SOUR:DATA[:TEL]:SDH:CONC:POV3:DATA:BLOC? . . . . . . . . . . . . R-155
:SOUR:DATA[:TEL]:SDH:CONC:POV3:MODE . . . . . . . . . . . . . . . . . . R-156
:SOUR:DATA[:TEL]:SDH:CONC:POV3:MODE? . . . . . . . . . . . . . . . . . R-156
:SOUR:DATA[:TEL]:SDH:CONC:POV3:PRES. . . . . . . . . . . . . . . . . . . R-157
:SOUR:DATA[:TEL]:SDH:CONC:POV4:DATA . . . . . . . . . . . . . . . . . . . R-158
:SOUR:DATA[:TEL]:SDH:CONC:POV4:DATA? . . . . . . . . . . . . . . . . . . R-158
:SOUR:DATA[:TEL]:SDH:CONC:POV4:DATA:BLOC . . . . . . . . . . . . . R-159
:SOUR:DATA[:TEL]:SDH:CONC:POV4:DATA:BLOC? . . . . . . . . . . . . R-159
:SOUR:DATA[:TEL]:SDH:CONC:POV4:MODE . . . . . . . . . . . . . . . . . . R-160
:SOUR:DATA[:TEL]:SDH:CONC:POV4:MODE? . . . . . . . . . . . . . . . . . R-160
:SOUR:DATA[:TEL]:SDH:CONC:POV4:PRES. . . . . . . . . . . . . . . . . . . R-161
:SOUR:DATA[:TEL]:SDH:ERR:FLEN. . . . . . . . . . . . . . . . . . . . . . . . . . R-162
:SOUR:DATA[:TEL]:SDH:ERR:FLEN? . . . . . . . . . . . . . . . . . . . . . . . . . R-162
:SOUR:DATA[:TEL]:SDH:ERR:MASK:HBIP. . . . . . . . . . . . . . . . . . . . . R-163
:SOUR:DATA[:TEL]:SDH:ERR:MASK:HBIP?. . . . . . . . . . . . . . . . . . . . R-163
:SOUR:DATA[:TEL]:SDH:ERR:MASK:LBIP . . . . . . . . . . . . . . . . . . . . . R-164
:SOUR:DATA[:TEL]:SDH:ERR:MASK:LBIP? . . . . . . . . . . . . . . . . . . . . R-164
:SOUR:DATA[:TEL]:SDH:ERR[:MODE] . . . . . . . . . . . . . . . . . . . . . . . . R-165
:SOUR:DATA[:TEL]:SDH:ERR[:MODE]? . . . . . . . . . . . . . . . . . . . . . . . R-166
:SOUR:DATA[:TEL]:SDH:ERR:RATE. . . . . . . . . . . . . . . . . . . . . . . . . . R-167
:SOUR:DATA[:TEL]:SDH:ERR:RATE?. . . . . . . . . . . . . . . . . . . . . . . . . R-167
x
Page 13
:SOUR:DATA[:TEL]:SDH:MAPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-168
:SOUR:DATA[:TEL]:SDH:MAPP? . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-168
:SOUR:DATA[:TEL]:SDH:MAPP:OFFS. . . . . . . . . . . . . . . . . . . . . . . . .R-169
:SOUR:DATA[:TEL]:SDH:MAPP:OFFS?. . . . . . . . . . . . . . . . . . . . . . . .R-169
:SOUR:DATA[:TEL]:SDH:MAPP:CONC[:MODE] . . . . . . . . . . . . . . . . .R-170
:SOUR:DATA[:TEL]:SDH:MAPP:CONC[:MODE]? . . . . . . . . . . . . . . . .R-170
:SOUR:DATA[:TEL]:SDH:MAPP:CONC:CSIZ. . . . . . . . . . . . . . . . . . . .R-171
:SOUR:DATA[:TEL]:SDH:MAPP:CONC:CSIZ?. . . . . . . . . . . . . . . . . . .R-171
:SOUR:DATA[:TEL]:SDH:MAPP:TUFL . . . . . . . . . . . . . . . . . . . . . . . . .R-172
:SOUR:DATA[:TEL]:SDH:MAPP:TUFL? . . . . . . . . . . . . . . . . . . . . . . . .R-172
Overview :SOUR:DATA[:TEL]:SDH:OVER[i]: ... commands . . . . . . . . .R-173
:SOUR:DATA[:TEL]:SDH:OVER:BYT . . . . . . . . . . . . . . . . . . . . . . . . . .R-174
:SOUR:DATA[:TEL]:SDH:OVER:BYT? . . . . . . . . . . . . . . . . . . . . . . . . .R-174
:SOUR:DATA[:TEL]:SDH:OVER[i]:DATA . . . . . . . . . . . . . . . . . . . . . . .R-175
:SOUR:DATA[:TEL]:SDH:OVER[i]:DATA? . . . . . . . . . . . . . . . . . . . . . .R-176
:SOUR:DATA[:TEL]:SDH:OVER[i]:DATA:BLOC . . . . . . . . . . . . . . . . . .R-177
:SOUR:DATA[:TEL]:SDH:OVER[i]:DATA:BLOC? . . . . . . . . . . . . . . . . .R-178
:SOUR:DATA[:TEL]:SDH:OVER:INS[:SOUR] . . . . . . . . . . . . . . . . . . . .R-178
:SOUR:DATA[:TEL]:SDH:OVER:INS[:SOUR]? . . . . . . . . . . . . . . . . . . .R-178
:SOUR:DATA[:TEL]:SDH:OVER[i]:PRES . . . . . . . . . . . . . . . . . . . . . . .R-179
:SOUR:DATA[:TEL]:SDH:OVER[i]:RDAT . . . . . . . . . . . . . . . . . . . . . . .R-182
:SOUR:DATA[:TEL]:SDH:OVER[i]:RDAT? . . . . . . . . . . . . . . . . . . . . . .R-183
:SOUR:DATA[:TEL]:SDH:OVER[i]:RDAT:BLOC . . . . . . . . . . . . . . . . . .R-183
:SOUR:DATA[:TEL]:SDH:OVER[i]:RDAT:BLOC? . . . . . . . . . . . . . . . . .R-184
:SOUR:DATA[:TEL]:SDH:OVER:RSTR. . . . . . . . . . . . . . . . . . . . . . . . .R-185
:SOUR:DATA[:TEL]:SDH:OVER:RSTR?. . . . . . . . . . . . . . . . . . . . . . . .R-185
:SOUR:DATA[:TEL]:SDH:OVER:SEQ[:ACT]. . . . . . . . . . . . . . . . . . . . .R-186
:SOUR:DATA[:TEL]:SDH:OVER:SEQ[:ACT]?. . . . . . . . . . . . . . . . . . . .R-187
:SOUR:DATA[:TEL]:SDH:OVER:SEQ:MNP:DATA . . . . . . . . . . . . . . . .R-187
:SOUR:DATA[:TEL]:SDH:OVER:SEQ:MNP:DATA? . . . . . . . . . . . . . . .R-188
:SOUR:DATA[:TEL]:SDH:OVER:SEQ:POS:POH . . . . . . . . . . . . . . . . .R-189
:SOUR:DATA[:TEL]:SDH:OVER:SEQ:POS:POH? . . . . . . . . . . . . . . . .R-189
:SOUR:DATA[:TEL]:SDH:OVER:SEQ:POS:SOH | TOH. . . . . . . . . . . .R-190
:SOUR:DATA[:TEL]:SDH:OVER:SEQ:POS:SOH? . . . . . . . . . . . . . . . .R-190
:SOUR:DATA[:TEL]:SDH:OVER:SEQ:TCM:DATA . . . . . . . . . . . . . . . .R-191
:SOUR:DATA[:TEL]:SDH:OVER:SEQ:TCM:DATA? . . . . . . . . . . . . . . .R-191
:SOUR:DATA[:TEL]:SDH:OVER:SEQ:TYPE. . . . . . . . . . . . . . . . . . . . .R-192
:SOUR:DATA[:TEL]:SDH:OVER:SEQ:TYPE?. . . . . . . . . . . . . . . . . . . .R-192
:SOUR:DATA[:TEL]:SDH:OVER:SEQ:TCM:DATA:BLOC. . . . . . . . . . .R-193
:SOUR:DATA[:TEL]:SDH:OVER:SEQ:TCM:DATA:BLOC?. . . . . . . . . .R-194
:SOUR:DATA[:TEL]:SDH:PAYL:TYPE . . . . . . . . . . . . . . . . . . . . . . . . .R-195
:SOUR:DATA[:TEL]:SDH:PAYL:TYPE? . . . . . . . . . . . . . . . . . . . . . . . .R-195
Overview of pointer sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-196
:SOUR:DATA[:TEL]:SDH:POIN[:ACT]. . . . . . . . . . . . . . . . . . . . . . . . . .R-198
:SOUR:DATA[:TEL]:SDH:POIN[:ACT]?. . . . . . . . . . . . . . . . . . . . . . . . .R-198
:SOUR:DATA[:TEL]:SDH:POIN:ADD:PER . . . . . . . . . . . . . . . . . . . . . .R-199
:SOUR:DATA[:TEL]:SDH:POIN:ADD:PER? . . . . . . . . . . . . . . . . . . . . .R-199
xi
Page 14
:SOUR:DATA[:TEL]:SDH:POIN:ADD[:STAT] . . . . . . . . . . . . . . . . . . . . R-199
:SOUR:DATA[:TEL]:SDH:POIN:ADD[:STAT]? . . . . . . . . . . . . . . . . . . . R-200
:SOUR:DATA[:TEL]:SDH:POIN:APER . . . . . . . . . . . . . . . . . . . . . . . . . R-200
:SOUR:DATA[:TEL]:SDH:POIN:APER? . . . . . . . . . . . . . . . . . . . . . . . . R-200
:SOUR:DATA[:TEL]:SDH:POIN:CANC:PER. . . . . . . . . . . . . . . . . . . . . R-201
:SOUR:DATA[:TEL]:SDH:POIN:CANC:PER?. . . . . . . . . . . . . . . . . . . . R-201
:SOUR:DATA[:TEL]:SDH:POIN:CANC[:STAT]. . . . . . . . . . . . . . . . . . . R-201
:SOUR:DATA[:TEL]:SDH:POIN:CANC[:STAT]?. . . . . . . . . . . . . . . . . . R-202
:SOUR:DATA[:TEL]:SDH:POIN:IPER. . . . . . . . . . . . . . . . . . . . . . . . . . R-202
:SOUR:DATA[:TEL]:SDH:POIN:IPER?. . . . . . . . . . . . . . . . . . . . . . . . . R-202
:SOUR:DATA[:TEL]:SDH:POIN:MODE . . . . . . . . . . . . . . . . . . . . . . . . R-203
:SOUR:DATA[:TEL]:SDH:POIN:MODE? . . . . . . . . . . . . . . . . . . . . . . . R-203
:SOUR:DATA[:TEL]:SDH:POIN:NDFL . . . . . . . . . . . . . . . . . . . . . . . . . R-203
:SOUR:DATA[:TEL]:SDH:POIN:NDFL? . . . . . . . . . . . . . . . . . . . . . . . . R-204
:SOUR:DATA[:TEL]:SDH:POIN:NUMB. . . . . . . . . . . . . . . . . . . . . . . . . R-204
:SOUR:DATA[:TEL]:SDH:POIN:NUMB?. . . . . . . . . . . . . . . . . . . . . . . . R-204
:SOUR:DATA[:TEL]:SDH:POIN:PER . . . . . . . . . . . . . . . . . . . . . . . . . . R-205
:SOUR:DATA[:TEL]:SDH:POIN:PER? . . . . . . . . . . . . . . . . . . . . . . . . . R-205
:SOUR:DATA[:TEL]:SDH:POIN:SEQ:DIR . . . . . . . . . . . . . . . . . . . . . . R-205
:SOUR:DATA[:TEL]:SDH:POIN:SEQ:DIR? . . . . . . . . . . . . . . . . . . . . . R-206
:SOUR:DATA[:TEL]:SDH:POIN:SEQ:TYPE . . . . . . . . . . . . . . . . . . . . . R-206
:SOUR:DATA[:TEL]:SDH:POIN:SEQ:TYPE? . . . . . . . . . . . . . . . . . . . . R-206
:SOUR:DATA[:TEL]:SDH:POIN:SSB . . . . . . . . . . . . . . . . . . . . . . . . . . R-207
:SOUR:DATA[:TEL]:SDH:POIN:SSB? . . . . . . . . . . . . . . . . . . . . . . . . . R-207
:SOUR:DATA[:TEL]:SDH:POIN:VAL . . . . . . . . . . . . . . . . . . . . . . . . . . R-207
:SOUR:DATA[:TEL]:SDH:POIN:VAL? . . . . . . . . . . . . . . . . . . . . . . . . . R-207
:SOUR:DATA[:TEL]:SDH:POV:DATA. . . . . . . . . . . . . . . . . . . . . . . . . . R-208
:SOUR:DATA[:TEL]:SDH:POV:DATA?. . . . . . . . . . . . . . . . . . . . . . . . . R-208
:SOUR:DATA[:TEL]:SDH:POV:DATA:BLOC . . . . . . . . . . . . . . . . . . . . R-209
:SOUR:DATA[:TEL]:SDH:POV:DATA:BLOC? . . . . . . . . . . . . . . . . . . . R-209
:SOUR:DATA[:TEL]:SDH:POV:HPTR. . . . . . . . . . . . . . . . . . . . . . . . . . R-210
:SOUR:DATA[:TEL]:SDH:POV:HPTR?. . . . . . . . . . . . . . . . . . . . . . . . . R-210
:SOUR:DATA[:TEL]:SDH:POV:HSEQ . . . . . . . . . . . . . . . . . . . . . . . . . R-211
:SOUR:DATA[:TEL]:SDH:POV:HSEQ? . . . . . . . . . . . . . . . . . . . . . . . . R-211
:SOUR:DATA[:TEL]:SDH:POV:PRES. . . . . . . . . . . . . . . . . . . . . . . . . . R-212
:SOUR:DATA[:TEL]:SDH:RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-213
:SOUR:DATA[:TEL]:SDH:RATE? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-213
:SOUR:DATA[:TEL]:SDH:REPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-214
:SOUR:DATA[:TEL]:SDH:REPL? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-214
:SOUR:DATA[:TEL]:SDH:SCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-215
:SOUR:DATA[:TEL]:SDH:SCR? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-215
:SOUR:DATA[:TEL]:SDH:STMN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-216
:SOUR:DATA[:TEL]:SDH:STMN:BCH . . . . . . . . . . . . . . . . . . . . . . . . . R-216
:SOUR:DATA[:TEL]:SDH:STMN:BCH? . . . . . . . . . . . . . . . . . . . . . . . . R-216
:SOUR:DATA[:TEL]:SDH:STMN:CHAN . . . . . . . . . . . . . . . . . . . . . . . . R-217
:SOUR:DATA[:TEL]:SDH:STMN:CHAN? . . . . . . . . . . . . . . . . . . . . . . . R-217
:SOUR:DATA[:TEL]:SDH:STSN:CHAN . . . . . . . . . . . . . . . . . . . . . . . . R-218
:SOUR:DATA[:TEL]:SDH:STSN:CHAN? . . . . . . . . . . . . . . . . . . . . . . . R-218
xii
Page 15
:SOUR:DATA[:TEL]:SDH:STSV:CHAN . . . . . . . . . . . . . . . . . . . . . . . . .R-219
:SOUR:DATA[:TEL]:SDH:STSV:CHAN? . . . . . . . . . . . . . . . . . . . . . . . .R-219
:SOUR:DATA[:TEL]:SDH:STMN:OVER:DATA . . . . . . . . . . . . . . . . . . .R-220
:SOUR:DATA[:TEL]:SDH:STMN:OVER:DATA? . . . . . . . . . . . . . . . . . .R-220
:SOUR:DATA[:TEL]:SDH:STMN:OVER:DATA:BLOC. . . . . . . . . . . . . .R-221
:SOUR:DATA[:TEL]:SDH:STMN:OVER:DATA:BLOC?. . . . . . . . . . . . .R-221
:SOUR:DATA[:TEL]:SDH:STMN:OVER:PRES . . . . . . . . . . . . . . . . . . .R-222
:SOUR:DATA[:TEL]:SDH:STMN:OVER:RDAT . . . . . . . . . . . . . . . . . . .R-226
:SOUR:DATA[:TEL]:SDH:STMN:OVER:RDAT? . . . . . . . . . . . . . . . . . .R-226
:SOUR:DATA[:TEL]:SDH:STMN:OVER:RDAT:BLOC. . . . . . . . . . . . . .R-227
:SOUR:DATA[:TEL]:SDH:STMN:OVER:RDAT:BLOC?. . . . . . . . . . . . .R-228
:SOUR:DATA[:TEL]:SDH:TRIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-229
:SOUR:DATA[:TEL]:SDH:TRIB:BPOV:DATA . . . . . . . . . . . . . . . . . . . .R-229
:SOUR:DATA[:TEL]:SDH:TRIB:BPOV:DATA? . . . . . . . . . . . . . . . . . . .R-229
:SOUR:DATA[:TEL]:SDH:TRIB:BPOV:LPTR . . . . . . . . . . . . . . . . . . . .R-230
:SOUR:DATA[:TEL]:SDH:TRIB:BPOV:LPTR? . . . . . . . . . . . . . . . . . . .R-230
:SOUR:DATA[:TEL]:SDH:TRIB:BPOV:PRES . . . . . . . . . . . . . . . . . . . .R-231
:SOUR:DATA[:TEL]:SDH:TRIB:BPOV:VC3:DATA . . . . . . . . . . . . . . . .R-232
:SOUR:DATA[:TEL]:SDH:TRIB:BPOV:VC3:DATA? . . . . . . . . . . . . . . .R-232
:SOUR:DATA[:TEL]:SDH:TRIB:BPOV:VC3:DATA:BLOC . . . . . . . . . . .R-233
:SOUR:DATA[:TEL]:SDH:TRIB:BPOV:VC3:DATA:BLOC? . . . . . . . . . .R-234
:SOUR:DATA[:TEL]:SDH:TRIB:BPOV:VC3:PRES . . . . . . . . . . . . . . . .R-234
:SOUR:DATA[:TEL]:SDH:TRIB:MAPP . . . . . . . . . . . . . . . . . . . . . . . . .R-235
:SOUR:DATA[:TEL]:SDH:TRIB:MAPP? . . . . . . . . . . . . . . . . . . . . . . . .R-235
:SOUR:DATA[:TEL]:SDH:TRIB:POIN[:ACT] . . . . . . . . . . . . . . . . . . . . .R-236
:SOUR:DATA[:TEL]:SDH:TRIB:POIN[:ACT]? . . . . . . . . . . . . . . . . . . . .R-236
:SOUR:DATA[:TEL]:SDH:TRIB:POIN:ADD:PER. . . . . . . . . . . . . . . . . .R-237
:SOUR:DATA[:TEL]:SDH:TRIB:POIN:ADD:PER?. . . . . . . . . . . . . . . . .R-237
:SOUR:DATA[:TEL]:SDH:TRIB:POIN:ADD[:STAT]. . . . . . . . . . . . . . . .R-237
:SOUR:DATA[:TEL]:SDH:TRIB:POIN:ADD[:STAT]?. . . . . . . . . . . . . . .R-238
:SOUR:DATA[:TEL]:SDH:TRIB:POIN:APER. . . . . . . . . . . . . . . . . . . . .R-238
:SOUR:DATA[:TEL]:SDH:TRIB:POIN:APER?. . . . . . . . . . . . . . . . . . . .R-238
:SOUR:DATA[:TEL]:SDH:TRIB:POIN:CANC:PER . . . . . . . . . . . . . . . .R-239
:SOUR:DATA[:TEL]:SDH:TRIB:POIN:CANC:PER? . . . . . . . . . . . . . . .R-239
:SOUR:DATA[:TEL]:SDH:TRIB:POIN:CANC[:STAT] . . . . . . . . . . . . . .R-239
:SOUR:DATA[:TEL]:SDH:TRIB:POIN:CANC[:STAT]? . . . . . . . . . . . . .R-240
:SOUR:DATA[:TEL]:SDH:TRIB:POIN:IPER . . . . . . . . . . . . . . . . . . . . .R-240
:SOUR:DATA[:TEL]:SDH:TRIB:POIN:IPER? . . . . . . . . . . . . . . . . . . . .R-240
:SOUR:DATA[:TEL]:SDH:TRIB:POIN:MODE . . . . . . . . . . . . . . . . . . . .R-241
:SOUR:DATA[:TEL]:SDH:TRIB:POIN:MODE? . . . . . . . . . . . . . . . . . . .R-241
:SOUR:DATA[:TEL]:SDH:TRIB:POIN:NDFL . . . . . . . . . . . . . . . . . . . . .R-241
:SOUR:DATA[:TEL]:SDH:TRIB:POIN:NDFL? . . . . . . . . . . . . . . . . . . . .R-242
:SOUR:DATA[:TEL]:SDH:TRIB:POIN:NUMB . . . . . . . . . . . . . . . . . . . .R-242
:SOUR:DATA[:TEL]:SDH:TRIB:POIN:NUMB? . . . . . . . . . . . . . . . . . . .R-242
:SOUR:DATA[:TEL]:SDH:TRIB:POIN:PER . . . . . . . . . . . . . . . . . . . . . .R-243
:SOUR:DATA[:TEL]:SDH:TRIB:POIN:PER? . . . . . . . . . . . . . . . . . . . . .R-243
:SOUR:DATA[:TEL]:SDH:TRIB:POIN:SEQ:DIR . . . . . . . . . . . . . . . . . .R-243
:SOUR:DATA[:TEL]:SDH:TRIB:POIN:SEQ:DIR? . . . . . . . . . . . . . . . . .R-244
xiii
Page 16
:SOUR:DATA[:TEL]:SDH:TRIB:POIN:SEQ:TYPE . . . . . . . . . . . . . . . . R-244
:SOUR:DATA[:TEL]:SDH:TRIB:POIN:SEQ:TYPE? . . . . . . . . . . . . . . . R-244
:SOUR:DATA[:TEL]:SDH:TRIB:POIN:VAL . . . . . . . . . . . . . . . . . . . . . . R-245
:SOUR:DATA[:TEL]:SDH:TRIB:POIN:VAL? . . . . . . . . . . . . . . . . . . . . . R-245
:SOUR:DATA[:TEL]:SDH:TRIB:POV:DATA . . . . . . . . . . . . . . . . . . . . . R-246
:SOUR:DATA[:TEL]:SDH:TRIB:POV:DATA? . . . . . . . . . . . . . . . . . . . . R-246
:SOUR:DATA[:TEL]:SDH:TRIB:POV:LPTR . . . . . . . . . . . . . . . . . . . . . R-247
:SOUR:DATA[:TEL]:SDH:TRIB:POV:LPTR? . . . . . . . . . . . . . . . . . . . . R-247
:SOUR:DATA[:TEL]:SDH:TRIB:POV:PRES . . . . . . . . . . . . . . . . . . . . . R-248
:SOUR:DATA[:TEL]:SDH:TRIB:POV:VC3:DATA . . . . . . . . . . . . . . . . . R-249
:SOUR:DATA[:TEL]:SDH:TRIB:POV:VC3:DATA? . . . . . . . . . . . . . . . . R-249
:SOUR:DATA[:TEL]:SDH:TRIB:POV:VC3:DATA:BLOC. . . . . . . . . . . . R-250
:SOUR:DATA[:TEL]:SDH:TRIB:POV:VC3:DATA:BLOC?. . . . . . . . . . . R-251
:SOUR:DATA[:TEL]:SDH:TRIB:POV:VC3:PRES . . . . . . . . . . . . . . . . . R-251
:SOUR:DATA[:TEL]:SOUR:DIV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-252
:SOUR:DATA[:TEL]:SOUR:DIV? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-253
:SOUR:DATA[:TEL]:SOUR[:SOCK] . . . . . . . . . . . . . . . . . . . . . . . . . . . R-253
:SOUR:DATA[:TEL]:SOUR[:SOCK]? . . . . . . . . . . . . . . . . . . . . . . . . . . R-253
:SOUR:DATA[:TEL]:STAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-254
:SOUR:DATA[:TEL]:STAN? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-254
:SOUR:MODE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-255
:SOUR:MODE?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-255
9 INPUT Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-256
:INP:CLOC:JITT[:STAT] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-256
:INP:CLOC:JITT[:STAT]? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-256
:INP:CLOC:WAND[:STAT] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-257
:INP:CLOC:WAND[:STAT]? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-257
:INP[:TEL]:AUX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-258
:INP[:TEL]:AUX:CODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-258
:INP[:TEL]:AUX:CODE? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-258
:INP[:TEL]:AUX:TYPE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-259
:INP[:TEL]:AUX:TYPE?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-259
:INP[:TEL]:LINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-260
:INP[:TEL]:LINE:CODE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-260
:INP[:TEL]:LINE:CODE?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-260
:INP[:TEL]:LINE:EQU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-261
:INP[:TEL]:LINE:EQU? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-261
:INP[:TEL]:LINE:EREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-261
:INP[:TEL]:LINE:EREF? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-261
:INP[:TEL]:LINE:LEV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-262
:INP[:TEL]:LINE:LEV?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-262
:INP[:TEL]:LINE:ROUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-262
:INP[:TEL]:LINE:ROUT? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-263
:INP[:TEL]:LINE:TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-263
:INP[:TEL]:LINE:TYPE? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-263
xiv
Page 17
10 SENSE subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-264
[:SENS]:DATA:FIN?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-264
[:SENS]:DATA:ACT? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-265
[:SENS]:DATA:EVEN?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-266
[:SENS]:DATA:EVEN:NUMB?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-267
Codes for the event memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-268
Alarm bit fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-272
Alarm field “CSTatus:SIGNal”/“HSTatus:SIGNal”. . . . . . . . . . . . . . . . . R-272
Alarm field “CSTatus:SDH”/“HSTatus:SDH”. . . . . . . . . . . . . . . . . . . . . R-272
Alarm field “CSTatus:SDH2”/“HSTatus:SDH2”. . . . . . . . . . . . . . . . . . . R-274
Alarm field “CSTatus:ATM”/“HSTatus:ATM”. . . . . . . . . . . . . . . . . . . . . R-277
Alarm field “CSTatus:PDH”/“HSTatus:PDH”. . . . . . . . . . . . . . . . . . . . . R-278
Alarm field “CSTatus:PDH2”/“HSTatus:PDH2”. . . . . . . . . . . . . . . . . . . R-279
Result field “CSTatus:FEAC:LOOP:ON”/ “CSTatus:FEAC:LOOP:OFF”/
“HSTatus:FEAC:LOOP:ON”/“HSTatus:FEAC:LOOP:OFF” . . . . . . . . . R-280
Result field “CSTatus:TCMonitoring”/“HSTatus:TCMonitoring” . . . . . . R-281
[:SENS]:DATA[:TEL]:AAL1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-282
[:SENS]:DATA[:TEL]:AAL1:CEM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-282
[:SENS]:DATA[:TEL]:AAL1:CEM?. . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-282
[:SENS]:DATA[:TEL]:ANAL:G821:ALL . . . . . . . . . . . . . . . . . . . . . . . . .R-283
[:SENS]:DATA[:TEL]:ANAL:G821:ALL? . . . . . . . . . . . . . . . . . . . . . . . .R-283
[:SENS]:DATA[:TEL]:ANAL:G821:DM:THR. . . . . . . . . . . . . . . . . . . . . .R-283
[:SENS]:DATA[:TEL]:ANAL:G821:DM:THR?. . . . . . . . . . . . . . . . . . . . .R-283
[:SENS]:DATA[:TEL]:ANAL:G821:EVAL . . . . . . . . . . . . . . . . . . . . . . . .R-284
[:SENS]:DATA[:TEL]:ANAL:G821:EVAL? . . . . . . . . . . . . . . . . . . . . . . .R-284
[:SENS]:DATA[:TEL]:ANAL:G821:MODE . . . . . . . . . . . . . . . . . . . . . . .R-285
[:SENS]:DATA[:TEL]:ANAL:G821:SES:THR . . . . . . . . . . . . . . . . . . . . .R-285
[:SENS]:DATA[:TEL]:ANAL:G821:SES:THR? . . . . . . . . . . . . . . . . . . . .R-285
[:SENS]:DATA[:TEL]:ANAL:G826:ALL . . . . . . . . . . . . . . . . . . . . . . . . .R-286
[:SENS]:DATA[:TEL]:ANAL:G826:ALL? . . . . . . . . . . . . . . . . . . . . . . . .R-286
[:SENS]:DATA[:TEL]:ANAL:G826:EVAL . . . . . . . . . . . . . . . . . . . . . . . .R-286
[:SENS]:DATA[:TEL]:ANAL:G826:EVAL? . . . . . . . . . . . . . . . . . . . . . . .R-287
[:SENS]:DATA[:TEL]:ANAL:G826:SES:THR . . . . . . . . . . . . . . . . . . . . .R-287
[:SENS]:DATA[:TEL]:ANAL:G826:SES:THR? . . . . . . . . . . . . . . . . . . . .R-288
[:SENS]:DATA[:TEL]:ANAL:G826:SES:THR:AUTO . . . . . . . . . . . . . . .R-288
[:SENS]:DATA[:TEL]:ANAL:G826:SES:THR:AUTO? . . . . . . . . . . . . . .R-288
[:SENS]:DATA[:TEL]:ANAL:G826:UAS:LIM[:STAT] . . . . . . . . . . . . . . .R-289
[:SENS]:DATA[:TEL]:ANAL:G826:UAS:LIM[:STAT]? . . . . . . . . . . . . . .R-289
[:SENS]:DATA[:TEL]:ANAL:G826:UAS:LIM:UPP . . . . . . . . . . . . . . . . .R-289
[:SENS]:DATA[:TEL]:ANAL:G826:UAS:LIM:UPP? . . . . . . . . . . . . . . . .R-290
[:SENS]:DATA[:TEL]:ANAL:G826:UAS:MODE . . . . . . . . . . . . . . . . . . .R-290
[:SENS]:DATA[:TEL]:ANAL:G826:UAS:MODE? . . . . . . . . . . . . . . . . . .R-290
[:SENS]:DATA[:TEL]:ANAL:G828:ALL . . . . . . . . . . . . . . . . . . . . . . . . .R-291
[:SENS]:DATA[:TEL]:ANAL:G828:ALL? . . . . . . . . . . . . . . . . . . . . . . . .R-291
[:SENS]:DATA[:TEL]:ANAL:G828:EVAL . . . . . . . . . . . . . . . . . . . . . . . .R-291
[:SENS]:DATA[:TEL]:ANAL:G828:EVAL? . . . . . . . . . . . . . . . . . . . . . . .R-292
xv
Page 18
[:SENS]:DATA[:TEL]:ANAL:G828:SEPI[:STAT] . . . . . . . . . . . . . . . . . . R-292
[:SENS]:DATA[:TEL]:ANAL:G828:SEPI[:STAT]? . . . . . . . . . . . . . . . . . R-292
[:SENS]:DATA[:TEL]:ANAL:G828:SES:THR . . . . . . . . . . . . . . . . . . . . R-292
[:SENS]:DATA[:TEL]:ANAL:G828:SES:THR? . . . . . . . . . . . . . . . . . . . R-293
[:SENS]:DATA[:TEL]:ANAL:G828:SES:THR:AUTO . . . . . . . . . . . . . . . R-293
[:SENS]:DATA[:TEL]:ANAL:G828:SES:THR:AUTO? . . . . . . . . . . . . . . R-293
[:SENS]:DATA[:TEL]:ANAL:G828:UAS:LIM[:STAT] . . . . . . . . . . . . . . . R-294
[:SENS]:DATA[:TEL]:ANAL:G828:UAS:LIM[:STAT]? . . . . . . . . . . . . . . R-294
[:SENS]:DATA[:TEL]:ANAL:G828:UAS:LIM:UPP . . . . . . . . . . . . . . . . . R-294
[:SENS]:DATA[:TEL]:ANAL:G828:UAS:LIM:UPP? . . . . . . . . . . . . . . . . R-294
[:SENS]:DATA[:TEL]:ANAL:G828:UAS:MODE. . . . . . . . . . . . . . . . . . . R-295
[:SENS]:DATA[:TEL]:ANAL:G828:UAS:MODE?. . . . . . . . . . . . . . . . . . R-295
[:SENS]:DATA[:TEL]:ANAL:G829:EVAL. . . . . . . . . . . . . . . . . . . . . . . . R-295
[:SENS]:DATA[:TEL]:ANAL:G829:EVAL?. . . . . . . . . . . . . . . . . . . . . . . R-296
[:SENS]:DATA[:TEL]:ANAL:G829:SES:THR . . . . . . . . . . . . . . . . . . . . R-296
[:SENS]:DATA[:TEL]:ANAL:G829:SES:THR? . . . . . . . . . . . . . . . . . . . R-296
[:SENS]:DATA[:TEL]:ANAL:G829:SES:THR:AUTO . . . . . . . . . . . . . . . R-297
[:SENS]:DATA[:TEL]:ANAL:G829:SES:THR:AUTO? . . . . . . . . . . . . . . R-297
[:SENS]:DATA[:TEL]:ANAL:M2100:ALL . . . . . . . . . . . . . . . . . . . . . . . . R-298
[:SENS]:DATA[:TEL]:ANAL:M2100:ALL? . . . . . . . . . . . . . . . . . . . . . . . R-298
[:SENS]:DATA[:TEL]:ANAL:M2100:BISO:ES? . . . . . . . . . . . . . . . . . . . R-298
[:SENS]:DATA[:TEL]:ANAL:M2100:BISO:MULT . . . . . . . . . . . . . . . . . R-298
[:SENS]:DATA[:TEL]:ANAL:M2100:BISO:MULT? . . . . . . . . . . . . . . . . R-299
[:SENS]:DATA[:TEL]:ANAL:M2100:BISO:SES?. . . . . . . . . . . . . . . . . . R-299
[:SENS]:DATA[:TEL]:ANAL:M2100:EVAL. . . . . . . . . . . . . . . . . . . . . . . R-299
[:SENS]:DATA[:TEL]:ANAL:M2100:EVAL?. . . . . . . . . . . . . . . . . . . . . . R-300
[:SENS]:DATA[:TEL]:ANAL:M2100:S1:ES? . . . . . . . . . . . . . . . . . . . . . R-300
[:SENS]:DATA[:TEL]:ANAL:M2100:S1:SES?. . . . . . . . . . . . . . . . . . . . R-300
[:SENS]:DATA[:TEL]:ANAL:M2100:S2:ES? . . . . . . . . . . . . . . . . . . . . . R-301
[:SENS]:DATA[:TEL]:ANAL:M2100:S2:SES?. . . . . . . . . . . . . . . . . . . . R-301
[:SENS]:DATA[:TEL]:ANAL:M2100:UAS:LIM[:STAT]. . . . . . . . . . . . . . R-301
[:SENS]:DATA[:TEL]:ANAL:M2100:UAS:LIM[:STAT]?. . . . . . . . . . . . . R-301
[:SENS]:DATA[:TEL]:ANAL:M2100:UAS:LIM:UPP. . . . . . . . . . . . . . . . R-302
[:SENS]:DATA[:TEL]:ANAL:M2100:UAS:LIM:UPP?. . . . . . . . . . . . . . . R-302
[:SENS]:DATA[:TEL]:ANAL:M2100:UAS:MODE. . . . . . . . . . . . . . . . . . R-302
[:SENS]:DATA[:TEL]:ANAL:M2100:UAS:MODE?. . . . . . . . . . . . . . . . . R-303
[:SENS]:DATA[:TEL]:ANAL:M2101:ALL . . . . . . . . . . . . . . . . . . . . . . . . R-304
[:SENS]:DATA[:TEL]:ANAL:M2101:ALL? . . . . . . . . . . . . . . . . . . . . . . . R-304
[:SENS]:DATA[:TEL]:ANAL:M2101:BISO:BBE?. . . . . . . . . . . . . . . . . . R-304
[:SENS]:DATA[:TEL]:ANAL:M2101:BISO:ES? . . . . . . . . . . . . . . . . . . . R-305
[:SENS]:DATA[:TEL]:ANAL:M2101:BISO:MULT . . . . . . . . . . . . . . . . . R-305
[:SENS]:DATA[:TEL]:ANAL:M2101:BISO:MULT? . . . . . . . . . . . . . . . . R-305
[:SENS]:DATA[:TEL]:ANAL:M2101:BISO:SEP?. . . . . . . . . . . . . . . . . . R-306
[:SENS]:DATA[:TEL]:ANAL:M2101:BISO:SES?. . . . . . . . . . . . . . . . . . R-306
[:SENS]:DATA[:TEL]:ANAL:M2101:EVAL. . . . . . . . . . . . . . . . . . . . . . . R-306
[:SENS]:DATA[:TEL]:ANAL:M2101:EVAL?. . . . . . . . . . . . . . . . . . . . . . R-307
[:SENS]:DATA[:TEL]:ANAL:M2101:S1:BBE?. . . . . . . . . . . . . . . . . . . . R-307
[:SENS]:DATA[:TEL]:ANAL:M2101:S1:ES? . . . . . . . . . . . . . . . . . . . . . R-307
xvi
Page 19
[:SENS]:DATA[:TEL]:ANAL:M2101:S1:SEP? . . . . . . . . . . . . . . . . . . . .R-308
[:SENS]:DATA[:TEL]:ANAL:M2101:S1:SES? . . . . . . . . . . . . . . . . . . . .R-308
[:SENS]:DATA[:TEL]:ANAL:M2101:S2:BBE? . . . . . . . . . . . . . . . . . . . .R-308
[:SENS]:DATA[:TEL]:ANAL:M2101:S2:ES? . . . . . . . . . . . . . . . . . . . . .R-308
[:SENS]:DATA[:TEL]:ANAL:M2101:S2:SEP? . . . . . . . . . . . . . . . . . . . .R-309
[:SENS]:DATA[:TEL]:ANAL:M2101:S2:SES? . . . . . . . . . . . . . . . . . . . .R-309
[:SENS]:DATA[:TEL]:ANAL:M2101:SEPI[:STAT] . . . . . . . . . . . . . . . . .R-309
[:SENS]:DATA[:TEL]:ANAL:M2101:SEPI[:STAT]? . . . . . . . . . . . . . . . .R-309
[:SENS]:DATA[:TEL]:ANAL:M2101:UAS:LIM[:STAT] . . . . . . . . . . . . . .R-310
[:SENS]:DATA[:TEL]:ANAL:M2101:UAS:LIM[:STAT]? . . . . . . . . . . . . .R-310
[:SENS]:DATA[:TEL]:ANAL:M2101:UAS:LIM:UPP . . . . . . . . . . . . . . . .R-310
[:SENS]:DATA[:TEL]:ANAL:M2101:UAS:LIM:UPP? . . . . . . . . . . . . . . .R-311
[:SENS]:DATA[:TEL]:ANAL:M2101:UAS:MODE . . . . . . . . . . . . . . . . . .R-311
[:SENS]:DATA[:TEL]:ANAL:M2101:UAS:MODE? . . . . . . . . . . . . . . . . .R-311
[:SENS]:DATA[:TEL]:ANAL:M2101:VERSion . . . . . . . . . . . . . . . . . . . .R-311
[:SENS]:DATA[:TEL]:ANAL:M2101:VERSion? . . . . . . . . . . . . . . . . . . .R-312
[:SENS]:DATA[:TEL]:ANAL:PERF:EVAL. . . . . . . . . . . . . . . . . . . . . . . .R-313
[:SENS]:DATA[:TEL]:ANAL:PERF:EVAL?. . . . . . . . . . . . . . . . . . . . . . .R-314
[:SENS]:DATA[:TEL]:ANAL[:TYPE]. . . . . . . . . . . . . . . . . . . . . . . . . . . .R-314
[:SENS]:DATA[:TEL]:ANAL[:TYPE]?. . . . . . . . . . . . . . . . . . . . . . . . . . .R-314
[:SENS]:DATA[:TEL]:APS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-314
[:SENS]:DATA[:TEL]:APS:GATE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-315
[:SENS]:DATA[:TEL]:APS:GATE?. . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-315
[:SENS]:DATA[:TEL]:APS:SENS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-315
[:SENS]:DATA[:TEL]:APS:SENS?. . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-316
[:SENS]:DATA[:TEL]:ATM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-316
[:SENS]:DATA[:TEL]:ATM:ANAL:CTD:OFFS . . . . . . . . . . . . . . . . . . . .R-316
[:SENS]:DATA[:TEL]:ATM:ANAL:CTD:OFFS? . . . . . . . . . . . . . . . . . . .R-317
[:SENS]:DATA[:TEL]:ATM:ANAL:CTD:RES . . . . . . . . . . . . . . . . . . . . .R-317
[:SENS]:DATA[:TEL]:ATM:ANAL:CTD:RES? . . . . . . . . . . . . . . . . . . . .R-317
[:SENS]:DATA[:TEL]:ATM:ANAL:TYPE. . . . . . . . . . . . . . . . . . . . . . . . .R-318
[:SENS]:DATA[:TEL]:ATM:ANAL:TYPE?. . . . . . . . . . . . . . . . . . . . . . . .R-318
[:SENS]:DATA[:TEL]:ATM:CLP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-319
[:SENS]:DATA[:TEL]:ATM:CLP? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-319
[:SENS]:DATA[:TEL]:ATM:CLP:FILT. . . . . . . . . . . . . . . . . . . . . . . . . . .R-319
[:SENS]:DATA[:TEL]:ATM:CLP:FILT?. . . . . . . . . . . . . . . . . . . . . . . . . .R-320
[:SENS]:DATA[:TEL]:ATM:NINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-320
[:SENS]:DATA[:TEL]:ATM:NINT? . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-320
[:SENS]:DATA[:TEL]:ATM:PAYL:SCR. . . . . . . . . . . . . . . . . . . . . . . . . .R-321
[:SENS]:DATA[:TEL]:ATM:PAYL:SCR?. . . . . . . . . . . . . . . . . . . . . . . . .R-321
[:SENS]:DATA[:TEL]:ATM:PAYL:TYPE. . . . . . . . . . . . . . . . . . . . . . . . .R-321
[:SENS]:DATA[:TEL]:ATM:PAYL:TYPE?. . . . . . . . . . . . . . . . . . . . . . . .R-321
[:SENS]:DATA[:TEL]:ATM:SENS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-322
[:SENS]:DATA[:TEL]:ATM:SENS?. . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-322
[:SENS]:DATA[:TEL]:ATM:VCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-323
[:SENS]:DATA[:TEL]:ATM:VCI? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-323
[:SENS]:DATA[:TEL]:ATM:VCI:FILT . . . . . . . . . . . . . . . . . . . . . . . . . . .R-323
[:SENS]:DATA[:TEL]:ATM:VCI:FILT? . . . . . . . . . . . . . . . . . . . . . . . . . .R-323
xvii
Page 20
[:SENS]:DATA[:TEL]:ATM:VPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-324
[:SENS]:DATA[:TEL]:ATM:VPI? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-324
[:SENS]:DATA[:TEL]:ERR:FAS:AMOD. . . . . . . . . . . . . . . . . . . . . . . . . R-324
[:SENS]:DATA[:TEL]:ERR:FAS:AMOD?. . . . . . . . . . . . . . . . . . . . . . . . R-325
[:SENS]:DATA[:TEL]:ERR:TSE:AMOD. . . . . . . . . . . . . . . . . . . . . . . . . R-325
[:SENS]:DATA[:TEL]:ERR:TSE:AMOD?. . . . . . . . . . . . . . . . . . . . . . . . R-325
[:SENS]:DATA[:TEL]:LED:AUL[:STAT]. . . . . . . . . . . . . . . . . . . . . . . . . R-325
[:SENS]:DATA[:TEL]:LED:AUL[:STAT]?. . . . . . . . . . . . . . . . . . . . . . . . R-326
[:SENS]:DATA[:TEL]:LED:TUL[:STAT] . . . . . . . . . . . . . . . . . . . . . . . . . R-326
[:SENS]:DATA[:TEL]:LED:TUL[:STAT]?. . . . . . . . . . . . . . . . . . . . . . . . R-326
[:SENS]:DATA[:TEL]:FLEX:RES:SEL. . . . . . . . . . . . . . . . . . . . . . . . . . R-327
[:SENS]:DATA[:TEL]:FLEX:RES:SEL?. . . . . . . . . . . . . . . . . . . . . . . . . R-327
[:SENS]:DATA[:TEL]:PAYL:PATT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-328
[:SENS]:DATA[:TEL]:PAYL:PATT?. . . . . . . . . . . . . . . . . . . . . . . . . . . . R-329
[:SENS]:DATA[:TEL]:PAYL:UWOR. . . . . . . . . . . . . . . . . . . . . . . . . . . . R-329
[:SENS]:DATA[:TEL]:PAYL:UWOR?. . . . . . . . . . . . . . . . . . . . . . . . . . . R-329
[:SENS]:DATA[:TEL]:PDH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-330
[:SENS]:DATA[:TEL]:PDH:DS1:CHAN . . . . . . . . . . . . . . . . . . . . . . . . . R-330
[:SENS]:DATA[:TEL]:PDH:DS1:CHAN? . . . . . . . . . . . . . . . . . . . . . . . . R-331
[:SENS]:DATA[:TEL]:PDH:DS1:FRAM . . . . . . . . . . . . . . . . . . . . . . . . . R-331
[:SENS]:DATA[:TEL]:PDH:DS1:FRAM? . . . . . . . . . . . . . . . . . . . . . . . . R-331
[:SENS]:DATA[:TEL]:PDH:DS3:CHAN . . . . . . . . . . . . . . . . . . . . . . . . . R-332
[:SENS]:DATA[:TEL]:PDH:DS3:CHAN? . . . . . . . . . . . . . . . . . . . . . . . . R-332
[:SENS]:DATA[:TEL]:PDH:DS3:FEAC:LOOP:RES. . . . . . . . . . . . . . . . R-332
[:SENS]:DATA[:TEL]:PDH:DS3:FRAM . . . . . . . . . . . . . . . . . . . . . . . . . R-333
[:SENS]:DATA[:TEL]:PDH:DS3:FRAM? . . . . . . . . . . . . . . . . . . . . . . . . R-333
[:SENS]:DATA[:TEL]:PDH:FRAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-334
[:SENS]:DATA[:TEL]:PDH:FRAM? . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-334
[:SENS]:DATA[:TEL]:PDH:M2:CHAN . . . . . . . . . . . . . . . . . . . . . . . . . . R-335
[:SENS]:DATA[:TEL]:PDH:M2:CHAN? . . . . . . . . . . . . . . . . . . . . . . . . . R-335
[:SENS]:DATA[:TEL]:PDH:M2:FRAM . . . . . . . . . . . . . . . . . . . . . . . . . . R-336
[:SENS]:DATA[:TEL]:PDH:M2:FRAM? . . . . . . . . . . . . . . . . . . . . . . . . . R-336
[:SENS]:DATA[:TEL]:PDH:M2:SEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . R-337
[:SENS]:DATA[:TEL]:PDH:M2:SEQ? . . . . . . . . . . . . . . . . . . . . . . . . . . R-337
[:SENS]:DATA[:TEL]:PDH:M8:CHAN . . . . . . . . . . . . . . . . . . . . . . . . . . R-338
[:SENS]:DATA[:TEL]:PDH:M8:CHAN? . . . . . . . . . . . . . . . . . . . . . . . . . R-338
[:SENS]:DATA[:TEL]:PDH:M34:CHAN . . . . . . . . . . . . . . . . . . . . . . . . . R-339
[:SENS]:DATA[:TEL]:PDH:M34:CHAN? . . . . . . . . . . . . . . . . . . . . . . . . R-339
[:SENS]:DATA[:TEL]:PDH:M34:FTYP . . . . . . . . . . . . . . . . . . . . . . . . . R-340
[:SENS]:DATA[:TEL]:PDH:M34:FTYP? . . . . . . . . . . . . . . . . . . . . . . . . R-340
[:SENS]:DATA[:TEL]:PDH:M34:G832:OVER:PLAB . . . . . . . . . . . . . . . R-341
[:SENS]:DATA[:TEL]:PDH:M34:G832:OVER:PLAB? . . . . . . . . . . . . . . R-341
[:SENS]:DATA[:TEL]:PDH:M34:G832:OVER:TRAC:FREF . . . . . . . . . R-342
[:SENS]:DATA[:TEL]:PDH:M34:G832:OVER:TRAC:FREF? . . . . . . . . R-342
[:SENS]:DATA[:TEL]:PDH:M34:G832:OVER:TRAC:REF. . . . . . . . . . . R-343
[:SENS]:DATA[:TEL]:PDH:M34:G832:OVER:TRAC:REF?. . . . . . . . . . R-343
[:SENS]:DATA[:TEL]:PDH:M140:CHAN . . . . . . . . . . . . . . . . . . . . . . . . R-344
[:SENS]:DATA[:TEL]:PDH:M140:CHAN? . . . . . . . . . . . . . . . . . . . . . . . R-344
xviii
Page 21
[:SENS]:DATA[:TEL]:PDH:M140:FTYP. . . . . . . . . . . . . . . . . . . . . . . . .R-345
[:SENS]:DATA[:TEL]:PDH:M140:FTYP?. . . . . . . . . . . . . . . . . . . . . . . .R-345
[:SENS]:DATA[:TEL]:PDH:M140:G832:OVER:PLAB . . . . . . . . . . . . . .R-346
[:SENS]:DATA[:TEL]:PDH:M140:G832:OVER:PLAB? . . . . . . . . . . . . .R-346
[:SENS]:DATA[:TEL]:PDH:M140:G832:OVER:TRAC:FREF. . . . . . . . .R-347
[:SENS]:DATA[:TEL]:PDH:M140:G832:OVER:TRAC:FREF?. . . . . . . .R-347
[:SENS]:DATA[:TEL]:PDH:M140:G832:OVER:TRAC:REF . . . . . . . . . .R-348
[:SENS]:DATA[:TEL]:PDH:M140:G832:OVER:TRAC:REF? . . . . . . . . .R-348
[:SENS]:DATA[:TEL]:PDH:PAYL:TYPE. . . . . . . . . . . . . . . . . . . . . . . . .R-349
[:SENS]:DATA[:TEL]:PDH:PAYL:TYPE?. . . . . . . . . . . . . . . . . . . . . . . .R-349
[:SENS]:DATA[:TEL]:PDH:RATE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-350
[:SENS]:DATA[:TEL]:PDH:RATE?. . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-351
[:SENS]:DATA[:TEL]:SDH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-352
[:SENS]:DATA[:TEL]:SDH:ALAR:RDIE:AMOD . . . . . . . . . . . . . . . . . . .R-352
[:SENS]:DATA[:TEL]:SDH:ALAR:RDIE:AMOD? . . . . . . . . . . . . . . . . . .R-352
[:SENS]:DATA[:TEL]:SDH:CHAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-353
[:SENS]:DATA[:TEL]:SDH:CHAN? . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-354
[:SENS]:DATA[:TEL]:SDH:ERR:BIP:AMOD . . . . . . . . . . . . . . . . . . . . .R-355
[:SENS]:DATA[:TEL]:SDH:ERR:BIP:AMOD? . . . . . . . . . . . . . . . . . . . .R-355
[:SENS]:DATA[:TEL]:SDH:ERR:TSE:SOUR . . . . . . . . . . . . . . . . . . . . .R-356
[:SENS]:DATA[:TEL]:SDH:ERR:TSE:SOUR? . . . . . . . . . . . . . . . . . . . .R-356
[:SENS]:DATA[:TEL]:SDH:MAPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-357
[:SENS]:DATA[:TEL]:SDH:MAPP? . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-357
[:SENS]:DATA[:TEL]:SDH:MAPP:CONC[:MODE]. . . . . . . . . . . . . . . . .R-358
[:SENS]:DATA[:TEL]:SDH:MAPP:CONC[:MODE]?. . . . . . . . . . . . . . . .R-358
[:SENS]:DATA[:TEL]:SDH:MAPP:CONC:CSIZ . . . . . . . . . . . . . . . . . . .R-359
:[SENS]:DATA[:TEL]:SDH:MAPP:CONC:CSIZ? . . . . . . . . . . . . . . . . . .R-359
[:SENS]:DATA[:TEL]:SDH:MAPP:TUFL . . . . . . . . . . . . . . . . . . . . . . . .R-360
[:SENS]:DATA[:TEL]:SDH:MAPP:TUFL? . . . . . . . . . . . . . . . . . . . . . . .R-360
[:SENS]:DATA[:TEL]:SDH:OVER:BYT . . . . . . . . . . . . . . . . . . . . . . . . .R-361
[:SENS]:DATA[:TEL]:SDH:OVER:BYT? . . . . . . . . . . . . . . . . . . . . . . . .R-361
[:SENS]:DATA[:TEL]:SDH:OVER:DROP[:MODE]. . . . . . . . . . . . . . . . .R-362
[:SENS]:DATA[:TEL]:SDH:OVER:DROP[:MODE]?. . . . . . . . . . . . . . . .R-362
[:SENS]:DATA[:TEL]:SDH:OVER:RSTR:FREF. . . . . . . . . . . . . . . . . . .R-362
[:SENS]:DATA[:TEL]:SDH:OVER:RSTR:FREF?. . . . . . . . . . . . . . . . . .R-363
[:SENS]:DATA[:TEL]:SDH:OVER:RSTR:REF . . . . . . . . . . . . . . . . . . . .R-363
[:SENS]:DATA[:TEL]:SDH:OVER:RSTR:REF? . . . . . . . . . . . . . . . . . . .R-364
[:SENS]:DATA[:TEL]:SDH:OVER:TCM:RES. . . . . . . . . . . . . . . . . . . . .R-364
:[SENS]:DATA[:TEL]:SDH:OVER:TCM:TYPE. . . . . . . . . . . . . . . . . . . .R-364
:[SENS]:DATA[:TEL]:SDH:OVER:TCM:TYPE?. . . . . . . . . . . . . . . . . . .R-364
[:SENS]:DATA[:TEL]:SDH:PAYL:TYPE. . . . . . . . . . . . . . . . . . . . . . . . .R-365
[:SENS]:DATA[:TEL]:SDH:PAYL:TYPE?. . . . . . . . . . . . . . . . . . . . . . . .R-365
[:SENS]:DATA[:TEL]:SDH:POIN:SSR. . . . . . . . . . . . . . . . . . . . . . . . . .R-366
[:SENS]:DATA[:TEL]:SDH:POIN:SSR? . . . . . . . . . . . . . . . . . . . . . . . . .R-366
[:SENS]:DATA[:TEL]:SDH:POV:HPTR:FREF . . . . . . . . . . . . . . . . . . . .R-366
[:SENS]:DATA[:TEL]:SDH:POV:HPTR:FREF? . . . . . . . . . . . . . . . . . . .R-367
[:SENS]:DATA[:TEL]:SDH:POV:HPTR:REF . . . . . . . . . . . . . . . . . . . . .R-367
[:SENS]:DATA[:TEL]:SDH:POV:HPTR:REF? . . . . . . . . . . . . . . . . . . . .R-368
xix
Page 22
[:SENS]:DATA[:TEL]:SDH:POV:HSEQ. . . . . . . . . . . . . . . . . . . . . . . . . R-368
[:SENS]:DATA[:TEL]:SDH:POV:HSEQ?. . . . . . . . . . . . . . . . . . . . . . . . R-368
[:SENS]:DATA[:TEL]:SDH:POV:PLAB . . . . . . . . . . . . . . . . . . . . . . . . . R-369
[:SENS]:DATA[:TEL]:SDH:POV:PLAB? . . . . . . . . . . . . . . . . . . . . . . . . R-369
[:SENS]:DATA[:TEL]:SDH:RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-370
[:SENS]:DATA[:TEL]:SDH:RATE? . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-370
[:SENS]:DATA[:TEL]:SDH:SCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-371
[:SENS]:DATA[:TEL]:SDH:SCR? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-371
[:SENS]:DATA[:TEL]:SDH:STMN:CHAN . . . . . . . . . . . . . . . . . . . . . . . R-372
[:SENS]:DATA[:TEL]:SDH:STMN:CHAN? . . . . . . . . . . . . . . . . . . . . . . R-372
[:SENS]:DATA[:TEL]:SDH:STSN:CHAN. . . . . . . . . . . . . . . . . . . . . . . . R-373
[:SENS]:DATA[:TEL]:SDH:STSN:CHAN?. . . . . . . . . . . . . . . . . . . . . . . R-373
[:SENS]:DATA[:TEL]:SDH:STSV:CHAN. . . . . . . . . . . . . . . . . . . . . . . . R-374
[:SENS]:DATA[:TEL]:SDH:STSV:CHAN?. . . . . . . . . . . . . . . . . . . . . . . R-374
[:SENS]:DATA[:TEL]:SDH:TRIB:MAPP . . . . . . . . . . . . . . . . . . . . . . . . R-375
[:SENS]:DATA[:TEL]:SDH:TRIB:MAPP? . . . . . . . . . . . . . . . . . . . . . . . R-375
[:SENS]:DATA[:TEL]:SDH:TRIB:POV:LPTR:FREF . . . . . . . . . . . . . . . R-375
[:SENS]:DATA[:TEL]:SDH:TRIB:POV:LPTR:FREF? . . . . . . . . . . . . . . R-376
[:SENS]:DATA[:TEL]:SDH:TRIB:POV:LPTR:REF . . . . . . . . . . . . . . . . R-376
[:SENS]:DATA[:TEL]:SDH:TRIB:POV:LPTR:REF? . . . . . . . . . . . . . . . R-377
[:SENS]:DATA[:TEL]:SDH:TRIB:POV:PLAB. . . . . . . . . . . . . . . . . . . . . R-377
[:SENS]:DATA[:TEL]:SDH:TRIB:POV:PLAB?. . . . . . . . . . . . . . . . . . . . R-378
[:SENS]:DATA[:TEL]:SENS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-378
[:SENS]:DATA[:TEL]:SENS? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-378
[:SENS]:DATA[:TEL]:STAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-378
[:SENS]:DATA[:TEL]:STAN?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-379
[:SENS]:FUNC:OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-380
[:SENS]:FUNC:OFF:ALL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-380
[:SENS]:FUNC[:ON] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-381
[:SENS]:FUNC[:ON]? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-381
Result IDs for :SENS:DATA and :SENS:FUNC commands . . . . . . . . . R-382
[:SENS]:FUNC:EVEN[:OFF] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-404
[:SENS]:FUNC:EVEN:OFF:ALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-404
[:SENS]:FUNC:EVEN[:ON]. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-405
[:SENS]:FUNC:EVEN[:ON]?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-406
[:SENS]:MODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-406
[:SENS]:MODE? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-406
[:SENS]:SWE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-407
[:SENS]:SWE:ITIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-407
[:SENS]:SWE:ITIM? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-407
[:SENS]:SWE:TIME. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-408
[:SENS]:SWE:TIME?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R-408
xx
Page 23
11 FETCH subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-409
:FETC[:ARR][:DATA][:TEL]:HIST:ATM:CTD? . . . . . . . . . . . . . . . . . . . .R-409
:FETC[:ARR][:DATA][:TEL]:HIST:ATM:FCEL[:BITRate]? . . . . . . . . . . .R-410
:FETC[:ARR][:DATA][:TEL]:HIST:ATM:LCEL[:BITRate]? . . . . . . . . . . .R-411
:FETC[:ARR][:DATA][:TEL]:PDH:BITS? . . . . . . . . . . . . . . . . . . . . . . . .R-412
:FETC[:ARR][:DATA][:TEL]:PDH:OVER? . . . . . . . . . . . . . . . . . . . . . . .R-413
:FETC[:ARR][:DATA][:TEL][:SDH]:OVER? . . . . . . . . . . . . . . . . . . . . . .R-414
:FETC[:ARR][:DATA][:TEL][:SDH]:OVER:PART[i]?. . . . . . . . . . . . . . . .R-415
:FETC[:ARR][:DATA][:TEL][:SDH]:OVER:CPARt[i]? . . . . . . . . . . . . . . .R-416
:FETC[:ARR][:DATA][:TEL][:SDH]:OVER:CAPT? . . . . . . . . . . . . . . . . .R-417
FIFO data structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R-419
:FETC[:ARR][:DATA][:TEL][:SDH]:OVER:CAPT:NUMB? . . . . . . . . . . .R-420
:FETC[:ARR][:DATA][:TEL][:SDH]:POV?. . . . . . . . . . . . . . . . . . . . . . . .R-421
:FETC[:ARR][:DATA][:TEL][:SDH]:TRIB:POV? . . . . . . . . . . . . . . . . . . .R-422
:FETC:SCAL[:DATA][:TEL]:PDH:M2:SBIT? . . . . . . . . . . . . . . . . . . . . .R-423
:FETC:SCAL[:DATA][:TEL][:SDH]:OVER? . . . . . . . . . . . . . . . . . . . . . .R-423
:FETC:SCAL[:DATA][:TEL][:SDH]:OVER:PART[i]?. . . . . . . . . . . . . . . .R-425
:FETC:SCAL[:DATA][:TEL][:SDH]:OVER:CPARt[i]? . . . . . . . . . . . . . . .R-426
:FETC:SCAL[:DATA][:TEL][:SDH]:TRIB:SSBits? . . . . . . . . . . . . . . . . .R-427
:FETC:STR[:DATA][:TEL]:PDH:TRAC?. . . . . . . . . . . . . . . . . . . . . . . . .R-428
:FETC:STR[:DATA][:TEL][:SDH]:HPTR?. . . . . . . . . . . . . . . . . . . . . . . .R-429
:FETC:STR[:DATA][:TEL][:SDH]:LPTR? . . . . . . . . . . . . . . . . . . . . . . . .R-430
:FETC:STR[:DATA][:TEL][:SDH]:RSTR?. . . . . . . . . . . . . . . . . . . . . . . .R-431
:FETC:STR[:DATA][:TEL][:SDH]:TCMonitoring:TRACe? . . . . . . . . . . .R-432
xxi
Page 24
Appendix: Theory / Standards
1 Recommendations / Standards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
1.1 ITU-T recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
1.2 ANSI standards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
1.3 Bellcore standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
1.4 ETSI standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
1.5 ATM Forum recommendations . . . . . . . . . . . . . . . . . . . . . A-6
2 Alarm messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
2.1 SDH/SONET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
2.2 ATM Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
2.3 Virtual Concatenation. . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
3 Multiplexing structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12
3.1 SDH Multiplexing Structure ITU-T G.707 . . . . . . . . . . . . A-12
3.2 SONET Multiplexing Structure ANSI T1.105-1995 . . . . . A-12
4 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13
5 SONET and SDH equivalent terms . . . . . . . . . . . . . . . . . . . . . . . . . A-23
xxii
Page 25
ANT-20 (Mainframe) 1 ANT-20, ANT-20E, ANT-20SE

Introduction

1 ANT-20, ANT-20E, ANT-20SE

1.1 General information

The following information also applies to the ABT-20.
For “ANT-20”, read “ABT-20”.
1.1.1 Overview
The ANT-20 can be remotely controlled using the
IEEE 488 (IEC 625) interface, often referred to as GPIB: Option BN 3035/92.10, Remote Control GPIB (PCMCIA)
– or –
V.24/V.28 (RS 232) interface: Option BN 3035/91.01, Remote Control V.24
The programming commands are identical, regardless of the type of remote control interface that is used.
The ANT-20 must be switched to remote control mode manually. In remote control mode, manual control of the ANT-20 is not possible.
To set the ANT-20 to remote control mode, follow these steps ANT-20, ANT-20E with
Windows 3.11: Double-click on the “Remote” icon in the “ANT-20” group in the
“Program Manager” window.
Windows95: 1. Enable remote control mode using the taskbar:
“Start/ANT-20/Remote On”.
2. Double-click on the “ANT-20” icon on the desktop – or – use the taskbar: “Start/ANT-20/ANT-20”.
To switch back to normal manual control, follow these steps ANT-20, ANT-20E with
Windows 3.11: Double-click on the “Remote Disable” icon in the “ANT-20”
group in the “Program Manager” window.
Windows95: 1. Disable remote control mode using the taskbar:
“Start/ANT-20/Remote Off”.
2. Double-click on the “ANT-20” icon on the desktop – or – use the taskbar: “Start/ANT-20/ANT-20”.
Introduction I-1
Page 26
1 ANT-20, ANT-20E, ANT-20SE ANT-20 (Mainframe)
From the viewpoint of remote control, each measuring module in the ANT-20 is a fully remote­controllable instrument with its own SCPI command tree, status reporting system and common command set.
The measuring module to be controlled is selected using the command MODule:SELect <module_name> (see Sec. 1.1.2).
The instrument’s display shows which measuring modules exist and which one is selected for remote control.
A built-in monitor function can be switched on for debugging purposes (see Sec. 1.1.3). To change the type of the remote control interface and/or its accompanying configuration
parameters, the batch file remote.bat must be edited.
ANT-20, ANT-20E with Windows 3.11: 1. Double-click on the “Remote Configuration” icon in the
“ANT-20” group in the “Program Manager” window to edit the remote.bat file.
2. Follow the on-screen instructions.
Windows95: 1. Click on the “Remote Configuration” icon via taskbar: “Start/
ANT-20/Remote Configuration” to edit the remote.bat file.
2. Follow the on-screen instructions.
1.1.2 Module selection
The remote control interface of the ANT-20 supports multiple internal mea suring modules. The module selection provides a mechanism to select one of these measuring modules for remote control.
Keyword Parameter form Notes MODule:SELect <module_name>
1 <module_name>: BASIC | JITTER | JITT16 | BAG
Table I-1 Module selection
This command selects the measuring module specified by <module_na me> for remote contro l and deselects all others. All subsequent commands (including commands in subsequent program messages) are passed to the selected measuring module. All other measuring modules are unavailable for programming until selected.
<module_name>: BASIC: Selects BASIC Module
JITTER: Selects JITTER Module for bit rates up to STM4/OC12 (extension slot)
JITT16: Selects JITTER Module for bit rates of STM16/OC48 (extension slot)
BAG: Selects BAG Module (Broadband Analyzer/Generator)
(not available for ABT-20)
(not available for ABT-20)
1
[no query]
Note: This command has no query form.
After power-on, the BASIC measuring module is selected.
If the MODule:SELect <module_name> command is required in a program
message, it must be the first (or the only) command in that program message.
I-2 Introduction
Page 27
ANT-20 (Mainframe) 1 ANT-20, ANT-20E, ANT-20SE
1.1.3 Monitor mode
A monitor function can be switched on or off in remote control mode. If it is switched on, the instrument displays all messages sent to and from the instrument, corresponding to each operating step performed.
1.1.4 LabWindows/CVI driver
A LabWindows/CVI instrument driver is available for each measuring module. Instrument drivers reduce application program development time and simplify instrument
control by eliminating the need to learn the complex programming commands fo r each measuring module.

1.2 GPIB Remote Control interface

This section describes the GPIB Remote Control interface for applications using the ANT- 20 as a remote controlled instrument.
Other applications using the ANT-20 as a GPIB controller for controlling external instruments are also possible (e.g. running the WG CA TS Test Executive BN 3045 on the ANT-20 to control the ANT-20 measurement hardware plus external instruments).
To allow both these mutually exclusive operating modes to b e used, the GPIB Remote Cont rol interface and installation comprises all the software required for both operating modes.
1.2.1 Items included
The Remote Control GPIB (PCMCIA) Option BN 3035/92.10 comprises:
ANT-20, ANT-20E with Windows 3.11: PCMCIA GPIB card including PCMCIA to GPIB cable
Windows95: PCMCIA GPIB card including PCMCIA to GPIB cable
(2 meters)
CardWare User’s Manual (Award Software Inc.)
Distribution disk: CardWare Version 2.0 (Award Software Inc.)
Installation disks: ANT-20 PCMCIA System (configured
CardWare 2.0), ANT-20 GPIB Remote Control (includes NI-488.2)
ANT-20 GPIB (NI-488.2) for Windows 3.x
Operating Manual: Remote Control
Brochure “SCPI and IEEE 488, Programmer‘s Introduction”
(2 meters)
Installation disks: ANT-20 GPIB Remote Control for Windows95 (includes NI-488.2M)
Operating Manual: Remote Control
Brochure “SCPI and IEEE 488, Programmer‘s Introduction”
Introduction I-3
Page 28
1 ANT-20, ANT-20E, ANT-20SE ANT-20 (Mainframe)
1.2.2 Installation
1.2.2.1 Overview
The PCMCIA GPIB interface from National Instruments Corp. (NI) is used with the NI-488.2/ NI-488.2M software for GPIB Remote Control.
For ANT-20 with Windows 3.11 only:
The NI-488.2 software requires standardized PCMCIA system software with Socket and Card Services (version 2.0 or higher) to be installed.
A software called CardWare (written by Award Software Inc.) is used as PCMCIA system software. It can also be used with a wide variety of other PCMCIA cards.
The CardWare software contained on the installation disk is already configured for use with the ANT-20.
1.2.2.2 Software installation
Software installation under Windows 3.11
If you ordered the Remote Control GPIB Option BN 3035/92.10 together with your ANT-20, the
required software packages are already installed on the ANT-20 and the icons “Remote”, “Remote Disable” and “Remote Configuration” are shown in the “ANT-20” group in th e “Program Manager” window.
Note: A release code is required to enable the Remote Control GPIB Option.
For detailed information contact your nearest Wavetek Wandel Goltermann Service Center. The addresses are listed at the end of this manual. When contacting the Service Center, always quote:
The serial number of the ANT-20
The version number of the ANT-20 software package
If you ordered the Remote Control GPIB Option BN 3035/92.10 separately, install the software packages as follows:
Installing the PCMCIA System software
1. Start or return to Windows.
2. Insert the ANT-20 PCMCIA System installation disk into drive A:.
3. Choose “Run ...” from the “File” menu in the “Program Manager” wind ow and type the following command into the dialog box: A:\setup Confirm with “OK”.
4. After complete installation exit Windows, remove the installation disk from drive A:, and reboot the ANT-20.
Installing the GPIB Remote Control software
1. Start or return to Windows.
2. Insert the ANT-20 GPIB Remote Control installation disk into drive A:.
I-4 Introduction
Page 29
ANT-20 (Mainframe) 1 ANT-20, ANT-20E, ANT-20SE
3. Choose “Run ...” from the “File” menu in the “Program Manager” window and
type the following command into the dialog box: A:\setup Confirm with “OK”.
4. After complete installation exit Windows, remove the installation disk from drive A:, and reboot the ANT-20.
Installing the ANT-20 Remote Control software
1. Start or return to Windows
2. Choose “Run...” from the “File” menu in the “Program Manager” window and type the following command into the dialog box: C:\ANT20.SUP\DISK1\setup.exe Confirm with “OK”.
3. Follow the on-screen instructions to install the ANT-20 Remote Control.
4. After complete installation exit Windows, and reboot the ANT-20.
After this installation procedure, the ANT-20 can be set to remote control mode by double­clicking on the “Remote” icon in the “ANT-20” group in the “Program Manager” window.
Installing the GPIB (NI-488.2) for Windows 3.x
This software is required for applications that use the ANT-20 as a GPIB controller for controlling external instruments (e.g. for running the WG CATS Test Executive BN 3045 on the ANT-20 to control the ANT-20 measurement hardware plus external instruments).
1. Start or return to Windows.
2. Insert the installation disk ANT-20 GPIB (NI-488.2) for Windows 3.x into drive A:.
3. Choose “Run...” from the “File” menu in the “Program Manager” window and type the following command into the dialog box: A:\setup Confirm with “OK”.
4. Follow the on-screen instructions to complete the installation.
5. After complete installation exit Windows, remove the installation disk from drive A:, and reboot the ANT-20.
After this installation procedure, you can access the “NI-488.2 PCMCIA GPIB So ftware” g ro up in the “Program Manager” window.
To view or modify the NI-488.2 software configuration, double-click the “GPIB” icon from the “Control Panel” in the “Main” group of the “Program Manager” window.
Software installation under Windows95
If you ordered the Remote Control GPIB Option BN 3035/92.10 together with your ANT-20, the required software packages are already installed on the ANT-20 and the icons “Remote On”, “Remote Off” and “Remote Configuration” ar e shown in the Windows95 file folder “ANT-20”.
Note: A release code is required to enable the Remote Control GPIB Option.
For detailed information contact your nearest Wavetek Wandel Goltermann Service Center. The addresses are listed at the end of this manual. When contacting the Service Center, always qu o te :
The serial number of the ANT-20
The version number of the ANT-20 software package
Verify the PCMCIA GPIB card installation as described in section “Verify the PCMCIA GPIB card installation” below.
Introduction I-5
Page 30
1 ANT-20, ANT-20E, ANT-20SE ANT-20 (Mainframe)
If you ordered the Remote Control GPIB Option BN 3035/92.10 separately, install the software packages as follows:
Installing the GPIB Remote Control software
1. Start or return to Windows95.
2. Insert the ANT-20 GPIB Remote Control for Windows95 installation disk 1 into drive A:.
3. Click the Windows95 “Start” button, choose “Run ...” and
type the following command into the dialog box: A:\setup Confirm with “OK”.
4. Follow the on-screen instructions during the installation procedure and en ter C:\Tmp\Gpib as GPIB distribution directory.
5. After completion, click the Windows95 “Start” button, choose “Run...” and type the following command into the dialog box: C:\Tmp\Gpib\gpib9513.exe Confirm with “OK”.
6. Follow the on-screen instructions during the setup procedure and use the default selection for components to install (all components selected).
7. After complete installation: – Shut down the ANT-20. – Remove the installation disk from drive A:. – Insert the PCMCIA GPIB card into a free PCMCIA slot. – Reboot the ANT-20.
Enable support for DOS applications as described below (by default, DOS sup port is disabled):
1. Return to Windows95, click the Windows95
“Start” button, choose “Settings” and then choose “Control Panel” from the submenu. In the “Control Panel” window, double-click the “System” icon.
2. In the “Device Manager” tab of the “System Properties” window, choose “View devices by type”, click on the “National Instruments GPIB Interfaces” icon in the list and then click on the “Properties” button.
3. In the “General” tab in the “National Instruments GPIB Interfaces Pr opertie s” window se lect the checkbox “Enable Support for DOS GPIB Applications” and confirm with “OK”.
4. Reboot the ANT-20.
Verify the PCMCIA GPIB card installation
1. The PCMCIA GPIB card must be in the slot!
2. Click the Windows95 “Start” button, choose “Settings” and then choose “Control Panel” from the submenu. In the “Control Panel” window, double-click the “System” icon.
3. In the “Device Manager” tab of the “System Properties” window, choose “View devices by type”, double-click the “National Instruments GPIB Interfaces” icon in the list and then double-click “PCMCIA GPIB” in the sublist.
4. In the “GPIB Settings” tab of the “PCMCIA GPIB Properties” window, the entry for “Interface Name” must be “GPIB0”. If it is not, change it to “GPIB0”.
5. Deactivate the “System Controller” checkbox. (All other parameters are properly set by starting the ANT-20 remote control mode after completion of the installation procedure.)
6. Confirm with “OK”.
I-6 Introduction
Page 31
ANT-20 (Mainframe) 1 ANT-20, ANT-20E, ANT-20SE
Installing the ANT-20 Remote Control software
1. Start or return to Windows95.
2. Click the Windows95 “Start” button,
choose “Run...” and type the following command into the dialog box: C:\ANT20.SUP\DISK1\setup.exe Confirm with “OK”.
3. Follow the on-screen instructions to install the ANT-20 Remote Control and select only the “Remote Control Software” as component to install.
The following patch installation described in steps 4, 5 and 6 is only required for ANT-20 software versions less or equal 7.0. It has no effect on versions greater than 7.0.
4. Insert the ANT-20 GPIB Remote Control for Windows95 installation disk 3 into drive A:.
5. Click on the Windows95 “Start” button, choose “Run...” and type the following command into the dialog box: A:\setup Confirm with “OK”.
6. Follow the on-screen instructions. After completion, remove the installation disk from drive A:.
Note: Only for ANT-20 software versions less or equal 7.0:
If there is any need to execute C:\ANT20.SUP\DISK1\setup.exe (with the component “Remote Control Software” selected) at a later time again, the above described patch installation (steps 4, 5 and 6) must also be executed again.
7. Exit Windows95 and reboot the AN T- 20 .
After this installation procedure, you can enable the remote control mode by using the taskbar:
1. “Start/ANT-20/Remote On”.
2. Then double-click on the “ANT-20” icon on the desktop or use the taskbar: “Start/ANT-20/ANT-20”.
1.2.2.3 Hardware installation
1. Insert the PCMCIA GPIB card into a free PCMCIA socket the same way you insert a disk into a floppy drive. The PCMCIA GPIB has no jumpers or switches to set, and you do not need to power down the ANT-20 when you insert or remove the card.
2. Connect the PCMCIA GPIB cable to the PCMCIA GPIB card.
Introduction I-7
Page 32
1 ANT-20, ANT-20E, ANT-20SE ANT-20 (Mainframe)
1.2.3 Connecting to GPIB
The GPIB Remote Control interface is equipped with a standar d 24-way con nector con forming to IEEE 488.1.
GPIB cables of various lengths are available for connecting the ANT-20 to other instr uments and to the bus controller:
1.2 m long: Part number K 420
2.0 m long: Part number K 421
Note: The total length of GPIB cable must not exceed 2 meters x the number of
instruments in the interface system.
Up to 15 instruments can be connected to the interface system. The maximum cable run used to connect a group of instruments is 20 meters. For more info rmation re fer to the IEEE 488.1 standard.
Longer distances can be bridged using interface couplers (2-wire or 4-wire connections, if necessary with suitable modems).
1.2.4 Device address
Each instrument in the interface system must have a unique address to allow the controller to access each one individually.
The ANT-20 address can be changed by editing the remote.bat batch file. Any address in the range 0 to 30 can be selected.
ANT-20, ANT-20E with Windows 3.11: 1. Double-click on the “Remote Configuration” icon in the
“ANT-20” group in the “Program Manager” window to edit the remote.bat file.
2. Follow the on-screen instructions.
Windows95: 1. Click on the “Remote Configuration” icon via taskbar: “Start/
ANT-20/Remote Configuration” to edit the remote.bat file.
2. Follow the on-screen instructions.
Note: Make sure that a given address is used only once within the interface system. The
controller address is reserved for the controller.
I-8 Introduction
Page 33
ANT-20 (Mainframe) 1 ANT-20, ANT-20E, ANT-20SE
1.2.5 Interface functions
1.2.5.1 Overview
Interface function Note SH1 Source Handshake Complete capability
AH1 Acceptor Handshake Complete capability T8 Talker No Talk Only capability
No Serial Poll capability L4 Listener No Listen Only capability SR0 Service Request No capability RL0 Remote/Local No capability PP0 Parallel Poll No capability DC1 Device Clear Complete capability DT0 Device Trigger No capability C0 Controller No capability
Table I-2 Interface functions conforming to the IEEE 488.1 standard
1.2.5.2 Device Clear
When the IEEE 488 interface message Device Clear ( DCL) o r Selected Device Clea r (SDC) is sent to the ANT-20, a device clear message is routed to all internal measuring modules, regardless of whether they are selected or deselected.
The device clear message initializes remote control of the instrument and ensures that a subsequently sent program message will be accepted and processed.
No instrument initialization is performed by DCL or SDC. To initialize the instrument, select every measuring module and send the reset command *RST (MODule:SELect <module_name>; *RST).

1.3 V.24/V.28 (RS 232) Remote Control interface

1.3.1 Items included
The Remote Control V.24/RS 232 Option BN 3035/91.01 consists of
Remote Control Operating Manual
Brochure “SCPI and IEEE 488, Programmer’s Introduction”
1.3.2 Installation
For remote control via RS 232 the built-in serial port (COM1) of the embedded PC-AT is used.
Introduction I-9
Page 34
1 ANT-20, ANT-20E, ANT-20SE ANT-20 (Mainframe)
1.3.2.1 Software installation
Software installation under Windows 3.11
If you ordered the Remote Control V.24/V.28 ( RS 232) Option BN 3035/91.01 together with your ANT-20, the required software package is already installed on the ANT-20 and the icons
“Remote”, “Remote Disable” and “Remote Configuration” are shown in the “ANT-20” group in the “Program Manager” window.
Note: A release code is required to enable the Rem ote Control V.24/V.28 (RS 23 2) Option.
For detailed information contact your nearest Wavetek Wandel Goltermann Se rvice Center. The addresses are listed at the end of this manual. When contacting the Service Center, always quote:
The serial number of the ANT-20
The version number of the ANT-20 software package
If you ordered the Remote Control V.24/V.28 ( RS 232) Option BN 3035/91.01 separately, install the software package as follows:
Installing the ANT-20 Remote Control software
1. Start or return to Windows
2. Choose “Run...” from the “File” menu in the “Program Manager” window and type the following command into the dialog box: C:\ANT20.SUP\DISK1\setup.exe Confirm with “OK”.
3. Follow the on-screen instructions to install the ANT-20 Remote Control.
4. After complete installation exit Windows, and reboot the ANT-20.
After this installation procedure, the ANT-20 can be set to remote control mode by double­clicking on the “Remote” icon in the “ANT-20” group in the “Program Manager” window.
Software installation under Windows95
If you ordered the Remote Control V.24/V.28 ( RS 232) Option BN 3035/91.01 together with your ANT-20, the required software package is already installed on the ANT-20 and the icons “Remote On”, “Remote Off” and “Remote Configuration” are shown in the Windows95 file folder “ANT-20”.
Note: A release code is required to enable the Rem ote Control V.24/V.28 (RS 23 2) Option.
For detailed information contact your nearest Wavetek Wandel Goltermann Se rvice Center. The addresses are listed at the end of this manual. When contacting the Service Center, always quote:
The serial number of the ANT-20
The version number of the ANT-20 software package
I-10 Introduction
Page 35
ANT-20 (Mainframe) 1 ANT-20, ANT-20E, ANT-20SE
If you ordered the Remote Control V.24/V.28 (RS 232) Option BN 3035/91.01 separately, install the software package as follows:
Installing the ANT-20 Remote Control software
1. Start or return to Windows95.
2. Click the Windows95 “Start” button,
choose “Run...” and type the following command into the dialog box: C:\ANT20.SUP\DISK1\setup.exe Confirm with “OK”.
3. Follow the on-screen instructions to install the ANT-20 Remote Control.
4. After complete installation exit Windows95, and reboot the ANT-20. After this installation procedure, you can enable the remote control mode by using the taskbar:
1. “Start/ANT-20/Remote On”.
2. Then double-click on the “ANT-20” icon on the desktop or use the taskbar: “Start/ANT-20/ANT-20”.
1.3.3 Connecting to V.24/V.28 (RS 232)
The interface connector (serial port COM1) is a 9-way SUB-D male connector.
Pin ITU-T
V.24
3 103 D1 BA TXD Transmitted data O 2 104 D2 BB RXD Received data I 7 105 S2 CA RTS Request to send O 8 106 M2 CB CTS Ready for sending/Clear to send I 6 107 M1 CC DSR Date set ready I 5 102 E2 AB SGND Signal ground or common return ­1 109 M5 CF DCD Data channel received line signal
4 108.2 S1.2 CD DTR Data terminal ready O 9 125 M3 CE RI Calling indicator/Ring indicator I
Table I-3 Pinning and signal description
DIN 66 020
EIA/TIA RS 232
Description ITU-T V.24 (RS 232)
detector/Data carrier detect
Input (I) or Output (O)
I
Introduction I-11
Page 36
1 ANT-20, ANT-20E, ANT-20SE ANT-20 (Mainframe)
The connection of an ANT-20 to a PC is shown below. Both the ANT-20 and the PC function as Data Terminal Equipment (DTE):
Fig. I-1 9-way connection
Fig. I-2 25-way connection
An appropriate cable with both 9-way and 25-way SUB-D female connectors on each end is available:
Part number K 764 (3.0 m long)
I-12 Introduction
Page 37
ANT-20 (Mainframe) 1 ANT-20, ANT-20E, ANT-20SE
1.3.4 Transmission parameters
The baud rate can be changed by editing the remote.bat batch file. ANT-20, ANT-20E with
Windows 3.11: 1. Double-click on the “Remote Configuration” icon in the
“ANT-20” group in the “Program Manager” window to edit the remote.bat file.
2. Follow the on-screen instructions.
Windows95: 1. Click on the “Remote Configuration” icon via taskbar: “Start/
ANT-20/Remote Configuration” to edit the remote.bat file.
2. Follow the on-screen instructions.
The following baud rates can be selected:
1200 bit/s
2400 bit/s
4800 bit/s
9600 bit/s
19200 bit/s
38400 bit/s
57600 bit/s
The interface operates in full-duplex (FDX) mode. The other transmission parameters are fixed and cannot be changed:
Parameter Setting Parity None Number of stop bits per character 1 Number of data bits per character 8 Flow control Hardware handshake by control lines RTS/CTS
Table I-4 Fixed V.24/RS 232 Transmission parameters
Introduction I-13
Page 38
1 ANT-20, ANT-20E, ANT-20SE ANT-20 (Mainframe)
1.3.5 Interface functions
1.3.5.1 Overview
There is no functional equivalence to the GPIB interface functions Service Request and Serial Poll.
However, the GPIB interface function Device Clear is simulated by a BREAK signal (see Sec. 1.3.5.2,Page I-14).
1.3.5.2 Device Clear
When the BREAK signal is sent to the ANT-20, a device clear message is routed to all internal measuring modules, regardless of whether they are selected or desel ected.
BREAK is detected when the RXD input is at positive voltage (i.e. logical 0 or SPACE) for the entire character frame including the stop bit.
The device clear message initializes remote control of the instrument and ensures that a subsequently sent program message will be accepted and processed.
No instrument initialization is performed by the device clear message. To initialize the instrument, select every measuring module and send the reset command *RST
(MODule:SELect <module_name>; *RST).
I-14 Introduction
Page 39
ANT-20 (Mainframe) 2 DominoCOM ANT-20
2 DominoCOM ANT-20

2.1 General information

2.1.1 Items included
The delivery includes the following items relating to remote control:
PCMCIA GPIB card including PCMCIA to GPIB cable (2 meters)
Configuration disk: DominoCOM ANT-20 Remote Control
Remote Control Operating Manual
Brochure “SCPI and IEEE 488, Programmer‘s Introduction”
For DominoCOM ANT-20 with Windows 3.11 only:
CardWare User´s Manual (Award Software Inc.)
Distribution disk: CardWare Version 2.0 (Award Software Inc.)
2.1.2 Overview
The DominoCOM ANT-20 can be remotely controlled using the
IEEE 488 (IEC 625) interface, often referred to as GPIB
– or –
V.24/V.28 (RS 232) interface
The programming commands are identical, regardless of the type of remote control interface that is used.
From the viewpoint of remote control, each measuring module in the DominoCOM ANT-20 is a fully remote-controllable instrument with its own SCPI command tree, status reporting system and common command set.
The measuring module to be controlled is selected using the command MODule:SELect <module_name> (see Sec. 2.1.5,Page I-17).
Factory-set configuration: Interface type V.24/V.28 (RS 232)
Baud rate 9600 bit/s
Refer to Sec. 2.1.3,Page I-15 for changing the type of remote control interface and/or its accompanying configuration parameters.
DominoCOM ANT-20 can operate in the ANT-20 mode with the use of an external monitor, keyboard and mouse. Refer to Sec. 2.1.4,Page I-16, for detailed information.
2.1.3 Changing the configuration
To change the type of remote control interface and/or its accompanying configuration parameters, follow these steps
1. Edit the remote.bat batch file (on the configuration disk) by using an external PC. Refer to the readme.txt file (on the configuration disk) for detailed editing information.
2. Insert the configuration disk into drive A: of the DominoCOM ANT-20 and reboot the DominoCOM ANT-20 (switch power off, then power on ).
Introduction I-15
Page 40
2 DominoCOM ANT-20 ANT-20 (Mainframe)
2.1.4 ANT-20 mode
By connecting an external monitor, keyboard and mouse to the embedded PC-AT, the DominoCOM ANT-20 can be operated in the same way as an ANT-20.
The display shows which measuring modules exist and which one is selected for remote control.
A monitor function can be switched on for debugging purposes during remote control mode that displays all messages sent to and from the DominoCOM ANT-20, corresponding to each operating step performed.
Edit the remote.bat batch file (for changing the type of the remote control interface and/or its accompanying configuration parameters) as follows:
DominoCOM ANT-20 with Windows 3.11: 1. Double-click on the “Remote Configuration” icon in the “ANT-20”
group in the “Program Manager” window.
2. Follow the on-screen instructions.
Windows95: 1. Click on the “Remote Configuration” icon via taskbar: “Start/
ANT-20/Remote Configuration”.
2. Follow the on-screen instructions.
To leave remote control mode and enter normal manual control, follow these steps DominoCOM ANT-20 with
Windows 3.11: Double-click on the “Remote Disable” icon in the “ANT-20”
group in the “Program Manager” window.
Windows95: 1. Disable remote mode using the taskbar: “Start/ANT-20/Remote
Off”.
2. Then double-click on the “ANT-20” icon on the desktop or use the taskbar: “Start/ANT-20/ANT-20”.
To switch back to remote control mode, follow these steps DominoCOM ANT-20 with
Windows 3.11: Double-click on the “Remote” icon in the “ANT-20” group in the
“Program Manager” window.
Windows95: 1. Enable remote mode using the taskbar: “Start/ANT-20/Remote
On”.
2. Then double-click on the “ANT-20” icon on the desktop or use the taskbar: “Start/ANT-20/ANT-20”.
I-16 Introduction
Page 41
ANT-20 (Mainframe) 2 DominoCOM ANT-20
2.1.5 Module selection
The remote control interface of the DominoCOM ANT-20 supports multiple internal measuring modules. The module selection provides a mechanism to select one of these measuring modules for remote control.
Keyword Parameter form Notes MODule:SELect <module_name>
1 <module_name>: BASIC | JITTER | JITT16 | BAG
Table I-5 Module selection
This command selects the measuring module specified by <module_name> for remo te co ntrol and deselects all others. All subsequent commands (including commands in subsequent program messages) are passed to the selected measuring module. All other measuring modules are unavailable for programming until selected.
<module_name>: BASIC: Selects BASIC Module
JITTER: Selects JITTER Module for bit rates up to STM4/OC12 (extension slot)
(not available for ABT-20)
JITT16: Selects JITTER Module for bit rates of STM16/OC48 (extension slot)
(not available for ABT-20)
BAG: Selects BAG Module (Broadband Analyzer/Generator)
Note: This command has no query form.
After power-on, the BASIC measuring module is selected.
If the MODule:SELect <module_name> command is required in a program
message, it must be the first (or the only) command in that program message.
1
[no query]
2.1.6 LabWindows/CVI driver
A LabWindows/CVI instrument driver is available for each measuring module. Instrument drivers reduce application program development time and simplify instrument
control by eliminating the need to learn the complex programming commands fo r each measuring module.

2.2 GPIB Remote Control interface

This section describes the GPIB Remote Control interface for applications using the DominoCOM ANT-20 as a remote controlled instrument.
Applications using the DominoCOM ANT-20 as a GPIB Controller for controlling external instruments are also possible (e.g. running the WG CATS Test Executive BN 3045 on the DominoCOM ANT-20 to control the DominoCOM ANT-20 measurement hardware plus external instruments).
To allow both these mutually exclusive operating modes to b e used, the GPIB Remote Cont rol interface and installation comprises all the software required for both operating modes.
Introduction I-17
Page 42
2 DominoCOM ANT-20 ANT-20 (Mainframe)
2.2.1 Installation
2.2.1.1 Overview
The PCMCIA GPIB interface from National Instruments Corp. (NI) is used with the NI-488.2/ NI-488.2M software for GPIB Remote Control. This software is already installed on the DominoCOM ANT-20.
For DominoCOM ANT-20 with Windows 3.11 only:
The NI-488.2 software requires standardized PCMCIA system software with Socket and Card Services (version 2.0 or higher) to be installed.
A software called CardWare (written by Award Software Inc.) is used as PCMCIA system software. It can also be used with a wide variety of other PCMCIA cards.
The CardWare software is already installed on the DominoCOM ANT-20 and suitably configured.
2.2.1.2 Configuration for GPIB
Set the configuration parameters:
Interface type GPIB
Device address
by editing the remote.bat batch file. Refer to Sec. 2.1.3,Page I-15, for detailed information.
Each instrument in the interface system must have an unique addre ss to allow the controller to access each one individually.
Any address in the range 0 to 30 can be selected. Note: Make sure that a given address is used only once within the interface system. The
controller address is reserved for the controller.
2.2.1.3 Hardware installation
1. Insert the PCMCIA GPIB card into a free PCMCIA socket the same way you insert a disk into a floppy drive. The PCMCIA GPIB has no jumpers or switches to set, and you do not need to power do wn the DominoCOM ANT-20 when you insert or remove the card.
2. Connect the PCMCIA GPIB cable to the PCMCIA GPIB card.
I-18 Introduction
Page 43
ANT-20 (Mainframe) 2 DominoCOM ANT-20
2.2.2 Connecting to GPIB
The GPIB Remote Control interface is equipped with a stand ard 24- way connector conforming to IEEE 488.1.
GPIB cables of various lengths are available for connecting the DominoCOM ANT-20 to other instruments and to the bus controller:
1.2 m long: Part number K 420
2.0 m long: Part number K 421
Note: • The total length of GPIB cable must not exceed 2 meters x the number of
instruments in the interface system.
Up to 15 instruments can be connected to the interface system. The m aximum cable run used to connect a group of instruments is 20 meters. For more informatio n re fer to the IEEE 488.1 standard.
Longer distances can be bridged using interface couplers (2-wire or 4-wire connections, if necessary with suitable modems).
2.2.3 Interface functions
2.2.3.1 Overview
Interface function Note SH1 Source Handshake Complete capability
AH1 Acceptor Handshake Complete capability T8 Talker No Talk Only capability
L4 Listener No Listen Only capability SR0 Service Request No capability RL0 Remote/Local No capability PP0 Parallel Poll No capability DC1 Device Clear Complete capability DT0 Device Trigger No capability C0 Controller No capability
Table I-6 Interface functions conforming to the IEEE 488.1 standard
No Serial Poll capability
Introduction I-19
Page 44
2 DominoCOM ANT-20 ANT-20 (Mainframe)
2.2.3.2 Device Clear
When the IEEE 488 interface message Device Clear ( DCL ) or Sele cted Device Clear (SDC) is sent to the DominoCOM ANT-20, a device clear message is routed to all internal measuring modules, regardless of whether they are selected or deselected.
The device clear message initializes remote control of the instrument and ensures that a subsequently sent program message will be accepted and processed.
No instrument initialization is performed by DCL or SDC. To initialize the instrument, select every measuring module and send the reset command
*RST (MODule:SELect <module_name>; *RST).
I-20 Introduction
Page 45
ANT-20 (Mainframe) 2 DominoCOM ANT-20

2.3 V.24/V.28 (RS 232) Remote Control interface

2.3.1 Installation
2.3.1.1 Overview
For remote control via RS 232 the built-in serial port (COM1) of the embedded PC-AT is used.
2.3.1.2 Configuration for V.24/V.28 (RS 232)
Set the configuration parameters:
Interface type V.24/V.28 (RS 232)
Baud rate
by editing the remote.bat batch file. Refer to Sec. 2.1.3,Page I-15.
The following baud rates can be selected:
1200 bit/s
2400 bit/s
4800 bit/s
9600 bit/s
19200 bit/s
38400 bit/s
57600 bit/s
The interface operates in full-duplex (FDX) mode. The other transmission parameters are fixed and cannot be changed:
Parameter Setting Parity None
Number of stop bits per character 1 Number of data bits per character 8 Flow control Hardware handshake by control lines RTS/CTS
Table I-7 Fixed V.24/RS 232 Transmission parameters
Introduction I-21
Page 46
2 DominoCOM ANT-20 ANT-20 (Mainframe)
2.3.2 Connecting to V.24/V.28 (RS 232)
The interface connector (serial port COM1) is a 9-way SUB-D male connector.
Pin ITU-T
V.24
3 103 D1 BA TXD Transmitted data O 2 104 D2 BB RXD Received data I 7 105 S2 CA RTS Request to send O 8 106 M2 CB CTS Ready for sending/Clear to send I 6 107 M1 CC DSR Date set ready I 5 102 E2 AB SGND Signal ground or common return ­1 109 M5 CF DCD Data channel received line signal
4 108.2 S1.2 CD DTR Data terminal ready O 9 125 M3 CE RI Calling indicator/Ring indicator I
Table I-8 Pinning and signal description
DIN 66 020
EIA/TIA RS 232
Description ITU-T V.24 (RS 232)
detector/Data carrier detect
Input (I) or Output (O)
I
I-22 Introduction
Page 47
ANT-20 (Mainframe) 2 DominoCOM ANT-20
The connection of a DominoCOM ANT-20 to a PC is shown below. Both the DominoCOM ANT-20 and the PC function as Data Terminal Equipment (DTE):
Fig. I-3 9-way connection
Fig. I-4 25-way connection
An appropriate cable with both 9-way and 25-way SUB-D female connectors on each end is available:
Part number K 764 (3.0 m long)
Introduction I-23
Page 48
2 DominoCOM ANT-20 ANT-20 (Mainframe)
2.3.3 Interface functions
2.3.3.1 Overview
There is no functional equivalence to the GPIB interface functions Service Request and Serial Poll.
However, the GPIB interface function Device Clear is simulated by a BREAK signal (see Sec. 2.3.3.2,Page I-24).
2.3.3.2 Device Clear
When the BREAK signal is sent to the DominoCOM ANT-20, a device clear message is routed to all internal measuring modules, regardless of whether they are selected or deselected.
BREAK is detected when the RXD input is at positive voltage (i.e. logical 0 or SPACE) for the entire character frame including the stop bit.
The device clear message initializes remote control of the instrument and ensures that a subsequently sent program message will be accepted and processed.
No instrument initialization is performed by the device clear message. To initialize the instrument, select every measuring module and send the reset command
*RST (MODule:SELect <module_name>; *RST).
I-24 Introduction
Page 49

ANT-20 (Mainframe) 3 TX/RX SCPI block diagram

3 TX/RX SCPI block diagram
V.11
Basic module
Through 4
ext.Mod.
SOURCE:
JITTER
Jitter mod.
[25]
Ref.Clock Input
[23]
Jitter Input
Ref.Clock Output
[22]
[21]
V.11
SOURCE: DATA:TEL ATM
from RX
SOURCE:
DATA:TEL
Aux.Clock
Synthesizer
SDH
PDH *chain
TX-Trib.
RX-Trib.
OUTPUT:TEL
:OPTIC
STM-1/4
OUTPUT:TEL
:LINE
1.5-155M
OUTPUT:TEL
:AUX
1.5-140M
optic
[18]
Line
bal
[13]
Aux.
[11]
[15]
TX
electrical
optic
OUTPUT:
TEL
STM-16 Through 16
SENSE:
JITTER
Jitter dem.
Dem.
Ref.
[24]
[26]
SENSE:
DATA:TEL:
ATM
Jitter Output
Trigger
Ref.2048 TSE TX Frame
TX Pattern
Through 1
OUTPUT:
TRIGGER
SENSE:
DATA:TEL: PDH
SENSE: DATA:TEL:
SDH
V.11
INPUT:TEL
:AUX
1.5-140M
INPUT:TEL
:LINE
1.5-155M
INPUT:TEL
:OPTIC STM-1/4
Through 4
INPUT:
STM-16
Aux.
[10]
bal
[12]
Line
[15]
optic unbal. STM-1/4
TEL
optic
electrical
RX
[17] [16]
Fig. I-5 TX/RX SCPI block diagram
Introduction I-25
Page 50

4 Operating information ANT-20 (Mainframe)

4 Operating information
This chapter gives the programmer some basic information which should make it easier to program this device.
Program messages are executed in the order they are received from the controller. However, the execution of any command does not start b efore the PMT (Progra m Message Terminator <NL>) or any other sequential command is received. This gives full flexibility in controlling the device without the need to worry about the dependencies between individual commands, because the settings of coupled commands received within a single message are checked after the whole message is received.
Commands are treated as “overlapped commands” except where otherwise noted. Overlapped commands allow the next command to be executed before the preceding command has finished execution. This gives better performance and makes it possible to change some settings while a measurement is running, for example. You can use the common command *WAI to force sequential operation whenever you need to.
Any error detected within a program message is written into the error queue. You can read entries out of the error queue using the SYST:ERR? command. Any program message is read from the input buffer and parsed as far as possible to detect potential errors. Nevertheless, the device setting may be undefined after any error.
Queries are not allowed to have side effects. Thus, queries of commands set in the same program message will return the old command setting.
Note that using the SCPI short form of the commands (capital letters) will reduce operational overhead and can increase your system performance.
The input buffer size is 4096 bytes (4 kB).
The output buffer size is 8192 bytes (8 kB). Requesting a response with more than
8192 bytes would cause a query error.
I-26 Introduction
Page 51

ANT-20 (Mainframe) 5 Command hierarchy

5 Command hierarchy

5.1 Introduction

This section is intended to give programmers an overview of the hierarchical relationships between the commands.
Each command is independent. However, since the parameters are related, each par ameter has a priority between 1 and 4, with 1 being the highest and 4 the lowest.
If a higher-priority parameter is modified, lower-priority param eters may be automatically modified as well. This automatic mechanism assures logically consistent instrument settings that comply with standards, thereby avoiding error messages. It also simplifies programming since many settings are made automatically and do not need to be programmed.
The priorities come into play when individual commands are sent to the instrument. However , if multiple commands are grouped in a command sequence, the priorities are inactive within the command sequence.
Note: Send individual commands in order of decreasing priority so that settings are not
overwritten by subsequent commands.
If you transmit command sequences, be careful to pro vid e consistent data since the instrument does not make automatic corrections in this case.

5.2 Command hierarchy (generator)

Remote Command Priority
*RST on page R-5 1 :SOUR:DATA[:TEL]:STAN on page R-254 2 :SOUR:MODE on page R-255 3 :SOUR:DATA[:TEL]:NEL on page R-86 4 :SOUR:DATA[:TEL]:SOUR:DIV on page R-252 5 :SOUR:DATA[:TEL]:SDH:RATE on page R-213 6 :SOUR:DATA[:TEL]:SOUR[:SOCK] on page R-253 7 :SOUR:DATA[:TEL]:SDH:MAPP on page R-168 8 :SOUR:DATA[:TEL]:SDH:MAPP:CONC[:MODE] on page R-170 9 :SOUR:DATA[:TEL]:SDH:MAPP:TUFL on page R-172 9 :SOUR:DATA[:TEL]:SDH:PAYL:TYPE on page R-195 10 :SOUR:DATA[:TEL]:SDH:TRIB:MAPP on page R-235 11 :SOUR:DA TA[:TEL]:SDH:CHAN on page R-144 12 :SOUR:DATA[:TEL]:SDH:STMN:CHAN on page R-217 12 all other commands of node :SOUR:DATA[:TEL]:SDH on page R-135 ff 13
Table I-9 Command hierarchy (generator)
Introduction I-27
Page 52
5 Command hierarchy ANT-20 (Mainframe)
Remote Command Priority
:SOUR:DATA[:TEL]:PDH:RATE on page R-129 12 :SOUR:DATA[:TEL]:PDH:FRAM on page R-104 13 :SOUR:DATA[:TEL]:PDH:PAYL:TYPE on page R-128 14 :SOUR:DATA[:TEL]:PDH:M2:FRAM on page R-107 15 :SOUR:DATA[:TEL]:PDH:M34:FTYP on page R-116 15 :SOUR:DATA[:TEL]:PDH:M140:FTYP on page R-123 15 :SOUR:DATA[:TEL]:PDH:DS1:FRAM on page R-96 15 :SOUR:DATA[:TEL]:PDH:DS3:FRAM on page R-101 15 all other commands of node :SOUR:DATA[:TEL]:PDH on page R-91 ff 16 :SOUR:DATA[:TEL]:ATM:NINT on page R-74 17 :SOUR:DATA[:TEL]:ATM:PAYL:TYPE on page R-75 18 :SOUR:DATA[:TEL]:ATM:HEAD:CLP on page R-70 and other commands of
the ...:HEAD node. :SOUR:DATA[:TEL]:ATM:DIST:TYPE on page R-66 20 all other commands of node :SOUR:DATA[:TEL]:ATM on page R-58 ff 21 all other transmitter commands 22
Table I-9 Command hierarchy (generator)

5.3 Command hierarchy (receiver)

Remote Command Priority
*RST on page R-5 1 [:SENS]:DATA[:TEL]:STAN on page R-378 2 [:SENS]:MODE on page R-406 3 [:SENS]:DATA[:TEL]:SDH:RATE on page R-370 6 [:SENS]:DATA[:TEL]:SENS on page R-378 7 [:SENS]:DATA[:TEL]:SDH:MAPP on page R-357 8
19
(continued)
[:SENS]:DATA[:TEL]:SDH:MAPP:CONC[:MODE] on page R-358 9 [:SENS]:DATA[:TEL]:SDH:MAPP:TUFL on page R-360 9 [:SENS]:DATA[:TEL]:SDH:PAYL:TYPE on page R-365 10 [:SENS]:DATA[:TEL]:SDH:TRIB:MAPP on page R-375 11 [:SENS]:DATA[:TEL]:SDH:CHAN on page R-353 12 [:SENS]:DATA[:TEL]:SDH:STMN:CHAN on page R-372 12
Table I-10 Command hierarchy (receiver)
I-28 Introduction
Page 53
ANT-20 (Mainframe) 5 Command hierarchy
Remote Command Priority
all other commands of node [:SENS]:DATA[:TEL]:SDH on page R-352 ff 13 [:SENS]:DATA[:TEL]:PDH:RATE on page R-350 12 [:SENS]:DATA[:TEL]:PDH:FRAM on page R-334 13 [:SENS]:DATA[:TEL]:PDH:PAYL:TYPE on page R-349 14 [:SENS]:DATA[:TEL]:PDH:M2:FRAM on page R-336 15 [:SENS]:DATA[:TEL]:PDH:M34:FTYP on page R-340 15 [:SENS]:DATA[:TEL]:PDH:M140:FTYP on page R-345 15 [:SENS]:DATA[:TEL]:PDH:DS1:FRAM on page R-331 15 [:SENS]:DATA[:TEL]:PDH:DS3:FRAM on page R-333 15 all other commands of node [:SENS]:DATA[:TEL]:PDH on page R-330 ff 16 [:SENS]:DATA[:TEL]:ATM:NINT on page R-320 17 [:SENS]:DATA[:TEL]:ATM:VCI on page R-323 18 [:SENS]:DATA[:TEL]:A TM:VCI:FILT on page R-323 18 [:SENS]:DATA[:TEL]:A TM:VPI on page R-324 18 [:SENS]:DATA[:TEL]:A TM:PAYL:TYPE on page R-321 19 all other commands of node [:SENS]:DATA[:TEL]:ATM on page R-316 ff 20 all other receiver commands 21
Table I-10 Command hierarchy (rec eiver)
(continued)
Introduction I-29
Page 54

6 Programming examples ANT-20 (Mainframe)

6 Programming examples
This chapter contains some short sample programs to help you get familiar with the remote control operation of this device.

6.1 Notation

The sample programs are written in C programming language style using the fun ctions “clear” , “write”, “wait” and “read” as placeholders for the different functions used by programmers depending on their programing language.
Note: A “NOEND” as the second parameter of the function “write” indicates that the same
program message is continued in the next line without sending a program message terminator (PMT). An “END” indicates that a program message terminat or (PMT) should be sent. Multiple commands can be appended into one “big” program message using NOEND. Checking of coupled parameters and the ex ecution of all commands starts after the PMT or any sequential command is received.

6.2 Example 1 (PDH measurement)

This sample program performs a simple 2 Mbit/s FAS (frame alignment signal) measurement. Note that the default device setting after a *RST command is a 2 Mbit/s framed PDH signal.
// Send device clear to reset input buffer // and output queue. // Initialize communication protocol.
clear();
// Clear status register and error queue.
write (“*CLS”, END);
// Reset device to standard setting. // TX and RX set to 2 Mbit/s (E1) framed signal.
write (“*RST”, END);
// Select 2 Mbit/s FAS error
// count and alarm ratio as requested results. write (“SENS:FUNC:ON ’ARAT:PDH:M2:FAS’”,END); write (“SENS:FUNC:ON ’ECO:PDH:M2:FAS’",END);
// Set measurement duration to 1 sec. write (“SENS:SWE:TIME 1 s”, END);
// start measurement. write (“INIT”, END);
// Wait until measurement has finished and
// place results into the output queue. write (“*WAI;SENS:DATA:FIN?”,END);
// Read response from device. read();
I-30 Introduction
Page 55
ANT-20 (Mainframe) 6 Programming examples

6.3 Example 2 (SDH C4 measurement)

This sample program performs a STM1 155 Mbit/s measurement using a C4 mapping which includes a PDH 140 Mbit/s signal.
// Send device clear to reset input buffer // and output queue. // Initialize communication protocol.
clear();
// Clear status register and error queue.
write (“*CLS”, END);
// Reset device to standard setting. // TX and RX set to 2 Mbit/s (E1) framed signal.
write (“*RST”, END);
// Set transmitter to SDH mode.
write (“:SOUR:MODE SDH;” ,NOEND);
// Set transmitter bit rate to STM1/STS3 (is default).
write (“:SOUR:DATA:SDH:RATE STM1;”,NOEND);
// Set C4/STS3CSPE mapping.
write (“:SOUR:DATA:SDH:MAPP C4;”,NOEND);
// Included PDH 140 Mbit/s MUX chain
// deactivated. write (“:SOUR:DATA:SDH:PAYL:TYPE PDH;”,NOEND); write (“:SOUR:DATA:PDH:RATE M140,M140;”,END);
// Set receiver to SDH mode. write (“:SENS:MODE SDH;”,NOEND);
// Set receiver bit rate to STM1 (is default). write (“:SENS:DATA:SDH:RATE STM1;”,NOEND);
// Set C4/STS3CSPE mapping. write (“:SENS:DATA:SDH:MAPP C4;”,NOEND);
// Included PDH 140 Mbit/s DEMUX chain
// deactivated. write (“:SENS:DATA:SDH:PAYL:TYPE PDH;”,NOEND); write (“:SENS:DATA:PDH:RATE M140,M140;”,END);
// Select requested results. write (“:SENS:FUNC:ON ’ACO:TSE’", END);
// Add more requested results. write (“:FUNC ’ECO:TSE’", END); write (“:FUNC ’ACO:SDH:MSB’", END); write (“:FUNC ’ECO:SDH:MSB’", END);
// Set measurement duration to 1 hour. write (“:SENS:SWE:TIME 1 hr”, END);
// Start measurement. write (“:INIT”, END);
// Wait 1 hour. wait 3600;
// Place results into the output queue. write (“:SENS:DATA:FIN?”,END);
// Read response from device. read();
Introduction I-31
Page 56
6 Programming examples ANT-20 (Mainframe)

6.4 Example 3 (SDH overhead)

This sample program performs a receiver STM1/STS3 155 Mbit/s section overhead (SOH/TOH) capture.
// Send device clear to reset input buffer // and output queue. // Initialize communication protocol.
clear();
// Clear status register and error queue.
write (“*CLS”, END);
// Reset device to standard setting. // TX and RX set to 2 Mbit/s framed signal.
write (“*RST”, END);
// Set receiver to SDH mode.
write (“:SENS:MODE SDH;” ,NOEND);
// Set receiver bit rate to STM1/STS3 (is default).
write (“:SENS:DATA:SDH:RATE STM1;” ,NOEND);
// Take an overhead snapshot and place data into the // output queue.
write (“:FETC:OVER?”,END);
// Read response from device.
read();

6.5 Example 4 (SDH overhead measurement)

This sample program performs a STM1/STS3 155 Mbit/s measurement within the communication channel (D1..D3) bytes of the STM1/STS3 overhead.
// Send device clear to reset input buffer // and output queue. // Initialize communication protocol.
clear();
// Clear status register and error queue.
write (“*CLS”, END);
// Reset device to standard setting. // TX and RX set to 2 Mbit/s framed signal.
write (“*RST”, END);
// Set transmitter to SDH mode.
write (“:SOUR:MODE SDH;” ,NOEND);
// Set overhead insertion into D1..D3 bytes.
write (“:SOUR:DATA:SDH:OVER:BYT SDCC;” ,NOEND);
// Activate overhead insertion from internal source.
write (“:SOUR:DATA:SDH:OVER:INS INT;” ,END);
// Set receiver to SDH mode.
write (“:SENS:MODE SDH;” ,NOEND);
// Set overhead drop to D1..D3 bytes.
write (“:SENS:DATA:SDH:OVER:BYT SDCC;” ,NOEND);
// Select measurement for test sequence errors within // the overhead instead of the payload.
write (“:SENS:DATA:SDH:ERR:TSE:SOUR OVER;” ,END);
// Select requested results.
I-32 Introduction
Page 57
ANT-20 (Mainframe) 6 Programming examples
write (“SENS:FUNC:ON ’CST:SIGN’", END); write (“FUNC ’ECO:TSE’", END);
// Set measurement duration to 1 minute. write (“SENS:SWE:TIME 1 min”, END);
// start measurement. write (“INIT”, END);
// Wait until measurement has finished and
// place results into the output queue. write (“*WAI;SENS:DATA:FIN?”,END);
// Read response from device. read();

6.6 Example 5 (SONET STS1-SPE measurement)

This sample program performs a STS1 51 Mbit/s measurement using a STS1SPE mapping which includes a DS3 signal.
// Send device clear to reset input buffer
// and output queue.
// Initialize communication protocol. clear();
// Clear status register and error queue. write (“*CLS”, END);
// Reset device to standard setting. write (“*RST”, END);
// Set ANSI mode (SONET instead of SDH) write (“SOUR:DATA:STAN ANSI;” , END);
// Set transmitter to synchronous mode instead of
// asynchronous (PDH) write (“:SOUR:MODE SDH;” ,NOEND);
// Set transmitter bit rate to STS1. write (“:SOUR:DATA:SDH:RATE STS1;”,NOEND);
// Set STS1SPE mapping. write (“:SOUR:DATA:SDH:MAPP STS1SPE;”,NOEND);
// select payload type (can be ATM or PATT (bulk) or PDH (DSn)| write (“:SOUR:DATA:SDH:PAYL:TYPE PDH;”,NOEND); write (“:SOUR:DATA:PDH:RATE DS3,DS3;”,END);
// Set receiver to synchronous mode (SONET). write (“:SENS:DATA:STAN ANSI;” , END); write (“:SENS:MODE SDH;”,NOEND);
// Set receiver bit rate to STM1 (is default). write (“:SENS:DATA:SDH:RATE STS1;”,NOEND);
// Set STS1SPE mapping. write (“:SENS:DATA:SDH:MAPP STS1SPE;”,NOEND);
// select payload type (can be ATM or PATT (bulk) or PDH (DSn)| write (“:SENS:DATA:SDH:PAYL:TYPE PDH;”,NOEND); write (“:SENS:DATA:PDH:RATE DS3,DS3;”,END);
// Select requested results. write (“:SENS:FUNC:ON ‘ACO:TSE’”, END);
// Add more requested results. write (“:FUNC ‘ECO:TSE’”, END); write (“:FUNC ‘ACO:SDH:MSB’”, END); write (“:FUNC ‘ECO:SDH:MSB’”, END);
// Set measurement duration to 1 hour.
Introduction I-33
Page 58
6 Programming examples ANT-20 (Mainframe)
write (“:SENS:SWE:TIME 1 hr”, END);
// Start measurement.
write (“:INIT”, END);
// Wait 1 hour.
wait 3600;
// Place results into the output queue.
write (“:SENS:DATA:FIN?”,END);
// Read response from device.
read();

6.7 Example 6 (SONET Transport overhead measurement)

This sample program performs a receiver STM1/STS3 155 Mbit/s Transport overhead (TOH) capture.
// Send device clear to reset input buffer // and output queue. // Initialize communication protocol.
clear();
// Clear status register and error queue.
write (“*CLS”, END);
// Reset device to standard setting (E1).
write (“*RST”, END);
// Set receiver to synchronous mode (SONET). write (“:SENS:DATA:STAN ANSI;” , END); write (“:SENS:MODE SDH;” ,NOEND);
// Set receiver bit rate to STS3 (is default). write (“:SENS:DATA:SDH:RATE STS3;” ,NOEND);
// Take an overhead snapshot and place data into the
// output queue. write (“:FETC:OVER?”,END);
// Read response from device. read();

6.8 Example 7 (SONET DS1 ESF testing with LOF inserted)

// Reset values write (“*RST;”, END) write (“:func:off:all;”, END)
// Line code & framing write (“:outp:line:code B8ZS;”, NOEND) write (“:inp:line:code B8ZS;”, NOEND) write (“:sour:mode pdh;”, NOEND) write (“:sens:mode pdh;”, NOEND) write (“:sour:data:pdh:fram fram;”, NOEND) write (“:sens:data:pdh:fram fram;”, NOEND) write (“:sour:data:pdh:ds1:fram esf107;”, NOEND) write (“:sens:data:pdh:ds1:fram esf107;”, NOEND) write (“:sour:data:pdh:rate ds1, ds1;”, NOEND) write (“:sens:data:pdh:rate ds1, ds1;”, NOEND)
// Test pattern write (“:sour:data:payl:patt qrss20;”, NOEND) write (“:sens:data:payl:patt qrss20;”, END)
I-34 Introduction
Page 59
ANT-20 (Mainframe) 6 Programming examples
// Insert LOF
write (“:sour:data:pdh:alar lof1_5, cont;”, END)
// Start/Stop measurement
write (“:sens:func ““CST:SIGN””,””CST:PDH2””,””ECO:TSE””,
””ECO:CODE””;”, END) wait 2; write (“:init;”, END) wait 3; write (“:abort;”, END)
// read and compare results write (“:sens:data:act?;”, END) read(); test int 50 “test status of CST:SIGN” test mask 0 245 “LOS !” test int 53 “test status of CST:PDH2 result (Defects DS1)” test mask 2 253 “Defect not LOF1.5” test int 100 “test status ECO:TSE result” test float 0 “bit error not 0” test int 130 “test status ECO:CODE result” test float 0 “BPV not 0”
Introduction I-35
Page 60

7 Release Notes ANT-20 (Mainframe)

7 Release Notes
This section contains a summary of all additions included from So ftware Release V6.6 onwards.

7.1 New commands

Summary of all new commands included from Software Release V6.6 onwards
:SOUR:DATA[:TEL]:PDH:DS3:FEAC[:ALAR] on page R-98 :SOUR:DATA[:TEL]:PDH:DS3:FEAC:LOOP[:TYPE] on page R-99 :SOUR:DATA[:TEL]:PDH:DS3:FEAC:LOOP:CODE on page R-100 :SOUR:DATA[:TEL]:SDH:ERR:FLEN on page R-162 :SOUR:DATA[:TEL]:SDH:MAPP:OFFS on page R-169 :SOUR:DATA[:TEL]:SDH:OVER:SEQ[:ACT] on page R-186 :SOUR:DATA[:TEL]:SDH:OVER:SEQ:MNP:DATA on page R-187 :SOUR:DATA[:TEL]:SDH:OVER:SEQ:POS:POH on page R-189 :SOUR:DATA[:TEL]:SDH:OVER:SEQ:POS:SOH | TOH on page R-190 :SOUR:DATA[:TEL]:SDH:OVER:SEQ:TYPE on page R-192 [:SENS]:DATA[:TEL]:PDH:DS3:FEAC:LOOP:RES on page R-332 [:SENS]:DATA[:TEL]:SDH:OVER:TCM:RES on page R-364 :FETC:SCAL[:DATA][:TEL][:SDH]:OVER? on page R-423 :FETC:STR[:DATA][:TEL][:SDH]:TCMonitoring:TRACe? on page R-432
Summary of all new commands included from Software Release V7.0 onwards
:SOUR:DATA[:TEL]:SDH:MAPP:CONC:CSIZ on page R-171 :SOUR:DATA[:TEL]:SDH:POIN:SSB on page R-207 :SOUR:DATA[:TEL]:SDH:OVER:SEQ:TCM:DATA on page R-191 :SOUR:DATA[:TEL]:SDH:OVER:SEQ:TCM:DATA:BLOC on page R-193
:INP:CLOC:WAND[:STAT] on page R-257 [:SENS]:DATA[:TEL]:SDH:MAPP:CONC:CSIZ on page R-359
Summary of all new commands included from Software Release V7.1 onwards
:OUTP[:TEL]:OPT3[:STAT] on page R-50 :SOUR:DATA[:TEL]:SDH:OVER[i]:DATA on page R-175 :SOUR:DATA[:TEL]:SDH:OVER[i]:DATA:BLOC on page R-177 :SOUR:DATA[:TEL]:SDH:OVER[i]:PRES on page R-179 :SOUR:DATA[:TEL]:SDH:OVER[i]:RDAT on page R-182 :SOUR:DATA[:TEL]:SDH:OVER[i]:RDAT:BLOC on page R-183 [:SENS]:DATA[:TEL]:ANAL:M2101:ALL on page R-304 [:SENS]:DATA[:TEL]:ANAL:M2101:ALL? on page R-304 [:SENS]:DATA[:TEL]:ANAL:M2101:BISO:BBE? on page R-304 [:SENS]:DATA[:TEL]:ANAL:M2101:BISO:ES? on page R-305 [:SENS]:DATA[:TEL]:ANAL:M2101:BISO:MULT on page R-305 [:SENS]:DATA[:TEL]:ANAL:M2101:BISO:MULT? on page R-305 [:SENS]:DATA[:TEL]:ANAL:M2101:BISO:SEP? on page R-306 [:SENS]:DATA[:TEL]:ANAL:M2101:BISO:SES? on page R-306 [:SENS]:DATA[:TEL]:ANAL:M2101:EVAL on page R-306 [:SENS]:DATA[:TEL]:ANAL:M2101:EVAL? on page R-307 [:SENS]:DATA[:TEL]:ANAL:M2101:S1:BBE? on page R-307 [:SENS]:DATA[:TEL]:ANAL:M2101:S1:ES? on page R-307 [:SENS]:DATA[:TEL]:ANAL:M2101:S1:SEP? on page R-308
I-36 Introduction
Page 61
ANT-20 (Mainframe) 7 Release Notes
[:SENS]:DATA[:TEL]:ANAL:M2101:S1:SES? on page R-308 [:SENS]:DATA[:TEL]:ANAL:M2101:S2:BBE? on page R-308 [:SENS]:DATA[:TEL]:ANAL:M2101:S2:ES? on page R-308 [:SENS]:DATA[:TEL]:ANAL:M2101:S2:SEP? on page R-309 [:SENS]:DATA[:TEL]:ANAL:M2101:S2:SES? on page R-309 [:SENS]:DATA[:TEL]:ANAL:M2101:UAS:LIM[:STAT] on page R-310 [:SENS]:DATA[:TEL]:ANAL:M2101:UAS:LIM[:STAT]? on page R-310 [:SENS]:DATA[:TEL]:ANAL:M2101:UAS:LIM:UPP on page R-310 [:SENS]:DATA[:TEL]:ANAL:M2101:UAS:LIM:UPP? on page R-311 [:SENS]:DATA[:TEL]:ANAL:M2101:UAS:MODE on page R-311 [:SENS]:DATA[:TEL]:ANAL:M2101:UAS:MODE? on page R-311 [:SENS]:DATA[:TEL]:LED:AUL[:STAT] on page R-325 [:SENS]:DATA[:TEL]:LED:TUL[:STAT] on page R-326 :[SENS]:DATA[:TEL]:SDH:OVER:TCM:TYPE on page R-364
Summary of all new commands included from Software Release V7.2 onwards
:SOUR:DATA[:TEL]:SDH:STSN:CHAN on page R-218 :SOUR:DATA[:TEL]:SDH:STSV:CHAN on page R-219 [:SENS]:DATA[:TEL]:SDH:STSN:CHAN on page R-373 [:SENS]:DATA[:TEL]:SDH:STSV:CHAN on page R-374 [:SENS]:DATA[:TEL]:ANAL:G828:ALL on page R-291 [:SENS]:DATA[:TEL]:ANAL:G828:ALL? on page R-291 [:SENS]:DATA[:TEL]:ANAL:G828:EVAL on page R-291 [:SENS]:DATA[:TEL]:ANAL:G828:EVAL? on page R-292 [:SENS]:DATA[:TEL]:ANAL:G828:SEPI[:STAT] on page R-292 [:SENS]:DATA[:TEL]:ANAL:G828:SEPI[:STAT]? on page R-292 [:SENS]:DATA[:TEL]:ANAL:G828:SES:THR on page R-292 [:SENS]:DATA[:TEL]:ANAL:G828:SES:THR? on page R-293 [:SENS]:DATA[:TEL]:ANAL:G828:SES:THR:AUTO on page R-293 [:SENS]:DATA[:TEL]:ANAL:G828:SES:THR:AUTO? on page R-293 [:SENS]:DATA[:TEL]:ANAL:G828:UAS:LIM[:STAT] on page R-294 [:SENS]:DATA[:TEL]:ANAL:G828:UAS:LIM[:STAT]? on page R-294 [:SENS]:DATA[:TEL]:ANAL:G828:UAS:LIM:UPP on page R-294 [:SENS]:DATA[:TEL]:ANAL:G828:UAS:LIM:UPP? on page R-294 [:SENS]:DATA[:TEL]:ANAL:G828:UAS:MODE on page R-295 [:SENS]:DATA[:TEL]:ANAL:G826:UAS:MODE? on page R-290 [:SENS]:DATA[:TEL]:ANAL:G829:EVAL on page R-295 [:SENS]:DATA[:TEL]:ANAL:G829:EVAL? on page R-296 [:SENS]:DATA[:TEL]:ANAL:G829:SES:THR on page R-296 [:SENS]:DATA[:TEL]:ANAL:G829:SES:THR? on page R-296 [:SENS]:DATA[:TEL]:ANAL:G829:SES:THR:AUTO on page R-297 [:SENS]:DATA[:TEL]:ANAL:G829:SES:THR:AUTO? on page R-297 [:SENS]:DATA[:TEL]:ANAL:M2101:SEPI[:STAT] on page R-309 [:SENS]:DATA[:TEL]:ANAL:M2101:SEPI[:STAT]? on page R-309 [:SENS]:DATA[:TEL]:ANAL:M2101:VERSion on page R-311 [:SENS]:DATA[:TEL]:ANAL:M2101:VERSion? on page R-312
Introduction I-37
Page 62
7 Release Notes ANT-20 (Mainframe)

7.2 Changed commands

Summary of all changed commands included from Software Release V6.6 onwards
:TRIG2[:SEQ]:LOG:SOUR on page R-30 <source> TCMF added :SOUR:DATA[:TEL]:PAYL:PA TT on page R-88 <pattern> IQRSS20 added :SOUR:DATA[:TEL]:PDH:ALAR[:MODE] on page R-92 <alarm> FEAC added :SOUR:DATA[:TEL]:PDH:ERR[:MODE] on page R-102 <error> CP45 added :SOUR:DATA[:TEL]:SDH:ERR[:MODE] on page R-165 <mode> PER added [:SENS]:DATA[:TEL]:PAYL:PATT on page R-328 <pattern> IQRSS20 added [:SENS]:DATA:EVEN:NUMB? on page R-267 added new codes for the event memory [:SENS]:FUNC[:ON] on page R-381 added new results for previous commands:
Result IDs for :SENS:DATA and :SENS:FUNC commands on page R-382
Result IDs for SDH/SONET results on page R-384
Alarm field “CSTatus:SDH2”/“HSTatus:SDH2” on page R-274
Alarm field “CSTatus:PDH2”/“HSTatus:PDH2” on page R-279
Result field “CSTatus:TCMonitoring”/“HSTatus:TCMonitoring” on page R-281
Result field “CSTatus:FEAC:LOOP:ON”/“CSTatus:FEAC:LOOP:OFF”/
“HSTatus:FEAC:LOOP:ON”/“HSTatus:FEAC:LOOP:OFF” on page R-280
Summary of all changed commands included from Software Release V7.0 onwards
:SOUR:DATA[:TEL]:SDH:ALAR[:MODE] on page R-136 <alarm> AISC5 ... 16 and LOPC5 ... 16 added :SOUR:DATA[:TEL]:SDH:STMN:BCH on page R-216 mode EQUipped added :SOUR:DATA[:TEL]:SDH:OVER:SEQ[: ACT] on page R-186 mode FSEQ added
An index [i] has been introduced for the STM-16/STS-48 SOH byte s in the following commands: :SOUR:DATA[: TEL]:SDH:OVER[i]:DA T A on page R-175 :SOUR:DATA[: TEL]:SDH:OVER[i]:DA T A:BLOC on page R-177 :SOUR:DATA[: TEL]:SDH:OVER[i]:PRES on page R-179 :SOUR:DATA[: TEL]:SDH:OVER[i]:RDA T on page R-182 :SOUR:DATA[: TEL]:SDH:OVER[i]:RDA T:BLOC on page R-183
:OUTP:CLOC[1]:DIV[:STAT] on page R-35: the exact settings ON | OFF are explained only in conjunction with the Jitter Module and O.171/O.172 options.
Summary of all changed commands included from Software Release V7.1 onwards
:STAT:QUES:COND?onpageR-16 :SOUR:CLOC:FOFF:OFFS on page R-53 :SOUR:DATA[:TEL]:SDH:ALAR:FLEN on page R-135 :SOUR:DATA[:TEL]:SDH:ERR:FLEN on page R-162 :SOUR:DATA[:TEL]:SDH:ERR[:MODE] on page R-165 :SOUR:DATA[:TEL]:SDH:RATE on page R-213 :OUTP[:TEL]:OPT2:WLEN on page R-49 [:SENS]:DATA[:TEL]:ANAL[:TYPE] on page R-314 [:SENS]:DATA[:TEL]:ANAL[:TYPE]? on page R-314 :FETC[:ARR][:DATA][:TEL][:SDH]:OVER? on page R-414 :FETC[:ARR][:DATA][:TEL][:SDH]:OVER:PART[i]? on page R-415 :FETC[:ARR][:DATA][:TEL][:SDH]:OVER:CPARt[i]? on page R-416 :FETC:SCAL[:DATA][:TEL][:SDH]:OVER? on page R-423 :FETC:SCAL[:DATA][:TEL][:SDH]:OVER:PART[i]? on page R-425 :FETC:SCAL[:DATA][:TEL][:SDH]:OVER:CPARt[i]? on page R-426
I-38 Introduction
Page 63
ANT-20 (Mainframe) 7 Release Notes
Summary of all changed commands included from Software Release V7.2 onwards
:SOUR:DATA[:TEL]:SDH:CHAN on page R-144 :SOUR:DATA[:TEL]:SDH:STMN:CHAN on page R-217 [:SENS]:DATA[:TEL]:SDH:CHAN on page R-353 [:SENS]:DATA[:TEL]:SDH:STMN:CHAN on page R-372 [:SENS]:DATA[:TEL]:ANAL:G826:EVAL on page R-286 [:SENS]:DATA[:TEL]:ANAL:G826:EVAL? on page R-287
Introduction I-39
Page 64
7 Release Notes ANT-20 (Mainframe)
Notes:
I-40 Introduction
Page 65
ANT-20 (Mainframe) *CAL?

Command reference

1 Common commands

Instrument behavior is based on: IEEE Standard Codes, Formats, ANSI/IEEE Std 488.2-1992. The common commands that are implemented are given below in alphabe tical
order.

*CAL?

Instrument calibration query.
Parameter None Comments Requests the instrument to perform an internal self calibration and to return the
result. The response indicates whether or not the instrument completed the calibration without error. A value of 0 indicates that the calibration has been completed successfully.
The instrument signals the need for calibration using the bit 8 of the “questionable status register” (see Status register structure on page R-11).
See also “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Note: The instrument is set to the reset state (as set by a *RST command) after a
*CAL? command.
Response 0: Calibration has been completed successfully
-1: Calibration failed
-2: Calibration failed (warm-up time not reached)
-3: calibration failed (EEPROM write error)
-10: Calibration failed (calibration currently not possible)
Example *CAL?
Response: 0
Related commands None
Common commands R-1
Page 66
*CLS ANT-20 (Mainframe)

*CLS

Clear Status Command.
Parameter None Comments Clears the data accumulated in the registers. Causes a partial initialization of
remote control. The masks contained in the registers (ENABLE Register) are not altered (see also SCPI Syntax and Style Section 4.1.3.2).
The following actions take place:
Clearing of all EVENT registers in the status register structure.
Clearing of the error queue and all other que ues which affect the status register
structure.
Interruption of an *OPC synchronization possibly underway, without a 1 being entered into bit 0 of the standard event status register.
Interruption of an *OPC? synchronization possibly underway, without a 1 be ing entered into the output queue.
See also “WG SCPI and IEEE488 Programmer’s Introduction” for more details. Example *CLS Related commands *RST on page R-5

*ESE

*ESE <mask> Standard Event Status Enable Command.
Parameter Name Type Range Default
mask numeric
Comments Sets the mask for the ESR register.
See also “WG SCPI and IEEE488 Programmer’s Introduction” for more details. Example *ESE 32 Related commands *ESR? on page R-3
*ESE?onpageR-3
#H00 - #HFF or #B00000000 - #B11111111 or 0 - 255
0
R-2 Common commands
Page 67
ANT-20 (Mainframe) *ESE?

*ESE?

Standard Event Status Enable Query.
Parameter None Comments Reads the mask for the ESR register.
See also “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Example *ESE?
Response: 64
Related commands *ESR? on page R-3
*ESE on page R-2

*ESR?

Standard Event Status Register Query.
Parameter None Comments Reads out the status register ESR. Range from 0 - 255.
See also “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Example *ESR?
Response: 64
Related commands *ESE on page R-2
Common commands R-3
Page 68
*IDN? ANT-20 (Mainframe)

*IDN?

Identification Query.
Parameter None Comments Reads out the instrument identification consisting of 4 fields, separated by “,”:
<Manufacturer>,<Instrument name>,<Serial no.>,<Firmware level>
<Manufacturer>:WANDEL&GOLTERMANN
<Instrument name>:ANT-20 / <Keycode no.>
<Serial no.>: A-0050
<Firmware level>:<Software version>/<Product no.>/<Version>/
<VXI code(HEX)>/<Card ID(HEX)> Example *IDN?
Response: WANDEL&GOLTERMANN,ANT-20/0A1234500000,B-0078,6.00/3035/
01/0C01/0255<NL> Related commands None
Note: This command must always be the last query in a programming command
(see also IEEE 488.2 Section 10.14.2.2). The response is always terminate d with a <NL> (0A HEX).

*OPC

Operation Complete Command.
Parameter None Comments Sets the OPC bit in the standard event status register ESR as soon as the
instrument has assumed the idle state. Used to synchronize overlapping
commands.
Use of this command makes sense only in conjunction with a service request
(SRQ).
See also “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Note: Execution of this command is started after all previously received commands
(sequential command).
Example *OPC Related commands *OPC? on page R-5
*WAI on page R-7
R-4 Common commands
Page 69
ANT-20 (Mainframe) *OPC?

*OPC?

Operation Complete Query.
Parameter None Comments Outputs an ASCII “1” to the output buffer of the instrument as soon as it is in the idle
state. As soon as all settings in the instrument are complete, a “1” is written to the output
buffer. Used to synchronize the user and instrument for overlapping commands. Example *OPC? Related commands *OPC on page R-4
*WAI on page R-7

*OPT?

Option Identification Query.
Parameter None Comments Outputs a list of the options available in the instrument.
Note: This command must always be the last query in a programming command
(see also IEEE 488.2 Section 10.20.2.2). The response is always terminated with a <NL> (0A HEX).
Example *OPT?
Response: 3035/90.33,3035/90.48 with various options set. Related commands None

*RST

Reset Command.
Parameter None Comments Instrument initialization.
The instrument goes to the STOP state and sets itself to defined default settings.
The result memory, event FIFO and list of d esired results formed with :SENS:F UNC
are cleared! “*RST” does not include the initialization operations which are executed
with “*CLS”!
See also “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Note: Execution of this command is started after all previously received commands
(sequential command).
Example *RST Related commands *CLS on page R-2
Common commands R-5
Page 70
*SRE ANT-20 (Mainframe)

*SRE

*SRE <mask> Service Request Enable Command.
Parameter Name Type Range Default
mask numeric #H00 - #HFF or
#B00000000 - #B11111111 or 0 - 255
Comments Sets the mask for service request (SRQ).
See also “WG SCPI and IEEE488 Programmer’s Introduction” for more details
Note: Bit number 6 (MSS) cannot be set and is ignored.
Example *SRE 128 Related commands *SRE? on page R-6
*STB?onpageR-7
0

*SRE?

Service Request Enable Query.
Parameter None Comments Reads out the bit mask (0 - 191) for forming the service request (SRQ).
See also “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Note: Bit number 6 (MSS) cannot be set and is always read as 0.
Example *SRE?
Response: 128
Related commands *SRE on page R-6
*STB?onpageR-7
R-6 Common commands
Page 71
ANT-20 (Mainframe) *STB?

*STB?

Read Status Byte Query.
Parameter None Comments Reads out the status byte register (0 - 255).
See also “WG SCPI and IEEE488 Programmer’s Introduction” for more
details Example *STB?
Response: 128 Related commands *SRE on page R-6
STATUS subsystem on page R-11 ff.

*TST?

Self Test Query.
Parameter None Comments Reads out the result of the power-on self-test.
0
test completed without errors
1
test found errors
Example *TST?
Response: 0 Related commands None

*WAI

Wait to Continue Command.
Parameter None Comments Waits until all previously started commands have finished.
See also “WG SCPI and IEEE488 Programmer’s Introduction” for more details
Note: This command is started after all previously received commands are
executed (sequential command).
Example *WAI Related commands *OPC on page R-4
*OPC?onpageR-5
Common commands R-7
Page 72
*WAI ANT-20 (Mainframe)
Notes:
R-8 Common commands
Page 73
ANT-20 (Mainframe) :SYST:DATE

2 SYSTEM subsystem

:SYST:DATE

:SYSTem:DATE <year>, <month>, <day> sets the current date in the instrument.
Parameter Name Type Range Default
year numeric 1970 - 2037 1970 month numeric 1 - 12 1 day numeric 1 - 31 1
Note: The setting is synchronized to the next, device- internal complete second. As
a result, erroneous values can be read if you do a read-out immediately a fter a previous setting! The setting is not changed by a *RST command.
Dependencies None Example SYST:DATE 1995,5,1 sets the date to May 1, 1995 Related commands :SYST:TIME on page R-10

:SYST:DATE?

:SYSTem:DATE? provides the current date in the instrument.
Example :SYST:DATE?
Response: 1995,5,1

:SYST:ERR[:NEXT]?

:SYSTem:ERRor[:NEXT]? reads the oldest entry out of the SCPI error queue.
See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Example :SYST:ERR?
Response: 0,”No error” if error queue is empty.
SYSTEM subsystem R-9
Page 74
:SYST:TIME ANT-20 (Mainframe)

:SYST:TIME

:SYSTem:TIME <hour>, <minute>, <second> sets the current time of day of the instrument.
Parameter Name Type Range Default
hour numeric 0 - 23 0 minute numeric 0 - 59 0 second numeric 0 - 59 0
Note: The setting is synchronized to the next, device-internal complete second. As
a result, erroneous values can be read if you do a read-out immediately after a previous setting! The setting is not changed by a *RST command.
Dependencies None Example SYST:TIME 12,10,0 sets the time of day to 12:10:0. Related commands :SYST:DATE on page R-9

:SYST:TIME?

:SYSTem:TIME? provides the current time of day of the instrument.
Example :SYST:TIME?
Response: 23,50,59

:SYST:VERS?

:SYSTem:VERSion? provides the SCPI version number on which this instrument is based.
Example :SYST:VERS?
Response: 1996.0 for version 1996 release 0.
R-10 SYSTEM subsystem
Page 75
ANT-20 (Mainframe)

3 STATUS subsystem

3.1 Status register structure

The status register structure is oriented towards the one issued by the SCPI, but with the addition of :STATus:SEQuence register and the event and capture FIFOs. The following figure shows the status register structure:
STATus:QUEStionable?
STM64/Oc192 laser heat up
STM64/OC192 laser asynchron
Calibration
Overhead Byte
Capture FIFO
not used
AU Pointer TU Pointer
SDH Alarm
(reserved)
ATM Alarm
OH sequence insertion
BPV/Code Error
Payload Error
SDH Error PDH Error ATM Error
Feac Loop
not used
Calibrating
Measuring
Wait for Trigger
8 9
10
STATus:SEQuence?
0 1 2
3 4
6
7
8
9 10 11 12 13 14 15
STATus:OPERation?
0
4
5
Event FIFO
Error Queue
SOH/TOH Byte Capture Gate
SOH/TOH Block Capture Trigger
Operation Complete
Device Dependent Error
APS Gate
not used
(not supported)
Query Error
Execution Error
Command Error
(not supported)
Power On
8
9 10
*ESR?
0
1
2
3
4
5
6
7
MAV RQS
Status Register
*STB?
0 1 2 3 4 5 6
7
Standard Event Status Register
Fig. R-1 Status register structure
STATUS subsystem R-11
Page 76
:STATus:OPERation register ANT-20 (Mainframe)

3.2 STATUS commands

:STATus:OPERation register
The OPERation status register contains conditions which are part of the
instrument’s normal operation.
:STAT:OPER:COND?
:STATus:OPERation:CONDition? provides the current value of the condition register.
Comments Bit position Meaning
0 If this bit is set the instrument is currently performing a calibration. 4 If this bit is set the instrument is currently measuring. 5 If this bit is set the instrument is in a “wait for trigger” state of the
trigger model (e.g. waiting for the start time during a timer controlled measurement).
8 This bit indicates the start and end of the measurement interval for
the APS (Automatic Protection Switch) measurement. A “1” indicates that the switching condition has been attained corresponding to the set sensor ([:SENS]:DATA[:TEL]:APS:SENS on page R-315). A “0” indicates the end of the following measurement interval, see also [:SENS]:DATA[:TEL]:A PS:GATE on page R-315.
9 If this bit is set the instrument is currently performing a SDH/
SONET overhead byte capture measurement. See also T RIGGER 2 subsystem on page R-27 ff.
10 If this bit is set the instrument is currently performing the capture
process for a complete homogeneous SDH/SONET overhead fetch result. See also TRIGGER 3 subsystem on page R-33 ff.
See SCPI handbook “Command Reference” or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Example :STAT:OPER:COND?
Response: 0
R-12 STATUS subsystem
Page 77
ANT-20 (Mainframe) :STAT:OPER:ENAB
:STAT:OPER:ENAB
:STATus:OPERation:ENABle <value> specifies the value of the enable register.
See SCPI handbook “Command Reference” or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Parameter Name Type Range Default
value numeric #H0000 - #H7FFF or
Note: Bit 15 cannot be set.
Example :STAT:OPER:ENAB 16
:STAT:OPER:ENAB?
:STATus:OPERation:ENABle? provides the current setting of the enable register. See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Example :STAT:OPER:ENAB?
Response: 0STAT:OPER:ENAB 16
:STAT:OPER[:EVEN]?
:STATus:OPERation[:EVENt]? reads the event register.
#H0 #B0000000000000000 ­#B0111111111111111 or 0 - 32767
See SCPI handbook “Command Reference” or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Note: Reading the event register clears its content.
Example :STAT:OPER?
Response: 16 if measuring event was detected.
STATUS subsystem R-13
Page 78
:STAT:OPER:NTR ANT-20 (Mainframe)
:STAT:OPER:NTR
:STATus:OPERation:NTRansition <value> specifies the value of the negative transition register.
See SCPI handbook “Command Reference” or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Parameter Name Type Range Default
value numeric #H0000 - #H7FFF or
Note: Bit 15 cannot be set.
Example :STAT:OPER:NTR 16
:STAT:OPER:NTR?
:STATus:OPERation:NTRansition? provides the current setting of the negative transition register.
See SCPI handbook “Command Reference” or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Example :STAT:OPER:NTR?
Response: 0
:STAT:OPER:PTR
#H0 #B0000000000000000 ­#B0111111111111111 or 0 - 32767
:STATus:OPERation:PTRansition <value> specifies the value of the positive transition register.
See SCPI handbook “Command Reference” or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Parameter Name Type Range Default
value numeric #H0000 - #H7FFF or
#B0000000000000000 ­#B0111111111111111 or 0 - 32767
Note: Bit 15 cannot be set.
Example :STAT:OPER:PTR 16
R-14 STATUS subsystem
#H0
Page 79
ANT-20 (Mainframe) :STAT:OPER:PTR?
:STAT:OPER:PTR?
:STATus:OPERation:PTRansition? provides the current setting of the positive transition register.
See SCPI handbook “Command Reference” or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Example :STAT:OPER:PTR?
Response: 0
:STAT:PRES
:STATus:PRESet performs a preset of the status register structure. See SCPI handbook “Command Reference” for mor e details.
Parameter None Comments The following actions are taken:
- :STAT:OPER:ENAB is set to all 0’s.
- :STAT:QUES:ENAB is set to all 0’s.
- :STAT:SEQ:ENAB is set to all 1’s.
- all positive transition registers (…:PTR) are set to all 1’s.
Example :STAT:PRES
:STATus:QUEStionable register
The QUEStionable status register set contains bits which give an indication of the quality of various aspects of the signal.
STATUS subsystem R-15
Page 80
:STAT:QUES:COND? ANT-20 (Mainframe)
:STAT:QUES:COND?
:ST ATus:QUEStionable:CONDition? provides the current value of the questionable status register.
Comments
Example :STAT:QUES:COND?
Bit position Meaning 8 If this bit is set results can be questionable because the module
needs a calibration (use the *CAL? query to initiate a calibration).
9 This bit is set while the laser is in the warm-up phase. This phase
always starts at power on. The bit is only activated for STM60 / OC192 operation.
10 This bit is set while the laser is in an unsettled state. This state
occurs each time the laser is switched on. The bit is only activated for STM60/OC192 operation.
See SCPI handbook “Command Reference” or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Response: 0
:STAT:QUES:ENAB
:ST ATus:QUEStionable:ENABle <value> specifies the value of the enable register. See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Parameter Name Type Range Default
value numeric #H0000 - #H7FFF or
#B0000000000000000 ­#B0111111111111111 or 0 - 32767
Note: Bit 15 cannot be set.
Example :STAT:QUES:ENAB 16
#H0
:STAT:QUES:ENAB?
:ST A Tus:QUEStionable:ENABle? pr ovides the current setting of the enable register. See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Example :STAT:QUES:ENAB?
Response: 0
R-16 STATUS subsystem
Page 81
ANT-20 (Mainframe) :STAT:QUES[:EVEN]?
:STAT:QUES[:EVEN]?
:STATus:QUEStionable[:EVENt]? reads the event register.
See SCPI handbook “Command Reference” or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Note: Reading the event register clears its content.
Example :STAT:QUES?
Response: 16 if measuring event was detected.
:STAT:QUES:NTR
:STATus:QUEStionable:NTRansition <value> specifies the value of the negative transition register.
See SCPI handbook “Command Reference” or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Parameter Name Type Range Default
value numeric #H0000 - #H7FFF or
#B0000000000000000 ­#B0111111111111111 or 0 - 32767
Note: Bit 15 cannot be set.
Example :STAT:QUES:NTR 16
#H0
:STAT:QUES:NTR?
:STATus:QUEStionable:NTRansition? provides the current setting of the negative transition register.
See SCPI handbook “Command Reference” or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Example :STAT:QUES:NTR?
Response: 0
STATUS subsystem R-17
Page 82
:STAT:QUES:PTR ANT-20 (Mainframe)
:STAT:QUES:PTR
:STATus:QUEStionable:PTRansition <value> specifies the value of the positive transition register.
See SCPI handbook “Command Reference” or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Parameter Name Type Range Default
value numeric #H0000 - #H7FFF or
Note: Bit 15 cannot be set.
Example :STAT:QUES:PTR 16
:STAT:QUES:PTR?
:STATus:QUEStionable:PTRansition? provides the current setting of the positive transition register.
See SCPI handbook “Command Reference” or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Example :STAT:QUES:PTR?
Response: 0
:STAT:SEQ register
#H0 #B0000000000000000 ­#B0111111111111111 or 0 - 32767
This status register indicates the states of any dynamic error/alarm/pointer sequence. This indication allows the user to get control over the state of running sequences. A bit set to “1” indicates a running sequence. A bit set to “0” indi cates a finished sequence. If bit 7 is set, then valid data are present in the FIFO of the SDH/SONET overhead capture measurement. The data can be read with the command :FETC[:ARR][:DATA][:TEL][:SDH]:OVER:CA PT? on page R-417.
Note: This status register is only accessed in the case of sequences of finite le ngth
such as single defect insertions or pointer sequences in “SINGle” mode.
:STAT:SEQ:COND?
:STATus:SEQuence:CONDition? See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
R-18 STATUS subsystem
Page 83
ANT-20 (Mainframe) :STAT:SEQ:ENAB
Example :STAT:SE Q:COND?
Response: 0
:STAT:SEQ:ENAB
:STATus:SEQuence:ENABle <value> specifies the value of the enable register.
See SCPI handbook “Command Reference” or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Parameter Name Type Range Default
value numeric #H0000 - #H7FFF or
Note: Bit 15 cannot be set.
Example :STAT:SE Q:ENAB 4
:STAT:SEQ:ENAB?
:STATus:SEQuence:ENABle? provides the current setting of the enable register. See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Example :STAT:SE Q:ENAB?
Response: 0
:STAT:SEQ[:EVEN]?
:STATus:SEQuence[:EVENt]? reads the event register.
#H0 #B0000000000000000 ­#B0111111111111111 or 0 - 32767
See SCPI handbook “Command Reference” or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Note: Reading the event register clears its content.
Example :STAT:SEQ?
Response: 0
STATUS subsystem R-19
Page 84
:STAT:SEQ:NTR ANT-20 (Mainframe)
:STAT:SEQ:NTR
:STATus:SEQuence:NTRansition <value> specifies the value of the negative transition register.
See SCPI handbook “Command Reference” or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Parameter Name Type Range Default
value numeric #H0000 - #H7FFF or
Note: Bit 15 cannot be set.
Example :STAT:SEQ:NTR 4
:STAT:SEQ:NTR?
:STATus:SEQuence:NTRansition? provides the current setting of the negative transition register.
See SCPI handbook “Command Reference” or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Example :STAT:SEQ:NTR?
Response: 0
:STAT:SEQ:PTR
#H0 #B0000000000000000 ­#B0111111111111111 or 0 - 32767
:STATus:SEQuence:PTRansition <value> specifies the value of the positive transition register.
See SCPI handbook “Command Reference” or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Parameter Name Type Range Default
value numeric #H0000 - #H7FFF or
#B0000000000000000 ­#B0111111111111111 or 0 - 32767
Note: Bit 15 cannot be set.
Example :STAT:SEQ:PTR 8
R-20 STATUS subsystem
#H0
Page 85
ANT-20 (Mainframe) :STAT:SEQ:PTR?
:STAT:SEQ:PTR?
:STATus:SEQuence:PTRansition? provides the current setting of the positive transition register.
See SCPI handbook “Command Reference” or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Example :ST AT:SEQ:PTR?
Response: 0
STATUS subsystem R-21
Page 86
:STAT:SEQ:PTR? ANT-20 (Mainframe)
Notes:
R-22 STATUS subsystem
Page 87
ANT-20 (Mainframe) :ABOR[1]

4 TRIGGER 1 subsystem

The Trigger subsystem is used for Start/Stop control of measurements (see also [:SENS]:SWE on page R-407)

:ABOR[1]

:ABORt[1] halts a measurement in progress or a timer sequence. Note: A measurement in progress is halted at the end of the next full second to
ensure homogeneous results. If the results are to be read after ending a measurement with ABORt[1], it is a good idea to insert a *W AI command between the ABORt[1] command and the read command for the results.
Parameter None Dependencies This command works only if a measurement has been previously activated using
:INIT[1][:IMM][:ALL] on page R-23. Example :ABOR Related commands :INIT[1][:IMM][:ALL] on page R-23
:TRIG[1][:SEQ]:SOUR on page R-24
:TRIG[1][:SEQ]:STIM on page R-25

:INIT[1][:IMM][:ALL]

:INITiate[1][:IMMediate][:ALL] starts the measurement on the next trigger.
Parameter None Dependencies None Comments The measurement is started on the next trigger. This can be when the next full
second is reached, or under timer control, by reaching the time preset with
:TRIG[1][:SEQ]:STIM on page R-25. The trigger condition to be fulfilled is specified
using :TRIG[1][:SEQ]:SOUR on page R-24. Example :INIT Related commands :ABOR[1] on page R-23
:TRIG[1][:SEQ]:SOUR on page R-24
:TRIG[1][:SEQ]:STIM on page R-25
TRIGGER 1 subsystem R-23
Page 88
:TRIG[1][:SEQ]:SOUR ANT-20 (Mainframe)

:TRIG[1][:SEQ]:SOUR

:TRIGger[1][:SEQuence]:SOURce <source> specifies the trigger source for the TRIGGER subsystem.
Parameter Name Type Range Default
source discrete AINTernal | STIMe |
IMMediate
Dependencies None Comments AINTernal: The trigger condition is satisfied when the next complete second is
reached.
STIMe: The trigger condition is satisfied when the start time set with
:TRIG[1][:SEQ]:STIM on page R-25 is reached.
IMMediate: The trigger condition is satisfied in an
asynchronous manner, i.e. at the next possible point in time. Example :TRIG[1][:SEQ]:SOUR STIM for the timer as a trigger source. Related commands :INIT[1][:IMM][:ALL] on page R-23
:ABOR[1] on page R-23 :TRIG[1][:SEQ]:STIM on page R-25
AINT

:TRIG[1][:SEQ]:SOUR?

This query provides the current trigger source setting.
Example :TRIG[1][:SEQuence]:SOUR?
Response: AINT for activated internal triggering at the next complete second.
R-24 TRIGGER 1 subsystem
Page 89
ANT-20 (Mainframe) :TRIG[1][:SEQ]:STIM

:TRIG[1][:SEQ]:STIM

:TRIGger[1][:SEQuence]:STIMe <year>,<month>,<day>,<hour>,<minute>,second> specifies the starting time of a timer-based measurement.
Parameter Name Type Range Default
year numeric 1994 - 2037 none month numeric 1 - 12 none day numeric 1 - 31 none hour numeric 0 - 23 none minute numeric 0 - 59 none second numeric 0 - 59 none
Dependencies Effective only if :TRIG[1][:SEQ]:SOUR STIM. Comments This command is used to set the point in time at which a timer-based measurement
is to start.
Example :TRIG:STIM 1996,6,3,18,30,00 sets the measurement start
to June 3, 1996 at 18:30:00
Related commands :INIT[1][:IMM][:ALL] on page R-23
:ABOR[1] on page R-23 :TRIG[1][:SEQ]:SOUR on page R-24

:TRIG[1][:SEQ]:STIM?

:TRIGger[1][:SEQuence]:STIMe? This query provides the current setting of the measurement start time.
Example :TRIG:STIM?
Response: 1995,12,31,23,30,20 for measurement start on December, 31, 1995 at 23:30:20.
TRIGGER 1 subsystem R-25
Page 90
:TRIG[1][:SEQ]:STIM? ANT-20 (Mainframe)
Notes:
R-26 TRIGGER 1 subsystem
Page 91
ANT-20 (Mainframe) :ABOR2

5 TRIGGER 2 subsystem

The Trigger 2 subsystem is used for Start/Stop control of SDH/SONET overhead data capture measurements (see also [:SENS]:FUNC:EVEN[:ON] on page R-405 and :FETC[:ARR][:DATA][:TEL][:SDH]:OVER:CAPT? on page R-417 ff. The status of a running capture measurement is indicated in the sta tus register (see Status register structure on page R-11 ff.) as follows:
Bit 9 (STAT:OPER) Capture Gate
Bit 7 (STAT:SEQ) Capture data available
INIT2
Capture trigger satisfied
All capture data read (FIFO is empty)
Fig. R-2 Capture measurement
Note: All commands in this group are valid only if the option BN 3035/90.15 is
available.
More captured data available
Capture aborted

:ABOR2

:ABORt2 halts a capture measurement in progress. Note: A capture measurement in progress is halted at the end of the next full
second to ensure homogeneous results.
If the results are to be read after ending a measurement with ABORt2, it is a good idea to insert a *WAI command between the ABORt2 command and the read command for the results.
Parameter None Dependencies This command works only if a capture measurement wa s previously activated using
:INIT2[:IMM][:ALL] on page R-28.
Comments A running capture measurement can be manually terminated with this command.
The measurement is automatically interrupted if the capture FIFO is full so that no further data can be recorded.
TRIGGER 2 subsystem R-27
Page 92
:INIT2[:IMM][:ALL] ANT-20 (Mainframe)
Example :ABOR2 Related commands :INIT2[:IMM][:ALL] on page R-28
:TRIG2[:SEQ]:LOG:SOUR on page R-30 :TRIG2[:SEQ]:LOG:TYPE on page R-31 :TRIG2[:SEQ]:LOG:VAL on page R-32

:INIT2[:IMM][:ALL]

:INITiate2[:IMMediate][:ALL] starts the capture measurement.
Parameter None Dependencies Option 90.15 is required for capture mea surements. Example :INIT2 Related commands :ABOR2 on page R-27
:TRIG2[:SEQ]:LOG:SOUR on page R-30 :TRIG2[:SEQ]:LOG:TYPE on page R-31 :TRIG2[:SEQ]:LOG:VAL on page R-32 :FETC[:ARR][:DATA][:TEL][:SDH]:OVER:CA PT? on page R-417

:TRIG2[:SEQ]:LOG:OBYT

:TRIGger2[:SEQuence]:LOGic:OBYTe <byte> determines the SOH/TOH byte or byte pair (K1K2) whose changes in value are to be recorded.
Parameter Name Type Range Default
byte discrete SOH/TOH bytes:
A11 | A12 | A13 | A21 | A22 | A23 | C1 | X18 | X19 | B1 | X22 | X23 | E1 | X25 | X26 | F1 | X28 | X29 | D1 | X32 | X33 | D2| X35 | X36 | D3 | X38 | X39 | H11 | H12 | H13 | H21 | H22 | H23 | H31 | H32 | H33 | B21 | B22 | B23 | K1K2 | X55 | X56 | X58 | X59 | D4 | X62 | X63 | D5 | X65 | X66 | D6 | X68 | X69 | D7 | X72 | X73 | D8 | X75 | X76 | D9 | X78 | X79 | D10 | X82 | X83 | D11 | X85 | X86 | D12 | X88 | X89 | S1 | Z12 | Z13 | Z21 | Z22 | M1 | E2 | X98 | X99 High path POH bytes: J1,B3,C2,G1,F2,H4,Z3,K3,N1 Low path POH (C3 mapping): J1L,B3L,C2L,G1L,F2L,H4L, Z3L,K3L,N1L Low path POH bytes: V5,J2,N2,K4
K1K2
R-28 TRIGGER 2 subsystem
Page 93
ANT-20 (Mainframe) :TRIG2[:SEQ]:LOG:OBYT?
Dependencies The set values of :TRIG2[:SEQ]:LOG:VAL and :TRIG2[:SEQ]:LOG:OBYT are
evaluated for the trigger source VALue and NVALue. For STM0/STS1, only bytes in the 1st, 4th and 7th column are allowed (i.e. A11 is possible but not A12 and A13). For STM4/OC12, the A1,A2,B1 bytes are not selectable. For STM16/OC48, the A1,A2,B1 bytes are not selectable. The selectable POH bytes are depending on the selected mapping (e.g. the received signal must contain a low path to select the LP-POH bytes).
Comments A11
A12 A13 A21 etc. up to X99
Bytes without a standardized name are indicated by their line and column numbers
in the SOH/TOH with a prefixed ‘X’. e.g. X25 indicates the byte in line 2 and column 5 (next to the E1 byte).
Example :TRIG2:LOG:OBYT D2
selects the D2 byte for capture measurement.
Related commands :INIT2[:IMM][:ALL] on page R-28
:ABOR2 on page R-27 :TRIG2[:SEQ]:LOG:VAL on page R-32 :TRIG2[:SEQ]:LOG:SOUR on page R-30 :TRIG2[:SEQ]:LOG:TYPE on page R-31
Value for the 1st A1 byte of the SOH as comparison byte Value for the 2nd A1 byte of the SOH as comparison byte Value for the 3rd A1 byte of the SOH as comparison byte Value for the 1st A2 byte of the SOH as comparison byte
Value for the SOH byte line 9, column 9 as comparison byte

:TRIG2[:SEQ]:LOG:OBYT?

:TRIGger2[:SEQuence]:LOGic:OBYTe? This query provides the set value for the SOH comparison byte for the trigger condition of the capture measurement.
Example :TRIG2:LOG:OBYTE?
K1K2 for the corresponding SOH comparison byte.
TRIGGER 2 subsystem R-29
Page 94
:TRIG2[:SEQ]:LOG:SOUR ANT-20 (Mainframe)

:TRIG2[:SEQ]:LOG:SOUR

: T RIGger2[:SEQuence]:LOGic:SOURce <source> determines the trigger source for the capture measurement.
Parameter Name Type Range Default
source discrete MANual | VALue | NVALue |
AUAIS | AULOP | MSRDI | MSAIS | TCMFrame
Dependencies For VALue/NVALue, the set values of :TRIG2[:SEQ]:LOG:VAL and
:TRIG2[:SEQ]:LOG:OBYT are evaluated.
Comments MANual: The SOH bytes selected with :TRIG2[:SEQ]:LOG:OBYT are
evaluated. If the measurement is started, recording begins
immediately.
VALue: The capture measurement is started if the comparison pattern
entered with :TRIG2[:SEQ]:LOG:VAL matches the received value
of the SOH byte selected with :TRIG2[:SEQ]:LOG:OBYT.
NVALue: The capture measurement is started if the comparison pattern
entered with :TRIG2[:SEQ]:LOG:VAL does not match the received
value of the SOH byte selected with :TRIG2[:SEQ]:LOG:OBYT.
AUAIS: The data recording is started if the alarm AUAIS is detected. AULOP: The data recording is started if the alarm AULOP is detected MSRDI: The data recording is started if the alarm MSRDI is detected. MSAIS: The data recording is started if the alarm MSAIS is detected. TCMFrame Tandem Connection Monitoring recording begins with the next
TCM-FAS-WORD that is found. Example :TRIG2:LOG:SOUR MSAIS
VALue
Related commands :INIT2[:IMM][:ALL] on page R-28
:ABOR2 on page R-27 :TRIG2[:SEQ]:LOG:VAL on page R-32 :TRIG2[:SEQ]:LOG:TYPE on page R-31

:TRIG2[:SEQ]:LOG:SOUR?

: T RIGger2[:SEQuence]:LOGic:SOURce? This query provides the set trigger sou rce for the capture measurement.
Example :TRIG2:LOG:SOUR?
Response: MAN for manual triggering of the capture measurement.
R-30 TRIGGER 2 subsystem
Page 95
ANT-20 (Mainframe) :TRIG2[:SEQ]:LOG:TYPE

:TRIG2[:SEQ]:LOG:TYPE

:TRIGger2[:SEQuence]:LOGic:TYPE <value> determines the time frame for data recording, referred to the trigger time point of the capture measurement.
Parameter Name Type Range Default
value discrete AFTer AFTer
Dependencies None Comments AFTer: The recording time frame of the capture measuremen t begins after
the trigger. Example :TRIG2:LOG:TYPE AFT Related commands :INIT2[:IMM][:ALL] on page R-28
:ABOR2 on page R-27 :TRIG2[:SEQ]:LOG:SOUR on page R-30 :TRIG2[:SEQ]:LOG:VAL? on page R-32 :TRIG2[:SEQ]:LOG:OBYT on page R-28

:TRIG2[:SEQ]:LOG:TYPE?

:TRIGger2[:SEQuence]:LOGic:TYPE? This query provides the set value of the recording time frame for the capture measurement.
Example :TRIG2:LOG:TYPE?
Response: AFT for recording after the trigger event.
TRIGGER 2 subsystem R-31
Page 96
:TRIG2[:SEQ]:LOG:VAL ANT-20 (Mainframe)

:TRIG2[:SEQ]:LOG:VAL

:TRIGger2[:SEQuence]:LOGic:VALue <pattern> determines the comparison pattern with which an SOH byte set with :TRIG2[:SEQ]:LOG:OBYT is compared to attain the trigger condition of the capture measurement.
Parameter Name Type Range Default
pattern string String with the allowable
characters “0” | “1” | “X” | “x” ,
16 characters long.
Dependencies The pattern set here is evaluated only for :TRIG2[:SEQ]:LOG:SOUR = VALue or
NVALue.
Comments pattern: Only the characters “0”, “1”, “X”, “x” are allowed.
A length of 16 characters is required.
For 1 byte capture, only the first 8 characters are valid. “X” | “x”: This bi t position is irrelevant for the trigger condition. “1’’ A logical 1 is necessary at this bit position to attain the trigger
condition. “0’’ A logical 0 is necessary at this bit position to attain the trigger
condition. After the trigger condition is attained, the comparison value set here is no longer
relevant, all subsequent byte changes are recorded regardless of the comparison value!
Example :TRIG2:LOG:VAL “XXXXXXXXXXXXXX01”
For K1K2 capture, Bit0 is set to 1 and Bit1 to 0 as the trigger condition. :TRIG2:LOG:VAL “XXXXXX01XXXXXXXX”
For 1 byte capture, Bit0 is set to 1 and Bit1 to 0 as the trigger condition since only the first 8 characters are relevant.
Related commands :INIT2[:IMM][:ALL] on page R-28
:ABOR2 on page R-27 :TRIG2[:SEQ]:LOG:TYPE on page R-31 :TRIG2[:SEQ]:LOG:SOUR on page R-30 :TRIG2[:SEQ]:LOG:OBYT on page R-28
“XXXXXXXX XXXXXXXX”

:TRIG2[:SEQ]:LOG:VAL?

:TRIGger2[:SEQuence]:LOGic:VALue? This query provides the set value of the comparison pattern for the trigger condition of the capture measurement.
Example :TRIG2:LOG:VAL?
Response: “XXXXXXXX0011X001” for the corresponding comparison pattern.
R-32 TRIGGER 2 subsystem
Page 97
ANT-20 (Mainframe) :ABOR3

6 TRIGGER 3 subsystem

The Trigger 3 subsystem is used to start and stop the capture process for a complete homogeneous SDH overhead fetch result. The following are required: Signal structure STM16/OC48 and options BN 3035/91.53, BN 3035/91.54 or BN 3035/91.59 (STM16c/OC48c hardware options).

:ABOR3

:ABORt3 halts the capture process started with :INIT3.
Parameter None Dependencies This command works only if the capture process has been previously activated
using :INIT3[:IMM][:ALL] on page R-33. Example :ABOR3 Related commands :INIT3[:IMM][:ALL] on page R-33

:INIT3[:IMM][:ALL]

:INITiate3[:IMMediate][:ALL] starts the capture process.
Parameter None Dependencies None Comments :INIT3 starts the capture process for a complete homogeneous SDH o verhead fetch
result. Example :INIT3 Related commands :ABOR3 on page R-33
:FETC[:ARR][:DATA][:TEL][:SDH]:OVER:CPARt[i]? on page R-416
:FETC:SCAL[:DATA][:TEL][:SDH]:OVER:CPARt[i]? on page R-426
TRIGGER 3 subsystem R-33
Page 98
:INIT3[:IMM][:ALL] ANT-20 (Mainframe)
Notes:
R-34 TRIGGER 3 subsystem
Page 99
ANT-20 (Mainframe) :OUTP:CLOC[1]:DIV[:STAT]

7 OUTPUT subsystem

:OUTP:CLOC[1]:DIV[:STAT]

:OUTPut:CLOCk[1]:DIVider[:STATe] <state> switches the clock output divider for
port [24] on or off.
Parameter Name Type Range Default
state boolean ON | OFF | 0 | 1 OFF
Dependencies Is only valid if [:SENS]:DATA[:TEL]:SDH:RATE = STM4.
A setting = ON is mandatory for STM-4 Wander measurements in conjunction
with the Jitter Module for options BN 3035/90.67 or O.172 BN 3035/90.86 with
firmware release 7.0 or later (not possible for ABT-20 devi ce s ).
A setting = ON is mandatory for STM-4 JITTER measurements in conjunction
with the Jitter Module ONLY for option O.172 BN 3035/90.86 with firmware
release 7.0 or later (not possible for ABT-20 devices).
A setting = OFF is mandatory for STM-4 JITTER measurements in conjunction
with the Jitter Module ONLY for option BN 3035/90.67 with firmware release
earlier than 7.0 (not possible for ABT-20 devices).
Comments ON | 1: The STM4 clock divider is switched on producing a 155 Mbit/s
clock signal at port [24] instead of the normal 622 Mbit/s. The setting in conjunction with the Jitter Module is explained above.
OFF | 0: Output divider off.
The setting in conjunction with the Jitter Module is explained
above. Example :OUTP:CLOC:DIV ON switches the clock output divider on. Related commands [:SENS]:DATA[:TEL]:SDH:RATE on page R-370
On Jitter Module: [:SENS]:DATA[:TEL]:RATE = STM4; [:SENS]:MODE.

:OUTP:CLOC[1]:DIV[:STAT]?

This query provides the status of the clock output divider.
Example :OUTP:CLOC:DIV?
Response: 1 if the clock output divider is switched on.
OUTPUT subsystem R-35
Page 100
:OUTP:CLOC2[:STAT] ANT-20 (Mainframe)

:OUTP:CLOC2[:STAT]

:OUTPut:CLOCk2[:STATe] <state> switches the 2488 MHz clock output (port [42]) on or off.
Parameter Name Type Range Default
state boolean ON | OFF | 0 | 1 OFF
Dependencies Is only valid if :SOUR:DATA[:TEL]:SDH:RATE = STM16. The output signal is only
valid if the receiver gets a valid STM16/OC48 input signal.
Comments ON | 1: Output on
OFF | 0: Output off This output is automatically switched ON if
:SOUR:DA TA[:TEL]:SDH:RATE = STM16 is set. Example :OUTP:CLOC2 ON switches the clock output on. Related commands :OUTP:CLOC3[:STAT] on page R-37

:OUTP:CLOC2[:STAT]?

This query provides the status of the 2488 MHz clock output.
Example :OUTP:CLOC2?
Response: 1 if the clock output is switched on.
R-36 OUTPUT subsystem
Loading...