Service

Brilliance CT
16-slice, 64-slice, and Big Bore
v3.6 Service Tools User Guide
4598 001 96541

Revision A
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.
© 2012 Koninklijke Philips Electronics N.V. All Rights Reserved.

CSIP Level 1
Brilliance CT 16-slice, 64-slice, and Big Bore v3.6 Service Tools User Guide Rev A
Philips Healthcare
© 2012 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.
4598 001 96541 © 2012 Koninklijke Philips Electronics N.V All Rights Reserved CSIP Level 1 2
Attention: This page contains copyrighted materials that are confidential and/or proprietary. Any release or distribution of this material, without permission, is a violation of law.
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
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 (using the on-site On-Off switch), and the internal/external un-interruptible 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.
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.
Revision History
Revision History
DCF # Revision Date Comments
2025002 A September 2012 For release of 3.6.
This document was prepared by CT Service Innovation.

For any additions, corrections, or suggestions, email: cle.cthelp@philips.com
Contents
Revision History .............................................................................................................................. 6
Service Tools Framework .............................................................................................................. 23

Multi-window View................................................................................................................................................ 24
Multiple Tabs in the Service Tools Framework .................................................................................................... 24
Progress bar......................................................................................................................................................... 25
History bar............................................................................................................................................................ 25
Help Button .......................................................................................................................................................... 26
IST Security Dongle ...................................................................................................................... 27

Overview .............................................................................................................................................................. 27
Activating the Dongle ........................................................................................................................................... 28
Install Cardman USB 6121 Driver................................................................................................................... 28
Install Safeguard SmartCard Provider ............................................................................................................ 32
Install SmartCard, setup Safeguard SmartCard Provider, and charge the Dongle ........................................ 35
Audio Test ..................................................................................................................................... 39
Backup and Restore ...................................................................................................................... 40

Backup ................................................................................................................................................................. 40
Restore................................................................................................................................................................. 42
BugRep Collector .......................................................................................................................... 44

BugRep Collector Archives .................................................................................................................................. 46
Bugrep Viewer ............................................................................................................................... 47

Opening a BugRep file ......................................................................................................................................... 48
Contents
Interacting with Bugrep Files................................................................................................................................ 50
Log File Window Navigation ........................................................................................................................... 51
Removing Bugrep Reports from the System........................................................................................................ 52
Bugrep Viewer Options ........................................................................................................................................ 52
Analyze Current State..................................................................................................................................... 52
View Multiple Analyses ................................................................................................................................... 53
Running System Monitor on Bugrep............................................................................................................... 53
Opening a UNIX Console ............................................................................................................................... 53
CAN Analyzer ................................................................................................................................ 54

Report Area.......................................................................................................................................................... 55
Query Area........................................................................................................................................................... 55
Charting Area ....................................................................................................................................................... 56
Tips for Queries and Charts ................................................................................................................................. 56
CAN Send ...................................................................................................................................... 57

Category Area ...................................................................................................................................................... 58
Selection Area...................................................................................................................................................... 58
Data Area ............................................................................................................................................................. 58
CAN Trace ..................................................................................................................................... 59

Category Area ...................................................................................................................................................... 60
Message Area ...................................................................................................................................................... 60
Data Area ............................................................................................................................................................. 61
Filter Area............................................................................................................................................................. 62
Additional Features .............................................................................................................................................. 63
Contents
CAT Viewer .................................................................................................................................... 64
CIRS Diagnostic Viewer ................................................................................................................ 65
CIRS Visual Diagnostics ............................................................................................................... 66

NGBP Diagnostic ................................................................................................................................................. 67
Acquisitor Diagnostic Optical Tests...................................................................................................................... 69
Acquisitor Diagnostic Electrical Tests .................................................................................................................. 74
NVIDIA GPU Diagnostic....................................................................................................................................... 77
Coast Down Test ........................................................................................................................... 79

Perform the test.................................................................................................................................................... 80
Configuration Settings .................................................................................................................. 81

Databases ............................................................................................................................................................ 82
Logger Database ............................................................................................................................................ 82
CanTrace Database........................................................................................................................................ 82
GLC...................................................................................................................................................................... 83
GSE...................................................................................................................................................................... 83
Gemini.................................................................................................................................................................. 84
PETMS................................................................................................................................................................. 84
MotionTable_107 ................................................................................................................................................. 85
ConfigTable_100.................................................................................................................................................. 86
CanBus Simulation............................................................................................................................................... 87
Contents
Controller Utilities ......................................................................................................................... 88
Service Mode ....................................................................................................................................................... 90
Utilities Menu........................................................................................................................................................ 91
Diagnostics Menu................................................................................................................................................. 93
Connect to Controller ........................................................................................................................................... 94
Connecting to MDP or Tilt............................................................................................................................... 95
Controller Boards menu ....................................................................................................................................... 95
Toolbox ........................................................................................................................................................... 96
CPM .......................................................................................................................................................... 96
LED Test............................................................................................................................................. 96
CPM Flash Menu................................................................................................................................ 96
CPM Serial Tests Menu...................................................................................................................... 97
Serial Port 1 Menu.............................................................................................................................. 97
Serial Port 2 Menu.............................................................................................................................. 98
CAN Menu .......................................................................................................................................... 98
NVRAM Menu..................................................................................................................................... 99
Utilities .......................................................................................................................................................... 100
Application Flash Burner Utility ............................................................................................................... 100
Boot Flash Burner Utility.......................................................................................................................... 101
Downloader Utility (Boot/MDP/TDP only)................................................................................................ 101
NVRAM Error Log Reader Utility............................................................................................................. 102
Board Debug Utility (Available for Zone Specialist Only) ........................................................................ 102
Bus Utility (Available for Zone Specialist Only) ....................................................................................... 102
RAM Utility (Available for Zone Specialist Only) ..................................................................................... 103
Upload as ASCII Utility (Available for Zone Specialist Only)................................................................... 103
Upload as Binary Utility (Available for Zone Specialist Only) .................................................................. 103
Download as Binary Utility (Available for Zone Specialist Only) ............................................................. 104
Location Monitor Utility (Available for Zone Specialist Only)................................................................... 104
State Menu Utility (Available for Zone Specialist Only) ........................................................................... 105
State Menu Example ........................................................................................................................ 107
Input/Output Utility (Available for Zone Specialist Only).......................................................................... 111
Contents
JTAG Utility (Available for Zone Specialist Only) .................................................................................... 112
Reboot .......................................................................................................................................................... 113
Connect To Baseboards ............................................................................................................... 114

GHost Baseboard............................................................................................................................................... 114
GCP / CTB Functions ................................................................................................................................... 114
Gantry Control Panel / CT Control Box Functions Menu......................................................................... 114
Command Action Sub Menu ................................................................................................................... 115
CT Control Submenu............................................................................................................................... 116
GCP & CTB Command Synopsis............................................................................................................ 116
R - Reset .......................................................................................................................................... 117
B - Button Switch Check................................................................................................................... 117
L - LED Lamp Set ............................................................................................................................. 118
H - Horizontal Display Set ................................................................................................................ 118
V - Vertical Display Set................................................................................................................... 118
T - Tilt Display Set ............................................................................................................................ 118
M - Milliamps Display Set ................................................................................................................. 118
K - Kilovolts Display Set ................................................................................................................... 118
S - Seconds Display Set................................................................................................................... 119
C - Clock Set/Display Toggle............................................................................................................ 119
D - Display Stored Parameters......................................................................................................... 119
F - Flash Seven Segment................................................................................................................. 120
P - Program Flash Data Save........................................................................................................... 120
DB - Debug Mode Toggle................................................................................................................. 120
OB - Option, Bounce Logic............................................................................................................... 120
OC - Option, Combine L+R .............................................................................................................. 121
OD - Option, Duty Cycle (0-10) ........................................................................................................ 121
ISP - In System Programming .......................................................................................................... 121
Button Switch & LED to Message Mapping...................................................................................... 122
Serial............................................................................................................................................................. 123
Seven Segment Test .................................................................................................................................... 123
E-Stop Loop Test.......................................................................................................................................... 124
Selecting E-Stop from the Baseboard Menu .................................................................................... 124
Contents
DMC Baseboard................................................................................................................................................. 125
Set Motor Speed........................................................................................................................................... 125
Set UHR Collimator ...................................................................................................................................... 126
Set P-Plane Collimator ................................................................................................................................. 126
Move Collimators Using Switches ................................................................................................................ 127
Read Temperatures...................................................................................................................................... 127
Set Scan Parameters.................................................................................................................................... 128
Print Scan Parameters.................................................................................................................................. 129
MxScan......................................................................................................................................................... 129
Reset Base Board......................................................................................................................................... 130
Start DMC Comm. Test ................................................................................................................................ 130
Stop DMC Comm. Test................................................................................................................................. 130
E-Stop Loop.................................................................................................................................................. 130
Selecting E-Stop from the Baseboard Menu ........................................................................................... 130
(DMC Power On) .......................................................................................................................................... 131
Main Drive Baseboard .................................................................................................................................. 131
Serial TI16544 Echo ..................................................................................................................................... 132
Resolver Reference Delay............................................................................................................................ 132
Spindle Block Control ................................................................................................................................... 132
Spindle Block Status..................................................................................................................................... 132
Main Contactor Control................................................................................................................................. 132
Main Contactor Status .................................................................................................................................. 132
Motor Status ................................................................................................................................................. 132
Rotor Position Status .................................................................................................................................... 133
Configuration Switch..................................................................................................................................... 133
Seven Segment & LED................................................................................................................................. 133
Accelerometer Control .................................................................................................................................. 133
DAC Control.................................................................................................................................................. 133
Increment DAC ............................................................................................................................................. 134
Decrement DAC............................................................................................................................................ 134
Serial............................................................................................................................................................. 134
Contents
Tilt Baseboard .................................................................................................................................................... 134
Target Angle Control..................................................................................................................................... 135
Current Position Control ............................................................................................................................... 135
Potentiometer Control................................................................................................................................... 135
Maximum Speed Control .............................................................................................................................. 135
Ramp Speed Control .................................................................................................................................... 136
Tilt Control .................................................................................................................................................... 136
Tilt Status...................................................................................................................................................... 136
Encoder Divide ............................................................................................................................................. 136
Jog Speed..................................................................................................................................................... 136
Service Mode................................................................................................................................................ 137
Gantry Motion Processor (GMP) Baseboard ..................................................................................................... 137
RHost Baseboard............................................................................................................................................... 138
Analog to Digital............................................................................................................................................ 138
Digital to Analog............................................................................................................................................ 138
Digital-Analog-Digital .................................................................................................................................... 139
CPM / DSP ................................................................................................................................................... 139
Digital Input................................................................................................................................................... 139
Digital Output ................................................................................................................................................ 139
Digital I/O ...................................................................................................................................................... 140
PWM Waveform............................................................................................................................................ 140
Interrupt Check ............................................................................................................................................. 140
Real Time Clock ........................................................................................................................................... 140
Seven Segment LED .................................................................................................................................... 140
Watchdog Timer ........................................................................................................................................... 141
E-Stop Loop.................................................................................................................................................. 141
Couch Baseboard (Galaxy Couch/Stargate Platform) ....................................................................................... 142
Couch Registers ........................................................................................................................................... 142
Read Vert A to D........................................................................................................................................... 143
Read Horz A to D.......................................................................................................................................... 143
Contents
Horizontal Encoder ....................................................................................................................................... 143
Serial............................................................................................................................................................. 143
Seven Segment LED V1............................................................................................................................... 144
Seven Segment LED V2............................................................................................................................... 144
Galaxy Control/Status Registers................................................................................................................... 145
Galaxy Power Monitor Register .................................................................................................................... 146
Remove Keep Alive ...................................................................................................................................... 147
E-Stop Loop.................................................................................................................................................. 147
(CCB Power On)........................................................................................................................................... 147
Vertical Couch Encoder Utility ...................................................................................................................... 148
Horizontal Couch Encoder Utility .................................................................................................................. 148
Couch Baseboard (Gemini/PET-CT).................................................................................................................. 149
Serial............................................................................................................................................................. 149
Seven Segment LED .................................................................................................................................... 150
Control/Status Registers............................................................................................................................... 150
Modify Register 0/n ?.................................................................................................................................... 151
Power Monitor Register ................................................................................................................................ 152
E-Stop Loop.................................................................................................................................................. 153
(CCB Power On)........................................................................................................................................... 153
Controller Board Troubleshooting ............................................................................................... 154

Boot-up Tests ............................................................................................................................................... 154
CPM ........................................................................................................................................................ 154
Baseboards ............................................................................................................................................. 155
LEDs ............................................................................................................................................................. 155
NVRAM......................................................................................................................................................... 156
“Green” Baseboards ..................................................................................................................................... 158
Contents
Controller Utilities Burn Procedures .......................................................................................... 159
Configuration of the Server ................................................................................................................................ 160
Important Tips for a Successful Upgrade/Reburn Procedure ............................................................................ 160
Re-burning Boot Flash ....................................................................................................................................... 162
For Field Use ................................................................................................................................................ 162
Procedure................................................................................................................................................ 162
Burning Application Flash After Boot Flash Has Been Installed ........................................................................ 163
For Field Use ................................................................................................................................................ 163
Procedure................................................................................................................................................ 163
Recovery procedures for an aborted boot flash burn using Utilities................................................................... 164
Scenario 1..................................................................................................................................................... 164
Scenario 2..................................................................................................................................................... 165
Scenario 3..................................................................................................................................................... 166
Scenario 4..................................................................................................................................................... 167
Couch Vertical Calibration ........................................................................................................... 169
CPM Reset .................................................................................................................................... 170
CPM Software Version Query Tool ............................................................................................... 171
DMS/Data Path Diagnostics ......................................................................................................... 172
DMS Tools .................................................................................................................................... 173

DMC Utility ......................................................................................................................................................... 174
Starting the program ..................................................................................................................................... 174
Overview....................................................................................................................................................... 174
Status Messages..................................................................................................................................... 175
A Plane Tab............................................................................................................................................. 176
Reading the A Plane Calibration from File into the GUI ................................................................... 177
Contents
Manually Entering A Plane Calibration Into The GUI ....................................................................... 177
Clearing the A Plane GUI ................................................................................................................. 177
Writing A Plane Calibration To NVRAM ........................................................................................... 177
Reading A Plane Calibration From NVRAM ..................................................................................... 178
Entering The A Plane Serial Number ............................................................................................... 178
A Offsets Tab .......................................................................................................................................... 179
Manually Entering A Offsets Calibration Into The GUI ..................................................................... 180
Clearing the A Plane GUI ................................................................................................................. 180
Z RPM Tab .............................................................................................................................................. 181
Obtaining Z Alignment Calibration.................................................................................................... 181
Manually Entering The Z Alignment Calibration Into The GUI.......................................................... 182
Clearing the Z RPM GUI................................................................................................................... 182
Writing The Z alignment Calibration Into The NVRAM ..................................................................... 182
Reading The Z alignment Calibration From NVRAM........................................................................ 182
Go2Position Tab On Host Application..................................................................................................... 183
Aplane Reader ................................................................................................................................................... 184
Starting the program ..................................................................................................................................... 185
Functions ...................................................................................................................................................... 186
Information .............................................................................................................................................. 186
Rotor........................................................................................................................................................ 187
Z-Tracking ............................................................................................................................................... 187
DOM ........................................................................................................................................................ 187
Ref........................................................................................................................................................... 188
Tube ........................................................................................................................................................ 188
Pplane ..................................................................................................................................................... 188
Aplane ..................................................................................................................................................... 189
Display Windows .......................................................................................................................................... 190
SW and Z (Position and Voltage) ............................................................................................................ 190
Filter (Position and Voltage) .................................................................................................................... 191
Data Analysis................................................................................................................................................ 192
Analyzing the SW data ............................................................................................................................ 192
Analyzing the Z data................................................................................................................................ 194
Analyzing the Filter data.......................................................................................................................... 195
Contents
DMS Temperature Monitor................................................................................................................................. 196
IBox Diagnostics .......................................................................................................................... 197

Running the IBox Diagnostics ............................................................................................................................ 197
Automatic Test.............................................................................................................................................. 198
Manual Test .................................................................................................................................................. 199
IBOX Program Update.................................................................................................................................. 200
Test Log........................................................................................................................................................ 200
LAN Config ................................................................................................................................... 201
Manual Exposure .......................................................................................................................... 202

Easy Mode ......................................................................................................................................................... 203
Expert Mode....................................................................................................................................................... 205
Protocol Selection......................................................................................................................................... 206
User-defined Protocols ................................................................................................................................. 206
Deleting Protocols......................................................................................................................................... 206
Command Buttons ........................................................................................................................................ 207
Operational Messages.................................................................................................................................. 207
Message Trace ............................................................................................................................................. 207
Message Trace Data .................................................................................................................................... 208
Real Time Data............................................................................................................................................. 208
Performing the test in Expert Mode .............................................................................................................. 209
Map Drive (for Varian Computer) ................................................................................................. 210
No Load Test ................................................................................................................................ 212

Overview ............................................................................................................................................................ 212
Components....................................................................................................................................................... 213
Scan Parameters .......................................................................................................................................... 213
Contents
Command Buttons ........................................................................................................................................ 213
Operational Messages.................................................................................................................................. 214
Real Time Data............................................................................................................................................. 214
Result Messages .......................................................................................................................................... 215
Running the No Load Test ................................................................................................................................. 216
Running the Test with Tube Connected ....................................................................................................... 216
Running the Test with Tube Disconnected ................................................................................................... 219
MRC High Voltage Connectors..................................................................................................................... 224
Real Time Data ............................................................................................................................. 227

Real Time Data Parameters............................................................................................................................... 228
Remote Configuration .................................................................................................................. 230
Resend Analyzer .......................................................................................................................... 231
Rotor Profile ................................................................................................................................. 236

Mode .................................................................................................................................................................. 237
Acc/Jog/Dec.................................................................................................................................................. 237
Position ......................................................................................................................................................... 237
Stop ............................................................................................................................................................. 237
CoastDown ................................................................................................................................................... 237
Rotor Balance .............................................................................................................................................. 238
Collect Data ................................................................................................................................................. 238
Estop Status....................................................................................................................................................... 239
Start Button ........................................................................................................................................................ 239
Abort the Rotor Profile Button ............................................................................................................................ 239
Partial Display .................................................................................................................................................... 239
Display area ....................................................................................................................................................... 240
Contents
Files.................................................................................................................................................................... 240
Software Distribution ................................................................................................................... 241

Manual Software Download ............................................................................................................................... 242
Manual Download Notes............................................................................................................................... 242
Manually Install Software ................................................................................................................................... 243
Manual Install Notes ..................................................................................................................................... 245
Automatic Software Download Notes................................................................................................................. 246
SpindleBlok Commissioning ........................................................................................................ 247
System Configuration .................................................................................................................. 248

View the Expected and Current Values of the Component Software................................................................. 249
Programming Components with System Configuration ..................................................................................... 250
Tilt Calibration ............................................................................................................................. 252
Tilt Profile .................................................................................................................................... 253

Quick Configuration............................................................................................................................................ 254
Encoders ............................................................................................................................................................ 254
Data To Collect .................................................................................................................................................. 254
Mode .................................................................................................................................................................. 255
AutoMode ..................................................................................................................................................... 255
Collect Last Data .......................................................................................................................................... 255
Real Time ..................................................................................................................................................... 255
Estop Status....................................................................................................................................................... 256
Tilt Position......................................................................................................................................................... 256
Contents
Start Button ........................................................................................................................................................ 256
Abort Tilt Profile Button ...................................................................................................................................... 256
Data To Display.................................................................................................................................................. 257
Partial Display ................................................................................................................................................... 257
Min Y Axis .......................................................................................................................................................... 258
Max Y Axis ........................................................................................................................................................ 258
Display area ....................................................................................................................................................... 258
Files.................................................................................................................................................................... 258
Tube History Form ....................................................................................................................... 259

Tube History Report ........................................................................................................................................... 260
Tube History Tool ......................................................................................................................... 261

Current Tube ...................................................................................................................................................... 261
Plot Arcs............................................................................................................................................................. 263
Export Tube Data .............................................................................................................................................. 264
Old Tubes........................................................................................................................................................... 265
Update Tube History Database.......................................................................................................................... 265
Universal Log Viewer ................................................................................................................... 266

Time From To..................................................................................................................................................... 266
Query Messages ................................................................................................................................................ 267
View Messages .................................................................................................................................................. 269
Save/Open Files................................................................................................................................................. 270
Save Files ..................................................................................................................................................... 270
Contents
Open Files .................................................................................................................................................... 270
Query Wizard ..................................................................................................................................................... 272
URL Restriction ............................................................................................................................ 273
View Logs with markers ............................................................................................................... 274

Marker Functions ............................................................................................................................................... 275
Place a marker on single or multiple entries ...................................................................................................... 277
Mark and search based on any column ............................................................................................................. 278
X-Ray Performance Tests ............................................................................................................. 280
Appendix A: Tips on how to use SQL for queries ........................................................................ 281

Using Data Manipulation Language ................................................................................................................... 281
Retrieving Records ....................................................................................................................................... 281
Restricting the Result Set........................................................................................................................ 282
Sorting the Result Set ............................................................................................................................. 283
Using Aggregate Functions to Work with Values .................................................................................... 284
Grouping Records in a Result Set........................................................................................................... 285
Intermediate Data Manipulation Language ........................................................................................................ 286
Predicates ............................................................................................................................................... 286
The ALL keyword .................................................................................................................................... 286
The DISTINCT keyword .......................................................................................................................... 287
The DISTINCTROW keyword ................................................................................................................. 287
The TOP keyword ................................................................................................................................... 288
SQL Expressions ............................................................................................................................................... 288
The IN operator ....................................................................................................................................... 288
The BETWEEN operator ......................................................................................................................... 289
The LIKE operator ................................................................................................................................... 290
The IS NULL operator ............................................................................................................................. 291
Contents
Subqueries ......................................................................................................................................................... 292
The IN subquery...................................................................................................................................... 292
The ANY/SOME/ALL subqueries ............................................................................................................ 293
The EXISTS subquery............................................................................................................................. 294
Joins................................................................................................................................................................... 295
INNER JOINs .......................................................................................................................................... 295
OUTER JOINs......................................................................................................................................... 297
The Cartesian product............................................................................................................................. 297
The UNION operator ............................................................................................................................... 298
The TRANSFORM statement.................................................................................................................. 299
Service Tools Framework
Service Tools Framework

NOTE Service Tools are enabled via IST security. You must plug your IST Security Dongle into the Host PC to use
Service Tools. If you have not setup your IST Security Dongle, see IST Security Dongle on page 27.
The Service Tools Framework consists of Analysis, Diagnostics, Repair, Performance, and Utilities workflow
buttons along the top of the page, and an application list along the left of the page. When you click a workflow
button, a corresponding application list will open.
Overview
Workflow Buttons
Application List
FSE Log On
Information
Multi-window View
Multi-window View
You can have one application open in the Service Tools Framework and another open in a separate window, or multiple
applications open in separate windows. With multiple windows, you are able to resize some of the windows to make
them smaller (depending on the open application).
When you open an application, you will see a pin icon on the tab next to the application name. For multi-window view,
click on the pin, and the application will open in a separate window. If you click on the pin again, the window will return
to a tab in the Service Tools Framework.
Multiple Tabs in the Service Tools Framework

You can open multiple applications as tabs in the Service Tools Framework.
Progress bar
Progress bar
The left bottom corner of the Main page shows the progress bar of the service tool in use (if applicable). It will show the
progress of the tool running (in percent completed).
History bar
The bottom part of the Main page shows the history of the Service Tools used and the results. The History is only for the
current, open Service Tools session.
Help Button
Help Button
The Help button on the right top part of the Main page provides access to Service
Documentation located on the Host PC. To open the Help Application, click on the Help
button, then select General Help from the Application List.
• When running a Service Tool, if you press F1, you will see the help file for that service
tool.
• In Visual Diagnostics, if you right click on the block
diagram for a test, a menu will appear with selections for
• Detailed Image
• FRU Description
• FRU Replacement
• FRU Calibration
• FRU Programming
IST Security Dongle
IST Security Dongle
Overview
NOTE If you have an older dongle (Omnikey 6020) you can update your certificate and continue using it according to its
current entitlements.
IST
IST (Integrated Security Tool) is a single common security mechanism to protect proprietary service documentation and
service diagnostics on field engineer laptops, and on compatible customer equipment.
ICE
ICE (Integrated Security Tool for Clinical Equipment) is the name of the IST client which resides on the customer
equipment. This client secures proprietary software and information on the customer equipment and is accessed by
recognizing a secure certificate.The secure certificate resides on the dongle.
Dongle
A dongle is a hardware security device that is plugged into the USB port of a customer system
to transfer a secure certificate to the system. It consists of two pieces; the SmartCard (which
looks like an SD memory card) and the SmartCard reader (which look like a USB memory
stick).
• IST SmartCard p/n 452221042322
• IST SmartCard reader p/n 452221042312 (Omnikey 6121)
Activating the Dongle

To use the USB dongle two pieces of software must be installed on your computer. The Cardman USB 6121 driver and
the Safeguard SmartCard Provider. They enable your computer to recognize the dongle and automatically charge the
dongle with an active certificate.
Install Cardman USB 6121 Driver

1. The software needed to use the dongle is located in the Zeppelin Toolbox. Go to: http://pww.zeppelin.philips.com/
zeppelin/user/toolbox.asp.
2. In the Zeppelin Toolbox, select the Cardman USB 6121 software that is appropriate for your machine.
NOTE You must allow pop-ups in Internet Explorer for the download box to be displayed. Click on the Download
location of your choice. If you do not have a code one computer you will not be able to download this software.
3. When you see the Login prompt, enter your IST User Name and Password. Then click Login.
4. When you select the necessary version you will get a download location selection box.
5. You may run the install software from the network, or save the file to your computer and run it locally.
6. If you clicked Run in the previous step, after the software is unzipped, click the Install button. If you clicked Save in
the previous step, double-click on the file, and then click the Install button.
7. Once the installation has completed, click the Close button.
8. Leave the Zeppelin Toolbox web page open for the next section.
9. Continue with Install Safeguard SmartCard Provider on page 32.
Install Safeguard SmartCard Provider

1. In the Zeppelin Toolbox, select the Safeguard SmartCard Provider software that is appropriate for your machine.
If you are using XP download the Windows XP software.
NOTE You must allow pop-ups in Internet Explorer for the download box to be displayed. Click on the Download
location of your choice. If you do not have a code one computer you will not be able to download this software.
You can download the software on a Code1 computer and transfer the software to the non-Code 1 computer and
run the install.
2. When you select the necessary version, you will get a download location selection box.
3. You may run the install software from the network, or save the file to your computer and run it locally.
4. If you clicked Run in the previous step, after the software is unzipped, click the Install button. If you clicked Save in
the previous step, double-click on SGSCP_4211.exe, and then click the Install button.
5. Once the installation has completed, click the Close button.
6. The SmartCard reader driver has been successfully installed.

7. Continue with Install SmartCard, setup Safeguard SmartCard Provider, and charge the Dongle on page 35.
Install SmartCard, setup Safeguard SmartCard Provider, and charge the Dongle
You must install the SmartCard into the SmartCard reader.
1. Insert the SmartCard into the reader with the foil side down, and the corner notch facing the left side of the
SmartCard reader:
SmartCard in slot.
SmartCard Reader
The SmartCard needs to be seated completely in the reader:
SmartCard seated in the Reader
SmartCard Activity Light SmartCard Ejection Tab (slide this

tab up to eject the SmartCard).
2. Insert the dongle into your computer. The activity light should flash as your computer recognizes the device.
3. On your laptop, click Start > Control Panel (or Start > Settings > Control Panel).
4. On the Control Panel window, double-click the SafeGuard SmartCard Provider icon.
5. If there is another SmartCard Reader other than the Omnikey listed,

make sure the ID is not A. Only the OMNIKEY AG Smart Card
Reader should have the ID as A.
If there is another SmartCard Reader in the list, and the OMNIKEY ID
is not A, then follow steps a - c. Otherwise continue with Step 6 on
page 36.
a. Click on the other SmartCard Reader in the list, then click the
Change button.
b. On the Set Binding dialog that appears, select another letter from
the drop-down list. Then click OK.
c. Click on OMNIKEY AG Smart Card Reader, then click the Assign
button.
6. Close the SafeGuard SmartCard Provider window, and click OK on
any popup that appears.
7. Remove your dongle form the computer and reboot your computer.
8. Once you computer has rebooted, make sure you log on to IST.
9. Open the IST Control Panel by double-clicking on the blue IST lock icon.
10. On the IST Control Panel, make sure your IST Client is running.
11. Insert your IST dongle into a USB port on you computer. The IST dongle charging window will appear, and indicate
the successful transfer of your IST certificate. Your dongle is now ready to use on customer systems.
12. To verify that your SmartCard dongle is charged, check the IST control panel and look for the recognized devices.
The top seven digit number is the SmartCard

Device ID. The bottom 10 digit number is the
computer device ID number.
Each device has a copy of your secure
certificate.
It is possible to have more devices on the list.
IST allows multiple devices (dongles,
computers, etc.) to have the same certificate.
A single device can NOT have multiple
certificates.
Audio Test
Audio Test
To run the Audio Test:

1. Launch the Service Tools Framework.
2. Click the Diagnostics Workflow button at the top of the window.
3. On the Application List, select Audio Test.
4. Audio Test Tool will open in STF.
5. Select a test, and click the Start button.
Mode Test Name Summary Expected Test Results

Automatic CT-Box Speaker Test Click Start Verify that you hear a response (the recorded word “breathe”) from the Scan Control
Box speaker.
Automatic Gantry Speaker Test Click Start Verify that you hear a response (the recorded word “breathe”) from the Scan Control
Box and Gantry speakers.
Backup and Restore
Backup and Restore

To perform a Backup, see below. To perform a Restore, see Restore on page 42
Backup
1. On the Service Tools Framework, click the Repair workflow button.
2. On the Application List, select Backup and Restore.
3. On the Backup/Restore dialog, select the Backup tab (see Figure 1).
4. On the Backup/Restore dialog, click the Browse button.
5. In the Browse for Folder window, go to the storage location.
6. Click OK.
NOTE If you are performing a backup to an external device, another
copy of the backup will be saved to D:\Temp.
7. Select all of the options (see Figure 1).
8. Click Start Backup.
9. A log window appears, and displays the progress of the backup.
Figure 1:
Backup
10. When backup is complete, END BACKUP appears (see Figure 2). Scroll up and check for errors.
Figure 2:
11. Click Close on the Log window (see Figure 2).
12. Click Exit on Backup/Restore dialog.
Restore
Restore
1. On the Service Tools Framework, click the Repair workflow button.
2. On the Application List, select Backup and Restore.
3. On the Backup/Restore dialog, select the Restore tab (see Figure 3).
4. On the Backup/Restore dialog, click the Browse button.
5. In the Browse for Folder window, go to the location of the backup file.
6. Select the backup file to restore.
7. Click OK.
8. Select all of the options (see Figure 3).
9. Click Start Restore.
10. A log window appears, and displays the progress of the restore.
Figure 3:
Restore
11. When the restore is complete, a Restore Complete popup appears. Click OK.
Figure 4:
12. On the Restore Log, scroll up and check for errors.
Figure 5:
13. Click Close on the Log window (see Figure 5).
14. Click Exit on Backup/Restore dialog.
BugRep Collector
BugRep Collector
The Service Tools Framework BugRep Collector gathers logs and other information from the Gantry, Console, Couch,
and CIRS.
2. Click the Analysis Workflow button at the
top of the window.
3. On the Application List, select BugRep
Collector.
4. In the column list under Bugrep Collector,
make sure all items are selected.
5. Enter the following information:
• Your name.
• The problem.
• Time of the event.
• A description of the problem.
6. Select if the problem is an intermittent or
persistent problem.
7. Click Browse, and go to where you want to
save the Bug Report.
8. Click Collect Bugrep.
BugRep Collector
While the application runs, you can view the progress in the Status bar at the bottom of the Service Tools Framework.
Figure 6:
When the application finishes, the Status Bar displays a message, and the Error and Warning Messages area shows
any error and warning messages.
BugRep Collector
BugRep Collector Archives

Click on the Archives tab to display previously collected Bug Reports. There are four function buttons at the bottom of
the screen:
Refresh: Refreshes the list of Bug Reports.
Delete: Deletes a Bug Report.
View: Opens BugRep Viewer so you can look at the Bug Report.
CopyTo: Opens a Browser For Folder dialog, so you can copy the Bug Reports to external media.
Bug Reports
Functions Buttons
Function Buttons
Bugrep Viewer
Bugrep Viewer
The Bugrep Analyzer/Viewer simplifies problem reports analysis. It will load bug reports from a repository, automatically
analyze files included in the report, and display the found problems. The Bug Report contains many files in different
formats. The Analyzer displays a list of files with color-coded status for each format. Viewers for different formats are
integrated into the Analyzer and are loaded by double-clicking on the corresponding file.
The Bugrep Viewer, shown at right, uses an interface
similar to that of the Windows Explorer.
The left section of the Bugrep Viewer shows
Categories that reflect the logical hierarchy of the files.
Because of this, files from different directories may be
found in the same Category. The same file may also
appear in multiple Categories.
The right section of the Bugrep Viewer shows
Summary files, resulting from automatic file analysis.
When a Summary file is opened, its internal records
may be color-coded to reflect their status. Alerts are
displayed in red; warnings are displayed in yellow.
The Bugrep Viewer provides error code definitions for
different log files. The error code definition consists of
4 fields:
• Log file name
• Text pattern corresponding to the error
• Error code
• Error description
To open a BugRep file, see Opening a BugRep file on page 48. Also, see Bugrep Viewer Options on page 52 for more
information.
Opening a BugRep file

2. Click the Analysis Workflow button at the top of the window.
3. On the Application List, select BugRep Viewer.
4. The BugRep Viewer window will open (see Figure 7).
5. On the File menu, click Open Bugrep.
Figure 7:
6. The Open Bugrep in Tar Format dialog box appears (see Figure 7).
7. Select a Bugrep file and click Open. The selected file will be loaded into the Bugrep Viewer.
Figure 8: Opening a Bugrep File

8. Continue with Interacting with Bugrep Files on page 50.
Interacting with Bugrep Files
To select an individual Log file for viewing:

1. Double-click on the file. The Log File window
opens.
2. You can now move through the selected file
and examine its contents, using the mouse,
keyboard, or the various navigation
elements at the bottom of the Log File
window. For more details on using these
navigation elements, see Log File Window
Navigation on page 51.
Figure 9: Log File Window
NOTE Whenever an error message is selected, the highlight is enlarged slightly to differentiate it from other
error messages, and make viewing easier. When an error message contains an alert or warning indication,
it will appear highlighted in one of the following colors: Alerts will appear in Red, Warnings will appear in
Yellow.
Log File Window Navigation
Function Description
Click these buttons to skip from one highlighted with an error message row to the next.
Search Text Box, Find Next
Enter text to search for in the Search text box. Searching is case sensitive. Choose Down
or Up to determine the direction of the search. Click the Find Next button to continue
searching for the next occurrence.
Click this button to return to the cursor location when it is off the screen. This function is
useful when you want to search through the entire file for additional information, and then
return to your original location in the file.
Copies all rows found in last search into a new window.
Export Content (accessed from the File menu)- saves contents of search window as a text
file.
Removing Bugrep Reports from the System
Removing Bugrep Reports from the System

To erase an entire Bugrep report from the system:
1. Select File | Remove Reports. A file list of reports appears.
2. Select the Bugrep report you want to erase, and click Remove. A confirmation window appears.
3. Click Yes to confirm its deletion.
NOTE When you remove a Bugrep Report form the system, the Logbook is also updated. The hyperlink for the
deleted report is changed from Show to Erased.
Bugrep Viewer Options

The Bugrep Viewer enables you to perform the following additional activities, to support solving problems:
• Analyzing the current state of the system.
• Viewing multiple Bugrep analyses.
• Running System Monitor using a selected Bugrep report, enabling you to recreate the environment that existed at
the time the bug was reported.
• Opening a UNIX console (csh window) to enable a service technical to perform tasks and run environment-specific
commands.
Analyze Current State

This option enables you to create a Bugrep report of the current system state on demand. It displays the report in the
Bugrep Viewer and performs an immediate analysis.
To analyze the current state of the system:
1. Select Options | Analyze Current State.
Bugrep Viewer Options
View Multiple Analyses

This option enables you to combine numerous events (errors) found in the Bugrep log files, and automatically analyze
results. The findings are then displayed for review. Generally, a multiple analysis is used to pinpoint the initial cause of a
series of errors.
To view multiple analyses simultaneously:
1. Select Options | View Multiple Analyses.
2. The analyses will be performed, and a summary window appears.
Running System Monitor on Bugrep

To run System Monitor on a selected Bugrep report:
1. Select Options | Run Sysmon Over Current Bugrep. For more information, see the System Monitor Utility.
Opening a UNIX Console

To open a UNIX shell to perform tasks or run environment-specific commands:
1. Select Options | Open Console.
CAN Analyzer
CAN Analyzer
CAN Analyzer provides analysis functions for messages transmitted on the CAN network. This tool expands the
capabilities of CAN Trace. CAN Trace keeps a database of all messages that are transmitted on the CAN Network.
CAN Analyzer provides query operations on that database so you can look at statistical information based on CAN
messages transmitted over a period of time. For example, you can plot the couch movement positions, or the time that
each new series was loaded. CAN Analyzer provides three areas to view/enter information. These are the Report Area,
the Query Area and the Charting Area.
To use CAN Analyzer:

1. Start the Service Tools
Framework.
2. Click the Utilities Workflow
button at the top of the
window.
3. On the Application List,
select CAN Analyzer.
Report Area
Report Area
This area at the top of the screen shows the results or "reports" of
queries made to the database in a table format. At the bottom of the
this area is the Query Area that indicates the query that generated
this report. When you open this page, there is a default query
Select All From Tube History in the New Report Name field, and
the Report Area will show the results of this query. This query has all
fields that relate to the tube. User defined queries can be made, and
queries can be loaded and saved using the Query Area.
Query Area
The Query Area is just below the Report Area. Use the Query Area to execute predefined queries, save queries, and
create user defined queries
Report Statement You can create a user-defined query by entering appropriate SQL statements in this field.
New Report Name When you open Tube History, there is a default query Select All From Tube History in this field,
and the Report Area will show the results of this query. This query has all fields that relate to the
tube.
Saved Reports To select predefined queries, use the drop-down list. All predefined queries and any saved
queries will appear in the list.
Save As Text To save results of a query, click the Save As Text button. This will save the current results from
the Report Area into the file C:\TubeHistory.txt in tabular format. This text file can be used
independently, and it can be copied and pasted to Excel or other data related programs.
Requery When you select a query, the Report Area will not update until you click this button.
SaveQuery To save a query, enter a name in the New Report Name field, and click the SaveQuery button.
DeleteQuery To delete a query, select a query from the list and click the Delete Query button.
Charting Area
Charting Area
This area graphically displays data from the Report Area. It can show
information in different plot types including bar, pie, X-Y, trends, 2D, and 3D
charts. At the top-left of this area there is a dropdown list that shows the
selectable plot types. At the top-right of this area, there are check boxes to
show and hide the following plot attributes:
Legend Shows the names for the current series at the right.
Marks Shows all values in all series with special marks.
Stack Reorganizes all values in all series in such a manner that the
value from the next series will be always bigger that the previous
one.
In Rows Flips series data from columns (the default) to rows (similar to a
vertical-horizontal flip in table data). To change the type of the
plot, select the appropriate one from the drop-down list at top-left.
When a query is saved, the current chart setting are saved along with the
query. These settings are when the query is selected at a later time.
Tips for Queries and Charts

• All queries use standard SQL syntax. See Appendix A: Tips on how to use SQL for queries on page 281.
• The chart shows the same data currently present in the report area.
• For "Legend" series names, the chart is looking for the name of the columns (the headers). These headers are
formed from fields that have been typed in a SELECT clause. To change the field name, use the AS flag. For
example: "SELECT lastMeasuredCurrent AS mA,..." will get mA as the name of the field. If you apply any math to
the field, it will cause "ExpressionN" as a name, unless you use the AS statement. For example: "SELECT
lastMeasuredCurrent/100 AS mA,..."
• To mark the X-axis, the chart will look for the first column that has data in a string format. If it finds nothing it will use
"R1......RN" as the X-axis mark.
• Use conversion functions to manipulate data formats. You can also use VBScript functions (to show date stamps on
the X-axis use "Select CStr(ShotDate) as STime....").
CAN Send
CAN Send
This tool sends messages on the CAN. The CAN is a network that connects all the processing modules in the Gantry
and the Host PC. The modules communicate by sending messages on the CAN network. Using CAN Send involves:
• Selecting a message to send.
• Editing the data within the message.
• Clicking the Send to Can button to send the message.
To use CAN Send:

1. Start the Service Tools Framework.
2. Click the Utilities Workflow button at the top of the window.
3. On the Application List, select CAN Send.
CAN Send allows you to send any message that has been defined in the system. It is a powerful tool because it can
send a message that would normally be sent by one of the processor modules. For example, you can use it to turn on
or turn off switches in the system. Because of this, you should be aware of the function and purpose of each message
that you send.
Category Area Data Area
Selection Area
Category Area
Category Area
This area on the left of the screen shows a list of message categories. Within a category, there may be many
messages. A category is selected by clicking in the check box in front of the category type. When a box is checked,
each message from that category will appear in the Selection Area. Note that at the top of this area is an ALL category
which will display all the system messages in the Selection Area if checked.
Selection Area
This area in the middle of the screen shows all messages from each category selected in the Category Area. The
message name is displayed along with the message ID, which is a unique number that defines the message on the
CAN network. When you click a message, the message parameters will appear in the Data Area of the screen. Click the
column header MsgName to reorder the list alphabetically by message name. Click the column header ID to reorder
the list numerically by message ID.
Data Area
This area on the right of the screen displays the message parameters of a message that is selected in the Selection
Area. Each parameter's value can be modified by click on the data value in the Value column. To make it easy to enter
data values, you can load and save data from and to this control. Loading and saving is done using the buttons at the
top of this control.
Once the desired data values are entered for each parameter in the message (or loaded from a file), clicking on the
Send to Can button will send the message. Note that some messages may have no parameters so no data will appear
in the Data Area. These messages are essentially "signaling" messages.
Message data saved using this control can be used in other tools that use this same control. For example, saved
parameters can be used later by Can Sender itself, or by the Manual Exposure tool, the No Load Test tool, and others.
CAN Trace
CAN Trace
CAN Trace monitors activity on the CAN. The CAN is a network that connects all the processing modules in the Gantry
and the Host PC. The modules communicate by sending messages on the CAN network. CAN Trace maintains a
database of all messages that are sent on the CAN.
To use CAN Trace:
2. Click the Utilities Workflow button at the
top of the window.
3. On the Application List, select CAN
Trace.
Category Area
Using CAN Trace involves selecting the message category to monitor, filtering unwanted messages and possibly
viewing message data. The screen has four major parts: the Category Area, the Message Area, the Data Area, and the
Filter Area.
Category Area
This area is on the far left of the screen and shows a list of message categories. Within a category, there may be many
messages. A category is selected by clicking in the check box in front of the category type. When a box is checked, the
program will re-query the database and show only the messages from the selected category or categories in the
Message Area. Note that at the top of this area is an "ALL" category. If this category is checked, the program will display
all the messages from the database in the Message Area.
Message Area
Message Area
This area is in the middle of the screen and shows all the database messages from each category selected in the
Category Area. The message time, message name, message ID, and board ID are displayed. The messages are
ordered by time. The message ID is a unique number that defines the message on the CAN network. When a message
is clicked, the message parameters will appear in the Data Area of the screen.
Data Area
The third part of the display is the Data Area to the far right of the screen. This area displays the parameters of a
message that is selected or clicked in the Message Area. This is a standard message control that is used throughout
Service Tools. This area allows you to save message data by using the buttons at the top of this control.
Message data saved using this control can be used in other tools that use this same control. For example, saved
parameters can be used later by Can Sender, the Manual Exposure tool, the No Load tool, and others.
Filter Area
Filter Area
Because many message are sent on the CAN, it is useful to filter out certain messages. Messages are filtered or
"blocked" by using the Filter Area. This area is on the bottom portion of the display screen.
The Filter Area will show all the messages from each category selected in the Category Area. These messages will
appear in the column labeled "Available Messages". Individual messages can be blocked from display in the Message
Area by selecting them (clicking on them) and then clicking on the right arrow button in the middle of the filter display.
This will move the message to the column labeled "Blocked Messages". The left arrow button can be used to unblock a
message and move it back to the "Available Messages" list. The "Select All" and "Deselect All" buttons can be used to
block and unblock all the messages.
There is a special button that makes it easy for the user to block a specific message that appears in the Message Area.
This button is the “Block Selected Msg(s)” button and it is located at the top left of the display screen. Select a message
in the Message Area, and click on the “Block Selected Msg(s)” button. This will add the messages to the “Blocked
Messages” list and block the message from the Message Area.
Additional Features
Additional Features
There are some special features that make this tool more useful.
• Show Last appears at the bottom-left of the display. This controls the number of the most recent messages
displayed from the database. Changing this number effects the update rate of the Message Area. If this number is
large, the database query will take more time. If this number is small, the database query will be faster and the
Message Area will update more quickly.
• Find appears at the top-center of the display. Enter a string in this field and click the button, and CAN Trace will
search the Message Area and highlight the next occurrence of this string.
• At the top-right of the display, there is a Stop Update and a Transform check box. When Stop Update is checked,
CAN Trace will stop updating the Message Area. The Transform check box becomes available only if more than
two message categories have been selected. This feature breaks down messages in the Message Area based on
the message name column by categories. This presents the data in a form similar to a sequence diagram.
NOTE There are some messages in the system that occur frequently and periodically. Because these messages will fill up
the Message Area very quickly, it is convenient to block these frequent messages so that more critical messages
can be observed.
NOTE CanTrace will not work properly if CanTraceServer.exe is not running. If CanTraceServer.exe is not running, new
messages will not be written to the database file, and the Message Area will only show "old" data from the
database file. If CanTraceServer.exe is running, it will show up as a process in Windows Task Manager. If it is not
running, start it by navigating to C:\usr\dimond.root\bin\gantryservers, then double-click on CanTraceServer.exe.
CanTraceServer.exe is normally started when a user logs onto the system. You cannot start multiple instances of
CanTraceServer.exe. Only one server will run at a time.
CAT Viewer
CAT Viewer
When using CAT Viewer, click the Help button for extensive online help.
CIRS Diagnostic Viewer
CIRS Diagnostic Viewer

The CIRS Diagnostic Viewer allows you to connect to a CIRS server remotely.
3. On the Application List, select CIRS Diagnostic Viewer.
4. From the drop down menu, select the server. Then click the Connect
button at the bottom of the column.
5. In the window, you will see the sever

desktop. You can run any of the CIRS
diagnostics from here.
6. To choose another server, first click the
Disconnect button at the bottom of the
column. Then choose another server from
the drop-down menu and click Connect.
CIRS Visual Diagnostics
CIRS Visual Diagnostics

NOTE This tool is not available for Brilliance 16.
This application lets you run the Acquisitor, NGBP, and NVIDIA GPU diagnostics from the Host Computer. For the
Acquisitor Diagnostics you will need the Optical and Electrical loopback cables. Always reboot the gantry after using
CIRS Visual Diagnostics.
See:
• NGBP Diagnostic on page 67
• Acquisitor Diagnostic Optical
Tests on page 69
• Acquisitor Diagnostic Electrical
Tests on page 74
• NVIDIA GPU Diagnostic on page
77
NGBP Diagnostic
NGBP Diagnostic
This test runs the NGBP Diagnostics. For more information on the tests that run, see the CIRS Service Manual.
1. Select CIRS.NGBPDiagnostic.
2. Click the Start button.
Select CIRS.NGBPDiagnostic
While the test runs, you will

see a progress bar.
NGBP Diagnostic
3. When the test is complete, you will see the results page.
Figure 10:
4. If this is the only CIRS Visual Diagnostics test you run, then reboot the gantry after closing CIRS Visual Diagnostics.
Acquisitor Diagnostic Optical Tests

This runs the Acquisitor Diagnostics Optical Loopback Tests. For more information on the tests that run, see the CIRS
Service Manual.
1. Select CIRS.ACQDiagnosticOP.
3. The application tells you to connect the Acquisitor Optical Loopback Cable:
!
CAUTION Do not click the Continue button until after you connect the Loopback Cable!
a. Write down the order of where each fiber optic lead connects to the Acquisitor, then remove the four fiber optic
leads and four spacers from the Acquisitor. See Figure 11.
NOTE The figure shown below is the factory standard. Your leads may have been inserted in a different order.
Spacer
Fiber Optic Lead
Figure 11:
b. Connect all eight leads of the optical loopback cable from left to right shown in Figure 12 and Figure 13.
Figure 12:
Figure 13:
c. Click the Continue button.
Figure 14:
4. After the test completes, the application tells you to disconnect the Optical Loopback cable, and reattach the
Acquisitor cable fiber optic leads. Again, do not click the Continue button until after you have re-attached the
fiber optic leads!
a. Re-connect the Acquisitor cable fiber optic leads, and insert the spacers. See Figure 15 and Figure 16.
NOTE The figures shown below are the factory standard. Your leads may have been inserted in a different order.
Figure 15:
Figure 16:
b. Click the Continue button.
5. The Application will show the results page.
Figure 17:
Acquisitor Diagnostic Electrical Tests

This runs the Acquisitor Diagnostics Electrical Loopback Tests. For more information on the tests that run, see the CIRS
Service Manual.
1. Select CIRS.ACQDiagnosticES.
3. The application tells you to connect the Acquisitor Electrical Loopback Cable:
!
CAUTION Do not click the Continue button until after you connect the Loopback Cable!
a. Remove the gray Acquisitor Electrical cable, then attach the Electrical Loopback cable. See Figure 11.
Attach one end of the loopback

cable to the Acquisitor Board....
...and attach the other
end to the port on the
server chassis.
Figure 18:
Figure 19:
4. After the test completes, the application tells you to disconnect the Electrical Loopback cable. Again, do not click
the Continue button until after you have re-attached the Acquisitor Electrical Cable!
a. Remove the Electrical Loopback cable, and re-connect the Acquisitor Electrical cable to the Acquisitor.
5. The Application will show the results page. If this is the only CIRS Visual Diagnostics test you run, then reboot the
gantry after closing CIRS Visual Diagnostics.
NVIDIA GPU Diagnostic

This runs the Acquisitor Diagnostics Electrical Loopback Tests. For more information on the test that runs, see the CIRS
Service Manual.
1. Select CIRS.GPUDiagnostic.
3. When the test completes, it will show the results page.
Coast Down Test
Coast Down Test
Coast Down Test measures the rotor bearing friction of the gantry. The
test rotates the rotor to a certain speed, and then measures the time it
takes to coast down to a stop.
Information area
Displays a series of messages to guide you through the test.
Requested Rotor Speed (RPM’s)

Drop-down list that allows you to select the starting rotor speed.
Begin Button
Starts the rotor. When rotor is up to speed, this button changes to
Start Test.
Abort Test Button

Aborts the test.
Speed
Indicates the speed from which the coast down took place, and is
displayed in rotations per minute.
Time
Indicates the time measured by the rotor controller in the gantry, and is displayed in 10ths of milliseconds.
Elapsed Time (seconds)

Counts each second the coast down process takes. When test is complete, this field indicates the time measured
by the test software.
Graph
When the test is complete, the graph will plot the speed in RPM's against the time in seconds. If you check the
Logarithmic box, the graph will plot the natural logarithm of the speed against time. The large dashed lines
represent the mean and the small dashed lines represent the standard deviation.
Perform the test
Perform the test

1. Select the starting rotor speed from the Requested Rotor Speed drop-down list.
2. Click the Begin button. The rotor will spin up to the requested speed, and you will see the message "Rotor is being
started. Please wait until rotor is up to speed."
3. When the rotor is at speed, the Begin button will change to Start Test and you will see the message "Rotor is at
speed. Press <Start Test> to begin coast down".
4. Click Start Test to start the coast down, and you will see the message "Coast down has been started. Please wait
until rotor stops."
5. When the rotor stops, you will see the message “Coast down complete! Press <Begin> to start a new test.” This
indicates the test has completed successfully, and the time is displayed.
If the test software does not receive proper acknowledgement from the gantry during the test, you will see the message
“Coast down request failed. The Rotor is not acknowledging the coast down request. Suggest pressing <Abort Test>”. If
this message appears, click on the Abort Test button and attempt the test again. At any time during the test, you may
click Abort Test to terminate the test.
If the bearings are in proper condition, the rotor should coast down in a specified time. The bearing specifications will be
supplied by the CT Service Department. Verify that the coast down time is within specification.
Configuration Settings
Configuration Settings
Configuration Settings works with Windows Registry Settings that define configuration for the different Host
applications. In particular, Logger, CanTrace, GSE, CanBus Simulator and others.
NOTE The following sections show the default configuration settings.
• To apply a new setting, click the Write Values to Registry button.
• To read the current setting from the Windows Registry, click the Read Current From Registry button.
• To restore the default settings, click the Restore Defaults button.
Databases
Databases
Logger Database
The server program, LoggerServer.exe, runs in the background on Host machine and dumps all error and event
messages to the Logger database file (Logger.mdb). The Logger Identical Messages Rejection Interval in
milliseconds field allows you to set the interval time, so that if LoggerServer receives the same message within that
interval it will refuse to save it to the database.
CanTrace Database
The server program, CanTraceServer.exe, runs in the background on Host machine and dumps all messages that go
through the CAN BUS to the database file (CanTrace.mdb). CanTraceServer saves information about the that shot has
been made by scanner into a separate table (ShotsHistory.mdb). Tube History is the subset of this information. The list
of Available Items shows the messages you can block from being saved to the CanTrace database file, and Selected
Items shows the messages you have selected to block from the CanTrace database file.
GLC
GLC
GSE
Gemini
Gemini
PETMS
MotionTable_107
MotionTable_107
ConfigTable_100
ConfigTable_100
CanBus Simulation
CanBus Simulation
These settings are for the GantryServers applications and utilities (including GSE), and for those applications that are
using CanMsgServers.dll as CAN BUS communication engine. Based on the boards and components that are used in
scanner there is a list of such components user could switch on/off simulation of the CAN BUS. When any of such
components is turned on - there is a CanBusSimulator Server that reroutes messages belongs to that component
locally, not to the CAN BUS itself. If user chose Simulate All - all messages will be circulated inside of the PC from the
local sender to the local receiver. Communication objects inside CanMsgServers.dll will decide based on this on/off
settings which message send to the CAN BUS and which message send locally through the CanBusSimulator Server.
Controller Utilities

3. On the Application List, select Controller Utilities.
4. The Connect as: option gives you the choice of connecting as:
• Field Service Engineer - Error messages are limited to pass/fail. Tests use default values and therefore do not
prompt for test parameters.
• Zone Specialist - Detailed error messages are displayed. Tests prompt for test parameter entry.
After selecting either Field Service Engineer or Zone Specialist, click the Connect button in the upper right hand
corner.
At initial use, the Server has not been configured. The Options menu allows you to enable the CAN or the serial driver.
If you are connecting through the Host PC, CAN access is the best way to go. If you connecting through a laptop, serial
is the only alternative.
Once you select an access option, the Server creates a file called Config.txt in C:\usr\diamond.root\Diag\Config.
This file contains the access choice. After initial use, Controller Utilities will always default to your initial access choice
when you click the Connect button. To change your access choice, you must delete the Config.txt file and restart the
Server.
When you select CAN access to controllers, the next display appears.
There are two status indicators for the CPMs appearing in the Ordinary Text window. The first one indicates what mode
the CPMs are in, application or utility mode. The other status indicator informs you which driver is currently enabled.
The option Application mode puts the CPMs in the app mode and sends a message to all Gantry Controller cards.
This message causes any cards that are in Service mode to reset and boot up into the application.
The option Service mode puts the CPMs in Service mode and sends a message to all of the cards. If any of the cards are running the application, they reset themselves and boot
into Service mode.
Service Mode
By making the Service mode selection, all boards present in the system and communicating are put into service mode.
The following information is then displayed describing the behavior of the Server:
This Server operates as a Supreme Controller.
It allows all the Gantry Controllers to be put into utility or application mode. While this
Server is running, it is in control of what mode the Controllers boot to. With the Server in
utility mode, a gantry power cycle, individual CPM push button reset, or reboot from the
baseboard menu will boot the board(s) back into utility mode. With the Server in application
mode, a gantry power cycle or push button reset will boot the board(s) into application mode.
Exiting the Interface does not stop the Server from running. When the Server is not running, a
push button reset or power cycle puts the board(s) in application mode.
Service Mode
Selecting Service mode through either Serial or CAN Access leads to the next menu in the Options window.
The Service mode menu consists of a Utilities, Diagnostics, Connect to controller, and Return option. The Utilities are a
collection of maintenance tools that allow the Operator to do things such as back up and restore the NVRAM and to
upgrade/downgrade the application and boot flash. The Diagnostics are some tools for the purpose of evaluating the
functionality of the gantry controller boards. The Connect to controller option is for interacting directly with a specific
controller board's built in test and utility functionality.
Utilities Menu
Utilities Menu
Clicking the Utilities Button will display the menu shown at right.
The menu now makes use of check boxes. The top grouping of options shows all
the boards that can be selected for participation. Click in the check box to select a
board. You can also select multiple boards. The middle grouping of options shows
all the utilities that can be executed on all the selected boards. The utilities
execute in a top to bottom order. Each utility will execute to completion on all
selected boards before the next checked utility is started.
Make your selections, and then click the Submit button to execute the utilities.
The Save NVRAM utility uploads the entire content of the selected board's
NVRAM to a file on disk. The location and filename can be observed and changed
by first selecting File configuration and clicking on Submit. The default location is
the C:\usr\diamond.root\Diag\Backup directory. The format of the filename is
boardnameNVRAM.bin, where boardname is ghost, rhost, couch, etc.
The RAM downloader utility downloads executable code from a file on disk to the
RAM of a selected board. The location and filename can be observed and
changed by first selecting File configuration and clicking on Submit. The default
file to download is C:\usr\diamond.root\Diag\CPMIntFlash\CPMIntFlashImage.bin.
The Backup boot flash burner utility burns a back up version of the boot flash
over top of the application in external flash. This is used to create a more robust
environment for altering the content of the boot flash. In the event of a boot flash
burn being prematurely aborted, the presence of the back up boot flash in external
flash allows the boot flash burn to be resumed. The location and filename can be
observed and changed by first selecting File configuration and clicking on Submit.
The default file to burn is
C:\usr\diamond.root\Diag\CPMExtFlash\CPMExtFlashImage.bin.
The Boot flash burner utility allows a new boot image to be burned into internal flash. The location and filename can
be observed and changed by first selecting File configuration and clicking on Submit. The default file to burn is
C:\usr\diamond.root\Diag\CPMIntFlash\CPMIntFlashImage.bin. As a pre-requisite, the Backup boot flash burner should
be run. In the event that the Boot flash burner is prematurely aborted, whether from a power cycle, CPM reset, or the
software stopping execution, the backup would allow the board to boot up and the boot flash burn to be restarted.
The Application flash burner utility allows a new application image to be burned into the external flash. The location
and filename can be observed and changed by first selecting File configuration and clicking on Submit. The default file
to burn is found in the directory C:\usr\diamond.root\GantryCPM. Each board is automatically paired up with the image
appropriate for it.
Utilities Menu
The Controller reset utility is used to reset the selected controller board. This is mainly here for the purpose of
verification of a boot flash burn. Next to each board name is the current release and memory that release is running
from. In order to burn the boot flash, the Operator must download a boot image to RAM. If the boot image was in RAM,
this display would indicate “Release x.x in RAM”. By selecting and submitting the Controller reset, when the menu
updates, it indicates whether the boot flash burn was successful or not.
The Restore NVRAM utility downloads the content of a file on disk to the NVRAM of a board. The location and filename
can be observed and changed by first selecting File configuration and clicking on Submit. The default location is the
C:\usr\diamond.root\Diag\Backup directory. The format of the filename is boardnameNVRAM.bin, where boardname is
ghost, rhost, couch, etc.
The reason this utility is not grouped with the check boxes is because under normal circumstances it is not necessary to
restore it.
The Zero NVRAM utility is used to destroy the content of the NVRAM for the purpose of moving it to another board.
The File configuration utility is used to set up which files the file using utilities use. The File configuration menu allows
the Operator to display and override the files currently in use for the particular utility. I
The Loops option of the Utilities menu allows a non-FSE Operator to chose the number of times the selected utilities
execute.
The Return option allows the previous menu to be returned to.
Diagnostics Menu
Diagnostics Menu
The menu functions like the Utilities menu. Select the boards, select the utilities to run, and
then click the Submit Checkbox) button. The selected tests are run on the selected
boards.
The CPM test executes the power on tests for the selected boards.
The CAN test transmits pseudo-random data from the PC to the selected boards. The
boards CRC test the data and echo it back where the Server CRC tests the data again.
The Save/test/restore NVRAM test is a non-destructive test of the selected board's
NVRAM. First, the entire content of the NVRAM is copied to a file on disk, the NVRAM is
exercised, and then the data is restored. The test portion does not proceed if the back up
does not exist or is too small.
The purpose of the CPM swapper utility is to allow you to determine if a problem exists on
a CPM. If by moving the CPM, the problem follows it, the likelihood of the defect being on
the CPM is high. The CPM swapper automation utility constructs a dynamic menu based
upon boards it finds in the system. Boards not found are labeled with NO RESPONSE.
Boards found at releases prior to release 1.5 are labeled PRE-1.5 RELEASE. The first two
post release 1.4 boards that are found are left enabled by default, but may be disabled from participation in the swap.
Another board may be enabled in it's place. Once the Execute option is submitted, both enabled boards have the entire
content of their NVRAM uploaded to a uniquely named file located in the C:\usr\diamond.root\Diag\Backup directory.
The format of the filename is boardnameNVRAM.bin, where boardname is ghost, rhost, couch, etc. The content of
each NVRAM is then downloaded to the other board and written to that board's NVRAM. Each board opens the file in
C:\usr\diamond.root\GantyCPM that corresponds to the other boards application flash. The application flashes are
then burned. Once the process completes, the gantry can be powered down, the CPM's from the enabled boards
physically swapped, and the gantry powered back up. It's important to run the Save/test/restore NVRAM test before
running the swapper. The reason is that if the NVRAM is not working, then the data that comes out of the NVRAM
during the CPM swapper execution will be bad and will therefore contaminate the CPM the data is going to. There is a
possibility that both CPMs would then begin failing.
The File comparison utility allows you to determine if two files are the same or not. In the event that a person has just
burned the application flash or the boot flash and they are concerned about it's integrity, they have some means to
come to a conclusion. If the Upload as binary utility located on the Utilities menu on each board via the Software
Engineer Operator role is used, the content of the application or boot flash can be uploaded to a file on disk. This file
can then be compared with the file that was just burned. For both the application and boot flash, use an access size of
32 bits in the Upload utility. For the address, use 0 for the boot flash if it is running from internal flash and 0x400000 if it
is running from RAM. For the external flash, use an address of 0xff800000. For the size, use 0x70000 for the internal
flash. For the external flash, get the size from the file you are going to compare the upload to.
Connect to Controller
IMPORTANT ! In the event the Service Tools GUI hangs during execution of any of these utilities, the
operation continues regardless. If the Service Tools GUI is started up before the process
ends, the Operator will pick up seeing the User Feedback from the point at which the
connection is re-established. The Utility Interface is much more robust, but even if it did
crash, it too could be reconnected to the continuing process.
Connect to Controller
Click the Connect to controller button to display the menu at right:
The Server sends a message to all the boards in the system. Those boards that
respond are put on the menu with the ability to connect to them. Those boards that
do not respond are displayed with a status of NO RESPONSE. Therefore, the
menu itself has diagnostic value. Second of all, if the board that responded is at a
release of 0.3, 1.0, 1.2, or 1.4, it's status will be PRE-1.5 RELEASE. One
interpretation of this is that the boot flash should be upgraded or an old release is
running from RAM. Last of all, if the boot flash is at release 1.5, 1.6, or 2.0, then the
status will indicate which release is present and what memory it is running from.
These are the three possibilities:
Release X.X Boot flash
Release X.X in RAM
Release X.X App flash
where X.X means 1.5, 1.6, or 2.0
Release X.X Boot flash means that the framework is running from internal flash, the usual location. Release X.X in RAM
means the framework is running out of external RAM which occurs after the Operator downloads the binary to RAM.
Release X.X App flash means the framework is running out of external flash where the application normally resides.
This happens after someone has burned the back up boot flash into application flash, starts a boot flash burn and
aborts it before it finishes.
NOTE The Host PC use of the CAN bus is disabled when the Gantry is in Service mode.
Controller Boards menu
Connecting to MDP or Tilt

In the past, the MDP or the Tilt boards had to be in utility mode before they could be selected from the menu on the Host
PC Server. This is no longer true because of the Service mode option. Since the boards are now in Service mode, these
boards can be connected to immediately from the menu on the Server.
The connection to the Main Drive or Tilt can also be performed via the GHost. After connection is made to the GHost an
option, "Connect to Controller" is presented. By selecting the "Connect to controller" option and hitting SUBMIT the
Operator will be provided the choice to connect to the Main Drive or Tilt. Selecting the TDP or MDP and selecting
SUBMIT will connect the Operator to the desired controller board. The original communication to the board takes place
over the serial line leading from the Ghost to the board of interest, but once communication is established, the
framework switches communication to be directly between the Host PC and the destination board via the CAN bus.
NOTE The Application utility ResetBoards is NOT needed for release 1.0 and greater. The GHost will send an
Application reset message to the application running on the Main Drive or Tilt. Initial diagnostic communication
occurs between GHost baseboard serial ports and the Main Drive or Tilt board.
NOTE If the connection is successful, the Event window will display “Contact established.” If the HostPC server is used,
the connection is direct between the MDP or Tilt and the HostPC server, bypassing the GHost. If the Server is
used with the serial cable, the connection is between the MDP or the Tilt and the GHost and then from the
GHost serial channel to the computer the Server is running on.

Clicking on a Controller button will display a menu with the following three
options: Toolbox, Reboot, and Return.
NOTE The GHost presents an extra option, Connect to controller.

At the top of the Controller menu, there appears the name of the baseboard the server is connected to, the revision, and
revision date.
Baseboard type: 0
Baseboard firmware rev: None
The contents of the Baseboard Revision and Type Registers are listed at the head of each of the Baseboard Menus as
an ASCII value (Baseboard Firmware revision) and hex value (Board Type). The Baseboard Revision and Baseboard
Type are displayed in the Utilities and Baseboard menus only.
Toolbox
The Toolbox options are CPM, Utilities, and Return.
CPM
The CPM menu options are LED, Flash, Serial, CAN, NVRAM, and Return.
LED Test
The LED test will blink the LED. The register controlling the LED is written to and read back and verified for both the on
and off condition. The Operator is expected to visually check that the LED3 turns on and off.
The Operator can Repeat or Quit the LED test. If the Operator Quits a pass/fail message will be displayed. Selecting
Continue will return the Operator to the previous menu.
CPM Flash Menu

The flash CRC test will calculate the CRC (Cyclic Redundancy Check) of the internal flash of the PPC555.
Internal Flash CRC - 32 bit Test

The internal flash of the PPC555 is calculated by reading 32 bits of memory at a time. The calculated value is then
compared with a pre-calculated value stored in flash.


CPM Serial Tests Menu

This menu presents the Operator with options for serial port one, serial port two, and return.
!
WARNING Do not use the CPM Serial tests. A defect prevents the CPM serial tests from
functioning correctly in the 2.0 diagnostic release.
Serial Port 1 Menu

This menu presents the Operator with options for the external echo test and to return.
External Echo Test

The Operator is prompted to enter the seed for a pseudo-random generated data sequence and the number of bytes to
send for all Operator roles other than Field Service Engineer.
NOTES • Data is sent through Serial Port 1 of the CPM, which then leads to the baseboard. Even though this test is
under the CPM category, a faulty baseboard can cause this test to fail since the serial port connector is on the
baseboard.
• A loop back connector is needed on this port to successfully run the External Echo test. The loop back
connector simply has the Read and Write signals tied together. The loop back connector for the DMC is a
female DB-9 with pins 2 and 3 tied together and pin 6 tied to ground. The other Gantry Controller boards use
a male phone connector with the write line tied to the read line.
Serial Port 2 Menu

This menu presents the Operator with options for the external echo test and to return.
External Echo Test

The Operator is prompted to enter the seed for a pseudo-random generated data sequence and the number of bytes to
send for all Operator roles other than Field Service Engineer.
Important: Data is sent through Serial Port 2 of the CPM, which then leads to the baseboard. Even though this test is
under the CPM category, a faulty baseboard can cause this test to fail since the serial port connector is on
the baseboard.
Important: Normally, the serial ports would be tested via the CAN port. If the serial ports are to be tested via serial
access, then the diagnostic Framework is using one of the serial ports. In this case, the Server is
designed to act as a loopback connector and to echo the data back to the CPM Server.
Important: A loop back connector is needed on this port to successfully run the External Echo test. Because this port
goes over the control link for the rotating boards, the female phone connector socket is located on the
GHost. A cable may need to be temporarily replaced with the loop back connector. The loop back male
phone connector simply has the Read and Write signals tied together.
CAN Menu
This menu presents the Operator with options for the echo test and to return.
Echo Test
The Operator is prompted for a destination on the CAN bus, the seed for a pseudo-random generated data sequence,
and the number of bytes to send for all Operator roles other than Field Service Engineer.
Important: The destination Controller board must be in Utility mode for the Echo test to work.
NVRAM Menu
This menu presents the Operator with options for the destructive test and to return.
Destructive Menu
This menu presents the Operator with the following options: memory test, calculate and write CRC utility, calculate and
read CRC utility, and return.
Memory Test: The Operator is prompted to enter the start address and number of locations to test. The test verifies the
ability of all locations to hold a zero and a one, transition to one from zero, transition from one to zero, and ability to
address memory in the ascending and descending directions.
Important: Any previous content will not be in the NVRAM after this test.
Calculate and write CRC Utility: The CRC of the NVRAM is calculated and written to the last location of NVRAM. This
utility can be used for storing a CRC prior to a power cycle test of the NVRAM.
Calculate and read CRC Utility: The CRC of the NVRAM is calculated and compared to the CRC found in the last
location of NVRAM. This utility can be used to verify the CRC after a power cycle.
Utilities
"Wide-open" utilities exist which will allow the Operator to perform various tasks. In general, wide-open means the
Operator must know the addresses they want to access. These types of tests assume the Operator knows what they
are doing. The wide-open utilities are not available when the Operator is Field Service Engineer.
Application Flash Burner Utility

The Operator can program the external flash found on the CPM board with baseboard specific application code. The file
to be transferred to flash must exist on the PC where the Interface is running. The Operator can change the name of the
file to be burned. The default file is the binary file of the baseboard the diagnostics are running on. For example, if
diagnostics are being operated on the GHost then the default file is GhostBd.bin. The directory name where all of the
baseboard application binaries are located is C:\usr\diamond.root\GantryCPM
The Application Flash Burner utility will identify and display the type of external flash located on the CPM. The two types
are AMD and Intel. During programming an event message will display the flash type and the appropriate flash
programming algorithm will be used.
The file to be transferred to flash must exist on the PC where the Interface is running. The Operator can change the
name of the file to be burned. The default file is the binary file of the baseboard the diagnostics are running on. For
example, if diagnostics are being operated on the GHost then the default file is GhostBd.bin. The directory name where
all of the baseboard application binaries are located is C:\usr\diamond.root\GantryCPM.
Blocks of data are read from the file and burned into external flash until the end of the file is reached.
NOTES • The application code being burned must match the baseboard.
• If the boot flash is at 0.3 or above please disregard the rest of this note. The procedure to program external
flash requires K2000 software to be loaded and operational if version 0.2 boot flash (internal flash of MPC555)
and version 0.3 Interface/Server are running. If not, the application flash burner (which is located in the boot
flash) will burn external flash over and over without stopping. Resetting the CPM will end the cycle. There is a
compatibility problem between O-level(K2000 off, version 0.2 bootflash, and version 0.3 Interface/Server.
Version 0.3(and above) boot flash does not have this problem.
Boot Flash Burner Utility

The Operator can program the internal flash of the MPC555, found on the CPM board, with diagnostic code.
The file to be transferred to flash must exist on the PC where the Interface is running. The Operator can enter the
location and name of the file to burn. The default file name is
C:\usr\diamond.root\Diag\CPMIntFlash\CPMIntFlashImage.bin
Blocks of data are read from the file and burned into internal flash until the end of the file is reached.
Important: The Boot Flash Burner is ONLY appears in the menu if the Boot Flash has been downloaded to external
RAM and is executing.
Downloader Utility (Boot/MDP/TDP only)

The Operator can download an executable, which will be run from the CPM external RAM. The file to be transferred to
RAM must exist on the PC where the Interface is running. The Operator is prompted for the location and name of the
file to load.
The file is read and written to high external CPM RAM. Next, high external CPM RAM is copied to low external CPM
RAM. Then, a jump to the start point occurs and the downloaded code begins.
One intention is to use down loading of diagnostics after internal CPM flash is full. Another intention is for special
versions of the application code that are under evaluation by the developer prior to actually committing the code to
external flash. The last intention is that special diagnostic applications can be downloaded to specific boards that work
in conjunction with the actual application on the other boards.
The Diagnostic binary file can be downloaded and executed from external RAM. At this point, the internal flash of the
CPM can be programmed.
NOTES • The Downloader is available to proprietary and 0-level Operators.
• Due to memory limitations only the Boot, MDP, and TDP binaries can be downloaded and executed. The
other binaries are to large and cannot be completely downloaded into CPM external RAM.
• After downloading the Boot Flash, this item will not appear in the menu list, and will be replaced by the Boot
Flash Burner Utility.
NVRAM Error Log Reader Utility

Diagnostic errors are written to the NVRAM error logger and can be read via this utility.
This NVRAM Error Log Reader is a proprietary utility.
The Diagnostic section of the NVRAM is initialized after a power-up, CPM push button reset, or Reboot utility. In
previous releases the only way to initialize NVRAM was to cycle power.
Board Debug Utility (Available for Zone Specialist Only)

The following operations can be performed:
Peek (reading from a memory or register location),
Poke (writing to a memory or register location),
Load (execute a script file),
Display (view memory or register locations),
Fill (write data to memory or register locations), and
Find (find data in memory or register locations)
The start address can be entered.

The data to be Poked, Filled, or Found can be entered.
The locations to be Filled, Displayed, or used in Finding can be entered.
The access size, 1 byte, 2 bytes, or 4 bytes can be entered.
Bus Utility (Available for Zone Specialist Only)

The Operator can perform a walking one's or zero's test to a specified memory or register location.
The Operator is prompted for an address.
The Operator can select 8, 16, or 32 bit accesses.
RAM Utility (Available for Zone Specialist Only)

The Operator is prompted to enter the start address and number of locations to test. There are three tests which are
based upon an 8, 16, and 32 bit access size. The test verifies the ability of all locations to hold a zero and a one,
transition to one from zero, transition from one to zero, and ability to address memory in the ascending and descending
directions. Testing of certain memories can clobber the executing diagnostic framework.
Upload as ASCII Utility (Available for Zone Specialist Only)

The Operator can upload memory or consecutive register locations as ASCII values to a file on the PC. The Operator
is prompted for the starting address, data size, number of locations to upload, and file name.
Upload as Binary Utility (Available for Zone Specialist Only)

The Operator can upload memory or consecutive register locations as binary values to a file on the PC. The Operator
can enter the access size, the address, the byte quantity, and the file name.
1. Connect to the board of interest.
2. Select Toolbox and Submit.
3. Select Utilities and Submit.
4. Select Upload as binary and Submit.
5. Select access size of 8 bits (default).
6. Select start address of 1400000.
7. Select byte quantity of 8000.
8. Select appropriate file name.
9. Select Execute.
10. Select 1 loop if prompted.
Download as Binary Utility (Available for Zone Specialist Only)

The Operator can download binary values from a file on the PC to memory or consecutive register locations. The
Operator can enter the access size, the address, the byte quantity, and the file name.
1. Connect to the board of interest.
2. Select Toolbox and Submit.
3. Select Utilities and Submit.
4. Select Download as binary and Submit.
5. Select access size of 8 bits (default).
6. Select start address of 1400000.
7. Select appropriate file name.
8. Select Execute.
9. Select 1 loop if prompted (FSE Operator role does not prompt for loops).
Location Monitor Utility (Available for Zone Specialist Only)

The Operator can view a single memory or register location. The Operator can enter the access size, the byte quantity,
and number of loops to view the location.
State Menu Utility (Available for Zone Specialist Only)

The Operator can easily view registers as a single 8, 16, or 32 bit value or as individually defined bits. Access
information is put into files allowing the Operator to view different registers quickly and easily.
The State Menu utility identifies which of the 10 Gantry Controller boards it is running on. Knowing this, the utility uses a
default filename. All the default files are kept in the directory C:\usr\diamond.root\Diag\States. The filenames for the
boards are as follows:
RHost RHost.txt
GHost GHost.txt
DMC DMC.txt
Galaxy Galaxy.txt
Main Drive MP.txt
Tilt Tilt.txt
164 GHost GHost164.txt
164 Main Drive MP164.txt
164 RHost RHost164.txt
164 Tilt Tilt164.txt
The default file is called the scenario file. The opening menu to the utility presents the scenario file as an option to the
Operator. The Operator can use this file or select a different file. The file that is selected is opened and displayed as
menu options. These options are the names of “other” files called register files. The scenario file can contain a minimum
of 1 or a maximum of 16 register files. The register files must exist in the same directory as the scenario file. These
register files define necessary parameters for creating menus of hardware registers that can be written to and read
from. The intent of this section is to provide some rules that apply to the format of the register files. The rules are:
• Blank lines are permitted.
• A comment on an entire line must have a semicolon(:) in the first column.
• All lines with parameters on them must be terminated with a semicolon(:) with comments to the right side of the
semicolon.
• Ten parameters are used to describing each register that appears on a menu.
• The first parameter is ASCII text describing the register name. The ASCII text is 32 characters max.
• The second parameter is the 32-bit hex address without leading 0x.
• The third parameter is the accessibility.
WR = Write/Read
WO = Write Only
RO = Read Only
NO = None.
• The fourth parameter is the bit access size in hex with no leading 0x.
8 = 8 bits
10 = 16 bits
20 = 32 bits.
• The fifth parameter is the AND mask for reading. All registers read are logically AND'ed with this value to strip off
undefined bits.
• The sixth parameter is the OR mask for writing. All registers written are logically OR'ed with this value as a
convenience.
• The seventh parameter is a flag indicating whether the utility is to perform an initialization write to the register. The
values are INIT_ENABLED and INIT_DISABLED.
• The eight parameter is the initialization value. It is the responsibility of the person configuring the file to only enable
initialization on registers that the hardware allows a write to.
• The ninth parameter is a flag that indicates whether the tenth parameter is valid or not. The ninth parameter values
are BITFILE_ENABLED and BITFILE_DISABLED.
• The tenth parameter is an optional bit filename that defines the bits of a register. This file contains text describing
each bit's function and that bit's accessibility using the same flags the third parameter uses. Undefined bits are
normally given an access of NO so that they do not appear on the menu. If a register has 8 bits in it, the bit file must
have 8 sets of text and access. If a register has 16 bits in it, the bit file must have 16 sets of text and access. If a
register has 32 bits in it, the bit file must have 32 sets of text and access.
The register file can contain a minimum of 1 and a maximum of 16 register set parameters. The text describing the
register and the text describing a bit is limited to 32 characters. The bit file contents from top to bottom correlates to
most to least significant bit.
If the ninth parameter is BITFILE_ENABLED the tenth parameter or bit file is used to display the register value as
individual bits. Two parameters are used to define each bit. There are a few rules the Operator must follow when
creating a bit file. The rules are:
• Blank lines are permitted.

• A comment on an entire line must have a semicolon(:) in the first column.
• All lines with parameters on them must be terminated with a semicolon(:) with comments to the right side of the
semicolon.
• The first parameter is ASCII text describing the register name. The ASCII text is 32 characters max.
• The second parameter is the accessibility.
WR = Write/Read
WO = Write Only
RO = Read Only
NO = None.
State Menu Example

The following text demonstrates how to use the scenario, register, and bit files. The example is for a fictitious television
board. The scenario file is called TVBoard.txt. This results in the following opening menu where the leading O
represents the GUI radio button:
O File: ...\TVBoard.txt
O Execute
O Return
Submit
Figure 20: State Menu 1

Clicking the File radio button and then the Submit button allows a different scenario file to be selected.
Clicking the Execute radio button and the Submit button uses the current scenario file.
The content of the scenario TVBoard.txt file is:
TVVideo.txt
TVAudio.txt
TVTest.txt
The next menu to appear after the submission of the Execute would be:
O TVVideo.txt
O TVAudio.txt
O TVTest.txt
O Return
Submit

The following is an example of the content of the TVVideo.txt file:
Horizontal control: Radio button text (ASCII, 32 characters max)
00100000: 32-bit address (hex without leading 0x)
RO: Accessibility (RO, WO, WR, NO)
08: Access size in bits (08, 10, 20)(hex without leading 0x)
ff: 08, 16, or 32-bit AND mask for reading (hex without leading 0x)
00: 08, 16, or 32-bit OR mask for writing (hex without leading 0x)
INIT_ENABLED: Flag for use of initial write value (INIT_ENABLED/INIT_DISABLED)
00: 08, 16, or 32-bit initial write value (hex without leading 0x)
BITFILE_ENABLED: Flag for use of bitwise definition file (BITFILE_ENABLED/BITFILE_DISABLED)
HorCntrl.txt: Bitwise definition file
Vertical control: Radio button text (ASCII, 32 characters max)

WO: Accessibility (RO, WO, WR, NO)
ffff: 08, 16, or 32-bit AND mask for reading (hex without leading 0x)
VerCntrl.txt: Bitwise definition file
Volume: Radio button text (ASCII, 32 characters max)

WR: Accessibility (RO, WO, WR, NO)
ffffffff: 08, 16, or 32-bit AND mask for reading (hex without leading 0x)
Volume.txt: Bitwise definition file
Tint: Radio button text (ASCII, 32 characters max)

0010000c: 32-bit address (hex without leading 0x)
NO: Accessibility (RO, WO, WR, NO)
0000ffff: 08, 16, or 32-bit AND mask for reading (hex without leading 0x)
0000c000: 08, 16, or 32-bit OR mask for writing (hex without leading 0x)
BITFILE_DISABLED: Flag for use of bitwise definition file (BITFILE_ENABLED/BITFILE_DISABLED)
tbd.txt: Bitwise definition file
The TVAudio.txt and TVTest.txt files are not shown here.
Selecting the TVVideo.txt radio button from State Menu 2 and submitting it would result in the following menu:
O Horizontal control(RO): 00
O Vertical control(WO): 0000
O Volume(WR): 00000000
O Tint(NO)
O Refresh
O Return
Submit
The display of the value following the semicolon (:) indicates the access size of the register. Because the Vertical
control register is Write Only, the value shown is the last value written to the register. Every time this menu is displayed,
any readable register is read and it's current value displayed. Registers with an accessibility of NO are not read. If a
register is INIT_ENABLED, it will be written to without regard to the defined accessibility of the register. One of the
reasons for the NO accessibility of a register is because reading some hardware at certain times can disrupt processes.
The accessibility of a register can always be redefined at run time. For example, selecting the Tint radio button and
submitting it, will bring up a menu of all the possible accessibility states the register can be changed to. If the Horizontal
control button is selected and submitted, it's associated bit file will be accessed because it is enabled.
The HorCntrl.txt bit file is as follows:

Bit #7: Radio button text (ASCII, 32 characters max)
NO: Accessibility (RO, WO, RW, NO)
Bit #3 Radio button text (ASCII, 32 characters max)
Sequence enable*: Radio button text (ASCII, 32 characters max)

RO: Accessibility (RO, WO, RW, NO)
Horizontal enable*:Radio button text (ASCII, 32 characters max)
WR: Accessibility (RO, WO, RW, NO)
Board reset*: Radio button text (ASCII, 32 characters max)
WO: Accessibility (RO, WO, RW, NO)
This file will result in the following menu:
Sequence enable*(RO): 1
O Horizontal enable*(WR): 0
O Board reset*(WO): 1
O Operation: Write
O Execute
O Return
Submit
The use of the * is a convention to indicate that the bit is active low. The Sequence enable bit does not have a radio
button next to it because it cannot be written to. Likewise, the Board reset bit reflects the last value written. WR
accessible registers and bits reflect the last value read. Had this register been 16 bits long, there would have had to be
8 more bits defined. A 32-bit register would have had 24 more bits.
Input/Output Utility (Available for Zone Specialist Only)

The Operator can exercise hardware IO signals. A few of the characteristics of the Input/Output Utility are the following.
• The Input/Output utility will exercise hardware output IO signals and verify hardware input IO signals
• External loopback connectors or external circuitry are required to “tie back” the hardware output IO signals to the
hardware IO input signals.
• Access information is put into files that allow the Operator to quickly and easily change access information.
• Access information is put into an Output and Input file.
• The Operator can easily change the type of pattern to be used to exercise the hardware IO signals.
JTAG Utility (Available for Zone Specialist Only)
The Operator can perform any number of operations on baseboard CPLDs. The operations are: program, verify,
blankcheck, and erase. Each operation is comprised of commands (XSVF commands to be specific) which are
executed on each CPLD. The commands are found in an .xsvf file. Each .xsvf file can contain commands to program
CPLD #1, verify CPLD #2, program CPLD #2, verify CPLD #2, etc. There is no file size limit to the number of commands
to be executed.
The baseboard is not configured to support JTAG operations.

NOTE The JTAG Utility is NOT enabled on baseboards that do not have the necessary hardware to program baseboard
devices.
The opening menu for all boards, except the DMC16, will present the following options to the Operator:
• XSVF file:…\JTAG.xsvf
• Execute
• Return
The default file is JTAG.xsvf and resides in the C:\usr\diamond.root\Diag\JTAG directory. The default file, JTAG.xsvf,
executes 3 commands which do NOT exercise the JTAG port. The Operator must selct the appropriate .xsvf file. If the
execution of the commands fail an error message will be displayed. Also, the expected/differences are dumped into a
file called JTAG.txt in the C:\usr\diamond.root\Diag\Record directory. The process to create the .xsvf file can be found in
the Create XSVF document.
For the DMC16 the user will be presented with the following options:
• XSVF file:…\JTAG.xsvf
• DMC16 chain: enabled
• RCOM chain: disabled
• CDMP chain: disabled
• Execute
• Return
The Operator can enable or disable the ability to program devices on the DMC16, RCOM, GMP or CDMP. The
preferred method is enable one chain at a time.
Reboot
The Controller board can be rebooted into Utility mode. Power-up diagnostics are performed as long as the binary in
internal flash is running. When the binary is running from RAM, the power-on tests are skipped. This is a defect for the
release 1.5 binary intended to be fixed in the future.
Important: The Operator must wait for the power-up diagnostic complete AND the for the CPM to boot into utility
mode.
Connect To Baseboards
Connect To Baseboards
GHost Baseboard
On the Options menu, select Connect to Controller > GHost > Toolbox >
GHost Baseboard.
GCP / CTB Functions

The Gantry Control Panel (GCP) & CT Control Box (CTB) Functions Diagnostic allow the operator to reset,
communicate with and test the GCP & CTB and also to reprogram the internal firmware that runs the GCP & CTB.
Gantry Control Panel / CT Control Box Functions Menu

Command Widow
CT Control Box
Execute
Return
GHost Baseboard
Command Action Sub Menu
Command Window opens a command window the operator can type ASCII commands to the GCP & CTB into. The
responses to the commands can be observed on the GCP & CTB hardware and serial command responses can be
observed in the Event Window. The Command Window is terminated by using the commands “exit” or “quit”.
Button Monitor requests a "loop count" and then allows the operator to monitor the serial messages transmitted by the
GCP & CTB in response to pushing and releasing the push button switches on the GCP & CTB. These message are
displayed in the Event Window, and each line received is counted as one (1) (hexadecimal) "loop count" value. See the
GCP & CTB Command Synopsis and the Switch Table I that follows to interpret the messages. (When the GCP & CTB
are in "debug mode", in response to the serial command "DB", the messages display the device name, GCP or CTB,
and switch name, besides the hexadecimal message usually sent to the Ghost Application software).
Hardware Reset allows the operator to reset the GCP & CTB through the Hardware Control lines from the Ghost to the
GCP & CTB like the Ghost Application software does. It can also be used to re-boot the GCP & CTB after doing In-
System-Programming, initiated with the GCP & CTB "ISP" command.
In-System-Program is used to replace the firmware in the GCP & CTB that control it's actions. This had been done
with a special adapter connecting the GCP & CTB to a lap-top PC running WinISP or FlashMagic. The In-System-
Program function automatically reads the current release of the GCP & CTB firmware file, which was included in
Diagnostic Release 2.0. The current GCP & CTB file is version U1.03 here:
C:\usr\diamond.root\Diag\GCP_CTB\gcp_ctb_U103.hex
The In-System-Program reads the file, scans it for the highest address, sets up the correct number of blocks to erase,
the oscillator frequency and the autobaud rate and should only require an Execute step. These parameters can be
changed, including the file, if necessary.
Before starting In-System-Programming the operator should command the GCP & CTB to enter ISP Mode with the
GCP & CTB "ISP" command, using the Command Window diagnostic function.
In-System-Program also includes a Hardware ISP Help page. In the event that the In-System-Programming (ISP) fails
for some reason, the GCP & CTB firmware will have been erased and/or partially reprogrammed, resulting in that
device becoming inoperable. It will be necessary to open the device enclosure and set the internal Jumpers (included
with the hardware) to the ISP mode. Using Hardware Reset after setting the ISP Jumpers will place the device back into
ISP Mode and the ISP can then be retried. The Hardware ISP Help page tells the operator how to set the jumpers, in
case this becomes necessary.
Patch J15 Spare is for future development.
Serial Statistics lists some statistics for the serial communications between the Ghost and the GCP & CTB, including
Receiver Buffer Overflows, UART Overrun Errors and Parity & Framing Errors.
GHost Baseboard
CT Control Submenu
* CT Control Box
* Gantry Panel Front
* Gantry Panel Rear
The Command Target Submenu allows the operator to change the target of the Command Action to either the CT
Control Box (CTB), the Gantry Control Panel (GCP) or both the CTB & GCP. For other than Hardware reset, it can be
confusing to try and sort out the responses from each device in the Event Window. It is suggested at this time that only
one device be used as the Command Target at a time.
GCP & CTB Command Synopsis

The GCP & CTB question mark "?" command lists the supported commands:
?
R - Reset
B - Button Switch Check
L - LED Lamp Set
H - Horizontal Display Set
V - Vertical Display Set
T - Tilt Display Set
M - Milliamps Display Set
K - Kilovolts Display Set
S - Seconds Display Set
C - Clock Set/Display Toggle

D - Display Stored Parameters
F - Flash Seven Segment
DB - Debug Mode Toggle
OB - Option, Bounce Logic
GHost Baseboard
OC - Option, Combine L+R

OD - Option, Duty Cycle (0-10)
OP - Program Flash Data Save
ISP - In System Programming
SGL - Run in Stargate "L" Mode

SG164 - Run in Stargate 164 Mode
SGP - Run in Stargate PET Mode
Messages between the Ghost and the GCP & CTB

All messages begin with a command byte, optional data bytes, a 2b CRC represented by 4 Hex digits or a 1b checksum
(Presently revising message scheme) and terminated by a Line-Feed, "C" new-line, ASCII 0x0A.
For all data display messages, if the digit is an ASCII space character '.', 0x20, or an underline '_', 0x5F, that display
digit is blanked, or turned off. Additionally, if the data field doesn't exist, all the display digits will be blanked. Also if a
period or decimal point, '.', 0x2E is included in the data string, the decimal point for the preceding digit will be turned on.
R - Reset
Resets the Control Panel software & variables, ends with the ten (10) second lamp test.
B - Button Switch Check

Requests a Button state sample from the Control Panels. The GCP & CTB also send an unsolicited Button message
any time the switches change state, excepting single switch changes that require an enabling switch.
Bxxxxc<nl>
Where “B” is the Button switch command identifier, “x” are Hexadecimal digits representing the 16 switch bits, “c” is the
1b ASCII converted checksum.
GHost Baseboard
L - LED Lamp Set

Sets the state of all the LED's on the Control Panel.
Lxxxxxxxxxxxxxxxxc<nl>
Where "L" is the LED command identifier and "x" is the LED state to set. Represented by ASCII characters:
0 - Set LED Off
1 - Set LED On
S - Set LED Flashing Slow
F - set LED Flashing Fast
H - Horizontal Display Set

Hoxxxxc<nl>
V - Vertical Display Set

Vox‘xxc<nl>
T - Tilt Display Set

Toxxxc<nl>
For each of these, the leading digit, "o" is an Overflow digit which can display a minus sign (-), plus sign (+) the digit one
(1) and a decimal point. The remaining 4 "x" Horizontal and 3 Vertical & Tilt digits can display the numbers 0-9, A-F, a
decimal point, and various other odd values.
M - Milliamps Display Set

Mxxxc<nl>
K - Kilovolts Display Set

Kxxxc<nl>
GHost Baseboard
S - Seconds Display Set

Sxxxc<nl>
For each of these the 3 digits can display a minus sign, the numbers 0-9 & A-F, a decimal point, and various other odd
values
C - Clock Set/Display Toggle

Sets & toggles counter derived clock display on / off.
C hh:mm:ss Sets the time of day.
C Toggles scrolling clock display.
D - Display Stored Parameters

DB> d
DB: X:00F2 1=d
LED: 00000000
SDS: 00000000
MA : FF FF FF Horz: F6 82 83 84 85 (+1.|2.3.4.5.)
KV : FF FF FF Vert: F6 82 83 84 (+1.|2.3.4.)
S : FF FF FF Tilt: F6 82 83 84 (+1.|2.3.4.)
RXO: 00 (RX Overruns)
T0D: 3 3 3 3 3 3 3 3
L15: 0 0 0 0 0 0 0 0
L07: 0 0 0 0 0 0 0 0
R15: 0 0 0 0 0 0 0 0
R07: 0 0 0 0 0 0 0 0
Stargate "L" Mode
DB>
The LED line lists the 32 bits representing 2 bits for each LED. Each LED's 2 bits indicate if it is off (00), on (01), flashing
slow (10), or flashing fast (11).
The SDS line lists the 32 bits representing the 16 switches on the CTB or the GCP Left, and the GCP Right, depending
which device you are operating.
The MA/Horz, KV/Vert and S/Tilt list internal representations of the seven segment displays for those items.
GHost Baseboard
The RXO line lists the number of times the Controller software's Receive (RX) Buffers have been Overrun. Normally this
should be zero (0). (If the RX buffers do get overrun by rapid commands from the Ghost, the Horizontal display is also
set briefly to “+boXX”, representing Buffer Overrun, and the overrun count in 2 Hexadecimal digits.)
The T0D line lists the Duty Cycle selected from the Timer 0 Driver for each column of the seven segment displays. The
large displays on the GCP have a greater variation in the brightness available, than the smaller displays on the CTB.
The displays are multiplexed by the controller software in columns, with a duty cycle consisting of 1 millisecond (ms) per
column, and 8ms for the eight (8) columns, or a refresh rate of 125 cycles/second (Hz). Each columns' duty cycle can
be set from zero (0), full off, to ten (10), full on; or any value of 10% in between. These duty cycles are what is listed in
the T0D line for column zero (0) to column seven (7).
The L15 - L07 and R15 - R07 lines list how many seconds the switches on the CTB or GCP Left and GCP Right have
been depressed without being released. If a switch remains depressed for two (2) minutes, or 120 seconds, an error
message is sent to the Ghost in an attempt to flag stuck switches.
If the GCP or CTB does not receive a command from the Ghost in two (2) minutes, or 120 seconds, the Horizontal and
Vertical displays are set to "dISC" & "Err", representing a Disconnect Error. (Reference Stargate L Software Defect
number STGaa00000433.)
F - Flash Seven Segment

Toggle Seven Segment Display Flashing 1/2 sec on, 1/2 sec off, once per second.
P - Program Flash Data Save

Saves the current setting of the Eight (8) Seven Segment Display Columns Duty Cycle into unused flash memory.
These values are retrieved after a power-on or reset and used for the Eight (8) Seven Segment Columns Duty Cycle.
See OD - Option Duty Cycle.
DB - Debug Mode Toggle

List switches depressed, released and tracks the depressed switch with the LED's. Switches without an LED, like the
Enable switches, use both action switches. Also ignores incorrect CRCs or Checksums.
OB - Option, Bounce Logic

Elaborate Switch Debouncing logic is built into the GCP & CTB, but wasn't required due to the switches acting very
cleanly. For details see:
X:\stargate_doc\gantry\state2\software\SRS\GCP-CTB
GCP-CTBSrsSdd.doc & sdd-draft.doc
GHost Baseboard
OC - Option, Combine L+R

Combines the Gantry Control Panel Left & Right side switches by logically OR'ing them together. This would allow, for
example Left Side Tilt Enable & Right Side Tilt Forward/Backward to operate the Tilt.
OD - Option, Duty Cycle (0-10)

Sets the Duty Cycle for each of the Eight (8) Seven Segment Display Columns. They can be changed from zero (0), full
off, to ten (10), full on, or any increment of 10% in between. (See "P - Program Flash Data Save" to save this set of duty
cycles)
OD x x x x x x x x
Sets the Duty Cycle for Columns 0 though 7. (An actual "x" instead of a digit from 0-9 leaves that current setting as is).
ISP - In System Programming

Enters "In System Programming", ISP, mode. Use Philips "winisp.exe" to erase and reprogram the flash memory.
Can also enter ISP mode by holding all three (3) Tilt Enable, Forward and Backward depressed during a reset cycle.
ISP Sets the horizontal Display to "ISP" for five (5) seconds, blanks all the displays & enters ISP mode, waiting for a
serial connection from the Philips "winisp.exe" program.
GHost Baseboard
Button Switch & LED to Message Mapping

Messages representing the Switches or LED's are sent with the MSD first and the LSD last.
Switch Gantry Control Panel CT Control Box
15 Horizontal Enable
14 Mark Abs/Ref Toggle
13 Laser On/Off Toggle Auto Enable
12 Unload Enable
11 Unload Pause
10 Horizontal Out Horizontal Out
9 Horizontal In Horizontal In
8 Vertical & Horizontal Enable Vertical Enable
7 Vertical Down Vertical Down
6 Vertical Up Vertical Up
5 Index Enable
4 Index Out Auto
3 Index In Manual
2 Tilt Enable Tilt Enable
1 Tilt Backward Tilt Backward
0 Tilt Forward Tilt Forward
LED's Gantry Control Panel CT Control Box

15 Status LED 3 Status LED 3
12 Mark Absolute
11 Mark Reference
10 Laser Off Auto Enable
9 Laser On
8 Unload Pause
7 Horizontal Out Horizontal Out
GHost Baseboard
LED's Gantry Control Panel CT Control Box

6 Horizontal In Horizontal In
5 Vertical Down Vertical Down
4 Vertical Up Vertical Up
3 Index Out Auto
2 Index In Manual
1 Tilt Backward Tilt Backward
0 Tilt Forward Tilt Forward
Serial
Not functional at this time.
Seven Segment Test

The Operator is prompted to select one of eight seven-segment tests. The selections are:
• Display 0 count test
• Display 0 on/off test
• Display 0 walking 1 test
• Display 1 count test
• Display 1 on/off test
Display 0 & 1 are the two seven segment displays. The count tests will sequentially count through all hex values. The
walking 1 test will turn on all segments and sequentially turn off & on each segment. The walking 0 test will turn off all
segments and sequentially turn on & of each segment. The registers are verified the correct value was written but the
Operator must examine the displays.
GHost Baseboard
E-Stop Loop Test

E-Stop functionality was changed from questions requiring a 0 (Open) or 1 (Close) response to the radio-button
method.
Selecting E-Stop from the Baseboard Menu

In the Options Window:
Open E-Stop
Close E-Stop
Return
In the User Feedback Window:
E-Stop
E-Stop = 0 Opened (before command)
E-Stop = 1 Closed (after command)
This Utility is implemented on the GHost, DMC, RHost & Couch Control Boards. The same E-Stop Loop Control Utility
is used by all of the boards, as it is controlled by the Modular I/O System 16-bit Parallel Port I/O Submodule, MPIOSM,
of the MPC555.
DMC Baseboard
DMC Baseboard
On the Options menu, select Connect to Controller > DMC > Toolbox > DMC Baseboard.
Set Motor Speed

The Set Motor Speed utility allows the operator to set motor speeds for the collimators. The value the operator inputs
represents a percentage value of the motor’s maximum potential speed. For example, a value of 5 would mean 5% of
the motor’s maximum speed. The value input by the operator, typed as a simple numeric string (e.g.: 23, not 0x23), is
understood to be a Hex value.
The first value input by the operator will set the motor speed for both the P-Plane and UHR collimators. The valid range
of values is 0x5 to 0x32 (i.e.: 5 – 50% decimal).
The second value input will set the motor speed for the A-Plane slice width selector and A-Plane Z-dimension collimator
motors. The valid range of values is 0x5 to 0x55 (i.e.: 5 – 85% decimal).
DMC Baseboard
Set UHR Collimator

The Set UHR Collimator test allows the operator to select either 0 to move the collimator out or 1 to move the collimator
in.
If the operator selects 0, the collimator moves out until the hardware detects an interrupt that indicates it is fully out, at
which point a message appears indicating success.
If it does not go fully out, an error message appears on the screen.
If the user selects 1, the collimator moves in until the hardware detects an interrupt that indicates it is fully in, at which
point a message appears indicating success.
If it does not go fully in, an error message appears on the screen.
Set P-Plane Collimator

The Set P-Plane Collimator test allows the operator to select either 0 to open the collimator or 1 to close the collimator.
If the user selects 0, the collimator opens until the hardware detects an interrupt that indicates it is fully open, at which
If it does not fully open, an error message appears on the screen.
If the user selects 1, the collimator closes until the hardware detects an interrupt that indicates it is fully closed, at which
If it does not fully close, an error message appears on the screen.
DMC Baseboard
Move Collimators Using Switches

The Move Collimator Using Switches utility enables the switches/push buttons on the control panel of the DMC board.
The switches allow the movement of each collimator in each direction. The collimators will move at their default speeds,
if the operator has not set a speed.
The operator will first input a timeout value to cause the buttons to operate for the desired testing period.
Important: The timing is done with loops and is approximate.
Via…
• Can Bus Connection: An input value of 1 is approximately 30-40 seconds of operation. (E.g.: An input of 10 will run
for about 5 minutes.)
• Serial Port Connection: An input value of 1 is approximately 3-5 seconds of operation. (E.g.: An input of 10 will run
for about 30 seconds.)
The buttons are:
1. Open P-Plane
2. Close P-Plane
3. Move UHR In
4. Move UHR Out
5. Open A-Plane (slice width selector)
6. Close A-Plane
7. Move A-Plane In (Z dimension)
8. Move A-Plane Out
9. Move A-Plane Filter In (if filter is present)
10. Move A-Plane Filter Out (if filter is present)
Read Temperatures
The Read Temperatures utility will read each of the 3 temperature sensors. The test has a time-out selector value. Each
input of 1 is approximately 30 seconds. (E.g.: A selection of 10 is approximately 5 minutes.)
Important: The 4th sensor value, which is reported on the screen, is not connected to any sensor, and the value is to
be disregarded.
DMC Baseboard
Set Scan Parameters

The Set Scan Parameters utility allows the operator to set various parameters to simulate a scan. The selected settings
can be read with the Print Scan Parameters utility, and they are executed by the MxScan utility. The selectable
parameters and their ranges follow:
1. Integration Period (in uSec):
Range: 0x200..0x80000
2. Number of Frames:
Range: 1..0xFFFF
3. Offset Freq.:
Range: 0=2.5KHz
1=5KHz
2=10KHz
3=20KHz
4=0KHz
5=Other
4. Gain:
Range: 1..16 (i.e.: 0x10)
5. Use Different Parameters for ref. modules?
Range: 0(No)..1(Yes)
if (yes)
{
Ref. Offset Freq.:
Range: 0=2.5KHz
1=5KHz
2=10KHz
3=20KHz
4=0KHz
5=Other
DMC Baseboard
Ref. Gain:
Range: 0x1 .. 0x10
}
6. Do Offset Subtraction?
7. Do Delta Data Correction?
8. Enable Asic Offset Correction?
if (yes)
{
Trigger Offset Correction Now?
Range: (0=No 1=Yes)
}
9. Take Offset before each scan?
10. Program scan according to parameters?
Print Scan Parameters

The Print Scan Parameters utility displays the default scan parameters if no selections have been made with the Set
Scan Parameter utility. Otherwise the parameters most recently selected with the Set Scan Parameters utility are
displayed.
MxScan
The MxScan utility performs a simulated scan based on the settings set with the Set Scan Parameters Utility.
DMC Baseboard
Reset Base Board

The Reset Base Board utility resets the DMC baseboard. The CPM is not reset. It is possible to loop on this utility, if so
desired.
Start DMC Comm. Test

Not used.
Stop DMC Comm. Test

Not used
E-Stop Loop
method. Selecting E-Stop from the Baseboard Menu:

Open E-Stop
Close E-Stop
Return

E-Stop
DMC Baseboard
(DMC Power On)

A new Power On Utility to check the load status and start a reload of the DMC FPGA if necessary can also be run by the
Operator. Apparently the DMC FPGA sometimes fails to load properly when the board is Powered On.
When the Utility runs at Power On or by the Operator, the load status of the FPGA is checked for up to one (1) second
using bit 6, 0x40, of the Modular I/O System 16-bit Parallel Port I/O Submodule, MPIOSM, of the MPC555. If the load
completes ok, the function is complete. Otherwise the load is restarted by strobing bit 0, 0x01, of the MPIOSM low and
the load status is checked for up to one (1) more second. If the load completes ok, the function is complete. If the load
does not complete ok, a Diagnostic Error is logged to NVRAM & the board remains in Diagnostic Mode.
Main Drive Baseboard

On the Options menu, select Connect to Controller > MDP > Toolbox > Gantry Motion Baseboard.
DMC Baseboard
Serial TI16544 Echo

The Serial TI16544 Echo test will echo a single byte. The path is via an external loopback connector or internally “to &
from” the TI16544 serial component. The Operator is prompted to select 1 of 4 serial ports
Resolver Reference Delay

The Operator can view and set the Resolver Reference Delay register providing a square wave input has been
connected to the P2 connector. The Resolver Reference Delay register is 12 bits long.
Spindle Block Control

The Operator can view and set the Spindle Block Control Word register providing an I/O fixture has been connected to
the J5 connector.
The Operator can exercise the LEDs and seven segment displays.
Spindle Block Status

The Operator can view the Spindle Block Status providing the spindle block or I/O test fixture is connected to J5. Open/
closed relay status is displayed.
Main Contactor Control

The Operator can view and open/close the Main Contactor providing there is an I/O connection to P2.
Main Contactor Status

The Operator can view the Main Contactor status (open/close) providing there is an I/O connection to P2.
Motor Status
The Operator can view Motor temperature (over/normal) providing there is an I/O connection to P10.
DMC Baseboard
Rotor Position Status

The Operator can view the Rotor position providing there is an I/O connection to the Main Drive.
Configuration Switch
The Operator can view the Configuration Switches providing there is an I/O connection to the Main Drive.
Seven Segment & LED

The seven segment displays and LEDs are exercised.
Accelerometer Control
The Operator can set the Accelerometer Control word providing the Accelerometer is connected.
DAC Control
A connection to the P9 is required to operate the DAC Control utility.
The operator can:
1. Select data register E. Writing a 1 will cause data register E to be the digital input for all DACs. Writing a 0 will cause
each DACs data register to be used as its digital input.
2. Clear all DACs. Writing a 1 will cause all DAC outputs to be 0V. Writing a 1 will cause all DAC outputs to return to
previous analog values. The previous analog values are based on each DACs data register values.
3. Set data register E value.
4. Set all data registers to a specified value.
5. Set data register A to a specified value.
6. Set data register B to a specified value.
7. Set data register C to a specified value.
8. Set data register D to a specified value.
Tilt Baseboard
Increment DAC
The Operator can output a rising ramp waveform from one of 4 DACs located on the Main Drive. Initially the Operator is
prompted to select a DAC. Also, the Operator can vary the slope of the ramp by changing the delay value. The number
of loops executed determines the number of ramp waves outputted.
Decrement DAC
The Operator can output a falling ramp waveform from one of 4 DACs located on the Main Drive. Initially the Operator is
prompted to select a DAC. Also, the Operator can vary the slope of the ramp by changing the delay value. The number
of loops executed determines the number of ramp waves outputted.
Serial
Tilt Baseboard
On the Options menu, select Connect to Controller > TDP > Toolbox > Tilt Drive Board.
Tilt Baseboard
Target Angle Control

The target angle control utility reads the target angle register and displays it’s value. The Operator is then prompted as
to whether they want to set a new value or not. Entering a value of 0 quits the utility and a value of 1 continues. If the
utility is continued, then the Operator is prompted for a value in the range of 0x000 to 0x3ff. This value is written to the
register, read back and displayed before the utility is quit.
Current Position Control

The current position control utility reads the current position register and displays it’s value. The Operator is then
prompted as to whether they want to set a new value or not. Entering a value of 0 quits the utility and a value of 1
continues. If the utility is continued, then the Operator is prompted for a value in the range of 0x000 to 0x3ff. This value
is written to the register, read back and displayed before the utility is quit.
Potentiometer Control
The potentiometer control utility reads pots 1 and 2 eight times to clear them out. The pots are then read and displayed
along with the value of the current position register. The Operator is then prompted to set the current position register
from pot 1 or 2. Entering a 1 will use the value previously read from pot 1 and entering a 2 will use the value previously
read from pot 2. Entering any other value will quit the utility. The value from the selected pot is then written to the current
position register. The current position register is then read back and displayed. The Operator is then prompted for the
number of loops for which both pots will be read and the previously selected pot will be written to the current position
register. The current position register is then read back and displayed. At the conclusion of the loop, the utility is quit.
Maximum Speed Control

The maximum speed control utility reads the maximum speed register and displays it’s value. The Operator is then
prompted as to whether they want to set a new value or not. Entering a value of 0 quits the utility and a value of 1
continues. If the utility is continued, then the Operator is prompted for a value in the range of 0x0 to 0xf. This value is
written to the register, read back and displayed before the utility is quit.
Tilt Baseboard
Ramp Speed Control

The ramp speed control utility reads the ramp speed register. This value is displayed. This value is anded with 0xf and
bits 0 through 3 are displayed as the speed. The ramp speed register value that was previously read is then anded with
0x10 and this value is displayed as bit 4. If bit 4 is set, the ramp is indicated as being off and on otherwise. The Operator
is then prompted as to whether they want to set the ramp speed. Entering a 0 will quit the utility and any other value will
continue. If the utility is continued, then the Operator is prompted for the new ramp speed in the range 0 to 0x1f. The
new ramp speed is written to the ramp speed register, read back and displayed. The utility is then quit.
Tilt Control
The tilt control utility reads the tilt control register and displays it’s value. Individual bit values 0 through 3 are displayed
along with the definition of those bits. The Operator is then prompted as to whether they want to set the tilt control. A 0
will quit the utility and any other value up to 0xff will continue. If the Operator continues, they are prompted for the new
value between 0 and 0xf. This value is written to the tilt control register, read back, and displayed. The utility is then quit.
Tilt Status
The tilt status utility reads the tilt status register, ands it with 0x3fff, and displays it’s value. The values for the individual
bits 0 through 0xd are displayed along with the definition of the bits. The utility is then quit.
Encoder Divide
The encoder divide control utility reads the encoder divide register and displays it’s value after anding it with 0xf. The
Operator is then prompted as to whether they want to set a new value or not. Entering a value of 0 quits the utility and a
value of 1 continues. If the utility is continued, then the Operator is prompted for a value in the range of 0 to 3. This
value is written to the register, read back and displayed before the utility is quit.
Jog Speed
The jog speed control utility reads the jog speed register and displays it’s value after anding it with 0xf. The Operator is
then prompted as to whether they want to set a new value or not. Entering a value of 0 quits the utility and a value of 1
continues. If the utility is continued, then the Operator is prompted for a value in the range of 0 to 0xf. This value is
written to the register, read back and displayed before the utility is quit.
Gantry Motion Processor (GMP) Baseboard
Service Mode
The service mode control utility reads the service mode register and displays its’ value after ANDing it with 0xf. The
Operator is then prompted as to whether they want to set a new value or not. Entering a value of 0 quits the utility and a
value of 1 continues. If the utility is continued, then the Operator is prompted for a value in the range of 0 to 1. This
value is written to the register, read back and displayed before the utility is quit.
Gantry Motion Processor (GMP) Baseboard

The Gantry Motion Processor (GMP) combines functionality of the Tilt Drive Processor & Main Drive Processor. The
Main Drive Functions and the Tilt Drive Functions can be selected from the GMP Baseboard Menu. The functions are
the same as found in the Main Drive and Tilt Drive Baseboard previously mentioned sections.
Main Drive Functions
Tilt Drive Functions
Return
RHost Baseboard
RHost Baseboard
On the Options menu > select Connect to Controller > RHost > Toolbox > RHost Baseboard.
Analog to Digital
All 12 analog to digital inputs are read. The 16-bit digital value, analog input description, and analog input board
reference descriptors are displayed.
Digital to Analog
The Operator can output an analog signal. The Operator can set a constant digital value and output a constant analog
voltage. Also, the Operator can output a sawtooth or triangle analog waveform. The Operator can set the step and the
size of the analog waveform.
RHost Baseboard
Digital-Analog-Digital
A RHost test fixture is needed to operate this utility. The test fixture connects the Digital-to-Analog converter (DAC)
outputs to the Analog-to-Digital converter (ADC) inputs. This utility will write to the digital register of the DAC and digital
register of the ADC will be read. The computed difference and computed percent difference are calculated and written
to a file in the C:\usr\diamond.root\Diag\Record directory.
The permissible computed differences and percent differences are defined in a file. The name of the file is
RHostDAD_Parameters.txt and is located in the C:\usr\diamond.root\Diag\Record directory. The file contains the
following text:
19800 8192 # MUST BE FIRST: Special Case - DAC2 Cutoff at 6v = 19660 to 2.5v = 8192
1024 240 # Range from 0 - 1024 Percent Error (x 10) Allowed = +/- 24.0%
# FOR EXPEDIENCY THIS IS A FIXED FORMAT FILE.
# THE DAC OUTPUT & PERCENT ERROR (x 10) ALLOWED ARE
# FIVE (5) DECIMAL DIGITS EACH WITH SPACES BETWEEN.
# POUND (#) OR SEMI-COLON (;) IS COMMENT TO END OF LINE.
# ANY OTHER FORMAT WILL PRODUCE UNDEFINED RESULTS.
CPM / DSP
There are no CPM/DSP tests. This test does nothing at this time.
Digital Input
All RHost digital inputs are mapped to a single 32-bit word. All digital inputs can be read from one 1 32-bit word
displayed by this utility. See document
Digital Output
All RHost digital outputs are mapped to a single 32-bit word. All digital outputs can be read from one 1 32-bit word
displayed by this utility.
RHost Baseboard
Digital I/O
A RHost test fixture is needed to execute this test. The RHost test fixture connects the digital inputs to the digital
outputs. The Operator can output a single value out the digital outputs and the Digital I/O test will verify the digital inputs
are correct. Also, a walking 1’s and walking 0’s test can be performed.
PWM Waveform
The Operator can start & stop & specify the parameters for the Pulse Width Modulation (PWM) Waveform Utility. Default
values for board checkout are displayed and can be entered as is or changed. Additional information about these
parameters can be found in the MPC555 User's Manual.
"Enter MIOS Prescaler - xx"
"Enter PWM Prescaler - xx"
"Enter PWM Period - xx"
"Enter PWM Pulse - xx"
The PWM Waveform starts running after all the parameters are entered. The PWM Waveform runs until the Loop Count
is exhausted, although entering 0 will allow it to run, until the Loop Count of 0 is entered. The Test Points at which the
PWM Waveform can be observed with a scope are displayed as a convenience.
"PWM0 -> TP51 PWM1 -> TP52 PWM2 -> TP12"
Interrupt Check
This test is for future RHost test fixture development. The Operator can enable interrupt request 3 or 4. The utility will
check for expected and unexpected interrupt 3 or 4 requests.
Real Time Clock

The Operator can set the real time clock.
Seven Segment LED

The Operator can set a segment, set a hex value, walk a segment, or flash all the segments.
RHost Baseboard
Watchdog Timer
The Operator can verify the Watchdog timer went off.
E-Stop Loop

Open E-Stop
Close E-Stop
Return

E-Stop
Couch Baseboard (Galaxy Couch/Stargate Platform)

On the Options menu, select Connect to Controller > Couch > Toolbox > Galaxy Couch Baseboard.
Couch Registers
Couch Baseboard Absolute Pos (LSB)
Couch Absolute Pos (MSB)
Couch Delta Pos (LSB)
Couch Delta Pos (MSB)
Read Vert A to D
Vertical Analog to Digital Converter (ADC) test requests number of loops to monitor & display the couch Vertical ADC
value.
Read Horz A to D
Horizontal Analog to Digital Converter (ADC) test requests number of loops to monitor & display the couch Horizontal
ADC value.
Horizontal Encoder
Similar to the Read Horz A to D, this utility reads the Horizontal Encoder and displays the position. The encoder
presently used is a Stegmann AG626 XKR with 8192 positions / revolution and 2048 total revolutions, of which we use
only about 40. The couch moves 50mm in one (1) revolution, providing 8192 position measurements per 50mm, or
163.84 position measurements per one (1) mm. The utility displays the actual hexadecimal value read from the CPLD,
followed by the integer and fractional revolutions in hexadecimal and the integer and fractional millimeters in decimal.
Serial
Seven Segment LED V1

Exercises the Dual Seven Segment Displays one of 3 ways:
Hex Digits (00-FF)
Displays a pair of hexadecimal digits entered by the operator (these displays persist). (The pattern displayed on the
7 Segment Displays is programmed in the hardware, so each segment cannot be exercised.)
Count (00-FF)
The 7 Segment Displays each count from 0 - F, with each pattern being displayed for about 1 second, turning the
decimal point on for each odd digit and off for each even digit. (The pattern displayed on the 7 Segment Displays is
programmed in the hardware, so each segment cannot be exercised.)
Flash
The 7 Segment Displays flash "8." on and off ten (10) times, with each on and off period being about 1/2 second.
Seven Segment LED V2

Display 0 count test
Display 0 on/off test
Display 1 count test
Display 1 on/off test
Galaxy Control/Status Registers

Displays & Sets the Control & Status Registers
Displays the hexadecimal value of each of the following Control & Status registers:
1. Carbon Top Control
2. Carbon Top Position
3. Vertical Control
4. Vertical ADC Status
5. Vertical ADC Data
6. Top Support Control
7. Top Support Position
8. Program Speed Fail 0
9. Program Speed Fail 1
Modify Register 0/n ?

Selecting a register to modify displays the hexadecimal value of the register, followed by the bit descriptions of the
bits that are set to one (1).
Once a register is selected for modifying, the operator is prompted for the new value, that value written to the
register, and the register value displayed again.
The register can be modified and displayed until the same value is entered twice (2).
!
CAUTION The Couch Control Board (CCB) Registers should not be modified without comprehensive
knowledge of the operation of the CCB, as unintended motion or damage to the motors or
mechanism may result.
Galaxy Power Monitor Register

Displays the value of the Power Monitor register. If any bits are set, displays the description of the bit with it's
hexadecimal value. If the Revision Info bit is set, displays the two (2) Revision Info words, otherwise displays zeros (0).
Bit Hex Description
12 1000 Error 5V RS232-B
11 0800 Error 5V RS232-A
10 0400 Error V CAN Bus
9 0200 Error 24V Unreg
8 0100 Error 12V V-Motor
7 0080 OR'd All Latch
6 0040 Revision Info Bit
5 0020 Error 24Vdc Supply
4 0010 Error +15Vdc Supply
3 0008 Error -15Vdc Supply
0 0001 Error 3Vdc Xilinx
Power Monitor Register can also test the fuses, F4, F5 & F6. The test displays the status of the three (3) fused power
supply bits in the Power Monitor Register.
• Test Fuse F4(4) F5(5) F6(6) ?
• F4 (+15Vdc) & LED 22
• F5 (-15Vdc) & LED 21
• F6 (24Vdc) & LED 24
The fuse test can run in Prompt(0) (display value & wait for continue or quit response), Loop(1) (running loop displaying
the value for "count" loops), or Step(2) (running loop displaying values only when they change, for "count" loops)
modes.
Remove Keep Alive

Sets the Remove Keep Alive (RKA) and checks setting of the Remove Keep Alive Active (RKAA) status bit.
When the Remove Keep Alive bit is set LED 35 should also be on, and when reset should be off.
Sets the Remove Keep Alive bit in the Carbon Top Control Register & checks the Remove Keep Alive Active status bit
in that register. Operator can Reset(0), Set(1) or RKA(2) (copy the Active status) bit to the Remove Keep Alive bit.
E-Stop Loop
Stop functionality was changed from questions requiring a 0 (Open) or 1 (Close) response to the radio-button method.
Selecting E-Stop from the Baseboard Menu:

Open E-Stop
Close E-Stop
Return

E-Stop
(CCB Power On)

Provides the capability to manually run the Power Monitor test that runs at power-on. Reads the Power Monitor Register
and excepting the bits for the 24v Unregulated Supply, the OR'd All Latch and the Revision Information bit; if any of the
remaining bits are set indicating an error on that supply, the Power Monitor register value is logged to the Diagnostic
Error NVRAM. (The 24v Unregulated Supply only comes on after the E-Stop loop is closed, and as of this writing, the
diagnostics run with the E-Stop loop open.)
NOTE When this test runs at power-on, a failure of the monitored power supplies results in the Couch Control Board
(CCB) remaining in diagnostic mode.
Vertical Couch Encoder Utility

This utility helps the operator diagnose problems with the Vertical Couch Encoder. While the operator manually
manipulates the couch’s vertical string pot, stretching it or retracting it, the utility displays the current encoder value on
the screen.
Configurations:
This utility reports the current encoder value when the couch CCB board is in standard release configuration, or
mounted in the couch simulator available to manufacturing.
Additionally manufacturing can use it when the couch CCB board is on the bench by attaching a “wiper” pot to
board Vertical Pot plug P718. Turning the pot will have the same effect as manipulating the string pot.
Horizontal Couch Encoder Utility

This utility helps the operator diagnose problems with the Horizontal Couch Encoder. While the operator manually
moves the couch top in and out of the gantry, the utility displays the current encoder value on the screen.
Configurations:
This utility reports the current encoder value when the couch is in standard release configuration, or in the couch
simulator available to manufacturing.
Additionally manufacturing can use the utility when the couch CCB board is on the bench by attaching horizontal A
to D “Absolute” encoder to board plug P715.
Couch Baseboard (Gemini/PET-CT)

Special Note on Jumper for Using Diagnostic Utility Serially:
When it is desirable to use a laptop to run the diagnostic utility serially on the PET-CT/Gemini couch board, you must
connect to the board via the PPC 555's serial port #2. The serial line uses a 6-wire telephone jack that is plugged into
Jack J6.
However, before the server can connect serially to the board, a jumper (labeled J7) must be put in place on the board.
When it is in proper position for serial communication, LED 7 (adjacent to it) is lit red. This LED is off when the jumper is
positioned properly for normal application use.
In instances where the diagnostic utility's connection to the board would be made via the CAN bus, the J7 jumper's
position would not have to be modified.
NOTE After serial connection using the diagnostic utility is complete, before returning to normal application use, this
jumper must be restored to its original position since the serial port has been found to generate significant noise
on the bus when it is not jumper-ed out.
Serial
Seven Segment LED

Exercises the Dual Seven Segment Displays one of 3 ways:
Hex Digits (00-FF)

Displays a pair of hexadecimal digits entered by the operator (these displays persist). (The pattern displayed on the 7
Segment Displays is programmed in the hardware, so each segment cannot be exercised.)
Count (00-FF)
The 7 Segment Displays each count from 0 - F, with each pattern being displayed for about 1 second, turning the
decimal point on for each odd digit and off for each even digit. (The pattern displayed on the 7 Segment Displays is
programmed in the hardware, so each segment cannot be exercised.)
Flash
The 7 Segment Displays flash "8." on and off ten (10) times, with each on and off period being about 1/2 second.
Control/Status Registers
Displays and sets the hexadecimal value of each of the following Control and Status registers:
1. Gemini Table Control
2. Gemini Revision Register
3. Gemini ID Register
Modify Register 0/n ?

Selecting a register to modify displays the hexadecimal value of the register, followed by the bit descriptions of the bits
that are set to one (1). Once a register is selected for modifying, the operator is prompted for the new value, that value
written to the register, and the register value displayed again. The register can be modified and displayed until the same
value is entered twice (2).
!
CAUTION THE COUCH CONTROL BOARD (CCB) REGISTERS SHOULD NOT BE MODIFIED
WITHOUT COMPREHENSIVE KNOWLEDGE OF THE OPERATION OF THE CCB, AS
UNINTENDED MOTION OR DAMAGE TO THE MOTORS OR MECHANISM MAY RESULT.
Power Monitor Register

Displays the value of the Power Monitor register. If any bits are set, displays the description of the bit with it's
hexadecimal value. If the Revision Info bit is set, displays the two (2) Revision Info words, otherwise displays zeros (0).
Bit Hex Description
19 1000 Error 5V RS232-B
20 0800 Error 5V RS232-A
21 0400 Error 5V CAN Bus
24 0080 OR'd All Latch
25 0040 Board ID & Revision Info Bit
28 0008 60Vdc Supply
31 0001 Error 3Vdc Xilinx
Power Monitor Register can also test the fuses, F1, F2 & F3. The test displays the status of the three (3) fused power
supply bits in the Power Monitor Register.
• Test Fuse F1(1) F2(2) F3(3) ?
• F1 (+5Vdc) & LED 40
• F2 (+24Vdc) & LED 41
• F3 (12Vdc) & LED 35
The fuse test can run in Prompt(0) (display value & wait for continue or quit response), Loop(1) (running loop displaying
the value for "count" loops), or Step(2) (running loop displaying values only when they change, for "count" loops)
modes.
E-Stop Loop

Open E-Stop
Close E-Stop
Return

E-Stop
(CCB Power On)

Provides the capability to manually run the Power Monitor test that runs at power-on.
Reads the Power Monitor Register and the OR'd All Latch and the Revision Information bit; if any of the remaining bits
are set indicating an error on that supply, the Power Monitor register value is logged to the Diagnostic Error NVRAM.
!
CAUTION WHEN THIS TEST RUNS AT POWER-ON, A FAILURE OF THE MONITORED POWER
SUPPLIES RESULTS IN THE COUCH CONTROL BOARD (CCB) REMAINING IN
DIAGNOSTIC MODE.
Controller Board Troubleshooting
Boot-up Tests
The boot-up tests are divided into 2 sections – CPM and baseboard. If a CPM test fails, LED3 will blink an appropriate
number of times. The board will remain in utility mode. It will not boot into the application. The board will not allow
connection by the Interface. See section LEDs on page 155 for more details. If a baseboard test fails, the board will
remain in utility mode. The board will allow connection by the Interface.
CPM
After power-up, the following CPM tests are performed:
• LED
LED3 blinks on and off twice. This is a visual test. It is intended to indicate that the power-on tests are executing. It
is also intended to prove the functionality of the LED since subsequent tests use it to communicate that those tests
failed.
• Limp mode test
The term "limp mode" means the external clock used by the processor has failed for some reason, and the
processor is compensating by using the Backup Clock (BUCLK). For normal baseboard operational purposes this is
unacceptable and is considered a failure. The Limp Mode Power Up test detects whether the processor is in this
mode by reading a status bit that indicates whether the Backup Clock is in use, and if so, blinks LED3.
• Internal flash CRC test
8, 16, & 32 bit accesses
• External SRAM bus test
Walking 0 for 32 bits
Walking 1 for 32 bits
• External SRAM memory test
0 and 1’s retention
Up and down transition
Addressing in forward and backward direction
8, 16, & 32 bit accesses
• First Diagnostic NVRAM test

The Diagnostic section of the NVRAM is checked and initialized. If an NVRAM access fails, the test will fail and
LED3 will blink.
• Second Diagnostic NVRAM test
The Diagnostic section of the NVRAM is initialized. If the initialization fails LED3 will blink.
• CPLD Power on test
A baseboard access is attempted. If the access fails to complete, the watchdog timer will expire and the baseboard
will reboot. The power-up tests will execute again, but a baseboard access will not be attempted the second time.
An error will be logged into NVRAM stating the baseboard access failed and the devices might not be programmed.
• External flash test
If the type of external flash, AMD or Intel, cannot be determined than blink LED3. If the type can be determined and
the type is AMD the wait state value is set to 0x2. If the type is Intel than the wait state value is 0x4.
• DMC FPGA test
The DMC FPGA load status bit is checked. If the FPGAs on the DMC have not been loaded the FPGAs are "kick
started" or loaded. If the FPGAs fail to load LED3 will blink.
• CPLD flag check test
The CDPLD flag, located in NVRAM, is tested. The values of 0x0, 0xff, 0x0, walking 1s, and walking 0s are written
and verified. If the verification fails LED3 will blink
NOTE The CPM tests are NOT performed after a manual reset of the CPM. In other words, power on testing is skipped
when the local reset button on the CPM is pushed. Other than a power cycle, the only other way to execute the
power-on tests is to submit a Reboot via the GUI while connected to the diagnostics in internal flash.
Baseboards
• Couch - After power-up tests are performed on the Baseboard, verify Power Monitor register is correct. See (CCB
Power On) on page 153 for more details. If the test fails, the Couch will boot into diagnostics.
LEDs
The first power-on test to execute is the LED3 test. It blinks twice and then goes out while the remainder of the tests
execute. In the event that any of the CPM tests fail, this is communicated to the outside world through repeating blink
sequences using LED3. For example, if test x fails, it will blink y times, pause, blink y times, pause, etc. The blink occurs
at about a 1 Hz rate while the pause is about 1 second in duration.
For Service purposes: Replace FRU when LED3 is blinking/pausing continuously.
For Technician purposes: LED3 will blink sequences to communicate the failing component.
The blink sequence and failed test are:

Three blinks and a pause: 8 bit Internal Flash CRC test has failed.
Four blinks and a pause: 16 bit Internal Flash CRC test has failed.
Five blinks and a pause: 32 bit Internal Flash CRC test has failed.
Six blinks and a pause: 32-bit Walking Zeros test has failed.
Seven blinks and a pause: 32-bit Walking Ones test has failed.
Eleven blinks and a pause: 8-bit external SSRAM has failed.
Twelve blinks and a pause: 16-bit external SSRAM has failed.
Thirteen blinks and a pause: 32-bit external SSRAM has failed.
Fourteen blinks and a pause: Unexpected exception has occurred.
Fifteen blinks and a pause: Limp-mode test has failed.
Sixteen blinks and a pause: First Diagnostic NVRAM test has failed.
Seventeen blinks and a pause: Second Diagnostic NVRAM test has failed.
Eighteen blinks and a pause: CPLD flag check power on test has failed.
Nineteen blinks and a pause: External flash power on test has failed.
Twenty blinks and a pause: DMC FPGA power on test has failed.
There is no test for LED4 because the act of turning it on enables writes to flash. Its functionality can be judged by
watching it before and during the burning of the boot flash. Before the burn, it should be off. During the burn, it should
be on.
NVRAM
During normal operations (such as traversing the CPM Toolbox menu), NVRAM is checked and used to store operating
status information. If at any time an NVRAM access failed the following event or feedback message will appear:
An NVRAM access has recently failed and the NVRAM must be re-initialized. To re-initialize the
NVRAM a gantry power cycle or individual CPM push button reset or reboot from the baseboard menu
must be performed. If this message continues to appear after a gantry power cycle or individual
CPM push button reset or reboot from the baseboard menu has been performed, the re-
initialization of the NVRAM failed and the CPM should be replaced.
An error message will appear multiple times. The error message is:
NVRAM access failed, reset CPM or power cycle or reboot the CPM.
If you access the Utilities menu, the following messages will appear in the menu or ordinary text box. The GHost was
used as an example.
GHost
NVRAM access failed
Reboot CPM to re-initialize NVRAM
Utilities
All of the previous event and error messages will tell you to re-initialize the NVRAM. To re-initialize the NVRAM:
1. Power cycle the Gantry or board.
2. Press the CPM push button reset.
3. Select the Reboot utility the from the baseboard menu.
IMPORTANT ! If the previously mentioned messages continue to appear after a power cycle or CPM reset
or reboot the NVRAM is bad and the CPM should be replaced.
“Green” Baseboards
At power-up a baseboard access is performed to verify the CPLDs and FPGAs devices on the baseboard have been
programmed. If the baseboard access failed the baseboard will reset and a flag in the Diagnostic section of the NVRAM
will be set. An error will be logged into NVRAM stating the following:
Baseboard access failed, devices might not be programmed (JTAGed)
IMPORTANT ! If the devices are not programmed than the board is considered to be “green.”
When you connect to the "green" baseboard the following messages will appear in the menu or ordinary text box:
Baseboard access failed
Program baseboard devices
At this time the Operator should program the baseboard devices using the JTAG utility on the Utilities menu.
IMPORTANT ! The baseboard access involves the use of a single FPGA device on each of the different
baseboards. If the FPGA device is not programmed the previously mentioned messages will
appear. However, if the other CPLDs, FPGAs, and memory devices are not programmed
the previously mentioned messages will not appear. Any access to the baseboard which
involves the use of the unprogrammed devices will likely cause the baseboard to reset. This
condition should only appear in the manufacturing environment.
Controller Utilities Burn Procedures
Controller Utilities Burn Procedures
The Automation Utilities are available for proprietary use only. Third party is provided with Connect to controller where
the burn process is manual as it was in previous releases.
Prior to using these procedures, be sure to open the E-Stop by pressing the red button on the CT Box. If you forget to
do this, it sometimes results in certain boards, predominately the Couch and/or the DMC, yielding NO RESPONSE. To
remedy this, press the red button, back out to the menu that says “Service mode”, select this option again, and
continue.
If the system contains a GMP board, it will respond as the MDP. The menus will indicate NO RESPONSE from the TDP
since the GMP is its replacement.
NOTE There is a known defect with the Server/interface interaction. This occurs through usage of the Utility Interface
or the Service Tools GUI. This only occurs through the use of the Automation utilities. The problem is that
occasionally text sent from the Server to the Event section of the Utility Interface or the User Feedback window
of the Service Tools GUI is lost. In the event that the text that normally signals that the executing process has
finished is lost, it could give the impression that the process is hung up. There are two ways to distinguish
between a loss of text and a hung up process. First, if after waiting a while, the Menu section on the Diagnostic
Interface or the Options window on the Service Tools GUI does not re-enable the options, then the process could
be hung up. If the options are enabled, the process went to completion. Second, you can access the Events.rec file
to see that the process finished. The file is located in C:\usr\diamond.root\Diag\Record. You will have to exit the
interface, then use Task Manager to kill the Server. At this point, you can open the file, and the Events that the
Server was to display on the interface should be present.
In the event that a board or boards yield a status of NO RESPONSE while the boards are known to be in the
system, it is wise to push the CPM reset button on the board of interest. A software defect is currently resulting
in some boards not responding. Once the reset button has been pressed, select Return on the menu indicating
NO RESPONSE and re-select the menu. If the board now responds, the culprit is the software defect. If the board
does not respond, the possibility of a hardware problem should be investigated.
Configuration of the Server
Configuration of the Server

The functionality of the Laptop Server has been combined with the Host PC Server. The Laptop Server was used to
provide serial access to the Gantry Controllers while the Host PC Server provided CAN access. As a result, the first
time you launch the Controller utilities, a menu will appear with two choices: CAN Access or Serial access. For running
Service Tools from the Host, choose CAN. Once a choice is made, a file called Config.txt is written to
C:\usr\diamond.root\Diag\Config. As long as this file exists, subsequent start-ups will not require you to choose a driver.
To choose the other access option, you will have to delete the Config.txt file, and restart the Controller Utilities.
Important Tips for a Successful Upgrade/Reburn Procedure

This section will provide important tips to insure a successful upgrade or burn. Also, tips will be given on how to recover
or resume from a failed attempt.
1. Power the system off and on. Starting with a "fresh" system insures the boards are in a known good state. Also, not
starting the scanner application will assure the CAN bus is clear for Utility messages only.
2. The Service Tools GUI has been known to disappear. If at anytime the Service Tools GUI disappears, restart the
Service Tools GUI and begin again. If the Service Tools GUI successively crashes and no new operations can be
performed than read the next item.
3. If at any time during a file open sequence (Upload NVRAM, RAM Download, etc.) the Host Server or Service Tools
GUI or Diagnostic Interface crashes, the CPM can be left in a state that will cause the Service Tools GUI or
Diagnostic Interface to crash or hang on successive attempts to communicate with the board. The situations the
Service Tools GUI or Diagnostics Interface will crash or hang are:
• If the Operator attempts to connect to the board the Interface will crash. Repeated attempts will cause the
Interface to crash. Either press the reset on the CPM or power the system off/on.
• If the Operator is using the Server automation Utilities the Interface will hang. For example, if the CPM on the
DMC is in this state and the Operator attempts to upload NVRAM from all the boards the upload will begin and
then hang. Either pressing the reset on the boards or powering the system off/on will allow the Operator to start
the action again.
Important Tips for a Successful Upgrade/Reburn Procedure
4. A board does not respond. In the event that the status indicator adjacent to the board name indicates no response,
try pushing the CPM reset button associated with the baseboard of interest. The Utilities menu, Diagnostics menu,
and Connect to controller menus all behave the same way. These menus are dynamically created menus and must
be recreated. Select the Return radio button and hit Submit. Now select the Utilities, Diagnostics, or Connect to
controller radio button and hit Submit again. An alternate version of this is rather than hitting the CPM reset button,
follow the same steps but power cycle the gantry instead. A third tip is to just Return and regenerate the menu
again without the resets. The last tip is to back out to the menu where the option to chose Service mode exists.
Select Service mode and Submit.
5. Sometimes a reason boards do not respond is because one or more of the boards on the CAN bus is still in
application mode. You can verify this by starting up CAN Scope. If you go to the directory C:\PHILIPS\Eng_tools,
select CAN Scope or CANSDK to install CAN Scope. To start CAN Scope:
• Select baud of 500
• Select CAN->Enable 29-Bit-IDs
• Select Initialize
• Select Start
If the bus is quiet, then this is a good sign. If there is a periodic message, every couple of seconds, this is usually
because the Host is running the scanner application. This is harmless with our experience. One way to tell if the
board on the bus is in application mode is if it's ID has non-zero digits throughout all places. A board that is in
diagnostic mode will use ID of the format 000000xx where the x's are hexadecimal numbers. Diagnostic mode
messages are o.k. to see on the bus in response to selecting something on the Interface.
Re-burning Boot Flash
Re-burning Boot Flash
For Field Use

Using Utility Interface:
Select Field Service Engineer, then enter the password: Star*.
Using Service Tools GUI:

Select Field Service Engineer, then click Connect.
Procedure
1. Select Service mode.
2. Select Utilities, and click Submit.
3. Check the boxes for all the boards to be reburned.
4. Check the Save NVRAM box.
5. Check the RAM downloader box.
6. Check the Back up boot flash burner box.
7. Check the Boot flash burner box.
8. Check the Application flash burner box.
9. Check the Controller reset box.
10. Click on Submit.
11. Wait until all previous check marks disappear and procedure is completed.
12. Select Return.
13. Select Return.
14. Select Application mode.
15. Exit the interface, and use Task Manager to end DiagServHost.exe.
16. Power cycle the scanner.
17. Verify the flash has been re-burned by using the CPM Software Version Query in Service Tools.
Burning Application Flash After Boot Flash Has Been Installed
Burning Application Flash After Boot Flash Has Been Installed
For Field Use

Using Utility Interface
1. Select Field Service Engineer.
2. Enter password: Star*
Using Service Tools GUI

1. Select Field Service Engineer.
2. Click on Connect.
Procedure
2. Select Utilities, and click Submit.
3. Check the boxes for all the boards to be burned.
4. Check the Save NVRAM box.
5. Check the Application flash burner box.
6. Click on Submit.
7. Wait until all previous check marks disappear and procedure is completed.
8. Select Return.
9. Select Return.
10. Select Application mode.
11. Exit the interface, and use Task Manager to end DiagServHost.exe.
12. Verify the flash has been properly installed.
=
Recovery procedures for an aborted boot flash burn using Utilities

In the context of this document, an aborted boot flash burn is a boot flash burn that is started, but stopped prior to
completion. The stop occurs because power to the board(s) is cycled or because of a CPM push button reset.
There are two critical factors necessary for a recovery to be possible. The first is that the backup boot flash must have
been burned into the external flash. Boards at boot flash release 0.3 and 1.0 are not recoverable. The backup boot flash
cannot be properly burned into these board’s external flash. The second is that the abort does not take place during the
erase and write of the first boot sector.
A manual burn erases all of the boot flash sectors and then burns the data. A manual burn takes place by connecting
directly to the board.
An automated burn compares the data with what is in flash and erases the sector if they are different. An automated
burn takes place though use of the options of the Utility Server.
There are three ways in which a boot flash burn can be aborted. The first is the interface crashes. The second is that
the Server crashes. The third is that the Gantry Controller board is reset.
Scenario 1
An aborted boot flash burn occurs under recoverable circumstances where the Service Tools GUI has crashed while
doing an automated burn.
1. Restart the Service Tools GUI.
2. Select Diagnostic Tools.
3. Select Controller Utilities,
4. Click on the Connect button,
The GUI will connect to the Server and display the User Feedback corresponding to the state of the burn the Server/
CPM(s) are in. There may be a temporary pause before the User Feedback window displays anything, but this should
not be longer than about ten seconds. In the event that the Operator waits too long before reconnecting the GUI to the
Server, or the GUI crashes toward the end of the burn process, there would be no User Feedback messages. In this
case, the Options window would display an enabled menu. This indicates the process went to completion.
Once the boot flash burn completes, the next step is to perform the Application flash burn.
Scenario 2
An aborted boot flash burn occurs under recoverable circumstances where the Service Tools GUI has crashed while
doing a manual burn.
1. Either cycle power to the Gantry, or hit the CPM reset button on the boards that were burning.
2. Restart the Service Tools GUI.
4. Select Controller Utilities.
5. Click on the Connect button.
7. Select Connect to controller.
8. Select the board to resume the burn on.
9. Select Toolbox.
10. Select Utilities.
11. Select Downloader.
12. Select the file to download. The usual file is
C:\usr\diamond.root\Diag\CPMIntFlash\CPMIntFlashImage.bin.
13. Select Connect to controller.
14. Select the board to resume the burn on.
15. Select Toolbox.
17. Select Boot flash burner.
18. Select the file to burn. The default file is
C:\usr\diamond.root\Diag\CPMIntFlash\CPMIntFlashImage.bin.
19. Select Execute.
20. Select Exit.
Scenario 3
An aborted boot flash burn occurs under recoverable circumstances where the Server has crashed.
1. Either cycle power to the Gantry or hit the CPM reset button on the boards that were burning.
2. Use the Task Manager to stop the Service Tools GUI if it is still running. Right-click on mshta.exe, click on End
Process, and click on Yes.
3. Start up the Service Tools GUI.
9. Override the default file CPMIntFlashImage.bin found in C:\usr\diamond.root\Diag\CPMIntFlash if a different file is
desired by selecting File configuration followed by RAM downloader followed by the boards to be overridden. Select
Return.
desired by selecting File configuration followed by Boot flash burner followed by the boards to be overridden. Select
Return twice to get to the Utilities menu.
11. Select boards to participate.
12. Select RAM Downloader.
14. Select Controller reset.
15. Select Submit.
Scenario 4
An aborted boot flash burn occurs under recoverable circumstances where the Gantry Controller board was reset. A
reset can occur from a power cycle or the CPM reset button being pressed.
NOTE If the 164 RHost board is reset far enough into the boot flash burn process, then the board will not respond
thereafter. This baseboard is not capable of being contacted when it is executing code out of the external flash.
(The application is stored in external flash, but is copied to RAM and executed from there.) One way to verify
that any board is executing out of external flash is after a power cycle, it blinks LED3 on the CPM twice
significantly slower than when the code is running out of internal flash. In order to complete the boot flash burn
on the RHost CPM, power the gantry down. Leave the Supreme Controller in Utility mode. Remove the CPM
from another baseboard, such as the Ghost. Remove the CPM from the RHost. Put the CPM from the RHost on
the Ghost and the CPM from the Ghost on the RHost. Power the gantry up. Wait about 30 seconds for the
boards to run through their power on tests. Go into the RAM downloader automation utility. Disable all the
boards other than the Ghost. Execute the downloader. Return and select the Boot flash burner automation
utility. Select execute in order to finish burning the CPM. After this finishes, power the gantry down and swap the
CPM's on the Ghost and the RHost. Power the gantry up. Finish burning the application on any boards that
require it. (Do not leave the back up boot flash in the external flash.)
1. Use the Task Manager to stop the Service Tools GUI if it is still running. Right click on mshta.exe, click on End
2. Use the Task Manager to stop the Utility Server if it is still running. Right click on DiagServHost.exe, click on End
3. Start up the Service Tools GUI.
desired by selecting File configuration followed by RAM downloader followed by the boards to be overridden. Select
Return.
desired by selecting File configuration followed by Boot flash burner followed by the boards to be overridden. Select
Return twice to get to the Utilities menu.
11. Select RAM downloader.

12. Select boards to participate.
13. Select RAM downloader.
15. Select Controller reset.
16. Select Submit.
Couch Vertical Calibration
Couch Vertical Calibration
On InCenter, see the “Couch Vertical Calibration” procedure in the v3.6 Calibration Manual for your system. This will
ensure that you have the latest version of the calibration procedure.
CPM Reset
CPM Reset
CPM Reset will reset an individual processor module in the Gantry or Couch. Under Reset Boards, clicking on any of
the buttons with a processor name will reset that processor module.
CPM Software Version Query Tool
CPM Software Version Query Tool
This tool is used to show what software is installed in each processor

module that makes up the Gantry system. There are six different
processors modules, called CPMs (Common Processor Module), in
the Gantry:
• TILT processor
• ROTOR processor
• RHOST processor
• GHOST processor
• COUCH processor
• DMC processor
Clicking on any of the buttons will display the software version

numbers of the software installed on that processor module. The
software versions displayed should be compared with the installation
instructions to verify the correct versions are loaded.
DMS/Data Path Diagnostics
DMS/Data Path Diagnostics

NOTE This tool is only available for the Brilliance 64 and Brilliance Big Bore.
For information on using the DMS/Data Path Diagnostics, see Visual Diagnostics Introduction (p/n 455019309411) on
InCenter. For your scanner, it is located under Maintenance > Diagnostic Tools and Information.
DMS Tools
DMS Tools
The DMS Tools consist of:

• DMC Utility on page 174
• Aplane Reader on page 184
• DMS Temperature Monitor on page 196
DMC Utility
DMC Utility
Starting the program

On the Service Tools menu, click Diagnostic > DMS Utilities > DMC Utility.
Overview
The Status Bar at the bottom of the window displays status information:
Displays messages during and after reading and writing calibration, and after an A Plane and UHR move is initiated.
Status The current message will remain in the Status field regardless of which tab is forward.
Closing and re-opening the application will clear the message. See Status Messages on page 175
Allows you to load in the A Plane serial numbers. When the A Plane tab is forward, click on this field to load in the serial
Serial#
number. Closing and re-opening the application will clear the message.
Motor Type Displays the motor type number when you open a JIG file (*.clb)
DMC Utility
Status Messages
Table 1: Status Messages
Button Message Meaning
GetAC Getting AC... Reading A Plane Calibration from NVRAM.
GetAC GetAColl status is OK A Plane read was successful.
SetAC Setting AC... Writing A Plane calibration to NVRAM.
SetAC SetAColl status is OK A Plane write was successful.
GetAOffset Getting OA... Reading A Offset calibration from NVRAM.
GetAOffset GetAOffsets status is OK A Offset read was successful.
SetAOffset Setting OA... Writing A Offset calibration to NVRAM.
SetAOffset SetAOffsets status is OK A Offset write was successful.
AutoOffset ON AutoCalibration is OK Automatic offset calculate was successful.
GetZC Getting ZC... Reading Z calibration from NVRAM.
GetZC GetZColl status is OK Z read was successful.
SetZC Setting ZC... Writing Z calibration to NVRAM.
SetZC SetZColl status is OK Z write was successful.
GetTempParam Getting PID... Reading PID from NVRAM.
GetTempParam Getting TempOffset... Reading Temp offsets from NVRAM.
GetTempParam GetTempParamStatus is OK Temp parameters read was successful.
SetTempParam Setting PID... Writing PID to NVRAM.
SetTempParam Setting sensors... Writing sensor offsets to NVRAM.
SetTempParam SetTempParamStatus is OK Temp parameters write successful.
UHR ON Moving UHRplane in... Moving UH Plane in.
UHR OFF Moving UHRplane out... Moving UH Plane out.
Move (A) Moving Aplane to position... Moving A Plane to position.
DMC Utility
A Plane Tab
Tables
The A Plane Tab is divided into three tables:
SW This is the calibration table for controlling the slice width of the A Plane.
Z This the calibration table for controlling Z carriage motion.
This is the calibration table for the filter section. Currently, there is only one fixed filter, so there will not be any filter calibration to enter
Filter
into the table.
Fields
Each table has three fields. he default field entries range from 0 - 3, with 0 signifying the first cell and 3 the last cell. Each table has its own 0 - 3
grouping, and the coarse and fine grouping corresponds to the encoder grouping.
Encoder Designates specific A Plane collimator openings.
Coarse and Fine Encoder values from the coarse and fine modes of the encoder corresponding to the specific A Plane collimator openings.
Buttons
GetAC Reads the current values in the NVRAM designated for A Plane calibration and loads the calibration into the GUI.
Clear Sets all fields back to default values.
SetAC Writes the values in the GUI to the NVRAM.
DMC Utility
Reading the A Plane Calibration from File into the GUI

The Open JIG File button on the toolbar reads the calibration from media (disk, network, etc.) and loads the calibration
into the GUI. You can click the button when any tab is active. A pop-up box will appear that will allow you to select the
file you wish to read:
1. Click the Open JIG File button on the toolbar.
2. Browse for the media that contains the calibration file, and click on
the calibration file for your A Plane.
3. Click the Open button.
4. Click the OK button.
5. The Status field will display GettingAC… while it reads the NVRAM
and then it will display GetAColl status is OK if the read was
successful.
Manually Entering A Plane Calibration Into The GUI

If you have access to the calibration data, it is also possible to enter the A Plane calibration manually. Click on a field to
edit the value in the field. There is a translation from calibration file to GUI, so having access to the calibration file does
mean you have access to the calibration data that needs to be entered into the GUI. If you have the calibration data
from the GUI, then you could manually reload the calibration data if you needed to.
Clearing the A Plane GUI

Click the Clear button on the A Plane tab, and the fields will update with the default values.
Writing A Plane Calibration To NVRAM

After loading calibration data into the A Plane tab, click the SetAC button. The Status field will display SettingAC… while
it writes the calibration, and then it will display SetAColl status is OK if the write was successful.
DMC Utility
Reading A Plane Calibration From NVRAM

On the A Plane tab, click the GetAC button. The Status field will display GettingAC… while it reads the calibration, and
then it will display GetAColl status is OK if the read was successful.
Figure 23: A Plane tab after successfully reading the calibration from NVRAM.
Entering The A Plane Serial Number

The second field on the Status Bar displays the A Plane serial number. Double-click on the Serial #: field in order to
display the serial number pop-up. Enter the A Plane serial number into the field, and click the OK button.
DMC Utility
A Offsets Tab
Tables
The Tab is divided into two tables:
SW This is the calibration table for controlling the slice width of the A Plane.
Z This the calibration table for controlling Z carriage motion.
This is the calibration table for the filter section. Currently, there is only one fixed filter, so there will not be any filter calibration to enter
Filter
into the table.
Fields
For each table there are four fields: CosCoarse, CosFine, SinCoarse and SinFine. The default field entry is 511.
Buttons
GetAOffset Reads the current values in the NVRAM designated for A Plane Offsets calibration and loads the calibration into the GUI
Clear Sets all fields back to default values.
SetAOffset Writes the values in the GUI to the NVRAM.
DMC Utility
Status Bar
The Status Bar for the A Offsets tab is the same as the A Plane tab with the following exceptions:
• While reading, the Status field will display GettingOA…, and after successfully reading, the Status field will display
GetAOffsets status is OK.
• While writing, the Status field will display SettingOA…, and after successfully reading, the Status field will display
SetAOffsets status is OK.
Manually Entering A Offsets Calibration Into The GUI

If you have access to the calibration data, it is also possible to enter the A Offsets calibration manually. Click on a field
to edit the value in the field. There is a translation from calibration file to GUI, so having access to the calibration file
does mean you have access to the calibration data that needs to be entered into the GUI. If you have the calibration
data from the GUI, then you could manually reload the calibration data if you needed to.
Clearing the A Plane GUI

Click the Clear button on the A Offsets tab GUI, and the fields will update with the default values.
DMC Utility
Z RPM Tab
Tables
The Z RPM tab is divided into two tables, Rotor Speed and Z
Position. The first table, Rotor Speed, designates allowable rotor
rotations. The mapping between rpm and time is in the following
table. The scanning application uses time.
Table 2: RPM-to-time mapping
RPM 0 30 40 60 80 120
Seconds X 2 1.5 1 .75 05
The default field entries are numbers ranging from 0 to 5.
Buttons
GetZC Reads the current values in the NVRAM designated for Z calibration and loads the calibration into the GUI.
Clear Sets all fields back to the default values.
SetZC Writes the values in the GUI to the NVRAM.
Status Bar
The Status Bar for the Z RPM tab is the same as the A Plane tab with the following exceptions:
While reading, the Status field will display GettingZC…, and after successfully reading, the Status field will display
GetZColl status is OK.
While writing, the Status field will display SettingZC…, and after successfully reading, the Status field will display
SetZColl status is OK.
Obtaining Z Alignment Calibration

Z alignment if performed after air, phantom and HCOR calibration. See the Performance Manual for the procedure for Z
alignment.
DMC Utility
Manually Entering The Z Alignment Calibration Into The GUI

Double-click on a Z Position field to edit the value. The figure at right shows the Z RPM tab with manually entered Z
alignment calibration. There is no status message while entering the values so the last message will remain in the
status field.
Figure 24:
Clearing the Z RPM GUI

Click the Clear button on the Z RPM tab, and the fields will update with the default values.
Writing The Z alignment Calibration Into The NVRAM

After loading calibration data into the Z RPM tab, click the SetZC button. The Status field will display SettingZC… while
it writes the calibration, and will then display SetPColl status is OK if the write was successful
Reading The Z alignment Calibration From NVRAM

From the Z RPM tab, click the GetZC button. The Status field will display GettingZC… while it reads the calibration, and
will then display GetZColl status is OK if the read was successful.
DMC Utility
Go2Position Tab On Host Application
The A Plane Units table allows movement of the SW, Z and Filter motors. The table contains the values corresponding
to specific A Plane SW collimator openings. Openings can be entered in microns or mills (thousandths of an inch)
depending on which radio button is selected.
The default value is 0. The recommended range of widths is 20 to 3400 micrometers. The default unit is micrometers.
The Move button initiates the move to position.
NOTE Since there is only one button, the Status field will display Moving Aplane to position … during and after a move.
Double-click the Aplane Units field in order to edit it. Enter a value within the allowed range then click the Move button.
In order to move the Z position of the A Plane, click on one of radio buttons indicating Rotor Speed. The Z motor will
move the collimator according to the value set in the Z RPM tab.
To change the Filter position, select one of the three positions for the motor. This will place the Filter desired in the
center of the collimator opening once the Move button is pressed.
Aplane Reader
Aplane Reader
Aplane Reader displays the position and voltage of the Slice Width, Z, and filter of the Aplane Collimator both
graphically and numerically. The software includes an analysis window that allows you to focus on segments of the
collected data and print data to a hard copy. The Aplane Reader allows real-time reading of devices, such as Aplane
encoders, rotor position, rotor speed, Tube Heat, Tube Status, Z tracking, Dose Modulation, and Reference Converter
values.
Aplane Reader
Starting the program

1. On the Service Tools menu, click Diagnostic > DMS Utilities > Aplane Reader.
2. Upon entering the program, enter the Password "164" in order to see the appropriate screens.
Once you start the Utility, you must set the frequency of reading:
1. Click View > Options.
2. Select any value between 50 and 10000 ms in increments of 50 using the following dialog:
3. On the Options dialog, click on Apply then OK before proceeding.
Aplane Reader
Functions
Information
There are four readouts in the information box:
Reading When in the ON position Aplane Reader collects data about filter and blade position and voltage
from the DMC. This data is then displayed graphically and numerically.
When resetting the DMC or loading the Calibration file close A-plane reader Program!
ClearAll Clears all data previously collected
GetData Retrieves data from the DMC
DataAmount The last data point along the horizontal axis of the display window collected from the DMC. This
number is in terms of an unspecified unit of time (approximately 1/10 second.)
• To get one reading only, click on the GetData button. This retrieves one reading from each device.
• To get continuous readings, click on the Reading button. The main display indicates the linear encoder readings for
the Z, Slice Width and Filter motors, for Sin (blue) and Cos (pink) as well as a calculated value for position (red).
The current position of the collimators is shown graphically in the displays on the right hand side of the screen.
• To stop continuous readings, click on the Reading button again.
• Click ClearAll to clear all displayed data.
Aplane Reader
Rotor
The dial rotates in sync with the rotor. The blue number indicates the direction of the rotor; 0 for forward. The green
number gives the rotor position in degrees. 0° and 360° are at the top as shown below. 90° is to the right, 270° is to the
left. This is for Reference Only.
The rotating knob indicates the rotor position. The rotor speed (in seconds/revolution) is indicated in blue and the rotor
position (in degrees) is indicated in green.
The indicator on the rotor knob is lit when x rays are being applied.
The X-ray status icon is lit when x rays are being applied
Z-Tracking
Non-functional Read out.
DOM
Aplane Reader
Ref
Tube
This bar shows the percent tube heat. For Reference Only.
Pplane
Gives the UHR Reading. For Reference Only.
Aplane Reader
Aplane
The numbers along the sides of the blades show the number of mm that the blades move. Negative
numbers will not work. This window is for visual information only. Actual measurement of position
should be determined by the red values shown by the graphs.
The indicators numbered zero show weather the motor is disabled or enabled. The indicators turn
green when the motor is in motion. All motors should time out after 30 seconds.
The indicators numbered one tell the motor position, either in or out. The indicator in the SW Motor
box reads out when the blades are fully closed. The indicator in the Filter Motor box reads out when
the filter tray is in position number three.
The following chart are the limits to use while positioning the collimator with the DMC Utility.
Slice Width 0 to 16000 um
Z +/- 1100 um
Filter Fixed Positions um
Aplane Reader
Display Windows
SW and Z (Position and Voltage)

The red numbers to the right give the blade position in mm. The smaller display window shows the SIN/COS voltage of
the blade encoder and the larger display window shows the position/SIN/COS with respect to Time.
The Z analysis window is similar to the SW analysis window with the exception that there is no three dimensional
display window.
Aplane Reader
Filter (Position and Voltage)

The display to the right shows the filter location.
The Red (bottom most) set of numbers gives the filter location and corresponds to the numbers next to the graphical
display. The smaller of the two windows gives a graphical display of the voltage while the larger window gives a
graphical display of the filter position.
Aplane Reader
Data Analysis
Analyzing the SW data

Click on the middle analysis button to analyze the SW data.
SW Analysis Button
The 3-D Graph can be

rotated by clicking with
the cursor and
dragging to the desired
position.
The SW Analysis (above) shows the Angle and the Encoder separately. Cursors show the position of the cursor when
choosing a point on the Angle or Encoder display windows.
Aplane Reader
Under Mode, there are three options, Zoom, Pan, and Cursor. Cursor allows the user to choose a data point on the
graph and read the position. The data under Cursors and Results will change depending on the point chosen. Pan will
allow the user to scroll along the time line to a new data set. Zoom allows the user to magnify a designated data range.
The Zoom feature will automatically zoom in on both the Encoder and Angle display windows when the user zooms in
on either one.
Min and Max determine the data range to be analyzed. This allows the user to include more data as it is collected or to
focus in on a specific range of data. The units are called DataAmount and are approximately 1/10 second. Clicking
Refresh will re-display the data to encompass the new data range.
Aplane Reader
Analyzing the Z data

Click on the first analysis button to analyze the Z data.
Z Analysis Button
The Z analysis window is similar to the SW analysis window with the exception that there is no three dimensional
display window.
Aplane Reader
Analyzing the Filter data

Click on the last button to analyze the Filter data.
Filter Analysis Button
The analysis window gives the graphical display on a print friendly window separating the voltage from the position.
This screen allows you to zoom in on a particular data set or pan to observe a different data set.
DMS Temperature Monitor
DMS Temperature Monitor

Press the Start Toggle button to start readings of the motherboard temperatures and fan speeds in the DMS. You can
adjust the time between readings by changing the period (seconds) value. To stop readings, press the toggle button
again. Values written to the screen for the motherboard temperatures and fan speeds are also saved in the MS-Excel
compatible file c:\usr\service.root\RCOMMotherBoardTemperatures.csv.
Figure 25: Temperature Reading in Celsius Figure 26: Temperature Reading in Fahrenheit
IBox Diagnostics
IBox Diagnostics
IBox diagnostics is a utility for doing the following tasks:

• Checking the IBox hardware
• Updating the IBox internal software
Running the IBox Diagnostics
Run the IBox diagnostics program from the

service screen or directly by running IBoxDiag.
There are three options:
• Automatic test – running a batch of tests
automatically.
• Manual test – running each test separately –
used by advanced users.
• Program update – updating the internal IBox
software
Figure 27:
Automatic Test
Click Automatic Test in main window and then click Next. The test list is then presented to the user. The user can
select/deselect each test.
Figure 28:
NOTE The discrete signal test requires a special cable, and hence is cleared as default.
Running the test is done by clicking Next. At the end of the test, the results are displayed at the “Result” column in the
screen.
Manual Test
Click Manual Test in the main window and then click

Next. An option screen with eight buttons is displayed
and the user can run each test separately. The tests list
is as follow:
• Display & LEDs Check – shows a raising counter in
one 7 segment display, Show a lowering counter in
the next 7 segment display, and blink the LEDs one
after an other. The test program can not determine if
the test succeeded, since it evolves looking at the
display & LEDs.
• Get version – This is not a test. This is a function for
extracting the internal version of the FPGA
programming and of the internal IBox software. This
function also gives the information if the software
currently runs from the boot flash or from the
program flash. The normal behavior is running from
the program flash.
• FPGA test – Run an internal test for checking the
FPGA
• Relay test – Run an internal test for checking the
relays. Figure 29:
• RAM test – Run an internal test for checking the
RAM.
• ECG Test – Run a short ECG detection process. The ECG signal is created by the IBox internal signal generator.
• EEPROM test – Run an internal test for the EEPROM. This test deletes all information form the EEPROM.
• Discrete signals – Run an internal test for checking input and output digital lines. This check should be done using
a special IBOX test cable.
IBOX Program Update

To activate program update, select IBox program upgrade in the main window and then click Next. The process is
done as follows:
1. The user can save the current internal program into a file. This is done by typing a file name into the text box and
clicking Next. The user can skip this stage by clicking Skip.
2. The user selects the new program file. This is a file with “BIX” extension. After selecting the file the user must click
Next.
3. A burning screen appears and shows the burning process.
4. At the end of the burning process, the user is asked to reset the IBox. Resetting the IBox activates the new burned
software.
Test Log
The program saved a detailed log of all its activities. This log can be save to a log file by clicking Save test log in the
main screen.
LAN Config
LAN Config
When using LAN Config, see Incenter for the Networking Installation and Configuration manual for your system. It is
located under Reference > Service Manual.
Manual Exposure
Manual Exposure
Manual Exposure generates X-rays and executes a series structure without using the Scanner Application. This allows
you to test the X-ray system and gantry operation without the Scanner Application running. There are two operating
modes: Easy Mode and Expert Mode. The application defaults to Easy Mode.
To use Manual Exposure:

2. Click the Diagnostics workflow button at the top of the window.
3. On the Application List, select Manual Expose.
• To use Easy Mode, see page 203
• To use Expert Mode, see page 205
Easy Mode
Easy Mode
System Parameters
Start Test Button
1. Click the Start Test button.

2. Make your selections from the System Parameters.
3. Click the Execute Series button.
4. Click OK on the dialog box that asks you to Press the appropriate button..., then press the Auto Button on the CT
Box.
If an error occurs, the Operational Message section will display “Timeout waiting for series ready, suggest sending
<Series Cancel> then press <Continue> to restart”. This means the gantry did not respond to the series and a
cancel should be sent to the gantry to reset the gantry state machine. This is done by clicking “Send Series
Cancel”.
5. When the test completes, click the Continue button.
Easy Mode
6. When you are finished with the test:

• If you performed a Rotating Scan, click the Send Series Cancel button to stop the rotor from spinning.
• If you performed a Stationary Scan, you must reset the GHost as follows:
i. A dialog box will remind you to do this first.
ii. turn the Key Switch on the CT Box to open E-stop,
iii. On Service Tools, click on General Tools > CPM Reset,
iv. On CPM Reset, click the GHost button.
v. When you see the GHost Reset message, turn the Key Switch on the CT Box to close E-stop.
Expert Mode
Expert Mode
To use Expert Mode, click on the
Expert Mode Button.
It is important to note that generating
X-rays and executing a series
requires the interaction of many
subsystems on the gantry. Manual
Exposure is installed with pre-
defined “protocols”. A protocol is a
user friendly name associated with a
“series structure”. A series structure
is a data structure that contains all
the parameters the gantry needs to
execute a CT scan. You can also
define custom protocols. However,
only a qualified user should attempt
to define custom protocols.
Using the tool requires a basic
understanding of the tool's interface
screen. The screen has six basic
areas: protocol selection, command
buttons, operational messages,
message trace, message trace data
and real time data. These areas are
shown below.
To run the test in Expert Mode, Performing the test in Expert Mode on page 209.
Expert Mode
Protocol Selection
The protocol selection area lets the user select a predefined
protocol or create a user defined protocol. The current database of
protocols is displayed in the drop down select list at the top of the
protocol selection area. The default protocols are No Load and
Warm Up. A protocol in the list is selected by right clicking on it. To
create a user defined protocol, User-defined Protocols on page
206. To delete a protocol, see the Deleting Protocols section.
User-defined Protocols
The tool allows the user to define his or her own protocol. A protocol is an association of a user friendly name and a
saved series structure. Before creating a protocol, the desired series structure must be saved on the computer. A
typical way to do this is to start with the predefined warm up series, make changes to the warm up series parameters
and save this modified series with a new name. The warm up series can be modified using the message trace data
control. When the data values in this control are clicked, they become modifiable. The Save To button on the top of the
control will save the new series. The user can choose the name. The .tSeries file extension should be used for all series
structures.
Once the custom series structure has been saved to disk, the Add Protocol button is used to create the protocol.
When this button is clicked, the “Name” edit box and the “Browse” button will become active. In the “Name” field, the
user should type a name that will appropriately describe the series such as “High kV Warm Up”. When a name has
been chosen, the user should click the “Browse” button and locate the saved series structure that is to be associated
with this protocol name. Once this is done, clicking on the “Apply Changes” button will complete the add protocol
procedure. At any time the user may click the “Cancel” button to stop the add protocol procedure.
Deleting Protocols
Protocols can be deleted from the protocol list by selecting them and clicking on the "Delete Protocol" button. The user
will be asked to verify the delete action with a message box. Once a protocol is deleted, it is removed from the database
and will not appear in the protocol selection list.
Expert Mode
Command Buttons
The command buttons are used to execute a series and to cancel a series. The uppermost button in the section is used
to execute the series and the text on the button will change as the series executes. This button will initially be labeled
"Start". Once a protocol is selected from the protocol selection list, the user should click the start button. The button will
change to "Continue". Instructions in the Operational Messages area will instruct the user what to do next. At any time,
the user may click "Send Series Cancel" to abort the protocol.
Operational Messages
This section guides the user through the test with instructions. The messages will change as the user clicks on the start
command button and the test executes. The sequence of instructions is:
1. Make changes to series then press the Continue button.
2. Press the Execute Series button to send the series.
3. Loading Series, waiting for Series Ready.
4. Got Series Ready - Scan Started. Check the results, press the Continue button to restart.
If an error occurs, the operational message section will display "Timeout waiting for series ready, suggest sending
series cancel". This means the gantry did not respond to the series and a cancel should be sent to the gantry to reset
the gantry state machine. This is done by pressing "Send Series Cancel".
Message Trace
The Message Trace area is a mini "CAN Trace" tool that shows only "GANTRY_SERIES" messages. This part of the
tool accesses the CAN Trace database and displays all messages that begin with "GANTRY_SERIES". The
GANTRY_SERIES messages include commands to load and execute a series so these messages are pertinent to
making an exposure. Using this area of the tool, the user can examine the sequence of commands to load and execute
the series. The data associated with the messages is displayed when the message is clicked. The data will appear in
the Message Trace Data area.
Expert Mode
Message Trace Data

This is a standard message control that is used throughout the tool package. It is used to display the data values
associated with one of the defined messages in the system. The control allows loading and saving of the data values.
With respect to the tool, this area of the tool has two purposes. It is used to display and change the series structure data
values associated with a protocol and it is used to display data values when a message is clicked on in the Message
Trace area.
Real Time Data

During use of the tool, the real time data area displays the values of critical system parameters. This includes the
current kV and mA, the percent of maximum tube heat, the couch horizontal and vertical positions and the gantry tilt
position. Additionally, the operating state of the gantry is displayed. These values are updated once per second.
Expert Mode
Performing the test in Expert Mode

1. Select a protocol from the Protocols menu list.
2. In the Series In selected protocol area, check that the value of seriesTriggerType is set to
SERIES_AUTO_TRIGGER.
NOTE Make sure the Use System Grid Voltages box is checked (see Figure 30 on page 209). This tells the protocols to use
the grid voltages read from the Grid Voltage Calibration file. Otherwise, the Protocols use default grid voltage
values, which may result in false readings.
4. To run the Protocol as is, click the Continue button. Or, make any changes as necessary, then click the Continue
button.
5. Press the Execute Test button.
6. When the Operational messages area displays Series_Ready, push the Auto Button on the CT Box to make an
exposure.
7. When the test is complete, press the Continue button.
Figure 30:
Map Drive (for Varian Computer)

1. Ask the site IT Administrator for the Varian RPM™ user name and password.
2. Make sure that the Varian RPM is on and connected to the network. If the Varian RPM is not connected, then:
a. Connect the Varian RPM to the network and turn it on.
b. Restart the CT Host computer
c. Log On as philips_service.
4. On the Service Tools FrameWork, click on the Utilities workflow button
5. On the Utilities menu list, click on Map Drive. The Create Mapping window will appear.
Figure 31:
6. In the IP Address text box, enter the IP Address and the Varian RPM™ share folder name in the following format:
\\xxx.xxx.xxx.x\share folder name)
where xxx.xxx.xxx.x is the IP Address
7. In the User Name text box, enter the Varian RPM™ user name.
NOTE A domain name may be required as a modifier for the user name and should be entered as part of the user name,
i.e. “<domain name>\<user name>”.
8. If a password is required, enter the Varian RPM™ user password in the Password text box.
9. Click OK. A success message will appear.
10. Click Close.
No Load Test
No Load Test
Overview
The No Load Test allows you to discover the source of

an arc in the High Voltage Power Supply (HVPS)
subsystem. You can determine whether the arc
occurred in the X-ray tube or in the generator.
When commanded into a “no load” mode, the generator
disables the filament fault detection, the “KV_BAL”
(anode/cathode KV differential) and the filament supply.
Additionally, when in no load mode, the RHOST
software performs as follows: (a) The generator is
commanded to run in open-loop; (b) There is no KV- mA
imbalance monitoring; (c) There is no monitoring for the
ALE signal at the end of an exposure.
You can run the No Load Test with the tube either
connected or disconnected.
When an exposure is made with the tube connected and
an arc occurs, but an arc does not occur with the tube
disconnected, then it is fairly certain that the arc
occurred in the tube. If the tube is disconnected and an
arc occurs then obviously the arc occurred in the
generator.
• For information on the interface components, see Components on page 213.

• To run the test, see Running the No Load Test on page 216. Make sure you read the entire test procedure
before starting!
Components
Components
This section has information on the components that make up the No Load interface.
!
CAUTION Do not use the Components section to try and run the test!
To run the test, see Running the No Load Test on page 216.
Scan Parameters
You can select the number of shots, shot time, and kV.
Command Buttons
The command buttons execute the no load test. The button initially labeled
Start Test controls the test. Note that the text on this button will change as
the test executes, to more appropriately indicate what operation comes next.
Instructions in the Operational Messages area will tell you what to do next.
The Send Series Cancel button may be clicked at any time during the test
to send a “series cancel” message. The series cancel message will
terminate the no load test.
The Change Tube Status button is primarily for informational purposes. If
you change the connected/disconnected status of the tube, you can click
this button to toggle the informational message that indicates the connected
state of the tube.
Components
Operational Messages
The messages appear in the middle of the interface, beneath the Send Series Cancel button. The messages guide you
through the test with instructions. The messages will change as you click on the Start Test button and the test executes.
The basic sequence of instructions is:
• Make changes to series, Then press <continue>
• Press <Execute Series> to send the series
• Loading Series, waiting for Series Ready
• Got Series Ready - Scan Started. Check the results when scan completes, press <Continue> to restart
If an error occurs, the Operational Message section will display “Timeout waiting for series ready, suggest sending
<Series Cancel> then press <Continue> to restart”. This means the gantry did not respond to the series and a cancel
should be sent to the gantry to reset the gantry state machine. This is done by clicking “Send Series Cancel”.
Real Time Data

During the test, the real time data area displays the values of critical system parameters. This includes the operating
state of the gantry and the current kV and mA.
Components
Result Messages
The results of the test are encoded in the GANTRY_INFO_ERROR_BKST and RHOST_NORMAL_ERROR_BKST
messages. The strings associated with each message provide information regarding the results of the test. If there is an
arc, you will see APM Arc or CPM Arc in the string. Both the Anode and Cathode Power Modules will detect an arc in
the tube so you will see both APM Arc and CPM Arc strings in the messages.
Running the No Load Test

It is recommended to run the test multiple times with both the x-ray tube connected (see Running the Test with Tube
Connected on page 216) and with the x-ray tube disconnected (see Running the Test with Tube Disconnected on page
219). Start with the lowest kV and work your way up. Make sure you read the entire section before running the test!
Running the Test with Tube Connected

NOTE Prior to running the No Load Test, ensure that the scanner application is not running.
1. Log-on as philips_service and enter password.
2. On the Desktop, double-click on the Service Tools icon.
3. On Service Tools, click the Diagnostics tab, then select Tube Tools/Diagnostics/No Load Test. A dialog box will
appear asking if the X-Ray Tube is disconnected. Click on No. After you answer this question, the connected/
disconnected state of the tube will display in the upper right corner of the No Load test screen.
NOTE The tube state is updated based on your answer to the dialog box, not the real-time state of the gantry.
4. On the No Load Test, click the Start

Test button.
Figure 32:
5. A dialog box will be displayed stating
that protocols not using CT BOX
triggers are not recommended.
Note: the first time this test is run,
this dialog box will be displayed
after Step 7 is performed).
Figure 33:
Click OK.
6. Wait for Keyswitch Prompt dialog
box to be displayed.
7. You will see a message asking you

to verify E-stop is Open. If needed,
turn the Key Switch on the CT Box to
open E-stop, then click the Init
Rhost button.
Figure 34:
8. After the Rhost initiates you will see
a message “Waiting for E-stop
closed, PRE-SERIES state”.
Turn the Key Switch to close the E-
stop, then click OK on the prompt.
NOTE If you see a series time out
message, just click the
Continue Button.
Figure 35:
9. You will see a message asking you
to set the Number of Shots, Shot
Time, and kV. Select the number of
shots, the shot time and the kV. The
first time the test is performed, select
80 kV.
Figure 36:
10. After making your selections, click
the Execute Series Button.
Figure 37:
11. A message Loading Series,
waiting for Series Ready... will be
displayed as the test is running.
Figure 38:
12. A message Press the appropriate

button on CT BOX to start scan(s)...
will be displayed. Press the Auto
Button on the CT Box to start scan.
Auto Button on CT Box

Figure 39:
13. When the test is complete, you will see
the following message, then click the
Continue button.
Figure 40:
14. A dialog box will be displayed to
reconnect any disconnected cables.
Click OK.
Figure 41:
15. Repeat test, increasing kV each time to 90, 120, and 140. Click on Start Test (Step 4 on page 216) to repeat the
test.
16. When you are finished testing, click on Send Series Cancel.
reconnect any disconnected cables.
Click OK.
Figure 42:
18. Continue No Load Test with the x-ray tube cables disconnected. Go to Running the Test with Tube Disconnected
on page 219.
Running the Test with Tube Disconnected

NOTE Read this entire section before running the test!
NOTE Make sure you have the following items on hand as you will inspect, clean, and grease the High Voltage
Connectors:
• Silicone Paste (p/n 131250148202)
• Silicone Washer O3 for Anode (p/n 451210459971) and Silicone Washer O4/2 for
Cathode (p/n 451210497591)
WARNING HAZARDOUS VOLTAGES ARE PRESENT. WHILE SERVICING, EXERCISE

PROPER PRECAUTIONS TO AVOID CONTACT WITH THE ENDS OF THE HIGH
VOLTAGE CONNECTORS. FAILURE TO DO SO MAY RESULT IN SERIOUS
INJURY OR DEATH.
1. Click on Change Tube Status. A dialog box will appear asking if the X-Ray Tube is disconnected. Do not answer
the dialog box at this time.
2. Use the keyswitch on the CT Box to open E-Stop.
3. Momentarily press and release the blue button on the side of the gantry switch panel. This will de-energize the
utility contactor (UTK) and turn the gantry off.
BLUE BUTTON
4. Open the gantry front cover. Ensure the gantry interlock switch is engaged.
NOTE Ensure the x-ray tube is in the 12 o’clock position.
5. Pin the rotor with the locking pin (use the inner hole on the lower right side).
!
CAUTION Wait five minutes before disconnecting the High Voltage Connector cables from the Anode and
Cathode Power Modules.
6. Remove the High Voltage Connector cables from the Anode and Cathode Power Modules. After removing the
cables, ground the ends of the High Voltage Connectors against the rotor chassis to discharge any residual current.
7. Momentarily press and release the blue button on the side of the gantry switch panel. This will energize the utility
contactor (UTK) and turn the gantry on.
8. At the dialog box asking if the X-Ray Tube is disconnected, answer Yes. After you answer this question, the
connected/disconnected state of the tube will display in the upper right corner of the No Load test screen.
NOTE The tube state is updated based on your answer to the dialog box, not the real-time state of the gantry.
9. Wait for Keyswitch Prompt

dialog box to be displayed.
Figure 43:
10. On the No Load Test, click the

Start Test button.
Figure 44:
11. A dialog box will be displayed
stating that protocols not using
CT BOX triggers are not
recommended. Click OK.
Figure 45:
12. You will see a message
“Waiting for E-stop closed,
PRE-SERIES state”. Turn the
Key Switch on the CT Box to
close E-stop, and click OK at
the dialog box prompt.
NOTE If you see a series time
out message, just click
the Continue Button.
Figure 46:
13. You will see a message asking
you to set the Number of
Shots, Shot Time, and kV.
Select the number of shots, the
shot time and the kV.
Figure 47:
14. After making your selections,
click the Execute Series
Button.
Figure 48:
15. A message Loading Series,

waiting for Series Ready...
will be displayed as the test is
running.
Figure 49:
16. A message Press the
appropriate button on CT
BOX to start scan(s)... will be
displayed. Press the Auto
Button on the CT Box to start
scan.
Auto Button
Figure 50:
17. When the test is complete, you will see the

following message, then click the Continue
button.
Figure 51:
18. A dialog box will be displayed to reconnect any
disconnected cables. Click OK.
Figure 52:
19. Repeat test, increasing kV each time to 90, 120, and 140. Click on Start Test (Step 10 on page 221) to repeat the
test.
20. When you are finished testing, click on Send Series Cancel.
reconnect any disconnected
cables. Click OK.
Figure 53:
22. Use the keyswitch on the CT Box to open E-Stop.

23. Close the No Load Test tool.
24. Clean, grease, gap the split pins (if necessary); and install the high voltage connectors (see MRC High Voltage
Connectors on page 224 for details).
MRC High Voltage Connectors

There are two types of pins for the HV Connectors on the MRC tubes. Older connectors will have split pins, while newer
connectors will have banana-style, spring-loaded pins.
1. Momentarily press and release the blue button

on the side of the gantry switch panel. This will
de-energize the utility contactor (UTK) and turn
the gantry off. BLUE BUTTON
WARNING HAZARDOUS VOLTAGES ARE PRESENT. MAKE SURE YOU GROUND THE
ENDS OF THE HIGH VOLTAGE CONNECTORS AGAINST THE ROTOR CHASSIS
TO DISCHARGE ANY RESIDUAL CURRENT BEFORE CONTINUING. FAILURE
TO DO SO MAY RESULT IN SERIOUS INJURY OR DEATH.
2. Ground the end of the High Voltage Connectors against the rotor chassis to discharge any residual current.
3. For each connector:
a. Check the washers to see if they are swollen. If the washer is noticeably larger than the diameter of the
connector, replace the washer. Otherwise you will not be able to re-sea the connector in the power module.
NOTE If the washer is missing, check to see if the washer is stuck in the power module.
b. Remove the washer, and clean the washer with isopropyl alcohol and a cleaning cloth.
c. Clean the connector with isopropyl alcohol and a cleaning cloth. Do not touch the connector pins with your
fingers.
4. If your connectors have the split pins, perform step a below. If your connectors have the banana pins, skip to
Step 5.
a.Using the HV cable seating tool (p/n 9890 000 02841), check the pins at the end of the plug. Ensure the tool sits
against the flat end of the plug. The pins are factory set to the desired distance of 1 mm, but should be
checked for spreading. See Figure 54 below.
Figure 54: Checking Pins With HV Cable Seating Tool
5. Using silicon paste, put a small dab of paste in the center of

the plug between the connector pins as shown in Figure 55.
6. Install the silicon washer over the pins of the plug. The
connector pins must be free from silicon paste.
7. Put a second small dab of paste in the center of the silicon
washer between the connector pins as shown in Figure 55.
NOTE Do not grease the sides of the connector plug!
Figure 55:
8. Plug the High Voltage Connectors into the power modules. Make sure the connectors are seated properly in the
power modules, then tighten the coupling rings.
9. Refer to the Gantry Repair/Replacement Manual for the appropriate system for any components that need to be
replaced.
10. Remove the gantry locking pin from the rotor.
11. Close the front cover.
12. Momentarily press and release the blue button on the side of the gantry switch panel. This will energize the utility
contactor (UTK) and turn the gantry on.
13. Perform a test scan to verify operation of the system.
Real Time Data
Real Time Data
Real Time Data displays the “real time” values of important parameters in the gantry system. See Real Time Data
Parameters on page 228 for the parameter description.
Real Time Data Parameters

:
Gantry Status
If the value is non-zero, then there is an error on the gantry.
Gantry State
The current executing state of the gantry. The possible states are:
• STUDY_EXECUTION (0)
• LIFE_WAIT (1)
• CONFIG_WAIT (2)
• ESTOP_INIT (3)
• PRE_SERIES (4)
• STUDY_EXECUTE (5)
• SERIES_PREP (6)
• SERIES_READY (7)
• SERIES_EXIT (8)
• SERIES_EXECUTE (9)
• PRESHOT (10)
• SHOT (11)
• POSTSHOT (12)
• WARMUP_PRESHOT (13)
• WARMUP_SHOT (14)
• WARMUP_POSTSHOT (15)
• SHUTDOWN_IMMEDIATE (16)
• SHUTDOWN_LONG (17)
Heat Units
The current percentage of the maximum allowed heat of the X-ray tube.
Vertical Abs Position

The absolute vertical position of the couch in 0.1mm.
Horizontal Abs Position

The absolute horizontal position of the couch in 0.1mm.
Zero Position
The horizontal position of zero in 0.1mm.
Single Rotation Time

The time in msec for a single rotation of the rotor.
Read Error
If the value is non-zero, then the gantry servers on the Host computer are not running.
Current KV
The X-ray tube voltage in kV.
Current MA
The X-ray tube current in mA.
Filament Current
The filament current in mA.
Remote Configuration
Remote Configuration
For information on using Remote Configuration, see the Remote Service User Guide on InCenter.
Resend Analyzer
Resend Analyzer
NOTE This tool is only available for Brilliance 64 and Brilliance Big Bore.
This application enables analysis of the resends existing in the Data Path. There are log files in the CIRS S1 Server that
contain information regarding resends existing in the system.
Resend Analyzer
To use the Resend Analyzer:

Resend Analyzer
3. On the Application List, select Resend Analyzer.

4. A message appears asking if you want to copy the CIRS event logs to the Host PC. Click Yes to copy the log files
to the Host directory C:\TEMP\serviceTmp\DataPathAnalyzer\CIRS_evt_logs.
Figure 56:
5. The Resend Analyzer application will then open.
6. Click the Browse button (see Figure 57), and in the Open File dialog, select one or more files located in the
directory C:\TEMP\serviceTmp\DataPathAnalyzer\CIRS_evt_logs.
Figure 57:
Resend Analyzer
!
CAUTION Do not click the Analyze Button without manually selecting files first! YOU WILL NOT BE ABLE
TO STOP THE UTILITY ONCE THE ANALYSIS BEGINS. Clicking the Analyze Button without
manually selecting files first tells the utility to analyze all the event logs that were copied over,
and this could take quite a while.
7. Click the Analyze button to start the analysis process.
NOTE Do not attempt to close the Resend Analyzer tool while analysis is in progress. Doing so might cause the tool to
crash
8. The Analysis Report window shows an “Analyzing file..” message, and the bottom of the window displays a
“Parsing evt file...” message, along with a progress bar.
Figure 58: Figure 59:
9. When the process is complete some statistic and Result information appears.
Resend Analyzer
NOTE If a message appears in the Analysis Report window that says “The Data Path results are out of limits, corrective
action is recommended”, there is a problem and you will need to troubleshoot the system to find the reason for
the resends.
10. To export the results:
a. Click Export results button in the lower left corner of the Data Path Analyzer window.
b. Enter the file name, and browse to the directory C:\TEMP\serviceTmp\DataPathAnalyzer\CIRS_evt_logs, or
to other directory to save the Analysis report.
Rotor Profile
Rotor Profile
This tool is used to Display the Rotor Profile. Just choose the speed
you which to test and press the Start button. Low speeds are more
able to detect Unbalance problems.
Rotor Profile is a diagnostic tool. It does not configure the Rotor. This
tool can be used on an MDP/GMP/CGMP.
Rotor Profile gathers and displays information from the Rotor
Component (the exception is the ACC/JOG/DEC mode which draws
along the Min and Max requirements). We shall refer to the Rotor
component on the MDP/GMP/CGMP as RotorComp.
All the position displays are in Ticks only (not in Degrees). There are
42240 Ticks per rev.
Mode
Mode
There are 6 modes in this tool:
Acc/Jog/Dec
This mode profiles Acceleration, Jog, and Deceleration. Set the speed and select the data to collect while jogging, then
click the Start button. After a safety check, Rotor Profile will collect and display the data along with Min and Max
Requirements (which are +/- 2% of the speed).
NOTE In this mode, the main display is the 'Display All'.
Position
This mode profiles a Position cycle. Set the Position to go to, and select the data to collect after positioning, then click
the Start button. After a safety check, Rotor Profile will collect and display the data.
NOTE In this mode, there are two displays, Position and Volts.
Hint: If you put a Position value of more than 360, then Rotor Profile will not ask the rotor to position, it will only collect
the amount of data specified in the nb Data to Collect after Positioning field. This is useful when using CanTrace for
positioning, or when you have a position error. Then, before issuing any other command to the rotor, you can open
Rotor Profile and use this hint to collect the latest positioning data that caused the error.
Stop
There is no profile for this mode, it only issues a STOP command to the rotor, and waits for a Stop Answer.
CoastDown
This mode profiles a CoastDown. Set the Speed (in general, the speed used is 120 RPM), then click the Start button.
After a safety check, Rotor Profile will collect and display the data.
NOTE In this mode, there are two displays, Speed, and Acc/speed (which is the friction).
Mode
Rotor Balance
This is another way for doing a rotor balance. This mode should be only used for test purposes, not for real calibration.
The method using the Service Tools GUI is the formal and more precise one. This mode collects rotor position data
while the rotor is jogging in a mode called Volts/Hertz mode, which is a mode in the SpindleBlok (where it does not
adjust its speed).
You set the Speed and the number of data to collect (keep the speed at 40 RPM and nb Data to 115s of data if you want
to use the Matlab tool to calculate the Unbalance), then click the Start button. After a safety check Rotor Profile will
perform the following steps:
1- A special Jog command in V/H mode is sent to the Gantry with the requested speed.
2- After the Rotor has reached the speed, the tool shall wait the amount of time specified by you.
3- Rotor Profile will collect the Data.
4- Rotor Profile will copy a position text file 'rotorBalance.txt' in the C:\matlab directory and it will display the speed
profile.
5- You then have to go to the C:\matlab directory and double-click on Matlab_Runtime.bat.
6- In the Select a Calibration Type drop-down menu, select Rotor Balance.
7- Click on Browse (and select All Files (*.*) in the 'Files of Type') and choose the rotorBalance.txt file.
8- Click on Calibrate, and you will see the display for the Rotor Unbalance.
NOTE In this mode, there is one display which is the speed.
Collect Data
This mode collects the latest position data of the last command issued to the rotor. You have to choose nb Data to
Collect, then click the Start button. Rotor Profile will not send any move command to the rotor, it will only collect the
Data for time specified by you. Rotor Profile will then display the position and speed for the data collected.
Hint: This mode is useful when you have a 'NO_MORE_AT_SPEED' error. Then, without sending any other command
to the rotor, you can open Rotor Profile, select this mode, decide upon the amount of data to collect, then look at the
profile to have an idea why this error happened.
NOTE In this mode, there are two displays, Position and Speed.
Estop Status
Estop Status
This field is only a status about the Estop mode of the Gantry. It has 3 modes:
Unknown: The tool has not yet detected any status related to the Estop from the Gantry.
Closed: The tool has detected that the Estop is Closed.
Open: The tool has detected that the Estop is Open.
Start Button
Press this button whenever you want the tool to begin the process of collecting data (with or without moving the rotor),
and displaying the data.
Abort the Rotor Profile Button

Press this button whenever you want to Abort the Rotor/Data Collection operation.
Partial Display
When this field is checked, Rotor Profile will display only the events that happened between the Data from and To
fields. You must click on one of the Display buttons for the modifications to take effect.
Data from: Starting Time (in 10 ms) for the display. The Partial Display check Box has to be checked in order to
modify this field.
To: End Time (in 10 ms) for the display. The Partial Display check Box has to be checked in order to modify
this field.
Display area
Display area
The X Axis of the display area is always the Time. 1 time value is 10ms (which is the rate the data is collected in the
RotorComp), so a difference of 100 on the X Axis is equal to 1s. When the Partial Display check box is not checked,
Rotor Profile will display the whole range of time. When it is checked, Rotor Profile will only display the time specified in
the Data from and To.
The Y Axis of the display area depends on the type of Data Displayed. Rotor Profile will adjust the Y Axis range to the
Min and Max values of all the Data selected for display.
Files
The data collected from the RotorComp is stored in a .txt file with a specific format before being displayed. These files
reside in:
C:\usr\diamond.root\bin\ServiceTools\help\HelpRotorProfilePage_files
Software Distribution
Software Distribution
The application allows you to manually download and install available software packages. You can also see if any
software packages were automatically downloaded to the Host computer. The packages are limited to 100 mB in size,
and these include help files, Hot fixes, and config files.
2. You must have completed Remote Configuration first.
3. Click the Repair Workflow button at the top of the window.
4. On the Application List, select Software Distribution.
For more information on using Software Distribution:

• Manual Software Download on page 242
• Manually Install Software on page 243
• Automatic Software Download Notes on page 246
Manual Software Download
Manual Software Download

1. On the menu tree, click on Download to see if there are software packages available. You will see a list similar to
the one shown below.
2. Click on the check box to select the package, then click the Download button.
Figure 60:
Manual Download Notes

• To cancel a software package download, click the Cancel button. When you cancel a package download, the
Status will update accordingly.
Figure 61:
• To temporarily suspend a software package download, click the Suspend button. The Status will update
accordingly (see Figure 62 on page 242. To restart the download click the Download button. The download will
start again from the point of suspension.
Figure 62:
Manually Install Software

1. On the menu tree, click on Install to see if any Software packages are available.
2. If software packages are available, click on the check box to select the package, then click the Install button at the
bottom of the window.
Figure 63:
3. A confirmation dialogue box appears. Click Yes.
Figure 64:
4. To install the software, on the Installation Wizard click Resume, then Next.
.
Figure 65:
5. Follow the instructions on the Installation Wizard.
Manual Install Notes

• To cancel a software package installation, click the Cancel button on the Installation Wizard. When you cancel a
package installation, the Status will update accordingly (see Figure 66).
Figure 66:
• For additional information, you can click the icon that is next to the component in the list. This will display the
Additional Information window (see Figure 67). Click OK to close the window.
Figure 67:
Automatic Software Download Notes
Automatic Software Download Notes

• Automatic download of packages only happens when the system is in clinical and also idle mode.
• Automatic download of packages does not have any user interface.
• When the system is in idle mode the automatic download process is fired and the download of the packages
happen one by one.
• When download of a package is on process, if the system comes back to non-idle mode then download of a
package will be stopped and the process is killed.
• You can know the status of the packages downloaded automatically by viewing the PSUS viewer in service mode.
SpindleBlok Commissioning
SpindleBlok Commissioning
On InCenter, see “SpindleBlok Repair and Replacement” in the Gantry Repair and Replacement Manual for your
system. The SpindleBlok Repair and Replacement procedure includes SpindleBlok Commissioning. This will ensure
that you have the latest version of the commissioning procedure.
System Configuration
System Configuration
• View the Expected and Current version of the software on Gantry, Couch, DMS, and CIRS components.
• Program the Boot and Application Flash on the Couch Controller Board, GHost, RHost, GMP, and DMC.
Go to: View the Expected and Current Values of the Component Software on page 249
Programming Components with System Configuration on page 250.
View the Expected and Current Values of the Component Software
View the Expected and Current Values of the Component Software

1. Log on as philips_service.
2. Turn the keyswitch on the CT Box to open E-Stop.
3. On the Host desktop, double-click the Service Tools icon to launch the Service
Tools Framework.
4. On the Service Tools Framework, click the Analysis Workflow button.
5. On the Application List, click System Configuration.
6. The application opens, and automatically reads and displays the Expected Values (it takes about 30 seconds to
complete this action).
7. Click Verify.
8. When verification completes, the application shows any deviations in red.
Deviations are shown in

red.
Programming Components with System Configuration

1. Log on as philips_service.
2. Turn the keyswitch on the CT Box to open E-Stop.
3. On the Host desktop, double-click the Service Tools icon to launch the Service
Tools Framework.
4. On the Service Tools Framework, click the Analysis Workflow button.
5. On the Application List, click System Configuration.
6. The application opens, and automatically reads and displays the Expected Values (it takes about 30 seconds to
complete this action).
7. When the application is ready, you can program components:
• For Gantry and Couch components, click on uCT.Gantry.All.
• For DMS Components, click on both Dms.dmc.BootFlash and Dms.dmc.ApplicationFlash.
8. Click Program.
9. When the E-stop Message appears, make sure E-Stop is open, then click Yes.
10. The application starts programming the components. Gantry and couch component programming takes about
seven minutes to complete, while DMS component programming takes about five minutes to complete.
11. The Progress and Status bars show the percentage complete, and what the application is doing at that moment.
Figure 68: Progress Bar

Figure 69: Status Bar
12. When the application finishes programming, Success appears in the Result box.
NOTE Ignore any messages in the Status Bar. The messages do not clear when programming finishes.
13. Click Back.
14. You must reboot the Gantry!

15. After the Gantry Reboots, click Verify to make sure there are no deviations.
Tilt Calibration
Tilt Calibration
On InCenter, see the “Tilt Calibration” procedure in the v3.6 Calibration Manual for your system. This will ensure that
you have the latest version of the calibration procedure.
Tilt Profile
Tilt Profile
Tilt Profile gathers information from the Tilt Component and displays it. This tool is a diagnostic tool only. It does not
configure or calibrate the Tilt component on the GMP/CGMP.
Quick Configuration
Quick Configuration
For a quick configuration, and to draw a quick Tilt profile:
1. Keep all the default values, and change the targetPosition(10th deg) to the desired tilt angle in tenths of degrees
(for example,15º = 150).
2. Click on the Start button.
3. When prompted, press and hold the Enable button on the CT-Box until the Tilt reaches its position. At that point,
you can release the Enable button, and the tool will collect the Data and display it.
Encoders
These are two angle counters (one for the right side and one for the left) that the Tilt FPGA uses to adjust the speed of
the right and left actuators. Providing the FPGA has the correct version, Tilt Profile can retrieve the Encoder values. In
order to support old versions of Tilt FPGA, the Tilt Profile does not read the Encoder values by default. You have to click
on the Enable Encoder Collection button to enable the Tilt Profile to read the Encoder values. If at that point, the
GMP/CGMP resets, it means that it has an old FPGA code that does not support Encoder reading.
By default, the FPGA automatically resets the Equilibrium (which is the difference between right and left encoders) to
ensure a proper synchronization of the Actuators. For test purposes, you can manually reset the Equilibrium, or put the
Equilibrium reset in Manual mode.
Data To Collect
Tilt Profile will collect data for all the following check boxes that you select:
Pot1: Main Pot (also known as Pot1).
Encoders: Right and Left Encoders and Equilibrium (Make sure to click on the Enable Encoder Collection
button if you checked this box).
State Machine: Mainly used for Engineering debugging.
Control: Mainly used for Engineering debugging.
Status: Mainly used for Engineering debugging.
Mode
Mode
Tilt Profile has the following modes:
AutoMode
In this mode, set the targetPosition (in tenths of a degree), Speed (in tenths of a degree per second, and not the same
value as targetPosition), and the number of seconds (Nb Data to Collect after Positioning) you want the tool to wait
after reaching position before collecting the Data.
After making your selections, press the Start button. Tilt Profile will then prompt you to press the Enable button on the
CT-Box. Press and hold this button until the Tilt reaches its position. At that point, you can release the Enable button.
Tilt Profile will collect data from the time the Tilt starts to jog, until it reaches the targetPosition (plus the time specified in
the Nb Data to Collect after Positioning check box). Tilt Profile will then display the data at the bottom of the frame.
NOTE If the Estop opens (or the MDC opens) while tilting, abort the test and collect the data using the Collect Latest
Data Mode (see below). In this case, you shall have to specify enough time to cover the time the Tilt started until
the Estop.
Collect Last Data

In this mode, you only have to specify the number of seconds of data you want the tool to collect, then press the Start
button.
NOTE Tilt Profile is always collecting (at least) the Pot1 value every 10 ms. The value(s) are put in a buffer until it
reaches what is worth 50 seconds of Data. This Data is re-written every time you issue a new Jog command
(regardless if it is Manual or Auto). The Data will always be in the buffer until the next Jog command. You can
collect this Data anytime (regardless of the Estop state) by using the 'Collect Latest Data' mode.
Real Time
This Mode is for Future development.
Estop Status
Estop Status
This field is only a status about the Estop mode of the Gantry, and has three modes:
Unknown: The tool has not yet detected any status related to the Estop from the Gantry.
Closed: The tool has detected that the Estop is Closed.
Open: The tool has detected that the Estop is Open.
Tilt Position
This field displays the position of the Tilt in 10th of degrees, and has two modes:
Unknown: The tool has not yet detected any Tilt position.
Specific Value: The tool has detected that the tilt is at the Specific Value.
Start Button
Press this button to begin collecting and displaying data (with or without Tilting).
Abort Tilt Profile Button

Press this button to abort the Tilt/Data Collection.
Data To Display
Data To Display
This filed has a lot of options. Whenever an option changes, you have to click on the Refresh Display button for the
modifications to take effect. Tilt Profile will display data for all the following check boxes that you select:
Pot1: Displays the raw value of the Main Pot as collected by Tilt Profile.
Pot1Deg: Converts Pot1 value to Degree and displays it.
DegMA (MovAvg): Runs a Moving Average filter on Pot1Deg and displays it.
SpeedMA(Periodic): Converts Pot1Deg to speed, runs a Moving Average filter on it and displays it.
Speed: Displays the raw speed calculated from Pot1Deg. This speed is very noisy because of the low
precision of the Pot and the speed we are collecting the data.
Right Encoder: Displays the raw values collected from the Right Encoder.
Left Encoder: Displays the raw values collected from the Left Encoder.
Equilibrium: Displays the raw values collected from the Equilibrium.
Torque: Displays the torque applied by the Actuators to tilt the Gantry (Not Available yet).
Control: Reserved for Engineering debugging
Status: Reserved for Engineering debugging
Partial Display
When this field is checked, Tilt Profile will display only the events that happened between the Data from and To
settings. You have to click on the Refresh Display button for the modifications to take effect.
Data from: Start Time (in 10 ms) for the display. The Partial Display check Box has to be checked in order to modify
this field.
To: End Time (in 10 ms) for the display. The Partial Display check Box has to be checked in order to modify
this field.
Min Y Axis
Min Y Axis
When this field is checked, Tilt Profile will adjust the display so that the Y Axis has a Minimum Value near to the value
you entered in the field. You have to click on the Refresh Display button for the modifications to take effect.
Max Y Axis
When this field is checked, Tilt Profile will adjust the display so that the Y Axis has a Maximum value near to the value
you entered in the field. You have to click on the Refresh Display button for the modifications to take effect.
Display area
The X Axis of the display area is always the Time. 1 time value is 10ms (which is the rate the data is collected), so a
difference of 100 on the X Axis is equal to 1s. When the Partial Display check Box is not checked, the Tilt Profile will
display the whole range of time. When it is checked, Tilt Profile will only display the time specified in the Data from and
To.
The Y Axis of the display area depends on the boxes checked in the Data To Display area. If the Min Y Axis and the
Max Y Axis check boxes are not checked, Tilt Profile will adjust the Y Axis range to the Min and Max values of all the
Data selected for display. Otherwise, Tilt Profile will adjust the Y Axis to the values specified in one or both check boxes.
Files
The Data collected is stored in .txt files with a specific format before being displayed. These files reside in:
C:\usr\diamond.root\bin\ServiceTools\help\HelpTiltProfilePage_files.
A History file is also created that logs the time, date and the type of the test. It also logs the configuration and
Calibration data of the TiltComp.
Tube History Form
Tube History Form

This tool allows you to create a Tube History Report for every time you service the X-ray Tube and/or Generator
system.
To use the Tube History Form:
3. On the Application List, select Tube History Form.
4. Enter all the relevant information in the fields, then click Save Report.
Figure 70: Top portion of the Tube History Form
Tube History Report
Tube History Report

When you create a Tube History report, the results are shown in the bottom portion of the window. You will have to scroll
down to see it all.
Figure 71: Bottom portion of Tube History showing the Tube History report.
Tube History Tool
Tube History Tool

The Tube History Tool shows information on the current tube, and any previous tubes that were installed on the system.
The tool initially displays the Total System Scan Seconds and Total System Shots Count.
Current Tube
Click on Current Tube, and the X-Ray Tube Summary at the top shows the following information for the current tube:
Tube Install Date Total Scan Seconds Total_mA_Seconds

Tube Type Total System Shots Count Total Large Arcs Count
Total Shots Count Total System Scan Seconds Total Soft Arcs Count
Tube History Tool
Click the GetShotsData button to view the following X-Ray Tube Shots Data.
Shot End Tube Voltage_100V Generator Shot Status

Series ID Filament Current in milliampere (mA) Nominal Duration in milliseconds (mS)
Scan Duration in milliseconds (mS) Soft Arc Count Nominal Current in milliampere (mA)
Shot Count Table Motion Nominal Voltage in kiloVolts (kV)
Series Count Tilt position Spot Size
Tube Heat Percentage Gantry Rotation in milliseconds (mS) Tube Heat in kilojoules (kJ)
Average Tube Current in milliampere (mA) Hard Arc Series Retries
Tube History Tool
Plot Arcs
If the X-Ray Tube Shots Data has any values in the Hard Arc column, click Plot Arcs/Day.
You will see a plot of the hard arcs and when they occurred.
Figure 72: Hard Arcs Plot
Tube History Tool
Export Tube Data

You can export the Tube Data to a .csv file.
1. Click Export.
2. On the Save X-Ray Tube Shots Data dialog, browse to the location of your external media.
3. Click Save.
Tube History Tool
Old Tubes
Click on Old Tubes, then click the GetAllTubeSummary button to view the tube summary for tubes that were
previously installed on the system.
Update Tube History Database

You would only use this function when updating from an earlier version of software.
Universal Log Viewer
Universal Log Viewer
The Universal Log Viewer gathers all logs and messages generated by the system. You can you can query specific
messages on any of the log files gathered by the viewer. The Message Display Area then lists the messages, and
allows you to view all the information for a specific message.
Show Panel displays the Query Panel. To only view the Message Area, uncheck this box.
Time From To
This allows you to see all the messages within a specific time frame.
1. Enter the From time in the left-hand field.
2. Enter the To time in the right-hand field.
3. Click the Apply button.
Query Messages
Query Messages
There are two ways to query specific messages:
1. The first way is to select a single file group from the drop-down menu. WEventsApp and WEventsSys are
Microsoft Windows logs. MDB shows the Stargate.Errors.MDB file.
Then select a query from the Query Info drop-down menu to perform on the File Group you selected above. All
queries that appear in the menu list are specific to the File Group you selected.
Query Messages
2. The second way is to select the Combine Logs check box on the main window. This will list all of the file groups at
once, and allow you to select a query for each file group. After making your selections, click the Apply Selection
button to view the messages.
View Messages
View Messages
The messages appear in the Display Area.
To view information for a specific message, click the Info button. You will see the following display.
Save/Open Files
Save/Open Files
Save Files
After you have selected a file group(s) and queries, you can save the messages for viewing later.
1. Click the Save View As button.
2. In the Path Window, browse to where you want to store the file.
3. In the File Name box, enter a file name.
4. Click the OK icon.
NOTE If the file is saved as .xml, when you want to view it again, you have to first select XML under File Groups, then
click the Open File button and browse to your saved file.
Open Files
When you select a file group on the main page, Universal Log Viewer automatically opens the default log file. The
default log file is limited to certain number of entries. When the default log file is full, Universal Log viewer creates a
backup of the default log file, and clears out the messages so the log file can receive new messages.
With Open File, you can open and view backup or other log files, and Views that you have saved.
Save/Open Files
To open a file:
1. Click the Open File button on the main page.
2. To open the following log files, browse to their listed location:
• Data Logger - D:\Data_Logger\LoggerQueries.mdb
• UspLog - D:\usp.data\log\usplog.log
• TamarLog - C:\usr\tmp\TAMAR_LOG
• WEventsApp - D:\Data_Logger\BlobInfo.xsd
• WEventsSys - localhost\WindowsEvent\System
• CIRS_1 - <192.168.0.200>\WindowsEvent\CIRS
• CanTrace - D:\Data_CanTrace\CanTrace.mdb
• ShotsHistory - D:\Data_TubeHistory\ShotsHistory.mdb
• MDB - D:\Data_Logger\Stargate_Errors.mdb
• XML - D:\Data_Logger\BlobInfo.xml
3. Click on the file you want to open.
4. Click on the OK icon .
Query Wizard
Query Wizard
The Query Wizard allows you to create new queries, or modify existing ones.
1. On the Main Page, select a File Group from the drop-down menu. The query you create will appear in the Query
Info menu list for this specific File Group.
2. Click the AddNew Button. The new query will appear at the top of the list.
3. In the Query Name field, enter a name for the query.
4. In the Query Info field, enter text that describes the query.
5. In the SQL field, enter SQL commands to build the query. For help on SQL, see Appendix A: Tips on how to use
SQL for queries on page 281.
6. Click Update to add the query to the Query Info menu list associated with the file listed in File Group. Note: The
Test button is not functional at this time.
Edit allows you to modify exiting queries.

1. Click on Edit in the query you want to modify.
2. Modify the fields in the query.
3. Click Update to save the changes and update the query. Click Cancel to not make any changes and leave the
query with the original information intact.
Delete will delete the selected query from the Query Info menu list. It also deletes the query from the Query Wizard list.
URL Restriction
URL Restriction
URL Restriction Configuration allows you to add to the list of approved websites the system can access.
3. On the Application List, select URL Restriction.
4. In the Allow this website field, enter the website address.
5. Click Add.
NOTE To delete a website from the list of approved websites, click on the website in the list, then click the Delete
button.
View Logs with markers
View Logs with markers

Markers allow you to flag an entry or multiple entries in the Error Log Viewer so you can locate the entries easily.
Functionally, View Logs with markers is the same as the other View Logs tool in Service Tools, with the addition of the
Markers. You can place a marker on single or multiple entries (see Place a marker on single or multiple entries on page
277), and you can also change the mark and search functions of the columns (Mark and search based on any column
on page 278). For a description of the Marker buttons, Marker Functions on page 275.
To use View Logs with markers:
3. On the Application List, select View Logs with markers.
Marker Functions
Marker Functions
The following table lists each button and the function.
Set sound marker for selected entry.
Jump to the previous marker.
Jump to the next marker.
Remove marker from selected entry.
Clear all markers from view.
Set markers. This will open two more buttons: Marks all entries of the same type , and Marks selected entry
only .
Jump to the previous marker found.
Find a string in a [*] column.
Jump to the next marker found.
Marker Functions
Clear all content from ListView. This will clear messages and all.
Stop update view
Open saved markers profile.
Save markers profile to a file.
Show properties of View Control. This allows you to set markers on different columns (see Mark and search based on any
column on page 278).
Place a marker on single or multiple entries
Place a marker on single or multiple entries

1. In the tool, highlight the line of interest (or lines of interest by holding CTRL and selecting multiple lines).
2. Click on the Set Markers button .

3. Two buttons appear to the right of the Set Markers button:
• To select a single entry, click on the Marks selected entry only button
• To select multiple entries, click on the Marks All Entries of The Same Type button
4. Select the desired marker from the display area.
Markers
5. Click on the Set Markers button again to set the markers. Only the selected line(s) will be highlighted.
Mark and search based on any column

You can set a marker in any column, but you have to change the default Marker Column setting first. The columns are
numbered from left to right, start at 1. The following example shows how to change the Marker Column setting to the
ErrNum column.
1. With View Logs with markers open, under the Filters area, apply the desired filter and columns you want to
display.
2. Click on the Show Properties of View Control icon .

3. On the STViewCtrl Class Properties window that appears, change the Marker Column value to 6 (to match the
ErrNum column number).
4. Click OK.
5. Notice that the [m] is moved to the ErrNum column.
6. Highlight the desired error message, and set the marker (see Place a marker on single or multiple entries on page
277).
7. Repeat the same steps for the Search column.
X-Ray Performance Tests
X-Ray Performance Tests
On InCenter, see the either Brilliance 64 Image Quality and Dose Testing Instructions or the Brilliance 16-slice or
Brilliance Big Bore System Performance Manual for your system. This will ensure that you have the latest version of the
X-Ray Performance Test procedures.
Appendix A: Tips on how to use SQL for queries
Appendix A: Tips on how to use SQL for queries
Using Data Manipulation Language

DML is all about working with the data that is stored in the database tables. Not only is DML used for retrieving the data,
it is also used for creating, modifying, and deleting it.
Retrieving Records
The most basic and most often used SQL statement is the SELECT statement. SELECT statements are the workhorses
of all SQL statements, and they are commonly referred to as select queries. You use the SELECT statement to retrieve
data from the database tables, and the results are usually returned in a set of records (or rows) made up of any number
of fields (or columns). You must designate which table or tables to select from with the FROM clause. The basic
structure of a SELECT statement is:
SELECT field list
FROM table list
To select all the fields from a table, use an asterisk (*). For example, the following statement selects all the fields and all
the records from the customers table:
SELECT *
FROM tblCustomers
To limit the fields retrieved by the query, simply use the field names instead. For example:
SELECT [Last Name], Phone
FROM tblCustomers
To designate a different name for a field in the result set, use the AS keyword to establish an alias for that field.
SELECT CustomerID AS [Customer Number]
FROM tblCustomers
Restricting the Result Set

More often than not, you will not want to retrieve all records from a table. You will want only a subset of those records
based on some qualifying criteria. To qualify a SELECT statement, you must use a WHERE clause, which will allow you
to specify exactly which records you want to retrieve.
SELECT *
FROM tblInvoices
WHERE CustomerID = 1
Note the CustomerID = 1 portion of the WHERE clause. A WHERE clause can contain up to 40 such expressions, and
they can be joined with the And or Or logical operators. Using more than one expression allows you to further filter out
records in the result set.
SELECT *
FROM tblInvoices
WHERE CustomerID = 1 AND InvoiceDate > #01/01/98#
Note that the date string is enclosed in number signs (#). If you are using a regular string in an expression, you must
enclose the string in single quotation marks ('). For example:
SELECT *
FROM tblCustomers
WHERE [Last Name] = 'White'
If you do not know the whole string value, you can use wildcard characters with the Like operator.
SELECT *
FROM tblCustomers
WHERE [Last Name] LIKE 'W*'
There are a number of wildcard characters to choose from, and the following table details what they are and what they
can be used for.
Wildcard character Description
* or % Zero or more characters
? or _ (underscore) Any single character
# Any single digit (0-9)
[charlist] Any single character in charlist
[!charlist] Any single character not in charlist
NOTE The % and _ (underscore) wildcard characters should be used only through the Jet OLE DB provider and
ActiveX® Data Objects (ADO) code. They will be treated as literal characters if they are used though the Access
SQL View user interface or Data Access Objects (DAO) code.
For more information about using the Like operator with wildcard characters, type wildcard characters in the Office
Assistant or on the Answer Wizard tab in the Microsoft Access Help window, and then click Search.
Sorting the Result Set

To specify a particular sort order on one or more fields in the result set, use the optional ORDER BY clause. As
explained earlier in the "Working with Indexes" section, records can be sorted in either ascending (ASC) or descending
(DESC) order; ascending is the default.
Fields referenced in the ORDER BY clause do not have to be part of the SELECT statement's field list, and sorting can
be applied to string, numeric, and date/time values. Always place the ORDER BY clause at the end of the SELECT
statement.
SELECT *
FROM tblCustomers
ORDER BY [Last Name], [First Name] DESC
You can also use the field numbers (or positions) instead of field names in the ORDER BY clause.
SELECT *
FROM tblCustomers
ORDER BY 2, 3 DESC
For more information about using the ORDER BY clause, type ORDER BY clause in the Office Assistant or on the
Answer Wizard tab in the Microsoft Access Help window, and then click Search.
Using Aggregate Functions to Work with Values

Aggregate functions are used to calculate statistical and summary information from data in tables. These functions are
used in SELECT statements, and all of them take fields or expressions as arguments.
To count the number of records in a result set, use the Count function. Using an asterisk with the Count function
causes Null values to be counted as well.
SELECT Count(*) AS [Number of Invoices]
FROM tblInvoices
To count only non-Null values, use the Count function with a field name:
SELECT Count(Amount) AS
[Number of Valid Invoice Amounts]
FROM tblInvoices
To find the average value for a column or expression of numeric data, use the Avg function:
SELECT Avg(Amount) AS [Average Invoice Amount]
FROM tblInvoices
To find the total of the values in a column or expression of numeric data, use the Sum function:
SELECT Sum(Amount) AS [Total Invoice Amount]
FROM tblInvoices
To find the minimum value for a column or expression, use the Min function:
SELECT Min(Amount) AS [Minimum Invoice Amount]
FROM tblInvoices
To find the maximum value for a column or expression, use the Max function:
SELECT Max(Amount) AS [Maximum Invoice Amount]
FROM tblInvoices
To find the first value in a column or expression, use the First function:
SELECT First(Amount) AS [First Invoice Amount]
FROM tblInvoices
To find the last value in a column or expression, use the Last function:
SELECT Last(Amount) AS [Last Invoice Amount]
FROM tblInvoices
For more information about using the aggregate functions, type SQL aggregate functions in the Office Assistant or on
the Answer Wizard tab in the Microsoft Access Help window, and then click Search.
Grouping Records in a Result Set

Sometimes there are records in a table that are logically related, as in the case of the invoices table. Since one
customer can have many invoices, it could be useful to treat all the invoices for one customer as a group, in order to find
statistical and summary information about the group.
The key to grouping records is that one or more fields in each record must contain the same value for every record in
the group. In the case of the invoices table, the CustomerID field value is the same for every invoice a particular
customer has.
To create a group of records, use the GROUP BY clause with the name of the field or fields you want to group with.
SELECT CustomerID, Count(*) AS [Number of Invoices],
Avg(Amount) AS [Average Invoice Amount]
FROM tblInvoices
GROUP BY CustomerID
Note that the statement will return one record that shows the customer ID, the number of invoices the customer has,
and the average invoice amount, for every customer who has an invoice record in the invoices table. Because each
customer's invoices are treated as a group, we are able to count the number of invoices, and then determine the
average invoice amount.
Intermediate Data Manipulation Language
You can specify a condition at the group level by using the HAVING clause, which is similar to the WHERE clause. For
example, the following query returns only those records for each customer whose average invoice amount is less than
100:
SELECT CustomerID, Count(*) AS [Number of Invoices],
Avg(Amount) AS [Average Invoice Amount]
FROM tblInvoices
GROUP BY CustomerID
HAVING Avg(Amount) < 100

The article “Fundamental Microsoft Jet SQL for Access 2000" showed how to use SQL to retrieve and manage the
information stored in a database. In the sections that follow in this article, we discuss intermediate Data Manipulation
Language (DML) statements that will allow you to have even greater control over how information can be retrieved and
manipulated.
Predicates
A predicate is an SQL clause that qualifies a SELECT statement, similar to a WHERE clause, except that the predicate
is declared before the column list. Predicates can further restrict the set of records you are retrieving, and in some
instances filter out any duplicate data that may exist.
The ALL keyword

The ALL keyword is the default keyword that is used when no predicate is declared in an SQL statement. It simply
means that all records will be retrieved that match the qualifying criteria of the SQL statement. Returning to our invoices
database example, let's select all records from the customers table:
SELECT *
FROM tblCustomers
Notice that although the ALL keyword was not declared, it is the default predicate. We could have written the statement
like this:
SELECT ALL *
FROM tblCustomers
The DISTINCT keyword

The DISTINCT keyword is used to control how duplicate values in a result set are handled. Based on the column(s)
specified in the field list, those rows that have duplicate values in the specified columns are filtered out. If more than one
column is specified, it is the combination of all of the columns that is used as the filter. For example, if you query the
Customers table for distinct last names, only the unique names will be returned; any duplicate names will result in only
one instance of that name in the result set.
SELECT DISTINCT [Last Name]
FROM tblCustomers
It is important to note that the result set returned by a query that uses the DISTINCT keyword cannot be updated; it is
read-only.
The DISTINCTROW keyword

The DISTINCTROW keyword is similar to the DISTINCT keyword except that it is based on entire rows, not just
individual fields. It is useful only when based on multiple tables, and only when you select fields from some, but not all,
of the tables. If you base your query on one table, or select fields from every table, the DISTINCTROW keyword
essentially acts as an ALL keyword.
For example, in our invoices database, every customer can have no invoices, or one or more invoices. Let's suppose
that we want to find out how many customers have one or more invoices. We will use the DISTINCTROW keyword to
determine our list of customers.
SELECT DISTINCTROW [Last Name], [First Name]
FROM tblCustomers INNER JOIN tblInvoices
ON tblCustomers.CustomerID = tblInvoices.CustomerID
If we had left off the DISTINCTROW keyword, we would have gotten a row returned for every invoice each customer
has. (The INNER JOIN statement will be covered in a later section.)
SQL Expressions
The TOP keyword

The TOP keyword is used to return a certain number of rows that fall at the top or bottom of a range that is specified by
an ORDER BY clause. The ORDER BY clause is used to sort the rows in either ascending or descending order. If there
are equal values present, the TOP keyword will return all rows that have the equal value. Let's say that we want to
determine the highest three invoice amounts in our invoices database. We'd write a statement like this:
SELECT TOP 3 InvoiceDate, Amount
FROM tblInvoices
ORDER BY Amount DESC
We can also use the optional PERCENT keyword with the TOP keyword to return a percentage of rows that fall at the
top or bottom of a range that is specified by an ORDER BY clause. The code looks like this:
SELECT TOP 25 PERCENT InvoiceDate, Amount
FROM tblInvoices
ORDER BY Amount DESC
Note that if you do not specify an ORDER BY clause, the TOP keyword will not be helpful: it will return a random
sampling of rows.
For more information about predicates, type all, distinct predicates in the Office Assistant or on the Answer Wizard
tab in the Microsoft Access Help window, and then click Search.
SQL Expressions
An SQL expression is a string that is used as part of an SQL statement that resolves to a single value. You can use any
combination of operators, constants, literal values, functions, field names, controls, or properties to build your SQL
expressions. The article “Fundamental Microsoft Jet SQL for Access 2000" describes how you can use expressions in
WHERE clauses to qualify SQL statements; and in the following sections of this article, we examine different SQL
operators that can be used in expressions.
The IN operator
The IN operator is used to determine if the value of an expression is equal to any of several values in a specified list. If
the expression matches a value in the list, the IN operator returns True. If it is not found, the IN operator returns False.
Let's suppose that we want to find all shipping addresses that are in the states of Washington and Georgia. Although we
could write an SQL statement with a long WHERE clause that uses the AND logical operator, using the IN operator will
shorten our statement.
SQL Expressions
SELECT *
FROM tblShipping
WHERE State IN ('WA','GA')
By using the NOT logical operator, we can check the opposite of the IN operator. This statement will return all shipping
addresses that are not in Washington State:
SELECT *
FROM tblShipping
WHERE State NOT IN ('WA')
The BETWEEN operator

The BETWEEN operator is used to determine if the value of an expression falls within a specified range of values. If the
expression's value falls within the specified range, including both the beginning and ending range values, the
BETWEEN operator returns True. If the expression's value does not fall within the range, the BETWEEN operator
returns False. Let's suppose that we want to find all invoices that have an amount between $50 and $100 dollars. We'd
use the BETWEEN operator in the WHERE clause with the AND keyword that specifies the range.
SELECT *
FROM tblInvoices
WHERE Amount BETWEEN 50 AND 100
By using the NOT logical operator, we can check the opposite of the BETWEEN operator to find invoice amounts that
fall outside that range.
SELECT *
FROM tblInvoices
WHERE Amount NOT BETWEEN 50 AND 100
Note that the range can be in reverse order and still achieve the same results (BETWEEN 100 AND 50), but many
ODBC-compliant databases require that the range follow the begin-value-to-end-value method. If you plan for your
application to be scaled or upsized to an ODBC-compliant database, you should always use the begin-value-to-end-
value method.
SQL Expressions
The LIKE operator

The LIKE operator is used to determine if the value of an expression compares to that of a pattern. A pattern is either a
full string value, or a partial string value that also contains one or more wildcard characters. By using the LIKE operator,
you can search a field within a result set and find all of the values that match the specified pattern.
SELECT *
FROM tblCustomers
WHERE [Last Name] LIKE 'Johnson'
To return all customers who have a last name that starts with the letter J, use the asterisk wildcard character.
SELECT *
FROM tblCustomers
WHERE [Last Name] LIKE 'J*'
By using the NOT logical operator, we can check the opposite of the LIKE operator and filter out all the Johnsons from
the list.
SELECT *
FROM tblCustomers
WHERE [Last Name] NOT LIKE 'Johnson'
There are a variety of wildcard characters that you can use in the LIKE operator patterns, as shown in the following
table.
Wildcard Character Description
* (asterisk) Matches any number of characters and can be used anywhere in the pattern string.
Matches any number of characters and can be used anywhere in the pattern string. (ADO and the Jet OLE
% (percent sign)
DB provider only)
? (question mark) Matches any single character and can be used anywhere in the pattern string.
Matches any single character and can be used anywhere in the pattern string. (ADO and the Jet OLE DB
_ (underscore)
provider only)
# (number sign) Matches any single digit and can be used anywhere in the pattern string.
Matches any single character within the list that is enclosed within brackets, and can be used anywhere in
[] (square brackets)
the pattern string.
! (exclamation point) Matches any single character not in the list that is enclosed within the square brackets.
- (hyphen) Matches any one of a range of characters that is enclosed within the square brackets.
SQL Expressions
NOTE The "%" and "_" wildcard characters in the previous table can be executed only through the Jet OLE DB provider
and ADO. They will yield an empty result set if used through the Access SQL View user interface.
For more information about wildcard characters, type wildcard characters in the Office Assistant or on the Answer
Wizard tab in the Microsoft Access Help window, and then click Search.
The IS NULL operator

A null value is one that indicates missing or unknown data. The IS NULL operator is used to determine if the value of an
expression is equal to the null value.
SELECT *
FROM tblInvoices
WHERE Amount IS NULL
By adding the NOT logical operator, we can check the opposite of the IS NULL operator. In this case, the statement will
weed out invoices with missing or unknown amounts.
SELECT *
FROM tblInvoices
WHERE Amount IS NOT NULL
Subqueries
Subqueries
A subquery is a SELECT statement that is used inside another SELECT, SELECT INTO, INSERT INTO, DELETE, or
UPDATE statement. It can help further qualify a result set based on the results of another result set. This is called
nesting, and since a subquery is a SELECT statement, you can also nest a subquery inside another subquery. When
you use a subquery in an SQL statement, it can be part of a field list, a WHERE clause, or a HAVING clause.
There are three basic forms of subqueries, and each uses a different kind of predicate.
The IN subquery
The IN subquery is used to check the value of a particular column against a list of values from a column in another table
or query. It is limited in that it can return only a single column from the other table. If it returns more than one column, an
error is returned. Using the invoices database example, let's write an SQL statement that returns a list of all customers
who have invoices.
SELECT *
FROM tblCustomers
WHERE CustomerID
IN (SELECT CustomerID FROM tblInvoices)
Using the NOT logical operator, we can check the opposite of the IN subquery and generate a list of customers who do
not have invoices.
SELECT *
FROM tblCustomers
WHERE CustomerID
NOT IN (SELECT CustomerID FROM tblInvoices)
Subqueries
The ANY/SOME/ALL subqueries

The ANY, SOME, and ALL subquery predicates are used to compare records from the main query with multiple rows
from the subquery. The ANY and SOME predicates are synonymous and can be used interchangeably.
Use the ANY or SOME predicate when you need to retrieve from the main query the set of records that satisfy the
comparison with any of the records in the subquery. Use the predicate just before the opening parenthesis of the
subquery.
SELECT *
FROM tblCustomers
WHERE CustomerID = ANY
(SELECT CustomerID FROM tblInvoices)
Notice that the result set returned by the SQL statement above is the same as the one returned by the example with the
IN subquery. What makes the ANY and SOME predicates different is that they can also be used with relational
operators other than Equals (=), such as Greater Than (>) or Less Than (<).
SELECT *
FROM tblCustomers
WHERE CustomerID > ANY
When you want to retrieve records from the main query that satisfy the comparison with all of the records in the
subquery, use the ALL predicate.
SELECT *
FROM tblCustomers
WHERE CustomerID > ALL
Subqueries
The EXISTS subquery

The EXISTS predicate is used in subqueries to check for the existence of values in a result set. In other words, if the
subquery does not return any rows, the comparison is False. If it does return one or more rows, the comparison is True.
SELECT *
FROM tblCustomers AS A
WHERE EXISTS
(SELECT * FROM tblInvoices
WHERE A.CustomerID = tblInvoices.CustomerID)
Note that in the previous SQL statement an alias is used on the tblCustomers table. This is so that we can later refer to
it in the subquery. When a subquery is linked to the main query in this manner, it is called a correlated query.
By using the NOT logical operator, we can check the opposite of the EXISTS subquery to obtain a result set of
customers who do not have any invoices.
SELECT *
FROM tblCustomers AS A
WHERE NOT EXISTS
(SELECT * FROM tblInvoices
WHERE A.CustomerID = tblInvoices.CustomerID)
For more information about subqueries, type SQL subqueries in the Office Assistant or on the Answer Wizard tab in
the Microsoft Access Help window, and then click Search.
Joins
Joins
In a relational database system like Access, you will often need to extract information from more than one table at a
time. This can be accomplished by using an SQL JOIN statement. A JOIN statement enables you to retrieve records
from tables that have defined relationships, whether they are one-to-one, one-to-many, or many-to-many.
INNER JOINs
The INNER JOIN, also known as an equi-join, is the most commonly used type of join. This join is used to retrieve rows
from two or more tables by matching a field value that is common between the tables. The fields you join on must have
similar data types, and you cannot join on MEMO or OLEOBJECT data types. To build an INNER JOIN statement, use
the INNER JOIN keywords in the FROM clause of a SELECT statement. Let's use the INNER JOIN to build a result set
of all customers who have invoices, plus the dates and amounts of those invoices.
SELECT [Last Name], InvoiceDate, Amount
ON tblCustomers.CustomerID=tblInvoices.CustomerID
ORDER BY InvoiceDate
Notice that the table names are divided by the INNER JOIN keywords and that the relational comparison is after the ON
keyword. For the relational comparisons, you can also use the <, >, <=, >=, or <> operators, and you can also use the
BETWEEN keyword. Also note that the ID fields from both tables are used only in the relational comparison, they are
not part of the final result set.
To further qualify the SELECT statement, we can use a WHERE clause after the join comparison in the ON clause. In
the following example, we have narrowed the result set to include only invoices dated after January 1, 1998.
SELECT [Last Name], InvoiceDate, Amount
WHERE tblInvoices.InvoiceDate > #01/01/1998#
Joins
In cases where you need to join more than one table, you can nest the INNER JOIN clauses. In this example, we will
build on a previous SELECT statement to create our result set, but we will also include the city and state of each
customer by adding the INNER JOIN for the tblShipping table.
SELECT [Last Name], InvoiceDate, Amount, City, State
FROM (tblCustomers INNER JOIN tblInvoices
ON tblCustomers.CustomerID=tblInvoices.CustomerID)
INNER JOIN tblShipping
ON tblCustomers.CustomerID=tblShipping.CustomerID
Note that the first JOIN clause is enclosed in parentheses to keep it logically separated from the second JOIN clause. It
is also possible to join a table to itself by using an alias for the second table name in the FROM clause. Let's suppose
that we want to find all customer records that have duplicate last names. We do this by creating the alias "A" for the
second table and checking for first names that are different.
SELECT tblCustomers.[Last Name],
tblCustomers.[First Name]
FROM tblCustomers INNER JOIN tblCustomers AS A
ON tblCustomers.[Last Name]=A.[Last Name]
WHERE tblCustomers.[First Name]<>A.[First Name]
ORDER BY tblCustomers.[Last Name]
Joins
OUTER JOINs
The OUTER JOIN is used to retrieve records from multiple tables while preserving records from one of the tables, even
if there is no matching record in the other table. There are two types of OUTER JOINs that the Jet database engine
supports: LEFT OUTER JOINs and RIGHT OUTER JOINs. Think of two tables that are beside each other, a table on
the left and a table on the right. The LEFT OUTER JOIN will select all rows in the right table that match the relational
comparison criteria, and it will also select all rows from the left table, even if no match exists in the right table. The
RIGHT OUTER JOIN is simply the reverse of the LEFT OUTER JOIN; all rows in the right table are preserved instead.
As an example, let's suppose that we want to determine the total amount invoiced to each customer, but if a customer
has no invoices, we want to show it by displaying the word "NONE."
SELECT [Last Name] & ', ' & [First Name] AS Name,
IIF(Sum(Amount) IS NULL,'NONE',Sum(Amount)) AS Total
FROM tblCustomers LEFT OUTER JOIN tblInvoices
GROUP BY [Last Name] & ', ' & [First Name]
There are a few things going on in the previous SQL statement. The first is the use of the string concatenation operator
"&". This operator allows you to join two or more fields together as one string. The second is the immediate if (IIF)
statement, which checks to see if the total is null. If it is, the statement returns the word "NONE." If the total is not null,
the value is returned. The final thing is the OUTER JOIN clause. Using the LEFT OUTER JOIN preserves the rows in
the left table so that we see all customers, even those who do not have invoices.
OUTER JOINs can be nested inside INNER JOINs in a multi-table join, but INNER JOINs cannot be nested inside
OUTER JOINs.
The Cartesian product

A term that often comes up when discussing joins is the Cartesian product. A Cartesian product is defined as "all
possible combinations of all rows in all tables." For example, if you were to join two tables without any kind of
qualification or join type, you would get a Cartesian product.
SELECT *
FROM tblCustomers, tblInvoices
This is not a good thing, especially with tables that contain hundreds or thousands of rows. You should avoid creating
Cartesian products by always qualifying your joins.
Joins
The UNION operator

Although the UNION operator, also known as a union query, is not technically a join, it is included here because it does
involve combining data from multiple sources of data into one result set, which is similar to some types of joins. The
UNION operator is used to splice together data from tables, SELECT statements, or queries, while leaving out any
duplicate rows. Both data sources must have the same number of fields, but the fields do not have to be the same data
type. Let's suppose that we have an Employees table that has the same structure as the Customers table, and we want
to build a list of names and e-mail address by combining both tables.
SELECT [Last Name], [First Name], Email
FROM tblCustomers
UNION
FROM tblEmployees
If we wanted to retrieve all fields from both tables, we could use the TABLE keyword, like this:
TABLE tblCustomers
UNION
TABLE tblEmployees
The UNION operator will not display any records that are exact duplicates in both tables, but this can be overridden by
using the ALL predicate after the UNION keyword, like this:
FROM tblCustomers
UNION ALL
FROM tblEmployees
Joins
The TRANSFORM statement

Although the TRANSFORM statement, also known as a crosstab query, is also not technically considered a join, it is
included here because it does involve combining data from multiple sources of data into one result set, which is similar
to some types of joins.
A TRANSFORM statement is used to calculate a sum, average, count, or other type of aggregate total on records. It
then displays the information in a grid or spreadsheet format with data grouped both vertically (rows) and horizontally
(columns). The general form for a TRANSFORM statement is this:
TRANSFORM aggregating function
SELECT statement
PIVOT column heading field
Let's suppose that we want to build a datasheet that displays the invoice totals for each customer on a year-by-year
basis. The vertical headings will be the customer names, and the horizontal headings will be the years. Let's modify a
previous SQL statement to fit the transform statement.
TRANSFORM
IIF(Sum([Amount]) IS NULL,'NONE',Sum([Amount]))
AS Total
SELECT [Last Name] & ', ' & [First Name] AS Name
FROM tblCustomers LEFT JOIN tblInvoices
GROUP BY [Last Name] & ', ' & [First Name]
PIVOT Format(InvoiceDate, 'yyyy')
IN ('1996','1997','1998','1999','2000')
Note that the aggregating function is the SUM function, the vertical headings are in the GROUP BY clause of the
SELECT statement, and the horizontal headings are determined by the field listed after the PIVOT keyword.
For more information about joins, type SQL joins in the Office Assistant or on the Answer Wizard tab in the Microsoft
Access Help window, and then click Search.

Service

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

Service

Uploaded by

Copyright:

Available Formats

Brilliance CT

16-slice, 64-slice, and Big Bore

v3.6 Service Tools User Guide

4598 001 96541

© 2012 Koninklijke Philips Electronics N.V. All Rights Reserved.

Attention symbol Radiation warning symbol

Laser warning symbol Biohazard warning symbol

Magnetism warning symbol Projectile warning symbol

Electrical warning symbol Do not touch

Diagnostic Imaging Systems - Mechanical-electrical Warning

Diagnostic Imaging Systems - Radiation Warning

DCF # Revision Date Comments

2025002 A September 2012 For release of 3.6.

This document was prepared by CT Service Innovation.

Service Tools Framework .............................................................................................................. 23

IST Security Dongle ...................................................................................................................... 27

Audio Test ..................................................................................................................................... 39

Backup and Restore ...................................................................................................................... 40

BugRep Collector .......................................................................................................................... 44

Bugrep Viewer ............................................................................................................................... 47

CAN Analyzer ................................................................................................................................ 54

CAN Send ...................................................................................................................................... 57

CAN Trace ..................................................................................................................................... 59

CIRS Diagnostic Viewer ................................................................................................................ 65

CIRS Visual Diagnostics ............................................................................................................... 66

Coast Down Test ........................................................................................................................... 79

Configuration Settings .................................................................................................................. 81

Connect To Baseboards ............................................................................................................... 114

Controller Board Troubleshooting ............................................................................................... 154

Couch Vertical Calibration ........................................................................................................... 169

CPM Reset .................................................................................................................................... 170

CPM Software Version Query Tool ............................................................................................... 171

DMS/Data Path Diagnostics ......................................................................................................... 172

DMS Tools .................................................................................................................................... 173

IBox Diagnostics .......................................................................................................................... 197

LAN Config ................................................................................................................................... 201

Manual Exposure .......................................................................................................................... 202

Map Drive (for Varian Computer) ................................................................................................. 210

No Load Test ................................................................................................................................ 212

Real Time Data ............................................................................................................................. 227

Remote Configuration .................................................................................................................. 230

Resend Analyzer .......................................................................................................................... 231

Rotor Profile ................................................................................................................................. 236

Software Distribution ................................................................................................................... 241

SpindleBlok Commissioning ........................................................................................................ 247

System Configuration .................................................................................................................. 248

Tilt Calibration ............................................................................................................................. 252

Tilt Profile .................................................................................................................................... 253

Tube History Form ....................................................................................................................... 259

Tube History Tool ......................................................................................................................... 261

Universal Log Viewer ................................................................................................................... 266

URL Restriction ............................................................................................................................ 273

View Logs with markers ............................................................................................................... 274

X-Ray Performance Tests ............................................................................................................. 280

Appendix A: Tips on how to use SQL for queries ........................................................................ 281

Service Tools Framework

Multiple Tabs in the Service Tools Framework

IST Security Dongle

Activating the Dongle

Install Cardman USB 6121 Driver

7. Once the installation has completed, click the Close button.

Install Safeguard SmartCard Provider

5. Once the installation has completed, click the Close button.