Most commands require a parameter to be specified. The parameters must be separated from the header by a "white space". Permissible parameters are numerical values, Boolean parameters, text, character strings and block data. The type of parameter required for the respective command and the permissible range of values are specified in the command description.
| Numerical values | Numerical values can be entered in any form, i.e. with sign, decimal point and exponent. Values exceeding the resolution of the instrument are rounded up or down. The mantissa may comprise up to 255 characters, the values must be in the value range -9.9E37 to 9.9E37. The exponent is introduced by an "E" or "e". Entry of the exponent alone is not allowed. In the case of physical quantities, the unit can be entered. Permissible unit prefixes are G (giga), MA (mega), MOHM and MHZ are also permissible), K (kilo), M (milli), U (micro) and N (nano). If the unit is missing, the fundamental unit is used. | |
| Example: | ||
SENS:SPEC:FREQ:STOP
1.5GHz is equivalent to
|
||
| Special numerical values | The texts MINimum, MAXimum, DEFault, UP and DOWN are interpreted
as special numerical values.
In the case of a query, the associated numerical value is provided. |
|
| Example: | ||
Setting command: CONF:POW:CONT:REP MAXimum, NONE, NONE |
||
Query: CONF:POW:CONT:REP?
Response: |
||
|
| ||
| MIN/MAX | MINimum and MAXimum denote the minimum and maximum value. | |
|
| ||
| DEF | DEFault denotes the preset value. This value is set by the *RST command. | |
|
| ||
| INF/NINF | INFinity, Negative INFinity (NINF) represent the numerical values -9.9E37 or 9.9E37, respectively. INF and NINF are only sent as device responses. | |
|
| ||
| NAN | Not a Number (NAN) represents the value 9.91E37. NAN is only sent as device response. This value is not defined. Possible causes are division by zero, subtraction or addition of infinite and the representation of missing values. | |
|
| ||
| Boolean Parameters | Boolean parameters represent two states. The ON state (logically true) is represented by ON or a numerical value different from 0. The OFF state (logically untrue) is represented by OFF or the numerical value 0. A query responds with 0 or 1. | |
| Example: | ||
Setting command: SOURce:DM:CLOCk:STATe ON |
||
Query: SOURce:DM:CLOCk:STATe?
Response: 1 |
||
| Text | Text parameters observe the syntax rules for key words, i.e. they can be entered using a short or long form. Like any parameter, they have to be separated from the header by a white space. In the case of a query, the short form of the text is provided. | |
| Example: | ||
Setting command: TRIGger:SOURce EXTern |
||
Query: TRIGger:SOURce?
Response: |
||
| Strings | Strings must always be entered within quotation marks (' or "). | |
| Example: | ||
:SYST:REM:ADDR:SEC
1,"GSM900MS_NSig" or |
||
|
||
| Block data | Block data are a transmission format which is suitable for the transmission of large amounts of data. A command using a block data parameter with definite length has the following structure: | |
| Example: | ||
:HEADer:HEADer #45168xxxxxxxx |
||
| The hash symbol # introduces the data block. The next number
indicates how many of the following digits describe the length of the
data block. In the example the 4 following digits indicate the length
to be 5168 bytes. The data bytes follow. During the transmission of these
data bytes all End or other control signs are ignored until all bytes
are transmitted.
A #0 combination introduces a data block of indefinite length. The use of the indefinite format requires a NL^END message to terminate the data block. This format is useful when the length of the transmission is not known or if speed or other considerations prevent segmentation of the data into blocks of definite length. |
||