atl hdi 3000 service manual rev b

7/17/2019 ATL HDI 3000 Service Manual Rev B

http://slidepdf.com/reader/full/atl-hdi-3000-service-manual-rev-b 1/219

P/N4730-0230-01 RevB

HDI 3000Field Service Manual

Diagnostics Supplement

Service Manual 4730-0230-01 Rev A consists of:

HDI 3000 Service Manual Diagnostics SupplementP/N 4720-0230-01 Rev A (August 1997)

August1999



Incremental updates may occur to this manual after its initial release. Pages changed or

added after the initial release can be identified by a change date located at the bottom of the

page. No change date on a page indicates that page is the original release and has not been

changed (hardcopy version only). A change bar ( ) located in the outside margin of a page

denotes the specific part of a page that was changed on that date. The List of Effective

Pages included herein (hardcopy version only), indicates the change dates for each page.

ATL Ultrasound

P.O. Box 3003

Bothell, WA 98041-3003

USA

Copyright E 1997 by ATL Ultrasound All rights reservedPrinted in USA

“ATL”, “Advanced Technology Laboratories”, and ”HDI” are registered trademarks of ATL Ultrasound

“High Definition” and “Tissue Specific” are trademarks of ATL Ultrasound.

Non-ATL product names may be trademarks or registered trademarks of their respective owners.



i

How to Use This Manual

Audience

This manual supports the field service maintenance and repair of the

HDI 3000 system. The user of this document is a qualified ultrasound

electronics technician who has completed training classes on the

system and its peripherals.

Manual Organization

This manual has been formatted and distributed in two versions: for

laptop-computer-screen viewing and for printed-page viewing. Al-though both versions contain identical information, the laptop page

numbers and printed page numbers do not always correspond to

each other. Use paragraph, figure, and table numbers when referring

others to specific parts of this manual. In the laptop version, the table

of contents, index entries, and cross references use hypertext links to

provide access to the referenced information.



9A--1

1 9A Diagnostics

9A--1 IntroductionDiagnostic information for the HDI 3000 is contained in Section 9 of

the HDI 3000 Field Service Manual Volume 2, Procedures, (P/N

4720-0015-03 or later) and in this Diagnostics Supplement. Section 9

of the field service manual contains information on core bootup fault

isolation, system alerts, and system diagnostics. The information in

Section 9 is applicable to all service personnel.

The Diagnostics Supplement expands upon the general diagnosticinformation in the service manual and provides information on remote

diagnostics (Service Access Diagnostics). The information in the

Diagnostics Supplement is applicable only to ATL field service per-

sonnel and others with remote access to diagnostics.

The Diagnostics Supplement sections can be inserted directly into

thefieldservicemanualafterSection9.Section9Acontainsinforma-

tion on general fault isolation, channel walk tests, ECG tests, up-



9A--2

grade procedures, and other information. Section 9B contains fault

isolation tables to quickly reference suspected Field Replaceable

Units (FRUs). Section 9C contains information on the capabilities of

Service Access Diagnostics.

9A--2 General Fault Isolation

After the system boots up, the preferred method of troubleshooting

the system is to access the diagnostics and to run the following tests

in the order listed.

1. 2D End-To-End Test

2. 2D Back-End Test

3. Color End-To-End Test

4. Color Back-End Test

5. Comprehensive Test

6. Channel Board Fault Isolation

7. Channel Walk Test



9A--3

9A--2.1 Error Code Interpretation

When a system dialog alert or run-time alert is displayed, a descrip-

tion of the error code is displayed with the error code at the bottom of the dialog box. There are approximately 20 reportable error codes.

The error codes are 20-digit numbers formatted as follows:

abcd efgh ijkl xxxxxxxx

Where:

ab = PCB reporting the error. (Refer to Table 9A--1.)

cd = processor reporting the error on the PCB. (Refer to

Table 9A--1.)e through l = 32 bit hex error ID unique to the reported error.

xxxxxxxx = data associated to the error and applicable only to engi-

neering. Error codes in this manual will omit these last eight digits.



9A--4

Table 9A--1. PCB and Processor Error Codes

PCB Codes

“ab” Code PCB Reporting Error02 ADAPTR

03 AIFOM1

04 AIFOM2

11 CPANEL

12 CPU

19 FEC

1e MPS

1f PCM

20 PIM

21 PSP1

23 SSP1

24 SSP2

25 SSP3



9A--5

Processor Codes

“cd” Code Processor Reporting Error

01 SCIP

02 MOP

10 ADAPTR TRAP

11 ADAPTR PAP

NOTE: When “ab” is the same as “ef” a PCB has sent an unsolicitedmessage to the system software. For example, error code

“1902 1902 0124 02f3e754” indicates an error sent by the

FEC MOP to the system software.

NOTE: Only 20 run-time alerts and system dialog alerts report to

the monitor, however, there are a number of errors that may

occur and report only to the error log. Refer to paragraph

9A--3.3 or 9A--3.4.

Refer to the diagnostic tables in Section 9B for a list of the error

codes and the PCBs that may be responsible for each error.



9A--6

NOTE: Only 20 run-time alerts and system dialog alerts report to

the monitor, however, there are a number of errors that may

occur and report only to the error log. Refer to paragraph

9A--3.3.

CAUTION

Most error codes may not be caused by the PCB

reporting the error. For example, a front end error

code may actually be caused by the AIM, ChannelPCBs, or Scanhead Select PCB.

9A--2.2 2D Tests

The 2D End-To-End Test fakes a TEST Linear 5.0 scanhead and is

used to verify the 2D data path from the FEC to the monitor.

The 2D Back-End Test also fakes a TEST Linear 5.0 scanhead but

verifies only the “back-end” of the 2D End-To-End Test data path

(from the IMEM PCB to the monitor). During the 2D Back-End Test,

the CPU injects a known test pattern into the IMEM PCB. The test

pattern simulates data that would be expected to come from the

FEC.



9A--7

If the 2D End-To-End Test fails, perform the 2D Back-End Test. If

both tests fail, the problem is in the data path between the IMEM

PCB and the monitor. If only the 2D End-To-End Test fails, the prob-

lem is in the data path between the front end and the IMEM PCB.

The 2D End-to-End Test and the 2D Back-End-Test each may be run

in less than one minute.

- Perform the following procedure to run the 2D End-To-End Test or 2D

Back-End Test:

NOTE: If the Comprehensive Test has been run, reboot the system

before executing the 2D End-To-End or 2D Back-End Test.

1. Verify at least one scanhead connector is not being used.

2. Press and hold Superkey, then press zero from the keyboard.

The Machine Diagnostics Menu is displayed.



9A--8

3. In the User field, type the appropriate information using the key-

board, and press RETURN. The cursor moves to the Password

field.

4. In the Password field, type the appropriate information using the

keyboard.

5. Use the trackball to move the cursor to OK. Press SELECT. The

Diagnostic Tools Menu is displayed on the left of the display

with the following options:

User Login

Tests, Utils.Error Log

Configuration

Options

Fake Scanheads

Close

6. Select Tests, Utils. from the menu. Press SELECT.



9A--9

7. Select Machine with the trackball. Quickly press SELECT twice.

8. Select 2D Ultrasound. Select the diamond to the left of the Test

& Utilities option at the bottom of the display. Press SELECT. Amenu is displayed with the Back-End-Test and the End-To-End

Test options.

9. Select the desired test. Select the Execute button. Press

SELECT. The test status is displayed on the monitor.

9A--2.3 Color Tests

The Color End-To-End Test fakes a TEST Linear 5.0 scanhead and isused to verify the color data path from the IMEM to the ADAPTR to

the SSP and back to the IMEM and on to the monitor. (The fake

scanhead sets up the front end to pass the correct imaging parame-

ters. A test pattern of I and Q data is generated on the CPU PCB and

passes through the AIFOM where the correct header information is

attached.) From the AIFOM, the I and Q test pattern follows the same

data path as other color data.



9A--10

The Color Back-End Test also fakes a TEST Linear 5.0 scanhead but

verifies only the “back-end” of the Color End-To-End Test data path

(from the IMEM to the monitor). During the Color Back-End Test, the

CPU injects a known test pattern into the IMEM. The test pattern sim-ulates data that would be expected at the IMEM.

Perform the Color End-To-End Test to verify the entire color data path

is functional. If this test fails, perform the Color Back-End Test. If both

tests fail, the problem is in the data path between the IMEM PCB and

the monitor. If only the Color End-To-End Test fails, the problem is in

the data path between the AIFOM and the IMEM PCB. Both the

Color End-To-End Test and the Color Back-End Test display similar

color test patterns in the center of the linear display.

The Color End-to-End Test and the Color Back-End Test each may

be run in less than two minutes. During the Color End-To-End Test,

the system clock stops updating for approximately 20 to 25 seconds.

During the Color Back-End Test, the system clock stops updating for

approximately 4 to 6 seconds.



9A--11

- Perform the following procedure to run the Color End-To-End Test, or

Color Back-End Test:

NOTE: If the Comprehensive Test has been run, reboot the systembefore executing the Color End-To-End or Color Back-End

Test.

1. Perform steps 1 through 7 of the 2D End-To-End or 2D Back-

EndTestprocedure(paragraph9A--2.2 ).

2. Select Color Ultrasound. Select the diamond to the left of the

Test & Utilities option at the bottom of the display. Press

SELECT. A menu is displayed with the Color Back-End Test,and the Color End-To-End Test options.

3. Select the desired test. Select the Execute button. Press

SELECT. The test status is displayed on the monitor.



9A--12

9A--2.4 Comprehensive Test

Refer to Section 9, Diagnostics of the HDI 3000 Field Service Manual

Volume 2 Procedures (P/N 4720-0015-03 or higher) for a descriptionof the Comprehensive Test.

9A--2.5 Channel Board Fault Isolation

Use the following procedure to isolate image artifacts to a specific

Channel Board, scanhead, or the Scanhead Select PCB.

1. Verify the system has booted up.

2. Connect scanheads to all three scanhead connectors.

3. Perform the Channel Walk Utility (paragraph 9A--2.6) using

scanheads connected to all three connectors.



9A--13

a. If image artifacts are seen at all three scanhead connectors

using multiple scanheads, the problem has been isolated to

a specific Channel PCB.

b. If the test results are bad with a scanhead connected to

only one connector, either the scanhead or the Scanhead

Select PCB is bad.

NOTE: You must exit diagnostics and reboot the system when

re-selecting a scanhead.

4. Swap two of the scanheads.

a. If the problem moves with the scanhead from one connec-

tor to the other, replace the scanhead.

b. If the problem does not move with the scanhead, replace

the Scanhead Select PCB.



9A--14

9A--2.6 Channel Walk Utility

The Channel Walk Utility is used to check receive and transmit func-

tionsofindividualchannelsorboards(Table9A--2).

Table 9A--2. Chan Walk Test Receiver and Transmitter Status

Chan Walk Test Receiver Status1 Transmitter Status2

Receive Walk 1 Board All receivers on selected boardturned on. All others off.

All transmitters should be on.Select “T” to turn them on.

Receive Walk 0 Board All receivers on selected boardturned off. All others on.


Receive Walk 1 Channel All receivers turned off except forselected receiver.


Receive Walk 0 Channel All receivers turned on except forselected receiver.


Transmit Walk 1 Board All receivers should be turned on.Select “R” to turn them on.

All transmitters on selected boardturned on. All others off.

Transmit Walk 0 Board All receivers should be turned on.Select “R” to turn them on.

All transmitters on selected boardturned off. All others on.



9A--15

Chan Walk Test Transmitter Status2Receiver Status1

Transmit Walk 1 Channel All receivers should be turned on.Select “R” to turn them on.

All transmitters turned off exceptfor selected transmitter.

Transmit Walk 0 Channel All receivers should be turned on.Select “R” to turn them on.

All transmitters turned on exceptfor selected transmitter.

1. The receiver status is independent of the transmitter status. Turning on the receiver does not affect the trans-

mitter.

2. The transmitter status is independent of the receiver status. Turning on the transmitter does not affect thereceiver.



9A--16

- To use the Channel Walk Utility:

1. Connect and select a scanhead to a scanhead.

2. Verify the system has booted up and is imaging.

3. Set the system gain and TGC settings to maximum.

4. Press Superkey and zero and type the correct username andpassword to access the Diagnostic Tools Menu. Use the track-

ball to select Tests, Utils. from the menu. Press SELECT. The

following menu items are displayed:

External Environment...

Machine...

5. Select Machine. Press SELECT twice. The following individual

test options are displayed:

2D Ultrasound

Color Ultrasound



9A--17

Doppler Ultrasound

M-Mode Ultrasound

Image Bus

Internal Ethernet

RF Bus

SCSI

Power Subsystem...

Display Subsystem...

Control Subsystem...

Processing Subsystem...

Acquisition Subsystem...

6. Select the Acquisition Subsystem from the list. Verify it is high-

lighted with reverse video.

7. Select the diamond to the left of the Test & Utilities option at thebottom of the display. Press SELECT. The display appears as in

Figure 9A--1.

8 S l E d SELECT Th di l i



9A--18

8. Select Execute and press SELECT. The display appears as in

Figure 9A--2.

9. Move the cursor to the blank box under the word ChanWalk.Press SELECT. The displayed cursor changes from a shaded

box to an “I” shape.

10. Press the “h” key on the keyboard to display the help screen

(Figure 9A--3). The first six items on the displayed list indicatethe capabilities of the ChanWalk Utility. The remaining items

indicate the options available to the service representative.

(Refer to step 13.)

NOTE: The most commonly used test within this utility is to check

for receiver gain or “drop-out”. Press the greater than or less

than keys (> or <) to initiate default settings for receiver gain

(single receivers walked on).

11. Select OK at the bottom of the display to exit the help screen.

Press SELECT. The system appears as in Figure 9A--2.

12 M th t th b b l Ch W lk P SELECT



9A--19

12. Move the cursor to the box below ChanWalk. Press SELECT.

The cursor changes from a shaded box to an “I” shape.

13. With the “I” shaped cursor in the box below ChanWalk, type anyof the following characters on the keyboard to obtain the

desired results. The typed characters will not be displayed in

the box, but the beamformer status will change.



9A--20

Print

Figure 9A--1. Channel Walk Utility Test Screen



9A--21

Figure 9A--2. Channel Walk Utility Selection Screen



9A--22

Chan--Walk utilityoptions available to

the servicerepresentative

Capabilities of Chan--Walk Utility

t

T

rR

0

1

Figure 9A--3. Channel Walk Utility Help Screen

Chan Walk Utility Setup



9A--23

Chan Walk Utility Setup

D “D” to display a list of the current Chan Walk Utility parame-

ter settings or beamformer status (Figure 9A--4). This optionis used for reference only. Select OK at the bottom of the

display to exit the beamformer status screen.

D “M” to change from transmit to receive or from receive to

transmit

D “B” to change from channel to board or from board to chan-

nel

D “1” to walk on a channel or board (selects walk 1)

D “0” to walk off a channel or board (selects walk 0)

Receive Commands

D “>” to increment an individual channel or board

D “<” to decrement an individual channel or board

NOTE: The following parameters will not change on the display until

“>” or “<” has been pressed.

D “R” to enable all receive channels



9A--24

D R to enable all receive channels

D “r” to disable all receive channels

D “s” to check a particular receive channel. (Press “s”, then

enter the desired channel number, then press Enter.)

D “B” to change from channel to board or from board to chan-

nel

D “D” to review the current parameter settings.

Transmit Commands

D “T” to enable all transmit channels

D “t” to disable all transmit channelsD “>” to increment an individual channel or board

D “<” to decrement an individual channel or board

D “S” to check a particular transmit channel. (Press “S”, then

enter the desired channel number, then press enter.D “B” to change from channel to board or from board to chan-

nel

D “D” to review the current parameter settings.

NOTE: Refer to steps 3 and 4 of paragraph 9A--2.5 to determine if



9A--25

NOTE: Refer to steps 3 and 4 of paragraph 9A 2.5 to determine if

the problem is the scanhead, the Scanhead Select PCB or a

Channel Board.

14. Refer to Figure 9A--5 for information required to interpret the

displayed test results.

15. To exit the ChanWalk Utility, select Quit at the bottom of the dis-

play and press SELECT.



9A--26

Figure 9A--4. Channel Walk Utility Parameter Settings

2 Receive “sectors” are displayed due to receiver



9A--27

multiplexing

This text line indicates re-ceiver status. Refer toTable 9A--2.

This text line indicatestransmitter status.

Refer to Table 9A--2.

Elem = Scanhead ele-ment number or blank

Pin = S/H Select PCB ZIF

connector pin or blank

Board = 0--7 or 0--3Device = 0--3Channel = 0,1 or 0--3Element = 0,1

Indicates Element

(The image shows twoelements. 6210 and 6211are the same for receive.)

Indicates Device

Indicates Board

Indicates Channel

Figure 9A--5. Typical Receive Walk 1 Board Channel Walk Test

9A--2.7 ECG Gain Tests



9A--28

9A 2.7 ECG Gain Tests

The ECG Gain Tests check the ECG signal amplification and signal

path from the ECG simulator through the DDEA and ADAPTR PCBs

and to the display.

- To use the ECG Gain Tests:

1. Verify the system has booted up.

2. Press Superkey and zero. Type the correct username and

password o access the Diagnostic Tools Menu. Use the track-

ball to select Tests, Utils. from the menu. Press SELECT. The

following menu items are displayed:


Machine...

3. Select Machine. Press SELECT twice. The following individual

test options are displayed:

2D Ultrasound

Color Ultrasound



9A--29

Doppler Ultrasound

M-Mode Ultrasound

Image BusInternal Ethernet

RF Bus

SCSI

Power Subsystem...Display Subsystem...



Acquisition Subsystem...4. Select the Control Subsystem. Press SELECT twice. The fol-

lowing options are displayed:

SYSCPU

HD DriveMO Drive

IMEM

DDEA

5. Select DDEA. Press SELECT.



9A--30

6. Select the Test and Utilities option at the bottom of the display.

Press SELECT.

7. Connect an ECG simulator into the DDEA ECG connector.

8. Set the ECG simulator to 60 BPM and 0.5 mv amplitude.

9. Select ECG Gain Test or ECG Test. Select Execute.

10. Select Start Test. Press SELECT.

11. Read the test results from the results window. Run the test

twice to verify the results. If the ECG Test fails replace the

DDEA.

9A--3 Diagnostic Tools Menu (CSR Diagnostics)



9A--31

g ( g )

The Diagnostic Tools Menu displays the following options:

D User Login

D Tests, Utils.

D Error Log

D Configuration

D Options

D Fake Scanhead

D Close

- To access the Diagnostic Tools Menu:

1. Press and hold Superkey then press zero on the keyboard. The

Machine Diagnostics menu is displayed.


board. Press RETURN. The cursor moves to the Password

field.




9A--32

keyboard.

4. Use the trackball to move the cursor to OK. Press SELECT. TheDiagnostic Tools Menu is displayed.

5. Refertoparagraph9A--3.1through9A--3.8forinformationon

the Diagnostic Tools Menu Options. Use the trackball to select

the desired item from the menu. Press SELECT.

9A--3.1 User Login

The User Login option is not useful to field personnel.

9A--3.2 Tests, Utils.

The Tests, Utils. option is used to enter any of several Comprehen-

sive Test sub-tests (paragraph 9A--4) or to display the Test and Utili-ties Menu. The Test and Utilities menu options depend on the soft-

ware version. Systems with 36.06 software and below have the fol-

lowing options:

D Comprehensive Test



9A--33

D Display Feature List

D Enable/Disable Looping of Bootup

D Module Flash Loading Always Done

D Module Flash Loading Disabled

D Module Flash Loading on Next Boot

D PCB’s Bootup Error Status

D PCB’s Bootup Status

D Show Bootup Status Report

Systems with 38.15 software and above have the following options:

D Comprehensive Test

D Disable Flash Mismatch Notification

D Disable Flash Mismatch Notification on Next Boot

D Display Feature List

D Enable Flash Mismatch Notification

D Enable/Disable Looping of Bootup

D PCB’s Bootup Error Status



9A--34

D PCB’s Bootup Status

D Show Bootup Status Report

- To display the Tests and Utilities Menu and to execute the menu

options:

NOTE: The menu options are described after this procedure.

1. Use the trackball to select Tests, Utils. from the Diagnostic Tools

Menu. Press SELECT. The following menu items are displayed:

External Environment...Machine...

2. Select Machine. Press SELECT once. The Machine... option is

highlighted with a dashed box.

3. Use the trackball to select the diamond to the left of the Tests

and Utils option at the bottom of the display. Press SELECT.

The Test and Utilities Menu is displayed.

4. Move the cursor to the desired menu option. Press SELECT.



9A--35

5. Move the cursor to Execute in the center of the display.

6. Press SELECT to initiate the desired option.

Comprehensive Test

Refer to Section 9, Diagnostics of the field service manual (P/N4720-0015-03 or higher) for a description of the Comprehensive Test.

The test takes from 8 to 12 minutes to run depending on the installed

software version. The Comprehensive Test comprises the sub-tests

that are listed in Table 9A--4.

Display Feature List (30.05 Software and Above)

The display feature list displays hardware and software features of aparticular system. The display feature list was implemented with

30.05 software. Refer to Table 9A--3 for information regarding each

displayed feature.

Table 9A--3. Displayed Feature Information



9A--36

Feature Option

SWBuild

Level

Change

Status

Software

Option P/N HW Required NotesVideo Type NTSC 30.05 Added 8501-8665-01 -- 1

PAL 31.03 Added 8501-8666-01 -- 2

Access NetworkLink

On/Off -- -- 8501-8633-01 --

Access Disk Link On/Off 32.04and up

Added 8501-8668-01 -03 Upper UIF-04 Lower UIF3500-1560-03 or3500-1474-04 or-61 DDEA

WebLink On/Off -- -- 8501-9155-01 --

Extended DopplerCapability

On/Off 30.05only

Changed -- 8500-8507-01 3

On/Off 31.03and up

Changed -- 8500-8507-01 4

SoftwareChangeSW

Build



9A--37

Feature NotesHW RequiredSoftware

Option P/NChangeStatus

BuildLevelOption

Language English 30.05and up

Changed 8501-8523-02 8500-8523-02 5

French 31.03and up

Changed 8501-8525-02 8500-8525-02 5

German 31.03and up

Changed 8501-8524-02 8500-8524-02 5

Line Voltage 120 V 30.05and up

Changed -- 8500-8533-01 7

230 V 31.03and up

Changed -- 8500-8534-018500-8536-018500-8536-02

8

ECG Off All InitialRelease

-- 3500-1560--XXDDEA

On 30.05 Added -- 8500-8663-01(Domestic)8500-8664-01 (In-ternational)

9

SoftwareChangeSW

Build



9A--38



BuildLevelOption

ECG -- Physio Off All InitialRelease

--

On 3 Added --

DDEA Type(DDEA BaseNumber)

InitialRelease

-- Refer to servicemanual4721-0015-XX

Added --

Image Memory 16 MB InitialRelease

-- 8500-8667-02 10

32 MB All Initial

Release

-- 8500-8667-01 11

Control Panel / UIF Configuration

Maps 1,2, 3, 4

31.03 Added Refer toSB 3000--12 Rev B

12

Frame Grabberfor VCR

On/Off 30.05 Added -- 7500-0717-07 orhigher and

7500-0683-08/-09

13

31.03 Changed 8501-8689-01 7500-0717-07 orhigher and7500-0683-08/-09

SoftwareChangeSW

Build



9A--39



BuildLevelOption

Color M-mode On/Off 30.05 Added -- 7500-0818-08 orhigher

Stan-dardfeature

31.03and up

Changed 8501-8688-01 7500-0818-08 orhigher

14

Steered CW On/Off 30.05 Added -- -- 15

31.03and up

Changed 8501-8687-01 FEC, DOPACQ,SSP, APS

16

MachineDiagnostics

On 23.05 --36.06

Initial re-lease

-- --

Off 38.15and up Added -- --

Channel BoardsType

8 bd set All Initialrelease

-- See Note 17 17

4 bd set 31.03

and up

Added -- See Note 18 18

AIFOM Type 0769 -- -- 7500-0769-XXase

number) 0965 -- -- 7500-0965-XX

SoftwareChangeSW

Build



9A--40



BuildLevelOption

Triple Mode On/Off 8501-8694-01

Frame GrabPCMs

On/Off 30.05and up

-- 7500-0683-08/-09

Frame Grab PIMs On/Off

3D Color Power

Angio

On/Off 8501-8695-01

TSI Patient Opti-mization

8501-9109-01

AIM Type withoutregula-

torsMagneto OpticalDrive

On/Off

Product Family HDI

Product Model 8500-0030-01

Research Link On/Off

NOTES:



9A--41

1. Prior to 30.05, video type was coupled with 120V/60Hz line voltage (required 3500-1578-03 ACIM) and

8501-8533-01 MO file option.

2. Prior to 31.03, video type was coupled with 230V/50Hz or 230V/60Hz line voltage (required 3500-1579 or

3500-1580 ACIM) and 8501-8534-01 or 8501-8536-01/02 MO file.

3. ST CW/CW/TCD: Configured by presence of DOPACQ PCB (7500-0762) contained in 8500-8507-01. All

30.05 systems with Extended Doppler have ST CW capability.

4. CW/TCD: Configured by presence of DOPACQ PCB (7500-0762) contained in 8500-8507-01. ST CWbecomes separate software option.

5. The 8500-852X-01 contains the appropriate Upper and Lower User Interface Assemblies. Refer to the Con-

figuration section of this manual. French and German not supported on 30.05.

6. The 8501-8533-01 also contains the 3500-1578-XX ACIM 120V/60 Hz.

7. At 30.05 software and above there is no longer a Software Options P/N for configuring line voltage. The

8500-8533-01 contains the 3500-1578-XX ACIM 120V/60Hz.

8. At 31.03 software and above there is no longer a Software Options P/N for configuring line voltage. The

8500-8534-01 contains the 3500-1579-XX ACIM 240V/50Hz NTSC/PAL. The 8500-8536-01 and -02 con-tains the 3500-1580-XX ACIM 240V/60Hz NTSC.

9. 8500-8663-01 and 8500-8664-01 contain 3500-1474-XX DDEA PCB and ECG lead sets.

10.Standard for all systems shipped after approx. 12/15/95. 8500-8667-02 contains the 3500-1839-XX IMM

PCB.



9A--42

11.8500-8667-01 contains 7500-0933-XX IMM PCB.

12.Requires correct hardware and Maps configured by diagnostics. Maps 1, 2, 3 ,4 select the installed UIF. Map 1is the -02 Upper/Lower UIFs. Map 2 is the -03 Upper/Lower. Map 3 is the -03/04 Upper and -04/05 Lower UIFs.

Map 4 is the -04/05 Upper and -05/05 Lower UIFs.

13.All systems shipped with 30.05 have framegrab capability.

14.Color M-Mode was disabled in 31.03 and re-instated in 32.04.15.Standard with Extended Doppler option on systems shipped at 30.05.

16.ST CW becomes separate software option. Refer to the Configuration section for part numbers of the required

boards. Also requires Extended Doppler option.

17.Standard hardware for systems which shipped prior to 9/1/95. Requires 7500-0819-XX Channel PCBs,7500-0770-XX AIM PCB, and 7500-0822-XX Scanhead Select PCB.

18.Standard hardware for systems shipped after 9/1/95. Requires 7500-0974-XX Channel PCBs,

7500-0977-XX AIM PCB, and 7500-0976-XX Scanhead Select PCB and 8000-0999-05 or higher FEC PROM

kit. Requires 31.03 or higher software.

Enable/Disable Looping of Booting



9A--43

The Enable/Disable Looping of Booting option allows the system to

continuously reboot until it is told to stop. This option is used to trou-

bleshoot intermittent system bootup problems. The boot-looping

option is not a test with pass-fail criteria.

- To enable/disable looping of booting:

1. Turn system power on.

2. Access the Tests and Utilities Menu. Select the Enable/Disable

Looping of Booting option.

3. Select Execute. A message is displayed in the diagnostics win-

dow stating that the machine will reboot in 1 minute unless

Execute is selected again.

NOTE: The system will go through a complete bootup cycle. After

each complete bootup cycle, the display appears as in

Figure 9A--6.

4. To exit the bootup looping option, select Stop Looping. If Stop

Looping is not selected within one minute the system will



9A--44

p g y

reboot.

NOTE: You must select Stop Looping to exit. If system power is

turned off, you will initiate a new bootup cycle, however, the

system stays in the bootup looping mode after power-up.

5. If you are troubleshooting an intermittent bootup problem, re-enter the diagnostics and access the Error Log.



9A--45

Figure 9A--6. Bootup Looping Mode

Module Flash Loading Always Done (36.06 Software andBelow)



9A--46

)

For engineering use only. Not for field use.

Module Flash Loading Disabled (36.06 Software andBelow)

For engineering use only. Not for field use. Disables the FlashLoading Always Done option listed above.

Module Flash Loading on Next Boot (36.06 Software and

Below)Module flash loading consists of loading erasable PROMs with soft-

ware. It is necessary only during the initial bootup after a PCB has

been replaced or during an upgrade. (The system may take up to fif-

teen minutes for the initial bootup due to flash loading.) This optionaffects only the first bootup after the option is selected.

Module flash loading occurs on the AIFOM, SSP PSP1, ADAPTR,

and PCM PCBs.



9A--47

NOTE: This option must be selected before each PCB replacement.

NOTE: The automated software installation process automatically

sets the Module Flash Loading on Next Boot as part of the

software upgrade.

NOTE: With 38.15 software and above the flash loading utility has

been changed to automatically flash load during every

bootup cycle, if needed. Refer to “Flash Mismatch Notifica-

tion” later in this section.

- To turn on the module flash loading:

1 T bl h h b d l l



9A--48

1. Troubleshoot the system to board level.

2. Access the Tests and Utilities Menu. Select the Module Flash

Loading on Next Boot option.

3. Select Execute.

4. Turn system power off.

5. Replace the defective PCBs.

6. Power up the system. The bootup time may take as long as fif-teen minutes if the flash load is successful. Successive bootups

will take the regular amount of time.

PCB’s Bootup Error Status (36.06 Software and Below)

During the core bootup sequence the individual PCBs conduct self



9A--49

During the core bootup sequence, the individual PCBs conduct self-

tests to check circuit operation. The individual PCBs then talk to the

SYSCPU to communicate the bootup status of the PCB. If there wereerrors, they are displayed on the monitor when this option is

selected. Only the PCB or PCBs that reported an error during bootup

will be displayed. If an error is displayed, perform additional trouble-

shooting and diagnostics to confirm bootup status results.

NOTE: The PCB’s bootup error status is reset each time the system

is rebooted. The error status must be run immediately after

the system displays a system diagnostic alert indicating a

bootup error.

NOTE: Most error codes may not be caused by the PCB reporting

the error. For example, a front end error code may actually

be caused by the FEC, AIM, Channel PCBs, or ScanheadSelect PCB. An error code reported from the MPS may actu-

ally be caused by a problem on the MPS, APS, DPS, or

ACIM.

For systems with 38.15 software and above, PCB bootup slot status

and configuration errors are identified by the error name and the er-

t t i th b d f th E lt if th PCB



9A--50

ror target in the body of the message. Errors result if the PCB proc-

essor does not respond to queries from the system CPU or if the

PCB responds and the configuration (PCB dash number) is not what

the CPU expected. In previous software versions, the errors were re-

ported by generic error IDs for any given PCB or slot.

PCB’s Bootup Status

This option displays the bootup status of all PCBs. It displays bootup

errors as described in the previous paragraph (PCB’s Bootup Error

Status) and the pass condition of each PCB. The information dis-

played by this option is essentially the same as the information dis-

played by the PCB’s Bootup Error Status.

Show Bootup Status Report

The Show Bootup Status Report displays the bootup status of each

PCB as a pass--fail condition (Figure 9A--7).

Flash Mismatch Notification (38.15 Software and Above)

On systems with 38 15 software and above the machine diagnostics



9A--51

On systems with 38.15 software and above, the machine diagnostics

utilities related to firmware flashing (Module Flash Loading Always

Done, Module Flash Loading Disabled, and Module Flash Loading onNext Boot) were replaced with the following flash loading utilities:

D Disable Flash Mismatch Notification

D Disable Next Boot Flash Mismatch NotificationD Enable Flash Mismatch Notification

Upon bootup, the system queries each PCB to determine if new firm-

ware has been installed. If firmware has been installed (during PCB

replacement or an upgrade), the flash code will automatically be

loaded when the system power is turned on. The bootup time may

take several minutes if the system flash-loads the firmware. The new

flash loading utilities pertain only to system dialog alerts which are

displayed upon system bootup and occur due to flashing errors.

The Flash Mismatch Notification options cannot be changed by field

personnel.



9A--52

Figure 9A--7. Show Bootup Status Report

9A--3.3 Error Log (33.27 Software and Below)

NOTE: For information about the Error Log for 34 17 software and



9A--53

NOTE: For information about the Error Log for 34.17 software and

above, see paragraph 9A--3.4.

The Error Log (Figure 9A--8) may be used to display error informa-

tion, search f or a specific error, determine the error severity and the

PCB reporting the error, and control the types of errors displayed.

The Error Log display is divided into three functional sections. The

Errors box in the upper left of the display lists the errors. Specific

error information pertaining to the selected error is displayed in the

Error Information Box. The description of the selected error is dis-

played in the Error Description box across the bottom of the display.



9A--54

Errors Box

Error

Information Box

ErrorDescription

Box

Figure 9A--8. Error Log (33.27 and below)

Error Log Procedures

When you enter the Error Log, if there are system errors, a list of



9A--55

y g y

errors is displayed in the Errors box with the most current error listed

at the bottom of the Errors box. There are five ways to find a specificerror within the error list.

D Selecting an error directly from the displayed error list

D Using the scroll bar to the right of the error listD Searching for a specific error number within the list

D Searching for a character string within the error description

D Displaying the previous 25 user events with the error description

Once the desired error has been displayed, specific error information

may be viewed in the Error Description Box across the bottom of the

error log display or in the Error Information Box to the right of the

error list. See “Error Log Reference Information” later in this section

for more information about the Error Log. Use the following proce-

dures to find specific errors and to display the 25 user events.

NOTE: If you need to use the Error Log and the Comprehensive

Test before rebooting the system, run the Comprehensive

Test before using the Error Log to prevent the Error Log



9A--56

Test before using the Error Log, to prevent the Error Log

from interfering with the Comprehensive Test. Or, use the

Error Log, reboot the system, then run the Comprehensive

Test.

- To select an error directly from the displayed list:

1. Use the trackball to move the cursor to the desired item in the

error list.

2. Press SELECT.

- To use the scroll bar to locate an error:

1. Use the trackball to move the cursor to the up or down arrows

in the scroll bar to the right of the list of errors.

2. Press SELECT to scroll up or down through the list.

- To search for a specific error number:

NOTE: Errors are added and taken away from the Error Log on a



9A--57

y g

first-in-first-out basis. Consequently, the error numbers will

change as new errors are added to the Error Log.

1. Use the trackball to move the cursor to the Go To box below the

error list.

2. Press SELECT.

3. Type the desired error number from the keyboard.

4. Press Return on the keyboard.

- To search for a specific character string within the error description:

1. Use the trackball to move the cursor to the Search String box

below the Error Description Box.

2. Press SELECT.

3. Type the desired search string from the keyboard. The search

string can be a PCB abbreviation, a scanhead abbreviation, or

words from the error description (for example, “cold boot”).



9A--58

p ( p , )

4. Move the cursor to the Find box to the right of the Search String

box.

5. Press SELECT.

- To use the Error Log to display the previous 25 user events with the

error description:

1. Use the trackball to move the cursor to the Properties box at the

top of the display.

2. Press SELECT. The Error Log properties are displayed

(Figure 9A--9).

3. Use the trackball to move the cursor to Filter User Event. Select

Off.

4. Press SELECT.

5. Use the trackball to move the cursor to Close. Press SELECT to



9A--59

return to the Error Log. The user events are listed in the Error

Description Box.

Error Log Reference Information

Refer to Figure 9A--8 for the location of the Errors Box, Error

Information Box, and the Error Description Box.

Errors Box

Properties -- Displays the properties used to control the display of

Error Log information. Refer to Figure 9A--9.

Error List -- Displays the list of errors. The selected error is high-

lighted with reverse video.

Go To -- Enables the service representative to enter the error numberof the desired error to be searched for.

Clear Log -- Clears all errors from the error list.



9A--60

Figure 9A--9. Error Log Properties

Error Information Box

NOTE: The information in the Error Information Box pertains to the



9A--61

specific error selected in the error list.

Number of Occurrences -- Not implemented.

Severity -- Describes the severity of the error. The severity can be

Warning, Alert, Alarm, or Catastrophe. Warning is the least severe of the errors.

Reporter -- Describes the PCB or the module reporting the error.

Subsys -- Not useful to field personnel.

Func -- Not useful to field personnel.

Type -- Describes the type of the error. The error type can be hard-

ware, software, environment, configuration or assertion. (Assertion is

a type of software error.)

Proc -- Describes the processor reporting the error. The processor

may be the MOP, SCIP, DSP, or unknown.



9A--62

File -- Not useful to field personnel.

Error -- Not useful to field personnel.

Error Description Box

Description box -- The Error Description Box describes the selected

error. A number of error descriptions can be stored in a buffer.

Description Box scroll bar -- Enables the service representative to

scroll between the error descriptions stored in the description box.

Search String -- Enables the service representative to enter a char-

acter string from the error description that the Error Log will search

for. The search string can be any words from the error description

including a PCB abbreviation, scanhead abbreviation, or words like

“cold boot”, for example.

Find -- Activates the error search process if a search string has been

entered in the search string box.

C C



9A--63

Clear -- Clears the error descriptions from the descriptions buffer.

Save -- Not useful to field personnel.

Close -- Closes the error log.

Hide -- When selected, the system returns to the Diagnostic Tools

Menu without exiting the error log.

Error Log Properties

The error log properties control the type and the amount of informa-

tion displayed in the Error Log.

Error Handler -- Turns the Error Log on or off. When On is selected

errors are sent to the log. When Off is selected, no errors are logged.

Error Logger -- Not useful to field personnel.

Error--Tally -- Not useful to field personnel.

Suppress Repeat Messages -- When On is selected, if two of the

same type of error are detected back to back, only the first one is



9A--64

same type of error are detected back to back, only the first one is

retained in the log.Message Severity Filter -- Permits the service representative to

select the severity of the errors to be displayed in the error list. There

are four levels of severity. Ranging from least to most severe, they

are Warnings, Alerts, Alarms, and Catastrophes. No matter whichseverity level is selected, all higher severity levels will also be dis-

played in the error list. For example, if the Alert level is selected,

Alarm and Catastrophic errors are also displayed in the error list.

Filter User Event -- When Off is selected, the previous 25 userevents (keystrokes, switch activations, or control rotations) are dis-

played in the Error Description Box.

Match These Error/Test IDs -- Enables the service representative to

display to the error list only errors associated with a specific PCB.Enter the first two digits from the codes below. Leave the rest of this

field as question marks to retain the wildcard status and display all

the errors from that particular PCB.

1E MPS

1F PCM

02 ADAPTR



9A--65

03 AIFOM11 CPANEL

12 CPU

19 FEC

20 PIM

21 PSP1

23 SSP

Cancel -- Cancels any changes made to the error log properties

before they have been implemented. Resets any changes to the pre-vious settings.

Close -- Closes the Error Log properties and returns the display to

the Error Log.

9A--3.4 Error Log (34.17 Software and Above)

NOTE: For information regarding the Error Log for 33.27 software

and below see paragraph 9A 3 3



9A--66

and below, see paragraph 9A--3.3.

The Error Log (Figure 9A--10) was redesigned to be easier to use

and implemented into software version 34.17. The function of the

error log remains the same as the previous error log, however, the

user interface has changed. The error log may be used to displayerror information, search for a specific error, determine the error

severity and the PCB reporting the error, and control the types of

errors displayed.

The Error Log display is divided into three functional sections. TheError window in the upper part of the display lists the errors and gen-

eral error information. The Error Log Menu Bar contains the error log

controls. These controls allow the service representative to control

the displayed error information and to search the error list. The ErrorDescription Box located across the bottom of the display contains

specific error information pertaining to the selected error.

390 10/17/96 11:27:16 Sys Func Bootup Last Error Logged

389 10/17/96 11:27:16 Sys Func Bootup.Last Error Logged


Machine Error Log

02 88045B01) Software Version

CPU MOP Configuration Recove

nfiguration Recoverable: (1202--



9A--67

400 10/21/96 14:51:58 Sys Func Config.Config Invalid399 10/21/96 14:51:57 Machine.Config Changed





394 10/17/96 16:10:33 Machine Shutdown

393 10/17/96 11:27:32 Sys Func Config.Config Invalid

392 10/17/96 11:27:31 Machine.Config Changed391 10/17/96 11:27:16 Sys Func Bootup.Last Error Logged


Machine Power Down Event

Comparing the ”installed” and th

13 ”expected” component configed/od0

02--88045B01) Software Version

Comparing the ”installed” and th13 ”expected” component config

ed/od0

02--88045B01) Software Version

CPU MOP Configuration Recove

nfiguration Recoverable: (1202--

Show: Log Summary Hide Close

Groupby Fault

UserEvents

ErrorId’s

SearchList

StackTrace

Sys.Data

ClearLog Print Top Bottom

ErrorWindow

Error LogMenu Bar

Error

DescriptionBox

Figure 9A--10. Error Log (34.17 and above)

Error Window

When you enter the Error Log, a list of errors is displayed in the Error

window with the most current error listed at the bottom of the window.



9A--68

window with the most current error listed at the bottom of the window.

If the error log is full the most current error number is 400. If the errorlog is not full, the most current number may be any number between

1 and 399. The Error window also contains the following information

regarding each error: date/time of occurrence, error ID number (may

be toggled on or off), type of error, and an error description.

NOTE: Errors are added and taken away from the Error Log on a

first-in-first-out basis. Consequently, the error numbers will

change as new errors are added to the Error Log.

The service representative can scroll through the list of errors using

the scroll bar to the right of the error window, or use the Top/Bottom

controls to jump to the beginning or end of the error list. The service

representative can also use search functions of the Search List

option located on the Error Log Menu Bar to find specific error

information.

Errors listed using green text are considered normal events that

occur during system bootup. Normal system shutdowns (using the

ON/STANDBY switch) are also listed in green text.



9A--69

Error Log Menu Bar

The error log menu bar contains controls that are used to control the

type and the amount of the displayed error information and to search

the error list.

The control options are turned on when the indicator boxes (located

next to the control option name) are green. Move the cursor with the

trackball to the menu bar control option and press SELECT to turn

the option on or off. Refer to the following paragraphs for specificinformation on each control option.

Group by Fault

When this option is turned on, all errors reported due to a single root

cause are grouped together by horizontal lines across the display.

User Events

When this option is turned on, the error list is displayed in two col-

umns with a chronological list of the user events that precede each



9A--70

g p

error.

Error Id’s

When this option is turned on, the 12-digit error codes are added to

the list of displayed error messages.

Search List

Displays a list of criteria, which may be used to search for specificerrors (Figure 9A--11). Refer to the Error Log Search Procedures lat-

er in this section for information on how to search for specific errors.

Machine Error Log

Diags -- Hardware

Error Type: Error Id (? = match any; Can be incomplete)



9A--71


SearchReset CancelHardware--Related Errors

Diags -- Configuration

Runtime -- Communication

Ambiguous

Internal -- Assertion

Major -- Uif FailureMajor -- Service Call

Recoverable

Normal Event

Keyword -- search error description:

Figure 9A--11. Error Log Search List Criteria

Stack Trace

Not useful to field personnel.



9A--72

Sys Data

This option is used to display a list of the system control settings and

system parameters (Figure 9A--12) that were in effect at the time of

the system error. It is only available during normal run-time errors

and only if system data was saved at the time the error occurred.

(For example, Sys Data is not available during bootup, because the

system has not initialized and the system imaging parameters have

not been set up yet.)

The saved control settings and system parameters include: scan-

head ID, 2D, Doppler, and color imaging parameters.

Machine Error Log

System State Data Values:

Port 0Port 1Port 2

462Ah0000h074Ch

Dop RayDop FocusDop Scroll Rate

00.00 cm0 cm/sec

Color Start DepthColor Stop DepthColor Start Ray

0.00 cm0.00 cm0



9A--73


Return

Port 2

Port 32D Start Depth2D Stop Depth2D Start Ray2D End Ray2D Line Increment2D Line Density2D Frame Alt idx2D Left/Right

2D Top/Bottom2D Number of Zones2D Focal Zone (0)2D Focal Zone (1)2D Focal Zone (2)2D Focal Zone (3)2D Focal Zone (4)2D Zoom Mag2D X Pan

2D Y Pan

074Ch

000Fh0.16 cm15.93 cm0254201True

False19.00 cm0.00 cm0.00 cm0.00 cm0.00 cm1.000.00

0.00

Dop Scroll Rate

Dop Steer AngleDop Sv DepthDop Sv SizeDop Velocity PRFDop Display FmtDop Wall FilterDop 2D lines Per GapPhysio ECG OnDisplay Source

0 cm/sec

0 Deg0.00 cm0.00 cm0 Hz00010

Color Start Ray

Color End RayColor DMD OnColor Emboss IndexColor SensitivityColor PRF ActualColor PRF TargetColor Steering AngleColor Line DensityColor MM Ray line

Color MM PRFColor MM Wall FilterMMmode Ray lineMMode Display FmtMMode Speed

0

00000 Hz0 Hz0 Deg00

0 Hz0000

Figure 9A--12. System Data Used at System Power Down

Clear Log

Clears all error instances from the error log. The error log is backed

up on the hard drive prior to clearing the log.



9A--74

Print

When selected, a print dialog box is displayed, (Figure 9A--13) which

enables the service representative to select error-log printing options

and print the error log.

Machine Error Log

Print Options:



9A--75


Print Selected Error Only

Print Entire Error Log

Print Errors to1 400

Print to Output Port

Save to Disk File

Print Error Descriptions

Print User Events

Cancel Print

Figure 9A--13. Error Log Printing Options

Top

When selected, the system jumps to the beginning of the error list

(error 1).



9A--76

Bottom

When selected, the system jumps to the end of the error list (up to

error 400).

Log

When selected, the standard error log display appears on the monitor

(Figure 9A--10).

Summary

When selected, the error log summary (Figure 9A--14) displays a list

of the errors that occurred and a tally of each error’s occurrences.



9A--77

The errors listed in the error log summary are sorted into the follow-ing categories:

D Normal bootups

D Diagnostic-detected errors requiring a service call (Diags Service

Errors)

D Normal run-time errors requiring a service call (Run-time Service

Errors)

D Errors not requiring a service call (Recoverable Errors)

08/08/96 to 10/22/96

195 -- 1202--6608--1004 SysFuncBootup LastErrorLogged049 -- 1202--8B04--5B01 Machine ShutDown

Error Log Summary

Errors from:

245 Normal Bootups Logged:ed/od0Machine Power Down Event



9A--78

Error Number: 0x07 File for componCRASH -- Task = ”tmonitor”

049 1202 8B04 5B01 Machine ShutDown001 -- 1202--8806--0301 Machine ShutDown


None000 Diags Service Errors:

002 -- 1F02--1FE7--0801 Boards SoftwareAssertion001 -- 1202--8B01--0101 Machine Ambiguous

011 Runtime Service Errors:

058 -- 1202--8618--1607 Machine ConfigChanged054 -- 1202--8613--0416 SysFuncConfig.Configinvalid006 -- 1E02--1E32--0101 Boards.BoardSpecificError004 -- 1202--5002--3107 SCBus.CommDataSendTimeout003 -- 1202--6A02--2B19 SCBus.InterruptedSystemCall002 -- 1202--5801--0A16 SysFuncFloss.InternallyPropagatedError002 -- 1202--4D03--4F01 PSP.CommDataReceiveTimeout

144 Recoverable Errors:

Machine Power Down EventPower Down Event

13 ”expected” component configuraComparing the ”installed” and the ”eError Number: 0x2e Fan set to MaxNo response on the scbus from theNo descriptive message found.Board query failure errorSignal path startup failed. Failure o

Figure 9A--14. Error Log Summary

Hide

When selected, the system returns to the Diagnostic Tools Menu

without exiting the error log. The error log may be accessed without



9A--79

reconstructing it (by choosing Error Log from the Diagnostic ToolsMenu).

Close

When selected, the system exits the error log and returns to the

Diagnostic Tools Menu. If the system is in this state, and the service

representative attempts to access the error log, the error log must be

reconstructed.

Error Log Search Procedures- To select an error directly from the displayed list:

1. Use the trackball to move the cursor to the desired item in the

error list.

2. Press SELECT to highlight the error. The error information is

displayed in the error description box.

- To use the scroll bar to page through the error list:

1. Use the trackball to move the cursor above or below the rectan-

gle in the scroll bar to the right of the list of errors.



9A--80

2. Press SELECT to scroll up or down through the list one page at

a time.

- To use the scroll bar to move through each error in the error list:

1. Use the trackball to place the cursor to the up or down arrows in

the scroll bar to the right of the list of errors.

2. Press SELECT to scroll up or down through each error in theerror list.

- To search for a specific character string within the error description:

1. Use the trackball to move the cursor to the Search List control

in the error log menu bar.

2. Press SELECT. The search display appears (Figure 9A--11).

3. Move the cursor to the Keyword box.



9A--81

4. Press SELECT.

5. Type in the desired keywords.

6. Move the cursor to the Search control.

7. Press SELECT. The error list is displayed containing errors with

the desired keywords.

9A--3.5 ConfigurationThe system has the capability to recognize part numbers of PCBs

installed in the system. The system also knows what part number to

expect for each PCB (Figure 9A--15). The installed and expected

part numbers are stored in configuration files on the hard drive. If a

new PCB is installed, the system recognizes the part number as new.

The service representative then has the option of choosing Save

Installed as Expected, which saves the installed part number as the

part number the system expects to find the next time the service rep-

resentative selects the Installed option.



9A--82

The system cannot use the PCB part number information to checkwhether a PCB is compatible with other PCBs or with the system

software. The configuration files also cannot be used as a compre-

hensive history file of system configuration. Once the Save Installed

as Expected option is selected (Figure 9A--16), the part number of anewly installed PCB is what the system expects to see even if the

PCB is incompatible with the other PCBs or with system software.

Once the Save Installed as Expected option is selected, there is no

way to go back and retrieve the pre-existing configuration file.

NOTE: Use the part number information in the configuration files to

order a PCB replacement that is “Like-for-Like”. Always refer

to the HDI 3000 Field Service Manual and the most current

manual changes to resolve PCB and firmware compatibilityissues.

- To search the list of PCBs in the configuration file for a particular

PCB:

1. Use the trackball to move the cursor to the Search String box



9A--83

(Figure 9A--15). Press SELECT.

2. Type the name (abbreviation) of the PCB to be searched for.

3. Use the trackball to move the cursor to the Find control. Press

SELECT. If the system is searching up the list, the PCB is dis-

played on the top line. If the system is searching down the list,

the PCB is displayed on the bottom line.



9A--84

Machine ID, <not applicable>, 0000005f1906, 0, 0,Hard--Disk Software, 4252--0743--06, 038.04, 0X0,

APS, PS1, 7500--0764, 04, 04,DPS, PS2, 7500--0766, 02, 02,

MPS, PS3, 7500--0765, 04, 04,MPS_SCIP_Firmware, mps.hex, 2.22, 0xC422,MPS_FIRMWARE, mps.hex, 0xC422,

ACIM, PS4, 3500--1578, 02, 02,DDEA, A1F, 7500--0843, 02, 02,FEC, A4F, 7500--0818, 06, 06,FEC SCIP Firmware, SCIP.HEX, 003.03, 0xCCA3,FEC_Firmware, fecndy.hex, 033.00, 0xE1B3

FEC_Software, fec.out, 038.04, 0xD43D

Expected Configuration:

Figure 9A--15. Machine Configuration Display



9A--85

Installed vs. Expected Configuration:

9 “expected” component configurations are not installed in the system:(1) Hard--Disk Software, 038.04, 0x0,(2) FEC_Software, fec.out, 038.04, 0xD43D,(3) PCM_Software, pcmxserv.ld, 005.00, 0x3660,

(4) PSP1_Software, pspmop.fls, 010.09, 0x48C,(5) PSP1_Software, pspx1.fls, 004.00, 0x7A68,(6) PSP1_Software, pspx2.fls, 005.00, 0xA0C9,(7) ADAPTR_Software, adaptr.fls, 005.12, 0xEEC3,(8) ADAPTR_Software, trapdiag.fls, 002.00, 0x3696,(9) ADAPTR_Software, pap_app.fls, 003.04, 0xCD5D,9 installed components are not in the list of “expected” configurations:(1) Hard--Disk Software, Integ., , 0x0,

(2) FEC_Software, fec.out ,038.13, 0x9EF7,

Figure 9A--16. Machine Configuration Display

9A--3.6 Options

The Options selection (Figure 9A--17) displays the authorized and

unauthorized machine options loaded onto the hard drive. When the

A th i d l ti i l t d f th t f th di l th



9A--86

Authorized selection is selected from the top of the display, the sys-tem displays all the machine options that are available and enabled

for that particular system.

When the Unauthorized selection is displayed, all options are dis-

played that are available but not enabled (not purchased). The

options may not be enabled due to the system hardware or software

configuration. When the Both selection is selected, both the Autho-

rized and the Unauthorized options are shown on the same display.

When Both is selected, if the option is authorized, it is indicated witha yes to the right of the item; if it is unauthorized, it is indicated with a

no.

In addition to the information displayed on the Options display of the

User Diagnostics, the system Password, Version, and Machine ID

number are also displayed.

If a particular system is to be upgraded, insert a Machine Options

disk (P/N 4252-0738-01) into the optical drive and select Read New

Options Settings. The system then reads the Machine Options files

on the optical disk and copies them to the hard drive. The Options file

then should reflect the new configuration of the system



9A--87

then should reflect the new configuration of the system.

NOTE: Perform the Machine Options Software Backup on Hard

Drive procedure (paragraph 9A--5) af ter performing the

Read New Options Settings procedure.

- To search the Options list for a particular option:

1. Use the trackball to move the cursor to the Search String box.

Press SELECT.

2. Type the name (or keywords) of the desired item to be

searched for.

3. Use the trackball to move the cursor to the Find box. Press

SELECT. If the system is searching up the list, the desired item

is displayed on the top line. If the system is searching down the

list, the desired item is displayed on the bottom line.



9A--88

Figure 9A--17. Machine Options Display

9A--3.7 Fake Scanhead

The Fake Scanhead selection fakes a scanhead on a specific scan-

head port. When a fake scanhead is selected and connected, the

system hard drive down loads the appropriate scanhead files to the



9A--89

system hard drive down-loads the appropriate scanhead files to theFEC RAM, which sets up the FEC with the appropriate imaging

parameters.

The system transmits and receives through the open scanhead con-

nector like it would with a regular scanhead. However, because thereis no acoustic coupling between the transmit and receive pins of the

scanhead connector, the received signal is mainly noise. The only

difference between a regular scanhead and a fake scanhead is that

the system “thinks” there is a scanhead connected. The fake scan-

head has been identified as a regular scanhead.

If you need to use the Fake Scanhead utility in conjunction with the

Tests, Utils option on the Diagnostic Tools Menu, select the desired

fake scanhead prior to entering Tests, Utils. If you use the Tests,

Utils. option first, the system must be rebooted when exiting the

Tests, Utils. option. When the system is rebooted, the scanhead infor-

mation is lost.

For the fake scanhead selection to work, the scanhead port cannot

have a scanhead connected.

1. Select Fake Scanhead from the Diagnostic Tools Menu using

the trackball and the SELECT button A list of scanheads is dis-



9A--90

the trackball and the SELECT button. A list of scanheads is dis-played (Figure 9A--18).

2. Select the desired scanhead port. The scanhead port cannot

have a scanhead currently connected. If the port has a scan-

head connected, disconnect the scanhead before proceeding

with step 3.

3. Select the desired scanhead from the list. Use the scroll bar on

the right side of the display and press SELECT to move up anddown the list. The selected scanhead is highlighted with reverse

video.

4. Select Close at the bottom of the display. The display returns to

the Diagnostic Tools Menu.

5. Select Close on the Diagnostic Tools Menu.

6. Press the Scanhead function key on the far left of the keyboard.

The display appears similar to Figure 9A--19.

7. Move the cursor to the blank scanhead port selected in step 2.

Press SELECT The Tissue Specific Presets are displayed



9A--91

Press SELECT. The Tissue Specific Presets are displayed.

8. Select the clinical options from the items on the left of the dis-

play and the optimized presets from the items on the right.

9. Press the Scanhead function key on the keyboard to return to

the selected system operating mode.



9A--92

<Disconnect Fake Scanhead>C4--2 40RC3.5 76RC7--4 40RC8--4VC8--5

C9--5 ICTCIVT 5CL10--5 26mmCT8--4CW 10CW 2CW 5

Current port is now the “Middle” port.

Figure 9A--18. Fake Scanhead Selection



9A--93

Figure 9A--19. Scanhead Tissue Specific Setups Display

9A--3.8 Close

This option exits the system out of the Diagnostic Tools Menu. After

the option is selected, a message is displayed noting that system

parameters have changed and the system must be rebooted tol ti



9A--94

pa a ete s a e c a ged a d t e syste ust be ebooted toresume normal operation.

- To exit the system out of the Diagnostic Tools Menu before returning

the system to the customer:

1. If a message is displayed noting that system parameters have

changed, set the ON/STANDBY switch to STANDBY.

2. Set the ON/STANDBY switch to ON.

9A--4 Accessing Individual Diagnostic Tests

Diagnostic software is currently being validated and the results of the

individual diagnostic tests should be used with caution. Results of

one test may corrupt the results of the following test or tests, so, thet t t b i ifi d t lid lt



9A--95

y p g , ,tests must be run in a specific order to ensure valid results.

Under some circumstances, it may be necessary to run only the sub-

test that failed during the Comprehensive Test. If running individual

tests was not possible, it would take up to several minutes to verify

whether a repair was successful.

If the Comprehensive Test fails, the name of the failed sub-test is dis-

played on the monitor. In the list of sub-test menu paths inTable 9A--5, the sub-test names are bold. Refer to the failed sub-test

name in the list, then follow the menu path on that line to navigate

within the diagnostic menus.

- To access individual diagnostic tests:

CAUTION

Some individual tests require that the system be in

a certain operational mode (Freeze, M-mode, 2D,) f h b d bl DO



9A--96

p ( , , ,etc.) for the test to be accurate and repeatable. DO

NOT PERFORM INDIVIDUAL TESTS THAT ARE NOT

CONTAINED WITHIN THE COMPREHENSIVE TEST.

Refer to the individual tests in Table 9A--5 for the

menu paths associated with individual tests con-

tained in the Comprehensive Test.

1. Refer to the Comprehensive Test results to determine

which sub-test to access. Refer to Table 9A--5 for the sub-test menu path.

2. Reboot the system.

3. Perform steps 1 through 4 of paragraph 9A--3 (Accessing the

Diagnostic Tools Menu).

4. Select Tests, Utils., from the menu. Press SELECT. the follow-

ing menu items are displayed:


Machine...



9A--97

5. Select Machine. Press SELECT twice. The following test

options are displayed:

2D Ultrasound

Color UltrasoundDoppler Ultrasound

M-Mode Ultrasound

Image Bus

Internal EthernetRF Bus

SCSI

Power Subsystem...

Display Subsystem...

Control Subsystem...Processing Subsystem...


6. Use the trackball and the SELECT button to select the succes-

sive menu items to move from one menu item to the next, fol-

lowing the menu path from Table 9A--5.

7. When the individual test results are displayed, reboot the sys-tem and run the test again to verify the test results are consis



9A--98

tem and run the test again to verify the test results are consis-

tent.

NOTE: The tests in Table 9A--4 are listed in the order they are per-

formed in the Comprehensive Test.

Table 9A--4. Comprehensive Test Sub-Tests

Tested Item Test Name Description

IMEM PCM-based Cell

Test

Performs IMEM bootup test

PSP1 Stand-alone

Test

Verifies all board functions that can be tested by built-in

tests

Tested Item DescriptionTest Name

PSP1 Operational Test Verifies PSP1 and PSP2 operation using PCBs external

to the PSP1 and PSP2 to generate input signals.

PIM Stand-aloneTest

Verifies all board functions that can be tested by built-intests



9A--99

Test tests

PCM Stand-alone

Test


tests

PSP--PCMBus

PSP to PCMBus

Sends data across the PSP--PCM bus to verify that ithas no shorts or opens.

PCM PCM to IMEM

Frame Transfer

Verifies PCM circuitry involved with transferring video

frames to and from image memory.

PCM PSCAN VideoBus

Verifies the Progressive Scan Video Bus and its trans-ceivers from the PCM to the PIM by sending data pat-

terns over the data lines. Sends 0x5555 and 0xAAAA

data patterns over data lines. Performs walk 0/1 tests

through all data lines.


PCM Interlace Video

Bus

Verifies the Interlace Video Bus and its transceivers

from the PCM to the PIM by sending data patterns over

the data lines. Sends 0x5555 and 0xAAAA data pat-

terns over data lines. Performs walk 0/1 tests through



9A--100

all data lines.

PIM VCR Video Bus Verifies the VCR Video Bus and its transceivers from

the PIM to the PCM by sending data patterns over the

data lines. Sends 0x5555 and 0xAAAA data patterns

over data lines. Performs walk 0/1 tests through all data

lines.

PSP1 Primary Buffer

Test

Disabled -- Verifies the mono/color serial output data

path and the pixel tag circuitry by injecting a test patternin the PSP1’s output buffer. The image is frame

grabbed by the PCM and compared to the expected

image.

PSP1 SecondaryBuffer Test

Disabled -- Function is the same as the function for thePSP1 primary buffer test.


ADAPTR Stand-alone

Test


tests

AIFOM1 Stand-aloneTest

Verifies all board functions that can be tested by built-intests



9A--101

Test tests

SSP1 Stand-alone

Test


tests

AQ--Bus ComprehensiveTest

Verifies AQ Bus between AIFOM--ADAPTR and AI-FOM--SSP. Sends 0x5555 and 0xAAAA data patterns

over data lines. Performs walk 0/1 tests through all data

lines. Uses all standard headers.

PD--Bus SSP to ADAPTR Verifies PD Bus between SSP--ADAPTR. Sends 0x5555and 0xAAAA data patterns over data lines. Performs

walk 0/1 tests through all data lines. Uses all standard

headers.

FEC Stand-alone

Test


tests

FEC Comp Test Verifies front end functions including FEC PCB.


FEC Comp Off Brd

Test

Verifies front end functions but not including FEC PCB.

CB0--7 FEC-based Test Invokes FEC-based test of each Channel PCBAIM FEC-based Test Invokes FEC-based test of AIM



9A--102

AIM FEC based Test Invokes FEC based test of AIM

DOPACQ FEC-based Test Invokes FEC-based test of DOPACQ

SHSEL Relay Test Invokes FEC-based test of SHSEL relays

InternalEthernet

SYSCPU toPCM

Verifies data can be sent between SYSCPU--PCM viathe internal Ethernet.

Image Bus SYSCPU to

IMEM -- All

modes

Verifies Image Bus between SYSCPU--IMEM. Performs

walk 0/1 tests through all address and data lines using

block mode.Image Bus ADAPTR to

IMEM -- All

modes

Verifies Image Bus between ADAPTR--IMEM. Performs


block mode.

Image Bus PCM to IMEM -- All modes

Verifies several combinations of image data compres-sion and decimation during image transfer.


Image Bus PSP to IMEM --

All modes

Verifies Image Bus between PSP--IMEM. Performs the


byte mode.

RF Bus FEC to AIFOM Verifies proper operation of the RF Bus when driven by



9A--103

RF Bus Test

p p p y

the FEC.

Table 9A--5. Comprehensive Test Sub-Test Menu Paths

Machine Acquisition CB0--7. FEC Based Test (8 CB systems)Subsystem CB0--3. FEC Based Test (4 CB systems)

FEC. Standalone TestAIM FEC Based Test



9A--104

AIM. FEC Based Test

SH Sel. Relay Test

DOPACQ. FEC Based Test

Processing PD Bus. SSP to ADAPTRSubsystem AQ Bus. Comprehensive Test

ADAPTR. Standalone Test

SSP1. Standalone Test

AIFOM. Standalone Test

Display PSP--PCM BusSubsystem PIM. Standalone Test

PIM. VCR Video Bus

PSP1. Operational Test

PSP1. Primary Buffer Test

PSP1. Secondary Buffer Test

PSP1. Standalone Test

PCM. Interlace Video Test

PCM. PCM--IMEM Frame Transfer

PCM. PSCAN Video Path



9A--105

PCM. Standalone Test

Image Bus ADAPTR to IMEM -- All Modes

PCM to IMEM -- All ModesPSP to IMEM -- All Modes

ControlSubsystem

DDEA. PCM Based Test

InternalEthernet SYSCPU to PCM

9A--5 File Management Utilities

The file management utilities are used to manage the system soft-

ware files and MO files saved to the optical drive or the hard drive.

The file management utilities include the following:



9A--106

D Download Error Log to Optical Disk

D Download System to Optical Disk

D Machine Options Software Backup on Hard Drive

D Machine Options Software Restore on Hard Drive

D System Backup on Hard Drive

D System Restore on Hard Drive

D Verify System Files

- To access the File Management Utilities:

1. Press and hold Superkey then press zero on the keyboard.

The Machine Diagnostics menu is displayed.


board. Press RETURN. The cursor moves to the Password

field.

3. In the Password field, type the appropriate information using thekeyboard.



9A--107


Diagnostic Tools Menu is displayed.

5. Select Tests, Utils., from the menu. Press SELECT. The follow-

ing menu items are displayed:

External Environment...Machine...

6. Select Machine. Press SELECT twice. The following test


2D Ultrasound

Color Ultrasound

Doppler Ultrasound

M M d Ult d



9A--108

M-Mode Ultrasound

Image Bus

Internal Ethernet

RF Bus

SCSI

Power Subsystem...

Display Subsystem...Control Subsystem...



7. Select the Control Subsystem option. Press SELECT. The fol-lowing options are displayed:

SYSCPU

HD DRIVE

MO DRIVE

IMEM



9A--109

IMEM

DDEA

8. Select HD DRIVE from the list. Select Test and Utilities from thebottom of the display. Press SELECT. The list of file manage-

ment utilities is displayed. (Refer to the bulleted list at the begin-

ning of this paragraph.)

9. Refer to the information in the paragraphs that follow to select

the desired file management utility. Select Execute.

Download Error Log to Optical Disk

The Download Error Log to Optical Disk option saves the error log,

results of the last Comprehensive Test, the user event log, and other

diagnostic information to a blank formatted optical disk. The only dif-ference between this procedure and the Backup Diags Data proce-

dure in Section 9 of the field service manual is that the Backup Diags

procedure is accessed through the user diagnostics, and the Down-

load Error Log to Optical Disk procedure is accessed through theCSR diagnostics. Both procedures are applicable only to U.S. CSRs.



9A--110

CSRs from other countries should contact their respective Technical

Support Group prior to performing the procedure. This option is avail-

able only on software version 30.05 and higher.

The Download Error Log to Optical Disk option takes less than one

minute to complete unless there is a core file to copy, which takes an

additional 9 minutes. If there is a core file to copy, a message is dis-

played in the results window giving the system status.

Download System to Optical Disk

The Download System to Optical Disk option saves the system soft-

ware files on the hard drive to a blank formatted optical disk. The files

include all system software files, machine options, and user-defined

information. Use this option before performing an upgrade to a cus-

tomer system. If the upgrade is unsuccessful, the system may thenbe restored to the previous sof tware version using the Upgrade Sys-

tem From Optical Disk option in paragraph 9A--3.6. This option is

available only on software versions 33.09 and up.

NOTE: If the system will not boot up from the hard drive, and this

ti h b d t t ti l di k ith



9A--111

option has been used to generate an optical disk with a copy

of the system software, the system will boot from the optical

disk until the DDEA (or hard drive) has been repaired or re-

placed.

The Download System to Optical Disk option takes from 15 to 30

minutes to complete.

Machine Options Software Backup on Hard Drive

The Machine Options Software Backup on Hard Drive option makes

a backup of the machine options files located on the hard drive. Use

this option before performing an upgrade or after installing newoptions to a customer system. If the upgrade is unsuccessful, the

system may then be restored to the previous software version. The

option must be used with the Download System to Optical Disk andMachine Options Software Restore on Hard Drive options to suc-

cessfully restore the system to the previous software version.

The Machine Options Software Backup on Hard Drive option takesless than one minute to complete.



9A--112

Machine Options Software Restore on Hard Drive

The Machine Options Software Restore on Hard Drive optionrestores the machine options file backed up to the hard drive using

the procedure described in the previous paragraph. Use this option to

restore the previous system software version if an add-on upgrade

has been unsuccessful. The option must be used with the DownloadSystem to Optical Disk and Machine Options Software Backup on

Hard Drive options to successfully restore the system to the previous

software version.

The Machine Options Software Restore on Hard Drive option takesless than one minute to complete.

CAUTION

If the machine options have changed since the last

backup was performed, restoring the machine

options may disable system features. To prevent

disabling system features, perform the MachineOptions Software Backup on Hard Drive procedure

f di i lli h hi i



9A--113

after upgrading or installing the machine options.

System Backup on Hard DriveThe System Backup on Hard Drive option backs up system files

which are on the hard drive to another location on the hard drive. Use

this option before performing an upgrade to a customer system, if a

usable optical drive or optical disk is not available. If the upgrade isunsuccessful, the system may then be restored to the previous soft-

ware version. The option must be used with the System Restore on

Hard Drive option to successfully restore the system to the previous

software version.

The System Backup on Hard Drive option takes approximately 3 min-

utes to complete.

System Restore on Hard Drive

The System Restore on Hard Drive option restores system files

backed up to the hard drive using the procedure described in the pre-

vious paragraph. Use this option to restore the previous system soft-

ware version if an upgrade has been unsuccessful and a usable opti-

cal drive or optical disk is not available The option must be used with



9A--114

cal drive or optical disk is not available. The option must be used with

the System Backup on Hard Drive option to successfully restore the

system to the previous software version.

The System Restore on Hard Drive option takes approximately 3

minutes to complete.

Verify System FilesThe Verify System Files option verifies the system files by performing

cyclic redundancy checks (CRCs) on all read-only files (all files that

cannot be user modified). The Verify System Files option takes

approximately 2 minutes to complete.

9A--6 Upgrade System From Optical Disk

The Upgrade System From Optical Disk option is used to restore the

previous system software if an unsuccessful upgrade has been

attempted and the previous system software was stored to an opticaldisk via the Download System to Optical Disk option described in

paragraph9A--5



9A--115

paragraph9A 5.

NOTE: This option is not to be used during normal software

upgrades. Follow the instructions provided in the appropriatesoftware upgrade kit.

If the reinstall process is not successful, place the optical disk into the

drive and turn the system on. The system should boot up in a normal

manner.

- To access the Upgrade System From Optical Disk option:

1. Press and hold Superkey then press zero on the keyboard.The Machine Diagnostics menu is displayed.


board. Press RETURN. The cursor moves to the Password field.


keyboard.

4 Use the trackball to move the cursor to OK Press SELECT The



9A--116


Diagnostic Tools Menu is displayed.

5. Select Tests, Utils., from the menu. Press SELECT. The follow-ing menu items are displayed:


Machine...6. Select Machine. Press SELECT twice. The following test


2D Ultrasound

Color UltrasoundDoppler Ultrasound

M-Mode Ultrasound

Image BusInternal Ethernet

RF Bus

SCSI

Power Subsystem...Display Subsystem...

Control Subsystem



9A--117




7. Select the Control Subsystem option. Press SELECT. The fol-

lowing options are displayed:

SYSCPUHD DRIVE

MO DRIVE

IMEM

DDEA

8. Select MO DRIVE from the list of displayed options. Select Testand Utilities from the bottom of the display. The following

options are displayed.

FORMAT Optical DiskOptical Disk Eject Enable

Upgrade System From Optical Disk



9A--118

Upgrade System From Optical Disk

9. Insert the optical disk with the system files saved using the

Download System to Optical Disk procedure (paragraph 9A--5).

10. Select Upgrade System From Optical Disk.

11. Select Execute. The system reinstalls the previous software

version onto the hard drive.

9B Diagnostic Tables

This section is provided to assist new and infrequent troubleshooters

in isolating hardware faults to a specific field-replaceable-unit (FRU).

Successful use of this information requires the user to isolate the



9B--1

problem to a fault listed in Table 9B--1 and reference the table called

out for that identified fault. Identify the primary symptoms from the list

in the specific table, then the secondary symptom, then the tertiarysymptom, and finally the suspect FRU is identified.

The order of these tables and the entries in them is significant. The

“Suspect FRUs” for later entries often assume that there was no

match for earlier entry “Symptoms”. Thus, it is strongly recommended

that you start with the top-level table and go to lower-level tables as

directed.

NOTE: Do not swap out PCBs before troubleshooting has beencompleted.

9B--1 Top-Level Fault IndicationsThis table serves three functions:

D Road map to other fault isolation tables

D As a reference of which PCBs are likely to be involved with a spe-

cific error



9B--2

D Recommended top-level fault isolation sequence

Table 9B--1. Top-Level Fault Indications

SYMPTOMS

Primary Secondary Tertiary

Suspect FRUs(Primary / Secondary)

Instructions ( ' ), Detail Reference

User interface fails to boot ' See referenced tables. Table 9B--2

Bootup Test failure is indicated ' See referenced tables. Table 9B--3

A System Diagnostics or Run-time Alert appears ' See referenced tables. Table 9B--4

An operational fault is indicated Table 9B--5 to be added. Table 9B--5

SYMPTOMS

ReferencePrimary Reference

Suspect FRUs(Primary / Secondary)

Instructions ( ' ), DetailTertiarySecondary

Machine Functional Tests / TestPatterns failure is indicated

' See referenced tables. Table 9B--6

Machine Test failure is indicated ' See referenced tables Table 9B 7



9B--3

Machine Test failure is indicated ' See referenced tables. Table 9B--7

9B--2 User Interface Fails to Boot -- SummaryThe following circuit boards provide critical services to the rest of the

machine. They are often listed as “Secondary Suspect FRUs”.

D PIM -- video clocksD AIM -- system clocks

D MPS -- reset signal

D SYSCPU -- polls built-in-diagnostics on smart circuit boards

D CTRBRD -- interconnects

Table 9B--2. User Interface Fails to Boot

SYMPTOMS Suspect FRUs

Primary Secondary Tertiaryr mary econ ary ,

Instructions ( ' ), Detail

User interface fails toboot (End-user diag-nostics can not be

d ith

1. End-user accessi-ble LEDs or TestPatterns indicatef lt

a. ACIM LEDs do notindicate normalstatus

ACIM, MPS, DPS AIM, APS, CTRBRD



9B--4

accessed with fault<Setup> : <Diags>). b. Control panel LEDs

do not indicate nor-mal status (flicker 5times within 5seconds afterpower up)

PCM, CPANEL

ACIM, MPS, DPS, AIM,CTRBRD

c. PIM Bootup video

test pattern (moni-tor displays color/ graybar pattern) ismissing or incor-rect

MONITOR, VIDEO CABLE,

PIM, IIM

ACIM, MPS, DPS, AIM,CTRBRD

SYMPTOMS Suspect FRUs(Primary / Secondary),Instructions ( ' ), DetailPrimary

Suspect FRUs(Primary / Secondary),Instructions ( ' ), DetailTertiarySecondary

d. PCM Bootup videotest pattern (moni-tor displays bluescreen) is missingor incorrect, and

PCM, SYSCPU, DDEA, HDSW

PIM, AIM, MPS, CTRBRD



9B--5

PIM Bootup videotest pattern (color/ graybar) is OK.

2. CSR accessibleLEDs (for boardsinvolved in corebootu Test Pat-

a. MPS LEDs do notindicate normalstatus

ACIM, MPS, DPS

AIM, APS, CTRBRD

, -terns or serial con-sole output indicatefault

b. SYSCPU serialconsole output isnotnormal(seeTable9B--8)

SYSCPU, DDEA, HDSW,PCM, AIM

MPS, CTRBRD

c. 3. SYSCPU LEDs

do not indicate nor-mal status

SYSCPU

AIM, MPS, CTRBRD



d. PIM LEDs do notindicate normal

status

PIM

AIM, MPS, CTRBRD

e. PCM LEDs do not PCM



9B--6

e. PCM LEDs do notindicate normalstatus

PCM

PIM, AIM, MPS, CTRBRD

9B--3 Bootup Tests Indicate Failure -- SummaryThe following circuit boards provide critical services to the rest of the


D PIM -- video clocks

D AIM -- system clocks



9B--7




The circuit boards that contribute power (ACIM, MPS, DPS), software

load and execution capabilities (SYSCPU, DDEA, HDSW), and user

interface capabilities (PCM, PIM, IIM, Video Cable, MONITOR) areassumed to be functional. These FRUs are not listed as “Secondary

Suspect FRUs” unless they provide another function related to the

symptom.

Table 9B--3. Bootup Tests Indicate Failure




Bootup Tests indicatefailure

General Instructions:1. Press <Setups>, <Diag-

nostics>, <Show BootupSt t R t d



9B--8

Status Report> and<Execute> to display allboot up test failure codes

2. Enter CSR diagnostics andexecute Machine. PCB’sBootup Error Status. Thiswill display the name of theboard reporting the error.

NOTE: The PCB reportingthe fault may not be thefaulty board especially if thePCB is the FEC or theMPS.

3. Use the Error Log to deter-mine the history of bootuptest failures.



4. Check for fault indicationsper Table 9B--1 (order is

significant). This includeschecking for the following:

¯ Core bootup fault indica-



9B--9

¯ Core bootup fault indications

¯ Bootup test failures

¯ Operational faults¯ Machine functional test

failures¯ Machine Comprehensive

Test failures



Bootup Tests indicatefailure

1. Power SubsystemBootup fault is indi-

cated.

a. MPS Self testfailed and/or MPS

LEDs do not indi-cate normal status

ACIM, MPS, DPS, APS

AIM, SYSCPU, CTRBRD

2. Display Subsystem a PIM Self test failed PIM



9B--10

2. Display SubsystemBootup fault is indi-cated.

a. PIM Self test failedand/or PIM LEDsdo not indicate nor-

mal status

PIM

AIM, MPS, SYSCPU, CTRBRD

b. PCM Self testfailed and/or PCMLEDs do not indi-cate normal status

PCM

PIM, AIM, MPS, SYSCPU,CTRBRD

c. CPANEL Self testfailed and/or CPA-NEL LEDs do notindicate normalstatus (flicker 5times within 5seconds afterpower up)

CPANEL

PCM, AIM, MPS, SYSCPU,CTRBRD



d. PSP1 Self testfailed and/or PSP


PSP1, PSP2




9B--11

3. Control SubsystemBootup fault is indi-

cated.

a. SYSCPU Self testfailed and/or

SYSCPU LEDs donot indicate normalstatus

SYSCPU

AIM, MPS, CTRBRD

b. IMEM Self testfailed and/or IMEM


IMEM, PCM


4. Processing Sub-system Bootupfault is indicated.

a. ADAPTR Self testfailed and/or ADAPTR LEDs donot indicate normalstatus

ADAPTR




b. SSP1 Self testfailed and/or SSP1


SSP1


c. AIFOM1 Self test AIFOM1



9B--12

failed and/or AIFOM1 LEDs do

not indicate normalstatus

ADAPTR, AIM, MPS, SYSCPU,CTRBRD

5. Acquisition Sub-system Bootupfault is indicated.

a. FEC Self test failedand/or FEC LEDsdo not indicate nor-

mal status

FEC, SHSEL, DOPACQ, AIM,CBx


9B--4 System Diagnostics or Run-time AlertAppears -- Summary

This section lists high-level categories of alerts (for each board, pro-

cessor or driver that may report alerts). It also lists all specific alertsthat may be reported to a user in 30.05 or higher software. All alerts

are sorted by error ID.



9B--13

Look for the exact error ID first. If you can’t find it, then select the

nearest match according to the “#” wild card character.

The following circuit boards provide critical services to the rest of the


D PIM -- video clocks

D AIM -- system clocks


D SYSCPU -- polls built-in-diagnostics on smart circuit boardsD CTRBRD -- interconnects

The circuit boards that contribute power (ACIM, MPS, DPS), softwareload and execution capabilities (SYSCPU, DDEA, HDSW), and user

interface capabilities (PCM, PIM, IIM, Video Cable, MONITOR) are

assumed to be functional. These FRUs are not listed as “Secondary

Suspect FRUs” unless they provide another function related to the

symptom.



9B--14

Table 9B--4. System Diagnostics or Run-time Alert Appears




A System Diagnosticsor Run-time Alertappears.

####--####--#### General instructions:1. Press the Superkey and

CSI keys to the left of theSetups key on the key-



9B--15

p y yboard. Make a print of thelarge screen or write down

the alert information. (If Service Access Diagnosticsis disabled there is no largescreen.)

2. If the error is a Run-time

alert, also print the userevent information (using thearrow keys to scroll up/ down in the large alertscreen).




A System Diagnosticsor Run-time Alert

appears.

####--####--####

Applicable to U.S. CSRsonly: If an optical disk isavailable,refertotheBackupDiagsDataproce-d i S ti 9At



9B--16

dureinSection9Atobackuptheerrordatatothe

disk. Use the Backup DiagsData to save the Error Log,User Event Log, the lastComprehensive Test result,and other troubleshootingdata. Send the optical disk

to TSG at ATL (MS 440)Bothell.

3. Access User diagnosticsand execute Show MachineConfiguration. Note the

system software versionand the Machine ID.



4. Search for a more exactalert ID match below. This

will provide information tosupport a quick high level of fault isolation. Continuewith steps 5 and 6.



9B--17

p

5. Use the Error Log to deter-

mine the history of this par-ticular alert.

6. Check for fault indicationsper Table 9B--1 (order issignificant). This includes

checking for the following:¯ Core bootup fault indica-

tions¯ Bootup test failures¯ Operational faults¯ Machine functional test

failures¯ Machine Comprehensive

Test failures



0201--02##--#### = ADAPTR SCIP

ADAPTR

other SCIP boards, AIM, MPS,SYSCPU, CTRBRD

' Search for more exact matchbelow.



9B--18

0202--02##--#### =

ADAPTR MOP

ADAPTR, [After bootup:

upstream boards] AIM, MPS, SYSCPU, CTRBRD


0210--02##--#### =

ADAPTR TRAP

ADAPTR, upstream boards





0211--02##--#### = ADAPTR PAP




0301--03##--#### = AIFOM1



9B--19

030 03 AIFOM1 SCIP

O

other SCIP boards, AIM, MPS,

SYSCPU, CTRBRD' Search for more exact match

below.

0302--03##--#### = AIFOM1 MOP

AIFOM1, [After bootup:upstream boards]



1101--11##--#### =CPANEL MOP

CPANEL, PCM

AIM, MPS, SYSCPU, CTRBRD' Search for more exact match

below.



1201--####--#### =SYSCPU SCIP

SYSCPU

Other SCIP boards, AIM, MPS,SYSCPU, CTRBRD

' Search for more exact matchwith error codes below.



9B--20

1202--####--#### =

SYSCPU MOP

Almost all FRUs (if faulty, most

FRUs can cause the SYSCPUsoftware to detect errors).

' Search for more exact matchwith error codes below.



1202--35##--#### =SYSCPU MOP,

Boards--ACIM driver

(generally config.retrieval problem)

ACIM

MPS

1202 36## #### ADAPTR t b d



9B--21

1202--36##--#### =SYSCPU MOP,

Boards--ADAPTRdriver



1202--3604--0104 =SYSCPU MOP Com-munications Alarm,

bAdaptrFormat.c,adaptrSyncCB() =

Invalid Start/StopResponse from ADAPTR

(Reported to User) ADAPTR




1202--3604--2A01=SYSCPU MOP Com-

munications Alarm,bAdaptrFormat.c,bAdaptrFormat_IsS-topped() =

(Reported to User) ADAPTR


Detail: This alert has been seenin one Mfg. system. The end-user recovery procedure has



9B--22

ADAPTR didn’t stop

within 5 seconds

user recovery procedure hasnot been defined

1202--3604--2B01 =SYSCPU MOP Com-munications Alarm,bAdaptrFormat.c,bAdaptrFormat_IsS-tarted() =

ADAPTR didn’t startwithin 5 seconds

(Reported to User) ADAPTR, upstream boards




1202--37##--#### =SYSCPU MOP,

Boards--AIFOM driver

AIFOM1, upstream boards



1202--3704--0104 = (Reported to User) AIFOM1



9B--23

SYSCPU MOP, Com-

munications Alarm,bAifom1Format.c,aifom1SyncCB() =

Invalid Start/StopResponse from AIFOM


1202--3704--2E01 =SYSCPU MOP Com-munications Alarm,bAifom1Format.c, bAi-fom1Format_IsS-topped() =

AIFOM didn’t stopwithin 5 seconds

(Reported to User) AIFOM1 AIM, MPS, SYSCPU, CTRBRD



1202--3704--3101 =SYSCPU MOP Com-

munications Alarm,bAifom1Format.c, bAi-fom1Format_IsS-tarted(), =

AIFOM did ’

(Reported to User) AIFOM1, upstream boards




9B--24

AIFOM didn’t start

within 5 seconds1202--38##--#### =SYSCPU MOP,Boards--AIM driver

(generally config.

retrieval problem)

AIM, FEC


1202--39##--#### =SYSCPU MOP,Boards--APS driver

(generally config.

retrieval problem)

APS, MPS




1202--3C##--#### =SYSCPU MOP,

Boards--CB’s driver(generally config.retrieval problem)

FEC, CBx


1202--3D##--#### = (Boards are identified in the



9B--25

1202 3D## #### =SYSCPU MOP,

Boards--Commondriver

(Boards are identified in thedetailed alert message).

1202--3F##--#### =SYSCPU MOP,Boards--CPANEL driver

CPNLIF, PCM


1202--40##--#### =SYSCPU MOP,Boards--CPU driver

SYSCPU

AIM, MPS, CTRBRD



1202--41##--#### =SYSCPU MOP,

Boards--CTRBRDdriver


SYSCPU, CTRBRD

AIM, MPS



9B--26

1202--42##--#### =

SYSCPU MOP,Boards--DDEA driver


DDEA, SYSCPU

AIM, MPS, CTRBRD

1202--43##--#### =SYSCPU MOP,Boards--DOPACQdriver


FEC, DOPACQ




1202--44##--#### =SYSCPU MOP,

Boards--DPS driver(generally config.retrieval problem)

DPS , MPS


1202--45##--#### = FEC, MPS, APS, SHSEL, CBx



9B--27

SYSCPU MOP,

Boards--FEC driver

, , , ,



1202--4503--0504 =SYSCPU MOP Com-

munications Alarm,bFecFormat.c, Fec-SyncCB() =

Invalid Start/StopResponse from FEC

(Reported to User) FEC, MPS, APS, SHSEL




1202--4503--2F01 =SYSCPU MOP Com-

munications Alarm,bFecFormat.c, bFec-Format_IsStopped() =

FEC didn’t stop within5 seconds





9B--28

5 seconds

1202--4503--3001 =SYSCPU MOP Com-munications Alarm,bFecFormat.c, bFec-Format_IsStarted() =

FEC didn’t start within5 seconds



1202--46##--#### =SYSCPU MOP,Boards--IIM driver


IIM




1202--47##--#### =SYSCPU MOP,

Boards--IMEM driver(generally config.retrieval problem)

IMEM


1202--4A##--#### = MPS, DPS, APS, ACIM



9B--29

SYSCPU MOP,

Boards--MPS driver AIM, MPS, SYSCPU, CTRBRD

1202--4C##--#### =SYSCPU MOP,Boards--PIM driver

PIM


1202--4D##--#### =SYSCPU MOP,Boards--PSP driver

PSP1, PSP2 , upstreamboards


' Search for more exact match

below.



1202--4D03--4F01 =SYSCPU MOP Com-

munications Alarm,bPsp1Format.c,bPsp1Format_IsIma-geUpdated() =

PSP didn’t update

(Reported to User) PSP1, PSP2 , upstreamboards

AIFOM, ADAPTR, SSP, FEC.



9B--30

PSP didn t update

image within 10seconds.

1202--4E##--#### =SYSCPU MOP,Boards--SHSEL driver

AIM

FEC

1202--4F##--#### =SYSCPU MOP,Boards--SSP driver

SSP, upstream boards





1202--4F02--3201 =SYSCPU MOP Com-

munications Alarm,bSsp1Format.c,bSsp1Format_IsS-topped() =

SSP didn’t stop within

(Reported to User) SSP, upstream boards




9B--31

SS d d s op5 seconds

1202--4F02--3301 =SYSCPU MOP Com-munications Alarm,bSsp1Format.c,bSsp1Format_IsS-

tarted(), =

SSP didn’t start within5 seconds

(Reported to User) SSP, upstream boards




1202--50##--#### =SYSCPU MOP,

Boards--Transportdriver

(Boards are identified in thedetailed alert message).

Detail: This alert occurs whenthere is a low level communica-tions failure between theSYSCPU and other boards.

B## (R d U ) A U di i



9B--32

1202--5514--2B## =

SYSCPU MOP Soft-ware Alarm, cDiagsMa-chine.c,cDiagsMa-chine_PCBBootupSta-tus=A hardware PCBDiagnostic Alert has

been detected.

(Reported to User) 1. Access User diagnostics.

2. Execute the Show BootupStatus utility.

1202--5615--340A =SYSCPU MOP Soft-ware Alarm, cFecsE-vents.c, cFecsEv-

ents_newNotify =

FECS -- NewNotifyFailed

(Reported to User) FEC, MPS, APS, SHSEL, CBx,AIM, DOPACQ




1202--5615--4001 =SYSCPU MOP Soft-

ware Alarm, cFecsE-vents.c, cFecsEv-ents_PostNotify() =

FECS -- PostNotifyFailed

(Reported to User) FEC, MPS, APS, SHSEL, CBx,AIM, DOPACQ




9B--33

1202--561C--0D01 =SYSCPU MOP Config-uration Catastrophe,cFecsXdcr.c,CFecsXdcr_Prom-ChecksumTest() =

Scanhead PROMChecksum Mismatch

(Reported to User) SH, SHSEL, FEC



1202--5719--0D01 =SYSCPU MOP Config-

uration Catastrophe,cFecsXdcr.c,XdcrNormalizationGet() =

Scanhead PROM

(Reported to User) SH, SHSEL, FEC



9B--34

Checksum Mismatch

1202--6201--#### =SYSCPU MOP Com-munications Alarm,Sethernet.c, (variousfunctions)

(various communica-tions failures)

(Reported to User) SYSCPU, PCM


Detail: SYSCPU to PCM Ether-net communications error was

detected. In some cases thiscould be due to client softwareerrors.



1202--6201--0A04 =SYSCPU MOP Com-

munications Alarm,Sethernet.c, proces-sUnsolicitedMsg

(Reported to User) SYSCPU, PCM


User is required to reboot if thisalert occurs. Alert is due to acommunications problem withunsolicited PCM messages.



9B--35

1202--6B01--0101 =SYSCPU MOP Soft-ware Catastrophe,sSignal.c, sSignalHan-dler() =Exception at PC

0xXXXXXXXX

SYSCPU, HDSW (HDSW =Hard Drive Software)

Detail: This alert indicates theSYSCPU’s processor detectedan “exception” such as a BusError, Illegal Instruction,

Address Error, Divide by Zero,etc. This error is usuallycaused by corrupted systemsoftware or by SYSCPU hard-ware problems (where the pro-gram can not be correctly

fetched from memory).



1202--8618--1604 =SYSCPU MOP Config-

uration Alarm, VMach-CompConfigMgr_Init.c,VMachCompCon-figMgr_ValidateInstal-ledVsExpectedConfig()=

(Reported to User) ' To isolate to FRU: Check allmismatches against packslip.

If allowed, run Diags : Con-figuration : Save AsExpected, then rebootmachine. If not allowed andtype = hardware/firmware,replace hardware FRU If



9B--36

=

Installed Configurationdid not match lastsaved expected.

replace hardware FRU. If

not allowed and type = soft-ware, run Diags : SWConfigCheck and if necessary,reload software and/orreplace DDEA.

' To isolate within FRU: Hard-ware: verify configurationresistors are correct perboard revision. Firmware:Verify PROM version andinstallation. Software: verify

installation was done cor-rectly.




1202--861C--0D1F =SYSCPU MOP Soft-

ware Alarm, VMa-chOptsMgr.c, VMa-chOptsMgr::SyncMa-chOptsData() =

M01: Invalid password

(Reported to User) SYSCPU, OPTFILE


' Inspect error descriptionstring.

If it contains “M02”, then thecurrent machine option filewas destined for another



9B--37

M02: Bad Option File --Machine ID Mismatch

M03: Bad Option File --missing version, pass-word or machine ID; orfile open failed.

was destined for another

machine (ID), the machinehas a faulty ID chip, or themachine option file was tam-pered with. To correct, installa new option file and/or IDchip in the machine.

If it contains “M01”, then themachine’s ID is as expected,but the state of the optionsdoes not correspond to thepassword.




1202--861C--0D1F =SYSCPU MOP Soft-

ware Alarm, VMa-chOptsMgr.c, VMa-chOptsMgr::SyncMa-chOptsData() =

M01: Invalid password

(Reported to User) This is caused by a machineoption file that has been tam-

pered with or which is faulty.To correct, install a newoption file in the machine.

If it contains “M03”, then themachine option file is faulty



9B--38

M02: Bad Option File --Machine ID Mismatch

M03: Bad Option File --missing version, pass-word or machine ID; orfile open failed.

or has been tampered with.To correct, install a newoption file in the machine.

1902--19##--#### =FEC MOP

FEC, MPS, APS, SHSEL, CBx,AIM, DOPACQ




1902--1980--#### =FEC MOP PROM

based Diagnostic TestError

FEC

SYSCPU, CTRBRD

1902--1981--#### =FEC MOP DownloadedCode-based Diagnostic

FEC

SYSCPU, CTRBRD



9B--39

Test Error1902--1982--#### =FEC MOP DownloadedCode-based DiagnosticTest Error -- FEC RAM

FEC

SYSCPU, CTRBRD

1902--1990--13## =FEC MOP Fast Chan-nel Board RAM Test:error: unique error databyte 0= channel boardnumber (0--7)

CBx

FEC, SYSCPU, CTRBRD



1902--1990--14## =FEC MOP Fast Chan-

nel Board Transmit-Test: error: uniqueerror data byte 0=channel board number(0--7)

CBx

FEC, SYSCPU, CTRBRD



9B--40

1902--1990--16## =FEC MOP AIM VoltageTest error

AIMFEC, SYSCPU, CTRBRD

1902--1990--17## =FEC MOP AIM Inter-

face Test error

AIM, FEC

SYSCPU, CTRBRD

1902--1990--26## =FEC MOP FGASEQInterface error

FEC, CB0

SYSCPU, CTRBRD



1902--1991--18## =FEC MOP TGC

SequencerTest error

AIM, FEC

SYSCPU, CTRBRD

1902--1991--19## =FEC MOP ScanheadSelect Test error

SHSEL, AIM

FEC, SYSCPU, CTRBRD



9B--41

1902--1991--22## =FEC MOP DownloadedSoftware CRC error

FEC, HDSW

SYSCPU, CTRBRD

1E01--1E##--#### =

MPS MOP

MPS, ACIM, DPS, APS

Other SCIP boards, AIM,SYSCPU, CTRBRD

1E01--1E80--#### =MPS MOP, “BootupSelftest Error”

MPS, ACIM, DPS, APS

FEC, AIM, SYSCPU, CTRBRD



1F02--1F##--#### =PCM MOP

PCM, upstream boards


2001--20##--#### =PIM MOP

PIM

Upstream boards, PCM, IIM,SYSCPU, CTRBRD



9B--42

2101--21##--#### =PSP1 SCIP

PSP1


2102--21##--#### =PSP1 MOP

PSP1, PSP2, [After bootup:upstream boards]




2102--2181--#### =PSP1 MOP, “Bootup

Selftest Error”

PSP1


2102--2183--01## =PSP1 MOP, “BootupSelftest Error”

PSP1




9B--43


PSP1


2102--2183--03## =

PSP1 MOP, “BootupSelftest Error”

PSP1



PSP2




2102--2183--07## =PSP1 MOP, “Bootup

Selftest Error”

PSP2


2102--2186--#### =PSP1 MOP, “BootupSelftest Error”

PSP1




9B--44

2301--23##--#### =SSP1 SCIP

SSP1


2302--23##--#### =SSP1 MOP

SSP1, upstream boards AIM, MPS, SYSCPU, CTRBRD

9B--5 Operational Fault is Indicated -- SummaryThis section is reserved for future use. Until then, call your technical

support center.

Table 9B--5. Operational Fault is Indicated






9B--45

9B--6 Machine Functional Test Fails -- Summary

These tests should only be run after the machine has been re-

booted. The RF--Bus test can only be run once (the machine must be

re-booted to run it again).

The following circuit boards provide critical services to the rest of themachine. They are often listed as “Secondary Suspect FRU’s”.










9B--46

assumed to be functional. These FRU’s are not listed as “Secondary

Suspect FRU’s” unless they provide another function related to the

symptom.





Color Back-end Testpasses

AIFOM, ADAPTR, SSP, IMEM

AIM, MPS, SYSCPU, PSP1,

PSP2, PCM, CTRBRD' Verify test is run before the

Machine ComprehensiveTest or other diagnostics.



9B--48

9B--7 Machine Comprehensive Test Fails --Summary

This test should only be run after the machine has been re-booted.

However, it may be repeated or looped without a re-boot.

The following circuit boards provide critical services to the rest of the

machine. They are often listed as “Secondary Suspect FRU’s”.



9B--49








assumed to be functional. These FRU’s are not listed as “Secondary

Suspect FRU’s” unless they provide another function related to thesymptom.

Table 9B--7. Machine Comprehensive Test Fails




Machine Test indicatesfailure

General Instructions:

1 N h d ID f



9B--50

1. Note the name and ID of the high-level tests thathave failed. (All high-leveltests and their IDs are iden-tified in the remainder of this table.)

NOTE: If the Machine Test wasrun from the user diagnosticinterface, only the ID of thefailed test will be displayed.(Test names will not be dis-

played.)




Machine Test indicatesfailure

2. Access User diagnosticsand execute Show Machine

Configuration. Note thesystem software versionand the Machine ID.

3. If the problem is difficult toisolate to a faulty FRU andif an optical disk is avail-

bl f h B k



9B--51

able, refer to the Backupags a a proce ure n

the service bulletin tobackup the error data to thedisk. use the Backup Diags

Data to save the Error Log,User Event Log, the lastComprehensive Test result,and other troubleshootingdata. Send the optical diskto TSG at ATL (MS 440)

Bothell.



4. See below for SuspectFRU’s and further instruc-

tions/references.

(Power SubsystemTests fail -- no post--bootup tests are cur-rently available).

Display Subsystem PSP1 Standalone Test PSP1 PSP2



9B--52

Display Subsystemtest(s) fail

PSP1.Standalone Testfails

(TestID = 0x21FE0500)

PSP1, PSP2


PSP1.Operational Testfails

(TestID = 0x21900000)

PSP1, PSP2, IMEMPIM, AIM, MPS, SYSCPU,CTRBRD



PIM.Standalone Testfails

(TestID = 0x56150100)

PIM







9B--53

Display Subsystemtest(s) fail

PCM.Standalone Testfails

(TestID = 0x1FFE0500)

PCM


PSP--PCM Bus.PSP--PCM Bus Test fails

(TestID = Disabled)

PSP1, PSP2, PCM




PCM.PCM IMEMFrame Transfer Test

fails(TestID = 0x56120100)

PCM, IMEM, PSP1, PSP2

PIM, AIM, MPS, SYSCPU,

CTRBRD

PCM.PScan Video BusTest fails

(TestID = 0x56120400)

PCM, PIM




9B--54

PCM.Interlace VideoBus Test fails

(TestID = 0x56120700)

PCM, PIM


PIM.VCR Video BusTest fails

(TestID = 0x56121000)

PIM, PCM AIM, MPS, SYSCPU, CTRBRD

PSP.Primary BufferTest fails

(TestID = 0x56110400)

PSP1, PSP2, PCM, PIM




PSP.Secondary BufferTest fails

(TestID = 0x56110700)

PSP1, PSP2, PCM, PIM


(Control Subsystemtest(s) fail -- no post--bootup tests are cur-rently available)



9B--55




Processing Subsystemtest(s) fail ADAPTR.StandaloneTest fails

(TestID = 0x56040100)

ADAPTR AIM, MPS, SYSCPU, CTRBRD

AIFOM1.StandaloneTest fails


AIFOM, ADAPTR




SSP1.Standalone Testfails


SSP


AQ--Bus.Comprehen-sive Test fails

(TestID = 0x56061900)

ADAPTR, AIFOM, SSP


PD--Bus SSP to ADAPTR SSP



9B--56

PD Bus.SSP to ADAPTR fails

(TestID = 0x56140400)

ADAPTR, SSP


Acquisition Subsystem

test(s) fail

FEC.Standalone Test

fails(TestID = 0x19FE0500)

FEC




CBx.FEC Based Testfails

(TestID’s:0x56070100 = CB0

0x56070400 = CB1

0x56070700 = CB2

0x56070A00 = CB3

0x56070D00 = CB4

CBx, FEC

AIM, MPS, APS, SYSCPU,

CTRBRD



9B--57

0x56070D00 = CB4

0x56071000 = CB5

0x56071300 = CB6

0x56071600 = CB7 )

AIM.FEC Based Testfails

(TestID = 0x56050100)

AIM, FEC





Acquisition Subsystemtest(s) fail

DOPACQ.FEC BasedTest fails

(TestID = 0x560A0100)

DOPACQ, FEC, CB0


SHSEL.Relay Test fails

(TestID = 0x19911900)

SHSEL, FEC


Machine Bus/Function Internal Ether- SYSCPU, PCM



9B--58

Machine Bus/Functiontest(s) fail

Internal Ethernet.SYSCPU to PCMTest fails

(TestID = 0x560E0100)

SYSCPU, PCM

AIM, MPS, CTRBRD

Image Bus.SYSCPU toIMEM fails

(TestID = 0x560B0700)

IMEM, SYSCPU


Image Bus.ADAPTR toIMEM fails

(TestID= 0x560B0A00)

IMEM, ADAPTR




Image Bus.PCM toIMEM fails

(TestID= 0x560B0D00)

IMEM, PCM


Image Bus.PSP toIMEM fails

(TestID = 0x560B1000)

IMEM, PSP1, PSP2


RF Bus.FEC to AIFOM AIFOM1, FEC



9B--59

fails

TestID = 0x55190D00 )

,


9B--8 Core Bootup -- SYSCPU Console OutputFault Symptoms

NOTE: Paragraph 9B--8 requires use of a laptop computer. If you do

not have access to a laptop, refer to the core bootup proce-

dure in Section 9 of Volume 2 of the Field Service Manual.



9B--60

Table 9B--8. Core Bootup -- SYSCPU Console Output Fault Symptoms




No SYSCPU serial console

messages appear

SYSCPU PROM Boot failed,

SYSCPU Serial Chip failed,Serial Cable connection failed,Terminal or Terminal Emulatorimproperly setup, TBD.

Machine Level Solution: Cor-

rectly configure terminal or ter-minal emulator (19.2 KBaud, 8



9B--61

minal emulator (19.2 KBaud, 8data bits, 0 stop bits, TBD), usecorrect serial cable, reseatserial cable, Swap out serialcable,terminal, terminal emula-

tor or SYSCPU.



The SYSCPU Serial consolemessage:

Mounting /hd0 ...Mounted /hd0

Mounting /od0...

Mounted /od0

is not exactly output.

SYSCPU PROM Boot failedand/or mount of hard and/oroptical disks failed.

Machine Level Solution: Swapout the SYSCPU, Swap out theDDEA, Checkout SYSCPU andDDEA CTRBRD connectors,replace CTRBRD

Board Level Solution: Check



9B--62

SYSCPU MOP PROM seating,Check SYSCPU MOP PROMversion, TBD.

The SYSCPU Serial console

message:

sysStartType = 80000002


PROM based bootup tests

detected a failure or crashed.

Machine Level Solution: Swapout the SYSCPU.

Board Level Solution: CheckSYSCPU Serial ID Chip seat-

ing, TBD.




SYSCPU Serial Number =000000 xxxxxx


SYSCPU could not read IDfrom Serial ID Chip.

Machine Level Solution:Replace Serial ID Chip,Replace SYSCPU.

Board Level Solution: ReplaceSerial ID Chip, TBD.


SYSCPU Boot Parameters arenot properly initialized



9B--63

message: not properly initialized.



...

auto--booting...

...boot device : scsi

processor number : 0

host name :

file name :

/hd0/peg_hd/pegasus.st

inet on ethernet (e) :149 59 240 162:ffffff00

Machine Level Solution: Loginto VxWorks with “root”, <pass-word> and change boot param-eters to match those at left.

Board Level Solution:



9B--64

149.59.240.162:ffffff00

host inet (h) :

gateway inet (g) :

149.59.240.30

user (u) : vxboot

flags (f) : 0x8

target name (tn) : sweden

startup script (s) :

/hd0/boot.vsh

is not exactly output (for sys-

tems set up to boot com-pletely from the hard disk).




Loading /hd0/peg_hd/pega-sus.st... xxxxxxx + xxxxxx

+ xxxxxxx

Starting at 0x1000...


The software image file couldnot be loaded from the disk intomemory.

Machine Level Solution: Re-install software, swap outDDEA (or hard disk), TBD.

Board Level Solution: TBD.


The SYSCPU could not initiatenetwork communications with



9B--65

message:

Attaching network interface

pcm1... done.


network communications withthe PCM.

Machine Level Solution:Reseat SYSCPU and PCM,swap out PCM, swap outSYSCPU, swap out CTRBRD.

Board Level Solution: TBD.




skNetIfConfig: ei1,149.59.49.201, pegcpu,

ffffff00

Mounting /hd0 .Mounted /

hd0

Mounting /od0 .Mounted /

TBD. Also, the SYSCPU couldnot load the startup script fromthe disk into memory and startexecuting it.



9B--66

od0

...

< start.vsh

# Start.vsh




The SYSCPU Serial con-

sole message:

#

# Start of non-operating

system type of load

sequence.

#

...

putenv(“HARD DISK SW VER-

TBD.



9B--67

( HARD_DISK_SW_VER

SION=4252- xxxx-xx

xxx . xx ”)

value = 0 = 0x0

...

Done executing startup

script /hd0/boot.vsh

...

services -- local

boards -- local

services -- externalboards -- external



Checking for presence of

boards...

CmoduleLoader.c(339):

Evaluating

./version/mod/modprog.

sys...

CmoduleLoader.c(706):

Evaluation done.

Image memory initialized(size = 0x2000000).

TBD.



9B--68

( )

Comparing the ’installed’

and the ’expected’ configu-

rations: PASSED!

uif tool -- local

uiSocket.c(1710): ATI client

socket installed.



uif tool -- external

uif -- local

uif -- external

Diagnostics LangVideo

= >Englis_N<



Attempted: 0x56121000

TBD.



9B--69

(CDiagsMachine_Test)--

Software Version:

4252--0720--16 021.01


9C Local/Remote Diagnostics Access9C--1 Introduction

Local and remote access to system diagnostics is controlled by sys-tem software. Local access to diagnostics (access by someone

standing in front of the system) is controlled by the Service Access

Diagnostics machine option (SAD). Remote access to system diag-

nostics(modem access by the Technical Support Group) is controlled

by Remote Diagnostics.



9C--1

9C--2 Service Access Diagnostics

The Service Access Diagnostics machine option was implementedwith 038.15 software to control field-access to system diagnostic

tests and utilities and other diagnostic information. The option is dis-

abled on all domestic (U.S.) systems shipped with 038.15 software

and above (restricting access to system diagnostic capabilities). It is

enabled on international systems (no change in diagnostic capabili-

ties from previous software versions).

The Service Access Diagnostics machine option was implemented by

domestic Customer Support to encourage CSRs and BMETs to pass

the “triage” of a problematic system to the Bothell-based Technical

Support Group (TSG) which will troubleshoot the system using re-

mote diagnostics. This troubleshooting approach provides a more

timely response for the customer, better support for CSRs, and gives ATL more control over machine maintenance and repair.

Disabling Service Access Diagnostics does not affect diagnostics

used by the CSR to setup the system or install an upgrade. It also

does not affect customer access to User Diagnostics. However, dis-

bli S i A Di ti th f ll i ti



9C--2

abling Service Access Diagnostics removes the following options

from system diagnostics:

D Tests, Utils., Error Log, and Fake Scanhead menu items from theCSR diagnostics. (The User Login, Configuration, and Options

menu items are available in CSR diagnostics for upgrades and

installation of machine options whether the Service Access Diag-

nostic machine option is disabled or enabled.)

D Access to VxWorks and system messages via the serial port after

bootup. Bootup messages will be available regardless of whether

Service Access Diagnostics is enabled or disabled.

D Second page of all system dialog alert and run-time alert mes-

sages.

Disabling the Service Access Diagnostics machine option also adds

temporary field access to Tests, Utils., Error Log, and Fake Scanhead

menu items. (Restores diagnostic capabilities of previous software

versions.)

Di bli h S i A Di i d ff



9C--3

Disabling the Service Access Diagnostics does not affect access to

user diagnostics via the SETUPS key on the keyboard.

Access to Service Access Diagnostics is by enabling the machine op-tion for permanent continuous access or by obtaining an ”Access

Key” for temporary access. Access by either means requires entry of

the correct username and password.

9C--2.1 Temporary Field Access to DiagnosticsTemporary field access to diagnostics and the serial port may be ne-

cessary to support clinical trial systems, systems at shows, or for oth-

er reasons. This is facilitated by the Diagnostics menu option on the

Service Access Diagnostics menu (accessed using Superkey-0).When selected, the Diagnostics menu option displays the Diagnostic

Feature Access menu which prompts for an “Access Key” to be en-

tered.

The Access Key is generated by the Technical Support Group. Oncethe key is entered from the keyboard the Service Access Diagnostics



9C--4

the key is entered from the keyboard, the Service Access Diagnostics

option is enabled for the given date. The default date is the current

date, however, the date can be changed. Keys are unique per ma-

chine and date, and may not be re-used.

Clinical trial and show systems, etc., may have the Service Access

Diagnostics machine option enabled by default to allow for extended

diagnostics access.

- To obtain temporary field access to diagnostics:

1. Depress and hold Superkey then press zero on the keyboard.

The Machine Diagnostics menu is displayed.

2. In the User field, type the appropriate information using the key-board. Press RETURN. The cursor moves to the Password

field.

3. In the password field, type the appropriate information using the

keyboard.



9C--5


Service Access Diagnostics Menu is displayed (Figure 9C--1).

5. Move the cursor to Diagnostics. Press SELECT. The Diagnostic

License Setup menu is displayed (Figure 9C--2).

C4--2 40R Abd/General123456789000000

General HospitalJ. Smith

4:35:26 pm02 Jul 97

16 Hz 13.8cmTls 0.2 MI 1.0

HDI

Cl

User Login

Configuration

Options

Diagnostics



9C--6

Close

Figure 9C--1. Service Access Diagnostics Menu

C4--2 40R Abd/General123456789000000General HospitalJ. Smith 4:35:26 pm02 Jul 97 16 Hz 13.8cmTls 0.2 MI 1.0

HDI

Close

User Login

Configuration

Options

Diagnostics

Diagnostics License Setup

07/02/97

I

Date of Access:(mm/dd/yy)

Access Key:



9C--7

Cancel OK

Figure 9C--2. Diagnostics License Setup Menu

6. Call the Technical Support Group to obtain the Access Key.

7. Move the cursor to the Access Key field. Press SELECT.

8. Type the 8-digit Access Key from the system keyboard, paying

attention to whether the characters are upper or lower case. (Al-pha characters in the Access Keys are case sensitive.)

9. Select OK. Press SELECT. The Diagnostic Tools Menu is dis-

played. The system is capable of all diagnostic functions at this

point. Refer to Section 9A for information.



9C--8

NOTE: Temporary access to diagnostics expires the first time power

is cycled after midnight of the day of issue. Once expired, a

new Access Key must be generated by the Technical Sup-port Group.

9C--3 Remote DiagnosticsRemote Diagnostics adds the ability to remotely execute diagnostic

tests(paragraph9C--3.1)andtheabilitytokeepthemodemcontinu-

ouslyconnectedwithoutreprogrammingthemodem(paragraph

9C--3.2). (The system serial port output is disabled at the beginningof system bootup if the system detects a modem.)

Before using Remote Diagnostics the modem operating parameters

must be set to the system communication settings. Refer to the mo-

dem initialization procedure (paragraph 9C--3.3).

9C 3 1 Remote Test Execution



9C--9

9C--3.1 Remote Test Execution

Software version 038.15 enables the system to execute tests and

other functions for Remote Diagnostics. The executable tests andfunctions include:

D 2D and Color End-to-End Tests

D PSP Primary and Secondary Buffer Tests

D Execution of any test (given Test Component and Name)

D Test looping/aborting

Also, the System Diagnostic Tools (SDT) support a batch mode

which automatically executes any test, Vx Works, or Unix command

and saves the results to a log file. This feature is used by the System

Diagnostics group to execute tests on lab systems and to partially au-

tomate testing of production machines.

Remote Test Execution is available only from Bothell Technical Sup-

port Group to remote systems. However, it may be necessary for

CSRs to connect systems f or remote access. Refer to the procedure

below and Figure 9C--3 for information.

- To connect a system for remote test execution by the Technical Sup-



9C--10

- y y p

port Group:

1. Move the system to an analog phone line.

2. Turn on power to the system.

3. Connect the modem to the system and to the phone line as

shown in Figure 9C--3.

4. Turn on power to the modem.

5. Call TSG and provide them with the phone number of the direct

line to the system. TSG will dial the system and remotely inter-

rogate it as necessary.

6. When remote testing is complete, disconnect the system from

the modem and the phone line.



9C--11

Modem

Modem

Modem

Archive

Server(Sun)

SunSystem

SunSystem

UNIXNetwork

115VPower

Ph j k

HDI 3000

CPU PCB

Serial

port(9 pinDSUB)

25 pin to 9 pin adapter

RS232 cable(25 pin to 25 pin DSUB)



9C--12

Modem

PCNetworkPC 2

PC 2

Phone jackto analogphone line

1. Sun computer systems and UNIX network are located in ATL Product Generation Dept.

2. PC’s and PC network are located in ATL Technical Support.

Located at remote site.

Figure 9C--3. System Interconnect Diagram for Remote Diagnostics

9C--3.2 Continuous Modem Connection to theSerial Port

For systems with software version 036.06 and below, the modem

must be turned off when it is not being used to protect it from being

reprogrammed by the serial port output.For systems with software version 038.15 and above, the system

software checks for presence of the modem. If a modem is attached

and is not on-line, the serial port output is disabled and the modem is

reset. This sequence of events happens twice during bootup and en-ables the modem to remain attached to the system without being in-

advertently reprogrammed



9C--13

advertently reprogrammed.

9C--3.3 Modem Initialization

Before using the modem for Remote Diagnostics, the modem must

be initialized. Initialization is required to set modem operating param-

eters to values that the system will accept. These parameters include

baud rate, parity, start bits, and etc. The initialization process must be

done only once. After the initialization process is completed the mo-

dem can be used for Remote Diagnostics on any HDI 3000 system.

- To initialize the modem:

1. Connect the modem to the serial port on the rear of the system.

2. Press SETUPS on the system keyboard.

3. Select Diagnostics from the lower left corner of the display.

Press SELECT. The user diagnostics menu is displayed.

4. Select Initialize Modem from the lower left corner of the display.

Press SELECT. The system then sends a string of commandsthrough the serial port to the modem. The modem is then pro-

d t th t i ti t



9C--14

grammed to the correct communications parameters.

5. Disconnect the modem from the system.

6. Reboot the system.

Index

Numbers2D Tests, 9A--6

AA to atic Fi a e Flashi g 9A 51



Index--1

Automatic Firmware Flashing, 9A--51

BBack--End Test, 2D, 9A--2 , 9A--7

Back--End Test, Color, 9A--2 , 9A--9

Bootup Looping Mode Display, 9A--45

Index

Bootup Status

Show Report, 9A--50

Show Report Display, 9A--52Bottom, Error Log, 9A--76

CChan Walk Test, Receiver and Transmitter Status, 9A--14

Channel Board Fault Isolation, 9A--2



Index--2

,

Channel Walk Test, 9A--2

Receive Walk 1 Board Display, 9A--27

Channel Walk Utility, 9A--14

Help Screen, 9A--22

Parameter Settings, 9A--26

Receive Commands, 9A--23Selection Screen (30.05 and Above), 9A--21

Setup, 9A--23

Test Screen, 9A--20

Transmit Commands, 9A--24Clear Log, 9A--74

Color Tests, 9A--9

Comprehensive Test, 9A--2 , 9A--12

Sub-Test Menu Path, 9A--104Sub-Tests, 9A--98



Index--3

Configuration

Expected PCB Part Number, 9A--81

Installed PCB Part Number, 9A--81

Machine Config. Display, 9A--84 , 9A--85

Save Installed as Expected, 9A--81

Continuous Modem Connection to Serial Port, 9C--13

Index

CSR Diagnostics, 9A--31

Accessing Diagnostic Tools Menu, 9A--31

Close, 9A--31 , 9A--94Configuration, 9A--31 , 9A--81

Error Log, 9A--31

Fake Scanhead, 9A--31 , 9A--89

Options, 9A--31 , 9A--86Tests, Utils., 9A--31 , 9A--32



Index--4

User Login, 9A--31 , 9A--32

DDiagnostic Tables, 9B--1

Diagnostics

Accessing Individual Tests, 9A--95Bootup Tests Indicate Failure, 9B--7

Core Bootup -- SYSCPU Console Output Fault Symptoms, 9B--60

Introduction, 9A--1 , 9C--1 , 9C--4

Machine Comprehensive Test Fails, 9B--49Machine Functional Test Fails, 9B--45

Operational Fault is Indicated, 9B--45

Run-time Alert Appears, 9B--13

Top Level Fault Indications, 9B--2User Interface Fails to Boot, 9B--3



Index--5

Disable Flash Mismatch Notification, 9A--51

Disable Next Boot Flash Mismatch Notification, 9A--51

Display Feature List, System Feature History, 9A--36

Download Error Log to Optical Disk, 9A--106 , 9A--109

Download System to Optical Disk, 9A--106 , 9A--110

Index

EECG Gain Tests, 9A--28

Enable Flash Mismatch Notification, 9A--51Enable/Disable Looping of Booting, 9A--43

End--To--End Test, 2D, 9A--2 , 9A--7

End--To--End Test, Color, 9A--2 , 9A--9

Error Code Interpretation, 9A--3

Error Description Box, 033.27 and Below, 9A--62



Index--6

p , ,

Error Id’s, 9A--70

Error Information Box, 033.27 and Below, 9A--61Error Log, 9A--5 , 9A--6 , 9A--53

033.27 and Below

Error Description Box, 9A--62

Error Informaiton Box, 9A--61

Errors Box, 9A--59

Properties, 9A--63

034.17 and Above, 9A--66Bottom, 9A--76

Clear Log, 9A--74

Error Id’s, 9A--70

Error Window, 9A--68Group by Fault, 9A--69



Index--7

Log Button, 9A--76

Menu Bar, 9A--69

Print, 9A--74

Search List, 9A--70

Stack Trace, 9A--72

Summary, 9A--77Sys Data, 9A--72

Index

Top, 9A--76

User Events, 9A--70

Close, 9A--79Display, 9A--53

033.27 and Below, 9A--54

034.17 Software and Above, 9A--66

Display Figure, 034.17 Software and Above, 9A--67Hide, 9A--79

P i i O i Fi 9A



Index--8

Printing Options Figure, 9A--75

Properties Display, 9A--60

Search List Criteria Figure, 9A--71

Summary Figure, 9A--78

System Data Used at Power Down Figure, 9A--73

Error Log Menu Bar, 034.17 and Above, 9A--69

Error Log Procedures, 9A--79

033.27 and Below, 9A--55

Character String Search, 9A--57Displaying 25 Previous User Events, 9A--58

Error Selection, 9A--56

Scroll Bar Use, 9A--56

Specific Error Number Search, 9A--57Character String Search, 9A--55 , 9A--80

Di l i 25 P i U E t 9A 55



Index--9

Displaying 25 Previous User Events, 9A--55

Error Selection, 9A--55 , 9A--79

Scroll Bar Use, 9A--55 , 9A--80

Specific Error Number Search, 9A--55

Error Log Properties, 033.27 and Below, 9A--63

Error Log Reference Information, 033.27 and Below, 9A--59Error Window, 034.17 and Above, 9A--68

Index

FFake Scanhead, 9A--89

Selection Display, 9A--92Tissue Specific Setups Display, 9A--93

Fault Isolation

Channel Board, 9A--12

General, 9A--2

File Management Utilities, 9A--106



Index--10

GGroup by Fault, 9A--69

L

Log Button, Error Log, 9A--76

MMachine Options Software Backup on Hard Drive, 9A--106 , 9A--111

Machine Options Software Restore on Hard Drive, 9A--106 , 9A--112Modem Initialization, 9C--13

Module Flash Loading

Always Done, 9A--46

Disabled, 9A--46

On Next Boot, 9A--46



Index--11

OOptions

Authorized, 9A--86

Display, 9A--88

MO Files During Upgrade, 9A--87

Index

Unauthorized, 9A--86

PPCB

Bootup Error Status, 9A--49

Bootup Status, 9A--50

Replacement, 9A--46PCB LED, Card Cage Locations, Front, 9C--6 , 9C--7 , 9C--12

Print Error Log 9A 74



Index--12

Print, Error Log, 9A--74

RRemote Diagnostics, 9C--9

Continuous Modem Connection to Serial Port, 9C--13

Modem Initialization, 9C--13Remote Test Execution, 9C--9

Remote Test Execution, 9C--9

SSearch List, 9A--70

Service Access Diagnostics, Automatic Firmware Flashing, 9A--51

Stack Trace, 9A--72

Summary, 9A--77Sys Data, 9A--72

System Backup on Hard Drive 9A 106 9A 113



Index--13

System Backup on Hard Drive, 9A--106 , 9A--113

System Restore on Hard Drive, 9A--106 , 9A--114

System Upgrade, 9A--46

From Optical Disk, 9A--115

Index

TTests, Utils. Menu, 9A--32

Comprehensive Test, 9A--33 , 9A--35Display Feature List, 9A--33 , 9A--35

Enable/Disable Looping of Booting, 9A--33 , 9A--43

Module Flash Loading Always Done, 9A--33 , 9A--46

Module Flash Loading Disabled, 9A--33 , 9A--46

Module Flash Loading On Next Boot, 9A--33 , 9A--46

PCB’ B t E St t 9A 33 9A 34 9A 49



Index--14

PCB’s Bootup Error Status, 9A--33 , 9 A--34 , 9A--49

PCB’s Bootup Status, 9A--33 , 9A--34 , 9A--50Show Bootup Status Report, 9A--33 , 9A--34 , 9A--50

Top, Error Log, 9A--76

UUser Events, 9A--70

V Verify System Files, 9A--106 , 9A--114



Index--15

atl hdi 3000 service manual rev b

Documents