Operator Manual Firmware Ver.3.05 and higher Instruction Manual

BOP-1K-GL 022814 3-41
is defined by the way your programming language indicates the end of a line (“newline” charac-
ter). Sending a character with EOL line asserted is another way of sending a message termina-
tor. The message unit is a keyword consisting of a single command or query word followed by a
message terminator (e.g., CURR?<newline> or TRIG<end-of-line>). The message unit may
include a data parameter after the keyword separated by a space; the parameter is usually
numeric (e.g., CURR 5<newline>), but may also be a string (e.g., OUTP ON<newline>). Figure
3-10 illustrates the message structure, showing how message units are combined. The follow-
ing subparagraphs explain each component of the message structure.
NOTE: An alternative to using the message structure for multiple messages defined in the fol-
lowing paragraphs is to send each command as a separate line. In this case each com-
mand must use the full syntax shown in Appendix B.
3.7.4.1 KEYWORD
Keywords are instructions recognized by a decoder within the BOP, referred to as a “parser.”
Each keyword describes a command function; all keywords used by the BOP are listed in Figure
3-9.
Each keyword has a long form and a short form. For the long form the word is spelled out com-
pletely (e.g. STATUS, OUTPUT, VOLTAGE, and TRIGGER are long form keywords). For the
short form only the first three or four letters of the long form are used (e.g., STAT, VOLT, OUTP,
and TRIG). The rules governing short form keywords are presented in Table 3-11.
You must use the rules above when using keywords. Using an arbitrary short form such as
ENABL for ENAB (ENABLE) or IMME for IMM (IMMEDIATE) will result in an error. Regardless
of which form chosen, you must include all the letters required by that form.
To identify the short form and long form in this manual, keywords are written in upper case let-
ters to represent the short form, followed by lower case letters indicating the long form (e.g.,
IMMediate, EVENt, and OUTPut). The parser, however, is not sensitive to case (e.g., outp,
OutP, OUTPUt, ouTPut, or OUTp are all valid).
3.7.4.2 KEYWORD SEPARATOR
If a command has two or more keywords, adjacent keywords must be separated by a colon (:)
which acts as the keyword separator (e.g., CURR:LEV:TRIG). The colon can also act as a root
specifier (paragraph 3.7.4.7).
3.7.4.3 QUERY INDICATOR
The question mark (?) following a keyword is a query indicator. This changes the command into
a query. If there is more than one keyword in the command, the query indicator follows the last
keyword. (e.g., VOLT? and MEAS:CURR?).
TABLE 3-11. RULES GOVERNING SHORTFORM KEYWORDS
IF NUMBER OF LETTERS IN
LONGFORM KEYWORD IS:
AND FOURTH LETTER
IS A VOWEL?
THEN SHORT FORM
CONSISTS OF:
EXAMPLES
4 OR FEWER (DOES NOT MATTER) ALL LONG FORM LETTERS MODE
5 OR MORE
NO
THE FIRST FOUR
LONG FORM LETTERS
MEASure, OUTPut, EVENt
YES
THE FIRST THREE
LONG FORM LETTERS
LEVel, IMMediate, ERRor