Brilliance CT: 6-Slice, 10-Slice, 16-Slice, and 16 Power Configurations

TM
Brilliance CT
6-slice, 10-slice, 16-slice, and 16
Power configurations
CIRS Service Manual
4535 673 63861

Revision I
This document and the information contained in it is proprietary and confidential information of Philips Healthcare (“Philips”) and may not be reproduced, copied in
whole or in part, adapted, modified, disclosed to others, or disseminated without the prior written permission of the Philips Legal Department. Use of this document
and the information contained in it is strictly reserved for current Philips personnel and Philips customers who have a current and valid license from Philips for use by
the customer’s designated in-house service employee on equipment located at the customer’s designated site. Use of this document by unauthorized persons is strictly
prohibited. Report violation of these requirements to the Philips Legal Department. This document must be returned to Philips when the user is no longer licensed
and in any event upon Philips’ first written request.
© 2009 Philips Healthcare

Preliminary 21 August 2009
BrillianceTM CT 6-slice, 10-slice, 16-slice, and 16 Power configurations CIRS Service Manual Rev I
Philips Healthcare
© 2009 KONINKLIJKE PHILIPS ELECTRONICS N. V. ALL RIGHTS RESERVED.
Warranty Disclaimer
PHILIPS PROVIDES THIS DOCUMENT WITHOUT WARRANTY OF ANY KIND, IMPLIED OR EXPRESSED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE.
Limitation of Liability
PHILIPS HAS TAKEN CARE TO ENSURE THE ACCURACY OF THIS DOCUMENT. HOWEVER, PHILIPS ASSUMES
NO LIABILITY FOR ERRORS OR OMISSIONS AND RESERVES THE RIGHT TO MAKE CHANGES WITHOUT
FURTHER NOTICE TO ANY PRODUCTS HEREIN TO IMPROVE RELIABILITY, FUNCTION, OR DESIGN. PHILIPS
MAY MAKE IMPROVEMENTS OR CHANGES IN THE PRODUCT(S) OR PROGRAM(S) DESCRIBED IN THIS
DOCUMENT AT ANY TIME.
Password Notice
THE PASSWORD IS THE PROPERTY OF PHILIPS HEALTHCARE AND IS PROVIDED FOR THE EXCLUSIVE
PURPOSE OF PROVIDING ACCESS TO SELECTED SERVICE UTILITIES WHICH ARE DESCRIBED IN THIS
SERVICE MANUAL AS BEING ASSOCIATED WITH THE PASSWORD. USE OF THIS PASSWORD FOR ANY
PURPOSE OTHER THAN FOR THE ACCESS TO THE SELECTED SERVICES UTILITIES IS STRICTLY
PROHIBITED.
CSIP Level 1 4535 673 63861 © 2009 Koninlijke Philips Electronics N.V All Rights Reserved Refer to Front Cover II
Symbol Descriptions
! Attention symbol Radiation warning symbol
Laser warning symbol Biohazard warning symbol
Magnetism warning symbol Projectile warning symbol
Electrical warning symbol Do not touch
Crush warning symbol
CSIP Level 1 4535 673 63861 © 2009 Koninlijke Philips Electronics N.V All Rights Reserved Refer to Front Cover III
Safety Information
To the User of This Manual
The user of this manual is directed to read and carefully review the instructions, warnings and cautions contained herein prior to beginning installation or service activities.
While you may have previously installed or serviced equipment similar to that described in this manual, changes in design, manufacture or procedure may have occurred
which significantly affect the present installation or service.
!
WARNING In addition to the warnings listed above, make sure to follow all safety guidelines as
described in the Safety Manual. Failure to do so can result in severe personal injury.
Installation and Environment
Except for installations requiring certification by the manufacturer per federal standards, see that a radiation protection survey is made by a qualified expert in accordance
with NCRP 102, section 7, as revised or replaced in the future. Perform a survey after every change in equipment, workload, or operating conditions which might
significantly increase the probability of persons receiving more than the maximum permissible dose equivalent.
Diagnostic Imaging Systems - Mechanical-electrical Warning

All of the moveable assemblies and parts of this equipment should be operated with care and routinely inspected in accordance with the manufacturer’s recommendations
contained in the equipment manuals.
Only properly trained and qualified personnel should be permitted access to any internal parts. Live electrical terminals are deadly; be sure line disconnects are opened and
other appropriate precautions are taken before opening access doors, removing enclosure panels, or attaching accessories.
Do not under any circumstances, remove the flexible high tension cables from the x-ray tube housing or high tension generator and/or the access covers from the generator
until the main and auxiliary power supplies have been disconnected. Failure to comply with the above may result in serious or fatal bodily injuries to the operator or those
in the area.
Prior to any service and maintenance activities inside components:
Switch off the system at the main power supply (useing the on-site On-Off switch), and the internal/external uninterruptible power supply (UPS).
Make sure that no other person can switch on power or switch off the security measures, when installation, maintenance or service work on the system is performed.
Always use an ESD protection wrist strap when servicing any component in the system.
Electrical-grounding Instructions
The equipment must be grounded to an earth ground by a separate conductor. The neutral side of the line is not to be considered the earth ground. On equipment
provided with a line cord, the equipment must be connected to properly grounded, three-pin receptacle. Do not use a three-to-two pin adapter.
CSIP Level 1 4535 673 63861 © 2009 Koninlijke Philips Electronics N.V All Rights Reserved Refer to Front Cover IV
Diagnostic Imaging Systems - Radiation Warning

X-ray and Gamma-rays are dangerous to both operator and others in the vicinity unless established safe exposure procedures are strictly observed.
The useful and scattered beams can produce serious or fatal bodily injuries to any persons in the surrounding area if used by an unskilled operator. Adequate precautions
must always be taken to avoid exposure to the useful beam, as well as to leakage radiation from within the source housing or to scattered radiation resulting from the
passage of radiation through matter.
Those authorized to operate, participate in or supervise the operation of the equipment must be thoroughly familiar and comply completely with the current established
safe exposure factors and procedures described in publications, such as: Subchapter J of Title 21 of the Code of Federal Regulations, "Diagnostic X-ray Systems and Their
Major Components", and the national council on radiation protection (NCRP) no. 102, "Medical X-ray And Gamma-ray Protection For Energies Up To 10 Mev-
equipment Design and Use", as revised or replaced in the future.
Those responsible for planning of x-ray and gamma-ray equipment installations must be thoroughly familiar and comply completely with NCRP no. 49, "Structural
Shielding Design and Evaluation For Medical Of X-rays and Gamma-rays of Energies Up to 10 Mev", as revised and replaced in the future. Failure to observe these
warnings may cause serious or fatal bodily injuries to the operator or those in the area.
Add additional safety information as needed.
CSIP Level 1 4535 673 63861 © 2009 Koninlijke Philips Electronics N.V All Rights Reserved Refer to Front Cover V
Revision History
Revision History
ECO Revision Date Comments

A September 2005 New Release for 2.0
Added information about new CIRS Service CD. “Network Connections
Configuration for CIRS Servers” section now has the correct Intel NIC designations.
B March 2006
Includes S1 version 2, VS1 version 2, VS1 Plus, S2/S3 Version 4, and “Philips,
System Diagnostic Utilities (PN SOFGR-064) Rev. 16 CD” information.
The information on the Fan Control Board in the S2/S3 version 4 servers has
C May 2006 changed. Now, the fans must be running at all times to provide an additional load to
the power supply. If the fans are not running, power up issues may occur.
Removed information on IPMI View and Intel Server Management (ISM)
D August 2006 applications.Added information on replacement network switch and version 5 of the
S2/S3 server.
Added S1 version 3 information, S2 version 5 information, and new Troubleshooting
E January 2007
information.
Added in the VSD4 server. The VSD4 is a new Vertical S1 server with dual-core
F May 2007
processors.
Added information for 2UQ server (new quad-core processor S2) and 3UQ3 server
G January 2008
(new quad-core processor S1).
Added new UTS Browser utility to transfer raw data to and from CIRS. Also,
updated the Reload the Acquisitor Board FPGA procedure with which file to select
2018276 H April 2008 for each system. CIRS Image Test performance values were updated. Added
information for 3UD version 1 and 2, VSD4 version 2, 3UQ version 2, and 2UQ
version 2 servers.
CSIP Level 1 4535 673 63861 © 2009 Koninlijke Philips Electronics N.V All Rights Reserved Refer to Front Cover VI
Revision History
ECO Revision Date Comments

2021463 I August 2009 Added information for 2UQ version 3, VSD4 version 3, and 3UQ3 version 3 servers.
This document was prepared by the CT BU Cleveland Service Innovation Department.

For any additions, corrections, or suggestions, contact:
CT BU Cleveland Customer Support Department
Email: cle.cthelp@philips.com
CSIP Level 1 4535 673 63861 © 2009 Koninlijke Philips Electronics N.V All Rights Reserved Refer to Front Cover VII
TM
Brilliance CT 6-slice, 10-slice, 16-slice, and 16 Power configurations CIRS Service Manual Rev I
Revision History ............................................................................................................................. VI
Introduction .................................................................................................................................... 1
CIRS Rack Flow Diagram ...................................................................................................................................... 3
Combined Rack Console Flow Diagram ................................................................................................................ 4
Power down procedure .......................................................................................................................................... 5
S1 Server Recon Processes .................................................................................................................................. 6
Supervisor Process........................................................................................................................................... 7
Series Process.................................................................................................................................................. 8
Image Process.................................................................................................................................................. 9
Theory of Operation ............................................................................................................................................. 10
Horizontal Servers Functional Description ................................................................................... 11

Overview .............................................................................................................................................................. 11
S1 version 1 ......................................................................................................................................................... 12
Intel SE7501BR2 motherboard Block Diagram .............................................................................................. 13
S1 version 1 - Network Interface Controller.................................................................................................... 14
NIC Diagnostic LEDs................................................................................................................................. 14
S1 version 2 ......................................................................................................................................................... 15
SuperMicro X6DH8-XG2 motherboard Block Diagram................................................................................... 16
S1 version 2 - Network Interface Controller................................................................................................... 17
S1 version 3 (p/n 4535 674 02551) with SuperMicro X6HD-XG2 motherboard................................................... 18
S1 version 3 SCSI Drive Configuration and Interconnects ............................................................................. 20
S1 version 3 - Network Interface Controller................................................................................................... 21
CSIP Level 1 4535 673 63861 © 2009 Koninlijke Philips Electronics N.V All Rights Reserved Refer to Front Cover i
TM
3UD3 version 1 and version 2.............................................................................................................................. 22

SuperMicro X7DB8-X motherboard Block Diagram........................................................................................ 23
SuperMicro X7DB8-X Back Panel Connectors............................................................................................... 24
3UD3 Network Interface Controller................................................................................................................. 24
3UD3 SCSI Drive Configuration and Interconnects........................................................................................ 25
3UQ3.................................................................................................................................................................... 26
SuperMicro X7DB8-X motherboard Block Diagram........................................................................................ 27
SuperMicro X7DB8-X Back Panel Connectors............................................................................................... 28
3UQ3 Network Interface Controller................................................................................................................. 28
3UQ3 SCSI Drive Configuration and Interconnects........................................................................................ 29
S2/S3 version 3.................................................................................................................................................... 30
Intel SE7501WV2 motherboard Block Diagram.............................................................................................. 31
DIMM Failure LED .......................................................................................................................................... 32
S2/S3 version 3 Network Interface Controller................................................................................................. 32
S2/S3 version 4 and version 5 ............................................................................................................................. 33
Intel® Server Board SE7520JR2 – I/O Panel Features.................................................................................. 34
S2/S3 version 4 and version 5 Network Interface Controller .......................................................................... 34
NIC LEDs .................................................................................................................................................. 34
Fan Control Board .......................................................................................................................................... 35
2UQ...................................................................................................................................................................... 36
Intel® Server Board S5000PAL – I/O Panel Features.................................................................................... 37
2UQ Network Interface Controller................................................................................................................... 37
Fan Control Board .......................................................................................................................................... 38
Network Switch .................................................................................................................................................... 39
Netgear GS516T............................................................................................................................................. 39
Front Panel................................................................................................................................................ 39
Rear Panel ................................................................................................................................................ 40
Netgear GS116 (p/n 453567402301) ............................................................................................................. 40
CSIP Level 1 4535 673 63861 © 2009 Koninlijke Philips Electronics N.V All Rights Reserved Refer to Front Cover ii
TM
Vertical Servers Functional Description ....................................................................................... 41

Overview .............................................................................................................................................................. 41
Vertical S1 version 1 ............................................................................................................................................ 42
Rev. A enclosure and layout........................................................................................................................... 43
PCI slots .................................................................................................................................................... 45
SCSI .......................................................................................................................................................... 46
LAN ........................................................................................................................................................... 46
System disk drive ...................................................................................................................................... 47
CDROM..................................................................................................................................................... 49
SCSI array................................................................................................................................................. 50
Rev B and C enclosure and layout ................................................................................................................. 52
Intel SE7501BR2 Motherboard....................................................................................................................... 53
Vertical S1 version 2 and VS1 Plus ..................................................................................................................... 54
Vertical S1 version 2 and VS1 Plus Network Interface Controller ................................................................. 56
VSD4.................................................................................................................................................................... 57
SuperMicro X7DBE-X motherboard Block Diagram ....................................................................................... 58
SuperMicro X7DBE-X Back Panel Connectors .............................................................................................. 59
VSD4 Network Interface Controller................................................................................................................. 59
VSD4 SATA Drive Configuration .................................................................................................................... 60
Acquisitor and 3DBP Functional Description ............................................................................... 61

Acquisitor Board Block Diagram .......................................................................................................................... 61
3DBP Board - 6 ASIC configuration ..................................................................................................................... 62
3DBP Board - 2 ASIC configuration ..................................................................................................................... 64
CSIP Level 1 4535 673 63861 © 2009 Koninlijke Philips Electronics N.V All Rights Reserved Refer to Front Cover iii
TM
CIRS Server Configuration and Management ................................................................................ 65

Original S1 Servers: VS1/S1................................................................................................................................ 66
Check BIOS Version....................................................................................................................................... 66
Replacement S1 Servers: S1 V2, S1 V3, VS1 V2, and VS1 Plus ....................................................................... 67
Restore BIOS.................................................................................................................................................. 67
Bios Settings for S1 V2, S1 V3, VS1 V2, VS1 Plus (X6DH8-XG2 motherboard) ........................................... 68
3UD3/3UQ3 ......................................................................................................................................................... 74
Restore BIOS.................................................................................................................................................. 74
BIOS Settings for 3UD3/3UQ3 ....................................................................................................................... 75
VSD4.................................................................................................................................................................... 82
Restore BIOS.................................................................................................................................................. 82
BIOS Settings for VSD4.................................................................................................................................. 83
S2/S3 Server version 3 with Intel SE7501WV2 motherboard ............................................................................. 90
BIOS Parameters for S2/S3 V3 (p/n 4535 671 02401)................................................................................... 91
S2/S3 versions 4 and 5 with Intel SE7520JR2 motherboard ............................................................................... 92
Restore BIOS.................................................................................................................................................. 92
BIOS Settings for S2/S3 V4 and V5 ............................................................................................................... 93
2UQ ................................................................................................................................................................... 100
Check BIOS Version..................................................................................................................................... 100
Restore BIOS................................................................................................................................................ 100
BIOS Settings for 2UQ.................................................................................................................................. 101
Reconstruction Troubleshooting ................................................................................................. 107

CIRS Troubleshooting Guide ............................................................................................................................. 107
Server and System Issues............................................................................................................................ 108
Software Installation Issues .......................................................................................................................... 113
CIRS Image Test .......................................................................................................................................... 114
Acquisitor Related Issues ............................................................................................................................. 115
3DBP and Acquisitor Driver and FPGA Guide.............................................................................................. 116
CSIP Level 1 4535 673 63861 © 2009 Koninlijke Philips Electronics N.V All Rights Reserved Refer to Front Cover iv
TM
Troubleshooting Solutions ............................................................................................................................ 117

Verify that the Host-IRS Connection is active ......................................................................................... 117
Enable Supervisor Service on S1............................................................................................................ 117
Ping IP Addresses................................................................................................................................... 118
Verify amount of RAM ............................................................................................................................. 119
Verify CIRS Software Revision................................................................................................................ 120
Create RawData Directory on F:\ ............................................................................................................ 120
Host PC Disk Defragmentation ............................................................................................................... 121
Using Windows Task Manager................................................................................................................ 122
SCSI RAID - Import Foreign Disk and Re-create Array .......................................................................... 123
VSD4 SATA RAID - Re-create Array ...................................................................................................... 127
CIRS Image Test................................................................................................................................................ 135
Running the test............................................................................................................................................ 135
Network Connections Configuration for CIRS Servers ...................................................................................... 137
Acquisitor Board Diagnostics ............................................................................................................................ 139
Main GUI....................................................................................................................................................... 140
The Acquisitor Diagnostics ........................................................................................................................... 141
The Command Buttons................................................................................................................................. 144
The Output Window ...................................................................................................................................... 146
Typical Diagnostic Execution Cycle.............................................................................................................. 146
Normal Scanner Diagnostic Mode ................................................................................................................ 147
Internal Loop-back Diagnostics .................................................................................................................... 147
External Loop-back Diagnostics ................................................................................................................... 147
Loop-back Cable Connections ................................................................................................................ 148
Acquisitor Board Software ............................................................................................................................ 149
Check the Driver Version ........................................................................................................................ 149
Reload the Acquisitor Board Driver ......................................................................................................... 149
Reload the Acquisitor Board FPGA......................................................................................................... 150
3DBP Diagnostics .............................................................................................................................................. 151
Main GUI....................................................................................................................................................... 152
3DBP Diagnostics Components ................................................................................................................... 153
The Command Buttons................................................................................................................................. 157
Run Options Dialog....................................................................................................................................... 159
The Output Window ...................................................................................................................................... 159
CSIP Level 1 4535 673 63861 © 2009 Koninlijke Philips Electronics N.V All Rights Reserved Refer to Front Cover v
TM
The Progress Indicators................................................................................................................................ 159

Typical Diagnostic Execution Cycle.............................................................................................................. 160
3DBP Software ............................................................................................................................................. 161
To check the Driver Version .................................................................................................................... 161
Reload the 3DBP driver........................................................................................................................... 161
Reload 3DBP FPGA................................................................................................................................ 162
Check for Error Messages with EventViewer..................................................................................................... 163
Event Examples............................................................................................................................................ 164
Known error events that can be ignored....................................................................................................... 169
3UD3/3UQ3 Server BIOS POST Messages and Codes.................................................................................... 173
BIOS POST Messages ................................................................................................................................. 173
BIOS POST CODES..................................................................................................................................... 177
Recoverable POST Errors....................................................................................................................... 177
Terminal POST Errors............................................................................................................................. 177
VSD4 Server BIOS POST Messages and Codes .............................................................................................. 186
BIOS POST Messages ................................................................................................................................. 186
BIOS POST CODES..................................................................................................................................... 190
Recoverable POST Errors....................................................................................................................... 190
Terminal POST Errors............................................................................................................................. 190
Intel Confidence Tests for S2/S3 version 3 (p/n 4535 671 02401) .................................................................... 199
Troubleshoot S2/S3 version 4 and version 5 ..................................................................................................... 202
LED Information for the Intel SE7520jr2 motherboard.................................................................................. 202
BIOS POST Beep Codes for the Intel SE7520jr2 motherboard ................................................................... 203
Troubleshoot the 2UQ server............................................................................................................................. 204
Intel® Light Guided Diagnostics ................................................................................................................... 205
System ID LED and System Status LED................................................................................................. 206
DIMM Fault LEDs .................................................................................................................................... 208
Processor Fault LED ............................................................................................................................... 209
5-Volt Standby LED................................................................................................................................. 210
Post Code Diagnostic LEDs .................................................................................................................... 211
BIOS POST Beep Codes for the Intel S5000PAL motherboard ................................................................... 217
POST Error Messages and Handling ........................................................................................................... 218
CSIP Level 1 4535 673 63861 © 2009 Koninlijke Philips Electronics N.V All Rights Reserved Refer to Front Cover vi
TM
Troubleshoot the RAID Array ............................................................................................................................. 222

Check Disk Configuration and Health........................................................................................................... 223
Using Device Manager ................................................................................................................................. 225
Using Disk Manager ..................................................................................................................................... 226
Using Event Viewer ...................................................................................................................................... 227
CIRS event log ........................................................................................................................................ 227
SYSTEM event log .................................................................................................................................. 228
Adaptec "SCSISelect Utility" to run Non-destructive Media Tests ................................................................ 231
DiskTest for S1 SCSI RAID Array................................................................................................................. 236
Running the test ...................................................................................................................................... 236
Log Files.................................................................................................................................................. 239
Transfer Raw Data to and from CIRS ................................................................................................................ 240
Procedure for Brilliance 2.3 or later software................................................................................................ 240
Modify UTS Browser Shortcut ................................................................................................................. 241
Download Raw Data from CIRS.............................................................................................................. 242
Upload Raw Data to CIRS....................................................................................................................... 245
Procedure for Brilliance 2.2.x........................................................................................................................ 247
Using the component .............................................................................................................................. 247
Procedure for Brilliance 2.2.x software and five-digit study numbers ........................................................... 261
Get Raw Data from CIRS ........................................................................................................................ 261
To Store Raw Data on CIRS: .................................................................................................................. 265
CIRS Service Tools ...................................................................................................................... 266

Introduction ........................................................................................................................................................ 266
CIRS Service Vx.x.x.x CD ............................................................................................................................ 266
Philips, System Diagnostic Utilities (PN SOFGR-064) Rev. 16 or higher..................................................... 267
Booting from the CD................................................................................................................................ 267
Philips, System Diagnostic Utilities (PN SOFGR-064) Rev. 21 or higher..................................................... 269
Booting from the CD................................................................................................................................ 269
CSIP Level 1 4535 673 63861 © 2009 Koninlijke Philips Electronics N.V All Rights Reserved Refer to Front Cover vii
Introduction
Introduction
The Common Image Reconstruction System™ (CIRS) is the “Image Generation” process located between the Host
Computer and the Gantry.
There are two Racks: The CIRS Rack consists of Horizontal servers and a Network Switch, while the Combined Rack
Console consists of the Host PC and one Vertical S1 server. The Vertical S1 servers do not use the Network Switch
since there is only one server.
The Server(s) are used for receiving Log MDU from the Gantry (RCOM), Reconstructing the data, and transfer final
images to the Host Computer via LAN.
The Network Switch on the CIRS Rack is used for internal communication between the Servers (transfer images/
RAW), and for external communication with the Host Computer and Remote Reconstruction station. The
Communication between the devices runs via 1Gb LAN.
Server 3
Server 2
Server 1
Network
switch Combined Rack Console Host PC and
Vertical Server
CIRS ON/OFF
CIRS Rack with Horizontal servers and Network Switch
CSIP Level 1 4535 673 63861 © 2009 Koninlijke Philips Electronics N.V All Rights Reserved Refer to Front Cover 1
Introduction
The following Server configurations are available for CIRS:

• One Server configuration (VS1, VS1 Plus, VSD4, or S1 only) – performance 6 Img/sec for VS1 and S1, 20 Img/sec
for VS1 Plus, VSD4. The One Server configuration has the Acquisitor, and either 3DBP Board - 2 ASIC
configuration on page 64 or 3DBP Board - 6 ASIC configuration on page 62 + Power Board.
• Two Server configuration (S1 + S2) - performance 20 Img/sec (Acquisitor in S1, 3DBP Board - 6 ASIC
configuration on page 62 + Power Board in S2)
• Three Server configuration (S1 + S2 + S3) - performance 20+ Img/sec (Acquisitor in S1, 3DBP Board - 6 ASIC
configuration on page 62 + Power Board in S2). This older configuration is no longer available, but does exist out in
the field.
Horizontal Servers:
• S1 version 1 on page 12
• S1 version 2 on page 15
• 3UD3 version 1 and version 2 on page 22
• 3UQ3 on page 26
• S2/S3 version 3 on page 30
• S2/S3 version 4 and version 5 on page 33
• 2UQ on page 36
Vertical Servers:
• Vertical S1 version 1 on page 42
• Vertical S1 version 2 and VS1 Plus on page 54. VS1 Plus is a 20 ips system with faster processors, more memory,
and a 6 ASIC 3DBP board. The VS1 Plus requires Brilliance 2.0 software or higher.
• VSD4 on page 57. The VSD4 is a vertical S1 server with dual-core processors. The VSD4 version 1 requires
Brilliance 2.2.5 software. The VSD4 version 2 and version 3 requires Brilliance 2.3 software or higher.
Introduction
CIRS Rack Flow Diagram
*Server motherboards vary by model.

See Horizontal Servers Functional
Description on page 11 for more infor-
mation in the server models.
Introduction
Combined Rack Console Flow Diagram
*Server motherboards vary by model.

See Vertical Servers Functional
Description on page 41 for more
information in the server models.
Introduction
Power down procedure

Use the following steps to power down all CIRS Servers:
1. Open CIRS folder on the Host PC Desktop.
2. Double-click on the icon for the server you want to power down (Recon S-1, Recon S-2, Recon S-3).
3. Click OK at the security warning.
4. Log on as “philips_service”.
5. Click OK.
6. On the server Desktop, right-click on the Windows Taskbar and select Task Manager.
7. On Task Manager, click Shut Down > Turn Off.
8. Click Yes on any messages that appear.
9. Click OK on the Remote Desktop Disconnected prompt.
NOTE During shutdown, the Remote Desktop connection will automatically disconnect and return you to the
Host desktop.
10. Repeat for the other servers in your configuration.
Introduction
S1 Server Recon Processes

There are Recon processes that start automatically after boot on S1 servers.
• SuprSvc.exe
• Supervisor.exe
• SeriesProcess.exe
• ImageProcess.exe
• ImgNodeSvr.exe
Introduction
Supervisor Process
The Supervisor’s main task is to communicate with the Host. It receives messages from the host that can be seen in the
event viewer as “h2r…”.These messages that are received from the host let the Supervisor know what type of work
needs to be done – there are 3 types of work requested by the Host:
• Acquisition (ACQ)
• Reconstruction (RCN)
• Administrative/Misc.
Most of the time, the Host will request 2 types of work to be done, since a normal scan consists of the Acquisition (X-
rays on and collecting data) and Reconstruction (Making images). To handle an Acquisition, the Supervisor will create a
SeriesProcess to do the acquisition-related work. To handle a Reconstruction, the Supervisor will create an
ImageProcess to do the reconstruction-related work.
Introduction
Series Process
Introduction
Image Process
To handle a reconstruction, Supervisor creates one ImageProcess per reconstruction requested. This one
ImageProcess will then create an ImgNodeSvr on each of the servers (S1, S2, S3). ImgNodeSvr is the “worker”. It is
made up of the different software components that perform all of the reconstruction processing.
The type of reconstruction is specified by the MDU (sent by the Host).
Introduction
Theory of Operation
For a detailed explanation of CIRS Theory of Operation, visit InCenter and go to Computed Tomography > Brilliance
Series > Brilliance 16 Power [or Brilliance 6/10/16 (air)] > System Reference > Reference > Brilliance CT Theory of
Operation - Interactive Knowledge Index.
Horizontal Servers Functional Description
Overview
The following servers and components are covered in this section. To determine what servers you have in the system, check the part number sticker located either on the top of the server, or on the side of the server.
S1 Servers S2/S3 Servers

S1 version 1 (p/n 4535 670 25001), see page 12 S2/S3 version 3 (p/n 453567102401), see page 30
3UD3 version 1 (p/n 453567411961), see page 22 2UQ version 1 (p/n 453567412002), see page 36
3UD3 version 2 (p/n 453567411963), see page 22 2UQ version 2 (p/n 453567412002), see page 36
3UQ3 version 1 (p/n 453567411962), see page 26 2UQ version 3 (p/n 453567412006), see page 36
3UQ3 version 2 (p/n 453567411964), see page 26
3UQ3 version 3 (p/n 453567411966), see page 26
CIRS Rack Components

Network Switch, see page 39
S1 version 1
The S1 version 1 server (p/n 453567025001) has an Intel SE7501BR2 motherboard. For more technical information on
this motherboard, visit www.Intel.com, and search for “SE7501BR2“.
3.6 GHz Intel Xeon Processor 36 GB SCSI Hard

Memory Modules, 4GB, DDR
Modules (Qty. 2) Drive (Qty. 3)
Slot 5 for
Acquisitor
Board
IDE CD-ROM
80 GB ATA133
Hard Drive
Intel SE7501BR2 motherboard Block Diagram

The following block diagram is from the Intel
Technical Product Specification for the
SE7501BR2, which can be found at the
following URL:
http://support.intel.com/support/
motherboards/server/se7501br2/sb/CS-
007221.htm
S1 version 1 - Network Interface Controller

The SE7501BR2 server board (server S1) supports a 10Base-T/100Base-TX Fast Ethernet Network Controller based
on the Intel 82550PM controller (NIC1) and 10Base-T/100Base-TX/1000Base-TX Gigabit Ethernet Network Controller
based on the Intel 82540EM controller (NIC2). NIC1 is the designated Server Management NIC.
NIC Diagnostic LEDs

The 82550PM and 82540EM are highly integrated PCI LAN controllers. The 82550PM (NIC1) drives two LEDs located
on the network interface connector:
• The green LED to the right of the connector indicates network connections when on and transmit/receive activity
when blinking.
• The green LED to the left of the connector indicates 100-Mbps operations when lit and 10-Mbps when off.
The 82540EM (NIC2) drives two LEDs located on the network interface connector:
• The green LED to the right of the connector indicates network connections when on and
transmit/receive activity when blinking.
• The bi-color LED to the left of the connector indicates 1000-Mbps operations when yellow, 100-Mbps when green,
and 10-Mbps when off.
S1 version 2
The S1 version 2 server (p/n 453567342161) has a SuperMicro X6DH8-XG2 motherboard. For more technical
information on this motherboard, visit www.supermicro.com, and search for “X6DH8-XG2“.
NOTE Associated CIRS software for Brilliance 2.0 or higher release is required for this server.
IDE CD-ROM
80 GB SATA
Hard Drive
36 GB SCSI Slot 5 for

Hard Drive Acquisitor
(Qty. 3) Board
3.6 GHz Intel Xeon Processor 512 MB DIMM, DDR2, Memory Modules (Qty. 8)
Modules (Qty. 2)
*Memory must be populated in pairs
SuperMicro X6DH8-XG2 motherboard Block Diagram

The Server board supports a dual-channel gigabit network interface controller based on the Intel 82546EB. This is a
highly integrated PCI LAN Controller. The LAN Controller supports 10/100/1000 operation on both channels, as well as
supports alert-on-LAN functionality. The board supports independent disabling of the two NIC controllers using the
BIOS Setup menu.
NIC Diagnostic LEDs

The Ethernet ports (located beside the VGA port) have two LEDs. See the table for the functions associated with these
LEDs. On each GLAN port, the Left (Yellow) LED indicates activity while the Right LED may be green, orange or OFF to
indicate the speed of the connection.
Right LED
OFF No network connection

Green 100 MHz connection
Orange 1GHz connection
S1 version 3 (p/n 4535 674 02551) with SuperMicro X6HD-XG2 motherboard

The S1 version 3 server (p/n 453567402551) uses the SuperMicro X6DH8-XG2 motherboard, and has a new
orientation for the three RAID drives. For more technical information on this motherboard, visit www.supermicro.com,
and search for “X6DH8-XG2“.
l
512 MB DIMM, DDR2, Memory Modules (Qty. 8)

*Memory must be populated in pairs 3.6 GHz Intel Xeon Processor Modules (Qty. 2)
36 GB SCSI
Hard Drive
(Qty. 3)
Acquisitor
Board in Slot 5
IDE
CD-ROM
80 GB SATA
Hard Drive
S1 version 3 SCSI Drive Configuration and Interconnects

This label appears on the inside of the server cover.
Onboard SCSI Controller

highly integrated PCI LAN Controller. The LAN Controller supports 10/100/1000 operation on both channels. The board
supports independent disabling of the two NIC controllers using the BIOS Setup menu.
NIC Diagnostic LEDs

Right LED

3UD3 version 1 and version 2

The 3UD3 version 1 (p/n 453567411961) and version 2 (p/n 453567411963) servers have a SuperMicro X7DB8-X
motherboard, and Intel Dual-Core Processors. The ‘3U’ refers to the rack height, the ‘D’ signifies “Dual-Core”, and ‘3’
refers to the number of SCSI Drives. Notice on this motherboard, the Acquisitor resides in Slot 6. For more technical
information on this motherboard, visit www.supermicro.com, and search for “X7DB8-X”.
NOTE The 3UD3 version 1 server requires Brilliance 2.2.5 or later software, and the 3UD3 version 2 server
requires Brilliance 2.3 or later software.
1 GB DIMM, DDR2, Fully Buffered, 667 MHz Memory Modules (Qty. 4)
*Memory resides in slots 1A, 2A, 3A, 4A
Intel Xeon 5150 2.6 GHz Dual-Core Processor Modules (Qty. 2)
73.5 GB SCSI
Hard Drive
(Qty. 3)
Acquisitor
Board in Slot 6
80 GB SATA
Hard Drive
IDE CD-ROM
SuperMicro X7DB8-X motherboard Block Diagram
SuperMicro X7DB8-X Back Panel Connectors

1. Keyboard (Purple)
2. PS/2 Mouse (Green)
3. Back Panel USB
4. Back Panel USB
5. COM Port 1 (Turquoise)
6. VGA Port (Blue)
7. Gigabit LAN 1 (NIC1)
3UD3 Network Interface Controller

Intel 82563 Gigabit Ethernet controller supporting two Gigabit LAN ports.
NIC Diagnostic LEDs

Each Gigabit Ethernet LAN port has two LEDs. The Activity LED indicates activity, while the Link LED may be green,
amber or off to indicate the speed of the connection
.
Link LED
OFF No Connection or 10 Mbps

Green 100 Mbps
Amber 1 Gbps
3UD3 SCSI Drive Configuration and Interconnects

3UD3, 3UD5, 3UD8, 3UD12 SCSI DRIVE CONFIGURATION

S1 S1C S1A S1B
ID 1
ID 2
ID 3
ID 4
ID 5
ID 6
ID 8
Ch. A
Slot 7 ID 9
SCSI Controller Cards Slot 2
Slot 1 Ch. B
Ch. A Ch. B ID 10
ID 11
ID 12
ID 13
CABLING:
TERMINATOR
NUMBER OF
SCSI DRIVES
3 5 8 12 CONTROLLER DRIVE B DRIVE A
X X X X AIC-7902, Channel A, Slot 7 (MB) ID 2 ID 1
X AIC-7902, Channel B, Slot 7 (MB) NOT PRESENT ID 3
X X X AIC-7902, Channel B, Slot 7 (MB) ID 4 ID 3
X 39320A, Channel B, Slot 2 (PCI) NOT PRESENT ID 5
X X 39320A, Channel B, Slot 2 (PCI) ID 6 ID 5
X X 39320A, Channel A, Slot 2 (PCI) ID 9 ID 8
X 39320A, Channel A, Slot 1 (PCI) ID 11 ID 10
X 39320A, Channel B, Slot 1 (PCI) ID 13 ID 12
POSITION OF JUMPERS (LEFT TO RIGHT) MAY

JUMPER SETTINGS: VARY DEPENDING ON DRIVE (MAX SHOWN BELOW)
FRONT OF DRIVE
(VIEWED FROM FRONT OF CHASSIS)
LEGEND:
ID 1 ID 8
= INSTALLED
ID 2 ID 9
= NOT INSTALLED
ID 3 ID 10
OPERATION MODE
START COMMAND
ID 4 ID 11
WRITE PROTECT
TERMINATOR
REMOTE LED
BUS WIDTH
RESERVED
RESERVED
ID 1
ID 3
ID 2
ID 0
ID 5 ID 12
ID 6 ID 13 LAB01149 R001
3UQ3
The 3UQ3 version 1 (p/n 453567411962), version 2 (p/n 453567411964), and version 3 (p/n 453567411966) servers
have a SuperMicro X7DB8-X motherboard, and Intel Quad-Core Processors. The ‘3U’ refers to the rack height, the ‘Q’
signifies “Quad-Core”, and ‘3’ refers to the number of SCSI Drives. The Acquisitor resides in Slot 6.
NOTE The 3UQ3 version 1 server requires Brilliance 2.2.5 or later software, and the 3UQ3 version 2 and version
3 servers requires Brilliance 2.3 or later software.
1 GB DIMM, DDR2, Fully Buffered, 667 MHz Memory Modules (Qty. 4) Intel Xeon 5335 2.0 GHz Quad-Core Processor Modules (Qty. 2)
*Memory resides in slots 1A, 2A, 3A, 4A
73.5 GB SCSI
Hard Drive
(Qty. 3)
Acquisitor
Board in Slot 6
80 GB SATA
Hard Drive
IDE CD-ROM
SuperMicro X7DB8-X motherboard Block Diagram

For more technical information on this motherboard, visit www.supermicro.com, and search for “X7DB8-X”.
SuperMicro X7DB8-X Back Panel Connectors

3. Back Panel USB
4. Back Panel USB
6. VGA Port (Blue)
3UQ3 Network Interface Controller

NIC Diagnostic LEDs

.
Link LED

Green 100 Mbps
Amber 1 Gbps
3UQ3 SCSI Drive Configuration and Interconnects

3UD3, 3UD5, 3UD8, 3UD12 SCSI DRIVE CONFIGURATION

S1 S1C S1A S1B
ID 1
ID 2
ID 3
ID 4
ID 5
ID 6
ID 8
Ch. A
Slot 7 ID 9
SCSI Controller Cards Slot 2
Slot 1 Ch. B
Ch. A Ch. B ID 10
ID 11
ID 12
ID 13
CABLING:
TERMINATOR
NUMBER OF
SCSI DRIVES
3 5 8 12 CONTROLLER DRIVE B DRIVE A
X X X X AIC-7902, Channel A, Slot 7 (MB) ID 2 ID 1
X AIC-7902, Channel B, Slot 7 (MB) NOT PRESENT ID 3
X X X AIC-7902, Channel B, Slot 7 (MB) ID 4 ID 3
X 39320A, Channel B, Slot 2 (PCI) NOT PRESENT ID 5
X X 39320A, Channel B, Slot 2 (PCI) ID 6 ID 5
X X 39320A, Channel A, Slot 2 (PCI) ID 9 ID 8
X 39320A, Channel A, Slot 1 (PCI) ID 11 ID 10
X 39320A, Channel B, Slot 1 (PCI) ID 13 ID 12
POSITION OF JUMPERS (LEFT TO RIGHT) MAY

JUMPER SETTINGS: VARY DEPENDING ON DRIVE (MAX SHOWN BELOW)
FRONT OF DRIVE
(VIEWED FROM FRONT OF CHASSIS)
LEGEND:
ID 1 ID 8
= INSTALLED
ID 2 ID 9
= NOT INSTALLED
ID 3 ID 10
OPERATION MODE
START COMMAND
ID 4 ID 11
WRITE PROTECT
TERMINATOR
REMOTE LED
BUS WIDTH
RESERVED
RESERVED
ID 1
ID 3
ID 2
ID 0
ID 5 ID 12
ID 6 ID 13 LAB01149 R001
S2/S3 version 3
The S2/S3 version 3 server (p/n 4535 671 02401) has an Intel SE7501WV2 motherboard. For more technical
information on this motherboard, visit www.intel.com, and search for “SE701WV2“.
Power Supply
IDE CD-ROM
80 GB ATA133
Hard Drive 3DBP and
Power Board
Riser Assembly
(for S2.
3DBP and
Power Board
Plug into here
512 MB DIMM,
DDR266 SDRAM,
Memory Modules
(Qty. 6)
*Memory must be
populated in pairs
EITHER 3.6 GHz Intel Xeon Processor Modules, 512KB L2 cache, 533MHz, S604 (Qty. 2),
OR 3.6 GHz Intel Xeon Processor Modules, 512KB L2 cache, 1MB L3 cache, 533MHz, S604 (Qty. 2)
Intel SE7501WV2 motherboard Block Diagram
DIMM Failure LED

The SE7501WV2 Server provides DIMM Failure LEDs located next to each DIMM slot on the baseboard. The DIMM
Failure LEDs are used to indicate double-bit DIMM errors.
S2/S3 version 3 Network Interface Controller

highly integrated PCI LAN Controller.
The LAN Controller supports 10/100/1000 operation on both channels, as well as supports alert-on-LAN functionality.
The board supports independent disabling of the two NIC controllers using the BIOS Setup menu.
NIC Diagnostic LEDs

The NIC drives two LEDs located on each network interface connector. The link/activity LED (to the left of the
connector) indicates network connection when ON, and Transmit/Receive activity when blinking. The speed LED (to the
right of the connector) indicates as follows:
Right LED:
OFF 10 MHz connection

Amber 1GHz connection
S2/S3 version 4 and version 5

The S2 version 4 (p/n 453567342191) and S2 version 5 (p/n 453567400031) S2 servers have an Intel SE7520JR2
motherboard, which uses a riser card to mount the 3DBP and Power Boards in a 2U chassis. For more technical
information on this motherboard, visit www.intel.com, and search for “SE7520JR2“.
NOTE Associated CIRS software for Brilliance 2.0 or higher release is required for this server.
Fan Control Board

The Version 5 server has a
IDE CD-ROM Drive newer design fan control
board needed to help
80 GB SATA Hard power supply loading while
Drive maintaining the ability to
shut off the back projector
fans when the 3DBP is not
installed.
The fan control board in
Version 4 allows the 3DBP
fans to continuously run so
that the power supply sees
a sufficient load during
Filter power up.
3DBP and Power Board

Riser Assembly (S2 servers
only
512 MB DIMM, DDR2, Memory Modules (Qty. 6)

3.6 GHz Intel Xeon Processor Modules (Qty. 2) for a total of 3 GB
Intel® Server Board SE7520JR2 – I/O Panel Features
1. PS/2* keyboard and mouse connectors 6. Post-code diagnostic LEDs

(LSB, bit1, bit2, MSB)
2. RJ45 video connector
7. System-ID LED
3. Dual Ethernet connectors (NICs)
8. Optional external SCSI connector
4. Video connector
(not applicable to our system)
5. Dual USB connectors
9. System status LED
S2/S3 version 4 and version 5 Network Interface Controller
NIC LEDs
The LEDs at the right and left of each NIC (#3 in the picture above) provide the following information.
LED Color LED State Description

Off No network connection
Left LED Solid Amber Network connection in place
Blinking Amber Transmit/receive activity
10 Mbps connection (if left LED is on or
Off
blinking)
Right LED
Solid Amber 100 Mbps connection
Solid Green 1000 Mbps connection
Fan Control Board

This board controls power to the fans that cool the 3DBP assembly. The control board is present on all S2/S3 servers,
whether there is a 3DBP assembly installed or not. The P7 plug on the 3DBP power cable either plugs into the 3DBP
power board, or plugs into the J3 connector on the Fan Control Board. If P7 is not plugged into J3, the fans are
enabled. If P7 is plugged into J3, the fans are disabled.
NOTE If you have a version 4 server, verify that J3 on the fan control board is unplugged! The fans need to run at
all times to provide an additional load to the power supply. If the fans are not running, power up issues may
occur.
The Version 5 server has a newer design fan control board needed to help power supply loading while
maintaining the ability to shut off the back projector fans when the 3DBP is not installed.
Fans
Fan Control Board J3 Connector
Figure 1: Fan Control Board with J3 Disconnected
2UQ
The 2UQ version 1 (p/n 453567412002), version 2 (p/n 453567412004), and version 3 (p/n 453567412006) servers
have an Intel S5000PAL motherboard, and Intel Quad-Core Processors. The 2UQ is used as an S2/S3 server The ‘2U’
refers to the rack height, and the “Q” signifies ‘Quad-Core’. For more technical information on this motherboard, visit
www.intel.com, and search for “S5000PAL“.
1 GB DIMM, DDR2, Fully Buffered, 667 MHz Memory Modules (Qty. 4)
*Memory resides in slots A1, B1, C1, D1
Intel Xeon 2.0GHz Quad-Core Processor Modules (Qty. 2)
IDE CD-ROM or
SATA DVD-ROM
80 GB SATA
Hard Drive
3DBP and Power Board Riser Assembly

Fan Control Board
(S2 servers only, not in S3 servers)
Intel® Server Board S5000PAL – I/O Panel Features
Motherboard
A. PS/2 Mouse
B. PS/2 Keyboard
C. Serial Port B
D. NIC port 1 (1 Gb)
E. NIC port 2 (1 Gb)
F. Video
G. USB port 1
H. USB port 2
2UQ Network Interface Controller

The LEDs at the right and left of each NIC provide the following information.
LED Color LED State Description

Off No network connection
Left LED Solid Amber Network connection in place
Blinking Amber Transmit/receive activity
Off 10 Mbps connection (if left LED is on or blinking)
Right LED Solid Amber 100 Mbps connection
Solid Green 1000 Mbps connection
Fan Control Board

This board controls power to the fans that cool the 3DBP assembly. The control board is present on all S2/S3 servers,
whether there is a 3DBP assembly installed or not. The P7 plug on the 3DBP power cable either plugs into the 3DBP
power board, or plugs into the J3 connector on the Fan Control Board. If P7 is not plugged into J3, the fans are
enabled. If P7 is plugged into J3, the fans are disabled.
Fans
Fan Control Board J3 Connector
Figure 2: Fan Control Board with J3 Disconnected
Network Switch
Netgear GS516T
The front panel of the Model GS516T 16-Port Copper Gigabit Switch
contains the following LEDs that correspond to each network port:
• Activity (Rx/Tx)
• FDX/COL (full-duplex/collision)
• 10Mbps speed
Front Panel
The front panel of the Model GS516T switch contains the following LEDs:.
Label Color Activity Description

Power Green On Power is supplied to the switch.
Off Power is disconnected.
FDX/COL Green On The port is operating in full-duplex mode.
Yellow Off The port is operating in half-duplex mode.
Blinking Data collisions are occurring on the port. In a full-duplex environment, there is no
collision. In a half-duplex environment, some collisions are normal.
Activity Green Blinking Packet transmission or reception is occurring on the port.
1000M Green On A valid 1000 Mbps link is established on the port.
Off A link is not established on the port.
Rear Panel
The rear panel of the Model GS516T switch has fans for
cooling and a standard AC power receptacle for the
supplied power cord.
Netgear GS116 (p/n 453567402301)
This network switch is a replacement for the Model

GS516T. This switch is functionally the same as Model
GS516T. However, this switch has an external power
supply that mounts to the rack with the switch. The whole
switch (including power supply) is an FRU.
Vertical Servers Functional Description
Overview
The various Vertical S1 (VS1) servers are identical in functional configuration to the rack-mounted S1 version 1 and S1
version 2 servers used in the CIRS rack. The servers use the same motherboard, CD-ROM, System disk drive, and
SCSI array components as the S1s. It uses the same memory DIMMs as well, but the base configuration is populated
with 2GB of DDR SDRAM, as opposed to 4GB in the standard S1. An upgrade kit is available to extend the memory to
4GB. The components are mounted in a workstation-style enclosure, with access to the CD-ROM from the front of the
enclosure, and access to the internal components of the server via a removable side panel.
The following servers are covered in this section. To determine what servers you have in the system, check the part
number sticker located either on the top of the server, or on the side of the server. Click on the page links below to go to
that server’s page.
S1 Servers
Vertical S1 version 1 (p/n 453567061721), see page 42
Vertical S1 version 2 (p/n 453567307811), see page 54
VSD4 version 1 (p/n 453567412011), see page 57
Vertical S1 version 1
There are three revisions of the VS1 versions 1 server (p/n 453567061721): Rev A, Rev B, and Rev. C. All three version
use the same internal components (Intel "Bryson" mother board, drives, cables, fans…etc)., with the main difference
being the new enclosure designed by Granite Microsystems that has an auto sensing power supply, eliminating the
need for the voltage select switch. The enclosure is now in line with other CIRS servers that include the more
accessible air filters. Rev. C allowed the supplier to use an alternate Xeon CPU with a 1 MB L3 cache. This was due to
an end-of-life situation on the original 512K L2 cache Xeon processor. This does not mean that if the server is at rev. C
you will have 1MB L3 cache, it means that you could have either or. The processor configuration can be verified, if
necessary, by gaining access to BIOS during bootup by selecting F2, then under the "Main" heading, arrow down to
"Processor Settings" and hit <return>; the processor type and cache size will be displayed. System performance will be
virtually the same between the two different configurations.
Old Rev. A "Antec Chassis" server New 453567061721 Rev. B in Combined Rack Console (CRC)
Rev. A enclosure and layout
Enclosure CD-ROM Access Removable side panel

Figure 1: VS1 version 1 Rev. A enclosure
Two Intel Xeon 2.8 GHz, 512 MB L2 cache processors
ECC DDR266 SDRAM Memory. The

memory slots must be populated in pairs.
The VS1 base configuration has 2GB of
memory, using two 1GB DIMMs. The
memory can be expanded to 4GB using a
2GB memory upgrade kit.
Slot 1: Acquisitor Board

Slot 2: Power Board (only for 6 ASIC 3DBP)
Slot 3: Either 2 ASIC or 6 ASIC 3DBP Board.
*The 2 ASIC 3DBP does not require a Power

Board.
Cooling fans for 3DBP Power connection to Power Board
Figure 2: Rev A layout
PCI slots
There are four PCI-X (64b/100MHz) slots on the motherboard, and two PCI slots (32b/33MHz). The top slot (when
vertically oriented) is Slot 1, the bottom slot is Slot 6.
Figure 3: PCI slots on motherboard

The slots are populated in the following manner:
Slot # Slot Type Contents

1 PCI-X 100MHz Acquisitor
2 PCI-X 100MHz 3DBP Power Board (mechanical connection)
3 PCI-X 100MHz 3DBP
4 PCI-X 100MHz None
5 PCI 32b, 33MHz None
6 PCI 32b, 33MHz None
SCSI
The SCSI interface is provided by the on-board Adaptec AIC-7901, which provides a single channel U320 interface.
LAN
The motherboard provides a 10/100 MB LAN connection (NIC1), and a 10/100/1000 MB connection (NIC2) (Figure 4
on page 46).
Figure 4: LAN connections
System disk drive

There is one IDE disk drive in the server. The drive contains the OS and application software. It is a 80GB, ATA/133
8MB buffer, 7200 RPM drive, Maxtor P/N 6Y080P0. The disk drive is the master on the IDE cable that is connected to
the Primary IDE connector (Figure 6 on page 48) on the motherboard.
Figure 5: Disk drives
Figure 6: Primary IDE connector
CDROM
The CDROM used in the VS1 is the LiteOn 52X CDROM. It is the slave on the IDE cable connected to the IDE disk
drive.
Figure 7: CDROM drive
SCSI array
The SCSI disk array consists of three Fujitsu Model MAS3367NP 36GB, 15000 RPM SCSI U320 hard drives (Figure 5
on page 47). They are all attached to the same single channel SCSI port on the motherboard.
Figure 8: SCSI port on motherboard
The SCSI IDs on the disk drivers are jumpered to use IDs 1, 2, 3. The location of each particular SCSI ID is shown
below:
Figure 9: SCSI ID location
Rev B and C enclosure and layout
80 GB SATA Hard Drive
36 GB SCSI Hard
Drive (Qty. 3)
ECC DDR266 SDRAM Memory. The

memory slots must be populated in
pairs. The VS1 base configuration
has 2GB of memory, using two 1GB
DIMMs. The memory can be Two Intel Xeon 2.8 GHz,
expanded to 4GB using a 2GB 512 MB L2 cache
memory upgrade kit. processors
Slot 1: Acquisitor Board

Slot 2: Power Board (only for 6 ASIC 3DBP)
Slot 3: Either 2 ASIC or 6 ASIC 3DBP Board.
*The 2 ASIC 3DBP does not require a Power

Board.
IDE CD-ROM
3DBP Cooling Fans
Intel SE7501BR2 Motherboard

The VS1 version 1 Rev A, B, and C use the
Intel SE7501BR2 dual Xeon motherboard. The
motherboard uses the Intel E7501 chip set.
The following block diagram is from the Intel
Technical Product Specification for the
SE7501BR2, which can be found at the
following URL:
http://support.intel.com/support/
motherboards/server/se7501br2/sb/CS-
007221.htm
Figure 10: Memory populated with 4 X 1GB

DIMMs
Vertical S1 version 2 and VS1 Plus

The Vertical S1 version 2 (p/n 453567307811) and VS1 Plus (p/n 453567348651) servers use the SuperMicro X6DH8-
XG2 motherboard. For more technical information on this motherboard, visit www.supermicro.com, and search for
“X6DH8-XG2“.
36 GB SCSI Hard
Drive (Qty. 3)
80 GB SATA Hard Drive
512 MB DIMM, DDR2,

Memory Modules:
VS1 V2 - Qty. 4, 2GB total
VS1 Plus - Qty. 8, 4GB total
*Memory must be VS1 V2: Either 2.8 GHz
populated in pairs or 3.6 GHz Intel Xeon
Processor Modules
(Qty. 2)
Slot 5 for Acquisitor Board VS1 Plus: 3.6 GHz Intel
Xeon Processor Modules
(Qty. 2)
Slot 3 for:
VS1 Plus - 1 channel Power
Board for 6 ASIC 3DBP
Slot 2 for:
VS1 V2 - 2 ASIC 3DBP
VS1 Plus - 6 ASIC 3DBP
IDE CD-ROM
Vertical S1 version 2 and VS1 Plus Network Interface Controller

highly integrated PCI LAN Controller. The LAN Controller supports 10/100/1000 operation on both channels, as well as
supports alert-on-LAN functionality. The board supports independent disabling of the two NIC controllers using the
BIOS Setup menu.
NIC Diagnostic LEDs

Right LED

VSD4
The VSD4 version 1 (p/n 453567412011), version 2 (p/n 453567412012), and version 3 (p/n 453567412013) servers
have a SuperMicro X7DBE-X motherboard with Intel Dual-Core processors. The ‘D’ signifies “Dual-Core”, and ‘4’ refers
to the number of SATA Drives. The Acquisitor resides in Slot 5.
NOTE The VSD4 version 1 server requires Brilliance 2.2.5 or later software, and the VSD4 version 2 and version 3
servers requires Brilliance 2.3 or later software.
120 or 160 GB SATA

RAID Drive (Qty. 4) 80 GB SATA System
Hard Drive
512 MB DIMM, DDR2,
Fully Buffered, 667 MHz
Memory Modules (Qty. 2).
Resides in slots 3A and 4A. Intel Xeon 5110 1.6GHz
Dual-Core or 5205
1.86GHz Processor
1 GB DIMM, DDR2, Fully Modules (Qty. 2)
Buffered, 667 MHz
Memory Modules (Qty. 2).
Resides in slots 1A and 2A.
Acquisitor Board in Slot 5
Slot 3 for 1 channel Power

Board for 6 ASIC 3DBP
(20 ips config)
Slot 2 for:
6 ASIC 3DBP (20 ips config)
2 ASIC 3DBP on (6 ips config)
IDE CD-ROM Or
SATA DVD-ROM
SuperMicro X7DBE-X motherboard Block Diagram

For more technical information on this motherboard, visit www.supermicro.com, and search for “X7DBE-X”.
SuperMicro X7DBE-X Back Panel Connectors

3. Back Panel USB
4. Back Panel USB
6. VGA Port (Blue)
VSD4 Network Interface Controller

NIC Diagnostic LEDs

.
Link LED

Green 100 Mbps
Amber 1 Gbps
VSD4 SATA Drive Configuration
Acquisitor and 3DBP Functional Description
Acquisitor Board Block Diagram

R T
X T T R R X
_ X X X X _
Fiber E _ _ _ _ E Fiber
Optic N A C A C N Optic
RCV A C O C O A XMT
C Q M Q M C
Q O M O O Q
O K O K K O
K K K
HDMP- R HDMP- T
1034A X X
_ 1032A _
REFCLK Receiver C Transmitte C
40-62.5MHZ 16 L L
C/D
K 16 K
C/D
RX- TX-
7
RSND_CNT CTRL CTRL
Reading Timeout
RSND_ERR CRC 32
Frame,
Control ODL PCI GEM
Verify, Append
ODL_EN Readin Status CSR CSR CSR CRC,
g Registers Registers Rate
RESEND
DISABLED
Timer, Control
16
HEADER
Validation
Header Error
Overflow Error Register
16 Interface
READIN DMAR DMAR PCI Write PCI Read
Memory PCI DMA
G 64 64 FIFO 64 64 FIFO
Controller Controller
FIFO Sstatus Sstatus Sstatus
PCI Core
MEMORY CLK DCM 80Mhz
66Mhz
64
PCICLK
SDRAM 66MHZ
4 x 16M x16 PCI 64-Bit, 66Mhz
Note:. Shaded functions are used

in Gantry Emulator mode only.
3DBP Board - 6 ASIC configuration

The 6 ASIC 3DBP subsystem consists of a Power Board and a 3DBP Board.
Both the 3DBP and Power Boards are full size
PCI cards that plug into the host PC's PCI slots.
The Power Board has no electrical connection to
the PCI bus. The PCI slot is used for mechanical
mounting of the Power Board only.
The Power Board receives its input power from
the PC's switching power supply. The Power
Board has switching regulators that provide the
3DBP with the 4 desired voltages; 1.2V, 1.5V,
1.8V and 3.3V.
The 3DBP has a power cable harness that plugs
into a connector on the Power Board. The Power
Board has 1 connector for input power and 1
connector for output power.
The 3DBP must always have a Power Board
connection to function properly.
Although the 3DBP receives its 3.3V power from
the PCI connector, the DSPs require that the 1.2V
core power be provided prior to the 3.3V for the I/
O power. Therefore, the Power Board provides
3.3V that is used exclusively for the DSP I/O
power. Furthermore, the Power Board provides
sequencing of the power so that the 1.2V is
powered-up prior to the 3.3V.
The PC communicates with the 3DBP via the PCI
bus, refer to Figure 2 on page 63. The 3DBP
implements the PCI interface in an FPGA. The
FPGA implements PCI configuration space
registers to control the 3DBP's interaction with the
PCI bus. The FPGA also provides 12 channels of Figure 1: Power Board Block Diagram
DMA with FIFO buffering to move data and
communicate between the PCI bus and the DSPs.
The DMA channels are programmed via control registers that are mapped into PCI I/O Space. The PC host processor
has access to the DMA control registers, the DSPs do not. The DMA channels move data between PCI Memory Space
locations and the DSP link ports. The 12 DMA channels are dedicated as 6 PCI to DSP link port transfers (one channel
dedicated for each DSP) and 6 DSP link port to PCI transfers (again, one for each DSP). There are 2 additional DMA
channels dedicated to diagnostics, which are referred to as the loopback channels. One of the channels move data
between PCI Memory Space and the loopback FIFO internal to the FPGA. The other channel moves data between the
loopback FIFO and PCI Memory Space.
Figure 2: 6 ASIC 3DBP Board Block Diagram

The DSPs are used to provide the intelligence to communicate with the PC and manage the operation of the
backprojection ASICs. Each DSP communicates with a single ASIC via the DSP's External Port. There is also SDRAM
on each DSP's External Port for data buffering. The DSP controls the ASIC operation through memory mapped control
registers in the ASIC. Data is passed to/from the ASIC by either memory mapped writes/reads by the DSP or directly
between the ASIC and SDRAM by fly-by DMA across the External Port utilizing the DSP's internal DMA controller.
3DBP Board - 2 ASIC configuration

The 2 ASIC configuration is achieved by using a different PCB from the 6 ASIC board. The 2 ASIC board is referred to
as the 3DBP_LC. The PCB is laid out to support a maximum of 2 ASICs. The functions of the Power Board are
integrated onto the 3DBP_LC, so the Power Board is not required. All power for the 3DBP_LC is received from the PCI
connector. Furthermore, the FPGA is a smaller capacity device so a different FPGA file is required from that used for
the 6 ASIC boards.
Figure 3: 2 ASIC 3DBP Board Block Diagram
CIRS Server Configuration and Management
This section details the BIOS settings for each server, and how to check them.
• Original S1 Servers: VS1/S1 on page 66
• Replacement S1 Servers: S1 V2, S1 V3, VS1 V2, and VS1 Plus on page 67
• 3UD3/3UQ3 on page 74
• VSD4 on page 82
• S2/S3 Server version 3 with Intel SE7501WV2 motherboard on page 90
• S2/S3 versions 4 and 5 with Intel SE7520JR2 motherboard on page 92
• 2UQ on page 100
NOTE To determine what servers you have in the system, check the part number sticker located either on the
top or side of the server, and reference the following table:
S1 Servers Vertical S1 Servers S2/S3 Servers

S1 version 1 (p/n 4535 670 25001) Vertical S1 version 1 (p/n 453567061721) S2/S3 version 3 (p/n 453567102401)
S1 version 2 (p/n 4535 673 42161) Vertical S1 version 2 (p/n 453567307811) S2/S3 version 4 (p/n 453567342191)
S1 version 3 (p/n 4535 674 02551) VSD4 version 1 (p/n 453567412011) S2/S3 version 5 (p/n 453567400031)
3UD3 version 1 (p/n 453567411961) VSD4 version 2 (p/n 453567412012) 2UQ version 1 (p/n 453567412002)
3UD3 version 2 (p/n 453567411963) VSD4 version 3 (p/n 453567412013) 2UQ version 2 (p/n 453567412002)
3UQ3 version 1 (p/n 453567411962) VSD4 version 1 (p/n 453567412011) 2UQ version 3 (p/n 453567412006)
3UQ3 version 2 (p/n 453567411964)
3UQ3 version 3 (p/n 453567411966)
Original S1 Servers: VS1/S1

To control and manage the configuration of the VS1 (p/n 4535 670 61721) and S1 (p/n 4535 670 25001) servers,
disconnect the monitor, keyboard, and mouse from the Host, then attach them to the CIRS server.
Check BIOS Version

1. Attach a Monitor, Keyboard, and Mouse to the server.
2. Go into BIOS setup by pressing F2 at boot up.
3. On the BIOS menu, select Server > System Management.
4. The minimal required version of BIOS/BMC/FRU/SDR should be:
Server BIOS BMC FRU/SDR What actually appears:

VS1/S1 (SE7501BR2) P15-0074 1.18 5.6.I SBR20.86B.0074.P15
!
WARNING Be extremely careful when attempting to inspect or make changes to the BIOS
settings!
Replacement S1 Servers: S1 V2, S1 V3, VS1 V2, and VS1 Plus

To control and manage the configuration of the following S1 servers, disconnect the monitor, keyboard, and mouse from
the Host, then attach them to the CIRS server. The following servers all have the SuperMicro X6DH8-XG2
motherboard.
• S1 V2 (p/n 453567342161)
• S1 V3 (p/n 453567402551)
• VS1 V2 (p/n 453567307811)
• VS1 Plus (p/n 453567348651)
!
settings!
NOTE You must have a monitor, keyboard, and mouse attached to the server
• To view the current version of BIOS on the server, press the <Tab> key while Server is booting up. You should see:
X6DH8-XG2/X6DHE-XG2 BIOS Rev 1.2C
• If you receive a replacement server, you may want to check the BIOS settings. To access the BIOS Setup press
<Delete> key while Server is booting up.
Restore BIOS
If the BIOS settings appear to be in question, you can restore the BIOS by:
• Booting the server from the “Philips, System Diagnostic Utilities (PN SOFGR-064)” CD version 16 or later.
• When the server boots, select BIOS Update from the menu. The program will interrogate the motherboard, and
then download the correct BIOS for it.\
Bios Settings for S1 V2, S1 V3, VS1 V2, VS1 Plus (X6DH8-XG2 motherboard)
Figure 1: S1/VS1 with SuperMicro X6DH8-XG2 motherboard BIOS Main Tab
Figure 2: S1/VS1 with SuperMicro X6DH8-XG2 motherboard BIOS Advanced Tab - Boot Features, Memory
Cache, and PCI Configuration
Figure 3: S1/VS1 with SuperMicro X6DH8-XG2 motherboard BIOS Advanced Tab - PCI Configuration continued
Figure 4: S1/VS1 with SuperMicro X6DH8-XG2 motherboard BIOS Advanced Tab - Chipset Control, Processor
Options, I/O Device Configuration, and DMI Event Logging
Figure 5: S1/VS1 with SuperMicro X6DH8-XG2 motherboard BIOS Advanced Tab - Console Redirection and
Hardware Monitor
Figure 6: S1/VS1 with SuperMicro X6DH8-XG2 motherboard - Advanced Tab Hardware Monitor continued,
Security Tab, and Boot Tab
3UD3/3UQ3
To configure and manage the following servers, you will have to disconnect the monitor, keyboard, and mouse from the
Host, then attach them to the CIRS server:
• 3UD3 version 1 (p/n 453567411961)
• 3UD3 version 2 (p/n 453567411963)
• 3UQ3 version 1 (p/n 453567411962)
• 3UQ3 version 2 (p/n 453567411964)
• 3UQ3 version 3 (p/n 453567411966)
!
settings!
NOTE You must have a monitor, keyboard, and mouse attached to the server.
X7DB8-X BIOS Rev 1.2
• If you receive a replacement server, you may want to check the BIOS settings (see BIOS Settings for 3UD3/3UQ3
on page 75). To access the BIOS Setup press <Delete> key while Server is booting up.
Restore BIOS
Use the Philips, System Diagnostic Utilities (PN SOFGR-064) Rev. 21 or later CD to restore BIOS setting to the
recommended default settings. When complete, reboot the server and immediately remove the disk. press the <Tab>
key during boot-up to gain access to the system setup and verify the BIOS parameter settings as outlined in BIOS
Settings for 3UD3/3UQ3 on page 75.
BIOS Settings for 3UD3/3UQ3
Figure 7: 3UD3/3UQ3 BIOS Main Tab
Figure 8: 3UD3/3UQ3 BIOS Advanced Tab - Boot Features, Memory Cache, and PCI Configuration
Figure 9: 3UD3/3UQ3 BIOS Advanced Tab - PCI Configuration continued
2.0 GHz is for the quad-core processors.

The dual-core processors are 2.6 GHz.
Figure 10: 3UD3/3UQ3 BIOS Advanced Tab - Advanced Chipset Control and Advanced Processor Options
Figure 11: 3UD3/3UQ3 BIOS Advanced Tab - I/O Device Configuration, DMI Event Logging, and Console
Redirection
Figure 12: 3UD3/3UQ3 BIOS Advanced Tab - Hardware Monitor
DVD-ROM for 3UQ3 version 3 server
Figure 13: 3UD3/3UQ3 BIOS Security and Boot Tabs
VSD4
To configure and manage the VSD4 version 1 (p/n 453567412011), version 2 (p/n 453567412012), and
version 3 (p/n 453567412013) servers, you will have to disconnect the monitor, keyboard, and mouse from the Host,
then attach them to the CIRS server.
!
settings!
NOTE You must have a monitor, keyboard, and mouse attached to the server.
X7DBE-X BIOS Rev 1.2
• If you receive a replacement server, you may want to check the BIOS settings (see BIOS Settings for VSD4 on
page 83). To access the BIOS Setup press <Delete> key while Server is booting up
Restore BIOS
recommended default settings. When complete, reboot the server and immediately remove the disk. press the <Tab>
key during boot-up to gain access to the system setup and verify the BIOS parameter settings as outlined in BIOS
Settings for VSD4 on page 83.
BIOS Settings for VSD4
Figure 14: VSD4 BIOS Main Tab
Figure 15: VSD4 BIOS Advanced Tab - Boot Features, Memory Cache, and PCI Configuration
Figure 16: VSD4 BIOS Advanced Tab - PCI Configuration continued
Figure 17: VSD4 BIOS Advanced Tab - Advanced Chipset Control and Advanced Processor Options
Figure 18: VSD4 BIOS Advanced Tab - I/O Device Configuration, DMI Event Logging, and Console Redirection
Figure 19: VSD4 BIOS Advanced Tab - Hardware Monitor
DVD-ROM for VSD4 version 3 server
This is the system hard drive.
Figure 20: VSD4 BIOS Security and Boot Tabs
S2/S3 Server version 3 with Intel SE7501WV2 motherboard

To control and manage the configuration of the S2/S3 version 3 (p/n 4535 671 02401) servers, disconnect the monitor,
keyboard, and mouse from the Host, then attach them to the CIRS server.
Check BIOS Version

4. The minimal required version of BIOS/BMC/FRU/SDR should be:
Server BIOS BMC FRU/SDR What actually appears:

S2/S3 (SE7501WV2) P16-0190 1.19 5.6.A SWVR25.86B.0190.P16
!
settings!
BIOS Parameters for S2/S3 V3 (p/n 4535 671 02401)

If you receive a replacement server, you may want to check the following BIOS settings:
Main Menu
System Time Set to EST
System Date Set Date
Floppy A Not Installed
Advanced Menu
Peripheral Configuration
Diskette Controller Disabled
Front Panel USB Disabled
Advanced Chipset Control
Wake on LAN Enabled
Boot-time Diag Screen Enabled
Numlock ON
S2/S3 versions 4 and 5 with Intel SE7520JR2 motherboard

To configure and manage the version 4 (p/n 453567342191) and version 5 (p/n 453567400031) S2/23 servers, you will
have to disconnect the monitor, keyboard, and mouse from the Host, then attach them to the CIRS server. If you receive
a replacement server, you may want to check the BIOS settings (BIOS Settings for S2/S3 V4 and V5 on page 93).
NOTE This server has the Intel SE7520JR2 motherboard.
Check BIOS Version

4. The minimal required version of BIOS should be:
Server What actually appears:

S2/S3 V4/V5 (SE7520JR2) SE7520JR23.86B.P.08.10.0081
!
settings!
Restore BIOS
recommended default settings. Once the disk boots, select BIOS Update S2V4 4535 673 42191 only to initiate the
process. When complete, reboot the server and immediately remove the disk. Select F2 during boot-up to gain access
to the system setup and verify the BIOS parameter settings as outlined in BIOS Settings for S2/S3 V4 and V5 on page
93.
BIOS Settings for S2/S3 V4 and V5

This applies to the version 4 (p/n 453567342191) and version 5 (p/n 453567400031) S2/S3 servers.
Figure 21: S2/S3 versions 4 and 5 BIOS Main Tab
Figure 22: S2/S3 versions 4 and 5 BIOS Advanced Tab - Processor Configuration and IDE Configuration
Figure 23: S2/S3 versions 4 and 5 BIOS Advanced Tab - IDE Master and IDE Slave
Figure 24: S2/S3 versions 4 and 5 BIOS Advanced Tab - Floppy, Super I/O, USB, PCI, and Memory Configuration
Figure 25: S2/S3 versions 4 and 5 BIOS Boot and Security Tabs
Figure 26: S2/S3 versions 4 and 5 BIOS Server Tab - System Management and Serial Console Features
Figure 27: S2/S3 versions 4 and 5 BIOS Server Tab - Event Log Configuration
2UQ
NOTE This applies to the 2UQ version 1 (p/n 453567412002), version 2 (p/n 453567412004), and version 3 servers
(p/n 453567412006).
To configure and manage the 2UQ server, you will have to disconnect the monitor, keyboard, and mouse from the Host,
then attach them to the CIRS server. If you receive a replacement server, you may want to check the BIOS settings
(BIOS Settings for 2UQ on page 101).
NOTE This server has the Intel S5000PAL motherboard.
Check BIOS Version

4. The minimal required version of BIOS should be:
Server What actually appears:

2UQ S5000.86B.05.00.0070‘
!
settings!
Restore BIOS
recommended default settings. When complete, reboot the server and immediately remove the disk. Select F2 during
boot-up to gain access to the system setup and verify the BIOS parameter settings as outlined in BIOS Settings for
2UQ on page 101.
BIOS Settings for 2UQ
Figure 28: 2UQ BIOS Main Tab
Figure 29: 2UQ BIOS Advanced Tab - Processor Configuration
Figure 30: 2UQ BIOS Advanced Tab - Memory Configuration and ATA Controller Configuration
Figure 31: 2UQ Advanced Tab - Serial Port Configuration, USB Configuration, PCI Configuration, and System
Acoustic and Performance Configuration
Figure 32: 2UQ BIOS Security and Server Management Tabs
DVD-ROM for 2UQ version 3 server
DVD-ROM for 2UQ version 3 server
Figure 33: 2UQ BIOS Boot Options, Boot Manager, and Error Manager Tabs
Reconstruction Troubleshooting
The list below shows the many different tools you can use to troubleshoot the CIRS. A good place to start is with the
CIRS Troubleshooting Guide. If you already know which component you are having trouble with, then you can go
straight to the section that deals with that component.
• Consult the CIRS Troubleshooting Guide on page 107
• Run the CIRS Image Test on page 135
• Check Network Connections Configuration for CIRS Servers on page 137
• Acquisitor Board Diagnostics on page 139
• Run 3DBP Diagnostics on page 151
• Check 3UD3/3UQ3 Server BIOS POST Messages and Codes on page 173
• Check VSD4 Server BIOS POST Messages and Codes on page 186
• Use Intel Confidence Tests for S2/S3 version 3 (p/n 4535 671 02401) on page 199
• Troubleshoot S2/S3 version 4 and version 5 on page 202
• Troubleshoot the 2UQ server on page 204
• Troubleshoot the RAID Array on page 222
• Run the DiskTest for S1 SCSI RAID Array on page 236
• If you need to transfer raw data to or from the CIRS, see Transfer Raw Data to and from CIRS on page 240
CIRS Troubleshooting Guide

• Server and System Issues on page 108
• Software Installation Issues on page 113
• CIRS Image Test on page 114
• Acquisitor Related Issues on page 115
• 3DBP and Acquisitor Driver and FPGA Guide on page 116
Server and System Issues

Symptom Probable Cause and Solution
• IDE/SATA drive not seen – drive model # should be listed in bios setup, if not, re-seat power/signal cables, reboot and
verify IDE/SATA drive is listed as first hard drive in bios boot order, adjust boot order if necessary. See CIRS Server
Configuration and Management on page 65, then reference your server for BIOS information.
• IDE/SATA drive boot order is incorrect. This is an indication SATA power or signal connection is intermittent. See solution
above.
• Memory seating – power down, re-seat RAM, reboot.
— For S1 version 2, VS1 version 2 and VS1 Plus servers, swap DIMM 1A and 1B with DIMM 2A and 2B. If unit boots,
RAM is bad, replace Server. These servers all use the same motherboard, so see SuperMicro X6DH8-XG2
motherboard Block Diagram on page 16 for DIMM locations.
— For S1 version 1 and VS1 version 1 servers, swap DIMM 1A and 1B with DIMM 2A and 2B. If unit boots, RAM is bad,
replace Server. See S1 version 1 on page 12.
— For VSD4, swap DIMM 1A and 2A with DIMM 3A and 4A. If unit boots, RAM is bad, replace Server. See SuperMicro
X7DBE-X motherboard Block Diagram on page 58 for DIMM locations.
• Server LED’s light but — For 3UD3/3UQ3, swap DIMM 1A and 2A with DIMM 3A and 4A. If unit boots, RAM is bad, replace Server. See
server won’t boot to SuperMicro X7DB8-X motherboard Block Diagram on page 27 for DIMM locations.
Windows.
• Conductive Debris inside chassis. Use compressed air to blow off motherboard, memory slots, chipset, and CPU.
• The server Blue Screens.
• BIOS corrupt or settings incorrect – Boot SOFGR CD and reload bios/restore settings. See Philips, System Diagnostic
• The server hangs or blue Utilities (PN SOFGR-064) Rev. 16 or higher on page 267.
screens during software
• Acquisitor seating – re-seat board, if board fit is too tight, chassis/motherboard may be misaligned or Acquisitor (PCI
install.
notch) may be out of tolerance. If rear of chassis bows outwards > 3/32” with board installed and cover removed, chassis
is misaligned; replace server. If Acquisitor board card edge won’t fit into PCI slot, replace Acquisitor. If you need help re-
seating the board, see the CIRS Repair/Replace Manual. For the location of the Acquisitor board, see:
— S1 version 1 on page 12
— S1 version 2 on page 15
— Vertical S1 version 1 on page 42.
— Vertical S1 version 2 and VS1 Plus on page 54
— VSD4 on page 57
— 3UD3 version 1 and version 2 on page 22
— 3UQ3 on page 26
• Software install corrupted – perform a full install of the CIRS Software. See the Brilliance 6/10/16/16P System Software
Installation Manual.

On server--Power, Hard Disk • AC Power cable unseated - Re-seat power connection at server and at the ac distribution box.
Drive, and CD-ROM LED’s
not on.
• Re-check physical installation of board (see acquisitor seating above).

• Check device manager on server (see Using Device Manager on page 225).
Windows does not recognize
• Reload application software (see the Brilliance 6/10/16/16P System Software Installation Manual).
Acquisitor
• Reload driver (see Reload the Acquisitor Board Driver on page 149).
• JTAG the board using the Acquisitor Diagnostics GUI (see Reload the Acquisitor Board FPGA on page 150).
• Re-check physical installation of 3DBP board. Depending on the server you have, for the location of the 3DBP board, see:
— Vertical S1 version 1 on page 42.
— Vertical S1 version 2 and VS1 Plus on page 54
— VSD4 on page 57
— S2/S3 version 3 on page 30
Windows does not recognize
— S2/S3 version 4 and version 5 on page 33
Back Projector (3DBP)
— 2UQ on page 36
• Check device manager on server (see Using Device Manager on page 225).
• Reload application software (see the Brilliance 6/10/16/16P System Software Installation Manual).
• Reload driver (see Reload the 3DBP driver on page 161).
• JTAG the board using the 3DBP Diagnostics GUI (see Reload 3DBP FPGA on page 162).

• Open Task Manager to check the following items (see Using Windows Task Manager on page 122):
i. Performance tab-- second processor possibly disabled. Task Manager should display two CPU windows, if not,
replace server. Check all servers and Host.
ii. Select the Networking tab to verify that the speed of the Host-IRS connection is running at 1Gb/s.
Processing seems slow or • Check “System properties” > General tab. Verify the correct amount of RAM is present. Amount of RAM varies by server
type. See Verify amount of RAM on page 119.
reconstruction speed (images
• Verify that D: disk fragmentation on the Host is acceptable. Run Defrag if not (NOTE: may take a long time to complete).
per second) seems slow.
See Host PC Disk Defragmentation on page 121.
• Verify that the BIOS level is at the correct level on all CIRS servers. See CIRS Server Configuration and Management on
page 65, and refer to each server listed in that chapter.
• Verify that the software revisions are correct and the same on all CIRS servers. See Verify CIRS Software Revision on page
120.
Host takes long time to boot • Host needs to see at least one raw data file on S1. On S1, check that F:\RawData contains one or more files. If the
then displays message RawData folder does not contain any files, then on the S1 desktop, double-click on the Recon icon, and type the following
command (without quotes): “uts –addr=localhost sr 1” then press <Enter>. This writes a raw data file to the
“Timeout period expired, Not
RawData folder.
Ready IRS”
• Helical scans exclusively use the 3DBP for (3D) reconstruction, Axial scans use software (2D) recon. Run several Helical
and Axial scans and/or reconstructions to isolate the 3DBP. Artifacts that are rectangular in nature, streaks or pixilated
dropouts can be caused by the 3DBP.
Run the CIRS image test from the CIRS service CD 10 times in rapid succession to verify 3DBP operation at elevated
temperatures (see CIRS Image Test on page 135). Run the 3DBP diagnostics in multiple loops (see 3DBP Diagnostics on
page 151). If either test fails replace 3DBP.
• Artifacts observed in both 3D and 2D recon, or 3D artifacts that remain after a 3DBP replacement, could be related to the
Image Artifacts server hosting the 3DBP (typically S2). Try one or both of the following:
i. If the CIRS has 3 servers, swap S2 and S3 servers (moving the 3DBP to the other server). Reload CIRS Application
software on both (see the Brilliance 6/10/16/16P System Software Installation Manual), and check for proper IP address
configuration (see Network Connections Configuration for CIRS Servers on page 137).
ii. Remove S3 from service by shutting it down, then click 2-ServerCfg icon on the S1 desktop. Restart Supervisor on
S1 after re-config (see Enable Supervisor Service on S1 on page 117).
• The cause of all other types of artifacts (rings, splay, central "button"…etc.) are almost never caused by the CIRS hardware
but can be embedded in the calibration files, which are maintained on the S1. Almost all problems of this nature are Gantry
related.

• Network hardware problem:
i. Verify the Gb link LED is lit on the Host LAN port, CIRS server ports, and Netgear switch ports (Netgear ports are
only in the CIRS Rack for Horizontal Servers). For information on the CIRS server ports LEDs, see:
S1 version 1 - Network Interface Controller on page 14
S1 version 2 - Network Interface Controller on page 17
3UD3 Network Interface Controller on page 24
3UQ3 Network Interface Controller on page 28
S2/S3 version 3 Network Interface Controller on page 32
S2/S3 version 4 and version 5 Network Interface Controller on page 34
2UQ Network Interface Controller on page 37
Vertical S1 version 2 and VS1 Plus Network Interface Controller on page 56
One or more of the following
VSD4 Network Interface Controller on page 59
messages are displayed on the
HOST during or after Scanner ii. Re-seat the RJ-45 connections.
Application startup: iii. Check Windows System event log for hardware errors (see SYSTEM event log on page 228).
• Network configuration problem:
• IRS disconnected
i. On the Host, check that the status of the Host-IRS connection says Connected, the speed is 1Gb, and the IP address is
• “HOST_IRS 192.168.0.100. See Verify that the Host-IRS Connection is active on page 117.
communication error” ii. Verify no IP conflicts are logged in Windows system event log. See SYSTEM event log on page 228.
iii. Ping S1 (192.168.0.200 or 10.68.0.200). See Ping IP Addresses on page 118.
• Checking Recon, Please iv. Repeat steps ii and iii from each server, using the IP addresses of each server as necessary, and pinging the Host and
wait the other servers from each CIRS server. See Ping IP Addresses on page 118.
• Supervisor service is not running – Set Supervisor service startup type to Automatic and start the service (see Enable
Supervisor Service on S1 on page 117). If Supervisor is not listed, verify Acquisitor is functional by running Acquisitor
Diagnostics (see The Acquisitor Diagnostics on page 141), then reload CIRS Application software (see the Brilliance 6/10/
16/16P System Software Installation Manual for reloading CIRS Application Software).
• Supervisor service is having problems due to mis-configuration (correct the issue, then restart Supervisor):
i. F:\RawData folder is missing, possibly caused by terminating disk test. See Create RawData Directory on F:\ on page
120.
ii. F:\ drive is missing – Use disk manager to import foreign disk or re-create array:
— For SCSI RAID configurations, see SCSI RAID - Import Foreign Disk and Re-create Array on page 123). If disk
manager shows drives as missing, identify the SCSI ID’s and re-seat power and SCSI cables on the drive(s). If the power
connection to a drive is loose fitting, replace the server. Also see Troubleshoot the RAID Array on page 222.
— For the VSD4 SATA Raid configuration, see VSD4 SATA RAID - Re-create Array on page 127

• Number of servers not configured correctly – Depending on number of servers in your system, click on either the
1-ServerCfg, 2-ServerCfg, or 3-ServerCfg icon on S1 desktop.
• S1 communication issue with S2 or S3. (See previous “HOST_IRS communication error” symptom for network
configuration checks).
One or more of the following • 3DBP problem on S2:
messages are displayed on the — Check CIRS event log (see Using Event Viewer on page 227)
HOST during or after scan — run 3DBP Diagnostics (see 3DBP Diagnostics on page 151)
initialization: — run CIRS image test (see CIRS Image Test on page 135)
• “Resource Allocation for • Problem with SCSI Raid Array on S1 (see Troubleshoot the RAID Array on page 222).
Scan Failed” on Host. • Server hardware problem or one of the servers did not boot--Check device manager on server (see Using Device
Won’t scan.” Manager on page 225).
• "A Recon error has • Reboot and run Adaptec "SCSISelect Utility" to run Non-destructive Media Tests on page 231 to further isolate if drive,
occurred" SCSI cable, or molex connector is the problem.
• Re-seat power and SCSI cables at SCSI drive and SCSI controller.
• Check for bent pins on SCSI cable, replace drive or cable if FRU is available. Replace server is molex connector is loose or
functions intermittently.
• RAM configuration incorrect, see Verify amount of RAM on page 119.
Software Installation Issues

App install fails with error: • Check system event log for CD-ROM errors (see Using Event Viewer on page 227). If another CD-ROM is
available, try loading from another CD.
• (occurs with 4.2.4.13 and higher) Acquisitor not installed or not seen during CIRS Application Software
Supervisor not present in list of services on S1 install, correct and re-install CIRS Application Software (see the Brilliance 6/10/16/16P System Software
Installation Manual).
CIRS Image Test

Test reconstructs images but fails • Check that both power connectors are seated on Power Module. If both power connectors are seated
subtraction test. properly and the subtraction test still fails, replace 3DBP.
Test reconstructs images but indicates • Check for 3DBP reset error in event log (see Using Event Viewer on page 227). If there are reset errors,
images are missing. replace 3DBP.
Test fails to copy raw data to CIRS or is • Verify F:\RawData folder is present and Supervisor is started and happy (no errors in CIRS log).
unable to communicate to CIRS. • Check CIRS event logs on S1 for errors (see Using Event Viewer on page 227).
• Verify 3DBP is present in Device Manager on VS1 or S2 (see Using Device Manager on page 225).
• Check Host IP is 192.168.0.100 and CIRS S1 IP is 192.168.0.200. To check communication ping from both the
Host to CIRS, and from CIRS to Host (see Ping IP Addresses on page 118).
• Verify connection speed is 1Gb (see Using Windows Task Manager on page 122). Verify no IP conflicts on all
servers (see SYSTEM event log on page 228).
• Reload CIRS Application Software (see the Brilliance 6/10/16/16P System Software Installation Manual).
Acquisitor Related Issues

• Wait 3 minutes, sometimes it takes this long for the driver to allocate Acquisitor buffers. Make sure the
correct versions of the driver and FPGA are installed (see Reload the Acquisitor Board Driver on page
System appears to hang during driver install.
149 and Reload the Acquisitor Board FPGA on page 150), then reboot, and retry driver install after fresh
boot.
System hangs on bootup after Jtagging or • This can occur if the wrong file is used when Jtagging board. If this occurs, repeat Jtag (see Reload the
Acquisitor not seen in device manager after Acquisitor Board FPGA on page 150). Still bad; order a new board.
Jtagging.
After Jtagging, all fiber loopback related • Power Down, retry. Try another fiber loopback cable.
diagnostics fail. The 4 red line fault LEDs (2 – 5)
remain on with fiber loopback installed.
• Possible board seating issue. Make sure board is completely seated. Make sure IDE strain relief hood is
removed from CD-ROM cable (see CIRS Repair/Replace manual).
System hangs on bootup after board is installed. • Check Motherboard to Chassis alignment. If excessive force is required to install board or back of chassis
is bowed after installing board, order a new server. Make sure the defect is noted on the vendor failure
report!
• Issue can be ignored ONLY if error matches (the found string must match exactly): See CT3239
newsletter.
Jtag ID subtest of the 3DBP and Acquisitor
• AcqGemDiag.cpp(1835): read uJtagDrOffset_: expected=0x05026093 or 0x05036093,
diagnostic fails. found=0xf5036093
• AcqGem_Diag::JtagIdCodeVerifyTest FAILED.
2 of 19 Acquisitor diagnostic subtests fail • Reload CIRS Application Software (see the Brilliance 6/10/16/16P System Software Installation Manual), then
(onboard memory overflow and ODL memory re-run test. If problem persists replace board.
address bus test).
3DBP and Acquisitor Driver and FPGA Guide

NOTE Firmware download (JTAG) occurs automatically when loading CIRS Applications version 4.2.4.13 or
higher (providing that the software driver is properly configured). It can also be performed manually at any
time (see Reload the Acquisitor Board Driver on page 149 or Reload the Acquisitor Board FPGA on page
150).
Board Description Part # Driver FPGA (JTAG) for System

1X, 3DBP/6Asic/128Mb 453567006381 3DBP.inf 3DBP_FPGA.svf BR6/10/16/16P/Big Bore
3DBP_LC/2Asic/128Mb 453567062741 3DBP.inf 3DBPLC_FPGA.svf BR6/10/16
1.1Gb Acquisitor 453567023021 AG16.inf ACQ16_XXX.svf BR6/10/16/16P
Troubleshooting Solutions
This section contains some of the solutions identified in the CIRS Troubleshooting Guide that do not already appear
elsewhere in the CIRS Service Manual.
Verify that the Host-IRS Connection is active

1. On the Host PC Desktop, right-click on My Network Places and select Properties from the pop-up menu.
2. On the Network Connections window, click on View, and select Details.
3. The Status for the Host-IRS Connection should say Enabled or Connected. If the Status for the Host-IRS
Connection does not say Enabled or Connected, physically move the network cable to the open port on the
network card. Then, verify the Status for the Host-IRS Connection says Enabled or Connected.
4. Right-click on Host-IRS Connection, and select Properties from the pop-up menu.
5. On the Host-IRS Connection Properties dialog, double-click on Internet Protocol (TCP/IP).
6. Verify the IP Address is 192.168.0.100.
7. Close all open dialog boxes and windows.
Enable Supervisor Service on S1

This procedure will Start the Supervisor Service on S1, and set the Startup to Automatic.
1. On the S1 Desktop, double-click the Services icon.
2. Right-click on CIRS Supervisor Service, and select Start.
3. Right-click on CIRS Supervisor Service, and select Properties.
4. Change Startup type to Automatic.
5. Click Apply, then click OK.
6. Close the Services window.
Ping IP Addresses
To ping the servers from the Host:
1. On the Host desktop, click
Start > Run. In the Run field,
type cmd and press <Enter>.
2. At the Command Prompt:
• For S1, type ping
192.168.0.200 then press
<Enter>
look for 0%
• For S2, type ping packet loss
192.168.0.210 then press
<Enter>
• For S3, type ping
192.168.0.220 then press
<Enter>
To ping the Host from the Servers:

1. On the Server desktop,
double-click the “Recon” icon.
2. At the Command Prompt, type
ping 192.168.0.100 then
press <Enter>
Verify amount of RAM

On the server desktop, click Start > All Programs > Accessories > System Tools > System Information. The value
is listed in Total Physical Memory.
NOTE For the correct amount of RAM for your specific server, see either Horizontal Servers Functional
Description on page 11, or Vertical Servers Functional Description on page 41.
Verify CIRS Software Revision

On the Server Desktop, double-click the "Recon" desktop icon, and at the Command Prompt type: supervisor.exe -ver
Software Revision
Create RawData Directory on F:\

1. On server S1, open windows Explorer, navigate to the F: drive and create a folder labeled RawData (spelled
exactly as shown here).
2. Click "Recon" desktop icon, and at the Command Prompt type: uts -addr=localhost sr 1. This command inserts
a dummy raw data file into the folder.
Host PC Disk Defragmentation

This procedure will defragment both the C: and D: partitions on the Host PC.
NOTE This is only for the Host PC! The D: partition may take several hours the first time or if the disk is badly
fragmented. Subsequent Defrags on the D: partition will be much faster.
1. On the Host desktop, double-click on My
Computer.
2. Right-click on Local Disk (C:), and select
Properties.
3. On the Properties dialog, click on the Tools tab.
4. On the Tools tab, click Defragment Now...
5. On Disk Defragmenter, click on the C: partition to
select it, then click Defragment.
6. A confirmation pop will appear when
defragmentation is complete, just click Close.
7. On Disk Defragmenter, click on the D: partition to
select it, then click Defragment. The D: partition
may take several hours the first time or if the disk is
badly fragmented!
8. A confirmation pop will appear when
defragmentation is complete, just click Close.
9. Close Disk Defragmenter.
NOTE If the customer needs the scanner for a Patient Scan, click Stop on the Disk Defragmenter, then click Start
> Shut Down > Log off. Resume the defragmentation when convenient.
Using Windows Task Manager

On S1, you can use Task Manager to check the performance status of the CPUs and Host-IRS connection. To access
Task Manager, right-click on the Windows Task Bar, and select Task Manager from the menu.
.
CPU windows on all

servers except
VSD4, 3UD3/3UQ3,
and 2UQ.
The Networking tab shows Host-IRS

connection status and performance data
CPU windows on VSD4. The 3UD3/3UQ3

and 2UQ servers will show eight windows.
The Performance tab shows CPU status and usage data
SCSI RAID - Import Foreign Disk and Re-create Array

1. On the S1 Desktop, right-click on My Computer
and select Manage.
2. Click on Disk Management.
3. Right-click within the green highlighted area for
Disk 1 in the F: volume and select "Delete
Volume". When prompted that all data will be
lost select "yes".
This action will destroy all the raw data on
the SCSI RAID!
4. On the S1 desktop, double-click the Services
icon on the desktop. Right-click on CIRS
Supervisor Service and select Stop.
5. Go to Disk Management again. Recreate the
volume by right-clicking on any one of the drives
shown and select New Volume; this will launch
the New Volume wizard.
6. On the New Volume Wizard, click the Next button.
7. Select "Striped" for Volume Type. Click Next.
8. In the Select Disks window, click on each drive in

the Available pane, and then click the Add button.
When all the drives are in the Selected pane, click
Next.
9. In the Assign Drive Letter or Path, select drive

letter F. Click Next.
10. In the Format Volume window, delete "New

Volume" from the Volume label entry. Make sure
the field is absolutely empty including spaces!
11. Select Quick Format, and click Next.
12. On the last screen of the wizard scroll through and

make sure that all information is correct (including
Volume Label being empty). Click Finish if all is
correct.
13. Open windows Explorer, navigate to the F: drive
and create a folder labeled RawData (spelled
exactly as shown here).
14. Click the Recon desktop icon and at the command
prompt type: uts -addr=localhost sr 1. This
command inserts a dummy raw data file into the
folder.
15. Double-click the Services desktop icon, and
restart the CIRS Supervisor Service.
VSD4 SATA RAID - Re-create Array

The SATA disk drives for the RAID in the VSD4 are 120 GB; however, the software requires that they be partitioned to
use only 73 GB to maintain the disk access speed. For this reason, the disk volume cannot be rebuilt in the same way
that previous RAID SCSI drive volumes were rebuilt. To get the correct volume configuration with the 120 GB SATA disk
drives on the VSD4, the CIRS application software must be reinstalled and it will correctly configure the disk drives.
After one or more drives are replaced, reconfigure the volume as follows:
1. Power up the VSD4 server.
2. From the host, open a Remote Desktop to log on to S1:
a. On the Host Windows desktop, double-click on the CIRS Folder.
b. In the CIRS folder window, double-click on the Recon-S1 icon.
c. Log in as philips_service.
3. Left-click on the Windows Start button (see Figure 1).
4. Right-click on My Computer.
5. Left-click on Manage in the drop-down menu (see Figure 1). You will seethe Computer Management window shown
in Figure 2 on page 128.
Figure 1: Selecting Computer Management
6. In the left panel left-click on Disk Management (see Figure 2).
DISK MANAGEMENT
Figure 2: Computer Management Window

7. If the Initialize and Convert Disk Wizard box shown in Figure 3 on page 128 is displayed, click Cancel. The Disk
Management window shown in Figure 4 on page 129 should be displayed.
Figure 3: Initialize and Convert Disk Wizard Selection box
The Disk Management window (Figure 4 on page 129) should display all the drives. The status of the drive(s) that
were replaced will be listed as “Unallocated” (disk 3 in Figure 4 on page 129) and the status of the rest of the drives
will be listed as “Failed”. A “Missing” line will be added at the bottom since the volume that the system is looking for
is not operating.
The volume will have to be deleted and recreated according to the following instructions.
Figure 4: Disk Management Display for Replaced Disk 3
!
CAUTION Make absolutely sure that volume F: is selected before proceeding!!
8. Right-click on the volume in the upper pane of the Computer Management Window, and select Delete Volume
from the drop-down menu.
Figure 5: Volume Drop-Down Menu
9. In the “Delete Striped Volume” confirmation dialog box, click Yes to continue.
Figure 6: Delete Striped Volume Dialog Box
10. All disks will become un-allocated as shown.
Figure 7: All Disks Un-allocated (Disk 3 Replaced)
11. Close the Computer Management window by left-clicking on the red ‘X’ in the right upper corner of the window.
12. On the desktop, click on the CIRS Install Icon to reinstall the CIRS Application.
Cirs.ico 13. When the dialog box appears asking if you want to rebuild the array as shown in Figure 8 on page 133, click on
Yes.
Figure 8: CIRS Application Installation Message Box

14. The CIRS Application will continue. When the installation is complete it will automatically reboot the server. The
connection from the host to the server will be lost and the host Windows desktop will be returned to the screen.
15. After the server finishes booting up, reconnect to the server:
a. On the Host Desktop, double-click on the CIRS Folder.
b. In the CIRS folder window, double-click on the Recon-S1 icon.
c. Log in as philips_service.
16. After you reconnect to the server, verify you see “CIRS Application Installation Completed!” in the installation
window. Then close the window.
.
17. Double-click on the 1-server config icon from the desktop.

18. When the prompt “Value NumberOfNodes exists, overwrite (Y/N)?” appears, answer “Y”.
19. Double-click the Services icon and make sure the Supervisor is set to “Automatic” and is “Started”.
20. Check that the RAID disk volume has been set up:
a. Left-click on the Windows Start button (see Figure 1).
b. Right-click on My Computer.
c. Left-click on Manage in the drop-down menu. The Computer Management window should be displayed.
d. In the left panel left-click on Disk Management.
e. The disk array volume should be configured as shown in Figure 9 on page 134 and all the disks should show a
“Healthy” status for the 73.78 GB sections. The 38 GB sections are intentionally left un-allocated.
Figure 9: Correctly Configured VSD4 Disk Array
CIRS Image Test

The CIRS Image Test can verify CIRS performance and reconstruction. The test:
• submits data to CIRS,
• reconstructs the data and creates images,
• compares those images to known good images,
• and finally reports a summary of the reconstruction - which gives the Images Per Second (IPS).
• After this first output of performance times, the test performs another reconstruction with image balance enabled.
This reconstruction has improved image quality, and therefore will have a slightly lower performance time.
You can use this test in conjunction with the existing Acquisitor and 3DBP diagnostic tools. The test is not meant to
replace those diagnostic tools, but complement them and provide additional information.
NOTE When running the test, make sure the CIRS is not processing other reconstructions, or results will be
inaccurate.
This test assumes that the Service CD version and the CIRS application software versions are identical. To verify that
you are using the correct version of CIRS software:
1. Use Remote Desktop to log on to the S1 server from Host.
2. On the CIRS desktop, double-click on the Recon icon. At the Command Prompt, type supervisor.exe -ver.
3. Compare this version with the version number of the CIRS Service CD that you are running the test from. If they are
not the same, the image comparison portion of the test may fail.
Running the test

1. Login to the Host PC as philips_service.
2. Insert the CD labeled “CIRS Service Vx.x.x.x” into the Host PC.
NOTE Do not run the test from the CIRS servers.
3. Navigate to SERVICETOOLS > CIRSIMAGETEST.
4. Double-click on RUNTEST.BAT. If a Windows Security Alert window comes up, click on Unblock.
5. A message box will ask you if you want to Run the CIRS Image Test. Click Yes to start the test, or click No to exit.
6. The test output is sent to an Internet Explorer window, which will display the current test status.
NOTE The IE window may be hidden. If there is an

orange box flashing at the bottom of the
screen, click on it to bring the output window
to the foreground. Note that it may take 2 - 5
min. to store the raw data onto the CIRS
machine.
7. When the test is complete, you will see an output
similar to the one at right.
8. Record your results, then click the OK button on the
CIRS Image Test Complete prompt. The test will
close when you click the OK button, so record the
results before you click the OK button. If you
accidentally close the test too soon, you can always
re-run the test.
9. The test will continue even if the image comparison
portion of the test fails. If the image comparison
portion of the test fails, ensure that the Service CD
version and the CIRS Application versions are the example
same. IPS values
10. The times reported by the test denotes the best
CIRS performance. The IPS time used are for the
purposes of this test only. The reported IPS may
not reflect the actual IPS of the system.
11. Run the test two more times, and verify that the
higher of the two IPS values is greater than or equal
to 6 ips for 1-server, 20 ips for 2-server, or 40 ips for
3-server.
12. If both IPS values differ significantly from the
expected results, and/or the Image Comparison Test
failed, then see CIRS Troubleshooting Guide on
page 107.
Network Connections Configuration for CIRS Servers

There are 2 Network Adapters present per Server: two integrated Intel ®PRO Network Connections:
• One Intel PRO/100+ and one Intel PRO/1000 for S1/VS1 version 1
• 2 integrated Intel ®PRO Network Connections 10/100/1000 for S1 versions 2 and 3, VS1 version 2, VS1 Plus,
VSD4
• 2 integrated Intel ®PRO Network Connections 10/100/1000 for all versions of S2/S3.
The high speed NICs are used for data and have to be configured the following way:
For S1/VS1 version 1:
Brilliance 2.0.2 software Brilliance 2.2 software and
NIC Function
and Earlier Later
NIC1 (10/100) Spare 192.168.0.150 192.168.0.201
NIC2 (10/100/1000) data link 192.168.0.200 192.168.0.200
For S1 versions 2 and 3, VS1 version 2, and VS1 Plus:

NIC Function
and Earlier Later
NIC1 (10/100/1000) Spare 192.168.0.150 192.168.0.201
NIC2 (10/100/1000) data link 192.168.0.200 192.168.0.200
For all versions of S2:

NIC Function
and Earlier Later
NIC1 (10/100/1000) data link 192.168.0.210 192.168.0.210
NIC2 (10/100/1000)
Spare 192.168.0.151 192.168.0.211
(On S2 version 3, the bottom one)
For all versions of S3 (make sure this server is configured properly, since it might come configured as S2):

NIC Function
and Earlier Later
NIC1 (10/100/1000) data link 192.168.0.220 192.168.0.220
NIC2 (10/100/1000)
Spare 192.168.0.152 192.168.0.221
(On S2 version 3, the bottom one)
To test which Network Connection applies to which port:

1. On the S1 Desktop, double-click the Network Connections icon to display the Network Connections window.
2. Disconnect each port's cable one at a time, and you will see a red ‘X’ next to the port that corresponds with that
cable.
Acquisitor Board Diagnostics

To launch the Acquisitor Board Diagnostics, you must connect from the Host to the VS1/S1 Server using Windows
Remote Desktop:
1. Logon to the Host as philips_service.
2. On the Desktop, double-click on the CIRS Folder.
3. In the CIRS Directory, double-click on Recon-S1.
4. Click OK to any Security Warnings that appear.
5. At the Log On to Windows prompt, log on as philips_service.
6. On the VS1/S1 Desktop, double-click on the ACQ Diagnostics icon.
Main GUI
The main GUI is used to select and execute the various diagnostics. This interface consists of three distinct
components: the diagnostics, output window, and command buttons. Descriptions of each component are given in
detail below. The firmware version and ACQ Board version are located in the upper right corner of the GUI.
The Acquisitor Diagnostics

The diagnostics component of the GUI consists of seven main tests with several subtests. All of the Test and subtests,
except the Electrical Signals Test, are checked by default. To select tests, simply click their respective check box. To run
a test, click the “Run Diagnostics” button. The PCI interface portion of the design is tested through a combination of
accesses during the normal PC boot process along with dedicated diagnostic tests.
The PCI Diagnostic Register is used to validate proper response of the board to I/O space accesses and
also test the lower 32-bits of the multiplexed PCI address and data lines. A 32-bit pattern of walking 1's
and walking 0's are written then read from this register to validate these connections. The success or
Diagnostic Register Test
failure of this test is indicated by the "Diagnostic Register Test" pass or fail message. In the case of a
failure, the test can optionally be setup to write then read-back and verify any user defined 32-bit data
pattern. This will allow the user to test for intermittent failures and isolate the faulty data line.
You must install the optical external loop-back cable prior to running this test. One reading is
setup in the GEM PC Host memory. The slice data area of this reading will contain a constant 64-bit
pattern of either all zeros or all ones. The ACQ DMA Channel and ODL will be enabled, and the GEM
DMA channel will then be setup to transfer this one reading. The success or failure of the ODL Memory
Data-bus test is determined by comparing the Host ACQ buffer to the expected data from the GEM
buffer. After completing each pass of this test, the board is reset to re-initialize memory address pointers
Test Odl Memory Data Bus
and ODL logic. This test will be repeated 64 times. The data pattern used in each successive pass will
walk a "1" through a 64-bit field of zeros. The test will be repeated another 64 times. The data pattern
used in each successive pass will walk a "0" through a 64-bit field of 'ones'. 64 bits is the size of the ODL
Memory accesses. Therefore, if there is an error in either the walking 'ones' or walking 'zeros' test, it
indicates a bad data line either to memory or to/from the SERDES. The board and ODL logic is reset
between each reading to guarantee memory address pointers remain constant.
You must install the optical external loop-back cable prior to running this test. The PCI CSR
register bit, ACQ DMA Channel Disable, is set prior to this test. The GEM, DMA channel is setup to get
Readings from the PC Host Buffer and send them internally to the ACQ, ODL controller and thus on-
board ODL Memory. The slice data of these Readings will contain an incrementing pattern. Since the
Test Odl Memory Address Bus ACQ, DMA Channel is disabled, these Readings will accumulate in the ODL Memory Buffer. Once the
GEM transfer has completed, the ACQ, DMA channel shall be re-enabled. The data patterns test for
address opens and shorts as the ODL controller transfers data to/from memory. The success or failure
of the ODL Memory Address-bus Test is determined by comparing the Host ACQ buffer to the expected
data from GEM transfers.
This test uses the JTAG control and status registers to exercise the on-board JTAG chain connecting the
Xilinx XC18V04 EPROMs and XC2V1500 FPGA. This test reads back and verifies the JTAG ID from
each of the on-board XC18V04 EPROM's. Prior to running this test, any Xilinx programming cables
Verify JTAG ID
should be removed from connector J3. Occasionally, new productions EPROMS may have different
JTAG IDs than those coded in the test. While usually accounted for, sometimes the vendor changes
without notice. See Service Note CT3239.
You must install the optical external loop-back cable prior to running this test. The ODL serial
data link is tested by setting up 16-bit data patterns in the GEM buffer area of PC Host memory. These
data patterns will be embedded in the slice-data area of simulated Readings. In this mode, the GEM
DMA Channel is setup and data is then transferred from the GEM buffer, through the FPGA and out to
the serializer and fiber-optic transmitter. The external optical cable routes data back to the fiber-optic
receiver and the de-serializer. The ACQ ODL controller inside the FPGA will then write data to ACQ
Test DMA (includes subtests) buffer area of PC Host memory. The slice data of the Readings used for this test will contain the
following patterns: 16-bit walking 'ones', 16-bit walking 'zeros', 16-bit incrementing pattern, 16-bit
pseudo-random sequence. The walking ones and zeros patterns may change within the slice data of
one reading. The pseudo-random sequence and incrementing pattern will repeat after sequencing
through all possible pattern variations. The walking ones and walking zeros patterns test for opens and
shorts on the 16-bit data transfers to/from the FPGA and the serializer/de-serializers. The 16-bit pseudo-
random sequence will check the fiber-optic transceivers for proper operation.
You must install the optical external loop-back cable prior to running this test. The Gantry Data
Checks verify the ability to catch Reading and protocol errors. These tests use the GEM function to
Gantry Data Checks (includes
simulate Gantry-to-ACQ Reading transfers. Reading transfers are included which test both nominal and
subsets)
error conditions. All Gantry Data-Checks enable the work-queue and verify that the proper error
conditions were logged on the work-queue.
You must install the electrical loop-back cable prior to running this test. The external ENACQOK
signal is asserted by setting the GEM SCR bit, TX_ENACQOK. The success of this test is determined
by checking that the corresponding PCI CSR bit, RX_ENACQOK, is also set. The external ACQOK is
Electrical Signals Test asserted by setting the PCI CSR bit, S/W TX_ACQOK. The success of this test is determined by
checking that the corresponding GEM SCR bit, RX_ACQOK, is also set. The GEM SCR bit,
TX_ENACQOK, is cleared. The success of this test determined by verifying that the RX_ACQOK bit in
the GEM SCR is then de-asserted.
The PC BIOS accesses the boards PCI configuration space to determine, among other things, the
board's Vendor-ID and Device-ID, and I/O space requirements. During the boot process, the driver will
also access the board to setup the interrupt control registers and determine the FPGA revision level.
The success or failure of the boot process can be determined through Windows XP Device Manager. An
PC Boot Process entry should be displayed for the "Philips Acquisition Device, Philips ACQ Board ". If there is no entry, it
indicates that the BIOS boot code did not detect the ACQ Board (e.g. Configuration Device-ID/Vendor-
ID/space access failed). If there is an entry, the device status for the Philips Acquisition Device, Philips
ACQ Board should state that the "This device is working properly". If the device is not working properly,
it indicates the driver was unable to access I/O space.
The Command Buttons
Output Options launches the Output Options window, which allows you to filter out
certain categories of messages from the diagnostics:
• Show Status Messages
• Show Info Messages
• Show Warning Messages
• Enable Verbose Logging
By default, Show Warning Messages is enabled, while Show Status Messages and
Show Information Messages are filtered. Enable Verbose Logging is initially disabled.
The Defaults button restores the Output Filter Options to the original settings
Clear Output allows you to clear the contents of the Output Window.
Run Diagnostics first launches the Run Options dialog window, then executes the test based on the current
Diagnostic Test selections.
Select All/None will check or uncheck all of the Diagnostic Tests except the “Electrical Signals Tests”. First click will
uncheck all (select none), second click will check all (select all).
Reset Board will reset the board.
Board Settings allows you to change the board configuration to run the Diagnostics with Internal Loopback or
External Loopback.
Stop Diagnostics is only available during diagnostic execution, and allows you to stop the tests during execution.
JTAG Download allows you to perform a

JTAG download, or to verify the Current
revision of he installed FPGA file. When the
JTAG Download window appears, make sure
that Verify that the update is required
before download of FPGA file is selected.
Click OK, and the program will check to see if
the needs updating. Proceed to download if
needed.
Quit terminates the program.
The Output Window

The output window is where all feedback from the diagnostics
appears. Many message types are displayed ranging from
information to errors. A diagnostic report will be sent here
after every diagnostic cycle. Directly under the output window
is a progress bar, which reflects the progress of diagnostic
execution
Expected Results for one

loop with optical loopback
and electrical loopback
cables attached.
Typical Diagnostic Execution Cycle

1. In the Acquisitor Diagnostics area, select the tests to run.
2. Click the Output Options button, and set the output options on the dialog
window.
3. Click the Run Diagnostics button.
4. On the Run Options dialog window, select either Run diagnostics by
loop count or Run diagnostics until user response.
5. Click OK on the Run Options dialog window, and the program will
generate the test execution queue and begin running the tests. At this
point, you can wait until the diagnostics complete, or click the Stop
Diagnostics button to cancel the current test execution queue and return
to the main GUI.
NOTE Only the default "Loop Count: 1" option can be used at this time.
Normal Scanner Diagnostic Mode

In the normal scanner operation (optical and electrical cables connected to the Gantry), only the PCI interface and
FPGA programming chain is tested. You can select and run only two of the diagnostics: "Diagnostic Register Test" and
"Verify JTAG ID".
Internal Loop-back Diagnostics

The Board Settings button provides an option to enable "Internal Loop-back". This is disabled by default.
External Loop-back Diagnostics

The external loop-back diagnostics test all board functionality including the transmit/receive functions of the optical data
link (ODL) and electrical signals (COM_OK, ACQ_OK, ENABLE_ACQ_OK). With the external loop-back cables
installed, all of the diagnostics can be run and should pass successfully.
In order to run the external optical loop-back diagnostics, the optical cable from the gantry has to be disconnected
from the server, and a short optical loop-back cable has to be used to connect the transmitter and receiver on the
Acquisitor board. In order to run the external electrical loop-back diagnostics, the electrical cable from the Gantry
has to be disconnected from the server, and a short electrical loop-back cable (Gantry Emulation) has to be used to
connect the transmitter and receiver on the Acquisitor board.
Loop-back Cable Connections
For all SIA, and 3UD3/3UQ3 version 1 servers, con-

nect the Electrical Loopback Cable to the RJ-45
Connector located on the Acquisitor Board, and the
RJ-45 Connector on the back of the Acquisitor
Board.
For VSD4 and 3UD3/3UQ3 version 2

or later, connect the Electrical Loop-
back Cable to the RJ-45 Connector on
the back of the server and the RJ-45
Connector on the Acquisitor Board.
For the S1A, 3UD3/3UQ3, and VSD4 servers, connect the Optical
Loopback Cables as shown.
Acquisitor Board Software

Check the Driver Version
1. Click Start.
2. On the Start menu, right-click on My Computer and select Manage from the drop-down menu. Or, on the Desktop,
right-click on My Computer and select Manage from the drop-down menu.
3. Click on Device Manager, then from the list that appears, double-click on Philips acquisition devices.
4. Under Philips acquisition devices, double-click on Philips ACQ Board (1.1 Gb).
5. On the Dialog Window that appears, click on the Driver tab to view the Driver information (the driver should be
AG16.inf.)
Reload the Acquisitor Board Driver

1. On the S1 desktop, click Start, then right-click on My Computer and select Manage.
2. Click Device manager.
3. Right-click on Philips ACQ board (1.1Gb), and from the menu, select Update driver…
4. If the Hardware Update Wizard appears asking to connect to Windows Update to search for a driver, select No, not
this time. Then click Next.
5. On the Hardware Update Wizard, select “Install from a list or specific location (Advanced)”.
6. Click Next.
7. Select "Don't search. I will choose the driver to install".
8. Click Next.
9. Click Have Disk…
10. Click the Browse button, and browse to C:\Program Files\Philips\CIRS\drivers.
NOTE If the Open Window automatically shows the drivers folder, make sure that the full path to the folder is
C:\Program Files\Philips\CIRS\drivers!
11. In the drivers folder, select AG16, then click Open.
12. Click OK.
13. Click Next.
14. Click Finish, then close the Computer Management Window.
Reload the Acquisitor Board FPGA

1. On the Desktop, click on the ACQ Diagnostics icon to start the CIRS Acquisition Board Diagnostics application.
2. Click JTAG Download, to launch the JTAG Download window.
3. On the JTAG Download window, select “Bypass verify and download FPGA file”.
4. On the JTAG Download window, click Select File.
5. Navigate to the C:\ProgramFiles\Philips\CIRS\AcqGem folder.
NOTE If the Open Window automatically shows the AcqGem folder, make sure that the full path to the folder is
C:\Program Files\Philips\CIRS\AcqGem!
6. Navigate to the C:\ProgramFiles\Philips\CIRS\AcqGem folder and:
• For BR 6/10/16 (air) and 16 Power, select the file ACQ16_vxx.svf, where vxx is the version.
• For BR40 or Big Bore, select the file ACQ64_vxx.svf, where vxx is the version.
• For BR64 with 2.2.x - 2.3 software, select the file ACQ64X_vxx.svf, where vxx is the version.
• For BR64 with 2.4 software, select the file ACQ64X_FPGA
7. Click Open.
8. On the JTAG Download window, click OK.
9. On the AcqDiagGUI window, click OK. This will appear after programming is complete.
10. On the CIRS Acquisition Board Diagnostics window, click Quit.
11. Power off the server:
a. Right-click on the Windows Taskbar, and select Task Manager.
b. On Task Manager, click Shut Down > Turn Off.
c. Click Yes on any messages that appear.
d. Click OK on the Remote Desktop Disconnected prompt.
Host desktop.
12. Power on the server by depressing and holding the switch on the front of the server until the green light to the left of
the switch illuminates.
3DBP Diagnostics
To launch the 3DBP Diagnostics, you must connect from the Host to the VS1, VSD4, or S2 server using Windows
Remote Desktop:
1. Logon to the Host as philips_service.
2. On the Desktop, double-click on the CIRS Folder.
3. In the CIRS Directory, double-click on:
Recon-S1 if you have a vertical server configuration (VS1 or VSD4)
Recon-S2 if you have horizontal server configuration with an S2 server
4. Click OK to any Security Warnings that appear.
5. At the Log On to Windows prompt, log on as philips_service.
6. On the S2 Desktop, double-click on the 3DBP Diagnostics icon.
Main GUI
The main GUI is used to select and execute the various diagnostics. This interface is composed of four distinct
components: the diagnostics, output window, progress indicators, and command buttons. Descriptions of each
component are given in detail below.
3DBP Diagnostics Components

The diagnostics component of the GUI consists of twenty
selectable tests. Nineteen of the tests are specifically meant to
test the hardware in diagnostics mode. The twentieth test is an
external executable, which tests the hardware in application
mode. To select tests, simply check the checkboxes for the
desired tests. To run, click the Run Selected button. Tests are
presented in the order they are executed.
The host performs a series of writes and reads to the Diagnostic Register. First, a walking 1 pattern is used.
Diagnostic Register Test Secondly, a walking 0 pattern is used. This test exercises the target PCI interface and Diagnostic Register
operation.
The host tests the channel lock feature by performing the following steps:
• set up a 4 MB receive DMA loopback transfer
• sleep for 1 second
Channel Reset Test • verify the DMA loopback receive channel is not locked
• reset the receive DMA loopback channel
• read lock register to verify receive loopback DMA channel is locked.
This test exercises the target PCI interface and the Lock Channels and Reset Channels Registers in the FPGA.
The host reads the Hardware Control Register and tests bit 27 (ASIC DCM Reset bit). If bit 27 is 1 then bit 31
should be 0, or if bit 27 is 0 then bit 31 should be 1. If either of these conditions is not true, then the test fails. If
Hardware Control Register
either of these conditions is true, then the host toggles bit 27 and tests if bit 31 toggles. Finally, the Hardware
Test
Control Register is returned to its original value. This test exercises the target PCI interface and the Hardware
Control Register in the FPGA.
The host sets up a 5 MB DMA transfer to and then from the loopback buffer. Next, the host verifies that the transfer
DMA Test
occurred successfully. This test exercises the target PCI interface and the loopback DMA transfers in the FPGA.
The host sets up five 5 MB DMA transfer to and then from the loopback buffer in a chaining fashion. Next, the host
DMA Multiple Buffer Test verifies that all 5 transfers occurred successfully. This test exercises the target PCI interface and the loopback
DMA transfers in the FPGA.
The host sets up thirty-two 48000 byte DMA transfer to and then from the loopback buffer in a chaining fashion.
Multiple Loopback Test Next, the host verifies that all 32 transfers occurred successfully. This test exercises the target PCI interface and
the loopback DMA transfers in the FPGA.
The host sets up a ping message to DSP 1 and waits for a reply. Once the valid reply is received, the ping test is
DSP Ping Test performed with the other DSP(s) in series.This test exercises the target PCI interface, the FPGA DMA controllers,
master PCI accesses, FPGA to DSP link port transfers, and DSP to FPGA link port transfers.
The host sets up a ping message to DSP 1 and waits for a reply. Once the valid reply is received, the ping test is
DMA Ping Test performed with the other DSP(s) in series. This test exercises the target PCI interface, the FPGA DMA controllers,
master PCI accesses, FPGA to DSP link port transfers, and DSP to FPGA link port transfers.
Runs the Ping tests by sending 80 messages to each DSP, except the last DSP. The last DSP is sent 79
One Chan w/Fewer Xfers
messages. This tests ability of the 3DBP to handle a varying amount of messages.
The host exercises the FPGA JTAG bus by reading the device ID codes from the two XC18V04 EEPROM devices
JTAG ID Code Verification
in the chain. This test exercises the target PCI interface and the FPGA JTAG chain.
Link Send Test Sends a command to the Link Port to test port access.
The host sends a message to the DSP with some data. The command in the message is to invert the data and
Link Test return it to the host, which is the action taken by the DSP. This test exercises the target PCI interface, the FPGA
DMA controllers, master PCI accesses, FPGA to DSP link port transfers, and DSP to FPGA link port transfers.
The DSP tests the access and integrity of the External Port SDRAM. A walking '1' test is performed to test the data
bus connectivity and the address bus integrity is tested using accesses to random memory location. Also, tests are
DSP Memory Test performed to verify that the SDRAM paging function is working properly. This test exercises the target PCI
interface, the FPGA DMA controllers, master PCI accesses, FPGA to DSP link port transfers, DSP to FPGA link
port transfers and DSP accesses to SDRAM.
This is the most basic access test for the ASIC host interface. The DSP writes a value into the ASIC control
register and then reads the control register. This test exercises the target PCI interface, the FPGA DMA
ASIC Access Test
controllers, master PCI accesses, FPGA to DSP link port transfers, DSP to FPGA link port transfers and DSP
accesses to ASIC internal registers.
This tests exercises the operation of the wire-OR'ed READY signal. First, TIGER_A tests to see if it can drive
READY low. If successful, TIGER_A tests if it can release the READY and have it pulled high. If TIGER_A passes
the test, then the PC host commands TIGER_B to run the same tests. This continues until all 6 DSPs have
Ready Line Test
performed the test. This test exercises the target PCI interface, the FPGA DMA controllers, master PCI accesses,
FPGA to DSP link port transfers, DSP to FPGA link port transfers, DSP accesses to ASIC internal registers and
the function of the READY signal between ASICs.
The DSP writes a test pattern into the ASIC's View Memory and reads it back. An arbitrary test pattern is used.
The diagnostic tests accesses to the View Memory, but does not test the integrity of the memory. There are 4
modes in which the View Memory is accessed:
• DSP programmed I/O writes and reads

ASIC Memory Test • DSP programmed I/O writes and fly-by DMA ASIC to SDRAM transfers for reads
• Fly-by DMA SDRAM to ASIC for writes and DSP programmed I/O for reads
• Fly-by DMA transfers for both SDRAM to ASIC and ASIC to SDRAM transfers. This test exercises
the target PCI interface, the FPGA DMA controllers, master PCI accesses, FPGA to DSP link port
transfers, DSP to FPGA link port transfers and DSP accesses to ASIC internal memory (View
memory) and registers.
This test is only performed on ASIC6/TIGER_F and ASIC1/TIGER_A, since they are ASICs connected to Volume
Memory. The DSP writes a test pattern to one of the ASIC's Profile Memories and then commands the ASIC to
move the data into Volume Memory. The DSP clears the profile memory of a different BP, and the ASIC is
Volume Memory Access Test commanded to move the data from Volume Memory to the cleared Profile Memory. The DSP then compares the
data read from the Profile Memory. This test exercises the target PCI interface, the FPGA DMA controllers, master
PCI accesses, FPGA to DSP link port transfers, DSP to FPGA link port transfers, DSP accesses to ASIC internal
memory (View memory) and registers, and ASIC access to the Volume Memory SDRAM.
The DSP writes synthesized data into the ASIC profile memory. A backprojection is performed and the resulting
data is placed into Volume Memory. Next, the data is read back into the profile memory in a manner that exercises
the ALU scaling, offset and clipping functions. This test is done in both 16- and 32-bit modes. This test exercises
Volume Memory Test the target PCI interface, the FPGA DMA controllers, master PCI accesses, FPGA to DSP link port transfers, DSP
to FPGA link port transfers, DSP accesses to ASIC internal memory (View memory) and registers, ASIC access to
the Volume Memory SDRAM, ASIC sequencer, ASIC address generator and ASIC ALU functions. Note: This test
takes a few minutes to run.
The DSPs use synthetic view data to run through two complete backprojection cycles using the 2D model. The two
passes are used so that images can be backprojected in both directions through the ASIC pipeline. The resulting
image is tested against the expected result.This test exercises the target PCI interface, the FPGA DMA
Recon Test controllers, master PCI accesses, FPGA to DSP link port transfers, DSP to FPGA link port transfers, DSP
accesses to ASIC internal memory (View memory) and registers, ASIC access to the Volume Memory SDRAM,
ASIC sequencer, ASIC address generator, ASIC ALU functions, the function of the READY signal between ASICs
and interface between ASICs.
The DSPs use synthetic view data to run a 3D backprojection. The resulting image is tested against the expected
result. This test is not a diagnostic test. The 3DBP Diagnostic loads diagnostic code into the DSPs to perform the
Projection Unit Test
tests detailed above. The Projection Unit Test loads application code into the DSPs. When the test completes, the
diagnostic code will load back into the DSPs.
The Command Buttons

Output Options launches the Output Options dialog, which allows you to filter out certain
categories of messages from the diagnostics:
• Display Warning Messages
• Display Info Messages
• Display Status Messages.
By default, warning messages are shown while status and information messages are
filtered out. The Defaults Button Restores the output filter settings to the original settings:
show warning messages but do not show information and status messages.
Copy Text
Clear Output allows you to clear the contents of the Output Window.
Select All/None checks or unchecks all of the diagnostic tests. First click will uncheck all (select none), second click
will check all (select all).
Run Selected calls the run options dialog then build and execute the test queue based on the current selections.
This command button is hidden from view during test execution.
Stop Diagnostics is only available during diagnostic execution. This button is in the same location as the Run
Selected button. Clicking will issue a cancel request to the program where the program will cancel diagnostic
execution at the next convenient opportunity.
Reset Board issues a reset command to the 3DBP hardware in the event a manual reset is necessary. Resets the
3DBP hardware with the diagnostic DSP image.
JTAG Download allows you to perform a JTAG

download, or to verify the Current revision of he
installed FPGA file. When the JTAG Download window
appears, make sure that Verify that the update is
required before download of FPGA file is selected.
Click OK, and the program will check to see if the
needs updating. Proceed to download if needed.
Quit terminates the program.
Run Options Dialog

The Run Options dialog allows the user to choose the diagnostics will be
executed. Two options are given: “Run tests by loop count” and “Run tests until I
stop them.” Running the diagnostics by loop count will run the selected
diagnostics for a specified number of cycles. Running the diagnostics by the
other method will cycle the selected diagnostic tests until the user issues a
cancel request.
Notes on diagnostic execution:
The back projection unit test executes separate from the rest of the diagnostics.
When the unit test is run with the other diagnostics, the user must issue two
cancel commands to return to the main GUI. The first cancel command will cancel the standard diagnostics and the
second cancels the unit test.
The Output Window

The output window is where all feedback from the
diagnostics appears. Many message types are
displayed ranging from information to errors. There are
two command buttons strictly associated with the
output window: Output Options and Clear Output.
The Progress Indicators

The progress indicators are only used during
diagnostic execution cycles. Displayed
information includes tests remaining, tests
completed, tests passed, and tests failed. A
progress bar is also used to show percentage
completion of the queued diagnostics.
Typical Diagnostic Execution Cycle

A typical diagnostic execution starts with the user selecting the tests to run and setting any options. The user then
confirms the selections by clicking the “Run Selected” button. Once this is done the run options dialog will appear. The
user will select whether to run by loop count or until response. After the user clicks OK, the program will generate the
test execution queue and begin running the tests. At this point, the user can wait till the diagnostics complete or click the
“Stop Diagnostics” button to cancel the current queue and return to the main GUI.
Notes about the unit test utProjectionTG:

The “Projection Unit Test” check box included with the diagnostics is in a separate execution loop due to the
environment conditions utProjectionTG.exe requires. Therefore, if the user has queued the projection unit test with the
other diagnostics, the user will have to cancel twice to return to the main GUI.
3DBP Software
To check the Driver Version
1. Click Start.
2. On the Start menu, right-click on My Computer and select Manage from the drop-down menu.
3. Click on Device Manager, then from the list that appears, double-click on Philips back projection devices.
4. Under Philips back projection devices, double-click on 3DBP Backprojection board.
5. On the Dialog Window that appears, click on the Driver tab to view the Driver information.
Reload the 3DBP driver

1. Click Start, then right-click on My Computer.
2. Select Manage.
3. Click Device manager.
4. Click the [+] on Philips back projection devices.
5. Right-click on 3DBP Backprojection board, and from the menu, select Update driver…
6. If the Hardware Update Wizard wizard appears asking to connect to Windows Update to search for a driver, select
No, not this time. Then click Next.
7. On the Hardware Update Wizard, select “Install from a list or specific location (Advanced)”.
8. Click Next.
9. Select “Don't search. I will choose the driver to install”.
10. Click Next.
11. Click Have Disk…
12. Click the Browse button, and navigate to C:\Program Files\Philips\CIRS\drivers.
NOTE If the Open Window automatically shows the drivers folder, make sure that the full path to the folder is
C:\Program Files\Philips\CIRS\drivers!
13. In the Drivers Folder, select 3DBP, then click Open. Click OK.
14. Click Next, then click Finish.
15. Close the Computer Management Window.
Reload 3DBP FPGA

1. Double-click on the 3DBP Diagnostics icon to start the CIRS 3DBP Board Diagnostics application.
2. The Hardware Configuration section on the 3DBP Diagnostics window will show which model 3DBP board is
installed (designated by No. of ASICs).
3. On the 3DBP Board Diagnostics window, click JTAG Download to launch the JTAG Download window.
4. On the JTAG Download window, select “Bypass verify and download FPGA file”.
5. On the JTAG Download window, click Select File.
6. Navigate to the C:\ProgramFiles\Philips\CIRS\3DBP folder.
NOTE If the Open Window automatically shows the 3DBP folder, make sure that the full path to the folder is
C:\Program Files\Philips\CIRS\3DBP!
7. On the Open File dialog:
• for the 6 ASIC model, select 3DBP_FPGA.svf
• for the 2 ASIC model, select 3DBPLC_FPGA.svf
8. Click Open.
9. On the JTAG Download window, click OK.
10. In the BpDiagGUI window, click OK. This will appear after programming is complete.
11. In the CIRS 3DBP Board Diagnostics window, click Quit.
12. Power off the server:
a. Right-click on the Windows Taskbar, and select Task Manager.
b. On Task Manager, click Shut Down > Turn Off.
c. Click Yes on any messages that appear.
d. Click OK on the Remote Desktop Disconnected prompt.
Host desktop.
13. Power on the server by depressing and holding the switch on the front of the server until the green light to the left of
the switch illuminates.
Check for Error Messages with EventViewer

TTo use EventViewer:
1. On the Host desktop, double-click on the CIRS Folder.
2. In the CIRS Folder, double-click on the Recon S1, Recon S2, or Recon S3 Remote Desktop icon to connect to that
specific server.
3. On the server Desktop, double-click the EventViewer icon.
Four different EventViewers are available: Application, Security, System, and CIRS. You can filter the logs for a
specific task or by category. The System log contains system level entries for: AcqDriver, 3DBP Driver, and SCSI
controllers (best place to view RAID events). CIRS logs contains all application logs divided in 5 major categories:
• Info – for Engineering debug only
• Status – same as Info but at the key points
• Warning – workarounds for known software problem
• Error - error reported by specific task
• RPC Call - records of all RPC calls made to/from the Host
The following tasks have entries in CIRS logs:

• Supervisor
• Suprsvc – service which starts the Supervisor
• ImageProcess
• SeriesProcess
Additional:
• SuprNodeSvr
• ResMgr
• ImgNodeSvr
Event Examples
Figure 10: AcqDriver error in System Log “Invalid G-Frame header: G-Frame Number” points to the DMC
hardware problem.
Figure 11: Info entry from Supervisor indicates that startup was successful.
Figure 12: EventViewer Filter set to Errors/Warnings. Warning entry by ImageProcess task group points to
workaround/known software issue.
Figure 13: Remote Procedure Call (RPC) error indicates that client’s RPC Server is unreachable.
Figure 14: To filter Logs by task and/or message category, select View > Filter.
Known error events that can be ignored
Known error events in Windows SYSTEM Log that can be ignored:

Source Event ID Description Comment
Service
The following boot-start or system-start driver(s) failed to
Control 7026 If keyboard was connected and then later removed.
load: i8042prt
Manager
The machine wide Default Launch and Activation security
descriptor is invalid. It contains Access Control Entries with
permissions that are invalid. The requested action was
DCOM 10020 Several occur following bootup
therefore not performed. This security permission can be
corrected using the Component Services administrative
tool.
Can be ignored only if it occurs immediately
following boot up and then ceases. This can occur
DCOM was unable to communicate with the computer
if S2/S3 bootup lags S1. If errors persist beyond 3
DCOM 10009 192.168.0.210 (or 220) using any of the configured
minutes from boot then the error cannot be
protocols.
ignored and may be indicative of a communication
problem with S2/S3 or # nodes incorrectly set.
The time service has not been able to synchronize the
W32Time system time for 49152 seconds because none of the time
36
(warning) providers has been able to provide a usable time stamp. The
system clock is un-synchronized.
Known error events in S1 Windows CIRS Log that can be ignored:

SuprThreadMgr.cpp(100): Caught exception in LIST_MDUS_THREAD This sequence can occur when
Supervisor 0
(192.168.0.100:5812:r2h1:2) host is shut down
HRIFHost_Client.cpp(615): Error #1727 -The "r2h1ListMDUsReady" RPC failed (and
Supervisor 0
might not have executed)
Server Address: 192.168.0.100:5812 RPC Name: r2h1Error RPC CALL FAILED
Supervisor 2
<<RPC Parameters:>> Error #11, ReqID #32773
Server Address: 192.168.0.100:5812, RPC Name: r2h1RawAdded
Supervisor 2 Occurs intermittently
RPC CALL FAILED
ProxyServer.cpp(91): Exception occurred (type: class CCirsExcept). Error #12 - RCN
#454405C4:001 ('localhost' #2272/0x81) - Exception occurred (type: class CCirsExcept)
at AcqInfo.cpp(143): Error #12 - Error calling GetAcqProess - HRESULT: This sequence occurs when
0x80040208( A user-supplied component or subscriber raised an exception ) host cancels scan. It can occur
ImageProcess 0
Detail (from ResMgr.DiskHandlerSvc.1): possibly when tube heat limits
From .\sft\ResMgr\DiskHandlerSvc\DiskHandlerSvc.cpp, line: 326 - Exception occurred are reached.
(type: class Cirs::BasicExceptStream<class CCirsExcept>) at DiskHandlerSvc.h(269):
Error #12 - Read 0 object from pipe. (from RebinI3DTG-01)
ImgNodeCtrl.cpp(654): Exception occurred (type: class CCirsExcept) at
AcqInfo.cpp(143): Error #12 - Error calling GetAcqProess - HRESULT:
0x80040208( A user-supplied component or subscriber raised an exception )
ImgNodeSvr 0 Detail (from ResMgr.DiskHandlerSvc.1): From
.\sft\ResMgr\DiskHandlerSvc\DiskHandlerSvc.cpp, line: 326 - Exception occurred (type:
class Cirs::BasicExceptStream<class CCirsExcept>) at DiskHandlerSvc.h(269): Error #12
- Read 0 object from pipe. (from RebinI3DTG-01)

AcqInfo.cpp(143): Error #12 - Error calling GetAcqProess - HRESULT:
Detail (from ResMgr.DiskHandlerSvc.1):
ImgNodeSvr 0
From .\sft\ResMgr\DiskHandlerSvc\DiskHandlerSvc.cpp, line: 326 - Exception occurred
Error #12 - Read 0 object from pipe. (from RebinI3DTG-01)
AcqInfo.cpp(142): HRESULT:
Detail (from ResMgr.DiskHandlerSvc.1):
ImgNodeSvr 0
From .\sft\ResMgr\DiskHandlerSvc\DiskHandlerSvc.cpp, line: 326 - Exception occurred
Error #12 - Read 0 object from pipe.
DiskHandlerSvc.h(193): Exception occurred (type: class Cirs::BasicExceptStream<class
ResMgr 0
CCirsExcept>) at DiskHandlerSvc.h(269): Error #12 - Read 0 object from pipe.
OsSETranslator.cpp(244):
***Dumping Call Stack Trace for thread: 544 of process: 740 ***
70632E72: <no module>! <no symbol> (No File: Line -1)
00519236: C:\Program Files\Philips\CIRS\Supervisor.exe! h2r1_GetAppParam + 182 bytes
(f:\ccviewsnap\cirs_dev1_releaseview_sn\cirs_code\recon\sft\hrif\src\hrifsupr_server.cpp: This sequence can occur
Supervisor 0
Line 392) following server shutdown
77E79DC9: C:\WINDOWS\system32\RPCRT4.dll! CheckVerificationTrailer + 117 bytes
(No File:
… whole bunch more stuff not shown
***Call Stack Trace Dumped***

OsSETranslator.cpp(262): Error #0xC0000005 -
EXCEPTION_ACCESS_VIOLATION occurred at 0x70632E72 attempting to read
Supervisor 0
from address 0x70632E72
UNEXPECTED EXCEPTION occurred in h2r1_GetAppParam
CTReconClient.cpp(639): Error #0xFFFFFFFF - GetAppParam(
Supervisor 0
SUPR_GET_STUDY_LIST_APP_PARAM ) failed
Server Address: localhost:5804
This sequence can occur
Supervisor 2 RPC Name: h2r1CheckComm
following server shutdown
RPC CALL FAILED
HRIFSupr_Client.cpp(796): Error #1717 - RPC error 000006B5 (#1717) occurred calling
0
"h2r1CheckComm"The Supervisor is not responding
Various error messages including: About 13 or 14 of these occur
• cqGemDiagThread.cpp(52): Acquire error: Unknown errorWaitForStartOfSeries Gantry data for each loop of the acquisitor
error found while wait for start of series. diagnostic. Ignore these and
AcqDiagGUI 0 • AcqGemDiagThread.cpp(52): Acquire error: Unknown errorAcquireWorkQueue rely on the acquisitor diagnostic
WaitForShotData failed
interface to determine if there
• AcqGemDiagThread.cpp(52): Acquire error: Unknown errorWaitForStartOfShot Gantry data
error found while wait for start of shot. is a problem.
3UD3/3UQ3 Server BIOS POST Messages and Codes

This section descriptions of BIOS POST Message and BIOS POST codes that you can use to help troubleshoot the
3UQ3 servers.
NOTE The motherboard is not an FRU. If motherboard faults are detected the server must be replaced. However
a quick look at the indicated hardware may reveal a loose cable or memory card that simply needs to be
re-seated.
NOTE If you have to return a server, make sure to list any POST messages or codes on the Granite CIRS Server
Field Failure Report.
NOTE The following information is from the SuperMicro X7DB8-X/X7DBE-X User’s Guide. You can access this
document at www.supermicro.com.
BIOS POST Messages

During the Power-On Self-Test (POST), the BIOS will check for problems. If a problem is found, the BIOS will activate
an alarm or display a message. The following is a list of such BIOS messages:
Table 1: 3UD3/3UQ3 BIOS POST Messages
Message Problem
Fixed disk is not working or not configured properly. Check to see if fixed disk is
Failure Fixed Disk
attached properly. Run Setup. Find out if the fixed-disk type is correctly identified.
Stuck key Stuck key on keyboard.
Keyboard error Keyboard not working.
Keyboard Controller Failed Keyboard controller failed test.
Shadow Ram Failed at offset: nnnn Shadow RAM failed at offset nnnn of the 64k block at which the error was detected.
System RAM Failed at offset: nnnn System RAM failed at offset nnnn of in the 64k block at which the error was detected.
Extended RAM Failed at offset: nnnn Extended memory not working or not configured properly at offset nnnn.
Message Problem
The CMOS clock battery indicator shows the battery is dead. Replace the battery and
System battery is dead - Replace and run SETUP
run Setup to reconfigure the system.
System CMOS has been corrupted or modified incorrectly, perhaps by an application
System CMOS checksum bad - Default configuration program that changes data stored in CMOS. The BIOS installed Default Setup Values.
used Use the Granite SOFGR CD to re-flash/restore BIOS (see Philips, System Diagnostic
Utilities (PN SOFGR-064) Rev. 21 or higher on page 239).
System timer error The timer test failed. Requires repair of system board.
Real time clock error Real-Time Clock fails BIOS hardware test. May require board repair.
Check date and time settings BIOS found date or time out of range and reset the Real-Time Clock.
Previous POST did not complete successfully. POST loads default values and offers to
run Setup. If the failure was caused by incorrect values and they are not corrected, the
next boot will likely fail. On systems with control of wait states, improper Setup settings
Previous boot incomplete - Default configuration used
can also terminate POST and cause this error on the next boot. Use the Granite SOFGR
CD to re-flash/restore BIOS (see Philips, System Diagnostic Utilities (PN SOFGR-064)
Rev. 21 or higher on page 239). This error is cleared the next time the system is booted.
Memory Size found by POST differed from CMOS Memory size found by POST differed from CMOS.
Drive A: or B: is present but fails the BIOS POST diskette tests. Check to see that the
Diskette drive A error
drive is defined with the proper diskette type in Setup and that the diskette drive is
Diskette drive B error
attached correctly.
Incorrect Drive A type - run SETUP Type of floppy drive A: not correctly identified in Setup.
Incorrect Drive B type - run SETUP Type of floppy drive B: not correctly identified in Setup.
System cache error - Cache disabled RAM cache failed and BIOS disabled the cache.
CPU ID: CPU socket number for Multi-Processor error.
Message Problem
EISA CMOS not writeable ServerBIOS2 test error: Cannot write to EISA CMOS.
ServerBIOS2 test error: Cannot write to extended DMA (Direct Memory Access)
DMA Test Failed
registers.
Software NMI Failed ServerBIOS2 test error: Cannot generate software NMI (Non-Maskable Interrupt).
Fail-Safe Timer NMI Failed ServerBIOS2 test error: Fail-Safe Timer takes too long.
device Address Conflict Address conflict for specified device.
Run ISA or EISA Configuration Utility to resolve resource conflict for the specified
Allocation Error for: device
device.
CD ROM Drive CD ROM Drive identified.
Entering SETUP ... Starting Setup program
The hex number nnnn is a map of the bits at the RAM address which failed the memory
Failing Bits: nnnn test. Each 1 (one) in the map indicates a failed bit. See errors 230, 231, or 232 above for
offset address of the failure in System, Extended, or Shadow memory.
Fixed Disk n Fixed disk n (0-3) identified.
Invalid System Configuration Data Problem with NVRAM (CMOS) data.
I/O device IRQ conflict I/O device IRQ conflict error.
PS/2 Mouse Boot Summary Screen: PS/2 Mouse installed.
nnnn kB Extended RAM Passed Where nnnn is the amount of RAM in kilobytes successfully tested.
nnnn Cache SRAM Passed Where nnnn is the amount of system cache in kilobytes successfully tested.
nnnn kB Shadow RAM Passed Where nnnn is the amount of shadow RAM in kilobytes successfully tested.
nnnn kB System RAM Passed Where nnnn is the amount of system RAM in kilobytes successfully tested.
Message Problem
One or more I2O Block Storage Devices were There was not enough room in the IPL table to display all installed I2O block-storage
excluded from the Setup Boot Menu devices.
Operating system cannot be located on either drive A: or drive C:. Enter Setup and see
Operating system not found
if fixed disk and drive A: are properly identified.
Parity error found in the system bus. BIOS attempts to locate the address and display it
on the screen. If it cannot locate the address, it displays ????. Parity is a method for
Parity Check 1 nnnn
checking errors in binary data. A parity error indicates that some data has been
corrupted.
Parity error found in the I/O bus. BIOS attempts to locate the address and display it on
Parity Check 2 nnnn
the screen. If it cannot locate the address, it displays ????.
Displayed after any recoverable error message. Press <F1> to start the boot process or
Press <F1> to resume, <F2> to Setup, <F3> for <F2> to enter Setup and change the settings. Press <F3> to display the previous screen
previous (usually an initialization error of an Option ROM, i.e., an add-on card). Write down and
follow the information shown on the screen.
Press <F2> to enter Setup Optional message displayed during POST. Can be turned off in Setup.
PS/2 Mouse: PS/2 mouse identified.
One or more unclaimed block storage devices have the Configuration Request bit set in
Run the I2O Configuration Utility
the LCT. Run an I2O Configuration Utility (e.g. the SAC utility).
System BIOS shadowed System BIOS copied to shadow RAM.
Displays the address nnnn of the upper limit of Upper Memory Blocks, indicating
UMB upper limit segment address: nnnn
released segments of the BIOS which can be reclaimed by a virtual memory manager.
Video BIOS shadowed Video BIOS successfully copied to shadow RAM.
BIOS POST CODES

This section lists the POST (Power On Self Test) codes for the PhoenixBIOS. POST codes are divided into two
categories: recoverable and terminal.
NOTE Since the POST codes occur during boot-up, you will need to connect a Keyboard, monitor, and mouse to
the server to view the codes.
Recoverable POST Errors

When a recoverable type of error occurs during POST, the BIOS will display an POST code that describes the problem.
BIOS may also issue one of the following beep codes:
• 1 long and two short beeps - video configuration error
• 1 repetitive long beep - no memory detected
Terminal POST Errors

If a terminal type of error occurs, BIOS will shut down the system. Before doing so, BIOS will write the error to port 80h,
attempt to initialize video and write the error in the top left corner of the screen. The following is a list of codes that may
be written to port 80h.
Table 2: 3UD3/3UQ3 Terminal POST Errors
POST Code Description

01h IPMI Initialization
02h Verify Real Mode
03h Disable Non-Maskable Interrupt (NMI)
04h Get CPU type
06h Initialize system hardware
07h Disable shadow and execute code from the ROM.
08h Initialize chipset 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
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 Reset PCI Bus Mastering devices
14h Initialize keyboard controller
16h 1-2-2-3 BIOS ROM checksum
17h Initialize cache before memory Auto size
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
28h Auto size DRAM
29h Initialize POST Memory Manager

2Ah Clear 512 kB base RAM
2Ch 1-3-4-1 RAM failure on address line xxxx*
2Eh 1-3-4-3 RAM failure on data bits xxxx* of low byte of memory bus
2Fh Enable cache before system BIOS shadow
32h Test CPU bus-clock frequency
33h Initialize Phoenix Dispatch Manager
36h Warm start shut down
38h Shadow system BIOS ROM
3Ah Auto size cache
3Ch Advanced configuration of chipset registers
3Dh Load alternate registers with CMOS values
41h Initialize extended memory for RomPilot (optional)
42h Initialize interrupt vectors
45h POST device initialization
46h 2-1-2-3 Check ROM copyright notice
48h Check video configuration against CMOS
49h Initialize PCI bus and devices
4Ah Initialize all video adapters in system
4Bh QuietBoot start (optional)
4Ch Shadow video BIOS ROM
4Eh Display BIOS copyright notice

4Fh Initialize MultiBoot
50h Display CPU type and speed
51h Initialize EISA board (optional)
52h Test keyboard
54h Set key click if enabled
55h Enable USB devices
58h 2-2-3-1 Test for unexpected interrupts
59h Initialize POST display service
5Ah Display prompt “Press <ESC> to enter SETUP”
5Bh Disable CPU cache
5Ch Test RAM between 512 and 640 kB
60h Test extended memory
62h Test extended memory address lines
64h Jump to UserPatch1
66h Configure advanced cache registers
67h Initialize Multi Processor APIC
68h Enable external and CPU caches
69h Setup System Management Mode (SMM) area
6Ah Display external L2 cache size
6Bh Load custom defaults (optional)
6Ch Display shadow-area message

70h Display error messages
72h Check for configuration errors
76h Check for keyboard errors
7Ch Set up hardware interrupt vectors
7Dh Initialize Intelligent System Monitoring (optional)
7Eh Initialize coprocessor if present
80h Disable onboard Super I/O ports and IRQs (optional)
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
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 controllers

91h Initialize local-bus hard-disk controllers
93h Build MPTABLE for multi-processor boards
95h Install CD ROM for boot
96h Clear huge ES segment register
97h Fix up Multi Processor table
1-2 Search for option ROMs and shadow if successful. One long, two short beeps on checksum
98h
failure
99h Check for SMART Drive (optional)
9Ch Set up 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 <ESC> prompt
AAh Scan for <ESC> key stroke
ACh Enter SETUP
AEh Clear Boot flag
B0h Check for errors

B1h Inform RomPilot about the end of POST (optional)
B2h POST done - prepare to boot operating system
B4h 1 One short beep before boot
B5h Terminate QuietBoot (optional)
B6h Check password (optional)
B7h Initialize ACPI BIOS and PPM Structures
B9h Prepare Boot
BAh Initialize SMBIOS
BCh Clear parity checkers
BDh Display MultiBoot menu
BEh Clear screen (optional)
BFh Check virus and backup reminders
C0h Try to boot with INT 19
C1h Initialize POST Error Manager (PEM)
C2h Initialize error logging
C3h Initialize error display function
C4h Initialize system error flags
C6h Console redirection init.
C7h Unhook INT 10h if console redirection enabled
C8h Force check (optional)
C9h Extended ROM checksum (optional)

CDh Reclaim console redirection vector
D2h Unknown interrupt
D4h Check Intel Branding string
D8h Alert Standard Format initialization
D9h Late init for IPMI
DEh Log error if micro-code not updated properly
The following are for boot block in Flash ROM

E0h Initialize the chipset
E1h Initialize the bridge
E2h Initialize the CPU
E3h Initialize system timer
E4h Initialize system I/O
E5h Check force recovery boot
E6h Checksum BIOS ROM
E7h Go to BIOS
E8h Set Huge Segment
E9h Initialize Multi Processor
EAh Initialize OEM special code
EBh Initialize PIC and DMA
ECh Initialize Memory type

EDh Initialize Memory size
EEh Shadow Boot Block
EFh System memory test
F0h Initialize interrupt vectors
F1h Initialize Run Time Clock
F2h Initialize video
F3h Initialize System Management Manager
F4h Output one beep
F5h Clear Huge Segment
F6h Boot to Mini DOS
F7h Boot to Full DOS
* If the BIOS detects error 2C, 2E, or 30 (base 512K RAM error), it displays an additional word-bitmap (xxxx) indicating the
address line or bits that failed. For example, “2C 0002” means address line 1 (bit one set) has failed. “2E 1020" means data bits
12 and 5 (bits 12 and 5 set) have failed in the lower 16 bits. The BIOS also sends the bitmap to the port-80 LED display. It first
displays the checkpoint code, followed by a delay, the high-order byte, another delay, and then the loworder byte of the error. It
repeats this sequence continuously.
VSD4 Server BIOS POST Messages and Codes

This section descriptions of BIOS POST Message and BIOS POST codes that you can use to help troubleshoot the
VSD4 servers.
re-seated.
BIOS POST Messages

During the Power-On Self-Test (POST), the BIOS will check for problems. If a problem is found, the BIOS will activate
an alarm or display a message. The following is a list of such BIOS messages:
Table 3: VSD4 BIOS POST Messages
Message Problem
Fixed disk is not working or not configured properly. Check to see if fixed disk is
Failure Fixed Disk
attached properly. Run Setup. Find out if the fixed-disk type is correctly identified.
Stuck key Stuck key on keyboard.
Keyboard error Keyboard not working.
Keyboard Controller Failed Keyboard controller failed test.
Shadow Ram Failed at offset: nnnn Shadow RAM failed at offset nnnn of the 64k block at which the error was detected.
System RAM Failed at offset: nnnn System RAM failed at offset nnnn of in the 64k block at which the error was detected.
Extended RAM Failed at offset: nnnn Extended memory not working or not configured properly at offset nnnn.
Message Problem
The CMOS clock battery indicator shows the battery is dead. Replace the battery and
System battery is dead - Replace and run SETUP
run Setup to reconfigure the system.
System CMOS has been corrupted or modified incorrectly, perhaps by an application
System CMOS checksum bad - Default configuration program that changes data stored in CMOS. The BIOS installed Default Setup Values.
used Use the Granite SOFGR CD to re-flash/restore BIOS (see Philips, System Diagnostic
Utilities (PN SOFGR-064) Rev. 21 or higher on page 269).
System timer error The timer test failed. Requires repair of system board.
Real time clock error Real-Time Clock fails BIOS hardware test. May require board repair.
Check date and time settings BIOS found date or time out of range and reset the Real-Time Clock.
Previous POST did not complete successfully. POST loads default values and offers to
run Setup. If the failure was caused by incorrect values and they are not corrected, the
next boot will likely fail. On systems with control of wait states, improper Setup settings
Previous boot incomplete - Default configuration used
can also terminate POST and cause this error on the next boot. Use the Granite SOFGR
CD to re-flash/restore BIOS (see Philips, System Diagnostic Utilities (PN SOFGR-064)
Rev. 21 or higher on page 242). This error is cleared the next time the system is booted.
Memory Size found by POST differed from CMOS Memory size found by POST differed from CMOS.
Drive A: or B: is present but fails the BIOS POST diskette tests. Check to see that the
Diskette drive A error
drive is defined with the proper diskette type in Setup and that the diskette drive is
Diskette drive B error
attached correctly.
Incorrect Drive A type - run SETUP Type of floppy drive A: not correctly identified in Setup.
Incorrect Drive B type - run SETUP Type of floppy drive B: not correctly identified in Setup.
System cache error - Cache disabled RAM cache failed and BIOS disabled the cache.
CPU ID: CPU socket number for Multi-Processor error.
Message Problem
EISA CMOS not writeable ServerBIOS2 test error: Cannot write to EISA CMOS.
ServerBIOS2 test error: Cannot write to extended DMA (Direct Memory Access)
DMA Test Failed
registers.
Software NMI Failed ServerBIOS2 test error: Cannot generate software NMI (Non-Maskable Interrupt).
Fail-Safe Timer NMI Failed ServerBIOS2 test error: Fail-Safe Timer takes too long.
device Address Conflict Address conflict for specified device.
Run ISA or EISA Configuration Utility to resolve resource conflict for the specified
Allocation Error for: device
device.
CD ROM Drive CD ROM Drive identified.
Entering SETUP ... Starting Setup program
The hex number nnnn is a map of the bits at the RAM address which failed the memory
Failing Bits: nnnn test. Each 1 (one) in the map indicates a failed bit. See errors 230, 231, or 232 above for
offset address of the failure in System, Extended, or Shadow memory.
Fixed Disk n Fixed disk n (0-3) identified.
Invalid System Configuration Data Problem with NVRAM (CMOS) data.
I/O device IRQ conflict I/O device IRQ conflict error.
PS/2 Mouse Boot Summary Screen: PS/2 Mouse installed.
nnnn kB Extended RAM Passed Where nnnn is the amount of RAM in kilobytes successfully tested.
nnnn Cache SRAM Passed Where nnnn is the amount of system cache in kilobytes successfully tested.
nnnn kB Shadow RAM Passed Where nnnn is the amount of shadow RAM in kilobytes successfully tested.
nnnn kB System RAM Passed Where nnnn is the amount of system RAM in kilobytes successfully tested.
Message Problem
One or more I2O Block Storage Devices were There was not enough room in the IPL table to display all installed I2O block-storage
excluded from the Setup Boot Menu devices.
Operating system cannot be located on either drive A: or drive C:. Enter Setup and see
Operating system not found
if fixed disk and drive A: are properly identified.
Parity error found in the system bus. BIOS attempts to locate the address and display it
on the screen. If it cannot locate the address, it displays ????. Parity is a method for
Parity Check 1 nnnn
checking errors in binary data. A parity error indicates that some data has been
corrupted.
Parity error found in the I/O bus. BIOS attempts to locate the address and display it on
Parity Check 2 nnnn
the screen. If it cannot locate the address, it displays ????.
Displayed after any recoverable error message. Press <F1> to start the boot process or
Press <F1> to resume, <F2> to Setup, <F3> for <F2> to enter Setup and change the settings. Press <F3> to display the previous screen
previous (usually an initialization error of an Option ROM, i.e., an add-on card). Write down and
follow the information shown on the screen.
Press <F2> to enter Setup Optional message displayed during POST. Can be turned off in Setup.
PS/2 Mouse: PS/2 mouse identified.
One or more unclaimed block storage devices have the Configuration Request bit set in
Run the I2O Configuration Utility
the LCT. Run an I2O Configuration Utility (e.g. the SAC utility).
System BIOS shadowed System BIOS copied to shadow RAM.
Displays the address nnnn of the upper limit of Upper Memory Blocks, indicating
UMB upper limit segment address: nnnn
released segments of the BIOS which can be reclaimed by a virtual memory manager.
Video BIOS shadowed Video BIOS successfully copied to shadow RAM.
BIOS POST CODES

This section lists the POST (Power On Self Test) codes for the PhoenixBIOS. POST codes are divided into two
categories: recoverable and terminal.
NOTE Since the POST codes occur during boot-up, you will need to connect a Keyboard, monitor, and mouse to
the server to view the codes.
Recoverable POST Errors

When a recoverable type of error occurs during POST, the BIOS will display an POST code that describes the problem.
BIOS may also issue one of the following beep codes:
• 1 long and two short beeps - video configuration error
• 1 repetitive long beep - no memory detected
Terminal POST Errors

If a terminal type of error occurs, BIOS will shut down the system. Before doing so, BIOS will write the error to port 80h,
attempt to initialize video and write the error in the top left corner of the screen. The following is a list of codes that may
be written to port 80h.
Table 4: VSD4 Terminal POST Errors

01h IPMI Initialization
02h Verify Real Mode
03h Disable Non-Maskable Interrupt (NMI)
04h Get CPU type
06h Initialize system hardware
07h Disable shadow and execute code from the ROM.
08h Initialize chipset 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
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 Reset PCI Bus Mastering devices
14h Initialize keyboard controller
16h 1-2-2-3 BIOS ROM checksum
17h Initialize cache before memory Auto size
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
28h Auto size DRAM
29h Initialize POST Memory Manager

2Ah Clear 512 kB base RAM
2Ch 1-3-4-1 RAM failure on address line xxxx*
2Eh 1-3-4-3 RAM failure on data bits xxxx* of low byte of memory bus
2Fh Enable cache before system BIOS shadow
32h Test CPU bus-clock frequency
33h Initialize Phoenix Dispatch Manager
36h Warm start shut down
38h Shadow system BIOS ROM
3Ah Auto size cache
3Ch Advanced configuration of chipset registers
3Dh Load alternate registers with CMOS values
41h Initialize extended memory for RomPilot (optional)
42h Initialize interrupt vectors
45h POST device initialization
46h 2-1-2-3 Check ROM copyright notice
48h Check video configuration against CMOS
49h Initialize PCI bus and devices
4Ah Initialize all video adapters in system
4Bh QuietBoot start (optional)
4Ch Shadow video BIOS ROM
4Eh Display BIOS copyright notice

4Fh Initialize MultiBoot
50h Display CPU type and speed
51h Initialize EISA board (optional)
52h Test keyboard
54h Set key click if enabled
55h Enable USB devices
58h 2-2-3-1 Test for unexpected interrupts
59h Initialize POST display service
5Ah Display prompt “Press <ESC> to enter SETUP”
5Bh Disable CPU cache
5Ch Test RAM between 512 and 640 kB
60h Test extended memory
62h Test extended memory address lines
66h Configure advanced cache registers
67h Initialize Multi Processor APIC
68h Enable external and CPU caches
69h Setup System Management Mode (SMM) area
6Ah Display external L2 cache size
6Bh Load custom defaults (optional)
6Ch Display shadow-area message

70h Display error messages
72h Check for configuration errors
76h Check for keyboard errors
7Ch Set up hardware interrupt vectors
7Dh Initialize Intelligent System Monitoring (optional)
7Eh Initialize coprocessor if present
80h Disable onboard Super I/O ports and IRQs (optional)
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
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 controllers

91h Initialize local-bus hard-disk controllers
93h Build MPTABLE for multi-processor boards
95h Install CD ROM for boot
96h Clear huge ES segment register
97h Fix up Multi Processor table
1-2 Search for option ROMs and shadow if successful. One long, two short beeps on checksum
98h
failure
99h Check for SMART Drive (optional)
9Ch Set up 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 <ESC> prompt
AAh Scan for <ESC> key stroke
ACh Enter SETUP
AEh Clear Boot flag
B0h Check for errors

B1h Inform RomPilot about the end of POST (optional)
B2h POST done - prepare to boot operating system
B4h 1 One short beep before boot
B5h Terminate QuietBoot (optional)
B6h Check password (optional)
B7h Initialize ACPI BIOS and PPM Structures
B9h Prepare Boot
BAh Initialize SMBIOS
BCh Clear parity checkers
BDh Display MultiBoot menu
BEh Clear screen (optional)
BFh Check virus and backup reminders
C0h Try to boot with INT 19
C1h Initialize POST Error Manager (PEM)
C2h Initialize error logging
C3h Initialize error display function
C4h Initialize system error flags
C6h Console redirection init.
C7h Unhook INT 10h if console redirection enabled
C8h Force check (optional)
C9h Extended ROM checksum (optional)

CDh Reclaim console redirection vector
D2h Unknown interrupt
D4h Check Intel Branding string
D8h Alert Standard Format initialization
D9h Late init for IPMI
DEh Log error if micro-code not updated properly
The following are for boot block in Flash ROM

E0h Initialize the chipset
E1h Initialize the bridge
E2h Initialize the CPU
E3h Initialize system timer
E4h Initialize system I/O
E5h Check force recovery boot
E6h Checksum BIOS ROM
E7h Go to BIOS
E8h Set Huge Segment
E9h Initialize Multi Processor
EAh Initialize OEM special code
EBh Initialize PIC and DMA
ECh Initialize Memory type

EDh Initialize Memory size
EEh Shadow Boot Block
EFh System memory test
F0h Initialize interrupt vectors
F1h Initialize Run Time Clock
F2h Initialize video
F3h Initialize System Management Manager
F4h Output one beep
F5h Clear Huge Segment
F6h Boot to Mini DOS
F7h Boot to Full DOS
* If the BIOS detects error 2C, 2E, or 30 (base 512K RAM error), it displays an additional word-bitmap (xxxx) indicating the
address line or bits that failed. For example, “2C 0002” means address line 1 (bit one set) has failed. “2E 1020" means data bits
12 and 5 (bits 12 and 5 set) have failed in the lower 16 bits. The BIOS also sends the bitmap to the port-80 LED display. It first
displays the checkpoint code, followed by a delay, the high-order byte, another delay, and then the loworder byte of the error. It
repeats this sequence continuously.
Intel Confidence Tests for S2/S3 version 3 (p/n 4535 671 02401)
NOTE If Intel Confidence Test hangs, the proprietary cards (ACQ and 3DBP) must be removed in order to run
the diagnostics.
1. In order to run Intel Confidence Tests, insert the CD marked "Philips, System Diagnostic Utilities, Part Number
SOFGR-064, Revision 00X, Disk 1 of 1" and re-boot the server. The server will boot from the CD, and you will see
the following menu:
2. Select, 1. Intel Confidence tests for S1V1/ S2 or S3 Versions 1,2 &3 /Vs1 V1 only
3. Select either 1 for Quick Test, or 2 for Full Test.
4. If the test completes successfully, you will see the following screen:
5. In addition, you can view the test results and any errors by looking at the test.sum and error.log files.
For example,
• at the C:\ prompt, type test.sum
• at the C:\ prompt, type error.log
Since these files are larger than one screen size, they will quickly scroll past. You can use ‘more.exe’ from CD (A:\)
• at the C:\ prompt, type a: \more.exe test.sum
• Or, a: \more.exe error.log
Troubleshoot S2/S3 version 4 and version 5

NOTE The motherboard is not an FRU. If motherboard faults are detected the server must be replaced.
NOTE The following information is from the Intel® Server Board SE7520JR2 User Guide. You can access this
document at www.intel.com.
LED Information for the Intel SE7520jr2 motherboard
The Intel® Server Board SE7520JR2 includes LEDs that can aid in troubleshooting your system. A table of some of
these LEDs with a description of their use is listed below.
LED Name Function Location Color Notes
Green = No Fault
Green Blink = degraded
Control panel and board
System fault Visible fault warning Green or Amber Amber = critical error or non-
rear left corner
recoverable
Amber blink = non-critical
ATA and SCSI drive
Control panel Control panel Green Blinking = Activity. No action required.
activity
Identify failing memory
Memory fault 1–6 DIMM end rear of board Amber On = Fault
module
See the POST code table in the Intel®
Each LED can be
Diagnostic LEDs. 1–4 Server Board SE7520JR2 Technical Product
Displays port 80 POST codes Center back edge of board Off, Green, Amber,
(LSB, bit1, bit2, MSB) Specification. You can access this
Red
document at www.intel.com.
1” behind processor
CPU 1 & 2 Fault Identify processor failure Amber On = Fault
socket
Identify 5v standby power on
5v Standby Front left board Amber On = 5v standby power on
state
Off = Power is off (off or S5)
Identify the power state of
Power LED Control Panel Green On = Power on or S0)
the system
Slow Blink = Low power state (S1 – S3)
BIOS POST Beep Codes for the Intel SE7520jr2 motherboard

NOTE The following information is from the Intel® Server Board SE7520JR2 User Guide.
The table below lists the POST (Power-on Self Test) error beep codes. Prior to system video initialization, the BIOS
uses these beep codes to inform users of error conditions. Please note that not all error conditions are supported by
BIOS beep codes.
Table 5: POST Error Beep Codes

Number of Beeps Reason for the beeps and action to take
1, 2, or 3 Memory error. Reseat the memory or replace the DIMMs with known good modules.
Fatal error indicating a possible serious system problem. Remove all add-in cards and re-start the system.
If the error still occurs, contact your system manufacturer. If the beep codes are not generated after the
4 – 7 or 9 – 11
add-in cards are removed, insert the cards one at a time, booting the system between each card addition,
until the beeps again occur to reveal the malfunctioning card.
Replace or reseat the system video add-in card. If on-board video is being used, the server board may be
8
faulty.
In addition to the beep codes above, additional beep codes are provided if an Intel® Management Module is installed.
The Intel Management Modules provide the following additional beep codes.
Table 6: Error Beep Codes Provided by Intel® Management Modules

Beep Code Reason for the beeps and action to take
1 Control panel CMOS clear has been initiated.
1-5-1-1 Processor failure. Reseat or replace the failed processor.
1-5-2-1 No processor is installed or the CPU 1 socket is empty. Reseat or replace the failed processor.
Processor configuration error or CPU 1 socket is empty. Reseat or replace the failed processor. In a two-processor
1-5-2-3
system, make sure the processors are identical.
1-5-2-4 Front-side bus select configuration error.
1-5-4-2 DC power unexpectedly lost.
1-5-4-3 Chipset control failure.
1-5-4-4 Power control failure.
Troubleshoot the 2UQ server

re-seated.
NOTE The information in this section is from the Intel® Server Board S5000PAL User’s Guide and Intel® Server
Board S5000PAL/S5000XAL Technical Product Specification. See www.intel.com for more information.
There are various ways you can troubleshoot the 2UQ server:
• Intel® Light Guided Diagnostics on page 205
• BIOS POST Beep Codes for the Intel S5000PAL motherboard on page 217
• POST Error Messages and Handling on page 218
Intel® Light Guided Diagnostics

NOTE The information in this section is from the Intel® Server Board S5000PAL User’s Guide and Intel® Server
Board S5000PAL/S5000XAL Technical Product Specification. See www.intel.com for more information.
The server board has several on-board diagnostic LEDs to assist in troubleshooting board level issues. This section
shows where each LED is located and provides a usage description.
A. POST Code LEDs (see page 211)

B. ID LED (see page 206)
C. Status LED (see page 206)
D. DIMM A1 Fault (see page 208)
E. DIMM A2 Fault (see page 208)
F. DIMM B1 Fault (see page 208)
G. DIMM B2 Fault (see page 208)
H. DIMM C1 Fault (see page 208)
I. DIMM C2 Fault (see page 208)
J. DIMM D1 Fault (see page 208)
K. DIMM D2 Fault (see page 208)
L. CPU 1 Fault (see page 209)
M. CPU 2 Fault (see page 209)
N. 5V Standby (see page 210)
System ID LED and System Status LED

The server board provides LEDs for both System ID and System Status. The LEDs are located on the rear of the server
next to the NIC ports.
When the AC power is first applied to the system and 5V-STBY is present, the BMC controller on the server board
requires 15-20 seconds to initialize. During this time, the system status LED will blink, alternating between amber and
green, and the power button functionality of the control panel is disabled preventing the server from powering up. Once
BMC initialization has completed, the status LED will stop blinking and the power button functionality is restored and
can be used to turn on the server.
The bi-color System Status LED operates according to the table below, and on the following page:
Color State Criticality Description

Off N/A Not ready AC power off
Pre DC Power On – 15-20 second BMC Initialization when AC is applied to the server. Control
Green/Amber Alternating Blink Not ready
Panel buttons are disabled until BMC initialization is complete.
Green Solid on System OK System booted and ready.
Color State Criticality Description

System degraded
• Unable to use all of the installed memory (more than one DIMM installed).
• Correctable errors over a threshold of 10 and migrating to a spare DIMM (memory
sparing). This indicates that the user no longer has spared DIMMs indicating a
redundancy lost condition. Corresponding DIMM LED should light up.
• In mirrored configuration, when memory mirroring takes place and system loses
memory redundancy. This is not covered by (2).
Green Blink Degraded
• Redundancy loss such as power-supply or fan. This does not apply to non-redundant
sub-systems.
• PCI-e link errors
• CPU failure / disabled – if there are two processors and one of them fails
• Fan alarm – Fan failure. Number of operational fans should be more than minimum
number needed to cool the system
• Non-critical threshold crossed – Temperature and voltage
Non-fatal alarm – system is likely to fail
• Critical voltage threshold crossed
• VRD hot asserted
Amber Blink Non-critical
• Minimum number of fans to cool the system not present or failed
• In non-sparing and non-mirroring mode if the threshold of ten correctable errors is
crossed within the window
Fatal alarm – system has failed or shutdown
• DIMM failure when there is one DIMM present, no good memory present
• Run-time memory uncorrectable error in non-redundant mode
Critical, non- • IERR signal asserted
Amber Solid on
recoverable • Processor 1 missing
• Temperature (CPU ThermTrip, memory TempHi, critical threshold crossed)
• No power good – power fault
• Processor configuration error (for instance, processor stepping mismatch)
DIMM Fault LEDs

The server board provides a memory fault LED for each DIMM slot. The DIMM fault LED illuminates when the system
BIOS disables the specified DIMM after it reaches a specified number of given failures or if specific critical DIMM
failures are detected.
Processor Fault LED

The server board provides a Processor Fault LED for each of the two processor sockets. These LEDs will illuminate
when a CPU is disabled or a CPU configuration error is detected.
5-Volt Standby LED

Several server management features of this server board require that a 5 volt stand-by voltage be supplied from the
power supply. Some of the features and components that require this voltage be present when the system is “Off”
include the BMC within the ESB-2, onboard NICs, and optional Intel® RMM.
The LED located just below the system recovery jumper block labeled “5V STBY” is illuminated when AC power is
applied to the platform and 5 Volt standby voltage is supplied to the server board by the power supply.
Post Code Diagnostic LEDs

During the system boot process, BIOS executes a number of platform configuration processes, each of which is
assigned a specific hex POST (Power-On Self Test) code number. As each configuration routine is started, BIOS will
display the given POST code to the POST code diagnostic LEDs found on the back edge of the server board. To assist
in troubleshooting a system hang during the POST process, the diagnostic LEDs can be used to identify the last POST
process to be executed.
LEDs
USB Ports
POST Code Diagnostic LED Decoder

During the system boot process, BIOS executes a number of platform configuration processes, each of which is
assigned a specific hex POST code number. As each configuration routine is started, BIOS will display the given POST
code to the POST Code Diagnostic LEDs found on the back edge of the server board. To assist in troubleshooting a
system hang during the POST process, the Diagnostic LEDs can be used to identify the last POST process to be
executed.
Each POST code will be represented by a combination of colors from the four LEDs. The LEDs are capable of
displaying three colors: green, red, and amber.
The table on the following pages provides a description of the POST codes displayed with the LEDs.
Table 7: Diagnostic LED POST Code Decoder

Diagnostic LED Decoder
Checkpoint G=Green, R=Red, A=Amber Description
MSB LSB
Host Processor
0x10h OFF OFF OFF R Power-on initialization of the host processor (bootstrap processor)
0x11h OFF OFF OFF A Host processor cache initialization (including AP)
0x12h OFF OFF G R Starting application processor initialization
0x13h OFF OFF G A SMM initialization
Chipset
0x21h OFF OFF R G Initializing a chipset component
Memory
0x22h OFF OFF A OFF Reading configuration data from memory (SPD on DIMM)
0x23h OFF OFF A G Detecting presence of memory
0x24h OFF G R OFF Programming timing parameters in the memory controller
0x25h OFF G R G Configuring memory parameters in the memory controller
0x26h OFF G A OFF Optimizing memory controller settings
0x27h OFF G A G Initializing memory, such as ECC init
0x28h G OFF R OFF Testing memory
PCI Bus
0x50h OFF R OFF R Enumerating PCI busses
0x51h OFF R OFF A Allocating resources to PCI busses
0x52h OFF R G R Hot Plug PCI controller initialization
0x53h OFF R G A Reserved for PCI bus
0x54h OFF A OFF R Reserved for PCI bus

MSB LSB
0x55h OFF A OFF A Reserved for PCI bus
0x56h OFF A G R Reserved for PCI bus
0x57h OFF A G A Reserved for PCI bus
USB
0x58h G R OFF R Resetting USB bus
0x59h G R OFF A Reserved for USB devices
ATA / ATAPI / SATA
0x5Ah G R G R Resetting PATA / SATA bus and all devices
0x5Bh G R G A Reserved for ATA
SMBUS
0x5Ch G A OFF R Resetting SMBUS
0x5Dh G A OFF A Reserved for SMBUS
Local Console
0x70h OFF R R R Resetting the video controller (VGA)
0x71h OFF R R A Disabling the video controller (VGA)
0x72h OFF R A R Enabling the video controller (VGA)
Remote Console
0x78h G R R R Resetting the console controller
0x79h G R R A Disabling the console controller
0x7Ah G R A R Enabling the console controller
Keyboard (PS2 or USB)
0x90h R OFF OFF R Resetting the keyboard

MSB LSB
0x91h R OFF OFF A Disabling the keyboard
0x92h R OFF G R Detecting the presence of the keyboard
0x93h R OFF G A Enabling the keyboard
0x94h R G OFF R Clearing keyboard input buffer
0x95h R G OFF A Instructing keyboard controller to run Self Test (PS2 only)
Mouse (PS2 or USB)
0x98h A OFF OFF R Resetting the mouse
0x99h A OFF OFF A Detecting the mouse
0x9Ah A OFF G R Detecting the presence of mouse
0x9Bh A OFF G A Enabling the mouse
Fixed Media
0xB0h R OFF R R Resetting fixed media device
0xB1h R OFF R A Disabling fixed media device
0xB2h R OFF A R Detecting presence of a fixed media device (IDE hard drive detection, etc.)
0xB3h R OFF A A Enabling / configuring a fixed media device
Removable Media
0xB8h A OFF R R Resetting removable media device
0xB9h A OFF R A Disabling removable media device
0xBAh A OFF A R Detecting presence of a removable media device (IDE CDROM detection, etc.)
0xBCh A G R R Enabling / configuring a removable media device
Boot Device Selection
0xD0 R R OFF R Trying boot device selection

MSB LSB
0xD1 R R OFF A Trying boot device selection
0xD2 R R G R Trying boot device selection
0xD3 R R G A Trying boot device selection
0xD4 R A OFF R Trying boot device selection
0xD5 R A OFF A Trying boot device selection
0xD6 R A G R Trying boot device selection
0xD7 R A G A Trying boot device selection
0xD8 A R OFF R Trying boot device selection
0xD9 A R OFF A Trying boot device selection
0XDA A R G R Trying boot device selection
0xDB A R G A Trying boot device selection
0xDC A A OFF R Trying boot device selection
0xDE A A G R Trying boot device selection
0xDF A A G A Trying boot device selection
Pre-EFI Initialization (PEI) Core
0xE0h R R R OFF Started dispatching early initialization modules (PEIM)
0xE2h R R A OFF Initial memory found, configured, and installed correctly
0xE1h R R R G Reserved for initialization module use (PEIM)
0xE3h R R A G Reserved for initialization module use (PEIM)
Driver Execution Environment (DXE) Core
0xE4h R A R OFF Entered EFI driver execution phase (DXE)
0xE5h R A R G Started dispatching drivers

MSB LSB
0xE6h R A A OFF Started connecting drivers
DXE Drivers
0xE7h R A A G Waiting for user input
0xE8h A R R OFF Checking password
0xE9h A R R G Entering BIOS setup
0xEAh A R A OFF Flash Update
0xEEh A A A OFF Calling Int 19. One beep unless silent boot is enabled.
0xEFh A A A G Unrecoverable boot failure / S3 resume failure
Runtime Phase / EFI Operating System Boot
0xF4h R A R R Entering Sleep state
0xF5h R A R A Exiting Sleep state
Operating system has requested EFI to close boot services (ExitBootServices ( ) has
0xF8h A R R R
been called)
Operating system has switched to virtual address mode (SetVirtualAddressMap ( ) has

0xF9h A R R A
been called)
0xFAh A R A R Operating system has requested the system to reset (ResetSystem () has been called)
Pre-EFI Initialization Module (PEIM) / Recovery
0x30h OFF OFF R R Crisis recovery has been initiated because of a user request
0x31h OFF OFF R A Crisis recovery has been initiated by software (corrupt flash)
0x34h OFF G R R Loading crisis recovery capsule
0x35h OFF G R A Handing off control to the crisis recovery capsule
0x3Fh G G A A Unable to complete crisis recovery.
BIOS POST Beep Codes for the Intel S5000PAL motherboard

NOTE The following information is from the Intel® Server Board S5000PAL User’s Guide.
The following table lists POST error beep codes. Prior to system Video initialization, BIOS uses these beep codes to
inform users on error conditions. The beep code is followed by a user visible code on POST Progress LEDs (see Post
Code Diagnostic LEDs on page 211).
Table 8: POST Error Beep Codes

Number of Beeps Reason for the beeps and action to take
System halted because a fatal error related to the memory was detected. Re-seat the memory or replace
3
the DIMMs with known good modules.
6 The system has detected a corrupted BIOS in the flash part, and is rolling back to the last good BIOS.
In addition to the beep codes above, additional beep codes are provided if an Intel® Management Module is installed.
The BMC may generate beep codes upon detection of failure conditions. Beep codes are sounded each time the
problem is discovered, such as on each power-up attempt, but are not sounded continuously. Codes that are common
across all Intel® Server Boards and systems that use the Intel® S5000 chipset are listed in Table 7. Each digit in the
code is represented by a sequence of beeps whose count is equal to the digit.
Table 9: Error Beep Codes Provided by Intel® Management Modules

Beep Code Reason for the beeps
1-5-2-1 CPU: Empty slot / population error – Processor slot 1 is not populated.
1-5-2-2 CPU: No processors (terminators only)
CPU: Configuration error (e.g., VID mismatch). Re-seat or replace the failed processor. In a two-processor system,
1-5-2-3
make sure the processors are identical.
1-5-2-4 CPU: Configuration error (e.g., BSEL mismatch)
1-5-4-2 DC power unexpectedly lost.
1-5-4-3 Chipset control failure.
1-5-4-4 Power control failure.
POST Error Messages and Handling

NOTE The following information is from the Intel® Server Board S5000PAL Technical Product Specification.
Whenever possible, the BIOS will output the current boot progress codes on the video screen. The Response section in
the following table is divided into two types:
Pause:The message is displayed in the Error Manager screen, an error is logged to the System Event Log, and user
input is required to continue. The user can take immediate corrective action or choose to continue booting.
Halt:The message is displayed in the Error Manager screen, an error is logged to the System Event Log, and the
system cannot boot unless the error is resolved. The user needs to replace the faulty part and restart the system.
Table 10: POST Error Messages and Handling
Error Code Error Message Response

004C Keyboard / interface error Pause
0012 CMOS date / time not set Pause
5220 Configuration cleared by jumper Pause
5221 Passwords cleared by jumper Pause
5223 Configuration default loaded Pause
0048 Password check failed Halt
0141 PCI resource conflict Pause
0146 Insufficient memory to shadow PCI ROM Pause
8110 Processor 01 internal error (IERR) on last boot Pause
8111 Processor 02 internal error (IERR) on last boot Pause
8120 Processor 01 thermal trip error on last boot Pause
8121 Processor 02 thermal trip error on last boot Pause
8130 Processor 01 disabled Pause
8131 Processor 02 disabled Pause

8160 Processor 01 unable to apply BIOS update Pause
8161 Processor 02 unable to apply BIOS update Pause
8190 Watchdog timer failed on last boot Pause
8198 Operating system boot watchdog timer expired on last boot Pause
0192 L3 cache size mismatch Halt
0194 CPUID, processor family are different Halt
0195 Front side bus mismatch Pause
0197 Processor speeds mismatched Pause
8300 Baseboard management controller failed self-test Pause
8306 Front panel controller locked Pause
8305 Hot swap controller failed Pause
84F2 Baseboard management controller failed to respond Pause
84F3 Baseboard management controller in update mode Pause
84F4 Sensor data record empty Pause
84FF System event log full Pause
8500 Memory Component could not be configured in the selected RAS mode. Pause
8520 DIMM_A1 failed Self Test (BIST). Pause

8524 DIMM_B1 failed Self Test (BIST). Pause
8528 DIMM_C1 failed Self Test (BIST). Pause
8529 DIMM_C2 failed Self Test (BIST). Pause
852A DIMM_C3 failed Self Test (BIST). Pause
852B DIMM_C4 failed Self Test (BIST). Pause
852C DIMM_D1 failed Self Test (BIST). Pause
852D DIMM_D2 failed Self Test (BIST). Pause
852E DIMM_D3 failed Self Test (BIST). Pause
852F DIMM_D4 failed Self Test (BIST). Pause
8540 Memory Component lost redundancy during the last boot. Pause
8580 DIMM_A1 Correctable ECC error encountered. Pause
8584 DIMM_B1 Correctable ECC error encountered. Pause

8588 DIMM_C1 Correctable ECC error encountered. Pause
8589 DIMM_C2 Correctable ECC error encountered. Pause
858A DIMM_C3 Correctable ECC error encountered. Pause
858B DIMM_C4 Correctable ECC error encountered. Pause
858C DIMM_D1 Correctable ECC error encountered. Pause
858D DIMM_D2 Correctable ECC error encountered. Pause
858E DIMM_D3 Correctable ECC error encountered. Pause
858F DIMM_D4 Correctable ECC error encountered. Pause
8600 Primary and secondary BIOS IDs do not match. Pause
8601 Override jumper is set to force boot from lower alternate BIOS bank of flash ROM. Pause
8602 WatchDog timer expired (secondary BIOS may be bad!) Pause
8603 Secondary BIOS checksum fail Pause
Troubleshoot the RAID Array

NOTE S1 versions 1 and 2; 3UD3/3UQ3 versions 1 and 2; and VS1 versions 1, 2, and Plus have a SCSI RAID Array.
The VSD4 server has a SATA RAID Array.
RAID stands for Redundant Array of Independent Disks. A RAID configuration is needed to keep up with the speed of
data acquisition from the gantry. We use software RAID because it is faster than hardware RAID and works well across
multiple SCSI controllers. We use a "Striped volume" (RAID 0) for storing raw data as we receive it from the gantry on
logical drive F: (located on the S1 server).
Also called "stripe" mode, RAID 0 writes "stripes" of data to each disk simultaneously, making it very fast. The disks are
seen logically as one large hard drive. When data is read or written to this drive, it is done in parallel, accessing each of
the drives at the same time to retrieve/store data.
S1 versions 1 and 2; and VS1 versions 1, 2, and Plus use three 15,000 rpm hard disks, each with 36GB of storage. This
combines for a total of about 108GB of storage space. These servers have an on-board Adaptec AIC-7901 SCSI
Controller chip that has 2 channels (A and B) supporting the 3 drives.
The VSD4 has four 73GB SATA drives. This combines for a total of about 292GB of storage space.
Microsoft Windows features and tools (some specialized by the CIRS engineering group) can be used to isolate and
troubleshoot defective RAID components.
For the S1 version 2 (p/n 453567342161), VS1 version 2 (p/n 453567307811), and VS1 Plus (p/n 453567348651)
servers, the FRU level for the SCSI RAID system is the disk drives, replaceable as a three-pack (p/n 453567346201).
See the CIRS Repair/Replace manual for the particular server model/version for information.
For the VSD4 and 3UD3/3UQ3, the FRU level for the SATA RAID system includes the individual disk drives and cables.
See the CIRS Repair/Replace manual for information.
Check Disk Configuration and Health

1. Log on to the VS1/S1/VSD4/3UD3/3UQ3 server from the Host:
a. Open CIRS folder on the Host PC Desktop or Service Laptop.
b. Double-click the Recon-S1 Remote Desktop icon (if the Remote Desktop dialog appears, enter 192.168.0.200
for the IP address, then click the Connect button).
c. On the Remote Desktop dialog that appears, enter 192.168.0.200 for the IP address. Then click the Connect
button.
d. At the Log on prompt, enter “philips_service”. For the Password, use the philips_service password.
e. Click OK.
2. On the VS1/S1 Desktop, click Start, and on the Start Menu right-click on My Computer.
3. Click Manage.
4. On the Computer Management Menu, double-click on Disk Management.
5. A screen similar to the one

at right will appear
displaying all drives and
associated partitions, health
status and other
information.
6. The same process can be
used to check the disk
configuration and status on
S2 and S3. Basically the
same display will appear
with the exception of the
Striped (RAID) drive.
Using Device Manager

A quick look at Device Manager may reveal hardware issues through Warnings (yellow triangles with an explanation
point inside). To access Device Manager from the S1 Desktop: double-click on the System Properties icon, click on the
Hardware tab, then select Device Manager.
• The first example below shows the disk drives, SCSI controller devices, and Philips acquisition devices expanded
on S1.
• An S2 server would only show 3DBP Backprojection board under Philips acquisition devices.
• A VS1/VSD4 server would show both the Philips ACQ board and 3DBP Backprojection board
S2 Device Manager with 3DBP
VS1 Device Manager With Acquisitor and

S1 Device Manager With Acquisitor 3DBP
Using Disk Manager

To launch Disk manager: on the S1 Desktop, right-click on My Computer and select Manage. Then click on Disk
Management. Volume F: is displayed in the window shown below. The bottom View mode is set to "Disk List" so that
we can show all the drives in the RAID.
For a SATA RAID, the disk numbers and SATA ID numbers are the same. right-click on the drive in the Disk column,
then select Properties from the menu. A defective disk will show a Warning (yellow triangle with an explanation point
inside), or an "Unhealthy" status will be indicated in graphical view. In cases where the disk is unable to report (due to a
power failure or complete logical failure) the disk will report as "Missing".
For a SCSI RAID, the most important thing to note is that Windows assigns the disk numbers in this window and they
are not necessarily the same as the disk ID! The SCSI ID for the disk (derived from the jumpers on the drive) needs to
be identified to physically locate the drive in the RAID. To identify the SCSI ID, right-click on the drive in the Disk
column, then select Properties from the menu. A defective disk will show a Warning (yellow triangle with an
explanation point inside), or an "Unhealthy" status will be indicated in graphical view. In cases where the disk is unable
to report (due to a power failure or complete logical failure) the disk will report as "Missing". In this case the disk ID may
report as "-1". Note all the other drive IDs and service the missing one.
Drives that are intermittently reported as missing may have a loose power connection (see trouble shooting loose
power connection below)
SCSI RAID shown
Using Event Viewer

On the server desktop, double-click the "Event
Viewer" icon to gain access to the CIRS event log
on page 227 and SYSTEM event log on page
228.
CIRS event log

The CIRS event log displays events reported from processes running in the
CIRS application. When dealing with a defective RAID system or buffer
memory overflow errors may appear as displayed below:
The system or buffer memory overflow error occurs when either a defective
SCSI array is no longer able to buffer incoming scan data fast enough, or,
the data is coming into the Acquisitor faster than it can unload it. This means
that the buffer of the Acquisitor can only hold so much data before it
overflows and generates this error. The problem can be caused by either
the Acquisitor or the RAID hard drives. You'll need to interrogate the system
event log to look for issues in the RAID.
SYSTEM event log

This log contains events logged by the Windows OS
system components. The majority of RAID errors will be
logged here. Look at the time the memory/buffer
overflow issue happened and correlate the time to the
System event log. Look for warnings and or errors at
that time. The warning/error may indicate a bad hard
drive and the drive ID. Other errors may be reported by
the Adaptec SCSI control devices connected to the
drives.
The System Event log must also be used to identify
problem drives, controllers cables and other hardware
problems. SCSI drive, controller, and cable issues will
usually be reported in the system log with the source of
"adpu320" (see Figure 16 on page 230), "DISK", or
"dmio" (see Figure 15 on page 229).
A filter (select "View" > "Filter") can be used to quickly
list all of these errors. Disk and dmio errors will report
the Windows disk number which can be then used to
identify the SATA or SCSI ID using Disk Manager as
described before.
The adpu320 errors will identify the specific channel
where the problem is occurring which will narrow the
problem down to a specific SCSI cable, two drives
(sometimes one drive for S1), and the power cables
supplying those drives. The description text from an
adpu320 error will contain a device name which can be
traced using the information contained in the CIRS
Repair/Replace manual.
For the S1 version 2 (p/n 453567342161), VS1 version
2 (p/n 453567307811), and VS1 Plus (p/n
453567348651) servers, the FRU level for the SCSI
RAID system is the disk drives, replaceable as a three-
pack (p/n 453567346201). See the CIRS Repair/
Replace manual for the particular server model/version for information.
For the VSD4 and 3UD3/3UQ3, the FRU level for the SATA RAID system includes the disk drives and cables. See the
CIRS Repair/Replace manual for information.
Figure 15: dmio error
Figure 16: adpu320 errors
Adaptec "SCSISelect Utility" to run Non-destructive Media Tests

NOTE This test only runs on S1 version 2 (p/n 453567342161), VS1 version 2 (p/n 453567307811), VS1 Plus (p/n
453567348651), and 3UD3/3UQ3 servers. This test will not run on a VSD4 server.
1. Log off and shutdown the server.
2. Power up the server; about 50 seconds into the boot look for:
Adaptec SCSI BIOS v4.30
Copyright 2003 Adaptec, Inc. All rights Reserved.
<<< Press <Ctrl> <A> for SCSISelect™ Utility!>>>"
At this time, press <Ctrl> <A> to get into the utility (you may have to select it twice). You will see the following:
This screen may differ in content based on how many adaptor cards/devices are available on the server.
3. Press <Enter> to gain access to the utility options. Then Select "SCSI Disk Utilities" and press <Enter>.
4. You will see the following. Move down the list and select one of the 2 displayed drives (they can only be tested one
at a time). The SCSI ID for each active drive on that control channel is displayed and is derived from the jumpers on
the drive. The jumpers on the drives should correctly match the IDs silk-screened to the front panel of the server.
NOTE ID 0 and 7 do not exist with this or any CIRS server SCSI system. ID 7 appears but is reserved for the
onboard controller (you will notice that ID0 and ID7 are not silk-screened on the front bezel of the server
as well).
5. Press <Enter> and you will be prompted select Verify Disk Media.
6. You will see the following. Select Yes.
7. Observe that the sector count increases steadily and that the % complete progress indicator continues to increase
This media test can be used to check data and power connections by wiggling cables while the test runs. If the test
stalls (see graphic below), exit the test (may be necessary to reboot to get out). Remove power and Inspect the
cable for bent pins or other issues. Re-seat or replace the suspected cable as needed.
8. When finished, if there are no errors, you will see the following:
9. A media test that shows media errors will look something like this….
10. If a media defect occurs, re-assign the block if applicable and finish the test. Past experience shows that if a media
defect occurs once it will most likely happen again, so it is advised to order a replacement disk and replace it at the
next opportunity.
11. Press <Esc> numerous times to exit the utility. When prompted, hit any key to reboot. The server will boot up again.
DiskTest for S1 SCSI RAID Array

NOTE This test only runs on S1 version 2 (p/n 453567342161), 3UD3/3UQ3, VS1 version 2 (p/n 453567307811),
VS1 Plus (p/n 453567348651), and VSD4 (p/n 453567412011) servers.
This test checks that the system can store data at the required rates across the entire F: drive on the S1 server. It will
test the data transfer rate across the RAID. A failure would indicate a component in the RAID could be at risk. This
could be the SCSI adapter boards, cables, or drives; but this test does not isolate a specific component. Consult the
CIRS Repair/Replace Manual for details on SCSI Component Replacement.
This test also creates an empty Raw Data folder at the end. The F: drive must have a folder named RawData on it in
order to operate. The RawData folder name must not have any spaces, and the letter case must be as printed here.
!
WARNING This is a destructive disk test. The test will destroy all raw data on the f: drive.
You must back up all raw data to an eod before running this test.
Running the test

1. Log on to the S1 server from the Host using Remote Desktop.
2. Double-click on the Run DiskTest icon to start the test. When the test completes, it will issue a PASS/FAIL
notification.
In the Command Window, you will see the following output.
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
DiskSpeedTest -- Checking for SCSI drives
System has 4 physical drives

Disk 1: FUJITSU MAS3367NP SCSI Disk Device, 35063MB, SCSI ID 1, Status: OK
Found 3 SCSI drives
******** Server type: S1 ********
Test parameters: acquisition 102 MB/s, Buffer reserve 24 MB

Total size 100 GB, DiskFlush=True
**********************************************************
WARNING -- WARNING -- WARNING -- WARNING -- WARNING

DESTRUCTIVE Disk Speed Test for CIRS data disks
All raw data files will be deleted!
This test will DELETE ALL DATA on Volume F:
==== ARE YOU SURE YOU WANT TO CONTINUE? ====

Press “y” when
prompted to Enter 'y' to continue, 'n' to quit
start the test. y
**********************************************************
Attempting to stop any Recon services that are running.
Make sure supervisor.exe is not running

Please close other applications.
==== Continue? ====
Press “y” when Enter 'y' to continue, 'n' to quit

prompted.
y
**********************************************************
Executing disk speed test on F: 9/9/2005 1:28:12 PM

The test takes up to 28 minutes per run
Please ignore any Low Disk Space messages from Windows
********************************************************
Run #1 of 1 1:28:12 PM
********************************************************
Format F: -- completed. Writing data...
1.1 Write: avg=173.2 min=173.7 MB/s, Rsv buf used: 17.3 of 24MB
PASS/FAIL *** DiskSpeedTest PASSED
Notification
**********************************************************
Disk speed test completed 1:39:48 PM

Ready to create RawData folder Note: You must press “y” before you press the
and re-start services <Enter> key. If you do not press “y” first, the sys-
Press “y” when tem will be unusable, and you will have to run
prompted. Enter 'y' to continue, 'n' to quit this Disk Test again.
**********************************************************
Cleanup...
Formatting F:
Format F: completed
RawData folder created on F:
**********************************************************
Starting Recon services
Waiting for supervisor startup...

Creating one dummy raw data set
Log Files
The results of each test are stored as a text file in C:\Program Files\Philips\Cirs\DiskDiag. The file name is
TestF_year-day-month_time (for example, TestF_2005-07-15_1139). You can use the test results to track server
performance over a period of time.
Multiple failures during the disk test along with other symptoms such as memory buffer overflows, as seen in the event
log during scans, may indicate a degradation in the servers ability to receive and store raw data from the Acquisitor. If
the Acquisitor diagnostics can be performed successfully, ruling out any interaction with the motherboard, the server
may need to be replaced. Also, Network Connections Configuration for CIRS Servers on page 137. Over time, a
defective disk will display that it is "at risk".
If the RAID shows signs of poor performance or fails outright, replace all three disks in the RAID and/or the SCSI cable
assembly. See the CIRS Repair/Replace Manual for details.
Transfer Raw Data to and from CIRS

Use the following methods for transferring raw data to avoid fragmenting the CIRS drive and to ensure the data will
reconstruct correctly. The methods are software version dependent:
• Procedure for Brilliance 2.3 or later software on page 240 below
• Procedure for Brilliance 2.2.x on page 247
Procedure for Brilliance 2.3 or later software

This utility allows you to easily transfer Raw Data to and from
the S1 server.
Before using the utility, you have to first modify the shortcut on
the Host desktop, so the utility will function correctly. After
that, you can Download Raw Data from CIRS, and Upload
Raw Data to the CIRS.
See:
• Modify UTS Browser Shortcut on page 241
• Download Raw Data from CIRS on page 242
• Upload Raw Data to CIRS on page 245
Modify UTS Browser Shortcut

You have to modify the shortcut on Host desktop in order for the utility to function correctly:
1. On the Host desktop, right-click on the UTS Browser icon, and select Properties.
2. On the Shortcut Properties dialog, in the Start in: field, enter "\\192.168.0.200\c\Program Files\Philips\CIRS\"
Start in: field.

Make sure to include the quotation marks at
the beginning and end of the string!
3. Click Apply, then click OK.
Download Raw Data from CIRS

You can transfer raw data from CIRS to the Host, and then to your removable media of choice.
NOTE It is recommended to first transfer the raw data to the D:\Temp directory on the Host PC, then move the
data to your removable media. Transferring from CIRS directly to removable media devices may result in a
long transfer time, due to slow data transfer rates associated with certain media.
1. On the Host desktop, double-click on the UTS Browser icon.
NOTE If you see a Windows Security Alert, click Unblock.

2. On the UTS Browser, click the Refresh list of files button. This will show all the raw data files on S1.
3. Select all the files you want to transfer. Make sure you get all the files for each study, the files will have the same
study number.
4. Under Download (get from CIRS), click the browse button, and navigate to D:\Temp. Then click OK on the Browse
dialog.
5. Under Download (get from CIRS), click the Download all selected button.
6. While the utility is working you will see a blank Command Window, and the cursor will change to the
Hourglass.When the transfer is complete the Command Window will close. Do not close the blank Command
Window yourself!
Cursor
7. After the transfer is complete and the Command Window closes, close out the UTS Browser utility.
8. The raw data files will now reside in D:\Temp, and you can transfer them to your removable media of choice.
NOTE After transferring to the removable media, delete the files in the D:\Temp directory. Failure to delete the
files from D:\Temp will result in diminished space for patient images!
Upload Raw Data to CIRS

You can transfer raw data to the CIRS from the Host.
NOTE It is recommended to first transfer the raw data from your removable media to the D:\Temp directory on
the Host PC. Transferring to the CIRS directly from the removable media devices may result in a long
transfer time, due to slow data transfer rates associated with certain media.
1. First transfer the raw data from your removable media device to the D:\Temp directory on the Host PC.
2. On the Host desktop, double-click on the UTS Browser icon.
NOTE If you see a Windows Security Alert, click Unblock.

3. On the UTS Browser, under Upload (send to CIRS), click the Browse... button and navigate to the D:\Temp
directory. Select the raw data file, and click OK on the Browse dialog.
4. On the UTS Browser, under Upload (send to CIRS), click the Upload File button.
5. While the utility is working you will see a blank Command Window, and the cursor will change to the
Hourglass.When the transfer is complete the Command Window will close. Do not close the blank Command
Window yourself!
Cursor
6. After the transfer is complete and the Command Window closes, repeat steps 3 - 5 for the other files you want to
transfer.
7. After the transferring all files close out the UTS Browser utility, then delete the raw data files from the D:\Temp
directory.
NOTE Failure to delete the files from D:\Temp will result in diminished space for patient images!
Procedure for Brilliance 2.2.x

This method is an Scanner Application service component that allows you to Get Raw Data for a Study, Get Raw Data
for a Series in a Study, or Put Raw Data on the S1 server.
Using the component

NOTE This component will not work with five-digit study numbers. If you want to transfer a study with five-digit
study numbers, see Procedure for Brilliance 2.2.x software and five-digit study numbers on page 261.
1. To launch the component from the Scanner Application, click Home > Service > Get Raw Data.
NOTE If there are already .dat files in the D:\Temp file on the Host PC, you will see the following pop-ups:
2. After launching the component, you will see the following screen. Enter the password for philips_service, then press
the <Enter> key.
3. You will see the following screen. Enter 1 if your CIRS server is set to 192.168.0.200, or 2 if your CIRS server is set
to 10.168.0.200. Then press the <Enter> key.
4. You will see the following screen listing the operations you can select. Enter the number next to the operation, then
press the <Enter>.
Click on the following links for information on each operation:

• Get Raw Data for a Study on page 250
• Get Raw Data for a Series in a Study on page 254
• Put Raw Data on the S1 server on page 258
Get Raw Data for a Study

1. After you select Get Raw Data for a Study, you will enter the Study ID of the raw data (you can find the Study ID in
Archive Manager). Enter the Study ID, and then press the <Enter> key. When prompted, press any key to continue.
2. You will see the following screen. The long set of digits is the UID. Select the UID by click on the first digit and drag
the cursor to select the UID, then press the <Enter> key to copy the UID. Make sure you do not select any
spaces before or after the UID! When prompted, press any key to continue.
3. On the next screen, right-click the mouse to paste the UID number, then press <Enter>.
4. Enter a file name, then press <Enter>.
5. Answer Yes or No on the Verbose popup.
6. Answer Yes or No when prompted to .zip the file. If you answer Yes, then click OK on the Compress popup that
appears. If you answered No, skip to Step 7 on page 252.
7. Click OK on the Success popup that follows.
8. If you would like to transfer more files, then enter Y at the first question and you will start again at step 1.
9. If you enter N at the first step, then a second question will ask if you want to select another task to perform. If you
enter Y, you will start again from the task selection screen. If you enter N, you will see a Goodbye! popup.
10. Now, you can use Windows Explorer to easily copy the data to an EOD, USB drive, etc.
Get Raw Data for a Series in a Study

1. After you select Get Raw Data for a Series in a Study, you will enter the Study ID and Series Number of the raw data
(you can find the Study ID and Series Number in Archive Manager). Enter the Study ID and Series Number, and
then press the <Enter> key. When prompted, press any key to continue.
2. You will see the following screen. The long set of digits is the UID. Select the UID by click on the first digit and drag
the cursor to select the UID, then press the <Enter> key to copy the UID. Make sure you do not select any
spaces before or after the UID! When prompted, press any key to continue.
3. On the next screen, right-click the mouse to paste the UID number, then press <Enter>.
4. Enter a file name, then press <Enter>.
6. Answer Yes or No when prompted to .zip the file. If you answer Yes, then click OK on the Compress popup that
appears. If you answered No, skip to Step 7 on page 252.
7. Click OK on the Success popup that follows.
8. If you would like to transfer more files, then enter Y at the first question and you will start again at step 1.
9. If you enter N at the first step, then a second question will ask if you want to select another task to perform. If you
enter Y, you will start again from the task selection screen. If you enter N, you will see a Goodbye! popup.
10. Now, you can use Windows Explorer to easily copy the data to an EOD, USB drive, etc.
Put Raw Data on the S1 server

1. After you select Put Raw Data onto the S1 server, you will see the following screen. When prompted, press any key
to continue.
2. Using the File Browser that appears, browse to the .dat file that you want to store. Click on the file to select it, then
click Open.
3. Answer Yes on the Store Raw popup.
5. When the transfer completes, you will see the following popup. If you select Yes, you will start again from the task
selection screen. If you select No, you will see a Goodbye! popup.
Procedure for Brilliance 2.2.x software and five-digit study numbers

Follow this procedure if you have Brilliance 2.2.x software, and want to transfer a study that has a five-digit study
number.
Get Raw Data from CIRS

With the release of Brilliance 2.0, the data structure on the CIRS S1 server has changed. The previous versions had the
*.dat, *.idx, and *.mdu files all in the F:\RawData folder. Brilliance 2.0 now has only the *.dat file in the F:\RawData folder
and the corresponding *.idx and *.mdu files are now in C:\MountedStorage\RawData_Meta folder.
1. Record the date and time of the series for which raw data is desired (from images): _____________________
2. Log in to the Host as "philips_service".
3. Remotely connect to CIRS via Remote Desktop. Either open the CIRS folder on the Host desktop and double-click
the Recon-S1 shortcut icon, or see Remote Desktop instructions in CIRS Service Manual. This will connect you to
CIRS S1 server.
NOTE The IP address of CIRS S1 is 192.168.0.200.
4. On the S1 desktop, right-click on Start, and select Explore.
5. Right-click on the C:\ drive, and select the Sharing and Security...
6. On the Sharing tab, select Share this folder, and record the Share name:
7. Click OK on the Properties dialog.
8. Close the Remote Desktop window.
9. On the Host PC, start the Scanner Application.
10. If you have dual monitors, on the right panel click Directory. On the Selected Device list, select IRS. If you have a
single monitor, select Processing and then select the IRS from the list.
11. Find the patient name that you want the data for, then right-click on the name and select Lock from the menu. If
other patients are locked, record their names and study numbers, then unlock these patients.
12. On the keyboard, press the Windows key to open the Start menu. Click Start > Run, then type cmd in the Run
Dialog.
13. In the Command Window, type uts -a 192.168.0.200 list display=on
14. Press <Enter>.
T
15. he result will look like the window below. Note the 'P' on line 29; this indicates that this file is protected (locked).
16. Now left click on the corresponding UID number starting on the 1 and drag the cursor to the end of the UID. Make
sure that there are no spaces in the highlight preceding or proceeding. Once highlighted, press the <Enter> key.
This will save the contents to the clipboard for copying.
17. Scroll down to the next Command Prompt, and type:

uts -a 192.168.0.200 getraw d:\temp\XXXX.dat srcuid=
Where:
D:\temp is the folder to place the data into on the Host (if not there, make a D:\temp folder),
XXXX.dat is the variable file name you want to give the file (dat MUST be the file's extension),
18. Once you type srcuid=, then right-click immediately after the '=', and the source UID from the copy in step 14 will
be pasted.
The line will then look like this:
uts -a 192.168.0.200 getraw d:\temp\XXXX.dat srcuid=
1.2.840.113704.1.111.5528.1103715951.25111111111111111111111
19. Now press <Enter>, and the uts command will then join the *.idx, *.mdu, and *.dat and move it to the D:\temp folder
on the Host computer. You will get an acknowledgement once the task is completed (it may take around one
minute). Now, you can use Windows Explorer to easily copy the data to an EOD, USB drive, etc.
20. At the Command Prompt type exit, then press <Enter>.
21. Once the raw data is copied to another device, remove the raw data file from the D:\temp folder.
22. On the Scanner Application, go back to the Patient Name screen and unlock the raw data previously locked in step
4. Right-click the patient name, and select Lock again to uncheck it. If you had to unlock other patients, lock them
again now.
To Store Raw Data on CIRS:

1. Insert EOD that contains raw data file into the Host PC of the system to which you want to load it.
2. Remote Desktop to CIRS: Open the CIRS folder on the Host desktop, double-click on the Recon-S1 shortcut icon.
This will connect you to CIRS S1 server.
3. Click Start > My Computer. Under the "Other" section, select F: (EOD). Copy the raw data file from F: and paste it
into C: of CIRS.
4. Click on the Recon icon on the CIRS desktop to open a Command Window.
5. Assuming the name of your raw data file is "GoodStudy.dat" and it is on the C:\ drive, type "uts srf
C:\GoodStudy.dat" at the prompt and press <Enter>.
NOTE "srf" stands for "store raw file". There is no need to include the path for the RawData folder, the srf
command automatically puts it there.
6. Once the file finishes copying, disconnect the Remote Desktop connection.
CIRS Service Tools
CIRS Service Tools

Introduction
There are two different CDs that contain CIRS Service Tools:
• For Brilliance 2.0.2 software and later, the CD set includes the “CIRS Service Vx.x.x.x” CD.
• The “Philips, System Diagnostic Utilities (PN SOFGR-064) CD. This CD comes from Granite Microsystems and
ships with the system. Its primary use is to manage the hardware aspects of CIRS servers.
• Use SOFGR-064 rev 16 or higher for S1 version 1 and version 2 servers; VS1 version 1, version 2, and Plus
servers; and S2/S3 version 4 and version 5 servers. See Philips, System Diagnostic Utilities (PN SOFGR-064)
Rev. 16 or higher on page 267.
• Use SOFGR-064 rev 21 or higher, for the VSD4, 2UQ, and 3UD3/3UQ3 servers. See Philips, System Diagnostic
Utilities (PN SOFGR-064) Rev. 21 or higher on page 269.
CIRS Service Vx.x.x.x CD

The “CIRS Service Vx.x.x.x” CD contains the following components:
• CIRS Image Test. See page 107 for more information.
CIRS Service Tools
Philips, System Diagnostic Utilities (PN SOFGR-064) Rev. 16 or higher

Rev. 16 (or higher) of this CD has tools to support multiple versions of servers, and the new replacement servers going
out to the field. This CD comes with the system.
Booting from the CD
When you boot from this CD, you will see a list of the following options to choose from.
1. Intel Confidence tests for S1V1/S2 or S3 Versions 1, 2 &3 /VS1 V1 only

The tests are only available for the following servers with Intel motherboards:
• S1: p/n 453567025001
• S2/S3: p/n 453567102401
When you run the test, the application will determine what server board is present and run the appropriate tests for that
server. The test will prompt you to accept the Intel Licensing Agreement, so enter Y to accept.
You have the choice to run the full set of tests or the quick tests, which are a shorter subset of the full test suite. You can
view the progress while the tests are running, and note any errors (shown in red text). Upon completion, the test will
display a summary screen. If there are any errors or warnings, you can enter type error.log at the Command Prompt to
display the findings in detail.
2. BIOS Update S2 V4 4535 673 42191 Only

This application updates the BIOS (including SDR, FRU, clearing SEL) and sets the CMOS settings for the S2/S3
version 4 (p/n 4535 673 42191) and version 5 (p/n 4535 674 00031) servers ONLY. The application will first verify
that it is indeed the correct server board. The test will then prompt you to confirm the update by pressing Y. The prompt
will last for 10 seconds, and if you do not confirm or press any other key it will just exit out. Once confirmed, the
application updates the server board in the correct order that Intel recommends.
3. BIOS Flash and CMOS settings updates for all servers

This application updates the BIOS (including SDR, FRU, clearing SEL) and sets the CMOS settings for all other server
boards (S1, VS1, S2/3). The application will first verify that it is indeed the correct server board. The application will then
prompt you to confirm the update by pressing Y. The prompt will last for 10 seconds, and if you do not confirm or press
any other key it will just exit out. Once confirmed, the application updates the server board in the correct order that Intel/
SuperMicro recommends.
CIRS Service Tools
4. CMOS settings updates only for all servers

This application updates just the CMOS settings for all server boards (S1, S2/3, S1A, B & C). The application will first
verify that it is indeed the correct server board. The application will then prompt you to confirm the update by pressing Y.
The prompt will last for 10 seconds, and if you do not confirm or press any other key it will just exit out. Once confirmed,
the application updates the server board in the correct order that Intel/SuperMicro recommends.
5. Service Partition Restore for S1V1/S2 or S3 Versions 1,2 &3 /VS1 V1

This application creates/restores the hidden service partition on the hard drive. The service partition in only found on
S2/S3 servers with the part number 453567102401. The application will first verify that it is indeed the correct server
board. The application will then prompt you to confirm the update by pressing Y. The prompt will last for 10 seconds,
and if you do not confirm or press any other key it will just exit out. Once confirmed, the application creates the partition
and exits.
6. SuperMicro BMC Firmware Update for S1 version 2, S1A version 1 and 2, S1B and S1C version 1&2
This application updates the IPMI firmware on the BMC module found on the all SuperMicro motherboards. The
application will first verify that it is indeed the correct server board. The application will then prompt you to confirm the
update by pressing Y. The prompt will last for 10 seconds, and if you do not confirm or press any other key it will just exit
out. Once confirmed, the application updates the server board in the correct order that SuperMicro recommends. It will
also prompt you for BMC IP and MAC configuration information.
NOTE In servers manufactured after June 2006, the BMC card is no longer available
7. Update SCSI Controller

This application will only run for the servers that have PCI SCSI controller card(s) in them (S1A, S1B, S1C). The
out. Once confirmed, the application updates the SCSI Controller(s) firmware.
8. S2V4 Server Configuration Wizard Only

This application only runs on S2/S3 version 4 (p/n 4535 673 42191) and version 5 (p/n 4535 674 00031) servers
ONLY. It will first verify that this is a 22884-05. If so, it then will run the Server Configuration Wizard as is done on the
Intel CD. You can use this to change the IP address on the BMC chip in case there is an IP conflict. There is no other
use for this selection at this time.
9. Exit
Exit to a prompt.
CIRS Service Tools
Philips, System Diagnostic Utilities (PN SOFGR-064) Rev. 21 or higher

Rev. 21 (or higher) of this CD has tools to support multiple versions of servers, including the dual and quad-core
processor servers. This CD comes with the system.
NOTE Some of the menu selections on the CD refer to 2UD, this server was not released for this Brilliance
system. The 2UQ server is released for this system, and any 2UD menu selection also apply to the 2UQ
servers.
Booting from the CD

When you boot from this CD, you will see a list of the following options to choose from.
NOTE When an application completes, or if you select Exit, then you will see a Command Prompt. If you want to still
use the CD, press <Ctrl><Alt><Delte> to reboot the server. If you are finished using the CD, remove the CD
from the drive and then press <Ctrl><Alt><Delte> to reboot the server.
1. Intel Confidence tests for 2UD/S1V1/S2 or S3 Versions 1, 2 &3 /VS1 V1 only

The tests are only available for the following servers with Intel motherboards:
• S1: p/n 453567025001
• S2/S3: p/n 453567102401
• 2UQ: p/n 453567412002
When you run the test, the application will determine what server board is present and run the appropriate tests for that
server. The test will prompt you to accept the Intel Licensing Agreement, so enter Y to accept.
You have the choice to run the full set of tests or the quick tests, which are a shorter subset of the full test suite. You can
view the progress while the tests are running, and note any errors (shown in red text). Upon completion, the test will
display a summary screen. If there are any errors or warnings, you can enter type error.log at the Command Prompt to
display the findings in detail.
CIRS Service Tools
2. BIOS Update
This application updates the BIOS (including SDR, FRU, clearing SEL) and sets the CMOS settings. When you select
this menu item you will see the following:
1. BIOS Update S2v4 4535 673 42191 only
2. BIOS Update S2v5 4535 674 00031 only
3. BIOS Flash and CMOS Settings updates only for all servers except 2UD
4. BIOS Flash and CMOS Settings updates for 2UD
5. Return to Main Menu
6. Exit
The application you select will first verify that it is indeed the correct server board. The test will then prompt you to
confirm the update by pressing Y. The prompt will last for 10 seconds, and if you do not confirm or press any other key
it will just exit out. Once confirmed, the application updates the server board in the correct order that Intel recommends.
Selection 3, “BIOS Flash and CMOS Settings updates only for all servers except 2UD”, is for all other server boards
(S1, VS1, VSD4, 3UD3/3UQ3, S2/3), except the 2UQ servers. Selection 4, “BIOS Flash and CMOS Settings updates
for 2UD”, is for the 2UQ servers.
3. CMOS Settings updates only for all servers except 2UD

This application updates the BIOS (including SDR, FRU, clearing SEL) and sets the CMOS settings for all other server
boards (S1, VS1, VSD4, 3UD3/3UQ3, S2/3). The application will first verify that it is indeed the correct server board.
The application will then prompt you to confirm the update by pressing Y. The prompt will last for 10 seconds, and if you
do not confirm or press any other key it will just exit out. Once confirmed, the application updates the server board in the
correct order that Intel/SuperMicro recommends.
4. CMOS settings updates only for 2UD only

This application updates just the CMOS settings for the 2UQ server. The application will first verify that it is indeed the
correct server board. The application will then prompt you to confirm the update by pressing Y. The prompt will last for
10 seconds, and if you do not confirm or press any other key it will just exit out. Once confirmed, the application updates
the server board in the correct order that Intel/SuperMicro recommends.
5. Service Partition Restore for S1V1/S2 or S3 Versions 1,2 &3 /VS1 V1

This application creates/restores the hidden service partition on the hard drive. The service partition in only found on
S2/S3 servers with the part number 453567102401. The application will first verify that it is indeed the correct server
board. The application will then prompt you to confirm the update by pressing Y. The prompt will last for 10 seconds,
and if you do not confirm or press any other key it will just exit out. Once confirmed, the application creates the partition
and exits.
CIRS Service Tools
6. SuperMicro BMC Firmware Update for S1 version 2, S1A version 1 and 2, S1B and S1C version 1&2
This application is non-functional.
7. Update SCSI Controller

This application will only run for the servers that have PCI SCSI controller card(s) in them (S1A, S1B, S1C). The
out. Once confirmed, the application updates the SCSI Controller(s) firmware.
8. S2V4&V5 Server Configuration Wizard Only

This application only runs on S2/S3 version 4 (p/n 4535 673 42191) and version 5 (p/n 4535 674 00031) servers
ONLY. It will first verify that this is a 22884-05. If so, it then will run the Server Configuration Wizard as is done on the
Intel CD. You can use this to change the IP address on the BMC chip in case there is an IP conflict. There is no other
use for this selection at this time.
9. Exit
Exit to a prompt.

Brilliance CT: 6-Slice, 10-Slice, 16-Slice, and 16 Power Configurations

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

Brilliance CT: 6-Slice, 10-Slice, 16-Slice, and 16 Power Configurations

Uploaded by

Copyright:

Available Formats

TM

CIRS Service Manual

4535 673 63861

© 2009 Philips Healthcare

! Attention symbol Radiation warning symbol

Laser warning symbol Biohazard warning symbol

Magnetism warning symbol Projectile warning symbol

Electrical warning symbol Do not touch

Crush warning symbol

Diagnostic Imaging Systems - Mechanical-electrical Warning

Diagnostic Imaging Systems - Radiation Warning

ECO Revision Date Comments

ECO Revision Date Comments

This document was prepared by the CT BU Cleveland Service Innovation Department.

Revision History ............................................................................................................................. VI

Horizontal Servers Functional Description ................................................................................... 11

3UD3 version 1 and version 2.............................................................................................................................. 22

Vertical Servers Functional Description ....................................................................................... 41

Acquisitor and 3DBP Functional Description ............................................................................... 61

CIRS Server Configuration and Management ................................................................................ 65

Reconstruction Troubleshooting ................................................................................................. 107

Troubleshooting Solutions ............................................................................................................................ 117

The Progress Indicators................................................................................................................................ 159

Troubleshoot the RAID Array ............................................................................................................................. 222

CIRS Service Tools ...................................................................................................................... 266

CIRS Rack with Horizontal servers and Network Switch

The following Server configurations are available for CIRS:

CIRS Rack Flow Diagram

*Server motherboards vary by model.

Combined Rack Console Flow Diagram

*Server motherboards vary by model.

Power down procedure

S1 Server Recon Processes

Horizontal Servers Functional Description

S1 Servers S2/S3 Servers

CIRS Rack Components

3.6 GHz Intel Xeon Processor 36 GB SCSI Hard

Intel SE7501BR2 motherboard Block Diagram

S1 version 1 - Network Interface Controller

NIC Diagnostic LEDs

36 GB SCSI Slot 5 for

SuperMicro X6DH8-XG2 motherboard Block Diagram

S1 version 2 - Network Interface Controller

NIC Diagnostic LEDs

OFF No network connection

S1 version 3 (p/n 4535 674 02551) with SuperMicro X6HD-XG2 motherboard

512 MB DIMM, DDR2, Memory Modules (Qty. 8)

SuperMicro X6DH8-XG2 motherboard Block Diagram

S1 version 3 SCSI Drive Configuration and Interconnects

Onboard SCSI Controller

S1 version 3 - Network Interface Controller

NIC Diagnostic LEDs

OFF No network connection

3UD3 version 1 and version 2

SuperMicro X7DB8-X motherboard Block Diagram

SuperMicro X7DB8-X Back Panel Connectors

3UD3 Network Interface Controller

NIC Diagnostic LEDs

OFF No Connection or 10 Mbps

3UD3 SCSI Drive Configuration and Interconnects

3UD3, 3UD5, 3UD8, 3UD12 SCSI DRIVE CONFIGURATION

POSITION OF JUMPERS (LEFT TO RIGHT) MAY

SuperMicro X7DB8-X motherboard Block Diagram