Table of Contents
Advertisement
Syntax
Diagrams
Syntax
Overview
HP 16528/1653B
Programming Reference
The syntax diagrams in this appendix are similar to the syntax diagrams in
the IEEE 488.2 specification. Commands and queries are sent to the
instrument as a sequence of data bytes. The allowable byte sequence for
each functional element is defined by the syntax diagram that is shown
with the element description.
The allowable byte sequence can be determined by following a path in the
syntax diagram. The proper path through the syntax diagram is any path
that follows the direction of the arrows. If there is a path around an
element, that element is optional. If there is a path from right to left
around one or more elements, that element or those elements may be
repeated as many times as desired.
This overview is intended to give a quick glance at the syntax defined by
IEEE 488.2. It should allow you to understand many of the things about
the syntax you need to know. This appendix also contains the details of
the IEEE 488.2 defined syntax.
IEEE 488.2 defines the blocks used to build messages which are sent to
the instrument. A whole string of commands can therefore be broken up
into individual components.
Figure A-l shows a breakdown of an example c program message > .
There are a few key items to notice:
1. A semicolon separates commands from one another. Each
The < program message unit > s are separated by a semicolon.
2. A < program message > is terminated by a < NL > (new line). T h e
recognition of the < program message terminator > , or < PMT > ,
by the parser serves as a signal for the parser to begin execution of
commands. The < PMT > also affects command tree traversal (see
the Programming and Documentation Conventions chapter).
3. Multiple data parameters are separated by a comma.,
Message Communication and System Functions
A-5
Advertisement
Table of Contents
