The GPIB handshake is the mechanism that coordinates data exchange between instruments and a controller on the IEEE 488 bus. Rather than relying on a fixed delay, the bus uses control signals to indicate when data is available, whether receiving devices are ready, and when they have accepted a byte. For automation engineers and system integrators, understanding this sequence makes instrument communication easier to configure and troubleshoot.
The General Purpose Interface Bus (GPIB), also known as IEEE 488, was designed to let programmable instruments and controllers from different manufacturers communicate through a common interface. Its party-line structure connects multiple devices to shared data and control lines. A controller selects which devices will talk or listen, then the handshake manages the transfer itself.
How the IEEE 488 bus organizes communication
GPIB uses eight bidirectional data lines, DIO1 through DIO8, to carry information in parallel. Bytes are sent one after another, so the arrangement is commonly described as bit-parallel and byte-serial. The data lines can carry measurement data, device addresses or commands, depending on the state of the bus control signals.
In a typical exchange, one device acts as the talker and one or more devices act as listeners. The controller manages bus activity, including addressing devices and indicating when information on the data lines represents a command rather than ordinary data. Once the intended participants are established, the transfer-control lines coordinate each byte.
Understanding the GPIB handshake lines
Three lines form the core of the data transfer handshake: DAV, NRFD and NDAC. Their names describe their roles, but their active state is important: these signals are asserted low. The lines allow a transfer to accommodate devices that take different amounts of time to prepare or accept data.
- DAV (Data Valid): Controlled by the talker. It is asserted when the data on the DIO lines is valid for the listener to read.
- NRFD (Not Ready For Data): Controlled by the listeners. While asserted, it indicates that at least one listener is not ready for another byte.
- NDAC (Not Data Accepted): Also controlled by the listeners. It remains asserted until all participating listeners have accepted the current byte.
Because the listeners share the handshake lines, the slowest or least-ready listener can affect the pace of the transfer. The talker does not simply send bytes at an independent rate; it responds to the state of the bus.
The GPIB handshake sequence, step by step
After devices have been addressed, the listener first indicates readiness by releasing NRFD. The talker places a byte on the data lines and, after allowing the signals to settle, asserts DAV. This tells the listener that the byte is available.
The listener then indicates that it is taking the data by asserting NRFD. Once the byte has been captured, the listener releases NDAC. When the talker detects that the listeners have accepted the byte, it releases DAV, marking the data on the bus as no longer valid. The listeners then assert NDAC again as the byte is removed and release NRFD when they are ready for the next one.
The cycle repeats for each byte. In practical terms, the handshake gives the talker and listeners a shared way to coordinate progress without assuming that every device processes data at the same speed.
Commands, addressing and data are distinct phases
The handshake lines are also used while the controller sends addresses and commands. The ATN (Attention) line identifies this phase: when the controller asserts ATN, information on the data lines is interpreted as addressing or control information. When ATN is inactive, the addressed talker and listeners can exchange data.
Other GPIB management lines support broader bus functions. IFC (Interface Clear) allows the controller to return devices to an idle state. REN (Remote Enable) enables remote operation, while SRQ (Service Request) lets a device request attention from the controller. EOI (End Or Identify) can indicate the final byte of a message or participate in a parallel-poll sequence. These signals do not replace the three-line handshake; they help manage the bus and the meaning or boundaries of a transaction.
Using handshake behavior to troubleshoot transfers
When a transaction does not complete, examining the control-line sequence can help narrow down where communication stopped. A byte may be present on the data lines, for example, while DAV remains inactive; in that case, the listener has not yet been told that the byte is valid. If a listener keeps NRFD asserted, the talker must wait for readiness. If NDAC does not return to its inactive state, the talker has not received confirmation that all listeners accepted the byte.
These observations make bus timing diagrams useful during commissioning and fault diagnosis. Comparing the expected sequence with observed line transitions can reveal whether the problem lies in device readiness, byte acceptance, addressing or the transition between command and data phases. It can also expose cases where the controller and instrument are configured for different communication expectations, such as a device awaiting an additional command before sending data.
A systematic diagnostic approach is to verify that the intended devices are addressed, check the ATN state for the relevant phase, and follow DAV, NRFD and NDAC through a complete byte transfer. The handshake reports the progress of the exchange; it does not, by itself, explain why a device is not ready or accepting data. That distinction helps keep troubleshooting focused on the device behavior and transaction sequence.
Practical implications for automation systems
For engineers integrating programmable instruments, the GPIB handshake is more than a protocol detail. It is the mechanism that allows devices sharing a bus to coordinate transfers while accounting for differences in response time. Understanding each signal helps teams interpret bus activity, distinguish addressing issues from transfer delays, and make better use of timing documentation when a system behaves unexpectedly.
In short, reliable IEEE 488 communication depends on both correct device selection and a complete handshake. Treat DAV as the talker’s data-valid indication, NRFD as the listeners’ readiness signal, and NDAC as their acceptance confirmation. Following those signals byte by byte provides a practical foundation for commissioning and troubleshooting GPIB-connected instrumentation.