Digital PDFs

EK-VSTAA-MG-001

January 2000

224 pages

Original

7.5MB

Document:	VAXstation 2000 and MicroVAX 2000 Maintenance Guide
Order Number:	EK-VSTAA-MG
Revision:	001
Pages:	224
Original Filename:

OCR Text

VAXstation2000and
MicroVAX2000

Maintenance Guide

Order No. EK-VSTAA-MG-001

digital equipment corporation
maynard, massachusetts

First Edition, January 1987

Printed in U.S.A.
The Information in this document is subject to change without notice and should not be

construed as a commitment by Digital Equipment Corporation.
Digital Equipment Corporation assumes no responsibility for any errors that may appear in
this document.

The Software, if any, described in this document is furnished under a license and may be used

or copied only in accordance with the terms of such license. No responsibility is assumed

for the use or reliability of Software or equipment that is not supplied by Digital Equipment
Corporation or its affiliated companies.

The following are trademarks of Digital Equipment Corporation.
EDCS

RSTS
RSX

COMPACTape

FMS
MASSBUS
Micro/RSTS

DEC

MicroPDP-11

UNIBUS

DECconnect

Micro/RSX

VAX

DEC/MAP

MicroVAX II

VAXeluster

DECmate

PDP

VAXstation II

DECnet

VAXstation II/GPX

DECUS

P/OS
Professional

DECwriter

Q-Bus

DIBOL

Rainbow

BASEWAY
BIBus

RT
ThinWire

VMS

/#^

Contents

Chapter 1 Systems Introduction
1.1
1.2

The VAXstation 2000 and MicroVAX 2000 Systems
Mass Storage Expansion Box for Both Systems

1.3

Options

1.3.1

1.3.2
1.4

1-1
1-5
1-8

Internat Memory Options

1-8

ThinWire Ethernet Option on MicroVAX 2000

1-8

FRU Locations

1-8

Chapter 2 Testing and Troubleshooting
2.1

Introduction

2-1

2.2

Using Console Mode

2-1

2.2.1

Determining the Console Device

2-2

2.2.2

Entering Console Mode

2-2

2.2.3

Exiting Console Mode

2-3

2.2.4

Diagnostic Console Device

2-4

2.2.5

Console Commands

2-4

2.3

2.3.1

2.3.1.1
2.3.2

Testing

Power-up Tests

Power-up Test Error Codes
Self-test

2-5

2-8
2-9

2.3.2.1

Self-test with Loopback Connectors

2-11

2.3.2.2

Self-test Error Codes

2-11

2.3.3
2.3.3.1
2.3.3.2
2.4
2.4.1

System Exerciser Diagnostics
System Exerciser Diagnostic Commands
System Exerciser Error Codes
Troubleshooting Procedures

2.4.1.2
2.4.2
2.4.2.1

2.4.3
2.4.3.1

2-15
2-16

MONO — Monochrome Video Troubleshooting
Procedures (VAXstation 2000 only)

2.4.1.1

2-13
2-14

Self-test

System Exerciser
CLK — Time-of-Year Clock Troubleshooting Procedures. . .
Self-test

NVR — Non-Volatile RAM Troubleshooting Procedures . . .
Self-test

2-16
2-16

2-16
2-17
2-17

2-17
2-17

2.4.4

DZ — Serial Line Controller Troubleshooting Procedures . .

2-17

2.4.4.1

Self-test

2-18

2.4.4.2

System Exerciser

2-18

2.4.5

MEM — Memory Troubleshooting Procedures

2-19

2.4.5.1

Self-test

2-19

2.4.5.2

System Exerciser

2-19

2.4.6

MM — Memory Management Unit Troubleshooting
Procedures

2.4.6.1
2.4.7

2.4.7.1

2-20

Self-test
FP — Floating Point Unit Troubleshooting Procedures

2-20
...

Self-test

2.4.8
2.4.8.1

IT — Interval Timer Troubleshooting Procedures
Self-test

2.4.9

HDC — Disk Drives and Controller Troubleshooting

2-21

2-21
2-21
2-21

Procedures

2-21
2-22

2.4.9.1

Self-test

2.4.9.2

System Exerciser

2.4.9.3

Troubleshooting the Hard Disk Drive Expansion Box

2.4.9.4

Drive Select Jumper Settings on Disk Drives

2.4.10

2-24

. .

PC — Tape Drive Controller Troubleshooting
Procedures

2-27
2-27

2-29

2.4.10.1

Self-test

2-29

2.4.10.2

System Exerciser

2-31

Troubleshooting the Tape Expansion Box

2-35

2.4.10.3
2.4.11

2.4.12

Self-test

2-38
2-38

NI — ThinWire Ethernet Network Option Troubleshooting

Procedures

2-39

2.4.12.1

Self-test

2-39

2.4.12.2

System Exerciser

2-39

2.4.13

Power Supply Troubleshooting Procedures

2-40

2.4.14

VR260 Monochrome Monitor Troubleshooting Procedures. .

2-42

2.4.15

Terminal Communication Troubleshooting Procedures
(MicroVAX 2000 only}

2.5
2.5.1

Utilities
Configuration Table

2-44

2-46
2-47

2.5.1.1

DZ Explanation in Configuration Table

2-48

2.5.1.3

HDC Explanation in Configuration Table

2-51

2.5.1.4

TPC Explanation in Configuration Table

2-52

2.5.1.5

NI Explanation in Configuration Table

2-53

2.5.1.6

Determining the Revision Levels in the System

2.5.1.2

SYS — Interrupt Controller and ThinWire Ethernet ID

ROM Troubleshooting Procedures
2.4.11.1

MEM Explanation in Configuration Table

Module'sROM

2-48

2-53

""^

'~m\

f0^

2.5.2

Setting NVR Default Boot Device

2.5.3

Setting NVR Default Boot Flags

2-55

2.5.4

Setting NVR Default Recovery Action Flags

2-58

2.5.5

2-55

2.5.6

Circle Cross-Hatch Alignment Pattern

Language Inquiry Menü

2-58

2.5.7

Screen of E's Pattern

2-59

2.5.8

White Screen

2-59

2.5.9

Mass Storage Disk Formatter

2-59

Disk Formatter Messages

2-63

2.5.9.1
2.5.10

2.5.10.1

2-59

Mass Storage Disk Verifier

2-64

Disk Verifier Messages

2-65

2.5.11

Special Diagnostic Key for Field Service System
Exerciser

2-66

2.5.12

ThinWire Network Loop Testing Utility

2-67

Chapter 3 FRU Removal and Replacement Procedures
3.1

Introduction

3-1

3.2

Shield Removal

3-4

3.3

System Module Assembly Removal from Shield

3-10

3.4

System Module Removal

3-13

3.5

Memory Module Removal

3-17

3.6

Network Interconnect Module Removal

3-18

3.7

RD53 Hard Disk Drive Removal from System Box

3-19

3.7.1
3.8

RD53 Disk Drive Device Electronics Board Removal ....
RX33 and RD32 Drive Removal (Half-Height Drives) from

3-21

the System Box

3-24

3.8.1
3.9

RD32 Disk Drive Device Electronics Board Removal .... 3-27
Resistor Load Board Removal from System Box
3-31

3.10

Battery Pack Removal

3-33

3.11

Power Supply Removal from the System Box

3-34

3.12

VAXstation 2000 VR260 Monochrome Monitor

3-35

3.12.1

VR260 Cover

3-36

3.12.2

VR260 Deflection Board Removal

3-39

3.12.3
3.12.4
3.12.5

VR260 Rear Bulkhead Assembly
VR260 Video Board Removal
VR260 Transformer Assembly

3-42
3-44
3-45

3.12.6

VR260 Tube/Yoke/Bezel Assembly Removal

3-47

3.12.7

VR260 LED Assembly

3-50

3.13
3.14
3.15

Keyboard Removal (VAXstation 2000 only)
Mouse and Tablet (VAXstation 2000 only)
Terminal Disconnection from MicroVAX 2000

3-51
3-52
3-53

3.15.1

3.16
3.16.1
3.17

3.17.1

DEC423 Converter Removal from MicroVAX 2000

Expansion Adapter Removal

3-56

VAXstation 2000 and MicroVAX 2000 Expansion Box

3-58

Hard Disk Drive Expansion Box Disconnection from

Box
Resistor Load Board Removal from the Hard Disk

3.17.2

Tape Drive Expansion Box Disconnection from System

Expansion Box
Box
3.17.2.1

TZK50 Controller Board Removal from the Tape Drive

3.17.2.2

TK50 Tape Drive Removal from Tape Drive Expansion

Expansion Box
Box

3.18

3-66
3-70
3-72
3-73
3-76

Power Supply Removal from the Tape Drive Expansion
Box

3.17.2.4

3-60

Power Supply Removal from the Hard Disk Expansion

3.17.1.3

3.17.2.3

.^^\
3-58

Hard Disk Drive Removal from Hard Disk Expansion
Box

3.17.1.2

3-54

Expansion Adapter Disk Interface Module Removal

System Box

3.17.1.1

3-53

Resistor Load Board Removal from the Tape Drive

3-79

Expansion Box

3-81

Recommended Spares List

3-82

^*^

Chapter 4 Video Monitor Adjustments (VAXstation 2000)
4.1

Introduction

4-1

4.2

VR260 Monochrome Monitor

4-1

4.2.1

Preparations

4-2

4.2.2

Horizontal and Vertical Linearity and Focus Adjustments . .

4-4

4.2.3

Width, Height. and Centering Adjustments

4-6

4.2.4

Rechecking the Display

4-7

4.2.5

Adjusting Minimum Raster

4-7

4.2.6

Reassembling the VR260 Monitor

4-7

Chapter 5 Option Installation
5.1

Introduction

5-1

5.2
5.3

Memory Module Installation
ThinWire Ethernet Network Interconnect Module Installation .

5-2
5-2

5.4

System Box Disk Drive Installation

5-2

5.5

Expansion Adapter Installation

5-5

5.6

Hard Disk Expansion Box Installation

5-11

5.7

Tape Drive Expansion Box Installation

5-11

^N
'

/*«sk

Appendix A Console Test Commands
Appendix B Consoie Commands
B.l

Console Command Syntax

B-l

B.2

Console Commands

B-l

B.2.1

BOOT

B-l

B.2.2

COMMENT

B-2

B.2.3

CONTINUE

B-3

B.2.4

DEPOSIT

B-3

B.2.5

EXAMINE

B-4

B.2.6

FIND

B-5

B.2.7

HALT

B-5

B.2.8

INITIALIZE

B-5

B.2.9

REPEAT

B-6

B.2.10

START

B-6

B.2.11

TEST

B-6

B.2.12

UNJAM

B-7

B.2.13

TRANSFER

B-7

B.3

Special Keys

B-8

Appendix C Console Messages and Explanations

Appendix D VMB Boot Error Status Codes
Figures
1-1

Front View of the VAXstation 2000 and MicroVAX 2000

Systems

1-2

Rear View of the VAXstation 2000 System

1-3

Rear View of the MicroVAX 2000 System

1-4

Front View of the Hard Disk Expansion Box

1-5

Front View of the Tape Drive Expansion Box

1-6

System Box with Expansion Adapter

1-7

FRU Locations in the System Box

1-8

FRU Locations in the Expansion Boxes

1-9

2-1

Example of Power-up Tests Screen Display

2-5

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

Power-up Symbols Defined
Example of Power-up Tests Screen Display with Errors
Example of the Configuration Table
Example of Running Self-test on the Disk Controller
Example of Running a Series of Self-tests
Example of a Self-test Error on the Disk Controller

2-6
2-7
2-8
2-9
2-10
2-12

vii

2-8

System Exerciser Display Example

2-15

2-9

Example of MEM System Exerciser Error Code

2-20

2-10

HDC Power-up and Self-test Error Code

2-11

Example of System Exerciser Display for the Disk Controller

2-22
.

2-24

2-12

RD32 Drive Select Jumper Setting for DUA0

2-28

2-13

RD53 Drive Select Jumper Setting for DUAO and DUA1 ....

2-28

2-14

RX33 Drive Select Jumper Setting for DUA2

2-29

2-15

TPC Power-up and Self-test Error Code

2-30

2-16

Example of System Exerciser Display for the Tape Controller .

2-32

2-17

TZK50 Controller Board Jumper Locations

2-37

2-18

Flowchart for Troubleshooting the Power Supply

2-40

2-19

Power Connectors Pin Voltages

2-41

2-20

Flowchart for Troubleshooting Terminal Communications. . . .

2-44

2-21

Flowchart for Troubleshooting Terminal Communications
on the DEC423 Converter

2-45

2-22

Example of the Configuration Table

2-47

2-23

Example of the DZ Line in the Configuration Table

2-48

2-24

Example of MEM Error Display in the Configuration Table. . .

2-49

2-25

Example of the Second HDC Line in the Configuration Table. .

2-51

2-26

Example of the Second TPC Line in the Configuration Table . .

2-52

2-27

Example of the System Module's ROM Code Revision Levels. .

2-53

2-28

Example of Tape Port Bus Information

2-54

2-29

Example of the TZK50 and TK50 ROM Revision Levels

2-30

Example of Changing the Default Boot Device

2-55

2-31

Example of Changing the Default Boot Flag

2-56

2-32

Determining the NVR Code for Three Boot Flags

2-56

2-33

Example of Changing the NVR Recovery Action Flags

2-58

2-34

Example of Formatting a Hard Disk Drive

2-60

2-35

Example of Formatting an RX33 Floppy Diskette

2-61

2-36

Example of Formatting an Unknown Hard Disk Drive

2-62

2-37

Example of Running the Disk Verifier on DUA1

2-64

2-38

Example of Creating the Special Key on a Floppy Diskette . . .

2-66

2-39

Example of Creating the Special Key on a COMPACTape

....

Cartridge

2-55

2-67

2-40

Example of ThinWire Ethernet Loop Testing Using TEST 90

3-1
3-2

FRU Locations
Expansion Adapter Cover Screw Locations

3-3
3-4

3-3

System Box Cover Screw Locations

3-5

3-4

System Box Cover Removal

3-6

3-5

Shield Screw Locations

3-7

3-6

Removing the Shield from the Main Chassis

3-8

3-7

Disconnecting the Cables from the Shield

3-9

viii

2-68

f0^

/SSW**.,

3-8

System Module Assembly Screw Locations on the Shield ....

3-10

3-9

Network Interconnect Cables

3-11

3-10

Removing System Module Assembly from Shield

3-12

3-11

Battery Cable Location

3-13

3-12

Memory Module Removal

3-14

3-13

Network ID ROM Location on System Module

3-15

3-14

VAXstation 2000 and MicroVAX 2000 System Jumper

3-16

3-15

Memory Module Removal

3-17

3-16

Network Interconnect Module Removal

3-18

3-17

Hard Disk Screw Locations

3-19

3-18

Disconnecting the Hard Disk Drive from System Box

3-20

3-19

Drive Mounting Bracket Screw Locations

3-21

3-20

RD53 Device Electronics Board Removal

3-22

3-21

RD53 Device Electronics Board Jumper and Switch Locations .

3-23

3-22

Half-Height Drive(s) Screw Locations

3-24

3-23

Disconnecting the RX33 and RD32 Half-Height Drives

3-25

3-24

Half-Height Drives Mounting Brackets Removal

3-26

3-25

RD32 Device Electronics Board Screw Locations

3-27

3-26

Disconnecting J4 from RD32 Device Electronics Board

3-28

3-27

Disconnecting J5 and J6 from RD32 Device Electronics Board .

3-29

3-28

RD32 Device Electronics Board Jumper Location

3-30

Battery Cable Location

3-33

3-31

Power Supply Screw Locations in the System Box

3-34

3-32

VR260 FRU Locations

3-35

3-33

VR260 Controls and Video Cable Locations

3-36

3-34

VR260 Cover Screw Locations

3-37

3-35

VR260 Rear Bezel Location

3-38

3-36

VR260 Side Door Screw Locations

3-39

3-37

High-Voltage Discharge Tool

3-40

3-38

VR260 Deflection Board

3-41

3-39

VR260 Rear Bulkhead Screw Locations

3-42

3-40

VR260 Rear Bulkhead

3-43

3-41

VR260 Video Board

3-45

3-42

VR260 Transformer Assembly

3-46

3-43

VR260 Tube/Yoke/Bezel Assembly Screw Locations

3-47

3-44

VR260 Tube/Yoke/Bezel Assembly's LED Cable

3-48

3-45

3-46

VR260 Cable Connections

VR260 LED/Bezel Assembly

3-49

3-47

Disconnecting the Keyboard (VAXstation 20001

3-51

3-48
3-49
3-50

Disconnecting the Mouse or Tablet (VAXstation 2000»
DEC423 Converter's Mounting Screw Locations
Expansion Adapter Screws

3-52
3-53
3-54

3-29

Drive Mounting Bracket Screw Locations

3-32

3-50

3-51

Expansion Cables Locations

3-55

3-52

Expansion Adapter Cover Screws Location

3-56

3-53

Expansion Adapter Disk Interface Module Cables and Screw

Locations

3-57

3-54

Hard Disk Expansion Box Cable

3-59

3-55

Hard Disk Expansion Box Cover Screw Locations

3-60

3-56

Resistor Load Board Power Cable

3-61

3-57

Hard Disk Expansion Box Shield Screw Locations

3-62

3-58

Hard Disk Expansion Box Drive Mounting Screws

3-63

3-59

Hard Disk Expansion Box Drive Cables Locations

3-64

3-60

Hard Disk Expansion Box Drive Mounting Bracket Screws
Location

3-65

3-61

Hard Disk Expansion Box Cover Screw Locations

3-66

3-62

Hard Disk Expansion Box Resistor Load Board Power Cable . .

3-67

3-63

Hard Disk Expansion Box Shield Screw Locations

3-68

3-64

Hard Disk Expansion Box Power Supply Mounting Screw

Locations

3-69

3-65

Hard Disk Expansion Box Cover Screw Location

3-70

3-66

Hard Disk Expansion Box Resistor Load Board Power Cable . .

3-71

3-67

Tape Drive Expansion Box Data Cable

3-72

3-68

Tape Drive Expansion Box Cover Screw Locations

3-73

3-70

TZK50 Controller Board Jumper and Resistor Pack Locations .

3-75

3-71

Tape Drive Expansion Box Shield Screw Locations

3-76

3-72

Tape Drive Expansion Box Drive Mounting Screw

3-77

3-73

TK50 Tape Drive Cable Locations

3-78

3-74

Tape Drive Mounting Brackets Screw Locations

3-79

3-75

Tape Drive Expansion Box Power Supply Mounting Screw

3-76

Tape Drive Expansion Box Resistor Load Board Power

3-69

TZK50 Controller Board Cable Locations

Locations

3-74

Cable Locations

3-81

Brightness and Contrast Controls

4-3

4-2

VR260 Internal Adjustment Locations

4-4

4-3
4-4

Circle Cross-Hatch Display
Width and Height Measurements

4-5
4-6

5-1

Drive Mounting Brackets Screw Locations

5-3

5-2

Resistor Load Board Location

5-4

5-3

Drive Mounting Positions

5-5

Cover Plate Location

5-7

Drive Screw Location

3-80

4-1

5-4

"*%

5-6

^^\

5-6

Installing Expansion Adapter

5-8

5-7

Connecting RD Extension Cable to Disk Interface Module . . .

5-9

5-8

Connecting Read/Write Cable to Disk Interface Module

5-10

D-l

VMB Error Displays

D-l

Tables
2-1

Prompts

2-2

Keyboard LEDs Defined

2-7

2-3

Self-test Commands

2-10

2-4

System Exerciser Diagnostic Commands

2-14

2-5

MEM System Exerciser Error Codes

2-20

2-6

Power-up and Self-test Error Codes for each Disk Drive

2-23

2-7

HDC Disk Controller System Exerciser Error Codes

2-25

2-8

HDC Disk Drive System Exerciser Error Codes

2-26

2-9

TPC Tape Controller System Exerciser Error Codes

2-33

2-10

Tape Drive Expansion Box System Exerciser Error Codes . . .

2-34

2-11

VR260 troubleshooting Table

2-42

2-12

Utilities

2-46

2-13

Determining the Location of the Failing Memory Bank

2-50

2-14

Boot Flags Used by VMB for Booting All Operating
System Software

2-56

2-15

Specific Boot Flags Used by VMS

2-57

2-16

Default Recovery Flags

2-58

2-17

Disk Formatter Messages

2-63

2-18

Error Codes for the Disk Formatter

2-64

2-19

Disk Verifier Messages

2-65

2-20

Error Codes for the Disk Verifier

2-65
2-69

2-21

ThinWire Ethernet Loopback Test Report Definitions

3-1

FRU Section Listings

3-1

4-1

Base Video Alignment Test Commands

4-1

5-1

Options Installation Section Listings

5-1

A-l

Test Commands

A-l

B-l

Special Keys Used in Console Program Mode

B-8

C-l
D-l

Console Error Messages
VMB Boot Error Status Codes

C-l
D-2

ABOUT THIS BOOK
This book describes how to troubleshoot, adjust, and repair the VAXstation
2000 and the MicroVAX 2000 Workstation to the field replaceable unit (FRU)
level in the field. It Covers all FRU options presently available for these two
Systems.

•

Chapter 1 contains a System overview that outlines the components of
the VAXstation 2000 and MicroVAX 2000 Systems.

•

Chapter 2 contains testing and troubleshooting procedures to help isolate the problem to an FRU.

•

Chapter 3 contains FRU removal and replacement procedures.

•

Chapter 4 contains video monitor adjustment procedures for the VAX
station 2000 monitor.

•

Chapter 5 contains installation instructions for each Option available on
both the VAXstation 2000 and the MicroVAX 2000.

•

Appendix A contains a list of the test commands.

•

Appendix B contains a complete listing and definitions of the console
commands.

•

Appendix C contains a complete listing and definitions of the console
messages.

•

Appendix D contains a complete listing and definitions of the VMB boot
error Status codes.

The detailed index and glossary also help you find Information.
Notes, Cautions, and Warnings

Notes, cautions, and warnings appear throughout this book.

•

Notes contain general, supplemental Information about a topic.

•

Cautions contain information to prevent damage to equipment.

•

Warnings contain information to prevent personal injury.

xiii

REFERENCE MANUALS
Manual

Order Number

VAXstation 2000 Hardware Installation Guide

EK-VAXAA-IN

VAXstation 2000 Owner's Manual

EK-VAXAA-OM

VAXstation 2000/MicroVAX 2000 Technical Manual

EK-VTTAA-TM

MicroVAX 2000 Hardware Installation Guide

EK-MVXAA-IN

MicroVAX 2000 Owner's Manual

EK-MVXAA-OM

VR290 Service Guide

EK-VR290-SM

VAXstation 2000, MicroVAX 2000, VAXmate Network Guide

EK-NETAA-UG

RD53 Technical Description Manual

EK-RD53A-TD

RX33 Technical Description Manual

EK-RX33T-TM

TZK50/SCSI Controller Technical Manual

EK-TZK50-TM

TOOLS AND MATERIALS
You will need the following tools and materials to service the VAXstation
2000 and MicroVAX 2000 Systems.

•

Field Service Tool Kits

50 Hz Tool Kit p/n 29-23270-00
60 Hz Tool Kit p/n 29-23268-00
•

VR260 Video Monitor Tools
Metric Measuring Tape p/n 29-25342-00
High-Voltage Anode Discharge Tool p/n 29-24717-00

•

ThinWire Ethernet Tools
Face Plate Installation Kit p/n H8242

**^JSV

xiv

Chapter

Systems Introduction
1-1 The VAXstation 2000 and MicroVAX 2000
Systems

The VAXstation 2000 and MicroVAX 2000 Systems are mechanically
identical. Both come in the same style box, both use the same drives,
and both use the same mass storage expansion boxes. Also, both use
the same diagnostic tools for troubleshooting and repair. Once familiär
-with troubleshooting one System, you'll be able to troubleshoot the other
if necessary. One major difference is the VAXstation 2000 is a single-user
System and the MicroVAX 2000 is a multiuser System. Another difference
is the VAXstation 2000 uses a video monitor while the MicroVAX 2000 uses
video terminals.

(

Both the VAXstation 2000 and the MicroVAX 2000 have three main pieces

of hardware. They are the System box, the hard disk expansion box, and

the tape drive expansion box. The System box can have a half-height RX33

floppy disk drive, a half-height RD32 hard disk drive, or both the RX33 and
the RD32. A full-height RD53 hard disk drive can be substituted for the halfheight drives in the System box. The hard disk expansion box comes with a

full-height RD53 hard disk drive. The tape drive expansion box comes with

a TK50 tape drive.

1-1

Figure 1-1 shows the front of the VAXstation 2000 and MicroVAX 2000

Systems. There are three ways to differentiate between the two Systems:
the medallion next to the power switch on the front, the DEC423 Converter
on the back, or the System jumper position on the System module inside
the box.
^

Figure 1-1:

Front View of the VAXstation 2000 and MicroVAX 2000
Systems

MB-I286-MO5
M* 0063 87

1-2

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Figure 1-2 shows the rear view of the VAXstation 2000 and labeis each
connector. A modern or a terminal can be connected to the 25-pin communication port. A VR260 monochrome monitor can be connected to the
15-pin video port. A printer can be connected to the 9-pin printer port. The

ThinWire Ethernet port Supports IEEE 802.3 (Standard Ethernet) network
communications connections over the ThinWire Ethernet cable.

Figure 1-2:

Rear View of the VAXstation 2000 System

25-PIN COMMUNICATION PORT
15-PIN VIDEO PORT
9-PIN PRINTER PORT
HALT BUTTON

ThinWire Ethernet

POWER CORD

Mfi-1086-1246
MAO 132 67

Systems Introduction

1-3

Figure 1-3 shows the rear view of the MicroVAX 2000 and labeis each connector. Like the VAXstation 2000, the MicroVAX 2000 supports a modern
or a terminal on the 25-pin communication port. The MicroVAX 2000 sup
ports the DECconnect strategy which uses the modified modular jack (MMJ)
6-conductor telephone type cable (DEC423 asynchronous protocol) for connection to the terminals. The DEC423 Converter changes the 15-pin video

port and the 9-pin printer port (RS232 protocol) to three MMJ communi
cation ports. Port 1 on the DEC423 Converter is reserved for the console
terminal. Ports 2 and 3 can have either a terminal or a printer attached to
them. The operating System Software configures each port for either a termi
nal or a printer. The ThinWire Ethernet port supports IEEE 802.3 (Standard
Ethernet) network communications connections over the ThinWire Ethernet
cable.

Figure 1-3:

Rear View of the MicroVAX 2000 System

25-PIN COMMUNICATION PORT

DEC 423 CONVERTER
HALT BUTTON

ThinWire Ethernet

POWER CORD

MR.1086-124S

MAO134-B7

1-4

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

1.2 Mass Storage Expansion Box for Both
Systems

.p^
r

Additional mass storage devices are contained in expansion boxes that look
very similar to the System box. Figures 1-4 and 1-5 show the front view of
the expansion boxes.

The hard disk expansion box contains an RD53 or RD54 hard disk drive.
The tape drive expansion box contains a TK50 tape drive and a Controller
board. Each expansion box contains a power supply, a resistor load board
(to regulate the power supply), and the drive.

Figure 1-4:

Front View of the Hard Disk Expansion Box

RD53

MR13S6.14O6

ma-oms-87

Systems Introduction

1-5

Figure 1-5:

Front View of the Tape Drive Expansion Box

TK5O

MR-UBB-MIO
WA 0064 8 ;

1-6

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Both expansion boxes connect to the System box through an expansion
adapter that attaches to the bottom of the System box. The expansion
adapter has three connectors on the back labeled ports A, B, and C. Port
A connects the tape expansion box to the System. Port B connects the hard
disk expansion box to the System. Port C is reserved for future options. Figure 1-6 shows the back of a MicroVAX 2000 System box with an expansion
adapter.

Figure 1-6:

System Box with Expansion Adapter

SYSTEM BOX

EXPANSION
ADAPTER

PORTA
TAPE DRIVE
EXPANSION PORT

PORTB
HARD DISK
EXPANSION PORT
MII-1286-1409
MA 0135 87

Systems Introduction

1-7

1.3 Options
1.3.1 Internal Memory Options
Two additional memory modules are available for both Systems. One is a 2-

megabyte memory module and the other is a 4-megabyte memory module.
The memory module is located in the System box and is connected directly
to the System module.

1.3.2 ThinWire Ethernet Option on MicroVAX 2000
ThinWire Ethernet is an option on the MicroVAX 2000. It comes Standard
on the VAXstation 2000. It adds the capability of connecting the System to
the DECnet through the ThinWire Ethernet network. The option consists
of a network interconnect module that is located in the System box and is
connected to the System module through two 40-conductor cables.

1.4 FRU Locations
Figure 1-7 shows the locations of the FRUs in the System box. Figure 1-8
shows the locations of the FRUs in the expansion boxes.
Figure 1-7:

FRU Locations in the System Box

1
SYSTEM MODULE
MEMORY MODULE

RX33

ThinWire Ethernet MODULE

OR RD53
POWER SUPPLY

RD32

DISK INTERFACE MODULE

EXPANSION ADAPTER

VAXstation 2000 AND MicroVAX 2000 SYSTEM BOX
MA O15OB7

1-8

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Figure 1-8:

FRU Locations in the Expansion Boxes

POWER
SUPPLY

TK5O

RD53

POWER
SUPPLY

VAXstation 2000 AND MicroVAX 2000 EXPANSION BOXES
MHM86-127B
MAOI33B7

Systems Introduction

1-9

Chapter 2

Testing and Troubleshooting
2.1 Introduction
This chapter describes how to test and troubleshoot the VAXstation 2000
and the MicroVAX 2000 Systems. Differences between the VAXstation 2000
and the MicroVAX 2000 are specifically identified in the text.
This chapter contains the following sections.

•

How to use console mode: determining the console device, enter
ing console mode, exiting console mode, utilizing the diagnostic
console device, and where to find a list of the console commands.

•

How to run the diagnostic tests and interpret the error codes for
each test: power-up tests, self-test, and System exerciser.

•

How to troubleshoot all devices in the System.

•

How to use the Utilities.

2.2 Using Console Mode
The VAXstation 2000 and the MicroVAX 2000 Systems have two modes
of Operation: program mode and console mode. Normal Operation of the
VAXstation 2000 and the MicroVAX 2000 is in program mode, that is, with
the operating System Controlling the System. Console mode allows the user
to control the System from the console terminal using the console com
mands described in Appendix B. Console mode is contained in ROM on
the System module.

Testing is done while in console mode. The System returns the >>>
prompt when it is in console mode. Table 2-1 lists the prompts and the
mode of Operation each prompt represents.

f
2-1

Table2-1:

Prompts

Prompt

Mode of Operation

>> >

Console mode. Console commands are listed in Appendix B.

Program mode (VMS operating system)

Program mode (Ultrix operating aystem)

2.2.1 Determining the Console Device
The console device for a VAXstation 2000 System is the keyboard (LK201)
and monitor (VR260) connected to the video port. The keyboard inputs
commands at 4800 baud and the monitor displays Output from the video
circuits.

The console device for a MicroVAX 2000 System is the terminal (VT220 or
similar terminal) connected to connector 1 on the DEC423 Converter. The
terminal operates at 9600 baud.

2.2.2 Entering Console Mode
Console mode is entered any time the CPU halts. The CPU can be halted
automatically or manually. A halt means that CPU control has passed control from the operating System to the console mode program in ROM. If
the System halts the CPU, then the console mode program checks the nonvolatile RAM (NVR) for user-defined instructions on how to handle the halt.
If you manually halt the CPU, the System enters console mode program immediately without checking the NVR for instructions.

■*b®k

You can manually halt the CPU and enter console mode by one of the
following methods.
•

HALT button—Press the halt button. It is located next to the printer port
on the back of the System box. The > > > prompt is displayed when
ready for console commands.

•

BREAK key—Press the BREAK key on the diagnostic console device

that is connected to the printer port with the BCC08 cable. The > > >
prompt is displayed when ready for console commands.

The system automatically halts the CPU for the following reasons.
•

After power-up testing—If the default recovery action is halt, the system
automatically halts the CPU and enters console mode after power-up

tests are complete. See Section 2.5.4 for information on setting the
default recovery actions.

2-2

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

-**\

)

•

(

For a boot failure—If the System fails to boot properly, the System au-

tomatically halts the CPU and enters console möde. See Section 2.5.2
for Information on setting the default boot device.

On a System error—If the CPU detects a severe corruption of its oper-

ating environment, it halts and reads the default recovery action in the

NVR. The default recovery action can be restart, boot, or halt. When

it is restart and the restart fails, then the System automatically tries to
boot the operating System Software. If the boot fails, the CPU halts and
enters console mode. When the default recovery action is boot and the

boot fails, the CPU halts and enters console mode. When the default re

covery action is halt, the CPU unconditionally halts and enters console

mode.

One other way to halt the CPU is when the operating System Software exe-

cutes a halt instruction. The CPU then reads the default recovery action in
the NVR and acts on it as described above.

2.2.3 Exiting Console Mode
Console mode is exited by typing one of the following console commands.

•
^^

BOOT—This command initializes the CPU and boots the operating system Software from the device specified. If no device is specified, the
System searches each on-line device until the operating System Software

|s found. The boot command Starts the System similar to when power

is turned on except that the power-up tests are not run. If the System
attempts to boot over the net (ESAO) and no Software is available on
another node, the System keeps looking for the Software indefinitely.

If a boot message for the operating System Software does not appear
shortly after the Ethernet boot message (ESAO) is displayed, then you

must press the halt button to abort the Ethernet boot. If you still need
to boot over the Ethernet, make sure the node with the operating system Software is operating normally and the Software is loaded. Run the
Ethernet loopback Utility (TEST 90) to check the networking capability
of the System if the Ethernet boot continues to fail.

When a boot is invoked using this boot command, you can specify
several boot command flags by bit encoding the flags in a flag word
specified with the /R5: qualifier. These command flags are listed in

Paragraph 2.5.3.

Testing and Troubleshooting

2-3

•

CONTINUE—This command instructs the CPU to continue the operating System Software at the address contained in the program counter
(PC). This command Starts up the operating Software where it was halted
provided no console test commands were run. Running a test command
alters the PC and memory so that the operating System Software cannot
be started properly by entering the continue command. If a test command was entered, use the boot command to Start the operating System

Software. The continue command is similar to the Start command. The
start command can specify the address to Start the operating Software
and the continue command has the operating Software continue where
it left off.

•

START—This command Starts the operating System Software at a specified address. If no address is given, the contents of the PC are used.
However, running a test command alters the PC and memory so that the
operating System Software cannot be started properly by entering the
start command. If a test command was entered, use the boot command
to start the operating System Software.

2.2.4 Diagnostic Console Device
There is a diagnostic console device available on the VAXstation 2000. The
MicroVAX 2000 can use this device if the DEC423 Converter is removed.
The diagnostic console device can be utilized by connecting a terminal (such
as the VT100 or VT220) to the printer port with the Special BCC08 cable.

The terminal operates at 9600 baud. Field Service technicians can use this
terminal as a diagnostic tool to isolate a problem in the normal console
device.
To use this diagnostic console device you must turn off power, connect the
BCC08 cable to the printer port and terminal, and then turn power back on.
The diagnostic console device now controls the System. The normal console
monitor displays video test patterns on the VAXstation 2000 when the video
circuits are tested. The normal console keyboard does not operate.

2.2.5 Console Commands
Console commands are listed in Appendix B.

2-4

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

^m^.

2.3 Testing
Testing procedures on the VAXstation 2000 and the MicroVAX 2000 Systems
are almost identical. The differences between the Systems are explained
where applicable. All diagnostic tests are ROM-based and testine is done
while in console mode. Tests are executed in either of two ways:

•

Automatically—When power is turned on the power-up tests begin.

•

Manually—By entering one of the console test commands on the con

sole terminal. See Appendix A for a complete listing of the test com

mands.

2.3.1 Power-up Tests
Power-up tests run each time the System power is turned on. Power-up
testing consists of a sequence of tests executed for each device installed in

the System. The test number of each device is listed on the power-up screen
display as the device is tested. Figure 2-1 shows an example of the powerup screen display. The first line indicates the CPU name (KA410-A) and the

ROM version (VI.0). The test numbers are listed next in descending order
from the first test, F, to the final test, 1. TEST F will have an underscore

after it on the MicroVAX 2000 to indicate that TEST F was not run. Note in
Figure 2-1 that tests 4, 3, 2, and 1 have an underscore (_) immediately after
them. This underscore indicates that there is no Option device installed for
that test; thus, no tests are done. TEST F has an underscore after it on the
MicroVAX 2000 Systems because the monochrome video circuits are not
used by the MicroVAX 2000. No other test numbers can have underscores
after them. An asterisk (*) after TESTS 4 through 1 indicate that an Option is
installed, but its ROM is destroyed and the Option device must be replaced.

Only TESTS 1 through 4 can have an asterisk after them. Figure 2-2 lists

the symbols that can appear in between the tests and what they indicate.
Figure 2-1:

Example of Power-up Tests Screen Display

KA410-A VI.0

F...E...D...C...B...A. ..9...8...7...6...5...4_..3_..2_..i_..
Figure 2-2 lists the definitions of the symbols that appear between the test

numbers in the power-up test Countdown.

Testing and Troubleshooting

2-5

Figure 2-2:

Power-up Symbols Defined

Device tested successfully or has a soft error
?..

Device has a hard error

Device not installed or not tested

*..

Device installed but its ROM is destroyed

If any hard errors (errors that indicate the device must be replaced for
proper Operation) are found during power-up testing, a question mark is
placed after the failing test number during the Countdown sequence. An
error summary of all errors detected is listed after the power-up sequence
is complete. Two question marks in the error summary indicate a hard error.
Error codes that indicate the Status or soft errors do not put a question mark
after the failing test number in the sequence, but do list the error code in the
error summary. Figure 2-3 shows the power-up screen display with a hard
error found in TEST F and a soft error found in TEST E. The error summary
for each failed device is displayed before the boot sequence is started.
However, the screen usually scrolls so fast when the System Starts to boot
that you may not be able to see what the error summary contained (if there
was an error summary). To see what errors the power-up tests found, press
the halt button and enter TEST 50 on the console terminal. TEST 50 is the
command for bringing up the configuration table. The configuration table
is created during power-up testing. This configuration table contains all of
the error codes listed in the power-up error summary as well as error codes
for all devices installed in the System. The error codes in the configuration
table are updated every time self-test is run. See Paragraph 2.5.1 for an
explanation of how to use the configuration table.
Each error summary consists of one or two question marks, a test number,
the ID number of the failed device, and an eight-digit error code. For example, in Figure 2-3, the first line of the error summary shows a hard error
for TEST F, a device ID number of 00B0, and an error code of 0001.F002.
The second line shows a soft error for TEST E, a device ID of 0040, and an
error code of 0000.0005. Section ( 2.3.1.1) describes the error codes.

2-6

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Figure 2-3:

Example of Power-up Tests Screen Display with Errors.

KA410-A VI.0
/S§BB\

F7..E...0...C...B...A...9...8...7...6...5...4_..3_..2_..1_..

7? F
? E

00B0 0001.F002
0040

0000.0006

If there is a fatal error in the NVR during power-up testing, the System stops

testing the other devices and displays ?14 TOY ERR on the screen. When
this happens, the only way to determine the cause of the problem is by
viewing the LEDs on the keyboard. One of the LEDs will be lit to indicate
the failing module. Table 2-2 lists the LEDs and which module has failed.

Table 2-2:

Keyboard LEDs Deflned

Keyboard LED

Failing module

Hold Screen

System module

Lock

Not used

Compose

ThinWire Ethernet Option module

Wait

Not used

Once power-up testing is complete and no fatal or hard errors are found, the
System boots the operating System Software. Both the VAXstation 2000 and
the MicroVAX 2000 boot the operating System Software the same. The only
difference between the two is that the VAXstation 2000 clears the console
screen before it boots and the MicroVAX 2000 does not. If a default boot
device is loaded in the NVR, the System boots off of that device. If no
default device is loaded in the NVR, the System searches every on-line
storage drive for the operating Software. DUA2 is searched first if a floppy
diskette is loaded. Otherwise, it is not searched at all. The hard disks are
searched next, DUAO then DUAl. MUAO, the tape drive, is checked after
the hard disk drives if it is installed and a cartridge is loaded. Finally, the
System searches the Ethernet network for the Software and ESAO is listed
on the screen. The System continues to search the Ethernet network until
the operating System Software is found.

Testing and Troubleshooting

2-7

2.3.1.1 Power-up Test Error Codes

The power-up test error codes indicate Status and/or error information. Any
errors found by power-up tests are listed in the error summary after the

power-up test Countdown sequence. This summary, if any, gives you a brief
summary of the errors. Table 2-3 lists the test numbers and the devices that
are tested during that particular test. To look at the complete list of devices
and the Status of that device, you must display the configuration table. The
configuration table lists every device in the System and also lists the results

/emSl

of the self-test and power-up tests and is updated each time self-test is run.

The error codes for each device in the configuration table are explained in
the troubleshooting section for that individual device. Remember that the
configuration table contains the results of the self-test and power-up tests
and not the results of the System exerciser. Figure 2-4 shows an example
of the configuration table and for an explanation of the configuration table,
see Paragraph 2.5.1.

Figure 2-4:

Example of the Configuration Table

>» TEST 50

KA410-A VI.0
ID 08-00-2B-02-CF-A4
?? MONO

0001.F002

? CLK

0000.0005

NVR

0000.0001

00000001 00000001 00000001 00000001 00000001 000012AO
MEM

0002.0001
00200000

0000.0001

HDC

1710.0001
000146B8 00000000 00000320

TPC

0202.0001

FFFFFF03 01000001 FFFFFF06 FFFFFF05 FFFFFF05 FFFFFF05 ...

2-8

SYS

0000.0001

0000.0001 VI.0

VAXstation 2000 and MicroVAX 2000 Malntenance Guide

^"^
\

jgm^

(

The most common good error code is 0000.0001. There are, however, some
devices that use the first four digits in the error code to indicate the Status

of the device and the last four digits to indicate the error found on the
device. The memory (MEM) error code, for instance, contains 0002.0001
which indicates two megabytes of memory is available (0002.) and no error
found (.0001). On devices like these, the last four digits always indicate

.0001 as a good (non-error) indication.

Some error codes indicate no error at all and give a Status of the device
such as the clock (CLK) which shows that the date and time has not been

set. This is not an error, just a Status of the clock circuits.

Any error code other than 0000.0001 on the MONO, MM, FP, IT, or SYS
devices indicates a hard error and that device must be replaced for proper
Operation of the System. The other devices such as CLK, NVR, DZ, MEM,
HDC, TPC, and NI may have a Status or a soft error message in the error
codes and may still operate normally.
See the troubleshooting procedures section (Paragraph 2.4) for each device
to determine whether or not the error code indicates a fault or a Status for
the device.

2.3.2 Self-test

/""^

Self-test allows you to test every device again individually, a few at a time,

or all of them sequentially just like power-up tests. To individually test a

device, enter TEST # where # is the test number of the device you want
tested. Table 2-3 lists the test numbers and the devices tested by those
numbers. Figure 2-5 shows an example of running self-test successfully on
the disk Controller.

Figure 2-5:

Example of Running Self-test on the Disk Controller

»> TEST 7
7...

Testlng and Troubleshooting

2-9

To test a group of devices, enter TEST followed by the test number of the

first device to be tested and then the test number of the last device to be

tested. Figure 2-6 shows an example of testing a group of devices. In Figure
2-6, all tests between C and 4 are tested successrully. Note that you cannot
pick and choose which devices to test between C and 4, all tests between
C and 4 are tested when entered as a group.

Figure 2-6:

Example of Running a Series of Self-tests

>» TEST C 4

C...B...A...9...8,

To test all devices, enter TEST F 1. The MicroVAX 2000 skips over the
MONO video test (TEST F) since it does not use the video circuits.

Table 2-3:
Test
Number

Self-test Commands

Device
Tested

Option module (Network lnterconnect module) (NI)

Option module (not available)

Interrupt Controller and ThinWire Ethernet ID ROM (SYS)

Tape Controller. (TPC)

Disk conroller. (HDC)

Interval timer. (IT)

Floating point unit. (FP)

Memory management unit. (MM)

Memory. (MEM)

DZ Controller. (DZ)

Non-volatile RAM. (NVR)

2-10

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Table 2-3 (Cont.):
Test

Number

Self-test Commands

Device

Tested

Time-of-year dock. (CLK)

Base video (MONO) (VAXstation 2000 only)

2.3.2.1 Self-test with Loopback Connectors

Customer mode self-test does not test the drivers or the lines of the serial
line conroller (DZ) since loopbacks are not used. Run self-test in field service mode to test the DZ drivers by installing the loopback connectors on
the back of the System. Follow one of the procedures below.
To test the DZ on VAXstation 2000, install a loopback (p/n 29-24795) on
the 25-pin communication port and a loopback (p/n 29-24794) on the 9-pin
printer port. Run TEST C. You cannot use loopback connectors if you are

using the diagnostic console device with the BCC08 cable on the printer
port since there is no loopback connector for the video port.

To test the DZ on MicroVAX 2000, install a loopback (p/n 29-24795) on the
25-pin communication port and install an MMJ loopback on both ports 2
and 3. Run TEST C.

NOTE: The ThinWire Ethernet port on the back of the System box must be terminated properly when running diagnostics on the network Option WEST 1) othetwise

an error code of 0000.7001 or greater is listed in the cotifiguration table.
2.3.2.2 Self-test Error Codes

Figure 2-7 shows how an error is displayed if found during self-test. This
example shows an error on the disk Controller during self-test. The 84 FAIL
indicates an error was found on the device tested. You must display the
configuration table (TEST 50) after self-test is complete to see the error code,

if there is an error during self-test, since the error codes do not appear on
the screen. The configuration table lists every device in the System, fists the
results of the self-test and power-up tests, and is updated each time self-test

is run. The error codes for each device in the configuration table are explained in the troubleshooting section for that individual device. Remember
that the configuration table contains the results of the self-test and power-up

tests and not the results of the System exerciser. See Paragraph 2 5 1 for an
explanation of the configuration table.

Testing and Troubleshooting

2-11

Figure 2-7:

Example of a SelMest Error on the Disk Controller

>» TEST 7
7?. .
84 FAIL

(You must display the configuration table to see the error code)

2-12

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

2.3.3 System Exerciser Diagnostics
The System exerciser simulates a worst-case Situation test for each device
and checks how the device operates under these conditions. It does not use
the configuration table to list its results of the tests. The System exerciser
has a separate display that appears on the screen as the exerciser is running.
Any errors found are displayed in the exerciser display. When. examining
the exerciser display, a Single question mark in the far left column indicates
a soft error, a double question mark indicates a hard error, and the absence
of question marks indicate success. Figure 2-8 shows an example of the
exerciser display.

The System exerciser exercises most of the devices. However, some devices
such as the memory management unit (MM) and the interval timer (IT) are
tested through the testing of other devices and are not displayed. Of the
devices the exerciser does exercise, it runs each one sequentially until all
have been run once, then it runs them all at the same time (worst-case).
This type of testing usually finds any intermittent failures.
The System exerciser has two modes: customer mode and field Service
mode. Customer mode System exerciser (TEST 0) does not use loopback
connectors and does not fully test all of the devices. Field Service mode system exerciser requires loopback connectors installed and removable media

from the maintenance kit inserted and loaded. You must initialize the floppy
diskette in the maintenance kit with a Special diagnostic key so the exerciser
can perform write tests on the RX33. Refer to Paragraph 2.5.11 for more
Information on creating the Special diagnostic keys. Once the floppy has
been initialized, load it into the RX33 (if a füll read/write test of the RX33 is
necessary) before you run the System exerciser in field Service mode. You
must also initialize the COMPACTape cartridge in the maintenance kit with
a Special diagnostic key so the exerciser can perform read/write tests on
the TK50. Refer to Paragraph 2.5.11 for more information on creating the
Special diagnostic keys. Once the COMPACTape cartridge has been initial
ized, load it into the TK50 (if a füll read/write test of the TK50 is necessary)
before you run the System exerciser in field service mode. If the RX33 or

the TK50 are not loaded with the special-key media, the System exerciser
does not do destructive writes to them and tests them the same as it does
during the customer mode System exerciser. This special-key on the media
prevents the exerciser from accidentally destroying data on the customers

floppy diskette or COMPACTape cartridge. The field service mode System
exerciser is available in a run once (TEST 101) and a run forever (TEST 102)
configuration.

Testing and Troubleshooting

2-13

2.3.3.1 System Exerciser Diagnostic Commands

Table 2-4 lists the System exerciser diagnostic commands.

Table 2-4:
Test
Commands
0

System Exerciser Diagnostic Commands

Description of Commands
Runs customer mode System exerciser. It exercises each device once sequen-

tially, then exercises them simultaneously, and stops when the slowest device
finishes its second pass. No loopback connectors and no removable media required.

101

Runs field Service System exerciser. It exercises each device once sequentially,
then exercises them simultaneously, and stops when the slowest device finishes
its second pass. Do not stop the exerciser before it finishes exercising every
device twice (second pass). Loopbacks and removable media required.

102

Runs field Service System exerciser. It exercises each device once sequentially

and then exexcises them simultaneously until you enter a |CTRL/C|. Note that

the exerciser takes up to thirty seconds to stop after you enter |CTRL/Cl. Do

not stop the exerciser until every device is exercised twice (second pass). Also,
do not press the halt button to stop the exerciser. Loopbacks and removable
media required.

When the exerciser is started, PRAO is displayed and the monitor connected
to the video port on the VAXstation 2000 blinks white and black several
times while the monochrome circuits are being tested. The results of the
MONO tests are then displayed on the console screen. MicroVAX 2000
does not use the MONO circuits and, therefore, does not test them. The
DZ test results are the first to be displayed on the console screen. The rest
of the devices are then exercised one at a Urne and the results are listed
on the display. The console displays the results of each device until the
last device is finished testing. When the last device is done, the exerciser

Starts running all devices together at the same time. When this happens, the
monitor connected to the video port Starts blinking again until the slowest
device finishes testing. On the MicroVAX 2000, the console terminal holds
the first pass display until the slowest device is done testing then displays a
new exerciser display. The console screen (VAXstation 2000 and MicroVAX
2000) displays the results of each device tested. This display stays on the
screen for about 10 seconds, then the exerciser Starts running all devices
together again if TEST 102 was entered. If TEST 0 or TEST 101 was entered,
the exerciser stops after the slowest device is done testing. The halt message
is displayed when the exerciser is stopped.
To run the field Service mode System exerciser on VAXstation 2000, install a
loopback (p/n 29-24795) on the 25-pin communication port and a loopback
(p/n 29-24794) on the 9-pin printer port. Insert and load the floppy diskette

2-14

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

and TK50 COMPACTape cartridge from the maintenance kit if the System
has these devices installed. Run the exerciser by entering TEST 101 or TEST
102. If you are using the diagnostic console device, you will get errors on
the DZ line since there is no loopback for the video port.
To run the field Service mode System exerciser on MicroVAX 2000, install
a loopback (p/n 29-24795) on the 25-pin communication port and install an
MMJ loopback on both ports 2 and 3. Insert and load the scratch floppy
diskette and scratch TK50 COMPACTape cartridge from the maintenance
kit if the System has these devices installed. Run the exerciser by enter
ing TEST 101 or TEST 102. If the scratch floppy or TK50 cartridge is not
installed, the System tests those devices the same as in customer mode.

2.3.3.2 System Exerciser Error Codes
Figure 2-8 shows an example of the System exerciser display while running
the System exerciser in field Service mode. Customer mode gives the same
display, but with a CU in place of the FS on the top of the display.
Figure 2-8:

System Exerciser Display Example

KA410-A V1.0

00B0

MONO

0000.0001

0080

0000.0001

0 00:01:28.03

0010

MEM

0175.0001

0 00:02:03.07

0090

HDC

2000.0001

0 00:02:08.58

0 00:00:55.01

0700.7091

0 00:02:08.58

1002.0051

0 00:01:03:45

2500.0001
6

00A0

TPC

1000.0001

0 00:02:44.04

0 00:04:46.32

1300.0001
?? 1

OOCO

0000.7004

(The error codes are defined in the troubleshooting
procedures for each individual device)

The first line indicates the CPU name (KA410-A), the ROM version (VI.0),

the ROM Status (01 — the ROM is corrupted if this is anything other than
01), and the mode of the System exerciser (CU for customer and FS for field
Service mode). The next several lines list Information on the devices that
are exerdsed by the System exerciser.

The first column of the display lists the test number (F,C,B,7,6,1). TESTS 4
through 1 are Option modules and these options may not be installed. They

Testing and Troubleshooting

2-15

are listed in the display only if they are installed. The second column Iists
the device identifier (00B0, 0080, 0010,...). Next is the mnemonic for each
device (MONO, DZ, MEM,...) followed by the error code (0000.0000) for

that device (the HDC and TPC devices have additional error codes for each
drive). After the error code is the number of times the device was tested
followed by the time of the last pass the exerciser made on that device.
The time is in the format of days hours:minutes:seconds.hundredths of
seconds. Question marks identify hard (??) and soft (?) errors. See the
troubleshooting procedures (Paragraph 2.4) for the device that has an error
detected with it.

2.4 Troubleshooting Procedures
Each section below contains troubleshooting information for the device indicated. Find the section below with the mnemonic (such as MONO or TPC)
that you want to troubleshoot. Once the section is located, read through the
procedures to familiarize yourself with the testing of the device.

2.4.1 MONO — Monochrome Video Troubleshooting
Procedures (VAXstation 2000 only)
You can troubleshoot the monochrome circuitry on the System module
in either customer mode or field Service mode. Both modes test the
monochrome circuits the same. This procedure does not troubleshoot the
video monitor, just the video circuits on the System module.

2.4.1.1 Self-test
To run self-test on MONO, enter TEST F. The monitor connected to the
video port blinks white and black several times. This is normal. The results
of the self-test are displayed when self-test is complete. Any error code
other than 0000.0001 indicates a fault in the monochrome video circuits.
You must replace the System module to fix this problem.

2.4.1.2 System Exerciser
To run the System exerciser, enter TEST 0 for customer mode or TEST 101
for field Service mode. The monitor connected to the video port blinks white
and black several times while the monochrome circuits are being tested. The
results of the MONO tests are displayed on the console screen after they are
tested for the first time, then displayed again after each concurrent testing.
Any error code other than 0000.0001 indicates a fault in monochrome video
circuits. You must replace the System module to fix this problem. This
device is not exercised on the MicroVAX 2000 System since MicroVAX 2000
does not use video monitors.

2-16

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

2.4.2 CLK — Time-of-Year Clock Troubleshooting
Procedures
You can troubleshoot the CLK circuitry in either custpmer mode or field
Service mode. Both modes test the CLK circuits the same.
2.4.2.1 Self-test
To run self-test, enter TEST E. Any error code other than 0000.0001 indicates a fault in the CLK circuits. An error code of 0000.0005 indicates that
the System time is not set. Refer to the operating System Software docu-

mentation to set the time. If any other error code appears in the CLK error
display, you must replace the System module.

The System exerciser does not display the Status of the CLK circuits. The
CLK circuits are not directly tested but are tested through the testing of
other circuits.

2.4.3 NVR — Non-Volatlle RAM Troubleshooting
Procedures
You can troubleshoot the NVR circuitry in either customer mode or field
Service mode. Both modes test the NVR circuits the same.
2.4.3.1 Self-test

To run self-test, enter TEST D. Any error code other than 0000.0001 in
dicates a fault in the NVR. An error code of 0000.0005 indicates that the
battery Charge is below the normal voltage level. If the battery is low, al-

low the System to Charge the battery for five minutes and then run TEST D
again. If the error code is still 0000.0005, replace the battery. A charging
time of 20-25 hours is needed to fully Charge the battery. Leaving the system powered up charges the battery. If any other error code appears in the
CLK error display, you must replace the System module.

The System exerciser does not display the Status of the NVR circuits. The
NVR circuits are not directly tested but are tested through the testing of
other circuits.

2.4.4 DZ — Serial Line Controller Troubleshooting
Procedures
You can troubleshoot the DZ in either customer mode or field service mode.
The difference between the two modes is that field service mode tests the
serial line drivers on the System module and customer mode does not.

Testing and Troubleshooting

2-17

2.4.4.1 Self-test

To run customer mode self-test on either the VAXstation 2000 or the Mi
croVAX 2000, enter TEST C. Loopback connectors must not be installed
when in customer mode. Loopback connectors must, however, be installed
to run field Service mode diagnostics. Any error code other than 0000.0001
indicates a fault in the DZ Controller. You must replace the System module
to fix the problem. If you are using the diagnostic console device, any error
code other than 0000.4001 indicates a fault in the DZ Controller.
VAXstation 2000

To run self-test in field Service mode on VAXstation 2000, install a loopback
(p/n 29-24795) on the 25-pin communication port and a loopback (p/n 2924794) on the 9-pin printer port. Enter TEST C. If the error code is not
0000.0001, check to see if the loopbacks are still connected. Reconnect
them, if necessary, and test again. Replace the System module if the error
still exists. Loopbacks cannot be used to test the DZ Controller when the
console device is the diagnostic console with the BCC08 cable since there
is no loopback for the video port.
MicroVAX 2000

To run self-test in field Service mode on MicroVAX 2000, install a loop
back (p/n 29-24795) on the 25-pin communication port and install an MMJ

loopback on both ports 2 and 3. Enter TEST C. If the error code is not
0000.0001, check to see if the loopbacks are still connected. Reconnect
them, if necessary, and test again. Replace the System module if the error
still exists.

2:4.4.2 System Exerciser

To run the customer mode System exerciser on either the VAXstation 2000
or the MicroVAX 2000, enter TEST 0. The results are displayed on the video
screen as the tests are completed.
VAXstation 2000

To run the field Service mode System exerciser on VAXstation 2000, install a
loopback (p/n 29-24795) on the 25-pin communication port and a loopback
(p/n 29-24794) on the 9-pin printer port. Enter TEST 101. If you are using the
diagnostic console device, you will get errors on the DZ line since there is
no loopback for the video port. Any error code other than 0X00.0001, where
X is the serial line being used for the console device, indicates a fault in

the DZ Controller. You must replace the System module to fix the problem.

If the console device is connected to the video port on VAXstation 2000,
then you will see a 0 (zero) in the X position. If the console device is the
diagnostic console device with the BCC08 cable on the printer port, then
you will see a 3 in the X position. If the error code is not 0X00.0001, check

2-18

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

to see if the loopbacks are still connected. Reconnect them, if necessary,
and test again. Replace the System module if the error still exists.
MicroVAX 2000

To run the field Service mode System exerciser on MicroVAX 2000, install
a loopback (p/n 29-24795) on the 25-pin communication port and install an
MMJ loopback on both ports 2 and 3. Enter TEST 101 or TEST 102 Any
error code other than 0X00.0001, where X is the serial line being used for
the console device, indicates a fault in the DZ Controller. You must replace
the System module to fix the problem. With the console device connected to
port 1 on the MicroVAX 2000, you will see a 0 (zero) in the X position. If the
error code is not 0X00.0001, check to see if the loopbacks are still connected.
Reconnect them, if necessary, and test again. Replace the System module
if the error still exists. If the error still exists after replacing the System
module, replace the DEC423 Converter on the back of the System box.

2.4.5 MEM — Memory Troubleshooting Procedures
You can troubleshoot memory in either customer mode or field Service
mode. Both modes test the MEM circuits the same. These procedures are
for both VAXstation 2000 and MicroVAX 2000.
2.4.5.1 Self-test

To run self-test, enter TEST B. Any error code other than 000X.0001, where
X is the size of memory (megabytes) in the System, indicates a fault in the

memory circuits. The problem could either be with the System module or

the memory Option module. To determine which module is at fault eo to

Paragraph 2.5.1.2.

2.4.5.2 System Exerciser

To run the System exerciser, enter TEST 0 for customer mode or TEST 101
for field service mode. Figure 2-9 shows what the MEM System exerciser
error code indicates. The Status portion of the code indicates the number

of pages tested during the last test pass (1 page = 512 bytes) if there were
no errors found.

f
Testing and Troubleshooting

2-19

Figure 2-9:

0010

Example of MEM System Exerciser Error Code

MEM

0 00:02:03.07

0175.0001

Error code.

0001 = GOOD

Statue code.

Number of

pages of memory tested

when error code is 0001.

An error code of .0001 indicates no errors. If errors were detected during
the last test pass, the error portion of the code contains the error code.
Table 2-5 lists the MEM System exerciser errors and shows which module
is causing the error.

Table 2-5:

MEM System Exerciser Error Codes

Error Codes

Definition

0001.001F

Compare error on the System module

0002.001F

Compare error on the Option module

0001.002F

Parity error on the System module

0002.002F

Parity error on the Option module

2.4.6 MM — Memory Management Unit Troubleshooting
Procedures
You can troubleshoot the memory management (MM) circuitry in either
customer mode or field Service mode. Both modes test the MM circuits the
same.

2.4.6.1 Self-test

To run self-test, enter TEST A. Any error code other than 0000.0001 in
dicates a fault in the memory managment circuits. You must replace the
System module to fix the problem.
The System exerciser does not display the Status of the MM circuits. The
MM circuits are not directly tested but are tested through the testing of other
circuits.

2-20

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

■v

2.4.7 FP - Floating Point Unit Troubleshooting
Procedures
You can troubleshoot the floating point (FP) circuitry in either customer

mode or field Service mode. Both modes test the FP circuits the same.
\

2.4.7.1 Self-test
To run self-test, enter TEST 9. Any error code other than 0000.0001 indicates
a fault in the floating point circuits. You must replace the System module
to fix the problem.
The System exerciser does not display the Status of the FP circuits. The FP
circuits are not directly tested but are tested through the testing of other
circuits.

2.4.8 IT — Interval Timer Troubleshooting Procedures
You can troubleshoot the interval timer (IT) circuitry in either customer
mode or field Service mode. Both modes test the IT circuits the same.
2.4.8.1 Self-test

To run self-test, enter TEST 8. Any error code other than 0000.0001 indicates
a fault in the timing circuits. You must replace the System module to fix the
problem.
The System exerciser does not exercise the IT circuits.

2.4.9 HDC — Disk Drives and Controller Troubleshooting

Procedures
You can troubleshoot the disk Controller and drives using self-test and the
System exerciser. These diagnostics test the disk Controller on the System
module and also test the drives connected to the Controller. There is a maximum number of three drives that can be supported in either a VAXstation
2000 or a MicroVAX 2000. The three drives are labelled DUA0, DUA1, and
DUA2. DUA0 will always be the hard disk drive (RD) located in the System
box. DUA0 can be a full-height or a half-height drive. DUA1 will always be
the hard disk drive (RD) located in the expansion box. DUAI communicates
to the System module through port B on the expansion adapter; thus allowing you to isolate DUA1 during testing, if necessary, without opening the
System box. DUA2 will always be the half-height floppy disk drive (RX33)

/ÄS*N

and will only be located in the System box. If DUA0 is a full-height drive,
then a floppy disk drive cannot be installed because of lack of space in the
System box. The disk Controller labeis any drive off-line that is not installed.
It also labeis DUA2 off-line if a floppy diskette is not properly loaded.

Testing and Troubleshooting

2-21

2.4.9.1 Self-test

To run self-test on the HDC, enter TEST 7. Self-test gives a quick Status
of the disk Controller on the System module and the drives. You can run
self-test in either customer mode or field Service mode since both modes
test these devices the same. The error code for the disk Controller (HDC in
the configuration table) contains the test results of the disk Controller and
the Status of the three drives. Figure 2-10 shows how the error code is
broken into five Segments: Status of DUA2, DUA1, DUAO, tape Controller,
and the error code if a hard error is found. The power-up error code is the
same as the self-test error code.
Figure 2-10:

HDC Power-up and Self-test Error Code

7 0090 0000.0000

-> These four digits echo the first four digits

a hard error is found on the disk

Controller.

Otherwise,

0001 = Good.

-> Status of disk Controller on System module.
0 = Good.
-> Status code for DUAO,

listed in Table 2-6.

-> Status code for DUA1,

listed in Table 2-6.

-> Statue code for DUA2,

listed in Table 2-6.

DUAO is the hard disk drive in System box.

DUA1 is the hard disk drive in expansion box.
DUA2 is the floppy disk drive in System box.

Each drive has the same set of error codes. These codes are listed in Ta

ble 2-6. All odd-numbered error codes are soft errors or a Status. All even-

numbered error codes (including A and F) are hard errors. The last four
digits of the error code repeat the first four digits if a hard error is found on
the disk Controller. Otherwise, the last four digits contain 0001 to indicate
no errors or soft errors.

2-22

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Table 2-6:
Error Codes

Power-up and Self-test Error Codes for each

Dlsk Drive

Descrlption of error codes for each dlsk drlve

Good — No error for this drive.

Drive select error. Disk Controller or the drive failed. Replace the System
module first. Replace the drive lf the problem is not fixed after replacing

the System module.

Read during read test error. The disk or diskette may not be formatted. Run
the disk verifier to check out the disk. Copy the disk data onto another disk

or to another System over the net if you have to reformat the drive.

4
5

Read after write error. Drive failed. Replace the drive first. Replace the

System module if the problem is not fixed after replacing the drive.

Invalid UIB (DUAO and DUA1 only). Disk needs formatting or the disk is

not a Digital disk. Run the disk verifier to check out the disk. Copy the
disk data onto another disk or to another System over the net if you have
to reformat the drive.

Drive failed to restore. Drive failed. Replace the drive first. Replace the

Off-line — No drive installed, no floppy diskette loaded in DUA2, or DUA1

Drive not done error. Drive failed. Replace the drive first. Replace the

System module if the problem is not fixed after replacing the drive.
(in expansion box) is not turned on.

System module if the problem is not fixed after replacing the drive.

Invalid Status from Controller. Disk Controller or diskette failed. If DUAO

ro DUA1, replace the System module first then replace the disk drive if the
problem is not fixed after replacing the System module. If DUA2, replace
the floppy diskette first or save the data on it and reformat it. If DUA2 and
the floppy diskette is not the problem, replace the System module and then
replace the floppy disk drive if replacing the System module did not fix the
problem.

A
F

Drive select timeout error. Drive failed. Replace the drive first. Replace

the System module if the problem is not fixed after replacing the drive.

Untested — Drive was not tested because of a hard error found on the disk

Controller. For example, FFF8.FFF8 indicates an error on the disk Controller
and no drives were tested. Replace the System module.

If any error (except 7 and F) appears for any drive, check the drive for

power and check the cables for a good connection. If the error still exists,
the problem is either in the drive, in the cables, in the System module, or in
the disk interface module located in the expansion adapter. If, for example,

you replace one of the disks to fix an error code and the error still exists,'
replace the System module. If the system module does not fix the problem
replace the disk interface module.

Testing and Troubleshooting

2-23

2.4.9.2 System Exerciser

Start the System exerciser by entering TEST 0 for customer mode or install
the 25-pin loopback on the communications port and enter TEST 101 for
field service mode. The customer mode System exerciser does not exercise
the disks as thoroughly as the field service exerciser. The field service

System exerciser performs a complete read/write test on all drives and also
performs a data transfer test between the disk Controller and one of the

/*^S

drives.

The results of the System exerciser are displayed on the screen after the
first test pass of each device tested and again after all devices have been
run concurrently. Figure 2-11 shows the System exerciser display for the
disk Controller (HDC). There is one line for the Controller Status and one
line for each drive connected to the Controller. A drive that is not installed
or is off-line is not listed in the display. For example, no diskette in DUA2
or an unformatted diskette in DUA2 labeis DUA2 as off-line and no display
for DUA2 is listed. If there are two question marks on the Controllers line,
replace the System module. If there is a Single question mark on the drive's
line, there is a soft error in the drive and the drive may operate normally.
Two question marks on the drive's line indicate a hard error in the drive
or an error in the Controller. You must replace one or both to fix the error.
Two question marks for DUA2 may also indicate bad media on the floppy
diskette.

Figure 2-11: Example of System Exerciser Display for the Disk Controller

0090

HDC

1000.0001

0 00:02:09.47

0700.0001
1700.0001

2500.0001

Table 2-7 lists the error codes for the disk Controllers line and Table 2-8
lists the error codes for the drives.

2-24

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Table 2-7:

HDC Disk Controller System Exerciser Error

Codes

Error Codes

Possible Cause

Corrective Action

X000.0001

The X indicates the drive
used for the data trans

data transfer test was done.

0 « DUAO, 1 = DUA1, 2 - DUA2, and F = no

fer test.

0X00.0001

Data transfer error if X
is anything other than
zero.

Replace the System module. If the error still exists after replacing the System module, replace the
drive that was used for the data transfer test. Always replace the drive's device electronics board
(hard disk drives only) before replacing the whole
drive.

ooxx.oooi

The XX indicates the num- Run the exerciser again. Was the same drive used
ber of errors detected dur for the transfer test?
ing the data transfer test.
If yes, and the number of transfer errors are the
Make note of the drive
same (or dose to the same), replace System mod
used for the data trans
ule. Replace the drive that was used for the data
fer test.
transfer test if replacing the System module did
not fix the problem.

If no, and the number of transfer errors are zero,

replace the drive that got errors during the data
transfer test.

Always replace the dxive's device

electronics board (hard disk drives only) before
replacing the whole drive.
0O00.XXX1

Controller error.

If XXX is anything other than 000 (three zeros),

replace the System module.

Testing and Troubleshooting

2-25

Table 2-8:

HDC Dlsk Drive System Exerciser Error Codes

Error Codes

Possible Cause

Corrective Action

X000.0001

The X position indicates
the drive that this error
code is for.

0 = DUAO, 1 = DUA1, and 2 - DUA2.

0X00.0001

The X position indicates
the drive Status.

The X position indicates drive status as listed be-

low.

DUAO and DUA1:

7 writeable, formatted, UIB and RCT ok
5 writeable, formatted, no UIB and RCT
4 writeable, unformatted, no UIB and RCT
3 non-writeable, formatted, UIB and RCT ok
1 non-writeable, formatted, no UIB and RCT
0 non-writeable, unformatted, no UIB and RCT
DUA2:

5 writeable and formatted
4 writeable and unformatted
1 non-writeable and formatted
0 non-writeable and unformatted
OOXX.OOOl

The XX position indicates
the drive error count. 00
indicates no error.

Run the exerciser again. Note the error count for

the failing drive after each pass. If the count stays
the same or increases, replace the failing drive.
lf the error still exists after replacing the drive,
replace the System module. Always replace the

drive's device electronics board (hard disk drives
only) before replacing the whole drive.
000O.XXX1

The XXX position indi
cates the error codes for

the drive. 000 indicates
no error.

If anything other than zeros (0001), replace the

System module. Replace the drive if replacing the
System module did not fix the problem. Always
replace the drive's device electronics board (hard
disk drives only) before replacing the whole drive.

^■^ÜSk

2-26

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

(

2.4.9.3 Troubleshooting the Hard Disk Drive Expansion Box
Troubleshoot the hard disk in the expansion box (DUAl) using self-test and
the System exerciser. However, if the diagnostic tests indicate an error on

DUAl, perform the Steps in the following procedure.

Check to make sure the expansion box has power to it and it is switched
on.

2. Check to make sure the hard disk cable is properly connected to port
B on the expansion adapter and the back of the expansion box.

3. Run the tests again and if the Status code shows DUAl to be off-line,
troubleshoot the power supply in the expansion box.

Disconnect the cable from port B on the expansion adapter and run
self-test (TEST 6). If any Status other than the off-line indication (7) or
the not tested indication (F) shows up in the Status code for DUAl, then

replace the disk Controller on the System module.

If the starus code does show that DUAl is off-line after disconnecting
it from port B, check the drive select jumpers on DUAl for proper
positioning. Refer to Paragraph 2.4.9.4 below for proper drive select

jumper settings.

If the drive select jumper is set properly, replace DUAl in the disk
expansion box. Always replace the drive's device electronics board

before replacing the whole drive.

2.4.9.4 Drive Select Jumper Settings on Disk Drives

DUAO — Refer to Figure 2-12 to set the drive select jumper on an RD32 in
the System box. Refer to Figure 2-13 to set the drive select jumper on an
RD53 in the System box.

DUAl — Refer to Figure 2-13 to set the drive select jumper on an RD53 in
the expansion box.

DUA2 — Refer to Figure 2-14 to set the drive select jumper on an RX33 in

the System box.

Testing and Troubleshooting

2-27

Figure 2-12:

RD32 Drive Select Jumper Setting for DUAO

Figure 2-13:

RD53 Drive Select Jumper Setting for DUAO and DUA1

□
COMPONENTSIOE

PINiE— II

TERMINATOR

2-28

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Figure 2-14:

RX33 Drive Select Jumper Setting for DUA2

INDICATES

JUMPER

INSTALLED

MFDCONTROL
BOAHD

2.4.10 TPC — Tape Drive Controller Troubleshooting
Procedures

You can troubleshoot the tape drive Controller on the System module and
the tape drive Controller in the expansion box using self-test or the System
exerciser. The tape drive expansion box has an internal self-test to trou

bleshoot the TK50 tape drive as described in Paragraph 2.4.10.3.

These troubleshooting procedures assume that only one tape expansion box
is connected to the tape port (port A) on the expansion adapter. Although

the diagnostic firmware located in ROM supports up to seven devices on
port A of the expansion adapter, we will only cover how to troubleshoot one

tape expansion box since the VMS and ULTRIX operating Systems support

only one tape expansion box on either System. Also, the tape expansion
box must be configured for ID address 1 on the tape port.
2.4.10.1 Self-test

To run self-test, enter TEST 6. Self-test gives a quick Status of the tape

Controller on the System module and also the tape drive expansion box
connected to the tape Controller via port A of the expansion adapter. You
Testlng and Troubleshooting

2-29

can run self-test in either customer mode or field Service mode since both
modes test these devices the same. Enter TEST 50 to see the results of the
self-test. The TPC error code contains the test results of the tape Controller
on the System module and the tape drives connected to port A on the
expansion adapter. Figure 2-15 shows how the TPC error code is broken
into five segments: ID addresses of devices connected to the tape port,
ID addresses of the devices that tested successfully, two possible cause
indicators, and a Status of the tape Controller.
Figure 2-15:
6

TPC Power-up and Self-test Error Code

00A0 0000.0000

Status of tape Controller on ayatem module.
01

= Good.

-> Poaaible cause indicator.
0 = Good.

1 = Error moat likely on 8y8tem module
2 = Error most

likely in expanaion box.

3 = Error could be in either location.
-> PosBible cause

indicator.

0 = Good.

1 = Retest TPC again.

2 = Error moat likely in expanaion box.
3 = Combination of

1 and 2.

4 = DMA and interrupts not teated.
5 =• Combination of

1 and 4.

6 = Combination of 2 and 4.
7 = Combination of

and 4.

-> Status of the tape expanaion box.

The

ID addreaa of the expanaion box ia
diaplayed here if
aucceaafully.

it teated

These two digits ahould

be the same aa the first two digits.

00 a No box connected to port A or
no box teated aucceaafully.
02 = ID Addreaa

04 =

ID Addresa

08 ° ID Addreaa 3
10 » ID Address 4

20 =■ ID Addreaa 6
40 = ID Addreaa 6
80 =■ ID Addreaa 7

-> ID Addreaa

(ahown above)

of the tape

expanaion box that is connected to
port A.

2-30

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

A Status code of 0000.4001 indicates a good Status for the tape Controller
when no devices are connected to port A. If there is a tape expansion box
connected to port A and the Status code is 0000.4001, then the Controller
does not recognize it or it is not powered up.

If the second two digits of the Status code shown in Figure 2-15 (good
devices) do not match the first two digits (connected devices), then there
is a communication problem between the tape expansion box and the system. Disconnect the cable from port A on the expansion adapter and run
self-test again. If the Status code for TPC now contains anything other than
0000.4001, replace the System module. Otherwise, if the Status code is
0000.4001, reconnect the cable to port A and make sure the tape expan
sion box is powered up. Run self-test again. If the Status code for TPC
is not 0202.0001 after reconnecting the cable, run the System exerciser to
thoroughly test the tape Controller and the tape expansion box. If the error
code is 0202.0001 after reconnecting the tape expansion box, the tape Con
troller and the expansion tape box are operating properly. Note that there
may be more than one tape expansion box on Systems that run an operating
System other than VMS or ULTRIX. This means that the Status code may be
0606.0001 for two devices at ID address 1 and 2 or FEFE.0001 for all seven
devices connected to the tape port. However, if the System does use VMS
or ULTRIX, the tape expansion box at ID address 1 is the only device VMS
and ULTRIX can communicate with.

2.4.10.2 System Exerciser
Start the System exerciser by entering TEST 0 for customer mode or install
the 25-pin loopback on the communications port, load the COMPACTape
cartridge with the special-key into the TK50, and enter TEST 101 for field
Service mode. The customer mode System exerciser does not exercise the
tape Controller as thoroughly as the field Service exerciser. The field Service
mode System exerciser performs a complete read/write test on the TK50
tape drive and also performs a data transfer test while the customer mode
System exerciser does not test the TK50 tape drive at all.
The System exerciser runs a first pass test on MONO (VAXstation only), DZ,
MEM, and HDC before it runs the first pass test on the TPC. The first pass
test on the TPC tests the tape Controller on the System module and checks
the tape port for the presence of a tape expansion box only if the tape Con
troller is operating properly. If the tape Controller on the System module
tests bad, the error code for the tape Controller lists an error and the tape
port is not checked for the presence of the tape expansion box. The first

pass test of the TPC does not perform any diagnostics or data transfer tests
on the tape expansion box. The first pass test only checks whether or not the
tape expansion box is there and whether or not it can communicate over the
tape port to the tape Controller. Complete data transfer and read/write (field
Service mode only) testing is done on subsequent test passes. For example, in field Service mode with the Special keyed COMPACTape cartridge

Testing and Troubleshooting

2-31

installed, the error code for the tape expansion box shows that the TK50 is
not writeable (1100.0001) during the first pass. However, the second pass

shows that the TK50 is writeable (1300.0001) as long as the cartridge has a
good Special key on it and the tape expansion box is operating properly.
So you must wait for the System exerciser to complete at least two passes
on the TPC to see if the tape expansion box is operating properly.
Figure 2-16 shows the System exerciser display for the TPC. There is one
line for the Status of the tape Controller on the System module and one line
for each tape expansion box connected to the tape port if it is powered
up. The Status of the tape Controller is next to the TPC mnemonic (first
line) and the Status of the tape expansion box is listed under the Status of
the Controller. An easy way of determining if any errors are detected is by
looking for the question marks in the left column. If there are any question
marks on the tape Controllers Status line, the tape Controller is faulty and

the error code identifies the problem. Refer to Table 2-9 to decifer the tape

Controllers error code and determine how to fix the problem. If there are
any question marks on the tape expansion box's Status line, the problem
could be in either the tape expansion box, the tape expansion box cable, or
the tape Controller on the System module. An error that is listed in the tape
expansion box's error code may be a data transfer error and thus does not
isolate the problem to the tape expansion box; it may still be in the tape
Controller on the System module. Refer to Table 2-10 to decifer the tape
expansion box's error code and determine how to fix the problem.

If errors are detected with the TPC, disconnect the tape expansion box cable

from port A on the expansion adapter and run the test again. This procedure
isolates the tape expansion box from the System box. If any errors appear
in the tape Controllers error code, the problem is with the tape Controller
and the System module must be replaced. Otherwise, the error is in the
expansion box and you must run the internal self-test on the expansion box

as described below.

Figure 2-16:

Example of System Exerciser Display for the Tape Con
troller

OOAO

TPC

1OOO.O0O1

0 00:03:18.26

1300.0001

2-32

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

****>

Table 2-9 lists the System exerciser enor codes for the Controller's error line

and Table 2-10 lists the System exerciser error codes for the tape drives error
line.

Table 2-9:

TPC Tape Controller System Exerciser Error
Codes

Error Codes

Possible Cause

Correctlve Action

X000.0001

This error code indicates no Controller er
ror. The X indicates
the transfer test drive

The X position indicates the tape drive that was
used for data transfer testing. This number should
be 1 if a tape expansion box is connected to the Sys
tem and it is powered up. This number should be
8 if no tape expansion box is connected or if it is
turned off. An F will always be in this position
during the first pass of the exerciser. If the P is still
in this position after the first pass is complete, a
fatal error is detected in the tape Controller on the
System module and the tape expansion box is not

number.

tested.
0X00.0001

The X indicates a data
Replace the System module. If the error still exists,
tranBfer error if X is
replace the TK50 tape drive. Then if the error code
anything other than zero. still exists, replace tbe TZK50 Controller board.

0OXX.00O1

The XX indicates the num-Run the exerciser again. Was the same drive used
ber of data transfer erfor the transfer test? If yes, and the number of
rors detected. Make note transfer errors are the same (or dose to the same),

of the tape drive used
replace the System module. If no, and the number
for the data tranBfer test. of transfer errors are zero or considerably less than
before, replace the TK50 drive that was originally
used for the transfer test. If the error code still ex
ists, replace the TZK50 Controller board.
0000.XXX1

Controller error if any
X is anything other than

Replace the System module.

zero.

Testing and Troubleshooting

2-33

Table 2-10:

Tape Drive Expansion Box System Exerciser
Error Codes

Error Codes

Posslble Cause

Correctlve Action

XOOO.OOOl

The X indicates the device ID address of tape

This device ID address can be 1, 2, 3, 4, 5, 6, or 7. It
should normally be 1 unless the device ID address

expansion box.

jumpers (Pl, P2, P3) on the TZK50 Controller board
have been changed. It must never be 0. If a 0 is in
this position, the device ID address jumpers are set

to zero and they must be reset to another ID. The
ID address must be 1 for Systems running VMS or
ULTR1X.

0X00.0001

The X indicates the tape
cartridge status.

The X position indicates whether or not the device

on the tape port has removeable or non-removeable
media and also whether or not the device is writeable. 1 = removeable media, 2 = writeable, and 3
= removeable media and it is writeable. This digit
should be a 1 or a 3 since the TK50 has removeable
media. This digit should be a 1 in customer mode

and a 3 in field Service mode if the special-keyed
cartridge is installed and loaded in the TK50. Note
that this digit can never be a 3 in field Service mode

until a second pass test is done on the TPC since the
System exerciser does not do a write test on the first
pass.

00XX.0O01

The XX indicates the driveThe error may be in the TZK50 Controller board,
error count during the
the TK5Ü tape drive, or the tape Controller on the
data transfer test.
indicates no error.

System module. Run the exerciser again but with
another tape expansion box, if possible, to determine if the error is on the tape Controller or in
the tape expansion box you removed. If the data
transfer error still appears after replacing the tape
expansion box, replace the System module. Otherwise, troubleshoot the tape expansion box as shown
in Paragraph 2.4.10.3 below. If you do not have an

other tape expansion box to swap out, replace the
following FRUs one at a Urne and run the exerciser
after each one is replaced until there are no more
transfer errors. First, TZK50 Controller board; sec

ond, TK50 tape drive; third, the System module.
Remember that the TK50 tape drive is not tested in
customer mode and is also not tested in field service mode if the special-keyed tape cartridge is not
loaded in the TK50 tape drive.

2-34

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Table 2-10 (Cont.):

(

Tape Drive Expansion Box System
Exerclser Error Codes

Error Codes

Possible Cause

000O.XXX1

The XXX indicates the

error codes. 000 indicates no errors.

Corrective Actlon

If anything other than zeros (.0001) appear, Run

the exerdser again but with another tape expan-

sion box, if possible, to determine if the error is on

the tape Controller or in the tape expansion box you
removed. If the error still appears after replacing
the tape expansion box, replace the System module.

Otherwise, troubleshoot tne tape expansion box as
shown in Paragraph 2.4.10.3 below. If you do not
have another tape expansion box to swap out, re
place the following FRUs one at a time and run the

exerciser after each one is replaced until there are
no more transfer errors.

First, TZK50 Controller

board; second, TK50 tape drive; third, the System
module. Remember that the TK50 tape drive is not
tested in customer mode and is also not tested in

field service mode if the special-keyed tape cartridge
is not loaded in the TK50 tape drive.

2.4.10.3 Troubleshooting the Tape Expansion Box
If the results for the TPC indicate a problem in the tape expansion box, the
problem could be the TK50 tape drive, the TZK50 Controller board, or the
power supply. The TK50 tape drive performs an internal self-test every time
the tape expansion box is powered up. The TZK50 Controller also performs
an internal self-test at power up. To do an in-depth self-test on the TK50
tape drive and the TZK50 Controller board, follow the procedure below. Do
each step indicated until you find and fix the problem.

Remove the tape drive expansion box cover.

Check all cables to make sure they are connected properly. Remove the

shield to check the cables on the back of the drive. Note that there are
two power cables connected to the resistor load board.
3.

Check the jumpers on the TZK50 Controller board for proper installation. Refer to Figure 2-17 for jumper locations and tape port ID address confirmation. Figure 2-17 shows the Controller board set for ID
address 1, with parity checking enabled, and internal diagnostics disabled. Make sure the three ID address jumpers (Pl, P2, and P3) are set
to ID address 1. Jumper P4 is the parity checking jumper and must be
installed for normal Operation. Jumper P5 is the diagnostic jumper and

must not be installed for normal Operation. Note the position of the

spare jumper(s). Spare jumpers should be stored across P5 and one of
the spare posts.

Testing and Troubleshooting

2-35

Check the three resistor network packs (Z7, Z6, and Z5) to make sure
they are installed properly. If this expansion box is the only box con-

nected to the tape port, these resistor network packs must be installed

on this board. If this expansion box is not the only box connected to the
tape port, then make sure the last box in the chain contains these re
sistor network packs and all other boxes in the chain have their resistor
network packs removed.
5.

Plug in the power cord and switch on power to the expansion box.

If the LED on the TZK50 Controller board and on the TK50 tape drive
do not light when power is first turned on or the fan does not turn,
troubleshoot the power supply (Paragraph 2.4.13).

Watch the red light on the TK50 tape drive. It should shut off after five
to six seconds after power up if no tape is installed. If it Starts flashing,
replace the TK50 tape drive. When a tape is installed, the red light stays
lit.

Look at the LED on the TZK50 Controller board. It turns on at power
up, then turns off after two seconds. It must stay off once it turns off.
If it does not stay off, replace the TZK50 Controller board.

Insert and load a blank COMPACTape cartridge into the TK50 tape
drive. Do not use the special-keyed cartridge from the kit or a cartridge
that has good data, because the next few steps will erase the Special

key and the data on the cartridge. If you must use the special-keyed
cartridge, reload the Special key onto the cartridge using TEST 73 after
you complete this procedure.

10. Switch off power to the expansion box.
11. Remove a spare jumper and install it onto P5. If there are two spare
jumpers then both must be removed from their storage positions so one
of them can be installed onto P5.
12. Switch on the power switch.

13. Wait about one minute for the test to finish. If the LED on the TZK50
Controller board Starts flashing during or at the end of the test, replace
the TK50 tape drive. If the LED is on steady, replace the TZK50 Con
troller board. If the LED is off, the TZK50 Controller board and the TK50
tape drive are operating properly. Note that the LED comes on again

at the end of the test for about two seconds to indicate that the testing
cycle has completed and is starting over again. The test will continue
to cycle until the P5 diagnostic jumper is removed or power is switched
off.

2-36

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

'^5*v

Figure 2-17:

TZK50 Controller Board Jumper Location

P1 P2 P3 P4 P5 SPARE

<D
00

CQ
ß>
Q.

o
o
<Q

InstaMcd

tnsttlled

Insulled

ADDRE5S ID

InstAlIed

InstBÜed

Removed

2
3

Irmalied

Removed

tnitalled

Instollcd

Removed

Removcd

Instclled

Installed

5
6

Removed

Installed

Removed

Initallcd

Removed

14. Replace the faulty component, if any, and retest.

15. Set up the jumpers on the TZK50 Controller board for normal Operation.
Spare jumpers must be stored across P5 and one of the spare posts.
16. This concludes the troubleshooting procedures for the tape expansion
box.

2.4.11 SYS - Interrupt Controller and ThinWire Ethemet
ID ROM Troubleshooting Procedures
You can troubleshoot the interrupt Controller and ThinWire Ethernet ID
ROM (SYS) in either customer mode or field Service mode. Both modes
test these drcuits the same.
2.4.11.1 Self-test

To run self-test, enter TEST 5.

Any error code other than 0000.0001 or

0000.0100 indicates a fault in the interrupt Controller or the ThinWire Ether
net ID ROM on the System module. The 0000.0100 error code indicates that

the keyboard is disconnected from the VAXstation 2000 Systems. Replace
just the ThinWire Ethernet ID ROM on the System module to fix an error
code of 0000.0004. Replace the System module to fix any other error code.
The replacement procedure for the System module instructs you to remove
the Thinwire Ethernet ID ROM from the System module being removed and
install it onto the new System module. If the ThinWire Ethernet ID ROM
has been replaced for an error code of 0000.0004 and the same error code
of 0000.0004 reappears when you retest, replace the System module instead
of just the ThinWire Ethernet ID ROM.

The System exerciser does not display the Status of the SYS circuits. The
SYS circuits are not directly tested but are tested through the testing of other
circuits.

/SR^v

2-38

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

2.4.12 Nl - ThinWire Ethernet Network Option
Troubleshooting Procedures

^sp^

You can troubleshoot the ThinWire Ethernet network Option (NI) in either
customer mode or field Service mode. Both modes of self-test test the network Option the same. The field Service mode of the System exerciser does

a more in-depth testing of the Option. To troubleshoot the network Option,

run self-test (TEST 1) or run the System exerciser (TEST 0 for customer mode
or TEST 101 for field Service mode).

Self-test and the System exerciser test the network interconnect module,
the ThinWire transceiver circuits on the System module, and also perform
a loopback function on the ThinWire cable. All tests fail with an error
code of 0000.7004 if the ThinWire cable is not connected to the back of the
System box. An error code of 0000.7008 indicates the ThinWire cable is
not terminated properly. Check the ThinWire cable first if any error code

has a number seven in the fifth position (0000.7000). The seven in the fifth
Position indicates a loopback error, but it does not exclude a problem on the
network Option inside the System box. An error code of 0000.0001 indicates
no error and the network Option is operational.
2.4.12.1 SelMest

^^^

To run self-test, enter TEST 1. Any error code other than 0000.0001 indicates a fault in either the network interconnect module or on the ThinWire

Ethernet cable. Note that positions 3 and 4 (00XX.0001) in the error code

indicate the number of retries over the Ethernet cable before a success. If
the error code is not 0000.0001, check the ThinWire Ethernet cable on the
back of the System for proper connections and terminators. Reconnect the
Thinwire cable and terminators, if disconnected, and test again. If the error
code is 0000.7000 or above (for example, 0000.7001 or higher), disconnect
the ThinWire T connector from the back of the System and install the T con

nector with terminators from the Service kit. Run the test again. If the error
code is 0000.0001 after installing the T connector with both terminators, the
problem is on the ThinWire Ethernet cable. Otherwise, if the error code
is anything other than 0000.0001, replace the network interconnect module

and test again with the T connector and both terminators installed. If the
error code is still not 0000.0001 after repladng the network interconnect
module, replace the System module.
2.4.12.2 System Exerciser

To run the System exerciser, enter TEST 0 for customer mode or TEST 101

for field Service mode. Field Service mode does a more in-depth test of

the circuits. Any error code other than 0000.0001 indicates a fault in the

network interconnect module or on the System module. Unlike the self-test

for the network Option, the System exerciser does not do any testing over
the ThinWire Ethernet cable. It only tests the internal circuitry. If the error

Testing and Troubleshooting

2-39

code is not 0000.0001, replace the network interconnect module. If the error
code is still not 0000.0001 after replacing the network interconnect module,
replace the System module.

2.4.13 Power Supply Troubleshooting Procedures
Follow the flowchart in Figure 2-18 if a problem with the power supply in
either the System box, hard disk expansion box, or tape drive expansion
box exists. The flowchart is designed to troubleshoot the power supply in
any of the three boxes.

Figure 2-18:

Flowchart for Troubleshooting the Power Supply

IS POWER
PRESENTATTHE
WALL OUTLET

»j CALL AN ELECTRICIAN |

PLUG THE POWER CORD
INTOTHEBOXANDTHE
WALL OUTLET

OPEN THE BOX AND MAKE SURE THE POWER CABLES ARE
CONNECTED. THE 9-PIN POWER CABLE WILL NOT BE
CONNECTED IN THE EXPANSION BOXES. ONE OF THE 4-PIN
POWER CABLES WILL NOT BE CONNECTED IN THE SYSTEM
BOX WHEN ONLY ONE HARD DISK IS INSTALLED. ALL OTHER

POWER CABLES MUST BE COtfNECTED.

| SWITCH ONTHE POWER SWITCH |

REFER TO FIGURE 2-18 BELOW AND DO VOLTAGE CHECKS ON
THE POWER CONNECTORS. MAKE THE VOLTAGE CHECKS WITH
THE POWER CABLES CONNECTED. REPLACE THE POWER
SUPPLY IF ANY VOLTAGES ARE NOT WITHIN TOLERANCE.

2-40

VAXstatlon 2000 and MicroVAX 2000 Maintenance Guide

Figure 2-19:

Power Connectors Pin Voltages

CHECK VOLTAGE LEVELS WITH THE POWER CABLES CONNECTED!

PIN
1

2
3
4

5
6
7
8
9

VOLTAGE
GROUND
GROUND
GROUND
-12.0Vdc
-0.6 Vdc
5.1 Vdc
-0.25 Vdc
5.1 Vdc
-0.25 Vdc
12.1 Vdc
-0.60 Vdc
9.0 Vdc TO PIN 9
9.0 Vdc TO PIN 8

+ 12.1 Vdc

GROUND

MR-I286-1412
MAOIW »?

Testing and Troubleshootlng

2-41

2.4.14 VR260 Monochrome Monitor Troubleshooting

Procedures
Table 2-11 lists some Symptoms of common problems with the VR260.
When troubleshooting the VR260, follow the suggested corrective actions
in the order listed.

Table 2-11:

/**%.

VR260 Troubleshooting Table

Symptom

Corrective Action

No LED; blank screen.

Check the power cord connection.
Check the 120/240 Vac setting.

Check the fuse.
Remove the rear bulkhead assembly and check the con
nection to the transformer assembly.

Check the deflection board connections.
Replace the deflection board connections.

Flashing LED.

Check the deflection board connections, including the
chassis ground.
Make sure the high-voltage anode lead has a good connec

tion with the CRT.

Replace the deflection board.
Compressed raster; no video dis-

play.

Make sure the monitor cable is connected between the
System and the monitor.

Adjust the contrast and brightness adjustments.
Run the monochrome video diagnostics (TEST F). If a failure is indicated, replace the System module in the System
box before proceeding with troubleshooting the VR260.

Remove the rear bulkhead assembly and check the cable
connections to the video amp board.
Remove the video amp board and check the CRT pin con

nections.
Replace the video amp board.

Raster; no video display.

Run the monochrome video diagnostics (TEST F). If a failure is indicated, replace the System module in the System
box before proceeding with troubleshooting the VR260.
Ensure good CRT connections.

2-42

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Table 2-11 (Cont.):
Symptom

VR260 Troubleshooting Table
Corrective Action
Replace the video amp board.

No LED but good video display.

Remove the LED bezel assembly and check for a good connection.

Replace the LED.

Ensure proper cable connections fr.om.the deflection board
to the LED bezel assembly.

Video display but not to specifications.

Bring up the appropriate monochrome display alignment
pattern (TESTS 60, 61, or 62) and perform the adjustment
according to Chapter 4.

/f\

Testing and Troubleshooting

2-43

2.4.15 Terminal Communication Troubieshooting

Procedures (MicroVAX 2000 only)
If you are having communications problems on a terminal, follow the
flowcharts starting at Figure 2-20. If you have performed the loopback
test on the terminal and the terminal passed the tests, follow the flowcharts
starting at Figure 2-21.

Figure 2-20:

Flowchart forTroubleshooting Terminal Communications

INSTALLAN MMJ LOOPBACK
CONNECTOR ON THE TERMINALS
25-PIN ADAPTER (COMM PORT)

RUN THE LOOPBACK TEST ON
THE TERMINAL. REFER TO THE
TERMINALS PSG.

IS THE

TERMINAL THE
CONSOLE DEVICE
ON PORT 1

DO THE FOLLOWING STEPS IN ORDER UNTIL

THE CONSOLE DEVICE CAN COMMUNICATE
WITH THE SYSTEM.

2.
3.

SWAP TH E DATA CABLE WITH A KNOWN
GOOD CABLE.

REPLACE THE DEC423 CONVERTER.
REPLACE THE SYSTEM MODULE.

MR-1288-1 *Oa
MA-OO67-B7

2-44

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Figure 2-21:

Flowchart for Troubleshooting Terminal Communications
on the DEC423 Converter

INSTALL AN MMJ LOOPBACK
CONNECTOR ON PORTS 2 AND 3
AND ALSO THE 25-PIN LOOPBACK
ON THE COMM PORT. RUN THE DZ
SELF-TESTAGAIN.

REPLACE
DEC423

CONVERTER

is DZ ^^

ERROR CODE
sOOOO.0001^

REPLACE THE CABLE THAT

CONNECTS THE TERMINAL TO
THE DEC423 CONVERTER.
THE TERMINAL SHOULD NOW
OPERATE PROPERLY.

PUT THE MMJ
LOOPBACKS
ON THE NEW
DEC423. RUN
THE DZ SELFTESTAGAIN

MR-1286-1407
MAOOG8B7

Testing and Troubleshooting

2-45

2.5 Utilities
The Utilities help the user format a hard disk, set default and restart flags,
and display alignment patterns on VAXstation 2000's monitors as well as
other functions. Each Utility is described below and is available on VAXsta
tion 2000 and MicroVAX 2000 unless otherwise noted. Table 2-12 lists the
console mode TEST commands that invoke the Utilities.

Table 2-12:

Utilities

Test Number

Descriptlon of Utility

Configuration table

Set NVR default Boot device

Set NVR default Boot flags

Set NVR default recovery action flags

Language inquiry menu

Monochrome circle cross-hatch alignment pattern (25-pin loopback (p/n
29-24795) must be installed)

Monochrome screert of E's

Monochrome white screen

Mass storage disk Formatter

Mass storage verifier

Special key on floppy diskettes for field Service System exerciser (25-pin
loopback (p/n 29-24795) must be installed)

Special key on TK50 COMPACTapes for field Service System exerciser
(25-pin loopback (p/n 29-24795) must be installed)

80-8F

Reserved for future Option Utilities

Network test Utility

2-46

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

f0^

jm
f

2.5.1 Configuration Table
The configuration table lists the Status of each device installed in the System.
This configuration table holds the results of the self-test and power-up tests
and is updated each time self-test is run. See Figure 2-22 for an example of
a configuration table. The error codes for each device in the configuration
table are explained in the troubleshooting section for that individual device.
Remember that the configuration table contains the results of the self-test
and power-up tests and not the results of the System exerciser.
Figure 2-22:

Example of the Configuration Table

>» TEST 60

KA410-A VI.0
ID 08-00-2B-02-CF-A4
MONO

0000.0001

CLK

0000.0001

NVR

0000.0001

00000001 00000001 00000001 00000001 00000001 000012A0
MEM

0002.0001

00200000

0000.0001

HDC

1110.0001

000146B8 0028173 00000320
TPC

0202.0001

FFFFFF03 01000001 FFFFFF05 FFFFFF05 FFFFFF05 FFFFFF05
SYS

0000.0001

0000.0001 VI.0

...

The first line contains the CPU and the ROM version (KA410-A V1.0). The
second line contains the ThinWire Ethernet hardware address (in this ex
ample it is ID 08-00-2B-02-CF-A4). The rest of the display contains the error

-,_
{

codes for the devices installed on the System. The configuration table is
built during power-up testing and the error codes are the result of the selftest and power-up tests. This configuration table is the only place the results
of self-test are indicated. It is updated every time self-test is run. Additional
codes on the DZ, MEM, HDC, TPC, and NI give a more detailed Status on
these devices as listed below.

Testing and Troubleshooting

2-47

2.5.1.1 DZ Explanation in Configuration Table

The DZ has six 8-digit numbers that contain the Status of the four serial
lines, the keyboard, and the mouse or tablet. Any 8-digit number other
than 00000001 for the first five Status codes indicates a failure. A Status code
of 00000000 for the keyboard indicates that the keyboard is disconnected.
The sixth 8-digit number is anything other than 000012A0 (good Status) or
00000000 (nothing connected) indicates a failure in the device connected to
the monitor cable. The MicroVAX 2000 does not use the last two 8-digit
numbers and 00000000 is the normal display for the MicroVAX Systems.
Figure 2-23 shows what each 8-digit number represents.
Figure 2-23:
DZ

Example of the DZ Line in the Configuration Table
0000.0001

00000001 00000001 00000001 00000001 00000001 000012A0

Mouse or

Tablet Status
- Keyboard self-test

1— Printer port Status
1— Video port Status

1— Communication port Status

— Keyboard Port

(keyboard and video ports are physically
located in the video connector)

2.5.1.2 MEM Explanation in Configuration Table

The MEM has one 8-digit number that contains the amount of physical
memory in the System. This number is in hexadecimal. For example,
00200000 indicates that at least 2 megabytes of memory is in the System.

If there is an error in the memory, however, a second 8-digit number that
contains the location of the failed memory is displayed. Figure 2-24 shows
the second 8-digit number of the MEM display in the configuration table.
The 3 in the last digit indicates the error is on the System module. Only
the last digit needs to be explained because if any of the other seven digits
are anything other than 0 (zero), then an error is on the memory Option
module. Table 2-13 lists whether the System module or memory Option
module is faultly according to the last digit in the second 8-digit number.

2-48

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Figure 2-24:
?? MEM

Example of MEM Error Display in the Configuration Table
0000.0020

00200000 00000003

Bit map representation of the

memory bank that failed.

Digits

one through six are not used and
ahould always be 0.

Digit

seven

indicates a memory failure on the
memory Option module if not 0.
Digit eight

indicates either the

memory failed on the System module,
on the option module,

or on both.

The values for the eighth digit are
listed in Table 2-13.
Hexadecimal representation of the

total amount of memory in the System,

Testing and Troubieshooting

2-49

Table 2-13:
Error Codes

Determining the Location of the Failing Memory Bank

System Module

Option Module

0
1

X
X

8
9

X
/y

2-50

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

2.5.1.3 HDC Explanation in Configuration Table
The HDC has three 8-digit numbers that contain the megabyte size of the
hard disk drives and of the floppy diskette in the floppy drive. Figure 2-25

shows the Status codes that contain the sizes of the drives. The amount
of megabytes may be different for each drive because one drive may have
more revectored bad blocks than another.

Figure 2-25:

Example of the Second HDC Line in the Configuration
Table

HDC

1110.0001
000146B8 0028A173 00000320

— DUA2, nurnber of blocks (Hex) on
RX50 media diskette 00000320

- DUA2, number of blocks (Hex) on
RX33 media diskette 00000720

— DUA1, number of block (Hex) in RD53 in
the expaneion box

1— DUAO, number of blocks (Hex) in RD32 in System box

Testing and Troubleshooting

2-51

2.5.1.4 TPC Explanation in Configuration Table
The TPC has eight 8-digit numbers as shown in Figure 2-26. The example
in Figure 2-22 shows only six 8-digit numbers for lack of space. Each of the
8-digit numbers contain the Status of the devices connected to the tape port

(port A on the expansion adapter). Up to seven devices can be connected to
the tape port, but VMS and ULTRIX only support one tape expansion box.
The tape Controller on the System module alvvays holds ID address 0 as
shown in Figure 2-26 by the FFFFFF03 code in ID 0. ID address 1 contains
a Status code of 01000001 to indicate that the tape expansion box connected
to the tape port is at this address and it has no errors. The Status code

01000001 is the good Status code for the tape expansion box only, not for
any other type of device that the customer may have connected to port A (if
any). The other ID addresses hold a Status code of FFFFFF05 since, in this
example, no more devices are installed at those ID addresses. Normally,
when there is only one tape expansion box, it is located in ID address 1.
However, the ID address may be changed to any ID address except ID
address 0 since ID 0 is the tape Controller on the System module. The TPC
troubleshooting procedure shows how the ID address of the expansion box

can be changed. Figure 2-26 shows the ID addresses of the 8-digit numbers.
Figure 2-26:

Example of the Second TPC Line in the Configuration
Table

TPC

0202.0001

FFFFFFO3 01000001 FFFFFF06 FFFFFF05 FFFFFFO5 FFFFFFO5 FFFFFFO5 FFFFFF05

ID 0

NOTE:

ID 1

ID 2

ID 3

ID 4

ID 5

If there are no devices connected to port A,

powered up,

ID 6

or if they are not

the top line will indicate 0000.4001 with a Single question

mark for a good indication.

2-52

ID 7

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

/—

2.5.1.5 Nl Explanation in Configuration Table
The ThinWire Ethernet network interconnect Option module display in the
configuration table contains the revision level of the ROM located on the
NI module. V1.0 on the NI line in Figure 2-22 indicates the ROM on the
network interconnect Option module is version 1.
2.5.1.6 Determining the Revision Levels in the System Module's ROM

The ROM on the System module contains four separate sections of pro
gram code. These sections are the self-test code, console code, VMB code,
and the System exerciser code and all have different internal revision lev
els. Enter TEST 80000050 to see the internal revision levels of the self-test,
console, and VMB code displayed next to the KA410-A in the configuration
table. An example of these three revision levels is shown in Figure 2-27.
The V1.17C is for the self-test revision level, 0BF is for the console revision
level, and VI.0 is for the VMB revision level. The revision level of the system exerciser is shown in the System exerciser display when the exerciser
is running.

Figure 2-27:

Example of the System Module's ROM Code Revision
Levels

>» TEST 80000050

KA410-A VI.17C-OBF-V1.0
ID 08-00-2B-02-CF-A4
MONO

0000. 0001

CLK

0000. 0001

NVR

0000. 0001

Testing and Troubleshooting

2-53

2.5.1.7 Determining the Revision Levels of the Tape Expansion Box's
ROMS

/^m\

The tape expansion box contains two ROMs. One ROM is on the TZK50
Controller board and the other ROM is in the TK50 tape drive. Perform the
following steps to determine the revision levels of these two ROMs.
1.

Power up the tape expansion box.

Unload and remove any COMPACTape cartridge from the TK50 tape
drive.

Enter TEST 73.

Enter 1 when the System prompts with VStmk_QUE_id (1,2,3,4,5,6,7)
?.

Enter 60000001 when the System prompts withVStmk_QUE_RUsure
(1/0) ?.

The screen will scroll fast. Stop the screen from scrolling as soon as the
Information shown in the example in Figure 2-28.

Figure 2-28:

Example of Tape Port Bus Information

receive.diagnostic

command:

IC 00 00 00 50 00

data.in:

05 1E 00 OA FB 00

Status

n>8g_in :

The data.in: line holds the revision levels of the ROMs. Figure 2-29
shows the codes that identify the TZK50 firmware/hardware revision
and the TK50 firmware/hardware revision levels. These revision level
codes are in hexadecimal.

2-54

VAXstation 2000 and MIcroVAX 2000 Maintenance Guide

Figure 2-29:
data.in:

Example of the TZK50 and TK50 ROM Revision Levels
05 1E 00 OA FB 00

'— TK50 firmware revision (251)
- TK50 hardware reviaion (10)
- TZK50 firmware revieion (30)
- TZK50 hardware revision (5)

2.5.2 Setting NVR Default Boot Device
This Utility sets the default boot device in the NVR. There are five boot devices to choose from: DUAO, DUA1, DUA2, MUAO, or ESAO. Figure 2-30

shows an example of changing the default boot device from four periods
(....), no default device to DUA1 (RD53 in the expansion box).

Figure 2-30:

Example of Changing the Default Boot Device

>» TEST 51

? >» DUA1

Enter a carriage return to exit TEST 51 without changing the default boot
device. Enter a period (.) to clear the default boot device from NVR. Enter
the device, such as DUA1, to set the default boot device to that device.

2.5.3 Setting NVR Default Boot Flags
This Utility sets the default boot flags in the NVR. Table 2-14 lists the boot
flags common to all operating Systems. Table 2-15 lists additional boot
flags that the VMS operating System uses. The boot flags in Table 2-15
has additional definitions for other operating Systems. Figure 2-31 shows

y$\

an example of changing the default boot flag from 00000000 to 00000010
(diagnostic boot). Enter a carriage return to exit TEST 52 without changing
the default boot flag.

Testing and Troubleshooting

2-55

Figure 2-31:

Example of Changing the Default Boot Flag

>» TEST 52
00000000 ? >» 00000010
.|

You can specify one or any combination of boot flags in the NVR. To specify
more than one flag, enter the sum value (in hex) of the flags that you want
loaded into the NVR. For example, if you want to specify the RPB$V_DIAG
flag, RPB$V_HALT flag, and the RPB$V_MPM flag, add all three flags as
shown in Figure 2-32 and enter the sum into NVR (TEST 52).
Figure 2-32:

Determlning the NVR Code for Three Boot Flags

RPB$V_DIAG
RPB$V_HALT
RPB$V_MPM

—
—
—

00000010
00000200
00000800

Enter thia code

O0OO0A10

Table 2-14:

Boot Flags Used by VMB for Booting All Operatlng System Software

Flag

00000008

Definition

RPB$V_BBLOCK — This skips the files-11 boot and performs only the
boot block type boot.

00000010

RPB$V DIAG — Dlagnostic boot.

00000020

RPB$V_BOOBPT — Bootstrap breakpolnt. Stops the primary and sec
ondary bootstraps with a breakpoint instruction before testing memory.

00000040

RPB$V_ HEADER — Image header. Takes the transfer address of the sec
ondary bootstrap image from that file's image header. If RPB$V_HEADER
is not set, transfers control to the first byte of the secondary boot file.

00000100

[SYSMA1NTJDIAGBOOT .EXE.

Secondary bootstrap is image called

RPB$V_SOLICT — File name. Prompt for the name of a secondary boot
strap file.

2-56

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Table 2-14 (Cont.):

Boot Flags Used by VMB for Booting
All Operating System Software

Flag

00000200
00001000
X0000000

Table 2-15:

Definition

RPB$V_HALT - Halt before transfer. Executes a halt instruction before

transferring control to the secondary bootstrap.

RPB$V..PFILE - (overlays RPB$V_USEMPM) File name. Prompt for the
name of the parameters file on a network bootstrap Operation.
RPB$V_TOPSYS — The X position spedfies the top level directory number

for System disks with multiple Systems.

Speclfic Boot Flags Used by VMS

Flag

Definition

00000001

RPB$V_CONV — Conversational boot. At various points in the System
boot procedure, the bootstrap code solicits parameters and other input
from the console terminal. If the DIAG is also on, the diagnostic Su
pervisor then enters "MENÜ" mode and prompts the user for devices to
test.

00000002

RPB$V_DEBUG — Debug. If this flag is set, VMS mapa the code for the
XDELTA debugger into the System page tables of the running System.

00000004

RPB$V_INIBPT - Initial breakpoint. If RPB$V_DEBUG is set, VMS ex
ecutes a BPT instruction immediately after enabling mapping.

00000080

RPB$V.NOTEST — Memory test inhibit. Sets a bit in the PFN bit map
for each page of memory present. Does not test the memory.

00000400

RPB$V_NOPFND — No PFN deletion (not implemented; intended to teil
VMB not to read a file from the boot device that identifies bad or reserved
memory pages, so that VMB does not mark these pages as valid in the PFN
bitmap).

00000800

RPB$V_MPM — Specifies that multiport memory is to be used for the
total exec memory requirement. No local memory is to be used. This

is for tightly-coupled multiprocessing. If the DIAG is also on, then the
diagnostic Supervisor enters "AUTOTEST" mode.

00002000
00004000

00008000

00010000

RPB$V_MEMTEST — Specifies that a more extensive algorithm be used

when testing main memory for hardware uncorrectable (RDS) errors.

RPB$V_F1NDMEM — Requests use of MA780 memory if MS780 is insuf-

ficient for booting. Used for 11/782 installations.

RPB$V_AUTOTEST - Used by diagnostic Supervisor.

RPB$V.CRDTEST — Request pages with CRD errors to be removed from

bitmap.

Testing and Troubleshooting

2-57

2.5.4 Setting NVR Default Recovery Action Flags
This Utility sets the recovery action flags in the NVR. The default recovery
action flag is used by the System during power up and also if the System

detects a severe error of its operating environment. There are three flags to
choose from: restart, boot, or halt. Restart searches for the restart parameter
block (RPB) in memory (the RPB contains addresses of certain registers that
hold restart Information). Boot Starts booting the operating System Software.
Halt automatically halts the System and enters console mode. Table 2-16
lists the recovery flags available.

Table 2-16:
Number

Default Recovery Flags

Recovery Action Flag

RESTART

BOOT

HALT

To change the NVR recovery action flag, enter TEST 53. Figure 2-33 shows
an example of changing the flag from 2 (boot) to 3 (HALT). Enter a carriage
return to exit TEST 53 without changing the flag.

Figure 2-33:

Example of Changing the NVR Recovery Action Flags

>» TEST 53
2 ? >» 3

2.5.5 Language Inquiry Menu
This Utility is only available on the VAXstation 2000. This Utility displays the
language inquiry menu on the console device. To choose another language
for the keyboard, enter TEST 54 and select the proper language. Hit the
return key to obtain the console prompt without changing the language.

The terminal on the MicroVAX 2000 has the language menu available in the
setup procedures.

2-58

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

2.5.6 Circle Cross-Hatch Alignment Pattern
This Utility is only available on the VAXstation 2000. This Utility sends the
circle cross-hatch alignment pattern to the monitor connected to the video
port. Enter TEST 60 to display the circle cross-hatch alignment pattern. A
loopback (p/n 29-24795) must be attached to the 25-pin communication port
to run this Utility. Hit the carriage return to stop the display.

2.5.7 Screen of E's Pattern
This Utility is only available on the VAXstation 2000. This Utility sends a füll
screen of E's to the monitor connected to the video port. Enter TEST 61 to
display the screen of E's pattern. Hit the carriage return to stop the display.

2.5.8 White Screen
This Utility is only available on the VAXstation 2000. This Utility sends a füll
white screen to the monitor connected to the video port. Enter TEST 62 to
display the white screen. Hit the carriage return to stop the display.

2.5.9 Mass Storage Disk Formatter
This Utility formats the hard disk drives and RX33 floppy diskettes. The
command to start the formatter is TEST 70. Figure 2-34 shows an example
of running the formatter on DUA0. The procedure shown in Figure 2-34 is
for all Digital hard disk drives. Figure 2-35 shows an example of running
the formatter on an RX33 diskette in DUA2. This formatter cannot format

RX50 diskettes. If the hard disk is not a Digital hard disk drive or if it is
a hard disk drive that the formatter does not recognize, the formatter goes
into a query mode. This query mode allows you to input specific data about
the drive so the formatter can format it. Figure 2-36 shows an example of
formatting an unknown hard disk drive and also explains the data needed
to format the unknown disk drive.

CAUTION: Formatting destroys all user data on the disk or diskette.
To run the formatter, enter TEST 70 then enter the drive number when the
formatter asks, VSfmt_QUE_unitno (0-2) ?
. Enter a 0 for the hard disk
drive in the System box, enter 1 for the hard disk drive in the expansion
box, and enter 2 for a diskette in the floppy drive. If you entered a 0 or 1
for a hard disk, follow Figure 2-34. If you entered 2 for a floppy diskette,
follow Figure 2-35.

Testing and Troubleshooting

2-59

Figure 2-34:

Example of Formatting a Hard Disk Drive

>» TE8T 70

KA410-A

VSfmt_QUE_unitno (0-2) ?
VSfmt_STS_8iz

RDRXfmt

<— Enter drive nurober.
RD32

<— RD32 ia DUAO.

VSfmt_QUE_SerNbr (0-999999999) ? 361

<— Enter a number.

VSfmt_QUE_RUsure (DUAO 1/0) ? 1

<— Enter a 1 for yee,

VSfmt_STS_RdMbb

<--- Manufacturer's bad

0 for no.

block located.
V8fmt_STS_FMTing

<— Disk forraatted OK.

VSfmt.STS.ChkPss

<— Check pass is OK.

VSfmt_STS_BBRvec := 7

<—- Number of bad blocks

VSfmt_RE8_Succ

revectored.

Disk is formatted
aucceasfully.

)

2-60

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Figure 2-35:

Example of Formatting an RX33 Floppy Diskette

>» TEST 70
KA410-A

VSfmt_QUE_unitno (0-2) ?

RDRXfmt
<

Enter drive nuraber.

VSfmt_QUE_RXmedtyp

( 1=RX33 ) ? 1

<-— Enter a 1 if RX33

VSfmt_qUE_RUsure (DUA2 1/0) ? 1

VSfmt_STS_FMTing

Diskette formatted OK.

RX33 format checked OK.

diskette media.
Enter a 1 for yea,

0 for no.

VSfmt.STS.CkRXfmt

VSfmt_RE8_Succ

OK
OK

<— Diskette is formatted

successfully.

Testing and Troubleshooting

2-61

Figure 2-36:

Example of Formatting an Unknown Hard Disk Drive

>» TEST 70
KA410

VSfrat_QUE_unitno

(0-2)

RDRXfmt

VSfmt_STS_Siz

????

Enter drive number.

Unknown diak drive.

VSfmt_STS_EntUIB

Formatter needs

xbnsiz

:■ 54 \SV/

Enter number of tranßfer blocka.

dbnaiz :a 48/^,2}

Enter number of diagnostic blocks.

lbnaiz

:= 83236'-

^Enter number of

logical blocks.

rbnsiz

:= 200

Enter number

replacement blocke.

surpun := 6 (jo)

Enter number of surfacea per unit.

cylpun ;= 820f££OJ

Enter number of cylindera per unit.

wrtprc :- 82O'vv?)

Enter the write precompensation

rctsiz : = 4

\S )

Enter ßize of revectoring control

rctnbr :■ B

(ßj

Enter number of copies of RCT.

secitl := 1

(7)

Enter the sector interleave.

atBßkw :- 2

; /)

Enter the surface to surface skew,

ctcskw :■ 9 (£ I

Enter the cylinder to cylinder skew.

mediai :- 62732TpÖs)

disk

ßpecifics.

cylinder.

table (RCT).

Enter media MSCP ID.

VSfmt_Q,UE_SerNbr

(0-999999999)

VSfmt_QUE_RUBure

(DUAO 1/0)

? 361 <
1

Enter serial number.
Enter a 1 for yes,
0 for no.

VSfmt_STS_RdMbb

Manufacturer'b bad
block

located.

VSfmt_STS_FMTing

Diak formatted

VSfmt.STS^ChkPBB

Check paBB

VSfmt_8TB_BBRvec

:= 2

Number of

OK.

is OK.
bad blocks

revectored.

VSfmt_RES_Succ

Disk

is formatted

auccessfully.

2-62

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

2.5.9.1 Disk Formatter Messages

All messages for the formatter start with VSfmt_. The second segment of
the message indicates the type of message; STS_ for a Status message,
QUE_ for a question that waits for a response, and RES_ for an indication
of a resultant message. Table 2-17 lists all the formatter messages and gives

an explanation for each.
Table 2-17:

Disk Formatter Messages

Fomatter Message

Explanation

VSfmt.STS.ChkPss

A check pass is being done on the disk.

VSfmt_STS_CkRXfmt

The RX33 diskette format is being checked.

VSfmt.STS.EntUIB

The formatter has sized an unknown disk and will
prompt you to input information about the disk.

VSfmt.STS.FMTing

The disk is being formatted.

VSfmt.STS.RdMbb

The manufacturer's bad block is being located.

VSfmt.STS.RXfmt

The RX33 diskette is being formatted.

VSfmt.STS.Siz

The hard disk selected is being sized.

VSfmt.QUE.RUsure (DUA# 1/0) ?

The formatter uses this question as a safety check.

If you want to format the disk or diskette that is
indicated by the #, enter 1 for yes. Otherwise,
enter any character other than 1 to abort the for
matter.

VSfmt_QUE_SerNbr (0-999999999) ?

Enter a number for the hard disk you are formatting. The number can be any number from
0 to 999999999. This number should be the serial
number of the drive, but does not have to be. You
can enter a 0 for DUAO and a 1 for DUA1, but any
number will do.

VSfmt_QUE_unitno (0-2) ?

Enter the drive that needs formatting. Enter 0 for
DUAO, 1 for DU AI, and 2 for DUA2. Any other
character aborts the formatier.

VSfmt.RES.Succ

The disk has been successfully formatted.

VSfmt.RES.Abtd

The RDRX formatter has been aborted.

VSfmt.RES.ERR §

The formatter has been stopped because of the error code indicated by the #.

Table 2-18 lists the

error codes.

Testing and Troubleshooting

2-63

Table 2-18:
Code

Error Codes for the Disk Formatter

Description

Illegal unit number entered.

Error occurred during the RD autosizer. Either disk is not a Digital disk or the

disk is bad.

Error occurred during formatting.

Error occurred during the hard disk check pass.

Error occurred during the floppy disk check pass.

No diskette loaded in the floppy drive or the diskette is not RX33 media.

2.5.10 Mass Storage Disk Verifier
This Utility verifies the hard disk formats. It does not verify the diskette
formats nor does it destroy data on the disks. The command to Start the
verifier is TEST 71. Figure 2-37 shows an example of running the formatter
on DUAl.

To run the verifier, enter TEST 71, then enter the drive number when the
verifier asks, VSmsv_QUE_unitno (0-1) ?
. Enter a 0 for the hard disk
drive in the System box or enter 1 for the hard disk drive in the expansion
box.

Figure 2-37:

Example of Running the Disk Verifier on DUA1

>» TEST 71
KA41O-A

VSmflv_QUE_unitno (0-1) ?
VSmsv_STS_Siz

RD53

RDver

Enter drive number.

Drive being eized.

VSmsv_QUE_RU8ure (DUAl 1/0) ? 1

<—- Enter a 1 for yes,

VSmsv_STS_RDing

Read pass finished OK.

VSmsv_8TS_0BBcnt = 16

Old bad block count.

VSmav_STS_NBBcnt = 0

New bad block count.

VSmsv_RES_Succ

Disk verified

0 for no.
OK

successfully.

2-64

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

2.5.10.1 Disk Verifier Messages
All messages for the verifier Start with VSmsv_. The second segment of
the message indicates the type of message. STS_ for a Status message,
QUE_ for a question that waits for a response, and RES_ for an indication
of a resultant message.Table 2-19 lists all the verifier messages and gives
an explanation for each.

Table 2-19:

Disk Verifier Messages

Verifier Message

Explanation

VSmsv_STS_NBBcnt

The verifier lists the new bad block count since
the last time the disk was formatted.

VSmsv_STS_NBBpo3

The verifier lists the new bad block locations if
any new bad blocks are found. It lists the cylinder
number, surface, and the sector.

VSmsv_STS_OBBcnt

The verifier lists the old bad block count.

VSmsv.STS.RDing

The verifier is reading the disk.

VSmsv.STS.Siz

The hard disk selected is being sized.

VSmsv.QUE.RUsure (DUA# 1/0) ?

The verifier uses this question as a safety check,
lf you want to verify the disk indicated by the #,
enter 1 for yes. Otherwise, enter any character
other than 1 to abort the verifier.

VSmsv.QUE.unitno (0-1) ?

Enter the drive that you are verifying.

Enter 0

for DUAO or a 1 for DUA1. Any other character

aborts the verifier.
VSmsv_RES_Succ

The disk has been successfully verified.

VSmsv.RES.Abtd

The RD verifier has been aborted.

VSmsv.RES.ERR #

The verifier has been stopped because of the error
code indicated by the ». Table 2-20 lists the error
codes.

Table 2-20:
Code

Error Codes for the Disk Verifier

Descriptlon

Illegal unit number entered.

Error occurred during the RD autosizer. The disk may not be formatted.

Error reading the revectored block control table (RCT)

Testing and Troubleshooting

2-65

2.5.11 Special Diagnostic Key for Field Service System

Exerciser
The removable media in the maintenance kit contains a Special diagnostic
code on it that allows the System exerciser to write on this media when run-

ning in field Service mode. Without this Special coding, such as on normal

/-s**^

There are two Utilities that create these special-keys for the floppy diskette
and TK50 COMPACTapes. TEST 72 creates a special-key on the floppy
diskette and TEST 73 creates a special-key on the TK50 COMPACTape. The
diskette and COMPACTape in the maintenance kit must be initialized with
these Special diagnostic keys before they can be used. The COMPACTape
must be initialized every time you use it with the field Service System exer
ciser, because the Special diagnostic key on the COMPACTape is destroyed
once the exerciser recognizes the key. The Special diagnostic key on the
floppy diskette is not destroyed when it is used. Figure 2-38 shows a successrul example of creating a special-key floppy diskette. Figure 2-39 shows
a successful example of creating a special-key COMPACTape cartridge. If
any errors occur while running TEST 72 or TEST 73, make sure the drive
is on-line and operating properly and run the special-key command again.
Also, make sure the COMPACTape is not write protected.

^«^

customer media, the System exerciser does not do write testing on the removable media devices. This safety fearure prevents accidentally destroying
the customers programed floppy diskettes or TK50 COMPACTapes.

Figure 2-38:

Example of Creating the Special Key on a Floppy Diskette

>» TEST 72
KA410-A RXmker

VSfmk_QUE_MEDtyp (0-RX50)

(1°RX33) ? 0

<— Enter media type.

VSfmk_QUE_RUsure (DUA2 1/0) ? 1

<--- Enter 1 for yes,

VSfmk_RES_SUCC

<— Keyed successfully.

0 for no.

2-66

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Figure 2-39:

Example of Creating the Special Key on a COMPACTape
Cartridge

>» TEST 73
KA41O-A TPmker

VStmk_QUE_id (1.2,3,4,5,6,7) ? 1

<— Enter ID address of drive.

VStmk_QUE_RUsure (1/0) ? 1

Enter 1 for yes, 0 for no.

VStmk

Keyed auccessfully.

2.5.12 ThinWire Network Loop Testing Utility

jtfßms
f

This Utility enables a ThinWire Ethernet network loop test or System ID
procedure to verify correct Operation of the ThinWire Ethernet port. It sets
up the System to loopback Thinwire Ethernet data packets from another
node which uses troubleshootine Software such as NIE, Ethernim, UETP, or
NCP loop testing. This troubleshooting Software does Ethernet loop testing
at various levels: firmware/hardware loop testing, protocol loop testing,
operating System loop testing, and application loop testing. The level this
Utility works on is the firmware/hardware loop testing. You use this Utility
if booting over the network fails or if other levels of loopback testing fail.
The other levels of loopback testing do not need to use this Utility.
To run this Utility, halt the System and enter console mode. Once in console
mode, enter TEST 90 to Start the Utility. The screen blanks then displays _E_

net$_util followed by the Ethernet address of the System. Now the System
is ready to respond to the network loopback commands issued from any
other node on the network (typically the host System). Once TEST 90 is
entered, nothing more can be done on this System since this System is now
acting like a loopback connector. All loopback commands must be sent
from another node on the network.

/g§s?\
f

When a loopback data packet is received from another node, the System
checks for errors and extracts the Ethernet address of the next node that
this packet must be sent to. The Ethernet address of the next node that
this System is sending the loopback packet to is displayed on the screen.
Most likely, the Ethernet address displayed on the screen will be the node
that sent the packet, but some troubleshooting Software have the capability
to do three or more node loopback testing. Once all loopback testing is
complete, enter a carriage return to get a report on the Status of the loopback

Testing and Troubleshooting

2-67

testing. Enter a ICTRL/Cl to exit TEST 90 and return to the console prompt.
Figure 2-40 shows an example of the report. Table 2-21 Üsts the definitions
of each item in the report.
Figure 2-40:

Example of ThinWire Ethernet Loop Testing Using TEST
90

>» TEST 90

_E_net$_util
ID 08-00-2B-02-CF-A4

<— Ethernet address of this node

08-00-2B-03-CF-A8

<— Ethernet address of next node

req$_num

- 0

tx$_cnt
rx$_cnt
mxcst$_cnt

- 0

r_err

- 0

r.fram
r_crc

Enter a carridge

sysid$_cnt

- 0

jnk$_pkts

- 0

r_oflo

- 0

r.buff

- 0

t_err

- 0

t_more

- 0

t_one

- 0

t_def

- 0

t.buff

- 0

t.uflo

- 0

t.lcol

- 0

t_lcar

- 0

t_rtry

- 0

hng$_tx

- 0

s_err

- 0

s.babl

- 0

s_cerr

- 0

s.miss

- 0

8_raerr

- 0

2-68

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

.%V

Table 2-21:

ThinWire Ethernet Loopback Test Report Definitions

Item

Definition

req$_num

System ID request response sent

sysid$_cnt

Unsolicited System ID's sent

tx$_cnt

Packeis transmitted

rx$_cnt

Packets received

mxcst$_cnt

Multicast or broadcast packets received

jnk$_pkts

Packets received with bad format

r_err

Total receive errors detected by lance

r.fram

Receive framing error

r.oflo

Receive F1FO overflow error

r.crc

Receive crc error

r.buff

Receive buffer in chain not available error

t_err

Total transmit errors detected by lance

t.more

Transmits with more than one collision

t.one

Transmits with one collision

t.def

Transmits defer red

t.buff

Transmit buffer not available error

t_uflo

Transmit FIFO underflow error

t.lcol

Transmita with late collision error

t.lcar

Transmit loss of carrier error

t.rtry

Transmit maximum retry error

hng$_tx

Transmit failed to complete error

B_err

Total errors reported in CSRO of lance

3_babl

Babble error

8_cerr

Collision check (heartbeat) error
Mlssed packet, no buffer available

s_merr

DMA memory access or memory parity error

Testing and Troubleshooting

2-69

Chapter 3

FRU REMOVAL AND REPLACEMENT
PROCEDURES
3.1

Introducfion

This chapter describes the removal and replacement procedures for the

field replaceable units (FRUs). To use this chapter, find the name of the
FRU that needs replacing in Table 3-1 then go to the section listed beside
the FRU. Follow the Steps in the section to remove the FRU and reverse
the procedures to replace the FRU.

Table 3-1:

FRU Section Listings

FRU

[

Section

Page

Battery pack

3.10

3-33

DEC423 Converter (MicroVAX 2000 only)

3.15.1

3-53

Expansion adapter

3.16

3-54

Expansion adapter disk interface module

3.16.1

3-56

Hard disk expansion box

3.17.1

3-58

Keyboard (VAXstation 2000 only)

3.13

3-51

Memory module

3.5

3-17

Mouse (VAXstation 2000 only)

3.14

3-52

Network interconnect module

3.6

3-18

Power supply in hard disk expansion box

3.17.1.2

3-66

Power supply in System box

3.11

3-64

Power supply in tape drive expansion box

3.17.2.3

3-79

RD32 disk drive

3.8

3-24

RD32 disk drive device electronics board

3.8.1

3-27

3-1

Table 3-1 (Cont.):

FRU Sectlon Listings

FRU

Sectlon

Page

RD53 disk drive

3.7

3-19

RD53 disk drive device electronics board

3.7.1

3-21

RD53 disk drive in hard disk expansion box

3.17.1.1

3-60

Resistor load board in hard disk expansion box

3.17.1.3

3-70

Resistor load board in system box

3.9

3-31

Resistor load board in tape drive expnnsion box

3.17.2.4

3-81

RX33 floppy disk drive

3.8

3-24

System module

3.4

3-13

Tablet (VAXstation 2000 only)

3.14

3-52

Tape drive expansion box

3.17.2

3-72

Terminal disconnection from MicroVAX 2000

3.15

3-53

TK50 tape drive in tape drive expansion box

3.17.2.2

3-76

TZK50 Controller board in tape drive expansion box

3.17.2.1

3-73

VR260 deflection board

3.12.2

3-39

VR260 monochrome monitor

3.12

3-35

VR260 power LED

3.12.7

3-50

VR260 rear bulkhead assembly

3.12.3

3-42

VR260 transformer assembly

3.12.5

3-45

VR260 video board

3.12.4

3-44

VR260 tube/yoke/bezel assembly

3.12.6

3-47

3-2

Figure 3-1 shows the locations of the FRUs as seen from the front.
Figure 3-1:

FRU Locations

SYSTEM MODULE
MEMORY MODULE
RX33

ThinWire Ethernet MODULE

OR RD53

POWER SUPPLY

RD32

EXPANSION ADAPTER

DISK INTERFACE MODULE

VAXstation 2000 AND MicroVAX 2000 SYSTEM BOX

POWER

TK5O

SUPPLY

RD53

POWER
SUPPLY

VAXstation 2000 ANO MicroVAX 2000 EXPANSION BOXES

MRI186-1275
MA-OI33-87

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-3

3.2 Shield Removal
1.

Turn the System power switch off and disconnect all cables from the
rear of the System box.

If the System is a MicroVAX 2000, remove the DEC423 Converter from
the rear of the System box.

If the expansion adapter is installed, then remove the two screws shown

in Figure 3-2 on the bottom of the expansion adapter to access the four
screws securing the System box cover.

Figure 3-2:

Expansion Adapter Cover Screw Locations

MRlia6l27S
MA-0O69-S7

3-4

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Remove the four System box cover screws shown in Figure 3-3.

Figure 3-3:

System Box Cover Screw Locations

MR-1186-1277
MA-0070-87

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-5

Slide the cover off the System box as shown in Figure 3-4.

Figure 3-4:

System Box Cover Removal

MR-t 188-1278
MAOO71B7

3-6

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Put the System on its feet and remove the five screws shown in Figure
3-5 from the shield.

Figure 3-5:

Shield Screw Locations

/0\

MA-1tSa-l27S
MA-OOJIO;

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-7

Lift the shield as shown in Figure 3-6 and rest it on the rear of the
System.

Figure 3-6:

Removing the Shield from the Main Chassis

MR-11BS-I28O
MA-0073-87

/*®®$\

3-8

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Hold the shield with one hand and disconnect the power cable and the

drive interconnect cable(s) from the shield with the other hand. Refer
to Figure 3-7.

Figure 3-7:

Disconnecting the Cables from the Shield

Lift the shield off the main chassis.

10. Return to the FRU removal instructions that sent you to this procedure.

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-9

3.3 System Module Assembly Removal from
Shield
1.

Remove the two screws shown in Figure 3-8 from the shield.

Figure 3-8:

System Module Assembly Screw Locations on the Shield

MR-tltS-1382

MA-OO7S-B7

3-10

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Disconnect the two network interconnect cable9 shown in Figure 3-9
(if installed).

Figure 3-9:

Network Interconnect Cables

MfM18Ö-12Ö3

^iff^SSfV

MA-OO7B-07

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-11

Remove the System module assembly from the shield as shown in Figure 3-10 and lay it down beside the shield.

CAUTION: Disconnection of the battery cable from the System module destroys
all NVR memory. Be careful not to disconnect the battery cable from the System

module until a procedure specifically instructs you to do so.

Figure 3-10:

Removing System Module Assembly from Shield

M Hl 188-1284

MA-0077-87

3-12

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

3.4 System Module Removal
1.

Remove the shield (Paragraph 3.2).

Remove the System module assembly from the shield (Paragraph 3.3).

Disconnect the battery cable from the System module. Refer to Figure
3-11.

Figure 3-11:

Battery Cable Location

MR-1186-1296
MA-OO7B-8?

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-13

Remove the memory module (if installed). Refer to Figure 3-12. Two
connectors disconnect as you lift the memory module.

Figure 3-12:

Memory Module Removal

Remove the two network interconnect cables from the System module
and install them on the new System module.

3-14

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Remove the network ID ROM shown in Figure 3-13 from the System
module you are removing and install it on the System module you are

installing.

Figure 3-13:

Network ID ROM Location on System Module

MB-I1B8-1JS3
MA-OOeO-87

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-15

You must set the System jumper, shown in Figure 3-14, for either a
VAXstation 2000 or a MicroVAX 2000. Both Systems use the same system module and this System jumper teils the firmware whether the mod
ule is in a VAXstation 2000 or a MicroVAX 2000. Determine which system you are working on and set the jumper accordingly.

Figure 3-14:

VAXstation 2000 and MicroVAX 2000 System Jumper

VAXstation 2000
SYSTEM JUMPER

MicroVAX 2OOO
SYSTEM JUMPER

MH-I2B6-14M

Install the new System module by reversing the above procedures.

3-16

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

,"-

[

3.5 Memory Module Removal
1.

Remove the shield (Paragraph 3.2)

Remove the System module assembly from the shield (Paragraph 3.3)

Remove the memory module shown in Figure 3-15 Two connectors
disconnect as you lift the module.

Figure 3-15:

Memory Module Removal

Replace the memory module by reversing the above procedures.

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-17

3.6 Network Interconnect Module Removal
1.

Remove the shield (Paragraph 3.2)

Remove the System module assembly from the shield (Paragraph 3.3)

Remove the network interconnect module from the shield as shown in
Figure 3-16.

Figure 3-16:

Network Interconnect Module Removal

Replace the network interconnect module by reversing the above procedures.

3-18

VAXstatlon 2000 and MicroVAX 2000 Maintenance Guide

3.7 RD53 Hard Disk Drive Removal from System
Box
j$

Remove the shield (Paragraph 3.2).

Remove the three screws shown in Figure 3-17 that secure the drive to
the chassis.

Figure 3-17:

Hard Disk Screw Locations

MR-1186-1290
MA 0083-87

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-19

Slide the drive out halfway and disconnect the drive interconnect cables
and the power cable from the drive as shown in Figure 3-18.

Figure 3-18:

Disconnecting the Hard Disk Drive from System Box

MB-l 188-1291

Slide the drive out of the chassis.

3-20

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

/^%

Remove two screws on each side of the drive mounting brackets shown
in Figure 3-19. Remove the mounting brackets and front panels from
the drive.

Figure 3-19:

Drive Mounting Bracket Screw Locations

MR-UB6I292
MA 0084 87

If you removed the RD53 because of an error with the drive, go to
Paragraph 3.7.1.

Reverse the above procedures to replace the drive.

3.7.1 RD53 Disk Drive Device Electronics Board Removal
The RD53 disk drive has an FRU inside it. It is the device electronics board.
Always replace the device electronics board on the RD53 before you replace
an entire RD53 disk drive.
1.

If a skid plate is installed on the drive, remove the four phillips screws

securing the skid plate and ground clip to the frame. Remove the plate

and set aside.

Loosen the two captive screws that hold the device electronics board in
place and then disconnect the ground wire.

xpWSK

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-21

Rotate the board upward as shown in Figure 3-20 (the board pivots in
hinged slots at the front of the drive). Be careful not to strain any of
the connectors or cables, and tilt the board up and back until it rests
against the outer frame.

CAUTION: Flexible cirant material is fragile and requires careful handling to
avoid damage.

Figure 3-20:

RD53 Device Electronics Board Removal

DEVICE ELECTRONICS
BOARD

MOTOR CONTROL BOARD

SCREWS. MOTOR
CONTROL BOARD

PREAMPLIFIER BOARD
ANDSHIELD

SCREWS. BEZEL

Disconnect the two connectors from under the device electronics board.
Both connectors and cables are fragile, handle them with care.

Lift the board out of the hinged slots.

3-22

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Position the jumpers and Switches on the new board to the same posi-

tion as the jumpers and Switches on the old board you just removed.

Refer to Figure 3-21. Also be sure the new board has the resistor ter-

minator pack installed.
0\

Figure 3-21:

RD53 Device Electronics Board Jumper and Switch Locations

COMPONENTSIDE

yf^^

PIN 1

D
CZ1

Install the replacement device eiectronics board by reversing the above
procedure.

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-23

3.8 RX33 and RD32 Drive Removal (Half-Height
Drives) from the System Box
1.

Remove the shield (Paragraph 3.2).

Remove the three screws shown in Figure 3-22 that hold the drive(s) to
the chassis.

Figure 3-22:

Half-Height Drive(s) Screw Locations

3-24

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

3.
<

Slide the drive(s) out halfway and disconnect the drive interconnect
cable(s) and the power cable(s) from the drive(s). Refer to Figure 3-23.

Figure 3-23:

Disconnecting the RX33 and RD32 Half-Height Drives

Slide the drive(s) out of the chassis.

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-25

Remove four screws on each side of the mounting brackets shown in
Figure 3-24. Remove the mounting brackets and front panels from the
drive(s).

Figure 3-24:

Half-Height Drives Mounting Brackets Removal

MR-1168-1294
MAOOB7-87

If you are replacing the RX33 floppy drive, install the new RX33 by
reversing the above procedures.

If you removed the RD32 because of an error with the drive, go to

Paragraph 3.8.1 below. Then reverse the above procedure to reinstall
the drive.

3-26

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

3.8.1 RD32 Disk Drive Device Electronics Board Removal
The RD32 disk drive has an FRU inside it. It is the device electronics board.
Always replace the device electronics board on the RD32 before you replace
an entire RD32 disk drive.

CAUTION: Do not remove any of the screws that secure the cover (cover/ßter
assembly) to the base casting. Removing any of the screws violates the clean area.
1.

Remove the three flat head screws shown in Figure 3-25 that hold the
device electronics board in place under the drive unit. Besure to locate
the one screw with the nylon washer next to the drive motor when
replaceing the board.

Figure 3-25:

RD32 Device Electronics Board Screw Locations

CAUTION: MAKE SURE YOU REMOVE THE DEVICE
PRINTEDCIRCUIT BOARD WASHER. A
WASHER ACCIDENTALLY DROPPED IN THE
DISK DRIVE COULD DAMAGE THE DRIVE.
NOTE: IF IT IS NECESSARY TO REPLACE ANY OF THE
DEVICE ELECTRONICS BOARD SCREWS, THESE
MOUNTING SCREWS MUST NOT EXTEND MORE
THAN 0.64 CM (0.25 IN) INSIDE THE DRIVE.

SMR-039BB0

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-27

Disconnect the cable from J4 (middle of board) as shown in Figure 3-26.
The J4 connector is not keyed and can be reconnected incorrectly. Make
sure the violet and yellow wire in the connector is located near the LED
and the orange and blue wires are located toward the outer edge of the
board when reconnecting J4.

Figure 3-26:

Disconnecting J4 from RD32 Device Electronics Board

LJ 0090

SHFI-0297-86

Stand the board up. Be careful not to strain any of the connectors or
cables, and tilt the board over center until it rests against the outer
frame.

CAUTION: Flexible circuit material is fragile and requires careful handling to
avoid damage.

3-28

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Disconnect the cables from J6 and J5 as shown in Figure 3-27 from
the device electronics board. Both connectors and cables are fragile—
handle them with care.

Figure 3-27:

Disconnecting J5 and J6 from RD32 Device Electronics
Board

LJ069S
SHR0290 00

Remove the device electronics board from the RD32.

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-29

Position the jumper on the new board to the same position as the jumper
on the old board you just removed (Figure 3-28). Also be sure the new
board has the resistor termination pack installed.

Figure 3-28:

RD32 Device Electronics Board Jumper Location

J7-16PINCONNECTOR

IORIVE CONFIGURATION)

SHOWN WITH DRIVE CONFIGURED AS DS-1

Replace the new device electronics board by reversing the above procedures.

3-30

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

3.9 Resistor Load Board Removal from System
Box
The resistor load board loads down the power supply in a diskless System
or when just the RX33 floppy drive is installed in the System box. The

power supply does not have enough of a load on it to regulate properly
in these configurations. The load board simulates the drives by drawing
enough power to regulate the power supply. You must remove the load
board whenever a hard disk drive is installed in the System box.
The resistor load board in the System box is different from the resistor load
board in the expansion boxes. The part number of the resistor load board in
the System box must be 5417163-02. The -01 version goes in the expansion
boxes.
1.

Remove the shield (Paragraph 3.2).

Remove the three screws shown in Figure 3-29 that secure the drive
mounting bracket to the chassis.

Disconnect the power cable from the resistor load board.

Lift the load board up and out of the chassis.

If you are removing the load board to install a drive, remove and discard the standoffs that the load board sat on, then install the drive by
reversing the removal instructions for that drive. Otherwise, install the
new load board (p/n 5417163-02) by reversing the above procedures.

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-31

Figure 3-29:

Drive Mounting Bracket Screw Locations

MB- II88-1295
MA-011887

3-32

VAXstatJon 2000 and MicroVAX 2000 Maintenance Guide

3.10 Battery Pack Removal
1.

Remove the 9hield (Paragraph 3.2).

Remove the System module assembly from the shield (Paragraph 3.3)

Disconnect the battery cable from the System module.

Figure 3-30:

Battery Cable Location

MA-1ISS-12M

Take the battery pack out of its holder.

Replace the battery pack by reversing the above procedures.

NOTE: A new battery needs a minimttm of 25 hours of continous power on to
fully Charge the battery. If the battery's Charge fs low, you will see an error for
the NVR when you power up the System.

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-33

3.11 Power Supply Removal from the System
Box
1.

Remove the shield (Paragraph 3.2).

Disconnect the power cables from the rear of the drives. If you need
more room behind the drives, remove the three drive mounting screws
and slide the drives out part way.

Put the System on its side and remove the four screws shown in Figure
3-31 that hold the power supply to the bottom of the chassis.

Figure 3-31:

Power Supply Screw Locations in the System Box

MR-1189-1207
MAOI27-87

3-34

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Slide the power supply out of the chassis.

Replace the power supply by reversing the above procedures.

3.12 VAXstation 2000 VR260 Monochrome
Monitor
You may need the following tools to repair the VR260 Monitor.
•

Phillips screwdriver

•

Slotted screwdriver

•

High-voltage discharge tool (p/n 29-24717)

Figure 3-32 shows the FRUs in the VR260 monitor.

Figure 3-32:

VR260 FRU Locations

REAR

BULKHEAD

VIDEO

BOARD

TUBE/YOKE/BEZEL

ASSEMBLY

MR-1OBB-1255
MA0088-8?

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-35

3.12.1 VR260 Cover
1.

Switch the monitor power switch off.

Disconnect the power cord and video cable from the monitor. Refer to
Figure 3-33.

Figure 3-33:

VR260 Controls and Video Cable Locations

POWER ON/OFF
SWITCH

AC POWER INPUT

CONNECTOR

VOLTAGESELECT
SWITCH
COMPOSITE VIDEO
BNC CONNECTOR

FUSE

REAR VIEW
MA.7167.83

Carefully place the monitor on its face.

Loosen the four rubber feet on the bottom.

Slide the tilt-swivel base up and off the monitor.

Finish unscrewing the four rubber feet and remove them from the mon
itor.

3-36

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Remove the four phillips cover screws shown in Figure 3-34 from the
rear of the monitor.

Figure 3-34:

VR260 Cover Screw Locations

MR-10aa-1253

Lift the cover off.

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-37

Lift the rear bezel off. Refer to Figure 3-35.

Figure 3-35:

VR260 Rear Bezel Location
REAR BEZEL

MR-108S-I24B
MAOO90-87

10. Place the monitor back down to its normal position.
11. Reverse the above procedures to replace the cover.

3-38

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

3.12.2 VR260 Deflection Board Removal
The deflection board is mounted inside the chassis door.
1.

Remove the monitor cover (Paragraph 3.12.1)

Loosen the two 1/4-turn fasteners on the chassis door, and open the
door. Refer to Figure 3-36.

Figure 3-36:

VR260 Side Door Screw Locations

SCREWS

SIOE DOOR

MR-1086-1239
MA0O9I-B7

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-39

Discharge and disconnect the high-voltage anode wire from the cathode
ray tube (CRT) as follows.

•
•

Make sure the monitor's power switch is off.
Ground the high-voltage discharge tool (p/n 29-24717) to the tension
band or the chassis.

•

Insert the high-voltage discharge tool under the anode cap on the
CRT and make contact with the anode clip. Refer to Figure 3-37.

Figure 3-37:

High-Voltage Discharge Tool

MA 0704-35

•

Remove the discharge tool from the monitor.

•

Disconnect the high-voltage anode wire from the CRT by squeezing
the metal clips inside the cap.

3-40

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

/S^N

Disconnect the following cables from the deflection board.
Figure 3-38 for cable location.
•

CRT yoke (J3)

•

Power transformer (Jl, blue and green wires)

•

Slip-on ground (J4)

•

Video board (J5, red and orange wires)

•

Video board (J2)

Figure 3-38:

Refer to

VR260 Deflection Board
J1 TO
TRANSFORMER

J4 GROUND

HIGH-VOLTAGE
ANODE WIRE

MR-11B6-I323
MA-013087

Remove the deflection board from the six plastic clips on the chassis
door.

Reverse the above procedures to replace the deflection board.

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-41

3.12.3 VR260 Rear Bulkhead Assembly

Remove the monitor cover (Paragraph 3.12.1).

Carefully place the monitor on its face.

Loosen the six keyhole screws shown in Figure 3-39 on the rear bulk
head assembly.

Figure 3-39:

VR260 Rear Bulkhead Screw Locations

MR-1O86I2SI
MAOO92-B7

Slide the rear bulkhead assembly up and off.

3-42

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Disconnect the video wire from under the video board Refer to Figure
3-40.
6

Figure 3-40:

VR260 Rear Bulkhead

GROUND

TO TRANSFORMER
ASSEMBLY

TO VIDEO BOARD
MR-10861259
MA-0093-87

Disconnect the cable from the transformer assembly.

Disconnect the grounding strap.

CAUTION: Be sure to reconnect the grounding strap when replacing the rear

bulkhead assembly.

Reverse the above procedures to replace the rear bulkhead.

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-43

3.12.4 VR260 Video Board Removal
1.

Remove the monitor cover (Paragraph 3.12.1).

Remove the rear bulkhead assembly (Paragraph 3.12.3).

Release the video board from the three standoffs by pressing in on the
standoffs and lifting the video board.

Refer to Figure 3-41 and disconnect the following cables from the video
board.

•

Deflection board 012)

•

Deflection board (J9)

•

3-Wire cable (J6)

•

2-Wire cable (J7)

•

Ground wire (J8, double clip)

3-44

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Figure3-41:

VR260 Video Board

J6I3-W1RECABLE)
^\

J12 TO DEFLECTION BOARD

J8 TO GROUND
(DOUBLE CLIP)

J9 TO DEFLECTION
BOARD

J7(2WIRECABLE)

MR-1086-1258
MA 0129-8?

NOTE:

Wlten replacing the video board, be sure to match the keyed CRT socket

on the video board to the pins of the CRT. Squeeze the standoffs while pressing

the board onto the CRT.
5.

Reverse the above procedures to replace the video board.

3.12.5 VR260 Transformer Assembly
1.

Remove the monitor cover (Paragraph 3.12.1).

Remove the rear bulkhead assembly (Paragraph 3.12.3).

Remove the video board (Paragraph 3.12.4).

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-45

Disconnect the 2-wire cable from the deflection board (Jl) and remove
this 2-wire cable from the plastic clips (3) on the chassis. Refer to Figure
3-42.

Figure 3-42:

VR260 Transformer Assembly

TO REAR BULKHEAD

TO DEFLECTION

BOARD (Jl)
Mn-1086-1256
MA0034-87

CAUTION: Make sure the transformer does not drop onto the CRT while you
remove the four screws in the next step.

Remove the four screws holding the transformer assembly to the bottom

Reverse the above procedure to replace the transformer assembly.

of the chassis.

3-46

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

3.12.6 VR260 Tube/Yoke/Bezel Assembly Removal
The tube/yoke/bezel assembly is made up of the CRT, yoke, and front bezel
subassemblies.

Remove the monitor cover (Paragraph 3.12.1).

Remove the deflection board (Paragraph 3.12.2).

Remove the rear bulkhead assembly (Paragraph 3.12.3).

Remove the video board (Paragraph 3.12.4). Put the cable from J12 on
the video board aside or leave it connected to the video board so it will
not get misplaced.

If the tube/yoke/bezel assembly has a braided ground strap attached to
the tension band, then remove it from the chassis by unscrewing the

grounding screw on the chassis, not from the tension band. The braided
ground strap stays connected to the tension band. Unscrew any other
braided grounding Straps from the chassis.

Loosen the middle screws and remove the two outer screws as shown
in Figure 3-43. Do this for both sides of the chassis.

Figure 3-43:

VR260 Tube/Yoke/Bezel Assembly Screw Locations

REMOVE

LOOSEN

RFlUinVF
REMOVE /

MR-1086-1237
MA-009587

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-47

Lift the chassis from the tube/yoke/bezel assembly.

Place the new tube/yoke/bezel assembly face down and reverse the
above procedures to replace the tube/yoke/bezel assembly.

CAUTION: The cable behveen the deflecHon board (J2) and the video board (J9)
must be connected to the proper locations as shown in Figure 3-44. Ifyou were
to connect it backwards, (that is, the LED connector end to the video board) the
green LED zviü not light when poiver is turned on,
Figure 3-44:

VR260 Tube/Yoke/Bezel Assembly's LED Cable

MR-1O86-I257

Figure 3-45 shows the cable connections for the VR260 monochrome monitor.

3-48

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

■n

o
c

O
O

JJ
m

>
Z

Figure 3-45:

VR260 Cable Connections

ASSEMBLY

TRANSFORMER

BRIGHT. •■ CONTR.
CONTROL

MA-009'-»

MH-1086-1200

3.12.7 VR260 LED Assembly
Use a small-bladed screwdriver or a similar tool for the following procedure.

Carefully pry the LED/bezel assembly off the monitor. Refer to Figure
3-46.

Figure 3-46:

VR260 LED/Bezel Assembly

Disconnect the LED wires.

To replace the LED/bezel assembly, do the following.

Connect the LED wires to the LED/bezel assembly. The black wire is
connected to the notched connector leg.

Remove the protective paper backing from the double-sided tape on
the LED/bezel assembly.

Press the LED/bezel assembly in place.

3-50

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

3.13 Keyboard Removal (VAXstation 2000 only)
1.

Unplug the keyboard cable from the rear of the monitor. Refer to Figure 3-47.

NOTE: The keyboard is a Single FRU. Do not try to remove the keycaps or
disassemble the keyboard.
Figure 3-47:

Disconnecting the Keyboard (VAXstation 2000)

Mnitea-1332
MA0098BJ

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-51

3.14 Mouse and Tablet (VAXstation 2000 only)
1.

Disconnect the mouse or tablet from the monitor's cable. Refer to Figure 3-48.
NOTE: The mouse and the tablet are Single FRUs. Do not try to disassemble
them.

Figure 3-48:

Disconnecting the Mouse or Tablet (VAXstation 2000)

WfMI8OU33
MAOOttl)

3-52

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

3.15 Terminal Disconnection from MicroVAX 2000
1.

2.
3.

Switch off the terminal's power switch.

Disconnect the cable from the COMM connector on the back of the

terminal.

Refer to the terminal's pocket Service guide for troubleshooting and
removal and replacement procedures for the terminal.

3.15.1 DEC423 Converter Removal from MicroVAX 2000
1.

Switch off MicroVAX 2000's power.

Unscrew two screws on the bottom of the DEC423 Converter as shown
in Figure 3-49 and remove the DEC423 Converter from the back of the
MicroVAX 2000 System box.

Figure 3-49:

DEC423 Converter's Mounting Screw Locations

MR-1 136-1300
MA 0159 87

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-53

One at a time, disconnect the cables from the Converter you are remov-

ing and reconnect them to the same connectors on the new Converter.

Connect the new Converter to the back of the MicroVAX 2000 System
box and screw in the two mounting screws.

3.16 Expansion Adapter Removal
The expansion adapter is not an FRU. There is one FRU module located
inside the expansion adapter called the disk interface module. There is
also an interface cable for the tape drive expansion box that passes through
the expansion adapter and attaches directly to connector A on the back
of the expansion adapter. Removal procedures for the expansion adapter
are below. The removal and replacement Information for the disk interface
module is in Paragraph 3.16.1.
1.

Remove the shield (Paragraph 3.2)

Remove the four screws shown in Figure 3-50 that hold the expansion
adapter to the bottom of the System.

Figure 3-50:

Expansion Adapter Screws

MR-1180-1302
MA0I00B7

/^ik

3-54

VAXstation 2000 and MIcroVAX 2000 Maintenance Guide

Disconnect the disk expansion cables from the disk interface module.

Refer to Figure 3-51.

Figure 3-51:

Expansion Cables Locations

TAPE PORT CONNECTOR

MR-11SS-1334

Unscrew the tape port connector from the expansion adapter.

Replace the expansion adapter by reversing the above procedures.

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-55

3.16.1 Expansion Adapter Disk Interface Module
Removal
1.

Switch off power to the System.

Put the System box on its side and remove the two cover screws shown
in Figure 3-52 and remove the cover.

Figure 3-52:

Expansion Adapter Cover Screws Location

WR-1186-1276
MA 00698?

3-56

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

3. Disconnect the cables to the disk interface module and remove the three
screws shown in Figure 3-53.

Figure 3-53:

Expansion Adapter Disk Interface Module Cables and
Screw Locations

RD EXTENSION CABLE CONNECTOR

MR-1186-1335
MA-0IO2-87

Reverse the above proceduie to replace the disk interface module.

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-57

3.17 VAXstation 2000 and MicroVAX 2000
Expansion Box
There are two configurations of expansion boxes and both configurations
are available for the VAXstation 2000 and MicroVAX 2000 Systems. One

configuration consists of an RD53 hard disk drive in an expansion box
for 70 megabytes of storage memory. Another configuration consists of
a TK50 tape drive with a TZK50 Controller board in an expansion box for
94.5 megabytes of storage memory.

The expansion box with the hard disk contains five FRUs. They are the
disk, disk device electronics board inside the disk, a resistor load board,
the power supply, and the expansion box itself. The expansion box with the
tape drive also contains five FRUs. They are the TK50 tape drive, TZK50
Controller board, a resistor load board, the power supply, and the expansion
box itself.

Paragraph 3.17.1 contains removal procedures for the hard disk drive ex
pansion box and Paragraph 3.17.2 contains removal procedures for the tape
drive expansion box.

3.17.1 Hard Disk Drive Expansion Box Disconnection
from System Box
1.

Switch off power to the expansion box.

Disconnect the power cable on the expansion box from the wall plug
and then from the expansion box.

3-58

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

^^^
1

Disconnect the hard disk drive expansion box cable shown is Figure

3-54 from the back of the expansion box.

Figure 3-54:

Hard Disk Expansion Box Cable

MR-118S-13O4
MA0103-87

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-59

3.17.1.1 Hard Disk Drive Removal from Hard Disk Expansion Box
1.

Switch off power to the expansion box.

Unscrew the four screws shown in Figure 3-55 and remove the expan
sion box cover.

Figure 3-55:

Hard Disk Expansion Box Cover Screw Locations

MR-1108-1305
MA-OI04B7

3-60

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Disconnect the power cable shown in Figure 3-56 from the resistor load
board.

Figure 3-56:

Resistor Load Board Power Cable

MR-1180-1306
MA-01OS87

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-61

Remove the five screws shown in Figure 3-57 that hold the shieid to
the main chassis.

Figure 3-57:

Hard Disk Expansion Box Shieid Screw Locations

MR-1180-1107
MA-0100B7

/Wv

3-62

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Lift the shield up and off to the side of the expansion box.

Remove the three drive mounting screws shown in Figure 3-58.

Figure 3-58:

Hard Disk Expansion Box Drive Mounting Screws

MR-11B8-13O8
MAOIO7-B7

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-63

Slide the drive out halfway and disconnect the two data cables and the
power cable from the back of the drive, then remove the drive. See
Figure 3-59.

Figure 3-59:

Hard Disk Expansion Box Drive Cables Locations

MR-1188-130?
MA-0108-87

3-64

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Remove the four screws shown in Figure 3-60 and remove the mounting

bracket from the drive.

Figure 3-60:

Hard Disk Expansion Box Drive Mounting Bracket Screws
Location

MR.1186-1 292
MAOOB* 87

If you removed an RD53 because of an error with the drive, go to Para
graph 3.7.1 to replace the device electronics board. Replace the RD53
by reversing the above procedure.

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-65

3.17.1.2 Power Supply Removal from the Hard Disk Expansion Box
1.

Switch off power to the expansion box.

Unscrew the four screws shown in Figure 3-61 and remove the expan
sion box cover.

Figure 3-61:

Hard Disk Expansion Box Cover Screw Locations

MR-1186-1305
MA-OI04-B7

3-66

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

3. Disconnect the power cable shown in Figure 3-62 from the resistor load
board.

Figure 3-62:

Hard Disk Expansion Box Resistor Load Board Power

Cable

MR-1186-1308
MA-OI05-87

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-67

Remove the five screws shown in Figure 3-63 that hold the shield to
the main chassis.

Figure 3-63:

Hard Disk Expansion Box Shield Screw Locations

MR-1188-1307
MA-010687

3-68

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

5.
6.

Lift the shield up and hold it with one hand and disconnect the power

cable from the drive with the other hand.

Tip the expansion box on its side and remove the four screws shown in
Figure 3-64 that hold the power supply to the chassis.

Figure 3-64:

Hard Disk Expansion Box Power Supply Mounting Screw
Locations

MA01S78J

NOTE: One of the power supply cables has an extension cable on it. You must
remove this extension from the power supply you are removing and connect it
to the sowie cable on the new power supply.

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-69

Repiace the power supply by reversing the above procedure.

3.17.1.3 Resistor Load Board Removal from the Hard Disk Expansion
Box

The resistor load board in the expansion box is different from the resistor
load board in the System box. The part number for the resistor load board
in the expansion box is 5417163-01. The -02 version is for the System box.
1.

Switch off power to the expansion box.

Unscrew the four screws shown in Figure 3-65 and remove the expan
sion box cover.

Figure 3-65:

Hard Disk Expansion Box Cover Screw Location

MR-118S-130S
MA-0104-87

3-70

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Disconnect the power cable from the resistor load board Refer to Fieure 3-66.
ö

Figure 3-66:

Hard Disk Expansion Box Resistor Load Board Power

Cable

MR-M B6-13O6
MA-0105-87

Remove the resistor load board from the shield.

Replace the resistor load board by reversing the above procedure.

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-71

3.17.2 Tape Drive Expansion Box Disconnection from

System Box
1.

Switch off power to the expansion box.

Disconnect the power cable on the expansion box from the wall plug
and then from the expansion box.

Disconnect the tape drive expansion box cable shown in Figure 3-67
from the back of the expansion box.

Figure 3-67:

Tape Drive Expansion Box Data Cable

TAPE DRIVE
EXPANSION
BOX CABLE

3-72

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

•/aSB!^

3.17.2.1 TZK50 Controller Board Removal from the Tape Drive
Expansion Box

Switch off power to the expansion box.

Unscrew the four screws shown in Figure 3-68 and remove the expan

sion box cover.

Figure 3-68:

Tape Drive Expansion Box Cover Screw Locations

MR-1188-1305
MA-O1O4-B7

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-73

Disconnect the tape data cable (J3), the TK50 tape drive I/O cable (Jl),
and the power cable (Pl) from the TZK50 Controller board. Refer to
Figure 3-69.

Figure 3-69:

TZK50 Controller Board Cable Locations

DATA CABLE

POWER CABLE

TK50 I/O CABLE

MR-11B8-1312
MA-01I0B7

Remove the TZK50 Controller board from the shield.

Set the jumpers on the new TZK50 Controller board in the same position
as they. are on the old TZK50 Controller board you just removed (see
Figure 3-70). If the old board does not have the three resistor packs in-

stalled (Z7, Z6, and Z8), remove them from the new board. Figure 3-70
shows the TZK50 Controller board configured for ID address 1, with
parity checking enabled, and internal diagnostics disabled.
6.

Replace the TZK50 Controller board by reversing the above procedure.

3-74

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

o»

m
■o

Removed
Installed
Removed
Installed
Removed
Installed

Removed

Installed
Installed

Removed

Removed
Installed
Installed

Removed

Installed
Removed

Remwcd

Removed
Removed

Installed

Instslied

TZK50 Controller Board Jumper and Resistor Pack Locations

AODRESSID

Figure 3-70:

LED

M* 0158 87

SMB 0282 86

I/O CONNECTOR

TAPE DRIVE

3.17.2.2 TK50 Tape Drive Removal from Tape Drive Expansion Box

Remove the TZK50 Controller board (Paragraph 3.17.2.1).

Disconnect the power cable on the resistor load board that comes from
the power supply.

Unscrew the five screws shown in Figure 3-71 that secure the shield to
the main chassis.

Figure 3-71:

Tape Drive Expansion Box Shield Screw Locations

/Ä?V

3-76

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Lift the shield up and off of the main chassis.

Remove the three drive mounting screws shown in Figure 3-72.

Figure 3-72:

Tape Drive Expansion Box Drive Mounting Screw

MH I108I3M
imoujb:

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-77

Slide the tape drive out halfway and disconnect the I/O cable and the
power cable from the back of the drive then remove the drive. Refer to
Figure 3-73.

Figure 3-73:

TK50 Tape Drive Cable Locations

1-1168-1315
MA.0113-B7

3-78

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

7. Remove the four screws shown in Figure 3-74 that secure the mounting
brackets to the sides of the drive. Remove the mounting brackets from
thTdrive

Figure 3-74: Tape Drive Mounting Brackets Screw Locations

MR-iiaa-1316
MA-0114-87

8. Replace the tape drive by reversing the above procedure.

3.17.2.3 Power Supply Removal from the Tape Drive Expansion Box
1. Remove the TZK50 Controller board (Paragraph 3.17.2.1).

2. Disconnect the power cable on the resistor load board that comes from
the power supply.

3. Unscrew the five screws shown in Figure 3-71 that secure the shield to
the main chassis.

Lift the shield up and off of the main chassis.

5. Remove the three drive mounting screws shown in Figure 3-72.

6. Disconnect the power cable from the back of the drive and slide the
drive out of the box.

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-79

Put the expansion box on its side as shown in Figure 3-75 and remove
the four screws holding the power supply to the chassis.

Figure 3-75:

Tape Drive Expansion Box Power Supply Mounting Screw
Locations

MB 1186-1317
MA 0126-87

Replace the power supply by reversing the above procedure.

3-80

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

3.17.2.4 Resistor Load Board Removal from the Tape Drive Expansion
Box

l^dhoiSrHr
l0£d b°a.rd inuthe *xPansi™ box is different from the resistor
load board in the System box. The part number for the resistor load board
in the expansion box is 5417163-01. The -02 version is for the System box
1.

Switch off power to the expansion box.

2. Unscrew the four screws shown in Figure 3-68 and remove the expansion box cover.

3. pisconnect the two power cables shown in Figure 3-76 from the resistor
load board.

Figure 3-76: Tape Drive Expansion Box Resistor Load Board Power
Cable Locations

POWER CABLE

MFM 186-1318
MA0115-87

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-81

Remove the resistor load board from the shield.

Replace the resistor load board by reversing the above procedure.

3.18 Recommended Spares List

Part Number

DescrlpHon

QJy

70-24268-01

VAXstation 2000 and MicroVAX 2000 System module

54-16802-BA

4 Megabyte memory module

54-16802-AA

2 Megabyte memory module

H7848-BA

120V power supply

H7848-BB

240V power supply

54-16804-01

Network interconnect module

54-17163-01

Resistor load board for Expansion Box

54-17163-02

Resistor load board for System Box

29-24794-00

9-Pin loopback connector for printer port

29-24795-00

25-Pin loopback connector for communication port

12-19245-00

Battery pack

54-17003-01

Disk interface module (in expansion adaptor)

54-17639-01

(TZK50-AA) TZK50 Controller module (in expansion box)

TK50-AA

TK50 tape drive

29-26243-00

Branch suitcase

17-00303-07

Network interconnect interface cable (connects network
interconnect module to System module)

Internal RX/RD cable (connects internal RX and RD

17-01107-01

drives to System module)

17-01107-02

RX/RD cable (connects internal RX and RD drives and

also the disk interface module that is in the expansion
adapter to the System module)

17-01244-01

Internal tape port cable (connects the tape port A inside

the expansion adapter to the System module)
17-00674-03

3-82

RD expansion adapter cable (From the disk port B on
the expansion adapter to the hard disk expansion box)

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Part Number

Description

17-01247-02

TK50 tape drive I/O cable (From TK50 to TZK50 in tape

Load board power cable extension (in tape drive expan-

17-01249-01

Internal tape data cable (from TZK50 Controller board
to the bulkhead connector in tape drive expansion box)

17-01351-02

Tape drive expansion box data cable (from the tape port
A on the expansion adapter to the tape drive expansion

DEC423 Converter (MicroVAX 2000's RS232 to DEC423

17-00445-02

Hard disk drive expansion box data cable

17-00300-XX

BCC05 printer cable

17-00568-01

BC18P monochrome video cable

17-00289-XX

BCC04-10 modern cable

17-00301-XX

BCC08 console cable

17-00313-04

BC22D-50 null modern cable

17-00342-01

Power cable extension to resistor load board

17-01090-01

Internal RD data cable in expansion box

17-00811-03

Qty

drive expansion box)
17-01397-01

sion box)

box)

70-23766-01

MMJ pJugs Converter)

J0^\

BC16E-25 DECconnect office cable (with MMJ ends)

17-00811-04

BC16E-50 DECconnect office cable (with MMJ ends)

12-23599-01

H8571-A 25-Pin passive adapter

H3103

MMJ loopback connector

12-25869-01

ThinWire Ethernet "T" connector

12-26318-01

ThinWire Ethernet cable terminator

30-19448-06

RX50 blank media for field service System exerciser

30-25145-05

RX33 blank media for field service System exerciser

30-20515-01

TK50 blank media for field service System exerciser

70-21861-01

VR260 tube/yoke/bezel assembly

70-21862-01

VR260 LED bezel assembly

70-21266-01

VR260 rear bulkhead

FRU REMOVAL AND REPLACEMENT PROCEDURES

3-83

Part Number

Description

54-15624-01

VR260 deflection board

54-15626-01

VR260 video amp board

74-30063-01

VR260 video amp board standoffs

70-21863-01

VR260 brightness/contrast control

70-21478-01

VR260 H/V cable

70-21480-01

VR260 ground cable

70-21477-01

V/D cable assembly

70-21865-01

VR260 transformer assembly

70-21924-01

VR260 chassis subset

74-28316-01

VR260 foot

12-21126-04

VR260 fuse holder assembly (Europe)

12-19283-19

VR260 fuse, 240 Vac (Europe)

90-07212-00

VR260 fuse, 115 Vac (U.S.)

Qty

3-84

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Chapter 4

■

Video Monitor Adjustments
(VAXstation 2000)
4.1

Introduction

This chapter describes how to adjust the VR260 monochrome monitor for
its best picture. Alignment and adjustments for MicroVAX 2000's terminals
are not covered in this guide. See the terminal's pocket Service guide for
all alignments to MicroVAX 2000's terminals.

4.2 VR260 Monochrome Monitor
j0m\

Adjustments to the monitor are made with its cover removed. If the monitor's cover is not already removed, remove it (Paragraph 3.12.1) and then
reconnect the power cable and the video cable to the monitor.

FoUow the procedures in order. The success of one adjustment may depend
on the accuracy of preceding checks and adjustments with the exception of
the focus and G2 adjustments.
When the procedure teils you to display a test pattern, enter console mode
(Paragraph 2.2.2), attach a loopback connector (p/n 29-24795) to the 25-pin
communication port, and then type the appropriate test command listed in
Table 4-1. Table 4-1 lists the base video alignment patterns and the test
commands that invoke them.

Table 4-1:
Test Command

Base Video Alignment Test Commands
Test Pattern

Circle cross-hatch

Screen of all E's

White screen pattern

Loopback Requlred
X

4-1

You will need the followine tools to adjust the VR260 monitor.

•

Alignment tool (p/n 29-24746-00)

•

Metric measuring tape (p/n 29-25342)

4.2.1 Preparations
1.

Switch on power to the VR260 monitor and the System.

Set the brightness and contrast controls to their maximum positions
(Figure 4-1).

Wait 30 seconds for the monitor to warm up, then adjust the brightness
to extinguish the raster.

Adjust the contrast for normal viewing level.

Refer to Figure 4-2 for the adjustment locations on the VR260 monitor.

4-2

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Figure 4-1:

Brightness and Contrast Controls

PICTURE

RASTER

BLACK SCREEN

CONTRAST

\3 CONTROL

W BRIGHTNESS

~/VC CONTROL

MA .7567-83

Video Monitor Adjustments (VAXstation 2000)

4-3

Figure 4-2:

VR260 Infernal Adjustment Locations

G2 ADJ

LIN

FOCUS

WIDTH
H CENTER

MF11086I25O
MA0116-87

4.2.2 Horizontal and Vertical Linearity and Focus
Adjustments
1.

Display the circle cross-hatch pattern (TEST 60). If the customer is having problems with text, display the all E's pattern (TEST 61) for a reference check.

4-4

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Adjust the horizontal linearity (UN) (use the hex trimpot) for horizontal
uniformity of the Squares across the display. The display should contain
32 horizontal Squares and fill the screen. Refer to Figure 4-3.

Figure 4-3:

Circle Cross-Hatch Display

32 SQUARES

27 SQUARES

MP-1080-1261
MA 01 I7-B7

Adjust the vertical linearity (VL) (use the flat-bladed trimpot) for vertical
uniformity of the Squares up and down the screen. The display should
contain 27 vertical Squares and fill the screen.

Adjust the focus (use a long handled flat-blade screwdriver) for the best
vertical/horizontal line sharpness. Check an intersection of the crosshatch pattern that is at least three Squares in from any one of the four
corners.

Video Monitor Adjustments (VAXstation 2000)

4-5

4.2.3 Width, Height, and Centering Adjustments
1.

Display the white screen display (TEST 62).

Adjust the brightness so the raster is visible.

Adjust the contrast for normal viewing level.

Adjust horizontal centering (H CENT) (use the flat-blade screwdriver)
until the raster is centered.

Adjust the horizontal phase (HP) so the video is centered in the raster.

Adjust the brightness to extinguish the raster.

Measure the width of the display with the tape measure as shown in
Figure 4-4. The display should have a 334 mm width. Adjust width (use
the hex trimpot) until the display measures 334 mm across.

CAUTION: Avoid scratching the screen surface with the metal clip of the tape.
Start the measurement at 10 cm (100 mm) as shown below.
Figure 4-4:

Width and Height Measurements
,//CT*\

4-6

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

8. Adjust the vertical height (VH) and the vertical centering (VC) so that

the display touches the top and bottoni edges of the screen at the same
time.

9.
ä

Measure the height of the display with the tape measure. The display
should have a 282 mm height. Adjust the vertical height (VH) until the

display measures 282 mm top to bottom.
4.2.4 Rechecklng the Display
1.

Display the circle cross-hatch pattern (TEST 60).

Check the vertical and horizontal Unearity of the Squares. Readjust if
needed (Paragraph 4.2.2, steps 2 and 3).

Check the vertical and horizontal centering, the height, and the width
of the display. Readjust if needed (Paragraph 4.2.3).

4.2.5 Adjusting Minimum Raster

Set the brightness to maximum and the contrast to minimum. A raster
should be faintly visible.

If no raster is visible, adjust G2 (use a flat-blade screwdriver) until a

Adjust the brightness and contrast for normal viewing.

raster is faintly visible.

4.2.6 Reassembling the VR260 Monitor
1.

Switch the System power switch and the monitor power switch off.

WARNING: Wait at least 30 seconds after you turn off power to unplug the
power cord. Statte electricity dissipates for 30 seconds after power is tumed off.
2.

Disconnect the power cord and the video cable from the monitor.

Reverse the procedure in Paragraph 3.12.1.

Video Monitor Adjustments (VAXstation 2000)

4-7

Chapter 5

Option Installation
5.1

Introduction

This chapter contains installation instructions for the options available on
the VAXstation 2000 and MicroVAX 2000 Systems. These instructions are
for the initial installation of the options listed in Table 5-1. Table 5-1 also
lists the section and page each option's installation procedures are located
on.

Table 5-1:

Options Installation Section Listings

Option

Section

Page

Disk drives into the System box

5.4

5-2

Expansion adapter

5.5

5-6

Hard disk expansion box

5.6

5-11

Memory module

5.2

5-2

Tape drive expansion box

5.7

5-11

ThinWire Ethernet network interconnect module

5.3

5-2

After you complete the installation of the Option, power up the System and
the expansion boxes and run self-test on the Option as described in Chapter
2 Paragraph 2.3.2.

5-1

5.2 Memory Module Installation
Do the following steps to install the memory module Option in either the
VAXstation 2000 or the MicroVAX 2000.

Go to Chapter 3 Paragraph 3.5 and do steps 1 and 2.

Do step 3 of Paragraph 3.5 if a memory module is already installed.

Install the new memory module by reversing steps 1, 2, and 3 in Para
graph 3.5 starting at step 3.

5.3 ThinWire Ethernet Network Interconnect
Module Installation
Do the following steps to install the network interconnect module into the
MicroVAX 2000. The VAXstation 2000 comes with the network interconnect
module as Standard equipment.

Go to Chapter 3 Paragraph 3.6 and do steps 1 and 2.

Install the new network interconnect module by reversing steps 1, 2,
and 3 in Paragraph 3.6 starting at step 3.

5.4 System Box Disk Drive Installation
This procedure is for the initial installation of an RX33 floppy disk, an RD32
hard disk, or an RD54 hard disk drive into a System box. When the System
box does not have any drives installed, a resistor load board must be in
stalled for the power supply to regulate properly. This resistor load board
must also be installed if just the RX33 floppy disk drive is installed by itself.
The RX33 does not load the power supply enough for it to regulate. The
resistor load board must not be installed when either of the hard disk drives
are installed or if both the RD32 and RX33 drives are installed together.
Do the following steps to install a hard disk dirve or a floppy disk drive
in the System box. If the System box already has the drive installed, go to
Chapter 3 for the removal and replacement of the drive.
1.

5-2

Go to Chapter 3 and do all the steps in Paragraph 3.2.

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Remove the three screws shown in Figure 5-1 that secure the drive

mounting brackets to the chassis, then slide them out of the chassis.

Figure 5-1:

■

Drive Mounting Brackets Screw Locations

MUH 86-129S
MAOU3B7

Option Installation

5-3

Disconnect the power cables from the resistor load board as shown in
Figure 5-2. If you are just installing an RX33 floppy drive and you are
not installing the RD32 hard disk drive along with it, you must leave
one power cable connected to the resistor load board and then skip the
next two steps (steps 4 and 5).

Figure 5-2:

Resistor Load Board Location

RESISTOR LOAD BOARD

MR-1188-1358

MA-OI19-87

Lift the resistor load board up and out of the chassis. It will not be
reinstalled.

5-4

Remove the four standoffs from the chassis before installing the drives.

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

If you are installing an RX33 floppy drive, remove the top blank panel

from the mounting bracket9 by unscrewing the four screws. If you are
installing just the RD32 or just the RD54, leave both blank panels installed.
7.

Position the drive in the mounting brackets as shown in Figure 5-3.
Always put the RX33 in the top position and the RD32 on the bottom
position even if either one is not installed. Secure the drive with two
screws on each side.

Figure 5-3:

Drive Mounting Positions

MB-1186-1294
MA-O0S7-87

Slide the drive into the System box and connect the RD/RX cable and

Finish the Installation by reversing steps 2 and 1 above.

the power cable to the drive or drives if more than one.

Option Installation

5-5

5.5 Expansion Adapter Installation
1.

Do all steps in Chapter 3 Paragraph 3.2.

Remove the three screws shown in Figure 5-4 that secure the drives to
the chassis.

Figure 5-4:

Drive Screw Location

MA1186I293
MA0O8S-8J

5-6

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Slide the drives halfway out of the System box to access the cables
behind them later in this procedure.

Put the System box on its side and remove the cover plate as shown in
Figure 5-5.

Figure 5-5:

Cover Plate Location

SYSTEM BOX

COVER PLATE

MR-1186-1319
MAOI2OB7

Option Installation

5-7

Install the expansion adapter onto the bottom of box and secure it with
four screws as shown in Figure 5-6.

Figure 5-6:

Installing Expansion Adapter
SYSTEM BOX

EXPANSION ADAPTER

«89

MR-1186-1320
MAO12IB7

Disconnect the RD/RX cable from the drives. This cable is replaced in
the next step.

5-8

Install the new RD/RX cable (p/n 17-01107-02) on the drives then push
the RD extension cable through the opening into the expansion adapter.

VAXstation 2000 and MIcroVAX 2000 Maintenance Guide

Connect the RD extension cable to the disk interface module as shown
in Figure 5-7.

Figure 5-7:

Connecting RD Extension Cabie to Disk Interface Module

MR-1186-1321
MAO122B7

TAPE CABLE

Option Installation

5-9

Connect either end of the read/write cable (p/n 17-00674-03) to the disk
interface module, then push the other end up through the opening into
the System box as shown in Figure 5-8.

Figure 5-8:

Connecting Read/Write Cable to Disk Interface Module

MRHB8-1322
MAO123-B7

TAPE CABLE

10. Push the tape cable up through the opening into the System box.
11. Put the System box back onto its feet again.

12. Pull the read/write and tape cables up and hang them over the side of
the box so they do not get lost behind the drives.

13. Slide the drives back and secure them with three screws as shown in
Figure 5-4. Make sure the cables do not get pinched behind the drives.
14. Reinstall the shield by reversing the procedures in Paragraph 3.2.
%

5-10

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

There are no tests for the expansion adapter. However, the test you will
do when you verify the installation of an expansion box will also test the
connections within the expansion adapter.

/-v

5.6 Hard Disk Expansion Box Installation
The hard disk expansion box comes with the hard disk drive already in
stalled. You just have to connect the hard disk cable to the back of the
expansion box and to port B (middle connector) on the expansion adapter.
Then plug in the power cord to the expansion box and switch it on. Run
the HDC self-test (TEST 7) to verify the installation. The HDC error code in
the configuration table should indicate a one (1) for DUAl if the hard disk
exapansion box is installed properly. The hard disk in the expansion box
may or may not be formatted. Run the mass storage verifier Utility on the
disk to find out if it is formatted or not. Format the disk before using it if it
is not formatted.

5.7 Tape Drive Expansion Box Installation

ssm*^
\"

The tape drive expansion box comes with the TK50 tape drive already in
stalled. You just have to connect the tape drive cable to the back of the
expansion box and to port A on the expansion adapter. Then plug in the
power cord to the expansion box and switch it on. Run the TPC self-test
(TEST 6) to verify the installation. The TPC error code in the configura
tion table should indicate 0202.0001 if the tape expansion box is installed
properly.

[

Option Installation

5-11

Appendix

Console Test Commands
This appendix lists all of the test commands including the Utilities. See
Chapter 2 for a complete explanation of these test commands. Test numbers
for field Service diagnostics and certain non-customer Utilities are rejected if
the loopback connector is not installed on the 25-pin communication port.

Table A-1:
TEST

Command

Test Commands

Description

Loopback
Required

Diagnostic Commands

{

Customer mode System exerciser.

Self-test on the ThinWire Ethernet Option module (NI)

Self-test for future Option — no test run

Self-test on Interrupt Controller and ThinWire Ethernet 1D ROM

Self-test on tape drive Controller (TPC)

Self-test on hard disk Controller (HDC)

Self-test on interval timer (IT)

Self-test on floating point unit (FP)

Self-test on memory management unit (MM)

Self-test on System Memory (MEM)

Self-test on serial line Controller (DZ)

Self-test on non-volatile RAM (NVR)

(SYS)

A-1

Table A-1 (Cont.):

Test Commands

TEST

Loopback

Command

Description

Self-test on time-of-year clock (CLK)

Self-test on base video (MONO)

Requlred

101

Field service System exerciser (two pass).

102

Field service System exerciser (continuous).

Utility Commands

Configuration display

Set NVR default boot device

Set NVR default boot flags

Set NVR default recovery action flags

Display language inquiry menu

Monochrome monitor circle cross-hatch alignment pattern

Monochrome monitor screen of E's

Monochrome monitor white screen

Mass storage disk formatter

Mass storage disk verifier

Special key on floppy diskettes

Special key on TK50 COMPACTapes

80-87

Reserved for future color option

Network test Utility

A-2

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Appendix

Console Commands
B.1 Console Command Syntax
•

The console program accepts commands up to 80 characters long.
Longer commands result in an error message. The character count
does not include rubouts, rubbed-out characters, or the terminating
< RETURN >.

•

Type-ahead is not supported. Characters received before the con
sole prompt appears on the screen are discarded. Only Special

characters [CTRUS], [CTRL/ÖJ, [CTRL/c] are recognized.

•

Commands can be abbreviated by typing the first character in the
command name. All commands are recognized by their first char
acter. For example, B Stands for the boot command and T Stands
for the test command.

•

The console program treats multiple adjacent Spaces and tabs as a
Single Space. Leading and trailing Spaces and täbs are ignored.

•

Command qualifiers can appear after the command keyword or af-

•

All numbers (addresses, data, and counts) are hexadecimal except
for symbolic register names which are decimal.

•

The console program accepts uppercase and lowercase letters.

ter any symbol or number in the command.

B.2 Console Commands
B.2.1 BOOT
> > > BOOT [ < qualifier > ][ < device_name > ]
The boot program is called Virtual machine boot (VMB). The console pro

gram intializes and Starts VMB running.
Qualifier

/R5:<data> - After initializing the processor and before starting VMB,

B-1

R5 is loaded with the specified data (in hexadecimal).
console user to pass a parameter to VMB.

This allows a

Device_name

VMB boots the operating System from the device specified in the < device_name>. The device_name is in the form LLLD, where the first
three characters are uppercase letters and the fourth character is a digit
(0 through 9). A terminating colon in the device_name is acceptable,
but is not required. Devices for the VAXstation 2000 and the MicroVAX
2000 are listed below.
•

DUA0 — hard disk drive in System box.

•

DUAI — hard disk drive in expansion box.

•

DUA2 — floppy drive in System box.

•

MUA0 — tape drive in expansion box.

•

ESA0 — ThinWire Ethernet network.

If no device_name is specified, the console program begins a sniffer
boot which searches every device on the System in a specific order
until the operating System Software is found. It does not look in the
NVR for the default boot device. The sniffer searches DUA2 first, DUA0
second, DUA1 third, MUA0 fourth, then ESA0 last. If the sniffer boot
gets to ESA0, it stays there on the NET until it finds the operating
System Software or until you press the halt button. The sniffer boot is
not smart enough to stop looking for the Software on the NET if there
is no Software available on the NET. If a device is not installed on the
System, the sniffer boot skips over the device and searches the next
device in the order. An error message will appear on the screen if no
operating System Software is found (except over the NET because the
sniffer keeps looking).

B.2.2 COMMENT
>>> ! <comment>
The comment command (the exclamation point) is ignored by the console
program. It is used to annotate console I/O command sequences.

B-2

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

B.2.3 CONTINUE
> > > CONTINUE

The processor begins instruction execution at the address currently contained in the program counter. The address in the program counter is the
address that was saved when the console program was started or is the

address that was entered by the Operator using the deposit command. Pro
cessor initialization is not performed. The console program enters program
I/O mode (operating System such as VMS or Ultirx).

B.2.4 DEPOSIT
>>> DEPOSIT [<qualifier>] <address><data>

Deposits the data into the specified address. If no address Space or data
size qualifiers are specified, the defaults are the address Space and data size
used in the last deposit or examine command. After processor initialization,
the default address Space is physical memory, the default address is zero,
and the default data size is longword.
Qualifiers
•

/B — The data size is byte.

•

/W — The data size is word.

•

/L — The data size is longword.

•

/V — The address Space is Virtual memory. If memory mapping
is not enabled, Virtual addresses are equal to physical addresses.

•

/P — The address space is physical memory.

•

/I — The address space is Internat processor registers.

•

IG — The address Space is the general registers (RO through
R15).

•

IM — The address Space is the machine register

•

/U — Enables access to console program memory.

•

/N:<count> — The address is the first address in a ränge of
addresses specified in count. The console program deposits to
the first address and then to the specified number of succeeding
addresses. Even if the address is the symbolic address "-", the
succeeding addresses are at the larger addresses. The symbolic
address specifies only the starting address, not the direction
of succession. For repeated references to preceding addresses,
use "Repeat Deposit - <data>".

CONSOLE COMMANDS

B-3

Address
•

Processor Status longword (PSL) — The address space is set to

IM automatically. Do not specify any address space qualifiers

with PSL.

•

Program counter (PC) (general register R15) — The address

■/^

space is set to IG automatically.
•

Stack pointer (SP) (general register R14) — The address Space
is set to IG automatically.

•

General register (Rn) — The register number is in decimal. The
address space is IG.

•

+ (plus) — The location immediately following the last location
referenced in a deposit or examine command. For references
to physical or Virtual memory Spaces, the location referenced is
the last address plus the size of the last reference (1 for byte, 2
for word, 4 for longword). For other address Spaces, the address
is the last address referenced plus one.

•

- (minus) — The location immediately preceding the last location
referenced in a deposit or examine command. For references
to physical or Virtual memory Spaces, the location referenced is
the last address minus the size of this reference (1 for byte, 2 for
word, 4 for longword). For other address Spaces, the address is
the last address referenced minus one.

•

* (asterisk) — The location last referenced in a deposit or exam
ine command.

•

@ (at sign) — The location addressed by the last location refer
enced in a deposit or examine command.

/tam^
1

Data

The data is specified as a hexadecimal number.
number is zero.

The default

B.2.5 EXAMINE
>>> EXAMINE [<qualifier>] [<address>]

Examines the contents of the specified address. If no address is specified,
" +" is assumed. The address may also be one of the symbolic addresses
described in deposit.
Qualifiers
/*s^?v

B-4

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Same qualifiers as deposit.
Address

Same address specifications as deposit.

The response is in the form: < address spacex address > <data>

B.2.6 FIND
> > > FIND (< qualifier > ]

The console program searches main memory staring at address zero for a
page-aligned 64 Kilobyte segment of good memory or a restart parameter
block (RPB). If the segment or block is found, its address plus 512 is left in
the SP. If the segment or block is not found, an error message is issued and
the contents of the SP are unpredictable. If no qualifier is specified, /RPB
is assumed.

Qualifiers

•

/Memory

Searches memory for a page-aligned 64 kilobyte segment of
good memory. The search includes a read/write test of memory
and leaves the contents of memory unpredictable.
•

/RPB

Searches memory for a restart parameter block.
leaves the contents of memory unchanged.

The search

B.2.7 HALT
> > > HALT

The console prompt is displayed. No action is taken.

B.2.8 INITIALIZE
> > > INITIALIZE

A processor initialization is performed. The following registers are set (all

values are hexadecimal).

CONSOLE COMMANDS

B-5

Value

PSL

041F.0000

IPL

ASTLVL

S1SR

ICCS

RXCS

TXCS

MAPEN

*^\

)

All other registers are unpredictable.

The defaults used to fill in unsupplied qualifiers for deposit and examine

commands are set to physical address, longword size, and address 0.

B.2.9 REPEAT
>>>REPEAT <command>

The console program repeatedly displays and executes the specified com
mand. The repetition is stopped when the Operator types|CTRUC|. Any valid
console command may be specified for the command with the exception
of the repeat command.

B.2.10 START
> > > START [ < address > ]

)

The console program Starts instruction execution at the specified address.
If no address is given, the current content of the PC is used. If no qualifier
is present, macroinstruction execution is started. If memory mapping is
enabled, macroinstructions are executed from Virtual memory. The Start
command is equivalent to a deposit to PC followed by a continue command.
No Initialize is performed.

B.2.11 TEST
> >> TEST [<test number>]

The console program invokes a diagnostic test program specified by the test
number. Test numbers for field service diagnostics are rejected if the loop-

back connector is not installed on the 25-pin communication port. Some

of the test numbers are used to invoke Utilities.

See Appendix A for a

description of the test numbers.

B-6

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

B.2.12 UNJAM
> > > UNJAM

A system reset is performed.

B.2.13 TRANSFER
> > > X < address > < count > < RETURN > < date stream > < checksum >
Transfers binary data to and from physical memory. This command is used

by automatic Systems communicating with the console program. It is not

intended for Operator use. The console program loads or unloads (that is,
writes or reads memory) the specified number of data bytes, starting at the
specified address.
Address

The physical address the binary data are transferred to or from. It is
specified as a hexadecimal number.

Count

The number of bytes to be transferred. It is specified as a hexadecimal
number. If the high order bit of the count is one, the data are transferred
(read) from physical memory to the console device. If the high order

bit is zero, the data are transferred (written) from the console device to
physical memory.
RETURN

A carriage return.

Checksum

The two's complement checksum of the command string or data stream.
The checksum is one byte of data expressed as a two digit hexadecimal
number.

Data stream

"Count" bytes of binary data.

CONSOLE COMMANDS

B-7

B.3 Special Keys
Table B-1:

Special Keys Used in Console Program Mode

Special Key

Explanation of use

|BREAK|

Pressing this key on the Special attached console device with a BCC08

cable on the 9-pin printer port halts the CPU and enters console mode.
A host Computer attached to this line may transmit a break signal to get
into console mode. A received break on the normal console device on the
video port or on port 1 is treated as an illegal character.

|RETURN|

Terminates the command line so the console program can execute the
command.

This is used to delete Single characters within a command line. On video

terminals and video monitors, the character(s) deleted disappears (the con
sole program sends a BS/SP/BS). On hardcopy terminals, the deleted char
acters are retyped after a backslash delimiter as they are deleted. For un-

known attached console devices, the console program assumes they are
hardcopy.
Aborts the current command. The current program mode PC will be
displayed, and the console prompt is displayed on the next line. The
console program echoes this as "C.

Causes the console program to throw away transmissions to the console

device until the next 1CTRUO| ig entered. I CTRL/Ol is echoed as "O when

it disables Output, but is not echoed when it re-enables Output. Output is
re-enabled if the console program prints an error message or if the console
prompts for a command from the console device.

Output is also enabled by entering program I/O mode, and bylCTRL/Cl.
| CTRL/Ol clears |CTRL/S|.
Retypes the current command line. Deleted characters are not displayed.
CTRÜS
CTRUQ

and

The console program supports |CTRL/Sl and |CTRL/Q| on both the normal

and attached console devices. These keys are equivalent to the corresponding line pacing control characters XOFF and XON. Characters received
between the XOFF/XON pair may be ignored.

The hold screen key on the normal console device is not used for line
pacing.

Ignores the current command line. The console prompt is displayed on the
next line. This only affects entry of the current line. The console program

echoes this as "U. Pressing |CTRL/l)| when a command is executing does
not abort the command.

B-8

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Appendix
0

Console Messages and Explanations
Table C-1:
Message
02 EXT HLT

Console Error Messages
Explanation

<BREAK> was typed at the console, QBINIT or QHALT was as

ser ted.

04 ISP ERR

Attempt to push interrupt or exception state onto the interrupt Stack
when the interrupt stack is mapped NO ACCESS or NOT VALID.

05 DBL ERR

A second machine check occurred while the processor was attempting
to report a machine check to the operating system.

06 HLT INST

The processor executed a halt instruction in kernal mode.

07 SCB ERR3

Vector bits <l:0> =3.

08 SCB ERR2

Vector bits <l:0> =2.

0A CHM FR ISTK

A change mode instruction was executed when PSL<IS> was set.

OB CHM TO ISTK

Exception vector bit <0> was set for a change mode.

0C SCB RD ERR

A hard memory error occurred during a processor read of an excep
tion or interrupt vector.

10 MCHK AV

An access violation or invalid translation occurred during machine

check exception processing.
11 KSP AV

An access violation or invalid translation occurred during invalid

kernel stack pointer exception processing.
14 TOY ERR

Time-of-year (TOY) clock failure.

15 CORRPTN

The console database is corrupted. The console simulates a power-up
sequence and rebuilds its database.

16 ILL REF

The requested reference violates Virtual memory protection and the

address is not mapped. Either the reference is not valid in the spec-

ified address Space or the value is not valid in the specified destina-

tion.

CONSOLE MESSAGES AND EXPLANATIONS

C-1

Table C-1 (Cont.):

Console Error Messages

Message

Explanation

17 1LL CMD

The command string cannot be parsed.

18 1NV DGT

A number has an invalid digit.

19LTL

The command is too large for the console to buffer.

1A ILL ADR

The specified address is not in the address space.

1B CAL TOO LRG

The specified value doe9 not fit in the destination.

IC SW CONF

Conflicting switches. For example, an examine command that spec-

1D UNK SW

The switch is not recognized.

1E UNK SYM

The examine or deposit symbolic address is not recognized.

1F CHKSM

ifies two different data sizes.

Either the whole transfer (X) command or just the <data> portion

of the transfer command is not valid.

20 HLTED

The Operator entered the halt command.

21 FND ERR

A find command failed to find either the RPB or 64 kilobytes of good
memory.

22 TMOUT

Data failed to arrive in the expected time during a transfer (X) com
mand.

23 MEM ERR

Parity or other memory error detected.

24 UNXINT

An unexpected interrupt or exception occurred.

40 NOSUCHDEV

VMB message: No bootable device found.

41 DEVASSIGN

Device is not present.

42 NOSUCHFILE

Program image not found.

43 FILESTRUCT

Invalid boot device file structure.

44 BADCHKSUM

Bad checksum on header file.

45 BADFILEHDR

Bad file header.

46 BADIRECTORY

Bad directory file.

47 F1LNOTCNTG

Invalid program image file.

48 ENDOFFILE

Premature end-of-file encountered.

49 VADFILENAME

Bad file name given.

4A BUFFEROVF

Program image does not fit in available memory.

4B CTRLERR

Boot device I/O error.

C-2

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Table C-1 (Cont.):

Console Error Messages

Message

Explanatlon

4C DEV1NACT

Failed to initialize boot device.

4D DEVOFFUNE

Device is off-line.

4E MEMERR

Memory initialization error.

4F SCBINT

Unexpected SCB exception or machine check.

50 SCBZND1NT

Unexpected exception after starting program image.

51 MOROM

No valid ROM image found.

52 NOSUCHNODE

No reaponse from load Server.

53 INSFMAPREG

Invalid memory configuration.

54 RETRY

No devices bootable, retrying.

83 BOOT SYS

Bootstrapping.

84 FAIL

General failure.

85 RESTART SYS

Restarting System Software.

CONSOLE MESSAGES AND EXPLANATIONS

C-3

Appendix D

VMB Boot Error Status Codes
Figure D-1 shows the two types of VMB error displays. PC indicates the
contents of the program counter at the time of the error, RO indicates the
contents of register 0 (VMB boot error Status codes listed in Table D-1) at

the time of the error, and PSL indicates the contents of the program Status

longword.

Each error code's lower three bits (hexadecimal) represent a severitv level
and may be changed by the Software. For example, 000001F4 is a parity
error and represents an error Status, but 000001F0 through 000001F7 also

represent parity errors of varying severity. Therefore, the error codes numbers listed in Table D-1 represent the typical value of each error code.

Figure D-1:

VMB Error Displays

1) Generic error message where RO is a Status code (liated below)
%VMB-F-ERR, PC = nnnnnnnn

XVMB-I-STS, RO = nnnnnnnn

2) Unexpected exception. These represent internal VMB errors.
%VMB-F-SCBINT, PC = nnnnnnnn, PSL = nnnnnnnn
OR

%VMB-F-SCBINT2, PC = nnnnnnnn, PSL = nnnnnnnn

D-1

Table D-1:

VMB Boot Error Status Codes

Error Code

Mnemonic

Definition

00000001

SS$. NORMAL

Normal successful completion

00000054

SS$.CTRLERR

Fatal Controller error

00000084

SS$_DEVOFFUNE

Device is not in configuraüon or not available

0000008C

SS$_DRVERR

Fatal drive error

000000DC

SS$JLLBLKNUM

Illegal logical block number

000001A4

SSS.MEDOFL

Medium is off-line

000001AC

SS$_NODATA

Mailbox is empty

000001F4

SS$_PARITY

Parity error

0000022C

SS$_ TIMEOUT

Device timeout

0000028C

SSS.NOSUCHNODE

Remote node is unknown

000002AC

SS$_F1LNOTCNTG

File is not contiguous as required

00000344

SS$JNSFMAPREG

lnsufficient map registers

00000601

SS$.BUFFEROVF

Output buffer overflow

00000808

SS$_BADCHKSUM

Bad file header checksum

00000810

SS$_BADFILEHDR

Bad file header

00000818

SS$_ BADFILENAME

Bad file name syntax

00000828

SSS.BADIRECTORY

Bad directory file format

00000848

SS$_DEVASSIGN

Device has Channels assigned

00000870

SSS.ENDOFF1LE

End of file

000008C0

SS$_F1LESTRUCT

Unsupported file structure level

00000908

SS$_NOSUCHDEV

No such device available

00000910

SS$_NOSUCHFILE

No such file

000020D4

SSS.DEVINACT

Device inactive

00002144

SSS.FORCEDERROR

Forced error flagged in last sector read

00008000

SSS.MEMERR

No good pages of memory found

00008018

SS$_NOROM

System exerciaer not present

D-2

VAXstation 2000 and MicroVAX 2000 Maintenance Guide

Index
Console Commands (cont'd.)
Repeat, B-6
Alignment Pattern

Start, 2-4, B-6

Cirde Cross-hatch, 2-59

Syntax, B-l

Screen of E's, 2-59

Test, B-6

Test Commands, 4-1

Transfer, B-7

White Screen, 2-59

Unjam, B-7

Console Device

Baud Rate, 2-2

Battery Testing

See Troubleshooting, NVR
Baud Rate

Console Messages Explained, C-l
Console Mode
Exil, 2-3
How to Enter, 2-2

Console Device, 2-2

Special Keys Defined, B-8

Diagnostic Console, 2-4

Usage, 2-1

BCC08 Cable, 2-2, 2-4

Boot Device Settings, 2-55

Console Test Commands, A-l
CPU, halts, 2-2

Boot Flag Settings, 2-55

Commands, test, A-l

Configuration Table, 2-8, 2-47
DZ Example, 2-48

Example of MEM error display, 2-49
HDC Example, 2-51

MEM Example, 2-48
TPC Example, 2-52
Console Commands, B-l

Diagnostic Console, 2-4
Break Key, 2-2

Disk Drive

Drive Select Jumper Settings, 2-27
Installation, 5-2

Mnemonics, 2-21

Power-up and Self-test Error Codes,
2-23

Self-test Example Error Code, 2-22

Boot, 2-3, B-l

System Exerciser Error Codes, 2-25

Comment, B-2

System Exerciser Example Error

Continue, 2-3, B-3
Deposit, B-3

Code, 2-24
Disk Formatter, 2-59

Examine, B-4

Floppy Disk Example, 2-61

Find, B-5

Hard Disk Example, 2-60

Halt, B-5

Messages, 2-63

Initialize, B-5

Unknown Hard Disk Example, 2-62
Disk Verifier, 2-64

lndex-1

Disk Verifier (cont'd.)

Loop Testing on the Network, 2-69

Hard Disk Example, 2-64
Messages, 2-65

Memory bank error location, 2-52

Memory Module, 1-8

Expansion Adapter

Connectors, 1-7

Memory Module Installation, 5-2
MicroVAX 20(30

Connectors, 1-4

Installation, 5-6

Console Device, 2-2

Field Replaceable Units (FRU)
Locations, 1-8

Network ID ROM Location, 3-15

Formatter, disk, 2-59

Options, 1-8
Installation, 5-1

Halt Button
Location, 1-3, 1-4

Usage, 2-2
Halts CPU, 2-2

Hard Disk Drive Expansion Box, 3-58
See also Removal and Replacement

P
Poxver Supply Connector Pin Voltages,
2-41

Power-up Testing

Installation, 5-11

Error Codes, 2-8
Error Summary Display, 2-7

Example Display, 2-5

Initial Installation

Disk Drives, 5-2
Expansion Adapter, 5-6

Hard Disk Drive Expansion Box, 5-11
Memory Module, 5-2

Symbols, 2-6
Program Mode, 2-1
Prompts, 2-2

Network Interconnect Module, 5-2

Recommended Spares List, 3-82

Tape Drive Expansion Box, 5-11

Recovery Action Setting, 2-58
Removal and Replacement
Battery Pack, 3-33

Jumper, System, 3-16

DEC423 Converter from MicroVAX
2000, 3-53

Disk Interface Module from
Expansion Adapter, 3-56

Language lnquiry Menü, 2-58

Loopback Connectors, 2-11
Loopbacks

Usage, 2-14, 2-17

lndex-2

Expansion Adapter, 3-54

Expansion Boxes, 3-58
Hard Disk Drive Expansion Box
Disconnection, 3-58

Removal and Replacement

Hard Disk Drive Expansion Box
(cont'd.)

Hard Disk Drive, 3-60
Power Supply, 3-66

Resistor Load Board, 3-70

Keyboard from VAXstation 2000, 3-51
Memory Module, 3-17
Mouse and Tablet from VAXstation

2000, 3-52

Network lnterconnect Module, 3-18
Power Supply from System Box, 3-34

RD32 Device Electronics Board, 3-27

Self-test Commands, 2-10
Special Key for System Exerciser, 2-66

COMPACTape Example, 2-67
Floppy Diskette Example, 2-66
System Differences, 1-2
System Exerciser
Commands, 2-14
Error Codes, 2-15

Example Display, 2-15
System Jumper, 3-16

System module's ROM revision levels,
2-53

RD53 Device Electronics Board, 3-21
RD53 from System Box, 3-19
Resistor Load Board from System
Box, 3-31

RX33 and RD32 from System Box,
3-24

Shield, 3-4
System Module, 3-13
System Module Assembly from
Shield, 3-10
Tape Drive Expansion Box
Disconection, 3-72

Power Supply, 3-79

Resistor Load Board, 3-81

TK50 Tape Drive, 3-76
TZK50 Controller Board, 3-73
Terminal from MicroVAX 2000, 3-53

VR260, 3-35
VR260 Cover, 3-36

VR260 Deflection Board, 3-39
VR260 LED Assembly, 3-50
VR260 Rear Bulkhead, 3-42

VR260 Transformer Assembly, 3-45

VR260 Tube/Yoke/Bezel Assembly,
3-47

VR260 Video Board, 3-44

Tape Drive

lnternal Self-test, 2-35
Jumper Settings, 2-37

Self-test Example Error Code, 2-30
System Exerciser Error Codes, 2-33

System Exerciser Example Error
Code, 2-32
Tape Drive Expansion Box, 3-58

See also Removal and Replacement
Installation, 5-11

Tape expansion box's ROM revision
levels, 2-54
Test Commands, A-l
Testing, 2-5

Power-up, 2-5
Self-test, 2-9
System Exerciser, 2-13
Testing, battery

See Troubleshooting, NVR

ThinWire Ethernet Loop Testing
Example, 2-68

ThinWire Ethernet Network Module,
1-8

Installation, 5-2

ThinWire Ethernet Option Module
Loop testing Utility, 2-67

Self-test
/\

Error Codes, 2-11

Troubleshooting, 2-39
Troubleshooting, 2-16

Example Display, 2-9

Disk Controller (HDC), 2-21

Using Loopback Connectors, 2-11

Floating Point (FP), 2-21

lndex-3

Troubleshooting (cont'd.)
Hard Disk Expansion Box, 2-27
Interval Timer (IT), 2-21

Memory (MEM), 2-19
Memory Management (MM), 2-20

Monochrome Video (MONO), 2-16
Non-Volatile RAM (NVR), 2-17
Power Supply, 2-40
Serial Line Controller .{DZ), 2-17
System (SYS), 2-38

Tape Controller (TPC), 2-29
Tape Drive Expansion Box, 2-35
Terminal Communications, 2-44

ThinWire Ethernet Option Module
(Nl), 2-39
Time-of-Year Clock (CLK), 2-17
VR260 Monitor, 2-42

U
Utilities, 2-46
Circle Cross-hatch Alignment
Pattern, 2-59

Commands, 2-46
Configuration Table, 2-47
Disk Formatter, 2-59
Disk Verifier, 2-64

Language Inquiry Menü, 2-58
Screen of E's Pattern, 2-59

Setting Default Boot Device, 2-55
Setting Default Boot Flags, 2-55
Setting Default Recovery Action, 2-58
Special Key for F.S. System Exerciser,

2-66
ThinWire Ethernet Loop Testing,
2-67
White Screen, 2-59

y
VAXstation 2000

Connectors, 1-3
Console Device, 2-2
VMB Boot Error Status Codes, D-l
VR260 Adjustments, 4-1

lndex-4

VR260 Horiz., Vert., and Focus

adjustments, 4-4
VR260 Minimum Raster Adjustment, 4-7

VR260 removal and replacement
procedures, 3-35
VR260 Width, Height, and Centering
Adjustments, 4-6

■■