Prologix GPIB-USB Controller Bedienungsanleitung
PROLOGIX
GPIB-USB CONTROLLER
USER MANUAL
VERSION 6.102
April 18, 2011
PROLOGIX.BIZ
Prologix GPIB-USB ontroller User Manual
4/19/2011 2
Table of Contents
1. Introduction..........................................................................................................................4
2. Installation.............................................................................................................................4
3. Firmware Upgrade ...............................................................................................................4
4. Host Software.......................................................................................................................4
5. onfiguration........................................................................................................................5
6. Operating Modes..................................................................................................................5
6.1. ontroller Mode..........................................................................................................5
6.2. Device Mode................................................................................................................6
7. Data Transmission ...............................................................................................................6
7.1. Binary Data Transmission..........................................................................................7
8. ommands ............................................................................................................................8
8.1. addr................................................................................................................................8
8.2. auto................................................................................................................................8
8.3. clr...................................................................................................................................9
8.4. eoi ..................................................................................................................................9
8.5. eos................................................................................................................................10
8.6. eot_enable ..................................................................................................................10
8.7. eot_char ......................................................................................................................11
8.8. ifc.................................................................................................................................11
8.9. loc ................................................................................................................................11
8.10. lon................................................................................................................................11
8.11. mode ...........................................................................................................................12
8.12. read..............................................................................................................................12
8.13. read_tmo_ms .............................................................................................................12
8.14. rst.................................................................................................................................13
8.15. savecfg.........................................................................................................................13
8.16. spoll .............................................................................................................................13
8.17. srq ................................................................................................................................14
8.18. status ...........................................................................................................................14
8.19. trg.................................................................................................................................15
8.20. ver................................................................................................................................15
8.21. help..............................................................................................................................15
9. Specifications ......................................................................................................................15
Prologix GPIB-USB ontroller User Manual
4/19/2011 3
Change Log
April 18, 2011 Added ++lon command description.
Sept 14, 2009 Added ++savecfg command descripion. orrected maximum value
of read_tmo_ms to 3000 ms.
April 21, 2009 Added ++status command description. Updated ++addr, ++spoll
and ++trg command descriptions to include secondary address.
Added section on binary data transmission.
Mar 1, 2008 Updated ++trg command description.
Dec 22, 2007 Updated USB command terminator description and read_tmo_ms
command description.
Jul 9, 2007 Fixed typo in ++mode command description. Thanks Mike Schulz!
Jul 7, 2007 Added change log.
Renamed PERIPHERAL mode as DEVI E mode in line with
other GPIB literature.
Jul 5, 2007 Initial version.
Prologix GPIB-USB ontroller User Manual
4/19/2011 4
1. Int oduction
Prologix GPIB-USB controller converts any computer with a USB port into a GPIB
ontroller or Device.
In ontroller mode, Prologix GPIB-USB controller can remotely control GPIB enabled
instruments such as Oscilloscopes, Logic Analyzers, and Spectrum Analyzers.
In Device mode, Prologix GPIB-USB controller converts the computer into a GPIB
peripheral for downloading data and screen plots from the instrument front panel.
In both modes, Prologix GPIB-USB controller interprets high level commands received
from the host computer and performs the appropriate low-level GPIB protocol
handshaking.
2. Installation
Prologix GPIB-USB controller can be installed using these easy steps:
1. Download drivers for FT245R chip from FTDI website (www.ftdichip.com)
2. onnect Prologix GPIB-USB controller to a computer using USB A-B cable
3. Install drivers according to instructions in
www.ftdichip.com/Documents/InstallGuides.htm
4. Plug controller directly, or using a GPIB cable, to the GPIB connector on the
instrument
Two kinds of drivers are available: Virtual OM Port (V P) driver and Direct (D2XX)
driver. The V P driver emulates a standard serial port on the host computer such that
the Prologix GPIB-USB computer can be communicated with as a standard serial (RS-
232) device. D2XX driver allows direct access to the controller via a DLL interface.
3. Fi mwa e Upg ade
Prologix GPIB-USB controller firmware is field upgradeable. Latest firmware and
upgrade installations are available at prologix.biz
4. Host Softwa e
A wide variety of host software may be used to communicate with Prologix GPIB-USB
controller:
Te minal p og ams – any terminal emulation program such as HyperTerminal, Tera
Term Pro, or Minicom can be used to communicate with the controller and instruments
connected to it.
Prologix GPIB-USB ontroller User Manual
4/19/2011 5
Custom applications – any programming language or environment that provides access
to serial ports (if using V P driver) or allows interfacing to DLL (if using D2XX driver)
may be used to develop custom applications. Graphical programming environments like
National Instruments LabView and Agilent VEE may be used as well.
EZGPIB – an easy to use, programming environment developed by Ulrich Bangert for
developing data acquisition applications. Web link to this tool can be found at
prologix.biz.
Plotte emulato s – plotter emulation applications such as 7470.exe, Print apture and
Plottergeist can be used to render screen plots downloaded using Prologix GPIB-USB
controller. Details on how to configure these tools are available at prologix.biz.
5. Configu ation
Prologix GPIB-USB controller can be configured using any of the following methods:
P ologix.exe – Prologix.exe is an open source tool developed by John Miles for
configuring the controller. Web link to the tool can be found at prologix.biz.
Te minal p og am – any terminal emulation program such as HyperTerminal, Tera
Term Pro, or Minicom can be used to configure the controller by manually entering
appropriate commands (See ommands). Using the terminal program open the virtual
OM port created by the USB driver. Serial port parameters such as baud rate, data bits,
stop bits and flow control do not matter and may be set to any value. You may want to
enable the “Local Echo” feature in the terminal program to view the commands being
entered. Please consult the FAQ at prologix.biz, or the program’s user manual, for
detailed configuration steps for various terminal programs.
Prologix GPIB-USB ontroller stores the latest configuration settings in non-volatile
memory. These settings are not address specific. If you have multiple instruments on the
GPIB bus that require different configuration settings, you must change the settings
before communicating with each instrument.
6. Ope ating Modes
Prologix GPIB-USB controller can operate in two modes – ONTROLLER and
DEVI E. You can switch between the two modes using ++mode command (see
ommands).
6.1. Cont olle Mode
In ontroller mode, the GPIB-USB ontroller acts as the ontroller-In- harge ( I )
on the GPIB bus. When the controller receives a command over the USB port
terminated by the USB terminator – R (AS II 13) or LF (AS II 10) – it addresses the
Prologix GPIB-USB ontroller User Manual
4/19/2011 6
GPIB instrument at the currently specified address (See ++addr command) to listen, and
passes along the received data.
When Read-After-Write feature is enabled (See ++auto command) Prologix GPIB-USB
ontroller will addresses the instrument to talk after sending a command, in order to
read its response. All data received from instruments over GPIB is sent to host over
USB. Read-After-Write feature simplifies communication with instruments. You send
commands and read responses without consideration for low level GPIB protocol
details.
When Read-After-Write feature is not enabled Prologix GPIB-USB controller does not
automatically address the instrument to talk. You must use the ++read command to read
data.
ontroller mode is used to remotely control instruments and to download screen plots
by sending plot commands from a host computer.
6.2. Device Mode
In Device mode, Prologix GPIB-USB ontroller acts as another peripheral on the GPIB
bus. In this mode, the controller can act as a GPIB TALKER or GPIB LISTENER
only. Since Prologix GPIB-USB ontroller is not the ontroller-In- harge while in this
mode, it expects to receive commands from a GPIB controller. When Device mode is
enabled Prologix GPIB-USB controller configures itself as a GPIB Listener. All data
received by the controller over the GPIB port is passed along to the USB port without
buffering.
All data received from the host over USB is buffered until the GPIB controller addresses
Prologix GPIB-USB controller to talk, at which time the buffered data is passed along to
the GPIB port. The controller can buffer only one command. A subsequent command
received over USB will overwrite the previously buffered one, if the previous one has
not yet been transmitted over GPIB.
Device mode is used to download screen plots from the instrument front panel for
rendering using plotter emulation software.
7. Data T ansmission
In ontroller and Device modes, characters received over USB port are aggregated in an
internal buffer and interpreted when a USB termination character – R (AS II 13) or
LF (AS II 10) – is received. If R, LF, ES (AS II 27), or ‘+’ (AS II 43) characters are
part of USB data they must be escaped by preceding them with an ES character. All
un-escaped LF, R and ES and ‘+’ characters in USB data are discarded.
Prologix GPIB-USB ontroller User Manual
4/19/2011 7
As mentioned earlier, an un-escaped R or LF acts as the USB terminator. The
terminating R or LF is removed and GPIB termination characters (specified by ++eos
command) are appended before transmitting data to instruments.
Any USB input that starts with the unescaped “++” character sequence is interpreted as
a controller command and not transmitted over GPIB.
When configured to do so – using the ++auto command or the ++read command –
characters received from instruments are transmitted to host. Unlike while sending data
to instruments, no character substitution is performed. The firmware buffers only one
character. The FTDI USB driver provides additional buffering of about 4KB. If a device
is talking and the buffers (firmware’s and driver’s) are full, the device continues to be in
TALK mode but is stopped from further sending data using GPIB handshaking.
The ++eot_char command may be used to detect GPIB EOI signal assertion.
7.1. Bina y Data T ansmission
Prologix GPIB-USB controller can send and receive binary data to and from GPIB
enabled instruments.
No special action is necessary to receive binary data from instruments. Any binary data
received from the instrument is transmitted over USB to P unmodified, just as with
AS II data. Since binary data from instruments is not usually terminated by R or LF
characters (as is usually the case with AS II data), you may want to use the
++eot_enable command to detect EOI indicating end of data. See ++eot_enable
command help for more details.
Special care must be taken when sending binary data to instruments. If any of the
following characters occur in the binary data -- R (AS II 13), LF (AS II 10), ES
(AS II 27), ‘+’ (AS II 43) – they must be escaped by preceding them with an ES
character.
For example, to send the following (decimal) binary data:
00 01 02 13 03 10 04 27 05 43 06
it must be escaped as follows:
00 01 02 27 13 03 27 10 04 27 27 05 27 43 06
Further more, most instruments will get confused if GPIB termination characters, such
as R or LF, are appended to binary data. Use ++eos 3 command to disable such
behavior. See ++eos command help for more details.
Prologix GPIB-USB ontroller User Manual
4/19/2011 8
8. Commands
Prologix GPIB-USB controller provides several commands to configure its behavior.
They are explained in detail in the following sections. All commands start with the “++”
character sequence.
ommands must be terminated with R or LF.
8.1. add
The addr command is used to configure, or query the GPIB address. Meaning of the
GPIB address depends on the operating mode of the controller. In ONTROLLER
mode, it refers to the GPIB address of the instrument being controlled. In DEVI E
mode, it is the address of the GPIB peripheral that Prologix GPIB-USB controller is
emulating.
An optional secondary address may also be specified. Secondary address must be
separated from the primary address by a space character. Valid secondary address values
are 96 to 126 (decimal). Secondary address value of 96 corresponds to secondary GPIB
address of 0, 97 corresponds to 1, and so on. Specifying secondary address has no effect
in DEVI E mode.
If the command is issued with no parameters, the currently configured address (primary,
and secondary, if specified) is returned.
SYNTAX: ++addr [<PAD> [<SAD>]]
PAD (Primary Address) is a decimal value between 0 and 30.
SAD (Secondary Address) is a decimal value between 96 and 126. SAD is optional.
MODES AVAILABLE: ONTROLLER, DEVI E
EXAMPLES:
++addr 5 – Set primary address to 5
++addr – Query current address
++addr 9 96 – Set primary address to 9 and secondary address to 0
NOTE:
Default GPIB address of many HP-GL/2 plotters is 5.
8.2. auto
Prologix GPIB-USB controller can be configured to automatically address instruments
to talk after sending them a command in order to read their response. The feature called,
Prologix GPIB-USB ontroller User Manual
4/19/2011 9
Read-After-Write, saves the user from having to issue read commands repeatedly. This
command enabled or disabled the Read-After-Write feature.
In addition, auto command also addresses the instrument at the currently specified
address to TALK or LISTEN. ++auto 0 addresses the instrument to LISTEN and
++auto 1 addresses the instrument to TALK.
If the command is issued without any arguments it returns the current state of the read-
after-write feature.
SYNTAX: ++auto [0|1]
MODES AVAILABLE: ONTROLLER
NOTE:
Some instruments generate “Query Unterminated” or “-420” error if they are addressed
to talk after sending a command that does not generate a response (often called non-
query commands). In effect the instrument is saying, I have been asked to talk but I have
nothing to say. The error is often benign and may be ignored. Otherwise, use the
++read command to read the instrument response. For example:
++auto 0 — Turn off read-after-write and address instrument to listen
SET VOLT 1.0 — Non-query command
*idn? — Query command
++read eoi — Read until EOI asserted by instrument
"HP54201A" — Response from instrument
8.3. cl
This command sends the Selected Device lear (SD ) message to the currently specified
GPIB address. Please consult the programming manual for details on how a particular
instrument responds to this message.
SYNTAX: ++clr
MODES AVAILABLE: ONTROLLER
8.4. eoi
This command enables or disables the assertion of the EOI signal with the last character
of any command sent over GPIB port. Some instruments require EOI signal to be
asserted in order to properly detect the end of a command.
SYNTAX: ++eoi [0|1]
Prologix GPIB-USB ontroller User Manual
4/19/2011 10
MODES AVAILABLE: ONTROLLER, DEVI E
EXAMPLES:
++eoi 1 Enable EOI assertion with last character
++eoi 0 Disable EOI assertion
++eoi Query if EOI assertion is enabled or disabled
8.5. eos
This command specifies GPIB termination characters. When data from host is received
over USB, all non-escaped LF, R and ES characters are removed and GPIB
terminators, as specified by this command, are appended before sending the data to
instruments. This command does not affect data from instruments received over GPIB
port.
If the command is issued with no arguments then the current configuration is returned.
SYNTAX: ++eos [0|1|2|3] where: 0 – R+LF, 1 – R, 2 – LF, 3 – None
MODES AVAILABLE: ONTROLLER, DEVI E
EXAMPLES:
++eos 0 Append R+LF to instrument commands
++eos 1 Append R to instrument commands
++eos 2 Append LF to instrument commands
++eos 3 Do not append anything to instrument commands
++eos Query current EOS state
8.6. eot_enable
This command enables or disables the appending of a user specified character (see
eot_char) to USB output whenever EOI is detected while reading a character from the
GPIB port.
If the command is issued without any argument, the current state of eot_enable is
returned.
SYNTAX: eot_enable [0|1]
MODES AVAILABLE: ONTROLLER, DEVI E
EXAMPLES:
++eot_enable 1 Append user defined character when EOI detected
++eot_enable 0 Do not append character when EOI detected
++eot_enable Query current eot_enable state
Inhaltsverzeichnis
