Digital PDFs

EK-0TU58-UG-4

2000

104 pages

Original

38MB

view download

OCR Version

19MB

view download

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

OCR Text

EK-0TUS8-UG-004

TUS8 DECtape |
User Guide

EK-0TUS8-UG-004

TUS8 DECtao

Prepared by Educational Services
of

Digital Equipment Corporation

st Edition, October 1978
2nd Edition, June 1981
3rd Edition, October 1982
4th Edition, December 1983

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.

This equipment generates, uses, and may emit radio frequency. The equipment has been type tested and found to
comply with the limits for a Class A computing device
pursuant to Subpart J of Part 15 of FCC rules, which are
designed to provide reasonable protection against such
radio frequency interference. Operation of this equipment
in a residential area may cause interference in which case
the user at his own expense will be required to take
whatever measures may be required to correct the
interference.
The following are trademarks of Digital Equipment Corporation, Maynard, Massachusetts.

DEC
DECUS

DECnet
DECsystem-10

OMNIBUS
0S/8

DIGITAL

DECSYSTEM-20

PDT

PDP
UNIBUS
DECtape
DECtape 11

DIBOL
EduSystem
VAX
MASSBUS

RSX
VMS
IAS
VT

dlilgliltlall

DEChwriter

RSTS

CONTENTS

INTRODUCTION

i@;

€

#®

€

w——
L]
T
S v
¥

® & & ¥ ® B B & #

& %

# 8 =2 # B 2 ¥ ¥

T
¥

® ® & g ¥ 2 ® £ & % £ B 3 £ & #® # ¥ % & ¥ ® = B =

g & & & & %

O
i

Fee

Z}fifi
s & 2 2 % & ¥ £ % & ¥ ¥ ¥ 8 B ¥ £ €& % ¥ ¥ ¥ ¥ # ¥ ¥ =2 & ® 2 ¥ [
Specifications

£l

Eld

€

T TR

€

¥V

€

e
¥

£,

R S
|

B L O

T
i

Environmental ..................
¢

T
¥
T
|
¥
&

NS I NST NGT NS I NS R

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

e ee

..........

Application and Removal of ?i}%@ e

¥
¥
i

... ...

RV ISRV IV NSl NS

Front Panel

FrontPanel ......................
Run Indicator . . ..o
e
e e e
e
Application and Removalof Power . ........
... ... ... .......
TU58-VA Controls
and Indicators ....... e
e e
e
e

1€

Application and RemovalofPower ........................
0 o

C&ffiiéggiééézfigg;gHH%HHHHHHHH;HHH“*HH
o

it it

Operator Trouble Iso Eéé’:i@

C%figiégi §% far &= & = E 4 & & £ L E k4 & Ed #® = & & = # = B ® z L L & & Ed d * ¥ ® & Ed & & & & = # #

&®

€

Cartridge Storage and Care .. ... ... ittt
Maintenance
. ... ... .. it

Head and Puck Cleaning. . . .. ... o

¥
-

Efi%?féi&fi?ééMHH,H“MHHHH;HHHHHHHH

fe&

?’W"i”‘"

Mfi*
B

Wfi

fpot5

"mi

- @

W"’“
-

i&figzfiggijgggéézfifi%HMHHHHHMH §§§§§§§ e ..

;SRS
¥

W b Josmmms

T I
S e

W b e

PO DD

L 1
L

B BO b2

Run Indicator.................

RO B

B
W

DI B

e e

TUS8 Components Controls and Indicators . ...........cc......

e RV R RV RV RV RV N N

£
w

and Indicators

Ffé}fii?gfiaifluw, §§§§§§ e e e e e e

TUSS8-EA, -EB Controls and Indicators

o e e

B2 B

Run Indicator. .. ... .. . .
e e
Application and Removalof Power ...........
... ... .......

e e

OPERATION
TUS&-DA, -CA Rackmount Controls

et o

b2 B B RO PO B B

CHAPTER 2

Digital Repair Service . ... ...

Hardware Documentation {Z}fé%fifig Egié}z“g‘;‘zatzg}g e e e

Configurations ............ ..., e

A 4
Electrical
S 3
. isf

SE SN

;

Performance

T
]

Processor
.
g«w

L PSSRV

T
¥

Sy WA= S A" Ay Wt S

Scope
d
gvfsisif%%%é%a%é@%%fi&éi%éi?&i&i%% sssssss # % & £ ¥ 8 £ ¥ 8 F 2 & % &
% #

General Description ..............
Block Diagram
/ =
\
E}!
e Control
gi%fi
& ¥ £ % ® ¥ ¥ B ® E ¥ ¥ ® ¥ ® ¥ 2 B B 2 & & B ®R & & & % 2 § € £ % ¥ € g # & & 2

'
4 Ly

-’

CHAPTER 1

U YOI OSRS

[ B

£3

]

-3

€

Number, Byte Count, and Drive Number ..............

Radial Serial Protocol (RSP) and Modified RSP(MRSP) ..................

ittt ittt e

i
¥
i

sennnn ey

e
e e e

#”

E 3

e e e e

Jromi

L S

W
m

zfif%&géz@%i
Joomis

Eé%éé?%ifi%fi%%fi&?

Ez%%‘i‘ifiétion;EJ:

PASCAL TUSS gggééfisé
INSTALLATION

€

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

%;&a%sé%}éfi;g%gigéigé25%&%5&“HH%,HHHHHHMH,MHHHH;MH
RaCKmMOUNT o .ttt ittt s ettt e et ettt ennanssesneseeenennenneens
Power Selecti on for the RAck VEISION ..o ver o
e eeieee e annnn..
%52@%{%@%&@%2%§f§§%§¥§IS it e
e e
e e e
e
Reinstalling the Eé}{ég%
Installation (-EA ¢
%g?fié}
D18 vt
e e e
e et e e,

4-7
47
48
4-10
4-10
412

Removing Bottom Plates for Controller Board Configuration

MWM

Wfil?

Eg%top In
W‘y

olid

Mounting Installation

§%§§§£§“é§- (-VAVersion)

... ...

...

e
.

eneeenneneens

e
i

Mounting the TU58-VA
to the SB11

4.5.3

8.2
4.8.3

(or %fiéé%fifiJAY

:
e

Tabletop Installation .. ...... .. . .
i iiiiiirinnn
Solid Mounting Installation ..............
S

7.2
8
8.1

4-1

Rackmounting Procedure .. ...... ..ttt

s
B

4-1
1

4-1;
422

?i}%fif?ifiézfi&i}% ggggggg

e
e

§§: %%9%%%

5.1
%i:

4.6

f—

Special Address]§§§§§

L]
.4

L s Lad P e

B G b

Q
L]

e
*

S
S
o

N
*

*®
i

VR SV PV VR IV NI SO I NS I O Y NS I NS Y

ittt it ittt ettt

|950 16 R0 1 5 (o J o
N
AU
%EEzgigggggé%}é2@%{}%% R

. ...

Maintenance Mode . ...

#
A

L
e

[

FNEE SR SR SN SN SRS

Lo o0 Lo Lo La Gd o W Ld L

Command Packets

L L e N

PaCKetS & ittt
e i
e
et
e
et
Packet Usage . ... it
ittt i
e i ennnsn
Break and Initialization .. ..ttt
it ittt i ettt e e

NN N

3.2

; géffiiéé Efiiéééiig %g}g‘g}éfii;fi;}agéf% & & % = # = = ¥ & % & & % B ¥ ¥ B £ & 8 ¥ & ¥ # & % 8 2B B &8 ¥ 8% =

3.2.1
ilié
2.2

Wwwwwwwwmwwwwwww

Block

NV N N SO N

General P rinciples

COMPONENES & o vt vt sttt es e ennneaneseeeeensennssessonennaeeeseceres

Eéiigégifi%fiég%géigiiza}%&gé %igizg% I
aterface Standards .. .. v vttt
gStandards Jumpers.
. ......... ... L. R
Operational CheckoUt . ...ttt it i et iieeennecntanananneenes
Checkout
of Interface ... ... vttt irneerineeennneeenena.

413

L
41T
S
419
419

ii%é%géggé%fiizéifiigggjs 4-21
Checkout of Drive Command Function ..........c.ccviiirrrnvneeeene.... 431
&

e e e e

e e e ce

§§§§E§£§ §§§§§§§§§§ s
Operation
.. ....... .

e
ee
e e

e s e s ot s s s s s s s e e s

... e e e e e e

e e

Installation
. .. ..., e e

APP

e e

............ e e e .

Installation ... .. .
Boot Switch

LA Ly Ly W L Ly

Run Indic ator

TUS8/P

Cartridge %;@i;gézi e

Read Command Packet Exchange

. ........... e

e e

TUS8-DA Rear Panel .. ... e e
e e e

s
L

i inennn.. e

MRSP Write Transaction

%E%aéfiing Su
?Si"g? Brackets

............... e

%%ifik%éé}fi%izgie TUSE-DA . ...

...

.. e

e e

................. e :

e ..

. ..... e

N m%;w 5 N G AR SN N
]

TUSB-CA
Rear Panel

eee
e e

Rackmounting the TUS8-CA .................. e e

. . ... ittt e e

Installing Cage and Ret%é%ézEéi% gggggggggggg e e
Mounting
theT‘Z’fi%%%igé EB

Mounting Choices for the TUSE-VA ... ... .

Interfacing the Ef‘é%VA

rairaire
3

Mg Brackets
... .. . e

Bezel and Ball Stud

% ? il U-Nut Retainers.......... e e e

Fastening Support Bracket Extenders

e e e e e

Installingthe Bezel ............... e

o Jlm I R

e e

. .. ..ottt
e et et e e e e e e e e e

Rear Vertical Support U-Nut Retaine

OO ND OO0 =0 O W W W b

i i,

e e e e e

e e e

Drive Outline ?%g@%fix@”gw §§§§§§§§§ .

Board Outline Drawings ... ..ot

TUS8 Drive Mounting Hardware

ittt

teeereenns

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

o oL,

Data Rate and CatEiéi;fiééi%if%»é%

Interface Selection Jumper Pin 1@&@2233%HHMHHMH

]

e .

e e C

............... e .

RSP Write Transaction . ......cov

e e acenn
e e Ce

......... e

View Into Tape §§§%a f;rtridge Slot

Ins Egfi”’%%‘?%

e e .

e e C

S S N S

Do w00 Pod s OT

and -CA Rackmount Front Panel ....... e

Write Protect Tab..

TUS8-EA, -EB, and -VA Front Panel ........ e

oo L L 0 b %‘fi NN N TN (N

géz}gé;;};z{zfiz&{}g’ifig
TUS8-DA

?Ea nt

e .

e e e e
e

e e

...,

TUSSE

rial Protocol ..

P e U Wb o0 DO

i&ii §§§§§§i§f§ into Drive (Top View)

An %ri}iafizgé y

N G

N Wb e s 0 D

Tape Ca

CARTRIDGE REPAIR

4-21

4-22
4-23

4-24

Factory Wiring . . ................ P«
T{ESSWmfig@SGQBagé}g e e e e
e e e e
e e e e
DLVEE}FagtaryCéflf;gfifatiéfiSafiifi*&gf}f R
MXVI1I-A
Jumper Locations . ....... .ottt
teneeennnen. e
Installation of Run Indicator ... .. ... .
i
ettt i .
Baseplate
Screw Locations .
............. A
Threading the Metal-Base Cartridge ......... ... it
Head Gate and Spring . .. ..o ittt it it e et e e et et et et
et
Stretch the Belt with the Floating Roller .. ....... ... ... ... ..... ceieeee..
Threading the Plastic-Base Cartridge
. .. ........ .. .. .. .. ... .. ... e

28 |
4-21
S
<
426
5-1
D 55
D2
D-3
D-3
D-4

Operator Trouble Isolation
. . ... ot
i
i
i e
e e et e ...
Command Packet Structure .......... ... N
Data Packets . . ..o
e
e
e e
e e
End Packet ... it
e e e e e
e e
e
Instruction
Set ... ... it it it .

2-6
B
3-5
3-5
10

TUS8 Module CONNECtioNS . v v v v vt i ettt ee i es eesieieeeeeeraeneneee..
MXV11-A Standard Factory Configuration ........... ...

418
427

INTRODUCTION

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

Chapter 1 provides a general description of the TU58 and a list of its specifications, including electrical and
mechanical requirements. The céfifzg%zrg%{}as section describes the available variations of the TUSS.
Chapter 2 contains éfizpsfigfzi information for daily operation and routine maintenance. It is the system
operator’s reference section.

Chapter 3 is a programming guide. It contains functional descriptions of the TUS8 command set, illustrates command sequences, explains the details of the radial serial protocol (RSP) and the modified radial
serial ??éé%fi}ié} (MRSP), lists system instruction codes and byte sequences, and includes a general purpose
programming example for a TUS8 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 availablein 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 IV and PDP-11 MACRO-11
assembly language.
Appendix D covers cartridge repair procedures.

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

1.2 GENERAL DESCRIPTION
The TUSS
1s a random-access, fixed-length-block, mass-storage tape system. It uses preformatted tape
cartridges which store 262 kilobytes of datain 512-byte blocks. There are 256 blocks on each of two
tracks. Tfi%}f may be accessed b} a program in a fashion similar to that employed for data stored on
disks or DECtape, using a new, high-level instruction set. A file-oriented structure is easily implemented in an operating system by setting aside several blocks on the tape to store a directory.

yoonndy

The TUSS8 is compact and mechanically simple. The “s;;?*e ca é?;a% are DIGITAL-preforma éifii miniature, reel-to-reel ?%é%figé% containing 42.7 m (140 ft) of3.8 Emm (0.150 in) wide tape. A single
puck
drives the tape by engaging a roller which moves an elastomer §§g§§ belt in the ’ig%?éégi ?% belt
I oops around bothtape spools and ;z‘g?fi@ 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 % é
microprocessor (uP) to re duce the tape handlin

a single circuit board. The controller uses a

«%g%i’é%%%éfi%%%%é%é management
load on the host

system.

The motor and tape he>ad control, driver, and switching
ng
c circuits that manage the two tape drives are on
the printed circuit board with the uP. The controllerSu supports one or two drives, but only one drive can
operate at a time. The uP controls all activities of the TUS8. Head andmotor selection, speed and
direction changes, etc. are managed by outputs from I/O ports on a ;a?%??fif1l integrated circuit (1C).
The mechanical actions of the é?%@% are supervised by the uPin order to improve system performance.
Operational amplifiers, comparators, and logic circ gs perform amplification, signal s%gf%g%%é and conditioning, proportional control, and logic steering
f cti ons in %é controlller ??fii tape isprotected by
motor current limiting and an anti-runaway %zfizii

The uPintelligence requiress the
specifications about the tran:§
viston from the host.

radial serial protocol (MRSP). RSP uses two kinds z::;f %3te %i%iéiiaé%§£ %é message packets. Both com-

mandand data packets have protocol information placed i 1 specific locations in the byte sequence. This

format is easily generated by the TUS58, making host-peripheral interaction g‘fi%%éié at a high level with low
cost. Figure 1-2Ekifi?é%afi a typical RSP iiihéggi between a host computer and the TUS58. See Chapter 3
for a full discussion of RSP implementation.

Figure 1-1

Tape Cartridge Partially Inserted into Drive (Top Vi

When, owing to the data transfer rate selected, the buffer is unable to accept an entire transaction, modified serial protocol (MRSP) is utilized. MRSP 1s 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 gg%fffi%é:ffigaégfigé% rates of
150 to 38.4K baud. Send and receive rates may be §§é§§§§é§§§:§ set g@z‘%‘;éjumpers to operate inaccordance
with Electronic Industries Association (EIA) standards RS-422or RS-423. When set to RS-423, the TUSS8
is also compatible with devices complying with RS-232-C,

Figarfi 1-3 illustrates the structure of the TUS8 system. The data path1salong the top
of the diagram,
passing to the host through the processor at the fi%}hi The drive control
is at zis lower %Ls& also closely
associated with the processor through the 1/0O ports. The ports, memory, §§%§ universal asyE%é ronous
receiver-transmitter (UART) are connected to the processor by an
8
8-bit-wide data/address “bus
1.3.1
Drive Control
The cartridge drive motors are powered by servo-regulated §§§gg§ and direction circuits. These are controlled by the processor, which monitors with tachometers and with %%%é?‘% 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 %i??if}?iié by firmware in a 2-kilobyte, read only memory

(ROM) and by ggggfi;ih;}gd and data buffer memory in a 256-byte random access memory (RAM). The

processor communicates with the drive control circuitry ihf‘éég% a bidirectional 1/ E gz;@%%i The UART
Xéhagggs data between the TUS8 processor bus and the host computer via the serial line drivers and
receivers.

HOST

TUSBE

COMMAND
PACKET

CONTINUE

MESSAGE

END

FACHEPT

‘

[

DRIVE

HEAD

PEAK DETECTOR

SELECT

AND DECODER

WRITE AND

rmmmmfijg

;

SRIVE

§§f§§§ ;{j?%ié

;

TACH AND
CONTROL

CONTROL

|I e
-

DRIVER

CONTROLLER

VELOCITY

MOTOR

AND DRIVERS

LI
|

ereeon

INTERFACE
170 PORTS

PROCESSO#
8085

‘

)

SERVO AMP

AND

DRIVE

MOTOR

SELECT

DRIVER

RAM

ROM

256

BYTES

UART

DRIVERS

RECEIVERS

Figure 1-3

1.4.1

TUS8 Block Diagram

Performance

Capacity per cartridge

Data transfer rate
Read/write on tape
Data bgffef to interface
Cartridge life

262,144 bytes, formatted in 512
blocks of 5121 3tes 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

Soft §§; % error rate

| in 107 bits read (before selfcorrection)

Hard error rate

1 in 107 bits read (unrecoverable
wi%%‘%z 8 automatic retriesé

Hard error rate with
write-verify and

2 in 101 bits read /written

system correction
Error checking

Checksum with rotation

1-4

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

Medium

DECtape II cartridge with 42.7 m
(140 ft) of 38 fl{%%ié}zfiézag}i

Size:
6.1 X 8.1 X 1.3cm (2.4 x 3.2
% 0.5 1n). Order TU58-K.
Track format (Figure 1-4)

Two tracks, each containing 1024

individually numbered, firmwareinterleaved “records.” Firmware
manipulates four records at each
operation to form 512-byte blocks.

Drive

Single motor, head integrally cast
into molded chassis.

Drives per controller

I or 2 (only one may operate at a

time)

1.4.2

KElectrical

Power consumption

Boardand | or 2
drives

11 W typical, drive running

+5V £5%at0.75 A maximum
+12V 4+ 10% —5% at 1.2 A, peak

0.6 A average running
0.1 A idle
These voltages need not stabilize
simultaneously upon power-on.

} SOT

#128 | #384 | #129 | #385 | #130 | #386 | #1731
200
600 | 201
601
202
602 | 203

sor | #O | #256 | #1

400

| #257 | #2

401

| s288 | #

BOT: BEGINNING OF TAPE

EQOT: END OF TAPE

Figure 1-4

Bloc k Locations on Tape

402

|3 (

\ #2654 | #510 | #255 | #511
376 | 7786
377
777

EOT
‘

#126 | #382 | #127 | #383 |

176 | 576

177

577 |

# DECIMAL

OCTAL

Rackmount

Serial interface standards

1.4.3

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.

Mechanical

Drive

Wem (3.2 X 3.3
8.1 H X 83D X 10,6
% 4.1 in) with 19 cm (7.5 in) cable;
0.23 kg (0.51b)

Board

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

TUS8-DA

Same rackspace as -CA. See -EA for

TUSE-CA rackmount

13.2H X 38.1 D X483 Wcem (5.19 X
15.0 X 19.0in); 9 kg (20 Ibs)

chassis.

cabinet

WMW

X 29 §§X’7§35§% cm (3.6 X
2 H

1.6 X 13.3 in); with rubber feet,
add1.5 Hcm (0.6 in)

Power connector to
board

AMP 87159-6 with 87027-3 contacts
DEGiT%L PN 12-12202-09,
2-12203-00)

Power connector to
rackmount

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)

1.4.4

Environmental

When the TUS8-AB or -BB is integrated in a host device such as a terminal, convection provides ade-

quate cooling if the interior temperature is below 50° C (122° F) dry bulb, 26° C (79° F) wet bulb.
Maximum dissipation

TUSS-CA, -DA, -EA, -EB
TU58-AB, -BB, -VA

120 Btu/hour
34 Btu/hour

Temperature
TUS8 operating

159 C (59° F) to 42° C (108° F) ambient

TUS8 nonoperating

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

Maximum temperature
difference between

18° C (32.4° F)

ambient and TUS58 board

1-6

Relative humidity, noncondensing
TUS8 operating
Maximum dew point
Minimum dew point
Relative humidity

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

TUS8 nonoperating

5% to 98%

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.
.

TUS8-CA

Rackmount, large chassis, two drives, serial interface controller board, power
supply 115/230 V switch-selectable, detachable line cords and fuses for 115V
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), diagnostic kit (ZJ287-RG).

TUS58-DA

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 MRI11-EA, accessory assembly hardware kit (70-16753-00), User
Guide, Field Maintenance Print Sets (MP01014 and MP0O1063).

TUS8-EA

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

TUSS-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
cessory assembly hardware kit (70-16753-01).

Additional Supplies

BC22D-10 replaces BC17A-18 and BC17Bnew cable has an improved shield connection to com-

ply with FCC regulations.
BC22D-10

Interface cable from TUS58 to host.

(MP01013), ac-

BC17A-18

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

BC17B-18

BC21B-05

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

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.

TUS8-DB

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

TUSS-EC

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

TUSS-ED

Accessory kit containing detachable line cords for 115 V and 230 V and fuse for
230 V, two cartridges, two /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/O cable (70-1775681F), 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

70-16753-01

Accessory assembly hardware kit with brackets for mounting TUS58 tabletop

23-126F3-0-0

Boot ROM for BDVI1I.

MXVI11-A-2

Boot ROM for MXV11.

23-765A9-00

Boot ROM for MR11-EA.

versions to flat surface.

versions below a flat surface.

The following TUS5S8 DECtape Il Tape Subsystem hardware manuals can be purchased from
DIGITAL’s Accessory and Supplies Group.
Part No
EK-OTUS8-UG
EK-OTUS8-PS

Title
TUS8 DECtape II User Guide
TUS8 DECtape Il Pocket Service Guide

EK-0TUS58-TM
EK-0TUS8-IP
MP0O0747

TUS8 DECtape II Technical Manual (microfiche or paper)
TUS8 DECtape II Illustrated Parts Breakdown
TUS8-C Field Maintenance Print Set

MP01014-00

TUS8-E Field Maintenance Print Set
TUS8-V Field Maintenance Print Set
TUS8-D Field Maintenance Print Set

MP01013-00
MPO1063
ORDERING

You can order supplies and accessories from one of the following addresses, according to your location.

Continental USA
Call 800-258-1710, or mail order to:
Digital Equipment Corporation
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

1.7

DIGITAL REPAIR SERVICE

Digital Field Service offers a range of flexible service plans. Choose the one that is right for you.

ON SITE SERVICE offers the convenience of service at your site and insurance against unplanned repair
bills. For a small monthly fee you receive personal service from our Service Specialists. Within a few hours
the specialist is dispatched to your site with all the equipment and parts needed to give you fast and
dependable maintenance.

BASIC SERVICE offers full coverage from 8 a.m. to 5 p.m., Monday through Friday. Options are
available to extend your coverage to 12-, 16-, or 24-hour days, and to Saturdays, Sundays, and holidays.
DECservice offers a premium on-site service that guarantees extra-fast response and nonstop remedial
maintenance. We don’t leave until the problem is solved, which makes this service contract ideal for those
who need uninterrupted operations.

Under Basic Service and DECservice all parts, materials, and labor are covered in full.

CARRY-IN SERVICE offers fast, personalized response and the ability to plan your maintenance costs

for a smaller monthly fee than On-Site Service. When you bring your unit in to one of 160 Digital
Servicenters worldwide, factory:trained personnel repair your unit within two days (usually 24 hours). This
service is available on selected terminals and systems.

Digital Servicenters are open during normal business hours, Monday through Friday. Call one of the
following numbers for the location of the office nearest you.

DECmailer offers expert repair at a per use charge. This service is for users who have the technical
resources to troubleshoot, identify, and isolate the module causing the problem. You mail the faulty
module to our Customer Returns Center where the module is repaired and mailed back to you within five
days.

PER CALL SERVICE offers a maintenance program on a noncontractual, time-and-materials-cost basis.
This service is available with either On-Site or Carry-In service. It is appropriate for customers who have
the expertise to perform first-line maintenance, but may occasionally need in-depth support from Field
Service.

Per Call Service is also offered as s supplementary program for Basic Service customers who need
maintenance beyond their contracted coverage hours. There is no materials charge in this case.
On-Site Per Call Service is provided on a best effort basis, with a normal response time of two to
three days. It is available 24 hours a day, seven days a week.
Carry-In Per Call Service is available during normal business hours, with a two to three day
turnaround.

For more information on these Digital Service plans, prices, and special rates for volume customers, call
one of the following numbers for the location of the Digital Field Service office nearest you.
Digital International Field Service Information Numbers

U.SA.

1-(800)-554-3333

Canada
United Kingdom

(800)-267-5251
(0256)-57122

France

1-6873152

Belgium
West Germany
Italy
Japan

(02)-242-6790
(089)-9591-6644
(02)-617-5381/2
(03)-989-7161
1-10

Denmark

430-1005

Holland
Switzerland
Sweden
Norway

(01820)-34144
01-8105184
08-987350
2-256422

Spain
Finland

91-7334370
90-423332

CHAPTER 2

OPERATION

2.1

TUS8-DA, -CA RACKMOUNT CONTROLS AND INDICATORS

2.1.1 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
1
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 TUS8-DA has a power switch on its backpanel, while the TUS8-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 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
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.

RUN INDICATOR
DRIVE
1
-

D CATOR

TAPE STORAGE
AREA

Figure 2-1

MA-2381

TUS58-DA and -CA Rackmount Front Panel

2.2

TUSS-EA, -EB CONTROLS AND INDICATORS
Front Panel

2.2.1

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

2.2.2

Run Indicator

2.2.3

Application and Removal of Power

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

The TUS58-EA and -EB versions have power switches on their back panels. If an outlet is available on a
system power controller, these versions may be plugged into the controller. Otherwise, they do not need
to be turned off. Their 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 removai.

2.3

TUS58-VA CONTROLS AND INDICATORS

2.3.1

Front Panel

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

Run Indicator

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

PRIVET

ruN INDICATOR

DRIVE 1

RUN INDICATOR

DRIVEO

DRIVEO
MA-6843

Figure 2-2

TUSS-EA, -EB, and -VA Front Panel

2-2

2.3.3 Application and Removal of Power
The TUS8-VA requires +5 V and 412 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 TUS58-VA is 70-17569-1C. See Chapter 4 for installation information.
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
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 TUS8 COMPONENTS CONTROLS AND INDICATORS
See Chapter 5 for installation and operation of optional features.
2.4.1
Application and Removal of Power
The TUS8 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 than5 W.
When power is applied, the TUSS 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

CARTRIDGE

2.5.1 Cartridge Loading
The TUS8 drive is designfzé to make correct Iéading easy. To load the cartridge, hold it label-up, line it
up with the grooves in the chassis, and slide it in wath 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 1s 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
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 TUS8 does not know that a different cartridge was loaded; the operator must keep track of the contents of various cartridges.

2.5.4 Write Protect Tab
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 TUS8 with their write protect tabs set to record.

2-3

MA-2378

Figure 2-3

Cartridge Loading

WRITE PROTECT TAB IN
PROTECT POSITION
/

MOVE TO RIGHT TO RECORD
-

MOVE TO LEFT TO PROTECT
RRE

MA-2359

Figure 2-4

Write Protect Tab

The write protect tab can be completely removed for long-term write protection. On the metal-base
cartridge, use a fingernail 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 magnet-

ic objects away. If it 1s 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 Cleaning
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 Cartridge Wear
Cartridge tape is expected to last for 5000 end-to-end-and-back passes. If a cartridge is 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 shedding oxide and should be copied and discarded as
soon as possible.

i
DRIVE PUCK
MICROSWITCHES

Figure 2-5

\
?ég:gxgggg

MA-2374

View Into Tape Drive Cartridge Slot

2-5

Table 2-1

Operator Trouble Isolation

Symptom

Action/Comments

TUS58 does not respond

to host

Ensure that the TU58-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

TUS58 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.
3.

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 TUS8 is 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 asynchronous interfaces.
3.1.1 Block Number, Byte Count, and Drive Number
The TUS8 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 data is 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 TUS8 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
TUS8 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 block in 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 TUS58 firmware.

3.2

A short routine called Newtape (Appendix B) should be included in a TUS8 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 TUS5S8 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.

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

3.2.1 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

A special case of the Control packet, called an End packet, is sent from the TUS58 to the host after
completion of an operation or on an error. The End packet includes the status of the completed or
aborted operation.

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

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

Bootstrap — A flag byte saying Bootstrap (octal 10), followed by a byte containing a drive number,
causes the TUS8 to read block 0 of the selected drive. It returns the 512 bytes without radial serial
packaging. This simplifies bootstrap operations. Bootstrap may be sent by the host instead of a
second INIT as part of the initialization process described below.
Continue — Before the host sends a Data packet to the TUSS, it must wait until the TUS8 sends
Continue. This permits the TU58 to control the rate that data packets are sent to it.
XON - An alternate term for Continue.

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

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

Flag Byte Value

Packet Type

Data
Control (Command)
INIT
Bootstrap
Continue
XON
XOFF

Octal

01
02
04
10
20
21
23

Binary

00001
00010
00100
01000
10000
10001
10011

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

Multiple-byte (Control and Data) packets also contain a byte count byte, message bytes, and two checksum bytes. The byte count byte is the number of message bytes in the packet. The two checksum bytes
are a 16-bit checksum. The checksum is formed by summing successive byte-pairs taken as 16-bit words
while adding any carry back into the sum (end-around carry). The flag and byte count bytes are included in the checksum. (See example in Appendix B.)

3-2

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 TUSS 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 itself, 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.
The second character is discarded by the TUS58 controller. Next, send two INIT characters. The first is
discarded by the TUS58. The TUS58 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
9
0

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

Block Number — High

[

—

Byte

Checksum — Low
Checksum — High

Flag

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

Message Byte Count

Number of bytes in the packet, excluding the four message delivery bytes. This is decimal 10 for all command packets.

12,13

Checksum

The 16-bit checksum of bytes 0 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 being 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 TUS8.

8,9

Byte Count

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

10,11

Block Number

The block number to be used by commands requiring tape posi-

for definitions.)

Ignored by other commands.

tioning.

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 1
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 is the command packet from host to the TU58. Next, the data is transferred in 128-byte packets in
either direction (as required by read or write). After all data is transferred, the TUS58 sends an end packet.
If the TUS8 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 TUS8 only has 128 bytes of buffer space. For write commands, the host must wait between
message packets for the TU58 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 during power up. A good practice is to set bit 3 in every
MRSP command packet.

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 TUS8 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 XON is
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 handshake is employed.
3.2.5 End Packets
The end packet is sent to the host by the TU58 after completion or termination of an operation or an error.
End packets are sent using RSP or MRSP as specified by the last command packet. The end packet is
shown in Table 3-3.

Table 3-2

Data Packets

Byte

Byte Contents

Flag = 0000 0001
Byte Count = M

First Data Byte
Data

bata

M+ 1

Last Data Byte

M+ 2
M+ 3

Checksum L
Checksum H

Byte

Byte Contents

0
1

Flag = 0000 0010
Byte Count = 0000 1010

mmmw*mmmmmm*wmmw

2
3

Success Code

Unit

Not Used
Sequence No. L

[
Y

Sequence No. H

8
9

Actual Byte Count L
Actual Byte Count H
Summary Status L
Summary Status H

0
1

12
13

Checksum L
Checksum H

3-5

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

Byte 2

Op Code — 0100 0000 for end packet

Success Code
Decimal
Octal
0
0

Byte 3

1
377
376

1
—1
—2

=
=
=
=

Normal success
Success but with retries
Failed self test
Partial operation (end of

370
367
365
357
340
337
320
311

—8
—9
—11
—17
—32
—33
—48
— 55

=
=
=
=
=
=
=
=

Bad unit number
No cartridge
Write protected
Data check error

medium)

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

Summary Status

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

{

Bit 7

Byte 11
Bit 0
1
2
3
4
5

6
7

3.3

Reserved

Logic error
Motion error
Transfer error
Special condition (errors)

INSTRUCTION SET

The operation performed by the TU58 when it receives a Control (command) packet is determined by the
op code byte in the control packet message. Note that while any command can specify modified radial
serial protocol with the switch byte, the response will not be MRSP if a boot operation is being performed.
Instruction set op code byte assignments are listed in Table 3-4.

To allow for future development, certain op codes in the command set have been reserved. These commands have unpredictable results and should not be used. Op codes not listed in the command set are illegal
and result in the return of an end packet with the “bad op code’ success code.

Table 3-4

Instruction Set

Op Code
Decimal

Op Code
Octal

Instruction Set

0
1

NOP
INIT

2
3
4
5
6
7
8
9
10
11

2
3
4
5
6
7
10
11
12
13

Read
Write
(Reserved)
Position
(Reserved)
Diagnose
Get status
Set status
(Reserved)
(Reserved)

The following is a brief description and usage example of each.
OP CODE 0 NOP
This instruction causes the TUS8 to return an end packet. There are no modifiers to NOP. The NOP
packet is shown below.
BYTE
0
1
2
3
4
5
6
7
8
9
10
11
12
13

0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000

0010
1010
0000
0000
000X
0000
0000
0000
0000
0000
0000
0000
001X
1010

FLAG
MESSAGE BYTE CNT
OPCODE
MODIFIER
UNIT NUMBER (IGNORED)
SWITCHES (NOT USED)
SEQ NO. (NOT USED)
SEQ NO. (NOT USED)
BYTE COUNT L
BYTE COUNT H
BLOCK NO. L
BLOCK NO. H
CHECKSUM L
CHECKSUM H

NO DATA
INVOLVED
NO TAPE
POSITION

The TUS8 returns the following end packet.

0
1
2
3

0000
0000
0100
0000

0010
1010
0000
0000

FLAG
MESSAGE BYTE CNT
OPCODE
SUCCESS CODE

4
5
6
7
8
9
10
11
12
13

0000
0000
0000
0000
0000
0000
0000
XXXX
000X
XXXX

000X
0000
0000
0000
0000
0000
0000
XXXX
XXXX
XXXX

UNIT (IGNORED)
NOT USED
SEQ. L
SEQ. H
ACTUAL BYTECNTL
ACTUAL BYTE CNT H
SUMMARY STATUS L
SUMMARY STATUS H
CHECKSUM L
CHECKSUM H
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 TU58 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 TUS8 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 TU58
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 1 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

HOST

WWIW

3.2.3.1 and 3.2.3.2.

TUS8

COMMAND

PACKET

(READ 510 BYTES)

ok
|
|

Figure 3-1

OP CODE 3

DATA

128 BYTES

DATA
128 BYTES

DATA

128 BYTES

DATA

126 BYTES

END

MA-2378

Read Command Packet Exchange

Write, and Write and Read Verify

This op code causes the TU58 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 TUS8 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
TUS8 sends an end packet with the success code set to O (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 TUS58 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 TUSS8 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

BYTES

DATA

128 BYTES

CONTINUE

}

TAPE POSITIONS

AND WRITES DATA

DATA

128 BYTES

CONTINUE

TAPE POSITIONS

AND WRITES DATA

DATA

‘ .

128 BYTES

CONTINUE

TAPE POSITIONS

AND WRITES DATA
<

DATA

CONTINUE

128 BYTES

TAPE POSITIONS
AND WRITES DATA

DATA

108 BYTES

CONTINUE

TAPE POSITIONS AND WRITES
DATA. TUBB ZERO-FILLS REMAIN-

ING 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

3-9

[

TUS8

HOST

CONTINUE

> SEND “CONTINUE” HERE ONLY IF

THE FOLLOWING COMMAND PACKET

IS NOT THE FIRST COMMAND PACKET

AFTER SELECTING MRSP.

COMMAND

PACKET

WRITE

510 BYTES

‘

DATA

CONTINUE

128 BYTES

CONTINUE

{

TAPE POSITIONS
AND WRITES DATA

CONTINUE

{

‘

DATA

128 BYTES

CONTINUE

TAPE POSITIONS
AND WRITES DATA

DATA

CONTINUE

128 BYTES

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

OP CODE 4

(Reserved)

OP CODE 5

Position

OP CODE 6

(Reserved)

OP CODE 7

Diagnose

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

This command causes the TUS8 to run its internal diagnostic program which tests the processor, ROM,
and RAM. Upon completion, TUS58 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 TUS58 returns an end packet.

OP CODE 9 Set Status
This commandis treated as a NOP beeause TUSS8 status cannot be set from the host. The TUSS returns
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 the TUS8 in a
system. These algorithms are written in a pseudo-Pascal language and are therefore only designed to
illustrate the logic of operations involved in causing the TUS8 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.
1.

tudiagnose — Constructs and sends the command packet causing the TUS58 to execute its
built-in, self-test diagnostic. Returns the TUS58 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 TUS58 end packet as the result.

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

tuwrite — Constructs and sends the command packet which causes the TUS8 to write data
from the buffer area specified to the specified TUS8 tape unit. Returns the success code
obtained from the TUS8 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 TUS58 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

data

control

init
continue
Xoff

=
=
=

4;
167
19;

{

}

Define multi-byte packet opcodes

read.opcode
write.opcode

=
=

position.opcode
diagnose_.opcode

=
=

27
3;
5;
7;

end.pack.opcode

64;

{

flags

Define

}

initialization success codes
Hou

success

faillure

}

=127:

{ Define some useful subscript values

}

= 0;
command.flag
command.count
= 1
command.opcode
= 2;
command.unit
= 4;
data.count.low
= 8;
data.count.high = 9;
command.block.low = 10;
command.block.hiagh = 11;

{

Define length of command/data messages

command.length

=
=

data.block

GLOBAL.VARIABLES

{

}

10;
128:

Indicate gquantities used by all
:

single_byte.packet

functions

}

byte;

{ Note the variable lenqth of the array defined bpelow.
Its lenath 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

CALLING_PARAMETERS

{

ARRAY[O0..N+3]

byte;

Parameters defined by the calling routines}

unit.number, block.number :INTEGER; { Specified unit/block}
no.bytes : INTEGER; { Number of bytes in message }
buffer : ARRAY[1..no.bvtes] OF byte; { Data/message space }

3-12

tudiagnose;

{

This

routine

runs

the

TUS8

self=test

diagnostic

routine

}

BEGIN

{

Construct

and

send

the

command

necessary

cause

the

TU58

packet

controller

to execute its self-test diagnostic.
Return the value of the success code
contained in the TUS8 end packet, }
IF

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

tudiagnose

THEN

BEGIN

command.length+2):

get.end.packet

fajilure

END
ELSE

tudiagnose
tudiagnose }

{

tuseek

(unit_number,

block.number);

END;

{

Construct

and

send

TU58

command

should position
block.
This routine
the

TU5S58

end

packet

which

indicates

the

tne

specified unit to the specified
returns the success code sent in
as

its

result,

}

BEGIN
IF

initialize(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] := high(block.number):

send.packet(packet,

Conclude

tuseek

with

end

packet

get_end.packet;

{

command.lenath):

fafilure;

}

END:

tuseek
END;

{

tuseek

turead

{

ELSE
}

(unit_number,

block.number,

buffer,

no.bytes):

Constuct

and send the command packet reqguired
‘no.bytes’ from the unit and block specified,

from
the

the

tape

success

into

code

buffer

contained

space,
in

the

returning
TU58

end

read
Reads data

the

value

packet,

}

BEGIN

initialize(read.opcode)=success

{

Construct
return

low

command
byte,

packet;
high

packet [command.unit]

BEGINWN

operators

byte

‘low’,’high’

respectively

}

unit.number:;

packet [command.block.low]

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

THEN

low(block.numbner);

high(block.number);

command.lenqgth):

3-13

{

Get

data

output

and

stutf

buffer

get.data.packet(buffer)=success
turead := get.end.packet
ELSE turead := fallure

}

THEN

END
ELSE

turead

END;

{

tuwrite

turead

failure

}

(unit.number,

block.number,

buffer,

no.bytes);

{ Construct and send a command packet specifying the
write the data from
unit and block for writing data.
Return the
the specified buffer area to the tape,
success code obtained from the TU58 end packet as the
result,}

LOCAL.VARIABLES
count, data.count
BEGIN

INTEGER?

1F initialize(write.opcode)=success THEN BEGIN

{ Stuff parameters

into command packet }

packet [command.unit] := unit.number;
packet(command.block.low] := low(block.number);
packet(command.block.high] := high(block.number);
send.packet(packet, command.length);

‘get.byte’

{ 1f continue is received, send data;

‘put.byte’are implementation-dependent function

calls

}

data.count

no.bytes

WHILE get.byte=continue

DO BEGIN

THEN

{ Make blocks maximum of 128 bytes eacn }
count := minimum(data.count, data.block);
put.byte(count);

send.packet (buftfer[no.bytes~data.count+1],
count):;
‘

data.count

:= data.count

= count

END;

{

In any event,

tuwrite

}

try for an end packet at end

:= get.end.packet

END

ELSE

END;

{

tuwrite
tuwrite }

initialize
{

failure

(op.Code);

Initializes the TUS8 by sending break characters on the
communication line, followed by the single byte packet
for INIT sent twice,
The specified operation is then
transmitted to the TU58 as either a single byte packet

the

first

(command)

byte

a multi-byte packet,

communication

line

control

BEGIN

{

Set

BREAK

}

set.break.bit;

{

Delay multiple character

error

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.Code;

{

Send

INIT

f£lag

to TUSS8

single.byte_packet

}

init;

put.byte(single_.byte.packet):

get.byte=continue

ELSE

initialize

THEN

initialize

:= success

fajilure:

END; | ihitialize }
send.packet

(buffer,

no.bytes):;

{ Send information contained in

‘buffer’ to TUS8

}

LOCAL.VARIABLES

index,
BEGIN

{

check.sum,

check.word

INTEGER;

Must begin with checksum initialization

}

check.sum := 0;
check.word := 0;

{ Check for even/odd bytes, performing checksum only
the operator ‘odd’ returns a Boolean value
if even;
of TRUE if the argument is odd }
FOR index

TO no.bytes DO BEGIN

IF odd(index) THEN
check.word :=
ELSE BEGIN
check.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) THEN
check.sum := 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);

{

sent

Gets

the data

‘puffer”

from the TU58 and

stuffs

into

}

LOCAL.VARIABLES

index,

check.sum,

data.count

variables

}

INTEGER;

BEGIN

{

Initialize checksum

check.word := 0;
check.sum

{

Look

for

get.byte;

valid data packet

(check.sum<>data)

ELSE

structure

}

THEN get.data.packet

:= failure

BEGIN

{

Get

data

checksum

data.count

packet

from

buffer

the

:=
:=

check.sum

FOR

calculating
being

filled

}

data.count*256;

data.count

buffer{index]

IF odd(index)

THEN

check.word
ELSE

get.byte;

check.sum
index

TUS58,

BEGIN

get.byte;

:= buffer(index]

BEGIN

check.wWord

check.sSum

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;

cheCKk.word

checCck.wWord

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

ELSE

get.data.packet

check.word):;

error

}

get.byte*256;

THEN

fajilure

success

END

END;

{

get.data.packet

}

get.end.packet;

{
as

Gets

result

end

packet

from

the

TU5S8,

returning

success

code

)

LOCAL.VARIABLES

index,

check.sum,

check.word

INTEGER;

BEGIN

check.sum

{
IF

Look

for

get.byte;

valid command

(check.sum<>command)
OR

(get.byte<>end)

packet
OR

THEN

structure

)}

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

3-16

failure

BEGIN
Get success

code

get.end.packet

FLSE

{

Now do

from

command

packet

get.byte:

the checksum calculation

check.sum

:= check(check.word,

FOR

index

check.word
check.word

:=
:=

get.byte;
check.wWord

check.sum

}

get_end.packet*256);

BEGIN

get.byte*256;

check(check.sum,

check.word)

END;

{

Make

sure packet

check.word

was

not

in error

}

get.byte;

check.word := check.word + get.byte*256;
IF check.word<>check.sum THEN
get.end.packet := failure
END

END:

{

check

(argl,

{

get._end.packet

Computes
around

}

arg?);

the

carry

bit

checksum of

technique

TUS8

argl

and

arg2,

using end=

}

BEGIN

{

The function “carry’ returns a value of
1 if the sum of the arguments results in
a

carry;

check

END;

argl

{

check}

{

End

value
+

arg?2

0
+

algorithm

returned

otherwise

carry(argl,arqg?)

definitions

}

3-17

}

CHAPTER 4
INSTALLATION

4.1

INTRODUCTION

This chapter contains installation, configuration, and checkout procedures for all the versions of the
TUS58 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 the2 m (6 ft) power cord can reach a power controller outlet box such as the DIGITAL 861 or
any power outlet.
4.2.2

Unpacking

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

TUSS-EB
Bezel
Mounting brackets
Support brackets

2
24

Support bracket extenders
Phillips trusshead screws 10-32 X 1/2in

6
1
2

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

24
12

Internal lock washers
U-Nut retainers
Kep lock nuts 10-32 X 3/8
Line cord (120 V)

Power Selection

4.2.3

Detachable line cords for 115 V and 230 V, and two fuses are supplied with the TU5S8-DA. The line
cord receptacle meets European IEC standards. A switch on the back of the tape drive rear panel selects 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

Range
90 — 128 Vrms
180 — 256 Vrms

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

e e
B
e
e
R
s
Ts GT

e
o
e e
e

FUSE POST

120/240V

SWITCH

INTERFACE CABLE

CABLE SHIELD

INTERFACE CABLE GROUND
CABLE SHIELD
SCREW

CONNECTOR

AN
o

O
POWER

LINE CORD

POWER

SWITCH

RECEPTICAL

SWITCH

120/240V

SWITCH

FUSE POST

GROUND SCREW

CONNECTOR

(A) NON-FCC COMPLIANT CONFIGURATION

LINE CORD

RECEPTICAL

(B) FCC COMPLIANT CONFIGURATION
MA-783083

Figure 4-1

TUS58-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

4.2.4

Fuse
3/4 A slow-blow

3/8 A slow-blow

Removing Bottom Plates for Controller Board Configuration

The TUSS is shipped prewired for operation at 38.4K baud transmit and receive on RS-423. If a configuration change is necessary, the bottom plates must be removed in order to gain access to the controller board. Use the following procedure to remove the bottom plates. (See Paragraph 4.7 for configuration information.)

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

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

3.
4.

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 (with internal cables still

attached) and placing it rightside-up next to the TUSS.
Rackmounting Procedure

4.2.5

The following procedure enables one person to install the TU58-DA in the rack using a number 2 Phillips screwdriver.

With the power cord and interface cable removed (Figure 4-1), carefully place the TUS8-DA

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

upside-down on a flat working surface so the front of the device is facing you.

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

MA-8474

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 TUS8-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 TUS58-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 bottom 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

10.

Attach the power cord and interface cable and connect to the appropriate device or receptacle. Close the back of the rack.
Install the bezel by pushing into place over the ball studs (Figure 4-8).

4-3

MOUNTING BRACKET

BALL STUD —} |
MA-B473

U-NUT RETAINERS

I E

Y Y EYEEY

20 @ @ ofp)o o @fo)o

T ES \‘\

Installing Mounting Brackets

Figure 4-3

~is
s
o

]

&
&

MA.8472

Figure 4-4

Front Vertical Rail U-Nut Retainers

4-4

VERTICAL RAILS

FRONT VIEW

2.22

(7/8!

TOP OF BEZEL

|©

(5/8)
'
|

(sé{?fsy (gigffa)

+———WIDE

Oe
»

NARROW

—

" oA

WIDE

SPACING

st | O e WIDE

(5/8)

4.76

‘

BOTTOM OF BEZEL

B- S

S
BALL STUD

13.2

(5.19)

FRONT

34.3

]

(13.5)

445

(17.5)

* (s

‘3

13.2

(5.19)

gzgis
{ss,m\

*SUBJECT TO CHANGE

: i&

13i2
(5.19)

?fis}

MEASUREMENTS ARE IN CENTIMETERS EXCEPT VALUES IN PARENTHESES

ARE IN INCHES.

MA-B476

Figure 4-5

Rackmounting the TU58-DA

REAR VERTICAL SUPPORT

%
o

2
o

0
2

2
(2
P

MOUNTING BRACKET

MA.6478

Figure 4-6

Rear Vertical Support U-Nut Retainers

5999

6 9S

REAR VERTICAL SUPPORT

SUPPORT BRACKET

MOUNTING

EXTENDER

BRACKET

Figure 4-7

MA.G4EE

Fastening Support Bracket Extenders

4-6

MA.6485

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.

4-7

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 TUS58-CA. The chassis power
receptacle meets European IEC standards. A switch on the back of the rackmount cabinet selects 110
V or 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.

2.22-%

(7/8

1.59 #

(5/8)

(23/8) (11/8)

1.50 8

(5/8) | 4

{

<+—— WIDE

NARROW

e«—— WIDE

<——WIDE

.
;

BOTTOM OF BEZEL

?f%g;
g

.
599 (0:438)

fl*”;.__—--s

46.5

} i
(18.3)

I &QT ?gES) ! M

FRONT OF BOX (BEZEL REMOVED)

(5.19) _¥

1(0.25)

@“—T
1

365

318
*-F7
(1.25)
@

P —fo

13.2 (316 e 4

(0.375 [

TOP OF BEZEL

O-

2.86

6.04

)

FRONT VIEW

—

(0.50)
3

1.438)

48.3

5.24

(19.0)

(2.08)

13.2

FRONT

(5.19)

34.3

(13.5)

44.5

3.81

" (1.5)

{17.5)

13.2

(5.19)

]
13.2

(5.19)

;

SUBJECT TO CHANGE

48.3

o0)

MA-2384

Figure 4-10

Rackmounting the TU58-CA

CABLE SHIELD

GROUND SCREW

o WIIME 110/220 V SWITCH
.

INTERFACE

D CABLE

FUSE POST

CONNECTOR

LINE CORD RECEPTACLE

MA-2387

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.

4.3.4

Reinstalling the Module

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-B284

Figure 4-12

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 cage 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.

Replace the bezel and power cord.

4-11

4.4 INSTALLATION (-EA AND -EB VERSIONS)
The TUS8-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 TUS58 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.
4.4.1

Tabletop Installation
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.

Install the four rubber feet using the four 1.3 c¢m (1/2 in) Phillips head screws to secure
them to the bottom plates (Figure 4-13).

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

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

4.4.2
1.

Perform steps 1 and 2 as above.

Solid Mounting Installation

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 TUS8 rightside-up and place it in the desired location.

MA.gd471

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 a
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 TUS8-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 TU5S8-VA to the SB11 (or BA11-VA)
1.

Attach the four rubber feet to the TUS8-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 méuntmg
screws, so bezels or panels must not touch the drive.

4-13

* 4 MOUNTING BRACKETS

AND SCREWS WITH

LOCKWASHERS FOR MOUNTING
TOBATIVAORTO
HANG MOUNT

TU58-VA

DECTAPE Il s

;

SCREWS WITH LOCKWASHERS FOR |

MOUNTING TO THE TU58 VA

USE METAL BRACKETS WITH

10 32x 1/2 INCH SCREWS FOR
| SOLID MOUNTING
|

L7,

HARDWARE KIT

1“7 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.
MHA-4333
MA-8841

Figure 4-14

Mounting Choices for the TU58-VA

SB11 OR
BA11-VA
e

=
P

|
|
CPU SLOT

KD11-HA

Zand

MXV11-AC

(OR EQUIV-

7
SERIAL LINE
UNIT (SLU)

SCREW

1/0

ALENT)
a—

OPTION

3
SLOT

T _OPTION
SLOT
4

/
S

INTERFACE

GROUNDWIRE

TO DC SOURCE

o\ BA11.VA

ORSB11

T~4"Rs232.C OR Rs423
|

CONNECTOR ONLY

FOR EIA USE (CONSOLE)

TUS58.VA
MR-4334
MA-BEB42

Figure 4-15

Interfacing the TU5S8-VA

4-14

9.68

(3.812)

5715 (.19)

8.18

(3280) TYP

(322)
i

5.13

(2.02)

)

1.65

(.65}

2.36

DEC TUS58-K CARTRIDGE

(93¢

8255

isT;

1.60
(0.62}

(1.43) ?{223
o

;

363

{;?}

1.80

<+-3.50 %

MEASUREMENTS ARE IN

(1.38) DIA

‘

8,89

(3.50)

CENTIMETERS EXCEPT

VALUES IN PARENTHESES

ARE IN INCHES.

MA-2068

Figure 4-16

Drive Outline Drawings

4-15

24.85

)

1.27

{.50)

T"'

(9.79)

14.76

{5.82)

—

AMP HEADER #B87633-6

MATE: AMP #871569-6

AMP #87272-8

.48

{.19)

DECPT #12-13506-04

WITH # 87027 CONTACTS MATE: AMP #87133-5

HEAT SINK:
3.0 (1.2) ABOVE

0.5(0.2) BELOW
g
¥

(1.8}

08
o
(.27)

1.27

\
\

le—

“

5] It6
sLIGND

DRIVEO
r

14.64

(5.77)

SERIAL INTERFACE

\ CONNECTOR

1 3| |SNP connecTor

/ SINK
f"féfigg/
'

13.18

WITH #87124-1 CONTACTS
‘a%

[

[ 122

4.06
R(.6)

|
f

‘

(5.19)
12.32

12.24

(4.85)

(4.82)

{

17.73

‘

(6.98)

58
(9.50)

2472

(9.73)

MEASUREMENTS ARE IN CENTIMETERS EXCEPT VALUES IN PARENTHESES ARE IN INCHES
MEASUREMENTS ARE *.013 (.005) CENTER TO CENTER
MA-2370

Figure 4-17

Board Outline Drawings

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

CAUTION
The mounting surface for the drives must be flat
within 0.64 cm (0.025 in).
Mounting hardware is included with each drive. There is a shoulder screw, spring, and flat washer for

each of the four mounting holes. Figure 4-18 shows one assembly; in addition to the flatness specification for the mounting surface, there is a specification for the depth of the shoulder screw in the mounting surface. To prevent extra compression of the spring, the shoulder screw should meet the top of the

mounting surface. Any tapering of the mounting hole must be limited so that at the screw’s diameter of

0.419 cm (0.165 in) the edge of the shoulder is not more than 0.076 cm (0.030 in) below surface.

4.7 INTERFACE STANDARDS SELECTION AND SETUP
The TUS8 is shipped with factory-installed jumpers for a transmission rate of 38.4K baud and the RS423 unbalanced line interface. A variety of standards and rates may be selected by changing the jump-

ers on the controller board. Table 4-1 provides a list of all the pins on the board and their functions,
including the wire-wrap (WW) pins, interface, and power connectors.

4-16

THE MOUNTING

SURFACE FOR THE
DRIVES MUST BE FLAT
WITHIN 0.64 mm.

(0.025in.)

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.)

MAXPENETRATION
OF SHOULDER INTO
MOUNTING SURFACE.

FOUR ON EACH DRIVE

Figure 4-18

4.7.1

MA-E754

TUS58 Drive Mounting Hardware

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 byteis 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 TUS58 i1s
compatible with devices complying with RS-232-C.

The TUS8is 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

SR
RO

e
e
e

O
A

DEe
e

Table 4-1

TUS8 Module Connections

Wire-Wrap Pins

WWI

150 Baud

WWwW2

300 Baud

WW3

600 Baud
1200 Baud
2400 Baud

WW4
WW5

WWe6

4800 Baud

WW7

9600 Baud

WWg§

19200 Baud

WW9

38400 Baud

WW10

UART Receive Clock Input

WW11

UART Transmit Clock Input

WW12

Auxiliary A (to interface connector pin 1)*

WWi13

Auxiliary B (to interface connector pin 10)*

WWi4

Factory Test Point

WWI15

Ground }

WW17

RS-423 Driver

WWI18
WWI19

RS-423 Common (Ground)
Transmit Line+

WWw20

Transmit Line —

WWi16

Boot

WW21

RS-422 Driver+

WW22

RS-422 Driver
—

WW23

WWwW24

}

Connect together for auto-boot

on power-up.

Receiver Series Resistor

(Jump for RS-422)

Serial Interface Connector
J2-10
J2-9
J2 -8
J2 -7
J2-6

Power Input Connector
J1 -1
J1-3
J1-5
J1 -6
Drive Cable
J3,4-1

Auxiliary B
Ground
Receive Line+
Receive Line
—
Key (no
connection)

J2-5

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

Ground
Transmit Line
—
Transmit Line+
Ground
Auxiliary A

+12V
Ground
+5V
Ground

J3,4-2
J3,4-3
J3,4-4
J3,4-5

Cart L
No Connection
Permit L
Signal Ground
Motor +

J3,4-9

J3,4-10
J3,4-11
J3,4-12
J3,4-13

LED
Head Shield Ground
Erase Return
Erase 1
Erase 0

J3,4-6
J3,4-7
J3,4-8

Motor —
+12V
Tachometer

J3,4-14
J3,4-15
J3,4-16

Head Return
Head 0
Head 1

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

4-18

1200

300

150

500

\"’?’,;&
¢

\f,g,

{f%

20
%

CABLE

)

LENGTH
,

30 100
M

{5‘

N&
7,

A‘&

300 600 1K

10K 20K 40K

DATA RATE IN BAUDS
RS-423

Figure 4-19

4.7.2

MA-2368

Data Rate and Cable Length for RS-423

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 other pins in the

group are connected.

4.8

OPERATIONAL CHECKOUT
A confidence check of the operation of the newly installed TUS58 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 TUS58 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 for address
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

DIAGNOSTIC
LED
WW

(Do

TP EL

+
GND

=] BOOT -i-‘;""sw
.

150
4 WW

ols

300
+
600+
12004

2400+

-1

4800+

384K+

-1J

9600+

192K+

2321 17-19

RCV 4 CLK

423118-20

- L

XMIT 4+CLK

AUX A4

AUX s+§"§"

422
WW

21-19

23-24

+4+

22-20

]

—

4+
e

Wniw

rlElz|elE

=
iy
€3

—
1L

—

<
&4

1°l

R
iy

MA-Z2366

Figure 4-20

Interface Selection Jumper Pin Locations

4-20

mm%c?ommmmm

mmmmmmmmmm

38.4 KBAUD RCV + XMIT RS-423

Figure 4-21

9600 BAUD RCV + XMIT RS-423

Factory Wiring

Aa3IA

Figure 4-22 TUS58 Wiring (9600 Baud)

4.8.2. Configuring Interface Modules
This section lists the switch or jumper configurations recommended for DIGITAL’s asynchronous serial

interface modules. These modules connect the LSI-11 QBus or the PDP-11 UNIBUS to the TUS58’s serial
interface. Each module is configured to run at the fastest speed possible (either 9600 or 38400 baud), at
the standard bus address (176500) and vector (300) for the TUS8. For other speeds or addresses, read the
manual for the specific interface. And for TUS8 configuration, see Figures 4-21 and 4-22. The interface
requirements are as follows.

EIA RS-423 voltage levels (RC232-C compatible)
Eight data bits
One start bit
One stop bit
No parity
Break enabled
NOTE

In the following tables, R means a jumper is

removed, and I means a jumper is inserted. ON and
OFF refer to the positions on board-mounted switch
packs. An X means the TUSS8 will work regardless
of the seating.

4-21

Setting

A3
A4
A5
A6
A7
A8
A9
Al0
All

V3
V4
V5
V6

FRO
FR1

NBI
PEV
FEH
EIA

—TAXAATA

CLI1
CL2
CL3
CL4

K KKK

FR2
FR3

A”TTT

Al2

Jumper

RRRTRT R

DLV11-A (M7940)

2SB
NB2

Value

[76500 (address)

300 (vector)

9600 (baud rate)

DLV11-E (M8017)
Jumper

Setting

Value

A3
A4
AS
A6
A7

[76500 (address)

Al0

All
Al2

4-22

Setting

Vé
V7

RO
R1
R2

R3
TO

T2
T3
BG
P
E
1
2
PB

C
Cl
S
S1
H
B
‘B
-FD
-FR
RS
FB
M

Value

300 (vector)

9600 (baud rate)

AARAATTTAIIAIAI
T T AR IXATM

HKAAARARIITM

Jumper

o=
R R

DLV11-E (M8017) (Cont)

Setting

A4
A5

A6
A
A8
A9
Al10

All
Al2

Value

176500 (address)

Jumper

RITRAR

DLV11-F (M8028)

4-23

Setting

\&:

AT RARAA

RO
R1
R2
R3
TO
Tl
T2
T3

V5
V6

> Mmmwmongww m‘*-u

300 (vector)

9600 (baud rate)

DRI
= HKHHK

Value

RARRARXRTDRIBR
= =R
D X R~

Jumper

HKAAAXARID
TM

DLV11-F (M8028) (Cont)

4-24

DLV11-J (M8043)

Use channel 0 of the factory-configured module for the TUS8 interface. Change the baud rate for channel
0 from 9600 to 38400 by removing the jumper from O to N and connecting O to Z. Refer to Figure 4-23.
Channel 0 is now compatible with the factory-configured TU58 with address 176500 and vector 300.

CHZ AND

CHO AND

CH3EIA

CHIEIA

SELECTION

—1C

R3X2

2X3R

o7
©

2
3

' Y
N

" R23
BAUD RATE

o8 8M72

Niie - 8

§ 8- N7
e
& M3

& 98
8 N3

SELECTION

LuT

CH1 TERM RESISTOR

——CHO TERM RESISTOR

—=——={CHZ TERM RESISTOR
~CH3 TERM RESISTOR

CcHO|

gmi COMMUNICATION LINE
cH2 [ PARAMETERS

CH3

ADDRESS AND
A5 €3 )

VECTOR JUMPERS

AGEe&

AlZe o8

AL Bl
{A?*t

Allle o

Alls o8

e -8

CZ2e o

BXH

Cie -8

vsde ¢ |

01X

V7 o8

AR
& &b

BREAK SELECTION

]

(CHANNEL 3)

MR.1E23

MA-5E82
SHR-0056-84

Figure 4-23

DLVI11-J Factory Configuration Summary

4-25

MXV11-A (M8047)
Use channel 0 on factory-configured interface (address 176500 and vector 300). Refer to Figure 4-24
and Table 4-2

N
J2

|CHANNEL 1

| CHANNEL
O

J66 J6b

J64 J63 J62 JB1 J60 J5S
Lt

N
A

]

W
& J58

& J57

ggfi]

155
J54

J62
451
J50

& J48

J48

E J47

J48
J45

& J44
® .J43
# J42
& J41

& J40

J38

& 36

# I35
J34

ej28

QJ‘E?’?

J33 p—eJ
J32

§;§

i
;

& 25

J24 ‘

*J23
c.}?’é

421

®.i20

J18+

)18~

aji7
e J16

#.ji4

® 113

& .J12
#J11
& J10

s B
.

C: s 8o

J8Js J4 i3

MR-32884
MA-6828

EHR.O085.84

Figure 4-24 MXV11-A Jumper Locations

4-26

Table 4-2

MXV11-A Standard Factory Configuration

Wire~Wrap

Pins

Function

From

Level

RAM bank 0

J30
J32
J31

J31
J33
J32

L1
L1
L2

SLU CHO,
address 177560

J23
J24

J18
J19

L1
L1

SLU CHI,
address 177560

J28
J26
J25
J27

J10
J15
Ji4
J13

L2
L1
L1
L1

ROM bootstrap (TUS8)

J37
J21
J34
J33
J29

J38

JI15

L1
L1
L2
L2
L2

J22
J37
J39

SLU

CHO0(300)

J33

J57

vectors

CH1(60)

J54
J56
J54

J52
J51
J55

L1
L1
L2

SLU parameters
(eight data bits, no

J59
J62

J61
J64

L1
L1

parity bit, one stop
bit)

J60
J61
J59
J63

J63
J62
J66
J65

L1
L2
L2
L2

Baud

CHO(38400)

J45

J50

rates

CH1(9600)

J46

J48

Bread generation
(Half option)

Crystal clock

J68

J67

4-27

DL11-D (M7800 or M7800-YA)

Jumper

Setting

Value

A4
AS

176500 (address)

A8
A9
Al10
V3

300 (vector)

V5
V6

V7
V8

2SB
EPS
NB2

J1
N2
J3
J4
J5

J6
J7
J8
J9
J10
JI1

ATATRAT
T AR

—AXT
A

Baud rate switches
Position 8 for 9600 baud receive and transmit with speed group 4 crystal (4608 MHz).

4-28

DL11-E (M7800)

Jumper

Setting

A3
A4
A5

Value

176500 (address)

A6
A7
A8
A9
Al0
V3
V4

300 (vector)

V5
V6

Baud rate switches:

NP
2SB
EPS
NBI
NB2
Nl

mARARAXT
R

Position 8 for 9600 baud receive and transmit with speed group 4 crystal (4608 MHz).

J1
J2
J3

J4
J5
J6
J7
J8
J9
J10
JI1

4-29

DL11-W (M7856)
(address 176500, vector 300, speed 9600 baud)

Switch
Number

Position
Not used (Switch

Q0 ~J3 ON Ln B

Lo B

placement unspecified)

B L) DD e
<o

e ND OO0 S ON W
) DD e
B
N W
OO0 =T
— N

e W

Off
Off

ON W

Off

Switch Pack

On
Off
Off
On
Off
Off

Off
Off
Off
On
Off
On
On
On
Off

4-30

4.8.3

Checkout of Drive Command Function
1.

Insert a tape cartridge into drive O (left side). (The TUS8 should have sent Continue (20g)

already.)
2.

Transmit the following string of octal numbers to the TUS58. (Consult the programming chapter
for an explanation of this format.)

204
212

The TUS8 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-31

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.
5.1.1 Installation
The indicator (which may be any device capable of handling 30 mA with a forward voltage less than 1.8
V) is 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).

MA-Z3B5

Figure 5-1

Installation of Run Indicator

5-1

5.2

BOOT SWITCH

5.2.1

General

Special provision has been made for interfacing the TUS58 to the LSI-11 ODT keyboard interpreter.
The TUS58 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 or
reload and restart an unsupervised process controller or similar application. The Boot switch allows a
manual reboot without powering down to cycle the automatic sequence.
NOTE
Boot mode does not work in any DIGITAL operating system environment.
5.2.2

Operation

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

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

When the TUSS8 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 TUS58 begins the boot procedure.

The boot procedure positions the tape in drive 0 to block 0, sends Break to the host, and transfers ASCII characters from the tape to the host. A delay is inserted between characters to allow for the echo
from the LSI-11. If the character sent is ASCII 0 — 7, this delay is one character time at 9600 baud.
Any other character is interpreted as a control character, and time is allowed for 15 characters of echo.
The TUS58 exits the boot mode following the transfer of the terminating character ASCII G (147g) 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 O 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
RSP SEQUENCE

*NEWTAFE®

RSF

Seaquence

Checksum

Calculation

Examrle

12
]
0
0
0
0
0

carryr

SEEK

ELOCK

777

1
12
0
0
0

2
5
0
0

Octsal
Addition

377

(PR

377
1
&

0000101000000010
0000000000000101

2
12
5

0000000000000000
0000000000000000
0000000000000000

0
0
0

0
0

0
fors

SEEK TO
ELOCK ©

Bimary
Addition

APPENDIX C

SAMPLE DEVICE HANDLERS

232k XX XeKke N2 EeReReReReRe e e EeReNeRe ke XeReReie ke ke e ke EeEeRe ke R EeEe R Re e Ec oo Re e o R o oo N o NoRo R p N o Ny

ccceeececceececceeeeecececeecceeccecececececcecececceccececcececccecceccccecceceecceeecccccec
c

TTTTTTT U
T
T
T
T
T
T

U 5555555

88888

U
U s
8
8
u
us
B8
8
u
U 555555
88888
U
u
5 8
8
U
U
5 8
&
UUuUUUU 555555
B8888

ORTRAN

C
c
C
C
C
C

SUPPORT
P ACKAGE

CCCcCeeceecccececeececececcceceeceececceceecececcecceeccecceccecececececececececcccecececccecececcecceccc

The following program listing contains a complete TUS8 device
handler package written entirely in PDP=11 FORTRAN IV,
Wwhen
used with the RT=11 FORTRAN IV compiler and object-time system,
it

can

built

into

ROM/PROM/EPROM

based

LSI=11

microcomputer

applications.
The program
ierror

implements

TUREAD(

"bytecount"

unit

"unit"

TUWRIT(
write

bytes

from

random=access

unit,

block,

"bytecount"

TUSEEK(

buffer,

bytecount

the

into the data area

"huffer" onto TUS8
access block noted
ierror

user=program callable entry points:

block,

Read

starting

jerror

unit,

four

unit,

block

buffer,

oytes

from

TUS8

drive

specified

specified by
"plock"

bytecount
the

drive "unit",
by "block",

block

)

data

"buffer",

the

cartridge.

)

area

starting

specified

the

randome=

)

Position the TUSS8 és:tridge located in drive "unit" at
the

ierror

random=access

TUDIAG(
Run

In all

four

codes,

ierror

value

tne

block

specified

"block",.

)
TUS8

cases,

internal

the

controller

functions

return a

diaagnostic

standard

function,

set of

error

follows:

meaning

error

code

Normal]

1
-]
-2
-8
-9
-11
=17

Success, but retries were required
TUS8 failed self=test (TUDIAG)
Partial operation (end~of=-medium encountered)
Invalid unit number was specified
No cartridge 1s mounted in specified drive
Specified cartridge is write=protected (TUWRIT)
Data check error on cartridge

success

OO OOO0NOaG0000000 Q0000

This

Seek

=33

Motor

=48

Invalid

operation

-55

Invalid

record

=127

Communications

software

through
which

The

-32

software

mode

only

This

program

that

DLVii=J,

receiver

CSR

operates

for

(block

stopped

assumes

DLV11,

bhas

error

not

(TUS8

the

code

error)

(error

number

(bad

error

between

TUS8

controller

DLVii=E,
address

the

founa)

hardware

this

block

program)

number

host
is

and

passed)
TuS8

interfaced

DLV11=F,

MXVil

assignment

176500(8).

interface

non=interrupt=driven

simplicity.
is

neither

licensed

nor

supported

Digital

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

CCCCccereeecceeececeeeeccececcccecececececcececececcececcceceecccecececcececcecececcceccceccececcccccce

oo NoNe

INTEGER

FUNCTION

Runs

TUSB

coace

SRS’

controller

function

IMPLICIT

COmMON

function,

returning

success

(a=2)

packet(6)

command

packet

with

the

DIAGNOSE

operation

code.

Init(7)

(Tudiag.ne.0)

GOTO

100

sEe

diagnostic

result,

INTEGER

/cmdpkt/

Initialize
Tudiag

Tudiag

Now

transmit

CALL

And

the

packet

the

TUS5K

the

diagnostic

controller,

Sndpkt(packet,12,0)

ask

Tudiag

for

the

results

the

end

packet,

Getend(0)

RETURN

END

OO0

INTEGER

FUNCTION

Positions

by
as

Tuseek(

cartridge

unit,

"unit"

"block", returning the
the function result,

block
to

success

)

random=access

code

from

block

specified

TUS8

controller

the

oNeRY

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

Initialize

command

packet

with

the

POSITION

TUS8

controller

operation

code

Tuseek

3 2

= Init(5)
(Tuseek .,ne,0)

unit

packet (6)

plock

Transmit

s Ee g

CALL

100

GOQTO

packet(3)

And

command

the

Sndpkt(packet,12,0)
ask

Tuseek
RETUKN
END

the

100

for

the

status

Getend(0)

the

operation

from

the

end

packet

QOO0
0

INTEGER
Reads

into

FUNCTION

"pytcnt®

the

access

code

data

block

from

Turead(

pbytes

area

from

the

specified

"block"

the

unit,

TUS8

the

block,
TUSB8

buffer,

drive

controller

selected

"buffer",

cartridge,

the

bytcnt
by

starting

Returns

function

)
"unit"®

the

random=

success

result,

IMPLICIT

INTEGER (a=2z)
buffer(bytcnt), bword(2)

BYTE

aQ0On

COMMON /cmdpkt/ packet(6)
EQUIVALENCE (iword,bword)
Build

Turead

READ
=

command

packet

and

send

the

TUS8

controller

Init(2)

500

mwwn

IF (Turead,ne,0) GOTO
packet(3)
unit
packet(5)
bytent
packet(6)

block

3
3 0OY

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

the

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

datcnt

chksum
odd

100,

odd

Getpyt()

chksum

TUS8

GOTO

(odd.eq.0)

GOTO

400

not

data

packet

bword(1)

Getbyt()

bword(1i)

100

bword(2)

Getbyt()

Check(chksum,iword)

buffer(index)

pbword(2)

index

(odd.ne,.0)

chksum

bword(i)

Getbyt()

bword(2)

Getbyt()

(chksum.ne.iword)

GOTO

i=1,datcnt

!Proceed

datcnt*256

400

,not.odd

hksum

s NNy

bword(2)

GOTO

Check(chksum,iword)

GOTO

500

not

data

packet;

unit,

block,

buffer,

area

specified

Found

packet

Turead

500

from.the

bpuffer(index)

100

packet

chksum

data

which

try

for

end

packet

Getend(chksum)

RETURN
END

INTEGER
Writes

FUNCTION
"bytcnt®TM

TUS58

drive

Returns

bytes

from

"unit",

success

IMPLICIT
BYTE

Tuwrit(

code

INTEGER

data

starting
from

TUS8

bytcnt
by

random=access

controller

)

"pbuffer"®

block

function

"block",
result,

(a=z)

buffer(bytcnt),

bword(2)

Ty YO

COMMON /cmdpkt/ packet(6)
EQUIVALENCE (iword,bword)
Construct

Tuwrit

wRITE

Init(3)

(Tuwrit.ne,0)

command

GOTO 500

packet(3)

unit

packet(5)

bytcnt

packet(6) = block
CALL Sndokt(packet,12,0)

packet

and

transmit

the

TUS8

(@
YOO

datcnt

Prepare

bytent
to

transmit

new

data

packet

checking

for

CONTINUE

flaqg

chksum

Getbyt()

(chksum.ne,"020)

CALL

GOTO

400

!Proceed

Putbyt("001)

count

!Transmit

MinO(datcnt,128)

!Make

400

data

packets

CONTINUE
flag

maximum

128

Putbyt(count)

CALL

Sndpkt(puffer(bytcnt=datcnt+i),count,count*256+"001)

GOTO

datent

byte

not

CALL

datcnt

{0utput

packet

count

for

bytes

packet

count

rReceived

flag

Tuwrit

Getend(chksum)

was

not

CONTINUE,

Try

for

END

packet,

RETURN

OO0

END

INTEGER

FUNCTION

Check(

Computes

16~bit

checksum

technique

for

IMPLICIT

TUS8,

INTEGER

Sum

)

1is

returned

and

using

end=around

carry

function

value,

bit

(a=2z2)

sEeNe Ry

e ReNoRe'

check

neither

possible

(

both

7
input

operand

({.,0or.3).g9e,0
inputs

)

have

has

GOTO

high=order

set,

carry

200

high=order

bit

set,

carry

always

QOO n

generated

B
o= Oy OO
oW

(

(i.,and,3).1t.0

only

100
bit

has

high=order

the

sum

does

check,1t.0

)

end=~around

check

not

GOTO

Perform

GOTO

one

only
(

)

have

set,

its

then

carry

high=order

bit

occurred

set

200

carry

required

RETURN

END

OO0

oo
RO N

INTEGER

Gets

TU58

controller

byte

Getbyt

from
to

the
the

serial
host

interface

INTEGER

wait

for

input

(Ipeek("176500).and.%"200).eq.,0

Get

(

character

the

(a=2z)

character

from

data

available

buffer

= Ipeek("176502),.and,255
WRITE(6,222)GETBYT
FORMAT(® R",03)
RETURN
END

connecting

machine.

IMPLICIT

Getbyt

FUNCTION

and

(DONE

)

flag

GOTO

remove

set)

extraneous

bits

SUBROUTINE

QOO

anoan

BYTE

Writes a byte
controller to

outbyt

)

to the serial interface
the host machine,

IMPLICIT

INTEGER

wait

output

for

connecting

the

TUSS

(a=z)
interface

ready

(DONE

bit

set)

IF ( {Ipeek(”17$504),and,”2GG);€Q,G )} GOTIO0 10
Transmit
CALL

N O

Putbyt(

OUTBYT

character

by moving

to data

buffer

Ipoke("176506,0utbyt)

WRITE(6,222)0UTBYT

FORMAT(®

T7,03)

RETURN
END

IMPLICIT

INTEGER

Initialize
Init

opcode

Loop

OO0

area

with

opcode

specified

"002

i
o B

R
LI

allow

eight

retries

entire

initialization

procedure

packet

]

10%256

packet(2)

packet(6)

QO
r
<

command

packet(4)
packet(5)

50,

Set

J=1,8

BREAK pbit

in output

serial

CALL

Ipoke("176504,"000001)

wait

for

BREAK

transmitting eiaht

interface

cause

framing

NUL

characters

error

under

(XCSR)

TUS8

po 10, I=1,8
CALL Putoyt("000)

Remove BREAK condition on output interface
CALL

aOnn

)

(a=2z)

packet (1)

packet(3)

sNeRg

opcode

/cmdpkt/ packet(6)

(LB

oSNy

COMMON

oNeRe

Init(

Initializes TUS8 controller for operations.
Returns 0 if properly initialized, =127 otherwise,

Lo i

oo NeoNe

INTEGER FUNCTION

Ipoke("176504,"000000)

Discard

any

idummy

Output

two

(possiply

INIT

commands

Putbyt("004)

CALL

Putbyt("004)

wait

for

Getobyt().eq."020

(

character

Ipeek("176502)

CALL

CONTINUE

erroneous)

check

for

TUS8

CONTINUE
)

GOTO

controller

flag
100

response

input

buffer

<
<

no success after eight retries,

Init =
RETURN

report error

=127

END

a3
0

SUBROUTINE Sndpkt(buffer,bytcnt,chkini)
Transmits

a command or
sending "bytcnt" bytes
checksum,
Checksum is

data

packet

the

TUS8

controller,

from "buffer", followed by the updated
initialized from the "chkini" argument,

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

odd

Loop

100,

odd

transmit

(odd.eq.0)

GOTO

odd=numbered

contents,

one

remember

bvte,

bword(1)

buffer(i)

time

for

checksum

calculation

100
checksum

calculation

for

each

byte

pair

evens=

byte

bword(2)

chksum

Check(chksum,iword)

byte

bword(2)

Perform

3 O3 O3

packet

i=1,bytent
,not.odd

numbered

chkini

GOTO

either

buffer(i)

case,

output

byte

interface

CALL

Putbyt(buffer(i))
(odd.ne,0) chksum =

PESNS!

Output

computed

Check(chksum,iword)

checksum

for

packet

iword = chksum
CALL Putbyt(bword(1})
CALL Putbyvt(bword(2))
RETURN
END

30 3 OY

INTEGER

FUNCTION

Getend(chkini)

Reads an end packet
as

the

function

IMPLICIT

from

value

INTEGER

the TUS58 controller,

the

success

code

from

returning

the

packet,

(a=z)

BYTE

bword(2)
EQUIVALENCE (iword,bword)

chksum

chkini

If input checksum
already been read
IF

e
R K

(chksum,ne,0)

chksum

Getbyt()

Check

for

valid

not

zero,

the

caller,

GOTO

END

packet

first

byte

the

packet

has

"chkini"

value,

structure,

(chksum.,ne."002)

GOTO

500

fMust

have

flag

(Getbyt().ne.10)

GOTO

500

IMust

(Getbyt().ne,"100)

have

byte

count

GOTO

500

IMust

C-6

nave

opcode

COMMAND

END

C
C

If a valid packet
store it

found,

read

success

code

byte

and

Getend
chksum

=
=

Getbyt()
Check(10*256+4+"102,Getend*256)

Read and discard

remainder of

packet,

updating checksum

C
DO

100,

i=1,4

bword(1l)
bword(2)

100
C

chksum

Read

= Getbyt()
= Getbyt()
Check(chksum,iword)

transmitted checksum and compare with computed value

bword(1l)

Getbyt()

bword(2)

= Getbvt()
(iword.eg.chksum)

GOTO

600

Indicate

checksum or

500

Getend =

«127

600

RETURN
END

transmission error

TUS8

+IDENT

/0,1/

NON=INTERRUPT

DRIVEN

TU58

HANDLER

The following program listing contains a complete TUS58 device
handler package written in PDP=-11 MACRO assembly lanquage,
implements

IERROR

Read

starting

IERROR =

TUWRIT(

four

FORTRAN=callable

TUREAD(

UNIT,

BLOCK,

"BYTECOUNT"

bytes

from

unit

"UNIT"

BUFFER,

the

TUS®

entry

BYTECOUNT

drive

into the data area specified
random=access

UNIT,

block

BLOCK,

points:

"BLOCK"

BUFFEP,

)

specified

by
on

"BUFFFER",
the

cartridge.

BYTECOUNT

)

WE MR

program

ME WE M

The

RE WE

.TITLE

Write

"BYTECOUNT"

WS WE WE R

"BUFFER"
block

noted

IERROR

WE RS

onto

Position

WE
WE M

the

"UNIT",

data

area

startinag

specified
at

the

random=access

cartridae

block

TUDIAG(

BLOCK

)

located

specified

drive

"UNIT"

the

"BLOCK",

)

IERROR

UNIT,

TUS58

random=access

from

drive

"BLOCK",

TUSEEK(

the

bytes

TU58

the

TUS8

internal

the

functions

controller

diagnostic

function.

codes,

all

cases,
as

return

standard

set

status

follows:

IERROR

VALUE

MEANING

STATUS

CODE

Normal

Success,

WA WS

HRE WE RS WE WM

WR W

Run

success

-1

TU58

-2
-8

Partial
Invalid

out

failed

retries

self~test

were

required

(TUDIAG)

operation (end=of=medium encountered)
unit number was specified

-9
-11
-7

No cartridge is mounted in specified drive
Specifiled cartridge is write=protected (TUWRIT)
Data check error on cartridae

-32
-33

Seek

Motor

error

(block not found)
stopped (TUS5& hardware

C-7

error)

=48

Invalid

ME Me

=55

Invalid record
Communications

code

(error

this

program)

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

This

through

which

subroutines

-127

operation

software

space

assumes

DLVii,

has

that

DLVil=Jd,

receiver

were

CSR

are

TUS8

address

written

performances

the

DLVii=E,

with

not

controller

interfaced

DLVii=F,

MXVii

assignment

176500(8),

goal

readability:

interface
These

time

and

WME

This

Eguipment

WE e

optimal.

program

for its reliability
otherwise,

neither

computer

liscensed

and

system,

may

Digital

any

nor

supported

DIGITAL

copied

modified

assumes

responsibility

hardware,

for

Diacital=supplied

use

any

Corporation,

Define

Symbol

packet

flag

Definitions

byte

and

Data

Area

codes

«SBTTL

F.DATA

;

Data

F.CIRL

;

Control

F.,INIT

;

INIT

F.CONT

=
=

20
23

:
;

CONTINUE packet
XOFF packet

Define

Control

packet

ob=codes

bLT

F.X0FF

packet

;

Define

Macro

O.READ

;

perform

read

O.wRIT

;

perform

write

0.PCS
0.DIAG

=
=

5
7

;

perform

seek

0.END

100

:
s

packet

controller

interface

address

DLRCSR

176500

DLRBUF

DLRCSR+2

DLXCSR

DLRCSR+4

DLXBUF

DLRCSER+6

send

pyte

perform

operation
overation

operation

self=test
an End packet

assignment

TUSS

BPL

LAB

MOVE

ARG,

+ENDM

PUTBYT

PUTBYT
ARG,
@eDLXCSR

Macro

wait

«MACRO
TSTR

NOTE:

ARG

LAB:

into

the

LAB:

Area

byte

from

the

+MACRO

GETBYT

@#DLRCSR
LAR

TUS8

the

parity

bit

will

sign=extended

ARG,

@¥DLRBUF,

?LAB

ARG

GETBYT

area

+PSECT
¥

TSTB
BPL
.ENDM

Data

®R#DLXBUF

high=byte

MOVE

;

for
is

7?7LAB

used

USERSD
build

Rw,

Control

LCL,

REL,

CON

packets

PACKET:

word

+BYTE
« WORD
used

collect

10.
0,

;

Control

packet,

length

byte=pairs

for

16=bit

checksum

calculation

10,

;
AQRD:

Pure

+BLKW

(RUmM=able)

;

follows

code

I, LCL,

.PSECT

USERS$I

Rw,

+SBTTL

TUREAD

Read Data

REL, CON

From TUS®

TUREAD

¢
H

Description:

See

module

heading

;

Inputs:

7
:

O(RS)

points

= 4

2(R5)

;
H
;

4(RkR5) = address of block number word
6(k5) = address of callers input buffer
8.(R5) = address of bytecount word

: Outputs:

RO =

five

address

word
unit

standard
number

FORTRAN

arqument

block

byte

status code

16=pit

Build

INIT

injitialize

TST

;

BNE

50s

return

;

operation

store

unit

:
;

store
store

byte count
block number

:
H

CALL

points

TUREAD::

Control

#0,READ,

MOVB

@2(R5),

MOV

@K, (R5), PACKET+S8,
@4 (KS5), PACKET+10,

the

TISSH

error

caller

Control

PACKET+2
PACKET+4

packet

the

"ReaD"®

numper

TUSSH

Send

the

occured,

packet

MOVHE

MOV

error

CLR
CALL

zero

SNDPKT

Data

packets

initial
the

from

TUSSE,

packet

bytes

send

checksum

Control

followed

packet
an

End

packet,

#F.DATA

each pair of characters

20s:

characters

the

20s

GETBYT

WORD

MOVE

wORD,

30s

GETBYT

wORD+1

ADD

wORD,

ALC

MOVB

WORD+1,

Data

packet,

(R 1)+

(R1)+

#ORD

current

byte

checksum
count

even/odd

byte

flip=flop

updat ing checksum as

received.
he

COM
BEQ
CLK

restore

flip flag
branch if second character
puild character pair
with next data character
store data byte in callers

second

0s:

all

get

Bron Wl

Receive

clear hi=pyte
form initial cnecksum

packet,

Data

buffer

TUSS8

SWAB

CLR

callers

from

B1S

R2
R2,

not

byte

#°C<377>,

SwAB

address
flag

check for End packet
aet byte count from TU58

BIC

update

KO,

90s

K1
get

CMPEB
BNE
GETRYT

with

6(RS),

MOV

GETEYT

Wem

Receive

number

#PACKET,

MOV

store

C-9

byte

pair

buffer

palir

checksum

end-around

data

byte

carry

callers

buffer

30s:

SOB

R2,

TST

10s

packet,

;

loop

until

finish

odd

byte

number

count

data

zero

bytes

;

BEQ

408

ADD
ADC

Receive

wORD,

checksum

from

TUS58

and

compare

checksum

computed

value

;

408:

GETBYT

WORD

GETBYT

WwORD+1

CMP
BEQ

Checksum

WORD,

error,

get

compare

Return

error

l16=bit

the

checksum

with

samne,

computed

checksum

get

Data

packet

error

code

code,

*®

QBV

50s8:

#”IZ?t:

R§

RETURN

ChecCck

packet

90s$:
scaller

was

received

see

that

JMP

GETEND

«SBTTL

TUWRIT

from

the

TUS8

End

packet.,

;

set

function

and

return

that

;

was

not

check

End

value

caller

Data

packet,

packet

and

return

Send

Data

TUS8

TUWRIT

;

Description:

;
;s

See

module

heading

Inputs:

H
;
;

RS = address
O(RS) = 4
2(R5)

address

unit

4(R5)

address

block

6(R5)

address

output

;

B.(R5)

;
;

Outputs:

address

16=-hbit

five

status

word

standard

number

FORTRAN

arqument

block

byte

number

word

buffer

bytecount

word

code

TUWRIT::

Build

Send

CALL

INIT

TS1T

BNE

99s

Control

packet

MOVE

#O.WRIT,

MOVR

@2(R5),

MoV

8. (R5),

MOV

@4 (R5),

the

Control

initialize the TUSSH
if unsuccessful,

;

return

;

send

the

#PACKET,
#12.,

CLK

CALL

SNDPKT

ov=code

set

unit

number

PACKET+8,.

set

byte

count

PACKET+10,

;

set

bloCk

MOV

@8, (R5),

MOV

6(R5),

TUSSH,

packet

MOV

caller

PACKET+Z

PACKET+4

MOV

the

"WRITE"

number

TUS8,

;

address

number

;

initial

send

the

;

number

address

;

C-10

of
of

packet
bytes

send

checksum

packet
of
of

bytes

left

callers

data

send
nuffer

; Send one or more Data packets to the TUSSE,
;

10s:

GETBYT

BNE
PUTBYT

908
#F.DATA

CMPR

RO,

MOV

CMP
to

208

check for End packet
send Data packet flag

assume

if less than

; RESET R4 to actual number left
: send byte count
: RO = address of packet to send
¢ K1 = lenath of packet

not

CONTINUE,

128

bytes

left

R3,
208

MOV
PUTBYT
MOV
MOV

R3,
K4
R5,
R4,

MOV

R4,

R2Z

SwAE

#F . DATA,
SNDPKT
R4, R3

i0s

R4,

A byte was

See if the packet

;

99s:

RO
R1

ADD
CALL
SUB

;

908

128,

bytes left

send,

ADD

¢
:

#128.,

BHIS

received

SBTTL

TUSEEK

update data

buffer

pointer

; wait for acknowledgment from TUSS8
from the TUS58

GETEND

RETURN

that

was

1s an End packet,

CALL

R2 = initial checksum
send the packet to TUSS8
update number of bytes left to send

¢
:
:

not

return

a CUNTINUE,

to caller

Position the TUSS

TUSEEK

Description:

The

to send

;

; get a byte from TUSS8

#F,CONT

module

heading

Inputs:

R5 = address

See

Q(k5)

three word

standard

FORTRAN argument block

2(R5) = address of unit number byte
4(R5) = address of block number word

;
;
H

Outputs:

TUSEEK::

CALL
TST
BNE

INIT
RO
998

packet

send

:
s

initialize the TUSSH
if initiaslization failed,

return

error

caller

TUSS,

MOVR

#0.P0UOS,

PACKET+2

set

op=code

MOVE

@2(R5),

PACKET+4

set

unit

MOV

84(R5),

PACKET+10,

set

block

:
:
:

KO
R2
R?2

send

Send the Control

packet

number
number

the TUSS8.

BHuild Contrel

code

status

16=bit

§PACKET,
#12., R1
R2
SNDPKT

points to packet
= length of packet
= initial checksum
the

packet

Get an End packet from the TUS8 and return to caller,

MOV
MOV
CLR
CALL

99s:

CLR

CALL
RETURN

GETEND

indicate no

return

C-11

byte pre-read

caller

TUDIAG

Run

TUS8

Local

Djagnostic

RE WE

TUDIAG

+SBTTL

Description:
module

heading

Inputs:
none

Outputs:

16=bit

status

code

ME WE W

UG RE

WE WE

See

BNE

RO
99s

Control

packet,

MOVB

#0.DIAG,

initialize the TU58
if initialization failed,

INIT

TST

return

Build

CALL

set

error

code

caller

TUDIAG::

Send

the

Control

PACKET+2

packet

the

op=code

TuSS8,

CALL

SNDPKT
Fnd

address

=
=

length of packet
initial checksum

the

packet

status

code

caller.

packet

and

return

indicate

GETEND

get

return

+SBTTL

INIT

CLR

CALL
RETURN

99s:

Receive

CLR

#12.,
R2

#PACKET,

MOV

Initialize

the

no
End

packet

byte

pre=read

packet

caller

TUSS

INIT

:
¥

Description:

INIT i1s called by
to infitialize the

;
H

This

;

followed

;

The

should

H
:

TUS58

done

TUREAD,

TUWRIT,

TUS8

its

causing

sending

two

framing

INIT

with

TUSEEK,

power-up
error

packets

CONTINUE

and

TUDIAG

state,.
the

the

TUSS,

TUSH,

packet,

Inputs:

]

none

Outputs:

16=-bit

status

code

;’“

assume

retry

suUCCess

eight

times

before

fajilure

BREAK,

MOV

#1,

MOV

#8.,

PUTBYT
SOB

R2,

CLR

@#DLXCSR

TSTHE

@#DLRBUF

@#DLXCSR

208

#8.,

start

0s:

MOV

send

nulls

Send

CLR

stop

sending

INIT:

sending

remove

for

break

character

times

20s

C-12

any

the

pbreak

extraneous

input

byte

Send

two

INIT

packets.

See

PUTBYT

#F,INIT

PUTBRYT

#F,INIT

TUS58

;

get

two

GETBYT

CMPB

R2,

BEQ

99§

“

return

SOB

Ri,

10s

else

#F,CONT

Return error

INIT

packets

status

byte

from

TUSS

CONTINUE pacret,
to

caller

retry

to caller,

RETURN

SNDPKT

Send a Packet to TUSSB

SNDPKT

Description

SNDPKT is called by TUREAD, TUWRIT, TUSEEK, and TUDIAG to
send a multi~byte packet (either Control or Data) to the TUSS,

WME

SNDPKT will also compute the packets checksum and send the

WME

+SBTTL
we

send

sent a Continue packet

Retry failed.

99s:

checksum

the

TUSS.

Inputs:
RO
R1

address

number

R2 = the

of
of

to
to

send
send

initial checksum

already

been

(non=zero

part of

the packet has

sent)

Jutputs:
None

bytes
bytes

SNDPKT:

k-4
#

CLR

-(SP)

;

Send bytes to TU58,

Update

make

odd/even

byte

flip=flop

16=bit checksum after each byte pair,

1 0s:

COMm
BEQ
CLK
MOVB

(SP)
20s

308

WORD
(RO),

208

MOVE
ADD
ADC

wWORD,
R2

30s:

PUTBYT
sS0B

408:

(RO),

;
:
;
:

WORD

WORD+1

;

(RO)+
R1, 10s

;
:

send
loop

TST

(SP)+

1if

BEQ

408
;7

Update

;

send

return

WORD,
R2

PUTBYT
SwAB

R2
R2

PUTBYT
RETURN

.SBTTL

GETEND

pair

store second byte of palir

update checksum
with end=around

ADD

set up byte pair word
with first byte of vair

s
:

ADC

flip odd/even flag
branch if second byte

carry

the data byte
until byte count

odd

number

computed

16=bit

data

zero

bytes,

checksum

caller

Check for End Packet

GETEND

Description:

GETEND

;

an End Control packet

called

TUREAD,

TUWRIT,

from the TUS58,

C-13

TUSEFK,

and

TUDIAG

GETEND verifies that

the

received

word

packet

indeed

the

packet

equals

the

byte

already

read

16=bit

End

packet,

computed

;

and

that

the

checksum

End

Control

checksum.,

Inputs:

the

caller

;

Outputs:

status

zero

code

GETEND:
&

flag

byte

was

not

pre=read

caller,

read

now,

TSTE

BNE

108

GETBYT

Verify

that

the

packet

comina

from

read

the

not

TUS8

wme

10s:

CMPR

RO,

BNE
GETBYT

90s
RO

CMPB

RO,

BNE

90s

GETBYT

with

length

#0,END

;

and

op=code

= End

success

code

Control

GETBYT

BIC

#°C<377>,

MOV

RO,

SwAB

#10.*%256 ,+0,END+F ,CTRL,

ignore
#4,

wORD

rest

get

clear

;

form

16=~bit

checksum

form

1é6=bit

checksum

from

bytes

End

packet,

hi=byte

updating

WORD+1

ADD

WORD,

ADC

SOR

R2,

checksum

received

checksum.

20s

;

transmitted

GETBYT

WORD

GETBYT

WORD+1

CMP

wWORD,
1008

code

already

GETBYT

Return error

10,

;

MOV

BEQ

packet

;

GETBYT

Receive

from

TUS8

loop
and

four

times

compare

with

computed

get

bytes
checksum,

R1i

for

transmission

error.

;

90s:
1008:

MOVE

#=-127.,

MOVE

RO,

RETURN

packet,

20s:

#10.,

908

and

indeed

¢heck

BNE

Receive

;

RO,

ADC

#F,CTRL

CmMPR

ADD

pre=read,

RO
;

return

status

return

«END

C-14

caller

16=bit

value

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 tools are a number
1 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.

MA-2361

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
BELT

| SUPPLY

TAKE-UP

HUB

TAPE GUIDE _}\

(j J éiigz

ROLLER

Figure D-2

MA-2382

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

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

12.

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.

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.

D-2

MA-Z358

Figure D-3

13.
D.3

Head Gate and Spring

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

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.

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

.
Figure D-4

MA-2358

Stretch the Belt with the Floating Roller

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.

Using the top to hold the floating roller, belt and supply hub down, use a straightened paper
clip or pencil to guide the elastomer belt around the hub. The hub should seat against the
base with the belt around it.

D.3.2

Threading the Cartridge

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 Para-

graph D.3.1.

TAKE-UP
HUB

: y%ifi??i_y

HUB

8A-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.

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

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

feeding straight into the hub.

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

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

Now hold the takeup hub, drive roller, and floating rollers fixed and rotate the supply hub to

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

;
0
. o

Digital Equipment Corporation « Maynard, MA 01754