Digital PDFs

EK-0TU58-UG-3

2000

96 pages

Original

41MB

view download

OCR Version

16MB

view download

Document:	TU58 DECtape II User's Guide
Order Number:	EK-0TU58-UG
Revision:	3
Pages:	96
Original Filename:

OCR Text

EK-0TU58-UG-003

TUS8 DECtape

EK-0TU58-UG-003

TU58 DECtape |I
User Guide

Prepared by Educational Services
of

Digital Equipment Corporation

Ist Edition, October 1978

2nd Edition, June 1981
3rd Edition, October 1982

The reproduction of this material, in part or whole, is

strictly prohibited. For copy information, contact the
Educational Services Department, Digital Equipment
Corporation, Maynard, Massachusetts 01754.
The information in this document is subject to change
without notice. Digital Equipment Corporation assumes no

responsibility for any errors that may appear in this
document.

Printed in U.S.A.

The following are trademarks of Digital Equipment

Corporation, Maynard, Massachusetts.

DECUS

DEC

DECnet

OMNIBUS

DECsystem-10

0S/8
PDT

DIGITAL

DECSYSTEM-20

Digital Logo

DECwriter

RSTS

PDP

DIBOL

RSX

UNIBUS

EduSystem

VMS

DECtape
DECtape I

VAX
MASSBUS

10/82-14

IAS

CONTENTS

NN
NN

\FV)

E\J
:‘.’J\

Environmental .............. e e

Configurations .................

]

ot
[y

MECRhANICAL + v v v v ve e e

eeeevonneonnnoeenns

Hardware Documentatlon Ordenng INformation . ......ce

CHAPTER 2 OPERATION

1
1.1
1.2
1.3
1
2
3
1
3.2
3.3
4
4.1
S
5 1
5 2
5.3
5.4
5.5
.6
6.1
6.2

nesonses
e
anso
nc
oveeneos
ma
...c
Or
. ...
Perf
neeenns
menn
anen
Flectrical ... ...ovveiveen

o’

o.cocenn
....ns
tio
. ....
Specifica

e osnnmnaanssonnseosnaness

PrOCESSOT & v oo oo e oo

Do e

Drive Control ...........

. ........oveeoneonanneenanaeans

Block Diagram

sss
strrr
eo
emeeeemr
e e en
ve
e esan
v v vvvnve

]

General DESCHPHON

;.:::. h&wpwww

. vvvvvnnnns PR
SCOPE

o NP, B S H W
—

INTRODUCTION

O ~
N O VN

CHAPTER 1

vnnnneeenneeennnees 271
hmtmlsand INAICALOTS v vvve
TUS8-DA, -CARackmount
enenoraneaneenns e 27
Front Panel ... ...cvneenmmn
2
vivereennnn s
RunIndicator. .......ovv
2-1
.
er.“..‘..,.“..,..“,”...,.”.,.., .....
ApphcatmnandRemovalefPow
e, 272
ators ....... e e
Indicls
andro
TUS8-EA, -EB Cont
e 272
Front Panel .........c..cieenon. e
e e e 22
Run Indicator . e
ApphcatlanandRemevalofPower.,,.”,,..,,..,....fi.,,”t.,'.....,,..,,.i 2-2
2-2
TUSS-—VAContmlsandIndlcators.; e aa o a e 2-2
FLONE PANEL &+ o o v o eveeteeeeeeon,.,,., ,,,,, R s 2-2
RunIndlcater“...,”.. fPower.,...,,*”...“,”““”., ........ .. 2-3
ApphcatwnandRemovala
Indicators . ........c.oveeereemmneermerenees 2-3
TU58 Components Controls and
2-3
ApphcatxonandRemovalechwer. ,,,,,,
Cartridge ............ ifii!Qfiiiifl'6ii'tiCil!§§l!t}ili'gi!il*‘ii?‘fi 2-3
2—3
Cafindgemadmg‘c;ilit
2-3
ss
srss
erer
rnnr
meme
enmm
veeveoonnnnenren
Cartridge Unloading . ... ..vv
23
.
..
e
e
nre
nnm
idges . . .....oovvver
Keeping Track of Cartroot
2-3
e
oo ieaa
Write Protect TAh o oo
2-5
s
sess
rrrr
sesr
nmnr
neer
Cartridge Storage and Care . ..........ooeeecoenr
Maintenance ......... ..f....,...,..........,.....*.,.,;,..‘..,,... 2-5
2-5
HeadandPuckCleanmgi* . . . ... .vvvvevvenenrreeneem
2-5
t
e
Operator Trouble ISO1ation
2-5
Cartridge Wear ......

CHAPTER 3

PROGRAMMING

3.1

General Principles.

3.1.1

Special Handler Functions ......
... . ...
...
. ... .. ...
... .
. 3-1
Radial Serial Protocol (RSP) and Modified RSP (MRSP) e e e e e e e
e, 3-1
Packets .. ...
3-1
‘PacketUsage,....“.,...,””...”..............,.......,..
..... 3-2
Break and Initialization ...............
. . ...
...
. . et
e et 3-3
Command Packets ......... ... ... ... ... . . 00
3-3
Main
Mode
te
.......
na
......
nc
... ...
e... .
e 3-4
Special AddressMode . .......... ...
3-4
DataPackets. .. ... ... o o
3-4
Radial Serial Protocol. ....... ... ... ... . . .
3-4
Modified Radial Serial Protocol e e
ettt
e, 3-4
End Packets ... ... .. . .
3-4
Instruction Set .. ... ... .
3-6
PASCAL TUSS Handler Algorithm Definitions ...............
... ...
...
... 3-10

3.2

3.2.1

3.2.1.1
3.2.2
3.2.3

3.2.3.1
3.2.3.2

3.2.4
3.2.4.1

3.2.4.2

3.2.5
|

3.4

CHAPTER 4

INSTALLATION

4.1

Introduction................
... ...
.. ...
. ... e

4,2

4.2.1

4.2.2

4,2.3
4.2.4

4.2.5
4.3

4.3.4

4.4
4.4.1

4.5

4.5.1

4.5.2
4,53
4.6

4.8

4.8.1

4.8.2

Removing Bottom Plates for Controller Board Configuration

............... 4-2
Rackmounting Procedure . ....
... ...
..
000
..... 4-2

Tabletop Installation

4.4.2

4,7.2

Power Selection ......................e e
4-1

........ .. ... ...

... ..
i, 4-12
Solid Mounting Installation .........
... ... ...
000 .... 4-12
Installation (-VA Version) ........ et et et e ettt et et
e, 4-13
Tabletop Installation ......... ... ... ... ... ..
i
.
413
Solid Mounting Installation ..............................
.. .. ... ..
. 4-13
McuntmgtheTUSSVAthheSBll(orBAII-VA) e e
... 413
Components .......... .
4-13
Interface Standards Selection and Setup ........
.. 0.
....
0,
.. 4-16

;

|
|

|
?

i
i}

Selecting Interface Standards .. ...... ... ...

.. ... o' 4-17
ConnectmgStandards]umpers...,...““..”.,”........”,...,..
.,4-19
Operational Checkout ...................... e
.. 419
CheckoutofInterface ...................ccuvouo.
... e 4-19
Checkout of Drive Command Function .......... et
eri ettt 421

j
—

4.3.2
4,3.3

4.7.1

e ettt
e 4-1
Rack Installation (DA Version) ............ouuu
uuuunnnn 4-1
Rackmount ... ... .
4-1
Unpacking ....... ... . i
4-1

Rack Installation (<CA Version) ................
uuueime 4-7
Rackmount ... ... . .
4-7
Power Selection for the Rack Version . ............
... ... ...
....
. . . 4-8
Removing Module from Chassis . .. ....... F
4-10
Reinst
Module
al
......
li
... ...
ng
... ...
th
...e
... . ... . .. ... ... .. .. 410
Installation (-EA and -EB Versions) ...................couuu
eiunnn
. 4-12

4.3.1

4,7

3-1

Block Number, Byte Count, and Drive Number . ........... e
3-1

3.1.2

3.3

........ ..o

é
%3

CHAPTER 5
5.1
5.1.1

5.2

5.2.1
5.2.2

5.2.3

OPTIONS

Runlndicatertl,'Q'*GiQfil'.‘?‘(’ii"‘i.("‘fi‘fl‘lI!QQQQQQQQ'.‘ iiiiii S’l
Instanation $ & & # & B & = & ¥ £ # & & % % & % B ® 8 ® & @ & ® % & & & % 5 & % # Q‘ iiiiiiiiiiiiiiiii 5.‘1 ‘
BOOt SWItCH & v o et et it et it et e eneeneenssosocaanansessosnsnnnsans 5-2
e 5-2
e et ettt s s s et e
General........ e
R R R I 5-2
¢:1 5103 + K
(0)15)
v [ AR 5-2
e
Installation ... .....cvvev

APPENDIX A TU58/PDP-11 TOGGLE-IN BOOT
APPENDIX B RSP SEQUENCE

APPENDIX C SAMPLE DEVICE HANDLERS
APPENDIX D CARTRIDGE REPAIR
D.1

D.2
D.3
D.3.1

D.3.2
D.3.3

APPENDIX E

INtrOdUCHION &« &ttt ettt st e e esoennsaassesoosassanoesasanssssasasss D-1
Metal-Base Cartridge . . v v vvve ettt iei e ieennaae ste D-1
Plastic-Base Cartrid@e . . oo v v v v vt e vn teneoenoennnnaseosssnnnsssassenses D-3
R R R R D-3
for Threading .............. P
Preparation
Threading the Cartridge .................. e D-4
Closing the Cartridge . ........ouiitiimin

i D-5

FIELD REPLACEABLE UNIT SPARES LIST

FIGURES
1-1

1-2

1-3
1-4
2-1
2-2

2-3
2-4
2-5

3-1
3-2

3-3
4-1

4-2

4-3

4-4
4-5

4-6
4-7

4-8
4-9
4-10

Tape Cartridge Partially Inserted into Drive (Top View) ....... e 122

An Exchange in Radial Serial Protocol ......... ..o 1-3
TUSS Block Diagram . .....c.iivniiiiiueeeeenenennnnaaessesenson 1-4
Block Locations on Tape .. ..vciii it eninnnenrsesssocanasonananassss 1-5
TUS8-DA and -CA Rackmount FrontPanel .. ..... ... .. oo, 2-1
TUS8-EA,-EB,and-VA Front Panel ......... ... i, 2-2
Cartridge Loading . . ..o vt vt i it i i ii et enianaa i 2-4
Write Protect Tab . v v it ittt ittt et eaeeeonseeannnnannsesnsanessss 2-4
View Into Tape Drive Cartridge Slot ............c.covnnnn C e eseeae s 2-5
Read Command Packet Exchange .............cciiiie.. P co . 3-8
RSP Write Transaction . . ... ovv e vinneeneeeonooansnnsesnassssssnossssss 39
3-10
R R
MRSP Write Transaction .. ... e
P 4-2
A........ J AP
Rear Panel
TU58-D

Installing Support Brackets ......... ...t 4-3

...o T
... o
Installing Mounting Brackets ......

Front Vertical Rail U-Nut Retainers. .........coeeevnuuonesss e Ceeeeeen 4-4
)
nnees I
Rackmounting the TUS8-DA .. ... .. i
4-6
e
ee
e
R
ss
Rear Vertical Support U-Nut Retainers ..........cocveiicenevee

Fastening Support Bracket Extenders AP S EPRPRPRPRP o ¢
e nnenanns - o
Installingthe Bezel . ... ... iniii
s eesssscassesssnnsisuraseases 4-8
Stud ................L
and
BezelBall
rionranneetatoncnns 4-9
Rackmounting the TUS8-CA . ... ...ttt

4-11
4-12
4-13

4-14

4-15

4-16
4-17

418
4-19

4-20

4-21

5-1
D-1
D-2
D-3

D-4

D-5

TUS8-CA RearPanel ........ ... ... . ... ... ... . . 0
Installing Cage and Retainer Bar......
... 0000
...

4-10

.... 4-11

Mounting the TUS8-EAand-EB

..............oouuiui 4-12
MountmgChmcesfortheTUSS-VA,,...“‘..;,,,,...,,..“..“.,...
”_..4—14
Interfacing the TU58-VA e e e et et
e
e
e e e, 4-14
Drive Outline Drawings ....
.....
. ... 0
...... 4-15
Board Outline Drawings . . . . . .
... .. ... .. .
e
4-16
TUS8 Drive Mounting Hardware . ...............0.00o
0ooo 4-17

Data Rate and Cable Length for RS- 473 e
e e e e e e
e e e 4-19
Interface Selection Jumper Pin Locations .. ................. . e
4-20
FactoryW1r1ng e e
e e e
e e e
e e e S
3 |
Installation of Run Indicator .......... ... ... ... ... ... ...
... .. .. ..
5-1
Basepl
Screw Location
ate
s ................. i D-1
Threading the Metal-Base Cartridge ......
...
...
00
..... D-2
Head Gateand Spring....... ... ...
e
D-3
Stretch the Belt with the Floating Roller ... ........
... ......
.. .. .. . .
. D-3
Threading the Plastic-Ba
Cartridge . se
.
............oout
e D-4

TABLES

2-1

3-1
3-2
3-3

3-4

4-1

Operator Trouble Isolation . . ........ ... ...
2-6
Command Packet Structure ........... ... . ... i
3-3

Data Packets. . ... ...
i
3-5
End Packet .. ... oo
3-5
Instruction Set.. ...
3-7

TUS8 Module Connections . . . ...

vunesn

e o e 4-18

CHAPTER 1
INTRODUCTION

1.1

SCOPE

of applications.
The TU58 DECtape Il is a low-cost, mass-storage device that may be used in a wide variety
tape system. (For
This manual provides information that a user needs to install, interface, and operate the
specific information about using the TU58 under DIGITAL operating systems, refer to the individual system manuals.)

electrical and
Chapter 1 provides a general description of the TUS58 and a list of its specifications, including
mechanical requirements. The configurations section describes the available variations of the TUS8.
Chapter 2 contains important information for daily operation and routine maintenance. It is the system
operator’s reference section.

command set, illusChapter 3 is a programming guide. It contains functional descriptions of the TU58
the modified radial
and
(RSP)
protocol
serial
radial
the
of
details
trates command sequences, explains the
a general purpose
includes
and
,
sequences
byte
and
codes
on
serial protocol (MRSP), lists system instructi
programming example for a TU58 device handler.

Chapter 4 describes instructions for jumper selection; mechanical, electrical, and interface installation; and
operational checkout of the tape system.

Chapter 5 describes the optional features available in the TUSS.

Appendix A lists a PDP-11 toggle-in bootstrap for the TUSS.

Appendix B contains an RSP sequence to exercise a new cartridge.

Appendix C lists sample device handlers written in PDP-11 FORTRAN 1V and PDP-11 MACRO-11

assembly language.

Appendix D covers cartridge repair procedures.

Appendix E lists the field replaceable units (FRUs) in the TUS58.
1.2

GENERAL DESCRIPTION

preformatted tape
The TUS5S is a random-access, fixed-length-block, mass-storage tape system. It uses
on each of two
blocks
256
are
There
blocks.
512-byte
in
data
cartridges which store 262 kilobytes of
data stored on
for
d
employe
that
to
similar
fashion
a
in
tracks. They may be accessed by a program
easily impleis
structure
ted
file-orien
A
set.
n
instructio
disks or DECtape, using a new, high-level
mented in an operating system by setting aside several blocks on the tape to store a directory.

1-1

The TUS58 is compact and mechanically simple. The tape cartridges are DIGITAL-preformatted, miniature, reel-to-reel packages containing 42.7 m (140 ft) of 3.81 mm (0.150 in) wide tape. A single puck
drives the tape by engaging a roller which moves an elastomer drive belt in the cartridge. This belt
loops around both tape spools and provides uniform tension and spill-free winding without mechanical
linkages (Figure 1-1). The simple, single-point drive mechanism provides high reliability for the entire
system.

The control and drive circuitry of the TUS8 is located on a single circuit board. The controller uses a
microprocessor (uP) to reduce the tape handling and communications management load on the host
system.

The motor and tape head control, driver, and switching circuits that manage the two tape drives are on
the printed circuit board with the uP. The controller supports one or two drives, but only one drive can
operate at a time. The uP controls all activities of the TUS58. Head and motor selection, speed and
direction changes, etc. are managed by outputs from I/O ports on a peripheral integrated circuit (1C).
The mechanical actions of the drives are supervised by the uP in order to improve system performance.

Operational amplifiers, comparators, and logic circuits perform amplification, signal switching and conditioning, proportional control, and logic steering functions in the controller. The tape is protected by
motor current limiting and an anti-runaway timer.

The uP intelligence requires that requests from the host for data retrieval or storage contain only simple
specifications about the transfer. The controller positions the tape and performs the transfer without supervision from the host.

The host and controller communicate in a format called either radial serial protocol (RSP), or modified
radial serial protocol (MRSP). RSP uses two kinds of byte sequences called message packets. Both command and data packets have protocol information placed in specific locations in the byte sequence. This
format is easily generated by the TU58, making host-peripheral interaction possible at a high level with low
cost. Figure 1-2 illustrates a typical RSP exchange between a host computer and the TUS58. See Chapter 3
for a full discussion of RSP implementation.
DRP}IE PUCK

|_HEAD

— |
MICROSWITCHES
_ SWINGOUT

GATE

WRITE PROTECT/E

TAB

DRIVE /
ROLLER

SUPPLY

’

HUB

T~ rarE

TAPE

CARTRIDGE

Figure I-1

ELASTOMER
BELT

Tape Cartridge Partially Inserted into Drive (Top View)

1-2

When, owing to the data transfer rate selected, the buffer is unable to accept an entire transaction, modified serial protocol (MRSP) is utilized. MRSP is implemented by using the command packet switch byte.
See Paragraph 3.2 for a more detailed description of MRSP implementation.

The serial host interface operates on full-duplex, asynchronous, 4-wire lines at jumper-selectable rates of
150 to 38.4K baud. Send and receive rates may be independently set with jumpers to operate in accordance
with Electronic Industries Association (EIA) standards RS-422 or RS-423. When set to RS-423, the TUS8
is also compatible with devices complying with RS-232-C.
1.3 BLOCK DIAGRAM
Figure 1-3 illustrates the structure of the TUS58 system. The data path is along the top of the diagram,
passing to the host through the processor at the right. The drive control is at the lower left, also closely
associated with the processor through the 1/O ports. The ports, memory, and universal asynchronous
- receiver-transmitter (UART) are connected to the processor by an 8-bit-wide data/address bus.
1.3.1
Drive Control
|
|
The cartridge drive motors are powered by servo-regulated speed and direction circuits. These are con-

trolled by the processor, which monitors with tachometers and with signals from the tape. The heads

are selected by processor-controlled switches and either feed the automatic-gain-controlled (AGC) read
amplifier and decoder circuits or are driven by write currents encoded by the processor.
1.3.2 Processor
|
|
|
The processor consists of an 8085 processor supported by firmware in a 2-kilobyte, read only memory
(ROM) and by scratchpad and data buffer memory in a 256-byte random access memory (RAM). The
processor communicates with the drive control circuitry through a bidirectional 1/O port. The UART
exchanges data between the TUS8 processor bus and the host computer via the serial line drivers and
receivers.

HOST

TUs8

COMMAND

PACKET

CONTINUE

DATA

PACKET

CONTINUE

DATA

PACKET

END
o

MESSAG

PACKET|

MA-2384

Figure 1-2

An Exchange in Radial Serial Protocol

1-3

AGC

r Smennei

Sulieie SRS w1

DRIVE

READ

HEAD

AMP

sewect

PEAK DETECTOR

AND DECODER

WRITE AND

ERASE LOGIC

r'“""" I — d— """]
'

—

TR AND

VELOCITY
CONTRO

NTROL

AND DRIVERS

{

CONTROLLER

—

1/0 PORTS

8085

MOTOR
DRIVER

SERVO AMP

AND

{}

DRIVE
MOTOR

)

| seLeCT

DRIVER

RAM

ROM

256

BYTES

UART

DRIVERS

RECEIVERS

— TO HOST

MA-2378

Figure 1-3

1.4
1.4.1

TUS8 Block Diagram

SPECIFICATIONS
Performance

Capacity per cartridge

Data transfer rate
Read/write on tape

Data buffer to interface

Cartridge life

Data rehiability
Soft data error rate

Hard error rate

262,144 bytes, formatted in 512
blocks of 512 bytes each

41.7 us/data bit, 24 Kbits/s
150 to 38.4 kbaud, jumper selected
5000 minimum end-to-end-and-back
tape passes

1 in 107 bits read (before self-

correction)

1 in 109 bits read (unrecoverable

within 8 automatic retries)

Hard error rate with
write-verify and
system correction

2 in 10!! bits read /written

Error checking

Checksum with rotation

Average access time

9.3 seconds

Maximum access time

28 seconds

Read/write tape speed

76 cm/s (30 in/s)

Search tape speed

152 cm/s (60 in/s)

Bit density

315 bits/cm (800 bits/in)

Flux reversal density

945, fr/cm (2400 fr/in)

Recording method

Ratio encoding

DECtape II cartridge with 42.7 m
(140 ft) of 3.81 mm (0.150 in) tape.
Size: 6.1 X 8.1 X 1.3cm (2.4 X 3.2
X 0.5 in). Order TUS8-K.

Medium

Two tracks, each containing 1024
individually numbered, firmwareinterleaved “‘records.” Firmware

Track format (Figure 1-4)

manipulates four records at each
operation to form 512-byte blocks.

Drive

Single motor, head integrally cast

Drives per controller

1 or 2 (only one may operate at a
time)

1.4.2

into molded chassis.

Electrical

Power consumption
Board and 1 or 2
drives

11 W typical, drive running
+5V £5%at 0.75 A maximum

+12V 4+ 10% —5% at 1.2 A, peak
0.6 A average running
0.1 Aidle

These voltages need not stabilize
simultaneously upon power-on.

op | #128 | #384 | #1209 | #385 | #130
B
200

| e00 | 201

| 601

#386 | #131

| 202 | 602 | 203

| #3 [
| #2586
| #2
| #11 | #257
sor | #O
402 | 3
2
401
400
0 | #26

#254 | #510 | #255
376 | 776 | 377

| #382 | #127
#126
176 | 576 | 177
# DECIMAL
OCTAL

BOT: BEGINNING OF TAPE
EOT: END OF TAPE

Figure 1-4

Block Locations on Tape

1-5

casth

Rackmount

Serial interface standards

90 — 128 Vac, 180 — 256 Vac,
47 - 63 Hz, 35 W maximum

In accordance with RS-422 or RS-423;

compatible with RS-232-C.

1.43 Mechanical
8.1H X 83D x 10,6 Wem (3.2 X 3.3
X 4.1 in) with 19 cm (7.5 in) cable;

Drive

0.23 kg (0.5 1b)
Board

13.2H X 265D X 3.5Wcem (5.19 X
10.44 X 1.4in); 0.24 kg (0.53 1b)

TUS8-DA

Same rackspace as -CA. See -EA for

TU58-CA rackmount
cabinet

13.2H X 38.1 D X 48.3Wcm (5.19 X
15.0 X 19.01in); 9 kg (20 lbs)

TUS8-EA, -EB, -VA

92H X 29.5D X 33.7Wcm (3.6 X

Power connector to
board

AMP 87159-6 with 87027-3 contacts
DIGITAL PN 12-12202-09,
12-12203-00)

Power connector to

European IEC standard

Interface connector to
board

AMP 87133-5 with 87124-1 locking
clip contacts and 87179-1 index pin
(PN 12-14268-02, 12-14267-00,
|
12-15418-00)

chassis.

11.6 X 13.3 in); with rubber feet,
add 1.5 H cm (0.6 in)

rackmount

1.4.4

Environmental

When the TUS8-AB or -BB is integrated in a host device such as a terminal, convection provides adequate cooling if the interior temperature is below 50°. C (122° F) dry bulb, 26° C (79° F) wet bulb.
Maximum dissipation
TUS8-CA, -DA, -EA, -EB
TUS8-AB, -BB, -VA
Temperature

TUS8 operating

120 Btu/hour
34 Btu/hour

10° C (50° F) to 50° C (122° F)
ambient

TUS58 nonoperating

—34° C (—30° F) to 60° C (140° F)

Maximum temperature
difference between

18° C(32.4° F)

ambient and TUS58 board

Relative humidity, noncondensing
TUS8 operating

23° C(73.4°F)
2°C(36° F)
10% to 90%

Maximum dew point
Minimum dew point
Relative humidity

TUS8 nonoperating

5% to 98%
CAUTION

If a cartridge has been exposed to either the maximum or minimum temperature extreme, the tape
should be rewound one complete cycle before using.
This is done to bring the tape to the proper tension.
1.5

CONFIGURATIONS

The TUSS is available in the following configurations with accompanying designations.
TUS58-CA

Rackmount, large chassis, two drives, serial interface controller board, power
supply 115/230 V switch-selectable, detachable line cords and fuses for 115 V
and 230 V, two cartridges, boot ROM for MR11-EA, User Guide, Field Maintenance Print Set (MP00747), two I/0 cables (BC17A-18 and BC17B-18), di-

agnostic kit (ZJ287-RG).
TUS8-DA

TUS8-EA

Rackmount, tabletop chassis, two drives, serial interface controller board, power supply 115/230 V switch-selectable, detachable line cords and fuses for 115
V and 230 V, two cartridges, two I/O cables (BC17A-18 and BC17B-18), boot
ROM for MR11-EA, accessory assembly hardware kit (70-16753-00), User
Guide, Field Maintenance Print Sets (MP01014 and MP01063).

Tabletop, two drives, serial interface controller board, power supply 115/230 V
switch-selectable, detachable line cord and fuse for 115 V, accessory assembly
hardware kit (70-16753-00), User Guide, Field Maintenance Print Set
(MP01014).

TUSS8-EB

Tabletop, two drives, serial interface controller board, power supply 115/230 V
switch-selectable, detachable line cords and fuses for 115 V and 230 V, two cartridges, two 1/0 cables (BC17A-18 and BC17B-18), boot ROM for MR11-EA,
accessory assembly hardware kit (70-16753-00), User Guide, Field Maintenance Print Set (MP01014).

TUS8-VA

Tabletop, two drives, serial interface controller board, dc power cable (7017569-1C), 1/0 cable (70-17568-1F), two cartridges, MXV11-A-2 boot ROM,
User Guide, Configuration Guide, Field Maintenance Print Set (MP01013), accessory assembly hardware kit (70-16753-01).

Additional Supplies
BC17A-18

BC17B-18

Interface cable from TU58 to DL-11 and DLV-11, 5.4 m (18 ft) (10-pin-to-40-

pin connector).

Interface cable from TU58 to DLV-11J and MXV-11, 5.4 m (18 ft) (10-pin-to10-pin connector).

NOTE
BC17A-18 and BC17B-18 cables replace BC20Y-25
and BC20Z-25, respectively. The new cables have an
improved shield connection to improve system compliance with FCC regulations, Section 15, Subpart J.
BC20M-50

Interface cable from TU58 to DLV-11J and MXV-11, 15 m (50 ft) (10-pin-to-

10-pin connector).
BC20N-05

Null modem cable from TUS58 to EIA connector, 1.5 m (5 ft) (10-pin-to-DB25S female).
|
'

BC21B-05

Modem cable from TUS58 to EIA connector, 1.5 m (5 ft) (10-pin-to-DB25-P
male).

TUS8-K

Preformatted tape cartridges, available singly or in packs of five.

TUC-01

Tape Drive Cleaning Kit.

TU58-DB

Rackmount installation kit for tabletop versions -EA, -EB, -VA.

TUS8-EC

Accessory kit containing detachable line cord for 115 V, accessory assembly
hardware kit (70-16753-00), User Guide, Field Maintenance Print Set
(MPO0O1014).

TUS8-ED

Accessory kit containing detachable line cords for 115 V and 230 V and fuse for
230 V, two cartridges, two I/O cables (BC17A-18 and BC17B-18), boot ROM
for MR11-EA, accessory assembly hardware kit (70-16753-00), User Guide,
Field Maintenance Print Set (MP01014).

TUS8-VB

Accessory kit containing dc power cable (70-17569-1C), 1/0 cable (70-177568IF), two cartridges, MXV11-A2 boot ROM, User Guide, Configuration Guide,
Field Maintenance Print Set (MP01013), accessory assembly hardware kit (7016753-01).
|

17-00090-00

Line cord 250 V.

70-16753-00

Accessory assembly hardware kit with brackets for mounting TUS8 tabletop
versions to flat surface.

70-16753-01

Accessory assembly hardware kit with brackets for mounting TUS8 tabletop
versions below a flat surface.

23-126F3-0-0

Boot ROM for BDVI11.

MXVI1I-A-2

Boot ROM for MXV11.

23-765A9-00

Boot ROM for MR11-EA.

1-8

1.6

HARDWARE DOCUMENTATION ORDERING INFORMATION

The following TUS58 DECtape II Tape Subsystem hardware manuals can be purchased from
DIGITAL’s Accessory and Supplies Group.
Part No
EK-0TUS8-UG

Title TUS8 DECtape II User Guide

EK-OTUS8-TM

TUS8 DECtape II Technical Manual (microfiche or paper)

EK-OTUSS8-IP

TUS8 DECtape II Illustrated Parts Breakdown

MP00747
MP01014-00

TUS8-CA Field Maintenance Print Set
TUSS8-EA Field Maintenance Print Set

MP01063

TUS8-DB Field Maintenance Print Set

EK-0TU58-PS

MP01013-00

TUS58 DECtape II Pocket Service Guide

TUS58-VA Field Maintenance Print Set

ORDERING
You can order supplies and accessories from one of the follcwmg addresses, accerdmg to your location.

Continental USA

Call 800-258-1710, or mail order to:
Digital Equipment Corporatmn
P.O. Box CS2008
- Nashua, NH 03061

New Hampshire
Call 603-884-6660, or mail order to:
Digital Equipment Corporation
P.O. Box CS2008
Nashua, NH 03061

Alaska or Hawaii
Call 408-734-4915, or mail order to:
Digital Equipment Corporation
632 Caribbean Drive
Sunnyvale, CA 94086

Canada
Call 800-267-6146, or mail order to:
Digital Equipment of Canada LTD.
P.O. Box 13000
Kanata, Ontario, Canada K2K 2A6
Att: A&SG Business Manager
Telex: 610-562-8732

CHAPTER 2
OPERATION

2.1
2.1.1

TUS58-DA, -CA RACKMOUNT CONTROLS AND INDICATORS
|

Front Panel

The front panel (Figure 2-1) has two slots for the tape cartridges and two tape motion indicators for the
drives. In addition, the decorative bezel has a small compartment that can store up to four cartridges
(six on the -CA) in their boxes.

2.1.2 Run Indicator

Each tape drive has an indicator that lights to show tape motion. Since data loss can occur if a cartridge
is removed while the tape is being written, the cartridge should not be removed if the indicator is on.
2.1.3

Application and Removal of Power

The TUS58-DA has a power switch on its backpanel, while the TU58-CA does not. If an outlet is available on a system power controller, the TUS58 may be plugged into the controller. Otherwise, it does not
need to be turned off. Its idling power consumption is less than 20 W.
When power is applied, the TUS58 initializes itself, performs internal diagnostic tests, and then asks the
host for an acknowledgement before it settles down to wait for instructions. See Paragraph 3.2.2 for a

description of the required exchange.

If power is removed while a tape is being written, data may be lost. There are no other restrictions on
|

power removal.

DRIVEO

DRIVE 1

RUN INDICATOR

DRIVEO

TAPE STORAGE
AREA

Figure 2-1

MA-2381

TUS58-DA and -CA Rackmount Front Panel

2.2 TUS58-EA, -EB CONTROLS AND INDICATORS

The front panel (Figure 2-2) has two slots for the tape cartridges and two tape motion indicators for the
2.2.1

Front Panel

drives.

2.2.2

Run Indicator

Each tape drive has an indicator that lights to show tape motion in that drive.
Application and Removal of Power

panels. If an outlet is available on a
The TUS58-EA and -EB versions have power switches on theirtheback
er. Otherwise, they do not need
system power controller, these versions may be plugged into 20controll
W.
2.2.3

to be turned off. Their idling power consumption is less than

diagnostic tests, and then asks the
When power is applied, the TU58 initializes itself, performs internal
ions. See Paragraph 3.2.2 for a
host for an acknowledgement before it settles down to wait for instruct
|
description of the required exchange.

If power is removed while a tape is being written, data may be lost. There are no other restrictions

power removal.

2.3 TU58-VA CONTROLS AND INDICATORS

The front panel (Figure 2-2) has two slots for the tape cartridges and two tape motion indicators for the
2.3.1

Front Panel

drives.

2.3.2

Run Indicator

Each tape drive has an indicator that lights to show tape motion in that drive.
DRIVET

RUN INDICATOR

o N INDICATOR

DRIVE 1

DRIVEO

DRIVEO
MA.6843

Figure 2-2 TUS8-EA, -EB, and -VA Front Panel

2-2

2.3.3

Application and Removal of Power

The TUS8-VA requires +5 V and + 12 V from the device to which it connects. See the electrical specifications in Paragraph 1.4.2 for power requirements of a controller board and two drives. The part number of dc power cable supplied with the TU58-VA is 70-17569-1C. See Chapter 4 for installation infor|

mation.

When power is applied, the TUS8 initializes itself, performs internal diagnostic tests, and then asks the
host for an acknowledgement before it settles down to wait for instructions. See Paragraph 3.2.2 for a
v

description of the required exchange.

If power is removed while a tape is being written, data may be lost. There are no| other restrictions‘ on

power removal.

2.4 TU58 COMPONENTS CONTROLS AND INDICATORS
See Chapter 5 for installation and operation of optional features.
2.4.1

Application and Removal of Power

The TU58 may be supplied with power from a host system. It is ready for operation within one second
of voltage stabilization. It does not need to be turned off when not in use; its idling power consumption
|

is less than 5 W.

When power is applied, the TUS58 initializes itself, performs internal diagnostic tests, and then asks the
host for an acknowledgment before it settles down to wait for instructions. See Paragraph 3.2.2 for a
description of the required exchange.

If power is removed while a tape is being written, data may be lost. There are no other |restrictions on

power removal.
2.5

2.5.1

CARTRIDGE

Cartridge Loading

The TUSS drive is designed to make correct loading easy. To load the cartridge, hold it label-up, line it
up with the grooves in the chassis, and slide it in with a firm push. Figure 2-3 illustrates the fit of the
cartridge into the drive chassis grooves.
2.5.2

Cartridge Unloading

Unloading the cartridge is as simple as loading. Just pull it straight out. It is best to wait for the tape to
stop (run indicator turns off) before removing the cartridge. The mechanism cannot be damaged by
removing the cartridge while the tape is moving, but if a write is in progress, data may be lost. An error
message is sent to the host if a command is interrupted by removal of a cartridge. The cartridge may be
left in the drive as long as needed.
2.5.3

Keeping Track of Cartridges

2.5.4

Write Protect Tab

If the TUS8 is used in a non-file-structured system, the cartridge does not have an identifying number
or label recorded on the tape. If a cartridge is changed, the TU58 does not know that a different cartridge was loaded; the operator must keep track of the contents of various cartridges.
Each tape cartridge has a movable tab which, when properly positioned, protects data on the tape from
unintended write operations. When this write protect tab (Figure 2-4) is in the inner position (toward
the drive roller), it locks out the write circuitry.

When the write protect tab is in the outer position, it closes a switch in the chassis and allows the controller to write when it is commanded. The operator should be sure that system or program tapes are

backed up with copies before loading them into the TUS58 with their write protect tabs set to record.
&

2-3

MA-2376

Cartridge Loading

WRITE PROTECT TAB IN
PROTECT POSITION

Figure 2-3

MOVE TO RIGHT TO RECORD
-

MOVE TO LEFT TO PROTECT

MA-2359

Figure 2-4

Write Protect Tab

2-4

The write protect tab can be completely removed for long-term write protection. On the metal-base
cartridge, use a fmgernaxl under the protruding end to lift the protect tab. Replace it by dropping it into
its slot and pressing on it until it snaps. On the plastic-base cartridge, pry up the tab from its back edge
part way and then lift from the front. To replace it, drop it into its slot and press forward and down.
2.5.5

Cartridge Storage and Care

Store cartridges in their cases, away from dust, heat, and direct sunlight. Do not touch the tape; there is

no safe way to clean the tape and permanent errors may result. Keep tools and other ferrous or magnetic objects away. If it is possible that a tape has been exposed to environmental extremes (as listed in the
specifications), and if the software operating system permits, wind it all the way through with a Newtape (Paragraph 3.1.2) or equivalent command, or by requesting positionings to blocks at each end of
the tape before attempting to store data on the cartridge.

2.6

MAINTENANCE

2.6.1 Head and Puck Cleamng
After the first 20 hours of break-in runtime on each drive, clean the head and motor puck with a longhandled cotton applicator moistened with DIGITAL cleaning fluid (from cleaning kit TUC-01), 95 percent isopropyl alcohol, fluorocarbon TF, 113 or equivalent (Figure 2-5). Push the puck around with the
applicator to clean its entire surface. After the first cleaning, repeat the procedure after every 100
hours of runtime. Regular cleaning minimizes tape and head wear and prevents tape damage and data
errors caused by contamination. This is the only regular maintenance required by the TUSS.
2.6.2

Operator Trouble Isolation

Table 2-1 lists potential problems and possible corrective actions and comments. (Some items are not
applicable to components.)
2.6.3

Cartndge Wear

Cartridge tape is expected to last for 5000 end-to-end-and-back passes. If a cartridgeis at the end of its
life, a read operation may require several retries to get the data in the presence of soft errors. A soft
error is a temporary data loss which is usually caused by a speck of dirt or oxide on the tape or head
surface. This speck lifts the tape away from the head and causes signal loss and consequent read errors.
A few extra passes of the tape past the head may knock the speck away and allow error-free reading. If
it happens often, the tape is probably old and sheddmg oxide and should be copied and dlscarded as
soon as possible.

L
2 O]
DRIVE PUCK
MICROSWITCHES

HEL
TAPE HEAD
MA-2374

Figure 2-5 Vieww Into Tape Drive Cartridge Slot

Table 2-1

Operator Trouble Isolation

Symptom

Action/Comments

TUS58 does not respond

to host

Ensure that the TUS8-CA, -DA, -EA, or -EB is plugged into a live ac

socket (or proper dc source for -VA or components).

Check that the voltage selection switch is properly set.

Ensure that the fuse and power cord are intact and properly inserted.

Check that the baud rates and interface standards are the same for
both the TUS8 and the host interface board (Paragraph 4.7).
If possible, observe the self-test indicator on the controller board.
Remove the bezel on the rackmount version. When power is applied,
the indicator should light for a half second, go out for another half
second, and then relight. This means the controller has passed its
automatic self-test and is ready for operation. If the indicator remains
off, there is some problem within the board or in the interface.

Check that the interface cable is intact and properly inserted. If the
serial interface is suspected and the standards are correct, try a new

interface cable. An open wire in the line from the host prevents the
indicator from coming on. Other causes require servicing.

Check that the write protect tab is set correctly on the cartridge

TUS8 does not write
(reads okay)

(Figure 2-4).

The trouble may be in a drive. Try writing on the other drive. Any
problem except the write protect tab setting requires service.
Clean the head. Dirt and tape oxide buildup can cause errors.

Read errors (some host
operating systems may
provide this or a
similar message)

The tape may contain errors that were written onto it. If a tape is in
poor condition or if data is not verified at write-time, errors may
become a permanent part of the recording. A new cartridge with
format problems will produce the same error message. Try another
cartridge.

TUS58 sends motor-stopped
error messages

Motor or head is reaching end of life. Replace drive.

This indicates that a malfunction has occurred in the data recovery
section and the runaway timer has stopped the motor. The TUS8
should not be commanded to move tape more than twice under these
conditions without checking the cartridge. Make sure that the tape
is not getting near the end where it might come free of the hub.

CHAPTER 3

PROGRAMMING

3.1 GENERAL PRINCIPLES

The TUSSis controlled by a microprocessor that frees the host computer from device-related operations,
such as tape positioning and error retry. Only one high-level command to the microprocessor is necessary to
initiate a complex operation. The host and TUS58 communicate via strings of one or more bytes called
packets. One brief packet can contain a message which completely describes a high-level command. The
handshaking sequences between host and TUS58 as well as packet format are defined by the radial serial
protocol (RSP), or the modified radial serial protocol (MRSP), and were designed to be suitable for transmission by asynchrenous interfaces.

3.1.1

Block Number, Byte Count and Drive Number

The TUS58 uses a drive number, block number, and byte count to write or read data. Figure 1-4 (Chapter 1)
shows the locations of blocks on the tape. If all of the desired datais contained within a single 512-byte
block, the byte count will be 512 or less. When the host asks for a particular block and a 512-or-less byte
count, the TU58 positions the specified drive (unit) at that block and transfers the number of bytes specified. If the host asks for a block and also a byte count greater than that of the 512-byte boundary, the
TUS58 reads as many sequential blocks as are needed to fulfill the byte count. The same process applies to
the write function. This means that the host software or an on-tape file directory need only store the number of the first blockin a file and the file’s byte count to read or write all the data without having to know
the additional block numbers.
3.1.2

Special Handler Functions

Some device-related functions are not dealt with directly in the RSP, the MRSP, or in the TUS8 firmware.
1.

A short routine called Newtape (Appendix B) should be included in a TUS58 handler to provide a
complete wind-rewind for new or environmentally stressed tape cartridges. This procedure
brings the tape to proper operating tension levels.

A TU58 handler should check the success code (byte 3 of the RSP or MRSP end message) for
the presence of soft errors. This enables action to be taken before hard errors (permanent data
losses) occur.

3.2
3.2.1

RADIAL SERIAL PROTOCOL (RSP) AND MODIFIED RSP (MRSP)
Packets

All communication between the host and the TU58 is accomplished via sequences of bytes called packets.

There are two types of multi-byte packets: Control (Command) and Data. Either RSP or MRSP may be
selected using the command packet switch byte. In addition, there are three single-byte packets used to
manage protocol and control the state of the system: INIT, Continue, and XOFF.
Control (Command) - A Control packet is sent to the TUS8 to initiate all operations. The packet
contains a message completely describing the operation to be performed. In the case of a read or
write operation, for example, the message includes the function to be performed, unit (drive) number, byte count and block number.
3-1

i
I

the TU58 to the host after
A special case of the Control packet, called an End packet, is sent from
the status of the completed or

completion of an operation or on an error. The End packet includes
|

aborted operation.

message is actually the
Data - The Data packet holds messages of between 1 and 128 bytes. This
transmissions of larger
For
data transferred from or to the TU58 during a read or write operation.
than 128 bytes, the transfer is broken up and sent 128 bytes at a time.

p sequence. The TUS8
INIT - This single-byte packet is sent to the TU58 to cause the power-u
occurred. When the
has
returns Continue after completion, to indicate that the power-up sequenceizes and
sends INIT conTUS58 makes a protocol error or receives an invalid command, it reinitial
to restore the
TUS8
tinuously to the host. When the host recognizes INIT, it sends Break to the
protocol.

a byte containing a drive number,
Bootstrap — A flag byte saying Bootstrap (octal 10), followed by the
bytes without radial serial
causes the TU58 to read block 0 of the selected drive. It returns be 512
packaging. This simplifies bootstrap operations. Bootstrap may sent by the host instead of a
second INIT as part of the initialization process described below.

it must wait until the TUS8 sends
Continue — Before the host sends a Data packet to the TUSS,
data packets are sent to it.
Continue. This permits the TUS58 to control the rate that
XON - An alternate term for Continue.

es to the host. However, if the
XOFF - Ordinarily, the TU58 does not have to wait between messag
it may send XOFF. The
host is unable to receive all of a message from the peripheral at once,Continu
e to complete the
TUS8 stops transmitting immediately and waits until the host sends to the host
after the TUS3
transfer when it is ready. (Two characters may be sent by the UART
receives XOFF.)

the meaning of each byte. All packets
3.2.1.1 Packet Usage — Position within the packet determines
begin with a flag byte, which announces the type of packet to follow. Flag byte numeric assignments
are as follows.

Flag Byte Value

Octal Binary
Packet Type
00001
01
Data
00010
02
Control (Command)
00100
04
INIT
01000
10
Bootstrap

Continue
XON
XOFF

20
21
23

10000
10001
10011

(Bits 5 — 7 of the flag byte are reserved.)

count byte, message bytes, and two checkMultiple-byte (Control and Data) packets also contain a ebyte
in the packet. The two checksum bytes
bytes
sum bytes. The byte count byte is the number of messag g success
ive byte-pairs taken as 16-bit words
are a 16-bit checksum. The checksum is formed by summin The flag
and byte count bytes are includcarry).
while adding any carry back into the sum (end-around
x
ed in the checksum. (See example in Appendix B.)

3.2.2 Break and Initialization
Break is a unique logic entity that can be interpreted by the TU58 and the host regardless of the state
of the protocol. This is the logical equivalent of a bus init or a master reset. Break is transmitted when
the serial line, which normally switches between two logic states called mark and space, is kept in the
space condition for at least one character time. This causes the TU58’s UART to set its framing error
bit. The TUS8 interprets the framing error as Break.

If communications break down, due to any transient problem, the host may restore order by sending
Break and INIT as outlined above. The faulty operations are cancelled, and the TUS58 reinitializes it-

self, returns Continue, and waits for instructions.

With DIGITAL serial interfaces, the initialize sequence may be sent by the following sequence of operations. Set the Break bit in the transmit control status register, then send two null characters. When the
transmit ready flag is set again, remove the Break bit. This times Break to be one character time long.
is discarded by the TUS8 controller. Next, send two INIT characters. The first is
The second character
discarded by the TUS58. The TU58 responds to the second INIT by sending Continue. When Continue
has been received, the initialize sequence is complete and any command packet may follow.
3.2.3

Command Packets

The command packet format is shown in Table 3-1. Bytes 0, 1, 12, and 13 are the message delivery
bytes. Their definitions follow.

Table 3-1

Command Packet Structure
Byte Contents

0
1

Flag = 0000 0010(02g)
Message Byte Count = 0000 1010(12g)

2
3
4
5
6
7
8

Op Code
Modifier
Unit Number
Switches
Sequence Number — Low
Sequence Number — High
Byte Count — Low

ownd

Byte

9
0
]

12
13

Byte Count — High
Block Number — Low
Block Number — High
|

Flag

Message Byte Count

12,13

Checksum

Checksum - Low
Checksum — High

“This byte is set to 00000010 to indicate that the packet is a
Command packet.

Number of bytes in the packet, excluding the four message de-

livery bytes. This is decimal 10 for all command packets.

The 16-bit checksum of bytes O through 11. The checksum is
formed by treating each pair of bytes as a word and summing
words with end-around carry.

3-3

The remaining bytes are defined below

Op Code

Operation beivng commanded. (See Table 3-4 and Paragraph 3.3

Modifier

Permits variations of commands.

Unit Number

Selects drive 0 or 1.

Switches

Selects maintenance mode and specifies RSP or MRSP.

6,7

Sequence Number

Always zero for TU58.

8,9

Byte Coufit

Number of bytes to be transferred by a read or write command.

10,11

Block Number

The block number to be used by ccmmands requiring tape positioning.

for definitions.)

Ignored by other commands.

3.2.3.1 Maintenance Mode — Setting bit 4 of the switches byte (byte 5) to 1 in a read command inhibits retries on data errors. Instead, the incorrect data is delivered to the host followed by an end packet.
The success code in the end packet indicates a hard data error. Since data is transmitted in 128-byte
packets, a multiple packet read progresses normally until a checksum mismatch occurs. Then the bad
data packet is transmitted, followed by the end packet, and the operation terminates.
3.2.3.2 Special Address Mode — Setting the most significant bit of the modifier byte (byte 3) to |
selects special address mode. In this mode all tape positioning operations are addressed by 128-byte
records (0-2047) instead of 512-byte blocks (0-511). Zero-fill in a write operation only fills out to a 128byte boundary in this mode. To translate between normal addressing and special addressing, multiply
the normal address by 4. The result is the address of the first 128-byte record of the block. Add 1, 2, or
3 to get to the next three 128-byte records.
3.2.4

Data Packets

3.2.4.1 Radial Serial Protocol - A data transfer operation uses three or more message packets. The first
packet 1s the command packet from host to the TUS58. Next, the data is transferred in 128-byte packets in
either direction (as required by read or write). After all data is transferred, the TU58 sends an end packet.
If the TUS58 encounters a failure before all data has been transferred, it sends the end packet as soon as the
- failure occurs.
The data packet is shown in Table 3-2. The flag byte is set to 001g. The number of data bytes may be
between 1 and 128 bytes. For data transfers larger than 128 bytes, the transaction is broken up and sent
128 bytes at a time. The host is assumed to have enough buffer capacity to accept the entire transaction,
whereas the TUS58 only has 128 bytes of buffer space. For write commands, the host must wait between
message packets for the TUS58 to send the Continue flag 020g before sending the next packet. Because the
host has enough buffer space, the TU58 does not wait for a Continue flag between message packets when it
sends back read data.

3.2.4.2 Modified Radial Serial Protocol - When the host does not have sufficient buffer space to accept
entire transactions at the hardware selected data transfer rate, modified radial serial protocol (MRSP) may
be specified using the command packet switch byte. Bit 3 of the switch byte is set to specify the MRSP. Bit
3 remains set until intentionally cleared or cleared durmg power up. A good practice is to set bit 3 in every

MRSP command packet.

3-4

MRSP is identical to RSP except during transmission to the host. When a command packet specifies
MRSP for the first time (that is, bit 3 of the switch byte was previously cleared or cleared during power
up), the TU58 will send one data or end packet byte (whichever occurs first). The subsequent bytes, up to
and including the last byte of the end packet, will not be transmitted until a Continue or an XONis
received from the host. To prevent a protocol error from occurring, it is necessary to transmit Continue or
XON before transmitting any command packets. If a protocol error is detected, continuous INITs are sent
with the Continue handshake. If a bootstrap is being transmitted, however, no handshakeis employed.
3.2.5

End Packets

The end packetis sent to the host by the TUS8 after completlon or termination of an operation or an error.
End packets are sent using RSP or MRSP as spemfied by the last command packet The end packet is
shownin Table 3-3.

Table 3-2

Data Packets

0
1

Byte Contents

Byte

Flag = 0000 0001
Byte Count = M

2
3

First Data Byte
Data

i)ata

Last Data Byte

Checksum L
Checksum H

Byte Contents
Flag = 0000 0010

Byte Count
= 0000 1010
Op Code = 0100 0000
Success Code
Unit
Not Used
Sequence No. L
Sequence No. H
Actual Byte Count L
Actual Byte Count H
Summary Status L
Summary Status H
'~

Checksum L
Checksum H

The definition of bytes 0, 1, 12, and 13 are the same as for the command packet. The remaining bytes
are defined as follows,

Op Code — 0100 0000 for end packet

Byte 2

Success Code

Byte 3

Octal

Decimal

1
377

1
—1

-0

376

370
367
365
357

—8
-9
—11
—17

—
=
=
=

337
320
311

—33
—48
—55

=
=
=

—32

340

=
=

—

Normal success

Success but with retries
Failed self test

Partial operation (end of

medium)

Bad unit number
No cartridge
Write protected
Data check error

Seek error (block not found)
Motor stopped
Bad op code
Bad block number (>511)

Byte 4

Unit Number 0 or 1 for drive number

Byte 5

Always 0.

Bytes 6,7

Sequence number — always 0 as in command packet.

Bytes 8,9

Actual byte count — number of bytes handled in transaction. In a good oper-

Bytes 10,11

ation, this is the same as the data byte count in the command packet.
Summary Status
Byte 10
Bit 0

}

Bit 7

Byte 11

Reserved

Bit 0
1

4
5
6
7

Logic error
Motion error
Transfer error

Special condition (errors)

SET

3.3 INSTRUCTION
is determined by the
The operation performed by the TUS8 when it receives a Control (command) packet
modified radial
specify
can
command
op code byte in the control packet message. Note that while any
performed.
being
is
operation
boot
a
if
serial protocol with the switch byte, the response will not be MRSP

Instruction set op code byte assignments are listed in Table 3-4.

set have been reserved. These comTo allow for future development, certain op codes in theOpcommand
codes not listed in the command set are illegal
mands have unpredictable results and should not be used.

and result in the return of an end packet with the “bad op code” success code.

3-6

Table 3-4

Instruction Set

Op Code
Decimal

Op Code
Octal

Instruction Set

NOP

Read

INIT

Write

5
6
7

Position
(Reserved)
Diagnose

8
-9

10
11

Get status
Set status

(Reserved)

The following is a brief description and usage example of each.

OP CODE 0 NOP
This instruction causes the TUSS8 to return an end packet. There are no modifiers to NOP. The NOP
packet is shown below.
|
BYTE
0
1

0000

0010

FLAG

0000

1010

0000

MESSAGE BYTE CNT
OPCODE

3
4

0000
0000

0000
000X

MODIFIER
UNIT NUMBER (IGNORED)

5
6
7
8

0000
0000
0000
0000

SWITCHES (NOT USED)
SEQ NO. (NOT USED)
SEQ NO. (NOT USED)
BYTE COUNT L

NO DATA

9
10

0000
0000

BYTE COUNTH
BLOCK NO. L

INVOLVED
NO TAPE
POSITION

0000

BLOCK NO. H

0000
0000

001X
1010

CHECKSUM L
'CHECKSUM H

The TUS8 returns the following end packet.

b
L

ISP

0
1
2
3
4
5
6
7
8
9
10
11

0000

0010

FLAG

0000

1010

0100
0000
0000

0000
0000
000X

MESSAGE BYTE CNT
OPCODE
#
SUCCESS CODE
UNIT (IGNORED)

0000

NOT USED

0000

SEQ. L

0000
0000
0000

SEQ. H
ACTUAL BYTE CNT L
ACTUAL BYTE CNTH

0000

XXXX
000X

XXXX
XXXX
XXXX

SUMMARY STATUS L
SUMMARY STATUS H
CHECKSUM L
CHECKSUM H

XXXX

3-7

NO DATA
INVOLVED

OP CODE 1

INIT

This instruction causes the TUS8 controller to reset itself to a ready state. No tape positioning results
from this operation. The command packet is the same as for NOP except for the op code and the resultant change to the low order checksum byte. The TUS8 sends the same end packet as for NOP after
reinitializing itself. There are no modifiers to INIT.

OP CODE 2

Read, and Read with Decreased Sensitivity

This instruction causes the TU58 to position the tape in the drive selected by Unit Number to the block
designated by the block number bytes. It reads data starting at the designated block and continues
reading until the byte count (command bytes 8 and 9) is satisfied. After data has been sent, the TUS58
sends an end packet. Byte 3 indicates success, success with retries, or failure of the operation. In the
event of failure, the end packet is sent at the time of failure without filling up the data count. The end
packet is recognized by the host by the flag byte. The host sees a command flag (0000 0010) instead of
a data flag (0000 0001).

There are two modifiers to the read command. Setting the least significant bit of byte 3 to | causes the
TUS8 to read the tape with decreased sensitivity in the read amplifier. This makes the read amplifier
miss data if any weak spots are present. Thus, if the TUS8 can read error-free in this mode, the data is
healthy. The read transaction between TUS58 and host is shown for 510 bytes (just under a full block) in
Figure 3-1. Setting the most significant bit of byte 3 to 1 selects special address mode. See Paragraphs
3.2.3.1 and 3.2.3.2.

HOST

TUS8

COMMAND
-

PACKET

(READ 510 BYTES)

. l

DATA

128 BYTES

126 BYTES

DATA

. DATA

END

MA-2376

Figure 3-1
OP CODE 3

Read Cen{mand Packet Exchange

Write, and Write and Read Verify

This op code causes the TUSS8 to position the tape in the selected drive to the block specified by the
number in bytes 10,11 of the command packet and write data from the first data packet into that block.
It writes data from subsequent data packets into one or more blocks until the byte count called out in
bytes 8, 9 of the command packet has been satisfied.

The controller automatically zero-fills any remaining bytes in a 512-byte tape block.

3-8

There are two modifiers permitted with the write command. Setting the least significant bit of byte
3 to 1 causes the TU58 to write all of the data and then back up and read the data just written with
decreased sensitivity and test the checksum of each record. If all of the checksums are correct, the
TUS58 sends an end packet with the success code set to 0 (or 1 if retries were necessary to read the
data). Failure to read correct data results in a success code of — 17 (3573) to indicate a hard read
error. Setting the most significant
bit of byte 3 to 1 selects special address mode. See Paragraph
3.2.3.2.
The write operation has to cope with the fact that the TUS8 only has 128 bytes of buffer space. It is
necessary for the host to send a data packet and wait for the TU58 to write it before sending the next data
packet. This is accomplished using the continue flag. The continue flag is a single byte response of 0001
0000 from TUS8 to host. The RSP write transaction for both write and write/verify operations is shown in
Figure 3-2. The MRSP write transaction for both write and write/verify operations is shown in Figure 3-3.

HOST

TUS8

COMMAND
PACKET

WRITE

620

BYTES

DATA

{

128 BYTES

CONTINUE 1 ‘

TAPE POSITIONS

AND WRITES DATA
-

CONTINUE

DATA

128 BYTES

TAPE POSITIONS

AND WRITES DATA
<

DATA

__,_,__J_________,,

128 BYTES

CONTINUE

TAPE POSITIONS

AND WRITES DATA

-—

DATA

128 BYTES

CONTINUE

TAPE POSITIONS
AND WRITES DATA

DATA

108 BYTES

l l

CONTINUE

TAPE POSITIONS AND WRITES

DATA. TU58 ZERO-FILLS REMAINING 404 BYTES OF BLOCK. IF WRITE/

VERIFY, TAPE REWINDS AND READS
BLOCKS JUST WRITTEN AND TESTS
CHECKSUMS.

END
SUCCESS/FAILURE
MA-2377

Figure 3-2

RSP Write Transaction

TUSBS

HOST

contnue

IS NOT THE FIRST COMMAND PACKET

AFTER SELECTING MRSP.

. l

COMMAND

SEND “CONTINUE” HERE ONLY IF
THE FOLLOWING COMMAND PACKET

PACKET

WRITE

510BYTES

CONTINUE

4—————-—{
DATA

128 BYTES

]

CONTINUE

TAPE POSITIONS

AND WRITES DATA

]

CONTINUE

DATA

128 BYTES

CONTINUE

B
»

TAPE POSITIONS
AND WRITES DATA

CONTINUE

-—-—--—————{
DATA

128 BYTES

CONTINUE

—
TAPE POSITIONS

AND WRITES DATA
-

CONTINUE
-

DATA

128 BYTES

[

CONTINUE

}

WHEN USING MRSP, AN END PACKET
TRANSFER REQUIRES “CONTINUE" OR
“X-ON”” FROM THE HOST BEFORE EACH
REMAINING BYTE
END

SUCCESS/FAILURE
14 BYTES
Ma-10,483

Figure 3-3

MRSP Write Transaction

3-10

OP CODE 4

(Reserved)

OP CODE 5

Position

This command causes the TU58 to position tape on the selected drive to the block designated
by bytes 10,
I1. After reaching the selected block, it sends an end packet. See Paragraph 3.2.3.2.

OP CODE 6

(Reserved)

OP CODE 7 Diagnose
This command causes the TUS8 to run its internal diagnostic program which tests the processor,

ROM,

and RAM. Upon completion, TU58 sends an end packet with appropriate success code (0 = Pass, —1 =
Fail). Note that if the bootstrap hardware option is selected, boot information will be transmitted
without
handshaking even if the switch byte specifies MRSP.
OP CODE 8

Get Status

This command is treated as a NOP. The TU58 returns an end packet.

OP CODE 9 Set Status
This command is treated as a NOP because TUS8 status cannot be set from the host. The TUS8
retums’
an end packet.
OP CODE 10

(Reserved)

OP CODE 11

(Reserved)

3.4 PASCAL TUS8 HANDLER ALGORITHM DEFINITIONS
The following collection of algorithms describes the basic functions required for using

system. These algorithms are written in a pseudo-Pascal language and are therefore

the TUS8 in a
only designed to

illustrate the logic of operations involved in causing the TU58 to perform the intended function.
Actual
software for a particular host computer may be written using these algorithms along with
the program
examples found in Appendix C. The following is a list of the functions described.
I.

tudiagnose - Constructs and sends the command packet causing the TUS8 to execute
its
built-in, self-test diagnostic. Returns the TU58 end packet success code as the result.

tuseek — Constructs and sends the command packet which causes the TUS58 to position the

tape inserted in the specified drive to the specified block. Returns the success code obtained

from the TUS8 end packet as the result.
3.

turead - Constructs and sends the command packet which causes the TU58 to read data
from
the tape in the specified drive into a buffer area. Returns the success code obtained from
the
TUS58 end packet as the result.

tuwrite — Constructs and sends the command packet which causes the TU58 to write
data
from the buffer area specified to the specified TUS8 tape unit. Returns the success code
obtained from the TUS58 end packet as the result.

In addition to the above specific functions, algorithms for supporting routines are also provided.
These
routines are shared by the TU58 function routines and are included for the sake
of completeness. -

Digital Equipment Corporation assumes no responsibility for the correctness of these algorithms,
nor
offers corrections should errors be present. These algorithms may be copied for use on any
computer

system by any suitable language implementation.

CONSTANTS

{( Defines some interesting and useful constants }
}

{ Define single byte packet flags
=
=
=
=

data
control

init
continue
Xoff

12
27
43
16;
19;

{ Define multi-byte packet opcodes
read.opcode
write_opcode
position_opcode
diagnose.opcode
end.pack.opcode

=
=
=
=
=

}

27
¥
5;
7;
64;

{ Define initialization success codes }
07
-127;

success

failure

{ Define some useful subscript values )}
command.flag
command.count
command.opcode

= 0;
= 13
= 2;

command.unit
= 4;
data.count.low
= 8;
data.count.high =
9;
command.block._.low = 10;
command.block.high = 11;

{ Define length of command/data messages }
command.length
data.block

GLOBAL_VARIABLES

=
=

10;
128:;

{ Indicate guantities used by all functions }

single.byte_.packet

byte;

{ Note the variable lenqgth of the array defined below,

Its lenagth is a function of the type of message to be
sent, i.e., N is the number of bytes contained in the
message

)}

multi_byte_packet

ARRAY[0..N+3]

OF byte;

CALLING_PARAMETERS { Parameters defined by the c¢alling routines}
unit_number, block.number :INTEGER; { Specified unit/block}
no_bytes ¢ INTEGER; { Number of bytes in message }
buffer : ARRAY[1..no_.bytes] OF byte; { Data/message space }

3-12

tudiagnose;
{

This

BEGIN

routine

runs

the

Ti58

selft=test

diagnostic

routine

}

{ Construct and send the command packet
necessary

to execute
Return

the

contained
IF

cause

its

value

the

TUS8

self=test
of

the

TUS8

controller

diagnostic.
success

end

code

packet,

}

initialize(diagnose.opcode)=success
send.packet(packet,

tudiagnose

THFEN

BEGIN

command.length+2):

get.end.packet

failure

END

ELSE

tudiagnose
END;

{

tudiagnose

}

tuseek (unit.number, block‘nfimber)fi
{

Construct and send a
TUS8 should position

command packet which indicates tne
the specified unit to the specified

block.

returns

the

This

TU58

end

routine

packet
as

its

the

success

result,

code

sent

}

BEGIN

injtialize(position.opcode)=success
{

Construct/send

command

THEN

packet

BEGIN

}

packet[command.unit] := unit.number;
packet[command.block.low] := low(block.number);
packet[command.block.high]l] := high(block.number):

send.packet(packet,

{

command.lenath):

Conclude with an end packet

tuseek

get.end.packet;

failure;

}

END;

ELSE

END;

{

turead

{

tuseek
tuseek }

(unit.number,

block.number,

buffer,

no.bytes);

Constuct and send the command packet required to read
‘no.bytes’ from the unit and block specified,
Reads data
from the tape into a buffer space, returninag the value of
the success code contained in the TUS8 end packet, )}

BEGIN

THEN

initialize(read.opcode)=success

BEGIW

{ Construct command packet; operators ‘lcw’,'hiqh’
return

low

byte,

high

packet [command.unit]

byte

}

:= unit.number;

packet [command.block.low)]

packet(command.block.high]
send.packet (vacket,

respectively

low(block.numoer);

hiagh(blocKk.number);

command.lenath):

3-13

{

Get

data

output

and

stutf

buffer

get.data.packet(butfer)=success

ELSE

turead

get.end.packet

turead

fajilure

}

THEN

END

ELSE

turead

END;

{

turead

tuwrite

{

failure

}

(unit.number,

Construct

and

block.number,

send a

command

packet

unit and block for writino data.,
the specified buffer area to the
success

code

obtained

from

buffer,

the

no.bytes):;

specifying
the

write
tare,

TU58

end

the data from
Return the
packet

as the

result,}
LOCAL.VARIABLES

count,

data.count

INTEGER;

BEGIN

initialize(write.opcode)=success

{

Stuff

parameters

THEN

into command

BEGIN

packet

}

packet [commandounit] := unit.number;
packet[command_.block.low] 2= low(block_.number):

packet [command.block.high]
send.packet(packet,

{

:= hiagh(block.number);:;

command.lengtn);

If continue is received, send data; ‘get.byte”’
‘put.byte’are implementation=-dependept function
calls

}

data.count
WHILE

|
:=

no.bytes

get.byte=continue

{

Make

pblocks

THEN

maximum

REGIN

128

bhytes

eacn

}

count := minimum(data..count, data.block):;
put.byte(count);
send.packet(bufter(no.bytes~data.count+1],
count);
data.count

data.count

any event,

try

count

END;

{

for

tuwrite
END

:=
|

get.end.packet

tuwrite
tuwrite }

failure

end

packet

end

}

the

ELSE
END;

{

initialize

{

(op.code);

Initializes

the

TUS8

sending

communication

line,
. followed

for

twice,

INIT

sent

transmitted
or

the

first

the

The

TUSB

break

the

specified

either
a

(command)

byte

communication

line

control

characters

single

byte

operation

single

byte

multie-byte

{

Set

3-14

BREAK

then

packet

packet,
-}

BEGIN

packet

}

set.break.bit:

{

Delay multiple
error }

character

time

insure

framing

wait(n.character.times);

{ Remove BREAK condition from line }
reset.break.bit;

{

Initialize

command

packet

area

}

packet[command.flagl]
:= control;
packet [command.opcode] := op.CoOde;

{ send INIT flag to TUS8 )}
single.byte.packet

init;

put.bvte(single_.byte.packet):

IF get_.byte=continue THEN
ELSE

END;

{

initialize

:= success

failure:

}

'send_packet (buffer, no-bytes);
{ send information contained in ‘buffer’ to TUS8 }
LOCAL_.VARIABLES

index,

BEGIN

{

check.sum,

check.word

INTEGER?

Must beain with checksum initialization }

check.sum =
check.word

{ Check for even/odd bytes, performing checksum only
the operator ‘odd’ returns a Boolean value
if even;

of TRUE, if

the araqument

FOR index

odd

}

TO no.bytes DO BEGIN

odd(index) THEN
checkaword :=

ELSE

BEGIN

cneck.word
check.sum

bufferl(index]

:= buffer(index]#*256 + check.word;
check(check.sum, check.word)

END;

put.byte(butfer(index])
END:

IF odd(no.bytes)

check.sum

THEN

:= check(check.sum,

check.word);

{ Now output checksum information; operators “low?’,
‘high’ return low byte, high byte respectively }
put.byte(low(check.sum));
put.byte(high(check.sum))

END;

{

send.packet

}

3-15

get.data.packet

(buffer);

{ Gets the data sent from the TU56 and stuffs it into
‘butfer’

}

LOCALLVARIABLES

index,

check.sum,

data.count

variables

}

INTEGER;

BEGIN

{

Initialize

check.word
check.sum

{

Look

checksum

:=
:=

for

0;
get._byte;

valid

data

(check.sum<>data)

ELSE

packet
THEN

structure

}

get.data.packet

failure

BEGIN

{

Get data
checksum

packet
as the

data.Count

from TU58, calculating
buffer is being filled

get._byte;

check.sum

FOR

index

data.count*256;

data.count

BEGIN

buffer[index]

THEN

bufferl(index]

odd(index)
check.Word

ELSE

}

get_byte;

BEGIN
check.word

check.sum

buffer(index]*256

check(check.sum,

checkword;

check.word)

END
END

odd(data.count)
check.sum

{

Make

sure

THEN

check(check.sum,

packet

was

not

check.word

get.byte:;

cheCk.word

check.word

check.word<>check.sum
get.data.packet

ELSE

get.data.packet

check.word):;

error

}

get_byte*256;

THFN

failure

success

END

END:

{

get.data.packet

}

get.end.packet;

{
as

Gets

result

end

packet

from

the

TUS8,

returning

success

code

)

LOCAL.VARIABLES

index,

check.sum,

check.word

INTEGER;

BEGIN

check.sum

{
IF

Look

for

get_byte:

valid

command

(checkasum<>command)
OR

(get.byte<>end)

packet
OR

THEN

structure

)

(get.byte<>command.lenath)
get.end.packet

3-16

fajilure

BEGIN

FLSE
{

Get

success

code

get.end.packet

{

Now

the

from

command

checksum

calculation

check(check.word,

FOR

check.word

get.pyte;

check.word

}

get_end.packet*256);

REGIN

checka.word
checkesum

}

get.byte;

check.sum

index

packet

get.byte*256;

check(check.sum,

checka.word)

END;

{

Make

sure

packet

was

not

check.word

get.byte;

check.word

checkaword<>check.sum
get.end.racket

error

}

get.oyte*256;

THEM

failure

END

END:

{

check

(argl,

get.end_packet

}

ara?):

{ Computes the 16 bit checksum of argl and arg2,
-

around

carry

technigue

TUS8

using end=

}

BEGIN

{

The function
1 {f the sum
8

carry:;

check

END;

argl

{

check}

{

End

‘carry’ returns a value of
of the arguments results in

value
+

arq?2

0
+

algorithm

returneg

otherwise

carry(aragl,arqg2)

definitions

}

3-17

}

CHAPTER 4

INSTALLATION

4.1

INTRODUCTION

This chapter contains installation, configuration, and checkout precedures for all the versions of the
TUSS DECtape II (-DA, -CA, -EA, -EB, -VA components).
4.2

RACK INSTALLATION (-DA Version)
|

Rackmount

4.2.1

The TU58-DA mounts in 13.2 cm (5.2 in) of standard 48.3 cm (19 in) width rack. It should be located
so that the 2 m (6 ft) power cord can reach a power controller outlet box such as the DIGITAL 861 or
any power outlet,

Unpacking

4.2.2

The TUS58-DA shipping carton contains the following items for rackmounting.
1
1
2
2

TUS8-EB
Bezel
Mounting brackets
Support brackets

Support bracket extenders

Phillips trusshead screws 10-32 X 1/21in
Internal lock washers

U-Nut retainers

Line cord (120 V)

Kep lock nuts 10-32 X 3/8

Fuses (3/8 A and 3/4 A slow-blow)

Power Selection

4.2.3

Detachable line cords for 115 V and 230 V, and two fuses are supplied with the TU58-DA. The line
cord receptacle meets European IEC standards. A switch on the back of the tape drive rear panel se-

lects 115 V or 230 V (Figure 4-1).

Set the voltage switch to the correct value using a small screwdriver.
Switch

Position
Left
Right

Voltage
115V
230V
CAUTION

Range
90 - 128 Vrms
180 — 256 Vrms

If the TUSS is plugged into a 230 V circuit while set
for 115 V, it may be severely damaged.

120/240V

FUSE POST

SWITCH

INTERFACE CABLE

CONNECTOR

CABLE SHIELD

GROUND SCREW

V-G
/

O o©

POWER

LINE CORD

SWITCH

RECEPTICAL
MA.B8470

Figure 4-1

TUS8-DA Rear Panel

From the two fuses provided, select and install the proper fuse in the fuse post. To open the
fuse post, use a 3/16-inch blade type screwdriver. Press in the fuse post cap and turn it
counterclockwise. To close the fuse post, use the screwdriver to press in the cap and turn it
clockwise.
Voltage
115V
230V

Fuse
3/4 A slow-blow
3/8 A slow-blow

4.2.4 Removing Bottom Plates for Controller Board Configuration
The TUS8 1s shipped prewired for operation at 38.4K baud transmit and receive on RS-423. If a con-

figuration change is necessary, the bottom plates must be removed in order to gain access to the con-

troller board. Use the following procedure to remove the bottom plates. (See Paragraph 4.7 for configuration information.)
l.

Disconnect the power cord and interface cable from the rear panel of the TUS58 (Figure 4-1).

Place the TUS8 upside-down on a flat working surface so the rear panel faces you.

Remove the two Phillips head screws and lock washers from the front plate. Remove the
front plate, exposing the two tape drives.
Remove two Phillips head screws and lock washers from the bottom of the rear plate and one
flat Phillips head screw from the rear panel at the left side of the interface cable connector.

Remove the power supply assembly by lifting it out of the housing (thh internal cables still
attached) and placing it rightside-up next to the TUSS.
4.2.5 Rackmounting Procedure
The following procedure enables one person to install the TU58-DA in the rack using a number 2 Phillips screwdriver.
|
l.

With the power cord and interface cable removed (Figure 4-1), carefully place the TU58-DA
upside-down on a flat working surface so the front of the device is facing you.

Remove the rubber feet if attached by removing the screws that hold them in place (Figure
4-1). Refer to Figure 4-2 and align the two support brackets on the bottom of the TU58-DA
so they are flush with the left side. Fasten down the right side of each support bracket with
two screws and two lock washers.

4-2

WA G474

Figure 4-2

Installing Support Brackets

Fasten the mounting bracket to the left side of the TU58-DA with two screws and two lock

washers so the ball stud faces forward (bend in bracket toward center of TU58-DA). Install

the other mounting bracket in the same manner using two screws, two lock washers, and two

lock nuts to secure it to the support brackets (Figure 4-3).
Attach four U-Nut retainers (two per side) to the front vertical rails (Figure 4-4). Refer to
Figure 4-5 and position U-Nut retainers at the desired height for the TU58-DA.

Open the back of the rack. Attach four U-Nut retainers to the rear vertical rails (Figure 4-6).
If a non-DIGITAL rack is used, fasten the support bracket extenders to the rear vertical rails
with four screws, four lock washers, and four lock nuts. Use two per side in the top and bot-

tom holes (Figure 4-7).
Turn the TUS58-DA rightside-up and while supporting it with one hand, place it into position
in the rack.
NOTE
Be sure the mounting brackets are to the inside of
the rear vertical rails.
Fasten the mounting brackets to the front vertical rails with four screws and four lock washers (two per side in the top and bottom holes).

CAUTION
Install the two bottom screws first to avoid bending
the mounting ears.

For DIGITAL racks, fasten the mounting brackets to the rear vertical rails (Figure 4-6). For
non-DIGITAL racks, fasten the mounting brackets to the support bracket extenders (Figure
4-7).
10.

Attach the power cord and interface cable and connect to the appropriate device or receptacle. Close the back of the rack.

11.

Install the bezel by pushing into place over the ball studs (Figure 4-8).

MOUNTING BRACKET

-3

P s

| ;

2
g

MA.G473

Installing Mounting Brackets

[

U-NUT RETAINERS

"waaaflmoaaa

RO0T 0 o\

T OV I OGS IO D \\

JP 0P P

Jaanafiaao

Figure 4-3

MA-B4T72

Figure 4-4

Front Vertical Rail U-Nut Retainers

VERTICAL RAILS

2.22 |

(7/8) ,

1598

(5/3)“
3

?éagfs) fisf;g;
,

S—

TOP OF BEZEL

WIDE

o i

e——— NARROW

DT e

1.59 ¢:

(5/8)

)

FRONT VIEW

T
"“‘1

WIDE

. HOLE

SPACING

——— WIDE

4.76

BOTTOM OF BEZEL

(17/8)

BALL STUD

13.2

FRONT

(5.19)

34.3

(13.5)

3.81

“~(1.5)

44.5

(17.5)

|| 13?.2

(5.19)
S—

E_;g
*SUBJECT TO CHANGE

(18.0)

MEASUREMENTS ARE IN CENTIMETERS EXCEPT VALUES IN PARENTHESES

ARE IN INCHES.
MA-6478

Figure 4-5

Rackmounting the TU58-DA

REAR VERTICAL SUPPORT

%
o

o
o

o
2
?

MOUNTING BRACKET

o
Ve

MA.B475

Figure 4-6

Rear Vertical Support U-Nut Retainers

5O 9O 9SS

REAR VERTICAL SUPPORT

/%@

!
MOUNTING

SUPPORT BRACKET
EXTENDER

BRACKET

Figure 4-7

P
®

MA.B468

Fastening Support Bracket Extenders

4-6

MA-.6469

Figure 4-8

4.3

Installing the Bezel

RACK INSTALLATION (-CA Version)

4.3.1
Rackmount
|
The TUS58-CA rackmount unit mounts in 13.2 ¢cm (5.2 in) of standard 48.3 cm (19 in) width rack. It
should be located so that the 2 m (6 ft) power cord can reach a power controller outlet box such as the
DIGITAL 861 or any power outlet.
To get to the mounting holes, remove the bezel (Figure 4-9) by gripping it at the top and bottom with
both hands. Rotate it out from the bottom and lift it away. If the unit is installed in a recessed rack, the

bezel may be removed by gripping it with both hands on the left edge with fingers or thumbs inside the
storage well. Pull sharply out and swing the bezel away.

WARNING

Metal bezels are heavy!

If the rack requires them, install four U-Nut retainers at the holes spaced according to Figure 4-10. The
TUS8 is light enough for one person to install. Put the two bottom screws in first to avoid bending the
mounting ears.

N
/

Q
‘

%“,\

—

MA-2382

Figure 4-9

Bezel and Ball Stud

Four brackets and hardware are included with the TUS58-CA to support the back end of the chassis ina
rack. Use the two long brackets for DIGITAL cabinets. The short brackets are extenders for the long
brackets used in non-DIGITAL cabinets. Attach the long brackets to the chassis with the existing power supply screws, and attach to the side rails of the rack with the supplied clipnuts and screws. Hardware is also provided to fasten the extender to the long bracket if required. The bend on the long

~ bracket should point to the center of the rack while the bend on the extender should point to the outside
of the rack.

4.3.2 Power Selection for the Rack Version
Line cords for 110 V and 220 V and two fuses are supplied with the TU58-CA. The chassis power

receptacle meets European IEC standards. A switch on the back of the rackmount cabinet selects 110
Vor 220 V (Figure 4-11).

Set the switch to the correct value using a small screwdriver.
CAUTION
If the unit is plugged into a 220 V circuit while set
for 110 V, it may be severely damaged.

Install a fuse in the fuse post.
NOTE

A 3/8 Amp slow-blow fuse is required for 220 V, a
3/4 Amp slow-blow fuse for 110 V.

Insert the appropriate power cord into the receptacle. Do not plug it into an outlet until the

installation is complete.

FRONT VIEW

2.22

(7/8)

604

1.59 4

TOP OF BEZEL

(5/8) 1

;

286

(23/8)

(11/8)

1.50
$
:

WIDE

O e«

WIDE

(5/8)

WIDE

e« NARROW

—

BOTTOM OF BEZEL

1.11

8.0

(2.25

_¥

(0.375) % ‘(65125)

—

13 IEY

(5.19)

18,
(18.3)

"8?? l
?é? f}

16)

b,
1

46 5

438)
|
29y (0:438)

—

[©

L e

FRONT OF BOX (BEZEL REMOVED)

4365

*”"‘f
@

3.18

(1.25)

{ 1.438 ) ?

5.24
(2,96)_‘

(0.50)

48.3
(19.0)

13.2
(5.19)

FRONT

34.3

(13.5)

3.81

(1.5

44.5

{17.5)

13.2

(5.19)

+38.1

]
13.2

(15.0)

(5.19)

SUBJECT TO CHANGE

48.3

(19.0)
MA-2364

Figure 4-10

Rackmounting the TU58-CA

4-9

CABLE SHIELD
GROUND SCREW

o IIEE o 110/220V SWITCH
|

INTERFACE

FUSE POST
O)

D CABLE

CONNECTOR

LINE CORD RECEPTACLE

MA-2367

Figure 4-11

TUS58-CA Rear Panel

4.3.3 Removing Module from Chassis
Refer to Figure 4-12 and perform the following steps.
1.

Disconnect the power cord.

Remove the bezel.

Twist a coin or screwdriver in the gap between the retainer bar and the lip of the chassis. Lift
the bar out of the chassis and set it aside.

Pull the cage toward you a few inches and turn it to the right. Slide the module out an inch or
two and reach in at the back of the cage to remove the power and communication cables from
the module connectors. Remove the cage entirely from the chassis and put it on a stable work surface.

Reach in again at the back of the cage and remove the drive cables from their connectors on

the module.

Now slide the module out of the cage.
CAUTION

Be careful around the thin tachometer disk. It is easily bent (and its edge is sharp). If the disk gets bent
without creasing, it might be straightened with
pliers. Alignment is not critical, but it is better if the
disk does not rub against the optical sensor block. If
it cannot be aligned, or if it is creased, it must be
replaced.

Reinstalling the Module

4.3.4
1.

With the connector edge facing into the cage, slide the module partially into the cage along
the card guides.

Install the drive cables onto their connectors. Note that the drive cables cross each other,
with the left drive cable going to the right connector (as you look into the open end of the
cage).

4-10

MA-5264

Figure 4-12

4.
5.

Installing Cage and Retainer Bar

Place the cage partially in the chassis and run the power and communication cables up to the
module onto their connectors.
|

Slide the module all the way into the ’cagc and set the cage into the hooking tabs stamped

into the bottom of the chassis.

Align the retainer bar parallel to the floor of the chassis, with the spring on top. Engage the
two slots with the vertical sheet metal of the cage at the middle of the cutaways. Press each

end of the bar away and down, one at a time, so that the ends catch the lip of the chassis and
the bar holds the cage in place in the chassis. The module should sit in the cage with its edge
just clear of the retainer bar springs.
6.

Replace the bezel and power cord.

4-11

4.4

INSTALLATION (-EA AND -EB VERSIONS)

The TUSS-EA and -EB are tabletop units that require a minimum amount of space. Detachable line
cords for 115 V and 230 V and two fuses are supplied with the TU58-EB; only the 115 V cord and fuse
are supplied with the -EA. The cords are 6 ft long, enabling you to place the TU58 on a desk, tabletop,
or a convenient location within reach of a power outlet. See Paragraph 4.2.3 for the correct power selection information and Paragraph 4.2.4 for controller board configuration.
Tabletop Installation

4.4.1

Disconnect the power cord and interface cable from the rear of the TU58 (Figure 4-1).

Place the TUS58 upside-down on a flat working surface.

3. Install the four rubber feet using the four 1.3 c¢cm (1/2 in) Phillips head sérews to secure
them to the bottom plates (Figure 4-13).

Turn the TUS8 rightside-up and place it in the desired location.

Connect the power cord, interface cable, and cable shield wire to the rear panel.
Solid Mounting Installation

4.4.2

Perform steps 1 and 2 as above.

Install the four mounting brackets (bend facing the side of the TU58 housing) using the four
1.3 cm (1/2 in) Phillips head screws and lock washers to secure them to the bottom plates
(Figure 4-13).

Turn the TU58 rightside-up and place it in the desired location.

Ma.g6471

Figure 4-13

Mounting the TU58-EA and -EB

4-12

Fasten the unit to the mounting surface using four screws through the holes of the mounting
bracket bends.

NOTE
The four screws needed to secure the unit to the
mounting surface are not supplied with the TUSS.

Connect the power cord, interface cable, and cable shield wire to the rear panel.

4.5 INSTALLATION (-VA VERSION)
The TUS8-VA is a tabletop unit that requires a minimum amount of space and can be placed in

convenient location within reach of a dc power source. (See Paragraph 1.4.2 for power requirements
.)
In addition, the TUS58-VA can mount to the SB11 (or BA11-VA) if so desired.

NOTE
If reconfiguration is necessary, see Paragraph 4.2
before installing the TU58-VA.
4.5.1 Tabletop Installation
See Paragraph 4.4.1 for installation procedure.
4.5.2 Solid Mounting Installation
See Paragraph 4.4.2 for installation procedure.
4.5.3

Mounting the TU58-VA to the SB11 (or BA11-VA)
1.

Attach the four rubber feet to the TU58-VA as described in Paragraph 4.4.1, steps 1 through
4. (If solid mounting is desired, order hardware kit PN 70-16753-00).
’

Place the SB11 (or BA11-VA) upside-down on a flat working surface.

Remove the rubber feet from the SB11 (or BA11-VA) if attached by removing the screws
securing them to the bottom. Fasten the four brackets to the bottom (bend on the outside

edge) using four screws and lock washers (Figure 4-14).

Position the SB11 (or BA11-VA) rightside-up over the TU58-VA so the mounting brackets
line up with the holes on the side of the TU58-VA. Fasten to the TU58-VA using four screws
and lock washers (Figure 4-14).

Referring to Figure 4-15, connect the interface cables and power cord to their respective locations.
4.6 COMPONENTS
|
|
Figures 4-16 and 4-17 provide the mounting dimensions for the circuit board and drive mechanism.
The
drive has a 19 cm (7.5 in) cable which plugs into the board connector with the wires coming out
of the
plug toward the center of the board. The plug is keyed to ensure proper orientation. The cartridge
extends 1.60 cm (0.62 in) from the front of the drive. If the drive is recessed in a panel, clearance must
be
provided around the opening for fingers to grip the cartridge. Ideally, the cartridge slot in a front
panel
is somewhat larger than minimum, to allow easy insertion. The opening should be at least the dimensions of the cartridge, 1.3 cm (0.5 in) X 8.1 cm (3.2 in), located not more than 0.53 cm (0.17 in) above
the bottom mounting surface (line A in Figure 4-16). The drive must be free to float on its mounting
screws, so bezels or panels must not touch the drive.

4-13

* 4 MOUNTING BRACKETS
- AND SCREWS WITH

LOCKWASHERS FOR MOUNTING

TOBA11VAORTO
HANG MOUNT

SCREWS WITH LOCKWASHERS FOR r

METAL BRACKETS WITH
USE
10 32x1/2 INCH SCREWS FOR

| SOLID MOUNTING

MOUNTING TO THE TU58 VA

HARDWARE KIT

DEC P/N 70 1675300

USE RUBBER FEET

WITH 10-32 X 1/2 INCH
SCREWS FOR TABLE
TOP MOUNTING

* MOUNT BRACKETS TO BA11VA (SB11) FIRST.
MBA.4333
MA-6641

Mounting Choices for the TU58-VA

Figure 4-14

SB11 OR

BA11-VA

CPU SLOT

KD11-HA

MXV11-AC

%
.

SERIAL LINE

UNIT (SLU)
GROUND
SCREW

o gig;cg
OPTION
SLOT 4

R5.232.C OR RS423

CONNECTOR ONLY

FOR EIA USE (CONSOLE)

INTEREACE
|

(orREQUIV-

« ALENT)

GROUNDWIRE

TO DC SOURCE

o\ ga11.vA,

TUS58-VA

OR SB11

\R.4334
MA-6E4L2

Figure 4-15

Interfacing the TUS8-VA

fi §

me)

1046

(4.12)

523

(2.06)
L

9.68

J‘

(3.812) "

| & [

818

(3.22)

o1 (19) | [ l‘@é

(2.250) TYP

513

(2.02)
1

L
e

1.60
(0.62)

2.361

8255

(.93)

—i——n

(1.43) ?‘*22}

\-DEC TUS8-K CARTRIDGE
==

L2k

<+-3.50

MEASUREMENTS ARE IN

(1.38) DIA

8.89

(3.50)

7?1

CENTIMETERS EXCEPT

VALUES IN PARENTHESES

ARE IN INCHES.

MA-2369

Figure 4-16

Drive Outline Drawings

4-15

1.27

(.50)

(9.79)

14.76

| -G p

HEAT SINK:

(5.82)

e A3 ee T T T‘

—

? 152

| 1 lee
.l
8
o le—
68
(.27)

1.27
501

14,64

(6.77)

17.73
(6.98)

SERIAL INTERFACE

CONNECTOR

g6
14.72
f—

ooLt
]
‘
N
10
=

24.13
9.

(9.80)

MEASUREMENTS ARE IN CENTIMETERS EXCEPT VALUES IN PARENTHESES ARE

MEASUREMENTS ARE *.013 (.005) CENTER TO CENTER

13.18
(6.19)

142.;?
(4.85)

12.24

(4.82)

[
gl tt

(.04)

24.72

(9.73)

;

WITH #87124-1 CONTACTS

‘——'—*I 112
POWER
HEAT/
3| |GND coNNECTOR
,
SINK
pRIvVEQ _ DRIVET
B |5
'/ AREA//)

r‘ (.19)

’

AMP HEADER #87633-6 AMP #87272-8 06-04
DECPT #12-135
MATE: AMP #87159-6
WITH # 87027 CONTACTS MATE: AMP #87133-5

3.0 (1.2) ABOVE
0.5(0.2) BELOW

406
S(.6)

|
58
(.23)

IN INCHES

Figure 4-17 Board Outline Drawings

and 1 cm (3 /8 in) standoffs.
surface with 3 mm (4-40) hardwarethe
The board should be mounted on abeflatmount
drives to a surface above
ing
ed at any angle. For mount
Both the board and the drive may nce is requir
outline drawings. For
the
in
hole spacing is given
the drives, 1.80 cm (0.71 in) cleara the drivesed;, an
cm (3.50 in) chassis
8.89
X
8.18 cm (3.22 in)
mounting the drives to a surface below
cutout is required, with the same mounting hole spacing.
CAUTION

The mounting surface for the drives must be flat
within 0.64 cm (0.025 in).

, and flat washer for
each drive. There is a shoulder screw,onspring
Mounting hardware is included with
flatness specificathe
to
4-18 shows one assembly; in additishoulder screw
each of the four mounting holes. Figure
in the mountis a specification for the depth of the should meet the
tion for the mounting surface, thereessio
top of the
n of the spring, the shoulder screw at the screw’s diame
ing surface. To prevent extra compr mount
ter of
ing hole must be limited so that
the
mounting surface. Any tapering of the
e.
surfac
below
in)
(0.030
0.419 cm (0.165 in) the edge of shoulder is not more than 0.076 cm
P
4.7 INTERFACE STANDARDS SELECTION AND SETU
transmission rate of 38.4K baud and the RS-

alled jumpers for a
The TUS5S is shipped with factory-inst
ed by changing the jumpy of standards and rates may be selectboard
473 unbalanced line interface. A varietprovid
and their functions,
a list of all the pins on the
ers on the controller board. Table 4-1interface,es and
power connectors.
including the wire-wrap (WW) pins,

4-16

THE MOUNTING

SURFACE FOR THE
DRIVES MUST BE FLAT
WITHIN 0.64 mm.

(0.025 in.)

MOUNT ON 0.19mm.

(0.075 in.) MAX THICKNESS FLAT SURFACE

WITH 6-32 NUTS, ON

6-32 THREADED
SPACES, OR ON 6-32
THREADED INSERTS.

0.076mm. (.030 in.)
MAX PENETRATION

OF SHOULDER INTO
MOUNTING SURFACE.

FOUR ON EACH DRIVE

Figure 4-18

MA.67564

TUS58 Drive Mounting Hardware

4.7.1 Selecting Interface Standards
The serial interface operates on full-duplex, asynchronous, 4-wire lines at rates from 150 baud to 38.4K
baud. The transmit and receive rates may be independently set. Each 8-bit byte is transmitted with one
start bit, one stop bit, and no parity. The line driver and receiver may be set to operate in accordance
with EIA RS-422 balanced or RS-423 unbalanced signal standards. When set to RS-423, the TUS8 is

compatible with devices complying with RS-232-C.
The TUS8 is shipped prewired for operation at 38.4K baud transmit and receive on RS-423. The maximum wire length that may be used at that data rate in an electrically quiet environment like an office
is approximately 27 m (90 ft). The wire used with any installation should be no less than 24 AWG
diameter.

Longer wire runs may be made if data rates are reduced. RS-422 is considerably more noise-immune
than RS-423 and can be used over at least 1200 m (4000 ft) at any TUS8 data rate. Figure 4-19, derived from the EIA standards, illustrates the variations in distance needed by RS-423 for different data
rates. For more information, consult the standards for RS-422 and RS-423 published by the Electronic
Industries Association.

4-17

Table 4-1 TUS58 Module Connections
|

Wire-Wrap Pins

150 Baud
300 Baud
600 Baud
1200 Baud
2400 Baud
4800 Baud
9600 Baud
19200 Baud
38400 Baud

WWI
WW2
WW3
wWWw4
WW5
WW6
WW7
WWS§
WW9

WWI10
WWI1

WWi12
WWI13

UART Receive Clock Input
UART Transmit Clock Input

connector pin 1)*
Auxiliary A (to interfacee conn
ector pin 10)*
rfac
Auxiliary B (to inte

WWwWi4

Factory Test Point

WW16

Boot

WWI15

Ground }

WW17

RS-423 Driver

WWI19
WW20
WW21
WwWWw22

Transmit Line+
Transmit Line—
RS-422 Driver+
RS-422 Driver—

Connect together for auto-boot
on power-up.

RS-423 Common (Ground)

WWI18

Receiver Series Resistor
(Jump for RS-422)

WWwW23 }
WW24

Serial Interface Connector

J2-10
J2-9
J2-8
J2-17
J2-6

Power Input Connector

connection)

J1 -1
J1-3
J1-5
J1-6

+12V
Ground
+5V
Ground

Drive Cable

Cart L
No Connection
Permit L
Signal Ground
Motor +
Motor —
+12V
Tachometer

J3,4-1
J3,4-2
J3.4-3
J3,4-4
J3,4-5
J3.,4-6
13,4-7
J3,4-8

J2-5
J2 -4
J2-3
J2-2
J2 -1

Auxiliary B
~ Ground
Receive Line+
Receive Line—
Key (no

J3,4-9
J3,4-10
J3,4-11
J3,4-12
J3,4-13
J3,4-14
J3,4-15
J3,4-16

* For optional use, such as timing signals from baud clocks.

4-18

Ground
—
Transmit Line

Transmit Line+
Ground
Auxiliary A

LED

Head Shield Ground

Erase Return
Erase |
Erase O
Head Return
Head 0
Head 1

1200

300

150

500

4,%

\Q‘“@
W\@,?

CABLE

LENGTH

)

100

2
N

300

600 1K

10K 20K 40K

DATA RATE IN BAUDS
RS-423
MA-2368

Figure 4-19

Data Rate and Cable Length for RS-423

4.7.2 Connecting Standards Jumpers
The jumper pins are standard 0.635 mm (0.025 in) wire-wrap posts which may be connected
using 30
AWG wire and a hand tool. Other techniques that may be used include slip-on connectors,
such as
DIGITAL 915 patchcords, 917 daisy-chain, or soldering.

The baud rates may be set independently for transmission and reception, or both can operate
together.
Simply connect the pin with the desired baud value to either the XMIT or RCV pins or
both. Figure 420 illustrates the pin locations, and Figure 4-21 the factory-wired configuration.

The interface standards may be selected by connecting sets of pins together. The connections
are listed
in abbreviated form in Figure 4-20. The group of pins 17 through 24 are the interface pins.
The module
is shipped prewired for RS-423 with pin 17 connected to pin 19, and pin 18 connected
to pin 20. No
other pins in the group are connected.
For RS-422, pin 21 should be tied to pin 19, pin 22 to pin 20, and pin 23 to pin 24. No

group are connected.

other pins in the

4.8 OPERATIONAL CHECKOUT
A confidence check of the operation of the newly installed TU58 may be performed through
the console
or keyboard console emulator of a host system without the use of an operating system
device handler.
The light on the TUS8 board should be on, indicating a functional processor.
4.8.1
Checkout of Interface
|
|
To address the serial interface device registers with the console (consult the system manuals

and codes), perform the following steps.

Set the transmit control status register to send Break to the TUSS.

Remove the Break condition.

Transmit INIT: 04 (octal) to the TUSS.

Transmit a second 04.

Examine the receive data buffer to find Continue: 20 (octal)

4-19

for address

END VIEW

DIAGNOSTIC

LED

cim

S
st [H]
ao
— eocr+‘;”6

Oz |

WW
+0
15

+
300
6004

”

1200+
0+
240

=1 ! 4800+

9600+

192K+

384K+

@ | RCV4CLK

2321 17-19
21-19

20
2223-24

XMIT 4+CLK
R

18423118-20

422

:&5

24++++++++17

wlelnjvlw=
eiElElx|

Auxs-g-‘;“gw

©-

1
j !:-:..j
«

| ©I
=3c |_J|

1y]
[ ]

&
W

)
il

MA-2366

ons

Figure 4-20 Interface Selection Jumper Pin Locati

4-20

QB%DC}BDDDD

38.4 KBAUD RCV + XMIT RS-423

MA-2383

Figure 4-21

4.8.2

Factory Wiring

Checkout of Drive Command Function

Insert a tape cartridge into drive 0 (left side). (The TU58 should have sent Continue (20g)
already.)
Transmit the following string of octal numbers to the TUS58. (Consult the programming chapter
for an explanation of this format.)

S S

OO COOOCODOoO NN

204
212

The TU58 should wind to the beginning of the tape and read about half of the tape. If it does not work,
see Table 2-1, under “TUS58 does not respond to host.”

4-21

CHAPTER 5

OPTIONS

5.1
RUN INDICATOR
|
Each tape drive may have an LED indicator which lights to show tape motion. Since data loss can
occur if a cartridge is removed while the tape is being written, the cartridge should not be touched if
the indicator is on.
S5.1.1
[Installation
The indicator (which may be any device capable of handling 30 mA with a forward voltage less than 1.8

V) 1s wired in series with the tachometer source indicator. Splice the run indicator into the wire from
pin 7 of the drive connector. (Count from the end with the missing pin; that pin is number 2.) The anode

should be on the board side of the wire (symbol arrow pointing away from pin 7, Figure 5-1). The indicator is available from DIGITAL (PN 11-10324), and wires with slip-on connectors are available to
join the indicator to the tach (cable number 70-16526) and to extend the board connector end to the
indicator at the front of the drive (cable number 70-16525).

TOPIN7

ADDED

+12V

TACHL '

MCJ

PIN 8
PINO
MA-2388

Figure 5-1

Installation of Run Indicator

5-1

5.2

BOOT SWITCH

General

5.2.1

Special provision has been made for interfacing the TUS8 to the LSI-11 ODT keyboard interpreter.
The TUS8 is placed at the system console address and vector, permitting it to “type” in a program
using keyboard ODT. This means that a keyboard cannot be connected at the same time. This arrangement is useful in an unattended control system, where the TUS8 can automatically load and start ora
reload and restart an unsupervised process controller or similar application. The Boot switch allows
manual reboot without powering down to cycle the automatic sequence.
NOTE

Boot mode does not work in any DIGITAL oper-

ating system environment.

Operation

5.2.2

When the boot switch is connected according to Paragraph 5.2.3, the TUS8 operates in the following
manner.

1. On power-up, the TU58 checks for the presence of the closed switch. It then delays’ one second and begins the boot procedure.

When the TUSS is in the idle state, it monitors the Boot switch. Any switch contact openclose sequence causes a one-second delay (to allow for contact settling or to allow the host
processor to enter the halt mode), and then the TU58 begins the boot procedure.

ASThe boot procedure positions the tape in drive 0 to block 0, sends Break to the host, and transfers
echo
the
for
allow
to
s
character
between
inserted
is
delay
A
host.
the
to
CII characters from the tape
from the LSI-11. If the character sent is ASCII 0 — 7, this delay is one character time at 9600of baud.
~ Any other character is interpreted as a control character, and time is allowed for 15 characters g)echo.
The TUS58 exits the boot mode following the transfer of the terminating character ASCII G (147 and
enters the idle state. Because of the timing requirement, only rates of 9600, 19.2, and 38.4K baud may
be used with boot.
5.2.3

Installation

The boot pin on the board (WW16) may be connected to ground through a normally closed momentary
action switch. Wires may be wire-wrapped, DIGITAL 915 patch-corded, or soldered to the pins. Placement of the switch and lead dress are not critical if adequate clearance is provided around moving parts
of the drive and the heat sink and power resistors on the module.

The boot tape contents are formatted to appear to the LSI-11 as output from a console (keyboard)
operating under the ODT keyboard interpreter.

5-2

APPENDIX A

TUS8/PDP-11 TOGGLE-IN BOOT

This boots drive 0 only.

1000/012701
1002/176500
1004/012702

1006,/176504
1010/010100
1012/005212
1014/105712
1016,/100376
1020,/006300
1022/001005
1024,/005012
1026,/012700
1030/000004
1032/005761
1034/000002
1036,/042700
1040,/000020
1042/010062
1044,/000002
1046,/001362
1050/005003
1052/105711
1054/100376
1056/116123
1060/000002
1062/022703
1064,/001000
1066,/101371
1070/005007

APPENDIX B

"NEWTAFE®"

RSF

RSP SEQUENCE

Seauence

Checksum

Calculation

Examrle

carrugs

)
0
0
0

0
0

SEEK

RLOCK

777

Octal

Addition

0
377

1
———

377

0000101000000010
0000000000000101

2
12

o
+

O
0
0
0
ey

0000000111111111
*****************

Binary
Addition

0000000000000000

0
G

0000000000000000
0000000000000000

SEEK TO

BLOCK

0000110000000110

S~
14

6
\

”‘

APPENDIX C
SAMPLE DEVICE HANDLERS

CCCCCCCCCCCCCCeeceeeceeceeeleeeceeeCeececCeCeCctCCeCcecCCecCCCeCeCeCeCeeecceece

nnnnnnnmnnmmnnnmnnnmnmnnnnnnmnnnmnmnmmnnnnnnnnnnnnnm

TTTTTTT
T

U
u

U 5555555
Uus

Uus

T
T

UUUUUUU

88888

555555

C
F

88888

555555

ORTRAN

UPPORT

C
C
C

ACKAGE

|
|

88888

c
C

CCCCCCCCCCCeCcCCcecececeeeeeeecceceecccecececeecceeeceeececeeececececececceceeecec

The

following

handler

used

with

can

program

package

the

RT=11

puilt

into

program

lerror

"bytecount"

bytes

"unit"

the

TUWRIT(

all

four

codes,

ierror

value

TUS8
notea

the

TUS58

tne

the

area

and

When

object=time

LSI=11

system,

microcomputer

callable

"block"

bytecount

the

"unit",

data

entry

points:

)

the

cartridge.

)

area

starting

specified
at

tne

random=

"block",

)

cartridge

block

located

specified

drive

"unit"

"block",

)
TUS8

cases,

internal

the

controller

functions

return

diaanostic

follows:

meaning

Normal

Success,

-1
-2
-8

device

IV,

TUS8 drive specified by
specified by "bpuffer",

block

from

drive

TUS8

FORTRAN

bytecount

buffer,

oytes

block

random-access

TUDIAG(
Run

block,

unit,

Position

onto

block

TUSEEK(

the

unit,

complete

based

from

data

random=access

"bytecount"

access

compiler

bufter,

unit

"buffer"

ierror

block,

into

PDP-11

user=program

Read

write

lerror

four

unit,

starting

ierror

ROM/PROM/EPROM

implements

TUREAD(

contains

entirely

FORTRAN

applications.
The

listing

written

error

standard

function.

set

error

code

success

but retries were required
TUS8 fajiled self-test (TUDIAG)
Partial operation (end=of=-medium encountered)
Invalid unit nurber was specified

-9

-11
-17

Specified cartridge
Data check error on

cartridge

mounted

specified

drive

is write=protected
cartridage

(TUWRIT)

aNnOOOnaaOOnNnOOO0On0 OO0
0

-32
=33

Seek error (block not founao)
Motor stopped (TUS8 hardware error)

-55
«127

Invalid record number (bad block number passed)
Communications error between host and TUSS

Invalid operation code (error in this program)

=48

This software assumes that the TUS58 controller is interfaced

through a DLV11, DLVil=J, DLVii=¢, DLVI1=F, or MXVil intertface

which has a receiver CSR address assignment of 176500(8).

The software operates the interface in a non=interrupt=-driven
mode only for

simplicity.

This program is neither licensed nor supported by Digital

Equipment Corporation, and may be copied or modified for use
on any computer system, Diagital assumes no responsibility for
its reliapility on any hardware, Digital=supplied or otherwise,

cceceeeceeeeceecccececeecececeeceeecceceecceeeccccccecccecccececcceccccccceccc

aQOan

INTEGER FUNCTION Tudiag

Runs TUS8 controller diagnostic function, returning success
function result,

code as

oNeRP]

IMPLICIT INTEGER (a=7)
COMMON /cmdpkt/ packet(6)

Initialize a command packet with the DIAGNOSE operation code,
Tudiag =

Qa0

Init(7)

(Tudiaa.ne.0) GOTO 100

Now transmit the packet to the TU58 controller,

s EeEe

CALL Sndokt(packet,12,0)

And ask for the results of the diaanostic in the end packet,
Tudiag = Getend(0)

100

RETURN
END

OO On

INTEGER FUNCTION Tuseek( unit, block )
Positions cartridge in "unit" to random=access block specified
by "block", returning the success code from the TUS8 controller

the

function

result.

IMPLICIT INTEGER (a=2)
COMMON /cmdpkt/ packet (6)

Initialize a command packet with the POSITION operation code
Tuseek

Init(5)

IF (Tuseek.ne,0) GOTO 100
packet(3) = unit
volocCk

2NeRe

Transmit the command to the TUS8 controller

OoaOn

packet(6)

And ask for the status of the operation from the end packet

CALL Sndpkt(packet,12,0)

Tuseek
100

RETURN

END

= Getend(0)

QOO non

INTEGER FUNCTION Turead( unit, block, buffer, bytent )
Reads

into

"obytcnt"

the

access

code

data

block

from

oytes

area

from

"block"

the

specified

TUS8

the

TUS8

drive

cartridge,

controller

selected

"buffer",

the

starting

Returns

function

"unit"®

the

random=

success

result,

oRoNe!

IMPLICIT INTEGER (a=2z)
BYTE buffer(bytcnt), bword(2)
COMMON /cmdpkt/ packet (6)
EQUIVALENCE

(iword,bword)

Build

command

READ

packet

and

send

the

TUS8

controller

Turead

= Init(2)
(Turead.ne.0)

packet(3)

GOTO

500

unit

packet(5)

bytent

packet(6)

bplock

e EeXe'

CALL Sndpkt(packet,12,0)
index = 1
Read

the

data

packet

from

the

TUS58

chksum

= Getbyt()
(chksum.ne,"001)

datcnt

chksum
odd

100,

odd

Getpyt()

chksum

GOTO

400

!Proceed

400

for

end

not

data

packet

datcnt¥2%56

i=1,datcnt

,not.odd

(GdthQQO)

bword(2)

GOTJ

S50

bword(1) = Getbyt()
buffer(index) = bword(1)

100

GOTO

bword(2)
hksum

100

Getbyt()

Check(chksum,iword)

buffer(index)

index

(odd.ne.0)

pword(2)

1
chksum

bword(1)

bword(2)

Getbyt()

(chksum,ne,fiword)

GOTO

Found

packet

Turead
RETURN

which

(
Check(chksum,iword)

GOTO

%00

not

data

packet;

unit,

block,

buffer,

area

specified

try

packet

Getend(chksum)

END

IeEe
e EeKe!

INTEGER
Writes
to

FUNCTION
"bytcnt"

TU5S8

drive

Returns

Tuwrit(
bytes

"unit",

success

code

from

data

starting
from

TUS8

bytcnt
by

random=access

controller

)

"puffer"

block

function

"block",
result,

IMPLICIT

INTEGER (a=2)
buffer(bytcnt), bword(2)
COMMON /cmdpkt/ packet(6)
EQUIVALENCE (iword,bword)

OOn

BYTE

Construct
Tuwrit

wRITE

Init(3)

(Tuwrit,.ne,0)

packet(3)

command

GOTO

unit

packet (5)

bytcnt

packet(6)

= block

CALL

S00

Sndokt(packet,12,0)

packet

and

transmit

the

TUS8

000

datcnt

bytent

Prepare to transmit a new data packet by checking for CONTINUE
flag

chksum = Getbyt()

!Proceed to 400 if not CONTINUE
!Transmit data packet flag
IMmake packets maximum 128 bytes
!Output byte count for packet

IF (chksum,.ne,."020) GOTO 400
CALL Putbyt(®*001)
count = MinO(datcnt,128)
CALL Putbyt(count)

CALL Sndpkt(buffer(bytcnt-datcnt+1),count,count¥256+"001)
datcnt = datent
GOTO

= count

Received flag was not a CONTINUE,
00
500

Tuwrit = Getend(chksum)
RETURN
END

INTEGER FUNCTION Check(

aOan

Try for END packet,

3§

)

Computes 16=-bit checksum of i and j, using end=-around carry
Sum is returned as function value,
technique for TUS58,
INTEGER

(a=2)

IMPLICIT

s Ne NNy

aOOn

check =

1f neither input operand has high=-order bit set, no carry
is

possible

(

) GOTO 200

(i.or.3).ge.0

1f both inputs have high=order bit set, a carry is always
generated

IF (

AnNnaOon

(i.and.3).1t.0 ) GOTO 100

If only one has high-order bit set, then a carry occurred
only if the sum does not have its high=-order bit set
)

GOTO 200

aon

IF( check,1t.0

Perform end=around carry if required

100

check = check + 1

200

RETURN
END

sNeoNgNe!

INTEGER FUNCTION Gethyt

Gets next byte from the serial interface connectinag the
TUS8 controller

OO0

IMPLICIT INTEGER

(a=2z)

wait for input character available (DONE flag set)

(Ipeek("176500).and."200).eq.0 ) GOTO 10

IF (

Get character from data puffer and remove extraneous bits

I SNe

to the host machine,

WRITE(6,222)GETBYT
FOKMAT(® R”,03)

Getbyt = Ipeexk("176502),and,255

RETURM
END

SUBRKOUTINE

QOO

OO0

aaonn

BYTE

outbyt

)
k.

Writes

byte

controller

the

serial

host

interface

INTEGER

wait

for

output

(Ipeek("176504).and,."200).eq,0

(

Transmit

connecting

the

TUSSB

machine,.

IMPLICIT

CALL
N O

Putbyt(

OUTBYT

(a=z)
interface

character

ready

moving

(DONE

)

bit

set)

GOTIO

data

buffer

Ipoke("176506,0utbyt)

WRITE(6,222)0UTBYT

FORMAT(®

T7,03)

RETURN
END

oo Ne Ne'

INTEGER

FUNCTION

Initializes
Returns

TUS8

Initialize

Init

packet(5)
agoaoon

packet(6)

aOaOn
aaOnn
L=

Set

otherwise,

packet

area

with

opcode

specified

10%256

"002

opcode

allow

eight

retries

entire

initialization

J=1,8

BREAK

bit

output

serial

CALL

Ipoke("176504,"000001)

Wait

for

CALL

interface

(XCSR)

BREAK

transmitting

N
RN
aann

50,

to cause framing error in TUS8
eiaht NUL characters under it

Putoyt("000)

Remove

CALL

s Nelg

=127

procedure

aQnNnan

operations.

(a=2z)
packet(6)

command

HHunuu

packet(2)
packet(3)
packet(4)

50
C

for

initialized,

packet (1)

Loop

)

Lo Bl e Y o B o

sNeoNe

/cmdokt/

opcode

controller

properly

IMPLICIT INTEGER

CO¥MON

Init(

BREAK

condition

output

interface

Ipoke("176504,"000000)

Diséard any (possioly erroneous) charac;er in input buffer
idummy

Output

two

Ipeek("176502)
INIT

commands

CALL

Putbyt("004)

CALL

Putbyt("004)

wait

for

Getbyt().eq."020

(

CONTINUE

check

for

TUS8

CONTINUE

)

GOTO

controller

flag

100

response

1f no success after eight retries, report error
100

Init = =127
RETURN
END

sReNeNpRY!

SUBROUTINE Sndpkt(buffer,bytcent,chkini)
Transmits a command or
sending "bytcnt® bytes
checksum,
Checksum is

data packet to the TU58 controller,
from "buffer", followed by the updated
initialized from the "chkini" argument,

IMPLICIT INTEGER (a=z)
BYTE buffer(bytcnt), bword(2)
EQUIVALENCE (iword,bword)
chksum

Qa0

odd

Loop

chkini

transmit

packet

s Nelp!

DO 100, i=1.bytcnt
odd = ,not,.odd
IF (odd,eq.0) GOTO

nanoon
= MO

one

byte

time

1f an odd=numbered byte, remember it for checksum calculation
bword(2)
bword(1)
GOTO 100

=
=

0
buffer(i)

Perform checksum
numbered byte

calculation

bword(2)

chksum

Check(chksum,iword)

either

CALL

IF
sNeRe

contents,

for

each

byte

pair

even-

buffer(i)

case,

output

byte

interface

Putbyt(buffer(i))

(oad.ne,0)

Output

chksum

computed

Check(chksum,iword)

checksum

for

packet

iword = chksum

CALL Putbyt(bword(1))
CALL

Putbyt(bword(2))

RETUKN

END
eNele

INTEGER FUNCTION Getend(chkini)

Reads an end packet from the TU58 controller, returning
as the function value the success code from the packet,

)

IMPLICIT INTEGER (a=2)
BYTE bword(2)
EGUIVALENCE (iword,bword)

OO0 n

chksum = chkini
If input checksum
already pbeen read

is
by

not

the

IF (chksum,ne,.0) GOTO
chksum = Getbyt()

Check

for

valid

END

zero,

first
caller.,
1t

byte

of packet has
the *chkini" value,

packet

structure.

(chksum.,ne,®"002)

GOTO

500

IMust

have

flag

(Getbyt().ne,10)

GOTO

500

!Must

have

byte

count

(Getbyt().ne,"100)

!Must

nave

opcode

GOTO

500

C-6

COMMAND
=

END

annooOon

valld

store

packet

tound,

read

Getend

Getbyt()

chksum

Check(10%256+"102,Getend*256)

Read

and

discard

remainder

C
DO

100
C
C

100,

Getbyt()

bword(2)

Getbyt()

Read

packet,

uprdating

compare

with

byte

and

checksum

= Check(chksum,iword)

transmitted

checksum

C
bword(1l)

bword(2)

Getbyt()

code

i=1,4

bword(1)

chksum

C
C

success

(iword.eg.chksum)

Indicate

checksum

500

Getend

=127

600

RETURN

GOTO

computed

value

600

transmission

and

error

END

TuUSB

NON=INTERRUPT

DRIVEN

TUSH

/0,1/

HANDLER

ME WE RE BE WS WR R WE WP Re W W W we W TR WG W NG U ME RE NG R WE We S NS NE R WE e %e ME We e NG s NE e e Be e

.TITLE
+IDENT

The

following

handler
The

program

package

proaram

listing

written

implements

IERROR

contains

PDP=11

four

UNIT,

BLOCK,

Read

"BYTECOUNT"

bytes

from

unit

"UNIT"

the

starting

IERKOR

TUARIT(

write

block

UNIT,

onto

noted

IFRROR

BUFFFR,

block

BLOCK,

bytes

TU58

from

drive

TUSB8

entry

Run

all

codes,

the

cases,
as

"BLOCK"

BUFFEP,
the

"UNIT",

data

the

TUSEEK(

UNIT,

BLOCK

TUDIAG(

area

starting

)

specified

the

random=access

)

"UNIT"

the

)

TUS8

internal

the

functions

controller

return

VALUE

diagnostic

standard

MEANING
Normal

Success,
TUS8

out

failed

STATUS

retries

Partial

operation

Invalid

unit

cartridge

-11
-17

Specified
Data

check

.32

Seek

error

-33

Motor

were

self=-test

-2

set

function,

status

CODFK

success

-8

-9

cartridge,

"S8LOCK",

-1

)

BYTECOUNT

follows:

IERROR

points:

BYTFCOUNT

Position the TUS8 cartridae located in drive
random=access block specified py "BLOCK",
IERROR

device

lanquage,

the TUSE drive specifie] by
area specified by "RUFFFR",

data

random=access

"BYTECOUNT"

"BUFFER"

complete
assembly

FORTKRAN=callable

TUREAD(

into

MACROD

required

(TUDIAG)

(end-of-medium

encountered)

number

was

in specified drive
is write=protected (TUWRIT)
cartridae

mounted

cartridoge
error

specified

(block not found)
stopped (TUS® hardware

C-7

error)

W
we

=55
-127

Invalid operation

Invalid record
Communications

’

code

(error

this

proqgram)

number (bad block number passed)
error between host and TUSS

This

software assumes that the TUS58 controller is interfaced
through a DLVii, DLVii-J, DLVil1~E, DLVil=F, or MXViil interface
which has a receiver CSR address assianment of 176500(8),
These
subroutines were written with a goal of readability, time and
space pertormances are not optimal.
|

This program is neither liscensed nor supported by DIGITAL
Equipment Corporation, and may be copied or modified for use
on any computer system,
Digital assumes no responsibility
for its reliabjlity on any hardware, Digital=-supplied or
otherwise,

WE O ME

Wil

=48

Define

sSymbol

packet

flag

Definitions

byte

and

Data

Area

codes

Define

F.DATA

1
2

F.CIRL
F,INIT

INIT

F.CONT
F.XO0FF

=
=

20
23

:
:

CCONTINUE packet
XOFF packet

Control

packet

;

Data packet
Control packet
packet

op=codes

«SBTTL

Define

O0.READ

;

perform

read

O.WERFIT

;

perform

write

0.PGS

;

perform

seek

0.PIAG

perform

O.ENMD

100

}

racket

controller

interface

address

operation
operation

operation

self~test

End

packet

assignment

DLRCSR

176500

DLRBUF

DLRCSR+2

DLXCSR

DLRCSR+4

DLXBUF

DLRCSR+6

: Macro to send
a byte to TUS8
LAB:

.MACRO
TSTR

PUTBYT
ARG,
@#DLXCSR

BPL

LAB

Move

ARG,

+ENDM

PUTBYT

Macro

wait

NOTE:

ARG

Into

the

for
is

R#DLXBUF

?LAB

byte

from

high=byte

the

GETBYT
@#DLRCSR

BPL

LAR

MOVR

@¥DLRBUF,

Data

will

sign=-extended

ARG

GETBYT

area

.ENDM

bit

?7LAB

ARG,

.MACRC
TSTB

parjity

reqister.

;

LAB:

TUS8

the

.PSECT
:

Area

;
PACKET:

;

dord

used

USERSD
build

Rw,

Control

,BYTE

F.CTRL,

+WORD

used

collect

LCL,

REL,

packets

10,

CON

Control

packet,

length

byte=vairs

for

16=-bit

checksum

calculation

10,

«BLKW
¢

Pure

(RUm=able)

code

follows

H
.PSECT

USERSI

Rw,

.SBTTL

TURFEAD

Read Data From TUSS

LCL,

REL,

CON

TUREAD

H
;s

Description:

See

module

heading

Inputs:

(

O(R5)

points

five

word

stamdard

2(R5)

address

unit

4(K5)

address

block

;

6(R5)

address

8.(R5)

callers

H
s

Outputs:

FORTRAN

address

16~-pit

number

status

block

byte

number

word

input

of bytecount

arqgument

buffer

word

code

TUREAD::

Build

CALL

INIT

TST

initialize

BNE

508

;

return

Control

error

the

TUSS

occured,

error

caller

packet

H
#0.READ,

W2(RS),

PACKET+2

PACKET+4

MOV

@8, (RS),

PACKET+8,

MOV

@4(KS5),

PACKET+10,

MOV

#PACKET,

MOov

#12.,

CLR

CALL

SNDPKT

the

;

store

7 store

{is

"READ®

unit

number

byte

count

block

number

TUSS8

F0O

points

ki1

R2 =
send

Fk1

packet

store

Wme

Control

operation

the

packet

number

of cytes to
Initial checksum

the

Receive zero or more Data packets from TUSSE,

Control

followed

send

nacket
an

End

packet,

SwAR
B1S

SWwAB

CLR

COM

BEQ

20s

CLR

#0ORD

GETBYT

WORD

MOVB

WwORD,

308

(R1)+

GETRYT

wORD+1

ADD

wORD,

ADC

MOVE

WURD+1,

(R1)+

Data
End

nacket,
packet

count

from

TUS8

hi-pyte
initial

cnecksum
checksum

restore

packet,

buffer

TUSS

current

Data

callers

from

form

characters

the

byte

count

even/odd

updating

byte

flip-flop

checksum

received.

flip

flaa

wE we we

byte

puild

ne W

characters

a
for

store

branch

with

second

data

character

callers

second

byte

pair

with

store

pair

character

byte

update

pair

data

get

C-9

character

clear

not

20s:

palr

aget

address

flag

0s:

all

check

each

Pme g

Receive

R2,

#°C<377>,

WE Wl

BIC

GETRYT

#F
. DATA

90§

get

CMPE
BNE

6(RS),

GETBYT

MOV

Send

MOVH

MOVR

buffer

checksum

end=around

data

oyte

carry

callers

pbuffer

308

SOB

R2, 10s

TST

BEG

408

ADC

§BCKEt;

H
;

ADD

+ loop until byte count is zero
: {1f odd number of data bytes in
+ finish checksum

wORD, RO

: Recelive checksum from TUS8 and compare. to computed value
H
: get 16=hit checksum
GETRYT WwWORD
408:
|
GETBYT WORD+1
sum
check
ted
compu
with
re
compa
;
wORD, RO
of 1%
samne, get next Data packet

BEQ

s if the

s+ Checksum error,

Return error code,
set function value to error code

;

and return to caller

we we YD we e we

50s8:

RETURN

JMP

GETEND

.SBTTL

TUWRIT

that was nct'a Data packet,
A packet was received from the TUS8
packet.

Check to see that it is an End

0s$:

s+ check End packet and return to

Send Data to TU5S

‘.‘.“WQMM‘QW”*W“I“.“M*.‘O -

caller

TUWRIT

Description:

See module heading

RS = address of a five word standard FORTRAN araument block

Inputs:

O(R5)

= 4

2(R5) = address of unit number byte
4(R5) = address of block number word
6(RS) = address of output buffer

8,(R5) = address of bytecount word

Qutputs:

RO-= 16=-bhit status code

S
TUWRIT:

CALL
TS1
BNE

INIT
RO
998§

: initialize the TUSR
: {f unsuccessful,
s+ return to caller

Build a Control packet to send to the TUSH,

MOVE

]

MOVR
MOV
MOV

#0,WRIT, PACKET+2

@2(RS), PACKET+4
@8.(R5), PACKET+8.
@4 (R5), PACKET+10,

Send the Control packet to the TUS8,

: op=code is "WRITE"

s+ set unit number
s+ set byte count
; set plock number

MOV
MOV
CLK

$PACKET, RO
#12., R1
R2

s RO = address of packet
s R1 = number of bytes to send
; R2 = initial checksum

MOV
MOV

e8.(R5), R3
6(RS), RS

; R3 = number of bytes left to send
+ RS = address of callers data puffer

CALL

SNDPKT

s+ send the packet

- C-10

Send

one

Data

packets

the

TUSS8,

10s:

GETBYT

CMPR

RO,

BNE
PUTBYT
MOV

#128.,

send

send,

CMPp

208:

See

908§

not

#F,.DATA

check

for

send

Datas

;

8ssume

RESET

;

send

byte

BHIS

208

MOV

R3,

PUTEYT

byte

from
End

128

less

128,

actual

address

R4,

lenath

of
of

ADD

#F ,DATA,

CALL

SNDPKT

SUB

;

Send

R4,

ADD

;

update

R4,

number

10s

update

data

walt

was

received

packet

H
908

CALL

99s:

RETURN

left

bytes

left

from

the

End

TUS8

that

was

initial
the

not

packet

TUSS

of nytes

buffer

left

acknowledgment

CONTINUE,

caller

«SBTTL

TUSEEK

Position

the

from

TUSS

TUSEEK

;

Description:

;
H
:

See

module

heading

Inputs:

O(K5)

address

three

word

;

2(R5)

;

= address

unit

4(R5)

block

;

Outputs:

standard

2
address

16=bit

status

number

FORTRAN

arqument

block

byte

number

word

code

99§

Control

packet

BNE

#0.POS,

PACKET+2

MOVE

@2(R5),

MOV

PACKET+4

84 (R5),

PACKET+10,

packet

MOV

#PACKET,

MOV

#12.,

CLR

CALL

SNDPKT

End

packet

99s:

CLR
CALL
RETURN

the

TUS8

caller

ope=code

unit

set

bhlock

number
number

Ty58,

from

RO
GETEND

set

points

k2 =
send

Control

Get

MOVE

the

error

Send

return

TUSS,

e
e

send

initialize the TuUSRH
if initialization failed,

Build

INIT
RO

CALL

TUSEEK
¢
TST

and

return

packet

initial checksum
the packet

caller.

Indicate

return

C-11

length

byte

caller

send

pointer

GETEND

return

send

checksum

packet,

left

packet

for

number

count

the

bytes

R5,

flag

than

R4,

byte

packet

MOV

TUSS

CONTINUE,

MOV
MOV

get

R3,

SwWAFE

;
7

#F_,CONT

pre-read

TUSS

.SBTTL
i+

;

Run TUSB Local Dijagnostic

TUDIAG

;

: Description:

See module heading

:
H

Inputs:

none

;

Outputs:

RO = 16=bit status code

TUDIAG::

CALL

TST
BNE

s+ initialize the TUSS8
s 1f initialization falled,
: return error code to caller

INIT

RO
998§

Build Control packet,

MOVB

$0.DIAG, PACKET+2

s+ Send the Control packet to the TuSs8,
H

MoV
MOV
CLR
CALL

E
ATT

CLR

CALL

GETEND

SRTTL

INIT

RETURN

s+ indicate no byte pre=read

;s get the End packet

: return to caller

Initialize the TUS58

““MMMN’W‘MM‘M‘IHQM‘.Q‘

: RO = address of packet
: R1 = length of packet
: R2 = initial checksum
; send the packet

receive an End packet and return status code to caller.

89s:

$PACKET, RO
$12., R1
R2
SNDPKT

: set op=code

INIT

and TUDIAG
INIT is called by TUREAD, TUWRIT, TUSEEK,
to initialize the TUS8 to its power=up state,
r the TU58,
This is done by causing a framing erroin

Description:

followed by sending two INIT packets to the ,TUS58,
The TUS58 should reply with a CONTINUE packet

Inputs:
none

Qutputs:

RO = 16=-bit status code

INIT:

%
Send

0s:

208

: assume SsuCCess

MOV
MOV

$1, @#DLXCSR
#8., R2

s+ start senaing a break
; send nulls for 8 character times

SOB

R2,

TSTH

@ DLRAUF

CLR

MOV

#8., Ri

BREAK,

PUTEYT

CLR

20s$

@#DLXCSR

:» retry eight times before fajlure

; stop sending the break

s remove any extraneous input byte

C-12

Send

INIT

packets.

PUTBYT

#F,INIT

PUTRYT

#F . INIT

TUS58

sent

Continue

send

get

two

INIT

packets

packet

]

See

two

R2,

Bk G

99s

SOB

R1,

failed.

#F,CONT
10s

Return

MOV

99s:

error

#=127.,

SNDPKT

Send

RETURN

+SBTTL

a byte from TUSS
CONTINUE packet,
return to caller

else

Retry

GETBYT

CMPB

retry

status

caller,

Packet

TUSS

;

SNDPKT

H
s

Description

SNDPKT

send

multi-byte

SNDPKT

called

will

checksum

also

the

TUREAD,

packet

TUWRIT,

(either

compute

the

TUSEEK,

Control

packets

and

TUDIAG

Data)

checksum

and

the

send

TUSS.

the

TuUSS8,

«
Inputs:

7
:

address

number

the

of
of

initial

already

;
7

bytes
bytes

to
to

send
send

checksum

been

(non=zero

part

the

packet

has

sent)

Outputs:

None

;-—

SNDPKT:

CLR

Send bytes

-(SP)

;

to TUS8.

Update

i 0s:

COMm

(SP)

BEQ

208

CLKk

208

30s:

408:

(RO),

30s

WORD

MOVE

(RO},

WORD+1

ADD

WORD,

ADC

PUTBYT

(RO)+

SOB

Ri,

TST

(SP)+

BEQ

40s

108

ADD

wORD,

ADC

PUTBYT

SwAB

PUTBYT

flip=flop

;

flip

branch

set

with

odd/even
if

flag

second

byte

up byte pair
first

Store

update

byte

second

byte

;

with

end=around

{

send

the

;

loop

until

update

odd

word

pair

carry

byte

number

of pair

checksum

data

pair.

computed

count

data

zero

bytes,

checksum

GETEND

send

return

16=-bit

checksum

caller

Check for End Packet

GETEND

Description:

GETEND

byte

)

RETURN

.SBTTL

odd/even

16=bit checksum after each byte

WORD

MOVB

make

Control

End

called

TUREAD,

packet

from

TUWRIT,
the

TUS58.,

C-13

TUSEEK,
GETEND

and

TUDIAG

verifies

that

the

, and that the checks
received packet is indeed an End packet
ed checksum,

;

word in the packet equals the comput

H
H

Inputs:?

RO = a byte already read by the caller or zero

Outputs:

RO = 16=bit status code

H
;—

GETEND:

If flag byte was not -pre=-read by caller, read it now,
: i{f not pre=read,
" RO
TSTR
BNE

10s:

GETBYT

10§

;: read it

indeed an End Control packet.
; Verify that the packet comina from th e TUS8 is
H

CMPB

RO, #F.CTRL

: check Control packet

CMPB

RO, #10.

s with length = 10,

RO, #0,.,EQND

; and op=code = EnA

: get success code

s form 16=bit checksum

BNE
GETBYT
BNE
GETBYT

CMPB
BNE

GETBYT

BIC
MOV

SwABR
ADD

90¢
RO

90s
RO

908§

£$4C<377>, RO
RO, R1

: clear hi=byte
s form 16=bit checksum in Rl

D+F K1
,CTRL,
#10.%256.,+0.EN

; from bytes already received
s+ Receive and ignore rest of End packet, updating checksum,
H

208

ADC

MOV

$4,

GETRYT

WORD+1

GETBYT
ADD
ADC

sOB

wORD

wORD, R1

R2, 20s

: loop four times to get 8., bytes

ed checksum,

; Receive checksum transmitted from TUS8 and compare with comput
GETBYT

GETBYT
CMP
BEQ

WORD

WORD+1
WORD, R1
1008

s Return error code for transmission error.
H

908:

1008

MOVE

mOvVB

RETURN

$=127., RO

RO, RO

: return status as 1i6=bit value
s return to caller

<END

- C-14

APPENDIX D
CARTRIDGE REPAIR

D.1

INTRODUCTION

‘Under unusual circumstances of controller failure or cartridge mishandling, the tape might come free
of the hub. The tape is not fastened to the hub but is held in place by the elastomer belt and by the
tape’s wrap around itself. The procedures for looping the tape back onto the hub are given here to help
the user prevent the loss of important data. They are not a substitute for the customary precautions of
proper handling and backup copying. Two procedures are given here. One is for the metal-base cartridge and the other is for the plastic-base cartridge.

These are moderately difficult procedures requiring the use of small tools. Minimum tobls are a number
I Phillips head screwdriver and a small probe (a straightened paper clip can be used). Tweezers are

helpful.

NOTE
Keep magnetized tools away from the bulk of the
tape and do not touch the tape surface except at the
ends because fingerprints cause errors. (If staples or
paper clips stick to a tool, it is magnetized.)
D.2

METAL-BASE CARTRIDGE

Open the cartridge by removing the four baseplate Phillips head screws (Figure D-1) and set
it upright on the work surface with the cover still on.

@\
&

“Dof
®

MA-2381

Figure D-1

Baseplate Screw Locations

Lift the cover off.
NOTE

To remove the head gate, swing it out to clear the
tape before lifting it up. Its replacement is optional.

A spring is in the bottom of the gate. (Figure D-3).

Thread the end of the tape around the tape guides (Figure D-2).
ELASTOMER
BE Lif

| SUPPLY
HUB

TAKE-UP
HUB

TAPE GUIDE

. o|

Figure D-2

[\;‘ po

|
DRIVE
ROLLER

g[—_» TAPE
r J GUIDE
MA-2362

Threading the Metal-Base Cartridge

Moisten the end of the tape with water to get it to stick to the hub.

With a small amount of slack at the free end, insert the end between the hub and belt and
operate the drive roller with a finger to take up the tape. As soon as the tape is grabbed, keep
some back tension on the tape. This keeps it feeding straight into the hub.

Continue to wind. Watch for the loose ends as it comes around. If it separates from the hub,
tuck it under the next turn of tape with the probe. (Back up if the end is too long.)

Continue to wind a few more turns with the drive roller while applying tension to the tape.

Hold the takeup hub and drive roller fixed, and rotate the supply hub to take up the slack.

Continue winding the tape about 20 turns before reassembling.

10.

To reassemble the cartridge, reinstall the gate (if desired) by aligning the long and short ends

11.

Drop the spring into the well in the gate. Holding the spring down with a thumbnail or probe,
rotate the long end of the spring around to the slot that is at a right angle to the long dimension of the gate. Push the end of the spring into the slot; it should stay there by itself.

12.

Hold the gate halfway out so that the gate and the spring end do not touch the tape. Slowly
press the gate down onto its pin on the cartridge baseplate. Reach in with the probe and press
the spring down. It will clear its holding slot and snap into position, closing the gate.

of the spring with the long and short ends of the gate, as in Figure D-3.

D-2

MA-2358

Figure D-3

13.

Head Gate and Spring

Carefully lower the cartridge cover into place and reinstall the screws.

D.3 PLASTIC-BASE CARTRIDGE
Open the plastic-base cartridge case by removing the four baseplate
Phillips head screws (Figure D-1).
Carefully remove the top.

D.3.1
Preparation for Threading
,
The four rollers and tape hubs in the plastic-base cartridge are
held in their operating plane by the top
and bottom of the case together. When the top is off, the various parts
tend to creep out of position, and
the elastomer belt can get folded under the hubs.
I.

To organize the parts for threading, remove and discard the head
gate and spring. Take the
empty tape hub from the case and set it aside.

Remove the floating roller (Figure D-4).

FLOATING ROLLER

ELASTOMER

BELT

L
Figure D-4

MA.2355

Stretch the Belt with the Floating Roller

D-3

Rearrange the elastomer belt around the drive roller and the supply hub.

Put the takeup hub on its pin.

Put the empty tape hub on its pin.

hub down, use a straightened paper
Using the top to hold the floating roller, belt anddsupply
clip or pencil to guide the elastomer belt aroun the hub. The hub should seat against the

base with the belt around it.

Threading the Cartridge

D.3.2

Pull several centimeters (a few inches) of tape off the supply hub and through the tape guides

(Figure D-5).

NOTE

Hold all parts down when moving them. Otherwise,
the hubs will creep up the pins and cause the belt to
slip. Then the procedure must be restarted at Paragraph D.3.1.

TAKE-UP
HUB

GUIDE

ROLLER

| SUPPLY
HUB

GUIDE
MA-2364

Figure D-5 Threading the Plastic-Base Cartridge

Moisten the end of the tape with water to get it to stick to the hub.

free end, insert the end between the hub and belt, and
3 With a small amount of slack at the
up the tape.
operate the floating roller to take

As soon as the tape is grabbed, keep some back tension on the tape. This keeps the tape
feeding straight into the hub.

around. If it separates from the hub,
Continue to wind. Watch for the loose end as it comes
tuck it under the next turn of tape with the paper clip. (Back up if the end is too long.)
tape.
6. Continue to wind a few more turns with the floating roller while applying tension to the
the supply hub to
7. Now hold the takeup hub, drive roller, and floating rollers fixed and rotate
.

take up the slack.

D-4

D.3.3 Closing the Cartridge
Place the top back on the cartridge. Do not reinstall the head gate. The mirror window may need to be
pressed in slightly to clear the bottom. Reinstall the four baseplate screws.
Now use a finger to operate the drive roller and wind the tape about 20 turns onto the takeup hub

before inserting the cartridge into a drive.
NOTE
The only reason for performing this exercise is to
copy the data from the injured tape as soon as possible. Discard the cartridge after copying.

D-5

APPENDIX E
FIELD REPLACEABLE UNIT SPARES LIST

- Module

Serial Controller Board
Regulator Module
Drive
Tachometer Encoder Wheel
Tape Cartridge

DIGITAL P/N
54-13489
54-13609
70-15510
74-20649

36-15809

Option Name
TUS8 - XB

TUS8 - XA
TUS8 - K

|So

Reader’'s Comments

TUS8 DECtape USER GUIDE

Your comments and suggestions will help us in our continuous effort to improve the quality and

usefulness of our publications.

What is your general reaction to this manual?
Excellent

Very Good

Good

Fair

Poor

Accuracy

Completeness

Organization

Format

[

What features are most useful?

(Notes, Tables, lllustrations, etc.)

Does the publication satisfy your needs?

O Yes

O No

What errors have you found?
(Ref. page no., table no., figure no.)

Additional Comments

Name

Street

Title

City

Company

State/Country

Department

Zip

The Documentation Products Directory and the DECdirect Guide contain information on the
remainder of DIGITAL's technical documentation.

Copies of the above Directory and Guide, as well as additional copies of this document, are

available by writing or calling:

Digital Equipment Corporation
Accessories and Supplies Group
P.O. Box CS2008
Nashua, New Hampshire 03061

Attention: Documentation Products
Telephone: 1-800-258-1710

Order No.
MY

EK-0TU58-UG-003

raoooen

No Postage

Necessary
if Mailed in the

United States

BUSINESS REPLY MAIL
FIRST CLASS

PERMIT NO.33

MAYNARD, MA.

POSTAGE WILL BE PAID BY ADDRESSEE

Digital Equipment Corporation
Educational Services Development and Publishing

129 Parker Street, PK3-1/T12
Maynard, MA 01754

igital Equipment

orporation « Maynard, MA 01754