Anritsu Site Master S331L Owner's manual

SCPI Programming Manual
S331L Site Master™
Handheld Cable and Antenna Analyzer
Anritsu Company
490 Jarvis Drive
Morgan Hill, CA 95037-2809
USA
http://www.anritsu.com
Part Number: 10580-00322
Revision: F
Published: March 2022
Copyright 2022 Anritsu Company

NOTICE
Anritsu Company has prepared this manual for use by Anritsu Company personnel and customers as a
guide for the proper installation, operation and maintenance of Anritsu Company equipment and
computer programs. The drawings, specifications, and information contained herein are the property of
Anritsu Company, and any unauthorized use or disclosure of these drawings, specifications, and
information is prohibited; they shall not be reproduced, copied, or used in whole or in part as the basis
for manufacture or sale of the equipment or software programs without the prior written consent of
Anritsu Company.
UPDATES
Updates, if any, can be downloaded from the Anritsu Website at:
http://www.anritsu.com
For the latest service and sales contact information in your area, please visit:
http://www.anritsu.com/contact-us

S331L PM PN: 10580-00322 Rev. F Contents-1
Table of Contents
Chapter 1—General Information
1-1 About this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1-2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1-3 Remote Operation Setup and Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
USB Interface Connection and Setup . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Ethernet Interface Connection and Setup . . . . . . . . . . . . . . . . . . . . . . . 1-4
Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Site Master LAN Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
1-4 Sending SCPI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
USB Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Ethernet Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Chapter 2—Programming with SCPI
2-1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2-2 Introduction to SCPI Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
SCPI Common Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
SCPI Required Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
SCPI Optional Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2-3 Subsystem Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Command Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Hierarchical Command Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Query Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Data Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Unit Suffixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
2-4 Notational Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
2-5 Notational Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Command Terminators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
2-6 Formatting Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Contents-2 PN: 10580-00322 Rev. F S331L PM
Table of Contents (Continued)
Chapter 3—All Mode Commands
Chapter 4—Cable & Antenna Analyzer Mode Commands
Appendix A—Examples
A-1 C/C++ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
A-2 Visual Basic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
A-3 Visual Basic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
A-4 Visual Basic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10
A-5 LabVIEW™ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13
Appendix B—List of Commands by Mode
Appendix C—List of Commands, Alphabetical

S331L PM PN: 10580-00322 Rev. F 1-1
Chapter 1 — General Information
1-1 About this Manual
This SCPI Programming Manual provides information for remote operation of the Site
Master S331L, Cable and Antenna Analyzer, using commands sent from an external
controller through the USB or Ethernet connection.
This Programming Manual includes the following:
•An overview of the USB and Ethernet connections to the instrument.
•An overview of Standard Commands for Programmable Instruments (SCPI) command
structure and conventions.
•The IEEE common commands that are supported by the instruments.
•A complete listing and description of all the SCPI commands that can be used to
remotely control functions of the instrument. The commands are organized by
measurement mode starting in Chapter 3.
This manual is intended to be used in conjunction with the Site Master S331L User Guide.
Refer to the instrument user guide for general information about the instrument, including
equipment setup and operating instructions.
1-2 Introduction
This chapter provides a general description of remote programming setup and interface using
USB or Ethernet, and sending SCPI commands to the instrument.
1-3 Remote Operation Setup and Interface
Remote operation of the instrument is accomplished via the USB or Ethernet interface. The
following paragraphs provide information about the interface connections, cable
requirements, and setting up remote operation.
USB Interface Connection and Setup
The Universal Serial Bus (USB) architecture is a high-performance networking standard that
is considered “plug and play” compatible. The USB driver software is automatically detected
and configured by the operating system of the devices that are connected to the bus. The
instrument conforms to the USB 2.0 standard and is a USB “Hi-speed” device that supports
data rates of up to 480 Mbps with the following restrictions:
•One USB network can support up to 127 devices
•The maximum length of USB cables between active devices is 5 meters (for USB 2.0)
and 3 meters (for USB 1.0)
You must have NI-VISA 2.5 or later installed on the controller PC and must select the VISA
library (visa32.dll) as a reference in a Visual Basic project. For remote USB control, the
controlling PC needs to have a version of VISA installed that supports USBTMC (USB Test
and Measurement Class) devices.

1-3 Remote Operation Setup and Interface Chapter 1 — General Information
1-2 PN: 10580-00322 Rev. F S331L PM
USB Interface, Type Mini-B
The USB 2.0 Mini-B device connector is used to connect the instrument directly to a
PC. The first time the instrument is connected to a PC, the normal USB device
detection by the computer operating system takes place.
1. Power on the instrument and controller PC and wait for the systems to power up
completely.
2. Connect the USB cable Mini-B connector to the instrument.
3. Connect the USB cable A connector to the controller PC USB host port. The
controller PC should indicate “New Hardware Found” if the combination of USB
VID/PID/Serial Number has never been connected to this controller PC.
Figure 1-1. USB Found New Hardware Wizard

Chapter 1 — General Information 1-3 Remote Operation Setup and Interface
S331L PM PN: 10580-00322 Rev. F 1-3
4. Select to allow the Wizard to search for and install the USB software
automatically.
5. After the software installs, close the Wizard by clicking Finish.
Figure 1-2. USB Found New Hardware Wizard
Figure 1-3. USB Found New Hardware Wizard

1-3 Remote Operation Setup and Interface Chapter 1 — General Information
1-4 PN: 10580-00322 Rev. F S331L PM
Ethernet Interface Connection and Setup
The Site Master S331L fully supports the IEEE-802.3 standard. Most Site Master functions
(except power On/Off) can be controlled via an Ethernet connection to a PC that is connected
directly (with an Ethernet cross-over cable) or through a network.
Ethernet networking uses a bus or star topology in which all of the interfacing devices are
connected to a central cable called the bus, or are connected to a hub. Ethernet uses the
CSMA/CD access method to handle simultaneous transmissions over the bus. CSMA/CD
stands for Carrier Sense Multiple Access/Collision Detection. This standard enables network
devices to detect simultaneous data channel usage (called a collision) and provides for a
contention protocol. When a network device detects a collision, the CSMA/CD standard
dictates that the data is retransmitted after waiting a random amount of time. If a second
collision is detected, then the data are again retransmitted after waiting twice as long. This is
known as exponential back off.
The TCP/IP setup requires the following:
•USB-to-Ethernet Dongle: The S331L requires the use of an external USB-to-Ethernet
dongle, such as Anritsu part number 2000-1810-R, to enable TCP/IP communication.
•IP Address: Every computer/electronic device in a TCP/IP network requires an IP
address. An IP address has four numbers (each between 0 and 255) separated by
periods. For example: 128.111.122.42 is a valid IP address.
•Subnet Mask: The subnet mask distinguishes the portion of the IP address that is the
network ID from the portion that is the station ID. The subnet mask 255.255.0.0, when
applied to the IP address given above, would identify the network ID as 128.111 and
the station ID as 122.42. All stations in the same local area network should have the
same network ID, but different station IDs.
•Default Gateway: A TCP/IP network can have a gateway to communicate beyond the
LAN that is identified by the network ID. A gateway is a computer or electronic device
that is connected to two different networks and can move TCP/IP data from one
network to the other. A single LAN that is not connected to other LANs requires a
default gateway setting of 0.0.0.0. If you have a gateway, then the default gateway
would be set to the appropriate value of your gateway.
•Ethernet Address: An Ethernet address (also known as a MAC address) is a unique
48-bit value that identifies a network interface card to the rest of the network. Every
network card has a unique ethernet address permanently stored into its memory.

Chapter 1 — General Information 1-3 Remote Operation Setup and Interface
S331L PM PN: 10580-00322 Rev. F 1-5
Connectivity
TCP/IP connectivity requires setting up the parameters that are described at the beginning of
this section. The following is a brief overview of how to set up a general LAN connection on
the Site Master.
Site Master LAN Connections
The S331L requires the use of an external USB-Ethernet dongle, such as Anritsu part
number 2000-1810-R, to connect the Site Master to a local area network (LAN). Integrated
into this dongle are two LEDs (Light Emitting Diodes). The amber LED indicates the speed of
the LAN connection (ON for 100 Mb/s and OFF for 10 Mb/s), and the green LED flashes to
show that LAN traffic is present. The instrument IP address is set automatically by using
Dynamic Host Configuration Protocol (DHCP). DHCP is an Internet protocol that automates
the process of setting IP addresses for devices that use TCP/IP, and is the most common
method of configuring a device for network use. After the Ethernet cable is connected to the
instrument, go to System, Status, Connectivity Info to view the IP address that the
instrument has been assigned.
Table 1-1. 8-pin Ethernet RJ45 Connector Pinout Diagram
Pin Name Description Wire Color
1 TX+ Transmit data (> +3 volts) White/Orange
2 TX– Transmit data (< –3 volts) Orange
3 RX+ Receive data (> +3 volts) White/Green
4 — Not used (common mode termination) Blue
5 — Not used (common mode termination) White/Blue
6 RX– Receive data (< –3 volts) Green
7 — Not used (common mode termination) White/Brown
8 — Not used (common mode termination) Brown
Note You may need to consult your network documentation or network administrator for
assistance in configuring your network setup.
8 7 6 5 4 3 2 1

1-4 Sending SCPI Commands Chapter 1 — General Information
1-6 PN: 10580-00322 Rev. F S331L PM
1-4 Sending SCPI Commands
SCPI commands can be sent to the instrument through any Virtual Instrument Software
Architecture (VISA) controller. VISA is a commonly used API in the Test and Measurement
industry for communicating with instruments from a PC. The physical connection between
the PC and the instrument is USB or Ethernet. NI-VISA is the National Instruments
implementation of the VISA I/O standard. Information and downloads are available at:
http://www.ni.com/visa/
The following example describes the verification that a VISA controller can interact with the
instrument. The images shown and the instructions for your instrument and software may
differ from the examples.
USB Connectivity
1. On the PC, run NI Measurement & Automation Explorer or VISA Interactive Control
and double-click on the TMC Class instrument.
Figure 1-4. Figure 1-4. NI Measurement & Automation Explorer

Chapter 1 — General Information 1-4 Sending SCPI Commands
S331L PM PN: 10580-00322 Rev. F 1-7
2. Verify that the USB Settings list the correct Manufacturer, Model, and Serial Number,
as shown in the example below.
Figure 1-5. NI VISA Interactive Control USB Configurations / Settings Tab

1-4 Sending SCPI Commands Chapter 1 — General Information
1-8 PN: 10580-00322 Rev. F S331L PM
3. Select the Input/Output Basic I/O tab and execute the default *IDN? Query. If the PC is
connected to the instrument the command returns the following information from the
Buffer: manufacturer name (“Anritsu”), model number/options, serial number, and
firmware package number, as shown in the example below.
Figure 1-6. NI VISA Interactive Control USB Basic I/O Tab

Chapter 1 — General Information 1-4 Sending SCPI Commands
S331L PM PN: 10580-00322 Rev. F 1-9
Ethernet Connectivity
1. On the PC, run NI Measurement & Automation Explorer or VISA Interactive Control
and create a new LAN Resource under Network Devices. Add the TCP/IP resource
using a Manual Entry of Raw Socket, as shown in the example below.
Figure 1-7. NI VISA Interactive Control LAN Resource Addition Using Raw Socket


1-4 Sending SCPI Commands Chapter 1 — General Information
1-10 PN: 10580-00322 Rev. F S331L PM
2. Enter the IP address that the instrument has acquired (go to System, Status,
Connectivity Info). Enter the port number as 9001, as shown in the example below.
Figure 1-8. NI VISA Interactive Control LAN Resource Settings of IP Address and Port Number
Figure 1-9. NI VISA Interactive Control LAN Resource Validated


Chapter 1 — General Information 1-4 Sending SCPI Commands
S331L PM PN: 10580-00322 Rev. F 1-11
3. Select the Configuration I/O settings tab and verify that the Termination Methods are
set as shown in the example below.
Figure 1-10. NI VISA Interactive Control LAN Resource I/O Termination Method Settings

1-4 Sending SCPI Commands Chapter 1 — General Information
1-12 PN: 10580-00322 Rev. F S331L PM
4. Select the Input/Output Basic I/O tab and execute the default *IDN? Query. If the PC is
connected to the instrument the command returns the following information from the
Buffer: manufacturer name (“Anritsu”), model number/options, serial number, and
firmware package number, as shown in the example below.
Figure 1-11. NI VISA Interactive Control USB Basic I/O Tab
Note
When sending SCPI commands over Ethernet, it is required to send a newline
termination character at the end of each command. In the example above, a
newline character ("\n" in this case, but could be different depending on your
programming environment) was used to terminate the *IDN? command.
Note
When sending query commands over raw socket, the entire buffer must be read
before the next query command is sent. Each query result is terminated by a
newline to help identify the end of the query response. Query read operations
could be broken into multiple reads, if necessary.
Note
When using raw socket connections, you must close a session before opening a
new one or before switching to a new protocol (such as USB). If you try to open a
new session or switch protocols without first closing the previously opened
session, you may lose communications with the instrument and not be able to
reconnect until you reboot the instrument.

S331L PM PN: 10580-00322 Rev. F 2-1
Chapter 2 — Programming with SCPI
2-1 Introduction
This chapter provides an introduction to Standard Commands for Programming Instruments
(SCPI) programming that includes descriptions of the command types, hierarchical command
structure, command subsystems, data parameters, and notational conventions.
2-2 Introduction to SCPI Programming
Anritsu instruments can be operated with the use of SCPI commands. SCPI is intended to
give the user a consistent environment for program development. It does so by defining
controller messages, instrument responses, and message formats for all SCPI compatible
instruments. SCPI commands are messages to the instrument to perform specific tasks. The
command set includes:
•“SCPI Common Commands” on page 2-2
•“SCPI Required Commands” on page 2-2
•“SCPI Optional Commands” on page 2-2
Note
The Microwave Site Master follows the SCPI standard, but is not fully compliant
with that standard. The main reason that the Site Master is not fully compliant is
because it does not support all of the required SCPI commands, and because it
uses some exceptions in the use of short form and long form command syntax.

2-2 Introduction to SCPI Programming Chapter 2 — Programming with SCPI
2-2 PN: 10580-00322 Rev. F S331L PM
SCPI Common Commands
Some common commands are defined in the IEEE-488.2 standard and must be implemented
by all SCPI compatible instruments. These commands are identified by the asterisk (*) at the
beginning of the command keyword. These commands are defined to control instrument
status registers, status reporting, synchronization, and other common functions. For
example, *IDN? is a common command supported by the Microwave Site Master.
SCPI Required Commands
The required SCPI commands supported by the instrument are listed in the Table 2-1.
SCPI Optional Commands
Table 2-2 lists the optional SCPI commands that comprise the majority of the command set
described in this document. These commands control most of the programmable functions of
the instrument.
The SCPI optional commands are sorted by measurement modes and commands may be
repeated in more than one mode.
•Chapter 3, “All Mode Commands”
•Chapter 4, “Cable & Antenna Analyzer Mode Commands”
Table 2-1. SCPI Required Commands
:STATus
:SYSTem
Table 2-2. SCPI Optional Commands
:ABORt
:CALCulate
:CALibration
:CONFigure
:DISPlay
:FETCh
:FORMat
:INITiate
:INPut
:INSTrument
:MEASure
:MMEMory
:READ
:SENSe
:SOURce
:TRACe
:TRIGger
:UNIT
:[SENSe]

Chapter 2 — Programming with SCPI 2-3 Subsystem Commands
S331L PM PN: 10580-00322 Rev. F 2-3
2-3 Subsystem Commands
Subsystem commands control all instrument functions and some general purpose functions.
All subsystem commands are identified by the colon used between keywords, as in
:INITiate:CONTinuous.
The following information is provided for each subsystem command described in the following
chapters.
•The command name, see “Command Names” on page 2-3.
•The path from the subsystem root command, see “Hierarchical Command Structure” on
page 2-4.
•The query form of the command (if applicable), see “Query Commands” on page 2-5.
•A description of the purpose of the command.
•The data parameters used as arguments for the command, see “Data Parameters” on
page 2-6. This may include the parameter type and the available parameter choices.
Command Names
Typical SCPI commands consist of one or more keywords, parameters, and punctuation. SCPI
command keywords can be a mixture of upper and lower case characters. Except for common
commands, each keyword has a long and a short form. In this manual, the long form is
presented with the short form in upper case and the remainder in lower case. For example,
the long form of the command keyword to control the instrument display is :DISPlay.
The short form keyword is usually the first four characters of the long form (example: DISP
for DISPlay). The exception to this is when the long form is longer than four characters and
the fourth character is a vowel. In such cases, the vowel is dropped and the short form
becomes the first three characters of the long form. Example: the short form of the keyword
:POWer is :POW.
Some command keywords may have a numeric suffix to differentiate between multiple
instrument features such as multiple trace options. For example,
:CALCulate#:DATA? FDATa|SDATa|FMEM|SMEM can result in two different commands, one
for trace 1 ":CALC1:DATA? FDATa" and another for trace 2 ":CALC2:DATA? FMEM".
As with any programming language, the exact command keywords and command syntax
must be used. The syntax of the individual commands is described in detail in the
programming command chapters. Unrecognized versions of long form or short form
commands, or improper syntax, will generate an error.
Note
If a numeric suffix is not included in a command, the first option is implied. Curly
brackets { } designate optional keyword or command parameters. Square brackets
[ ] designate optional command keywords. For example, the command
:TRACe[:DATA]? {1|2} can be sent as :TRACe? or :TRACe? 1, or as
:TRAC? or :TRAC? 1 to obtain data from trace 1.

2-3 Subsystem Commands Chapter 2 — Programming with SCPI
2-4 PN: 10580-00322 Rev. F S331L PM
Long Format vs. Short Format
Each keyword has a long format and a short format. The start frequency can be specified by
:SENSe:FREQuency:STARt or :SENS:FREQ:STAR. The capital letters in the command
specification indicate the short form of the command. A mixture of the entire short form
elements with entire long form elements of each command is acceptable. For example,
:SENS:FREQuency:STAR is an acceptable form of the command. However,
:SENS:FREQuen:STA is not an acceptable form of the command because :FREQuen is not the
entire short or long form of the command element.
Hierarchical Command Structure
All SCPI commands, except the common commands, are organized in a hierarchical structure
similar to the inverted tree file structure used in most computers. The SCPI standard refers
to this structure as “the Command Tree.” The command keywords that correspond to the
major instrument control functions are located at the top of the command tree. The root
command keywords for the SCPI command set are shown in Figure 2-1.
All instrument SCPI commands, except the :ABORt command, have one or more
subcommands (keywords) associated with them to further define the instrument function to
be controlled. The subcommand keywords may also have one or more associated
subcommands (keywords). Each subcommand level adds another layer to the command tree.
The command keyword and its associated subcommand keywords form a portion of the
command tree called a command subsystem. The :CONFigure command subsystem is
shown in Figure 2-2.
Figure 2-1. SCPI Command Tree
:ABORt
:CALCulate
:CALibration
:CONFigure
:DISPlay
:FETCh
:FORMat
:INITiate
:INPut
:INSTrument
:MEASure
:MMEMory
:READ
:SENSe
:SOURce
:STATus
:SYSTem
:TRACe
:TRIGger
:UNIT
[:SENSe]
root