TU58_Engineering_Specification_Jun78 TU58 Engineering Specification Jun78
TU58_Engineering_Specification_Jun78 TU58_Engineering_Specification_Jun78
User Manual: TU58_Engineering_Specification_Jun78
Open the PDF directly: View PDF 
.
Page Count: 36
| Download | |
| Open PDF In Browser | View PDF |
DIGITAL EQUIPnt'f..ENT CORPORATION
MAYNARD, MASSACHUSETTS
ENGiNEERING SPEClflCAT10N
TITLE
DATE 27 June 1978
TUSS ENGINEERING SPECIFICATION
REVISIONS
DESCRIPTION
REV
U
CHG NO
ORtG
DATE
APPD BY
?U;.rrt=
DATE ,
rL, ... Cloj)I~
I
EN-1079A-1G-R873_(392)
ORA l07A
SHEET
OF
~
ENGINEERING SPECIFICATION
TITLE
CONTINUATION SHEET
TUS8 ENGINEERING SPECIFICATION
TABLE OF CONTENTS
1.0
PAGE
4
GENERAL DESCRIPTION
1.1
4
OPERATION
1.1.1
FEATURES
4
1.1.2
INTERFACE OPERATION
4
1.1.2.1
PARALLEL INTERFACE
4
1.1.2.2
SERIAL INTERFACE
5
POWER
5
CONFIGURATION
5
1.1. 3
1.2
1.2.1
MECHANICAL CONFIGURATION
7
1.2.2
OPTIONS AND INDICATORS
7
1. 2.3
SUBSYSTEH DESIGNATION PLAl.'1
7
1.3
8
INTERCHANGE COt-1PATIBILITY
1. 3 . 1
MEDIUM
8
1.3.2
RECORDING SCHEME
8
1.3.3
LOGICAL FORHAT
10
1.3.3.1
BOT, EOT, AND INTER RECORD MARKS
12
1.3.3.2
HEADER DESCRIPTION
12
1.3.4
DATA FIELD DESCRIPTION
13
1.3.5
RECORD USAGE
14
1.4
14
SYSTEM PERFORMANCE
1. 4.1
NEAR
14
1.4.2
SYSTEH RELIABILITY
14
1.4.3
DRIVE PERFORHANCE
15
1. 4.4
ENVIROm.lENTAL CHARACTERISTICS
15
t SAIZE \CSO;;E 1 I I I NUMBER
S~ -0 -(;
t-'
DEC FORM NO
ORA lOB
EN.OI02Z.16.N370.{381J
SHEET ~ OF
1 REV
IA
3~L
ENGINEERING SPECIFICATION
TITLE
CONTINUATION SHEET
TU58 ENGINEERING SPECIFICATION
PAGE
1.4.5
1. 5
ELECTRICAL
DIMENSIONS
17
21
1.5.1
CONTROLLER BOARD
21
1.5.2
DRIVE MODULE
21
1. 5. 3
CAGE
21
1.5.4
RACKMOUNT UNIT
21
2.0
SOFTWARE INTERFACE
24
2.1
GENERAL DESCRIPTION
24
2.2
RADIAL SERIAL l?~OTOCOL (RSP)
24
2.2.1
MESSAGE PACKETS
24
2.2.2
FLAG BYTE OP CODES
24
2.2.3
SIGNAL
25
2.3
CO~~D
SET
26
2.3.1
COMr-1&"'l'D PACKETS
26
2.3.2
DATA PACKETS
28
2.3.3
END PACKETS
28
2.3.4
THE INSTRUCTION SET
31
NUMBER
ills-g -0
DEC FORM NO EN.OI022.1S-N37o-(3811
ORA lOa
.:.a
I Ft
REV.
ENGINEERING SPECIFICATION
CONTINUATION SHEET
TUS8 ENGINEERING SPECIFICATION
TITLE
1.0
GENERAL DESCRIPTION
The TUS8 is a low cost mass memory device using the 3M DC-100A
cartridge. The cartridge is prefcr.matted to store 2048 records
each containing 128 bytes. The controller provides random
access to any record. The average search time to any record is
ten (10) seconds. All data transfers between the TUS8 and the
host are in S12-byte blocks. The TUS8 manipulates four 128byte records to accomplish this. The control and read/write
electronics will support two drives, but only one drive can
operate at a time. Two controller modules are available. One
has a parallel interface for use inside a terminal. The other
is designed for use with an asynchronous serial interface.
Baud rates for the serial interface are j~~per selectable from
150 baud up to 38.4K baud.
The TUS8 consists of one or two cartridge drives and a module
containing read/write circuits, motor speed, control, and a
firmware programmed control module. Power may be provided by
an external power s'.lpply or from an existing power supply in
devices with which it is integrated.
I
The TUS8 may be maintained in the field by sub unit swaps.
sub units are: TUS8-XA Drive and Cable
TUSS-XB Serial Controller Module
TUS8-XC Parallel Controller Module
1.1 OPERATION
1.1.1 FEATURES
The
The TUSS uses cartridges that have been factory prefo~atted
to have 2048 headers to identify each record number. The
TUS8 searches at 60 IPS to find the file requested then
reads the file at 30 IPS. Data read from the taoe are
verified via check sums at the end of each record or
header. Data are recorded on t<;vo tracks and both tracks
are recorded in the forward direction.
1.1.2
INTERFACE OPERATION
1.1.2.1' PARALLEL INTERFACE
The Parallel Interface is used in terminals where
the interconnect distance is one foot or less. It
permits the TUS8 to be wired directly to the terminal
processor bus. The terminal processor controls data
transfers between itself and the TUSS via the series
of commands defined for the serial radial bus
protocol. Each byte is processed by interrupt
service routines.
SIZE
A
DCC FORM NO
EN-oloz2-1a-N37Q.(381)
JCODEI
,sf?
NUMBER
\\.LS"8" -0 ...{)
SHEET
OF
I RTic"~V
-
~~-
ENGINEERING SPECJFICATION
TITLE
CONTINUATION SHEET
TUS8 ENGINEERING SPECIFICATION
1..1.2.2
SERIAL INTERFACE
The Serial Interface is an RX-232, RS-422 and RS-423
compatible asynchronous full duplex serial line
which permits operation of the TU58 through DL-ll,
DLV-ll or M8650 interface modules. Control commands
are distinguished from binary data via the serial
radial bus protocol. Transmit and receive baud
rates may be different. The appropriate interface
standard and baud rates are selected by jumpers on
the module. Table 1.1 shows the baud rates
obtainable. ana the resulting average data transfer
rate.
TABLE 1.1
AVERAGE DATA T~~~SFER
BAUD RATES AVAILABLE
_____~~~~~~----~_RA~'T~E~~(B~YTES/SZC.)
38.4K BAUD
1280
19.2K BAUD
750
9600 BAUD
520
4800 BAUD
330
2400 BAUD
190
1200 BAUD
100
600 BAUD
50
300 BAUD
25
150 BAUD
12.5
1. 1. 3
pm'lER
The TUSS requires the following power inputs:
+SV =5% @ .7SA
+12V -5% @1.2A peak (60ms)
+10% .6A average running
.1A idle
1.2
CONFIGURATION
See Figure 1 for configuration with the parallel interface
and Figure 2 for configuration with the serial interface.
Component Designations
TUS8-XA
TUS8-XB
TUSS-XC
DL-ll-D
DLV-II-J
M8650
DLV-ll
Drive and Cable
Serial Controller Module 5413489
Parallel Controller Module 5413491
Serial Interface Module
Serial Interface ~1odule
Serial Interface Module
Serial Interface ~lodule
lA
SIZE
DEC FORM NO
O"A lea
EN-01022-16-N37o-(381l
l
I CODE
f csP .
NUMBER
\fAS6'-C ,0
SHEET ~ OF ~.€i..
_
....
~
rf2- -IJiG
-rf-I1?5
w
:r:
(/)
z
o
~
::>
z
~
z
o
o
Parallel
Controller
Nodule
1 or 2
DRIVE
UNITS'
,
lor 2
./
DRIVE UNITY
Optional
Power
Supply
I
V
./
/ /
..----.(I
I
>-
IJJet
ex t----
..
c:::J J
0::
,I
""'
\
w,
01'1
'{f)DI
u..
0
~I
:1: 'x 't::>
z t.r) w
f
Serial
Controller
Module
w
:r:
ill
I--
w
on...
8~
CI
~-
I'Ii'.
E!l
\.J..t
~
w
W
IInterface
__
__________________________________________________________________________________________________
__
~
Z
L-~J-
TUS8 Configuration with Serial
...J
~
~
0:(1)
~~
U.
VELOCITY IS O.7S~ .oz.
~OPTlCALAXtS
2.
\.
.,C'l
'/
~
FC:=!CE RZCUIR2i
4 OZ. AT PERI?H2RY
3. TAPE TENSION IS 0.5 OZ. H'
TO 2.0 OZ M A~.
'i.'<~
["'.
4. DIMENSIONS ARE IN INCHES
S.TOLEl1:lloo}.lC'S.=.ooS
I ""es".,. AS '"°T"O
I- t
: I f""""':"r"""""~I:
t.......L.: rl=tl~;z~~~~===l----1-1
r-~-==-i""'-=~J~:""I
====---..,
-l~ t
.'2J~
{J
TA?!.-~-:;
~'llCATS·~ CA;:z,T~i7G<=' STOP,s
L? HOLE
EW HOLE
EOT HOLES
'-:-OC.Ai";::'g,S
"SCOTCH" IS A REGIS7EAEO TAAOEMAR!< Or- 3:.1 COI.V.<)
-".-~.'
FIGURE 3
.. "
ENGINEERING SPECIFICATION
CONTINUATION SHEET
TUS8 ENGINEERING SPECIFICATION
TITLE
record
head
current
I
I
+v 1
0
0
0
ov I
-v
recovery
Figure 4
Data are recovered using an integrater as shown in
Figure 4. The integrater is dumped on the positive edge
of the data waveform. The data waveform is then
integrated. The integrater output is sampled on the
next positive edge. If the integrater output is
positive at sample time, the recorded bit was a one.
If the integrater was negative at sample time, the
bit was a zero. The time between bits is 1/(800 bits
per inch} (30 ips) = 41.7 )ls.
1.3.3
LOGICAL FORMAT
Data are recorded on two tracks. Each track contains
1024 records of 128 bytes. To accommodate the orientation
of the record and erase head gaps, both tracks are
recorded in the same direction. The positioning of the
tracks is shown in Figure 5. To accommodate standard
mass storage blocks of 512 bytes, the controller groups
four 128 byte records: together. All addressing
from the host is done by block n~ers~ .
,,~,...
,...,.. """
..... ""
NUM8ER
!l.,,~ c.~ -L'" -c:)
-
_..
_--
''''''"'
au
011
;0
-4
»>0
=i
r-
~~
°0 i
co
JTI
;0
'"
z
0
t-3
;
c:
Record
1024
r~
2
b
~(
c""'
'"
,...
.~
~,
~OT
..,
~,
I
iw ,
BOT
1536
Record
1025
fRecord 2048
'I
H
DATA
M
H
DATA
M
H
DATA
M 'H
DATA
II
DA'l'A
M If
DATA
M Ii
DATA
M
DATA..t '-M
Record
0>
!:
Record
0
Reo:Jrd
512
Record
1
II
M H
II
Ul
00
Record 1535
DATA
M
H
DATA
DATA
M Ii
DATA
EOT
EOT
tJj'
~
Record 51311 Record 511 Record 1023
FIGURE 6A
~
~
TAPE FORMAT
'd
tJj
()
H
oj
II == Header
H
()
No mark for records 0, 1024
m
m
-Z
;;0
U\
H
Mark
-Z
tJj
ttl
(J';
= Interrecord
G'>
G'>
Gl
M
Z
H
Gl
~
'L
m
~
t-3
H
."
m
()
-
--n
»
-0-t
()
Z
0
Z
-;;
1> N
MARK
1010 •. 10
16 BI'l'S
f11
-
C-" g
HEADER
SYNC
000 .•• 01
16 BITS
RECORD
NUMBER
16 BITS
"1J 0
(J';
-"
,-n
M
-i
~
~'I1"',
DATA SYNC
(Xl.1PLEMENI' 000 •••• 01
16 BI'l'S
32 BITS
2400 FRPI
i"
CHED<
DATA
,\
1024 BITS 1\
1/
SUM
16
BITS
00
ZEROS
136 BITS
(written by
formatter)
~~~~~~~~~J~~~
-::t
:'-z
'~
C
;\ ::
(~ ~
,
.--v---.~------~-------------~----~
800 BPI
200 BPI
o
o
z
::j
z
c
~
o
z
\ :0
FIGURE
, C~
0
-"l
I'
RECORD
NUMBER
6B
RECORD AND HEADER FORMAT
Ul
I
fT1
:
;.0
111
<..:
JTI
-f
· ENGINEERING SPECIFICATION
TITLE
CONTINUATION SHEET
TUSS ENGINEERING SPECIFICATION
Figure 5
1.3.3.1
BOT, EOT,
&~D
INTER RECORD
~~RKS
Special marks are recorded during tape formatting
to indicate beginning and end of tape as well as
beginning of record. These marks are "recorded at
one fourth the bit density of data (600 FRPI).
The lower frequency is detected by the controller.
The encoding method used is not sensitive to tape
speed, so that ones and zeros 'may be recovered at
the lower frequency with no change in hardware.
The BOT, EOT, and IRM (Inter Record Marks) are
distinguished from one another as follows:
A.
Bw
c.
1.3.3.2
BOT is recorded as all zeros.
EOT is recorded as all ones.
IRM's are recorded as alternate ones and zeros.
HEADER DESCRIPTION
The header and data fields are shown in Fiaure 6.
The header contains the following components:
A.
Inter Record Marks - Sixteen bits recorded at
200 BPI and havina a data oattern of
1010101010101010. - During search, the controller
finds records by starting from a known position
and counting the inter record marks as they go
by at 60 IPS. When it reaches the record before
the record being searched for, it slows the taoe
down to 30 IPS and reads the next header. Ifthe header number read agrees with the header
NUMBER
TLLS""? -0 - ()
DEC FORM NO
ORA '08
EN.01022·1C-N37o-(3811
SHEET
.Ja:....
OF
36
ENGINEERING SPECIFICATION
TitLE
CONtiNUATION SHEET
TUSS ENGINEERING SPECIFICATION
number expected, the controller continues with
the read or write operation. Otherwise, it
corrects the current position and initiates a
new search.
. 1.3.4
B.
Pre-Amble (All of the following bits are
recorded at 800 BPI.) It consists of 15 zeros
followed by a one. The controller looks for
the one and then begins to accept the record
number.
C.
Record Number
D.
Record N~~ber Complement - The controller
tests this number to insure that the header
was read with no errors.
E.
Trailer - 31 zeros and a one. During a
write operation, the controller reads the
fi~st four zeros then switches to write mode
and writes the remaining zeros and one. The
glitches caused by switching on the write
current are then confined to a narrow space
which the controller blanks out during read
operations. After a fixed duration blank
(controller ignores tape output) the controller
begins to search for the one at the end of the
trailer. When it finds the one it begins
reading the data field .
-
16 bits (0 to 2041)
DATA FIELD DESCRIPTION
The data field is shown in Figure 6 and consists of the
following components:
A.
Data field - the next 1024 bits of data are stored
in the data buffer in the controller.
B.
-
Checksum - The checksUID.. .. contains 16 bits and is
used to find errors in the read data. During read,
each pair of bytes is summed in a 16 bit add. The
remainder is added to the checksum and the result
should be zero. If the result is not zero, the
record is re-read up to eight tries. If the correct
data cannot be read after eight tries, a hard error
is indicated to the host processor.
NUMBER
T1l5~-C-()
DEC FOR M NO €N-01022-16-N37o-(3811
ORA 108
I rr
R~V
SHEET~ OF ~
· ENGINEERING SPECIFICATION
TITLE
CONTINUATION SHEET
TUS8 ENGINEERING SPECIFICATION
1.3.5
C.
Trailer - This field is two zeros and is used to
prevent noise from influencing the last bit of
data.
o.
Post record zeros - tihen the tape is formatted, an
additional 136 zeros are written to allow for 10%
tolerance in motor speed. These zeros are never
rewritten or read in normal operation. Their purpose
is only to provide flux reversals where gaps might
be left from normal system operations.
RECORD USAGE
The TUs8 controller will treat all records as data
records. Any records may be used for directories,
error logs, etc., but these functions must be accomplished via user software.
1. 4
SYSTEM PERFOru1AL'lCE
1. 4 • 1
~'lEAR
The TUS8 read and write operations are performed by a
contact process resulting in wear at the head/tape
interface. The DC-100A cartridge maintains contact
between the tape and record/play back head whenever
the cartridge is inserted in the drive. This results
in wear during search and rewind operations as well as
read/write operations. The wear is, thus, a function of
total tape motion and not just read/write tape motion.
1. 4.2
SYSTEM RELIABILITY
Minimum number of tape
Search error rate**
Soft data error rate**
Hard data error rate
MTBF System*
l·lTTR System
passes l::eginning··~to . end to beginning
1 in 10 4 searches
1 in 10 7 bits read or written
1 in 10 9 bits read or written
1000 hours at 100% auty cycle
Less than .5 hour, module swap
* With expected 10% usage, MTBF will be 10,000 hours.
**
These errors will be recovered by the TUS8 controller.
I REV
1 ,~
NUMBER
-rU_~--C-l"
DEC FORM NO
ORA 108
EN-01022·16-N37Q-(3811
SHEET
.J...:±..
OF
ENGINEERING SPECIFICATION
TITLE
TOS8
ENGI~IEERING
1. 4.3
CONTINUATION SHEET
SPECIFICATION
**Continued
Search errors and soft data errors are usually attributed
to effects such as electrical noise, dust, or wear in
the medium.
If the error can be recovered in eight tries,
it is a soft error.
The errors that cannot be recovered
after eight tries are hard errors. The host will be
notified that retries occurred.
DRIVE PERFORHANCE
Capacit::t
per cartridge
262,144 bytes
per track
131,072 bytes
per record
(2048 records X l28bytes
128 bytes
Data Transfer Rate
read/wr i te
(...1
tape
41.7 psec/data bit
data buffer to interface 150 to 38.4K baud,
parallel interface
average access
....
,-~rne
),lS
9.3 sec.
28
sec.
read/write tape speed
30
ips
search tape speed
60
ips
800
bpi
2400
frpi
flux reversal density
selected
per data byte, min.
maximum access time
bit density
1.4.4
30
j~
ENVIRONMENTAL CHARACTERISTICS
The TUS8 will meet DEC STD 102 for class A devices.
When the TUSS is integrated in a host device such as
a terminal, the maximum temperature rise abovearnbient
inside the device must be restricted to 18°C.
(Performance limits under Class B to be defined.)
NUMBER
ILl, S~ ~ .-(.'
DEC FORM NO
ORA 108
EN-OI022-16-NJ1Q-P81)
SHEET
\5
OF
I ~~v t
~6
· ENGINEERING SPECIFICATION
TITLE
CONTINUATION SHEET
TUS8 ENGINEERING SPECIFICATION
Temperature
TUS8 operating
TUS8 non-operating
lSoC (S90F) to 32°C (90°F) ambient
-30°F to 140°F (-34°C to 60°C)
Medium operating
aOe (320F) to sooe (122°F)
Max temperature gradient between system ambient and
TUSS ambient
laoe (32.4 o F)
Relative Humidity
TUS8 operating
Maximum wet bulb
Minimum dew point
2soe (77°F)
2 0 e (36°F)
RH}
RH
Relative humidity
TUSS non-operating
20% to 80%
S% to 98%
Medium non-operating
10% to 80% RH
non-condensing
Magnetic field
NOTE:
It is recommended that if the recipient of a data
cartridge knows or suspects that the cartridge has
been exposed to either the maximum or minimum
temperature extreme, the tape should be rewound one
complete cycle before using.
EMI
IA
SIZE ICODE
DEC FORM NO
DRA 108
EN-01022.16-N37Q-(381)
sP
I
NUMBER
TU. C;k
-r .-()
SHEET ~ OF
3b
CONTINUATION SHEET
ENGINEERING SPECIFICATION
TITLE
TUS8 ENGINEERING SPECIFICATION
1.4.5
ELECTRICAL
Power Requirements
Module and Drive
5V :!: 5% ra .7SA
12V - 5%, + 10% ~ 1.2 A peak (60ms)
.6 A average running
.1 A idle
Rack Mount
110,220 VAC
50, 60 Hz
50 watts max.
Interface Levels
Parallel Interface - TTL levels
Serial Interface - In accordance with RS-422, or RS-423,
jumper selectable. Compatible with
RS-232-C when set for RS-423.
The serial interface operates on half-duplex, asynchronous
four-wire lines at rates from ISO baud to 38.4 kilobaud.
The transmit and receive rates may be independently set.
Each 8-bit byte is transmitted with one start bit, one
stop bit and no parity. The line driver and receiver may
be set to operate in accordance with EIA RS-422 balanced
or RS-423 unbalanced signal standards. ~qhen set to
RS-423, the TUS8 is compatible with devices complying
with RS-232-C.
The TUS8 is shipped prewired for operation at 38.4 kbaud
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 meters
(90 feet). The wire used with any installation should be
no less than 23 A~qG 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 meters (4000 feet) at any
TU58 data rate. The following chart, figure 4-10, 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.
IA
SIZE
OEC FORM NO
ORA10lJ
EN-olon'16-N3700(381)
Ic:.;:OE
'--'p
I
NUMBER
-'-US.-$' -("'-C'
SHEET
.J..1....
OF
3?.
~
- --
. .. ,
.
..
~1:-1-f-
~""..,
:~···l)(
M ,.
t:f
~ ,,'>")
('0
1'\ 4'1>f,..
~~~.
'M:.<-,,~
:
I
+-n"'"-'~
I
300
,to
I
11<.
~I<.
DAiA RATE. ,..... BA-!A D5
~S-4).~
ENGINEERING SPECIFICATION
TITLE
CONTINUATION SHEET
TUSS ENGINEERING SPECIFICATION
TUSS MODULE CONNECTIONS
WV'll
WW2
WW3
WW4
WWS
WW6
W'll7
WW8
WW9
liffllO
WWll
WW12
~~13
~~14
WWlS
WW16
150
Baud
300
Baud
600
Baud
1200 Baud
2400 Baud
4800 Baud
9600 Baud
19200 Baud
38400 Baud
UART Receive Clock
UART Transmit Clock
Auxiliary A (To interface connector pin L)
Auxiliary B (To interface connector pin A)
Factory Test Point
Groundl.
Boot J Connect together for auto-boot on power-up.
WW17
RS-423 Driver
RS-423 Common (Ground)
WW19 Transmit Line +
WW20 Transmit Line WW21 RS-422 Driver +
WW22 RS-422 Driver WW23~Receiver Series Resistor
WW2~ (Jump for RS-422)
Serial Interface Connector
J2-A Auxiliary B
H Transmit Line B Ground
J Transmit Line +
C Receive Line +
K Ground
L Auxiliary A
D Receive Line F Ground
m~18
Power
Jl-l
3
5
6
.
.
Input Connector
+12 volts
Ground
+5 volts
Ground
Drive Cable
J3,4-1 Cart L
2 n/c
3 Permit L
4 Signal Ground
5 Motor +
6 Motor 7 +12 volts
8 Tach
9
10
11
12
13
14
15
16
LED
H Ground
Erase Return
Erase 1
Erase f1
Head Return
Head f1
Head 1
NUMBER
Tu...S6 -C..(')
DEC FORM NO
DRA108
EN·OI022·16-N37C-{3S1)
SHEET ~ OF
RE.V
I.h
:36
DIA 6WOSTI(.
1-&:0
~
BOOT
GoNe 1-
~~
A B
C 1>
F
H
'W'../
+"
,
\50+~
'300 +
~
-i
W
6004-
+
IlOO
'1 'tOO ;.
~
'liDO 41'l.1f~+
(")
W
-i
UJ
1<1.11\ +
C"')
I
f'
C\I
'600~
!
N
,",:)KL
T? +'1'{
C"')
RC.V 4-CLk
XHCT+C.L~
N
W
AUXA+
~UX B+~)"'"
V'-'
\;J\..J
J.lf
17
lO
++-4-+++++
IT]
~
N
U
ltl
(\J
C'?
U
mm
--
-i
W
N
~~~
U
-_.. _-.
X\II.L..,./I (~(.c.. Sf-/~c.lr~
?; . . LCc.o...l;~..s _
ENGINEERING SPECIFICATION
TITLE
TUSS
ENGI~EERING
1.5
DIMENSIONS
1.5.1
CONTINUATION SHEET
SPECIFICATION
Controller Board
5.1S7 X 10.44 in.
X 26.5
13.2
1.5.2
Drive Module
3.2H
X
8.1
1. 5. 3
Cage
4. 2H
X
10.7
1.5.4
Rackmount Unit
em.
3.30
8.3
7 . 20
X
18.5
X
4. Hl in.
10.6
em.
11. 4W (including rrounting tabs) in .
29.1 cm.
5.2H
X 13.60
X 19.0N in.
(mounts on lS.3" centers)
13.3cm X 34.9
IA
X 4S.7cm.
SIZE ICOOEI
DEC FORM NO
ORA 108
e:N-01022-16-N37Q-(381)
sf I
SHEET ~J
OF
3b
---- --, -- --1
I
"t "7
(1.8)
,...--:-----J -
---~
10.'1'
t-----(4-. i 2.)
I
..J
L_
I
S ./~
C:.. '- '2.)
.
I
S" ./l
(?,C 2.)
j
_1
I.eo
( .7/)
~
I.,,,
G .... Q
(3.~S)
!
t
:1.8<-/
( / 12:)
,.L.·t_ _ _ _ __
t) • 00 <:. "'"
~SJ
f-{/.38
01 .......
(0. 00 ) ,'"
• "!.o
( .1'1)
~
1'1.,... --------4-____
f ""\"
""'i";-.------(5".30 )
I
00.00 c. ....
(00.00) ;""
+fEAT 5HJK:
3.00. '2.) AGaVE
0.5'(0.2) BELDw
0.,0,..,
(.14).-1
AMP I1EADER. .,.
MAlE: AM?
g70'3-~
~ 8,IS"1-6
~
/0.03
(3."1Sj
ALL HaLES
A
/
):!.o~
/11
\
(.;$;
.
AMP ~ g7'"l7:l.-i
DEC
PT,Nl-nso 6 - OJ
13./8
(F. 1'1 )
"ENGINEERING SPECIFICATION
CONTINUATION SHEET
TU58 ENGINEERING SPECIFICATION
TITLE
2. a
SOFT~'1ARE
2.1
INTERFACE
GENERAL DESCRIPTION
The TU58 is controlled by a high level command set that
unburdens the host from device-related operations such
as tape positioning, read retries, etc.
The commands are
~mplemented by the Radial Serial Protocol which arranges
commands and data in separate message packets.
These are
byte sequences suitable for transmission by asynchronous
serial or parallel interfaces.
2.2
RADIAL SERIAL PROTOCOL (RSP)
The full spec for radial serial protocol is included in
Appendix A.
This section provides an introduction to the
major features.
2.2.1
PACKETS
~~SSAGE
All communication between TU58 and host is broken up
into message packets.
Each packet begins with the flag
byte.
This byte is defined as follows:
BITS 7-5
BITS 4-0
=
=
RESERVED
OP CODE
The next byte in a message packet is the byte count.
This is the number of message characters in the packet,
excluding the flag, byte count, and checksum.
U9
to 128 bytes may be in each packet. Larger blocks
of data are sent with multiple packets.
The last two
bytes of the message packet are a 16 bit checks~~.
The
checksum is formed by summing successive byte pairs
taken as sixteen bit words and using an end around
carry from bit 15 to bit O. The flag and byte count
are included in the checksum.
2.2.2
FLAG BYTE OP CODES
00001
00010
00100
10000
10011
DATA
CONTROL (COM!1.fu'lD)
INIT
CONTINUE
XOFF
NUMBER
'-t\_-l_C;-? -(' -C~
DEC FORM NO
ORA 108
EN-OI022-16-N37Q-{3811
SHEET
~i
OF?{~
,
l
I
CONTINUATION SHEET
ENGINEERING SPECIFICATION
TITLE
TUS8 ENGINEERING SPECIFICATION
2.2.3
DATA:
This flag informs the receiver that data
rather than commands are arriving. The
receiver loads the incoming bytes into a
buffer area in memory.
It doesn't look
for an op code to execute.
COMMAND:
The CO~~ND flag informs the TUSS that a
command packet follows. This is particularly
important when the TUSS encounters an error
condition.
In this case it sends an end
packet before data transfer is complete. The
host knows that the end packet has been sent
because the packet received has a CO!~~~D
flag instead of a DATA flag.
INIT:
This op code is sent from the host to the
TUSS to cause it to execute its power-up
sequence. It is sent from the peripheral
to the host to tell the host that the
initialize sequence has occurred. When the
TUS8 makes a protocol error or receives an
invalid command, it reinitializes and sends
INIT to the host. The TUSS must send up to
261 INITs in this case because the host may
think it is receiving a message packet andwill not interpret the INIT until the message
packet is complete.
CONTINUE:
After a message is sent from host to TUS8,
the host must wait until the TUS8 sends
CONTINUE before any more messages can be sent.
This permits the TUS8 to control the flow of
data. CONTINUE means that the tape is in
position and ready for data.
XOFF:
Ordinarily, the TUSS 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 sends XOFF.
The TUS8 stops transmitting immediately and
waits until the host sends continue to complete
the transfer when it is ready.
SIGNAL
Signal is defined in the RSP spec as a unique logic
entity that can be interpreted as signal regardless of
the state of the protocol.
Its implementation for the
TUSS is the BREAK condition on the serial line. Break
\
DEC FORM NO
ORA loa
EN-01022-16-NJ7o-{J811
SIZE IC~DE
A
.-,P
I
NUMBER
-nL~?"
-/";- (J
SHEET ~.~
OF
3~
"ENGINEERING SPECIFICATION
TITLE
TUS8
ENGI~EERING
CONTINUATION SHEET
SPECIFICATION
is interpreted when the serial line is kept in the
space condition for more than one character time.
This causes the UART to set its framing error bit.
The TUS8 will interpret the framing error as signal.
2.3
COMMAND SET
The co~~and set is designed to be compatible with the
device handlers for any random access mass storage devices.
Since the full scale handlers are used with large disk
systems, the TUS8 implements only a subset of the commands .
available to higher performance devices. The TUS8 commands I
meet the minimum requirements for a device handler; the
differences are in characteristic and status flexibility
in large sy.stems.
A data transfer operation uses three or more message
packets. The first packet is the command packet from
host to peripheral. Next, the data is transferred in
128 byte packets in either direction (a~ required by
read or write). After all data is transferred, the
peripheral sends an end packet.
If the peripheral
encounters a failure before all data has been transferred,
it sends the end packet as soon as the failure occurs.
2•3. 1
COr-ll1.AND PACKETS
The command packet format is shown in Figure 2.1
Bytes 0, I, 12, 13 are the message delivery bytes.
Their definition is as follows:
a
FLAG
This byte is set to 00000010
to indicate that the packet is
a co~~and packet.
1
MES~ ~ ~~
Number of bytes in the packet
excluding the four message
delivery bytes. This is deci~al
10 for all command packets.
CHECKSUM
The 16 bit checks~~ of bytes
o through 11. The checks~~ is
formed by treating each ?air of
bytes as a word and summing
words with end around carry.
12,13
NUMBER
·-r-U
<:....X -("\ -r:.;
1
. 1
DEC FO R M NO . EN-01022-16-N37I)-P81)
DRA108
SHEET ~ OF
I REV
1\
lit
-
ENGINEERING SPECIFICATION
TITLE
~C>1l1I~Da.D
~U~!.l,~
CONTINUATION SHEET
TUS8 ENGINEERING SPECIFICATION
Figure 2.1
COMMAND PACKET STRUCTURE
BYTE
0
1
FLAG = 0000 0010
MESSAGE BYTE COUNT = 0000 1010
2
3
10
11
OP CODE
MODIFIER
UNIT NUMBER
SWITCHES
SEQUENCE NUMBER - LOW
SEQUENCE NU~£ER - HIGH
BYTE COUNT - LOW
DATA
BYTE COUNT - HIGH
BLOCK NU~1BER - LOW
BLOCK NUMBER - HIGH
12
13
CHECKSUM - LOi-l
CHECKSUM - HIGH
4
5
6
7
8
9
Figure 2.2
INSTRUCTION SET
OP CODE
0
1
2
3
4
5
6
7
8
9
10
11
NOP
INIT
READ
WRITE
COMPARE
POSITION
ABORT
DIAGNOSE
GET STATUS
SET STATUS
GET CHARACTERISTICS
SET CHARACTERISTICS
.,
ISIZE
1CODE I
A sP
DEC FORM NO
DRA 108
E:N-ol022-16-N3700(381j
NUMBER
'1"1)..S:? -C' ~ C
!.
REV
\
(i
SHEET ~~ OF ~~
· ENGINEERING SPECIFICATION
TITLE
CONTINUATION SHEET
TUSS ENGINEERING SPECIFICATION
The remaining bytes are defined as follows:
OP CODE
Operation being
See Figure 2.2
3
MODIFIER
Permits variations of commands.
4
UNIT NUMBER
Selects drive 0 or 1.
5
SWITCHES
Not used by TUS8.
6,7
SEQUENCE NUMBER
Used with devices that can
handle more than one outstanding
operation.. Always zero for TUS&
8,9
BYTE COUNT
Number of bytes to be transferred
by a read or write co~mand.
Ignored by other commands.
BLOCK
The block n~~ber to be used
by commands requiring tape
positioning.
10,11
2.3.2
co~.anded.
2
NUHBER
DATA PACKETS
The data packet is shown in Figure 2.3. The flag
byte is set to 00000001. 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 ass~~ed
to have enough buffer capacity to accept the entire
transaction, whereas the TUS8 only has 128 bytes of
buffer space. For write co~~ands the host must wait
between message packets for the TUSS to send the
Continue flag (00010000) before sending the next
packet. Since the host has enough buffer space,
the TUS8 does not wait for a continue flag between
~essage packets when it sends back read data.
2.3.3
END PACKETS
The end packet is sent to the host by the TUSS after
completion or termination of an operation or on an
error. The end packet is shown in Figure 2.4. The
definition of bytes 0, 1, 12, 13 are the Sru~e as for
the command packet. The remaining bytes a~o defined
as follows:
BYTE 2
OP CODE - 0100 0000 for end packet.
I Rh;f-V I
1
DEC FORM NO
ORA 108
EN-O l022-16-NJ7D-{3S1)
SHEET ~>{
OF
ENGINEERING SPECIFICATION
TITLE
CONTINUATION SHEET
TUSS ENGINEERING SPECIFICATION
Figure 2.3
DATA PACKETS
BYTE
0
1
2
3
"
"
"
"
M+l
M+2
M+3
FLAG = 0000 0001
BYTE COUNT = M
FIRST DATA BYTE
DATA
n
n
n
"
LAST DATA BYTE
CHECKSUM L
CHECKSUM H
I
Figure 2.4
END PACKET
BYTE
o
1
2
3
4
5
6
7
8
9
10
11
-12
13
FLAG = 0000 0010
BYTE COUNT = 0000 1010
OF CODE = 0100 0000
SUCCESS CODE
UNIT
NOT USED
SEQUENCE NO. L
SEQUENCE NO. H
ACTUAL BYTE COUNT L
ACTUAL BYTE COUNT H
SDr-1l-1ARY STATUS L
SUMMARY STATUS H
CHECKSUM L
CHECKSUH H
I
NUMBER
lU.S6-O...Q
DEC FO RM NO e:N-01022-16-NJ7Q-(J811
ORA 108.
SHEET ~
OF
REV
II
r-r
.
3G
• ENGINEERING SPECIF1CATION
TITLE
CONTINUATION SHEET
TUSS ENGINEERING SPECIFICATION
BYTE 3
SUCCESS CODE
o = NOR~ SUCCESS
1 = SUCCESS BUT WITH RETRIES
-1 = READ ERROR
-8 = WRITE ERROR
-15 = SEEK ERROR
-16 = COMMAND ERROR
-32 = NO CARTRIDGE
-33 = NON-EXISTfu~T UNIT
-34 = WRITE LOCKED
-35 = ABORTED
-36 = PARTIAL OPERATION (End of
Medi~~)
BYTE 4
UNIT NUMBER 0 or 1 FOR DRIVE NUMBER
BYTE 5
NOT USED
BYTE 6,7
SEQUENCE Nm·1.BER PACKET
BYTE 8,9
ACTUAL BYTE COUNT - Nm1BER OF BYTES
Hk~DLED IN TRru~SACTION.
IN A GOOD
OPERATION, THIS 'i'lILL BE THE SA11E AS
THE DATA BYTE COUNT IN THE CO~~~D PAC~ET.
0 AS IN COMr·tz\ND
AL~vAYS
BYTE 10,11 SUMMARY STATUS
BYTE 10
Bit 0
.L,
7
BYTE 11
Bit 0
1
2
.,
RESERVED
3
5
6
7
LOGIC ERROR
MOTION ERROR
TRANSFER ERROR
SPECIAL CONDITON (Errors)
NUMBER
-nl~-0-()
DEC FORM NO
ORA 108
S:!'I-OI022-16-N37Q-(381)
SHEET
...:3.c..-
OF
ENGINEERING SPECIFICATION
TITLE
CONTINUATION SHEET
TUS8 ENGINEERING SPECIFICATION
2.3.4
THE INSTRUCTION SET
The instructions and their op codes are shown in
Figure 2.2 The following is a brief description and
usuage 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
o
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
OOOX
0000
0000
0000
0000
0000
0000
0000
101X
1010
FLAG
MESSAGE BYTE CNT
OP CODE
MODIFIER
UNIT Nuz,1BER (IGNORED)
SNITCHES (NOT USED)
S~Q NO.} NOT USED
S.c.Q NO.
BYTE COTJNT L }
NO DATA
BYTE COUNT H
INVOLVED
B~OCK- NO. L}
NO TAPE
B.LOCK NO. H
POSITION
CHECKSUH L
CHECKSUH H
The TU58 returns the following end packet:
o
1
2
3
4
5
6
7
8
9
10
11
12
13
0000
0000
0100
0000
0000
0000
0000
0000
0000
0000
0000
XXXX
OOOX
XXXX
0010
1010
0000
0000
OOOX
0000
0000
0000
0000
0000
0000
XXXX
XXXX
xxxx
FLAG
MESSAGE BYTE CNT
OP CODE
SUCCESS CODE
UNIT (IGNORED)
NOT USED
S~Q. L} NOT USED
S.c.Q.
H
ACTUAL BYTE CNT L} NO DATA
INVOLVED
ACTUAL BYTE CNT H
SUr1MARY STATUS L
SU~~qy STATUS H
CHECKSUM L
CHECKSUM H
I. A
SIZE ICODEI
DEC FORM NO
ORA 108
E:N-Q1022"16-,.j37o-(3Sl.)
S-P
I P.
NUMBER
R.EV
-rltS8 -('\ ~~
SHEET
3J
OF
3b
"ENGINEERING SPECIFICATION
TITLE
CONTINUATION SHEET
TUS8 ENGINEERING SPECIFICATION
OP CODE 1
INIT
This instruction causes the TUS8 controller to reset
itself to a known state. No tape positioning results
from this operation. The co~mand packet is the Sru~e
as for NOP except for the OP CODE and the resultant
change to the low order checksum byte. The TUSS
sends the same end packet as for NOP after reinitializing itself. There are no modifiers to Init.
OP CODE 2
READ
This instruction causes the TUS8 to position the
tape in the drive selected by UNIT NO. to the b~ock
designated by the block, number bytes.
It reads
data starting at the first- block and continues
reading until the byte count (command bytes 8 and 9)
is satisfied. After data has been sent the TUSS
sends an end packet. Byte 3 will indicate success,
success with retries, or failure vf the operation.
In the event of failure, the end packet will be
sent at the time of failure without filling up the
data count. The end packet will be recognized by
the host by the flag byte. The host will see a
command flag (0000 0010) instead of a data flag
(0000 0001).
There- is one modifier to the read command.
A modifier of 0000 0001 will cause the TUSS to
read the tape with an increased threshold in the
data recovery circuit. This will make the tape
drop bits 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
TUS8 and host is shown on the next page.
.
DEC FORM NO
DRA 108
EN-O lO22-16-N37Q-(381)
ISAEI C~~EI
NUMBER
Tl~~-("\~
SHEET
--,
~
OF
REV
(\
I,
-,/
,
~o
I1
ENGINEERING SPECIFICATION
TITLE
~\'!\:3n~~n
~J.i~1 ~
CONTINUATION SHEET
TU58 ENGINEERING SPECIFICATION
HOST
TU58
COMHAND
PACKET
(READ 510 BYTES)
~
..
-~
I
~
,
..
,
....
CIiI
I
I
I
[
DATA
128 BYTES
DATA
128 BYTES
DATA
128 BYTES
DATA
126 BYTES
END
ISA E 1~~EI
DEC FORM NO
ORA 108
EN-OI022-16-N37o-(381)
I
I
I
-
I
NUMBER
\"" uS'? -c-o
I REV
In
SHEET ~ OF ~
"ENGINEERING SPECJFICATION
TITLE
CONTINUATION SHEET
TU58 ENGINEERING SPECIFICATION
OP CODE 3
WRITE
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 will automatically zero-fill any
remaining bytes in a 512 byte tape block.
There is one modifier permitted with the write
command. A modifier of 0000 0001 will cause the
TU58 to write all of the data and then back up and
.read the data just written and test the checks~~
of each record.
If all of the checksums are
correct, t~e TU58 will send an end packet with the
success code set to zero (or 1 if retries were
necessary to read the data). Failure to read
correct data will result in a success code of
-6 (1111 1010) to indicate a hard read error.
The write operation has to cope with the fact that
the TU58 only has 128 bytes of buffer space.
It
is necessary for the host to send a data packet and
wait for the TU58 to write it before sending the
next data packet. This is accomplished using the
continue flag.
The continue flag is a single byte
response of 0001 0000 from TU58 to host. The write
operation is shown for both write and write/verify
operations. (Figure
OP CODE 4
COMPARE
Treated as a NOP.
OP CODE 5
POSITION
This command causes the TU58 to position tape on
the selected drive to the block designated by
bytes la, 11. After reaching the selected block,
it sends an end packet. No modifiers are used.
OP CODE 6
ABORT
This command is treated as a NOP.
Its use is
intended for devices with multiple outstanding
operations. The TU58 returns an end packet.
I SIZE
I
DEC FORM NO
ORA 108
E:N.01022·16-NJ70·(J81l
A
!CODE
sP
I
NUMBER
--r\.A..S" g -0
SHEET
-0
OF
~u~DD~D
ENGINEERING SPECIFICATION
TITLE
CONTINUATION SHEET
TUS8 ENGINEERING SPECIFICATION
TUSS
HOST
COHHAND
PACKET
WRITE
510
BYTES
.......
..a
I
DATA
128 BYTES
I
.....
I
I
I
DATA
128 BYTES
DATA
128 BYTES
DATA
126 BYTES
I
r
r
--
I
CONTINUE
I
:.>
TAPE POSITIONS
A..1\lD ~'1RITES DATA
I
CONTINUE
I
SPTAPE POSITIONS
AND ~vRITES DATA
I
CONTINUE
I
E>
TAPE POSITIONS
MID WRITES DATA
I
CONTINUE
I
~
TAPE POSITIONS
AND WRITES DATA
IF ~vRITE/VERIFY, TAPE
REtHNDS, AND READS BLOCX JUST
WRITTEN AND TESTS CHECKSUMS
END
SUCCESS/FAILURE
ISIZE
ICODE I
A SP
DEC FORM NO
ORh,10a
EN-01022.16-N37Q-PRll
NUMBER
TvLS'S" -r-;. .-d
SHEET
~?,S:
OF
I
REV
(\
i':
~
~'-------------------------------------------------------------,
CONTINUATION SHEET
,;'ENGINEERING
SPECIFICATION
TITLE
TU58
ENGINEERI~lG
SPECIFICATION
OP CODE 7
DIAGNOSE
This command causes the TU58 to run its internal
diagnostic program.
Upon completion TU58 sends
an end packet with appropriate success code.
OP CODE 8
GET STATUS
OP CODE 9
SET STATUS
Treated as a NOP because TU58 status cannot be set
from the host.
The TU58 returns an end packet.
OP CODE 10
GET CHARACTERISTICS
This command caus'es the TU58 to send a data message
to the host containing its operating parameters.
The format of these parameters is not defined yet.
OP CODE 11
SET
CHAR~CTER!STICS
The TU58 characteristics cannot be changed so this
command is treated like a NOP.
1
SAIZE
DEC FORM NO
ORA 108
SN·01022·16-N37Q-(381)
l~pDE I
-J
!
NUM SER.
-;-~ -r\.-/) ,
1\ t
SHEET
...3k.-
OF
'I
~~v
r:r.;!
::...
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.3 Linearized : No XMP Toolkit : Adobe XMP Core 4.2.1-c043 52.372728, 2009/01/18-15:56:37 Create Date : 2014:06:30 12:50:44-08:00 Modify Date : 2014:06:30 12:07:47-07:00 Metadata Date : 2014:06:30 12:07:47-07:00 Producer : Adobe Acrobat 9.55 Paper Capture Plug-in Format : application/pdf Document ID : uuid:7a2a72ca-a5ff-6844-8fd7-349155bcb0ca Instance ID : uuid:29b820bf-9511-7b4e-9f3d-d1ae43c230a1 Page Layout : SinglePage Page Mode : UseOutlines Page Count : 36EXIF Metadata provided by EXIF.tools