'<directory_name>'

String parameter to specify the directory.

*RST value

–

SCPI, Command Types

Device-specific, command or query (returns the current directory).

Example:

'<directory_name>'

String parameter to specify the directory.

*RST value

–

'<file_name>'

Name and (possibly) directory of the cal kit file to be used for the automatic calibration (optional string parameter):

• If the parameter is omitted, the analyzer uses the last characterized cal kit file.

• If an empty string (' ') is specified, the factory cal kit file stored in the active calibration unit (SYSTem:COMMunicate:RDEVice:AKAL:ADDRess) is used. By default this file is also used in manual control.

• A NWA cal kit file name *.calkit without path denotes a specific cal kit file stored in the active calibration unit.

• A NWA cal kit file name *.calkit with path denotes a specific cal kit file stored in an arbitrary directory.

SCPI, Command Types

Device-specific, command or query (returns the current directory).

Example:

'<directory_name>'

String parameter to specify the directory. If the directory is omitted, the command queries the contents of the current directory, to be queried  with MMEMory:CDIRectory?

Response

Directory information in the following format:

<used_size>,<free_disk_space> {,<file_name>,,<file_size>}
 

The first two numeric parameters denote the total amount of storage currently used in the directory and the total amount of storage available, both expressed in bytes. All files are returned with their file name and their size in bytes.

*RST value

–

SCPI, Command Types

Confirmed, query only.

Example:

'<directory_name>'

String parameter to specify the directory. If the directory is omitted, the command queries the contents of the current directory, to be queried  with MMEMory:CDIRectory?

Response

Directory information in the following format:

Directory of <Dir_name>, <used_size>, <free_disk_space> {, <Subdir>, <DIR>,}{,<file_name>,,<file_size>},
Directory of <Subdir_name_1>, <used_size>,<free_disk_space> {, <Subdir>, <DIR>,}{,<file_name>,,<file_size>},
Directory of <Subdir_name_2>, <used_size>,<free_disk_space> ...
 

The first line is omitted if the current directory contains no subdirectories. The following lines are analogous to the output of MMEMory:CATalog?.

*RST value

–

SCPI, Command Types

Confirmed, query only.

Example:

'<directory_name>'

String parameter to specify the directory. If DEFault is used, the analyzer selects the default directory 'C:\Rohde&Schwarz\Nwa'.

*RST value

– (A *RST does not change the current directory)

SCPI, Command Types

Confirmed, command or query (without parameter, returns the current directory).

Example:

'<file_source>', '<file_destination>'

String parameters to specify the name of the file to be copied and the name of the new file.

*RST value

–

SCPI, Command Types

Confirmed, no query.

Example:

'<file_name>'

String parameter to specify the name of the file.

<data>

Data in 488.2 block data format. The delimiter EOI must be selected to achieve correct data transfer.

*RST value

–

SCPI, Command Types

Confirmed, with query. The query form is MMEMory:DATA? <file_name> with the response being the associated <data> in block format.

Example:

'<file_name>'

String parameter to specify the name and directory of the file to be removed.  If the path is omitted, the current directory is used (see MMEMory:CDIRectory).

*RST value

–

SCPI, Command Types

Confirmed, no query.  

Example:

'<file_name>'

String parameter to specify the name of the cal group file to be deleted. Cal group files must have the extension *.cal. The directory path must not be specified; the analyzer always uses the default cal pool directory C:\Rohde&Schwarz\NWA\Calibration\Data.

*RST value

–

SCPI, Command Types

Device-specific, no query.  

Example:

'<file_name>'

String parameter to specify the name and directory of the cal kit file to be loaded. If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?.  

Note: The loaded file must be a NWA-specific cal kit file with the extension *.calkit. ZVR cal kit files can be imported using the [SENSe<Ch>:]CORRection:CKIT:INSTall command. Agilent cal kit files can be imported manually and converted into *.calkit files.  

*RST value

–

SCPI, Command Types

Device-specific, no query.  

Example:

'<conn_name>'

String parameters containing the name of the connector type.

'<ckit_name>'

String parameters containing the name of a calibration kit available on the analyzer.

Parameters

Standard type; for a description refer to the table of standard types.

'<stdlabel_name>'

String parameter defining a label for the cal kit data. An empty string means that no label is defined.

'<file_name>'

String parameter to specify the name and directory of the Touchstone file to be loaded. A *.s1p file must be used for one-port standards, a *.s2p file for two-port standards. If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?.  

<port1_no>, <port2_no>

Port assignment: One port number for one-port standards, two port number for two-port standards. If the port numbers are omitted, the cal kit data is valid for all ports.

*RST value

–

SCPI, Command Types

Device-specific, no query.  

Example:

'<directory>'

String parameter to specify the directory path. The directory can be created separately (MMEMory:MDIRectory). An empty string means that no cal kit files will be loaded.  

*RST value

–

SCPI, Command Types

Device-specific, no query.  

Example:

'<file_name>'

String parameter to specify the name and directory of the cal kit file to be loaded. The default extension (manual control) for color scheme files is *.ColorScheme, although other extensions are allowed.

*RST value

–

SCPI, Command Types

Device-specific, no query.  

Example:

<channel> | ALL

Channel number of an existing channel. ALL applies the selected data set to all channels.

<file_name>

String parameter to specify the name of the cal group file to be loaded. Cal group files must have the extension *.cal. The directory path must not be specified; the analyzer always uses the default cal pool directory C:\Rohde&Schwarz\NWA\Calibration\Data.

*RST value

–

SCPI, Command Types

Device-specific, command or query. The query form returns the cal group file assigned to the specified channel (empty string if no cal group file is assigned).

Example:

<channel>

Channel number of an existing channel.  

'<file1>.cal', '<file2>.cal', ...

String parameters with the names of the merged cal group files. Cal group files must have the extension *.cal. The file extensions must be specified as part of the string parameters.
In contrast the directory path must not be specified; the analyzer always uses the default path C:\Rohde&Schwarz\NWA\Calibration\Data.

*RST value

–

SCPI, Command Types

Device-specific, no query.  

Example:

<channel> | ALL

Channel number of an existing channel. ALL resolves the pool link for all channels.

'<file_name>'

Optional string parameter to specify the name of the cal group file. Cal group files must have the extension *.cal. The directory must not be specified; the analyzer always uses the default path C:\Rohde&Schwarz\NWA\Calibration\Data.
If there is no link between <Ch> and the specified file, the command has no effect. If no file is specified, the command resolves any link between <Ch> and an arbitrary cal group file.  

*RST value

–

SCPI, Command Types

Device-specific, no query.  

Example:

'<file name>'

String parameter to specify the name and directory of the trace file to be loaded. The analyzer supports power meter correction list files (*.pmcl, to be generated using MMEMory:LOAD:CORRection:TCOefficient), *csv, and Touchstone (*.s<n>p) files. If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?.

The file extensions *.s<n>p, *.csv, and *.pmcl for Touchstone, ASCII, and power meter correction list files are mandatory.

'<parameter name/trace name>'

Optional string parameter: For imported Touchstone files for more than one port (*.s2p, *.s3p, *.s4p), the parameter denotes the imported S-parameter ('S11', 'S12', ...). For ASCII (*.csv) files, the parameter references a trace name in the file (case sensitive). If the parameter is omitted, the first trace in the specified file is imported.

The parameter is not used for power meter correction list files (*.pmcl).

*RST value

–

SCPI, Command Types

Confirmed, no query.  

Example:

'<trc_name>'

Name of an existing trace in the active setup (string parameter). The imported limit line is assigned to this trace, irrespective of the trace information in the limit line file.

*RST value

–

'<file_name>'

String parameter to specify the name and directory of the limit line file to be loaded. The default extension (manual control) for limit line files is *.limit, although other extensions are allowed. If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?. See also note on Touchstone files above.

*RST value

–

'<param_name>'

String parameter, selects an S-parameter from a Touchstone file. The parameter must be compatible with the file type (e.g. for one-port Touchstone files *.s1p, only the parameter name 'S11' is allowed).

*RST value

'S11' (if all optional parameters are omitted)

<x_offset>

Stimulus offset for limit lines loaded from a Touchstone file. A 1 GHz offset shifts the limit line by 1 GHz in (positive) horizontal direction.   

Range [def. unit]

Depending on the sweep range of the analyzer. [The default units for frequency, power and time sweeps are Hz, dB and s, respectively.]  

*RST value

0

<y_offset>

Response offset for limit lines loaded from a Touchstone file. A 1 dB offset shifts the limit line by 1 dB in (positive) vertical direction.  

Range [def. unit]

Depending on the measured quantity. [dB]

*RST value

0

<type>

Limit line type :

LMAX – upper limit line
LMIN – lower limit line
OFF – limit line off

*RST value

LMAX (if all optional parameters are omitted)

SCPI, Command Types

Device-specific, no query.  

Example:

<Channel>

Channel number

*RST value

–

'<file_name>'

String parameter to specify the name and directory of the loaded file. The default extension (manual control) for files containing known delays is *.csv, although other extensions are allowed. If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?. If a file name is specified, the analyzer activates variable delay mode.

CDELay

Use the constant delay values defined via SENSE<Ch>:FREQuency:MDELay:CDELay

*RST value

–

SCPI, Command Types

Device-specific, no query.  

Example:

<Channel>

Channel number

*RST value

–

'<file_name>'

String parameter to specify the name and directory of the calibration file to be loaded. The default extension (manual control) for mixer delay calibration files is *.mcal, although other extensions are allowed. If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?.

*RST value

–

SCPI, Command Types

Device-specific, no query.  

Example:

<Channel>

Channel number

*RST value

–

<Generator>

Generator number. In the present firmware version, this number is always 1.

*RST value

1

'<file_name>'

String parameter to specify the name and directory of the pulse train file to be loaded. The default extension (manual control) for pulse train files is *.train, although other extensions are allowed. If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?.

*RST value

–

SCPI, Command Types

Device-specific, no query.  

Example:

'<trc_name>'

Name of an existing trace in the active setup (string parameter). The imported ripple limit line is assigned to this trace, irrespective of the trace information in the ripple limit file.

*RST value

–

'<file_name>'

String parameter to specify the name and directory of the ripple limit file to be loaded. The default extension (manual control) for ripple limit files is *.ripple, although other extensions are allowed. If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?.

*RST value

–

SCPI, Command Types

Device-specific, no query.  

Example:

<Ch>

Channel number.

'<file_name>'

String parameter to specify the name and directory of the sweep segment file to be loaded. The default extension (manual control) for sweep segment files is *.seglist, although other extensions are allowed. If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?.

*RST value

–

SCPI, Command Types

Device-specific, no query.  

Example:

<numeric_value>

1 (the <numeric_value> is used for compatibility with the SCPI standard but is ignored).

<file_name>

String parameter to specify the name and directory of the setup file to be loaded. The default extension (manual control) for setup files is *.zvx, although other extensions are allowed. If no path is specified the analyzer searches the directory 'C:\RohdeSchwarz\Nwa\RecallSets'.

*RST value

–

SCPI, Command Types

Confirmed, no query.  

Example:

'<trc name>'

Name of an existing data trace in the active setup (string parameter). The trace data is loaded into a memory trace associated with the specified data trace. If one or more memory traces are already associated with the specified data trace, the last generated memory trace is overwritten.

'<file name>'

String parameter to specify the name and directory of the trace file to be loaded. Several file formats for trace files are supported. If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?.

The file extensions *.s<n>p, *.csv, and *.dat for Touchstone, ASCII, and Matlab files are mandatory.

'<parameter name/trace name>'

Optional string parameter: For imported Touchstone files for more than one port (*.s2p, *.s3p, *.s4p), the parameter denotes the imported S-parameter ('S11', 'S12', ...). For ASCII (*.csv) and Matlab (*dat) files, the parameter references a trace name in the file (case sensitive). If the parameter is omitted, the first trace in the specified file is imported.

*RST value

–

SCPI, Command Types

Confirmed, no query.  

Example:

<Ch>

Channel number

<Log_pt>

Logical port number

'<file_name>'

String parameter to specify the name and directory of the loaded Touchstone file. The balanced port circuit models STSL | STSC | SLST | SCST require two 2-port (*.s2p) files, to be assigned to the different ports PMAin and PSECondary; the FIMPort model requires a single 4-port (*.s4p) file but no additional port assignment.  

If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?.

Parameters

Port assignment for two 2-port (*.s2p) files:
PMAin – Port 1
PSECondary – Port 2

The ports must be specified for the import of 2-port (*.s2p) files; they must be omitted for 4-port (*.s4p) files.

[IPORts]

Interchange port numbers of loaded *.s2p file. If the parameter is omitted, the port numbers are not interchanged. The parameter must not be used for 4-port files.  

*RST value

–

SCPI, Command Types

Device-specific, no query.  

Example:

<Ch>

Channel number

<Log_pt>

Logical port number

'<file_name>'

String parameter to specify the name and directory of the loaded Touchstone file. The balanced port circuit models STSL | STSC | SLST | SCST require two 2-port (*.s2p) files, to be assigned to the different ports PMAin and PSECondary; the FIMPort model requires a single 4-port (*.s4p) file but no additional port assignment.  

If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?.

Parameters

Port assignment for two 2-port (*.s2p) files:
PMAin – Port 1
PSECondary – Port 2

The ports must be specified for the import of 2-port (*.s2p) files; they must be omitted for 4-port (*.s4p) files.

[IPORts]

Interchange port numbers of loaded *.s2p file. If the parameter is omitted, the port numbers are not interchanged. The parameter must not be used for 4-port files.  

*RST value

–

SCPI, Command Types

Device-specific, no query.  

Example:

<Ch>

Channel number.

'<file_name>'

String parameter to specify the name and directory of the loaded Touchstone file. If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?.

*RST value

–

SCPI, Command Types

Device-specific, no query.  

Example:

<Ch>

Channel number.

'<file_name>'

String parameter to specify the name and directory of the loaded Touchstone file. If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?.

*RST value

–

SCPI, Command Types

Device-specific, no query.  

Example:

<Ch>

Channel number

<List_idx>

Current number of a port pair in the list, defined via CALCulate<Ch>:TRANsform:VNETworks:PPAir:DEEMbedding<List_idx>:DEFine

'<file_name>'

String parameter to specify the name and directory of the loaded Touchstone file. The port pair circuit models STSL | STSC | SLST | SCST require two 2-port (*.s2p) files, to be assigned to the different ports PMAin and PSECondary; the FIMPort model requires a single 4-port (*.s4p) file but no additional port assignment.  

If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?.

Parameters

Port assignment for two 2-port (*.s2p) files:
PMAin – Port 1
PSECondary – Port 2

The ports must be specified for the import of 2-port (*.s2p) files; they must be omitted for 4-port (*.s4p) files.

[IPORts]

Interchange port numbers of loaded *.s2p file. If the parameter is omitted, the port numbers are not interchanged. The parameter must not be used for 4-port files.  

*RST value

–

SCPI, Command Types

Device-specific, no query.  

Example:

<Ch>

Channel number

<List_idx>

Current number of a port pair in the list, defined via CALCulate<Ch>:TRANsform:VNETworks:PPAir:EMBedding<List_idx>:DEFine

'<file_name>'

String parameter to specify the name and directory of the loaded Touchstone file. The balanced port circuit models STSL | STSC | SLST | SCST require two 2-port (*.s2p) files, to be assigned to the different ports PMAin and PSECondary; the FIMPort model requires a single 4-port (*.s4p) file but no additional port assignment.  

If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?.

Parameters

Port assignment for two 2-port (*.s2p) files:
PMAin – Port 1
PSECondary – Port 2

The ports must be specified for the import of 2-port (*.s2p) files; they must be omitted for 4-port (*.s4p) files.

[IPORts]

Interchange port numbers of loaded *.s2p file. If the parameter is omitted, the port numbers are not interchanged. The parameter must not be used for 4-port files.  

*RST value

–

SCPI, Command Types

Device-specific, no query.  

Example:

<Ch>

Channel number.

<Ph_pt>

Physical port number

'<file_name>'

String parameter to specify the name and directory of the loaded Touchstone file. If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?.

*RST value

–

[IPORts]

Interchange port numbers of loaded *.s2p file. If the parameter is omitted, the port numbers are not interchanged.

SCPI, Command Types

Device-specific, no query.  

Example:

<Ch>

Channel number.

<Ph_pt>

Physical port number

'<file_name>'

String parameter to specify the name and directory of the loaded Touchstone file. If no path is specified the analyzer searches the current directory, to be queried with MMEMory:CDIRectory?.

*RST value

–

[IPORts]

Interchange port numbers of loaded *.s2p file. If the parameter is omitted, the port numbers are not interchanged.

SCPI, Command Types

Device-specific, no query.  

Example:

'<directory_name>'

String parameter to specify the new directory. Either the full path or a subdirectory for the current directory (see MMEMory:CDIRectory).

*RST value

–

SCPI, Command Types

Device-specific, no query.

Example:

'<file_source>', '<file_destination>'

String parameters to specify the name and the path of the file to be copied and the name and the path of the new file.  

*RST value

–

SCPI, Command Types

Confirmed, no query.

Example:

'<file_name>'

String parameter to specify the file name. The supported file formats are *.wmf, *.ewmf, *.bmp, *.png; see command HCOPy:DEVice:LANGuage. The specified directory must exist, otherwise no file can be generated. If no path is specified the analyzer uses the current directory, to be queried with MMEMory:CDIRectory?.

*RST value

'Hardcopy'

SCPI, Command Types

Device-specific, with query.

Example:

'<directory_name>'

String parameter to specify the directory.

*RST value

–

SCPI, Command Types

Device-specific, no query.

Example:

'<kit_name>'

Name of a user-defined calibration kit available on the analyzer.

It is not possible to modify or store predefined or ideal kits.

'<file_name>'

String parameter to specify the name and directory of the cal kit file to be created. The file is a NWA-specific cal kit file with the extension *.calkit. If no path is specified the analyzer uses the current directory, to be queried with MMEMory:CDIRectory?.

*RST value

–

SCPI, Command Types

Device-specific, no query.  

Example:

'<file_name>'

String parameter to specify the name and directory of the color scheme file to be created. If no path is specified the analyzer uses the current directory, to be queried with MMEMory:CDIRectory?. The default extension (manual control) for color scheme files is *.ColorScheme, although other extensions are allowed.

*RST value

–

SCPI, Command Types

Device-specific, no query.  

Example:

<Ch>

Channel number

'<file_name>'

String parameter to specify the name of the created cal group file. There is no need to specify the directory path and file extension; the analyzer uses the default cal pool directory C:\Rohde&Schwarz\NWA\Calibration\Data and a *.cal extension.

*RST value

–

SCPI, Command Types

Device-specific, no query.  

Example:

'<file name>'

String parameter to specify the name and directory of the created power meter correction list file. The file extension *.pmcl is mandatory. If no path is specified the analyzer uses the current directory, to be queried with MMEMory:CDIRectory?.

*RST value

–

SCPI, Command Types

Confirmed, no query.  

Example:

'<trc_name>'

Name of an existing trace in the active setup (string parameter) for which a limit line definition exists.

'<file_name>'

String parameter to specify the name and directory of the created limit line file. The default extension (manual control) for limit line files is *.limit, although other extensions are allowed. If no path is specified the analyzer uses the current directory, to be queried with MMEMory:CDIRectory?.

*RST value

–

SCPI, Command Types

Device-specific, no query.  

Example:

'<file_name>'

String parameter to specify the name and directory of the created ASCII file. The default extension (manual control) for marker files is *.txt, although other extensions are allowed. If no path is specified the analyzer uses the current directory, to be queried with MMEMory:CDIRectory?. An example for the file contents is given below.

*RST value

–

SCPI, Command Types

Device-specific, no query.  

Example:

<Channel>

Channel number. This parameter is ignored; the data is assigned to a channel when the file is re-loaded.  

*RST value

–

'<file_name>'

String parameter to specify the name and directory of the created calibration file. The default extension (manual control) for mixer delay calibration files is *.mcal, although other extensions are allowed. If no path is specified the analyzer uses the current directory, to be queried with MMEMory:CDIRectory?.

*RST value

–

SCPI, Command Types

Device-specific, no query.  

Example:

<Channel>

Channel number. This parameter is ignored; the data is assigned to a channel when the file is re-loaded.

*RST value

–

<Generator>

Generator number. In the present firmware version, this number is always 1.

*RST value

1

'<file_name>'

String parameter to specify the name and directory of the created pulse train file. The default extension (manual control) for pulse train files is *.train, although other extensions are allowed. If no path is specified the analyzer uses the current directory, to be queried with MMEMory:CDIRectory?.

*RST value

–

SCPI, Command Types

Device-specific, no query.  

Example:

'<trc_name>'

Name of an existing trace in the active setup (string parameter) for which a ripple limit definition exists.

'<file_name>'

String parameter to specify the name and directory of the created ripple limit file. The default extension (manual control) for ripple limit files is *.ripple, although other extensions are allowed. If no path is specified the analyzer uses the current directory, to be queried with MMEMory:CDIRectory?.

*RST value

–

SCPI, Command Types

Device-specific, no query.  

Example:

<Ch>

Channel number.

'<file_name>'

String parameter to specify the name and directory of the created sweep segment file. The default extension (manual control) for sweep segment files is *.seglist, although other extensions are allowed. If no path is specified the analyzer uses the current directory, to be queried with MMEMory:CDIRectory?.

*RST value

–

SCPI, Command Types

Device-specific, no query.  

Example:

<numeric_value>

1 (the <numeric_value> is used for compatibility with the SCPI standard but is ignored).

'<file_name>'

String parameter to specify the name and directory of the created setup file. The default extension (manual control) for setup files is *.zvx, although other extensions are allowed. If no path is specified the analyzer uses the current directory, to be queried with MMEMory:CDIRectory?.

*RST value

–

SCPI, Command Types

Confirmed, no query.  

Example:

'<trc_name>'

Name of an existing data trace in the active setup (string parameter).

'<file_name>'

String parameter to specify the name and directory of the created trace file. Several file formats for trace files are supported. The file extensions *.s<n>p, *.csv, and *.dat for Touchstone, ASCII, and Matlab files are mandatory.

To generate a multiport Touchstone file *.s2p, *.s3p..., the channel must contain traces for the full set of S-parameters; the '<trc_name>' is ignored.  

If no path is specified the analyzer uses the directory 'C:\RohdeSchwarz\Nwa\RecallSets'.

Optional parameters

UNFormatted – Unformatted data export specified by the second optional parameter
FORMatted – Formatted data export (for *.csv and *.dat files only)

If the first optional parameter is omitted the command stores unformatted data.

COMPlex – Complex values (real and imaginary part)
LINPhase – Linear magnitude and phase
LOGPhase – dB-magnitude and phase

If the second optional parameter is omitted the command stores complex data.

POINt – Decimal separator: point  
COMMa – Decimal separator: comma  

If the third optional parameter is omitted, points are used.

SEMicolon – Field separator: semicolon
COMMa – Field separator: comma  
TABulator – Field separator: tabulator  
SPACe – Field separator: space

If the fourth optional parameter is omitted, semicolons are used.

*RST value

– (the default export format is UNFormatted)

SCPI, Command Types

Confirmed, no query.  

Example:

<channel no.> | ALL

Channel number in the active setup.
ALL – A separate file is created for each channel in the active setup.

'<file_name>'

String parameter to specify the name and directory of the created trace file. Several file formats for trace files are supported. The file extensions *.s<n>p, *.csv, and *.dat for Touchstone, ASCII, and Matlab files are mandatory.

To generate a multiport Touchstone file *.s2p, *.s3p..., the channel must contain traces for the full set of S-parameters; the '<trc_name>' is ignored.  

If no path is specified the analyzer uses the C:\Rohde&Schwarz\NWA\Traces directory.

Optional parameters

UNFormatted – Unformatted data export specified by the second optional parameter
FORMatted – Formatted data export (for *.csv and *.dat files only)

If the first optional parameter is omitted the command stores unformatted data.

COMPlex – Complex values (real and imaginary part)
LINPhase – Linear magnitude and phase
LOGPhase – dB-magnitude and phase

If the second optional parameter is omitted the command stores complex data.

POINt – Decimal separator: point  
COMMa – Decimal separator: comma  

If the third optional parameter is omitted, points are used.

SEMicolon – Field separator: semicolon
COMMa – Field separator: comma  
TABulator – Field separator: tabulator  
SPACe – Field separator: space

If the third optional parameter is omitted, semicolons are used.

*RST value

– (the default export format is UNFormatted)

SCPI, Command Types

Confirmed, no query.  

Example:

<channel no.>

Channel number in the active setup.

'<file_name>'

String parameter to specify the name and directory of the created Touchstone file. The file extension *.s<n>p for a n-port Touchstone file is mandatory.

If no path is specified the analyzer uses the current directory, to be queried with MMEMory:CDIRectory?.

Other parameters

COMPlex – Complex values (real and imaginary part)
LINPhase – Linear magnitude and phase
LOGPhase – dB-magnitude and phase

<Port 1>, <Port 2>... – First, second... port number
.

*RST value

– (the default export format in manual control is COMPlex)

SCPI, Command Types

Device-specific, no query.  

Example: