1813860

Prévia do material em texto

<p>BrillianceTM CT</p><p>6 - s l i c e , 1 0 - s l i c e , 1 6 - s l i c e a n d 1 6 P o w e r c o n f i g u r a t i o n s</p><p>Version 1.2.5</p><p>Model: 4535 670 73191, 4535 670 73181, 4535 670 78851, 4535 670 05721</p><p>O - L e v e l U t i l i t i e s M a n u a l</p><p>4535 671 33861</p><p>Revision B</p><p>© 2005 Philips Medical Systems</p><p>This document and the information contained in it is proprietary and confidential information of Philips Medical Systems (“Philips”) and may not be</p><p>reproduced, copied in whole or in part, adapted, modified, disclosed to others, or disseminated without the prior written permission of the Philips Legal</p><p>Department. Use of this document and the information contained in it is strictly reserved for current Philips personnel and Philips customers who have a</p><p>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.</p><p>Use of this document by unauthorized persons is strictly prohibited. Report violation of these requirements to the Philips Legal Department at 22100 Bothell</p><p>Everett Highway, Bothell, WA 98021.</p><p>This document must be returned to Philips when the user is no longer licensed and in any event upon Philips’ first written request.</p><p>Philips Medical Systems</p><p>© 2005 KONINKLIJKE PHILIPS ELECTRONICS N. V. ALL RIGHTS RESERVED.</p><p>Warranty Disclaimer</p><p>PHILIPS PROVIDES THIS DOCUMENT WITHOUT WARRANTY OF ANY KIND, EITHER IMPLIED OR EXPRESSED,</p><p>INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A</p><p>PARTICULAR PURPOSE.</p><p>Limitation of Liability</p><p>PHILIPS HAS TAKEN CARE TO ENSURE THE ACCURACY OF THIS DOCUMENT. HOWEVER, PHILIPS ASSUMES</p><p>NO LIABILITY FOR ERRORS OR OMISSIONS AND RESERVES THE RIGHT TO MAKE CHANGES WITHOUT</p><p>FURTHER NOTICE TO ANY PRODUCTS HEREIN TO IMPROVE RELIABILITY, FUNCTION, OR DESIGN. PHILIPS</p><p>MAY MAKE IMPROVEMENTS OR CHANGES IN THE PRODUCT(S) OR PROGRAM(S) DESCRIBED IN THIS</p><p>DOCUMENT AT ANY TIME.</p><p>Symbol Descriptions</p><p>Attention symbol Radiation warning symbol</p><p>Laser warning symbol Biohazard warning symbol</p><p>Magnetism warning symbol Projectile warning symbol</p><p>Electrical warning symbol Do not touch</p><p>Revision History</p><p>ECO # Revision Date Comments</p><p>A February 2005 New Release for Version 1.2</p><p>B May 2005 Manual clarifications for 1.2.5</p><p>Safety Information</p><p>To the User of This Manual</p><p>The user of this manual is directed to read and carefully review the instructions, warnings and cautions contained herein prior to</p><p>beginning installation or service activities. While you may have previously installed or serviced equipment similar to that described in this</p><p>manual, changes in design, manufacture or procedure may have occurred which significantly affect the present installation or service.</p><p>Installation and Environment</p><p>Except for installations requiring certification by the manufacturer per federal standards, see that a radiation protection survey is made</p><p>by a qualified expert in accordance with NCRP 102, section 7, as revised or replaced in the future. Perform a survey after every change</p><p>in equipment, workload, or operating conditions which might significantly increase the probability of persons receiving more than the</p><p>maximum permissible dose equivalent.</p><p>Diagnostic Imaging Systems - Mechanical-electrical Warning</p><p>All of the moveable assemblies and parts of this equipment should be operated with care and routinely inspected in accordance with the</p><p>manufacturer’s recommendations contained in the equipment manuals.</p><p>Only properly trained and qualified personnel should be permitted access to any internal parts. Live electrical terminals are deadly; be</p><p>sure line disconnects are opened and other appropriate precautions are taken before opening access doors, removing enclosure panels,</p><p>or attaching accessories.</p><p>Do not under any circumstances, remove the flexible high tension cables from the x-ray tube housing or high tension generator and/or the</p><p>access covers from the generator until the main and auxiliary power supplies have been disconnected. Failure to comply with the above</p><p>may result in serious or fatal bodily injuries to the operator or those in the area.</p><p>Electrical-grounding Instructions</p><p>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</p><p>earth ground. On equipment provided with a line cord, the equipment must be connected to properly grounded, three-pin receptacle. Do</p><p>not use a three-to-two pin adapter.</p><p>Diagnostic Imaging Systems - Radiation Warning</p><p>X-ray and Gamma-rays are dangerous to both operator and others in the vicinity unless established safe exposure procedures are strictly</p><p>observed.</p><p>The useful and scattered beams can produce serious or fatal bodily injuries to any persons in the surrounding area if used by an unskilled</p><p>operator. Adequate precautions must always be taken to avoid exposure to the useful beam, as well as to leakage radiation from within</p><p>the source housing or to scattered radiation resulting from the passage of radiation through matter.</p><p>Those authorized to operate, participate in or supervise the operation of the equipment must be thoroughly familiar and comply</p><p>completely with the current established safe exposure factors and procedures described in publications, such as: Subchapter J of Title 21</p><p>of the Code of Federal Regulations, "Diagnostic X-ray Systems and Their Major Components", and the national council on radiation</p><p>protection (NCRP) no. 102, "Medical X-ray And Gamma-ray Protection For Energies Up To 10 Mev-equipment Design and Use", as</p><p>revised or replaced in the future.</p><p>Those responsible for planning of x-ray and gamma-ray equipment installations must be thoroughly familiar and comply completely with</p><p>NCRP no. 49, "Structural Shielding Design and Evaluation For Medical Of X-rays and Gamma-rays of Energies Up to 10 Mev", as revised</p><p>and replaced in the future. Failure to observe these warnings may cause serious or fatal bodily injuries to the operator or those in the</p><p>area.</p><p>Add additional safety information as needed</p><p>Only qualified and system trained Philips service staff is allowed to perform service (installation, maintenance, quality assurance) on the</p><p>BrillianceTM CT systems. Make sure that the latest version of the service instructions are available. Read the corresponding instructions</p><p>carefully prior to working on the system. For your own safety and for more detailed safety information, refer only to the current version of</p><p>the documents.</p><p>Use only specified tools and auxiliary materials. After finishing any service activity, ensure that all covers of the BrillianceTM CT, including</p><p>the mylar gasket, are closed</p><p>Precautionary Measures Regarding Electrical Voltage</p><p>Before you start the procedure outlined in this manual, make sure that you read and understand the warnings listed below.</p><p>WARNING PRIOR TO ANY SERVICE AND MAINTENANCE ACTIVITIES INSIDE COMPONENTS:</p><p>SWITCH OFF THE SYSTEM AT THE MAIN POWER SUPPLY, (USING THE ON-SITE ON-OFF SWITCH)</p><p>AND THE INTERNAL/EXTERNAL UNINTERRUPTIBLE POWER SUPPLY (UPS).</p><p>MAKE SURE THAT NO OTHER PERSON CAN SWITCH ON POWER OR SWITCH OFF THE SECURITY</p><p>MEASURES, WHEN INSTALLATION, MAINTENANCE OR SERVICE WORK ON THE SYSTEM IS</p><p>PERFORMED.</p><p>WARNING IN ADDITION TO THE WARNINGS LISTED ABOVE, MAKE SURE TO FOLLOW ALL SAFETY</p><p>GUIDELINES AS DESCRIBED IN THE SAFETY CHAPTER OF THIS MANUAL. FAILURE TO DO SO</p><p>CAN RESULT IN SEVERE PERSONAL INJURY.</p><p>CAUTION Always use an ESD protection wrist strap when servicing any component in the system.</p><p>Philips Medical Systems Confidential and Proprietary Information I</p><p>Contents</p><p>O-Level Scanner Application Tools ................................................................................................... 1</p><p>Diagnostic Menu 1</p><p>Service parameters............................................................................................................................................. 1</p><p>Set Switch Procedure....................................................................................................................................</p><p>16 Power 1.2.5 O-Level Utilities Manual</p><p>A Plane Tab</p><p>Tables</p><p>The A Plane Tab is divided into three tables:</p><p>SW This is the calibration table for controlling the slice width of</p><p>the A Plane.</p><p>Z This the calibration table for controlling Z carriage motion.</p><p>Filter This is the calibration table for the filter section. Currently,</p><p>there is only one fixed filter, so there will not be any filter</p><p>calibration to enter into the table.</p><p>Fields</p><p>Each table has three fields:</p><p>Encoder Designates specific A Plane collimator openings.</p><p>Coarse and FineEncoder values from the coarse and fine modes of the encoder corresponding to the specific A Plane</p><p>collimator openings.</p><p>The 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,</p><p>and the coarse and fine grouping corresponds to the encoder grouping.</p><p>Buttons</p><p>GetAC Reads the current values in the NVRAM designated for A Plane calibration and loads the calibration into the</p><p>GUI.</p><p>Clear Sets all fields back to default values.</p><p>SetAC Writes the values in the GUI to the NVRAM.</p><p>Philips Medical Systems Confidential and Proprietary Information 36</p><p>DMC Host UtilityBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Reading the A Plane Calibration from File into the GUI</p><p>The Open JIG File button on the toolbar reads the calibration from media (disk, network, etc.) and loads the calibration into</p><p>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</p><p>to read:</p><p>1 Click the Open JIG File button on the toolbar.</p><p>2 Browse for the media that contains the calibration file, and click on the</p><p>calibration file for your A Plane.</p><p>3 Click the Open button.</p><p>4 Click the OK button.</p><p>5 The Status field will display GettingAC… while it reads the NVRAM and then</p><p>it will display GetAColl status is OK if the read was successful.</p><p>Manually Entering A Plane Calibration Into The GUI</p><p>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</p><p>the value in the field. There is a translation from calibration file to GUI, so having access to the calibration file does mean you</p><p>have access to the calibration data that needs to be entered into the GUI. If you have the calibration data from the GUI, then</p><p>you could manually reload the calibration data if you needed to.</p><p>Clearing the A Plane GUI</p><p>Click the Clear button on the A Plane tab, and the fields will update with the default values.</p><p>Writing A Plane Calibration To NVRAM</p><p>After loading calibration data into the A Plane tab, click the SetAC button. The Status field will display SettingAC… while it</p><p>writes the calibration, and then it will display SetAColl status is OK if the write was successful.</p><p>Philips Medical Systems Confidential and Proprietary Information 37</p><p>DMC Host UtilityBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Reading A Plane Calibration From NVRAM</p><p>On the A Plane tab, click the GetAC button. The Status field will display GettingAC… while it reads the calibration, and then it</p><p>will display GetAColl status is OK if the read was successful.</p><p>Figure 3 - 1: A Plane tab after successfully reading the calibration from NVRAM.</p><p>Entering The A Plane Serial Number</p><p>The second field on the Status Bar displays the A Plane serial number. Double-click on the Serial #: field in order to display</p><p>the serial number pop-up. Enter the A Plane serial number into the field, and click the OK button.</p><p>Philips Medical Systems Confidential and Proprietary Information 38</p><p>DMC Host UtilityBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>A Offsets Tab</p><p>Tables</p><p>The tab is divided into two tables.</p><p>SW This is the calibration table for controlling the slice width of the A</p><p>Plane.</p><p>Z This the calibration table for controlling Z carriage motion.</p><p>Fields</p><p>For each table there are four fields: CosCoarse, CosFine, SinCoarse</p><p>and SinFine. The default field entry is 511.</p><p>Buttons</p><p>GetAOffset Reads the current values in the NVRAM designated</p><p>for A Plane Offsets calibration and loads the calibration into the GUI.</p><p>Clear Sets all fields back to the default values.</p><p>SetAOffset Writes the values in the GUI to the NVRAM.</p><p>AutoOffset If the Automatic Offsets Button is ON (Green), and you press the SetAOffset button:</p><p>Philips Medical Systems Confidential and Proprietary Information 39</p><p>DMC Host UtilityBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>1 The settings currently displayed on the screen are saved to NVRAM.</p><p>2 A Reset is applied to the DMC.</p><p>3 The following window appears indicating that a reset is currently in progress:</p><p>4 Once the reset is complete, the DMC will go into Auto-Offset Mode. During this time, the following window appears:</p><p>5 Once the Automatic Offset is finished successfully, the new NVRAM values will appear in the A Offsets tab.</p><p>6 Another Reset is performed in order to complete the operation. The window shown in step 3 is shown again.</p><p>7 Once the Reset is complete, the values shown in the A Offsets tab will be operational on the DMC.</p><p>Status Bar</p><p>The Status Bar for the A Offsets tab is the same as the A Plane tab with the following exceptions:</p><p>• While reading, the Status field will display GettingOA…, and after successfully reading, the Status field will display</p><p>GetAOffsets status is OK.</p><p>• While writing, the Status field will display SettingOA…, and after successfully reading, the Status field will display</p><p>SetAOffsets status is OK.</p><p>Manually Entering A Offsets Calibration Into The GUI</p><p>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</p><p>the value in the field. There is a translation from calibration file to GUI, so having access to the calibration file does mean you</p><p>Philips Medical Systems Confidential and Proprietary Information 40</p><p>DMC Host UtilityBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>have access to the calibration data that needs to be entered into the GUI. If you have the calibration data from the GUI, then</p><p>you could manually reload the calibration data if you needed to.</p><p>Clearing the A Plane GUI</p><p>Click the Clear button on the A Offsets tab GUI, and the fields will update with the default values.</p><p>Philips Medical Systems Confidential and Proprietary Information 41</p><p>DMC Host UtilityBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>P Plane Tab</p><p>Tables</p><p>The P Plane tab is divided into two tables:</p><p>Encoder Contains the encoder values corresponding to the specific</p><p>P Plane collimator openings.</p><p>Station Designates specific P Plane collimator openings.</p><p>The default field entries are numbers ranging from 0 to 3. 0 signifies the first</p><p>cell and 3 signifies the last cell. Cells 0 - 3 in the Encoder table correspond</p><p>to 0 - 3 in Station table.</p><p>Column Headings</p><p>The column headings, 3 - 6, correspond to headings in the DMS P Plane</p><p>data sheet.</p><p>Buttons</p><p>GetPC Reads the current values in the NVRAM designated for P Plane calibration and loads the calibration into the</p><p>GUI.</p><p>Clear Sets all fields back to the default values.</p><p>SetPC Writes the values in the GUI to the NVRAM.</p><p>Status Bar</p><p>The Status Bar for the P Plane tab is the same as the A Plane tab with the following exceptions:</p><p>While reading, the Status field will display GettingPC…, and after successfully reading, the Status field will display GetPColl</p><p>status is OK.</p><p>While writing, the Status field will display SettingPC…, and after successfully reading, the Status field will display SetPColl</p><p>status is OK.</p><p>Philips Medical Systems Confidential and Proprietary Information 42</p><p>DMC Host UtilityBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>P Plane Data Sheet</p><p>The following is a sample P Plane data sheet distributed with the</p><p>DMS packet.</p><p>Philips Medical Systems Confidential and Proprietary Information 43</p><p>DMC Host UtilityBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Table 3 - 2 is the encoder calibration data from the data sheet. The third column, Encoder Measurements (Decimal) contains</p><p>encoder values corresponding to the positional data.</p><p>Table 3 - 3 is the positional calibration data from Figure 35. The third column, Station Measurements mm contains the</p><p>positional data.</p><p>Table 3 - 2: P Plane encoder calibration data</p><p>Encoder Required Range Encoder Measurements (Decimal) Encoder Measurements (Hexa)</p><p>1 (-300) - (-600) -398</p><p>2 0 - 4 2</p><p>3 850 - 1250 985 3D9</p><p>4 4030 - 4420 4168 1048</p><p>5 5950 - 6300 6088 17C8</p><p>6 6680 - 7150 6864 1AD0</p><p>7 7000 - 7350 7184</p><p>Table 3 - 3: P Plane positional calibration data</p><p>Station Name Station Measurements mm Station Measurements (Hexa)</p><p>1 LIMIT Sw. (OPEN)</p><p>2 INDEX</p><p>3 30 mm 30.08 1048</p><p>4 15 mm 15.05 1048</p><p>5 6 mm 5.99 17C8</p><p>6 2.5 mm 2.45 1AD0</p><p>7 LIMIT Sw</p><p>Philips Medical Systems Confidential and Proprietary Information 44</p><p>DMC Host UtilityBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Manually Entering The P Plane Calibration Into The GUI</p><p>Using the data in Table 3 - 2 and Table 3 - 3, manually enter the P Plane calibration into the P Plane tab. Double-click on a field</p><p>to edit it. The numbers in the first column of the tables corresponds to the column headings in the P Plane tab. From the tables,</p><p>enter the following data:</p><p>or, in the P Plane GUI format:</p><p>Table 3 - 4: P Plane calibration from P Plane data sheet</p><p>Column number Station Measurements mm Encoder Measurements (Decimal)</p><p>3 30.08 985</p><p>4 15.05 4168</p><p>5 5.99 6088</p><p>6 2.45 6864</p><p>Table 3 - 5: P Plane calibration in GUI format</p><p>GUI heading 3 4 5 6</p><p>Encoder 985 4168 6088 6864</p><p>Station 30.08 15.05 5.99 2.45</p><p>Philips Medical Systems Confidential and Proprietary Information 45</p><p>DMC Host UtilityBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>The following figure shows the P Plane tab with manually entered P Plane calibration. There is no status message while</p><p>entering the values so the last message will remain in the status field.</p><p>Clearing the P Plane GUI</p><p>Click the Clear button on the P Plane tab, and the fields will update with the default values.</p><p>Writing P Plane Calibration To NVRAM</p><p>After loading calibration data into the P Plane tab, click the SetPC button. The Status field will display SettingPC… while it</p><p>writes the calibration, and will then display SetPColl status is OK if the write was successful.</p><p>Reading P Plane Calibration From NVRAM.</p><p>On the P Plane tab, click the GetPC button. The Status field will display GettingPC… while it writes the calibration, and will</p><p>then display GetPColl status is OK if the write was successful.</p><p>Entering The P Plane (DMS) Serial Number.</p><p>The second field on the Status Bar displays the P Plane serial number. Double-click on the Serial #: field in order to display</p><p>the serial umber pop-up. Enter the A Plane serial number into the filed, and click the OK button.</p><p>Philips Medical Systems Confidential and Proprietary Information 46</p><p>DMC Host UtilityBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Z RPM Tab</p><p>Tables</p><p>The Z RPM tab is divided into two tables, Rotor Speed and Z Position. The</p><p>first table, Rotor Speed, designates allowable rotor rotations. The mapping</p><p>between rpm and time is in the following table. The scanning application</p><p>uses time.</p><p>The default field entries are numbers ranging from 0 to 5.</p><p>Buttons</p><p>GetZC Reads the current values in the NVRAM designated for Z calibration and loads the calibration into the GUI.</p><p>Clear Sets all fields back to the default values.</p><p>SetZC Writes the values in the GUI to the NVRAM.</p><p>Status Bar</p><p>The Status Bar for the Z RPM tab is the same as the A Plane tab with the following exceptions:</p><p>While reading, the Status field will display GettingZC…, and after successfully reading, the Status field will display GetZColl</p><p>status is OK.</p><p>While writing, the Status field will display SettingZC…, and after successfully reading, the Status field will display SetZColl</p><p>status is OK.</p><p>Table 3 - 6: RPM-to-time mapping</p><p>RPM 0 30 40 60 80 120</p><p>Seconds X 2 1.5 1 .75 05</p><p>Philips Medical Systems Confidential and Proprietary Information 47</p><p>DMC Host UtilityBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Obtaining Z Alignment Calibration</p><p>Z alignment if performed after air, phantom and HCOR calibration. See the T95 Performance document for the procedure for Z</p><p>alignment.</p><p>Manually Entering The Z Alignment Calibration Into The GUI</p><p>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</p><p>calibration. There is no status message while entering the values so the last message will remain in the status field.</p><p>Clearing the Z RPM GUI</p><p>Click the Clear button on the Z RPM tab, and the fields will update with the default values.</p><p>Writing The Z alignment Calibration Into The NVRAM</p><p>After loading calibration data into the Z RPM tab, click the SetZC button. The Status field will display SettingZC… while it</p><p>writes the calibration, and will then display SetPColl status is OK if the write was successful</p><p>Philips Medical Systems Confidential and Proprietary Information 48</p><p>DMC Host UtilityBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Reading The Z alignment Calibration From NVRAM</p><p>From the Z RPM tab, click the GetZC button. The Status field will display GettingZC… while it reads the calibration, and will</p><p>then display GetZColl status is OK if the read was successful.</p><p>Go2Position Tab On Host Application</p><p>The Go2Position tab consists of two tables:</p><p>Aplane Units Allows movement of the SW, Z and Filter</p><p>motors.</p><p>Pplane Units Also allows movement of the UHR filter.</p><p>A Plane Units table</p><p>The A Plane Units table contains the values corresponding</p><p>to specific A Plane SW collimator openings. Openings can</p><p>be entered in microns or mills (thousandths of an inch)</p><p>depending on which radio button is selected.</p><p>The default value is 0. The recommended range of widths</p><p>is 20 to 3400 micrometers. The default unit is micrometers.</p><p>The Move button initiates the move to position.</p><p>NOTE Since there is only one button, the Status field will display Moving Aplane to position … during and after a</p><p>move.</p><p>Double-click the Aplane Units field in order to edit it. Enter a value within the allowed range then click the Move button.</p><p>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</p><p>collimator according to the value set in the Z RPM tab.</p><p>To change the Filter position, select one of the three positions for the motor. This will place the Filter desired in the center of</p><p>the collimator opening once the Move button is pressed.</p><p>Philips Medical Systems Confidential and Proprietary Information 49</p><p>DMC Host UtilityBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>P Plane Units table</p><p>The P Plane Units table contains the values corresponding to specific P</p><p>Plane collimator openings. Openings can be entered in microns or mills</p><p>(thousandths of an inch) depending on which radio button is selected.</p><p>The default value is 0. The recommended range of widths is 20 to 3400</p><p>micrometers. The default unit is micrometers. The Move button initiates</p><p>the move to position.</p><p>Since there is only one button, the Status field will display Moving Pplane</p><p>to position … during and after a move.</p><p>Double-click the Pplane Units field to edit it. Enter a value within the</p><p>allowed range, then click the Move button.</p><p>In order to move the UHR filter, click on one of the two toggle positions. For</p><p>the UHR to move in, select OFF. The following screen will appear, with the</p><p>Status field indicating Moving UHRplane in...</p><p>Select the same switch again</p><p>to move the UHR back to the original</p><p>position. The Status field will indicate Moving UHRplane out...</p><p>Philips Medical Systems Confidential and Proprietary Information 50</p><p>DMC Host UtilityBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Temperature Tab</p><p>The Temperature tab is divided into two tables:</p><p>PID Designates the current settings as set in the TempCalib Utility.</p><p>Sensor Offset</p><p>Setting</p><p>Allows get and set of offsets that apply to the temperature sensors situated on the</p><p>DMS.</p><p>Philips Medical Systems Confidential and Proprietary Information 51</p><p>DMC Host UtilityBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Manually Entering The Temperature Calibration Into The GUI</p><p>Double-click on a Sensor Offset Setting field, or move the slider bars in either direction, to edit the value in the field. The</p><p>figure at right shows the Temperature tab with manually entered values.</p><p>Clearing the Temperature Calibration GUI</p><p>Click the Clear button on the Temperature tab, and the fields will update with the default values.</p><p>Writing Temperature Calibration Into The NVRAM</p><p>After loading calibration data into the Temperature tab, click the SetTempParam button. The Status field will display Setting</p><p>sensors... while it writes the calibration, and will then display SetTempParam Status is OK if the write was successful.</p><p>Reading Temperature Calibration From NVRAM</p><p>On the Temperature tab, click the GetTempParam button. The Status field will display Getting TempOffset... while it reads the</p><p>calibration, and will then display SetTempParam Status is OK if the read was successful.</p><p>Philips Medical Systems Confidential and Proprietary Information 52</p><p>Bug ReportBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Bug Report</p><p>Introduction</p><p>• The purpose of the Bugrep utility is to save all of the relevant information about a specific problem for postmortem/ remote</p><p>analysis. Correct bug reports allow troubleshooting without the need for problem reproducing.</p><p>• The Bugrep utility saves all of the data/log files that describe the current system status and previous operation.</p><p>• The Bugrep utility supports the management of reports on the local disk (compression, clean-up) and exports them to the</p><p>Brilliance CT EOD or sends them by e-mail to the Service Support Center (if the system configured for this option).</p><p>• The Bugrep default behavior is field-oriented-"save" means export in compressed form (saves all bug reports as a .tar file).</p><p>Producing and Saving Bugrep</p><p>1 On the Service menu, click Bug Report. The Bug Report dialog box appears</p><p>(see Figure 4 - 1).</p><p>2 Enter information in the Bug Report dialog box as follows:</p><p>a In the Problem Name field, enter a title or a short complaint description.</p><p>b In the Submitter field, enter a name/ corresponding field of a Bugrep utility.</p><p>c Click to clear the Save IRS state check box, if the problem has nothing to do</p><p>with the IRS.</p><p>d Verify that Compress Report is selected, to store in a compressed format.</p><p>e Select the Send Report By e-Mail- if you would like to send the Bugrep to</p><p>Support Center automatically. This option is active only if the system has an</p><p>e-mail option and it been configured to support this feature.</p><p>f In the Problem Description field, enter more details, such as description,</p><p>notes, or errors that appear during the problem.</p><p>3 Click Save Report to create the Bugrep and to save it in the d:/Bugrep/Reports</p><p>directory as a .tar file.</p><p>4 Click Clean up to delete old reports from the Archive.</p><p>Figure 4 - 1: Bug Report Dialog Box</p><p>Philips Medical Systems Confidential and Proprietary Information 53</p><p>Bug ReportBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>5 Click Export to export reports to the EOD. or send by e-mail.</p><p>Cleanup Bugrep</p><p>1 On the Service menu, click Bugrep. The Bug Report dialog box</p><p>appears (see Figure 4 - 1).</p><p>2 Click Clean up to delete old reports from the Archive. The Cleanup</p><p>Archive window appears (see Figure 4 - 2).</p><p>3 Select a report in the Cleanup Archive list to be deleted and click</p><p>Remove to delete them.</p><p>To select a consecutive series of reports, select the first report and</p><p>press Shift and click on the last report.</p><p>To select a non-consecutive series of reports, select the first report</p><p>and press Ctrl and click on additional reports.</p><p>4 Click Yes in the confirmation window to delete the selected reports.</p><p>Click No to cancel delete, and to return to the Cleanup Archive</p><p>window.</p><p>Figure 4 - 2: Cleanup Archive</p><p>Philips Medical Systems Confidential and Proprietary Information 54</p><p>Bug ReportBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Exporting Bugrep</p><p>1 On the Service menu, click Bugrep. The Bug Report dialog box appears (see</p><p>Figure 4 - 1).</p><p>2 Click Export to EOD to save reports from the Archive to the EOD, or click Send By</p><p>e-Mail, to send the reports by e-Mail/ Site Manager to the Service Support Center.</p><p>The Export Archive window appears (see Figure Figure 4 - 3).</p><p>3 To select a consecutive series of reports, select the first report and press Shift and</p><p>click on the last report.</p><p>To select a non-consecutive series of reports, select the first report and press Ctrl</p><p>and click on additional reports.</p><p>Sending Bug Reports</p><p>Sending Bug Reports can be accomplished either automatically or manually from the Bugrep Utility or from the LogBook.</p><p>In either service tool, select the Send by E-mail option.</p><p>Bugrep Analyzer/Viewer</p><p>• The Bugrep Analyzer/Viewer simplifies problem reports analysis. It supports the loading of bug reports from a repository,</p><p>automatically analyzes files included in the report, and displays the found problems.</p><p>• The Bug Report contains many files in different formats. The Analyzer displays a list of files with color-coded status for each</p><p>format.</p><p>• Viewers for different formats are integrated into the Analyzer and are loaded by double-clicking on the corresponding file.</p><p>• Infrastructure for complex multi-file error analysis is implemented.</p><p>• There are specific error types for each file in the Bug Report. A complex error containing a combination of error statuses in</p><p>different files is defined, for example, ACQ received all of the data, IRS reconstructed part of the images -> IRS error.</p><p>Figure 4 - 3: Export Archive</p><p>Philips Medical Systems Confidential and Proprietary Information 55</p><p>Bug ReportBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>• There is an option to run the System Monitor utility on Bugrep to simplify analysis.</p><p>Bugrep User Interface</p><p>The Bugrep Analyzer/Viewer, shown in Figure 4 - 4, uses an interface similar to that of the Windows Explorer.</p><p>The left section of the Bugrep Viewer shows Categories that reflect the logical hierarchy of the files. Because of this, files from</p><p>different directories may be found in the same Category. The same file may also appear in multiple Categories.</p><p>The right section of the Bugrep Viewer shows Summary files, resulting from automatic file analysis. When a Summary file is</p><p>opened, its internal records may be color-coded to reflect their status. Alerts are displayed in red; warnings are displayed in</p><p>yellow.</p><p>The Bugrep Viewer provides error code definitions for different log files. The error code definition consists of 4 fields:</p><p>• Log file name</p><p>• Text pattern corresponding to the error</p><p>• Error code</p><p>• Error description</p><p>Philips Medical Systems Confidential and Proprietary Information 56</p><p>Bug ReportBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Figure 4 - 4: Bugrep Viewer Window</p><p>Using the Bugrep Viewer</p><p>1 On the Service menu, click Bugview. The Bugrep Viewer window opens (see Figure 4 - 4).</p><p>2 On the File menu, click Open Bugrep. The Open Bugrep in Tar Format dialog box appears.</p><p>Philips Medical Systems Confidential and Proprietary Information 57</p><p>Bug ReportBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power</p><p>1.2.5 O-Level Utilities Manual</p><p>3 Select a Bugrep file and click Open (see Figure 13 - 112). The selected file will be loaded into the Bugrep Viewer.</p><p>Figure 4 - 5: Opening a Bugrep File</p><p>Interacting with Bugrep Files</p><p>To select an individual Log file for viewing:</p><p>1 Double-click on the file. The Log File window opens.</p><p>Philips Medical Systems Confidential and Proprietary Information 58</p><p>Bug ReportBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Figure 4 - 6: Log File Window</p><p>2 You can now move through the selected file and examine its contents, using the mouse, keyboard, or the various</p><p>navigation elements at the bottom of the Log File window. For more details on using these navigation elements, Log File</p><p>Window Navigation.</p><p>NOTE Whenever an error message is selected, its highlight will be enlarged slightly to differentiate it from other</p><p>error messages, and make viewing easier. When an error message contains an alert or warning indication, it</p><p>Philips Medical Systems Confidential and Proprietary Information 59</p><p>Bug ReportBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>will appear highlighted in one of the following colors: Alerts will appear in Red, Warnings will appear in</p><p>Yellow.</p><p>Log File Window Navigation</p><p>Figure 4 - 7:</p><p>Function Description</p><p>Click these buttons to skip from one highlighted with an error message row to the</p><p>next.</p><p>Search Text Box, Find Next</p><p>Enter text to search for in the Search text box. Searching is case sensitive.</p><p>Choose Down or Up to determine the direction of the search. Click the Find Next</p><p>button to continue searching for the next occurrence.</p><p>Click this button to return to the cursor location when it is off the screen. This</p><p>function is useful when you want to search through the entire file for additional</p><p>information, and then return to your original location in the file.</p><p>Copies all rows found in last search into a new window.</p><p>Export Content (accessed from the File menu)- saves contents of search window</p><p>as a text file.</p><p>Philips Medical Systems Confidential and Proprietary Information 60</p><p>Bug ReportBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Export / Send Reports</p><p>To export an entire Bugrep report to the EOD or send it by e-mail:</p><p>1 Select File | Export / Send Reports. A file list of reports appears.</p><p>2 Select the Bugrep report you want to export / send by e-mail, and click Export to</p><p>EOD or click Send by E-mail. A confirmation window appears.</p><p>3 Click Yes to confirm export / send by email.</p><p>Exporting Selected Bugrep Files</p><p>To export a single file from Bugrep for later analysis (for example, by a service technician in another location):</p><p>1 Select the Bugrep file that you want to export.</p><p>2 Select File | Export Selected File. A file destination window appears.</p><p>3 Enter a destination and name for the exported file, if different from the current destination and name. Click OK.</p><p>Removing Bugrep Reports from the System</p><p>To erase an entire Bugrep report from the system:</p><p>1 Select File | Remove Reports. A file list of reports appears.</p><p>2 Select the Bugrep report you want to erase, and click Remove. A confirmation window appears.</p><p>3 Click Yes to confirm its deletion.</p><p>NOTE When you remove a Bugrep Report form the system, the Logbook is also updated. The hyperlink for the</p><p>deleted report is changed from Show to Erased.</p><p>Philips Medical Systems Confidential and Proprietary Information 61</p><p>Bug ReportBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Bugrep Viewer Options</p><p>The Bugrep Viewer enables you to perform the following additional activities, to support solving problems:</p><p>• Analyzing the current state of the system.</p><p>• Viewing multiple Bugrep analyses.</p><p>• Running System Monitor using a selected Bugrep report, enabling you to recreate the environment that existed at the time</p><p>the bug was reported.</p><p>• Opening a UNIX console (csh window) to enable a service technical to perform tasks and run environment-specific</p><p>commands.</p><p>Analyze Current State</p><p>This option enables you to create a Bugrep report of the current system state on demand. It displays the report in the Bugrep</p><p>Viewer and performs an immediate analysis.</p><p>To analyze the current state of the system:</p><p>1 Select Options | Analyze Current State.</p><p>View Multiple Analyses</p><p>This option enables you to combine numerous events (errors) found in the Bugrep log files, and automatically analyze results.</p><p>The findings are then displayed for review. Generally, a multiple analysis is used to pinpoint the initial cause of a series of</p><p>errors.</p><p>To view multiple analyses simultaneously:</p><p>1 Select Options | View Multiple Analyses.</p><p>2 The analyses will be performed, and a summary window appears.</p><p>Running System Monitor on Bugrep</p><p>To run System Monitor on a selected Bugrep report:</p><p>1 Select Options | Run Sysmon Over Current Bugrep.</p><p>Philips Medical Systems Confidential and Proprietary Information 62</p><p>Bug ReportBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>For more information, see the System Monitor Utility.</p><p>Opening a UNIX Console</p><p>To open a UNIX shell to perform tasks or run environment-specific commands:</p><p>1 Select Options | Open Console.</p><p>Philips Medical Systems Confidential and Proprietary Information 63</p><p>Tips on how to use SQL for queriesBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Tips on how to use SQL for queries</p><p>Using Data Manipulation Language .................................. page 5-64</p><p>Retrieving Records....................................................... page 5-64</p><p>Restricting the Result Set............................................. page 5-65</p><p>Sorting the Result Set .................................................. page 5-66</p><p>Using Aggregate Functions to Work with Values ......... page 5-66</p><p>Grouping Records in a Result Set................................ page 5-68</p><p>Intermediate Data Manipulation Language ....................... page 5-68</p><p>Predicates.................................................................... page 5-69</p><p>The ALL keyword ......................................................... page 5-69</p><p>The DISTINCT keyword ............................................... page 5-69</p><p>The DISTINCTROW keyword ...................................... page 5-69</p><p>The TOP keyword ........................................................ page 5-70</p><p>SQL Expressions............................................................... page 5-70</p><p>The IN operator ............................................................ page 5-71</p><p>The BETWEEN operator.............................................. page 5-71</p><p>The LIKE operator........................................................ page 5-72</p><p>The IS NULL operator .................................................. page 5-73</p><p>Subqueries ........................................................................ page 5-74</p><p>The IN subquery........................................................... page 5-74</p><p>The ANY/SOME/ALL subqueries ................................. page 5-74</p><p>The EXISTS subquery ................................................. page 5-75</p><p>Joins .................................................................................. page 5-76</p><p>INNER JOINs............................................................... page 5-76</p><p>OUTER JOINs.............................................................. page 5-77</p><p>The Cartesian product.................................................. page 5-78</p><p>The UNION operator .................................................... page 5-78</p><p>The TRANSFORM statement ...................................... page 5-79</p><p>Philips Medical Systems Confidential and Proprietary Information 64</p><p>Tips on how to use SQL for queriesBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Using Data Manipulation Language</p><p>DML is all about working with the data that is stored in the database</p><p>tables. Not only is DML used for retrieving the data, it is</p><p>also used for creating, modifying, and deleting it.</p><p>Retrieving Records</p><p>The most basic and most often used SQL statement is the SELECT statement. SELECT statements are the workhorses of all</p><p>SQL statements, and they are commonly referred to as select queries. You use the SELECT statement to retrieve data from</p><p>the database tables, and the results are usually returned in a set of records (or rows) made up of any number of fields (or</p><p>columns). You must designate which table or tables to select from with the FROM clause. The basic structure of a SELECT</p><p>statement is:</p><p>SELECT field list</p><p>FROM table list</p><p>To select all the fields from a table, use an asterisk (*). For example, the following statement selects all the fields and all the</p><p>records from the customers table:</p><p>SELECT *</p><p>FROM tblCustomers</p><p>To limit the fields retrieved by the query, simply use the field names instead. For example:</p><p>SELECT [Last Name], Phone</p><p>FROM tblCustomers</p><p>To designate a different name for a field in the result set, use the AS keyword to establish an alias for that field.</p><p>SELECT CustomerID AS [Customer Number]</p><p>FROM tblCustomers</p><p>Philips Medical Systems Confidential and Proprietary Information 65</p><p>Tips on how to use SQL for queriesBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Restricting the Result Set</p><p>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</p><p>some qualifying criteria. To qualify a SELECT statement, you must use a WHERE clause, which will allow you to specify</p><p>exactly which records you want to retrieve.</p><p>SELECT *</p><p>FROM tblInvoices</p><p>WHERE CustomerID = 1</p><p>Note the CustomerID = 1 portion of the WHERE clause. A WHERE clause can contain up to 40 such expressions, and they</p><p>can be joined with the And or Or logical operators. Using more than one expression allows you to further filter out records in</p><p>the result set.</p><p>SELECT *</p><p>FROM tblInvoices</p><p>WHERE CustomerID = 1 AND InvoiceDate > #01/01/98#</p><p>Note that the date string is enclosed in number signs (#). If you are using a regular string in an expression, you must enclose</p><p>the string in single quotation marks ('). For example:</p><p>SELECT *</p><p>FROM tblCustomers</p><p>WHERE [Last Name] = 'White'</p><p>If you do not know the whole string value, you can use wildcard characters with the Like operator.</p><p>SELECT *</p><p>FROM tblCustomers</p><p>WHERE [Last Name] LIKE 'W*'</p><p>There are a number of wildcard characters to choose from, and the following table details what they are and what they can be</p><p>used for.</p><p>Wildcard character Description</p><p>* or % Zero or more characters</p><p>? or _ (underscore) Any single character</p><p># Any single digit (0-9)</p><p>Philips Medical Systems Confidential and Proprietary Information 66</p><p>Tips on how to use SQL for queriesBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>NOTE The % and _ (underscore) wildcard characters should be used only through the Jet OLE DB provider and</p><p>ActiveX® Data Objects (ADO) code. They will be treated as literal characters if they are used though the</p><p>Access SQL View user interface or Data Access Objects (DAO) code.</p><p>For more information about using the Like operator with wildcard characters, type wildcard characters in the Office Assistant</p><p>or on the Answer Wizard tab in the Microsoft Access Help window, and then click Search.</p><p>Sorting the Result Set</p><p>To specify a particular sort order on one or more fields in the result set, use the optional ORDER BY clause. As explained</p><p>earlier in the "Working with Indexes" section, records can be sorted in either ascending (ASC) or descending (DESC) order;</p><p>ascending is the default.</p><p>Fields referenced in the ORDER BY clause do not have to be part of the SELECT statement's field list, and sorting can be</p><p>applied to string, numeric, and date/time values. Always place the ORDER BY clause at the end of the SELECT statement.</p><p>SELECT *</p><p>FROM tblCustomers</p><p>ORDER BY [Last Name], [First Name] DESC</p><p>You can also use the field numbers (or positions) instead of field names in the ORDER BY clause.</p><p>SELECT *</p><p>FROM tblCustomers</p><p>ORDER BY 2, 3 DESC</p><p>For more information about using the ORDER BY clause, type ORDER BY clause in the Office Assistant or on the Answer</p><p>Wizard tab in the Microsoft Access Help window, and then click Search.</p><p>Using Aggregate Functions to Work with Values</p><p>Aggregate functions are used to calculate statistical and summary information from data in tables. These functions are used in</p><p>SELECT statements, and all of them take fields or expressions as arguments.</p><p>[charlist] Any single character in charlist</p><p>[!charlist] Any single character not in charlist</p><p>Wildcard character Description</p><p>Philips Medical Systems Confidential and Proprietary Information 67</p><p>Tips on how to use SQL for queriesBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>To count the number of records in a result set, use the Count function. Using an asterisk with the Count function causes Null</p><p>values to be counted as well.</p><p>SELECT Count(*) AS [Number of Invoices]</p><p>FROM tblInvoices</p><p>To count only non-Null values, use the Count function with a field name:</p><p>SELECT Count(Amount) AS</p><p>[Number of Valid Invoice Amounts]</p><p>FROM tblInvoices</p><p>To find the average value for a column or expression of numeric data, use the Avg function:</p><p>SELECT Avg(Amount) AS [Average Invoice Amount]</p><p>FROM tblInvoices</p><p>To find the total of the values in a column or expression of numeric data, use the Sum function:</p><p>SELECT Sum(Amount) AS [Total Invoice Amount]</p><p>FROM tblInvoices</p><p>To find the minimum value for a column or expression, use the Min function:</p><p>SELECT Min(Amount) AS [Minimum Invoice Amount]</p><p>FROM tblInvoices</p><p>To find the maximum value for a column or expression, use the Max function:</p><p>SELECT Max(Amount) AS [Maximum Invoice Amount]</p><p>FROM tblInvoices</p><p>To find the first value in a column or expression, use the First function:</p><p>SELECT First(Amount) AS [First Invoice Amount]</p><p>FROM tblInvoices</p><p>To find the last value in a column or expression, use the Last function:</p><p>SELECT Last(Amount) AS [Last Invoice Amount]</p><p>FROM tblInvoices</p><p>For more information about using the aggregate functions, type SQL aggregate functions in the Office Assistant or on the</p><p>Answer Wizard tab in the Microsoft Access Help window, and then click Search.</p><p>Philips Medical Systems Confidential and Proprietary Information 68</p><p>Tips on how to use SQL for queriesBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Grouping Records in a Result Set</p><p>Sometimes there are records in a table that are logically related, as in the case of the invoices table. Since one customer can</p><p>have many invoices, it could be useful to treat all the invoices for one customer as a group, in order to find statistical and</p><p>summary information about the group.</p><p>The key to grouping records is that one or more fields in each record must contain the same value for every record in the</p><p>group. In the case of the invoices table, the CustomerID field value is the same for every invoice a particular customer has.</p><p>To create a group of records, use the GROUP BY clause with the name of the field or fields you want to group with.</p><p>SELECT CustomerID, Count(*) AS [Number of Invoices],</p><p>Avg(Amount) AS [Average Invoice Amount]</p><p>FROM tblInvoices</p><p>GROUP BY CustomerID</p><p>Note that the statement will return one record that shows the customer ID, the number of invoices the customer has, and the</p><p>average invoice amount, for every customer who has an invoice record in the invoices table. Because each customer's</p><p>invoices are treated as a group, we are able to count the number of invoices, and then determine the average invoice amount.</p><p>You can specify a condition at the group level by using the HAVING clause, which is similar to the WHERE clause. For</p><p>example, the following query</p><p>returns only those records for each customer whose average invoice amount is less than 100:</p><p>SELECT CustomerID, Count(*) AS [Number of Invoices],</p><p>Avg(Amount) AS [Average Invoice Amount]</p><p>FROM tblInvoices</p><p>GROUP BY CustomerID</p><p>HAVING Avg(Amount) < 100</p><p>Intermediate Data Manipulation Language</p><p>The article “Fundamental Microsoft Jet SQL for Access 2000" showed how to use SQL to retrieve and manage the information</p><p>stored in a database. In the sections that follow in this article, we discuss intermediate Data Manipulation Language (DML)</p><p>statements that will allow you to have even greater control over how information can be retrieved and manipulated.</p><p>Philips Medical Systems Confidential and Proprietary Information 69</p><p>Tips on how to use SQL for queriesBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Predicates</p><p>A predicate is an SQL clause that qualifies a SELECT statement, similar to a WHERE clause, except that the predicate is</p><p>declared before the column list. Predicates can further restrict the set of records you are retrieving, and in some instances filter</p><p>out any duplicate data that may exist.</p><p>The ALL keyword</p><p>The ALL keyword is the default keyword that is used when no predicate is declared in an SQL statement. It simply means that</p><p>all records will be retrieved that match the qualifying criteria of the SQL statement. Returning to our invoices database</p><p>example, let's select all records from the customers table:</p><p>SELECT *</p><p>FROM tblCustomers</p><p>Notice that although the ALL keyword was not declared, it is the default predicate. We could have written the statement like</p><p>this:</p><p>SELECT ALL *</p><p>FROM tblCustomers</p><p>The DISTINCT keyword</p><p>The DISTINCT keyword is used to control how duplicate values in a result set are handled. Based on the column(s) specified</p><p>in the field list, those rows that have duplicate values in the specified columns are filtered out. If more than one column is</p><p>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</p><p>distinct last names, only the unique names will be returned; any duplicate names will result in only one instance of that name</p><p>in the result set.</p><p>SELECT DISTINCT [Last Name]</p><p>FROM tblCustomers</p><p>It is important to note that the result set returned by a query that uses the DISTINCT keyword cannot be updated; it is read-</p><p>only.</p><p>The DISTINCTROW keyword</p><p>The DISTINCTROW keyword is similar to the DISTINCT keyword except that it is based on entire rows, not just individual</p><p>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</p><p>you base your query on one table, or select fields from every table, the DISTINCTROW keyword essentially acts as an ALL</p><p>keyword.</p><p>Philips Medical Systems Confidential and Proprietary Information 70</p><p>Tips on how to use SQL for queriesBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>For example, in our invoices database, every customer can have no invoices, or one or more invoices. Let's suppose that we</p><p>want to find out how many customers have one or more invoices. We will use the DISTINCTROW keyword to determine our</p><p>list of customers.</p><p>SELECT DISTINCTROW [Last Name], [First Name]</p><p>FROM tblCustomers INNER JOIN tblInvoices</p><p>ON tblCustomers.CustomerID = tblInvoices.CustomerID</p><p>If we had left off the DISTINCTROW keyword, we would have gotten a row returned for every invoice each customer has. (The</p><p>INNER JOIN statement will be covered in a later section.)</p><p>The TOP keyword</p><p>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</p><p>ORDER BY clause. The ORDER BY clause is used to sort the rows in either ascending or descending order. If there are equal</p><p>values present, the TOP keyword will return all rows that have the equal value. Let's say that we want to determine the highest</p><p>three invoice amounts in our invoices database. We'd write a statement like this:</p><p>SELECT TOP 3 InvoiceDate, Amount</p><p>FROM tblInvoices</p><p>ORDER BY Amount DESC</p><p>We can also use the optional PERCENT keyword with the TOP keyword to return a percentage of rows that fall at the top or</p><p>bottom of a range that is specified by an ORDER BY clause. The code looks like this:</p><p>SELECT TOP 25 PERCENT InvoiceDate, Amount</p><p>FROM tblInvoices</p><p>ORDER BY Amount DESC</p><p>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</p><p>rows.</p><p>For more information about predicates, type all, distinct predicates in the Office Assistant or on the Answer Wizard tab in</p><p>the Microsoft Access Help window, and then click Search.</p><p>SQL Expressions</p><p>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</p><p>combination of operators, constants, literal values, functions, field names, controls, or properties to build your SQL</p><p>Philips Medical Systems Confidential and Proprietary Information 71</p><p>Tips on how to use SQL for queriesBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>expressions. The article “Fundamental Microsoft Jet SQL for Access 2000" describes how you can use expressions in</p><p>WHERE clauses to qualify SQL statements; and in the following sections of this article, we examine different SQL operators</p><p>that can be used in expressions.</p><p>The IN operator</p><p>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</p><p>expression matches a value in the list, the IN operator returns True. If it is not found, the IN operator returns False. Let's</p><p>suppose that we want to find all shipping addresses that are in the states of Washington and Georgia. Although we could write</p><p>an SQL statement with a long WHERE clause that uses the AND logical operator, using the IN operator will shorten our</p><p>statement.</p><p>SELECT *</p><p>FROM tblShipping</p><p>WHERE State IN ('WA','GA')</p><p>By using the NOT logical operator, we can check the opposite of the IN operator. This statement will return all shipping</p><p>addresses that are not in Washington State:</p><p>SELECT *</p><p>FROM tblShipping</p><p>WHERE State NOT IN ('WA')</p><p>The BETWEEN operator</p><p>The BETWEEN operator is used to determine if the value of an expression falls within a specified range of values. If the</p><p>expression's value falls within the specified range, including both the beginning and ending range values, the BETWEEN</p><p>operator returns True. If the expression's value does not fall within the range, the BETWEEN operator returns False. Let's</p><p>suppose that we want to find all invoices that have an amount between $50 and $100 dollars. We'd use the BETWEEN</p><p>operator in the WHERE clause with the AND keyword that specifies the range.</p><p>SELECT *</p><p>FROM tblInvoices</p><p>WHERE Amount BETWEEN 50 AND 100</p><p>By using the NOT logical operator, we can check the opposite of the BETWEEN operator to find invoice amounts that fall</p><p>outside that range.</p><p>SELECT *</p><p>FROM tblInvoices</p><p>Philips Medical Systems Confidential and Proprietary Information 72</p><p>Tips on how to use SQL for queriesBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>WHERE Amount NOT BETWEEN 50 AND 100</p><p>Note that the range can be in reverse order and still achieve the same results (BETWEEN 100 AND 50), but many ODBC-</p><p>compliant databases require that the range follow the begin-value-to-end-value method. If you plan for your application to be</p><p>scaled or upsized to an ODBC-compliant database, you should always use the begin-value-to-end-value method.</p><p>The LIKE operator</p><p>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</p><p>string value, or a partial string value that also contains one or more wildcard characters. By using the LIKE operator, you can</p><p>search a field within a result set</p><p>and find all of the values that match the specified pattern.</p><p>SELECT *</p><p>FROM tblCustomers</p><p>WHERE [Last Name] LIKE 'Johnson'</p><p>To return all customers who have a last name that starts with the letter J, use the asterisk wildcard character.</p><p>SELECT *</p><p>FROM tblCustomers</p><p>WHERE [Last Name] LIKE 'J*'</p><p>By using the NOT logical operator, we can check the opposite of the LIKE operator and filter out all the Johnsons from the list.</p><p>SELECT *</p><p>FROM tblCustomers</p><p>WHERE [Last Name] NOT LIKE 'Johnson'</p><p>There are a variety of wildcard characters that you can use in the LIKE operator patterns, as shown in the following table.</p><p>Wildcard Character Description</p><p>* (asterisk) Matches any number of characters and can be used anywhere in the pattern string.</p><p>% (percent sign)</p><p>Matches any number of characters and can be used anywhere in the pattern string.</p><p>(ADO and the Jet OLE DB provider only)</p><p>? (question mark) Matches any single character and can be used anywhere in the pattern string.</p><p>Philips Medical Systems Confidential and Proprietary Information 73</p><p>Tips on how to use SQL for queriesBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>NOTE The "%" and "_" wildcard characters in the previous table can be executed only through the Jet OLE DB</p><p>provider and ADO. They will yield an empty result set if used through the Access SQL View user interface.</p><p>For more information about wildcard characters, type wildcard characters in the Office Assistant or on the Answer Wizard</p><p>tab in the Microsoft Access Help window, and then click Search.</p><p>The IS NULL operator</p><p>A null value is one that indicates missing or unknown data. The IS NULL operator is used to determine if the value of an</p><p>expression is equal to the null value.</p><p>SELECT *</p><p>FROM tblInvoices</p><p>WHERE Amount IS NULL</p><p>By adding the NOT logical operator, we can check the opposite of the IS NULL operator. In this case, the statement will weed</p><p>out invoices with missing or unknown amounts.</p><p>SELECT *</p><p>FROM tblInvoices</p><p>WHERE Amount IS NOT NULL</p><p>_ (underscore)</p><p>Matches any single character and can be used anywhere in the pattern string. (ADO and</p><p>the Jet OLE DB provider only)</p><p># (number sign) Matches any single digit and can be used anywhere in the pattern string.</p><p>[] (square brackets)</p><p>Matches any single character within the list that is enclosed within brackets, and can be</p><p>used anywhere in the pattern string.</p><p>! (exclamation point) Matches any single character not in the list that is enclosed within the square brackets.</p><p>- (hyphen) Matches any one of a range of characters that is enclosed within the square brackets.</p><p>Wildcard Character Description</p><p>Philips Medical Systems Confidential and Proprietary Information 74</p><p>Tips on how to use SQL for queriesBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Subqueries</p><p>A subquery is a SELECT statement that is used inside another SELECT, SELECT INTO, INSERT INTO, DELETE, or</p><p>UPDATE statement. It can help further qualify a result set based on the results of another result set. This is called nesting, and</p><p>since a subquery is a SELECT statement, you can also nest a subquery inside another subquery. When you use a subquery in</p><p>an SQL statement, it can be part of a field list, a WHERE clause, or a HAVING clause.</p><p>There are three basic forms of subqueries, and each uses a different kind of predicate.</p><p>The IN subquery</p><p>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</p><p>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</p><p>returned. Using the invoices database example, let's write an SQL statement that returns a list of all customers who have</p><p>invoices.</p><p>SELECT *</p><p>FROM tblCustomers</p><p>WHERE CustomerID</p><p>IN (SELECT CustomerID FROM tblInvoices)</p><p>Using the NOT logical operator, we can check the opposite of the IN subquery and generate a list of customers who do not</p><p>have invoices.</p><p>SELECT *</p><p>FROM tblCustomers</p><p>WHERE CustomerID</p><p>NOT IN (SELECT CustomerID FROM tblInvoices)</p><p>The ANY/SOME/ALL subqueries</p><p>The ANY, SOME, and ALL subquery predicates are used to compare records from the main query with multiple rows from the</p><p>subquery. The ANY and SOME predicates are synonymous and can be used interchangeably.</p><p>Use the ANY or SOME predicate when you need to retrieve from the main query the set of records that satisfy the comparison</p><p>with any of the records in the subquery. Use the predicate just before the opening parenthesis of the subquery.</p><p>SELECT *</p><p>FROM tblCustomers</p><p>Philips Medical Systems Confidential and Proprietary Information 75</p><p>Tips on how to use SQL for queriesBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>WHERE CustomerID = ANY</p><p>(SELECT CustomerID FROM tblInvoices)</p><p>Notice that the result set returned by the SQL statement above is the same as the one returned by the example with the IN</p><p>subquery. What makes the ANY and SOME predicates different is that they can also be used with relational operators other</p><p>than Equals (=), such as Greater Than (>) or Less Than (<).</p><p>SELECT *</p><p>FROM tblCustomers</p><p>WHERE CustomerID > ANY</p><p>(SELECT CustomerID FROM tblInvoices)</p><p>When you want to retrieve records from the main query that satisfy the comparison with all of the records in the subquery, use</p><p>the ALL predicate.</p><p>SELECT *</p><p>FROM tblCustomers</p><p>WHERE CustomerID > ALL</p><p>(SELECT CustomerID FROM tblInvoices)</p><p>The EXISTS subquery</p><p>The EXISTS predicate is used in subqueries to check for the existence of values in a result set. In other words, if the subquery</p><p>does not return any rows, the comparison is False. If it does return one or more rows, the comparison is True.</p><p>SELECT *</p><p>FROM tblCustomers AS A</p><p>WHERE EXISTS</p><p>(SELECT * FROM tblInvoices</p><p>WHERE A.CustomerID = tblInvoices.CustomerID)</p><p>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</p><p>subquery. When a subquery is linked to the main query in this manner, it is called a correlated query.</p><p>By using the NOT logical operator, we can check the opposite of the EXISTS subquery to obtain a result set of customers who</p><p>do not have any invoices.</p><p>SELECT *</p><p>FROM tblCustomers AS A</p><p>WHERE NOT EXISTS</p><p>Philips Medical Systems Confidential and Proprietary Information 76</p><p>Tips on how to use SQL for queriesBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>(SELECT * FROM tblInvoices</p><p>WHERE A.CustomerID = tblInvoices.CustomerID)</p><p>For more information about subqueries, type SQL subqueries in the Office Assistant or on the Answer Wizard tab in the</p><p>Microsoft Access Help window, and then click Search.</p><p>Joins</p><p>In a relational database system like Access, you will often need to extract information from more than one table at a time. This</p><p>can be accomplished by using an SQL JOIN statement. A JOIN statement enables you to retrieve records from tables that</p><p>have defined relationships, whether they are one-to-one, one-to-many, or many-to-many.</p><p>INNER JOINs</p><p>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</p><p>two or more tables by matching a field value that is common between the tables. The fields you join on must have similar data</p><p>types, and you cannot join on MEMO or OLEOBJECT data types. To build an INNER JOIN statement, use the INNER JOIN</p><p>keywords in the FROM clause of a SELECT statement. Let's use the INNER JOIN to build a result set of all customers who</p><p>have invoices, plus the dates and amounts of those invoices.</p><p>SELECT [Last Name], InvoiceDate, Amount</p><p>FROM tblCustomers INNER JOIN tblInvoices</p><p>ON tblCustomers.CustomerID=tblInvoices.CustomerID</p><p>ORDER BY InvoiceDate</p><p>Notice that the table names are divided by the INNER JOIN keywords and that the relational comparison is after the</p><p>ON</p><p>keyword. For the relational comparisons, you can also use the <, >, <=, >=, or <> operators, and you can also use the</p><p>BETWEEN keyword. Also note that the ID fields from both tables are used only in the relational comparison, they are not part</p><p>of the final result set.</p><p>To further qualify the SELECT statement, we can use a WHERE clause after the join comparison in the ON clause. In the</p><p>following example, we have narrowed the result set to include only invoices dated after January 1, 1998.</p><p>SELECT [Last Name], InvoiceDate, Amount</p><p>FROM tblCustomers INNER JOIN tblInvoices</p><p>ON tblCustomers.CustomerID=tblInvoices.CustomerID</p><p>WHERE tblInvoices.InvoiceDate > #01/01/1998#</p><p>ORDER BY InvoiceDate</p><p>Philips Medical Systems Confidential and Proprietary Information 77</p><p>Tips on how to use SQL for queriesBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>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</p><p>a previous SELECT statement to create our result set, but we will also include the city and state of each customer by adding</p><p>the INNER JOIN for the tblShipping table.</p><p>SELECT [Last Name], InvoiceDate, Amount, City, State</p><p>FROM (tblCustomers INNER JOIN tblInvoices</p><p>ON tblCustomers.CustomerID=tblInvoices.CustomerID)</p><p>INNER JOIN tblShipping</p><p>ON tblCustomers.CustomerID=tblShipping.CustomerID</p><p>ORDER BY InvoiceDate</p><p>Note that the first JOIN clause is enclosed in parentheses to keep it logically separated from the second JOIN clause. It is also</p><p>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</p><p>find all customer records that have duplicate last names. We do this by creating the alias "A" for the second table and checking</p><p>for first names that are different.</p><p>SELECT tblCustomers.[Last Name],</p><p>tblCustomers.[First Name]</p><p>FROM tblCustomers INNER JOIN tblCustomers AS A</p><p>ON tblCustomers.[Last Name]=A.[Last Name]</p><p>WHERE tblCustomers.[First Name]<>A.[First Name]</p><p>ORDER BY tblCustomers.[Last Name]</p><p>OUTER JOINs</p><p>The OUTER JOIN is used to retrieve records from multiple tables while preserving records from one of the tables, even if there</p><p>is no matching record in the other table. There are two types of OUTER JOINs that the Jet database engine supports: LEFT</p><p>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</p><p>right. The LEFT OUTER JOIN will select all rows in the right table that match the relational comparison criteria, and it will also</p><p>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</p><p>the LEFT OUTER JOIN; all rows in the right table are preserved instead.</p><p>As an example, let's suppose that we want to determine the total amount invoiced to each customer, but if a customer has no</p><p>invoices, we want to show it by displaying the word "NONE."</p><p>SELECT [Last Name] & ', ' & [First Name] AS Name,</p><p>IIF(Sum(Amount) IS NULL,'NONE',Sum(Amount)) AS Total</p><p>FROM tblCustomers LEFT OUTER JOIN tblInvoices</p><p>ON tblCustomers.CustomerID=tblInvoices.CustomerID</p><p>Philips Medical Systems Confidential and Proprietary Information 78</p><p>Tips on how to use SQL for queriesBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>GROUP BY [Last Name] & ', ' & [First Name]</p><p>There are a few things going on in the previous SQL statement. The first is the use of the string concatenation operator "&".</p><p>This operator allows you to join two or more fields together as one string. The second is the immediate if (IIF) statement, which</p><p>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</p><p>final thing is the OUTER JOIN clause. Using the LEFT OUTER JOIN preserves the rows in the left table so that we see all</p><p>customers, even those who do not have invoices.</p><p>OUTER JOINs can be nested inside INNER JOINs in a multi-table join, but INNER JOINs cannot be nested inside OUTER</p><p>JOINs.</p><p>The Cartesian product</p><p>A term that often comes up when discussing joins is the Cartesian product. A Cartesian product is defined as "all possible</p><p>combinations of all rows in all tables." For example, if you were to join two tables without any kind of qualification or join type,</p><p>you would get a Cartesian product.</p><p>SELECT *</p><p>FROM tblCustomers, tblInvoices</p><p>This is not a good thing, especially with tables that contain hundreds or thousands of rows. You should avoid creating</p><p>Cartesian products by always qualifying your joins.</p><p>The UNION operator</p><p>Although the UNION operator, also known as a union query, is not technically a join, it is included here because it does involve</p><p>combining data from multiple sources of data into one result set, which is similar to some types of joins. The UNION operator</p><p>is used to splice together data from tables, SELECT statements, or queries, while leaving out any duplicate rows. Both data</p><p>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</p><p>an Employees table that has the same structure as the Customers table, and we want to build a list of names and e-mail</p><p>address by combining both tables.</p><p>SELECT [Last Name], [First Name], Email</p><p>FROM tblCustomers</p><p>UNION</p><p>SELECT [Last Name], [First Name], Email</p><p>FROM tblEmployees</p><p>If we wanted to retrieve all fields from both tables, we could use the TABLE keyword, like this:</p><p>TABLE tblCustomers</p><p>Philips Medical Systems Confidential and Proprietary Information 79</p><p>Tips on how to use SQL for queriesBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>UNION</p><p>TABLE tblEmployees</p><p>The UNION operator will not display any records that are exact duplicates in both tables, but this can be overridden by using</p><p>the ALL predicate after the UNION keyword, like this:</p><p>SELECT [Last Name], [First Name], Email</p><p>FROM tblCustomers</p><p>UNION ALL</p><p>SELECT [Last Name], [First Name], Email</p><p>FROM tblEmployees</p><p>The TRANSFORM statement</p><p>Although the TRANSFORM statement, also known as a crosstab query, is also not technically considered a join, it is included</p><p>here because it does involve combining data from multiple sources of data into one result set, which is similar to some types of</p><p>joins.</p><p>A TRANSFORM statement is used to calculate a sum, average, count, or other type of aggregate total on records. It then</p><p>displays the information in a grid or spreadsheet format with data grouped both vertically (rows) and horizontally (columns).</p><p>The general form for a TRANSFORM statement is this:</p><p>TRANSFORM aggregating function</p><p>SELECT statement</p><p>PIVOT column heading field</p><p>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</p><p>vertical headings will be the customer names, and the horizontal headings will be the years. Let's modify a previous SQL</p><p>statement to fit the transform statement.</p><p>TRANSFORM</p><p>IIF(Sum([Amount]) IS NULL,'NONE',Sum([Amount]))</p><p>AS Total</p><p>SELECT [Last Name] & ', ' & [First Name] AS Name</p><p>FROM tblCustomers LEFT JOIN tblInvoices</p><p>ON tblCustomers.CustomerID=tblInvoices.CustomerID</p><p>GROUP BY [Last Name] & ', ' & [First Name]</p><p>PIVOT Format(InvoiceDate, 'yyyy')</p><p>IN ('1996','1997','1998','1999','2000')</p><p>Philips Medical Systems Confidential and Proprietary Information 80</p><p>Tips on how to use SQL for queriesBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Note that the aggregating function is the SUM function, the vertical headings are in the GROUP BY clause of the SELECT</p><p>statement, and the horizontal headings are determined by the field listed after the PIVOT keyword.</p><p>For more information about joins, type SQL joins in the Office Assistant or on the Answer Wizard tab in the Microsoft Access</p><p>Help window, and then click Search.</p><p>O-Level Scanner Application Tools</p><p>Diagnostic Menu</p><p>Service parameters</p><p>Set Switch Procedure</p><p>Print ROI</p><p>Service Menu</p><p>Backup/Restore</p><p>Error Log Viewer</p><p>Features</p><p>Overview</p><p>Error Severity Definitions</p><p>Error Log Viewer User Interface</p><p>LogViewer Window</p><p>Filter Dialog Box</p><p>Search Dialog Box</p><p>Configuring the LogViewer Window</p><p>Refreshing the LogViewer Window</p><p>Saving USP Log Files</p><p>Process Monitor</p><p>Process Monitor Overview</p><p>Using the Process Monitor</p><p>Bug Report</p><p>Introduction</p><p>Producing and Saving Bugrep</p><p>Cleanup Bugrep</p><p>Exporting Bugrep</p><p>Sending Bug Reports</p><p>Service Terminal</p><p>Misc Menu</p><p>Classify Protocols</p><p>Preset Post Processing</p><p>LogBook</p><p>Starting LogBook</p><p>The LogBook Window</p><p>User Profiles</p><p>Using LogBook-Recommended Method</p><p>Adding an Event to the LogBook</p><p>Using the Operator Profile</p><p>Using the Service Profile (for Service Personnel Only)</p><p>Updating an Event to the LogBook</p><p>Using the Operator Profile</p><p>Using the Service Profile (for Service Personnel Only)</p><p>Using Filters</p><p>Filter by UID</p><p>Filter by Date</p><p>Printing the LogBook</p><p>The Help Menu</p><p>Default Storage Devices</p><p>Show Tube Heat</p><p>Gantry Shutdown</p><p>Prepare Movies</p><p>FTP Movies</p><p>Remove Movies</p><p>Service Tools (O-Level )</p><p>Coast Down Test</p><p>To perform the test:</p><p>Tube History</p><p>Cumulative Shot Area</p><p>Report Area</p><p>Query Area</p><p>Charting Area</p><p>Controller Utilities</p><p>Burning Application Flash</p><p>Burning Boot Flash</p><p>Tilt Calibration</p><p>Couch Vertical Calibration</p><p>Rotor Tools</p><p>SpindleBlok Commissioning</p><p>Performance Tests</p><p>DMC Host Utility</p><p>A Plane Tab</p><p>Reading the A Plane Calibration from File into the GUI</p><p>Manually Entering A Plane Calibration Into The GUI</p><p>Clearing the A Plane GUI</p><p>Writing A Plane Calibration To NVRAM</p><p>Reading A Plane Calibration From NVRAM</p><p>Entering The A Plane Serial Number</p><p>A Offsets Tab</p><p>Manually Entering A Offsets Calibration Into The GUI</p><p>Clearing the A Plane GUI</p><p>P Plane Tab</p><p>P Plane Data Sheet</p><p>Manually Entering The P Plane Calibration Into The GUI</p><p>Clearing the P Plane GUI</p><p>Writing P Plane Calibration To NVRAM</p><p>Reading P Plane Calibration From NVRAM.</p><p>Entering The P Plane (DMS) Serial Number.</p><p>Z RPM Tab</p><p>Obtaining Z Alignment Calibration</p><p>Manually Entering The Z Alignment Calibration Into The GUI</p><p>Clearing the Z RPM GUI</p><p>Writing The Z alignment Calibration Into The NVRAM</p><p>Reading The Z alignment Calibration From NVRAM</p><p>Go2Position Tab On Host Application</p><p>Temperature Tab</p><p>Manually Entering The Temperature Calibration Into The GUI</p><p>Clearing the Temperature Calibration GUI</p><p>Writing Temperature Calibration Into The NVRAM</p><p>Reading Temperature Calibration From NVRAM</p><p>Bug Report</p><p>Introduction</p><p>Producing and Saving Bugrep</p><p>Cleanup Bugrep</p><p>Exporting Bugrep</p><p>Sending Bug Reports</p><p>Bugrep Analyzer/Viewer</p><p>Bugrep User Interface</p><p>Using the Bugrep Viewer</p><p>Interacting with Bugrep Files</p><p>Log File Window Navigation</p><p>Export / Send Reports</p><p>Exporting Selected Bugrep Files</p><p>Removing Bugrep Reports from the System</p><p>Bugrep Viewer Options</p><p>Analyze Current State</p><p>View Multiple Analyses</p><p>Running System Monitor on Bugrep</p><p>Opening a UNIX Console</p><p>Tips on how to use SQL for queries</p><p>Using Data Manipulation Language</p><p>Retrieving Records</p><p>Restricting the Result Set</p><p>Sorting the Result Set</p><p>Using Aggregate Functions to Work with Values</p><p>Grouping Records in a Result Set</p><p>Intermediate Data Manipulation Language</p><p>Predicates</p><p>The ALL keyword</p><p>The DISTINCT keyword</p><p>The DISTINCTROW keyword</p><p>The TOP keyword</p><p>SQL Expressions</p><p>The IN operator</p><p>The BETWEEN operator</p><p>The LIKE operator</p><p>The IS NULL operator</p><p>Subqueries</p><p>The IN subquery</p><p>The ANY/SOME/ALL subqueries</p><p>The EXISTS subquery</p><p>Joins</p><p>INNER JOINs</p><p>OUTER JOINs</p><p>The Cartesian product</p><p>The UNION operator</p><p>The TRANSFORM statement</p><p>2005-05-19T13:33:03-0400</p><p>Cleveland, Ohio 44143 U.S.A.</p><p>Rebecca Nemenz</p><p>I am approving this document</p><p>2</p><p>Print ROI ............................................................................................................................................................. 3</p><p>Service Menu 4</p><p>Backup/Restore .................................................................................................................................................. 4</p><p>Error Log Viewer................................................................................................................................................. 4</p><p>Features ........................................................................................................................................................ 4</p><p>Overview ....................................................................................................................................................... 5</p><p>Error Severity Definitions............................................................................................................................... 6</p><p>Error Log Viewer User Interface ......................................................................................................................... 6</p><p>LogViewer Window........................................................................................................................................ 6</p><p>Filter Dialog Box ............................................................................................................................................ 7</p><p>Search Dialog Box......................................................................................................................................... 8</p><p>Configuring the LogViewer Window .............................................................................................................. 9</p><p>Refreshing the LogViewer Window ............................................................................................................... 9</p><p>Saving USP Log Files ................................................................................................................................... 9</p><p>Process Monitor.................................................................................................................................................. 10</p><p>Process Monitor Overview ............................................................................................................................ 10</p><p>Using the Process Monitor ............................................................................................................................ 10</p><p>Bug Report.......................................................................................................................................................... 11</p><p>Introduction.................................................................................................................................................... 11</p><p>Producing and Saving Bugrep....................................................................................................................... 11</p><p>Cleanup Bugrep ............................................................................................................................................ 12</p><p>Exporting Bugrep........................................................................................................................................... 12</p><p>Service Terminal................................................................................................................................................. 13</p><p>Misc Menu 13</p><p>Classify Protocols ............................................................................................................................................... 13</p><p>Preset Post Processing ...................................................................................................................................... 13</p><p>LogBook.............................................................................................................................................................. 13</p><p>Starting LogBook........................................................................................................................................... 14</p><p>The LogBook Window ................................................................................................................................... 14</p><p>User Profiles.................................................................................................................................................. 14</p><p>Using LogBook-Recommended Method ....................................................................................................... 15</p><p>Adding an Event to the LogBook................................................................................................................... 15</p><p>Philips Medical Systems Confidential and Proprietary Information II</p><p>Contents</p><p>Updating an Event to the LogBook................................................................................................................ 17</p><p>Using Filters .................................................................................................................................................. 18</p><p>Printing the LogBook ..................................................................................................................................... 19</p><p>The Help Menu.............................................................................................................................................. 19</p><p>Default Storage Devices ..................................................................................................................................... 19</p><p>Show Tube Heat ................................................................................................................................................. 19</p><p>Gantry Shutdown ................................................................................................................................................ 20</p><p>Prepare Movies................................................................................................................................................... 20</p><p>FTP Movies......................................................................................................................................................... 20</p><p>Remove Movies .................................................................................................................................................. 20</p><p>Service Tools (O-Level ) .................................................................................................................... 21</p><p>Coast Down Test 22</p><p>To perform the test: ............................................................................................................................................ 23</p><p>Tube History 24</p><p>Cumulative Shot Area......................................................................................................................................... 25</p><p>Report Area ........................................................................................................................................................ 25</p><p>Query Area ......................................................................................................................................................... 26</p><p>Charting Area...................................................................................................................................................... 27</p><p>Controller Utilities 28</p><p>Burning Application Flash ................................................................................................................................... 28</p><p>Burning Boot Flash ............................................................................................................................................. 29</p><p>Tilt Calibration 30</p><p>Couch Vertical Calibration 30</p><p>Rotor Tools 31</p><p>SpindleBlok Commissioning ...............................................................................................................................</p><p>31</p><p>Performance Tests 32</p><p>DMC Host Utility ................................................................................................................................ 33</p><p>A Plane Tab 35</p><p>Reading the A Plane Calibration from File into the GUI ..................................................................................... 36</p><p>Manually Entering A Plane Calibration Into The GUI.......................................................................................... 36</p><p>Clearing the A Plane GUI ................................................................................................................................... 36</p><p>Writing A Plane Calibration To NVRAM.............................................................................................................. 36</p><p>Reading A Plane Calibration From NVRAM ....................................................................................................... 37</p><p>Entering The A Plane Serial Number.................................................................................................................. 37</p><p>Philips Medical Systems Confidential and Proprietary Information III</p><p>Contents</p><p>A Offsets Tab 38</p><p>Manually Entering A Offsets Calibration Into The GUI ....................................................................................... 39</p><p>Clearing the A Plane GUI ................................................................................................................................... 40</p><p>P Plane Tab 41</p><p>P Plane Data Sheet ............................................................................................................................................ 42</p><p>Manually Entering The P Plane Calibration Into The GUI .................................................................................. 44</p><p>Clearing the P Plane GUI ................................................................................................................................... 45</p><p>Writing P Plane Calibration To NVRAM.............................................................................................................. 45</p><p>Reading P Plane Calibration From NVRAM. ...................................................................................................... 45</p><p>Entering The P Plane (DMS) Serial Number. ..................................................................................................... 45</p><p>Z RPM Tab 46</p><p>Obtaining Z Alignment Calibration ...................................................................................................................... 47</p><p>Manually Entering The Z Alignment Calibration Into The GUI............................................................................ 47</p><p>Clearing the Z RPM GUI..................................................................................................................................... 47</p><p>Writing The Z alignment Calibration Into The NVRAM ....................................................................................... 47</p><p>Reading The Z alignment Calibration From NVRAM.......................................................................................... 48</p><p>Go2Position Tab On Host Application ................................................................................................................ 48</p><p>Temperature Tab 50</p><p>Manually Entering The Temperature Calibration Into The GUI .......................................................................... 51</p><p>Clearing the Temperature Calibration GUI ......................................................................................................... 51</p><p>Writing Temperature Calibration Into The NVRAM............................................................................................. 51</p><p>Reading Temperature Calibration From NVRAM ............................................................................................... 51</p><p>Bug Report ........................................................................................................................................ 52</p><p>Introduction 52</p><p>Producing and Saving Bugrep 52</p><p>Cleanup Bugrep 53</p><p>Exporting Bugrep 54</p><p>Sending Bug Reports 54</p><p>Bugrep Analyzer/Viewer 54</p><p>Bugrep User Interface 55</p><p>Using the Bugrep Viewer 56</p><p>Interacting with Bugrep Files .............................................................................................................................. 57</p><p>Log File Window Navigation ............................................................................................................................... 59</p><p>Export / Send Reports 60</p><p>Exporting Selected Bugrep Files ........................................................................................................................ 60</p><p>Philips Medical Systems Confidential and Proprietary Information IV</p><p>Contents</p><p>Removing Bugrep Reports from the System 60</p><p>Bugrep Viewer Options 61</p><p>Analyze Current State......................................................................................................................................... 61</p><p>View Multiple Analyses ....................................................................................................................................... 61</p><p>Running System Monitor on Bugrep................................................................................................................... 61</p><p>Opening a UNIX Console ................................................................................................................................... 62</p><p>Tips on how to use SQL for queries ................................................................................................. 63</p><p>Using Data Manipulation Language 64</p><p>Retrieving Records........................................................................................................................................ 64</p><p>Restricting the Result Set.............................................................................................................................. 65</p><p>Sorting the Result Set ................................................................................................................................... 66</p><p>Using Aggregate Functions to Work with Values .......................................................................................... 66</p><p>Grouping Records in a Result Set................................................................................................................. 68</p><p>Intermediate Data Manipulation Language 68</p><p>Predicates ..................................................................................................................................................... 69</p><p>The ALL keyword .......................................................................................................................................... 69</p><p>The DISTINCT keyword ................................................................................................................................ 69</p><p>The DISTINCTROW keyword ....................................................................................................................... 69</p><p>The TOP keyword ......................................................................................................................................... 70</p><p>SQL Expressions 70</p><p>The IN operator ............................................................................................................................................. 71</p><p>The BETWEEN operator ............................................................................................................................... 71</p><p>The LIKE operator ......................................................................................................................................... 72</p><p>The IS NULL operator ................................................................................................................................... 73</p><p>Subqueries 74</p><p>The IN subquery............................................................................................................................................</p><p>74</p><p>The ANY/SOME/ALL subqueries .................................................................................................................. 74</p><p>The EXISTS subquery................................................................................................................................... 75</p><p>Joins 76</p><p>INNER JOINs ................................................................................................................................................ 76</p><p>OUTER JOINs............................................................................................................................................... 77</p><p>The Cartesian product................................................................................................................................... 78</p><p>The UNION operator ..................................................................................................................................... 78</p><p>The TRANSFORM statement........................................................................................................................ 79</p><p>Philips Medical Systems Confidential and Proprietary Information 1</p><p>O-Level Scanner Application ToolsBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>O-Level Scanner Application Tools</p><p>This section covers the Tools available in the Scanner Application under O-Level.</p><p>Diagnostic Menu</p><p>On the Scanner Application, click Home > Utilities > Diagnostic.</p><p>Service parameters</p><p>This section describes the user-defined system switches that</p><p>control different functions of the system for troubleshooting</p><p>purposes. All of the switches are ON/OFF and only the RCOM disk</p><p>pattern switches have pre-set values. Most of the switches are</p><p>independent. Use them in different combinations for diagnostic</p><p>purposes only. Each switch has a default state.</p><p>Switches are divided into two groups:</p><p>• Reconstruction Parameters</p><p>• Scan Parameters</p><p>Philips Medical Systems Confidential and Proprietary Information 2</p><p>O-Level Scanner Application ToolsBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>The Reconstruction Parameter switches allow performing reconstruction of the image without using the appropriate calibration</p><p>and are as follows:</p><p>• Phantom Calibrations removes the Phantom Calibration.</p><p>• Image Balance removes the Image Balance Calibration.</p><p>• Slice Normalisation disables the Slice Normalisation.</p><p>The Scan Parameters switches are:</p><p>• No Rotation disables the rotor rotation. Allows performing a scan without rotation</p><p>• X-Ray disables X-Ray during a scan. Allows performing the scan without X-Ray</p><p>• Dose control disables Dose control.</p><p>• Z-control disables Z- control (Control of the A-Plane Z-position according to the tube heat units)</p><p>• RCOM Disk Pattern provides synthetic data for the Data Path troubleshooting</p><p>• CDRH switch enables DMS modules to provide status information.</p><p>NOTE This switch has no limitations and does not interfere with the scan even if a faulty modules exist.</p><p>Set Switch Procedure</p><p>Set the switches as follows:</p><p>1 From the Diagnostic menu, click Service Parameters. The Configuration window appears with the Reconstruction</p><p>Parameters dialog box open.</p><p>2 Set the switch settings and click OK.</p><p>3 Click Scan Parameters. The Scan Parameters dialog box appears (see Figure 13 - 86).</p><p>4 Set the switch settings and click OK.</p><p>After setting the switches it is possible to perform a scan via the normal operator window in the service mode only, while the</p><p>switches overrule the scan parameters that were defined in the scan protocol (for example, if a rotational mode was selected</p><p>and the rotation switch is set to zero - the scan is a static scan).Reset the switches to their default state after finishing the</p><p>troubleshooting and before returning the system to the user.</p><p>Philips Medical Systems Confidential and Proprietary Information 3</p><p>O-Level Scanner Application ToolsBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Print ROI</p><p>Print ROI enables the user to print</p><p>the CT values (pixel-by-pixel) of a</p><p>selected ROI on-screen.</p><p>1 From the Diagnostics menu, click</p><p>Print ROI. The Archives Manager</p><p>opens.</p><p>2 Select one or more images and</p><p>click OK.</p><p>3 Draw one or more ROI's on the</p><p>image.</p><p>4 From the Graphics menu, click</p><p>Print ROI. Select one of the</p><p>drawn ROI's.</p><p>5 The CT value table always</p><p>appears in the last panel.</p><p>6 The CT value table is updated to reflect the last ROI selected. The CT value table can be printed on MasterFilm as any CT</p><p>image.</p><p>For a large ROI, the displayed CT value table contains only the central portion of the ROI. For a small ROI, the table can</p><p>include * , that indicate values that are out of the ROI (normally in corners).</p><p>View all values for the selected ROI as follows:</p><p>1 In Windows Explorer, navigate to c:\usr\diamond.data.</p><p>2 Right-click on ROI_values.txt and, from the shortcut menu, click Open with | Choose Program.</p><p>3 From the Open With dialog, select Wordpad.</p><p>The text file contains:</p><p>• Full CT value table</p><p>• Mean</p><p>• SD</p><p>• Area</p><p>• The abridged table that appears on the screen</p><p>Philips Medical Systems Confidential and Proprietary Information 4</p><p>O-Level Scanner Application ToolsBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Service Menu</p><p>On the Scanner Application, click Home > Utilities > Service.</p><p>Backup/Restore</p><p>**Full Information Coming Soon**</p><p>Error Log Viewer</p><p>Features</p><p>The Error Log collects error information during normal operation and stores it for troubleshooting use in a special error log file.</p><p>The error log file gathers the information generated during the main steps of nominal operation (log on,</p><p>new patient / study, scan protocol, Gantry switch ON / OFF, tube counter etc.) and the errors. An error is reported to error log</p><p>in each case when a hardware or software module cannot accomplish the operation/request.</p><p>All system components report errors to the error log file. All errors are reported in the fixed format and can be filtered by</p><p>different criteria to ease the use of the information contained in the error log.</p><p>The following filter capabilities are available by:</p><p>• User profile</p><p>• Operator</p><p>• Technician</p><p>• Programmer (Manufacturer's Research and Development Personnel).</p><p>Errors are defined by severity as follows:</p><p>• Critical-unrecoverable fatal error, scan fails</p><p>• Error-non-fatal error, most scans fails</p><p>• Warning-some error not causing the scan to stop happens during operation.</p><p>• Event -describes steps of nominal system operation</p><p>• Information-data about processes</p><p>Philips Medical Systems Confidential and Proprietary Information 5</p><p>O-Level Scanner Application ToolsBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>HTML files with explanations are associated to each error with a description of the error and suggestions for troubleshooting</p><p>for the service personnel.</p><p>The error log holds data information organized in FIFO (first in first out) for one month. Service engineers should preserve</p><p>current log files for later analysis.</p><p>Overview</p><p>The Error Log Viewer allows viewing log files that were created during nominal operation. It contains the following</p><p>features:</p><p>• Displays an online system error log</p><p>• Opens a specific error log file from a directory</p><p>• Searches for a string of up to 80 characters</p><p>• Sorts by any error viewer field</p><p>• Double-click on a Gantry error containing a message E ... (for example, E 20 3 20 0 15 ff 0) to open an HTML file.</p><p>The HTML file contains the following fields: Error Code and Error Text, Error Explanation, Possible Cause, and Service</p><p>Measures.</p><p>• Supports stand-alone running on computers without USP installation</p><p>• Opens a log file in errors only mode to select some specific error line</p><p>• Change filter to show nominal events in addition to errors.</p><p>When a fault is detected by the software, it is more problematic. In most cases, the software cannot detect the real reason for</p><p>problematic behavior without special testing.</p><p>System specific field experience allows for mapping of frequent hardware faults</p><p>to corresponding software error messages. Therefore, error log based recommendations for problem localization are</p><p>supported by two separate mechanisms:</p><p>• Reporting to an error log in a form understandable by service personnel and with the necessary level of details</p><p>• Error log analysis and automatic service recommendations (HTML)</p><p>In more complicated multi-line error log analysis, information management is addressed by filters with lists that contain all</p><p>possible values for specific fields.</p><p>The Error Log Viewer supports saving/restoring of its specific configuration and has different presets for service personnel and</p><p>R&D. With every logon, the Error Log Viewer opens with the predefined default settings.</p><p>Philips Medical Systems Confidential and Proprietary Information 6</p><p>O-Level Scanner Application ToolsBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Error Severity Definitions</p><p>The following is a list of error definitions according to declining severity:</p><p>Critical an unrecoverable fatal error; the scan fails</p><p>Error a non-fatal error; the scan fails, causes a critical error, and continues</p><p>Warning an error during operation that does not stop the scan</p><p>Event describes system operation</p><p>Information describes steps of nominal system operation</p><p>Error Log Viewer User Interface</p><p>LogViewer Window</p><p>In either the user mode or the service mode, from the Service menu, click Error Log Viewer. The LogViewer window appears</p><p>Figure 1 - 1: LogViewer Window.</p><p>Philips Medical Systems Confidential and Proprietary Information 7</p><p>O-Level Scanner Application ToolsBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>• To sort the events, click on a field heading as in Windows Explorer.</p><p>• To create a filter, click Create Filter, or from the Tools menu, click Filter. The Filter dialog box appears (see Figure 1 - 2).</p><p>• After creating a filter, the filter check box is selected. Clear the filter check box to view the events without the filter.</p><p>Filter Dialog Box</p><p>To filter the events in the LogViewer window (see Figure 1 - 1) by the categories that appear in the Filter dialog box (see</p><p>Figure 1 - 2), two options are available:</p><p>• Immediate filtering</p><p>• Create and save a filter for future use</p><p>NOTE The Filter Level (Med/Prog/Tech) function is not yet implemented. If you select the Filter Level option, a blank</p><p>screen appears.</p><p>Immediate Filtering:</p><p>1 On the LogViewer window, click Create Filter or from the Tools</p><p>menu, click Filter | Immediate. The Filter dialog box appears.</p><p>2 Select the categories for filtering.</p><p>3 Click OK.</p><p>Create and Save a Filter:</p><p>1 From the Tools menu, click Filter > Create and Save. The</p><p>Filter dialog box appears.</p><p>2 Select the categories for filtering.</p><p>3 Click Save. A Save as dialog box appears.</p><p>4 Enter a name and path for the filter and click Save.</p><p>To use the saved filter in the future, from the Tools menu, click</p><p>Filter | Open.</p><p>Figure 1 - 2: Filter Dialog Box</p><p>Philips Medical Systems Confidential and Proprietary Information 8</p><p>O-Level Scanner Application ToolsBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Search Dialog Box</p><p>To search for events in the LogViewer window, proceed as</p><p>follows:</p><p>1 From the Tools menu, click Search. The Search dialog box</p><p>appears (see Figure 1 - 3).</p><p>2 Enter up to 80 characters in the search string text box.</p><p>3 Select one or more fields in which to conduct the search.</p><p>4 Click OK to begin the search. The first event in the</p><p>LogViewer window that meets the search parameters is</p><p>selected.</p><p>5 To continue to the next event that meets the search</p><p>parameters, from the Tools menu, click Search Again.</p><p>6 Repeat step 5 as often as necessary.</p><p>Figure 1 - 3: Search Dialog Box</p><p>Philips Medical Systems Confidential and Proprietary Information 9</p><p>O-Level Scanner Application ToolsBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Configuring the LogViewer Window</p><p>To configure the fields in the LogViewer window, proceed as follows:</p><p>1 From the View menu, select the fields that are to appear in the LogViewer window.</p><p>2 To save the new configuration (including filters), from the File menu, click Save Configuration. A</p><p>Save as dialog box appears.</p><p>3 Enter a name and path for the new configuration and click Save.</p><p>4 To use the saved configuration in the future, from the File menu, click Open Configuration.</p><p>5 Select from the saved Configuration settings and click Open.</p><p>Refreshing the LogViewer Window</p><p>The LogViewer window can be refreshed either automatically or manually.</p><p>• To refresh automatically, from the File menu click Online. The LogViewer Window refreshes with each new message.</p><p>• To refresh manually, from the Tools menu, click Refresh. The LogViewer Window refreshes with all of the accumulated</p><p>messages.</p><p>Saving USP Log Files</p><p>1 To save the USP log file for sending, from the File menu, click Save as. A Save as dialog box appears.</p><p>2 Enter a name and path for the new configuration and click Save.</p><p>3 To open a saved USP log file, from the File menu, click Load log file. The selected file appears in the LogViewer window.</p><p>Figure 1 - 4: View Menu</p><p>Philips Medical Systems Confidential and Proprietary Information 10</p><p>O-Level Scanner Application ToolsBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Process Monitor</p><p>Process Monitor Overview</p><p>There are a lot of the processes running simultaneously and providing normal system functioning. They are running in tight</p><p>cooperation with each other. Failure of any of them causes different errors and sometimes cause the system to suspend</p><p>and/or crash.</p><p>The Process Monitoring Utility is intended for monitoring some of the main processes and provide an indication about failure</p><p>any of them.</p><p>Using the Process Monitor</p><p>1 To start the Process Monitor, on the Service menu, click Process Monitor. The</p><p>Process Monitor opens (in compact mode showing only the following processes:</p><p>• Scan Protocol</p><p>• Scanner Server</p><p>• Master Server</p><p>• IRS Server</p><p>A grey button indicates a properly functioning process.</p><p>A red button indicates a failed process.</p><p>2 Click any of the first four buttons to open the relevant log file.</p><p>3 Click USP on the lower part of the Process Monitor to see more processes. To view</p><p>and analyze details of the process or the failure click on the appropriate process</p><p>button.</p><p>The same color indicator rules are applied to all this indicators but windows with the</p><p>details do not opened.</p><p>Figure 1 - 5: Process Monitor</p><p>Philips Medical Systems Confidential and Proprietary Information 11</p><p>O-Level Scanner Application ToolsBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Bug Report</p><p>Introduction</p><p>• The purpose of the Bugrep utility is to save all of the relevant information about a specific problem for postmortem/ remote</p><p>analysis. Correct bug reports allow troubleshooting without the need for problem reproducing.</p><p>• The Bugrep utility saves all of the data/log files that describe the current system status and previous operation.</p><p>• The Bugrep utility supports the management of reports on the local disk (compression, clean-up) and exports them to the</p><p>Brilliance CT EOD or sends them by e-mail to the Service Support Center (if the system configured for this option).</p><p>• The Bugrep default behavior is field-oriented-"save" means export in compressed form (saves all bug reports as a .tar file).</p><p>Producing and Saving Bugrep</p><p>1 On the Service menu, click Bug Report. The Bug Report dialog box appears</p><p>(see Figure 1 - 6).</p><p>2 Enter information in the Bug Report dialog box as follows:</p><p>a In the Problem Name field, enter a title or a short complaint description.</p><p>b In the Submitter field, enter a name/ corresponding field of a Bugrep utility.</p><p>c Click to clear the Save IRS state check box, if the problem has nothing to do</p><p>with the IRS.</p><p>d Verify that Compress Report is selected,</p><p>to store in a compressed format.</p><p>e Select the Send Report By e-Mail- if you would like to send the Bugrep to</p><p>Support Center automatically. This option is active only if the system has an</p><p>e-mail option and it been configured to support this feature.</p><p>f In the Problem Description field, enter more details, such as description,</p><p>notes, or errors that appear during the problem.</p><p>3 Click Save Report to create the Bugrep and to save it in the d:/Bugrep/Reports</p><p>directory as a .tar file.</p><p>4 Click Clean up to delete old reports from the Archive.</p><p>5 Click Export to export reports to the EOD. or send by e-mail.</p><p>Figure 1 - 6: Bug Report Dialog Box</p><p>Philips Medical Systems Confidential and Proprietary Information 12</p><p>O-Level Scanner Application ToolsBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Cleanup Bugrep</p><p>1 On the Service menu, click Bugrep. The Bug Report dialog box</p><p>appears (see Figure 1 - 6).</p><p>2 Click Clean up to delete old reports from the Archive. The Cleanup</p><p>Archive window appears (see Figure 1 - 7).</p><p>3 Select a report in the Cleanup Archive list to be deleted and click</p><p>Remove to delete them.</p><p>To select a consecutive series of reports, select the first report and</p><p>press Shift and click on the last report.</p><p>To select a non-consecutive series of reports, select the first report</p><p>and press Ctrl and click on additional reports.</p><p>4 Click Yes in the confirmation window to delete the selected reports.</p><p>Click No to cancel delete, and to return to the Cleanup Archive</p><p>window.</p><p>Exporting Bugrep</p><p>1 On the Service menu, click Bugrep. The Bug Report dialog box appears (see</p><p>Figure 1 - 6).</p><p>2 Click Export to EOD to save reports from the Archive to the EOD, or click Send By</p><p>e-Mail, to send the reports by e-Mail/ Site Manager to the Service Support Center.</p><p>The Export Archive window appears (see Figure Figure 1 - 8).</p><p>3 To select a consecutive series of reports, select the first report and press Shift and</p><p>click on the last report.</p><p>To select a non-consecutive series of reports, select the first report and press Ctrl</p><p>and click on additional reports.</p><p>Sending Bug Reports</p><p>Sending Bug Reports can be accomplished either automatically or manually from the Bugrep Utility or from the LogBook.</p><p>In either service tool, select the Send by E-mail option.</p><p>Figure 1 - 7: Cleanup Archive</p><p>Figure 1 - 8: Export Archive</p><p>Philips Medical Systems Confidential and Proprietary Information 13</p><p>O-Level Scanner Application ToolsBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Service Terminal</p><p>**Full Information Coming Soon****</p><p>Misc Menu</p><p>Classify Protocols</p><p>See the Brilliance CT 16 Power Vol. 1 - Instructions for Use.</p><p>Preset Post Processing</p><p>See the Brilliance CT 16 Power Vol. 1 - Instructions for Use.</p><p>LogBook</p><p>The Logbook application is intended for the recording of every service event that occurs during the entire lifetime of the</p><p>system. This electronic logbook replaces the paper logbook currently in use.</p><p>Scanner technologists, field service personnel and service centers are the primary users of this application:</p><p>• Scanner technologists can report information regarding the errors, artifacts, system downtime, and any other issues</p><p>concerning system functioning.</p><p>• Field service personnel can attach system bug reports, report corrective actions taken, record replaced parts, and other</p><p>information.</p><p>• Service centers are able to remotely obtain comprehensive information from sites and analyze the recorded information.</p><p>This enables the planning of preventive actions to minimize the system downtime.</p><p>Each recorded event receives a Unique Identification Number (UID). Records cannot be deleted from the logbook. To correct</p><p>or update previously recorded events, additional records concerning the event must be added.</p><p>The entries relating to the same event are numbered sequentially so that each event can be differentiated from all others.</p><p>Philips Medical Systems Confidential and Proprietary Information 14</p><p>O-Level Scanner Application ToolsBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Starting LogBook</p><p>1 From the Misc menu, click LogBook. The User Profile selection dialog opens</p><p>(see Figure 1 - 9).</p><p>2 Select a user profile (Operator or Service) and click OK. The LogBook window</p><p>opens. When opened for the first time, the Logbook window appears as</p><p>follows (see Figure 1 - 10 ):</p><p>Figure 1 - 10: Empty LogBook Window</p><p>The LogBook Window</p><p>• Access commands either from the Menu Bar or from the icons on the Toolbar.</p><p>• You can display the entire Event List, or select a filter to display the events according to UID number or by dates.</p><p>• The Status Bar displays the current user profile. When the date filter is used, the date range requested is also displayed.</p><p>User Profiles</p><p>The User Profile selection dialog opens with you open LogBook. The user profile can be changed during LogBook operation.</p><p>The LogBook offers two user profiles:</p><p>• Operator</p><p>• Service</p><p>NOTE When starting LogBook, the default setting is the operator profile.</p><p>The Operator profile enables the user to add a new event, record the description of the event, and to close the event.</p><p>The Service profile enables the user to add a new event, record detailed information regarding service procedures related to</p><p>the event, and to close the event.</p><p>Figure 1 - 9: User Profile Selection Dialog</p><p>Philips Medical Systems Confidential and Proprietary Information 15</p><p>O-Level Scanner Application ToolsBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Set the desired profile as follows:</p><p>1 From the File menu, click Change user profile or click . The Pick an option window opens.</p><p>2 Select either Operator or Service and click OK.</p><p>The current user status is listed in the status bar.</p><p>Using LogBook-Recommended Method</p><p>An event is opened either by the scanner technologist or by the field service personnel. At this stage, the status of the event is</p><p>OPEN.</p><p>The event is then diagnosed and solved by the service personnel who lists the status as FIXED.</p><p>Finally, after the repair, the scanner technologist lists the event as CLOSED and enters the total Downtime for the entire event.</p><p>Adding an Event to the LogBook</p><p>Using the Operator Profile</p><p>Add an event in LogBook as follows:</p><p>1 Select the Operator profile User Profiles.</p><p>2 From the Insert menu, click Add new event or click . The operator's Add new event window opens.</p><p>Note that in the title bar of the Add new event window, an new UID number is already assigned to the new event.</p><p>Fill in the relevant information in the text boxes. Some text boxes are optional, but it is recommended that all information be</p><p>recorded.</p><p>3 In the Submitter's Name box, type your name (required field).</p><p>4 In the Down time box, type in the amount of machine downtime as a result of the event in hh:mm format (optional field).</p><p>5 In the Event Description box, type an account of the event (required field).</p><p>6 Click one of the Status options depending on the current event status (Open, Fixed, or Closed).</p><p>7 Click Generate Bugrep if a Bug Report is desired (optional field).</p><p>8 Click an appropriate option:</p><p>a Compress files-the default setting. Saving reports in compressed form is recommended. Saving without compression</p><p>takes slightly less time.</p><p>Philips Medical Systems Confidential and Proprietary Information 16</p><p>O-Level Scanner Application ToolsBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>b Save IRS State-the default setting. This option saves the core IRS files in the Bug Report.</p><p>c Send by E-Mail-to automatically send the Bugrep by e-mail to the Customer Support Center (this option is available only</p><p>if the system was configured for e-mail transfer.</p><p>9 Click OK to add the event to the event list. The new event now appears in the event list in the LogBook. It has a Unique</p><p>Identification Number (UID) that appears in red. Any subsequent updates pertaining to that event have consecutive UID</p><p>numbers</p><p>in black.</p><p>NOTE Once an event has been recorded into LogBook, it cannot be erased or modified. To correct the event, you</p><p>must update the event with a new entry detailing the correction (see Updating an Event to the LogBook).</p><p>Using the Service Profile (for Service Personnel Only)</p><p>1 Select the Service profile User Profiles.</p><p>2 From the Insert menu, click Add new event or click. The service Add new</p><p>event window opens.</p><p>Note that in the title bar of the Add new event window, an new UID number is</p><p>already assigned to the new event.</p><p>Fill in the relevant information in the text boxes. Some text boxes are</p><p>optional, but it is recommended that all information be recorded.</p><p>3 In the Submitter's Name box, type your name (required field).</p><p>4 In the Down time box, enter the amount of machine downtime as a result of</p><p>the event in hh:mm format (optional field).</p><p>5 In the Event Description box, enter an account of the event (required field).</p><p>6 In the Corrective Action box, enter a description of any service procedures</p><p>performed, such as diagnostic test, parts replacement, etc. (optional field).</p><p>7 In the Parts replaced P/N box, enter the Philips part number for any FRU</p><p>replaced during the service procedure (optional field).</p><p>8 Click one of the Status options depending on the current event status (Open,</p><p>Fixed, or Closed).</p><p>9 Click Generate Bugrep if a Bug Report is desired (optional field).</p><p>10 Click an appropriate option:</p><p>a Compress files-the default setting. Saving reports in compressed form is recommended. Saving without compression</p><p>takes slightly less time.</p><p>Figure 1 - 11: Service Add Event Dialog Box</p><p>Philips Medical Systems Confidential and Proprietary Information 17</p><p>O-Level Scanner Application ToolsBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>b Save IRS State-the default setting. This option saves the core IRS files in the Bug Report.</p><p>c Send by E-Mail-to automatically send the Bugrep by e-mail to the Customer Support Center (this option is available only</p><p>if the system was configured for e-mail transfer.</p><p>11 Click OK to add the event to the event list.</p><p>The new event now appears in the event list in the LogBook. It has a Unique Identification Number (UID) that appears in</p><p>red. Any subsequent entries pertaining to that event have consecutive UID numbers in black.</p><p>NOTE Once an event has been recorded into LogBook, it cannot be erased or modified. To correct the event, you</p><p>must update the event with a new entry detailing the correction (see Updating an Event to the LogBook).</p><p>Updating an Event to the LogBook</p><p>Generally events are opened by the operator. The event is updated either by the operator or by service personnel.</p><p>Using the Operator Profile</p><p>Update an event in LogBook as follows:</p><p>1 Select the Operator profile User Profiles.</p><p>2 Double-click the desired event field in the Event List. The operator's Update Event window opens.</p><p>Note that in the title bar of the Update event window, the UID of the current event is displayed along with a new subsequent</p><p>UID that links it to the current event.</p><p>3 Fill in the text boxes as previously explained in Adding an Event to the LogBook.</p><p>The update to the original event now appears in the event list in the LogBook. It has a Unique Identification Number (UID)</p><p>that appears in black. Any subsequent updates pertaining to that event have consecutive UID numbers in black.</p><p>NOTE Once an event update has been recorded into the LogBook, it cannot be erased or modified. You must update</p><p>the event with a new entry with the correction details (use the above procedure).</p><p>Philips Medical Systems Confidential and Proprietary Information 18</p><p>O-Level Scanner Application ToolsBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Using the Service Profile (for Service Personnel Only)</p><p>Update an event in the LogBook as follows:</p><p>1 Select the Service profile User Profiles.</p><p>2 Double-click the desired event field in the Event List. The operator's Update Event window opens.</p><p>Note that in the title bar of the Update event window, the UID of the current event is displayed along with a new</p><p>consecutively numbered UID linked to the current event.</p><p>3 Fill in the text boxes as previously explained in Section Adding an Event to the LogBook.</p><p>The update to the original event now appears in the event list in the LogBook. It has a Unique Identification Number (UID)</p><p>that appears in black. Any subsequent updates pertaining to that event have consecutive UID numbers in black.</p><p>NOTE Once an event update has been recorded into the LogBook, it cannot be erased or modified. You must update</p><p>the event with a new entry with the correction details (use the above procedure).</p><p>Using Filters</p><p>The Filters option enables you to re-arrange the Event List in the LogBook so that you can access necessary information</p><p>quickly.</p><p>The filter options are as follows:</p><p>• No filter</p><p>• Filter by UID</p><p>• Filter by Date</p><p>Filter by UID</p><p>Filter the Event List according to the UID number as follows:</p><p>1 From the Filters menu, click Filtered By UID or click . The UID filter window opens.</p><p>2 Select the event that you request and click OK.</p><p>3 The LogBook window now displays only the events with the UID that you requested.</p><p>Philips Medical Systems Confidential and Proprietary Information 19</p><p>O-Level Scanner Application ToolsBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Filter by Date</p><p>Filter the Event List according to the date as follows:</p><p>1 From the Filters menu, click Filtered By Date or click . The Time Period window opens.</p><p>2 Type in the requested range of dates and click OK.</p><p>3 The LogBook window now displays only the events in the time frame that you requested.</p><p>Printing the LogBook</p><p>You can send a printout of the LogBook to either a local or a network printer.</p><p>NOTE The LogBook prints the Event List as seen on the screen. Therefore, if you have used a filter to sort the Event</p><p>List, the printout will reflect the results on screen (WYSIWYG).</p><p>Print the LogBook as follows:</p><p>1 From the File menu, click Print LogBook or click . The LogBook is printed as an HTML file. The Microsoft Internet Explorer</p><p>opens.</p><p>2 In the Internet Explorer, select File | Print. Select the destination printer and click OK.</p><p>The Help Menu</p><p>The Help menu has two options:</p><p>• Help-online Help, this document.</p><p>• About LogBook 1.0-information regarding the version and copyright date.</p><p>Default Storage Devices</p><p>See the Brilliance CT 16 Power Vol. 1 - Instructions for Use.</p><p>Show Tube Heat</p><p>Philips Medical Systems Confidential and Proprietary Information 20</p><p>O-Level Scanner Application ToolsBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Gantry Shutdown</p><p>See the Brilliance CT 16 Power Vol. 1 - Instructions for Use.</p><p>Prepare Movies</p><p>See the Brilliance CT 16 Power Vol. 1 - Instructions for Use.</p><p>FTP Movies</p><p>See the Brilliance CT 16 Power Vol. 1 - Instructions for Use.</p><p>Remove Movies</p><p>See the Brilliance CT 16 Power Vol. 1 - Instructions for Use.</p><p>Philips Medical Systems Confidential and Proprietary Information 21</p><p>Service Tools (O-Level )Brilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Service Tools (O-Level )</p><p>Philips Medical Systems Confidential and Proprietary Information 22</p><p>Service Tools (O-Level )Brilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Coast Down Test</p><p>Coast Down Test measures the bearing friction of the</p><p>gantry. The test rotates the rotor to a certain speed,</p><p>and then measures the time it takes to coast down to</p><p>a stop.</p><p>Information area</p><p>Displays a series of messages to guide you</p><p>through the test.</p><p>Requested Rotor Speed (RPM’s)</p><p>Drop-down list that allows you to select the starting</p><p>rotor speed.</p><p>Begin Button</p><p>Starts the rotor. When rotor is up to speed, this</p><p>button changes to Start Test.</p><p>Abort Test Button</p><p>Aborts the test.</p><p>Speed</p><p>Indicates the speed from which the coast down</p><p>took place, and is displayed in rotations per minute.</p><p>Time</p><p>Indicates the time measured by the rotor controller</p><p>in the gantry, and is displayed in 10ths of</p><p>milliseconds.</p><p>Elapsed Time (seconds)</p><p>Counts each second while the coast down process</p><p>takes. When test is complete, this field indicates</p><p>the time measured by the test software.</p><p>Philips Medical Systems Confidential and Proprietary Information 23</p><p>Service Tools (O-Level )Brilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Graph</p><p>When the test is complete, the graph will plot the speed in RPM's against the time in seconds.</p><p>If you check the Logarithmic box, the graph will plot the natural logarithm of the speed against time. The large dashed lines</p><p>represent the mean and the small dashed lines represent the standard deviation.</p><p>To perform the test:</p><p>1 Select the starting rotor speed from the Requested Rotor Speed drop-down list.</p><p>2 Click the Begin button. The rotor will spin up to the requested speed, and you will see the message "Rotor is being started.</p><p>Please wait until rotor is up to speed."</p><p>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.</p><p>Press <Start Test> to begin coast down".</p><p>4 Click Start Test to start the coast down, and you will see the message "Coast down has been started. Please wait until rotor</p><p>stops."</p><p>5 When the rotor stops, you will see the message "Coast down complete! Press <Begin> to start a new test." This indicates</p><p>the test has completed successfully, and the time is displayed.</p><p>If the test software does not receive proper acknowledgement from the gantry during the test, you will see the message "Coast</p><p>down request failed. The Rotor is not acknowledging the coast down request. Suggest pressing <Abort Test>". If this message</p><p>appears, click on the Abort Test button and attempt the test again. At any time during the test, you may click Abort Test to</p><p>terminate the test.</p><p>If the bearings are in proper condition, the rotor should coast down in a specified time.</p><p>Philips Medical Systems Confidential and Proprietary Information 24</p><p>Service Tools (O-Level )Brilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Tube History</p><p>Tube History provides information about the use of the X-ray tube.</p><p>This tool tells how many exposures have been made and the</p><p>cumulative exposure time. Additionally, Tube History can display a</p><p>table of each shot made with important shot information displayed.</p><p>You can also query a database for specific tube information and</p><p>display graphs of this data.</p><p>Tube History uses the CAN Trace database. This database</p><p>contains all messages that are sent on the CAN. When a shot is</p><p>made, a GANTRY_SHOT_END_ANS and</p><p>GANTRY_SERIES_CANCEL_ANS message are sent after each</p><p>shot. Encoded in these two messages is X-ray tube exposure</p><p>information.</p><p>For each GANTRY_SHOT_END_ANS and</p><p>GANTRY_SERIES_CANCEL_ANS message received by</p><p>CanTraceServer, it records the associated shot information in</p><p>special "ShotsHistory" table. The table defaults to 50,000 entries.</p><p>Tube History acts as a client of CanTraceServer, and all reported</p><p>data is based on queries for data from the "ShotsHistory" table.</p><p>Tube History provides four areas to view tube history information</p><p>obtained from the CAN Trace database:</p><p>• Cumulative Shot Area</p><p>• Report Area</p><p>• Query Area</p><p>• Charting Area.</p><p>Philips Medical Systems Confidential and Proprietary Information 25</p><p>Service Tools (O-Level )Brilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Cumulative Shot Area</p><p>This area is at the top of the screen. There are two parts to the</p><p>display area. The columns on the left are totals from the time span</p><p>specified. This section shows the exposure count, exposure time</p><p>and arc count for the time indicated. The columns to the right show</p><p>the cumulative exposure count recorded by the RHOST, which is</p><p>the controller for the X-ray tube.</p><p>The left column shows the total exposure count measured on the</p><p>Gantry. The columns on the right are subject to a time span because</p><p>the data is collected by CanTraceServer, which is a monitoring</p><p>program running on the Host PC. The statistical analysis is</p><p>performed according to the data in the CanTrace.mdb file. The time</p><p>span applicable to the data is shown as "Totals From **** To *****".</p><p>Report Area</p><p>This area shows the results of queries made to the database in a table format.</p><p>Philips Medical Systems Confidential and Proprietary Information 26</p><p>Service Tools (O-Level )Brilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Query Area</p><p>The Query Area is just below the Report Area. Use Query Area to</p><p>execute predefined queries, save queries, and create user defined</p><p>queries.</p><p>Report Statement You can create a user-defined query by entering</p><p>appropriate SQL statements in this field.</p><p>New Report Name When you open Tube History, there is a default</p><p>query Select All From Tube History in this field,</p><p>and the Report Area will show the results of this</p><p>query. This query has all fields that relate to the tube.</p><p>Saved Reports To select predefined queries, use the drop-down list. All predefined queries and any saved queries will</p><p>appear in the list.</p><p>Save As Text To save results of a query, click the Save As Text button. This will save the current results from the Report</p><p>Area into the file C:\TubeHistory.txt in tabular format. This text file can be used independently, and it can</p><p>be copied and pasted to Excel or other data related programs, for example.</p><p>Requery When you select a query, the Report Area will not update until you click this button.</p><p>SaveQuery To save a query, enter a name in the New Report Name field, and click the SaveQuery button.</p><p>DeleteQuery To delete a query, select a query from the list and click the Delete Query button.</p><p>NOTE Data that relates to the tube is stored into the ShotsHistory table. Therefore, this tool allows you to save only</p><p>those queries that have a "FROM ShotsHistory" portion.</p><p>Philips Medical Systems Confidential and Proprietary Information 27</p><p>Service Tools (O-Level )Brilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Charting Area</p><p>This area graphically displays data from the Report Area. It can show</p><p>information in different plot types including bar, pie, X-Y, trends, 2D,</p><p>and 3D charts. At the top-left of this area there is a dropdown list that</p><p>shows the selectable plot types. At the top-right of this area, there are</p><p>check boxes to show and hide the following plot attributes:</p><p>Legend shows the names for the current series at the right.</p><p>Marks shows all values in all series with special marks.</p><p>Stack reorganizes all values in all series in such a manner that the</p><p>value from the next series will be always bigger that the</p><p>previous one.</p><p>In Rows flips series data from columns (the default) to rows (similar</p><p>to a vertical-horizontal flip in table data). To change the type</p><p>of the plot, select the appropriate one from the drop-down</p><p>list at top-left.</p><p>When a query is saved, the current chart setting are save along with</p><p>the query. These settings will be resorted when the query is selected</p><p>at a later time.</p><p>Tips for Queries and Charts</p><p>• All queries use standard SQL syntax. For more information on SQL</p><p>syntax see Tips on how to use SQL for queries.</p><p>• The chart shows the same data currently present in the report area.</p><p>• For "Legend" series names, the chart is looking for the name of the columns (the headers). These headers are formed from</p><p>fields that have been typed in a SELECT clause. To change the field name, use the AS flag. For example: "SELECT</p><p>lastMeasuredCurrent AS mA,..." will get mA as the name of the field. If you apply any math to the field, it will cause</p><p>"ExpressionN" as a name, unless you use the AS statement. For example: "SELECT lastMeasuredCurrent/100 AS mA,..."</p><p>• 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</p><p>"R1......RN" as the X-axis mark.</p><p>• Use conversion functions to manipulate data formats. For details, see Tips How to Work With SQL for Queries.</p><p>• VBScript functions can be used. For Example, to show date stamps on the X-axis use "Select CStr(ShotDate) as STime....".</p><p>• See Tips How to Work With SQL for Queries for mathematical, statistical, and other manipulations.</p><p>Philips Medical Systems Confidential and Proprietary Information 28</p><p>Service Tools (O-Level )Brilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Controller Utilities</p><p>Burning Application Flash</p><p>NOTE This assumes the release 2.0 Utility Server is being used.</p><p>1 On the O-Level Diagnostics Panel, click the Service Tools button.</p><p>2 On the Service Tools GUI, click on the Controller Utilities button .</p><p>3 Click the Connect button to connect to the Server.</p><p>4 Click on the Service mode option.</p><p>5 Click on the Connect to controller option.</p><p>6 For each Ghost, Couch, MDP, TDP, Rhost, and DMC board that is at 2.0; select that board and do the following:</p><p>a Select Toolbox.</p><p>b Select Application flash burner.</p><p>c On the Browser Window that opens, in the File Name field type C:\usr\diamond.root\GantryCPM\xxxxxx</p><p>Where, depending on the board, xxxxxx is:</p><p>GalaxyBd.bin</p><p>GHostBd.bin</p><p>RHostBd.bin</p><p>DMCBd.bin</p><p>MPBd.bin</p><p>TiltBd.bin</p><p>d After entering this full path information, click OK on the Browser Window to start burning Application Flash.</p><p>e When the burn process completes, click the Quit button on the Controller Utilities interface.</p><p>f Click the Continue button.</p><p>g Click the Return button.</p><p>h Click the Return button.</p><p>i To burn Application Flash for another board, click the Connect to controller. Otherwise, click Return.</p><p>Philips Medical Systems Confidential and Proprietary Information 29</p><p>Service Tools (O-Level )Brilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>j When you are finished burning Application Flash, click the Application Mode button to reset all the boards to Application</p><p>mode.</p><p>k When the Ordinary Text window displays Supreme Controller Mode:App, click the Exit button.</p><p>Burning Boot Flash</p><p>1 On the O-Level Diagnostics Panel, click the Service Tools button.</p><p>2 On the Service Tools GUI, click on the Controller Utilities button.</p><p>3 Click the Connect button to connect to the Server.</p><p>4 Click on the Service mode option.</p><p>5 Click on the Connect to controller option.</p><p>6 For each Ghost, Couch, MDP, TDP, Rhost, and DMC board that is at 2.0; select that board and do the following:</p><p>a Select Toolbox.</p><p>b Select Downloader.\</p><p>c On the Browser Window that opens, in the File Name field type</p><p>C:\usr\diamond.root\Diag\CPMIntFlash\CPMIntFlashImage.bin</p><p>d After entering this full path information, click OK on the Browser Window to start burning Boot Flash.</p><p>e When the burn process completes, click the Quit button on the Controller Utilities interface.</p><p>f Click the Continue button.</p><p>g Click the Return button.</p><p>h Click the Return button.</p><p>i To burn Boot Flash for another board, click the Connect to controller. Otherwise, click Return.</p><p>j When you are finished burning Boot Flash, click the Application Mode button to reset all the boards to Application</p><p>mode.</p><p>k When the Ordinary Text window displays Supreme Controller Mode:App, click the Exit button.</p><p>Philips Medical Systems Confidential and Proprietary Information 30</p><p>Service Tools (O-Level )Brilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Tilt Calibration</p><p>See the O-Level Calibration Manual.</p><p>Couch Vertical Calibration</p><p>See the O-Level Calibration Manual.</p><p>Philips Medical Systems Confidential and Proprietary Information 31</p><p>Service Tools (O-Level )Brilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Rotor Tools</p><p>SpindleBlok Commissioning</p><p>This tool is used to Commission the SpindleBlok.</p><p>The SpindleBlok eeprom version (address A01)</p><p>should be 040A. This version is read before doing</p><p>the commissioning.</p><p>1 Wait for the Gantry to power up.</p><p>2 Disable the Park of the Rotor.</p><p>3 Close the Estop.</p><p>4 Check the Release.</p><p>5 Initialize SpindleBlok registers.</p><p>6 Toggle IO Bit.</p><p>7 Setup Standard Commissioning.</p><p>8 Read and check the registers.</p><p>9 Perform Standard Commissioning.</p><p>10 Wait for End of Standard Commissioning.</p><p>11 Setup Extended Commissioning.</p><p>12 Perform Extended Commissioning.</p><p>13 Wait for End of Extended Commissioning.</p><p>14 Jog at a slow speed.</p><p>15 Stop the rotor and end of Commissioning.</p><p>NOTE During the Initialize and Check of SpindleBlok registers, the following file should be present. Otherwise the</p><p>commissioning will fail:</p><p>'C:/usr/diamond.root/bin/ServiceTools/help/HelpSBCommissioningPage_files/SGL_SB_040A_04302002.def'</p><p>Philips Medical Systems Confidential and Proprietary Information 32</p><p>Service Tools (O-Level )Brilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Performance Tests</p><p>See the O-Level Performance Manual.</p><p>Philips Medical Systems Confidential and Proprietary Information 33</p><p>DMC Host UtilityBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>DMC Host Utility</p><p>Start the DMC Utility by clicking Start > All Programs > DMC Utility > DMC Utility.</p><p>The Status Bar at the bottom of the window displays status information:</p><p>Status Displays messages during and after reading and writing calibration, and after an A Plane, P Plane, and UHR</p><p>move is initiated. The current message will remain in the Status field regardless of which tab is forward.</p><p>Closing and re-opening the application will clear the message.</p><p>Serial# Allows you to load in the A Plane and P Plane (DMS) serial numbers. When the A Plane tab is forward, click</p><p>on this field to load in the serial number. When the P Plane tab is forward, click on this field to load in the</p><p>serial number. The latest serial number will remain invisible regardless of which tab is forward. Closing and</p><p>re-opening the application will clear the message.</p><p>Motor Type Displays the motor type number when you open a JIG file (*.clb).</p><p>Philips Medical Systems Confidential and Proprietary Information 34</p><p>DMC Host UtilityBrilliance™CT 6-slice, 10-slice, 16-slice and 16 Power 1.2.5 O-Level Utilities Manual</p><p>Table 3 - 1: Status Messages</p><p>Button Message Meaning</p><p>GetAC Getting AC... Reading A Plane Calibration from NVRAM.</p><p>GetAC GetAColl status is OK A Plane read was successful.</p><p>SetAC Setting AC... Writing A Plane calibration to NVRAM.</p><p>SetAC SetAColl status is OK A Plane write was successful.</p><p>GetAOffset Getting OA... Reading A Offset calibration from NVRAM.</p><p>GetAOffset GetAOffsets status is OK A Offset read was successful.</p><p>SetAOffset Setting OA... Writing A Offset calibration to NVRAM.</p><p>SetAOffset SetAOffsets status is OK A Offset write was successful.</p><p>AutoOffset ON AutoCalibration is OK Automatic offset calculate was successful.</p><p>GetPC Getting PC... Reading P Plane calibration from NVRAM.</p><p>GetPC GetPColl status is OK P Plane read was successful.</p><p>SetPC Setting PC... Writing P Plane calibration to NVRAM.</p><p>SetPC SetPColl status is OK P Plane write was successful.</p><p>GetZC Getting ZC... Reading Z calibration from NVRAM.</p><p>GetZC GetZColl status is OK Z read was successful.</p><p>SetZC Setting ZC... Writing Z calibration to NVRAM.</p><p>SetZC SetZColl status is OK Z write was successful.</p><p>GetTempParam Getting PID... Reading PID from NVRAM.</p><p>GetTempParam Getting TempOffset... Reading Temp offsets from NVRAM.</p><p>GetTempParam GetTempParamStatus is OK Temp parameters read was successful.</p><p>SetTempParam Setting PID... Writing PID to NVRAM.</p><p>SetTempParam Setting sensors... Writing sensor offsets to NVRAM.</p><p>SetTempParam SetTempParamStatus is OK Temp parameters write successful.</p><p>UHR ON Moving UHRplane in... Moving UH Plane in.</p><p>UHR OFF Moving UHRplane out... Moving UH Plane out.</p><p>Move (A) Moving Aplane to position... Moving A Plane to position.</p><p>Move (P) Moving Pplane to position... Moving P Plane to position.</p><p>Philips Medical Systems Confidential and Proprietary Information 35</p><p>DMC Host UtilityBrilliance™CT 6-slice, 10-slice, 16-slice and</p>