Newport ESP300 Series, Руководство пользователя

Страница: 45 / 314

3.2.2 IEEE-488 Interface
HARDWARE CONFIGURATION
A typical IEEE-488 setup consists of a controller (host terminal) and
several devices connected to the bus. All devices are connected in
parallel to the data lines, data management and synchronization lines.
As a result of this type of connection, each device on the bus must
have a unique address so that the controller can selectively
communicate with it.
The address can be set through the optional front panel display or with
the
SA (set address) command.
( Note: that the factory default is address 1)
COMMUNICATION PROTOCOL
The IEEE-488 interface is implemented on the motion controller
somewhat differently from a typical instrument because the standard
IEEE-488.2 command set and command format are inadequate for a
complex motion control. Since the ESP controller has its own
language and command set, the IEEE-488 interface is used only as a
communication port. The extended protocol is not supported.
The ESP controller has an ASCII command set and also outputs
system status in ASCII format. It features a command input buffer. If
the buffer fills up, the ESP will not allow further communication until
memory becomes available to accept new characters.
To send a command to the ESP controller, use the command specific
to your IEEE-488 terminal [e.g., output (ASCII)].
If the host terminal asks the controller for a response [e.g., input
(ASCII)] and no response is obtained, the controller will eventually
will time-out.
USE OF SRQ LINE
The ESP controller can be instructed to generate an IEEE-488 service
request (SRQ) upon processing the
RQ command. This allows the user
to generate SRQs anywhere within the ESP command stream thereby
facilitating efficient event synchronization capability with the host
computer.
The following example illustrates the use of the
RQ command:
Section 3 – Remote Mode 3-5