SYSTem: COMMunicate Commands

SYSTem:COMMunicate:

  ECAL:CAT

GPIB

    | ADDRess

LAN:HOSTname

PSENsor

TCPip:CONTrol?

USB:PMETer:CAT?

(Read-only) Returns the ID string of ECals that are connected to the VNA USB. Use the list to select a Ecal for Ecal calibration.

Parameters

Examples

SYST:COMM:ECAL:CAT?

system:communicate:ecal:catalog?

Return Type

Comma-delimited strings.

Default

Not applicable

(Read-only) Returns the LAN hostname that is visible in the Help, About Network Analyzer dialog box. Learn more. This is the same information that is visible on the LXI compliance dialog.

Parameters

None

Example

SYST:CONF:LAN:HOSTname?

Return Type

String

Default

Not applicable

This command replaces SYST:COMM:GPIB:PMET:ADDR.

(Read-Write) Specifies the type and location of the power meter to be used in a source power calibration.

Parameters

<char>

Type of power meter/ sensor. Choose from:

• GPIB  GPIB power meter

• USB  USB power sensor or USB power sensor

• LAN  LAN enabled power meter

• ANY  Any VISA resource string or a visa alias

<string>

For GPIB, address of the power meter. Choose any integer between 0 and 30.

For USB, the ID string of the power meter or power sensor. Use SYST:COMM:USB:PMET:CAT? to see a list of ID strings of connected power meters and sensors.

For LAN, the hostname or IP address of the power meter.

For ANY,  any VISA resource string or a visa alias.

Examples

SYST:COMM:PSEN gpib, "14"

system:communicate:psensor usb, "Agilent Technologies,U2000A,MY12345678"

syst:comm:psen lan, "mymeter.agilent.com"

syst:comm:psen any, "TCPIP0::mymeter.agilent.com::5025::SOCKET"

Query Syntax

SYSTem:COMMunicate:PSENsor?

Return Type

Character / String

Default

GPIB

(Read-only) Returns the ID string of power meters / sensors that are connected to the VNA USB. Use the list to select a power sensor for a source power cal.

These meter/sensor ID strings can NOT be used as the resource string for configuring a USB-based PMAR (SYST:CONF:EDEV:IOConfig).

Parameters

Examples

SYST:COMM:USB:PMET:CAT?

system:communicate:usb:pmeter:catalog?

Return Type

Comma-delimited strings. Two power sensor strings are separate by a semicolon.

Default

Not applicable

(Read-only) Queries the TCP/IP port number to use for opening a TCP/IP socket control connection to the VNA.  The control connection is used for two purposes:

1. To perform a Device Clear operation on the VNA

2. To detect when a Service Request (SRQ) event occurs on the VNA.

The port number can range from 5000 to 5099. The VNA will skip over 5025 as it is being used for the primary socket connection.

To detect an SRQ, your program sends the appropriate commands via the regular socket connection to set up for a SRQ event to occur the same sequence of commands as if you were sending them via GPIB.  You write your program so that while your program is doing SCPI transactions on the standard socket connection, a second thread of execution in your program detects the SRQ on the control connection and responds to the event.  When the SRQ event occurs, the VNA sends a SRQ +xxx/n message on the control connection (where /n is linefeed character, ASCII value 10 decimal).  The xxx value in the SRQ +xxx/n string is the IEEE 488.2 status byte at the time the SRQ was generated.  So listening for that on the control connection is how your program detects the event.  If for your socket communication youre using a software API that provides for asynchronous communication via a callback mechanism (for example, if youre using Microsofts winsock API, or their .NET Socket class as in the example program below), in that case your listener execution thread is created implicitly for you so your program doesnt have to create one explicitly.

Note: If this SCPI query is sent to the VNA via a SCPI parser other than a TCP/IP socket connection (for example, if sent via GPIB), the query is not applicable in that case and will return value of 0.

Parameters

None

Example

See example program

Return Type

Integer

Default

Not applicable