Digital PDFs

EK-ORV20-IN-004

2000

80 pages

Original

16MB

view download

OCR Version

5.6MB

view download

Document:	RV20 Optical Disk Subsystem Installation Guide
Order Number:	EK-ORV20-IN
Revision:	004
Pages:	80
Original Filename:

OCR Text

EK-ORV20-IN-001

RV20
Optical Disk Subsystem
Installation Guide

EK-ORV20-IN-001

RV20

Optical Disk Subsystem
Installation Guide

Prepared by Educational Services
of Digital Equipment Corporation

I1st Edition, January, 1988

Copyright © 1988 by Digital Equipment Corporation.
All Rights Reserved.
Printed in U.S.A.
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
Corporation assumes no responsibility for any errors that

notice. Digital Equipment
may appear in this document.

WARNING
Use of controls and adjustments or performance of procedur

es other than

those specified herein may result in hazardous radiatio

n exposure.

DANGER

B LASER PRODUCT]S

INVISIBLE LASER RADIATION WHEN OPEN.

AVOID DIRECT EXPOSURE TO BEAM.

LEGAL NOTICE: TMSCP and STI protocols and document
ation are the proprietary
information of Digital Equipment Corporation. UNIBUS/
Q-BUS/BI-BUS port drivers
and documentation for MSCP/TMSCP products are also
proprietary information of
Digital Equipment Corporation.

NOTICE: This equipment generates and uses radio frequenc
y energy. It has been type
tested and found to comply with the limits for a Class
B computing device in accordance
with the specifications in Subpart J of Part 15 of FCC
Rules, which are designed to provide reasonable protection against radio and television
interference in a residential installation. However, there is no guarantee that interfere
nce will not occur in a particular
installation. If this equipment does cause interference to
radio or television reception, the
user is encouraged to try to correct the interference.
The following are trademarks of Digital Equipment

Massachusetts.

dlilglilt/al I
DEC

DECmate

DECnet

DECUS

Corporation, Maynard,

Professional

UNIBUS

DECwriter

Q-Bus

DIBOL
MASSBUS

VAX

Rainbow
RSTS

VAXstation
VMS

DECsystem-10

PDP

DECSYSTEM-20

RSX

P/OS

Work Processor

Contents
Chapter 1
1.1

1.2
1.3
1.4

1.5

1.6

Subsystem Overview . ............. ... .
Installation Overview . .. ... ... ... i
..
...
Tools and Equipment . . .. ........
.
i
....
...
Site Requirements . ........
. ... ... ..

1.4.1

Weight.

1.42

Temperature and Humidity . ... ...............

1.4.3

SPacCe

. . .. .

Unpacking and Inspection . . . . ........ ...
Related Documentation . . . ... ... ... oo

Chapter 2
2.1

Introduction

Installation

e .
General . .. ...

2.2

T1014 KLESI-B Adapter Module Installation—VAX 8200

2.3

T1014 KLESI-B Adapter Module Installation—VAX 8800

2.4

M7740 KLESI-Q Adapter Module Installation—MicroVAX

SYStEIMS . . . . . . i

SYSLEINS . . . v v v it i
SYSEEIMS . . . v v v v vt e e e

24.1

2.4.2
2.4.3
2.5

M7740 Address Setting . . . . ... ... oo

Determining M7740 Backplane Location . . . . ... ....
Completing M7740 Installation . . . .. ............

Cabling the RV20 Subsystem . . .. ....................

iii

2.6

2.7
2.8

Powering Up/Self-Testing

. ................
.
.. 2-26
Assigning TMSCP Unit Numbers ... ...
.........
.. . . 2-28
Completing the RV20 Installation . ......
......
.... 2-29

Chapter 3

Verification

Overview . ...

3.2

Internal Drive Power Up/Self—Testmg ....

3.3

ller . . ... ... ... 3-2
Performingthe Test ............
...
..... 3-4

Controller Fatal Error Indication . ... ...
......
. ..
3-5

LevellllTesting

3.41

3.4.1.4
3.4.1.5
3.4.2

4.3

Diagnostics . . ......
.. ..
..
... ..
..
.. .

3-6
ATTACH and SELECT . . ... ......
...
..
. 3-7
Running the Tests .. ..
.. .. .. P 3-8
Error Reporting . . . ....
... ..
... .. .. . 3-10

Running Level IIl Tests Under MDM . . ...
... .. . .. 3-10
3.4.2.1
Equipment . . . ..... .. . ... . . .. ... ...
3-10
3.4.2.2
Bringing MDM Up . .. ............
.
..
. 3-10
3.4.2.3
Running the Tests . ... ... ... .. ... ..
.. . 3-11

3.4.24
Error Reporting . . . ......
.. ...
..
.. ..
.
. 3-12
Creating a Dedicated Diagnostic Test Disk . ....
....... 3-12

Chapter 4
41

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

3-6
Running Level Il Tests Under VDS . . . .. ...
. ..
.
3-6
3.4.1.1
Equipment . .. ....
.. .. .....
... . . ..
.
.. 3-6
3.4.1.2
Bringing VDS Up and Loading the RV20

3.4.1.3

4.2

3-1

Power-Up Testing the Drive Subsystem Contro
3.3.2

3.5

...

................ 3-1

3.3.1

Installing an RV20 Add-On Drive

Overview . ........ .. ... ... ..
4-1
Unpacking and Inspecting . . . ...
.. ST 4-3
INSTALLATION ............
......
..
e 4-4
4.3.1
System Preparation ........
..
.. ..
..
.. ... 4-4
4.3.2
Assembling and Mounting the Two Slide Assemb
lies . . . 4-4
4.3.3
Securing the Drive to the Mounted Slides . . .
. ..
. ...
. 4-7
4.3.4
Installing the ESD Brackets . ......
...
.... 4-8

4.3.5

Cabling .. ..............
. e

4-9

4.3.6
4.3.7

Assigning a CM Number to the Drive ... ......... 4-10
Completing the Installation . ... ............... 4-11

Figures

1-1
1-2
1-3
1-4
1-5
1-6
1-7
2-1
2-2
2-3
2-4
2-5
2-6

RV20 Subsystem Cabinet . ..................... 1-2
RV20 Subsystem Block Diagram . . . . .............. 1-3
Removing the RV20 from its Skid - Step 1 .. ......... 1-5
.. 1-6
Removing the RV20 from its Skid - Step 2 . . . ......
1-7
..
......
...
Step3
Skid
its
Removing the RV20 from
.
Removing the RV20 from its Skid - Step 4 .. ........ 1-8
Removing the RV20 from its Skid - Step 5 ... ........ 1-9
2-2
Stabilizer Leg . . . . .. ...
BA32 Box Track Lock . . . .. ... .. i 2-3
BA32 Bottom Cover Removal . . . . . ............... 2-4
KLESI-B Cables. . .. ......... P e 2-5
KLESI-BI/O Connector . . . . . ..o v v v vi oo e v 2-7
VAX 8800 Cabinet (Front View) .. .. .............. 2-9

2-8
2-9
2-10
2-11
2-12
2-13
2-14
2-15
2-16
3-1
4-1
4-2
4-3
4-4
4-5
4-6

M7740 KLESI-Q Adapter Module . . . ............. 2-13
M7740 Jumper and Switches . ... ... 2-14
BA23 Backplane: Bus Grant Path . .. ............. 2-17
BA123 Backplane: Bus Grant Path. . . ............. 2-18
KLESI-Q I/O Connector . . ... .. ... 2-19
... 2-20
... ...
...
RV20Rear Panel ......
RV20 Subsystem Cabling Block Diagrams. . . ........ 2-21
. 2-26
RV20FrontPanel. . ... ....... ... ...
RV20 Maintenance Panel . . . . ... ............... 2-27
Drive Subsystem Controller LEDs . . . .............. 3-2
4-2
HO9643 Cabinet . . . . oot
o 4-5
.. .. . ...
Securing the Slides . ... ......
4-6
.
Mounting Holes . ... ..
Mounting the Drive to the Slides . .. .............. 4-7
ESD Bracket Installation . . .. ... ................ 4-8
Connecting to the Power Controller ... ............ 4-9

2-7

VAX 8800 Cabinet (Rear View) . . . ... ... ... .. .. 2-10

Tables
1-1

Parts List . ......

1-2

Related Documentation

Document

Part Number

Description

RV20 Optical Disk Subsystem Owner’s Manual

EK-ORV20-OM

Customer document containing operating procedures, maintenance and
troubleshooting instructions.

RV20 Optical Disk Subsystem Service
Guide

EK-ORV20-5V

Contains service information on the
RV20 subsystem, including instructions on how to run diagnostics to
isolate a problem to a Field Replaceable Unit (FRU). This guide contains
the Recommended Spares List (RSL)
and the removal and replacement
procedures for all FRUs.

Introduction

1-11

Chapter

Installation
2.1 General
This chapter explains how to install the RV20 subsystem to the point

where diagnostic verification can be done. The four major steps in this
process are as follows.

Setting up and installing the LESI adapter module in the host

(Paragraphs 2.2, 2.3, and 2.4)

Cabling the subsystem (Paragraph 2.5)

Powering up/self-testing all drives in the subsystem (Paragraph

Assigning and labeling each drive with a TMSCP unit number

2.6)

(Paragraph 2.7)

The RV20 subsystem can be installed in any Bl-based VAX or Q-Bus based
MicroVAX system.

In Bl-based systems, the LESI adapter is the T1014 module. The T1014
module installation is described in Paragraphs 2.2 and 2.3. Paragraph
2.2 gives installation instructions for the VAX 8200 family. Paragraph 2.3
gives installation instructions for the VAX 8800 family. For VAX 8250
systems, refer to the LESI adapter installation instructions in the host
installation manual. For VAX 8500 systems, use Paragraph 2.4 of this
manual. (8500 installation instructions are essentially the same as those
for 8800 systems.)

In MicroVAX systems, the LESI adapter is the M7740 module. The M7740
module installation is described in Paragraph 2.4.

Installation

2-1

2.2 T1014 KLESI-B Adapter Module Installation—
VAX 8200 Systems
In VAX 8200 family systems, the T1014 KLESL-B adapter module
is
installed in the BA32 box.

Warning
When working on any VAX 8200 family system, you must extend
the stabilizer leg (Figure 2-1) before pulling the BA32 box from
the cabinet. Failure to do so will cause the cabinet to tip forward
when the BA32 box is pulled out.

Figure 2-1:

Stabilizer Leg

STABILIZER

MKV85-1907
SHR-0304-87

2-2

Installation

1. Power down the host using the proper system shutdown procedures.
Remove the front and rear doors.

7 From the rear of the cabinet, release the BA32 box track lock safety
catch (Figure 2-2).

Slide the BA32 box out of the cabinet.
Caution

Always use an antistatic wrist strap connected to the processor
cabinet when working inside the host.

Figure 2-2:

BA32 Box Track Lock

A\
|l

RELEASE SAFETY

CATCH AND PUSH

PROCESSOR DRAWER
MKV86-0273
SHR-0305-87

Installation

2-3

Remove the BA32 box top cover.

Rotate the BA32 box up so it is in the position shown in Figure 2-3.
Remove the bottom cover.

Figure 2-3:

BA32 Bottom Cover Removal

MKV85-1921
SHR-0306-87

2-4

Installation

Select a slot for the T1014 KLESI-B adapter module. Make note of

the slot identification (node ID).

If necessary, install a transition header in the slot that will hold the
T1014 KLESI-B adapter module.

Feed the double-connector end of the KLESI-B internal ribbon cable
through the cable slot at the bottom of the BA32 box. Make sure the
cable does not scrape against the sheet metal edges of the slot.
Pull the cable out far enough to allow dual cable connectors to reach
the top of the VAXBI backplane assembly with adequate slack.
In some systems, the
10. Note the orientation of the BI backplane.
is important that you
It
2-4.
Figure
to
Refer
.
inverted
is
ne
backpla
install the KLESI-B module into Zone E of the backplane.

Using Figure 2-4 as a guide, insert the two cable connectors on the
KLESL-B internal ribbon cable into Zone E of the backplane slot that
will hold the T1014 module. Be sure the cable is properly oriented
|

and the connectors are seated correctly.

Figure 2-4: KLESI-B Cables

oo,

|o
|

E
ZONE

ZONE C
L

ZONE C

ZONE D

TO 1/0 DISTRIBUTION
PANEL

NORMAL Bl BACKPLANE
ZONE E
T

01/0

DISTRIBUTION
PANEL

INVERTED Bl BACKPLANE

SHR-0307-87

Installation

2-5

11. Replace the BA32 box bottom cover.
Route the free end of the T1014 module cable through the cabinet
to
the input/output (I/O) distribution panel at the rear of the cabinet.
13. Locate an available position for the KLESI-B connector
on the I/O
distribution panel (Figure 2-5).
14, Remove the blank insert for the KLESI-B cable connector
.

15. Route the cable through the opening in the panel.

16. Attach the I/O bulkhead panel to the KLESI-B cable with
the hex
standoffs and helical lockwashers (Figure 2-5). Tighten the standoffs
.
17. Install the I/O bulkhead panel on the I/Q distribution panel

screws (Figure 2-5),

18.

with two

Rotate the BA32 box down to its normal position.

19, Insert the T1014 KLESI-B adapter module into its slot in the VAXBI
card cage.
20. Replace the BA32 box top cover, but do not tighten the screws.

21. Power up the system. Check to see that the yellow Light
Emitting
Diode (LED) on the T1014 module lights up after about
10 seconds.
This indicates that the module is installed and is working
properly.
If the yellow LED does not light up, make sure that
nothing is
connected to the LESI cable on the I/O distribution panel. If
nothing
is connected to the cable and the yellow LED does not
light up at

power-up, then a module problem exists.

22. Upon successful completion of the module self-test,
power
system.

23. Tighten the BA32 box top cover screws.
24. Slide the BA32 box into the cabinet.
25. Replace the cabinet front and rear doors.

2-6

Installation

down the

KLESI-B I/O Connector

Figure 2-5:

INTERNAL RIBBON CABLE
CONNECTS TO KLESI-B 1/0

TRANSITION HEADER

I/O DISTRIBUTION
PANEL

N%
HEX

/‘@/

STANDOFFS

po|

AREA ENLARGED

SHR-0281-87

Installation

2-7

2.3 T1014 KLESI-B Adapter Module Installation—
VAX 8800 Systems
This installation procedure applies to all VAX 8800 family (8700 and 8800)

systems. VAX 8700 and 8800 systems have different cabinets. Another
difference between the two is that VAX 8700 systems have a single CPU,
while 8800 systems are dual processors. The VAXBI cabinet is located in
the same place in both systems, so the installation of the T1014 module
is the same for either system.
1.

Unlock and open the front doors to gain access to the front of the

system.

Locate the VAXBI backplane on the right side of the system behind
the module access gate (Figure 2-6).
The T1014 module will be
installed in an available slot. Select an available slot.

After you select a slot for the T1014 module, power down the system
using the proper system shutdown procedures.
Unlock the back doors to gain access to the rear of the system

(Figure 2-7). Examine the selected slot. Make sure there is a node
ID plug in the slot and make note of the slot identification (node ID).

If necessary, install a transition header in the slot.
Examine the I/O distribution panel and cable path (Figure 2-7). You

will need to use one of the small rectangular cutouts for the KLESI-B
cable.

At the front of the system, install the T1014 module in the selected
backplane slot.

At the rear of the system, open the I/O distribution panel. There are
three captive screws securing the I/O panel to the frame (Figure 2-7).
Loosen the three screws one-quarter turn each, and swing the I/O
panel down.
At the rear of the system, install the KLESI-B cable into Zone E of the
VAXBI backplane. Make sure the cable is oriented properly (refer to
Figure 2-4, if necessary).

2-8

Installation

Figure 2-6:

VAX 8800 Cabinet (Front View)
i

U
"0 T0o=o—o0~

e i
e G
ol

MODULE
ACCESS

GATE

rd 1

[RAMA

VAXBI

CPU

MEMORY

”~‘=\\\\\'4'§||“/'/;”/§‘¥1\

Y= AEE
Rkt

CPU CABINET (FRONT VIEW)
SHR-0400-87

Installation

2-9

Figure 2-7:

VAX 8800 Cabinet (Rear View)

AEWAY. LTI
|

T
ooppod

[lagapn

CPU BACKPLANE

\B/fiégi’LANE/" il
:

|
—

Blinm
-

;

‘

| —

(EXED

S -

Corive = /:—V’%
D

{ alilem

VAX 8800 CABINET (REAR VIEW)
MKV87-0334
SHR-0410-87

2-10

Installation

10.

Route the KLESI internal ribbon cable to the I/O distribution panel.
Follow the same cable path as for the other VAXBI modules, through
the opening to the left of the backplane and down.

11.

Remove a blank insert on the I/O distribution panel for the KLESI-B

12.

Route the cable through the opening in the panel.

cable connector.

Attach the I/O bulkhead panel to the KLESI-B cable with the hex
standoffs and helical lockwashers (use Figure 2-5, if necessary).
panel with 2
14. Attach the I/O bulkhead panel to the I/O distribution

13.

screws (use Figure 2-5, if necessary).

15.

Swing the 1/O distribution panel back into place and secure the three

captive screws.

16.

Power up the system. Check to see that the yellow LED on the T1014
module lights up within 10 seconds. This indicates that the module
is installed and is working properly.

If the yellow LED does not light up, make sure that nothing is
connected to the LESI cable on the I/O distribution panel. If nothing
is connected to the cable and the yellow LED does not light up at
power-up, then a module problem exists.

Turn to Paragraph 2.5, Cabling the RV20 Subsystem.

Installation

2-11

2.4 M7740 KLESI-Q Adapter Module Installation—

MicroVAX Systems

The M7740 KLESI-Q adapter module installation includes
®

2.4.1

module

Determining correct backplane location, and installing the M7740

module in the backplane

the following.

Determining and assigning the address for the M7740

Installing the I/O distribution panel bulkhead at the rear
of the
host, and connecting the cable from the bulkhead to the
installed
M7740
|

M7740 Address Setting

MicroVAX systems have two possible configurations:
the standard BA23
box and the BA123 box (“‘world box""). Except where noted,
the installation instructions given here apply to either of the two
system boxes.
First, determine the software address for the M7740
module. The Q-Bus
uses a 22-bit address structure (address bits 0 through 21).
Address bits
3 to 12 are set on the M7740 switchpack. Address
bit 2 is set on the
Jumper just below the M7740 switchpack. (Refer to
Figure 2-8 for M7740
switchpack and jumper locations.) Address bits 0 and
1, and 13 to 21 are
preset. They cannot be changed.
|

The specific address the M7740 is assigned depend
s on the present
configuration of the system. Use the SYSGEN utility
to find the present
configuration of the system.
Enter SYSGEN by typing MC SYSGEN at the
prompt (). Entry into
SYSGEN is indicated by the SYSGEN
> prompt. At SYSGEN
>, type

SHOW/CONFIG and the current system configuration

2-12

Installation

is displayed.

LES| BUS CONNECTOR

D31

M7740 KLESI-Q Adapter Module

Figure 2-8:

ADDRESS BITS 12-3
S10-S1
(E58)

SW1—ADDRESS BIT 12

/ SW2—ADDRESS BIT 1110

SW3—ADDRESS BIT

BT CWa_ADDRESSBIT
o

— SW5—ADDRESS BIT 8

SW6—ADDRESS BIT 7

= SW7—ADDRESS BIT65
e

SW8—ADDRESS BIT

SW9—ADDRESS BIT 4

\ SW10—ADDRESS BIT 3
JUMPER—ADDRESS BIT 2

EDGE CONNECTOR
MA1312-83

SHR-0172-86

Installation

2-13

The M7740 module is preset to address 774500 (octal). Address 774500 is
the first valid address for the M7740 module. If 774500 is not available,
the switchpack and jumper must be configured to an available floating
address. The floating addresses begin at 760404. Figure 2-9 shows how
to set the jumper and switches to 1 or'0. Table 2-1 gives the bit settings
for the first nine addresses.
|
Figure 2-9:

M7740 Jumper and Switches

SWITCHES S1 TO S10 (E58)

B
LI
[
B
-

Swi1

(ADDRESS BIT 12)

SW2

(ADDRESSBIT 11)

SW3

(ADDRESS BIT 10)

Sw4

(ADDRESS BIT 9)

SW5hH

(ADDRESS BIT 8)

SW6

(ADDRESS BIT 7)

Sw7

(ADDRESS BIT 6)

SW8

(ADDRESS BIT 5)

SW9

(ADDRESS BIT 4)

SW10

(ADDRESS BIT 3)

JUMPER (ADDRESS BIT 2)

JUMPER TO MATCH O

JUMPER TO MATCH 1
MA-1313-83
SHR-0174-86

2-14

Inustallation

M7740 Address Settings
774500 760404 760410 760414

" Table 2-1:

760420~ 760424

760430

760434 760440

SW1 | 0

sw2 | 1

SW3 | 0

SW5 | 1

111

SW6 | 0

sw7 | 1

sW8 | 0

SW10 | 0
Jumper | 0

S swa

SW9 | 0

Set the address according to Table 2-1. To determine the correct
backplane location for your M7740 module, proceed to Paragraph 2.4.2.
The following discussion of the SYSGEN utility gives greater detail on its
|
use in M7740 address setting.
SYSGEN Utility

Use the SYSGEN utility to aid in determining the correct address for a
VMS-based system. The SYSGEN utility uses the same rules for address
selection as the VMS operating system. To find the correct address for
your RV20, first determine the existing system components.

If the present configuration of the system is not known, enter SYSGEN
(follow step 1 below). Type SHOW/CONFIG at the SYSGEN> prompt,

and the current system configuration is displayed. To determine the
correct address for your RV20, follow these steps.
1.

Enter the SYSGEN utility.
$ MC SYSGEN <CR>
SYSGEN>

Installation

2-15

Enter the configuration section of SYSGEN,

SYSGEN> CONFIGURE <CR>

DEVICE>

At the DEVICE> prompt, enter the options that are present on the

system. Include the RV20 as one of the options.

For SYSGEN utility purposes, the RV20 is a TU81. To add an RV20 as a
device on the system, increase the TU81 count by 1.
For example, your current system has one QNA, two TUS81s, and two
UDAs. You want to add an RV20 to the system. In SYSGEN, you enter
three TU81s (the third one being the RV20).

The following illustrates this example. Remember, your system is probably configured differently.
DEVICE> QNA

DEVICE> TU81
DEVICE>

UDA

3
2

When all the devices are listed, press Ctrl/Z to end the input session.
SYSGEN calculates (and displays) the correct address for the RV20
and for all the other hardware you entered.

Once the correct address for the RV20 is known, yoii can then assign the

M7740 module to its correct address in the system.
DEVICE> Ctrl/2
DEVICE:

UDA

NAME:

PUA

CSR:

772150

DEVICE:

Vector:

TuUS81

154

NAME:

Support:

PTA

CSR:

yes

774500

Vector:

260

Support:

yes

Vector:

yes

DEVICE:

QNA

‘NAME:

XQA

CSR:

774440

DEVICE:

UDA

NAME:

120

PUB

Support:

CSR:

DEVICE:

7603
- 34*
Vector:

TU81

300

yes

DEVICE:

NAME: PTB

Support:

TU81

- CSR:

760444*

NAME:

Vector:

CSR:

760450*%

310

Support:

Vector:

314

yes

Support:

yes

SYSGEN>

PTC
-

Type EXIT at the SYSGEN > prompt
to exit from SYSGEN.

SYSGEN> EXIT
S
S

Note
Once you have entered an RV20 on the system with these pro-

cedures, subsequent SHOW/CONFIG commands recognize the
subsystem as an RV20, not a TU81. The RV20 is a TUS1 only

during a CONFIGURE.

2-16

Installation

2.4.2 Determining M7740 Backplane Location

MicroVAX systems have two possible configurations: the standard BA23
box or the BA123 box (‘““world box’’). The backplane restrictions for the
BA23 (8-slot) and BA123 (12-slot) boxes are as follows. Refer to Figures
2-10 and 2-11, respectively.

The CPU module always occupies the first slot of the backplane.
Memory modules always occupy the next slots after the CPU module.

If an RQDX controller (M8639) is in the system, it must occupy the

last used slot in the backplane.

When installing the M7740 module into an AB or CD row pair, the
other half of the slot must be occupied. If no other module occupies
that slot, an M9047 bus grant continuity card must be installed in the
unused row pair. This passes the grant through the priority granting
row of that slot. The priority granting rows are A for the AB side of
the slot, and C for the CD side of the slot.

You cannot install an M7740 module or a grant card in the following
CD rows.

‘BA23 (8-slot)

Slot 3

BA123 (12-slot)

Slots 3 and 4

Figure 2-10:

BA23 Backplane: Bus Grant Path
ROWS

A
-

;

CPU

MEMORY

SLOTS
5
6
7

—

°
*

INSLOTS 4 THROUGH 8
PRIORITY GRANTING ROWS
ARE: ROWA, ROWC
SHR-0010-85

Installation

2-17

Figure 2-11:

BA123 Backplane: Bus Grant Path
SLOTS

[)

| Y

e | Y

L B

R
0
W
S

IN SLOTS
4 THROUGH 12

PRIORITY GRANTING ROWS
ARE:

ROWA, ROWC

<IB/TWO=M=Z

MR-14068

SHR-0090-85

2.4.3 Completing M7740 Installation
Caution
Always use a static discharge kit with a grounded wrist strap
when accessing the internal parts of the MicroVAX system.

To complete the installation of the M7740, the module must be installed
in the backplane and connected to the patch panel at the rear of the
MicroVAX system.

The 1/O bulkhead panel must also be installed in the patch panel of the
system. The BA23 and BA123 boxes use the same bulkhead mounting
hardware. The bulkhead is mounted in any available rectangular cutout
at the rear of the system.
Proceed as follows.

Make sure that system power is off.

Install the M7740 module in the predetermined backplane slot.

If necessary, install an M9047 bus grant continuity card in the backplane.

2-18

Installation

4. Access the patch panel and remove an unused rectangular cutout
having two screws.

5. Route the KLESI-Q internal ribbon cable through the opening in the
panel.

6. Attach the I/O bulkhead panel to the KLESI-Q internal ribbon cable
using the hex standoffs (Figure 2-12). Tighten the standoffs.

Install the I/O bulkhead panel on the patch panel using two screws.

Route the internal ribbon cable from the patch panel to the installed
M?7740 module.

Now proceed to Paragraph 2.5, Cabling the RV20 Subsystem.
Figure 2-12:

KLESI-Q I/O Connector

HEX

STANDOFFS

SHR-0282-87

Installation

2-19

2.5 Cabling
The RV20 subsystem is cabled prior to shipping, You should, however,

verify that the cabling is correct.
cabling examples.

This paragraph gives some typical

A number of configurations are possible, ranging from one RV20 subsystem (one master drive with three slaves) to four separate RV20 subsystems
(four RV20 master drives). The cabling for a specific subsystem depends
on the configuration of that subsystem.

Figure 2-13 shows five connectors on the RV20 rear panel.
®

J61 — LESI interface connector

J18 — ISTin connector — ISI out connector

J19 — Master terminator connector

J62 — Slave terminator connector

Figure 2-13:

RV20 Rear Panel
LESI

INTERFACE

CONNECTOR

J61\

ISIIN

CONNECTOR

J18

CB1

GROUND

MASTER TERMINATOR

STRAP

AC POWER
CONNECTOR
J20

CONNECTOR

J18

ISIOUT
CONNECTOR
J17

SLAVE
TERMINATOR

CONNECTOR
J62
SHR-0283-87

2-20

Installation

The following items are connected to the rear panel of a cabled RV20.
@

LESI Interconnect Cable — The master RV20 in the subsystem
connects to the host with the LESI interconnect cable, The cable
is plugged into connector J61 at the rear of the RV20.

Terminator Assembly — A terminator assembly plugs into two
connectors on the RV20 rear panel. Separate terminator assemblies must be installed in the first and last drives in a subsystem.
If a subsystem consists of only one master (no slaves), then two
terminators must be installed in that master. The terminator in
the master RV20 is connected to J18/]J19 at the rear of the RV20,
The terminator in the last slave RV20 is connected to J17/J62 at
the rear of the RV20.
IST Interface Cable — In a multidrive subsystem, the drives
are daisy-chained together with the ISI interface cable. No ISI
interface cable is needed for a subsystem that consists of only
one RV20.
Figure 2-14 shows five common subsystem cabling configurations. Verify

that the cabling for your specific subsystem is correct.
After the subsystem cabling has been verified, route the LESI interconnect
cable from J61 on the RV20 master drive to the bulkhead connector
at the rear of the host system. Before connecting the cable, however,

power up/self-test the subsystem (Paragraph 2.6) and assign TMSCP unit
numbers to each drive (Paragraph 2.7).
Figure 2-14:

RV20 Subsystem Cabling Block Diagrams
&= TO HOST

MASTER
RV20

JB1: LES|

J18: IS1 IN

J17:1S1 OUT

019

MASTER

.
<

TERMINATOR

CONNECTORS

1 - DRIVE SUBSYSTEM

SHR-0284-87

Figure 2-14 Cont’d. on next page

Installation

2-21

RV20 Subsystem Cabling Block Diagrams

Figure 2-14 (Cont.):

p= TO HOST

[

MASTER

RV20

J61: LES

]
I

J18: 1Sl IN
J17:1SI0UT

J19

VIASTER

J62

TERMINATOR

SLAVE

CONNECTORS

J61: LESI

SLAVE

RV20

|
[Ifi

J18:ISIIN
A

r
J19

MASTER

J17: 18I OUT
TERMINATOR

CONNECTORS

n | J62

SLAVE

TR|

2 - DRIVE SUBSYSTEM

Figure 2-14 Cont’d. on next page

2-22

Installation

SHR-0286-87

Figure 2=-14 (Cont.):

RV20 Subsystem Cabling Block Diagrams
B> TO HOST

MASTER

RV20

r
:

JIBISIIN

J17:1810UT

J19

J61: LESI

MASTER

j
|

TERMINATOR

> I J62

CONNECTORS

SLAVE

B TO HOST

MASTER

[

RV20

J61: LESI

J18: ISl IN

—

J17: ISl OUT

J19

I -

MASTER || =

TERMINATOR

CONNECTORS

2 SEPARATE SUBSYSTEMS

> I J62

SLAVE

SHR-0287-87

Figure 2-14 Cont’d. on next page

Installation

2-23

Figure 2-14 (Cont.):

RV20 Subsystem Cabling Block Diagrams
= TO HOST

MASTER

RV20

[

J61: LESI

J18: ISIIN

]

‘

J17:1S81 OUT

J19

TERMINATOR

MASTER

CONNECTORS

SLAVE

RV20

J61: LESI

J18: 1Sl IN

J17:1SI0UT

J19

—

MASTER

SLAVE

RV20

J62

SLAVE

]

TERMINATOR

CONNECTORS

J61: LESI

| J62

SLAVE

J18:ISIIN

l|<

J17:1SI0UT

J19

MASTER

J62

CONNECTORS

= |

SLAVE

Figure 2-14 Cont’d. on next page

Installation

TERMINATOR

3 - DRIVE SUBSYSTEM

2-24

SHR-0288-87

Figure 2-14 (Cont.):

RV20 Subsystem Cabling Block Diagrams
[

MASTER

RV 20

[

J61: LESI

- TO HOST

}

J18: 18I IN

J17: 181 QUT

TERMINATOR
CONNECTORS

62
SLAVE

J19
—TM MASTER

SLAVE

RV20

J61: LESI

J18: ISl IN

J17:1S10UT

TERMINATOR
| """ CONNECTORS

62
SLAVE

719
MASTER

J61: LESI

SLAVE

RV20

I
I
J19

MASTER

~
I <

RV20

J18:ISI IN

.':

J17:1S10UT

TERMINATOR

CONNECTORS

SLAVE

]

J62

SLAVE

J61: LES

[

J18:1SIIN

Iz:

J17:1S1 OUT

l——

J18

TERMINATOR

J62

MASTER

CONNECTORS

SLAVE

4 - DRIVE SUBSYSTEM

SHR-0288-87

Installation

2-25

2.6 Powering Up/Self-Testing
First, familiarize yourself with the RV20 maintenance panel. The maintenance panel is located on the right of the RV20 front panel behind an
access door. Figure 2-15 shows the RV20 front panel. Figure 2-16 shows
the maintenance panel controls and indicators.
Figure 2-15:

RV20 Front Panel

\
\

J—

=
/
DOOR
\\‘\ ZREARAD

CARTRIDGE

(&)

[EFR =
T—

1§

FILTER
GRILL

| Start Write
Stop

Protect

S
TMSCP
UNIT
NUMBER

Power

[

MAINTENANCE
PANEL ACCESS
DOOR

HEXADECIMAL —%
DISPLAY

OPERATOR PANEL

2-26

Installation

SHR-0308-87

Figure 2-16:

RV20 Maintenance Panel
HEXADECIMAL
DISPLAY

INCR LSD

/ KEY

START/STOP KEY

AND INDICATOR L=

DISP MEM KEY *
AND INDICATOR

F1 KEY AND /

INDICATOR

;

REER

KEY

R[N

INCR MSD

ENTER KEY

—"" AND INDICATOR

CE MODE KEY
AND INDICATOR

« \ MASTER

RESET KEY

SHR-0335-87

To power up/self-test the drives in the subsystem, you must connect the
main power cable coming from the power controller to a power outlet
rated for the proper voltage.
1.

Make sure the circuit breakers (CB1) at the rear of each RV20 in the
subsystem are OFF.

Power up the power controller by switching the main breaker to ON.

Power up each drive in the subsystem individually. Set CB1 to ON
and let the drive run through its power up/self-test. Upon successful
completion of the power up/self-test, the maintenance panel display
reads 00 and the CE mode indicator is on.

If the power up/self-test fails, refer to the RV20 Optical Disk Subsystem

Service Guide (EK-ORV20-SV).
If the power up/self-test passes, proceed to Paragraph 2.7 and assign each
drive a unique TMSCP unit number.

Installation

2-27

2.7 Assigning TMSCP Unit Numbers
Note
The RV20 subsystem is a disk drive, but the host operating system
‘’sees’’ it as a tape device.

Each RV20 drive in the subsystem must be assigned a unique TMSCP
unit number. For example, if an RV20 subsystem is MUAO on the host
system, 0 is the unit number, MU is the device identifier (tape drive),
and A represents the device (the entire subsystem as a whole). Each
drive within a subsystem must have a unit number unique to the device
(MUAO, MUA1, and so on).
Any number from 0 to 251 can be used. The only restriction is that no two
RV20 drives within a subsystem can have identical TMSCP unit numbers.
You cannot have two RV20 drives that have device name MUAO. You
can, however, have an MUAQ and an MUBOQ because MUA is completely
independent of MUB.
If you have four RV20 subsystems, and they have device names MUA,
MUB, MUC, and MUD, it is valid to assign TMSCP unit number 0 to all
four master drives MUAQ, MUBO, MUCO0, and MUDO0). However, it may
be less confusing to a customer if you assign TMSCP unit numbers like
MUAQO, MUB1, MUC2, and MUD4. Also, if you assign unique TMSCP
unit numbers, a customer who has multiple RV20 subsystems can swap
the drives between subsystems without having to change the TMSCP unit
numbers.
Before performing test Al (to assign the unit number), decide what
numbers each drive should have. After you assign the unit number, you
need to label the drive with that number.

To assign a unit number to each RV20 drive, power up the drive, enter
CE mode, and perform test Al. This test allows access to the EEPROM
where the unit number is stored (EEPROM address 00H).
If the drive is not powered up, power up now and let the system cycle
through its self-tests (3 to 4 minutes). If no error code is displayed, the
drive is already in CE mode. The CE mode indicator lights up when you
are in CE mode.

If the drive is already powered up, you can enter CE mode by pressing the
CE mode switch on the maintenance panel (Figure 2-16). The Start/Stop
switch on the front panel must be in the Stop (out) position, however.
1.

2-28

Press the INCR LSD and INCR MSD keys.
Al appears on the
maintenance panel hexadecimal display. Press ENTER.

Installation

Start the test by pressing the maintenance panel START/STOP key.
If a 9D, 9E, or 9F appears on the operator panel display, a problem
is present in the EEPROM. You cannot access the EEPROM until the
problem is corrected. Follow the corrective procedures in Paragraph
3.7 of the RV20 Optical Disk Subsystem Service Guide (EK-ORV20-5V).

Ifno error code appears, press the INCR LSD and INCR MSD keys on
the maintenance panel. When 00 appears on the maintenance panel
display, press the ENTER key. Then the address 00 appears on the
operator panel display, while the contents of that address shows on
the maintenance panel display.

Use the INCR LSD and INCR MSD keys to enter the TMSCP
unit number (hexadecimal). Table 2-2 is a decimal-to-hexadecimal
conversion chart for numbers 0-251. Make sure you enter the unit
number in hexadecimal. Also, be sure the unit number you assign the
drive is unique to that controller. Two drives on the same controller
cannot have the same unit number.

To exit the test and store the new values, press the START/STOP key or
the CE mode key on the maintenance panel. This writes the new data
into the EEPROM.

To quit the test without saving the changes, press the MASTER RESET
key on the maintenance panel.

After you assign the unit number, label the drive in the recessed area
on the front panel (Figure 2-15). Use the numbered labels supplied
with this manual.

2.8 Corhpletng the RV20 Installation
1.
2.

Make sure that the host power is off.
Connect the LESI cable to the patch panel at the rear of the host and
secure it.

Replace the rear cover on the H9643 cabinet.
drives in the subsystem remain on.

Replace the host rear door.

Make sure the RVZO

Proceed to Chapter 3 and run verification tests on the subsystem.
This completes the RV20 subsystem installation.

Installation

2-29

Table 2-2:

Decimal-to-Hexadecimal Conversion

Decimal

Hex

Decimal

Hex

Decimal

Hex

Decimal

Hex

00
01
02
03

64
65
66

40
41
42

126
127
128
129

1
2
3

7F
80
81

189
190
191
192

BD
BE
BF
Cco

4
5
6
7
8

04
05
06
07
08

67
68
69
70
71

43
44
45
46
47

130
131
132
133
134

82
83
84
85
86

193
194
195
196
197

Cl
C2
C3
c4
C5

135

198

cé

07:

136

199

137

200

cs8

0oC

138

201

13
14
15
16
17

0D
OE
OF
10
11

76
77
78
79
80

4C
4D
4E
4F
50

139
140
141
142
143

8B
8C
8D
8E
8F

202
203
204
205
206

ca
CB
CcC
CD
CE

144

207

19
20
21
22
23
24
25
27
28
29
30

13
14
15
16
17
18
19
1B
1C
1D
1E

82
83
84
85
86
87
88
89
91
92
93

52
53
54
55
56
57
58
59
5B
5C
5D

145
146
147
148
149
150
151
153
154
155
156

91
92
93
94
95
96
97
99
9A
9B
9C

208
209
210
211
212
213
214
215
217
218
219

DO
D1
D2
D3
D4
D5
D6
D7
D9
DA
DB

32
33

157

220

20
21

95
96

5F
60

158
159

9E
9F

221
222

160

223

161

224

36
37
38
39
40
41
42
43
44

24
25
26
27
28
29
2A
2B
2C

99
100
101
102
103
104
105
106
107

63
64
65
66
67
68
69
6A
6B

162
163
164
165
166
167
168
169
170

A2
A3
Ad
AS
Ab
A7
A8
A9
AA

225
226
227
228
229
230
231
232
233

El
E2
E3
E4
E6
E6
E7
E8
E9

108

171

234

109

172

235

47
48
49
50
51
52
53
54
55
56
57
58
59
69
61
62

2F
30
31
32
33
34
35
36
37
38
39
3A
3B
3C
3D
3E

110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125

6E
6F
70
71
72
73
74
75
76
77
78
79
7A
7B
7C
7D

173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188

AD
AE
AF
BO
Bl
B2
B3
B4
B5
B6
B7
B8
B9
BA
BB
BC

236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251

EB
EC
ED
EE
EF
FO
Fl
F2
F3
F4
F5
F6
F7
F8
F9
FA
FB

2-30

Installation

Chapter

Verification
3.1 Overview
After the subsystém is installed, verify that all the drives are operational

by performing three types of tests.
e

Power up/self-tests on all the drives in the subsystem (Paragraph 3.2)

Power-up test of the drive subsystem controller (Paragraph 3.3)

Level IIl functional tests (Paragraph 3.4)

Paragraph 3.5 gives instructions on how to create a dedicated diagnostic
test disk (should this be necessary).

3.2 Internal Drive Power Up/Self-Testing
Paragraph 2.6 gives instructions on how to power up/self-test all the drives
in the subsystem. This is done prior to assigning TMSCP unit numbers
to each drive. Refer to Paragraph 2.6 for instructions on running these
tests.

Verification

3-1

3.3 Power-Up Testing the Drive Subsystem
Controller
The drive subsystem controller module has a set of power-up tests that
run whenever power is applied to the master drive in an RV20 subsystem.
The results of the tests are indicated on seven LEDs located on the
module. These LEDs are numbered D0 through Dé6. Figure 3-1 shows
the location of the LEDs on the drive subsystem controller.

Figure 3-1:

Drive Subsystem Controller LEDs

FRONT OF DRIVE

LES! LED D6

“DIAG” LED D5
ISI LED D4

3-2

Verification

The seven LEDs are divided into a group of three test LEDs (D4 to D6)
and another group of four communications LEDs (D0 to D3). After all
the power-up tests run (or when a failure occurs in one of the tests), the
three test LEDs are updated as described below. Then, communication
with the drives in the subsystem is attempted, and the communication
LEDs are updated.

D6 — LESI LED

As with all seven LEDs, on power-up D6 lights up. The drive subsystem
controller checks for the presence of the KLESI adapter. The adapter is
assumed to be present if the CIP (Cable In Place) signal is asserted. If
the CIP signal is not asserted, D6 is extinguished. If CIP is asserted,
a handshake test is done.
When the handshake test passes, D6 is
extinguished.
\
It is important to remember the limitations of D6. D6 is extinguished if
the test passes, but it is also extinguished if the CIP signal is not present.
The meaning of this extinguished LED should not be misinterpreted to
mean the test definitely passed. If the LED stays on, however, you can
be sure that the CIP signal is present and the LESI handshake test did
indeed fail.

D5 — ““DIAG’” LED

As with all seven LEDs, on power-up D5 lights up. Upon successful
completion of the Level A microdiagnostics that do not require driving

the ISI bus, D5 is extinguished.
D4 — ISI Bus LED

As with all seven LEDs, on power-up D4 lights up. After the power-up
microdiagnostics pass, the remaining microdiagnostics run. These tests
drive the data and control lines on the ISI bus. When these tests pass,
D4 is extinguished.
D0 to D3 — Communications LEDs

The four communications LEDs correspond to the Control Module (CM)
numbers (0 to 3) that each of the drives in the subsystem has been
assigned. They are labeled as ISI addresses in Figure 1-2.
The master RV20 is always CM 0. The first slave in the daisy-chain is
always CM 1, the second slave in the chain is always CM 2, and the third
slave is always CM 3. The CM number for each drive is stamped on top
of the power indicator/address plug on the RV20 front panel.

Verification

3-3

On power-up, all four of these LEDs light up. After successful completion
of the Level A microdiagnostics, communication is attempted with each
of the drives in the subsystem. As communication is established with
each drive, the corresponding LED (D0 to D3) is extinguished. If all four
LEDs stay on, it may be due to a faulty drive, Level A microdiagnostics
failure, or a fatal error encountered by the drive subsystem controller.

3.3.1 Performing the Test
Make sure that the entire subsystem is cabled properly, including the
cabling to the host from J61 on the master drive. Make sure that all
the slave drives are powered up and have passed their internal power

up/self-tests. The test is executed by powering up the master RV20.
Warning
Don’t forget to extend the cabinet’s stabilizer leg before pulling

the drive from the cabinet (Figure 4-1).

1.
2.

Pull the master RV20 out of the cabinet to expose the top cover.
Remove the rear piece of the top cover on the RV20 master drive.
Locate the drive subsystem controller module in the card cage (top

PCA). Locate the seven LEDs on the outer edge of the PCA (Figure
3-1).
3.

Begin the test by powering up the master drive.

Observe the three test LEDs.

All three test LEDs light up, and then the Level A microdiagnostics run.
At the end of the microdiagnostics, all three test LEDs extinguish. If any

of the three LEDs stays on, this indicates a test failure.
descriptions of each LED above.)

(Refer to the

A flashing sequence follows, indicating the results at the end of the Level
A microdiagnostics. If all three LEDs extinguish and no flashing sequence

occurs, it is likely that the drive subsystem controller encountered a fatal
error. Refer to Paragraph 3.3.2 to determine the problem.

3-4

Verification

If only D5 flashes, this indicates that no CIP signal is present. This could
be because the LESI cable from J61 to the host is not connected. It could
also be because there is no LESI adapter in the host, a bad LESI adapter
is in the host, or the LESI cable is bad,
If only D5 and D6 flash, this indicates that the CIP signal is present, and
the potential for establishing communication with the host exists.
If all three LEDs flash successively, this indicates that the Level A
microdiagnostics passed and communication with the host has been
established.
5.

Observe the four communications LEDs. The LEDs corresponding
to the CM number of each drive in the subsystem extinguish. If the
Level A microdiagnostics do not pass, this communication is never
established and all four of these LEDs stay on.

3.3.2 Controller Fatal Error Indication
The LEDs are set to a unique state if the drive subsystem controller
encounters a fatal error. Possible causes of a fatal error include the
following.

e Power fail interrupt in the controller (the system still has power)
*

Lost communication with the LESI adapter

U/Q port fatal error

When a fatal error occurs, the seven LEDs are set to the following state.
e

3 test LEDs (D4, D5, and D6) — Off

4 communications LEDs — On

Verification

3-5

3.4 Level Il Testing
After the drives and the drive subsystem controller have been verified
(Paragraphs 3.2 and 3.3), run the functional portion of the Level III tests.
When these tests pass, the installation is complete. This paragraph gives
instructions for running the tests under the VAX Diagnostic Supervisor
(3.4.1) and the MicroVAX Diagnostic Monitor (3.4.2). These instructions
are for running the functional tests only. Test descriptions and more
detailed instructions are found in the RV20 Optical Disk Subsystem Service
Guide (EK-ORV20-5V).
It is a good idea to create dedicated diagnostic test disks for each drive
in the subsystem. Paragraph 3.5 explains how to create a dedicated
diagnostic test disk.

3.4.1 Running Level lll Tests Under VDS
On Bl-based systems, the Level III RV20 diagnostics are run through the
VAX Diagnostic Supervisor (VDS). VDS can only be run in standalone
mode. The system must be taken off-line to run VDS.
3.4.1.1 Equipment
To run RV20 diagnostics under VDS, you must have the RV20 diagnostics
on-line. If your system has the latest version of VDS (which includes
the RV20 diagnostic package, or EVRVA), you may simply implement
it. If the system has not been updated with RV20 diagnostics, you must
load the diagnostic package through removable media (tape or floppy
diskette).
You must also use a diagnostic test disk to test drives. A test disk can be

created with utility test 32. (Refer to Paragraph 3.5.) Never use customer
media to do Level III testing. Make sure that the drive to be tested has a
test disk installed and the Start/Stop switch is pressed in.

3.4.1.2 Bringing VDS Up and Loading the RV20 Diagnostics
Begin the test session by booting the diagnostic supervisor.
the diagnostic supervisor is indicated by the DS > prompt.

Entry into

Load the RV20 diagnostics with the following command and press the
Return key (< CR>).
DS>

LOAD

EVRVA <CR>

DS>

When the diagnostics are loaded, the DS> prompt comes up.

3-6

Verification

3.4.1.3 ATTACH and SELECT
The ATTACH command is used to specify a device on the system under
test.
A device cannot be accessed by VDS unless it has first been
ATTACHed.
Before the RV20 can be tested, its device type, location, and characteristics must be ATTACHed. The subsystem is connected to the drive
subsystem controller in the master RV20. The master connects to the
KLESI-B adapter in the host, which is connected to the processor. The
complete path from processor to device must be established with two
ATTACH sequences before testing can begin.
- To ATTACH the subsystem using the standard ATTACH sequence for
all VDS diagnostic packages, use the following command.

ATTACH DEVICE_TYPE DEVICE_LINK DEVICE_NAME BI{NODE #

The ATTACH sequence can be entered on one line or, you will be
prompted for each parameter in the command.

DS> ATTACH DWBLA HUB BLAO

<CR>

DS>
or

DS> ATTACH <CR>

Device Type?

DWBLA <CR>

Device Link?

HUB <CR>

Device Name?

BLAO <CR>

Node

(Hex)?

DS>

The first ATTACH sequence is successful when the DS
> prompt reappears without any error messages. The next ATTACH sequence has the
following format.
ATTACH

DEVICE_TYPE

DEVICE_NAME

DEVICE

CSR_ADDRESS

VECTOR

Because the subsystem has been ATTACHed with the first ATTACH

command string, the supervisor now recognizes the DEVICE_TYPE as
RV20. The DEVICE is the logical name of the controller (MUXX). Further,
you must know the CSR and vector addresses as well as the BR level.

Verification

3-7

Here is an example of the second ATTACH sequence. Remember, the
addresses are probably different for your subsystem.
DS> ATTACH RV20 BLAO MUAO

774500 300 5 <CR>

DS>

The second ATTACH sequence is successful when the DS> prompt
reappears without any error messages.

‘The next step is to SELECT the drive subsystem controller.
DS> SELECT MUAO

<CR>

DS>

3.4.1.4 Running the Tests

When the controller
is SELECTed, you may SELECT and SET the test
parameters you want to use in this testing session.

The tests only run on drives that have disks installed and spinning. (This
is the case if the Ready indicator, located on the drive’s Start/Stop switch,
is on.) When a set of tests is running on a multidrive subsystem, a test
runs on each drive before the next test is performed.
Caution

Never use customer media when doing tests. Use a scratch disk
or a dedicated test disk.

The following commands are used in VDS to run the functional tests.
The complete functional test set is the default testing mode. To run the

complete functional test set (tests 1 through 19), type START with no

qualifiers.
DS>

START <CR>

To run a specific functional test, type START followed by the test number.

For example, to run test 10, type the following,
DS> START/TEST=10:10 <CR>

To run a series of tests in sequence, type the starting and the ending test
numbers in the test number field of the string. For example, to run tests
6 through 15, type the following.

DS> START/TEST=06:15 <CR>

3-8

Verification

SHOW TESTS lists all the RV20 tests. The functional tests are listed in
Table 3-1. Table 3-1 also gives the duration (per drive in the subsystem)
of each test.
SET TRACE traces the test and output status of each test as it runs.
Table 3-1:

Level lll Functional Tests

Number

Name

Duration

1-4 seconds

Power-Up Initialization

1-4 seconds

Steps 1-4 Initialization

1-4 seconds

Diagnostic SA Wrap

1-4 seconds

Vector and BR Level

1-4 seconds

Purge and Poll Test

1-4 seconds

Small Ring Buffer Initialization

1-4 seconds

Large Ring Buffer Initialization

1-4 seconds

Get DUST Status

1-4 seconds

CPU/Server Bus Data Test

1-4 seconds

Internal Drive Microdiagnostic Test

4 minutes per drive

Drive Spin-up Test

1 minute per drive

Drive Spin-down Test

1 minute per drive

Illegal Command and Function Test

1 minute per drive

Basic Seek Test

2 minutes per drive

Serpentine/Pump Seek Test

4 minutes per drive

Basic Read Test

2 minutes per drive

Basic Write Test

2 minutes per drive

CPU/Drive Bus Data Test

1 minute per drive

Verification

3-9

3.4.1.5 Error Reporting

When an error is detected, the diagnostic calls out one of the following
failed items.

an RV20 drive

the communication path to the host (KLESI adapter, the drive
subsystem controller, or LESI cable from subsystem to host)

When the RV20 drive is called out as a replaceable item, specific tests can
be run on the RV20 in error. The procedures for running off-line tests
on a specific RV20 drive are given in Chapter 3 of the RV20 Optical Disk
Subsystem Service Guide (EK-ORV20-SV).

3.4.2 Running Level lll Tests Under MDM

On the MicroVAX, the Level III diagnostics are run through the MicroVAX

Diagnostic Monitor (MDM). MDM can only be run in standalone mode.
The system must be taken off-line in order to run MDM.
3.4.2.1 Equipment

To run the RV20 diagnostics under MDM, you need the version of MDM
that contains the RV20 diagnostics.
You must also use a diagnostic test disk to test drives. A test disk can be
created with utility test 13. (Refer to Paragraph 3.5.) Never use customer
media to do Level III testing. Make sure that the drive to be tested has a
test disk installed and the Start/Stop switch is pressed in.
3.4.2.2 Bringing MDM Up
To start the tests, you must first boot MDM. Once MDM is booted, a
disclaimer screen appears.

Input the date and time at the disclaimer screen. The display echoes
the date and time you typed in and then asks if you want to enter menu
mode.
Enter menu mode by typing 1 and pressing the Return key. The main
menu appears. At the main menu, choose option 4 to display the service
menu.

3-10

Verification

At the service menu, you have a number of options. If you choose option
1, the basic testing parameters currently SELECTed will be displayed.

You may SET new parameters at this screen.

If you choose option 2, you will run the Service mode tests. These tests
perform write operations on the diagnostic test disk. If you wish to run
the Service mode tests without overwriting data on the diagnostic test
disk, press in the Write Protect switch on the front panel of the RV20
being tested. Another way to write protect the diagnostic test disk is to
slide the Write Protect tab on the disk to the WRITE PROTECT position.

Option 4 takes you out of Menu mode and brings you into Line mode,
> prompt. Refer to Paragraph 3.4.2.3,
where you will be at the MDM
on running tests in Line mode.
instructions
for
Tests,
Running the
Option 3 brings you to the device menu, where you can select an RV20
controller from the devices available on the system. When an RV20
controller has been selected, you can run specific tests and series of tests.
3.4.2.3 Running the Tests

In Line mode, once the RV20 subsystem is SELECTed, you may SELECT
and SET the test parameters you want to use in this testing session.

The tests only run on drives that have disks installed and spinning. (This
is the case if the Ready indicator, located on the drive’s Start/Stop switch,

is on.) When a set of tests is running on a multidrive subsystem, a test
runs on each drive before the next test is performed.
Caution

Never use customer media when doing tests. Use a scratch disk
or a dedicated test disk.

There are 19 functional tests. Table 3-1 lists the tests and their durations.
The following commands are used in MDM to run the functional tests.

SET DETAILED ON causes a detailed error report to be displayed

whenever a test fails.

SET SECTION FUNCTIONAL enables only the functional tests (tests 1
through 19) in the specific mode. When the START command is issued
in Verify mode, tests 1 to 11 run. When the START command is issued
in Service mode, tests 12 to 19 run.

SET MODE VERIFY selects Verify mode (tests 1 to 11). These tests take

four to five minutes (per drive) to run.

SET MODE SERVICE selects Service mode (tests 1 through 19). These

tests take 20 to 25 minutes (per drive) to run.

Verification

3-11

SELECT PROGRESS BRIEF enables brief progress reports to display
during the testing session. If you run a test 10 times, a message is
displayed after the tenth pass of the test.
SET TEST NN selects a specific test. SET TEST 2 runs test 2. SET TEST
2-4 runs tests 2, 3, and 4. SET TEST 2,4-6,8 runs tests 2, 4, 5, 6, and 8.

SET PASSES NN selects the number of times a specific test runs.
PASSES 10 runs each test that is set to run 10 times.

SET

SHOW DEFAULT shows the current selected testing parameters.
3.4.2.4 Error Reporting
When an error is detected, the diagnostic calls out one of the failed items.
e

an RV20 drive

the communication path to the host (KLESI adapter, the drive
subsystem controller, or LESI cable from subsystem to host)

3.5 Creating a Dedicated Diagnostic Test Disk
You should use dedicated diagnostic test disks when verifying the installation of a subsystem with Level III testing.

Utility test 32 (utility test 13 in MDM) is called Initialize Diagnostic Test

Disk. It creates a diagnostic test if there is a blank disk in the drive being
tested.

Load a blank disk into the drive being tested and run utility test 32 (utility

test 13 in MDM). You are prompted as to whether you want to create a
dedicated diagnostic test disk. Typ YES and the diagnostic test disk is
then created.
In MDM, type the following to run utility test 13.
MDM>

SET

SECTION

MDM>

SET

TEST

MDM>

START

UTILITY

In VDS, type the following to run utility test 32.
DS> START/SECTION:UTILITY/TEST=32:32

3-12

Verification

Chapter

Installing an RV20 Add-On Drive
This chapter explains how to install and verify an RV20 add-on in an

existing subsystem.

4.1 Overview
A typical add-on installation adds a slave RV20 (PN RV20-B) to an existing
subsystem. However, this is not the only add-on configuration. For
example, the RV20 you are adding on may be an RV20 master drive
(PN RV20-A) that is being installed into an available slot in a customer’s
RV20 cabinet (H9643). Whatever the configuration, there can be no more

than three RV20 add-ons in an H9643 cabinet (Figure 4-1).
More parts are needed when you add on a master RV20 (the KLESI
adapter for the host, the LESI cable, an additional terminator assembly,
and so on) than when you add on a slave. Therefore, it is very important
that you know exactly how the add-on you are installing will sit relative to
the present subsystem before attempting any installation. Check with the
customer after unpacking and inspecting your add-on carton to make sure
the add-on configuration you are installing is what the customer wants.

Installing an RV20 Add-On Drive

4-1

Figure 4-1:
DRI

VE O

H9643 Cabinet

DRIVE 2

STABILIZER

=
:

SHR-0359-87

Installation of an RV20 add-on involves the following. Wherever possible,
previous sections of this book are referenced.

Unpacking and inspecting the add-on carton

Installing RV20 in the H9643 cabinet

Assigning a CM number and a TMSCP unit number to the drive

Verifying the installation through testing
Warning
An RV20 drive weighs 55 Ib. Digital safety standards require that
- two people install the RV20.

4-2

Installing an RV20 Add-On Drive

4.2 Unpacking and Inspecting
Unpack the add-on carton and inspect the contents. Make sure that you
have the right parts for your add-on configuration. Make sure that all
parts are included and are undamaged. Table 4-1 is an inventory list for
an add-on carton.
Table 4-1:

Add-On Carton Contents

Item

Part Number

Quantity

RV20 drive

Master drive: RV20-A
Slave drive: RV20-B

KLESI adapter module

KLESI-B: T1014
KLESI-Q: M7740

1 per master drive (not
included with slave

add-on)
KLESI interface cable

BC17Y-20

1 per master drive (not
included with slave

add-on)
ISI internal cable

29-26800-00

1 per slave drive (not
included with master
add-on)

ISI terminator assembly

29-26458-00

2 per master add-on
(RV20-A)
1 per slave add-on
(RV20-B)

Slide assembly

Slide brackets

4 (2 per slide)

ESD brackets

70-23519

TMSCP unit number labels

36-18940-01

1 sheet

Package of CM
number switch caps

1bag (containing 4 switch
caps)

Mounting hardware

1 bag

Installing an RV20 Add-On Drive

4-3

4.3 INSTALLATION
The instructions for installing an add-on drive in the H9643 cabinet are
set up in the following order.
¢

System preparation (Paragraph 4.3.1)

Assembling the two slide assemblies (Paragraph 4.3.2)

Securing the drive to the slides (Paragraph 4.3.3)

Installing the ESD brackets (Paragraph 4.3.4)

Using shims (Paragraph 4.3.5)

(Cabling the drive and the subsystem (Paragraph 4.3.6)

Assigning a CM number to the drive (Paragraph 4.3.7)

Assigning a TMSCP unit number to the drive (Paragraph 4.3.8)

Verifying the installation with host testing (Paragraph 4.3.8)

4.3.1 System Preparation
1.
2.

Gain access to the rear of the H9643 cabinet by removing the rear
door (and the ground strap).
Make sure all drives in the cabinet are powered down and that the
power switch on the power controller (on the bottom of the cabinet)

is OFF.

Pull out and secure the H9643 stabilizer leg (Figure 4-1).

4.3.2 Assembling and Mounting the Two Slide Assemblies
Each slide assembly includes the following.
*

Two brackets and six (three per bracket) screws for mounting the

slide to the cabinet
°

A slide and three philips screws for mounting the slide to the
RV20 drive

Using Figure 4-2 as a guide, attach each slide to its two brackets.
Do not completely tighten the screws that secure the slides to the
brackets.
Note
Place mounting screws through holes exactly as shown.

4-4

Installing an RV20 Add-On Drive

Figure 4-2:

Securing the Slides
H
H

H
H

H
N

o
N

°
a

[

o
4
a
@
a
4
I
3
3
o

Now mount the slide assembly to the vertical uprights in the H9643
cabinet. First, determine the correct H9643 mounting holes. Different
holes are used for different RV20 drive positions (second, third or
fourth spaces from the top). Figure 4-3 shows the correct holes to use
for each drive position.
a.

Select a vertical upright. Start from the bottom and count up to
the appropriate hole (50, 41, 32).

Secure each pair of slide brackets to the vertical uprights. Use
three philips screws. (Refer to Figure 4-2.) Do not completely
tighten the screws yet!

Installing an RV20 Add-On Drive

4-5

SHR-0361-87

RAIL

)Lty

(_—\-'

«
—
=z

-".'_.—.—'
(o

@)
EI

=2z

73]

[#)]
w

oooood(oo@o]ooooc’ooooooooo’oooooooo

b\ HOLE 32

TM~ HOLE 41

TM~ HOLE 50

w
=

l®))
c

=
=

ql.

§oooooq&oo@ooooo

[AV]

4-6

Installing an RV20 Add-On Drive

ooooooooo\ooooooooQ
3

4.3.3 Securing the Drive to the Mounted Slides
The next step is to mount the RV20 add-on drive to the slide assembly.
Warning
An RV20 drive weighs 55 Ib. Digital safety standards require that
two people install the RV20.

Extend each slide out as far as it will go.

Carefully mount the RV20 drive on the extended slide assembly.
Using three philips screws per slide, secure the drive between the
slides (Figure 4-4).
As you press the slide’s service clips, push the drive into the cabinet.

Make sure the slide’s rubber bumper touches the slide’s stop plate at

the rear. If it does not touch, move the stop plate toward the rubber
bumper (Figure 4-3).

Once the stop plate meets the rubber bumper, extend the drive.
Tighten the slide’s mounting screws in the brackets.

Figure 4-4:

Mounting the Drive to the Slides

Installing an RV20 Add-On Drive

4-7

4.3.4 Installing the ESD Brackets
Install the ESD brackets for the drive. Each drive uses two ESD brackets.
The brackets are mounted on different holes on either side.

Using Figure 4-5 as a guide, install the right ESD bracket in the correct
hole. Make sure the bracket is oriented properly. Do not completely
tighten the mounting screws.
ESD Bracket Installation

(@)

BRACKET

@Il

t‘@Pl

ier

%oooo(@fiooooo@"@j;oooo

BRACKET

REAR OF RV20 DRIVE

Figure 4-5:

rtfi@ 0o o 0 @.@Joooo
ol@®,
L@,@}oooo@,@)oooooooo}

Using Figure 4-5 as a guide, install the left ESD bracket in the correct

hole. Make sure the bracket is oriented propetly. Do not completely
tighten the mounting screws.

\*@Poooo\a\oooA

SHR-0363-87

4-8

Installing an RV20 Add-On Drive

4.3.5 Cabling
Now cable the drive power cord to the power controller and also cable
the subsystem.

If there is an RA- series disk drive in the cabinet, it has to be pushed
out to access the rear of the 874-E power controller.

Route the power cord for the RV20 to the rear of the power controller
(Figure 4-6).

Connect the cord to an available outlet on the power controller.
The subsystem cabling must be done next. The cabling depends
on the configuration of the subsystem and also on whether you are
installing an RV20-A (master drive) or an RV20-B (slave drive). Refer
to Paragraph 2.5, Cabling the RV20 Subsystem.
Figure 4-6:

Connecting to the Power Controiler
RA-

o
o

0
©

o
o

DISK DRIVE

]

¢
|l

)

‘

)

‘

)

o
o

¢}

IEA VN

/17 //-/fl' BARVRERAANNINNN [ B
Slee e o

A9.649.f3.F.0

I
°
0

’
I

@
O

J -

[T { \- 0 L T Y WA S0 W W v e {

\ POWER CONTROLLER POWER CORD

SHR-0364-87

ROUTE ALL RV20 POWER CORDS THROUGH HERE

Installing an RV20 Add-On Drive

4-9

4.3.6 Assigning a CM Number to the Drive
A CM number is now assigned to the drive.
The CM number is
independent of the TMSCP unit number. The CM number is an internal
number used by the drive and has no impact on drive operation. The
restrictions for CM numbers follow.
e

The only valid CM numbers are 0, 1, 2, and 3.

A drive must have a CM number that is unique to its subsystem
(no two drives in a subsystem can have the same CM numbers).

The following guidelines should also be followed when assigning CM
numbers.
®

e
e

A master RV20 is always CM 0.

The first RV20 slave ina subsystem (the drive that is daisy-chained

from the master) is always CM 1.

The second RV20 slave in a subsystem (the drive that is daisychained from the first slave) is always CM 2.

The third RV20 slave in a subsystem (the drive that is daisy-

chained from the second slave) is always CM 3.
To assign a CM number, select the correct switch cap from the package

of switch caps and insert the cap into the available position on the RV20
front panel (the open portion next to the Start/Stop switch.

4-10

Installing an RV20 Add-On Drive

4.3.7 Completing the Installation
1.

If you are installing an RV20-A (a master RV20), then at this point you
must install the KLESI adapter in the host. Instructions for installing
the KLESI adapter are given in Chapter 2 of this manual (Paragraphs
2.2, 2.3, and 2.4).
The drive must be assigned a unique TMSCP unit number. Instructions for assigning the TMSCP unit number are given in Paragraph
2.7,

Run tests to verify the installation.

Power up/self-test the drive (Chapter 3) to verify that the drive is
operational.

Run Level IlI tests (Chapter 3) to verify that the drive is a working
device on the system.

When the drive has been verified as operational and as a working
device on the system, the installation is complete. Make sure that
all drives in the subsystem are powered up and ready for use by the
customer (not in CE mode).
Replace the rear door of the H9643 cabinet. Do not forget to connect
the ground strap.

Installing an RV20 Add-On Drive

4-11

Index
F

A
Add-on installation, 4-1 to 4-11
Parts list, 4-3

Front panel, 2-26

H
H9643 cabinet, 1-1, 1-2,

Block diagrams

4-1, 4-2

Hex-decimal conversion, 2-30

Cabling, 2-21 to 2-25

Subsystem, 1-3
Installation

Add-on, 4-1to 4-11

Overview, 1-3, 2-1

Cabling

Add-on, 4-9

Block diagrams, 2-21 to 2-25

Subsystem, 2-20 to 2-25
CM number, 1-1, 4-10

ISI bus, 1-1

K
KLESI-B installation

VAX 8200, 2-2 to 2-7

VAX 8800, 2-8 to 2-11

Decimal-hex conversion, 2-30
Deskidding, 1-5 to 1-10
Drive subsystem controller, 1-1

KLESI-Q installation

MicroVAX, 2-12 to 2-19

Fatal error, 3-5

LEDs, 3-2

LESI

Power-up testing, 3-1

E
ESD brackets, 4-8

See KLESI
LESI bus, 1-1
Level III testing

MDM, 3-10to 3-12
VDS, 3-6to 3-10
Level 11 tests, 3-9

Index-1

M7740 module, 2-1

Unit number, 2-28

Address setting, 2-12
Installation, 2-12 to 2-19

Maintenance panel, 2-27

MDM testing, 3-10 to 3-12
MDM tests, 3-9

Parts lists

Add-on installation, 4-3
Subsystem installation, 1-10
Power controller, 4-9
Power up/self-test

Drive subsystem controller, 3-2

Subsystem, 2-26

R
Rear panel, 2-20
Related documentation, 1-11

S
Self-testing
Drive subsystem controller, 3-2

Subsystem, 2-26
Site requirements, 1-4

Subsystem

Block diagram, 1-3

Configurations, 1-1
Overview, 1-1

SYSGEN utility, 2-15
T

T1014 installation, 2-1

VAX 8200, 2-2 to 2-7
VAX 8800, 2-8 to 2-11

Test disk, 3-12
TMSCP unit number, 2-28
Tools and equipment, 1-4

Index-2

Unpacking and inspection, 1-5

V
VDS testing, 3-6 to 3-10
VDS tests, 3-9

Digital Equipment Corporation e Shrewsbury, MA

01545