Sharp FDD-412A - Page 83

119 pages

Save Page as PDF

To Next Page

To Next Page

To Previous Page

To Previous Page

Loading...

Oe

Dy!

FDD4i2A/B

TROUBLESHOOT

ING

Troubleshooting

Flowchart

Objective:

To

minimize

the

repair

time

upon

FDD

error

Notes

on

use

(1)

(2)

(3)

(4)

(5)

This

flowchart

covers

only

the

cases

in

which,

upon

system

error,

its

cause

is

suspected

to

exist

in

the

FDD.

FDD

usages

(i.e.,

control

methods)

vary

depending

on

the

system.

It

follows

that

not

all

paths

may

be

applied

to

a

specific

con-

figuration.

In

such

a

case,

the

flowchart

serves

solely

as

a

rule-of-thumb

guideline

for

maintenance.

Keep

the

error

information

that

was

output

on

a

console

type-

writer

or

other

devices

upon

error.

In

case

of

a

data-related

error,

keep'

intact

the

contents

of

the

recorded

surface

at

the

time

of

the

error.

That

is,

do

not

write

data

into

the

track

applicable

to

the

error

until

the

error

is

remedies.

The

knowledge

that

an

abnormal

output

waveshape

was

present

or

absent

upon

error,

and/or

details

of

how

the

error

occurred

can

be

very

helpful

and

may

serve

as

a

key

to

finding

what

caused

the

error.

In

the

flowchart,

the

abbreviations

and

numbers

in

parantheses

indicate

measuring

points.

Example:

(TP-7)

Test

point

(33-7)

Pin

7

of

J3

connector

(IC2-7)

Pin

7

of

IC2

-7-