# PCI-3488/LPCI-3488/PXI-3488

# High-Performance IEEE488 GPIB Interface

# Features

 Fully compatible with IEEE 488 standard
 Supports a 32-bit 3.3 V or 5 V PCI bus (PCI-3488 & LPCI-3488)
 PXI specification Rev. 2.2 compliant (PXI-3488)
 Up to 1.5 MB/s data transfer rates
 Onboard 1 KB FIFO for read/write operations
 Provides driver APIs compatible with NI-488.2\* driver software
 Supports industrial-standard VISA library
 Interactive utility for testing and diagnostics

 Operating Systems

• Windows Vista/XP/2000/2003

 Recommended Software

• VB/VC++/BCB/Delphi

·LabVIEWTM\*

·LabWindows/Cyl\*

![Close-up of a blue printed circuit board with various electronic components and connectors (no visible text or symbols)](.pci-3488-datasheet-19/61b12f873527fb109fbdcc863cd4b91b4699c3ab0abd73eb21df9fdf1aa2de45.jpg)

PCI-3488

![Close-up of a blue printed circuit board with various electronic components (no visible text or symbols)](.pci-3488-datasheet-19/9becc5b012d8c311b48631c7f58cb087244739978d9102e0093eb5ee8e95f6e2.jpg)

LPCI-3488

![Close-up of a blue printed circuit board with various components and connectors (no visible text or symbols)](.pci-3488-datasheet-19/6bc94ef67328f506d3ed614db0f4a938241a44a748b3a6ab745e8bc3d239f2df.jpg)

PXI-3488

# Introduction

The IEEE488 standard, also known as GPIB, is a bus interface that connects instruments with a computer to form an ATE system. GPIB was initially developed by Hewlett Packard and was recognized as an IEEE standard in 1978. The IEEE488.1-1978 standard defines the convention for electrical and mechanical bus characteristics, as well as the state diagram for each bus function. In 1987, another standard was derived from the original IEEE488.1- 1978 known as the IEEE488.2-1987. It was introduced to define data formats, common commands, and control protocols for instruments. In general, IEEE488.1 defines hardware specifications, and IEEE488.2 defines software specifications. The IEEE488 standard has been widely accepted by instrument vendors for the past few decades. Today, GPIB is still the most popular interface between computer and instruments.

ADLINK’s GPIB controller interface cards,are fully compatible with the IEEE488 instrumentation control and communication standard,and are capable of controlling up to 14 stand-alone instruments via IEEE488 cables. They are designed to meet high performance requirements and maximize programming portability. They are equipped with 1 KB onboard FIFO and a block transfer mode able to reach GPIB transfer rates up to 1.5 MB/s. With the Application Program Interfaces (APIs) that are compatible with NI-488.2\* driver software and VISA support, ADLINK’s GPIB controller interface cards provide the greatest compatibility with your existing applications and instrument drivers.

![Based on the provided image, here is an accurate and concise description of the flowchart:\n\n**Labeled Blocks (Top Row):**\n*   **Instrument A:** Labeled 'Instrument A / Able to Talk, / Listen and Control / ex: Computer' situated above a laptop icon.\n*   **Instrument B:** Labeled 'Instrument B / Able to Talk / and to Listen / ex: Oscilloscace' situated above an oscilloscope icon.\n*   **Instrument C:** Labeled 'Instrument C / Able to Listen / ex: Function / Generator' situated above a function generator icon.\n\n**Connections and Bus Lines:**\n*   **Instrument to Bus:** Vertical red lines extend downward from each instrument icon to the horizontal blue bus lines. Large pink arrows point upward from the bus lines to each instrument, indicating bidirectional communication.\n*   **Horizontal Bus Lines:** A series of parallel blue lines connect the three instruments horizontally across the diagram.\n\n**Signal Labels (Left Side):**\n*   **Top Group:** 'EOI', 'IFC', 'SRQ', 'ATN', 'REN'\n*   **Middle Group:** 'DAV', 'NRFD', 'NDAC'\n*   **Bottom Line:** 'DIO1-8'\n\n**Signal Categories (Right Side):**\n*   **Top Group:** '5ystem / Management / lines' (Note the number '5' instead of 'S')\n*   **Middle Group:** '3 handshake / lines'\n*   **Bottom Group:** '8 data lines'\n\n**Bottom Text:**\n*   'Handshake and data signals on the GPIB bus'](.pci-3488-datasheet-19/f6bf354a11542faf25fadd5641c1544b7937580638497157455ed0406e5757a0.jpg)

![The image displays two block diagrams illustrating different instrument connection topologies, labeled at the bottom as 'Linear instrument connection' and 'Star instrument connection'.\n\n**Left Diagram: Linear instrument connection**\nThis diagram shows a daisy-chain configuration.\n*   **Blocks:** A computer (desktop PC), three connector blocks (represented by groups of three vertical circles with colored dots), and three blue vertical rectangles labeled 'Instrument A', 'Instrument B', and 'Instrument C'.\n*   **Connections:**\n    *   A pink line connects the computer to the first connector block.\n    *   From the first connector block, a line connects to 'Instrument A'.\n    *   From 'Instrument A', a line connects to the second connector block.\n    *   From the second connector block, a line connects to 'Instrument B'.\n    *   From 'Instrument B', a line connects to the third connector block.\n    *   From the third connector block, a line connects to 'Instrument C'.\n\n**Right Diagram: Star instrument connection**\nThis diagram shows a star-like configuration branching out from a central point.\n*   **Blocks:** A computer (desktop PC), a central connector block (bottom left of the instrument cluster), three other connector blocks (one between Instrument A and B, one above Instrument C, one above Instrument D), and four blue vertical rectangles labeled 'Instrument A', 'Instrument B', 'Instrument C', and 'Instrument D'.\n*   **Connections:**\n    *   A pink line connects the computer to the central connector block.\n    *   From the central connector block, a direct line connects to 'Instrument A'.\n    *   From the central connector block, a line connects to the second connector block (located between Instrument A and B), which then connects to 'Instrument B'.\n    *   From the central connector block, a line goes upward and splits into two branches.\n    *   The left branch connects to a connector block (above Instrument C), which connects to 'Instrument C'.\n    *   The right branch connects to a connector block (above Instrument D), which connects to 'Instrument D'.](.pci-3488-datasheet-19/fdf932036d1d2466e7bf43bec29131a9ee95f695617a931e268c2ede6cd6b8ae.jpg)

ADLINK GPIB Data Xfer Rate (Small Block Data)
![| Block Size (Bytes) | Data Xer Rate (KB/s) |\n| ------------------ | -------------------- |\n| 0                  | 0                    |\n| 200                | 200                  |\n| 400                | 400                  |\n| 600                | 500                  |\n| 800                | 600                  |\n| 1000               | 650                  |](.pci-3488-datasheet-19/12895a05bafaec333fbbf5b40074d941be4ff6be9d596b94aed66d5b9a56565c.jpg)

ADLINK GPIB Data Xfer Rate (Large Block Data)
![| Block Size (KBytes) | Data Xfer Rate (KB/s) |\n| ------------------- | --------------------- |\n| 0                   | 0                     |\n| 15                  | 1200                  |\n| 30                  | 1400                  |\n| 45                  | 1450                  |\n| 60                  | 1480                  |\n| 75                  | 1500                  |\n| 90                  | 1520                  |\n| 105                 | 1530                  |\n| 120                 | 1540                  |\n| 135                 | 1550                  |\n| 150                 | 1560                  |](.pci-3488-datasheet-19/6aa9b5394f288359f363dba85ac4fd51ac7d585256d668ef13ccf168f344cb16.jpg)

# Performance

ADLINK’s expertise in the PCI and PXI field was elevated after completing our newest GPIB controller. The PCI-3488 and LPCI-3488 supports both 3.3 V and 5 V PCI buses and can be adapted to most industrial and desktop computers. The PXI-3488 is compliant with PXI specification Rev. 2.2 and can be installed on standard PXI and CompactPCI chassis.

A 1 KB onboard FIFO is placed between the GPIB bus and PCI controller to buffer GPIB read/write operations. The FIFO eliminates the gap between the slower GPIB bus (\~1.5 MB/s) and the faster PCI bus (132 MB/s), and dramatically increases overall system performance.

# 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:

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 costeffective GPIB solution compatible with all your applications.

![Based on the provided image, here is the description of the flowchart:\n\n**Labeled Blocks:**\n*   ADE\n*   VISA\n*   Driver API (GPIB-32.DLL)\n*   GPIB Cards\n\n**Connections:**\n*   A downward arrow connects **ADE** to **VISA**.\n*   A downward arrow connects **VISA** to **Driver API (GPIB-32.DLL)**.\n*   A downward arrow connects **Driver API (GPIB-32.DLL)** to **GPIB Cards**.\n*   A long downward arrow connects **ADE** directly to **Driver API (GPIB-32.DLL)**.](.pci-3488-datasheet-19/344966b73c74d5ef18a426ced781c91459dffc082f5e6a9dada4e3ee98aae0e0.jpg)

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.

# 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.

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.

# 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

<table><tr><td colspan="2">Power consumption</td></tr><tr><td>+5 V</td><td>+3.3 V</td></tr><tr><td>400 mA (typical)</td><td>400 mA (typical)</td></tr><tr><td>750 mA (maximum)</td><td>750 mA (maximum)</td></tr></table>

 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)

# 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

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.
[🔗 Link to the original document](.pci-3488-datasheet-19/pci-3488-datasheet-19.pdf)
