What is GPIB and is it obsolete?

The bus, codified as the IEEE 488 standard, continues to find use in legacy test-system upgrades and in calibration labs.

The General-Purpose Interface Bus (GPIB) began life as the Hewlett-Packard Interface Bus (HP-IB). Hewlett-Packard, whose electronic test-and-measurement business has evolved into today’s Keysight Technologies, created the interface in the 1960s to connect multiple instruments in automatic test equipment (ATE) systems. Hewlett-Packard licensed the technology to other companies, and the term GPIB began appearing. In 1978, the IEEE codified the interface as the IEEE 488 Standard Digital Interface for Programmable Instrumentation.

The 1960s and 1970s — so it must be obsolete, or close to it, right?
Not at all. GPIB is still widely used in legacy test systems, especially in military and aerospace applications.

What are the technical details?
GPIB is an 8-bit parallel interface employing 16 signal lines and eight return (ground) lines. Figure 1 shows the connector and pin numbers, signal names, and signal descriptions. The GPIB interface includes eight bidirectional data lines (orange), five bus-management lines (blue), three handshake lines (red), and eight ground lines (gray).

What are the drawbacks of GPIB?
GPIB has comparatively low data rates, limited data-transmission distances, and large, costly cables and connectors compared to alternatives. The basic interface has a data rate of 1 MB/sec. An HS488 version developed by National Instruments (now NI) raises the data rate to 8 MB/s. The maximum data-transfer distance is about 20 m. In addition, parallel interfaces have fallen out of favor for several reasons, one being that the parallel bits in each byte can exhibit timing skew at high data rates.

What are the alternatives?
The Ethernet and USB serial interfaces are increasingly popular for interconnecting instruments. The LXI Consortium has defined LAN Extensions for Instrumentation (LXI), which enhances Ethernet with features specific for instrument control.

You mentioned that GPIB finds use in legacy systems. What benefits does it offer for legacy systems?
Say you have a GPIB-based legacy system consisting of several instruments of different types, and a signal generator fails. Your best approach would be to replace the failed unit with a new one of equivalent performance, identical interface connectors, and identical software calls.

Is GPIB still readily available?
It rarely comes standard anymore, though some calibrators such as the Fluke 5522A still have GPIB as a standard feature. Many vendors offer it as an added-cost option. For example, AMETEK Programmable Power offers GPIB as an option on its Asterion AC programmable power source. The company also offers an emulation mode that enables the Asterion AC to substitute for one of its older sources with no or minimal changes to test programs.

What if one of my instruments fails and I cannot find a suitable replacement with GPIB?
At that point, your best bet might be to migrate toward a hybrid system, such as the one shown in Figure 2, which incorporates GPIB and LXI. A hybrid system includes an Ethernet/GPIB gateway that lets you continue to use your GPIB instruments that still work. One such gateway is Keysight’s E5810B, which supports Ethernet and GPIB as well as USB and RS-232, the 1960s-era serial interface. The downside of evolving toward a hybrid architecture is that you will very likely have to make significant revisions to your test programs.

Where can I learn more?
NI has a paper titled “Eight Ways to Increase GPIB System Performance.” The LXI Consortium has more on hybrid systems here. CONTEC has the basics on GPIB, including information on daisy-chain and star connection topologies. Omega has an overview that discusses GPIB protocol, mechanical and electrical specifications, handshaking, addressing, and system controllers.