![Close-up of a blue LPCI-3488A microcontroller board with visible components and connectors (no readable text or symbols beyond label)](.PXI-3488_Datasheet_10/5b2af93a1fe184d1e01458560fe39ec3f5d692bab1271663ba4fb92bc4fd311b.jpg) ![Close-up of a blue printed circuit board (PCB) with visible components and connectors, labeled PXI-3488 at bottom (no readable text on board)](.PXI-3488_Datasheet_10/c45814c8e46d986985998bf8825f010465679f88aa1e4555455f4e0bb3c3d173.jpg) ![The image shows a partial graphic containing a light blue inverted triangle at the top. Below the triangle, the black text 'Fe' is visible in a bold, sans-serif font.](.PXI-3488_Datasheet_10/a6bf08556080f5ff859f2860a92cb278268a164729073b3d32a4441fdc17a8dd.jpg) # Features ■ Fully compatible with the IEEE-488 standard ■ Supports a 32-bit 3.3 V or 5 V PCI bus ■ PXI specification Rev. 2.2 compliant (PXI-3488) ■ Up to 1.5 MB/s data transfer rates ■ Built-in FIFO for read/write operations ■ Provides 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 Server Recommended Software \- VB/VC++/BCB/Delphi \- LabVIEW\* \- LabWindow/CVI\* # Introduction The IEEE-488 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 IEEE-488.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 IEEE-488.1-1978 and known as IEEE-488.2-1978. It was introduced to define data formats, common commands, and control protocols for instruments. In general, IEEE-488.1 defines hardware specifications, and IEEE-488.2 defines software specifications. The IEEE-488 standard has been widely accepted by instrument vendors over the past few decades. Today, GPIB is still the most popular interface between computer and instruments. ![Based on the provided flowchart/block diagram, here is the accurate description of the labeled blocks and connections:\n\n**Labeled Blocks (Instruments)**\n* **Instrument A:** Labeled 'Instrument A / Able to Talk, Listen and Control / ex: Computer', shown above a laptop icon.\n* **Instrument B:** Labeled 'Instrument B / Able to Talk and to Listen / ex: Oscilloscoe', shown above an oscilloscope icon.\n* **Instrument C:** Labeled 'Instrument C / Able to Listen / ex: Function Generator', shown above a function generator icon.\n\n**Signal Lines and Connections**\n* **Left Labels:** A stack of horizontal blue lines is labeled vertically from top to bottom: 'EOI', 'IFC', 'SRQ', 'ATN', 'REN', 'DAV', 'NRFD', 'NDAC'.\n* **Bottom Label:** A horizontal pink line is labeled 'DIO1-8'.\n* **Connections:** Red vertical lines connect the horizontal signal lines to the bottom of each instrument icon. Large pink arrows point upward from the signal lines toward each instrument.\n\n**Group Labels (Right Side)**\n* '5system Management lines' points to the top five blue signal lines (EOI through REN).\n* '3 handshake lines' points to the next three blue signal lines (DAV through NDAC).\n* '8 data lines' points to the bottom pink line (DIO1-8).\n\n**Caption**\n* The text at the bottom reads: 'Handshake and data signals on the GPIB bus'.](.PXI-3488_Datasheet_10/ce07a9f150b9400d7530c4019264fd30bae055a5d0b5433a19375b82beaaafb8.jpg) ![The image displays two diagrams illustrating different methods for connecting instruments to a computer.\n\n**Left Diagram: Linear instrument connection**\n* **Labeled Blocks:** A computer (monitor and tower), 'Instrument A', 'Instrument B', and 'Instrument C'.\n* **Connections:** Pink lines depict a daisy-chain topology. The computer connects to a connector block, which links to 'Instrument A'. From 'Instrument A', a connector block connects to 'Instrument B'. Finally, from 'Instrument B', a connector block connects to 'Instrument C'.\n\n**Right Diagram: Star instrument connection**\n* **Labeled Blocks:** A computer (monitor and tower), 'Instrument A', 'Instrument B', 'Instrument C', and 'Instrument D'.\n* **Connections:** Pink lines depict a hierarchical star topology. The computer connects to a bottom connector block. From this block, lines extend directly to 'Instrument A' and 'Instrument B'. A line also extends upward from this bottom connector block to a second, upper connector block. From this upper connector block, lines extend to 'Instrument C' and 'Instrument D'.](.PXI-3488_Datasheet_10/12f26947f593b7b7da6c67b25f949458ea1ce1fbeef0f1c225fa354d6bead434.jpg) ADLINK's LPCI-3488A and PXI-3488 GPIB controller interface cards are fully compatible with the IEEE-488.2 instrumentation control and communication standard and are capable of controlling up to 14 stand-alone instruments via IEEE-488 cables. The LPCI-3488A and PXI-3488 are designed to meet the requirements for high performance and maximum programming portability. The LPCI-3488A is developed using ADLINK's intellectual property in FPGAs which incorporates a GPIB controller, provides reliable GPIB bus control capability, and supports a transfer rate up to 1.5 MB/s. With APIs that are compatible with NI-488.2\* driver software and VISA support, the LPCI-3488A and PXI-3488 offer the best compatibility with your existing applications and instrument drivers ![| Block Size (Bytes) | Data Xfer Rate (KB/s) |\n| ------------------ | --------------------- |\n| 0 | 0 |\n| 200 | 200 |\n| 400 | 400 |\n| 600 | 550 |\n| 800 | 650 |\n| 1000 | 700 |](.PXI-3488_Datasheet_10/376afa62184c363c1261c75fa2ca3f225cc750e47fcd3adb15507701c16f0ab2.jpg) ![| Block Size (KBytes) | Data Xfer Rate (KB/s) |\n| ------------------- | --------------------- |\n| 0 | 0 |\n| 15 | 1400 |\n| 30 | 1500 |\n| 45 | 1550 |\n| 60 | 1575 |\n| 75 | 1580 |\n| 90 | 1585 |\n| 105 | 1590 |\n| 120 | 1595 |\n| 135 | 1600 |\n| 150 | 1600 |](.PXI-3488_Datasheet_10/a7a0470e01fb7f6067d21fd6b65102f0a302eed9733c4f140afea06255c943ef.jpg) # Performance ADLINK's expertise in PCI and PXI interface cards was leveraged when developing these newly designed GPIB interface card. The LPCI-3488A, which is the low-profile PCI form factor, supports both 3.3 V and 5V 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 used with most PXI and CompactPCI system. A built-in FIFO is placed between the GPIB bus and PCI controller to buffer GPIB read/write operations. This FIFO eliminates the gap between the slow GPIB bus ( $\sim$ 1.5 MB/s) and the fast PCI bus (132 MB/s), and dramatically increases overall system performance. # Fully Compatible with Your Existing Applications ADLINK GPIB interface cards are delivered with complete software support, including a driver API that is fully binary compatible with NI-488.2\* driver software. All programs written based on GPIB-32.DLL can be executed with LPCI-3488A or PXI-3488 without any modification. VISA library is also supported to ensure compatibility with applications utilizing VISA. The ADLINK LPCI-3488A and PXI-3488 thus provides the “Plug and Play” compatibility with all your existing applications. # How do ADLINK's GPIB Interface Cards Work? The objective of a test and measurement application is to test a specific UUT (Unit Under Test) automatically. A typical automatic testing system includes testing programs and various 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: ADEs (Application Development Environments), the environment where applications are written. Some ADEs 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: invoke the native driver API or use the 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 detailed control over GPIB instruments, using a driver API with SCPI string commands is a good 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 of the instrument drivers use a VISA library to control the GPIB interface and communicate with instruments. VISA support is essential in this case. ADLINK GPIB interface cards work with your applications in both ways. Its GPIB-32.DLL provides binary compatibility with the popular NI-488.2\* driver software. The LPCI-3488A and PXI-3488 also provide 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, ADLINK GPIB interface cards are the most cost-effective GPIB solutions compatible with all your applications. ![Based on the provided image, here is the accurate description of the flowchart:\n\n**Labeled Blocks (from top to bottom):**\n1. **ADE**\n2. **VISA**\n3. **Driver API (GPIB-32.DLL)**\n4. **GPIB Cards**\n\n**Connections and Annotations:**\n* **Primary Path:** A vertical stack of arrows connects the blocks in sequence: an arrow points from **ADE** to **VISA**, from **VISA** to **Driver API (GPIB-32.DLL)**, and finally from **Driver API (GPIB-32.DLL)** to **GPIB Cards**.\n * To the left of this path, the text reads: '• Using existing instrument drivers via VISA in ADE'\n* **Direct Path:** A separate green arrow points directly from the right side of the **ADE** block down to the **Driver API (GPIB-32.DLL)** block.\n * To the right of this path, the text reads: '• Direct invocation to GPIB driver API functions'\n\n**Side List Text:**\n* **Top Right (Next to ADE):**\n * '• Microsoft VC++/VB'\n * '• NI LabVIEW*'\n * '• NI LabWindows/CVI*'\n * '• Agilent TestExec'\n* **Middle Right (Next to Driver API):**\n * '• Native driver API to provide IEEE-488 functions'\n* **Bottom Right (Next to GPIB Cards):**\n * '• ADLINK LPCI-3488A'\n * '• ADLINK PXI-3488'\n * '• Agilent 82350B'\n * '• NI PCI-GPIB*'\n * '• ...'](.PXI-3488_Datasheet_10/ca8c677be7887d6ae0195b6f57ffcfa024a02fa7abca1be1688afff741301003.jpg) # Specifications
GPIB Bus SpecificationsUp to 14 instruments connectedMaximum 1.5 MB/s data transfer rateCable length-2 meters between each instrument (suggested)-20 meters total cable lengthData transfer mode: 8 bits parallelHandshake: 3 wire handshake, reception of each data byte is acknowledged
CertificationsEMC/EMI: CE, FCC Class A
Programming InterfaceVB/VC++/BCB/DelphiLabVIEWTM*LabWindows/CVI*
General SpecificationsI/O connector : IEEE-488 standard 24-pinOperating temperature : 0°C to 55°CStorage temperature : -20°C to 80°CRelative humidity : 5% to 95%, non-condensingPower requirementsLPCI-3488A+5 V250 mA (typical)300 mA (maximum)PXI-3488+5 V400 mA (typical)750 mA (maximum)+3.3 V400 mA (typical)750 mA (maximum)
Dimensions (not including connectors) :LPCI-3488A: 120 mm x 64 mmPXI-3488: 160 mm x 100 mm
# Ordering Information # LPCI-3488A High-Performance IEEE-488 GPIB interface card for low-profile PCI bus, shipped with an additional low-profile bracket. # PXI-3488 High-Performance IEEE-488 GPIB interface card for PXI/CompactPCI bus # ACL-IEEE488-1 IEEE-488 standard cable, I 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, LabWindows, and 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](.PXI-3488_Datasheet_10/PXI-3488_Datasheet_10.pdf)