beautypg.com

Ieee 488.2 common command format, Scpi command keywords, Scpi keyword separator – Quantum Composers 9730 Series User Manual

Page 33: Scpi optional keywords, Ieee 488.2 common command format -33, Scpi command keywords -33, Scpi keyword separator -33, Scpi optional keywords -33

background image

10-33

could use the behavior to know when to stop reading from the unit. However, if the
“echo” parameter is enabled, there will be two sets of line terminators, one following the
echoed command string, and the one f

ollowing the pulse generator’s response.


Note: The pulse generator will echo commands on the DB9 serial port only.

The pulse generator responds to every communication string. If the communication
string is a query, the unit responds with the queried response (or error code) followed by
the line terminators. If the communication string is a parameter change, the response is
“ok” (or error code) followed by the line terminators. For this reason, it is not
recommended that multiple commands be stacked together into single strings as is
common with some other types of instruments. It is recommended that the coded
application send a single command in a string and follow immediately by reading the
response from the unit. Repeat this sequence for multiple commands.

IEEE 488.2 Common Command Format

The IEEE 488.2 Common Commands control and manage generic system functions
such as reset, configuration storage and identification. Common commands always
begin with the asterisk (*) character and may include parameters. The parameters are
separated from the command pneumonic by a space character. For example:

*RCL 1

*IDN?

SCPI Command Keywords

SCPI commands control and set instrument specific functions such as setting the
pulsewidth, delay and period. SCPI commands have a hierarchical structure compose
of functional elements that include a header or keywords separated with a colon, data
parameters and terminators. For example:

SCPI Keyword Separator

A colon (:) must always separate one keyword from the next lower-level keyword. A
space must be used to separate the keyword header from the first parameter. If more
than one parameter is used, you must separate subsequent parameters with a comma.

SCPI Optional Keywords

Optional keywords and/or parameters appear in square brackets ([]) in the command
syntax. Note that the brackets are not part of the command and should not be sent to
the pulse generator. When sending a second level keyword without the optional
keyword, the pulse generator assumes that you intend to use the optional keyword and
responds as if it had been sent.