Axa4-100 840 02 04 02

ra
Z
s
n
m
ie
S
AXIOM Artis
AX
Troubleshooting Guide
Image System
Troubleshooting Guide for the Image System
05998468
05998450
05998427
05998419
05225235
05225227
© Siemens 2006
The reproduction, transmission or use
of this document or its contents is not
permitted without express written
authority. Offenders will be liable for
damages. All rights, including rights
created by patent grant or registration
of a utility model or design, are
reserved.
Print No.: AXA4-100.840.02.04.02 English

Replaces: AXA4-100.840.02.03.02 Doc. Gen. Date: 07.07
2 Revision / Disclaimer
1Revision / Disclaimer
Document revision level

The document corresponds to the version/revision level effective at the time of system
delivery. Revisions to hardcopy documentation are not automatically distributed.
Please contact your local Siemens office to order current revision levels.
Disclaimer
The installation and service of equipment described herein is to be performed by qualified
personnel who are employed by Siemens or one of its affiliates or who are otherwise autho-
rized by Siemens or one of its affiliates to provide such services.
Assemblers and other persons who are not employed by or otherwise directly affiliated with
or authorized by Siemens or one of its affiliates are directed to contact one of the local
offices of Siemens or one of its affiliates before attempting installation or service proce-
dures.
AXIOM Artis AXA4-100.840.02.04.02 Page 2 of 178 Siemens

07.07 CS PS AX IR/C
Table of Contents 3
0Table of Contents
1 _______ General Information______________________________________________ 7
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Required Aids and Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
General Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Product-specific Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Product-specific Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Conventions and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2 _______ Introduction ___________________________________________________ 11
Image System Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Block Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
IMPAC Board Overview (QDP Version) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
IMPAC Board Overview (AAQ COPRA Version) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3 _______ Decision Finding _______________________________________________ 16
Problems during SW Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Boot Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Function Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Image Problems, Corrupted Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4 _______ Boot Problems _________________________________________________ 26
General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
POI/PCM Board Power-up Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Power-up Sequence with POI Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Power-up Sequence with PCM Board (Type II Power Supply) . . . . . . . . . . . . . . . . . 29
Black Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
“Black Screen” General Troubleshooting Sequence . . . . . . . . . . . . . . . . . . . . . . . . 33
Startup Diagnostics Fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Symptoms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
How to solve the problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Windows OS does not start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Windows NT-based Systems (SW VA42/60). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Windows XP-based Systems (VB..) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Blue Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
“Blue Screen” Troubleshooting Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Syngo, Artis Application does not start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
BSR RT PC does not boot, IMPAC HW cannot be initialized. . . . . . . . . . . . . . . . . . . . . 42
BSR RT PC Bootup Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Cyclical Reboot of the BSR RT PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
BSR RT PC Boots into a Fatal Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
BSR RT PC displays error messages at a high repetition rate . . . . . . . . . . . . . . . . 43
Stand-along BSR RT PC bootup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Siemens AXA4-100.840.02.04.02 Page 3 of 178 AXIOM Artis

07.07 CS PS AX IR/C
4 Table of Contents
5 _______ Diagnostics____________________________________________________ 45
General Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
POST Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
General Information about the POST Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
POST Card User Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Successful Power-on Self-test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
POST Card Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
POST Code Table for Host 2 Module, BSR RT PC Module (Motorola PATX5000,
PATX3070 Mb) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Post Code Table Host 3 Module (Intel SE7210TP1-E TPS Mb) . . . . . . . . . . . . . . . . 53
Post Code Table BSR RT PC 2 Module (Raptor ATX Mb). . . . . . . . . . . . . . . . . . . . . 56
Known Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Startup Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
HW Check during Startup Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Startup Diagnostic Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Disabling the Startup Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Factory Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Prerequisites to Run the Factory Diagnostic Tests . . . . . . . . . . . . . . . . . . . . . . . . . . 67
How to Start the Factory Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Starting the Factory Diagnostics Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
How to Start the Diagnostic Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Which test should be executed when? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Display of the Diagnostic Test Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Extended Factory Diagnostic Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Factory Diagnostic Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
How to Close the Factory Diagnostic Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Known Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Formatting the Image Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Hardware Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Prerequisites for running the Hardware Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
How to Start the Hardware Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Which tests should be executed and when . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Display of the Hardware Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Extended Hardware Test Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
How to close the Hardware Test menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
BSR RT PC Developer Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Checking the Bootup Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Extended Developer Mode Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
How to close the Developer Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Network Adapter Diagnostics (Host 2 Module only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
How to start the Network Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Running the Network Adapter Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
6 _______ BIOS Functions ________________________________________________ 97
General Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Host BIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Entering the Host BIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
BIOS Functions with Host 2 Module (Motorola PATX5000 MB) . . . . . . . . . . . . . . . . 98

07.07 CS PS AX IR/C
Table of Contents 5
BIOS Functions with Host 3 Module (Intel SE7210TP1-E MB). . . . . . . . . . . . . . . . 101

Selecting the Boot Device without Entering the BIOS . . . . . . . . . . . . . . . . . . . . . . 102
Common Host BIOS Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Clearing the CMOS (BIOS Password) on the Host Motherboard . . . . . . . . . . . . . 103
Adaptec BIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Entering the Adaptec BIOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Formatting the System Drive in the Host 2 Module . . . . . . . . . . . . . . . . . . . . . . . . 106
Verification of the Host 2 Module System Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Symbios BIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Entering the Symbios BIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Formatting the Image Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Verification of an Image Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
How to identify the image drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
BIOS of the BSR RT PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Entering the BSR RT PC BIOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Clearing the CMOS on the BSR RT PC Motherboard . . . . . . . . . . . . . . . . . . . . . . 111
7 _______ Voltages and LEDs_____________________________________________ 114
Voltage Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

LED Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
POI Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
PCM Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Host 2 Module Motherboard (Motorola PATX 5000) . . . . . . . . . . . . . . . . . . . . . . . . 118
QDP Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
AAQ COPRA Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
DAM Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
1KD Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
SHA Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
IPM Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
IPS Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
VSD Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
TPS Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
CD-ROM (ULTRAPLEX 40max) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
CD-R (Plextor PX-W4012TS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
IDE DVD/CD-R (Plextor PX716 / PX760) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
SBE Board (in Host PC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
SBE Board (in RPAU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
LEX Module (in BSR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
REX Module (in RPAU2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
8 _______ Downgrade to the Minimum HW__________________________________ 128
Minimizing Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Stand-alone Host PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Stand-alone BSR RT PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Minimizing the IMPAC HW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
9 _______ Databases____________________________________________________ 134
Function Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

07.07 CS PS AX IR/C
6 Table of Contents
Host Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

BSR RT PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Disk Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
How the patient images are stored: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Clearing the Exchange Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Checking the Free Space in the "Exchange Board" Database . . . . . . . . . . . . . . . . 137
Clearing the Exchange Board:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Deleting the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Deleting the database in SW versions VA42/60 . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Deleting the database in SW versions VB11, VB22/23, VB30/31 . . . . . . . . . . . . . . 140
Manual Deletion of the ifs.dat File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Known Database Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
10 ______ Procedures ___________________________________________________ 145
Explanation regarding the Procedures Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Using the COM 2 port of the BSR RT PC for service . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Connection of the Service PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Enabling the Developer Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Starting the Terminal Emulation Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Terminal Emulation Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
BIOS Initialisierung . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Resetting the BIOS when Changing the Image Drive Configuration . . . . . . . . . . . . 151
Resetting the Host 2 Module Motherboard BIOS when Changing the Board Configura-
tion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Resetting the Symbios BIOS when Changing the Image Drive Configuration . . . . 155
Stopping/Starting the Application SW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Stop Application SW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Start Application SW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Network, Display Driver Initialization in SW Version VA42/60 . . . . . . . . . . . . . . . . . . . . 159
Resetting “Display Properties” when Installing Additional 1KD Boards (valid for SW
VA42/60 only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Restoring Intel Network Drivers (valid for SW VA42/60 only) . . . . . . . . . . . . . . . . . 160
Device Driver Installation with VB11 SW Versions < VB11M . . . . . . . . . . . . . . . . . . . . 161
General Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Display Driver Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Disabling the SCSI Controller Driver for the Disk Array. . . . . . . . . . . . . . . . . . . . . . 166
Driver Installation for Other Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Installation of the PoiWdm Device Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Device driver installation with SW ≥VB11M, VB22/23, VB30/31. . . . . . . . . . . . . . . . . . 173
General Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
VB11M, VB22/23, VB30/31 Driver Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
11 ______ Changes to Previous Version ____________________________________ 176
12 ______ Index ________________________________________________________ 177

07.07 CS PS AX IR/C
General Information 7
1-
Requirements
1General Information
Required Aids and Tools 0
All tools, test equipment and aids, with the exception of the “standard service tool kit”, are
listed and specified in the Service Tools Catalogue.
• Standard service tool kit

• POST Card (shipped with each system)
• Service PC with a Terminal Emulation Program see note below
• Serial Cable (0 Modem) P/N 99 00 440
Terminal Emulation Program

Hyper Term, which is part of Windows 98, NT, XP, can be used as the terminal program.
Unfortunately the suitability of the Hyper Terminal is very limited. Therefore it is recom-
mended to use the TeraTerm terminal emulation program, which can be dowloaded from
the CS home page in the Intranet. Refer to <Product Information> <AX Systems> <Angiog-
raphie> <AXIOM Artis Family> <Software> <Tools>.

07.07 CS PS AX IR/C
8 General Information
Remarks 1.1
General Safety Information 0
When carrying out the work steps and checks, the general safety information for medical
products must be observed.
Product-specific Safety Information 0
RTC, Image System
WARNING [hm_serv_NoteProtectEyes]
Laser Class 3B units having a maximum output of 500 mW.

This kind of laser is used for the image transfer
a) from the FD to the RTC
b) from the RTC to the Image System.
The laser beam is invisible, dangerous to the human eye, and
in some cases, to the skin.
¹ Proper use must be observed.
¹ Required safety equipment must be used.
Control Cabinets
WARNING [hm_serv_LabelPowerPresent]
Even after shutting down (Shutdown) the system, there is
still voltage present in the system control cabinet and in the
generator.
If this is not observed, death or serious bodily injury can
occur.
¹ The warning labels in the cabinets must be observed.
¹ Switch power off to the radiographic system at the
on-site on/off switch.

07.07 CS PS AX IR/C
Image System with UPS
WARNING [hm_serv_WarnSetUPSPowerMayBePresent]
If a UPS option is configured for the image system, it is pos-

sible that the UPS is still supplying the image system with
voltage when the line power is switched off.
If not observed, death or serious bodily injury can occur.
¹ If the UPS is configured, unplug the power input con-
nector in the image system or switch off the UPS prior
to beginning service work.
AXIOM Miyabi
For specific Safety Information on AXIOM Miyabi systems, see AXA4-000.860.01
(AXA4-000.860.01 / AXIOM Miyabi)
Product-specific Remarks 0
Location of the Assemblies
3 7
2 5 1
Fig. 1: Image system module overview

Pos. 1 Host PC module
Pos. 2 Realtime PC module
Pos. 3 IMPAC module
Pos. 4 Disk array
Pos. 5 Power supply
Pos. 6 CD-ROM, CD-R, floppy drives
Pos. 7 POI board

07.07 CS PS AX IR/C
10 General Information
Conventions and Abbreviations 0
Abbreviations
BSR = Abbreviation for Image System (in German)

BSR RT PC = Image System Real-time PC Module
IMPAC = Image Processing And Control
IPM = IMPAC Master
IPS = IMPAC Slave (Biplane only)
POI = Power O/I
PCM = Power Control Module
VSD = Video Signal Distribution
TPS = Temperatur Sensor
DAM = Data Acquisition Module
QDP = Quad Digital Signal Processor
COPRA = Common Processing Architecture
AAQ = Artis AcQuisition daughter board
AAQ/COPRA = COPRA board with piggyback AAQ board
1KD = 1K Display (1024 Matrix)
DMA = Direct Memory Access
SHA = SCSI Host Adapter
COM = Communication (PCI)
RPAU = Remote Power Archive Unit (uses SCSI extender boards and
fiber optic cables)
RPA = Remote Power Archive Board
SBE = SCSI Bus Extender Board (for RPAU)
RPAU2 = Remote Power Archive 2 Unit (uses IDE to USB converters)
LEX = USB Local Extender for RPAU2 (located in the BSR)
REX = USB Remote Extender for RPAU2 (located in RPAU)

07.07 CS PS AX IR/C
Introduction 11
2-
Image System Overview
2Introduction
The complete unit is an image system and control processor for an Angiographic suite. It
contains the Host PC, the Realtime PC and an IMPAC module.
The host PC, which controls the system, is either a Motorola dual Pentium board or an Intel
Server board with 2048 MB RAM.
It runs Windows NT (XP) and contains the SYNGO SW as well as the application SW. Its
PCI bus connects to a COM board, which is used to extend the PCI bus to the IMPAC mas-
ter board.
The IMPAC Master is a multi-slot PCI expansion card which permits many more expansion
cards to be installed in the PCI bus than would be possible on a commercially available PC
motherboard. It also includes memory used for image processing functions of the system.
In a biplane system, an additional IMPAC module is installed, namely the IMPAC slave
(IPS), which is similar to the IMPAC master (IPM). It expands the PCI bus for more boards
and provides separate memory space for the second plane image processing.
There is a second PC in the image system, which is used for real-time processing. This
Real-time PC (BSR RT PC) runs the VRTX operating system and handles those events
which must be processed in real time.
Image processing is performed using digital signal processor (DSP) techniques for flexibil-
ity in processing. The DSP devices are on the digital acquisition module (DAM) and on the
Quad DSP (QDP) boards. In newer systems (beginning with version VB22), the 3 QDP
boards and the DAM board are replaced by one AAQ-COPRA board.
The processed images are sent to the 1k display (1KD) boards for display on the monitors.
The video signals are buffered to drive the monitor cables by the video signal distributor
(VSD) board.
The power on/off board (POI/PCM) board provides the image system with a way to turn
on/off the distributor power and the image system power.

07.07 CS PS AX IR/C
12 Introduction
Block Diagrams 0
Fig. 2: Block diagram, single plane image system (QDP / DAM version)
Fig. 3: Block diagram, single plane image system (AAQ / COPRA version)

07.07 CS PS AX IR/C
Introduction 13
IMPAC Board Overview (QDP Version) 0
Fig. 4: Biplane Board Overview
Board Single Plane Systems, Biplane Systems, IMPAC Board Board No.
Slot IMPAC Master (IPM Slave (IPS) ID in Fig. 2
1 DAM DAM 15 1
2 ------------------------------- -------------------------------- -----------
3 1KD 1KD 2/0 2
4 ------------------------------- -------------------------------- -----------
5 1KD (optional) 1KD (optional) 4/6
6 1KD (optional) 1KD (optional) 8
7 ------------------------------- -------------------------------- -----------
8 QDP (Format) QDP (Format) 14 3
9 ------------------------------- ------------------------------- -----------
10 QDP (Primary) QDP (Primary) 13 3
11 ------------------------------- -------------------------------- -----------
12 QDP (Secondary) option QDP (Secondary) option 12
13 ------------------------------- -------------------------------- -----------
14 SHA (SCSI Host Adapt.) -------------------------------- 16 / 17 4
15 DMA -------------------------------- 18 5

07.07 CS PS AX IR/C
14 Introduction
IMPAC Board Overview (AAQ COPRA Version) 0
Fig. 5: Overview of IMPAC Boards (COPRA Version)

Pos. 1 1KD Board
Pos. 2 COPRA/AAQ Board
Pos. 3 SHA Board
Pos. 4 DMA Board
Slot IMPAC Master (IPM) Slave (IPS) ID in Fig. 3
1 ------------------------------- -------------------------------- -----------
2 ------------------------------- -------------------------------- -----------
3 1KD 1KD 2/0 1
4 ------------------------------- -------------------------------- -----------
5 1KD (optional) 1KD (optional) 4/6 1
6 1KD (optional) 1KD (optional) 8
7 ------------------------------- -------------------------------- -----------
8 AAQ COPRA AAQ COPRA 10 2
9 ------------------------------- -------------------------------- -----------
10 ------------------------------- --------------------------------
11 ------------------------------- -------------------------------- -----------
12 ------------------------------- --------------------------------

07.07 CS PS AX IR/C
Introduction 15
Slot IMPAC Master (IPM) Slave (IPS) ID in Fig. 3
13 ------------------------------- -------------------------------- -----------
14 SHA (SCSI Host Adapt.) -------------------------------- 16 / 17 3
15 DMA1 -------------------------------- 18 4

07.07 CS PS AX IR/C
16 Decision Finding
3-
Problems during SW Installation
3Decision Finding
Problem Links and Solutions

The SW installation from CD does not This is probably caused by an incorrect setting (Scan ID is
work. Partitioning of the hard drive fails. active) in the Symbios BIOS. Perform the following steps to
check, solve the problem:
• Reboot the system and activate the Symbios BIOS, see
(Symbios BIOS / p. 108).
• Set the Scan ID back to [NO], see (Set the scan ID back
to [ NO] in the Symbios Bios. / p. 153).
The system initialization (HW check) Check whether the SHA board (Symbios SCSI controller) is
that runs during the SW installation correctly plugged in. Try to install the software with the SHA
fails, or does not finish. board removed from the IMPAC.
The file copy from CD (DVD) fails. A The installation medium (CD, DVD) is corrupt. Try another
message about missing files is dis- SW CD / DVD.
played.
The installation of the clone image This is probably caused by a HW problem in the IMPAC sec-
(VB23, VB30/31) fails. The systems tion. Disconnect the COM board from the Host PC, see
resets and offers to boot in the save (Stand-alone Host PC / p. 128). Install the clone DVD on the
mode, which will fail. Host without the IMPAC connected. Connect the COM board
again when the installation is finished and run diagnostics to
identify the HW problem.

07.07 CS PS AX IR/C
Decision Finding 17
Boot Problems 3.1

System does not switch on when the • Check whether the main room power is switched ON.
ON button is pressed on the image sys- • The LED marked “ON_PRESSED” on the MD.D90 must
tem front panel. be active when pressing the Power ON push-button; if
not, check the cable connection from POI (PCM) connec-
tor X70 to MD connector X2.
• Make sure that Power ON is not blocked by the switch
marked “OFF_SWITCH“ on the MD.D90.
If a RPAU Option is Configured:
• Check whether the RPA board (behind the push-buttons)
is moved back.
• Check the 15-pin cable between RPAU and POI/PCM for
good contact.
Remedy: Try to power ON the system using the push-button
marked “ON_SWITCH” on the MD.D90 board.
The system can be switched ON, but If a POI board is present (S/N < 1491SP, < 3099 BP), see
the image system receives no power (Power-up Sequence with POI Board / p. 27).
from the power distributor (MD). If a PCM board is present (S/N >1490SP, > 3098 BP), see
(Power-up Sequence with PCM Board (Type II Power
Supply) / p. 29).
Image system cannot be switched ON. See (POI/PCM Board Power-up Sequence / p. 27), and
(Known Problems / p. 31)
Power up sequence out of sync. --> The This usually happens in systems with Type II power supplies.
lab can be switched ON, the image sys- See (Known Problems / p. 31).
tem gets power from the power distribu-
tor, but the image system does not boot
up.
Image system components do not See (POI/PCM Board Power-up Sequence / p. 27), and
power up (Known Problems / p. 31)
Host does not boot, control room moni- See (“Black Screen” General Troubleshooting
tor shows a “black screen”. Sequence / p. 33).
SIEMENS logo screen is displayed, BIOS should be reset to default with <F9>, see (Setup of
boot does not go any further. This may Default BIOS / p. 103)
happen if the HW configuration has
been changed (e.g. after a downgrade
to the minimum HW configuration).
Startup Diagnostics fails See (Startup Diagnostics Fail / p. 36)
Windows does not start. See (Windows OS does not start / p. 37).
System crashes with a “blue screen”. See (“Blue Screen” Troubleshooting Sequence / p. 39).

07.07 CS PS AX IR/C
18 Decision Finding

Syngo, Artis Application does not start. See (Syngo, Artis Application does not start / p. 40).
BSR RT PC does not boot or connect to See (BSR RT PC does not boot, IMPAC HW cannot be
application. initialized. / p. 42).
BSR RT PC performs a cyclical reboot. See (Cyclical Reboot of the BSR RT PC / p. 43).
BSR RT PC boots to a fatal error. See (BSR RT PC Boots into a Fatal Error / p. 43).

07.07 CS PS AX IR/C
Decision Finding 19
Function Problems 3.2

System message “Image System • Check the temperature LEDs on the POI, PCM and TPS
temperature high” boards, see (LED Description / p. 115).
• Check the air inlet and outlet.
Check the air filters located in the front cover.
• Open the image system and check all fans.
• Make sure the room temperature is inside the allowed
range of 10 ... 35 degrees centigrade.
Note: There are three temperature sensors:
• On the TPS board, set to 37 degrees Centigrade
• On the POI board, set to 40 degrees Centigrade
• On the IPM board, set to 40 degrees Centigrade
All three sensors are OR-connected; the temperature informa-
tion is displayed in the system message line.
Hang-up during fluoro or acquisition. • Open the event log and search for the component that
caused the problem. If the problem was caused by the
image system, the following message should be present:
W AX_SYC 2 Component down Text: SYC SET: [00002]CEr-
hRegComp::registerReady BSR not ready
• Check whether the event log contains AX_IMP errors next
to this entry and follow the info in the action field of the
AX_IMP error.
• Perform Hardware Tests (Factory Diagnostics / p. 67)
Sporadic hang-ups during the post- • Check the event log for AX_IMP errors and follow the info
processing operation in the action box.
• Perform Hardware Tests (Factory Diagnostics / p. 67)
Archiving to or reading from CD-R, • Open the Windows Explorer and check whether drive “S:\”
CD-ROM not possible in VA42/60 (CD-R) or R:\ (CD-ROM is present. If not, check configura-
systems tion item “Archive Devices”.
• Check the SCSI cable connection between CD-R drive and
Host PC motherboard
• Check the power connection and the voltage
• Check the patching for the SCSI termination on the
CD-ROM drive, see (AXA4-100.841.02 / CD Drives, Floppy
Drive).
• Test with different CDs (not all CDs are good)
• SBE board problem (with RPAU only)
• Replace the CDR

07.07 CS PS AX IR/C
20 Decision Finding

Archiving to or reading from CD-R, • Open the Windows Explorer and check whether the correct
CD-ROM not possible in VB.. sys- drive letters R:\ and S:\ are assigned to the particular drive.
tems If not, see (AXA4-100.841.13 / Configuration with SW Ver-
sions VB11, VB22/23, VB30/31 (Windows XP))
• Check the configuration under <Offline Devices>, see
(AXA4-100.841.13 / Configuration with SW Versions VB11,
VB22/23, VB30/31 (Windows XP))
• If read/write from/to the CD drive is still not possible even if
the drive letters and Offline Device configuration are o.k.,
perform the following steps:
- Open <Local Service> <Configuration>.
- Remove the checkmark in front of “DICOM Offline
Devices” and click on <Next>
- Run <Config Check>, <Auto Conf> and reboot the sys-
tem using the <Home> button.
- When the system is up, open <Configuration>, set the
checkmark in front of “DICOM Offline Devices”, continue
with <Next>.
- Configure offline devices, see (AXA4-100.841.13 / Con-
figuration with SW Versions VB11, VB22/23, VB30/31
(Windows XP))
- Run <Config Check>, <Auto Conf> and reboot the sys-
tem using the <Home> button.
- Open <Utilities> and perform <Tune CD Burning>.
Archive device (CD-R) not present • Check the cable connections and LEDs on the USB
and drive not visible in Windows extender modules, see (LEX Module (in BSR) / p. 126)
Explorer in systems with RPAU2 • Reset the Host Motherboard BIOS with the <F9> key back
to default, see (Setup of Default BIOS / p. 103).

07.07 CS PS AX IR/C
Decision Finding 21
Image Problems, Corrupted Images 3.3
Image corruption can be caused either by malfunctions on the image system HW or by the
DIPP (digital pre-processing) in the RTC. As the signal processing is quite similar (4 DSPs
are used on the VIPER, COPRA board as well as on the QDP), it is sometimes difficult to
decide whether the image problem is caused by the pre-processing or the image system.
Perform the following steps to locate the problem:
• Generate the service images by activating <Options> <Load Test Image>.
• Select the service patient generated and check the images for problems.
- Case 1: Images are corrupted or show disturbances.
¹ The problem was possibly caused inside the image system. See table below for
more information.
- Case 2: Images are o.k.
¹ The problem was caused either by the DAM, AAQ/COPRA board or by the digital
pre-processing in the RTC.

Corrupted images during fluoro or Problem is caused either by the digital pre-processing or the
acquisition. Internally generated test the DAM board (old HW) or COPRA/AAQ (new HW). Please
images are o.k. Images imported from perform the following steps:
CD or Network are o.k. • Check the event log for AX_IMP errors
• Perform Hardware Tests of DAM board (newer BSR HW
AAQ/COPRA board), see (Factory Diagnostics / p. 67)
• Replace the DAM or AAQ/COPRA board
Corrupted images during playback. • Perform hardware tests of IMPAC, DMA, 1KD, DAM and
Internally generated test images and QDP modules (on newer BSR HW AQ/COPRA), see (Fac-
images imported from CD or Network tory Diagnostics / p. 67) and replace the defective part.
are also affected.
Blank images during fluoro or acquisi- • Check the LEDs on DAM board, see (DAM Board / p. 120).
tion • Perform diagnostic tests of the digital acquisition module
(DAM board) or COPRA/AAQ, see (Factory
Diagnostics / p. 67).
• Perform the video signal test (go to Local Service, Control,
Service Switches and select Test Image DIPP) to see
whether the problem is caused in the image system or by
the DIPP.
• Replace the DAM or COPRA/AAQ board

07.07 CS PS AX IR/C
22 Decision Finding

No image or wrong image on some • Swap the video cables on the VSD board, e.g. Live1 Exam.
monitors (e.g. control room Live room with Live1 Contr. room to find out whether the con-
image is displayed on Ref. monitor, nection to the monitor is good.
etc.) • Use the Lemo BNC video cable provided in the service kit
located at the right side cover to connect the monitor
directly to the 1KD board. If an image appears, check,
replace the VSD board.
• Perform the 1KD diagnostic test, see (Factory
With SW VB11/22/23, VB30/31:
• The monitor designation may be corrupted. This could
happen after certain HW is replaced. Use the following
steps to correct this:
- Stop the application SW, see (Stop Application
SW / p. 158)
- Run the enumdisp.exe utility, see (Automatic Display
Settings using the EnumDisp Utility / p. 164)

07.07 CS PS AX IR/C
Decision Finding 23

Application menu and Windows dia- Depending on the HW, the error may be caused for different
logs are covered by thin black vertical reasons.
stripes. Stripes may go away if a • BSR with POI board and old “Power One “ power supply:
“warm boot” (Restart System) is car-
ried out. Stripes may come back after ¹ Defective SD RAM on IPM or IPM board itself
the power is recycled (shutdown • BSR with ATX (Type II) power supply and PCM board
power off/on)
¹ Defective PCM board or PCM board with revision
level < 05
• BSR with Host 3 module
¹ Reset the Host motherboard BIOS to default, see
(Setup of Default BIOS / p. 103)
¹ Incorrectly connected cables on the terminal strip of
the Host 3 motherboard, see (1/Fig. 6 / p. 23)
Fig. 6: Host / Realtime PC terminal strip

07.07 CS PS AX IR/C
24 Decision Finding

One eighth of the image is missing in • One of the 8 image drives is defective or has been refor-
the horizontal direction on each matted. The concerned drive can be recognized by the
image acquired in the 1024 Matrix. position of the horizontal stripe within the image. The chan-
nel number and the SCSI ID can be found in the drawing.
CHA ID0 For the location of the drive in the disk array, see (How to
CHB ID0 identify the image drives / p. 110).
CHA ID1 NOTE: When the scene is acquired in the 512 Matrix, every
CHB ID1 eighth image (entire image) is affected (missing).
CHA ID2
CHB ID2
CHA ID3
CHB ID3
Fig. 7: 8-drive system
One quarter of the image is missing in • One of the 4 image drives is defective or has been refor-
the horizontal direction on every matted. The concerned drive can be recognized by the
image acquired in the 1024 Matrix. position of the horizontal stripe in the image. The channel
number and the SCSI ID can be found in the drawing. For
CHA ID0
the location of the drive in the disk array, see (How to iden-
tify the image drives / p. 110).
NOTE: When the scene is acquired in the 512 Matrix, every
CHB ID0
fourth image (entire image) is affected (missing).
CHA ID1
CHB ID1
One half of the image is missing in the • One of the 2 image drives is defective or has been refor-
horizontal direction on every image matted. The concerned drive can be recognized by the
acquired in the 1024 Matrix. position of the horizontal stripe in the image. The channel
number and the SCSI ID can be found in the drawing. For
the location of the drive in the disk array, see (How to iden-
tify the image drives / p. 110).
CHA ID0
NOTE: When the scene is acquired in the 512 Matrix, every
second image (entire image) is affected (missing).
CHB ID0

07.07 CS PS AX IR/C
Decision Finding 25

One half of the image in the vertical • The problem could be caused either by the AAQ/COPRA
direction is corrupted or contains arti- board (newer BSR HW), or DAM board or the format QDP
facts. in slot 8 (old BSR HW). Both boards process the image in
the same way. Run diagnostics to verify (Factory
Fig. 10: DAM, QDP Slot 8 problem
One quarter of the image in the verti- • The problem could be caused by the AAQ/COPRA board
cal direction is corrupted or contains (newer BSR HW) or QDP board in slot 10 or 12 (old BSR
artifacts. HW). Both boards process the image in the same way. Run
diagnostics to verify (Factory Diagnostics / p. 67).
• The problem could also be caused by any of the VIPER,
COPRA (newer RTC HW) boards in the DIPP (RTC).
Fig. 11: QDP Slot 10, 12 problem

07.07 CS PS AX IR/C
26 Boot Problems
4-
General Information
4Boot Problems
Image System Bootup Steps:

The diagram below shows the different bootup steps within the Host and Realtime PC. As
shown, the Realtime PC is controlled by the Host and reset twice during a normal bootup
cycle.
Host PC Realtime PC
Power on Power on
Host BIOS Realtime hold in
Siemens Medical Sys. Logo RESET via
is displayed Resetsignal cont. Active POI/PCM Board
SCSI initialisation
Adaptec-/Symbios
Messages are displayed
Realtime BIOS
Windows NT/XP VRTX operating Sys.
Resetsignal Removed (Power Up Diagnostics)
Startup
Blue Windows start screen RT waits for Boardmap
Display on SPC on RT COM2:
Load boar ds f r om Hos t
SYNGO Startup
Number count up
Artis Application Realtime BIOS

Short Reset applied VRTX operating Sys.
Display of Image System
Artis User Interface

Display of Application Tabcards Boardmap Download
Send Boardmap
by the Host
IMPAC HW Initializing
DAM, QDP, 1KD, SHA,
Disk Array
Display on SPC on RT COM2:
I ni t i al i z i ng. . . Compl et e
Image System
Ready
Free Disk Space % value present
Fig. 12: Overview of image system bootup

07.07 CS PS AX IR/C
Boot Problems 27
POI/PCM Board Power-up Sequence 4.1
Different hardware is used in the image system:

• Up to image system Serial Numbers 01490 (single plane) and 03098 (biplane), a POI
board (Power ON/OFF) is used in conjunction with a power supply with 5 outputs
(model: Power One).
• Beginning with image system Serial Numbers 01491 (single plane) and 03099
(biplane), the PCM board (Power Control Module) is used in conjunction with a ATX
power supply (Type II power supply).
NOTE The power up sequence is different, depending on the hard-

ware that is configured (POI or PCM). Check the configured
HW and refer to the correct chapter below.
Power-up Sequence with POI Board 0
The figure below shows the POI LED display when the system has successfully booted.
The LED sequence is explained in the table below.
Fig. 13: POI LED display when system is up

07.07 CS PS AX IR/C
28 Boot Problems
Power ON Activities POI LED Status (ON)

Power ON push-button pressed HOST PWR SW LED and RTime
PWR SW LED
Main distributor provides AC to the Image Sys- LAB POWER (+12V local LED is ON)
tem power supply
Power supply provides +6VSB to POI +5V (Local STDBY)
POI provides +5VSB to Host PC and BSR RT PC RT 5SVB and HOST 5SVB
Host sends PS_ON to POI HOST PS ON
POI enables +12V/-12V/+5V supply voltages to +12V SUP, -12V and +5V SUP
entire image system
After about 2 msec, POI enables 3.3 V 3.3V SUP
Detection of all voltage power goods from power No LED indication
supply (+12V Good, -12V Good, +5V Good and
+3.3V Good)
Immediately enable IPM power ok IPM PWR GOOD
Then enable BSR RT PC power ok RT PWR GOOD
If the FPGA config (IPM) is correct, then enable HOST PWR GOOD
Host power ok
The Host PC activates a relay on POI to hold the RTIME RESET
BSR RT PC in Reset until Host software is up
Known Problems
Problem Remedy, Links and Solutions

System can be switched ON, but The LEDs marked with “Host 5VSVB” , “5V Local
the Image System does not get STBY” “RT 5 SVB” on the POI board must go on,
power from the power distributor after the ON button is pressed.
(MD). If not, check the F6 in the power distributor (MD)
and the fuse located next to the AC inlet connector
in the image system

07.07 CS PS AX IR/C
Boot Problems 29

+12V SUP, -12V, +5V SUP not Different reasons: PS defective, cabling problem or
present. POI defective.
System is not booting, LED “HOST This usually means the “FPGA_CONFIG” signal,
PWR GOOD” does not light up which is generated on the IMPAC board, is not o.k.
or cannot be received by the POI board.
Please check:
• Cable connectors J33 and J55 must be con-
nected to the IPM board and should not be
reversed.
• Connector J8 must be connected to the POI
If the connections are o.k., the IMPAC board most
likely is not generating a ““FPGA_CONFIG” signal
and therefore the IPM/IPS has to be replaced.
Power-up Sequence with PCM Board (Type II Power Supply) 0
The power-up sequence with PCM board and Type II power supply basically differs from
the sequence when a POI board is present.
When the X70 connector is connected to the system, power-up with PCM and the
Type II power supply works as follows:
• After power on with the front switch, the Host motherboard gets power from the power
distributor and switches ON the ATX power supply via the PS_ON signal (no LED),
which is generated on the motherboard.
• The PCM board then switches ON the BSR RT PC and IMPAC board.

07.07 CS PS AX IR/C
30 Boot Problems
PCM ( LED display if system is up)
PD UPS OFFH UPS 24V

LAB 24V PS OVER Temp in
HOST PWR SW -
HOST RESET -
RT HD LED RT PWR SW
RTIME RESET -12V
- +5V SUP
LOCAL 3.3V +12V SUP
+5V (STDBY) FPGA_GFG
T COM T HIGH
- RT PS ON
PWR GOOD -
Fig. 14: PCM LED display when system is up
Power ON Activities PCM LED Status (ON)

Line power is applied to the system. LAB 24V
Power ON push-button pressed No LED indication
Power distributor provides AC to the image sys- RT PS ON, 5V(STDBY), LOCAL 3.3V
tem power supply.
The Host motherboard switches on the ATX No LED indication
power supply.
After approx. 5 sec. -12V, +5V SUP, +12V SUP
Power Good is enabled PWR GOOD
After ca. 3 sec. if FPGA_CFG is o.k FPGA_CFG
The Host PC activates a relay on PCM to hold the RTIME RESET is ON
BSR RT PC in Reset until Host software is up.

07.07 CS PS AX IR/C
Boot Problems 31
Known Problems

LAB 24V not present System not switched on or cabling problem (X70 plug).
5V(STBY), LOCAL 3.3V not Check AC on PS input. If AC is present, the power supply
present is defective or there is a wiring problem.
If AC is not present, check the F6 fuse in the power dis-
tributor (MD) and the fuse located next to the AC inlet plug
in the image system.
-12V, +5V SUP, +12V SUP Different reasons:
not present • Either the ATX power supply is defective, or the Host
motherboard does not supply the PS_ON signal to the
ATX power supply. Make the following check to distin-
guish:
- Make a connection using a service cable from the
motherboard ATX power supply plug pin 14
(PS_ON, green colored wire (Fig. 62 / p. 114) to
ground (chassis). If the power supply starts after
this, the Host motherboard is defective. If the power
supply does not start, the power supply is defective.
• The power-up sequence is out of sync (see next step
below).
Power-up sequence out of Power-up sequence is out of sync; this can happen if (dur-
sync. --> Lab can be switched ing troubleshooting), the X70 was disconnected and the
ON, the image system gets image system was switched off hard. Please try the fol-
power from the power distrib- lowing steps to resolve the problem:
utor, but the image system • Press the ON switch to power up the Lab.
does not boot up.
• Remove X70 connector from the POI/PCM board.
This connector is marked with “To Power Distri” and is
located on the rear of the drive tower.
• Switch on the image system using the ON switch. The
yellow LED marked with “HOST PWR SW” should
light up as long the ON switch is pressed, and the
image system should power on. If so, let the bootup
finish, reconnect the X70 cable (while the image sys-
tem is on) and power down the system using
<Options> <End Session> <Shut Down>. After this,
the next power-up should work.

07.07 CS PS AX IR/C
32 Boot Problems

Image system does not power Check whether the cable connector for the PWR
up with the X70 connector dis- switch is correctly connected to the terminal strip, Pins
connected. 8-9 on the motherboard; for the location of the termi-
nal strip, see (1/Fig. 15 / p. 32).
Fig. 15: Host / Realtime PC terminal strip

07.07 CS PS AX IR/C
Boot Problems 33
Black Screen 4.2
A “Black Screen” means no display is present on the control room monitor after the system
is switched on. A “black screen” could have different reasons. Reasons are also different
according to the present hardware (Host 2 Module or Host 3 Module. Use either description
under (Black Screen with POST Code 49/69 on Systems equipped with Host 2
Module / p. 33) or (Black Screen with Post Code 2A on Systems equipped with Host 3
Module / p. 34).
“Black Screen” General Troubleshooting Sequence 0
Perform the following steps if the control room monitor shows nothing on the screen after
the system is switched on:
1. Check whether the monitor has power and is fully functional.
2. Check the POI / PCM board LEDs if the power-up sequence has successfully com-
pleted.
¹ If not, troubleshoot the POI/PCM, power supply. See (POI/PCM Board Power-up
Sequence / p. 27)
¹ If yes, proceed with the next step.
3. Insert the POST Card into the Host PC, see (POST Diagnostics / p. 46).
4. Determine the problem according to the POST code table, see (POST Code Table for
Host 2 Module, BSR RT PC Module (Motorola PATX5000, PATX3070 Mb) / p. 48).
5. Observe the different post code tables for the different Host modules.
Black Screen with POST Code 49/69 on Systems equipped with Host 2 Module
A Black Screen with POST code 49/69 occurs only on “older” image systems equipped with
with Host 2 Module (Motorola PATX5000 Mb) and old 2000W power supply. It means that
the PCI Bus is blocked and is hanging up. This could be caused for one of the following
reasons:
• Defective Host 2 Module
• Defective 1KD board
• Defective IMPAC (IPM, IPS) board
• Defective COM board or COM DMA cable
• Defective SHA board or any other board present on the IMPAC.
Perform the steps below to narrow down the problem:
• Remove the COM board from the Host PC and insert the 1KD board into the same slot.
Connect a monitor to this 1KD board and switch the system on.
¹ Case 1: The Host does not boot, POST code 49(69) is still present. Means that
the Host PC or the 1KD board probably is defective. Try the 2nd 1KD to find out.
Note: The POST code counts up to 88 if no board is inserted in the Host and if the
Host is o.k.
¹ Case 2: The Host PC boots. Means the Host PC and 1KD board are o.k. Try all
1KD boards to make sure all are o.k and proceed with next step.

07.07 CS PS AX IR/C
34 Boot Problems
• Remove the 1KD board from the Host PC and connect COM board again. Remove all
boards from the IMPAC except the 1KD and switch it on.
¹ Case 1: The Host does not boot, POST code 49(69) is still present. Try to use the
1KD in different slots. If the Host does not boot at all, order an IMPAC board,
COM board and COM cables. In biplane systems, disconnect the IPS from the
IPM do find out whether the problem is caused by the IPS or IPM.
¹ Case 2: The Host PC boots. Means one of the IMPAC slots, or one of the boards
is defective. Walk the 1KD board through each slot and check whether the middle
LED blinks. Check each boot for POST code 49(69). If all slots are o.k. middle
(LED on 1KD board blinks), one board must be faulty. Add all boards succes-
sively, boot up between each board and check for the POST code 49. This can
show which board or slot is causing the error. Replace the identified board or the
IPM, IPS board.
NOTE Reset the Host, Symbios BIOS after the hardware has been
completed again, see (Resetting the Host 2 Module Mother-
board BIOS when Changing the Board
Configuration / p. 154).
Black Screen with Post Code 2A on Systems equipped with Host 3 Module
A black screen with POST code 2A occurs only on “newer” image systems equipped with
with Host 3 Module (Intel SE7210TP1-E Mb). It could be caused for one of the following
reasons:
• Defective 1KD board
• Defective IMPAC (IPM, IPS) board
• Defective COM board or COM DMA cable
• Corrupted driver
Perform the steps below to narrow down the problem:
• Remove the COM board from the Host PC
• Connect a monitor (standard PC monitor with a 15-pole VGA connector) to the VGA
connector (labeled as Video), which is located on the connector panel of the Host mod-
ule. Switch on the system.
¹ Case 1: The Host does not boot, POST code 2A is still present. Means that the
the Host Module is defective.
¹ Case 2: The Host PC boots up, a display is available on the connected monitor.
Means the Host PC is o.k.. Continue with the step below.
• Remove a 1KD board from the Impac and insert the board into the COM board slot of
the Host PC. Connect a monitor to this 1KD board and switch the system on.
¹ Case 1: The Host does not boot, POST code 2A is still present. Means that the
the 1KD board probably is defective. When present, try the same with the 2nd or
3rd 1KD board to find out if the problem is caused by these boards.
¹ Case 2: The Host PC boots. Means the Host PC and 1KD board(s) are o.k. Pro-
ceed with next step.

07.07 CS PS AX IR/C
Boot Problems 35
• Remove the 1KD board from the Host PC and connect COM board again. Remove all
boards from the IMPAC except the 1KD and switch it on.
¹ Case 1: The Host does not boot, POST code 2A is still present. Try to use the
1KD in a different slot. If the Host does not boot at all, order an IMPAC board,
COM board and COM cables. In biplane systems, disconnect the IPS from the
IPM do find out whether the problem is caused by the IPS or IPM.
¹ Case 2: The Host PC boots. Means one of the IMPAC slots, or one of the boards
is defective. Walk the 1KD board through each slot and check whether the middle
LED blinks. Check each boot for POST code 2A. If all slots are o.k. (middle LED
on the 1KD blinks), one board must be faulty. Add all boards successively, boot
up between each board and check for the POST code 2A. This can show which
board or slot is causing the error. Replace the identified board or the IPM, IPS
board.

07.07 CS PS AX IR/C
36 Boot Problems
Startup Diagnostics Fail 4.3
The startup diagnostics are performed during each power up cycle.
Symptoms 0
Symptom 1:
The Startup diagnostics do not start at all, the Host PC does not boot further.
Symptom 2:
Certain startup tests (e.g. IMPAC SDRAM startup diagnostics) fail and block the system
from booting.
How to solve the problem 0
Symptom 1:
Could be caused by a defective system disk or by a corrupted SW on the system disk.
Depending from the present Host module, perform the following steps to solve it:
If a Host 2 Module (Motorola PATX5000 Mb) is present:
1. Reboot, start the Adaptec BIOS with CTRL+A and run disk verify, see (Verification of
the Host 2 Module System Drive / p. 107)
2. Try to format the system drive if verification fails. If this fails too, replace the Host PC
module or system drive.
3. Reload the SW
If a Host 3 Module ((Intel SE7210TP1-E Mb) is present:
1. The Host 3 is equipped with a SATA IDE drive, therefore formatting and verifying of the
system disk is not possible.
2. Check if the SATA, power cable is connected to the disk, check if the disk motor runs.
3. Replace the system disk or Host 3 module.
Symptom 2:
Could be caused by a defective hardware, perform the following steps to solve it:
1. Press the ESC key on the failing test to skip this test and to carry on with the remaining
tests.
2. Open the event log when the system is up and check the system log for any startup
diagnostics messages, see (Startup Diagnostics / p. 64) for more information.
3. The startup diagnostics message should contain the board which did not pass the star-
tup diagnostics test.

07.07 CS PS AX IR/C
Boot Problems 37
Windows OS does not start 4.4
Windows NT-based Systems (SW VA42/60) 0
Symptoms
Symptom 1:
• Adaptec and Symbios Bios messages appear on the screen, “NT detect” does not
appear.
Symptom 2:
• Bootup stops at the display of the NT service pack version shortly after the blue startup
screen is displayed.
How to solve the problem

If symptom 1 is present, the problem can be caused by and solved with:
• A defective system drive.
¹ Reboot, start the Adaptec BIOS with CTRL+A and run disk verify, see (Verifica-
tion of the Host 2 Module System Drive / p. 107).
¹ Try to format the system drive if verification fails. If this fails too, replace the Host
PC module (system drive).
• A defective SHA board (SCSI controller for the disk array)
¹ Boot without the SHA board. If this works, replace the SHA board.
• Problem with the CD-R, CD-ROM.
¹ Reboot, start the Adaptec BIOS with CTRL+A, check whether the DR-ROM,
CD-R is recognized by the BIOS.
¹ Boot with the CD-ROM, CD-R drive disconnected.
Windows XP-based Systems (VB..) 0
Symptoms
Symptom 1:
• The boot up stops after the startup diagnostics finishes successfully. The Windows
desktop does not appear
How to solve the problem

• A shared network drive on a computer, which is not switched on.
¹ Press the <Return> key. If the system boots further, open the Windows Explorer
and check if any permanently shared drive is configured. Disconnect this drive via
Tools, Disconnect Network Drive ....

07.07 CS PS AX IR/C
38 Boot Problems
• A defective SHA board (SCSI controller for the disk array)

¹ Boot without the SHA board. If this works, replace the SHA board.
• Problem with the CD-R, CD-ROM.
¹ Reboot, start the Adaptec BIOS with CTRL+A, check whether the DR-ROM,
CD-R is recognized by the BIOS.
¹ Boot with the CD-ROM, CD-R drive disconnected.
• SW on system disk is corrupted
¹ Reload the SW software.

07.07 CS PS AX IR/C
Boot Problems 39
Blue Screen 4.5
Symptom:
Windows NT(XP) boots up to the first blue screen and then crashes. This condition can be
caused by a failure of NT(XP) to load device drivers or hardware problems causing the soft-
ware to crash.
“Blue Screen” Troubleshooting Sequence 0
Perform the following steps if the control room monitor shows a permanent “blue
screen” during each boot:
• Remove the COM board from the Host PC and insert the 1KD board into the same slot.
Connect a monitor to the 1KD and switch it on. If a Host 3 Module is present, remove
the COM board and connect Monitor to the Video connector located on the connector
panel of the Host 3.
¹ Case 1: The Host boots without the blue screen. The problem is probably caused
by the IMPAC board or any board connected to the IMPAC. Try to remove the
boards successively to find out which board causes the blue screen.
¹ Case 2: The blue screen still appears. Try to reload the system software. If this
does not solve the fault, replace the Host PC.
Perform the following steps if the control room monitor shows a intermittent “blue
screen”:
• No valid suggestion can be made here. Change first the Host Module. If the “Blue
Screen” still appears, try to reload SW or change the other hardware on IMPAC succes-
sively.

07.07 CS PS AX IR/C
40 Boot Problems
Syngo, Artis Application does not start 4.6
The following symptoms could be present:

• Syngo application starts to boot. The number count is present on the screen. After a
short time the count stops and the monitor screen shows the Windows Desktop again.
• Syngo application starts to boot, the number count display does not change.
NOTE The number count display will not change (stays always on
1) in biplane systems equipped with 6 1KD boards. This is not
a fault.
• System boots into the gray error task card, showing the message “Initialization Error,
call Service”.
The above mentioned symptoms can be caused by, solved with:

• An incorrect or incomplete network configuration
¹ Open <Local Service> <Configuration> <TCPIP/LAN> and check the IP number
and subnet mask.
- In the IP number, leading zeros (0) are not allowed.
- The subnet mask should not be configured to 4 times 255 (255.255.255.255).
- A host name should be configured.
• A defective or an incomplete Versant database generated.
¹ Open a command tool window (DOS box) and type in the command “dblist”. The
following databases must be displayed:
-- ArchiveStore@”hostname”
-- Local@”hostname”
-- SchedulerStore@”hostname”
-- Exchangeboard@”hostname
¹ Recreate the database, see (Deleting the Database / p. 138)
• A corrupted application software.
¹ Reload the system software
• Too little free disk space on partition C:\ to start the application.
¹ Check the contents of the C:\ partition using the Properties function from the NT
Explorer. A minimum amount of 1 GB disk space (see Note below) must be free. If
the disk space is low, the following folders may contain several GBs of log data:
- C:\AXIOM\log.
- C:\sysmgmt\TND\LOGS
¹ Delete the contents of theses folders.

07.07 CS PS AX IR/C
Boot Problems 41
NOTE The size for the C:\ partition varies between the SW versions
and Host modules. Examples:
• SW VB23 (Host 2/3): C:\ partition = 12GB, D:\ partition =
7GB
• SW VB30/31 (Host 3): C:\ partition = 20GB, D.\partition =
95GB

07.07 CS PS AX IR/C
42 Boot Problems
BSR RT PC does not boot, IMPAC HW cannot be initialized. 4.7
BSR RT PC Bootup Sequence 0
During a normal bootup, the BSR RT PC bootup sequence behaves as follows:
1. The BSR RT PC is held in reset by the Host PC until the startup diagnostic screen
appears and the startup diagnostics start.
2. After the reset is removed, the BSR RT PC boots its VRTX operating system and stops
at “Load board from Host”.
3. Shortly before the Host application bootup is finished (when BSR cube is displayed),
the BSR RT PC is reset again by the Host. At this time, the boot continues, initializes the
hardware in the IMPAC and stops at “... Initializing ... Complete”.
A failed boot up is indicated by the following symptoms:
• The display of the free disk space (Disk Free ..%) in the Examination task card will not
show any value.
• The message “IS not available, try power off/on” is displayed in the ACQ message line
of the monitor.
• The BSR RT PC will report “?” instead of a SW version in the service applications “Ver-
sion Check” and “SW Manager”.
Perform the following steps to locate the problem:

• Switch system to development mode, see (Enabling the Developer Menu / p. 146).
• Connect a service PC to the COM 2 board and start a terminal emulation program, see
(Connection of the Service PC / p. 146).
• Perform a reset to the BSR RT PC using the Test Tools service page.
¹ Case 1: Nothing is displayed on the service laptop.
Switch off and insert the POST card into a free slot, see (POST Card User
Instructions / p. 46). Power up (wait until the RT Reset is released) and check the
POST code, see (POST Code Table for Host 2 Module, BSR RT PC Module
(Motorola PATX5000, PATX3070 Mb) / p. 48). Replace the BSR RT PC (depend-
ing on the POST code).
¹ Case 2: The BSR RT PC boots, trace messages appear on the Service PC
screen, but the bootup does not finish and an error message is displayed.
See (Checking the Bootup Trace / p. 82) to determine where the bootup stops.
Replace the suggested hardware.
¹ Case 3: The BSR RT PC performs a cyclical reboot. See (Cyclical Reboot of the
BSR RT PC / p. 43).
¹ Case 4: BSR RT PC displays error messages at a high repetition rate. See (BSR
RT PC displays error messages at a high repetition rate / p. 43)

07.07 CS PS AX IR/C
Boot Problems 43
Cyclical Reboot of the BSR RT PC 0
Miscellaneous function problems during bootup of the BSR RT PC and IMPAC HW, for
instance a defective or missing image drive, will force the BSR RT PC to perform cyclical
resets. There is no way to communicate to the BSR RT PC while it is performing cyclical
reboots. These resets will continue unless the Host Application is stopped, see (Stop Appli-
cation SW / p. 158). To find the problem, the BSR RT PC bootup trace (Checking the
Bootup Trace / p. 82) should be checked. Compare the number of installed drives with the
recognized number of drives in the bootup trace. If one or more installed drives are missing
in the trace, check the following:
• Cabling of the SCSI ribbon cables from the SHA board to the disk array.
• Power cables and connectors on the disk array drives.
• Verify the function of the image drives via the Symbios BIOS, see (Verification of an
Image Drive / p. 109).
BSR RT PC Boots into a Fatal Error 0
Some function problems detected during boot up of the BSR RT PC and IMPAC HW will
result in a fatal error on the BSR RT PC. If a fatal error occurs, communication with the BSR
RT PC through the Terminal Emulation program or the Service UI cannot be established
anymore. This fatal error could have different reasons. It is recommended to connect a Ser-
vice PC to the BSR RT PC, see (Using the COM 2 port of the BSR RT PC for
service / p. 146) and check the boot up trace, see (Checking the Bootup Trace / p. 82).
If an incompatible ifs.dat file is the cause of the fatal error, perform the following steps to
clear the problem:
• Stop the application SW, see (Stop Application SW / p. 158).
• Reset the BSR RT PC using the Factory Diagnostics, see (Reset RT: / p. 73)
¹ The BSR RT PC boots to “Load boards from host”
• Delete the ifs.dat, ifs.bak files, see (Manual Deletion of the ifs.dat File / p. 141).
CAUTION Deleting the ifs.dat file will delete all patients stored on the
system
¹ If the images are still required, make sure no other
solution exists to solve the problem before deleting the
file.
BSR RT PC displays error messages at a high repetition rate 0
NOTE The problem described bellow may appear only on image

systems equipped with a new Type II power supply.
If the error messages below (Fig. 16 / p. 44) appear on the Service PC screen at a high
repetition rate, one of the following problems could be present:
• Reset cable not connected to the BSR RT motherboard during power-on.

07.07 CS PS AX IR/C
44 Boot Problems
• PCM board does not hold the BSR RT PC in Reset after power-on. Check the RT Rest
LED on the PCM board, see (Power-up Sequence with PCM Board (Type II Power
Supply) / p. 29)
Fig. 16: Error following BSR RT PC bootup
Stand-along BSR RT PC bootup 0
A service PC connected to the COM 2 port shows the following trace messages if the BSR
RT PC is booted as a stand-alone without a COM board inserted. This indicates that the
RT SW is installed and RT PC HW is o.k.
Fig. 17: BSR RT PC stand-alone bootup trace

07.07 CS PS AX IR/C
Diagnostics 45
5-
General Remarks
5Diagnostics
The following diagnostic functions are available in the image system:
Type of Diag. Executable via Purpose

(from)
POST Diag. Post Card inserted in Check of the BSR RT PC and Host PC mod-
(POST Host or BSR RT PC. ules if a “black screen” is present.
Diagnostics / p. 46
)
Startup Diag. Automatically during Power-up check of the IPM, IPS, SD RAM,
(Startup each bootup DAM, QDP, or COPRA AAQ boards
Diagnostics / p. 64
)
Factory Diag. Windows NT Desktop On-site diagnostic tests of the image system
(Factory HW
Diagnostics / p. 67
)
Hardware Tests <Local Service> Remote and on-site diagnostics of the
(Hardware <Test Tools> image system HW
Tests / p. 77)
Developer Menu Service PC on COM 2 Verification of bootup of the BSR RT PC and
(BSR RT PC BSR RT PC IMPAC Hardware.
Developer
Menu / p. 82)
Network Adapter Win NT <Settings> Function Check of the Network Adaptors
Diagnostics <Control Panel>
(Network Adapter <Network> <Adap-
Diagnostics (Host tors>
2 Module
only) / p. 94)
BIOS Tests Adaptec BIOS, Sym- Verification of the SCSI adapters and con-
(BIOS bios BIOS nected drives
Functions / p. 97)

07.07 CS PS AX IR/C
46 Diagnostics
POST Diagnostics 5.1
POST means Power On Self Test. POST routines are performed by the BIOS each time
the system is reset (or powered on). The main purpose of these routines is to perform diag-
nostic tests on the system components and to initialize parts of the system. It will put the
POST code in port address 80H for each test procedure process. A test card (POST card)
can latch this value and show it on the 7-segment LED display. This code can be used dur-
ing troubleshooting to establish at which point the system failed and which routine was
being performed.
General Information about the POST Card 0
The POST card is shipped with every system. It can be found in the Service Tool Box, which
is located on the inside of the right side cover. The POST card can be used on the 32-bit
PCI slots (short PCI slot) in the Host PC motherboard and BSR RT PC motherboard.
NOTE On the BSR RT PC 2 Module (Raptor ATX Mb), the post card
functionality is included on the motherboard. The 7-segment
display is available on the board. The external POST card is
not required.
The POST card should be used if:

• The Host PC 2 / 3 Module or BSR RT PC does not start to boot at all.
• No display is present on the control room monitor connected to the Host PC
• No display is present on the service PC connected to the COM2 port of the BSR RT PC.
NOTICE Using the POST card in any of the IMPAC PCI slots is
mechanically not possible.
¹ Do not dismantle the bracket from the board. Inserting
the POST card without a bracket in any of the IMPAC
slots will cause serious damage to the system.
POST Card User Instructions 0
• Turn off the system power.

• Remove the covers from the image system.
• Insert the POST card board into an open 32-bit PCI slot (short PCI slot) of the PC mod-
ule you want to check.
• It is recommended to have some free slots on the right side of the POST card, other-
wise the 7-segment display is hard to read.
• Apply power to the image system. The green LEDs marked D1 and D2, see
(1/Fig. 18 / p. 48) should light up after approx. 3 seconds. After this, the POST Card dis-
play starts counting.

07.07 CS PS AX IR/C
Diagnostics 47
NOTE The reset cable must be removed from the RT motherboard

when the POST card is used in the BSR RT PC, otherwise the
BSR RT PC will be held in reset by the Host PC.
• The display has to be read towards the motherboard. Figure (2/Fig. 18 / p. 48) shows
the code 60.
• If the BIOS detects an error condition, it halts POST after issuing a terminal error beep
code.
• The terminal error code is displayed on the POST Card 7-segment display.
Successful Power-on Self-test 0
If inserted, the POST card counts up to a certain number during the POST. Depending on
the PC motherboard, the following numbers indicate a successful power on self test:
PC Module Displayed number after success-

ful POST
Host 2 Module (Motorola PATX5000 Mb) 88 (see note *1 below)
Host 3 Module (Intel SE7210TP!-E Mb) AA (see note *1 below)
BST RT PC Module (Motorola PATX3070 Mb) C0 (see note *1 below)
BSR RT PC 2 Module (Raptor ATX Mb) 00 (see note *2 below)
*1 = Number is valid directly after POST. Number may change when the application is
running.
*2 = Display shows 00 on start of the POST, counts during the POST and displays AA
for a short time followed by a beep. After this, it switches back to 00 again.

07.07 CS PS AX IR/C
48 Diagnostics
POST Card Overview 0
Fig. 18: POST Card
POST Code Table for Host 2 Module, BSR RT PC Module (Motorola PATX5000,
PATX3070 Mb) 0
Use the table below to detect the possible hardware failure if the POST code does not count
to 88 (Host 2 Module), or C0 (BSR RT PC Module).
Code Beep Motorola PATX5000, PATX3070 Mb POST Routine Description)

02h Verify Real Mode
03h Disable Non-Maskable Interrupt (NMI)
04h Get CPU type
06h Initialize system hardware
07h Disable system BIOS shadow and execute from ROM
08h Initialize chip set with initial POST values
09h Set IN POST flag
0Ah Initialize CPU registers
0Bh Enable CPU cache
0Ch Initialize caches to initial POST values
0Eh Initialize I/O component

07.07 CS PS AX IR/C
Diagnostics 49

0Fh Initialize the local bus IDE
10h Initialize Power Management
11h Load alternate registers with initial POST values
12h Restore CPU control word during warm boot
13h Initialize PCI Bus Mastering devices
14h Initialize keyboard controller
16h 1-2-2-3 BIOS ROM checksum
17h Initialize cache before memory autosize
18h 8254 timer initialization
1Ah 8237 DMA controller initialization
1Ch Reset Programmable Interrupt Controller
20h 1-3-1-1 Test DRAM refresh
22h 1-3-1-3 Test 8742 Keyboard Controller
24h Set ES segment register to 4 GB
26h Enable A20 line
28h Autosize DRAM
29h Initialize POST Memory Manager
2Ah Clear 512 KB base RAM
2Ch 1-3-4-1 RAM failure
2Eh 1-3-4-3 RAM failure on data bits of low byte of memory bus
2Fh Enable cache before system BIOS shadow
30h 1-4-1-1 RAM failure
32h Test CPU bus clock frequency
33h Initialize Phoenix Dispatch Manager
36h 1-3-4-3 Warm start shut down
38h Shadow system BIOS ROM
3Ah Autosize cache
3Ch Advanced configuration of chip set registers
3Dh Load alternate registers with CMOS values
42h Initialize interrupt vectors
45h POST device initialization

07.07 CS PS AX IR/C
50 Diagnostics

46h 2-1-2-3 Check ROM copyright notice
47h Initialize I20 support
48h Check video configuration against CMOS
49h Initialize PCI bus and devices: can be caused by any board, even an
empty slot can cause this error. Normally a “Black Screen” is
present if the POST stops at this point. See (Known
Problems / p. 62) for more information.
4Ah Initialize all video adapters in system
4Bh Quiet Boot start (optional)
4Ch Shadow video BIOS ROM
4Eh Display BIOS copyright notice
4Fh Multi Boot initialization (optional)
50h Display CPU type and speed
51h Initialize EISA board
52h Test keyboard
54h Set key click if enabled
55h USB initialization (optional)
58h 2-2-3-1 Test for unexpected interrupts
59h Initialize POST display service
5Ah Display prompt ’Press F2 to enter SETUP’
5Bh Disable CPU cache
5Ch Test RAM between 512KB and 640KB
60h Test extended memory
62h Test extended memory address lines
64h Jump to User Patch 1
66h Configure advanced cache registers
67h Initialize Multi Processor APIC
68h Enable external and CPU caches
69h System Management Mode (SMM) setup area. Normally a “Black
Screen” is present if the POST stops at this point. See (Known
Problems / p. 62) for more information.
6Ah Display external L2 cache size
6Bh Load custom defaults (optional)

07.07 CS PS AX IR/C
Diagnostics 51

6Ch Display shadow area message
6Eh Display possible high address for UMB recovery
70h Display error messages
72h Check for configuration errors
76h Check for keyboard errors
7Ch Set up hardware interrupt vectors
7Eh Initialize co-processor if present
80h Disable onboard Super I/O ports and IRQs
81h Late POST device initialization
82h Detect and install external RS232 ports
83h Configure non-MCD IDE controllers
84h Detect and install external parallel ports
85h Initialize PC-compatible PnP ISA devices
86h Re-initialize onboard I/O ports
87h Configure Motherboard Configurable Devices (optional)
88h Initialize BIOS Data Area.
Note: The Host PC stops here after a successful power-on
self-test (POST).
89h Enable Non-Maskable Interrupts (NMIs)
8Ah Initialize Extended BIOS Data Area
8Bh Test and initialize PS/2 mouse
8Ch Initialize floppy controller
8Fh Determine number of ATA drives (optional)
90h Initialize hard disk controller
91h Initialize local bus hard disk controllers
92h Jump to User Patch 2
93h Build MPTABLE for multiprocessor boards
95h Install CD ROM for boot
96h Clear huge ES segment register
97h Fix up multiprocessor table
98h 1-2 Search for option ROMs. One long, two short beeps on checksum
failure

07.07 CS PS AX IR/C
52 Diagnostics

99h Check for SMART Drive (optional)
9Ah Show option ROMs
9Ch Setup Power Management
9Dh Initialize security engine (optional)
9Eh Enable hardware interrupts
9Fh Determine number of ATA and SCSI drives
A0h Set time of day
A2h Check key lock
A4h Initialize typematic rate
A8h Erase F2 prompt
AAh Scan for F2 key stroke
ACh Enter SETUP
AEh Clear Boot flag
B0h Check for errors
B2h POST done - prepare to boot operating system
B4h 1 One short beep before boot
B5h Terminate Quiet Boot (optional)
B6h Check password (optional)
B9h Prepare Boot
BAh Initialize DMI parameters
BBh Initialize PnP Option ROMs
BCh Clear parity checkers
BDh Display Multi Boot menu
BEh Clear Screen (optional)
BFh Check virus and backup reminders
C0h Try to boot with INT 19.
Note: The BSR RT PC stops here after a successful power-on
self-test (POST).
C1h Initialize POST Error Manager (PEM)
C2h Initialize error logging
C3h Initialize error display function

07.07 CS PS AX IR/C
Diagnostics 53

C4h Initialize system error handler
C5h Dual CMOS (optional)
C6h Initialize note dock (optional)
C7h Initialize note dock late
C8h Force check (optional)
C9h Extended checksum (optional)
CAh Initialize serial keyboard device (optional)
CBh Initialize ROM/RAM disk (optional)
CCh Initialize serial video device (optional)
CDh Enable PCMCIA cards (optional)
D2h Unknown interrupt
none 1- 4 Serial EEPROM device failure
none 1- 5 CMOS restored from serial EEPROM
none 1- 6 CMOS and serial EEPROM contents invalid; CMOS defaults loaded
E0H - Boot block in Flash ROM
F7h
Post Code Table Host 3 Module (Intel SE7210TP1-E TPS Mb) 0
to AA (Host 3 Module).
Code POST Routine Description (Intel SE7210TP1-E TPS Mb)

03h Disable NMI, Parity, video for EGA, and DMA controllers. Initialize BIOS,
POST, Runtime data area. Also initialize BIOS modules on POST entry
and GPNV area. Initialized CMOS as mentioned in the Kernel Variable
"wCMOSFlags."
04h Check CMOS diagnostic byte to determine whether battery power is OK
and the CMOS checksum is OK. Verify the CMOS checksum manually by
reading the storage area. If the CMOS checksum is bad, update CMOS
with power-on default values and clear the passwords. Initialize status reg-
ister A. Initializes data variables that are based on CMOS setup questions.
Initializes both 8259-compatible PICs in the system.
05h Initializes the interrupt controlling hardware (generally PIC) and interrupt
vector table.

07.07 CS PS AX IR/C
54 Diagnostics

06h Perform a R/W test to CH-2 count reg. Initialize CH-0 as a system timer.
Install the POSTINT1Ch handler. Enable IRQ-0 in PIC for system timer
interrupt. Traps INT1Ch vector to "POSTINT1ChHandlerBlock."
08h Initializes the CPU. The BAT test is being done on KBC. Program the key-
board controller command byte is being done after Auto detection of
KB/MS using AMI KB-5.
C0h Early CPU Init Start -- Disable Cache - Init Local APIC
C1h Set up bootstrap processor information
C2h Set up bootstrap processor for POST
C5h Enumerate and set up the application processors
C6h Re-enable cache for the bootstrap processor
C7h Early CPU Init Exit
0Ah Initializes the 8042-compatible keyboard controller.
0Bh Detects the presence of a PS/2 mouse.
0Ch Detects the presence of a keyboard in the KBC port.
0Eh Testing and initialization of different input devices. Also, update the kernel
variables. Traps the INT09h vector so that the POST INT09h handler gets
control for IRQ1. Decompress all available language, BIOS logo, and Silent
logo modules.
13h Early POST initialization of chipset registers.
24h Decompress and initialize any platform-specific BIOS modules.
30h Initialize System Management Interrupt.
2Ah Initializes different devices through DIM. Normally a “Black Screen” is
present if the POST stops at this point. See (Known Problems / p. 62)
for more information.
2Ch Initializes different devices. Detects and initializes the video adapter
installed in systems that have optional ROMs.
2Eh Initializes all the output devices.
31h Allocate memory for ADM module and decompress it. Give control to the
ADM module for initialization. Initialize language and font modules for
ADM. Activate the ADM module.
33h Initializes the silent boot module. Set the window for displaying text infor-
mation.
37h Displays sign-on message, CPU information, setup key message and any
OEM-specific information.
38h Initializes different devices through DIM. See the DIM Code Checkpoints
section of document for more information.

07.07 CS PS AX IR/C
Diagnostics 55

39h Initializes DMAC-1 & DMAC-2
3Ah Initialize RTC date/time.
3Bh Test for total memory installed in the system. Also, check for DEL or ESC
keys to limit memory test. Displays total memory in the system.
3C Mid-POST initialization of chip set registers.
40h Detects different devices (parallel ports, serial ports, and coprocessor in
CPU, … etc.) successfully installed in the system and updates the BDA,
EBDA…etc.
50h Programming of the memory hole or any kind of implementation that needs
an adjustment in system RAM size, if needed.
52h Updates the CMOS memory size from the memory found in memory test.
Allocates memory for the Extended BIOS Data Area from the base mem-
ory
60h Initializes NUM-LOCK status and programs the KBD typematic rate.
75h Initializes Int-13 and prepares for IPL detection.
78h Initializes IPL devices controlled by the BIOS and optional ROMs.
7Ah Initializes the remaining optional ROMs.
7C Generates and writes contents of ESCD in NVRam.
84h Log errors encountered during POST.
85h Displays errors to the user and gets the user response to the error.
87h Executes the BIOS setup if needed / requested.
8Ch Late POST initialization of chip set registers.
8Dh Builds ACPI tables (if ACPI is supported)
8Eh Programs the peripheral parameters. Enables/disables NMI as selected
90h Late POST initialization of system management interrupt.
A0h Checks boot password if installed.
A1h Clean-up work needed before booting to OS.
A2h Handles runtime image preparation for different BIOS modules. Fills the
free area in the F000h segment with 0FFh. Initializes the Microsoft IRQ
Routing Table. Prepares the runtime language module. Disables the sys-
tem configuration display, if needed.
A4h Initializes the runtime language module.
A7h Displays the system configuration screen, if enabled. Initializes the CPUs
before boot, which includes the programming of the MTRRs.
A8h Prepares the CPU for OS boot, including final MTRR values.

07.07 CS PS AX IR/C
56 Diagnostics

A9h Wait for user input in config display, if needed.
AAh Uninstall POST INT1Ch vector and INT09h vector. Deinitializes the ADM
module.
Note: The Host 3 Module stops here after a successful power-on self
test (POST)
ABh Prepares BBS for Int 19 boot.
ACh End of POST initialization of chip set registers.
B1h Saves system context for ACPI.
00h Passes control to OS Loader (typically INT19h).
Post Code Table BSR RT PC 2 Module (Raptor ATX Mb) 0
to AA-> 00 (BSR-RT-PC with Raptor ATX Mb.
Code POST Routine Description (Raptor ATX Mb)

D0h The NMI is disabled. Power on delay starts. Next, the initialization code
checksum is verified.
D1h Initializes the DMA controller, performs the keyboard controller BAT test,
starts memory refresh and enters 4 GB flat mode next.
D3h Starts memory sizing next.
D4h Returns to real mode. Executes any OEM patches and sets the stack next
D5h Passes control to the uncompressed code in shadow RAM at E000:0000h.
The initialization code is copied to segment 0 and control is transferred to
segment 0
D6h Control is in segment 0. Next, checks whether <Ctrl> <Home> was pressed
and verifies the system BIOS checksum. If either <Ctrl> <Home> was
pressed or the system BIOS checksum is bad, next it will go to checkpoint
code E0h. Otherwise it goes to checkpoint code D7h.
D7h Main BIOS runtime code is decompressed and control is passed to the
main BIOS in the shadow RAM
E0h If available, the onboard floppy controller is initialized. Next, begins the
base 512 KB memory test.
E1h Initializes the interrupt vector table next.
E2h Initializes the DMA and interrupt controllers next.
E6h Enables the floppy drive controller and timer IRQs. Enables internal cache
memory.

07.07 CS PS AX IR/C
Diagnostics 57

EDh Initializes the floppy drive.
EEh Looks for a floppy diskette in drive A:. Reads the first sector of the diskette.
EFh A read error occurred while reading the floppy drive in drive A:.
F0h Next, searches for the AMIBOOT.ROM file in the root directory
F1h The AMIBOOT.ROM file is not in the root directory.
F2h Next, reads and analyzes the FAT floppy diskette to find the clusters occu-
pied by the AMIBOOT.ROM file.
F3h Next, reads the AMIBOOT.ROM file, cluster by cluster.
F4h The AMIBOOT.ROM file is not the correct size.
F5h Next, disables internal cache memory.
FBh Next, detects the type of flash ROM.
FCh Next, erases the flash ROM.
FDh Next, programs the flash ROM.
FFh Flash ROM programming was successful. Next restarts the system BIOS.
03h The NMI is disabled. Next, checks for a soft reset or a power-on condition.
05h The BIOS stack has been built. Next, disables cache memory.
06h Decompresses the POST code next.
07h Next, initializes the CPU and the CPU data area
08h The CMOS checksum calculation is done next.
0Ah The CMOS checksum calculation is done. Initializes the CMOS status reg-
ister for date and time next.
0Bh The CMOS status register is initialized. Next, performs any required initial-
ization before the keyboard BAT command is issued.
0Ch The keyboard controller input buffer is free. Next, issues the BAT command
to the keyboard controller.
0Eh The keyboard controller BAT command result has been verified. Next, per-
forms any necessary initialization after the keyboard controller BAT com-
mand test.
0Fh Initialization after the keyboard controller BAT command test is done. The
keyboard command byte is written next.
10h The keyboard controller command byte is written. Next, issues the Pin 23
and 24 blocking and unblocking command.
11h Next, checks whether <End or <Ins> keys were pressed during power on.
Initializes CMOS RAM if the Initialize CMOS RAM in every boot AMIBIOS
POST option was set in AMIBCP or the <End> key was pressed.

07.07 CS PS AX IR/C
58 Diagnostics

12h Next, disables DMA controllers 1 and 2 and interrupt controllers 1 and 2.
13h The video display has been disabled. Port B has been initialized. Next, ini-
tializes the chip set.
14h The 8254 timer test will begin next.
19h The 8254 timer test is over. Starts the memory refresh test next.
1Ah The memory refresh line is toggling. Checks the 15 second on/off time next.
23h Reads the 8042 input port and disables the MEGAKEY Green PC feature
next. Makes the BIOS code segment writable and performs any necessary
configuration before initializing the interrupt vectors.
24h The configuration is required before interrupt vector initialization has com-
pleted. Interrupt vector initialization is about to begin.
25h Interrupt vector initialization is done. Clears the password if the POST DIAG
switch is on.
27h Any initialization before setting video mode will be done next.
28h Initialization before setting the video mode is complete. Configures the
monochrome mode and color mode settings next.
2Ah Bus initialization system, static, output devices will be done next, if present.
See Table D-7 for additional information.
2Bh Passes control to the video ROM to perform any required configuration
before the video ROM test.
2Ch All necessary processing before passing control to the video ROM is done.
Looks for the video ROM next and passes control to it.
2Dh The video ROM has returned control to BIOS POST. Performs any required
processing after the video ROM has control.
2Eh Completed post-video ROM test processing. If the EGA/VGA controller is
not found, performs the display memory read/write test next.
2Fh The EGA/VGA controller was not found. The display memory read/write
test is about to begin.
30h The display memory read/write test passed. Looks for retrace checking
next.
31h The display memory read/write test or retrace checking failed. Performs the
alternate display memory read/write test next.
32h The alternate display memory read/write test passed. Looks for alternate
display retrace checking next.
34h Video display checking is over. Sets the display mode next.
37h The display mode is set. Displays the power on message next.
38h Initializes the bus input, IPL, general devices next, if present.

07.07 CS PS AX IR/C
Diagnostics 59

39h Displays bus initialization error messages.
3Ah The new cursor position has been read and saved. Displays the Hit <DEL>
message next.
3Bh The Hit <DEL> message is displayed. The protected mode memory test is
about to start.
40h Prepares the descriptor tables next.
42h The descriptor tables are prepared. Enters protected mode for the memory
test next.
43h Entered protected mode. Enables interrupts for diagnostics mode next.
44h Interrupts enabled if the diagnostics switch is on. Initializes data to check
memory wraparound at 0:0 next.
45h Data initialized. Checks for memory wraparound at 0:0 and finds the total
system memory size next.
46h The memory wraparound test is done. Memory size calculation has been
done. Writes patterns to test memory next.
47h The memory pattern has been written to extended memory. Writes patterns
to the base 640 KB memory next.
48h Patterns written in base memory. Determines the amount of memory below
1 MB next.
49h The amount of memory below 1 MB has been found and verified. Deter-
mines the amount of memory above 1 MB memory next.
4Bh The amount of memory above 1 MB has been found and verified. Checks
for a soft reset and clears the memory below 1 MB for the soft reset next. If
this is a power on situation, goes to checkpoint 4Eh next.
4Ch The memory below 1 MB has been cleared via a soft reset. Clears the
memory above 1 MB next.
4Dh The memory above 1 MB has been cleared via a soft reset. Saves the
memory size next. Goes to checkpoint 52h next.
4Eh The memory test started, but not as the result of a soft reset. Displays the
first 64 KB memory size next.
4Fh The memory size display has started. The display is updated during the
memory test. Performs the sequential and random memory test next.
50h The memory below 1 MB has been tested and initialized. Adjusts the dis-
played memory size for relocation and shadowing next.
51h The memory size display was adjusted for relocation and shadowing. Tests
the memory above 1 MB next.
52h The memory above 1 MB has been tested and initialized. Saves the mem-
ory size information next.

07.07 CS PS AX IR/C
60 Diagnostics

53h The memory size information and the CPU registers are saved. Enters real
mode next.
54h Shutdown was successful. The CPU is in real mode. Disables the Gate A20
line, parity and the NMI next.
57h The A20 address line, parity and the NMI are disabled. Adjusts the memory
size depending on relocation and shadowing next.
58h The memory size was adjusted for relocation and shadowing. Clears the Hit
<DEL> message next.
59h The Hit <DEL> message is cleared. The <WAIT...> message is displayed.
Starts the DMA and interrupt controller test next.
60h The DMA page register test passed. Performs the DMA Controller 1 base
register test next.
62h The DMA controller 1 base register test passed. Performs the DMA control-
ler 2 base register test next.
65h The DMA controller 2 base register test passed. Programs DMA controllers
1 and 2 next.
66h Completed programming DMA controllers 1 and 2. Initializes the 8259 inter-
rupt controller next.
67h Completed 8259 interrupt controller initialization.
7Fh Extended NMI source enabling is in progress.
80h The keyboard test has started. Clears the output buffer and checks for stuck
keys. Issues the keyboard reset command next.
81h A keyboard reset error or stuck key was found. Issues the keyboard control-
ler interface test command next.
82h The keyboard controller interface test completed. Writes the command byte
and initializes the circular buffer next.
83h The command byte was written and global data initialization has com-
pleted. Checks for a locked key next.
84h Locked key checking is over. Checks for a memory size mismatch with
CMOS RAM data next.
85h The memory size check is done. Displays a soft error and checks for a
password or bypasses WINBIOS Setup next.
86h The password was checked. Performs any required programming before
WINBIOS Setup next.
87h The programming before WINBIOS Setup has completed. Decompresses
the WINBIOS Setup code and executes the AMIBIOS Setup or WINBIOS
Setup utility next.

07.07 CS PS AX IR/C
Diagnostics 61

88h Returns from WINBIOS Setup and clears the screen. Performs any neces-
sary programming after WINBIOS Setup next.
89h The programming after WINBIOS Setup has completed. Displays the
power on screen message next.
8Bh The first screen message has been displayed. The <WAIT...> message is
displayed. Performs the PS/2 mouse check and extended BIOS data area
allocation check next.
8Ch Programs the WINBIOS Setup options next.
8Dh The WINBIOS Setup options are programmed. Resets the hard disk con-
troller next.
8Fh The hard disk controller has been reset. Configures the floppy drive control-
ler next.
91h The floppy drive controller has been configured. Configures the hard disk
drive controller next.
95h Initializes the bus option ROMs from C800 next.
96h Initializes before passing control to the adaptor ROM at C800.
97h Initialization before the C800 adaptor ROM gains control has completed.
The adaptor ROM check is next.
98h The adaptor ROM had control and has now returned control to BIOS POST.
Performs an
99h Any initialization required after the option ROM test has completed. Config-
ures the timer data area and printer base address next.
9Ah Set the timer and printer base addresses. Sets the RS 232 base address
next.
9Bh Return after setting the RS-232 base address. Performs any required ini-
tialization before the coprocessor test next
9Ch Required initialization before the coprocessor test is over. Initializes the
coprocessor next.
9Dh Coprocessor initialized. Performs any required initialization after the copro-
cessor test next.
9Eh Initialization after the coprocessor test is complete. Checks the extended
keyboard, keyboard ID, and Num Lock key next. Issues the keyboard ID
command next.
A2h Displays any soft errors next.
A3h The soft error display has completed. Sets the keyboard typematic rate
next.
A4h The keyboard typematic rate is set. Programs the memory wait states next.

07.07 CS PS AX IR/C
62 Diagnostics

A5h Memory wait state programming is over. Clears the screen and enables
parity and the NMI next.
A7h NMI and parity enabled. Performs any initialization required before passing
control to the adaptor ROM at E000 next.
A8h Initialization before passing control to the adaptor ROM at E000h com-
pleted. Passes control to the adaptor ROM at E000h next.
A9h Returned from adaptor ROM at E000h control. Performs any initialization
required after the E000 option ROM had control next.
AAh Initialization after E000 option ROM control has completed. Displays the
system configuration next.
Note: The Raptor ATX Module stops here after a successful power on
self test (POST.)
ABh Decompresses the DMI data and executes DMI POST initialization next.
B0h The system configuration is displayed.
B1h Copies any code to specific areas.
00h Code copying to specific areas is done. Passes control to INT 19h boot
loader next.
Known Problems 0

POST card LEDs D1, D2 off, Motherboard has no power. Checks power supply,
no display POI/PCM board. See (Power-up Sequence with PCM
Board (Type II Power Supply) / p. 29)
LED D1 off Board is held in reset.
Host 2 Module with Motorola PCI Bus cannot be initialized. There is probably no display
PATX5000 Mb stops on available on the monitor (black screen).
POST code 49/69 • Switch off the image system, remove the COM board.
• If the POST stops again at 49/69, the motherboard is
defective.
• If the count goes through to 88 (Host) or C0 (BSR RT
PC), the problem is caused by the COM board, PCI
cable, IMPAC, 1KD board or any other board on the
IMPAC, see (BSR RT PC does not boot, IMPAC HW
cannot be initialized. / p. 42).

07.07 CS PS AX IR/C
Diagnostics 63

Host 2 Module with Motorola SD-RAM on motherboard defective.
PATX5000 Mb stops on Note: On the Host 2 Module, code 60 is displayed for
POST code 60 about 1.5 minutes because of the RAM check of the
2GB RAM.
Host 3 Module with Intel There is probably no display available on the monitor
SE7210TP1-E Mb stops on (black screen). Could be caused by a defective 1KD
POST code 2A board, or corrupted driver. Downgrade to minimum HW,
see (Stand-alone Host PC / p. 128) and reload the drivers,
see (Device driver installation with SW ≥VB11M, VB22/23,
VB30/31 / p. 173).

07.07 CS PS AX IR/C
64 Diagnostics
Startup Diagnostics 5.2
Beginning with SW VA 42C, all systems contain startup diagnostics. The startup diagnos-
tics run during every power-up or reset of the image system. The startup diagnostics are
executed prior to the start of the Windows operating system. Test results (pass/fail) are dis-
played on the control room monitor and written into the system event log.
HW Check during Startup Diagnostics 0
The following image system hardware is tested by the startup diagnostics:

• Host COM board and PCI cables. All PCI jumpers on the IPM, IPS board.
Monitor display: PCI - PCI Startup Diagnostics ... Passed
• DMA board
Monitor display: DMA Startup Diagnostics ... Passed
• SD-RAM (1GB) located on the IPM, IPS board
Monitor display: IMPAC SDRAM Startup Diagnostics ... Passed
• All installed DAM, QDP boards (VA42/60, VB11 only)
Monitor display: QDP - DAM Startup Diagnostics ... Passed
• COPRA board (VB22 , VB30 only)
Monitor display: COPRA Startup Diagnostics ... Passed
• AAQ board (VB22, VB30 only)
Monitor display: AAQ Startup Diagnostics ... Passed
• All installed 1KD boards
Monitor display: 1KD Startup Diagnostics ... Passed
• Communication between Host PC and BSR RT PC
Monitor display: NTB and RT PC Startup Diagnostics ... Passed
NOTE Execution of the power-up diagnostics can be aborted using

the ESC key, when prompted.
The following image system hardware is not tested by the startup diagnostics:
• SHA board (SCSI Host Adapter).
• All connected image drives in the disk array.

07.07 CS PS AX IR/C
Diagnostics 65
Startup Diagnostic Results 0
For each successfully performed startup diagnostic test, the following 3 messages are writ-
ten into the system event log, see (How to Open the System Log / p. 65):
13 IscComm n/a ISCCOMM RT PC DIAGS COMPLETED.
13 IscComm n/a ISCCOMM RT PC DIAGS STARTED.
2 DiagStupMgr n/a DIAG_STUP_MGR: Startup diagnostics device driver
started -
If one or more startup tests fail, a log entry message will be created in the system event
log, e.g.:
10 IscComm n/a ISCCOMM: RT PC ver. failure RT PC DID NOT REBOOT
If there is a change in the HW configuration, e.g. a QDP board is removed from the system,
the startup diagnostics will recognize this and will also write it to the system event log, e.g.:
10 DiagStupMgr n/a DIAG_STUP_MGR Bus 9, Dev 1, Fun 0. PCI
Configuration register change from one boot to the next
How is a failing startup diagnostics test indicated in the user Interface?

Whenever one of the startup diagnostics tests fail, the message “Possible HW failure.
Please call Service” will be permanently displayed in the ACQ message line of the control
room monitor. This message cannot be switched away, it will stay unless a successful boot
up (all startup test passed) takes place.
How to Open the System Log

The system event log is part of the event log accessible via <Options> <Local Service>
<Event Log>. To view the startup diagnostic messages, the following settings have to be
made in the event log:
• Domain: System
• Severity: All
• NT Messages: Must be selected
Disabling the Startup Diagnostics 0
In some cases it may be necessary to disable the startup diagnostics. This is possible only
via the Windows Registry.
1. Open <Options> <Local Service> <Utilities> <Escape to OS> . Type the command
“regedit”into the Parameters box.
¹ The Registry Editor should open up.
2. Open the following registry path: < HKey_Local_Machine\System\CurrentCon-
trolSet\Services\DiagStupMgr\Parameters>
¹ A row of parameters is displayed. Either the complete startup diagnostics or sin-
gle tests can be disabled

07.07 CS PS AX IR/C
66 Diagnostics
3. Set value from 1 = ENABLED to 0 = DISABLED for the startup diagnostics test that is to
be disabled. See the table below for specific information:
Registry Parameter Enables / Disables:

Diag1kdRunNum 1KD Board Startup Diagnostics
DiagAaqRunNum AAQ Board Startup Diagnostics
DiagCopraRunNum COPRA Board Startup Diagnostics
DiagIscCommRunNum PCI - PCI Startup Diagnostics
DiagQdpDamRunNum QDP - DAM Startup Diagnostics
DiagSdramRunNum SD RAM Test on IMPAC
DiagStupEnable The entire startup diagnostics (all Tests)

07.07 CS PS AX IR/C
Diagnostics 67
Factory Diagnostics 5.3
As the name implies, factory diagnostics were originally developed to use in the factory test
bay. The diagnostic tests available under factory diagnostics are the same as the tests
which run from the <Hardware Test> <Image System> section located under <Local Ser-
vice> <Test Tools>. The Factory Diagnostics have a different user interface (Windows
instead of HTML). Board subtests can be started separately. The Factory Diagnostics can
be started from an icon directly on the Windows Desktop. This could be useful if the appli-
cation SW cannot be started.
The Factory Diagnostics should be used in the field if:
• The CSE is on site.
• The image drives in the disk array have to be formatted.
• The system does not boot into the Application menu.
Prerequisites to Run the Factory Diagnostic Tests 0
Most parts of the diagnostic programs (except some “Host stand-alone” tests) are located
on the system disk of the BSR RT PC and executed from there via the diagnostic user inter-
face which runs on the Host PC. The task split is as follows:
• Host PC CPU: Provides the graphical user interface (GUI), test control and reports
results
• BSR RT CPU: Performs the actual tests
To run the Factory Diagnostics, the following minimum system functions are
required:
• The Host PC must be able to boot to the Windows Desktop in Administrator mode.
• The BSR Realtime PC must be able to boot the VRTX operating system and the diag-
nostic program.
• Communication between the Host PC and the BSR RT PC must be fully established
and working.
• The “Board Map” must be successfully downloaded, see (Send Board Map: / p. 73)
This requires the following hardware to be fully functional:
• Host PC and BSR RT PC
• COM boards and COM DMA cables on the Host and BSR RT PC side.
• IMPAC-M and IMPAC-S (Biplane only)
• DMA board
NOTE If a connection to the BSR RT PC cannot be established, only

a limited number of tests located under “Host Stand-alone
Test” will run. In this case, the suspected HW (COM, IMPAC,
COM DMA cables) has to be changed.

07.07 CS PS AX IR/C
68 Diagnostics
How to Start the Factory Diagnostics 0
Factory Diagnostics can be started from the Windows Desktop. To get to the Desktop,
either the Application has to be stopped or the System has to be started in Administrator
mode.
Stopping the Application SW:

This should be used if the system is fully booted in the application mode
• See (Stop Application SW / p. 158).
Starting the System in Administrator Mode:

This should be used if the system is off and you wish to boot directly to the Factory Diag-
nostics menu.
• Switch on the system. During the boot phase, press and hold the <Shift key> until the
login window appears (appears on the Live monitor in the examination room).
• Enter “Administrator” as the user name. For the password, see the AX Password List in
the CS Knowledge Base.
¹ The system boots to the desktop.

07.07 CS PS AX IR/C
Diagnostics 69
Starting the Factory Diagnostics Program 0
• Double-click on the Factory Diagnostics icon (Fig. 19 / p. 69) located on the left side of
the desktop.
Fig. 19: Factory Diagnostics icon

¹ After a few seconds, the following menu opens up:
Fig. 20: Factory Diagnostics menu

Pos. 1 Selection Tree
Pos. 2 Results View
Pos. 3 Information View
Pos. 4 Overall Progress
Pos. 5 Function Buttons
Pos. 6 Operating Buttons
How to Start the Diagnostic Tests 0
The selection tree field contains the test groups:

• + Board Level Tests
• + System Level Tests
• + Interactive Tests

07.07 CS PS AX IR/C
70 Diagnostics
• + Interactive System Tests
Fig. 21: Selection Tree

These test groups (1/Fig. 21 / p. 70) can be opened by clicking on the + symbol. All test
groups contain several subtest groups (2/Fig. 21 / p. 70). Under them, the individual diag-
nostic tests (3/Fig. 21 / p. 70) become visible. Executable are complete test groups, several
test groups, subtests, single tests and groups of all combinations (selectable with CTRL &
mouse click). Under <Board Level Tests> <PlaneA(B)>, subtests are available for each
board. If one board is not recognized at all by the system, it is marked with a cross as shown
in (4/Fig. 21 / p. 70). The selected diagnostic test(s) can be executed by clicking on the
“Start Button” which is located in the Factory Diagnostics. For the Operating Button bar, see
(Fig. 22 / p. 71) below.

07.07 CS PS AX IR/C
Diagnostics 71
Fig. 22: Factory Diagnostics Operating Buttons

Pos. 1 Save test log to ...
Pos. 2 Start run of selected tests
Pos. 3 Pause test execution
Pos. 4 Cancel (Stop)
Pos. 5 Log ON / OFF to disk, when active test logs are saved to Desktop\Factory Logs\
Pos. 6 Loop Tests
Pos. 7 Help (not available)
Typically, the BSR RT PC performs a reset after the first test is started. The Information
View area (3/Fig. 20 / p. 69) should display “Attempting to establish communication with
RT, please wait ...”. If communication cannot be established, the diagnostics cannot be exe-
cuted and the communication problem has to be fixed first, see (Prerequisites to Run the
Factory Diagnostic Tests / p. 67).
Diagnostic tests can be executed to run once or in a loop mode. To run the tests in loop
mode, the “Loop Test” icon (6/Fig. 22 / p. 71) has to be activated. If the diagnostics are set
to loop mode, it is possible to configure how the system should behave if a problem is
detected. This can be set under <Option> <Failure Mode|>. The diagnostics offer the pos-
sibilities <Stop> , <Continue> and <Prompt user>.
Which test should be executed when? 0
Depending on the particular problem, different diagnostic tests can be executed. It is rec-
ommended to start with the test group “Board Level Test”. The meaning of the different
tests groups is as follows:
Board Level Tests:
• Should always be executed first, verifies Host, BSR RT PC, IPM (IPS) and all boards
are plugged into the IPM (IPS).
• Supplies a test and subtest for each board or module, which can be executed in recycle
(loop test) mode.
System Level Tests:
• Should be executed if the problem cannot be identified by the “Board Level Test”.
• Simulates a real ACQ mode. The system test uses a 1024x1024x12 image pattern and
transfers it with a transfer speed of 30 F/s through the different IMPAC boards using the
IPM (IPS) board and IMPAC SD-RAM. After the test is completed, the image pattern is
verified against a “golden pattern” which resides on the BSR RT PC HD.
• Provides subtests with different board combinations and selectable ACQ modes.
Interactive Test:
• Consists of a list of tests which requires interaction from the user.
• Contains the routine to format the image drives in the disk array.

07.07 CS PS AX IR/C
72 Diagnostics
• Contains some tests which can be executed only at the factory (Simulator required).
Interactive System Tests:
• Consists of a subset of ACQ and display tests.
• Compared to the “System Level Tests”, the test image pattern is not automatically veri-
fied but has to be visually checked on the monitor by the user.
Display of the Diagnostic Test Results 0
The section “Result View” (2/Fig. 20 / p. 69) displays the test results of the sub tests.
Fig. 23: Test Results

All passed tests are marked with a smiling face symbol (1/Fig. 23 / p. 72), all failed tests
are marked with an “X” (2/Fig. 23 / p. 72). Test results can be opened with a double-click.
A suggestion of which FRU (Field Replacable Unit) should be replaced is given in a sepa-
rate pop-up window when any of the failed tests is double-clicked.
Fig. 24: FRU suggestion
Extended Factory Diagnostic Functions 0
The Factory Diagnostics menu contains a few further helpful functions (5/Fig. 22 / p. 71)
which can be used.

07.07 CS PS AX IR/C
Diagnostics 73
Fig. 25: Factory Diagnostics Function Buttons
Reset RT:
• The Host PC resets the BSR RT PC via the reset cable connected to the RT mother-
board.
Send Board Map:

• The Host PC sends the Board Map to the BSR RT PC. The Board Map contains of infor-
mation from the Host PC PCI scan and the image system configuration file. Without a
downloaded Board Map, the BSR RT PC will not finish the bootup, see (Checking the
Bootup Trace / p. 82).
Display Board Map:

• Displays the Board Map. With this function, the Board Map information is displayed.
The following should be present:
- Board name of the installed boards (derived from the image system configuration file)
- Slot Number, Vendor ID, Device ID (obtained from the PCI scan)
Fig. 26: Results of Display Board Map

• The Board Map display can be used as service tool to find out if all installed boards are
recognized by the SW
Check RT Version:
• Displays the currently installed SW version of the BSR RT PC in the information view
(3/Fig. 20 / p. 69).
Download to RT:
• Downloads the RT software from the Host to the BSR RT PC. The same function is
available via <Local Service> <Configuration> <SW Manager>.
Factory Diagnostic Log Files 0
Each diagnostic session creates a log file, when the “Log to Disk” is set to on
(5/Fig. 22 / p. 71). These log files are stored to the folder “Factory Logs” which is available
on the desktop.

07.07 CS PS AX IR/C
74 Diagnostics
How to Close the Factory Diagnostic Program 0
After the diagnostic tests are finished, the system must be powered down using the shut-
down function from the operating system. This is necessary to reset all functions so they
are ready for application.
NOTE The system should always be reset after finishing diagnos-

tics and before running applications.
Known Problems 0

Exceptions for some Host The BSR RT PC is not ready or cannot be reached by the
stand-alone tests, Factory Host.
Diagnostics will not run, Perform the following steps to narrow down the problem:
resetting the BSR RT PC will
not work. • Connect a Service PC to the COM2 port of the BSR
RT PC and check how far the BSR RT PC boots, see
(BSR RT PC Developer Menu / p. 82).
When running the “1K Dis- The system is in bypass mode when the diagnostics are
play Module Live 1 Exam” active. Therefore the Live exam room monitor shows the
test, located under “Interac- bypass image from the DIPP and not the image from the
tive Tests”, no image is dis- image system.
played on the Live exam Perform the following steps to get the image displayed:
room monitor.
• Temporarily disconnect the video cable connected to
X10 on the VSD board.
• Disconnect the video cable from X40 and connect it to
X10
¹ The expected diagnostic images are now dis-
played on the control room Live monitor.
• Reconnect the video cables to their original positions
when the test is finished.
Formatting the Image Drives 0
The drives in the disk array can be formatted either via the interactive tests of the factory
diagnostics or through the Symbios Bios, see (Formatting the Image Drives / p. 108). With
the format utility from the factory diagnostics, all connected drives are formatted together
(simultaneously).

07.07 CS PS AX IR/C
Diagnostics 75
CAUTION Reformatting of the image drives will erase all patient data on
the disk array.
¹ Reformatting should be done only if all data is saved.
To perform the format via the Factory Diagnostics menu, proceed as follows:
1. Stop the application SW, see (Stopping the Application SW: / p. 68)
2. Start the Factory Diagnostics menu, see (Starting the Factory Diagnostics
Program / p. 69).
3. Select <Interactive Tests> <SCSI Disk Controller> <Drive(s) Format>.
¹ Ignore the incorrectly displayed time duration of 02:46:40 h.
4. Confirm the message “Formatting will erase all image data, Continue” with <True>.
Fig. 27: Formatting drives

¹ All drives in the disk array will now be formatted, which takes about 27 minutes.
¹ The database (folder D:\Database) in the Host PC will be automatically purged.
¹ The when the format is finished, a passed message appears in the Factory Diag-
nostics menu.
Fig. 28: Drive Format menu

07.07 CS PS AX IR/C
76 Diagnostics
Recreating the Security DB Folder (required for VB.. systems only)

These steps are required to recreate the db security folder, which is deleted during the for-
mat. Without this folder, no patient can be registered.
1. Open a CMD tool box as follows:
- Open the “Run” dialog by pressing the Windows key+ R key simultaneously
- Type the command “ cmd ” into the input field and click on <OK>.
¹ The CMD tool box opens.
2. Type the command “create_securitydb Install d:\Database“ into the CMD
tool box and press <Return>
¹ The db security folder is created under D:\Database.
Final Checks
1. Start the application SW, see (Start Application SW / p. 158).

¹ The boot to application takes longer (Syngo count is extended) as the database
has to be recreated in the background
2. Open the Patient Browser.
¹ No patients should be available except the emergency patient.
¹ The free disk indicator should display 100%.

07.07 CS PS AX IR/C
Diagnostics 77
Hardware Tests 5.4
The hardware tests selectable via Test Tools in the Service UI are the same as the diag-
nostic tests selectable under Factory Diagnostics. The test groups are arranged in the
same way.
The following is different from Factory Diagnostics:
• The Hardware Test User Interface is in HTML.
• Hardware Tests can (must) be started with the Application fully running.
• Most of the Hardware Tests can be run via Remote Diagnostics.
• Single subtests cannot be selected for execution in the Hardware Diagnostics.
Prerequisites for running the Hardware Tests 0
The prerequisites to start the Hardware Tests are the same as the prerequisites applicable
for starting the Factory Diagnostics, see (Prerequisites to Run the Factory Diagnostic
Tests / p. 67).
In addition to these prerequisites, the following has to be observed:
• The Artis Application SW must be almost fully up and running to start the Hardware
Tests. If the image system cannot connect to the AXCS network communication, the
Hardware Tests will not start and the following message appears when the first test is
started:
Fig. 29: HW Tests, test not possible alert

¹ If this is the case, an attempt should be made to stop the application and run the
Factory Diagnostics, see (Factory Diagnostics / p. 67).

07.07 CS PS AX IR/C
78 Diagnostics
How to Start the Hardware Tests 0
Selection of the Tests
Fig. 30: HW Test menu

Hardware Tests for the image system are selectable via <Options> <Local Service> <Test
Tools> <Hardware Tests> <Imaging System>. The following menu appears:
The Hardware Test menu consists of 3 sections:
• Settings for the repeat function and self-defined tests can be set on the section
(1/Fig. 30 / p. 78). This section also shows the run time messages of active tests.
• The component that is to be tested can be selected in the section (2/Fig. 30 / p. 78). A
tick in “Select all” will select all available tests for a component.
• The diagnostic subtests of the component (FRU Tests) selected in section 2 are dis-
played and are selectable in the section (3/Fig. 30 / p. 78).
Starting the Tests

The selected diagnostic tests can be started with a mouse click on the <GO> symbol in the
action bar. Once activated, the following confirmation checkbox that also displays the dura-
tion of the selected tests appears:
Fig. 31: HW Tests, Confirm checkbox

Clicking on <OK> starts the diagnostic test. While the test is running, run time messages
and test results (2/Fig. 32 / p. 79) are displayed in section 1 (1/Fig. 30 / p. 78).

07.07 CS PS AX IR/C
Diagnostics 79
Fig. 32: HW Tests Progress indication
Which tests should be executed and when 0
Basically, the same definition is valid for the Hardware Tests as for the Factory Diagnostics,
since the tests performed are the same, see (Which test should be executed
when? / p. 71).
The following differences from the Factory Diagnostics are present:
• The FRU tests start with the functions “Image System Realtime reset” and “Display
Image System Board Map”. For an explanation, see (Extended Factory Diagnostic
Functions / p. 72).
• The “Board Level Tests” headline is not present, but the “Board Level Tests” them-
selves, starting with the “Host Stand-alone” test, are selectable in the same way as for
the Factory Diagnostics.
Display of the Hardware Test Results 0
HW Test results are displayed in section 1 (1/Fig. 30 / p. 78) while the tests are running.
Test results logs are stored to the Host PC system drive and can be reviewed via <Local
Service> <Reports> <Log Files> <Hardware Tests>, see (Fig. 33 / p. 80). If tests are failed,
the test log file should contain an indication about which FRU should be replaced.

07.07 CS PS AX IR/C
80 Diagnostics
Fig. 33: Hardware test results
Extended Hardware Test Functions 0
The Hardware Test menu contains a few more options:

Repeat Mode:
• Can be activated by a mouse click on the <Repeat> button located in the Action Bar.
• Runs selected tests in repeat mode according to the setting in the menu below, see
(Fig. 34 / p. 80).
Fig. 34: Hardware Tests Repeat Mode

Self-Defined:
• Offers the possibility to combine several tests in a self-defined “package”.
• To create a self-defined package, proceed as follows:
- Select the desired FRU tests.
- Click on the <Save> button located in the Action Bar.
- Enter a name for the self-defined test.

07.07 CS PS AX IR/C
Diagnostics 81
- Click on the <Save> button again to store the self-defined test under this name.
• Once generated, the self-defined test can be invoked in the self-defined pull-down box.
Problem-oriented:
• Was intended to provide predefined tests created at the factory. Is not available at this
time.
How to close the Hardware Test menu 0
After the diagnostic tests are finished, the system must be powered down using the shut-
down function from the operating system. This is necessary to reset all functions so they
are ready for application.


07.07 CS PS AX IR/C
82 Diagnostics
BSR RT PC Developer Menu 5.5
The developer menu is a tool which was intended as a service tool for the Engineering
Department. A few functions from this tool are also useful for troubleshooting in the field.
The developer menu is mainly used to monitor the bootup trace messages of the BSR RT
PC and the IMPAC hardware. Since there is no monitor graphics card in the BSR RT PC,
the terminal screen output is redirected to the COM 2 port of the BSR RT PC. It can be
viewed there using a Service PC.
To display the terminal output, the following settings have to be made:
• Connect a Service PC to COM 2 of the BSR RT PC, see (Connection of the Service
PC / p. 146).
• Enable bootup trace on the IMPAC board, see (Enabling the Developer Menu / p. 146)
• If required, download the TeraTerm terminal program from the Intranet and is set up,
see (Terminal Emulation Program / p. 148)
• Start the Terminal Emulation program, see (Starting the Terminal Emulation
Program / p. 147)
Checking the Bootup Trace 0
When the service switches on the IMPAC are set to the service position, trace messages
are generated during bootup of the BSR RT PC for the hardware initialized in the BSR RT
PC, IMPAC HW and Disk Array and are displayed on the Service PC. If the bootup does
not complete, the bootup trace will be either stopped, interrupted by a fatal error message
or some parts of the trace will be missing. If this is the case, the bootup trace should be
compared to the traces in figures below. Dependent on the SW/HW version different traces
are available, please see either trace (BSR RT PC bootup trace with SW VA42/60, VB11/23
(QDP/DAM, PATEX 3070 BSR RT PC HW installed) / p. 83) or (BSR RT PC bootup trace
with SW VB22/23/30/31 (AAQ-COPRA HW, Raptor ATX Mb) / p. 88).
NOTE Attached bootup traces are just examples. They may differ
dependent on the installed HW. Systems without all HW
options installed will show fewer trace messages. Please
select the correct trace to compare.

07.07 CS PS AX IR/C
Diagnostics 83
BSR RT PC bootup trace with SW VA42/60, VB11/23 (QDP/DAM, PATEX 3070 BSR RT
PC HW installed)
Fig. 35: BSR RT PC bootup trace 1

07.07 CS PS AX IR/C
84 Diagnostics

07.07 CS PS AX IR/C
Diagnostics 85

07.07 CS PS AX IR/C
86 Diagnostics
NOTE For location of the disk drives, see (How to identify the image
drives / p. 110).

07.07 CS PS AX IR/C
Diagnostics 87

07.07 CS PS AX IR/C
88 Diagnostics
BSR RT PC bootup trace with SW VB22/23/30/31 (AAQ-COPRA HW, Raptor ATX Mb)
Fig. 40: VB30 boot trace, part 1

07.07 CS PS AX IR/C
Diagnostics 89

07.07 CS PS AX IR/C
90 Diagnostics

07.07 CS PS AX IR/C
Diagnostics 91
Extended Developer Mode Functions 0
IMPAC Diagnostic Test

A limited number of tests can be run from the Developer menu. Running these tests would
make sense only if a communication problem between the Host PC and the BSR RT PC is
present and the Factory or Hardware Diagnostic tests cannot be performed. Then the
IMPAC tests could be performed to narrow down the problem.
Start the IMPAC Diag. test as follows:
• Type <O> for “O-IMPAC Diags” in the Developer menu.
¹ The menu below opens up.

07.07 CS PS AX IR/C
92 Diagnostics
Fig. 44: IMPAC Diagnostics

The following available subtests are executable:
• <A> Com DMA Test
¹ Tests communication with the COM board, which is plugged into the BSR RT PC.
• <I> NTB (21554) Test
¹ Tests communication with the Non-Transparent Bridge chip, which resides on the
IMPAC board.
• <J> NTB PRB Test
¹ Tests communication with the Non-Transparent Bridge Parallel Rom Bus on the
IMPAC.
The following available subtests are executable only if the Board Map is down-
loaded by the Host, see (Send Board Map: / p. 73)
• <C> IMPAC Bridge Test
¹ Tests the access to the IMPAC Bridge chips
• <Q> RAM IF Chip Diag, <R> RAM Access Test, <S> RAM Address Test, <T> Ram
Walk Bit Test
¹ These tests check the SD-RAM on the IMPAC board.
NOTE Tests “<S> RAM Address Test” and “<T> RAM Walk Bit Test”
take quite a long time (up to 1 hr.).
Test Performance and Results

• Start the test by entering the appropriate letter.
• When prompted, select the plane you would like to test. [0]=Plane A, [1]=Plane B
• Press <Return>.
¹ The test starts, test results are displayed in the window, see (Fig. 44 / p. 92).

07.07 CS PS AX IR/C
Diagnostics 93
How to close the Developer Menu 0
• Set the service switches back to the normal position (all to the left), see
(Fig. 84 / p. 147).
• Reboot the system


07.07 CS PS AX IR/C
94 Diagnostics
Network Adapter Diagnostics (Host 2 Module only) 5.6
If there is a network problem, the function of the network adapters located on the Host 2
module motherboard (Motorola PATX 5000 Mb) can be checked with the built-in network
adapter diagnostics.
NOTE The Host 3 Module (Intel SE 7210TP1-E Mb) does not supply
a network adapter diagnostics.
How to start the Network Diagnostics 0
• Open <Local Service> <Utilities> <Escape to OS>. Under command, select the “NT
command interpreter”.
Fig. 45: Start network

• Enter the command “control ncpa.cpl” into the Parameters box and click on <GO>.
¹ The Network menu opens up:
Fig. 46: Network adapter selection

07.07 CS PS AX IR/C
Diagnostics 95
• Select the adapter you want to test and click on <Properties ...>
¹ The following menu opens up:
Fig. 47: Network activity indication

• In this window, the adapter setting for Link Speed and Duplex Mode can be checked.
The activity of the network adapter is also displayed.
• Select the <Diagnostics> tab card.
¹ The Network Adapter Diagnostics menu opens up:
Fig. 48: Network adapter diagnostics

07.07 CS PS AX IR/C
96 Diagnostics
Running the Network Adapter Test 0
NOTE Since the network adapter test will interrupt active network
transfers, it should never be run while the system is in use by
the customer.
The offered Network Adapter test can be selected via the checkboxes and started with
<Run Tests>. The duration of the tests is only a few minutes. The test results will be indi-
cated with Pass/Fail.
NOTE The “Cable Test” will pass only if the system is connected to
the network. Therefore a network cable must be connected
between the network adaptor outputs at the BSR Host and
network switch (AXCS Hub, switch) before running this test.

07.07 CS PS AX IR/C
BIOS Functions 97
6-
General Remarks
6BIOS Functions
The following BIOS functions are available in the image system:
Type of BIOS Located at Activated by Purpose

Host BIOS, see Host Mother- F2 Setting of the Host motherboard
(Host BIOS / p. 98) board options, boot device priority, reset
configuration.
For Adaptec BIOS, Host 2/3 Module CTRL+A Setting of the Host system disk
see (Adaptec Motherboard, (Motorola PATX 5000 MB only),
BIOS / p. 106) (see *1) CD-ROM and CD-R drives.
For Symbios BIOS, (SCSI Host CTRL+C Setting of the SHA board and
see (Symbios Adapter) SHA Image drives in the disk array.
BIOS / p. 108) Board
For the BSR RT PC BSR RT PC F2 (if Motorola 3070 MB) Setting of the BSR RT PC Moth-
BIOS, see (BIOS of Motherboard DEL (if Raptor ATX MB) erboard options
the BSR RT
PC / p. 111) Note: A Keyboard must
be connected to the BSR
RT PC)
*1 = The Adaptec BIOS is not available on Host 3 modules with P/N 10183516. A SCSI Adapter
does not exist any longer on this host module.

07.07 CS PS AX IR/C
98 BIOS Functions
Host BIOS 6.1
Depending on the Host module, the BIOS functions are different. Please use the descrip-
tion according to the present Host Module.
Entering the Host BIOS 0
To enter the Host BIOS, the following has to be done:

• Switch on, or restart the system.
With Host 2 Module (Motorola PATX5000 Mb) With Host 3 Module (Intel SE7210TP1-E Mb)
• Press the <F2> key while the Siemens Medi- • Press the <F2> key while the first part of the
cal Solutions logo is displayed on the screen progress bar above the Siemens Medical Solu-
¹ Entering setup ...” will be displayed tions logo is displayed on the screen.
¹ After initializing the Adaptec and Sym- ¹ After initializing the Adaptec and Sym-
bios devices, the system will boot into bios devices, the system will boot into the
the BIOS and ask for the password BIOS and ask for the password
• Enter the BIOS password (see PW list in CS Knowledge Base) and press <Enter>.
¹ The BIOS main menu will be displayed.
CAUTION It is strongly recommended that you alter only the settings

that are explained in the following pages.
¹ Setting items on this menu and its submenus to incor-
rect values may cause your system to malfunction.
¹ Incorrect settings can be set back to default with the F9
key.
BIOS Functions with Host 2 Module (Motorola PATX5000 MB) 0
In this section, only those BIOS functions which are necessary for service purposes are
explained.
Advanced Menu
When you select the Advanced menu, the following screen appears.

07.07 CS PS AX IR/C
BIOS Functions 99
Fig. 49: Host BIOS Advanced menu

In the Advanced menu the function, “Reset Configuration Data” has to be carried out if the
HW configuration of the system has changed. This is noted in the manuals when required,
for information see (Resetting the Host 2 Module Motherboard BIOS when Changing the
Board Configuration / p. 154).
Purpose of Reset Configuration Data

The Extended System Configuration Data (ESCD) area stores information about the
devices in the system. In most cases, when you add or remove devices, the BIOS automat-
ically updates the ESCD based on the configuration detected during POST (Power Up Self
Test). Setting the Reset Configuration Data feature to “Yes” clears the ESCD after you exit
Setup. During the next bootup, the ESCD is updated and Reset Configuration Data auto-
matically returns to “No.”
Boot Menu
When you select the Boot menu, the following screen appears.

07.07 CS PS AX IR/C
100 BIOS Functions
Fig. 50: Host BIOS Boot menu
Fig. 51: Host BIOS Boot Device Priority

The boot device priority is selectable in the Boot menu. Changing the priority may be
required if the system is to boot from other devices such as the hard drive (e.g. from CD
during SW download). The Boot menu can also be used to check whether the system
drives are correctly configured. If the Scan ID is incorrectly set in the Symbios BIOS, there
will be more than one hard drive visible in the Boot menu.
Security Menu
When you select the Security menu, the following screen appears:

07.07 CS PS AX IR/C
BIOS Functions 101
Fig. 52: Host BIOS Security menu

The Security menu is used to set the supervisor password.
BIOS Functions with Host 3 Module (Intel SE7210TP1-E MB) 0
In this section, only those BIOS functions which are necessary for service purposes are
explained. As a main difference compared to the Host 2 Module, the Host 3 Module has a
PCI Auto Configuration, which means the function “Reset Configuration” is not available
and required on the Host 3 Module BIOS.
Advanced Menu
When you select the Advanced menu, the following screen appears:
Fig. 53: Host 3 module advanced menu

The Advanced menu is mainly used to reconfigure the Floppy Configuration. Because of
the auto configuration function in the Host 3 Module, the floppy is set to disabled every time
the Host is booted without the floppy drive connected. This happens mostly after the BSR
RT PC has been downloaded using the floppy method. The following steps need to be
done to configure the floppy drive again:
• Select Advanced on the menu bar, then Floppy Configuration.
• Set “Floppy A” to <1.44MB>
• Set “Onboard Floppy Controller” to <Enable>
• Press <ESC> and save settings with <F10>.

07.07 CS PS AX IR/C
102 BIOS Functions
Boot Menu
When you select the Boot menu, the following screen appears:
Fig. 54: Host 3 module boot menu

The Boot menu is mainly used to set the Quick Boot (enabled by default) and the Boot
Device Priority during SW Installation. See the SW Installation Instruction for how to do this.
Security Menu
When you select the Security menu, the following screen appears:
Fig. 55: Host 3 module security menu

The Security Menu is used to set the Supervisor Password (BIOS Password). This may be
necessary after the C-Mos was cleared or the C-Mos battery was replaced.
Selecting the Boot Device without Entering the BIOS 0
Instead of launching the OS directly, the BIOS provides the possibility to select the Boot
Device without entering the boot device priority menu in the BIOS.
• Press the <Esc> key while the Siemens Med- • Press the <Esc> key 2 times while the first part
ical Solutions logo is displayed on the screen of the progress bar above the Siemens Medical
¹ The Siemens Medical logo disappears. Solutions logo is displayed on the screen.
¹ After initializing the Adaptec and Sym- ¹ The Siemens Medical logo disappears.
bios devices, the system displays a boot ¹ After initializing the Adaptec and Sym-
device selection boot menu, similar to bios devices, the system displays the
the one shown below. boot menu, similar to the one shown
below.
Fig. 56: Boot device selection

07.07 CS PS AX IR/C
BIOS Functions 103
This “Boot First” menu displays the boot sequence specified in the Setup Utility’s Boot
menu and allows you to:
• Override the existing boot sequence (for this boot only) by selecting another boot
device. (If the specified device does not load the operating system, the BIOS reverts to
the previous boot sequence.)
• Enter Setup.
• Press <Esc> to continue with the existing boot sequence.
Common Host BIOS Functions 0
The following common functions are available in the BIOS of the Host 2 Module BIOS as
well as on the Host 3 Module.
Setup of Default BIOS

• <F9> Setup Defaults. This key is used to reset all BIOS configurations to default. It
ensures that the system will run with default values. <F9> is also working on the Host 3
Module BIOS, even if it is not displayed in the BIOS menu.
Save and Exit

• <F10> Save and Exit, is used to save the configured setup and to exit the BIOS.
Clearing the CMOS (BIOS Password) on the Host Motherboard 0
In some cases it may be required to clear the CMOS RAM on the Host motherboard to set
the BIOS back to the default. The work steps to clear the CMOS are different for the 2 dif-
ferent host modules, see either (Host 2 Module (Motorola PATX5000 Mb) / p. 104) or (Host
3 Module (Intel SE7210TP1-E Mb) / p. 105).

07.07 CS PS AX IR/C
104 BIOS Functions
Host 2 Module (Motorola PATX5000 Mb)
Fig. 57: Motorola PATX5000 MB layout

Proceed as follows to clear the CMOS on a Host 2 module:
E 1. Switch off the power
2. Move the jumper on J34 (3/Fig. 57 / p. 104) from Pins 2-3 to Pins 1-2 to disable the
CMOS Restore from Backup function.
3. Remove jumper J9 (2/Fig. 57 / p. 104) for a minimum of 30 seconds. After this time,
reinstall the jumper.
4. Boot up the system, press “F2” while the Siemens Medical Solution Logo is displayed
on the screen.
¹ The system should boot into the BIOS screen without prompting for a password.
5. Select System Date and System Time in the Main menu and set the correct date and
time. The format is “HH:MM:SS “ for time and “MM/DD/YYYY“ for date.
6. Select the Security menu and enter the supervisor password (see AX Password List in
the Knowledge Base).
7. Power down the system and move the jumper on J34 (3/Fig. 57 / p. 104) from Pins 1-2
to Pins 3-4.

07.07 CS PS AX IR/C
BIOS Functions 105
Host 3 Module (Intel SE7210TP1-E Mb)
Fig. 58: Host 3 Module MB Layout (Intel SE7210TP1-E)

Proceed as follows to clear the CMOS on a Host 2 module:
E 1. Switch off the power
2. Set jumper J1D1, see (Fig. 58 / p. 105) to position 2-3, power the system on, and wait
until the system begins beeping.
3. Switch off the power, set jumper back to position 1-2.
4. Boot up the system. Press the <F2> key while the first part of the progress bar above
the Siemens Medical Solutions logo is displayed on the screen
¹ The system should boot into the BIOS screen without prompting for a password.
5. Select System Date and System Time in the Main menu and set the correct date and
time. The format is “HH:MM:SS “ for time and “MM/DD/YYYY“ for date.
6. Select the Security menu and enter the supervisor password (see AX Password List in
the Knowledge Base).
The BIOS of the Intel Motherboard also provides the feature to clear only the BIOS pass-
word. Proceed as follows if you want to do this:
1. Switch off the power
2. Set jumper J1D1, see (Fig. 58 / p. 105) to position 6-7 and power the system on.
3. Switch off the power, set jumper back to position 5-6.
4. Set the BIOS password again (see above description).

07.07 CS PS AX IR/C
106 BIOS Functions
Adaptec BIOS 6.2
The Adaptec BIOS controls the Host system drive and CD-R, CD-ROM drives. In the
Adaptec BIOS, the Host 2 Module SCSI system drive can be checked (verified) and format-
ted. The presence of the SCSI CD-R and CD-ROM drives can be checked, too. The
Adaptec BIOS is not available on Host 3 modules with P/N 10183516. An SCSI Adapter no
longer exists on this host module.
Entering the Adaptec BIOS 0
To enter the Adaptec BIOS, the following has to be done:
• Switch on the system. Wait until the Siemens • Switch on the system, press the <Esc> key
Medical Solution Logo goes away. while the first part of the progress bar above the
Siemens Medical Solutions logo is displayed
on the screen.
¹ The Siemens Medical logo disappears.
• Press the CTRL+A keys when prompted on the screen.

¹ The Adaptec BIOS screen should appear on the screen.

Formatting the System Drive in the Host 2 Module 0
NOTE The system drive (SATA Drive) in the Host 3 Module cannot
be formatted
NOTICE Reformatting the Host 2 module system drive will erase all
data (also patient data) on the drive.
¹ Reformatting should be done only if all data are saved.
To start the format, the following has do be done:

• Under [Bus:Channel:Device], select [12:03:A] (channel A) and press <Enter>
¹ The next screen will be displayed.
• Select [SCSI Disk Utilities] and press <Enter>.
¹ The system scans the SCSI bus for devices and switches to the next screen.
• Select [SCSI ID 0 SEAGATE ST 318404LW] and press <Enter>.
¹ The next screen will be displayed.

07.07 CS PS AX IR/C
BIOS Functions 107
• Select [Format Disk] and press <Enter>.

¹ [Format Disk] [Yes] [No] will be displayed.
• Select [Yes] to start the low level format.
¹ The formatting procedure takes about 20 minutes.
NOTE Use CTRL+ESC to go back one level.
Verification of the Host 2 Module System Drive 0
Disk verification scans the drive for media defects. It can be used to check the SCSI system
drive in the Host 2 Module.
NOTE The system drive (SATA Drive) in the Host 3 Module cannot
be verified.
To select disk verification, the following has to be done:

• Perform steps described under (Formatting the System Drive in the Host 2
Module / p. 106). Instead of selecting [Format Disk], select [Verify Disk Media] and
press <Enter>.
¹ [Verify Disk] [Yes] [No] will be displayed.
• Select [Yes] to start the verification.
¹ The verification procedure takes about 12 minutes. <ESC> can be used to abort
the disk verification.
NOTE If ESC does not work, use CTRL+ESC to abort or to go back

one level.

07.07 CS PS AX IR/C
108 BIOS Functions
Symbios BIOS 6.3
The Symbios BIOS is located on the SHA board and controls the image drives in the disk
array. The image drives can be checked (verified) and formatted in the Symbios BIOS.

Entering the Symbios BIOS 0
To enter the Symbios BIOS, the following has to be done:
• Switch on the system. Wait until the Siemens • Switch on the system, press the <Esc> key
Medical Solution Logo goes away. while the first part of the progress bar above the
Siemens Medical Solutions logo is displayed
on the screen.
¹ The Siemens Medical logo disappears.
• Wait until the Adaptec initialization is completed.

• Press the CTRL+C keys when prompted on the screen.
¹ The Symbios BIOS screen should appear on the screen. The first channel (Chan-
nel A) of the multifunction 53C896 SCSI card should be selected.
Formatting the Image Drives 0
The image drive(s) in the disk array can be formatted either in the Factory Diagnostics
menu, see (Formatting the Image Drives / p. 74) or through the Symbios BIOS. The
description below describes the format procedure via the Symbios BIOS.
NOTICE Reformatting the image drive(s) will erase all patient image
data on the drive.
¹ Reformatting should be done only if all data are saved.
To start the format, the following has do be done:

• Press the <Enter> key.
¹ The system will again scan for devices and return with <Device Properties>
selected.
• Press the <Enter> key.
¹ All connected (found) SCSI devices are listed by the SCSI ID in the first column of
the table.

07.07 CS PS AX IR/C
BIOS Functions 109
• Use the down arrow key to select the SEAGATE ST318404(6) drive you would like to
format, see (How to identify the image drives / p. 110) for the drive location.
• Use the right arrow key to move the cursor to the column marked with <Format> and
press <Enter>.
¹ A warning message appears on the screen.
• Press <Enter> to start the format.
¹ The format takes about 20 minutes.
If you would like to format another drive, select SCSI channel, drive(s) and proceed as
described above. In the Symbios BIOS, drives can only be formatted successively.

one level.
Verification of an Image Drive 0
Disk verification scans the drive for media defects. It can be used to check the drive.
To select disk verification, the following has to be done:
• Perform steps described under (Formatting the Image Drives / p. 108). Instead of
selecting <Format>, select <Verify> and press <Enter>.
• Select <Enter> again to start the verification.
¹ The verification procedure takes about 12 minutes. <ESC> can be used to abort
the disk verification.

one level.

07.07 CS PS AX IR/C
110 BIOS Functions
How to identify the image drives 0
Channel B
SCSI ID3
Channel A
SCSI ID2
SCSI ID1 SCSI ID3
SCSI ID0 SCSI ID2

SCSI ID1
SCSI ID0
Fig. 59: SCSI drive disk array location

07.07 CS PS AX IR/C
BIOS Functions 111
BIOS of the BSR RT PC 6.4
Depending on the BSR RT PC module, the BIOS functions are different. Please use the
description according to the present BSR RT PC Module.
Entering the BSR RT PC BIOS 0
To enter the BSR RT PC BIOS, the following has to be done:

• Connect a Service PC to the COM 2 port of the BSR RT PC using a 0-modem service
cable, P/N 99 00 440.
• Start the terminal emulation program on the Service PC, see (Starting the Terminal
Emulation Program / p. 147).
• Unplug the keyboard from the Host module and connect it to the BSR RT PC keyboard
connector.
• Open <Local Service> <Test Tools> <Hardware Tests> <Image System> and start the
“Imaging System Real-time reset” test.
With RT Module (Motorola PATX3070 Mb) With RT 2 Module (Raptor ATX MB)
• Press the “F2” key on the keyboard connected • Press the “DEL” key on the keyboard con-
to the BSR RT PC while the PC is booting nected to the BSR RT PC while the PC is boot-
¹ The BSR RT PC BIOS main menu will ing
be displayed on the Service PC screen. ¹ The BSR RT PC BIOS main menu will be
displayed on the Service PC screen.
Now the arrow keys from the connected keyboard can be used to navigate through the set-
tings. Only the BIOS menu in the BSR RT PC BIOS that may be used is the Boot menu to
set the boot device priority and the Quick boot, see (AXA4-100.841.13 / Changing the Boot
Device Priority in the BIOS).
Clearing the CMOS on the BSR RT PC Motherboard 0
In some cases, it may be required to clear the CMOS RAM on the BSR RT PC mother-
board. The work steps to clear the CMOS are different for the 2 different BSR RT PC mod-
ules.

07.07 CS PS AX IR/C
112 BIOS Functions
BSR RT PC Module (Motorola PATX3070 Mb)
Fig. 60: Motorola PATX3070 MB layout

Proceed as follows to clear the CMOS on the BSR RT PC Module:
• Switch off the power
• Move the jumper on J27 (1/Fig. 60 / p. 112) from pins 2-3 to pins 1-2 to disable the
CMOS-to-EEPROM backup
• Clear the CMOS by moving the jumper on J34 (2/Fig. 60 / p. 112) temporarily from pins
2-3 to pins 1-2. Wait for 30 seconds, return the jumper to pins 2-3.
• Power down the board once more. Return the jumper on J27 to pins 2-3 to re-enable
the CMOS-to-EEPROM backup.

07.07 CS PS AX IR/C
BIOS Functions 113
BSR RT PC 2 Module (Raptor ATX Mb)
Fig. 61: ATX Raptor MB layout

Proceed as follows to clear the CMOS on the BSR RT PC 2 Module:
• Switch off the power
• Move jumper JP5 (3/Fig. 61 / p. 113) from position 1-2 to position 2-3
• Turn the system on, wait about 1 minute, turn the system off.
• Move the J5 jumper back to position 1-2.

07.07 CS PS AX IR/C
114 Voltages and LEDs
7-
Voltage Description
7Voltages and LEDs
Voltages can be either measured on:

• the power supply (on systems with Type I power supply only)
• the POI/PCM board
• the IPM board, Host, BSR RT PC power connector
If the voltage is out of tolerance on systems with a Type I power supply, (Serial Nos.
<1491 SP, < 3099 BP), perform the adjustment per the adjustment procedure, see
(AXA4-100.842.02).
On systems with a Type II power supply(Serial Nos. >1490 SP, >3098 BP), a voltage
adjustment is not possible and not required.
The following table shows the Pins on the main power connector of the Host PC (the Host
3 Module has a 24-pin connector, but the upper 4 pins are not connected):
Pin Signal Color Pin Signal Color Pin location

1 +3.3VDC Orange 11 +3.3VDC Orange
2 +3.3VDC Orange 12 -12VDC Blue
3 COM Black 13 COM Black
4 +5VDC Red 14 PS_ON Green
6 +5VDC Red 16 COM Black
8 PWR_GOOD Gray 18 NC NC
9 NC NC 19 +5VDC Red
Fig. 62: Host ATX
10 +12VDC Yellow 20 +5VDC Red PS Plug/RT
PC
This chart shows the general wire color code which is used in the image system, unless
otherwise specified:
Color Signal Color Signal

ORG +3.3V, +/-0.06 V BRN 6.0V Standby, +/-0.2V
BLK COM GND BLU -12V, +/-0.24V
RED +5V, +/-0.1V GRN PS_ON
GRAY PW_OK YEL +12V, +/-0.24V

07.07 CS PS AX IR/C
Voltages and LEDs 115
LED Description 7.1
POI Board 0
POI Board LEDs and Meaning:
Fig. 63: POI LED display, all LEDs
LEDs on front Description

O / green Power on LED
A / green Disc access LED on Host PC system drive
B / green Disc access LED on disc array drives
LEDs on board Description

PD_UPS_OFF Power off signal to UPS
LAB POWER (12V Indicates 24V supply from the lab
Local)
HOST PWR SW Host PC power switch (relay contact closure)
HOST RESET Host PC reset switch (relay contact closure)
RT HD LED BSR RT PC hard drive access LED
RTIME RESET BSR RT PC reset switch (relay contact closure)

07.07 CS PS AX IR/C

+3.3V SUP +3.3V measured on POI (remote sensor line is used to assure
voltage)
HOST 5SVB 5V standby voltage for Host PC (on after stated machine starts)
+5V (LOCAL STDBY) 5V unswitched used by POI logic (always present when AC
applied); 5V on the board, 6V on the supply
TCOM Indicates over/under temp. condition occurred during this power
cycle (overtemp.> 40 deg. Celsius, undertemp.< 10 deg. Celsius)
HOST PS ON Request signal ’power supply ON’ from Host PC to POI
HOST PWR GOOD Host power good signal; all voltages must be o.k. and
IPM_FPGA_CONFIG must be loaded
IPM PWR GOOD IMPAC Master power good signal; all voltages must be o.k.
UPS +24V +24V supply from UPS
PS OVER TEMP IN Power supply over-temperature indicator
PS PWR FAIL IN Power failure indicator from power supply (loss of AC to power
supply); signal for Host PC and BSR RT PC to save BIOS set-
tings;
RT PWR LED LED indicating power to BSR RT PC
RTime_PWR_SW BSR RT PC power switch (relay contact closure)
-12V SUPPLY -12V measured on POI (remote sensor line is used to assure
voltage)
+5V SUPPLY +5V measured on POI (remote sensor line is used to assure volt-
age)
+12V SUPPLY +12V measured on POI (remote sensor line is used to assure
voltage)
RT 5SVB 5V standby voltage for BSR RT PC (on after stated machine
starts)
THigh Indicates over-temperature (actual temperature)
RT PS ON Request signal ’power supply ON’ from BSR RT PC to POI
RT PWR GOOD BSR RT PC power good signal; all voltages must be o.k.
PCM Board 0
PCM Board LEDs and Meaning:

07.07 CS PS AX IR/C
Fig. 64: PCM LED display, all LEDs

PD_UPS_OFF Power off signal to UPS
LAB 24 V Indicates 24V supply from the lab power distributor
HOST PWR SW Host PC power switch (relay contact closure)
HOST RESET Host PC reset switch (relay contact closure)
RT HD LED BSR RT PC hard drive access LED
RTIME RESET BSR RT PC reset switch (relay contact closure)
LOCAL +3.3V +3.3V is present
+5V (STDBY) Present when AC is on
TCOM Indicates over/under temp. condition occurred during this power
cycle (overtemp.> 40 deg. Celsius, undertemp.< 10 deg. Celsius)
PWR GOOD All voltages are o.k.
UPS +24V +24V supply from UPS
PS OVER TEMP IN Power supply over-temperature indicator
RT PWR SW BSR RT PC power switch (relay contact closure)
-12V -12V present
+5V SUP +5V present
+12V SUP +12V present

07.07 CS PS AX IR/C

FPGA_CFG FPGAs on IMPAC are successfully configured
THigh Indicates over-temperature (actual temperature)
RT PS ON Request signal ’power supply ON’ from BSR RT PC to PCM
Host 2 Module Motherboard (Motorola PATX 5000) 0
LED / color Description

DS1 / yellow +5V standby
DS2 / green ON, main supply from system present
OFF, in system off situation
QDP Board 0
Fig. 65: QDP board layout

DS1 / green 1.8V o.k.
DS2 / green 2.5V o.k.

07.07 CS PS AX IR/C
AAQ COPRA Board 0
Fig. 66: AAQ board layout
NOTE Description is only for the LEDs on the AAQ board. For
COPRA LEDs, see (AXA4-100.840.12 / COPRA Board, Status
of LEDs during Standby, Fluoro and ACQ.).

DS50 / green +5V o.k.
DS33 / green +3.3V o.k.
DS25 / green +2.5V o.k
ERR / red ACTIVE: When any of the following occurs and the Gigalink mod-
ule has been enabled to receive images: Protocol error, overflow,
or RXERROR asserted by the HDMP_1034 receiver chip.
INACTIVE: When the mode bit in the configuration register is writ-
ten with a one after a reset (when the Gigalink module is setup).
After reset / power up: Always off (even if the cable is disconnected
and reconnected) until the Gigalink module has been enabled to
receive images.
NOTE: If the LED goes on because of an error that occurred when
the Gigalink module was enabled to receive images, the LED will
go off when the cable is disconnected (link not ready) and go back
on when the cable is reconnected (link ready).

07.07 CS PS AX IR/C

RX / yellow ACTIVE: When a beginning transfer (BOT) is detected in the out-
going data stream.
INACTIVE: When the end of transfer (EOT) is detected in the out-
going data stream or when the Gigalink module is in reset.
After reset / power up: Always off.
RDY / yellow ACTIVE: Indicates a good connection link with the transmitter
board
GP1 / yellow General purpose test point LED. Currently blinks after download is
complete.
GP2 / yellow General purpose test point LED. Currently blinks with any LAD
(local address and data bus) access.
GP3 / yellow General purpose test point LED. Currently on when front bus go is
enabled.
GP4 / yellow General purpose test point LED. Currently unused.
FB / yellow Indicates that the front bus has asserted valid.
MEM / yellow Indicates LAD access of the memory
FIFO / yellow Indicates LAD access of the LADO or LADI FIFO.
REG / yellow Indicates LAD access or any register.
DMA0 ... DMA5 Indicates that DMA 0 to DMA 5 is active.
yellow
DAM Board 0
Fig. 67: DAM board layout

DS1 / green 2.5 V o.k.
DS2 / green 1.8 V o.k.

07.07 CS PS AX IR/C

RDY / yellow Ready LED indicates good Gigalink connection
IRX / yellow ON, when transfer is detected on Gigalink
OFF, when there is no data transfer on Gigalink
Blinking, when images are received
After reset / power up always OFF
ITX / yellow Toggles whenever the link is lost, useful for troubleshooting to
see if the link was lost for a very short time (which cannot be seen
on the RDY LED)
ERR / red ON, if receiving an invalid combination of data
OFF, after reset and if there is no error
1KD Board 0
Fig. 68: 1KD board layout

DS1 / red Configuration error
DS2 / yellow Configuration done
DS3 / yellow on 1KD1 ON, when busy with configuration
green on 1KD Blinking when system reset removed and PCI clock present
DS4 / green Power ON (3.3 V and/or 5 V)

07.07 CS PS AX IR/C
SHA Board 0
Fig. 69: SHA board layout
LED / color / function Description

CR1 / green / SCSI activity Indicates activity on channel A SCSI bus
CR2 / green / SCSI activity Indicates activity on channel B SCSI bus
CR3 / green / TERMPWR shorted Indicates when the termination power self-resetting
fuse has opened on channel A
CR4 / green / TERMPWR shorted Indicates when the termination power self-resetting
fuse has opened on channel B
CR5 / green / LVD Mode Indicates when channel A is operating with all LVD
SCSI devices
CR6 / green / LVD Mode Indicates when channel B is operating with all LVD
SCSI devices
CR7 / green / TERMPWR Good Indicates that the termination voltage on channel A is
above 3 V
CR8 / green / TERMPWR Good Indicates that the termination voltage on channel B is
above 3 V

07.07 CS PS AX IR/C
IPM Board 0
Fig. 70: IPM board layout

DS1- DS8 / red Status LEDs (for internal use only)
DS9 / green +12 V
DS10 / green +5 V
DS11 / green +3 V
D12 / green -12 V
V1 / yellow / T_HIGH ON, if temperature > 40 degrees centigrade
OFF, if temperature < 40 degrees centigrade

07.07 CS PS AX IR/C
IPS Board 0

D9 / green +12 V
D10 / green +5 V
D11 / green +3 V
D12 / green -12 V
VSD Board 0

DS1 / green +5VB (analog)
DS2 / green -5VA (analog)
DS3 / green +5VA (analog)
DS4 / green +5V digital
DS5 / green 24V
TPS Board 0

DS1 / red / T_HIGH ON, if temperature > 37 degrees centigrade
OFF, if temperature < 37 degrees centigrade
DS2 / red / T_COM ON, if temperature has exceeded 37 degrees centigrade
once. It will go OFF only if the system is switched off or the
temperature drops below 10 degrees centigrade;
OFF, if temperature was never > 37 degrees centigrade
CD-ROM (ULTRAPLEX 40max) 0

DISC / green Green when power is ON and disc is inserted
OFF if no disc is inserted
ON/BUSY / yellow Yellow when power is turned ON
Blinking when disc is inserted and being accessed
OFF when disc is inserted and not being accessed

07.07 CS PS AX IR/C
CD-R (Plextor PX-W4012TS) 0

DISC / green Green when power is ON and disc is in the drive
ON/READ / green Green when power is ON and no disc in the drive
WRITE/L / orange Orange when recording CD-R discs at 1X, 4X or 8X speed, or
low-speed CD-RW discs at 2X or 4X speed
WRITE/H / orange Orange when recording CD-R discs at 12X speed
Both WRITE H and WRITE L indicators are turned ON when
recording CD-RW discs at 4X, 8X or 10X speed with high-speed
CD-RW media
IDE DVD/CD-R (Plextor PX716 / PX760) 0

Lights up yellow Disc initializing, reading and ejecting
Lights up green During standby and when Proof Technology is operational
Lights up orange When writing CD-R discs (blink rate indicates speed).
SBE Board (in Host PC) 0

ACT / green LINK ACTIVE; visual indication that laser link units are communi-
cating and sending sync data over the fiber optic link; the laser
link will disconnect from SCSI bus when the link is not active
BSY / green BUS ACTIVE; visual indication of the BUSY signal on the SCSI
bus interface; LED indicates devices communicating on the SCSI
bus

07.07 CS PS AX IR/C
SBE Board (in RPAU) 0

POWER / green The power LED indicates that power is applied to the unit
LINK ACTIVE / yellow Visual indication that laser link units are communicating and
sending sync data over the fiber optic link; the laser link will dis-
connect from SCSI bus when the link is not active
BUS ACTIVE / yellow Visual indication of the BUSY signal on the SCSI bus interface;
LED indicates devices communicating on the SCSI bus
LINK ERROR / yellow Indicates that the integrity of the fiber optic link is below specifi-
cation and data transfer errors will occur if not corrected; the laser
link will disconnect from SCSI bus when a Link Error is detected.
LEX Module (in BSR) 0
Fig. 71: LEX module, overview of LEDs

(1/Fig. 71 / p. 126) LED is “ON” if the USB connection from the Host USB connector
/Green to the LEX USB connector is o.k.
LED is “OFF” if the USB connection is interrupted or if the link
between the LEX and REX module is open
(2/Fig. 71 / p. 126) / LED is “ON” if the CAT 5 Network Link between the LEX and the
Green REX module is o.k.
(3/Fig. 71 / p. 126) / LED is “ON” if power is supplied via the mouse connector.
Green

07.07 CS PS AX IR/C
REX Module (in RPAU2) 0
Fig. 72: REX module, overview of LEDs

(1/Fig. 72 / p. 127) / LED is “ON” if the USB connection from the REX USB connector
Green to the USB / IDE adaptor and DVD drive connector is o.k.,
(2/Fig. 72 / p. 127) / LED is “ON” if the CAT 5 Network link between the LEX and the
Red REX module is o.k.
(3/Fig. 72 / p. 127) / LED is “ON” if power is applied to the REX board.
Green

07.07 CS PS AX IR/C
128 Downgrade to the Minimum HW
8-
Minimizing Hardware
8Downgrade to the Minimum HW
Sometimes it is necessary to reduce the system to a minimum HW configuration in order

to locate a defective part. The measures described below can be performed for trouble-
shooting.
Stand-alone Host PC 0
The HW of the Host PC should be minimized to a stand-alone PC as follows, especially if

the monitor shows a black screen during the boot:
1. Unplug the COM board from the Host PC motherboard.

2. Remove one 1KD board from the IPM and put it into the PCI slot of the COM board pre-
viously removed.
3. Pull over the LEMO cable marked with J1 from the IMPAC side and connect it the out-
put J1 of the 1KD board now plugged into the Host PC, or use the supplied service
video cable (LEMO/BNC), which can be connected directly to the monitor
4. Switch ON the image system.
¹ The Host PC should now boot up and start the operating system and the applica-
tion SW. The boot will end in the error tab card, because of the missing IMPAC
hardware.
5. If no display is present, try another 1KD board to eliminate this board as a cause of the
problem.
If the Host PC does not boot at all, the Host PC (or the system drive) is possibly defective.
To determine this, perform the following checks:
• Check the power-up sequence, see (POI/PCM Board Power-up Sequence / p. 27).
• Check the motherboard with the Post Card Diagnostics, see (POST
• Enter the BIOS and set BIOS to default using the <F9> key (Setup of Default
BIOS / p. 103)
• Check system drive with the Adaptec BIOS, see (Verification of the Host 2 Module Sys-
tem Drive / p. 107). This works only in systems with the Host 2 module (SCSI system
drive).
Additional Information for the Host 3 Module (Intel SE7210TP1-E Mb)

The Host 3 module motherboard has a built-in onboard SVGA video controller. This video
controller is active (enabled) if the COM board is removed and if no 1KD board is plugged in
in its place. The integrated controller can be used to test the Host PC stand-alone function
as follows:
1. Unplug the COM board from the Host PC motherboard.
2. Connect a monitor (standard PC monitor with a 15-pole VGA connector) to the VGA
connector (labeled as Video) which is located on the connector panel of the host mod-
ule.

07.07 CS PS AX IR/C
Downgrade to the Minimum HW 129

¹ The Host PC should now boot up and start the operating system and the applica-
tion SW. A display is available on the connected monitor. The boot will end in the
error tab card, because of the missing IMPAC hardware.
Stand-alone BSR RT PC 0
Minimize the BSR RT PC to a stand-alone PC as follows:

1. Unplug the COM board from the BSR RT PC motherboard.
2. Connect a service PC to the COM2 port of the BSR RT PC and start a terminal pro-
gram, see (BSR RT PC Developer Menu / p. 82).
The BSR RT PC should boot the VRTX operating system after the reset is removed. A cer-
tain trace should be displayed on the service PC, see (Stand-along BSR RT PC
bootup / p. 44).
If the BSR RT PC does not boot, perform the following checks:
• Check the power-up sequence, see (POI/PCM Board Power-up Sequence / p. 27).
• Check the RT motherboard with the Post Card Diagnostics, see (POST
Minimizing the IMPAC HW 0
If the Host PC boots successfully, the rest of the image system should be minimized by
removing all of the boards from the IMPAC Master (IPM) and IMPAC Slave (IPS). The IPS
itself should also be disconnected from the IPM.
The following cases describe the system behavior depending on the available hardware in
the IMPAC. After each step, a power-off and power-on is necessary.
Case 1: All boards connected to the IPM; COM cables removed from the COM board
in the BSR RT PC.
(Description is valid for QDP/DAM and AAQ/COPRA configuration)
• A image is present on the monitor, the Host PC boots to the application menu.
• The BSR RT PC does not finish the POST and sticks in the BIOS because of the open
PCI bus.
Factory Diagnostic Results:
• The RT reset does not work, therefore only some Host stand-alone tests will run.
• The “Host RT Memory Space” and “DMA Interrupt” tests fail, see below

07.07 CS PS AX IR/C
Fig. 73: COM cables removed from COM in BSR RT PC
Case 2: All boards removed from the IPM except the 1KD board in slot 3
• Several messages about drivers and services that were not started appear.
• The BSR RT PC bootup trace (Checking the Bootup Trace / p. 82) shows “Load boards
from Host”
• The RT reset does not work. Since the DMA is not present, almost none of the Host
stand-alone tests will run, see results below.
Fig. 74: All boards removed except 1KD, Slot 3
Case 3: All boards removed from IPM except 1KD in slot 3 and DMA
• The board map (Send Board Map: / p. 73) is sent by the Host PC.
• The BSR RT PC bootup trace (Checking the Bootup Trace / p. 82) fails at “FSM Ini-
tializing ... Physical Capacity 0 images” and ends in fatal error
(VRTX_Pend).
• The RT reset does not work.
• All Host stand-alone tests are passed, see below. All further tests fail.

07.07 CS PS AX IR/C
Fig. 75: All boards removed except 1KD, Slot 3, and DMA
Case 4: All boards removed from IPM except 1KD in slot 3, DMA and SHA
• An image is present on the monitor, the Host PC boots to the application menu.
• The board map (Send Board Map: / p. 73) is sent by the Host PC.
• The BSR RT PC bootup trace (Checking the Bootup Trace / p. 82) fails at “IMGFLW:
Initializing QDSP board not found” and ends in fatal error (VRTX_Pend).
• The RT reset does not work.
• All Host stand-alone tests are passed, see (Fig. 75 / p. 131). All further Plane A tests
fail.
• The SCSI Disk Array Control Channel A/B tests run
Case 5: All boards removed from IPM except 1KD in slot 3, DMA, SHA and QDP in
slot 8
(Description is valid only for QDP/DAM configuration)
• Behavior is the same as the description under Case 4.
Case 6: All boards removed from IPM except 1KD in slot 3, DMA, SHA and QDPs in
slots 8, 10
(Description is valid only for QDP/DAM configuration)
• An image is present on the monitor, the Host PC boots to the application menu.
• The Host PC boots to the Error Task Card. If the DSA option is configured, the following
message is displayed: “Startup failed - please call service. Missing
QDP board for DSA”
• The RT reset works.
• All Plane A tests run.
• Boards which are not present (DAM, 1KD) can not be selected.
• The SCSI Disk Array Control Channel A/B tests run

07.07 CS PS AX IR/C
Case 7: All Boards Installed on IPM, except AAQ/COPRA in Slot 8

(Description is valid only for AAQ/COPRA configuration)
• The system is booting, the COPRA startup diagnostics test is skipped (not indicated)
• he Host PC boots to the Error Task Card. If the DSA option is configured, the following
message is displayed: “Startup failed - please call service. Missing
QDP or COPRA board for DSA or Card Sub option”
• The RT reset works.
• DAM, QDP boards are displayed under Plane A, but indicated as not available
(crossed out), see below.
Fig. 77: With AAQ/COPRA
Fig. 76: Without AAQ/COPRA
• The illustration on the right shows the diagnostics display if a functional AAQ/COPRA
board is installed.

07.07 CS PS AX IR/C
NOTE When boards are removed from or installed in the IMPAC sec-
tion, it is possible that certain drivers will be lost during this
operation. To reestablish the drivers, see:
• For VA.. SW: (Resetting “Display Properties” when Install-
ing Additional 1KD Boards (valid for SW VA42/60
only) / p. 159) and (Restoring Intel Network Drivers (valid
for SW VA42/60 only) / p. 160).
• For VB..SW: (Device driver installation with SW ≥VB11M,
VB22/23, VB30/31 / p. 173) or (Device Driver Installation
with VB11 SW Versions < VB11M / p. 161).

07.07 CS PS AX IR/C
134 Databases
9-
Function Description
9Databases
Overview 0
To open a patient and store patient images, the following system components are required
and should be fully functional:
• The Host PC must be up and running. The Host database must be created and fully
functional.
• The BSR RT PC must be fully booted and ready. A ifs.dat file must be available on the
BSR RT PC system disk.
• The disk array needs to be fully functional. All drives must be formatted and working.
Host Databases 0
The Host PC contains the Versant DB supplied by Syngo. This DB is located on the system
drive of the Host PC. The Versant DB consists of the folders “C:\osc”, “D:\Database” and
“E(D):\Image”. The Partition D:\database consists of several sub folders. The contents are
different depending on the SW version VA.., VB... See the table below for more information.
Database folders VA.. VB.. Purpose

C:\osc X X Front end of the application
E:\Image X - Contains the ECG curve data in VA42/60
D:\Image - X Contains the ECG curve data in VB11/22/30
D:\Database\Local DB X X Contains all stored patients.
D:\Database\Scheduler Store X X Contains all pre-registered patients
DB
D:\Database\Exchange Board X X Required to store temporary patient data for patients
DB transferred to film, network or CD
D:\Database\Archive Store DB X X Required to display the contents of a CD when import
from CD is selected.
D:\Database\db security - X Contains HIPAA settings. Without the db security
folder, a patient cannot be registered, see the informa-
tion below.
X = Available in version VA.. or VB.. - = Not available in version VA.. or VB..
Information about the DB Security Folder

Without the db security folder, patients cannot be registered. If the db security folder is
deleted by mistake, it needs to be recreated with the following work steps:
1. Open a cmd tool box (press the Windows key + R, type in “cmd” and press <Return>)

07.07 CS PS AX IR/C
Databases 135
2. Type in the command “ create_securitydb Install d:\Database “ and press <

Return>
¹ The db security folder is created under D:\Database.
BSR RT PC 0
The BSR RT PC contains the ifs.dat (ifs.bak) file. This file contains the image file number
to LBA (= Logical Block Address on disk array HDs) mapping.
Disk Array 0
According to the available options, 1 to 8 drives are present in the disk array. The pixel data
are stored differently, depending on the selected matrix size:
• 1024 Matrix
¹ One image is distributed to all available drives. Only a part (horizontal stripe) of an
image is stored to one drive.
• 512 Matrix
¹ A complete image is stored to one drive.
How the patient images are stored: 0
The following simplified scenario takes place whenever an ACQ is triggered:

• A LOID (Logical Object ID) is created in the Versant DB
• This LOID is converted to a file number by the FSIL (File System Isolation Layer) pro-
cess running on the Host PC.
• Under this file name, the pointer information (LBA) for the image drives is stored in the
ifs.dat file on the BSR RTPC system drive.

07.07 CS PS AX IR/C
136 Databases
Fig. 78: Database function, simplified diagram

07.07 CS PS AX IR/C
Databases 137
Clearing the Exchange Board 9.1
The Exchange Board is used for all export and send operations. Patient data are stored
only temporarily with the exchange board and are removed again when the export or send
operation is finished. Due to a bug in SW version VA42/VA60 (bug is solved in VB.. ver-
sions), this does not always work and some patients remain in the exchange board. This
leads to a full exchange board after a certain period of operation and export; send and film-
ing tasks can no longer be performed. If this is the case, the exchange board has to be
cleared. Since the exchange board holds only temporary data, it can be deleted (cleared)
without affecting the patient data stored in the local DB. It must be remembered that pixel
data on the disk array are part of the temporarily stored patients on the exchange board.
These pixel data remain on the disk array and occupy disk space after the exchange board
is cleared. Therefore the database should be always deleted after the exchange board has
been cleared and all patient data are saved.
Checking the Free Space in the "Exchange Board" Database 0
• Open a cmd tool box.

• Type: txtexplorer -i, press <Enter>.
• Type: loadlibrary FSIL.dll, press <Enter>.
• Type: open Exchange Board, press <Enter>.
• Type: listdb, press <Enter>.
¹ At this point, you should see a listing of free space in the Exchange Board.
• Type: exit, press <Enter>.
• Close the cmd tool box.
Clearing the Exchange Board: 0
• Clear the Exchange Board by performing the following steps:

- Switch off the system.
- Log onto the system as administrator . While the system attempts to log back in, hold
down the Shift key.
- Log on as the "administrator" and enter the password (see PW List in the CS Knowl-
edge Base).
- Open an "explorer.exe" window. (Windows key + e)
- Select View/Folders Options in the NT Explorer menu bar.
- Select the View tab card, and under Hidden Files, click on Show All Files. Manually
delete the file C:\osc\ExchangeBoard. Do not touch the other files listed under
C:\osc.
- Manually delete the folder D:\Database\ExchangeBoard (complete Exchange Board
folder). Do not touch the other folders listed under D:\Database.
• Archive all patients to CD, Network, etc.
• When all patient data are saved, delete the database, see (Deleting the
Database / p. 138)

07.07 CS PS AX IR/C
138 Databases
Deleting the Database 9.2
NOTE All stored patient information is lost when the database is

deleted. Archive all unarchived patients first.
Depending on the SW version, the work steps to delete the
database are different. Select either (Deleting the database in
SW versions VA42/60 / p. 138) or (Deleting the database in
SW versions VB11, VB22/23, VB30/31 / p. 140).
Deleting the database in SW versions VA42/60 0
The following steps have to be performed to delete the database in Windows NT based
systems (valid for VA42/60 SW versions only):
1. Configuring the Database ID
1. If the system is not up and running, boot up the system.

2. Press <CTRL><ALT><B> and deselect "Disable Windows Hot Keys".
3. Open Windows Explorer by pressing the "Windows key + e" key combination.
4. Right mouse-click on <My Computer>, select <Properties> and <Environment>
5. Under "System Variables", select <DBID_OFFSET>.
NOTE If the variable “DBID_OFFSET” is not available, it has to be

created as follows:
• Click on one of the variables listed in "System Variables",
see (1/Fig. 79 / p. 139); it will then be displayed in the field
"Variable", see (2/Fig. 79 / p. 139).
• Overwrite the name with <DBID_OFFSET> under
"Variable"(2/Fig. 79 / p. 139).

07.07 CS PS AX IR/C
Databases 139
6. Under "Value", see (3/Fig. 79 / p. 139), type in the current date in the format YMMDD,
e.g. 50601.
Fig. 79: DBID Offset

7. Select <Set>, <Apply> and <OK>.
8. Close the window.
NOTICE A new DBID OFFSET Variable (current date) has to be created

each time the database is deleted. If the database has to be
deleted twice a day, the "Value" needs to be changed again.
If this is not observed, duplicate UIDs could be created.
¹ Before you delete the database the 2nd time, increase
the day by at least 1 ( --> 50602)
2. Deleting the Database
1. Switch on the system.

2. Log onto the system as administrator.
- While the system attempts to log back in, hold down the Shift key.
- Log on as the "administrator" and enter the password (see the PW List, CS Knowl-
edge Base).
3. Open an "explorer.exe" window. (Windows key + e)
4. Select View/Folders Options in the NT Explorer menu bar.
5. Select the View tab card, and under Hidden Files, click on Show All Files.
6. Manually delete the “C:\osc” file.

07.07 CS PS AX IR/C
140 Databases
7. Manually delete the “D:\Database” folder (complete Database folder).

8. Manually delete the contents of the “E:\Image” folder (delete only the content, do not
delete the folder).
9. Reboot the system, the free disk indication should display 100%.
NOTE When the database is deleted, the ifs.dat (bak) file on the BSR
RT PC system disk is normally purged and created again dur-
ing the next bootup. If this operation is successful, it is indi-
cated by the 100% free disk space. If automatic purging of the
ifs.dat file fails (free disk space <100%), the ifs.dat file must
be deleted manually, see (Manual Deletion of the ifs.dat
File / p. 141).
3. Checking the new Database ID

The previously changed Database ID needs to be checked with the following procedure:
1. Select <Start><Run>, type in "cmd" and select <OK>.
2. Type in "dblist"
¹ The following IDs would be listed for the example YMMDD = 50602:
ID = 50604 LocalStore@hostname
ID = 50603 ArchiveStore@hostname
ID = 50605 SchedulerStore@hostname
ID = 50606 Exchangeboard@hostname
NOTE The new ID will be updated only after deletion of the data-
base and reboot.
Deleting the database in SW versions VB11, VB22/23, VB30/31 0
The following steps have to be performed to delete the database in Windows XP-based
systems (valid for VB11, VB22, VB23, VB30, and VB31 SW versions only):
1. Open <Local Service> <Utilities>.
2. Under “Source” select <Database tools>
3. Under “Command” select <DB Remove>
4. Click on the <Go> button located in the action bar.
¹ The system starts to reboot. The databases will be deleted and recreated during
boot up. The complete process will take some time, do not interact.
¹ When the boot is finished, the disk free indication should display 100%.

07.07 CS PS AX IR/C
Databases 141
NOTE When the database is deleted, the ifs.dat (bak) file on the BSR
RT PC system disk is normally purged and created again dur-
ing the next boot up. 100% free disk space indicates that the
operation was successful. If automatic purging of the ifs.dat
file fails (free disk space <100%), the ifs.dat file must be
deleted manually, see (Manual Deletion of the ifs.dat
File / p. 141).
Manual Deletion of the ifs.dat File 0
This is necessary only if the system does not display 100% free disk space after the data-
base is deleted and generated again.
1. Stop the application software, see (Stop Application SW / p. 158).
2. Start the BSR RT PC Developer menu, see (Enabling the Developer Menu / p. 146).
3. Connect a Service PC to the COM 2 port of the BSR RT PC, see (Connection of the
Service PC / p. 146).
4. Start the Terminal Emulation Program, see (Starting the Terminal Emulation
Program / p. 147).
5. Type in an “A” (for smntr_noe) and press <Return>. The following display appears:
Fig. 80: Deletion of ifs.dat, 1st step

07.07 CS PS AX IR/C
142 Databases
6. Type in “3” (for DirManager) and press <Return>. The display changes to:
Fig. 81: Deleting ifs.dat, 2nd step

7. Type in “G” (for readDir) and press <Return>. The contents of the BSR RT PC system
disk is displayed. There should be a “ifs.dat” file; the “ifs.bak”, “ifs.new” and “insane.ifs”
files may also be present.
Fig. 82: Deleting ifs.dat, 3rd step

07.07 CS PS AX IR/C
Databases 143
8. Type in “A” (for Delete File). Enter the file name “ifs.dat” and press <Return>. Repeat
this with the files “ifs.bak”, “ifs.new” and “insane.ifs” (if present).
Fig. 83: Deleting ifs.dat, 4st step

9. Type in “G” (for readDir) and press <Return>. The files should no longer be there.
10. Start the application SW, see (Start Application SW / p. 158).
¹ The disk free indication should display 100% when the application is ready.

07.07 CS PS AX IR/C
144 Databases
Known Database Problems 9.3

Free disk space indication • The ifs.dat file still contains file numbers of patients
does not show 100%, even if which no longer present in the Versant database of
there is no patient present in the Host PC. This is could be caused by:
the Patient Browser. ¹ Patients were deleted from the Patient Browser
while the BSR RT PC was not ready.
¹ The Exchange Board DB was deleted without
afterwards deleting the entire database.
• The exchange board still contains patients.
One or more of the following The exchange board is full. To clear the exchange board,
actions cannot be performed, see (Clearing the Exchange Board / p. 137).
while viewing the scenes is
still possible:
• Archiving over the net-
work
• Exporting to CD
• Storing reference or stor-
ing monitor images
• Copying to a film sheet
• Intermittent missing
scenes on archived C
No patient can be registered The DB folder “D:\Database\dbsecurity” is not present or
(message: “Registration corrupt. Create a new db security folder, see (Information
failed. Error reading the local about the DB Security Folder / p. 134).
database”

07.07 CS PS AX IR/C
Procedures 145
10-
Explanation regarding the Procedures Chapter
10Procedures
The section “Procedures” provides a set of different activities which need to be performed
during troubleshooting of the image system. These tasks are summarized in the Proce-
dures section if they are required more than once in different chapters. If required, a docu-
ment link points from the chapter to the appropriate work step in the Procedures section.

07.07 CS PS AX IR/C
146 Procedures
Using the COM 2 port of the BSR RT PC for service 10.1
Connection of the Service PC 0
• Connect the COM port of the Service PC to the COM 2 port of the BSR-RT-PC, using a
0-modem service cable, P/N 99 00 440.
NOTE Do not connect or disconnect the Service PC while the sys-

tem is in use by the customer, because connecting or discon-
necting the service cable from the COM2 port may cause the
BSR RT PC to perform a reboot.
NOTE Image systems equipped with a ATX power supply type

“Dongah” may not start (powers down immediately after
switch on) if a standard service 0-modem cable is connected
to the COM 2 port of the BSR RT PC.
A cable adapter (with only 2 pins connected) must be used to
avoid this problem. This cable adapter is available in the ser-
vice tool box which is located on the inside of the right side
cover.
Enabling the Developer Menu 0
Viewing the BSR-RT-PC bootup, trace or deleting the ifs.dat (.bak) files requires the devel-
oping menu to be active. Perform the following steps to enable the developing menu:
• Remove the right side cover (AXA4-100.841.13 / Removing the Cover Panels).
• Flip switch Nos. 1 and 2 of the SW1 to the right position as shown in figure below
(Fig. 84 / p. 147).

07.07 CS PS AX IR/C
Procedures 147
EH103074-220302-00-01
J48
Application mode
1
J49
8 ON
Service mode
1
SW1
8 ON
IPM
J54
J57
J17
J16
J51
Fig. 84: IMPAC master board (IPM)
NOTE Set the 2 switches back to normal position (all to the left),
when done with service.
Starting the Terminal Emulation Program 0
A Terminal Emulation Program is required to view the bootup trace. It is recommended to

use the TeraTerm Pro terminal evaluation program. See section (Terminal Emulation
Program / p. 148) for how to install and configure it.

07.07 CS PS AX IR/C
148 Procedures
• Start the TeraTerm Pro program. When opened, press <X> followed by a <Return>.
The developer mode main page should appear as shown below.
Fig. 85: Developing menu main page
NOTE The menu will not appear if:

• The BSR RT PC does not boot the VRTX operating system
• The switches on the IPM are not set to service position
NOTE If SW VB11J(K) is installed, the menu is set to a special video

dump mode, and the display shows “M-Dump Video Data to
File”. To return to the normal developer mode, successively
press the letters A - D - V - C - X, followed by a <Return>.
CAUTION Incorrect use of the developer functions can corrupt the SW.
¹ Do not use functions of the developer menu differently
from what is described in this manual.
Terminal Emulation Program 0
To view the BSR RT PC bootup trace or delete the ifs.dat (bak) files, a Service PC with a
terminal emulation program is required. The Hyper Terminal supplied by Microsoft could be
used as the terminal emulation program, but it has some disadvantages. The “TeraTerm
Pro” emulation program offers all requirements and should be used on the BSR RT PC.
The Tera Term Pro program can be downloaded from the CS Homepage in the Intranet.
Refer to <Product Information> <AX Systems> <Angiographie> <AXIOM Artis Family>
<Software> <Tools>.

07.07 CS PS AX IR/C
Procedures 149
Installation of the Tera Term Pro Program
1. Download the Tera Term Pro program from the Service Home Page on the Intranet
(Link: <AX> <Axiom Artis> <Software> <Tools>.
2. Open the self-extracting file “TeraTerm.exe” with a double-click.
3. Select the folder to which the files are to be unzipped (default is “C:\temp”) and click to
<unzip>.
4. Browse to the folder to which the files are to be unzipped. Search for the “setup.exe” file
and start setup with a double-click.
¹ The program will be installed, a “Tera Term Pro” program group will be created
Setup of the Tera Term Pro Program
1. Start the Tera Term Pro via the Start menu. The following menu should appear:
Fig. 86: New connection

2. Set “Serial” and the “COM1” port and close the window with <OK>.
¹ The Tera Term program window opens up.
3. Click on <Setup> in the task bar and select <Serial port ...>; the following menu
appears:
Fig. 87: Serial port setup

4. Change the setting for Flow Control to “Xon/Xoff”; do not touch the other settings, and
click on <OK>.

07.07 CS PS AX IR/C
150 Procedures
5. Click on <Setup> in the task bar and select <Font ...>, the following menu appears.
Fig. 88: Font setup

6. Select Font: Courier New, Size: 10 and click on <OK>.
7. Click on <Setup> in the task bar and select <Window ...>. The menu displayed at the
bottom left appears.
Fig. 89: Window and Save setup

8. Change the setting for "Scroll buffer” from 100 to 500 lines, see (1/Fig. 89 / p. 150).
Click on <OK> to close the window.
9. Click on <Setup> in the task bar and select <Save setup...>. The menu displayed at the
top right appears.
10. Click on <Save>.

07.07 CS PS AX IR/C
Procedures 151
BIOS Initialisierung 10.2
Resetting the BIOS when Changing the Image Drive Configuration 0
NOTE This procedure must be performed on systems equipped

with a Host 2 Module (Motorola PATX5000 MB) if additional
image disk drives were installed or image disk drives were
removed. This procedure must also be performed after a Host
2 Module has been replaced.
The sequence is as follows:
• Set the scan ID to [Yes] in the Symbios BIOS, save the set-
tings.
• Reset the host motherboard BIOS, save the settings.
• Set the scan ID back to [NO] in the Symbios Bios. Save the
settings.
Setting the Scan ID to [Yes] in the Symbios BIOS:
1. Apply power to the system by pressing the power ON/OFF button on the POI1 (PCM).
2. While the Siemens logo is being displayed, press the Esc key to enter the Diagnostic
screen.
NOTE If you miss pressing the ESC key here, you will have to enter
Ctrl+Esc when the Esc key is required later.
¹ Approximately 35 sec. into the system bootup, the following message will appear
on the PC monitor: “Enter Ctrl + C to start the Symbios Configuration Utility”
3. Enter Ctrl+C to go to the “Symbios SCSI Configuration Utility menu”.
¹ The first channel of the multifunction 53C896 SCSI card with the lowest
“Dev/Func” number should be selected.
4. Press the Enter key.
¹ The system will again scan for devices and return with “Device Properties”
selected.
6. Verify that the SEAGATE ST318404(6) drive or the MAXTOR 8B036L0 is shown as the
first device.
7. Use the down arrow key to move the cursor down to the line that contains “53C896”.

07.07 CS PS AX IR/C
152 Procedures
8. Using the right arrow key, move the cursor to the “Scan ID” column and change [ No]
to [ Yes] by pressing the “+“ key. Use the +/- keys from the Num Pad section, see
(1/Fig. 90 / p. 152).
Fig. 90: +/- Keys Num Pad Section

9. Press the Esc key (or press Ctrl+Esc if required), to exit the Device Properties page.
10. Press the Esc key (or press Ctrl+Esc if required), to exit the Adapter Properties page.
11. Using the down arrow key, again move the cursor to <Save changes, then exit this
menu> and press the Enter key.
12. Using the down arrow key, move the cursor to the other channel of the multifunction
53C896 SCSI card with the next “Dev/Func” number and press the Enter key.
selected.
(1/Fig. 90 / p. 152).
16. Press the Esc key (or press CTRL+Esc if required), to exit the Device Properties page.
17. Press the Esc key (or press CTRL+Esc if required), to exit the Adapter Properties
page.
19. Press the Esc key (or press CTRL+Esc if required) to exit the <Boot Adapter List>
page.
20. Using the down arrow key, again move the cursor to <Exit the Configuration Utility>
and press the Enter key. The software will then automatically reboot the system.
Resetting the Host 2 Module Motherboard BIOS
1. While the Siemens logo is being displayed, enter F2 to enter the BIOS setup.
2. Enter the BIOS password (see password list in CS Knowledge base) and press the
ENTER key.
3. Load the default settings by pressing F9.
4. Select Yes and press the ENTER key in the confirmation window.
5. From the BIOS “Main” menu, select the “Advanced” menu.

07.07 CS PS AX IR/C
Procedures 153
6. Set the “Reset Configuration Data” to “Yes”.

7. Press the ENTER key when the “Confirmation” window is displayed.
8. Press the Esc key to exit the current sub menu.
9. Select the “Exit Saving Changes” and press the ENTER key.
¹ The software will then automatically reboot the system.
Set the scan ID back to [ NO] in the Symbios Bios.
1. While the Siemens logo is being displayed, press the Esc key to enter the Diagnostic
screen.
¹ After approximately 35 sec into the system bootup, the following message will
appear on the PC monitor. “Enter Ctrl+C to start Symbios Configuration Utility”
selected.
5. Verify that the SEAGATE ST318404(6) drive or MAXTOR 8B036L0 is being shown as
the first device.
6. Use the down arrow key to move the cursor down to the line which contains “53C896”.
7. Using the right arrow key, move the cursor to the “Scan ID” column and change
[ Yes] to [ No] by pressing the “+“ key. Use the +/- keys from the Num Pad section,
see (1/Fig. 90 / p. 152).
10. Using the down arrow key, again move the cursor to <Save changes then exit this
53C896 SCSI card the next “Dev/Func” number and press the Enter key.
selected.
see (1/Fig. 90 / p. 152).

07.07 CS PS AX IR/C
154 Procedures
17. Using the down arrow key, again move the cursor to <Save changes then exit this
18. Press the Esc key (or press CTRL+Esc, if required) to exit the <Boot Adapter List>
page.
and press the Enter key.
Resetting the Host 2 Module Motherboard BIOS when Changing the Board Con-
figuration 0
NOTE This section must be performed on systems equipped with a

Host 2 Module (Motorola PATX5000 Mb) if any additional
boards were installed in the IMPAC and the hardware config-
uration is affected.
1. Switch on the system; after approximately 5 sec. into the system boot, the Siemens
logo will appear in the center of the PC monitor
2. While the Siemens logo is being displayed, enter F2 to enter the BIOS setup.
3. Enter the BIOS password (see password list in CS Knowledge base)and press ENTER
.
4. Load the default settings by pressing F9.
6. From the BIOS “Main” menu, select the “Advanced” menu.
7. Set the “Reset Configuration Data” to “Yes”.
8. Press the ENTER key when the “Confirmation” window is displayed.
9. Press the Esc key to exit the current sub menu.
10. Select the “Exit Saving Changes” and press the ENTER key.

07.07 CS PS AX IR/C
Procedures 155
Resetting the Symbios BIOS when Changing the Image Drive Configuration 0
NOTE This procedure must be performed on systems equipped

with a Host 3 Module (Intel SE7210TP1-ET motherboard) to
update the Symbios BIOS on the SHA board if the SHA board
was replaced, if additional image disk drives were installed,
or if image disk drives were removed.
The sequence is as follows:
• Set the scan ID to [Yes] in the Symbios BIOS, save the set-
tings.
• Set the scan ID back to [NO] in the Symbios Bios. Save the
settings.
Setting the Scan ID to [Yes] in the Symbios BIOS:
1. Apply power to the system by pressing the power ON/OFF button on the POI1 (PCM).
2. While the Siemens Medical Solutions logo is being displayed, press the Esc key to
enter the Diagnostic screen.
on the PC monitor: “Enter Ctrl + C to start the Symbios Configuration Utility”
selected.
6. Verify that the SEAGATE ST318404(6) drive or the MAXTOR 8B036L0 is shown as the
first device.

07.07 CS PS AX IR/C
156 Procedures
(1/Fig. 91 / p. 156).
Fig. 91: +/- Keys Num Pad Section

53C896 SCSI card with the next “Dev/Func” number and press the Enter key.
selected.
(1/Fig. 91 / p. 156).
16. Press the Esc key (or press CTRL+Esc if required), to exit the Device Properties page.
17. Press the Esc key (or press CTRL+Esc if required), to exit the Adapter Properties
page.
19. Press the Esc key (or press CTRL+Esc if required) to exit the <Boot Adapter List>
page.
and press the Enter key. The software will then automatically reboot the system.
Set the scan ID back to [ NO] in the Symbios Bios.
1. While the Siemens Medical Solutions logo is being displayed, press the Esc key to
enter the Diagnostic screen.
on the PC monitor. “Enter Ctrl+C to start Symbios Configuration Utility”

07.07 CS PS AX IR/C
Procedures 157

selected.
5. Verify that the SEAGATE ST318404(6) or MAXTOR 8B036L0 drive is shown as the first
device.
see (1/Fig. 91 / p. 156).
53C896 SCSI card the next “Dev/Func” number and press the Enter key.
selected.
see (1/Fig. 91 / p. 156).
18. Press the Esc key (or press CTRL+Esc, if required) to exit the <Boot Adapter List>
page.
and press the Enter key.

07.07 CS PS AX IR/C
158 Procedures
Stopping/Starting the Application SW 10.3
Stop Application SW 0
Perform the following steps to stop the application software.

1. Open <Local Service> <Utilities>.
2. Under “Source” select <Escape to OS>
3. Make sure “NT Command Interpreter” is selected in the command field.
4. Enter the command “stopcm” into the parameters field and click <Go>.
¹ “Stopping application software ...” appears, and the application shuts
down.
5. Before starting any further activity, wait until the message “Component Manager
stopped” appears.
6. Close the Service menu.
Start Application SW 0
Perform the following steps to stop the application software. Vorraussetzung: The Applica-
tion SW was stopped previously with the “stopcm” command.
1. Open the “Run” dialog (Windows key + R). Type in “cmd” and click <OK>
¹ A cmd tool box opens.
2. Enter the command “startcm” into the cmd tool box and press <Return>.
¹ “Component manager started” is displayed.
3. Enter the command “rti startpmgt appl” and press <Return>.
¹ After a while, the application starts up.
4. Close the cmd tool box when the application is up and running.

07.07 CS PS AX IR/C
Procedures 159
Network, Display Driver Initialization in SW Version VA42/60 10.4
Resetting “Display Properties” when Installing Additional 1KD Boards (valid for
SW VA42/60 only) 0
1. Login as administrator as follows:

- Switch on the system.
- Wait until the Siemens Medical Solutions Logo and BIOS messages have disap-
peared and the blue screen with dots appears on the screen.
- Hold down the Shift key, until the “Login Information” dialog box appears.
NOTE If you miss this step, the system will auto login to applica-
tions and you must reboot the system.
NOTE The login dialog box may be displayed on the examination

room monitor. Use the mouse to move it to the control room
monitor.
- When the Logon Information dialog box appears, change the name: to “Administra-
tor”, then type the Administrator Account password (see AX Password list in the CS
Knowledge Base) and then click once on the <OK> button (or press the ENTER key).
2. When the Invalid Display Settings utility window appears, place the cursor in the win-
dow and click once to select the window, if required.
3. Click once on the <OK> button or press the <Enter> key to continue.
4. The “Display Properties” window should still be displayed. Set the Desktop Area as fol-
lows:
System / Number of 1KD Boards Desktop Area Setting

Single Plane with 1 1KD Board 2560 x 1024
Single Plane with 2 1KD Boards 5120 x 1024
Single Plane with 3 1KD Boards 7680 x 1024
Biplane with 1 1KD Board 5120 x 1024
5. Set Font Size to “Small Fonts”.

6. Click on the “Apply” button to define the resolution.
7. Click on the “OK” button to close the Display Properties window.

07.07 CS PS AX IR/C
160 Procedures
Restoring Intel Network Drivers (valid for SW VA42/60 only) 0
NOTE Most likely, this section must be performed if an additional

1KD board is installed or a 1KD board is removed and if the
following symptoms are present:
- Message: "At least one driver has failed ..." during sys-
tem start.
- No Network communication, DDIS shows only " ********
"
- No adapter found if the "ipconfig /all" command is
entered.
1. Right-click on the Network Neighborhood icon located on the desktop, and select
Properties.
NOTE The steps below are used to copy the drivers and to update
the network cards, PCI bus slot and settings.
2. Select the Adapters tab to open the Network Adapters window.

3. Select the first adapter in the list.
4. Click once on the Update button to update the drivers for this adapter.
5. In the update window, type in the path “C:\Set_OEM\i8255x” and select continue.
6. Select the second adapter in the list.
7. Click once again on the Update button to update the drivers for this adapter.
8. In the update window, type in the path “C:\Set_OEM\i8255x” and select continue.
9. Save the settings and exit by clicking once on the Close button. The system will now
ask you if you wish to reboot your system
10. Click once on the Yes button.

07.07 CS PS AX IR/C
Procedures 161
Device Driver Installation with VB11 SW Versions < VB11M 10.5
If certained boards are replaced or if the HW configuration is changed, it is possible that the
Windows XP Plug & Play Manager will recognize new HW and will then disable different
device drivers. This may happen if:
• A 1KD board is replaced with a 1KD1 board (or vice versa)
• A COM board is replaced with a COM1 board (or vice versa)
• A IPM/IPS board is replaced with a IPM1/IPS1 board (or vice versa)
• If an optional QDP, 1KD board is added or removed from the system.
Problems with the device drivers can be noticed by the following symptoms:
• The “Found New Hardware Wizard” is present in the screen.
• The monitor image is not displayed in full size (if display drivers are missing)
• The system does not switch off automatically (if the PoiWdm device driver is missing)
In VB11 systems with system SW version < VB11M, the work steps below should be per-
formed to reinstall the device drivers.
Preparations 0
Several reboots are required to reinstall the device drivers. To shorten the boot time, it is
recommended to stop the CsaCompMgrInit service. This prevents the system from boot-
ing to the application. Perform the following steps to stop the service:
1. Stop the Application SW, see (Stop Application SW / p. 158).
2. Right-click on the desktop icon <My Computer>
3. From the pull down-menu select <Manage>
¹ The “Computer Management” menu opens.
4. Click on the + sign in front of <Services and Applications>
¹ The tree expands.
5. Click on <Services>
¹ All Services are displayed.
6. Double-click on the “CsaCompMgrInit” service and set the startup type from “Auto-
matic” to “Manual”.
7. Close all open menus.
NOTE Once the device driver installation is completed, this service

startup type will need to be set back to Automatic.

07.07 CS PS AX IR/C
162 Procedures
Display Driver Installation 0
Verify that the display driver for the 1K Display board is loaded by performing the fol-
lowing steps:
1. If not already done, stop the Application SW, see (Stop Application SW / p. 158).
2. Simultaneously press the Windows key + Pause/Break key to open System Properties
3. Select the Hardware tab and select the <Device Manager>.
Fig. 92: System Properties, Hardware tab card

4. Click to the + sign in front of “Display adapters”
¹ Two “Chips and Technologies Asiliant 69000” drivers should be present for
each 1KD board installed (below display appears on a system with Host 3 and 2
1KD boards installed)

07.07 CS PS AX IR/C
Procedures 163
NOTE The ATI RAGE XL PCI driver is present only on systems with
Host 3 modules.
Fig. 93: Display Adapters (Host 3)

5. If the default VGA display driver “Video Controller (VGA Compatible)” is displayed, the
correct Chips and Technologies (Asiliant) 69000 display driver was not installed or was
disabled by the system. If this is the case, install the correct driver as described below.

07.07 CS PS AX IR/C
164 Procedures
Perform the following steps to install the correct display drivers:

1. Either the “Found New Hardware Wizard” is already open, or open it by selecting the
first driver under “Display adapters”, right-click on it and select “Update Driver ...”, the
following window opens up:
Fig. 94: New HW Wizard

2. Select: “Install from a list or specific location (Advanced)". Click Next button to continue.
3. Select: "Don't search. I will choose the driver to install". Click on the Next button to con-
tinue.
4. Select: Have Disk ... button.
5. Browse to the: C:\Axiom\SmsAx\Video folder. Select the chipsxp.inf installation file
and press the Open button. Press the OK button.
¹ The driver will be installed.
6. When the installation is finished, click on the <Next> button, click on the <Finish> but-
ton.
7. Repeat this for all drivers unless the correct number of Chips and Technologies Asiliant
69000 display drivers are installed (2 for each 1KD board), see figure (Fig. 93 / p. 163).
8. Click on the <Yes> button to restart the computer after the installation of the last dis-
play driver has been completed.
Automatic Display Settings using the EnumDisp Utility

Changing the PCI-to-PCI bridge type on the first 1KD board may be present as a unique
situation because this is used as the primary display monitor. If this board bridge changes,
the system will disable the driver for the display devices on this board and use the first video
port on the second board as the primary monitor video (and boot device). The EnumDisp

07.07 CS PS AX IR/C
Procedures 165
Utility should be used to automatically set the display settings for all installed display
devices.
NOTE This utility should be executed only after the display drivers
for all the existing display devices are installed.
Perform the following steps to set the display designation back to normal:
2. Simultaneously press the Windows key + E key to open the Windows Explorer.
3. Execute the C:\AXIOM\SmsAx\Video\EnumDisp.exe program.
¹ The following window opens:
Fig. 95: EnumDisp Utility

4. Press the "Attach all monitors" button.
¹ The display disappears on all connected monitors.
¹ After about 20 sec. the exam room monitor shows the EnumDisp window again,
the other connected monitors remain off.
5. Use the scroll bar and verify that the display settings (SetDispSettings) for all display
devices was successful (i.e. 2 times the number of 1K display boards in the system).

07.07 CS PS AX IR/C
166 Procedures
6. Scroll down and verify that number of display devices attached to the desktop
(ATTACHED_TO_DESKTOP) is correct (i.e. 2 times the number of 1K display boards
in the system).
7. Reboot the system.
¹ The expected display should be present in the appropriate monitor after the sys-
tem is up again (control room monitors show the control room display and exami-
nation room show the examination room display, reference monitors show the
reference display).
Disabling the SCSI Controller Driver for the Disk Array 0
When replacing the PCI-to-PCI bridge in front of the SCSI controller device for the disk
array, the Windows XP system may automatically load a device driver for these devices.
This will cause a conflict, since these devices are controlled from the BSR RT PC. Thus the
Host PC device needs to be disabled so that it is not controlled from the Host PC side.
Follow the instructions below to verify that the device driver for the SCSI LSI Logic
Device is disabled:
2. Select the Hardware tab and select the Device Manager.
3. Click on the + sign in front of “SCSI and RAID controllers”
¹ The driver for the two SCSI Adapter devices for the Disk Arrays should be dis-
abled. A red "X" meaning that the device is disabled should be in front of each LSI
Logic Device, see figure below.
Fig. 96: SCSI and Raid controllers (Host 3)

If the red “X” is not present, select each SCSI and RAID controller's 53C896 LSI Logic
device and disable it as follows:
1. Double-click on the device to open the Properties menu.
2. Set the device usage to: "Do not use this device (disable)".

07.07 CS PS AX IR/C
Procedures 167
Driver Installation for Other Devices 0
Drivers for the devices listed below may be disabled as well. The following list shows the
devices and the driver installation file in parentheses (the .inf files are located in the Win-
dows\inf directory).
• NTB (NtbS.inf)
• Dam (DamS.inf)
• QDP (QdpS.inf)
• SVB (SvbS.inf)
• AIC DMA (AicDmaS.inf)
• RAPTOR (RaptorS.inf)
• Adv GPGA (AdvFpgaS.inf)
The presence of these drivers can be checked as follows:

07.07 CS PS AX IR/C
168 Procedures
4. Click on the + sign in front of “Other devices”

¹ A list of drivers should be present. The figure below shows the drivers required on
a biplane system with 6 ODP boards installed; for monoplane, see
(Fig. 99 / p. 171).
Fig. 97: Other devices (biplane)

07.07 CS PS AX IR/C
Procedures 169
If the system requires a device driver to be loaded for one of the above devices, pro-
ceed as follows:
1. The “Found New Hardware Wizard” will appear if one of the above listed drivers is miss-
ing
Fig. 98: Other Devices Wizard

2. Select: "Install the software automatically (Recommended)". Click on Next to continue
3. Wait until the Wizard finds the installation file for this device.
4. Click on Finish to close the Wizard.
5. Repeat this procedure until all drivers are reloaded and the “Found New Hardware Wiz-
ard” no longer appears.
6. Reboot the system after all devices are installed.
Depending on the configuration, a different number of drivers is required.

07.07 CS PS AX IR/C
170 Procedures
Driver Monoplane System Biplane System

Advantage FPGA (Dummy) 1 1
Other PCI Bridge Devices ---- 1
PCI Memory Controller ---- 8
QDP (Dummy) 3 *1 6 *1
Raptor (Dummy) 8 8
SvB (Dummy) 2 4
*1: Number depends on the number of installed QDPs, could be also 2 (SP) or 4 (BP).
Installation of the PoiWdm Device Driver 0
The PoiWdm device driver signals the POI driver when the system is about to enter the
power-off status and this is used to power off the lab. The system will not power off if the
driver is not present.
The presence of these drivers can be checked as follows:
2. Simultaneously press the Tab key+Del key+ + key (from the NumPad) to gain access to
Windows XP.
5. Click on the + sign in front of “Other devices”
¹ The POI WDM Device driver should be present, see (1/Fig. 99 / p. 171)

07.07 CS PS AX IR/C
Procedures 171
Fig. 99: POI WDM device driver, Other Devices, Monoplane

If the presence of the PoiWdm device driver is missing, follow the steps below to
install the PoiWdm device driver:
1. Select "Add Hardware Wizard" from the Hardware tab card. Click on the Next button to
continue.
2. Select: "Yes, I have already connected the hardware". Click on the Next button to con-
tinue.
3. Select "Add a new hardware device". Click on the Next button to continue.
4. Select: "Install the hardware that I manually select from a list (Advanced)". Click on the
Next button to continue.
5. Select "Show All Devices". Click on the Next button to continue.
6. Select "Siemens Medical Solutions USA, Inc.".Click on the Next button 2 times to con-
tinue.
7. In the Files Needed dialog, browse to C:\Windows\System32\drivers and select the
PoiWdm.sys file.
8. Click on the Open button.

07.07 CS PS AX IR/C
172 Procedures
9. Click on the OK button to copy the file.

10. Click the on Finish button.
NOTE Do not forget to set the set the CsaCompMgrInit service star-
tup back to Automatic, see (Preparations / p. 161)

07.07 CS PS AX IR/C
Procedures 173
Device driver installation with SW ≥VB11M, VB22/23, VB30/31 10.6
If certain boards are replaced or if the HW configuration is changed, it is possible that the
Windows XP Plug & Play Manager will recognize new HW and will then disable different
device drivers. This may happen if:
• A 1KD board is replaced with a 1KD1 board (or vice versa)
• A COM board is replaced with a COM1 board (or vice versa)
• A IPM/IPS board is replaced with a IPM1/IPS1 board (or vice versa)
• If any board is replaced in the IMPAC.
Problems with the device drivers can be noticed by the following symptoms:
• The “Found New Hardware Wizard” is present on the screen.
• The monitor image is not displayed in full size (if display drivers are missing).
• The system does not switch off automatically (if the PoiWdm device driver is missing).
The work steps below should be performed to reinstall the device drivers.
Preparations 0
Two reboots are required to reinstall the device drivers. To shorten the boot time, it is rec-
ommended to stop the CsaCompMgrInit service. This prevents the system from booting to
the application. Perform the following steps to stop the service:
1. Stop the Application SW, see (Stop Application SW / p. 158).
2. Right-click on the desktop icon <My Computer>.
3. From the pull-down menu, select <Manage>.
¹ The “Computer Management” menu opens.
4. Click on the + sign in front of <Services and Applications>.
¹ The tree expands.
5. Click on <Services> .
¹ All Services are displayed.
6. Double-click on the “CsaCompMgrInit” service and set the startup type from “Auto-
matic” to “Manual”.
7. Close all open menus.
NOTE Once the device driver installation is completed, this service

startup type will need to be set back to Automatic.
VB11M, VB22/23, VB30/31 Driver Installation 0
In version ≥ VB11M and in versions VB22/23, VB30/31, a batch file exists to update all of
the BSR drivers.

07.07 CS PS AX IR/C
174 Procedures
Perform the following steps to update the drivers:

1. Open the Windows Explorer, browse to “C:\AXIOM\utils”.
2. Start the batch file “bsrdd.bat” by double-clicking on it.
¹ Different cmd tool boxes occur.
3. When ready (all cmd tool boxes are closed), restart the system with <Start> <Shut-
down> <Restart>.
NOTE All drivers should now be updated. However, the size of the
monitor display and the allocation of the displays to the
appropriate monitor may still be wrong. This can be cor-
rected using the EnumDisp utility.
Perform the following steps to run the EnumDisp utility:

1. Open the Windows Explorer, browse to “C:\AXIOM\SmsAx\Video”.
2. Start the batch file “EnumDisp.exe” by double-clicking on it.
¹ The following window opens:
Fig. 100: EnumDisp Utility

07.07 CS PS AX IR/C
Procedures 175
3. Click on the "Attach all monitors" button.

¹ The display disappears on all connected monitors.
¹ After about 20 sec. the exam room monitor shows the EnumDisp window again;
the other connected monitors remain off.
¹ The process is finished when “-- Attach all monitors end --” is displayed in the
message window.
4. Set the startup of the “CsaCompMgrinit” service from “Manual” back to “Automatic”,
see section (Preparations / p. 173) at the beginning of this chapter.
¹ The expected display should be present on the appropriate monitor after the sys-
tem is up again (control room monitors show the control room display and the
examination room monitors show the examination room display, reference moni-
tors show the reference display).

07.07 CS PS AX IR/C
176 Changes to Previous Version
11Changes to Previous Version 11-
Chapter Subchapter Changes

All All All chapters upgraded to be in compliance with the
newest HW and SW versions (VB23, VB31).

07.07 CS PS AX IR/C
Index 177
1
12Index
1KD Board LED Description . . . . . . . .121
A AAQ COPRA LED Description . . . . . .119
B BIOS Host. . . . . . . . . . . . . . . . . . . . . . .98

BIOS Reset when Changing Image Drive Configuration151
BIOS Reset when Changing the Board HW Configuration154
BIOS Symbios . . . . . . . . . . . . . . . . . .108
BIOS, Adaptec . . . . . . . . . . . . . . . . . .106
Black Screen, Troubleshooting . . . . . . .33
Block Diagram . . . . . . . . . . . . . . . . . . .12
Blue Screen, Troubleshooting. . . . . . . .39
Board Overview with AAQ COPRA . . .14
BR RT PC Bootup Trace Check . . . . . .82
BSR RT PC BIOS. . . . . . . . . . . . . . . .111
BSR RT PC Boots into a Fatal Error. . .43
BSR RT PC displays errors at a high repetition rate43
BSR RT PC does not boot . . . . . . . . . .42
BSR RT PC, Cyclical Reboot . . . . . . . .43
C CD-R LED Description . . . . . . . . . . . . 125

CD-ROM LED Description . . . . . . . . .124
CMOS Clearing, Host Motherboard . .103
Conventions and Abbreviations . . . . . .10
D DAM Board LED Description . . . . . . .120

Database Function Description . . . . .134
Developer Menu . . . . . . . . . . . . . . . . . .82
Developer menu enable . . . . . . . . . . .146
E Exchange Board Clear . . . . . . . . . . . . 137
F Factory Diagnostics . . . . . . . . . . . . . . .67

Factory Diagnostics, how to start . . . . .68
Formatting the Host 2 System Drive. .106
Formatting the Image Drive(s) via the Symbios BIOS108
Formatting the Image Drives in the Factory Diagnostics74
H Hardware Tests. . . . . . . . . . . . . . . . . . .77

Hardware Tests, how to start . . . . . . . .78
hm_serv_LabelPowerPresent. . . . . . . . .8
hm_serv_NoteProtectEyes. . . . . . . . . . .8
hm_serv_WarnSetUPSPowerMayBePresent9

07.07 CS PS AX IR/C
178 Index
I IDE DVD/CD-R LED Description. . . . 125

Ifs.dat Delete . . . . . . . . . . . . . . . . . . . 141
Image Drive Verification . . . . . . . . . . 109
Image Problems, Corrupted Images . . 21
IMPAC Board, Overview with QDP Boards13
IPM Board LED Description . . . . . . . 123
IPS Board LED Description. . . . . . . . 124
N Network Adapter Diagnostics . . . . . . . 94

Network Driver Restore. . . . . . . . . . . 160
O Overview, Image System . . . . . . . . . . 11
P PCM LED . . . . . . . . . . . . . . . . . . . . . 116

POI LED description . . . . . . . . . . . . . 115
POI/PCM Power-up Sequence . . . . . . 27
POST Card User Instructions . . . . . . . 46
POST Code Table Host 2 Module, BSR RT PC Module48
POST Diagnostics. . . . . . . . . . . . . . . . 46
Q QDP Board LED Description. . . . . . . 118
R Remarks . . . . . . . . . . . . . . . . . . . . . . . . 8
Resetting the Display Properties when Installing Additional 1KD Boards159
S Safety Information, General . . . . . . . . . 8

Safety Information, Product-specific . . . 8
SBE Board (Host) LED Description. . 125
SBE Board (RPAU) LED Description. 126
Service PC connection to BSR RT PC146
SHA Board LED Description . . . . . . . 122
Startup Diagnostics. . . . . . . . . . . . . . . 64
Symbios BIOS Reset . . . . . . . . . . . . 155
Syngo does not start . . . . . . . . . . . . . . 40
System Drive Verification . . . . . . . . . 107
T TPS Board LED Description . . . . . . . 124
V Voltage Description . . . . . . . . . . . . . . 114

VSD Board LED Description . . . . . . . 124
W Windows does not start. . . . . . . . . . . . 37

07.07 CS PS AX IR/C

Axa4-100 840 02 04 02

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Axa4-100 840 02 04 02

Uploaded by

Copyright:

Available Formats

ra

Troubleshooting Guide for the Image System

Print No.: AXA4-100.840.02.04.02 English

Document revision level

AXIOM Artis AXA4-100.840.02.04.02 Page 2 of 178 Siemens

1 _______ General Information______________________________________________ 7

2 _______ Introduction ___________________________________________________ 11

Image System Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

3 _______ Decision Finding _______________________________________________ 16

Problems during SW Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

4 _______ Boot Problems _________________________________________________ 26

Siemens AXA4-100.840.02.04.02 Page 3 of 178 AXIOM Artis

6 _______ BIOS Functions ________________________________________________ 97

AXIOM Artis AXA4-100.840.02.04.02 Page 4 of 178 Siemens

BIOS Functions with Host 3 Module (Intel SE7210TP1-E MB). . . . . . . . . . . . . . . . 101

7 _______ Voltages and LEDs_____________________________________________ 114

Voltage Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

8 _______ Downgrade to the Minimum HW__________________________________ 128

Minimizing Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

9 _______ Databases____________________________________________________ 134

Function Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Siemens AXA4-100.840.02.04.02 Page 5 of 178 AXIOM Artis

Host Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

10 ______ Procedures ___________________________________________________ 145

Explanation regarding the Procedures Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

11 ______ Changes to Previous Version ____________________________________ 176

12 ______ Index ________________________________________________________ 177

AXIOM Artis AXA4-100.840.02.04.02 Page 6 of 178 Siemens

Required Aids and Tools 0

• Standard service tool kit

Terminal Emulation Program

Siemens AXA4-100.840.02.04.02 Page 7 of 178 AXIOM Artis

General Safety Information 0

Product-specific Safety Information 0

RTC, Image System

Laser Class 3B units having a maximum output of 500 mW.

AXIOM Artis AXA4-100.840.02.04.02 Page 8 of 178 Siemens

Image System with UPS

If a UPS option is configured for the image system, it is pos-

Location of the Assemblies

Fig. 1: Image system module overview

Siemens AXA4-100.840.02.04.02 Page 9 of 178 AXIOM Artis

Conventions and Abbreviations 0

BSR = Abbreviation for Image System (in German)

AXIOM Artis AXA4-100.840.02.04.02 Page 10 of 178 Siemens

Siemens AXA4-100.840.02.04.02 Page 11 of 178 AXIOM Artis

AXIOM Artis AXA4-100.840.02.04.02 Page 12 of 178 Siemens

IMPAC Board Overview (QDP Version) 0

Fig. 4: Biplane Board Overview

Siemens AXA4-100.840.02.04.02 Page 13 of 178 AXIOM Artis

IMPAC Board Overview (AAQ COPRA Version) 0

Fig. 5: Overview of IMPAC Boards (COPRA Version)

AXIOM Artis AXA4-100.840.02.04.02 Page 14 of 178 Siemens

Siemens AXA4-100.840.02.04.02 Page 15 of 178 AXIOM Artis

Problem Links and Solutions

AXIOM Artis AXA4-100.840.02.04.02 Page 16 of 178 Siemens

Boot Problems 3.1

Problem Links and Solutions

Siemens AXA4-100.840.02.04.02 Page 17 of 178 AXIOM Artis

Problem Links and Solutions

AXIOM Artis AXA4-100.840.02.04.02 Page 18 of 178 Siemens

Function Problems 3.2

Problem Links and Solutions

1 _ General Information________________________________________ 7

2 _ Introduction _____________________________________________ 11

3 _ Decision Finding _________________________________________ 16

4 _ Boot Problems ___________________________________________ 26

6 _ BIOS Functions __________________________________________ 97

7 _ Voltages and LEDs_______________________________________ 114

8 _ Downgrade to the Minimum HW____________________________ 128

9 _ Databases______________________________________________ 134

10 Procedures _____________________________________________ 145

11 Changes to Previous Version ______________________________ 176

12 Index __________________________________________________ 177