Anritsu MT1000A Network Master Pro User manual

MT1000A Network Master Pro
OTDR Modules
Remote Scripting Operation Manual
Seventh Edition
ANRITSU CORPORATION
Document No.: M-W3859AE-7.0

•For safety and warning information, please read this manual
before attempting to use the equipment.
•Additional safety and warning information is provided
within the MT1000A Network Master Pro OTDR Modules
Operation Manual(M-W3810AE). Please also refer to it be-
fore using the equipment.
•Keep this manual with the equipment.
Notes On Export Management
This product and its manuals may require an Export Li-
cense/Approval by the Government of the product's country of
origin for re-export from your country.
Before re-exporting the product or manuals, please contact us to
confirm whether they are export-controlled items or not.
When you dispose of export-controlled items, the prod-
ucts/manuals need to be broken/shredded so as not to be un-
lawfully used for military purpose.
June 13, 2016 (First Edition)
December 18, 2020 (Seventh Edition)
Copyright c 2016-2020 ANRITSU CORPORATION.
All rights reserved. No part of this manual may be reproduced without the prior written permission of the
publisher.
The operational instructions of this manual may be changed without prior notice.
Printed in Japan
2

About This Manual
This operation manual describes the SCPI (Standard Commands for Programmable Instruments) commands
for Network Master Pro OTDR modules.
Note: SCPI commands described in this manual are supported in Network Master Pro version 11.00.
Some commands or queries in this manual may require that specific hardware or software options are installed.
These options must be purchased separately.
This operation manual uses the notations described in the following standards:
•IEEE: Std 488.2-1992
•SCPI: VERSION 1999.0 (SCPI Consortium)
3

Contents
1 Overview 9
1.1 Ethernet Based Remote Control .................................... 9
1.1.1 Connecting Cable ....................................... 9
1.1.2 Ethernet Remote Control Settings .............................. 10
1.1.3 Communication Buffers .................................... 10
1.2 Program Messages ........................................... 11
1.2.1 Program Message Unit .................................... 11
1.2.2 Program Headers ....................................... 12
1.2.3 Program Data ......................................... 13
1.2.4 Program Message Terminator ................................ 14
1.2.5 Compound Program Messages ................................ 14
1.2.6 Sequential Execution ..................................... 14
1.3 Response Messages ........................................... 15
1.3.1 Response Data ........................................ 15
1.3.2 Response Messages Terminator ............................... 17
1.3.3 Prompt ............................................. 17
1.4 Status .................................................. 18
1.4.1 IEEE488.2 Standard Status and SCPI-defined Registers ................. 18
1.4.2 Network Master Unique Status Registers .......................... 22
1.4.3 Reading, Writing and Clearing Status Registers ...................... 25
1.5 Controller Example ........................................... 27
1.5.1 PuTTY ............................................ 27
1.6 Definitions ................................................ 30
1.6.1 NaN (Not a Number) ..................................... 30
1.6.2 →Right Arrow ........................................ 30
1.6.3 Data Bit (DB) ......................................... 30
1.6.4 Port Number (Logical Port) ................................. 30
2 SCPI Conformance Information 31
2.1 SCPI Version .............................................. 31
2.2 IEEE 488.2 Mandatory Commands .................................. 32
2.2.1 *CLS .............................................. 32
2.2.2 *ESE .............................................. 32
2.2.3 *ESR? ............................................. 33
2.2.4 *IDN? ............................................. 33
2.2.5 *OPC ............................................. 33
2.2.6 *RST .............................................. 34
2.2.7 *SRE .............................................. 34
2.2.8 *STB? ............................................. 35
2.2.9 *TST? ............................................. 35
2.2.10 *WAI .............................................. 35
2.3 SCPI System Subsystem Commands ................................. 36
2.3.1 SYSTem:VERSion? ...................................... 36
2.3.2 SYSTem:ERRor[:NEXT]? .................................. 36
2.3.3 SYSTem:ERRor:ADDitional[:MESSage] .......................... 36
2.3.4 SYSTem:DATE ........................................ 37
2.3.5 SYSTem:TIME ........................................ 37
2.3.6 SYSTem:REBoot ....................................... 37
2.3.7 SYSTem:GPS:NSATellites? ................................. 38
4

CONTENTS
2.3.8 SYSTem:GPS:TIME? ..................................... 38
2.3.9 SYSTem:GPS:LOCation? .................................. 38
2.3.10 SYSTem:GPS:POWEr .................................... 38
2.3.11 SYSTem:GPS:POWEr? .................................... 38
2.3.12 SYSTem:GPS:SYNCmode .................................. 38
2.3.13 SYSTem:GPS:SYNCmode? ................................. 39
2.3.14 SYSTem:GPS:ANTNpower .................................. 39
2.3.15 SYSTem:GPS:ANTNpower? ................................. 39
2.3.16 SYSTem:GPS:PWRElapsed? ................................. 39
2.3.17 SYSTem:GPS:LOCElapsed? ................................. 39
2.3.18 SYSTem:GPS:SYNElapsed? ................................. 39
2.3.19 SYSTem:COMMunicate:TERMinator ............................ 40
2.3.20 SYSTem:PROMpt ...................................... 40
2.3.21 SYSTem:LOCal:CONTrol .................................. 40
2.3.22 SYSTem:WAIT[:IDLE] .................................... 41
2.3.23 SYSTem:WAIT:DURation .................................. 41
2.4 SCPI Instrument Subsystem Commands ............................... 42
2.4.1 Connection to Application Server .............................. 42
2.4.2 Connection to multiple applications ............................. 42
2.4.3 Connection from multiple users ............................... 42
2.4.4 Force Termination of Application Server .......................... 42
2.4.5 INSTrument:STARt[:DEFault] ................................ 43
2.4.6 INSTrument:STARt:LAST .................................. 45
2.4.7 INSTrument:STARt:GUI ................................... 45
2.4.8 INSTrument:TERMinate ................................... 45
2.4.9 INSTrument:TERMinate:FORCe .............................. 45
2.4.10 INSTrument:COUNt? ..................................... 45
2.4.11 INSTrument:CATalog? .................................... 46
2.4.12 INSTrument:STATe? ..................................... 46
2.4.13 INSTrument:CONNect .................................... 46
2.4.14 INSTrument:CONNect:ALL ................................. 46
2.4.15 INSTrument:CONNect[:CATalog]? ............................. 47
2.4.16 INSTrument:DISConnect ................................... 47
2.4.17 INSTrument[:SELect] ..................................... 47
2.4.18 INSTrument:ERRor[:NEXT]? ................................ 48
2.4.19 INSTrument:PORT? ..................................... 48
2.4.20 INSTrument:PORT:FREE? ................................. 48
2.4.21 INSTrument:PORT:CATalog? ................................ 48
2.4.22 INSTrument:MODule:CATalog? ............................... 48
2.4.23 INSTrument:CTRL:NAME? ................................. 49
2.4.24 INSTrument:CTRL:SN? ................................... 49
2.4.25 INSTrument:CTRL:TRT? .................................. 49
2.4.26 INSTrument:CTRL:OPTion:CATalog? ........................... 49
2.4.27 INSTrument:MODule<Md>:NAME? ............................ 49
2.4.28 INSTrument:MODule<Md>:SN? .............................. 49
2.4.29 INSTrument:MODule<Md>:TRT? ............................. 50
2.4.30 INSTrument:MODule<Md>:OPTion:CATalog? ...................... 50
2.5 SCPI Status Subsystem Commands .................................. 51
2.5.1 STATus:OPERation[:EVENt]? ................................ 51
2.5.2 STATus:OPERation:CONDition? .............................. 51
2.5.3 STATus:OPERation:ENABle ................................ 51
2.5.4 STATus:OPERation:PTRansition .............................. 52
2.5.5 STATus:OPERation:NTRansition .............................. 52
2.5.6 STATus:QUEStionable[:EVENt]? .............................. 52
2.5.7 STATus:QUEStionable:CONDition? ............................. 53
2.5.8 STATus:QUEStionable:ENABle ............................... 53
2.5.9 STATus:QUEStionable:PTRansition ............................ 53
2.5.10 STATus:QUEStionable:NTRansition ............................ 54
2.5.11 STATus:PORT[:EVENt]? ................................... 54
5

CONTENTS
2.5.12 STATus:PORT:CONDition? ................................. 54
2.5.13 STATus:PORT:ENABle ................................... 54
2.5.14 STATus:PORT:PTRansition ................................. 55
2.5.15 STATus:PORT:NTRansition ................................. 55
2.5.16 STATus:PRESet ........................................ 56
2.6 Mass Memory Subsystem Commands ................................. 57
2.6.1 MMEMory:LOAD ....................................... 57
2.6.2 MMEMory:STORe:STATe .................................. 57
2.6.3 MMEMory:STORe:DATA .................................. 58
2.6.4 MMEMory:DELete ...................................... 58
2.6.5 MMEMory:DATA? ...................................... 58
2.6.6 MMEMory:COPY ...................................... 58
2.6.7 MMEMory:MOVE ...................................... 59
2.6.8 MMEMory:INFO? ...................................... 59
2.6.9 MMEMory:CATalog? ..................................... 59
2.6.10 MMEMory:DCATalog? .................................... 59
2.6.11 MMEMory:MDIRectory ................................... 60
2.6.12 MMEMory:RDIRectory ................................... 60
2.6.13 MMEMory:SAVE ....................................... 60
3 Standard OTDR 61
3.1 Measurement Conditions ........................................ 61
3.1.1 OTDR:SOURce:PORT .................................... 61
3.1.2 OTDR:SOURce:TESt .................................... 61
3.1.3 OTDR:SOURce:WAVelength:AVAilable? .......................... 62
3.1.4 OTDR:SOURce:WAVelength ................................. 62
3.1.5 OTDR:SOURce:RANge:AVAilable? ............................. 62
3.1.6 OTDR:SOURce:RANge ................................... 62
3.1.7 OTDR:SOURce:RESo:AVAilable? .............................. 63
3.1.8 OTDR:SOURce:RESo .................................... 63
3.1.9 OTDR:SOURce:PULSe:AVAilable? ............................. 63
3.1.10 OTDR:SOURce:PULSe .................................... 63
3.1.11 OTDR:SOURce:AVERages:TIMe .............................. 64
3.2 IOR/BSC ................................................ 65
3.2.1 OTDR:SENSe:FIBer:IOR .................................. 65
3.2.2 OTDR:SENSe:FIBer:BSC .................................. 65
3.3 Splittter ................................................. 66
3.3.1 OTDR:SOURce:SPLitter ................................... 66
3.4 Status .................................................. 67
3.4.1 OTDR:SENSe:AVERages:TIMe? .............................. 67
3.4.2 OTDR:SENSe:TRACe:READY? .............................. 67
3.5 Measurement Functions ........................................ 68
3.5.1 OTDR:SENSe:CONCheck .................................. 68
3.5.2 OTDR:SENSe:CONState? .................................. 68
3.5.3 OTDR:CONTinue ...................................... 68
3.5.4 OTDR:SENSe:LIVCheck ................................... 68
3.5.5 OTDR:SENSe:FIBCheck ................................... 69
3.6 Analysis ................................................. 70
3.6.1 OTDR:SENSe:PATCh:LAUnch ............................... 70
3.6.2 OTDR:SENSe:PATCh:LAUnch:CORrelation ........................ 70
3.6.3 OTDR:SENSe:PATCh:RECeive ............................... 70
3.6.4 OTDR:SENSe:PATCh:RECeive:CORRelation ....................... 71
3.6.5 OTDR:SENSe:ACURsor ................................... 71
3.6.6 OTDR:SENSe:BCURsor ................................... 71
3.6.7 OTDR:SENSe:LSALeft .................................... 72
3.6.8 OTDR:SENSe:LSARight ................................... 72
3.6.9 OTDR:SENSe:LOSS:MODE ................................. 72
3.6.10 OTDR:SENSe:ORL:MODE ................................. 73
3.6.11 OTDR:SENSe:ANALyze:PARameters ........................... 73
6

3.7 TRACE ................................................. 75
3.7.1 OTDR:TRACe:PARameters? ................................ 75
3.7.2 OTDR:TRACe:ANALyze .................................. 75
3.7.3 OTDR:TRACe:ANALyze:ORL ............................... 75
3.7.4 OTDR:TRACe:MDLOss? .................................. 75
3.7.5 OTDR:TRACe:EELOss? ................................... 75
3.7.6 OTDR:TRACe:LOAD:TEXT? ................................ 76
3.7.7 OTDR:TRACe:HOFFset? .................................. 76
4 OLTS 77
4.1 Loss Test Set .............................................. 77
4.1.1 OLTS:SOURce:POWer:WAVelength:AVAilable? ...................... 77
4.1.2 OLTS:SOURce:POWer:WAVelength ............................. 77
4.1.3 OLTS:SOURce:AM:FREQuency:AVAilable? ........................ 77
4.1.4 OLTS:SOURce:AM:FREQuency ............................... 78
4.1.5 OLTS:SOURce:POWer:STATe ................................ 78
4.1.6 OLTS:SENSe:POWer:WAVelength:AVAilable? ....................... 78
4.1.7 OLTS:SENSe:POWer:WAVelength .............................. 78
4.1.8 OLTS:SENSe:CORRection:COLLect:ZERO ........................ 79
4.1.9 OLTS:SENSe:AVERage:COUNt ............................... 79
4.1.10 OLTS:SENSe:POWer:REFerence .............................. 79
4.1.11 OLTS:SENSe:POWer:THReshold .............................. 80
4.1.12 OLTS:FETCh:POWer .................................... 80
5 Measurement 81
5.1 Application, Start and Stop ...................................... 81
5.1.1 MEASurement:APPLication? ................................ 81
5.1.2 MEASurement:STARt .................................... 81
5.1.3 MEASurement:STOP ..................................... 81
5.1.4 MEASurement:RESult:SUMMary? ............................. 81
A Example Scripts 83
A.1 Hints ................................................... 83
A.2 OTDR Test ............................................... 84
List of Figures
1.1 System setup using Ethernet ...................................... 9
1.2 Connector panel ............................................. 9
1.3 Configure TCP Port for Remote Control ............................... 10
1.4 Program message structure ....................................... 11
1.5 Program message unit .......................................... 11
1.6 Response message structure ....................................... 15
1.7 IEEE488.2 standard status and SCPI-defined registers/queues. ................... 18
1.8 The Network Master Unique Status registers for some of the supported interfaces. ........ 22
1.9 The general structure for the Alarms and Errors status register for the interfaces ......... 23
1.10 The structure for the Port Status register ............................... 23
1.11 The register model for the Network Master Unique Status registers. ................ 24
1.12 Enable Implicit CR in every LF in PuTTY ............................ 27
1.13 IP Address on the instrument ..................................... 28
1.14 Specify the destination and Open the connection in PuTTY .................... 28
1.15 Connection established with PuTTY .................................. 29
1.16 Data bit .................................................. 30
1.17 The physical and logical port number of the OTDR module ..................... 30
7

LIST OF FIGURES
2.1 INST:STAR automatically connects and selects started application server. .............. 43
2.2 Original client session has to disconnect, before another client session can connect......... 43
2.3 When connected to multiple application servers, client session selects to which application server
the application specific commands are dispatched. .......................... 43
8

Chapter 1
Overview
The Network Master command based remote control functions support the built-in Ethernet service interface.
Software specifications are in conformity with the IEEE488.2 standard based on SCPI version 1999 (Standard
Commands for Programmable Instruments). Network Master becomes an automated measurement instrument
when it is connected to an external controller.
Figure 1.1: System setup using Ethernet
1.1 Ethernet Based Remote Control
1.1.1 Connecting Cable
To use remote control via the Ethernet service interface, connect an Ethernet cable to the Ethernet connector
next to the power socket.
Figure 1.2: Connector panel
9

Chapter 1 Overview
1.1.2 Ethernet Remote Control Settings
Port Number
To change a TCP port number (for a valid range, see Table 1.1) type the number in the TCP Port field (see
Figure 1.3).
Figure 1.3: Configure TCP Port for Remote Control
Setup item Description Allowable range
Port Number TCP Port Number 1024 to 65535 (default:
56001)
Table 1.1: Allowable TCP port range
1.1.3 Communication Buffers
The input- and output streams are buffered. Besides the TCP receive buffer (87380 bytes) and the TCP trans-
mit buffer (16384 bytes), the two streams share a common command/response buffer of 32 entries. Each buffer
entry can hold a compound program message of maximum 4 KB or a response message of maximum 64 KB.
Program data transferred as <ARBITRARY BLOCK PROGRAM DATA>does not go through the inter-
nal buffer, but is streamed directly from the TCP receive buffer to the internal file system. Similar for response
data of type <DEFINITE LENGTH ARBITRARY BLOCK RESPONSE DATA>; it is streamed directly from
the internal file system to the TCP transmit buffer.
10

1.2 Program Messages
1.2 Program Messages
Program messages are the remote commands sent to Network Master as shown in Figure 1.4.
Figure 1.4: Program message structure
A program message consists of one or more program message units separated with a semicolon (;). Space(s)
before or after a semicolon is ignored (space has no meaning). For more information on program message units,
see section 1.2.1 Program Message Unit.
When a program message is sent to Network Master, a terminator is appended after it. Network Master
receives the program message by detecting the terminator. For a description of the terminator, see section 1.2.4
Program Message Terminator.
The Network Master is able to handle program messages with a maximum length of 4096 characters including
the message terminator.
1.2.1 Program Message Unit
A program message unit consists of a program header and a program data, see Figure 1.5.
Figure 1.5: Program message unit
There must be one or more spaces between a program header and a program data. Network Master recognizes
the program header and program data using the space(s). One or more spaces before a program header are
ignored.
11

Chapter 1 Overview
1.2.2 Program Headers
The program header specifies the function of the command message unit sent from the controller to Network
Master. There are two types of program headers:
•Program headers for command message units.
•Program headers for query message units. Similar to headers for command message unit, but are always
followed by a question mark ”?”.
The Network Master supports some of the common commands defined in the IEEE488.2 standard. These
common commands are special in the way that they are always preceded by an asterisk ”*”; e.g. *IDN?. All
other commands are referred to as ”device specific commands”. Device specific commands consists of two or
more <program mnemonic>'s (hereinafter called ”mnemonic”) separated with a colon ”(:)”.
[:]<program mnemonic>[:<program mnemonic>]... e.g. SYSTem:TIME
A mnemonic is a character string, which consists of capital and small letters. The capital part of the
mnemonic is also referred to as the short form of the mnemonic.
•Long form program header: INSTrument:STARt
•Short form program header: INST:STAR
The Network Master recognizes a mnemonic even if only the short form is sent. For example, mnemonic SYSTem
is recognized as a normal mnemonic when SYST is sent.
In this way, capital and small letters are used for recognizing long and short forms of a mnemonic, The
Network Master does not distinguish between capital and small letters when reading the program header.
However, the Network Master only accepts the short form or the complete long form of a mnemonic. Hence
SYSTe is not a valid mnemonic. The following program headers are all acceptable and assumed to be the same:
•SYSTEM:POWER:SOURCE?
•system:power:source?
•SySteM:PoWeR:SoUr?
•syst:POW:sour?
12

1.2 Program Messages
1.2.3 Program Data
Program data is sent following the program header as parameters specified in the command message unit. This
operation manual uses the notations given below in Table 1.2 for indicating the program data format. Most of
them are defined in the IEEE488.2 standard.
Program data type Description
<BOOLEAN PROGRAM DATA>Defined in IEEE488.2
Indicates On/Off, Enable/Disable, or Yes/No.
To specify On/Enable state, set {ON|1}.
To specify Off/Disable state, set {OFF|0}.
<NUMERIC PROGRAM DATA>Comprises <DECIMAL NUMERIC PROGRAM DATA>and
<NON-DECIMAL NUMERIC PROGRAM DATA>as defined in
IEEE488.2
The Network Master accepts both decimal and non-decimal entries
for the <NUMERIC PROGRAM DATA>.
<DECIMAL NUMERIC PROGRAM Defined in IEEE488.2
DATA>Comprises <NR1>,<NR2>and <NR3>decimal values, where
<NR1>indicates an integer value.
<NR2>indicates a numeric value in fixed point format.
<NR3>indicates a numeric value in floating point format.
Examples:
<NR1>: 123
<NR2>: -123.456
<NR3>: 1.23E-3
<NONDECIMAL NUMERIC PRO- Defined in IEEE488.2
GRAM DATA>Comprises <HEXADECIMAL>,<OCTAL>or <BINARY>pro-
gram data.
See below for further details.
<HEXADECIMAL>Conforms to the hexadecimal format defined in IEEE488.2 as fol-
lows:
#{H|h}{A|a|B|b|C|c|D|d|E|e|F|f|<digit>}. . .
<digit>is an ASCII character with a value in the range of 0x30 to
0x39 (48 to 57 in decimal), that is, a numeric 0 to 9.
Examples:
#h1234ABCD
#Hfe1a9
<OCTAL>Conforms to the octal format defined in IEEE488.2 as follows:
#{Q|q}{0|1|2|3|4|5|6|7}. . .
Examples:
#q12345670
#Q77
<BINARY>Conforms to the binary format defined in IEEE488.2 as follows:
#{B|b}{0|1}. . .
Examples:
#b10101010
#B110
<STRING PROGRAM DATA>Defined in IEEE488.2
A character string in a pair of single quotation marks (') or double
quotation marks (”).
Examples:
"Network Master"
'Testing the network'
continued on next page. . .
13

Chapter 1 Overview
. . . continued from previous page
Program data type Description
<CHARACTER PROGRAM DATA>Defined in IEEE488.2
Indicates two or more mnemonics for selections. Like pro-
gram header mnemonics, <CHARACTER PROGRAM DATA>
mnemonics can have a short and a long form. The syntax used
in the Network Master additionally allows a digit as the first char-
acter of a mnemonic and also allows a dash (-) inside a mnemonic.
Table 1.2: Acceptable program data
1.2.4 Program Message Terminator
A program message terminator indicates the end of the program message. Upon reception of a terminator, the
Network Master assumes that the program message is complete and starts processing the message. A terminator
must always be added to the end of a program message. For Network Master the program message terminator is:
[<WHITE SPACE>]{NL}for Ethernet based remote control
<WHITE SPACE>is one or more ASCII characters with a value in the range of 0x00 to 0x09 or 0x0B to
0x20 (0 to 9 or 11 to 32 in decimal). These ranges include the ASCII control characters and space, except
NL (newline). Since <WHITE SPACE>includes CR (0x0D) (13 in decimal), {CR}{NL}is also interpreted as
a terminator by Network Master in Ethernet based remote control - to keep compatibility with conventional
models.
1.2.5 Compound Program Messages
Compound headers are supported by the Network Master. Examples of the use of the compound headers are
shown below.
The three program message units:
SYSTem:TIME?
SYSTem:DATE?
SYSTem:POWer:SOURce?
can be combined in one program message as follows:
SYSTem:TIME?; :SYSTem:DATE?; :SYSTem:POWer:SOURce?
or just:
SYSTem:TIME?; DATE?; POWer:SOURce?
(SYST: mnemonic can be omitted in the second and third program data units)
For further information on compound headers, see Appendix A of the IEEE488.2 standard.
1.2.6 Sequential Execution
The Network Master processes one program message unit at a time and in the same order in which they are
arranged within the program message. The Network Master will not start processing a new program message
until the processing of the current program message is finished.
14

1.3 Response Messages
1.3 Response Messages
Response messages are messages sent from a Network Master to a controller as reply to queries, see Figure 1.6.
Figure 1.6: Response message structure
A response message consists of one or more response data separated with a semicolon (;). The response
message is terminated with the response message terminator.
1.3.1 Response Data
Response data is a data returned by Network Master as reply to a query received from the controller. Table
1.3 shows examples of the response data format used in this manual.
Response data type Description
<BOOLEAN RESPONSE DATA>Defined in SCPI-99
Indicates On/Off, Enable/Disable, or Yes/No.
When ”1” is returned, it indicates an On/Enable state.
When ”0” is returned, it indicates an Off/Disable state.
<NR1 NUMERIC RESPONSE DATA>Defined in IEEE488.2
Indicates an decimal integer value.
Examples:
123
-500
<NR2 NUMERIC RESPONSE DATA>Defined in IEEE488.2
Indicates a numeric value in fixed point format.
Examples:
123.45
-500.0
continued on next page. . .
15

Chapter 1 Overview
. . . continued from previous page
Response data type Description
<NR3 NUMERIC RESPONSE DATA>Defined in IEEE488.2
Indicates a numeric value in floating point format.
Examples:
1.23E3
-5.67E-4
<HEXADECIMAL NUMERIC RE-
SPONSE DATA>
Conforms to the hexadecimal format defined in IEEE488.2 as fol-
lows:
#H{A|B|C|D|E|F|<digit>}. . .
<digit>is an ASCII character with a value in the range of 0x30 to
0x39 (48 to 57 in decimal), a numeric 0 to 9.
Example:
#H0011EEFF
<BINARY NUMERIC RESPONSE Conforms to the binary format defined in IEEE488.2 as follows:
DATA>#B{0|1}. . .
Example:
#B10101010
<STRING RESPONSE DATA>Defined in IEEE488.2
A character string enclosed in a pair of double quotation marks (”).
Example:
"Network Master - Testing the network."
<CHARACTER RESPONSE DATA>Defined in IEEE488.2
Indicates two or more mnemonics for selections. Like pro-
gram header mnemonics, <CHARACTER RESPONSE DATA>
mnemonics can have a short and a long form. The Network Mas-
ter always returns the short form. The syntax used in the Net-
work Master additionally allows a digit as the first character of a
mnemonic and also allows a dash (-) inside a mnemonic.
<EXPRESSION RESPONSE DATA>Defined in IEEE488.2
A Network Master-defined set of <RESPONSE DATA>elements
separated by a comma (,) and enclosed by a set of parenthesis.
Example:
(2,0.5),(3,0.25),(4,1.75)
For further details refer to the detailed description of the Network
Master specific commands.
<DEFINITE LENGTH ARBITRARY Defined in IEEE488.2
BLOCK RESPONSE DATA>This response data type is used when the instrument streams binary
data (typically PDF files) to the controller. It is defined as
#<nonzero digit><digits><8 bit data bytes>,
where:
<nonzero digit>is a single ASCII character in the range of '1'-'9'.
It represents the length of <digits>in number of bytes.
<digits>is a number of ASCII characters in the range of '0'-'9',
which together are a decimal representation of the number of suc-
ceeding data bytes.
Example:
#49137<9137 bytes of binary data>
Table 1.3: Network Master response data
16

1.3 Response Messages
1.3.2 Response Messages Terminator
A response message terminator indicates the end of the response message. Network Master appends the termi-
nator to the end of a response message to indicate the end of the message. For Network Master the response
message terminator is {NL}.
1.3.3 Prompt
For Ethernet based remote control a prompt can optionally be returned by the Network Master when all com-
mands in a program message has completed. The prompt is inserted after the response message if any. It can
be useful to enable the prompt when manually typing commands on the command line of the remote control
interface. The prompt inserted is:
SCPI:>
17

Chapter 1 Overview
1.4 Status
1.4.1 IEEE488.2 Standard Status and SCPI-defined Registers
Figure 1.7: IEEE488.2 standard status and SCPI-defined registers/queues.
⊕means logical OR.
18

1.4 Status
Status Byte
Bit Name Description
0 Port 1 Summary-message bit for the Port Event Summary regis-
ter.
Use the STATus:PRESet command described in section
2.5.16 and the STATus:PORT:ENABle command described
in section 2.5.13 to enable generation of this summary-
message.
1 Event Queue Summary-message bit for the Event Queue for the cur-
rently selected application server.
Use the SYSTem:ERRor[:NEXT]? command described in
section 2.3.2 to retrieve the messages.
2 Error Queue Summary-message bit for the Error queue for all connected
application servers.
Use the INSTrument:ERRor[:NEXT]? command described
in section 2.4.18 to retrieve the messages.
3 QUEStionable Summary-message bit for the Questionable Status register.
Use the STATus:QUEStionable:ENABle command de-
scribed in section 2.5.8 to enable generation of this
summary-message.
4 Output Queue Summary-message bit for the Output Queue.
5 Standard Event Summary-message bit for the Standard Event Status reg-
ister.
Use the *ESE command described in section 2.2.2 to enable
generation of this summary-message.
6 Master Summary The Master Summary Status message.
Use the *SRE command described in section 2.2.7 to enable
generation of this summary-message.
7 OPERation Summary-message bit for the Operation Status register.
Use the STATus:OPERation:ENABle command described
in section 2.5.2 to enable generation of this summary-
message.
Table 1.4: Bits in the Status Byte register (unused bits are not listed)
For more information about the Status Byte register, see section 2.2.8 on page 35.
Standard Event Status
All condition bits are immediately changed back to 0 after they are set. This means that the only way to check
the bits is to read the Event register. For more information on what triggers the Device Dependent, Execution
and Command Errors see the Error/Event Queue section on page 20.
For more information on the Standard Event Status register see section 2.2.2 on page 32.
19

Chapter 1 Overview
Bit Name Description
0 Operation Complete The condition bit changes to 1 when *OPC command is
received.
3 Device Dependent Error The condition bit changes to 1 when a required SW or
HW options is missing or the Error/Event queue is full.
4 Execution Error The condition bit changes to 1 when a command fail to
execute properly.
5 Command Error The condition bit changes to 1 when a unknown or er-
rored command is received.
7 Power On The condition bit changes to 1 when the external power
supply is connected.
Table 1.5: Bits in the Standard Event Status register (unused bits are not listed)
Error/Event Queue
When an unexpected error or event occurs, an entry is added to the Error/Event queue. This queue can hold 4
errors or events. If the queue overflows, the most recent events are discarded. A summary-message in bit 2 of
the Status Byte is 1 when the queue is not empty. Table 1.6 gives an overview of the different errors and events
inserted in the queue.
For more information about the Event queue, see section 2.4.18 on page 48.
Event Number Error Description
0 No Error (when queue is empty)
Command errors (Command Error bit is simultaneously set)
-100 Command error
-102 Syntax error
-104 Data type error
-115 Unexpected number of parameters
-130 Suffix error
-131 Invalid suffix
-138 Suffix not allowed
Execution errors (Execution Error bit is simultaneously set)
-200 Execution error
-220 Parameter error
-221 Settings conflict
-222 Data out of range
-224 Illegal parameter value
-250 Mass storage error
Device Dependent errors (Device Dependent Error bit is simultaneously set)
1 Options Missing
-350 Queue overflow
Table 1.6: Errors and events that can occur in the Error/Event queue
For more information about the Error queue, see section 2.3.2 on page 36.
20