The story of this documentAll the older CBM/PET Commodores are equipped with an IEEE-488 interface (from now on referred to as CBM). Due to the lack of any documentation on Internet about the technical background of IEEE for these Commodores on Internet, I started to collect all kind information I could lay my hands on to make my own electronic manual.
Everything in this manual is based on the original concept. Where Commodore did something else, I will mention this.
The historyThe IEEE bus was developed by Hewlett-Packard to connect and control programmable instruments and they called it HP-IB. The interface quickly became very popular in the computer industry. The IEEE committee gave it its present number and renamed it to GPIB (General Purpose Interface Bus). But it is better known under the number given by the IEEE committee: IEEE-448.
Commodore used the IEEE-448 bus to connect their floppy disks and printers to their computers. With the development of the VIC-20 they started to use another bus, but one still partly based on the IEEE-488. Instead of sending the data parallel, it is serialized. This bus became known as the IEC bus.
IEEE-488 OverviewYou can connect three type of devices to the IEEE-488 bus:
Some devices can perform more than one of these functions. The standard allows a maximum of 31 devices to be connected on the same bus. A minimum system consists of one Controller and one Talker or Listener, for example a CBM 8032 computer and a CBM 8023 printer.
A Listener is a device that can read data from the bus when instructed by the Controller. A Talker writes data to the bus when instructed. It is possible to have several Controllers on the bus but only one may be active at any given time: the Active Controller. The Active Controller may pass control to another controller that in turn can pass it back or pass it to yet another controller. The Controller can set up a talker and a group of listeners so that it is possible to send data between groups of devices as well.
If you have more Controllers connected to each other, only one can be active at the startup time. This Controller is called the System Controller.
We can connect more CBM computers to the same bus without any problem as long as we take care of the fact that only one computer is performing a command at the time. In IEEE-488 terms: you, the user, acts as the System Controller, allowing one of the connected computers to be an Active Controller for the time being.
Interface SignalsThe IEEE-488 interface system consists of 16 signal lines and 8 ground lines. The 16 signal lines are divided into 3 groups: 8 data lines, 3 handshake lines, and 5 interface management lines.
Data LinesThe lines DIO1 through DIO8 are used to transfer addresses, control information and data. The formats for addresses and control bytes are defined by the IEEE-488 standard. DIO1 is the Least Significant Bit, corresponding to bit 0 on a CBM.
Handshake LinesThe three handshake lines (NRFD, NDAC, DAV) control the transfer of message bytes among the devices and they acknowledge the transfer of data. This handshaking process guarantees that the bytes on the data lines are sent and received without any transmission errors and is one of the unique features of the IEEE-488 bus.
The NRFD (Not Ready for Data) handshake line is asserted by a Listener to indicate it is not yet ready for the next data or control byte. Note that the CBM will not see NRFD released (ie., ready for data) until all devices have released it.
The NDAC (Not Data Accepted) handshake line is asserted by a Listener to indicate it has not yet accepted the data or control byte on the data lines. Note that the CBM will not see NDAC released (ie., data accepted) until all devices have released it.
The DAV (DAta Valid) handshake line is asserted by the Talker to indicate that a data or control byte has been placed on the data lines and has had the minimum specified stabilising time. The byte can now be safely accepted by the devices.
HandshakingThe handshaking process is performed as follows. When the CBM or a Talker (ie.: floppy disk) wishes to transmit data on the bus, it sets the DAV line high, data is not valid, and checks to see that the NRFD and NDAC lines are both low, and then it puts the data on the data lines. When all the devices that can receive the data are ready, each releases its NRFD (Not Ready For Data) line. When the last receiver releases NRFD, and it goes high, the CBM or Talker takes DAV low indicating that valid data is now on the bus. In response each receiver takes NRFD low again to indicate it is busy and releases NDAC (Not Data Accepted) when it has received the data. When the last receiver has accepted the data, NDAC will go high and the CBM or Talker can set DAV high again to transmit the next byte of data.
Note that if after setting the DAV line high, the Controller or Talker senses that both NRFD and NDAC are high, an error will occur. Also if any device fails to perform its part of the handshake and releases either NDAC or NRFD, data cannot be transmitted over the bus. Eventually a timeout error will be generated.
The speed of the data transfer is controlled by the response of the slowest device on the bus, for this reason it is difficult to estimate data transfer rates on the IEEE-488 bus as they are always device dependent.
Interface Management LinesThe five interface management lines (ATN, EOI, IFC, REN, SRQ) manage the flow of control and data bytes across the interface.
The ATN (Attention) signal is asserted by the Controller to indicate that it is placing an address or control byte on the data bus. ATN is released to allow the assigned Talker to place status or data on the data bus. The Controller regains control by reasserting ATN; this is normally done synchronously with the handshake to avoid confusion between control and data bytes.
The EOI (End or Identify) signal has two uses. A Talker may assert EOI simultaneously with the last byte of data to indicate end-of-data. The CBM may assert EOI along with ATN to initiate a parallel poll. Although many devices do not use parallel poll, all devices should use EOI to end transfers (many currently available ones do not).
The IFC (Interface Clear) signal is asserted only by the System Controller in order to initialize all device interfaces to a known state. After releasing IFC, the System Controller is the Active Controller. In the CBMs IFC is operated by the RESET line through a buffer. In equipment like disk drives this signal is directly connected to the RESET line. So resetting the computer also resets a drive but resetting a drive does NOT reset the computer.
The REN (Remote Enable) signal is asserted only by the System Controller. Its assertion does not place devices into remote control mode; REN only enables a device to go into remote mode when addressed to listen. When in remote mode, a device should ignore its local front panel controls. This line is connected to ground inside the Commodores ie. no other System Controller is allowed.
The SRQ (Service Request) line is like an interrupt: it may be asserted by any device to request the Controller to take some action. The Controller must determine which device is asserting SRQ by conducting a serial poll. The requesting device releases SRQ when it is polled. The CBMs can only read this line. I doubt if there is a use for this line at all as all the schematics of the Commodore IEEE drives reveal that this line isn't used at all.
Line NRFD NDAC DAV ATN EOI IFC REN SQR | I O | I O | I O | I O | I O | I O | I O | I O | ------------|------|------|------|------|------|------|------|------| Listener | X | X | X | X | X | X | | | Talker | X | X | X | X | X | X | | | Controller | X X | X X | X X | X X | X X | X | G | X |X marks lines that can be used as well as "I = Input" as "O = Output"
As mentioned before, the line REN is n ot used by CBMs and has been hardware wired to GROUND. Therefore the "G".
Service Request and Serial PollingIf a device encounters a problem or a preprogrammed condition, it can activate the SQR line by setting it (L). If the Controller detects this request, it can initiate a 'Serial Poll' by transmitting the command SPE ($18) on the bus. It then places an address on the bus, activates ATN (which makes the addressed device a talker) an deactivates it.
If the device requested service, it will respond by setting DIO7 (L). It may indicate the nature of the request by setting other lines low as well. The Controller can now take appropriate actions.
When all devices have been polled, the controller terminates the serial poll by issuing the command SPD ($19).
Device AddressesThe IEEE-488 standard allows up to 31 devices to be interconnected on one bus. Each device is assigned a unique primary address, ranging from 0-30, by setting the address switches on the device. A secondary address may also be specified, ranging from 0-31. See the device documentation for more information on how to set the device primary and optional secondary address.
Commodore has assigned the addresses 0 till 3 to internal devices: keyboard, cassette recorder #1, cassette recorder #2/RS232 interface and screen. The printer address can range from 4 to 7. The drive address can range from 8 to 15. This range is limited by a hardware/software combination of the Commodore drives, not by the CBM. My CBMs accept without any problem device numbers above 15 generated by CBM-HD, a virtual Commodore disk drive.
The hardwareLooking at the schematic of a PET, like the 3008, you'll see that the MC3446 is used as the driver for almost all the signals. According to "The PET revealed" by Nick Hampshire, these ICs have 'Open Collector' outputs which means you can interconnect all kind of IEEE device without any fear of 'blowing up' them.
Other models are equipped with the SN75160 and the SN75161 from Texas Instruments. These ICs are drivers especially developed for IEEE-488.
The major difference between the two types is that when using the MC3446, you need one separate input and output line for every IEEE line, together 32 lines. This means two 6522s or 6520s. For the SN drivers you only need 19 lines or one 6525.
The SN75160You can roughly describe the 75160 as a bidirectional 8-bit bus interface. (like the 74245)
The SN75161The SN75161 is used to buffer the handshake and interface management lines. There is some internal logic to steer the output as follows:
| IFC | | NRFD | REN | ATN | TE | DC || EOI | DAV | NDAC | ATN | SRQ ------------------------------------------------------------------ L | L | L || O | I | O | O | I L | L | H || I | I | O | I | O L | H | L || O | O | I | O | I L | H | H || I | O | I | I | O H | L | L || O | I | O | O | I H | L | H || O | I | O | I | O H | H | L || I | O | I | O | I H | H | H || I | O | I | I | OIn words: ATN, IFC, REN and SQR are outputs if DC = (L), else inputs. DAV,NDAC and NRFD are outputs if TE = (L), else inputs. EOI behaves like DAV when ATN = (H), else like SQR.
+-----------+ TE -+ 1 20 +- VCC | | REN -+ 2 19 +- REN | | IFC -+ 3 18 +- IFC | | NDAC -+ 4 17 +- NDAC | | NRFD -+ 5 16 +- NRFD Connector side | | Computer side DAV -+ 6 15 +- DAV | | EOI -+ 7 14 +- EOI | | ATN -+ 8 13 +- ATN | | SRQ -+ 9 12 +- SRQ | | GND -+ 10 11 +- DC +-----------+
Physical CharacteristicsYou can link devices in either a linear, star or combination configuration using a shielded 24-conductor cable. The standard IEEE-488 cable has both a plug and receptacle connector on both ends. This connector is the Amphenol CHAMP or Cinch Series 57 MICRO RIBBON type. (it looks like a Centronics connector, but smaller) As far as I know all Commodore peripheral devices, like floppy disks, and the CBM-8xxx series are equipped with this type of connector. The other CBMs and PETs are equipped with a male edge connector. (like the userport of a C64 or VIC-20)
Pin Signal Abbreviation Source --- ---------------- ------------ ------------------ 1 Data Bit 1 DIO1 Talker 2 Data Bit 2 DIO2 Talker 3 Data Bit 3 DIO3 Talker 4 Data Bit 4 DIO4 Talker 5 End Or Indentity EOI Talker/Controller 6 Data Valid DAV Controller 7 Not Ready For Data NRFD Listener 8 No Data Accepted NDAC Listener 9 Interface Clear IFC Controller 10 Service Request SRQ Talker 11 Attention ATN Controller 12 Shield 13 Data Bit 5 DIO5 Talker 14 Data Bit 6 DIO6 Talker 15 Data Bit 7 DIO7 Talker 16 Data Bit 8 DIO8 Talker 17 Remote Enabled REN Controller 18 Ground DAV 19 Ground NRFD 20 Ground NDAC 21 Ground IFC 22 Ground SRQ 23 Ground ATN 24 Logical Ground
- Gary Pfeiffer, Hewlett-Packard
You can email me here.