Wikipedia

GPIB

IEEE 488,also known asHP-IB(Hewlett-Packard Interface Bus) and generically asGPIB(General Purpose Interface Bus), is a short-range digital communications8-bitparallelmulti-masterinterface busspecification developed byHewlett-Packard.It subsequently became the subject of several standards.

IEEE 488 cable with stacking connectors

Although the bus was created in the late 1960s to connect togetherautomated test equipment,it also had some success during the 1970s and 1980s as aperipheral busfor earlymicrocomputers,notably theCommodore PET.Newer standards have largely replaced IEEE 488 for computer use, but it is still used by test equipment.

History

edit

In the 1960s,Hewlett-Packard(HP) manufactured various automated test and measurement instruments, such as digitalmultimetersandlogic analyzers.They developed theHP Interface Bus (HP-IB)to enable easier interconnection between instruments and controllers (computers and other instruments).[1]This part of HP was later (c. 1999) spun off asAgilent Technologies,and in 2014 Agilent's test and measurement division was spun off asKeysight Technologies.[citation needed]

The bus was relatively easy to implement using the technology at the time, using a simple parallelbusand several individual control lines. For example, the HP 59501 Power Supply Programmer and HP 59306A Relay Actuator were both relatively simple HP-IB peripherals implemented inTTL,without the need for a microprocessor.

HP licensed the HP-IB patents for a nominal fee to other manufacturers. It became known as the General Purpose Interface Bus (GPIB), and became ade facto standardfor automated and industrial instrument control. As GPIB became popular, it was formalized by variousstandards organizations.

In 1975, theIEEEstandardized the bus asStandard Digital Interface for Programmable Instrumentation,IEEE 488; it was revised in 1978 (producing IEEE 488-1978).[2]The standard was revised in 1987, and redesignated as IEEE 488.1 (IEEE 488.1-1987). These standards formalized the mechanical, electrical, and basic protocol parameters of GPIB, but said nothing about the format of commands or data.

In 1987, IEEE introducedStandard Codes, Formats, Protocols, and Common Commands,IEEE 488.2. It was revised in 1992.[3]IEEE 488.2 provided for basic syntax and format conventions, as well as device-independent commands, data structures, error protocols, and the like. IEEE 488.2 built on IEEE 488.1 without superseding it; equipment can conform to IEEE 488.1 without following IEEE 488.2.

While IEEE 488.1 defined the hardware and IEEE 488.2 defined the protocol, there was still no standard for instrument-specific commands. Commands to control the same class of instrument,e.g.,multimeters, varied between manufacturers and even models.

The United States Air Force,[4]and later Hewlett-Packard, recognized this as a problem. In 1989, HP developed their Test Measurement Language (TML)[5]or Test and Measurement Systems Language (TMSL)[6]which was the forerunner toStandard Commands for Programmable Instrumentation(SCPI), introduced as an industry standard in 1990.[7]SCPI added standard generic commands, and a series of instrument classes with corresponding class-specific commands. SCPI mandated the IEEE 488.2 syntax, but allowed other (non-IEEE 488.1) physical transports.

TheIECdeveloped their own standards in parallel with the IEEE, with IEC 60625-1 and IEC 60625-2 (IEC 625), later replaced byIEC 60488-2.

National Instrumentsintroduced a backward-compatible extension to IEEE 488.1, originally known as HS-488. It increased the maximum data rate to 8Mbyte/s, although the rate decreases as more devices are connected to the bus. This was incorporated into the standard in 2003 (IEEE 488.1-2003),[8]over HP's objections.[9][10]

In 2004, the IEEE and IEC combined their respective standards into a "Dual Logo" IEEE/IEC standard IEC 60488-1,Standard for Higher Performance Protocol for the Standard Digital Interface for Programmable Instrumentation - Part 1: General,[11]replaces IEEE 488.1/IEC 60625-1, and IEC 60488-2,Part 2: Codes, Formats, Protocols and Common Commands,[12]replaces IEEE 488.2/IEC 60625-2.[13]

Characteristics

edit

IEEE 488 is an8-bit,electricallyparallelbus which employs sixteen signal lines — eight used for bi-directional data transfer, three forhandshake,and five for bus management — plus eight ground return lines.

The bus supports 31 five-bit primary device addresses numbered from 0 to 30, allocating a unique address to each device on the bus.[14][15]

The standard allows up to 15 devices to share a single physical bus of up to 20 metres (66 ft) total cable length. The physical topology can be linear or star (forked).[16]Active extenders allow longer buses, with up to 31 devices theoretically possible on a logical bus.

Control and data transfer functions are logically separated; a controller can address one device as a "talker" and one or more devices as "listeners" without having to participate in the data transfer. It is possible for multiple controllers to share the same bus, but only one can be the "Controller In Charge" at a time.[17]

In the original protocol, transfers use an interlocked, three-wireready–valid–acceptedhandshake.[18]The maximum data rate is about one megabyte per second. The later HS-488 extension relaxes the handshake requirements, allowing up to 8 Mbyte/s. The slowest participating device determines the speed of the bus.[19]

Connectors

edit
IEEE 488
Pinout
Female IEEE 488 connector
Pin 1 DIO1 Data input/output bit
Pin 2 DIO2 Data input/output bit
Pin 3 DIO3 Data input/output bit
Pin 4 DIO4 Data input/output bit
Pin 5 EOI End-or-identify
Pin 6 DAV Data valid
Pin 7 NRFD Not ready for data
Pin 8 NDAC Not data accepted
Pin 9 IFC Interface clear
Pin 10 SRQ Service request
Pin 11 ATN Attention
Pin 12 SHIELD
Pin 13 DIO5 Data input/output bit
Pin 14 DIO6 Data input/output bit
Pin 15 DIO7 Data input/output bit
Pin 16 DIO8 Data input/output bit
Pin 17 REN Remote enable
Pin 18 GND (wire twisted with DAV)
Pin 19 GND (wire twisted with NRFD)
Pin 20 GND (wire twisted with NDAC)
Pin 21 GND (wire twisted with IFC)
Pin 22 GND (wire twisted with SRQ)
Pin 23 GND (wire twisted with ATN)
Pin 24 Logic ground

IEEE 488 specifies a 24-pinAmphenol-designedmicro ribbonconnector. Micro ribbon connectors have a D-shaped metal shell, but are larger thanD-subminiatureconnectors. They are sometimes called "Centronics connectors" after the 36-pin micro ribbon connectorCentronicsused for their printers.

One unusual feature of IEEE 488 connectors is they commonly use a "double-headed" design, with male on one side, and female on the other. This allows stacking connectors for easydaisy-chaining.Mechanical considerations limit the number of stacked connectors to four or fewer, although a workaround involving physically supporting the connectors may be able to get around this.

They are held in place by screws, either 6-32 UNK[20](now largely obsolete) ormetricM3.5×0.6threads.Early versions of the standard suggested that metric screws should be blackened to avoid confusion with the incompatible UTS threads. However, by the 1987 revision this was no longer considered necessary because of the prevalence of metric threads.[21]

The IEC 60625 standard prescribes the use of 25-pinD-subminiatureconnectors (the same as used for theparallel portonIBM PC compatibles). This connector did not gain significant market acceptance against the established 24-pin connector.

Capabilities

edit
IEEE-488 port with listed capabilities on a laboratory temperature controller
Capabilities[22]
Function Abbreviation Description and examples
Source Handshake SH 1 Complete
Acceptor Handshake AH 1 Complete
Basic Talker T 5 Responds to serial poll; untalks when listen address received; talk only capability
6 Untalks when listen address received; no talk only
7 No serial poll; untalks when listen address received; talk only capability
Extended Talker TE 0 No extended talker
Basic Listener L 3 Listen only mode; unlistens if talk address received
4 Unlistens if talk address received
Extended Listener LE 0 No extended listener
Service Request SR 0 No service request capability
1 Complete
Remote-Local RL 0 No local lockout
1 Complete
Parallel Poll PP 0 Does not respond to Parallel Poll
Device Clear DC 1 complete
Device Trigger DT 0 No device trigger capability
1 Complete
Controller C 0 No controller function
E 1 Open collector drive electronics
2 Three state drivers

Use as a computer interface

edit
National InstrumentsGPIB controller card forPCIbus

HP's designers did not specifically plan for IEEE 488 to be a peripheral interface for general-purpose computers; the focus was on instrumentation. But when HP's earlymicrocomputersneeded an interface for peripherals (disk drives,tape drives,printers,plotters,etc.), HP-IB was readily available and easily adapted to the purpose.

HP computer products which used HP-IB included theHP Series 80,HP 9800 series,[23]theHP 2100series,[24]and theHP 3000series.[25]HP computer peripherals which did not utilize the RS-232 communication interface often used HP-IB including disc systems like theHP 7935.Some of HP's advanced pocket calculators of the 1980s, such as theHP-41andHP-71Bseries, also had IEEE 488 capabilities, via an optionalHP-IL/HP-IB interface module.

Other manufacturers adopted GPIB for their computers as well, such as with theTektronix 405xline.

TheCommodore PET(introduced 1977) range of personal computers connected their peripherals using the IEEE 488 bus, but with a non-standard card edge connector. Commodore's following 8-bit machines utilized aserial buswhose protocol was based on IEEE 488.[26]Commodore marketed an IEEE 488 cartridge for the VIC-20[27]and the Commodore 64.[28]Several third party suppliers ofCommodore 64 peripheralsmade a cartridge for the C64 that provided an IEEE 488-derived interface on a card edge connector similar to that of the PET series.[29]

Eventually, faster, more complete standards such asSCSIsuperseded IEEE 488 for peripheral access.

Comparison with other interface standards

edit

Electrically, IEEE 488 used a hardware interface that could be implemented with some discrete logic or with a microcontroller. The hardware interface enabled devices made by different manufacturers to communicate with a single host. Since each device generated the asynchronous handshaking signals required by the bus protocol, slow and fast devices could be mixed on one bus. The data transfer is relatively slow, sotransmission lineissues such as impedance matching and line termination are ignored. There was no requirement forgalvanic isolationbetween the bus and devices, which created the possibility ofground loopscausing extra noise and loss of data.

Physically, the IEEE 488 connectors and cabling were rugged and held in place by screws. While physically large and sturdy connectors were an advantage in industrial or laboratory set ups, the size and cost of the connectors was a liability in applications such as personal computers.

Although the electrical and physical interfaces were well defined, there was not an initial standard command set. Devices from different manufacturers might use different commands for the same function.[30]Some aspects of the command protocol standards were not standardized untilStandard Commands for Programmable Instruments(SCPI) in 1990. Implementation options (e.g. end of transmission handling) can complicate interoperability in pre-IEEE 488.2 devices.

More recent standards such asUSB,FireWire,andEthernettake advantage of declining costs of interface electronics to implement more complex standards providing higher bandwidth. The multi-conductor (parallel data) connectors and shielded cable were inherently more costly than the connectors and cabling that could be used with serial data transfer standards such asRS-232,RS-485,USB, FireWire or Ethernet. Very few mass-market personal computers or peripherals (such as printers or scanners) implemented IEEE 488.

See also

edit
Wikimedia Commons has media related toIEEE 488.

References

edit
  1. ^Nelson, Gerald E.; Ricci, David W. (October 1972)."A Practical Interface System for Electronic Instruments"(PDF).Hewlett-Packard Journal.24(2): 2–7.Controllers: 3260A Marked Card Reader;9820ACalculator (with 11144A Interface Kit)
    Loughry, Donald C. (October 1972)."A Common Digital Interface for Programmable Instruments: The Evolution of a System"(PDF).Hewlett-Packard Journal.24(2): 8–11.
  2. ^IEEE Standard Digital Interface for Programmable Instrumentation,Institute of Electrical and Electronics Engineers,1978,doi:10.1109/IEEESTD.1978.7425098,ISBN978-1-5044-0366-5,ANSI/IEEE Std 488-1978
    IEEE Standard Digital Interface for Programmable Instrumentation,Institute of Electrical and Electronics Engineers,1987,ISBN0-471-62222-2,ANSI/IEEE Std 488.1-1987,p. iii
  3. ^IEEE Standard Codes, Formats, Protocols, and Common Commands for Use With IEEE Std 488.1-1987, IEEE Standard Digital Interface for Programmable Instrumentation,Institute of Electrical and Electronics Engineers,1992,ISBN978-1-55937-238-1,IEEE Std 488.2-1992
  4. ^Project Mate in 1985
  5. ^"GPIB 101, A Tutorial of the GPIB Bus".ICS Electronics. p. 5, paragraph = SCPI Commands.
  6. ^"Hewlett Packard Test & Measurement Catalog 1991"(PDF).hparchive. p. 8, paragraph = SCPI.
  7. ^"History of GPIB".National Instruments.Retrieved2010-02-06.In 1990, the IEEE 488.2 specification included the Standard Commands for Programmable Instrumentation (SCPI) document.
  8. ^"Upgraded Standard Boosts Speed of IEEE 488 Instrument Buses Eightfold".IEEE. 2003-10-06. Archived fromthe originalon December 7, 2003.Retrieved2010-02-06.
  9. ^"HP and Other Test and Measurement Companies Urge IEEE to Oppose Revisions of Established IEEE 488 Standard"(Press release). Hewlett-Packard Company. December 1997. Archived fromthe originalon 2011-06-10.Retrieved2010-02-16.
  10. ^"P488.1 Project Home".IEEE. Archived fromthe originalon 2010-04-28.Retrieved2010-02-16.
  11. ^IEC/IEEE Standard for Higher Performance Protocol for the Standard Digital Interface for Programmable Instrumentation - Part 1: General (Adoption of IEEE Std 488.1-2003).IEEE.doi:10.1109/IEEESTD.2004.95749.ISBN978-0-7381-4536-5.
  12. ^Standard Digital Interface for Programmable Instrumentation- Part 2: Codes, Formats, Protocols and Common Commands (Adoption of (IEEE Std 488.2-1992).IEEE.doi:10.1109/IEEESTD.2004.95390.hdl:11059/14380.ISBN978-0-7381-4100-8.
  13. ^"Replaced or Withdrawn Publications".IEC. Archived fromthe originalon 2012-04-17.Retrieved2010-02-06.
  14. ^"GPIB Addressing"(PDF).NI-488.2 User Manual.National Instruments Corporation. February 2005. p. A-2. NI P/N 370428C-01.Retrieved2010-02-16.The primary address is a number in the range 0 to 30.
  15. ^"Table 1-1: 82350 GPIB interface card configuration parameters"(PDF).Agilent 82350B PCI GPIB Interface: Installation and Configuration Guide.Agilent Technologies. 2009-07-20. p. 26. Agilent P/N 82350-90004.Retrieved2010-02-16.any address in the range 0 - 30, inclusive, may be used
  16. ^"GPIB Instrument Control Tutorial".National Instruments. 2009-08-24.Retrieved2010-02-16.connected in either a daisy-chain or star topology
  17. ^NI-488.2 User Manual(PDF).National Instruments Corporation. February 2005. p. A-1. NI P/N 370428C-01. Archived fromthe original(PDF)on 2008-12-02.Retrieved2010-02-16.
  18. ^"Handshake Lines"(PDF).NI-488.2 User Manual.National Instruments Corporation. February 2005. p. A-3. NI P/N 370428C-01.Retrieved2010-02-16.
  19. ^"Using HS488 to Improve GPIB System Performance".National Instruments Corporation. 30 March 2009.Retrieved2010-02-16.
  20. ^"Mechanical Aspects"(PDF).Tutorial Description of the Hewlett-Packard Interface Bus.Hewlett-Packard. p. 28.Retrieved2022-06-13.Some existing cables use English threads (6-32UNK).
  21. ^IEEE Standard Digital Interface for Programmable Instrumentation,Institute of Electrical and Electronics Engineers,1987, p. v,ISBN978-0-471-62222-2,ANSI/IEEE Std 488.1-1987,The "helpful note" on metric threads found in previous editions has been deleted since metric thread use is common IEEE 488 practice. Consequently, the recommendation to coat such parts in black material to call attention to metric threads is also considered unnecessary.
  22. ^Tilden, Mark D. (1983),"Appendix A: Subsets Describe Interface Functions"(PDF),4041 GPIB Programming Guide,Tektronix, Inc., pp. 113–115{{citation}}:Cite uses generic title (help)
  23. ^"HP 98135A HP-IB Interface 9815".HP Computer Museum.Retrieved2010-02-06.
  24. ^"59310A HP-IB Interface".HP Computer Museum.Retrieved2010-02-06.HP-IB interface for HP1000 and HP2000 computers
  25. ^"27113A HP-IB Interface".HP Computer Museum.Retrieved2010-02-06.CIO HP-IB interface for 3000 Series 900
  26. ^Bagnall, Brian (2006).On the Edge: The Spectacular Rise and Fall of Commodore.Variant Press. p. 221.ISBN0-9738649-0-7.OCLC761384138.
  27. ^Commodore drawing for VIC-1112 - Drawing no. 1110010 Rev:A
  28. ^Reverse-engineered schematics for Commodore C64 IEEE interface
  29. ^http:// zimmers.net/anonftp/pub/cbm/schematics/cartridges/c64/ieee-488/index.htmlLink to schematic for one such converter.
  30. ^Early devices might respond to anIDcommand with an identification string; later standards had devices respond to the*IDcommand.
edit
Retrieved from "https://en.wikipedia.org/w/index.php?title=GPIB&oldid=1244027458"