fbpx
Wikipedia

IEEE-488

IEEE 488, also known as HP-IB (Hewlett-Packard Interface Bus) and generically as GPIB (General Purpose Interface Bus), is a short-range digital communications 8-bit parallel multi-master interface bus specification developed by Hewlett-Packard. It subsequently became the subject of several standards.

IEEE 488 stacking connectors

Although the bus was created in the late 1960s to connect together automated test equipment, it also had some success during the 1970s and 1980s as a peripheral bus for early microcomputers, notably the Commodore PET. Newer standards have largely replaced IEEE 488 for computer use, but it is still used by test equipment.

History edit

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

The bus was relatively easy to implement using the technology at the time, using a simple parallel bus and 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 in TTL, 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 a de facto standard for automated and industrial instrument control. As GPIB became popular, it was formalized by various standards organizations.

In 1975, the IEEE standardized the bus as Standard Digital Interface for Programmable Instrumentation, IEEE 488; it was revised in 1978 (producing IEEE 488-1978).[1] 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 introduced Standard Codes, Formats, Protocols, and Common Commands, IEEE 488.2. It was revised in 1992.[2] 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,[3] and later Hewlett-Packard, recognized this as a problem. In 1989, HP developed their Test Measurement Language (TML)[4] or Test and Measurement Systems Language (TMSL)[5] which was the forerunner to Standard Commands for Programmable Instrumentation (SCPI), introduced as an industry standard in 1990.[6] 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.

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

National Instruments introduced a backward-compatible extension to IEEE 488.1, originally known as HS-488. It increased the maximum data rate to 8 Mbyte/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),[7] over HP's objections.[8][9]

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,[10] replaces IEEE 488.1/IEC 60625-1, and IEC 60488-2,Part 2: Codes, Formats, Protocols and Common Commands,[11] replaces IEEE 488.2/IEC 60625-2.[12]

Characteristics edit

IEEE 488 is an 8-bit, electrically parallel bus which employs sixteen signal lines — eight used for bi-directional data transfer, three for handshake, 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.[13][14]

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).[15] 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.[16]

In the original protocol, transfers use an interlocked, three-wire ready–valid–accepted handshake.[17] 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.[18]

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-pin Amphenol-designed micro ribbon connector. Micro ribbon connectors have a D-shaped metal shell, but are larger than D-subminiature connectors. They are sometimes called "Centronics connectors" after the 36-pin micro ribbon connector Centronics used 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 easy daisy-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[19] (now largely obsolete) or metric M3.5×0.6 threads. 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.[20]

The IEC 60625 standard prescribes the use of 25-pin D-subminiature connectors (the same as used for the parallel port on IBM 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[21]
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 Instruments GPIB controller for PC ISA bus
 
HP 7935 disc drive HP-IB Panel

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 early microcomputers needed 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 the HP series 80, HP 9800 series,[22] the HP 2100 series,[23] and the HP 3000 series.[24] HP computer peripherals which did not utilize the RS-232 communication interface often used HP-IB including disc systems like the HP 7935. Some of HP's advanced pocket calculators of the 1980s, such as the HP-41 and HP-71B series, also had IEEE 488 capabilities, via an optional HP-IL/HP-IB interface module.

Other manufacturers adopted GPIB for their computers as well, such as with the Tektronix 405x line.

The Commodore 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 a serial bus whose protocol was based on IEEE 488.[25] Commodore marketed an IEEE 488 cartridge for the VIC-20[26] and the Commodore 64.[27] Several third party suppliers of Commodore 64 peripherals made a cartridge for the C64 that provided an IEEE 488-derived interface on a card edge connector similar to that of the PET series.[28]

Eventually, faster, more complete standards such as SCSI superseded 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, so transmission line issues such as impedance matching and line termination are ignored. There was no requirement for galvanic isolation between the bus and devices, which created the possibility of ground loops causing 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.[29] Some aspects of the command protocol standards were not standardized until Standard 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 as USB, FireWire, and Ethernet take 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 as RS-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

References edit

  1. ^ IEEE Standard Digital Interface for Programmable Instrumentation, Institute of Electrical and Electronics Engineers, 1987, ISBN 0-471-62222-2, ANSI/IEEE Std 488.1-1987, p. iii
  2. ^ 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, ISBN 978-1-55937-238-1, IEEE Std 488.2-1992
  3. ^ Project Mate in 1985
  4. ^ "GPIB 101, A Tutorial of the GPIB Bus". ICS Electronics. p. 5, paragraph = SCPI Commands.
  5. ^ "Hewlett Packard Test & Measurement Catalog 1991" (PDF). hparchive.com. p. 8, paragraph = SCPI.
  6. ^ "History of GPIB". National Instruments. Retrieved 2010-02-06. In 1990, the IEEE 488.2 specification included the Standard Commands for Programmable Instrumentation (SCPI) document.
  7. ^ "Upgraded Standard Boosts Speed of IEEE 488 Instrument Buses Eightfold". IEEE. 2003-10-06. Retrieved 2010-02-06.
  8. ^ (Press release). Hewlett-Packard Company. December 1997. Archived from the original on 2011-06-10. Retrieved 2010-02-16.
  9. ^ . IEEE. Archived from the original on 2010-04-28. Retrieved 2010-02-16.
  10. ^ 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. ISBN 978-0-7381-4536-5.
  11. ^ 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. ISBN 978-0-7381-4100-8.
  12. ^ "Replaced or Withdrawn Publications". IEC. Archived from the original on 2012-04-17. Retrieved 2010-02-06.
  13. ^ "GPIB Addressing" (PDF). NI-488.2 User Manual. National Instruments Corporation. February 2005. p. A-2. NI P/N 370428C-01. Retrieved 2010-02-16. The primary address is a number in the range 0 to 30.
  14. ^ "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. Retrieved 2010-02-16. any address in the range 0 - 30, inclusive, may be used
  15. ^ "GPIB Instrument Control Tutorial". National Instruments. 2009-08-24. Retrieved 2010-02-16. connected in either a daisy-chain or star topology
  16. ^ (PDF). National Instruments Corporation. February 2005. p. A-1. NI P/N 370428C-01. Archived from the original (PDF) on 2008-12-02. Retrieved 2010-02-16.
  17. ^ "Handshake Lines" (PDF). NI-488.2 User Manual. National Instruments Corporation. February 2005. p. A-3. NI P/N 370428C-01. Retrieved 2010-02-16.
  18. ^ "Using HS488 to Improve GPIB System Performance". National Instruments Corporation. 30 March 2009. Retrieved 2010-02-16.
  19. ^ "Mechanical Aspects" (PDF). Tutorial Description of the Hewlett-Packard Interface Bus. Hewlett-Packard. p. 28. Retrieved 2022-06-13. Some existing cables use English threads (6-32UNK).
  20. ^ IEEE Standard Digital Interface for Programmable Instrumentation, Institute of Electrical and Electronics Engineers, 1987, p. v, ISBN 978-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.
  21. ^ 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)
  22. ^ = 463 "HP 98135A HP-IB Interface 9815". HP Computer Museum. Retrieved 2010-02-06. {{cite web}}: Check |url= value (help)
  23. ^ = 522 "59310A HP-IB Interface". HP Computer Museum. Retrieved 2010-02-06. HP-IB interface for HP1000 and HP2000 computers {{cite web}}: Check |url= value (help)
  24. ^ = 786 "27113A HP-IB Interface". HP Computer Museum. Retrieved 2010-02-06. CIO HP-IB interface for 3000 Series 900 {{cite web}}: Check |url= value (help)
  25. ^ Bagnall, Brian (2006). On the Edge: The Spectacular Rise and Fall of Commodore, Variant Press. Page 221. ISBN 0-9738649-0-7
  26. ^ Commodore drawing for VIC-1112 - Drawing no. 1110010 Rev:A
  27. ^ Reverse-engineered schematics for Commodore C64 IEEE interface
  28. ^ http://www.zimmers.net/anonftp/pub/cbm/schematics/cartridges/c64/ieee-488/index.html Link to schematic for one such converter.
  29. ^ Early devices might respond to an ID command with an identification string; later standards had devices respond to the *ID command.

External links edit

  • IEC 60488-1: Higher performance protocol for the standard digital interface for programmable instrumentation. Vol. Part 1: General. International Electrotechnical Commission. 2004-07-15.
  • IEC 60488-2: Standard digital interface for programmable instrumentation. Vol. Part 2: Codes, formats, protocols and common commands. International Electrotechnical Commission. 2004-05-07.
  • GPIB / IEEE 488 multiple page tutorial

ieee, this, article, lead, section, short, adequately, summarize, points, please, consider, expanding, lead, provide, accessible, overview, important, aspects, article, january, 2024, ieee, also, known, hewlett, packard, interface, generically, gpib, general, . This article s lead section may be too short to adequately summarize the key points Please consider expanding the lead to provide an accessible overview of all important aspects of the article January 2024 IEEE 488 also known as HP IB Hewlett Packard Interface Bus and generically as GPIB General Purpose Interface Bus is a short range digital communications 8 bit parallel multi master interface bus specification developed by Hewlett Packard It subsequently became the subject of several standards IEEE 488 stacking connectorsAlthough the bus was created in the late 1960s to connect together automated test equipment it also had some success during the 1970s and 1980s as a peripheral bus for early microcomputers notably the Commodore PET Newer standards have largely replaced IEEE 488 for computer use but it is still used by test equipment Contents 1 History 2 Characteristics 3 Connectors 4 Capabilities 5 Use as a computer interface 6 Comparison with other interface standards 7 See also 8 References 9 External linksHistory editIn the late 1960s Hewlett Packard HP manufactured various automated test and measurement instruments such as digital multimeters and logic analyzers They developed the HP Interface Bus HP IB to enable easier interconnection between instruments and controllers computers and other instruments This part of HP was later c 1999 spun off as Agilent Technologies and in 2014 Agilent s test and measurement division was spun off as Keysight Technologies citation needed The bus was relatively easy to implement using the technology at the time using a simple parallel bus and 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 in TTL 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 a de facto standard for automated and industrial instrument control As GPIB became popular it was formalized by various standards organizations In 1975 the IEEE standardized the bus as Standard Digital Interface for Programmable Instrumentation IEEE 488 it was revised in 1978 producing IEEE 488 1978 1 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 introduced Standard Codes Formats Protocols and Common Commands IEEE 488 2 It was revised in 1992 2 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 3 and later Hewlett Packard recognized this as a problem In 1989 HP developed their Test Measurement Language TML 4 or Test and Measurement Systems Language TMSL 5 which was the forerunner to Standard Commands for Programmable Instrumentation SCPI introduced as an industry standard in 1990 6 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 The IEC developed their own standards in parallel with the IEEE with IEC 60625 1 and IEC 60625 2 IEC 625 later replaced by IEC 60488 National Instruments introduced a backward compatible extension to IEEE 488 1 originally known as HS 488 It increased the maximum data rate to 8 Mbyte 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 7 over HP s objections 8 9 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 10 replaces IEEE 488 1 IEC 60625 1 and IEC 60488 2 Part 2 Codes Formats Protocols and Common Commands 11 replaces IEEE 488 2 IEC 60625 2 12 Characteristics editIEEE 488 is an 8 bit electrically parallel bus which employs sixteen signal lines eight used for bi directional data transfer three for handshake 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 13 14 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 15 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 16 In the original protocol transfers use an interlocked three wire ready valid accepted handshake 17 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 18 Connectors editIEEE 488Pinout nbsp Female IEEE 488 connectorPin 1DIO1Data input output bitPin 2DIO2Data input output bitPin 3DIO3Data input output bitPin 4DIO4Data input output bitPin 5EOIEnd or identifyPin 6DAVData validPin 7NRFDNot ready for dataPin 8NDACNot data acceptedPin 9IFCInterface clearPin 10SRQService requestPin 11ATNAttentionPin 12SHIELDPin 13DIO5Data input output bitPin 14DIO6Data input output bitPin 15DIO7Data input output bitPin 16DIO8Data input output bitPin 17RENRemote enablePin 18GND wire twisted with DAV Pin 19GND wire twisted with NRFD Pin 20GND wire twisted with NDAC Pin 21GND wire twisted with IFC Pin 22GND wire twisted with SRQ Pin 23GND wire twisted with ATN Pin 24Logic groundIEEE 488 specifies a 24 pin Amphenol designed micro ribbon connector Micro ribbon connectors have a D shaped metal shell but are larger than D subminiature connectors They are sometimes called Centronics connectors after the 36 pin micro ribbon connector Centronics used 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 easy daisy 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 19 now largely obsolete or metric M3 5 0 6 threads 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 20 The IEC 60625 standard prescribes the use of 25 pin D subminiature connectors the same as used for the parallel port on IBM PC compatibles This connector did not gain significant market acceptance against the established 24 pin connector Capabilities edit nbsp IEEE 488 port with listed capabilities on a laboratory temperature controllerCapabilities 21 Function Abbreviation Description and examplesSource Handshake SH 1 CompleteAcceptor Handshake AH 1 CompleteBasic Talker T 5 Responds to serial poll untalks when listen address received talk only capability6 Untalks when listen address received no talk only7 No serial poll untalks when listen address received talk only capabilityExtended Talker TE 0 No extended talkerBasic Listener L 3 Listen only mode unlistens if talk address received4 Unlistens if talk address receivedExtended Listener LE 0 No extended listenerService Request SR 0 No service request capability1 CompleteRemote Local RL 0 No local lockout1 CompleteParallel Poll PP 0 Does not respond to Parallel PollDevice Clear DC 1 completeDevice Trigger DT 0 No device trigger capability1 CompleteController C 0 No controller functionE 1 Open collector drive electronics2 Three state driversUse as a computer interface edit nbsp National Instruments GPIB controller for PC ISA bus nbsp HP 7935 disc drive HP IB PanelHP 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 early microcomputers needed 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 the HP series 80 HP 9800 series 22 the HP 2100 series 23 and the HP 3000 series 24 HP computer peripherals which did not utilize the RS 232 communication interface often used HP IB including disc systems like the HP 7935 Some of HP s advanced pocket calculators of the 1980s such as the HP 41 and HP 71B series also had IEEE 488 capabilities via an optional HP IL HP IB interface module Other manufacturers adopted GPIB for their computers as well such as with the Tektronix 405x line The Commodore 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 a serial bus whose protocol was based on IEEE 488 25 Commodore marketed an IEEE 488 cartridge for the VIC 20 26 and the Commodore 64 27 Several third party suppliers of Commodore 64 peripherals made a cartridge for the C64 that provided an IEEE 488 derived interface on a card edge connector similar to that of the PET series 28 Eventually faster more complete standards such as SCSI superseded IEEE 488 for peripheral access nbsp Rear of the Commodore CBM II showing card edge connector IEEE 488 port nbsp Rear of the Commodore SFD 1001 floppy disk drive with IEEE 488 port nbsp Rear of a Tektronix TDS 210 digital oscilloscope with IEEE 488 port nbsp Rear view of an Keysight 34970A data acquisition chassis multimeter nbsp C64 interface nbsp Acorn IEEE 488 Interface nbsp USB GPIB ConverterComparison with other interface standards editThis section does not cite any sources Please help improve this section by adding citations to reliable sources Unsourced material may be challenged and removed February 2010 Learn how and when to remove this template message 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 so transmission line issues such as impedance matching and line termination are ignored There was no requirement for galvanic isolation between the bus and devices which created the possibility of ground loops causing 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 29 Some aspects of the command protocol standards were not standardized until Standard 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 as USB FireWire and Ethernet take 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 as RS 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 nbsp Wikimedia Commons has media related to IEEE 488 Commodore bus Serial bus of the home computers series of Commodore HP series 80 1980 Hewlett Packard small scientific desktop computer HP IL communications protocolPages displaying wikidata descriptions as a fallback LAN eXtensions for Instrumentation Standard for controlling instrumentation and data acquisition instrumentation over Ethernet PCI eXtensions for Instrumentation Rocky Mountain BASIC Dialect of the BASIC programming language Standard Commands for Programmable Instruments Communications protocol for test equipment Virtual Instrument Software Architecture input output API used in the test and measurement industryPages displaying wikidata descriptions as a fallbackReferences edit IEEE Standard Digital Interface for Programmable Instrumentation Institute of Electrical and Electronics Engineers 1987 ISBN 0 471 62222 2 ANSI IEEE Std 488 1 1987 p iii 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 ISBN 978 1 55937 238 1 IEEE Std 488 2 1992 Project Mate in 1985 GPIB 101 A Tutorial of the GPIB Bus ICS Electronics p 5 paragraph SCPI Commands Hewlett Packard Test amp Measurement Catalog 1991 PDF hparchive com p 8 paragraph SCPI History of GPIB National Instruments Retrieved 2010 02 06 In 1990 the IEEE 488 2 specification included the Standard Commands for Programmable Instrumentation SCPI document Upgraded Standard Boosts Speed of IEEE 488 Instrument Buses Eightfold IEEE 2003 10 06 Retrieved 2010 02 06 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 from the original on 2011 06 10 Retrieved 2010 02 16 P488 1 Project Home IEEE Archived from the original on 2010 04 28 Retrieved 2010 02 16 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 ISBN 978 0 7381 4536 5 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 ISBN 978 0 7381 4100 8 Replaced or Withdrawn Publications IEC Archived from the original on 2012 04 17 Retrieved 2010 02 06 GPIB Addressing PDF NI 488 2 User Manual National Instruments Corporation February 2005 p A 2 NI P N 370428C 01 Retrieved 2010 02 16 The primary address is a number in the range 0 to 30 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 Retrieved 2010 02 16 any address in the range 0 30 inclusive may be used GPIB Instrument Control Tutorial National Instruments 2009 08 24 Retrieved 2010 02 16 connected in either a daisy chain or star topology NI 488 2 User Manual PDF National Instruments Corporation February 2005 p A 1 NI P N 370428C 01 Archived from the original PDF on 2008 12 02 Retrieved 2010 02 16 Handshake Lines PDF NI 488 2 User Manual National Instruments Corporation February 2005 p A 3 NI P N 370428C 01 Retrieved 2010 02 16 Using HS488 to Improve GPIB System Performance National Instruments Corporation 30 March 2009 Retrieved 2010 02 16 Mechanical Aspects PDF Tutorial Description of the Hewlett Packard Interface Bus Hewlett Packard p 28 Retrieved 2022 06 13 Some existing cables use English threads 6 32UNK IEEE Standard Digital Interface for Programmable Instrumentation Institute of Electrical and Electronics Engineers 1987 p v ISBN 978 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 Tilden Mark D 1983 Appendix A Subsets Describe Interface Functions PDF 4041 GPIB Programming Guide Tektronix Inc pp 113 115 a href Template Citation html title Template Citation citation a Cite uses generic title help 463 HP 98135A HP IB Interface 9815 HP Computer Museum Retrieved 2010 02 06 a href Template Cite web html title Template Cite web cite web a Check url value help 522 59310A HP IB Interface HP Computer Museum Retrieved 2010 02 06 HP IB interface for HP1000 and HP2000 computers a href Template Cite web html title Template Cite web cite web a Check url value help 786 27113A HP IB Interface HP Computer Museum Retrieved 2010 02 06 CIO HP IB interface for 3000 Series 900 a href Template Cite web html title Template Cite web cite web a Check url value help Bagnall Brian 2006 On the Edge The Spectacular Rise and Fall of Commodore Variant Press Page 221 ISBN 0 9738649 0 7 Commodore drawing for VIC 1112 Drawing no 1110010 Rev A Reverse engineered schematics for Commodore C64 IEEE interface http www zimmers net anonftp pub cbm schematics cartridges c64 ieee 488 index html Link to schematic for one such converter Early devices might respond to an ID command with an identification string later standards had devices respond to the ID command External links editIEC 60488 1 Higher performance protocol for the standard digital interface for programmable instrumentation Vol Part 1 General International Electrotechnical Commission 2004 07 15 IEC 60488 2 Standard digital interface for programmable instrumentation Vol Part 2 Codes formats protocols and common commands International Electrotechnical Commission 2004 05 07 GPIB IEEE 488 multiple page tutorial Retrieved from https en wikipedia org w index php title IEEE 488 amp oldid 1203083748, wikipedia, wiki, book, books, library,

article

, read, download, free, free download, mp3, video, mp4, 3gp, jpg, jpeg, gif, png, picture, music, song, movie, book, game, games.