The MMEMory system provides mass storage capabilities for the analyzer.
Internal and external mass storage
The mass storage of the analyzer may be internal or external. The internal mass storage device can be any section of the internal hard disk (mapped to drive C:\). The external mass storage device can be a USB memory stick connected to one of the USB ports (mapped to any free drive letter) or a network connection.
The <file_name> and <directory_name> parameters are strings. Some commands use a fixed directory; for others the <file_name> can contain the complete path including the drive name and all subdirectories, e.g. 'C:\TEMP\TRASH\test.txt' for the file named test.txt in the TEMP\TRASH subdirectory of the internal hard disk drive C:\. If no complete path is specified, the file location is relative to the current directory (queried with MMEMory:CDIRectory?). The file name itself may contain the period as a separator for extensions.
File and directory names can be chosen according to Windows™ conventions; the restrictions placed on file names known from DOS systems do not apply. All letters and numbers are allowed, as well as the special characters "_", "^", "$", "~", "!", "#", "%", "&", "-", "{", "}", "(", ")", "@" and "`". Reserved file names are CON, AUX, COM1, ..., COM4, LPT1, ..., LPT3, NUL and PRN.
The use of wildcards ? and * is not allowed.
Command tree: MMEMory
:AKAL
:FACTory
:USER
:LOAD
:VNETworks<Ch>
:BALanced
:GLOop
:SENDed
:STORe
Converts the factory calibration data of the standards in the active calibration unit (SYSTem:COMMunicate:RDEVice:AKAL:ADDRess) to Touchstone format and copies it to the specified directory.
'<directory_name>' |
String parameter to specify the directory. |
*RST value |
–
|
SCPI, Command Types |
Device-specific, command or query (returns the current directory).
|
Example: |
|
Converts an arbitrary (e.g. user-defined) set of calibration data of the standards in the active calibration unit (SYSTem:COMMunicate:RDEVice:AKAL:ADDRess) to Touchstone format and copies it to the specified directory.
'<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):
|
SCPI, Command Types |
Device-specific, command or query (returns the current directory).
|
Example: |
MMEM:AKAL:USER:CONV 'C:\AKAL\Touchstone', 'user.calkit'
|
Returns the contents of the current or of a specified directory.
Use MMEMory:CATalog:ALL? to query the contents of the current directory and all subdirectories.
'<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: 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: |
|
Returns the contents of the current or of a specified directory and all subdirectories.
Use MMEMory:CATalog? to query the contents of the current directory.
'<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: 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: |
|
Changes the default directory for mass memory storage.
'<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: |
|
Copies an existing file to a new file.
'<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: |
|
Loads <data> into the file <file_name>.
'<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: |
|
Removes a file from the specified directory.
'<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: |
|
Deletes a system error correction data set stored in the cal pool (cal group file).
'<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
|
*RST value |
–
|
SCPI, Command Types |
Device-specific, no query.
|
Example: |
|
Loads cal kit data from a specified NWA cal kit file.
'<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: |
|
Loads cal kit data for a specific connector type, cal kit, and calibration standard from a specified Touchstone file, assigning a label for the cal data. A restriction on the port assignment may be defined in addition.
'<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: |
|
Connector and cal kit naming conventions
Connector and calibration kit names must be entered as string parameters. The strings contain the connector and cal kit names used in the Calibration Kits dialog; a Ω in the name must be replaced by 'Ohm', e.g.:
'NewKit1' denotes the user-defined calibration kit NewKit1.
'N 50 Ohm Ideal Kit' denotes the N 50 Ω Dummy Kit.
'ZV-Z21 typical' denotes the cal kit ZV-Z21 typical.
Specifies the Directory for Additionally Available Cal Kits and Conn Types. All cal kit files in the special directory will be (re-)loaded automatically as predefined kits (i.e. read-only kits which cannot be modified) every time the NWA application is started.
'<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: |
|
Loads a color scheme from a specified NWA color scheme file.
'<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: |
Color the first trace red, the second trace green.
|
Applies a system error correction data set stored in the cal pool (cal group file) to channel no. <Ch>.
<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
|
*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: |
|
Merges (activates) several cal group files for channel no. <channel> so that the query :SENSe1<Ch>:CORRection:COLLect:METHod:DEFine? returns a list of all merged calibration types (equivalent to the Calibration Pool list in the Calibration Manager dialog). The merged cal group files can be stored to a common file; see 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.
|
*RST value |
–
|
SCPI, Command Types |
Device-specific, no query.
|
Example: |
Store both sets of calibration data to a common cal group file.
|
Resolves the pool link between channel <Ch> and a correction data set (cal group file). After resolving the pool link, the analyzer keeps the previous system error correction as a channel calibration (Channel Cal). A new calibration will replace the channel calibration but not overwrite the old cal group file (and not affect other channels).
<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
|
*RST value |
–
|
SCPI, Command Types |
Device-specific, no query.
|
Example: |
|
Loads trace data from a specified power meter correction file or trace file and assigns it to a trace with a specified name. Traces are created using the CALCulate<Ch>:PARameter:SDEFine... command.
'<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: |
|
Loads a limit line definition from a specified file and assigns it to a trace with a specified name. Limit lines are created using the CALCulate<Chn>:LIMit... commands.
Limit lines can be loaded from Touchstone files (*.s<n>p, where <n> denotes the number of ports). The optional parameters '<param_name>', <x_offset>, <y_offset>, <type> are only relevant for Touchstone files. For *.limit files, no optional parameters can be set.
'<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 |
*RST value |
LMAX (if all optional parameters are omitted)
|
SCPI, Command Types |
Device-specific, no query.
|
Example: |
Show the limit line in the diagram.
|
Loads the known delay values of a calibration mixer, to be used as a reference for a mixer delay measurement calibration, and enables variable or constant delay mode. Mixer delay measurements are controlled using the SENSe<Ch>:FREQuency:MDELay... commands.
<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: |
|
Loads correction data for a mixer delay measurement calibration from a specified file and assigns it to a channel with a specified number. Mixer delay measurements are controlled using the SENSe<Ch>:FREQuency:MDELay... commands.
Use MMEMory:LOAD:MDAData to load delay values of a calibration mixer stored in a file.
<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: |
SENS1:FREQ:MDEL:ACQ
|
Loads a pulse train definition from a specified file and assigns it to a channel with a specified number. Pulse train definitions are created using the SENSe<Ch>:PULSe:GENerator<Gen>... commands.
<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: |
|
Loads a ripple limit definition from a specified file and assigns it to a trace with a specified name. Ripple limits are created using the CALCulate<Chn>:RIPPle... commands.
'<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: |
Show the ripple limit line for the active trace in the diagram.
|
Loads a sweep segment definition from a specified file and assigns it to a specified channel. Sweep segments are defined using the [SENSe<Ch>:]SEGMent<Seg>... commands.
<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: |
|
Loads configuration data from a specified setup file and sets the analyzer to the corresponding instrument state.
<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: |
|
Loads trace data from a specified trace file and assigns it to a trace with a specified name. Traces are created using the CALCulate<Ch>:PARameter:SDEFine... command.
'<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: |
Create four traces to measure the two-port S-parameters S11, S12, S21, S22. The traces are not displayed.
|
Loads data from a specified Touchstone file defining a balanced port circuit model for deembedding. Select a balanced port circuit model involving file import before using the command.
<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: 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: |
Define a balanced port configuration.
|
Loads data from a specified Touchstone file defining a balanced port circuit model for embedding. Select a balanced port circuit model involving file import before using the command.
<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: 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: |
Define a balanced port configuration.
|
Loads data from a specified one-port (*.s1p) Touchstone file defining a ground loop circuit model for deembedding. Select the ground loop circuit model involving file import (FIMPort) before using the command.
<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: |
|
Loads data from a specified one-port (*.s1p) Touchstone file defining a ground loop circuit model for embedding. Select the ground loop circuit model involving file import (FIMPort) before using the command.
<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: |
|
Loads data from a specified Touchstone file defining a port pair circuit model for deembedding. Select a port pair with a circuit model involving file import before using the command.
<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: 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: |
Define a port pair configuration with two port pairs (<List_idx> = 1 or 2).
|
Loads data from a specified Touchstone file defining a balanced port circuit model for embedding. Select a port pair with a circuit model involving file import before using the command.
<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: 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: |
Define a port pair configuration with two port pairs (<List_idx> = 1 or 2).
|
Loads data from a specified two-port (*.s2p) Touchstone file defining a single ended circuit model for deembedding. Select the single ended port circuit model involving file import (FIMPort)before using the command.
<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: |
|
Loads data from a specified two-port (*.s2p) Touchstone file defining a single ended circuit model for embedding. Select the single end. Select the single ended port circuit model involving file import (FIMPort)before using the command.
<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: |
|
Creates a new subdirectory for mass memory storage in an existing directory.
'<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: |
|
Moves a file to the indicated directory and stores it under the file name specified, if any. If <file_destination> contains no path indication, the command renames the file without moving it.
'<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: |
|
Defines a name for a file which can be used to store the printer output. The file is created when it is selected as a printer destination (HCOPy:DESTination 'MMEM').
'<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: |
|
Removes an existing directory from the mass memory storage system.
'<directory_name>' |
String parameter to specify the directory. |
*RST value |
–
|
SCPI, Command Types |
Device-specific, no query.
|
Example: |
|
Stores the data of a calibration kit to a specified file.
'<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: |
|
Stores a color scheme to a specified NWA color scheme file.
'<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: |
|
Copies the correction data of channel <Ch> to the
cal pool, generating a new correction data file (cal group). The file
has the extension *.cal and is stored in the C:\Rohde&Schwarz\
NWA\Calibration\Data directory.
<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
|
*RST value |
–
|
SCPI, Command Types |
Device-specific, no query.
|
Example: |
|
Saves the current power loss list to a specified power meter correction list file.
'<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: |
|
Saves the limit lines associated to a specified trace to a limit line file. Limit lines are created using the CALCulte<Chn>:LIMit... commands.
'<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: |
|
Saves the values of all markers to a ASCII file.
'<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: |
|
Stores the correction data for a mixer delay measurement calibration to a specified file. Mixer delay measurements are controlled using the SENSe<Ch>:FREQuency:MDELay... commands.
<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: |
|
Saves a pulse train definition associated with a specified channel to a pulse train file. Pulse train definitions are created using the SENSe<Ch>:PULSe:GENerator<Gen>... commands.
<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: |
|
Saves the ripple limits associated with a specified trace to a ripple limit file. Ripple limit definitions are created using the CALCulte<Chn>:RIPPle... commands.
'<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: |
|
Saves the sweep segment definition of a specified channel to a sweep segment file. Sweep segments are defined using the [SENSe<Ch>:]SEGMent<Seg>... commands.
<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: |
|
Stores the configuration data of the current setup to a specified setup file.
MMEMory:STORe:STATe
renames the current setup, appending a .zvx extension. See example for
MMEMory:LOAD:STATe.
<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: |
|
Stores the trace data of a specified data trace to a trace file. Traces are created using the CALCulte<Ch>:PARameter:SDEFine... command.
*.s<n>p Touchstone files (<n> = 1, 2, 3, ...) are intended for a complete set of <n>-port S-parameters. Data export fails if the active channel does not contain the full set of <n>2 traces. If the necessary traces are available, '<trc_name>' can be the name of any of the traces. To create Touchstone files while less than <n>2 single-ended traces are available, use MMEMory:STORe:TRACe:PORTs.
'<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 If the first optional parameter is omitted the command stores unformatted data. COMPlex –
Complex values (real and imaginary part) If the second optional parameter is omitted the command stores complex data. POINt –
Decimal separator: point If the third optional parameter is omitted, points are used. SEMicolon –
Field separator: semicolon 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: |
|
Stores the trace data of all data traces in the specified channel to a trace file. Traces are created using the CALCulte<Ch>:PARameter:SDEFine... command.
*.s<n>p Touchstone files (<n> = 1, 2, 3, ...) are intended for a complete set of <n>-port S-parameters. Data export fails if the active channel does not contain the full set of <n>2 traces.
<channel no.> | ALL |
Channel number 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
|
Optional parameters |
UNFormatted –
Unformatted data export specified by the second optional parameter If the first optional parameter is omitted the command stores unformatted data. COMPlex –
Complex values (real and imaginary part) If the second optional parameter is omitted the command stores complex data. POINt –
Decimal separator: point If the third optional parameter is omitted, points are used. SEMicolon –
Field separator: semicolon 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: |
Reset the instrument, creating a default channel no 1 and a default trace 'Trc1'.
Create four traces to measure the two-port S-parameters S11, S12, S21, S22. The traces are not displayed.
|
Generates a Touchstone file for the specified ports. The Touchstone file (.s<n>p where <n> is the number of ports) contains a full set of <n>2 single-ended S-parameters for the selected ports. Traces are created using the CALCulte<Ch>:PARameter:SDEFine... command. The command fails unless the following conditions are met:
For a one-port Touchstone file, the reflection coefficient for the specified port (e.g. S11 for port no. 1) must be measured. If a full one-port system error correction is available for the specified port, it is also possible to export transmission parameters that are related to the calibrated port (e.g. S12 or S21 for port no. 1).
For a multiport Touchstone file, a full multiport system error correction must be available. It is not necessary to measure the full set of S-parameters. Moreover, if the port configuration contains balanced ports, the Touchstone file will contain the converted single-ended S-parameters.
<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) <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: |
Suppose that a full four-port calibration for ports 1 to 4 and channel 1 has been performed, and that a DUT with two balanced ports is connected. The analyzer measures an arbitrary mixed mode S-parameter. MMEM:STOR:TRAC:PORT 1, 'Test.s4p', COMPlex, 1,2,3,4 Calculate all single-ended S-parameters and store them to a four-port Touchstone file.
|