GPIB Interface
6-1
www.adlinktech.com
ADLINK’s PCI-3488 works with your applications in
both ways. Its GPIB-32.DLL, provides the binary
compatibility with the world's most popular NI-488.2*
GPIB commands. The PCI-3488 also provides VISA
library support that can be used with most common
instrument drivers written by instrument vendors.
Regardless if you are using VC++, VB, Delphi,
LabVIEW*, or any other T&M ADE, PCI-3488 is the
most cost-effective GPIB solution compatible with all
your applications.
• Microsoft VC++/VB
• NI LabVIEW*
• NI LabWindows/CVI*
• Agilent TestExec
• Direct invocation
to GPIB driver API
functions
ADE
VISA
Driver API
(GPIB-32.DLL)
GPIB Cards
• Native driver API
to provide IEEE-
488 functions
• Using existing
instrument drivers
via VISA in ADE
• ADLINK PCI-3488
/LPCI-3488
• ADLINK PXI-3488
• Agilent 82350B
• NI PCI-GPIB*
• ...
Product names mentioned herein are used for
identification purposes only and may be trademarks and/or
registered trademarks of their respective companies.
*NI, LabVIEW, and LabWindows/CVI are trademarks or
registered trademarks of National Instruments Corporation
or its subsidiaries in the United States and other countries.
Ordering Information
PCI-3488
High-Performance IEEE488 GPIB Interface
card for PCI bus
LPCI-3488
High-Performance IEEE488 GPIB Interface
card for low-profile PCI bus, shipped with an
additional low-profile bracket.
PXI-3488
High-Performance IEEE488 GPIB Interface
card for PXI/CompactPCI bus
ACL-IEEE488-1
IEEE 488 standard cable, 1 meter length
ACL-IEEE488-2
IEEE 488 standard cable, 2 meter length
ACL-IEEE488-4
IEEE 488 standard cable, 4 meter length
ACL-IEEE488-8
IEEE 488 standard cable, 8 meter length
Specifications
GPIB Bus Specification
Up to 14 instruments connected
Maximal 1.5 MB/s data transfer rate
Cable length
• 2 meters between each instrument (suggested)
• 20 meters total cable length
Data transfer mode: 8 bits parallel
Handshake: 3 wire handshake, reception of each
data byte is acknowledged
Certificate
EMC/EMI: CE, FCC Class A
Programming Interface
VB/VC++/BCB/Delphi
LabVIEW™*
LabWindows/CVI*
General Specification
I/O connector : IEEE 488 standard 24-pin
Operating temperature : 0 to 55˚C
Storage temperature : -20 to 80˚C
Relative humidity : 5 to 95%, non-condensing
Power Consumption
Dimension :
• PCI-3488:
134 mm x 107 mm (not including connectors)
• LPCI-3488:
120 mm x 64.5 mm (not including connectors)
• PXI-3488:
160 mm x 100 mm (not including connectors)
Fully Compatible with Your
Existing Applications
ADLINK’s GPIB interface cards come with complete
software support, including a driver API that is fully
binary compatible with NI-488.2* driver software. All
programs written for the interface cards is based on
GPIB-32.DLL and can be executed on the PCI-
3488/LPCI-3488/PXI-3488 without any modification.
The interface cards also support the VISA library in
order to ensure compatibility with applications
utilizing VISA. ADLINK’s GPIB interface cards are all
“Plug and Play” compatible, thus can work with all
your existing applications.
How ADLINK’s GPIB Interface
Cards Work?
The objective of a test and measurement
application is to test a specific Unit Under Test
(UUT) automatically. A typical automatic testing
system includes various testing programs and
testing equipment connected to the host computer
via a GPIB interface. To manage the connections
with GPIB instruments, testing programs are
usually developed according to the following
model:
Application Development Environments (ADEs) is
an the environment where applications are written.
These are popular because users can implement
any function needed using textual programming
(ex. VC++/VB, TestExec) or graphical programming
(ex. LabVIEW*) techniques. A vital part of a test
and measurement application is to control and
communicate with GPIB instruments. Two
techniques are generally used to control the GPIB
interface: invoking native driver API or using
existing instrument drivers via VISA.
A native driver API is provided by most GPIB
interface vendors and is usually in the form of ANSI
C functions. For users who need more
comprehensive control over GPIB instruments,
using a driver API with SCPI string commands is a
better choice. For others who want to keep away
from complicated instrument commands,
instrument drivers developed for specific ADEs (ex.
LabVIEW*/TestExec) can significantly simplify the
complexity of instrument control. Most instrument
drivers use a VISA library to control the GPIB
interface and to communicate with instruments.
VISA support is essential in those cases.
ADLINK’s GPIB interface cards work with your
applications in two ways. Its GPIB-32.DLL provides
binary compatibility with the popular NI-488.2* driver
software. The PCI-3488/LPCI-3488/PXI-3488 also
provides VISA library support that can be used most
common instrument drivers written by instrument
vendors. Regardless if you are using VC++, VB,
Delphi, LabVIEW*, or any other T&M ADE,
ADLINK’s GPIB interface cards are the most cost-
effective GPIB solution compatible with all your
applications.
Power consumption
+5 V
400 mA (typical)
750 mA (maximum)
+3.3 V
400 mA (typical)
750 mA (maximum)