The GP-IB defines operation of a three-wire handshake that is used for all data transfers on the bus.

The bus
operation is asynchronous in nature. The data-transfer rate of the GP-IB is 500 kHz for standard applications and can go
up 1 MHz if special conventions are followed. Each transaction carries 8 bits, the maximum data bandwidth is on the order
of 4 to 8 megabits (1 M byte) per second. The bus is a two way communications channel and data flows in both directions.
Figure 2 illustrates the structure of the GP-IB bus and identifies the 16 connections of the interconnecting cable.

GPIB
Listner
and / or
Talker

GPIB
Listner
and / or
Talker

GPIB
Listner
and / or
Talker

GPIB
Listner
and / or
Talker

DAV
NRFD
NDAC

Handshake Bus

IFC
ATN
SRQ
REN
EOI

Management Bus

DIO - 1

Data Bus
DIO - 8

Figure 2. GP-IB Instrumentation Bus Structure

The cabling limitations make it a less-than-ideal choice for large separation between devices. These limitations
can be overcome with bus extenders. Those attempting to use bus extenders should be aware that few extenders are as
transparent as claimed. This is especially true in handling of continuous data and interrupts. In nonextended environments,
it provides an excellent means for high-speed computer control of multiple devices.
The following table shows the various interface functions, the mnemonics and the descriptions.
Table 1. GP-IB Interface Functions
Interface Function

Mnemonic Description

Talker (extended talker)

T (TE)

Device must be able to transmit

Listener (Extended listener)

L (LE)

Device must receive commands and data

Source Handshake

SH

Device must properly transfer a multiline message

Acceptor Handshake

AH

Device must properly receive remote multiline messages

Remote/Local

RL

Device must be able to operate from front panel and remote information from bus

Service Request

SR

Device can asynchronously request service from the controller

Parallel Poll

PP

Upon controller request, device must uniquely identify itself if it requires service

Device Clear

DC

Device can be initialized to a predetermined state

Device Trigger

DT

A device function can be initiated by the talker on the bus

Controller

Device can send addresses, universal commands, address commands, and conduct
polls

Drivers

This code describes the type of electrical drivers in a device

9-5.2

IFF - IDENTIFICATION - FRIEND OR FOE

Originated in WWII for just that purpose - a way for our secondary radars to identify U.S. aircraft from enemy aircraft by
assigning a unique identifier code to U.S. aircraft transponders.
The system is considered a secondary radar system since it operates completely differently and independently of the primary
radar system that tracks aircraft skin returns only, although the same CRT display is frequently used for both.
The system was initially intended to distinguish between enemy and friend but has evolved such that the term "IFF"
commonly refers to all modes of operation, including civil and foreign aircraft use.
There are four major modes of operation currently in use by military aircraft plus one submode.
C
Mode 1 is a nonsecure low cost method used by ships to track aircraft and other ships.
C
Mode 2 is used by aircraft to make carrier controlled approaches to ships during inclement weather.
C
Mode 3 is the standard system also used by commercial aircraft to relay their position to ground controllers
throughout the world for air traffic control (ATC).
C
Mode 4 is secure encrypted IFF (the only true method of determining friend or foe)
C
Mode "C" is the altitude encoder.
The non-secure codes are manually set by the pilot but assigned by the air traffic controller.
A cross-band beacon is used, which simply means that the interrogation pulses are at one frequency and the reply pulses
are at a different frequency. 1030 MHz and 1090 MHz is a popular frequency pair used in the U.S.
The secondary radar transmits a series of selectable coded pulses. The aircraft transponder receives and decodes the
interrogation pulses. If the interrogation code is correct, the aircraft transponder transmits a different series of coded pulses
as a reply.
The advantage of the transponder is that the coded pulses "squawked" by the aircraft transponders after being interrogated
might typically be transmitted at a 10 watt ERP, which is much stronger than the microwatt skin return to the primary radar.
Input power levels may be on the order of several hundred watts.
The transponder antenna is low gain so that it can receive and reply to a radar from any direction.
An adjunct to the IFF beacon is the altitude encoding transponder known as mode C - all commercial and military aircraft
have them, but a fair percentage of general aviation light aircraft do not because of cost. The number of transponder
installations rises around many large metropolitan areas where they are required for safety (easier identification of aircraft
radar tracks).
Air traffic control primary radars are similar to the two dimensional search radar (working in azimuth and range only) and
cannot measure altitude.
The expanded display in figure 1 is typical of an air traffic control IFF response. The aircraft was told to squawk a four
digit number such as "4732". The altitude encoded transponder provides the aircraft altitude readout to the ground
controllers display along with the coded response identifying that particular aircraft.

5-6.1

The GP-IB defines operation of a three-wire handshake that is used for all data transfers on the bus. The bus
operation is asynchronous in nature. The data-transfer rate of the GP-IB is 500 kHz for standard applications and can go
up 1 MHz if special conventions are followed. Each transaction carries 8 bits, the maximum data bandwidth is on the order
of 4 to 8 megabits (1 M byte) per second. The bus is a two way communications channel and data flows in both directions.
Figure 2 illustrates the structure of the GP-IB bus and identifies the 16 connections of the interconnecting cable.

GPIB
Listner
and / or
Talker

GPIB
Listner
and / or
Talker

GPIB
Listner
and / or
Talker

GPIB
Listner
and / or
Talker

DAV
NRFD
NDAC

Handshake Bus

IFC
ATN
SRQ
REN
EOI

Management Bus

DIO - 1

Data Bus
DIO - 8

Figure 2. GP-IB Instrumentation Bus Structure

The cabling limitations make it a less-than-ideal choice for large separation between devices. These limitations
can be overcome with bus extenders. Those attempting to use bus extenders should be aware that few extenders are as
transparent as claimed. This is especially true in handling of continuous data and interrupts. In nonextended environments,
it provides an excellent means for high-speed computer control of multiple devices.
The following table shows the various interface functions, the mnemonics and the descriptions.
Table 1. GP-IB Interface Functions
Interface Function

Mnemonic Description

Talker (extended talker)

T (TE)

Device must be able to transmit

Listener (Extended listener)

L (LE)

Device must receive commands and data

Source Handshake

SH

Device must properly transfer a multiline message

Acceptor Handshake

AH

Device must properly receive remote multiline messages

Remote/Local

RL

Device must be able to operate from front panel and remote information from bus

Service Request

SR

Device can asynchronously request service from the controller

Parallel Poll

PP

Upon controller request, device must uniquely identify itself if it requires service

Device Clear

DC

Device can be initialized to a predetermined state

Device Trigger

DT

A device function can be initiated by the talker on the bus

Controller

Device can send addresses, universal commands, address commands, and conduct
polls

Drivers

This code describes the type of electrical drivers in a device

9-5.2

F1

Receiver

F2

Decode

Transmitter

TRANSPONDER
F1

Receiver

F2

Decode

Transmitter

Display

Select
Code

INTERROGATOR
Figure 1. IFF Transponder

5-6.2