Clear Status Command

This command clears all status data structures in the device (registers and error queue) and forces the Operation Complete state to Idle.

Standard Event Status Enable

This command provides access the Standard Event Status Enable Register.

Refer to the Status System Reporting section within this manual or IEEE 488.2, section 11.5.1 for more information about each supported bit.

Value ranges from 0 to 255.

Query returns a NR1 Numeric response.

Refer to *ESR? for the list of supported bit values.

<numeric_value>

Standard Event Status

This command queries the Standard Event Status Register.

Refer to the Status System Reporting section within this manual or IEEE 488.2, section 11.5.1 for more information about each supported bit.

Query returns a NR1 Numeric response.

Supported bits:

bit 0: Operation Complete (OP)

bit 1: Not Used

bit 2: Query Error

bit 3: Device Dependent Error

bit 4: Execution Error

bit 5: Command Error

bit 6: Not Used

bit 7: Power On

Identify

This command returns the following information in <string> format separated by commas: manufacturer name ("Anritsu"), model number, serial number, and firmware package number.

Operation Complete

The *OPC command causes the device to set the OPC bit of the Standard Event Status Register on the next transition of the No Operation Pending flag from false to true.

The *OPC? command returns 1 in the response whenever the No Operation Pending Flag is true, blocking until the operation is complete.

Note that for IQ streaming, *OPC? will return 1 immediately so that ABORt is not blocked.

Option Identification

The *OPT command queries the device to identify reportable device options. The response is a list of numeric options separated by commas. If no options are available, a value of "0" will be reported

Recall Setup

Recalls the saved setup from the desired slot, 1-9. If no setup exists at that slot, will produce an error.

Recalling from slot 0 will recall the instrument's last auto-saved setup.

<numeric_value>

Reset

This command sets the instrument into a known state that is ready for SCPI command processing. Setting the instrument into a known state includes the following steps:

1. All applications beside the default application of the particular model will be turned off.

2. Settings for all applications (regardless of an application being active) are preset to default values.

3. System settings excluding settings associated with client connections (like Ethernet addresses or DNS) are preset to default values.

4. Pending operations are aborted and the pending operation flag will be reset. The instrument will be forced into the operation complete command idle state (OCIS) and the operation complete query idle state (OQIS) before the pending operation flag is reset.

Save Setup

Saves the current instrument configuration to internal storage. Differs from :MMEMory:STORe:STATe in that the setup file is not stored in a user-accessible location.

The command accepts a number 0-9, where numbers 1-9 will save a setup to that numbered slot, and *RCL <n> will recall the setup from that slot.

Entering 0 will instead manually trigger the instrument's auto-save functionality. The instrument saves settings every 5 minutes and when shut down safely, but this may be used for situations where you wish to have a guaranteed save.

The saved setups in slots 1-9 are deleted during a User File Reset and Reset All.

<numeric_value>

Service Request Enable

This command provides access to the Service Request Enable Register.

Refer to the Status System Reporting section within this manual or IEEE 488.2, section 11.5.1 for more information about each supported bit.

Refer to *STB? for the list of supported mask bit values.

Bit 6 (MSS) cannot be set as per IEEE 488.2 standard.

Query returns a NR1 Numeric response.

<numeric_value>

Status Byte Query

This command queries the Status Byte Register.

Refer to the Status System Reporting section within this manual or IEEE 488.2, section 11.5.1 for more information about each supported bit.

Query returns a NR1 Numeric response.

Supported bits:

bit 0: Not Used

bit 1: Not Used

bit 2: Error Queue (ERRQ)

bit 3: Not Used

bit 4: Message Available (MAV)

bit 5: Standard Event Status (ESB)

bit 6: Master Summary Status (MSS)

bit 7: Not Used

Trigger

Triggers instrument if :TRIGger:SOURce command data parameter is BUS. Refer to INITiate and TRIGger subsystem commands. It performs the same function as the Group Execute Trigger <GET> command defined in IEEE 488.1.

Self Test

Causes the unit to perform a full internal self-test.

Status messages that indicate self-test results are placed in the error queue in the order they occur. Bits in the status register are also affected.

Returns the number of errors placed in the error queue. 0 means the unit passed self-test.

Wait-to-Continue Command

This command causes the device to execute no further commands or queries until the No Operation Pending flag is TRUE.

Used Memory

This command returns the total memory available on the instrument, the free memory, and the memory used by the backend process in kB.

If the instrument runs into an error while retrieving system memory data, "nan,nan,nan" will be returned as the response and a "-100" (SCPI command error) will be placed in the SCPI error queue.

Basic GPS Information

This command returns the timestamp, latitude, and longitude of the device. The response is a comma-delimited ASCII response of one of the following forms: NO FIX or GOOD FIX,<timestamp>,<latitude>,<longitude>

If no GPS fix is currently available, the first response form (NO FIX) is returned.

If the GPS does have a fix, the second response form (GOOD FIX) is returned.

<timestamp> is in ISO8601 format. The timestamp provides the 24-hour time, and will include the year/date and/or UTC offset if the hardware supports it. If no UTC offset is provided, the time is in UTC time.

<latitude> and <longitude> are specified in decimal degrees.

Full GPS Information + Satellite System Information

This command returns the fix timestamp, latitude, longitude, altitude and information on the satellites used for the last fix and the GNSS systems they are from. The response is in JSON format in the one of the following forms: {"fix":"GPS OFF"}

or {"fix":"GOOD FIX","timestamp":<timestamp>,"latitude":<latitude>,"longitude":<longitude>,"altitude":<altitude>, "satellitesUsed":<satellitesUsed>,"satellites":[ {"name":"GPS","count":x}, {"name":"Galileo","count":x}, {"name":"GLONASS","count":x}, {"name":"BeiDou","count":x}]} {"name":"SBAS","count":x}]} <timestamp> is in ISO8601 format. The timestamp provides the 24-hour time, and will include the year/date and/or UTC offset if the hardware supports it. If no UTC offset is provided, the time is in UTC time.

<latitude> and <longitude> are specified in decimal degrees.

<altitude> specifies the current altitude relative to mean sea level, in meters\.

All satellite systems will be present with a count of 0 if they are not used in the fix.

Full GPS Information

This command returns the timestamp, latitude, longitude, altitude, and satellite count of the device. The response is a comma-delimited ASCII response of one of the following forms: NO FIX or GOOD FIX,<timestamp>,<latitude>,<longitude>,<altitude>,<satellites>

If no GPS fix is currently available, the first response form (NO FIX) is returned.

If the GPS does have a fix, the second response form (GOOD FIX) is returned.

<timestamp> is in ISO8601 format. The timestamp provides the 24-hour time, and will include the year/date and/or UTC offset if the hardware supports it. If no UTC offset is provided, the time is in UTC time.

<latitude> and <longitude> are specified in decimal degrees.

<altitude> specifies the current altitude relative to mean sea level, in meters.

<satellites> specifies an integer count of the number of satellites currently used in the fix.

Activate or Deactivate Application

This command turns the specified application ON or OFF one at a time. When an application is turned ON (i.e. activated), it is loaded into memory and can be used to make measurements. An application must be activated before it will respond to commands. Please expect some delay in the application response to a command right after being turned on. The delay will vary depending on the application type and the options being installed. When an application is turned OFF (i.e. deactivated), any measurements it is making are stopped and it is unloaded from memory. Attempting to turn ON the same application twice or turn OFF an application that is not currently ON is not permitted and will result in an execution error (-200).

Attempting to turn on a different application (not the currently active application) requires turning the current application OFF. Otherwise, it will result in an execution error. To turn off an application uses the :INSTrument:APPLication:STATe command.

Unlike INSTrument:SELect, which selects a given application and makes it active if it is not already active, this command can be used to activate an application without selecting it.

If the requested application is the selected application (which can be queried with INSTrument:SELect?), turning it OFF will cause the current application selection to be reported as NONE via INSTrument:SELect?.

This command takes two parameters. The first parameter is a string value that specifies which application should be turned ON or OFF. The permitted values of this parameter are the same as those used by the INSTrument:SELect command. The second parameter is a Boolean value that specifies whether the application should be turned ON or OFF.

After a reset, the default selected application is the only active application.

<SG>,<0 | 1 | ON | OFF>

List Active Applications

This command queries all active applications. The response is returned as a comma delimited list of application names. The application names are the same as those returned by the INSTrument:CATalog:FULL? query or used as parameters to the INSTrument:SELect command.

If no applications are currently active, this query will return NONE.

Query Available Applications with all information

This query returns a JSON list of available applications with metadata including active status, appId modes and SCPI API version. [ {"name":"SPA", "active":"true", "appId":"1","modes":["SPEC","NRAD"], "version": 1}, {"name":"VNA", "active":"false", "appId":"26","modes":["VNA"], "version": 1}, {"name":"SYSTEM", "version":1 } ]

The list will always contain at least one item since the System application will always be included.

Query Available Applications

This query returns a list of string - number pairs. The string contains the name of the available application. The immediately following NR1-formatted number is its associated application number. All response data elements are comma separated.

If no application is available, a null string followed by a zero is returned.

Select Application by Number

Sets the selected application based on the value of <integer>. The query version returns the number associated with the current application. The list of valid integers and the applications they correspond to can be queried with INSTrument:CATalog:FULL?

Selecting a different application (not the currently active application) requires turning the current application OFF. Otherwise, it will result in an execution error. To turn off an application uses the :INSTrument:APPLication:STATe command.

If no applications are active, the query version of this command will return 0.

<numeric_value>

Select Application by Name

Sets the selected application based on the application name specified by <identifier>. The <identifier> is a valid application name (character data). The list of valid application names can be queried with INSTrument:CATalog:FULL?

Selecting a different application (not the currently active application) requires turning the current application OFF. Otherwise, it will result in an execution error. To turn off an application uses the :INSTrument:APPLication:STATe command.

The query version returns the name of the current application.

If no applications are active, the query version of this command will return NONE.

<SG>

NONE|SPA|VNA|SG|HIPM|CAAUSB|CWSG|VVM|CAA

NONE

Memory Catalog Directory

Returns the non-recursive contents of the memory specified by the MSUS and DIRECTORY parameters. Both parameters are case sensitive.

Parameter 1: Directory. Use "/" as a directory separator. Note that this parameter should NOT be an empty string. To access the root directory, pass in "/" as the first parameter.

Parameter 2: MSUS (Use :MMEMory:CATalog:MSUSs query command to retrieve the list of available storage devices).

For example:

MMEMory:CATalog:DIRectory? "/", "USB1-1"

The response is formatted as follows: <total space used on MSUS>,<total space available on MSUS>,{<file entry1>},..{<file entryN>} where <file entry> is: <file or directory name>,<file type>,<file size>

<string>,<string>

MMemory Catalog Directory Size

This command is query-only and returns the size of a given directory. It has two parameters. Both are case sensitive.

<directory>,<msus>

Parameter 1: The full path of a directory to query the size. Use "/" as a directory separator. Note that this parameter should NOT be an empty string. To access the root directory, pass in "/" as the first parameter.

Parameter 2: MSUS (Use :MMEMory:CATalog:MSUSs query command to retrieve the list of available storage devices).

For example:

MMEMory:CATalog:DIRectory:SIZE? "/", "USB1-1"

The response is a single ASCII string of the size of the given directory.

<string>,<string>

Memory Catalog Msuss

Returns a list of all available mass storage devices present, formatted as follows: <Device Name 1>,<Device Name 2>,...<Device Name N>

For example, sending:

MMEMory:CATalog:MSUSs?

could return:

Internal,USB1-1

Default Mass Storage Directory

This command selects the default directory on the default mass storage device (see :MMEMory:MSIS) for use with MMEMory commands. The parameter is case sensitive. Use "/" as a directory separator.

For example:

MMEMory:CDIRectory "/example_folder"

The set command will fail and an error is reported if the requested directory does not exist. Note that the query command returns the name of the default directory that was previously set and the device does not check whether the directory is still present.

<string>

/

Copy File

This command copies the specified source file into a new file located at the specified destination location. Four parameters are required for this command:

1. Source File Location: The file path to the file to be copied.

2. Source MSUS: The mass storage device the file is located in (i.e. Internal).

3. Destination File Location: The destination file path that the file should be copied to.

4. Destination MSUS: The mass storage device that the destination file should be written to (i.e. Internal).

For example:

MMEMory:COPY "/example_file.ext", "Internal", "/example_file.ext", "USB1-1"

Please note that if a file already exists at the destination location or if the source file does not exist, the command will fail to execute and add an execution error into the SCPI error queue. This command will only copy files. If a directory path is passed in as a parameter, the command will fail to execute.

<string>,<string>,<string>,<string>

Create Directory

Creates a directory at the specified mass storage device. Both parameters are case sensitive.

Parameter 1: Directory. Use "/" as a directory separator.

Parameter 2: MSUS (Use :MMEMory:CATalog:MSUSs query command to retrieve the list of available storage devices)

For example:

MMEMory:CREate:DIRectory "/example_folder", "USB1-1"

If the intermediate directories in the path don't exist, the command will automatically create them. Common causes of the command failure are:

- The MSUS device is not present (Use :MMEMory:CATalog:MSUSs query command to retrieve the list of available storage devices)

- The total space available on MSUS device is not big enough (Use :MMEMory:CATalog:DIRectory query command to retrieve the total space available on MSUS)

<string>,<string>

File Transfer

This command imports/exports a file to/from the instrument. Data is transferred to/from the instrument as an IEEE definite length arbitrary block response, which has the form <header><block>.

This set command takes three parameters:

1. File Path: The path of the file to be written

2. Msus: The mass storage device to write the file to

3. Block Data: The data to be written to the instrument in block data format

If any directories in the file path do not exist, the instrument will automatically create the required directories. Please note that the maximum file transfer size to the instrument is 25 MB.

The ASCII header specifies the number of data bytes of the file. It looks like #AX, where A is the number of digits in X and X is the number of bytes in the <block>. The first character is the literal ascii hash '#' 043. The second character (A) is a single ascii digit '1' to '9' describing the number of bytes in the length section (X). This number is called nlength. The next nlength bytes make up an ascii string of digits '1' to '9' describing the length of the <block> data.

For example, if the first 6 bytes are #49999, then the nlength is 4. The 4 bytes of length are 9999. After that follows the <block>, which would be 9999 bytes in size.

The query command takes two parameters.

1. File Path: The path to the file to be retrieved.

2. Msus: The mass storage device to retrieve the file from.

The file is returned in block data format with an ASCII header The query command will return a #10 if the file cannot be found.

<string>,<string>,<block data>

<string>,<string>

Delete Directory

Deletes the specified directory and all its content at the specified mass storage device. The two parameters for this command are directory name and mass storage device. Both parameters are case sensitive. Use "/" as a directory separator. To delete the root folder in a specified mass storage device, enter "/" for directory name parameter.

For example:

MMEMory:DELete:DIRectory "/example_folder", "USB1-1"

The available mass storage devices can be retrieved by using the :MMEMory:CATalog:MSUSs command. The command will fail if the directory doesn't exist or the mass storage device is not present.

<string>,<string>

Delete File

Deletes the specified file at the specified mass storage device. The two parameters for this command are file name with relative path and mass storage device. Both parameters are case sensitive. Use "/" as a directory separator.

For example:

MMEMory:DELete:FILe "/example_folder/example_file.ext", "USB1-1"

The available mass storage devices can be retrieved by the :MMEMory:CATalog:MSUSs command. The command will fail if the file doesn't exist or the mass storage device is not present.

<string>,<string>

Eject USB drive

This command safely ejects (unmounts) a USB drive from the instrument. Following this command, a USB drive can be safely removed from the instrument. See :MMEMory:CATalog:MSUSs for more information on obtaining the name of the USB drive(s) currently mounted on the instrument.

For example:

MMEMory:EJECT "USB1-1"

<string>

Load State

This command recalls the specified setup. The file location is resolved using the MSUS and file path parameters. These parameters are case sensitive.

Parameters:

1. Numeric Value: currently unused. Send a 0.

2. File path: The file path (including file name) relative to the MSUS root directory. File extension is optional.

3. MSUS: Device to recall the file from. See MMEMory:CATalog:MSUSs? for information on obtaining the list of available devices.

For example:

MMEMory:LOAD:STATe 0,"/example_setup_file", "Internal"

The model of the device that the setup was created in must match the model of the device to recall in; otherwise, the recall will be rejected. The options of the device that the setup was created in must be enabled in the device to recall in; otherwise, the recall will be rejected.

<numeric_value>,<string>,<string>

Default Mass Storage Device

This command selects the default device for use with MMEMory commands. The mass storage device parameter is case sensitive and must match a device returned from the :MMEMory:CATalog:MSUSs? command

For example:

MMEMory:MSIS "Internal"

<string>

Internal

Screen Shot

The set command prompts a screenshot of the local UI to be taken and saved to local user storage. The naming convention and file path will be the same as what has been set up when taking a screenshot through the UI.

The query command will take a screenshot and return the image file as block data. No image will be saved in the local user storage.

The binary block header specifies the number of data bytes. It looks like #AX, where A is the number of digits in X and X is the number of bytes in the <block>.

The first character is the literal ascii hash '#' 043.

The second character (A) is a single ascii digit '1' to '9' describing the number of bytes in the length section (X). This number is called nlength.

The next nlength bytes make up an ascii string of digits '1' to '9' describing the length of the <block> data.

For example, if the first 6 bytes are #49999, then the nlength is 4. The 4 bytes of length are 9999. After that follows the <block>, which would be 9999 bytes in size.

Store State

This command saves the current setup to the specified file location. The file location is resolved using the MSUS and file path parameters. These parameters are case sensitive. If a file with the resolved name already exists, it will be overwritten.

Parameters:

1. Numeric Value: currently unused. Send a 0.

2. File path: The file path (including file name) relative to the MSUS root directory. File extension should not be specified.

3. MSUS: Device to save the file on. See MMEMory:CATalog:MSUSs? for information on obtaining the list of available devices.

For example:

MMEMory:STORe:STATe 0,"/example_setup_file", "Internal"

A common cause of the command failure is not having enough space available on MSUS to save the setup. Use :MMEMory:CATalog:DIRectory query command to retrieve the total space available on MSUS.

<numeric_value>,<string>,<string>

Status Operational Condition

Returns the contents of the Operational Condition register in <NR1> format. When executed, this command does not clear the Operational Condition register.

Status Operational Enable

Sets the bits of the Operational Enable register associated with the Operational Event register to the binary weighted integer value specified by the mask parameter.

<numeric_value>

Status Operational Event

Returns the contents of the Operational Event register in <NR1> format. This command clears the Operational Event register.

Status Operational Negative Transition

Sets the bits of the negative transition filter for the Operational Condition register to the binary weighted integer value specified by the mask parameter.

<numeric_value>

Status Operational Positive Transition

Sets the bits of the positive transition filter for the Operational Condition register to the binary weighted integer value specified by the mask parameter.

<numeric_value>

Status Preset

This command is an event that configures the SCPI and device-dependent status reporting structures so that device-dependent events are summarized and reported. This command performs the following functions:

Sets the Operational Enable register to all 0's.

Sets the Operational Positive Transition Filter to all 1's.

Sets the Operational Negative Transition Filter to all 0's.

Sets the Questionable Enable register to all 0's.

Sets the Questionable Positive Transition Filter to all 1's.

Sets the Questionable Negative Transition Filter to all 0's.

Status Questionable Condition

Returns the contents of the Questionable Condition register in <NR1> format. When executed, this command does not clear the Questionable Condition register.

Status Questionable Enable

Sets the bits of the Questionable Enable register associated with the Questionable Event register to the binary weighted integer value specified by the mask parameter.

<numeric_value>

Status Questionable Event

Returns the contents of the Questionable Event register in <NR1> format. When executed, this command clears the Questionable Event register.

Status Questionable Negative Transition

Sets the bits of the negative transition filter for the Questionable Condition register to the binary weighted integer value specified by the mask parameter.

<numeric_value>

Status Questionable Positive Transition

Sets the bits of the positive transition filter for the Questionable Condition register to the binary weighted integer value specified by the mask parameter.

<numeric_value>

Primary GPIB Address

This command sets the Primary GPIB address of the instrument.

<numeric_value>

Numeric

5

0 to 30

GPIB Output Terminator

This command configures the line termination method for message data

sent by the instrument. Selection is between line feed (LFeed), carriage return (CReturn),

or carriage return and line feed (CRLFeed). Note that regardless of selection,

response data is always terminated with EOI.

<CRETurn|CRLFeed|LFEed>

CRET|CRLF|LFE

LFEed

Static LAN Configuration

This command set and queries the static ethernet configuration of the device. The static configuration allows user to specify the ip, gateway, and subnet mask of the unit on a network. Parameters:

- Static IP Address: The desired IP address of the unit.

- Gateway: (optional) The network gateway

- Subnet Mask: (optional) The subnet mask of the network the device is connected to.

For a subnet mask of 255.255.255.0(/24), you only have a valid host IP range of x.x.x.1-x.x.x.254. The first IP in the subnet (x.x.x.0) is reserved for the network ID and the last one (x.x.x.255) is reserved as the broadcast ID. You can have a different range of valid host addresses if you change the subnet mask to a different number. For example, if a subnet mask of 255.255.254.0 is used, the gateway can be set to 192.168.101.0 since the valid host IP range is 192.168.100.1-192.168.101.254.

More information on subnetting can be found here:

https://docs.microsoft.com/en-us/troubleshoot/windows-client\networking/tcpip-addressing-and-subnetting

A calculator for finding valid host IP addresses in a subnet can be found here:

https://www.calculator.net/ip-subnet-calculator.html

The Gateway and Subnet Mask settings will remain no change if user has no input.

The dhcp will be turned off.

A new valid configuration will automatically be applied to the device. The user will be required to access the unit through the new configuration.

CAUTION: Consult with your network administrator when configuring the network interface to avoid potential loss of access or discovery of the device.

<string>,[<string>],[<string>]

Current LAN Configuration

This command queries the current ethernet configuration of the device.

DHCP Configuration

This command sets and queries the DHCP configuration of the device. If the DHCP configuration is set to OFF, the device is configured to the static ethernet configuration (See :SYSTem:COMMunicate:LAN:CONFig). If the DHCP configuration is set to ON, the device will obtain its IP address, gateway, and subnet mask from the DHCP server in the network.

This set command should be used to caution, as changing the ethernet configuration will result in temporary loss of communication with the device.

CAUTION: Consult with your network administrator when configuring the network interface to avoid potential loss of access or discovery of the device.

<ON|OFF>

ON|OFF

OFF

Dynamic DNS Configuration

This command sets and queries the Dynamic Domain Name Server (Dynamic DNS) configuration of the device. Currently, only http://www.noip.com (TM) is available for use. For support, please contact the vendor at http://www.noip.com.

- Dynamic DNS NoIp.com Host Name: Desired host name of the device.

- Dynamic DNS NoIp.com Username: noip.com username.

- Dynamic DNS NoIp.com Password: noip.com password.

<string>,<string>,<string>

Domain Name System Server Append

This command will add one or more Domain Name System Servers to the end of the device's current list of DNS Servers.

To view the entire list of DNS Servers, see SYSTem:COMMunicate:LAN:DNSServer:LIST. To remove a DNS Server, see SYSTem:COMMunicate:LAN:DNSServer:DELete.

This command takes a list of one or more string values. For example: SYSTem:COMMunicate:LAN:DNSServer:APPend "8.8.8.8", "123.125.81.6"

<string>, {<string>}, ...

Domain Name System Server Delete

This command will delete the device's given Domain Name System Servers from the device's current list of DNS servers. To view the entire list of DNS Servers, see SYSTem:COMMunicate:LAN:DNSServer:LIST.

This command takes a list of one or more string values. For example: SYSTem:COMMunicate:LAN:DNSServer:DELete "8.8.8.8", "123.125.81.6"

<string>, {<string>}, ...

Domain Name System Server List

This command sets and retrieves a list of the device's currently set Domain Name System Servers.

The DNS Server is used to resolve a Domain Name. The list of DNS Servers will be contacted after any DNS Server assigned by DHCP Setting, if applicable, and will be contacted in the order given in the list.

This command takes a list of one or more string values. Setting the DNS server list with this command will override the currently set DNS server list.

An example of using the command: SYSTem:COMMunicate:LAN:DNSServer:LIST "8.8.8.8", "123.125.81.6"

This query version of this command returns a comma delimited list of strings. For example: 123.125.81.6,8.8.8.8

To remove DNS Server, see SYSTem:COMMunicate:LAN:DNSServer:DELete.

To add to the end of the current list, see SYSTem:COMMunicate:LAN:DNSServer:APPend.

<string>, {<string>}, ...

FTP Server State

This command sets the system up to execute (ON) or bypass (OFF) the FTP server startup on the next instrument boot.

The query returns the state of the FTP server based on the bypass flag, 0 for bypass, 1 for start. The actual state of the FTP server is not check for the query.

<0 | 1 | ON | OFF>

Local Host Name

This command sets and retrieves the local host name of the instrument. A valid hostname may contain only the ASCII letters 'a' through 'z' (in a case-insensitive manner), the digits '0' through '9', and the hyphen ('-'). They cannot start/end with '-'.

No other symbols, punctuation characters, or white space are permitted.

<string>

HTTPS Port State

This command sets the system up to allow (ON) or bypass (OFF) the HTTPS port setup on the next instrument boot.

The query returns the state of the HTTPS port based on the bypass flag, 0 for bypass, 1 for configure. The actual state of the HTTPS port is not check for the query.

<0 | 1 | ON | OFF>

System Date

This command sets and queries the system's internal calendar. Changing the system date does not affect the system time zone (if time zone is available). The three parameters for this command are <year>,<month> and <day>. The query response message shall consist of three fields separated by commas: <year>,<month>,<day>.

The year shall be entered as a four-digit number, including century and millennium information. This shall not be affected by a *RST command. Note: Some products only support the query version of this command.

<numeric_value>,<numeric_value>,<numeric_value>

Default Reset All

This command performs a factory reset as well as deletes last saved settings, log files, and user files. The factory reset includes presetting parameters in all applications, presetting all system settings with the exception of ethernet settings (DHCP On/Off, static IP, Static Gateway, Static Subnet) and time zone settings, and cleaning up all previous access point connections if the instrument is equipped with WiFi.

Reset System Files

This command deletes the instrument data files as specified in the following table:

Parameter Value Description

USER Deletes all user files in the instrument's internal memory including measurements, setup files, and screen shots. User-customized system files will not be deleted.

SYSTem Deletes all user-customized system files including keyboard EZ names, cable lists, antenna lists, and log files.

<USER|SYSTem>

Factory Default Reset

This command presets parameters in all applications as well as system settings with the exception of ethernet settings (DHCP On/Off, static IP, Static Gateway, Static Subnet) and time zone setting to their factory default values, and restarts the instrument. Last saved settings will be deleted. If unit equips with WiFi, the previous access point connections will be clean up.

SCPI Error Message State

Sets or queries the state of SCPI error messages being displayed. By default, when a SCPI error enters the error queue it will be displayed on-screen. This command toggles whether those errors should be displayed. This command defaults to 0, meaning errors will NOT be displayed.

Usage: Suppress SCPI Error Messages: SYST:ERR:DISP 0 Show all SCPI Error Messages: SYST:ERR:DISP 1.

<0 | 1 | ON | OFF>

0 | 1

OFF

System Error Queue

If an error occurs, the error number and message are placed in the error queue, which can be read by this query command. Errors are cleared by reading them. Error code 0 is "No error".

Error codes from -100 to -199 belong to the Command error category and set bit 5 of the standard ESR register.

Error codes from -200 to -299 belong to the Command error category and set bit 4 of the standard ESR register.

Error codes from -400 to -499 belong to the Query error category and set bit 2 of the standard ESR register.

Error codes from -300 to -399 and 1 to 32767 belong to the Device-specific error category and set bit 3 of the standard ESR register.

Negative error numbers (command error, execution error, device-dependent error, query error) are standard SCPI errors. Positive error numbers are device specific errors, not standard SCPI errors.

The error queue is also cleared by *CLS, *RST, and when power is turned on.

If more errors have occurred than can fit in the buffer, the last error stored in the queue (the most recent error) is replaced with -350, Queue overflow. No additional errors are stored until removing errors from the queue. If no errors have occurred when reading the error queue, the instrument responds with 0, No error.

Firmware Update

Initiate a firmware update from the MSUS whose path is specified as parameters. If the requested firmware package is not recognized, an appropriate error will be added to the error queue. Otherwise, the instrument will verify that the package is safe to install, update to the new firmware.

The two parameters for this command are file name with relative path and mass storage device. Both parameters are case sensitive. Use "/" as a directory separator.

For example:

SYSTem:FIRMware:UPDate "V2019.01.1.raucb", "USB4-1"

The available mass storage devices can be retrieved by the :MMEMory:CATalog:MSUSs command. The command will fail if the file doesn't exist or the mass storage device is not present.

<string>,<string>

Firmware Package List

This command queries the instrument for a list of firmware packages that can be installed from mounted USB block devices. Please note that firmware packages are only detected on the top level of a USB block device. Any files located in subfolders will be ignored.

The response is in JSON format and consists of the path of the package relative to the root of the MSUS, the MSUS that the package is located in, and the version of the package.

The following is an example of the response: [{"msus":"USB1-1","path":"V2018.2.22.raucb","version":"V2018.2.22"}, {"msus":"USB2-1","path":"V2018.2.19.raucb","version":"V2018.2.19"}]

These package names enumerate the valid parameter values to the :SYSTem:FIRMware:UPDate command.

Remote Firmware Update

Initiate a remote firmware update to the package whose name is specified as a parameter. Use :SYSTem:FIRMware:UPDate:REMote:LIST? to inspect the packages that can be installed. If the requested firmware package is not recognized, an appropriate error will be added to the error. Otherwise, the instrument will download the specified firmware package, verify that the package is safe to install, update to the new firmware.

The instrument will disconnect all remote clients and reboot after the new firmware has been installed.

If the <STRING DATA> argument begins with (case insensitive) any of

http://

https://

ftp://

Then the firmware update will be downloaded from that URL. The URL must be percent-encoded per RFC-2396 section 2.4.1.

<string>

Remote Firmware Update Auto Check

This command sets and queries the state to enable automatically checking a remote server (see SYSTem:FIRMware:UPDate:REMote:SOURce?) for software updates. If this command is set to ON, The server will be checked for a newer version on bootup and every 24 hours thereafter. If this command is set to OFF, no automatic checking will take place, but a check can be initiated manually (see SYSTem:FIRMware:UPDate:REMote:LIST:REFResh command). If the check finds a newer version available, the SYSTem:FIRMware:UPDate:REMote:LATest? query will indicate the newer version. Use the SYSTem:FIRMware:UPDate:REMote command to initiate the download and install.

<0 | 1 | ON | OFF>

0 | 1

ON

Check For Firmware Update

Check whether the instrument firmware is at the latest version. This command will access the package list specified by SYST:FIRM:UPD:REM:SOUR and return a response of the form <string>,<number> where <string> is the name of the latest firmware package, and <number> is 1 if the latest firmware package is newer than the version of firmware currently installed (a firmware update is available), or 0 if the current instrument firmware version matches the latest version (the instrument is up to date).

Clients can update the instrument to the latest firmware by passing the <string> component of the response as a parameter to the SYST:FIRM:UPD:REM command.

Remote Firmware Package List

This command queries the instrument for a list of firmware packages that can be installed remotely. The package list will be populated from a resource file that is downloaded from a URL specified by the current value of :SYSTem:FIRMware:UPDate:REMote:SOURce.

The response is ASCII response consisting of one or more comma-delimited package names. For example: 2.0.0,1.0.0

These package names enumerate the valid parameter values to the :SYSTem:FIRMware:UPDate:REMote command.

Remote Firmware Package List Refresh

This command causes the list of firmware packages that can be installed remotely (:SYSTem:FIRMware:UPDate:REMote:LIST?) to be refreshed from the remote source server immediately. Normally the list is automatically updated on a timer interval to limit the amount of network requests. The exact timer interval varies by model and could be anywhere from one minute to one day. Use this command if you do not want to wait for the next automatic timer-based update to the remote firmware package list.

Note that this command only initiates the request to the server to get the updated list of packages. It does not wait until the list (as visible by :SYSTem:FIRMware:UPDate:REMote:LIST?) is actually updated as the request is made asynchronously.

Remote Firmware Package Source

This command sets or queries the instrument's remote firmware update package list source. This source must be an http URL that is accessible to the instrument over the current network interface.

The set version of this command takes a string that spells the URL to the package list file. The query version returns that string. The default value points to the repository on anritsu.com where official firmware packages for this instrument are distributed. Most users will never need to change this setting from the default.

For example, the url value either set or query returned may be:

http://softwareupdates.anritsu.com/en-us/ms209xa.txt

The package list file must be a JSON file that has a minimum structure. The root object must contain a "version" string (which is reserved but currently unused), a "packages" array of zero or more package objects (each at minimum have a "name", "url", "version", and "model"), and a "default" string that matches one of the package names, or is "". The version and model attributes have semantic meaning, but the name and filename (url) can be anything. An example package list file is shown below:

{

"default": "V2021.11.2 (MS209xA)",

"packages": [

{

"name": "V2021.11.2 (MS209xA)",

"version": "V2021.11.2",

"model": "MS209xA",

"url": "http://softwareupdates.anritsu.com/en-us/MS2090A_V2021.11.2.raucb"

}

],

"version": "1.0.0"

}

or, as with MS2710xA:

{

"default": "V1.0.0 (MS2710xA)",

"packages": [

{

"name": "V1.0.0 (MS2710xA)",

"version": "V1.0.0",

"model": "MS2710xA",

"url": "http://softwareupdates.anritsu.com/en-us/MS2710xA_V1.0.0.tar"

}

],

"version": "1.0.0"

}

When the package source is set, the instrument will attempt to download the file and validate it according to the above rules before making the change permanent. If the file cannot be accessed or the file does not conform to the minimum criteria, a device specific error will be added to the error queue and the package source will remain unchanged.

<string>

Firmware Version

This command queries the device firmware version.

GPS Satellite System Search Mode

Sets and queries the GPS Satellite system search option.

The satellite system search options can be:

GPS: GPS only

GGLonass: GPS + GLONASS

GGALileo: GPS + GALILEO

GBEidou: GPS + BEIDOU

GGGalileo: GPS + GLONASS + GALILEO

<GGLonass|GGALileo|GBEidou|GGGalileo>

GGL|GGAL|GBE|GGG

GGGalileo

GPS State

Enable or disable the GPS. When the GPS is OFF, the GPS module is placed into standby to save power, and features which depend on the GPS may be unusable.

<0 | 1 | ON | OFF>

0 | 1

OFF

System Error Log

This command retrieves the error log. The log is encrypted and can be saved to a file and sent to Anritsu Service if required.

MAC Address

Query the MAC address of the instrument.

Setting the MAC address is only available to customer service.

System Model Override

Allows the user to specify an override for the model returned by *IDN? for

backwards compatibility. Defaults to NONE.

<NONE|MG369xA|MG369xB|MG369xC>

NONE|MG369xA|MG369xB|MG369xC

NONE

Query Options

This command retrieves the options that are currently set. The response is returned in "/" delimited form.

Query All Options

This command returns all installed options with their metadata in JSON format. The expiration date time is in UTC time and in a string format of the form yyyy-MM-ddTHH:mm:ss corresponding to the ISO 8601 specification.

Example:

[{"expirationDate":"","option":"0090", "state":"active", "description":"Gated Sweep"},

{"expirationDate":"2022-07-05T19:00:42Z","option":"9103", "state":"pendingReboot", "description":"50 MHz Analysis Bandwidth" },

{"expirationDate":"","option":"9431", "state":"available", "description":"Coverage Mapping"}]

Option Configuration

This command returns a quoted string of characters readable only by Anritsu Customer Service. Only instrument configuration information is returned. No setup information is included.

Activate Timed Options

This command activates an existing Timed Option.

<string>

Option Update Remote

This command retrieves all available Licenses for given instrument and installs them.

Option Upgrade

This command upgrades the options of the device with a valid license key provided as a quoted string parameter. The device must be rebooted immediately after this command for the installation of the new options to complete. The device must not be powered off while the command is executing. When the operation completes, a success message will be shown and request to reboot the device. The recommended way to restart the device safely is by sending the *RST command after this command. This command might report the following error code: -200: The command failed to complete. A detailed error message will be provided in the response of :SYStem:ERRor[:NEXT]? command. -2: The command failed because the options provided in the option file are incompatible with this instrument.

<string>

Preset

This command presets parameters in the current application to their factory default values.

System Reboot

This command saves the current state of the instrument and reboots the instrument.

System Shutdown

This command shuts down the instrument. The current instrument state and settings will be saved.

Get CPU Temperature

This command returns the CPU temperature in Celsius.

System Time

This command sets and queries the system's internal clock. Changing the system time does not affect the system time zone (if time zone is available). The three parameters for this command are <hour>,<minute> and <second>. The query response message shall consist of three fields separated by commas: <hour>,<minute>,<second>. Note: Some products only support the query version of this command.

<numeric_value>,<numeric_value>,<numeric_value>

Sync System Time

This command sets the system to either automatically synchronize with GPS/Internet server or manually adjust the time setting. Valid parameter values are AUTO|MANual. When AUTO is selected, GPS takes priority if it is present and turned on (see command :SYSTem:GPS:STATe to set GPS on or off). When the time setting is AUTO synchronized, the current time zone setting is not changed.

<AUTO|MANual>

AUTO|MAN

AUTO

Sync Time Status

This command query the last system time synchronization status. The return value range are INT, GPS, NONE, or NA.

INT - the system time was successfully synchronized with internet server.

GPS - the system time was successfully synchronized with GPS device time.

NONE - the system time was set to automatically synchronize with GPS/internet. However, it was unable to synchronize with the time source. It may indicates the time source connection is not available or time source is not ready such as GPS is off.

NA - the system time was set to manually update, thus synchronization status is not available.

INT|GPS|NONE|NA

INTernet

System Time Zone

This command sets and queries the system time zone. The time zone parameter is in string format of "(UTC+/-offset) Area/Location" as returned from the :SYSTem:TIME:ZONE:CATalog command. Changing the system time zone affects the system date/time.

<string>

(UTC-08:00) America/Los_Angeles

System Time Zone Catalog

This command queries the available system time zone catalog. The query returns comma delimited description for time zone sorted by UTC offset. Each item is in the format of "(UTC+/-offset) Area/Location" where Area/Location is defined in the tz database

System Unit Name

This command sets/queries the unit name of the current system.The name of the unit must not be greater than 45 ASCII characters

<string>

Self Test

Perform a self-test and return the results. The response is formatted as a JSON (http://json.org/) array of name,value pair result objects. Some result objects also include a 'status' property that will be either 'pass' or 'fail' based on whether the criteria for that test was met.

For tests of voltages, the test passes if the measured voltage is within 10% of the expected voltage.