The basic concept was suggested by Gordon Bell in July, 1972, and a committee of DEC engineers was formed to produce the first version of the specification, which came out in August.
The fact that the MASSBUS connects to disk drives and tape controllers causes terminological difficulties, since there is also a 'controller' to connect the MASSBUS to the host computer. Hence, the term 'device' will be used in this article to refer, generically, to things connected to the MASSBUS (other than the controller in the host system). A single MASSBUS can contain up to 8 devices.
A variety of controllers existed to connect a MASSBUS to various kinds of DEC systems: the RH10 for the PDP-10, the RH20 for the KL10, the RH11 for the UNIBUS (usually on a PDP-11), the RH70 for the PDP-11/70, the RH750 for the VAX-11/75x, and the RH780 for the Synchronous Backplane Interconnect bus found on VAX-11/78x, VAX 86xx, etc.
In the MASSBUS system, most device-specific registers (e.g. 'current cylinder' for disk drives) are actually in the device; the MASSBUS interface to the host computer only contains registers such as main memory transfer address and transfer word counts.
The MASSBUS contained two separate sections (effectively, separate busses): an asynchronous control section (the 'Control Bus'), and a synchronous data transfer section (the 'Data Bus'). The two sections operate completely independently.
The control section is used to allow the CPU access to device registers implemented in the devices. The data section is 18 (optionally 16) bits wide, to allow use with both DEC's 36-bit and 16-bit (later 32-bit) architectures.
Control Bus lines
The Control Bus contains the following signals:
- Control Lines 0:15 - used to transfer control data
- Control Lines Parity
- Drive Select 0:2 - selects the entity
- Register Select 0:4
- Controller to Drive - direction of transfer
- Demand - set by the controller to initiate a transfer
- Transfer - acknowledgement from the entity
- Attention - set by an entity to notify the controller
- Initialize - set by the controller
- MASSBUS Fail - set by the controller to indicate power loss
Data Bus lines
The Data Bus contains the following signals:
- Data Lines 0:18 - used to transfer control data
- Data Lines Parity
- Sync Clock - on write, a request from the entity for data to be sent; on read, notification from the entity that data is ready
- Write Clock - on write, notification from the controller that data is ready
- Run - a signal from the controller to start a transfer
- End of Block - a signal from the entity to indicate the end of a transfer
- Exception - a signal from the entity to indicate that an error has occurred during a transfer
- Occupied - set by an entity to indicate that it is using the Data Bus