Table of Contents
Advertisement
Data types and formats
The SCPI language defines different data formats for use in program messages
and response messages. Instruments are flexible listeners and can accept
commands and parameters in various formats. However, SCPI-equipped
instruments are precise talkers. This means that SCPI-equipped instruments
always respond to a particular query in a predefined, rigid format.
Numeric
Parameters that accepts all commonly used decimal representations of
numbers including optional signs, and decimal points, scientific notations
(3e2 = 3 × 10
notations (M, k, m, μ, n) Special values for numeric parameters such as AUTO,
MIN, MAX, and DEF are also accepted. If only specific numeric values are
accepted, the instrument will automatically round the input numeric
parameters. As an example, the following command requires a numeric
parameter for the amplitude value:
[SOURce:]VOLTage[:LEVel][:IMMediate][:AMPLitude] <value>
Discrete
Parameters (used in program settings) that have a limited number of values
such as IMMediate and BUS. Some of these parameters have a short form and
a long form just like command keywords. You can mix upper-case and
lower-case letters. Query responses will always return the abbreviated form in
all upper-case letters. As an example, the following command require a
discrete parameter for the trigger source.
TRIGger:SOURce {IMMediate|BUS}
Boolean
Parameters that represent a single binary condition that is either true or false.
For a false condition, the U3606B will accept OFF or 0. For a true condition,
the U3606B will accept ON or 1. When you query a boolean setting, the U3606B
will always return 0 or 1. As an example, the following command require a
boolean parameter for the instrument output state:
OUTPut[:STATe] {0|OFF|1|ON}
U3606B Programmer's Reference
2
, 5.43e–3 = 5.43 × 10
SCPI Conventions and Data Formats
–3
6
, or 10e6 = 10 × 10
Introduction to SCPI
), and engineering
1
9
Advertisement
Table of Contents
