C2-030 840 01 08 02 PDF

Siemens, 2009
- For internal use only - All documents may only

be used by authorized personnel for rendering
services on Siemens Healthcare Products. Any
document in electronic form may be printed
once. Copy and distribution of electronic docu-
ments and hardcopies is prohibited. Offenders
will be liable for damages. All other rights are re-
served.
Print No.:
SiemensGrimm
SOMATOM Definition Flash
System
Troubleshooting Guide
CT
2009
C2-030.840.01.08.02
Replaces: C2-030.840.01.07.02
English
Doc. Gen. Date: 08.11
n.a. H CX CS SD CR-CT
Instructions for Troubleshooting
Siemens, 2009
10430603
2 Copyright / Version / Disclaimer
SOMATOM Definition Flash C2-030.840.01.08.02 Siemens, 2009
08.11 H CX CS SD CR-CT
Page 2 of 212
For internal use only
1Copyright / Version / Disclaimer
Copyright
Siemens, 2009 refers to the copyright of a Siemens entity such as Siemens Aktienge-
sellschaft - Germany, Siemens Shenzhen Magnetic Resonance Ltd. - China, Siemens
Shanghai Medical Equipment Ltd. - China, Siemens Medical Solutions USA Inc. - USA
and/or Siemens Healthcare Diagnostics Inc. - USA.
Document Version
Siemens reserves the right to change its products and services at any time.
In addition, manuals are subject to change without notice. The hardcopy documents corre-
spond to the version at the time of system delivery and/or printout. Versions to hardcopy
documentation are not automatically distributed. Please contact your local Siemens office
to order current version or refer to our website http://www.healthcare.siemens.com.
Disclaimer
Siemens provides this documentation as is without the assumption of any liability under
any theory of law.
The service of equipment described herein is to be performed by qualified personnel who
are employed by Siemens or one of its affiliates or who are otherwise authorized by Sie-
mens or one of its affiliates to provide such services.
Assemblers and other persons who are not employed by or otherwise directly affiliated with
or authorized by Siemens or one of its affiliates are not entitled to use this documentation
without prior written authority.
Siemens, 2009 C2-030.840.01.08.02 SOMATOM Definition Flash
Table of Contents 3
Page 3 of 212

0Table of Contents
1 _______ General ________________________________________________________ 8
Safety information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Safety warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Information for switching off the gantry power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Service push-button S1 in PDC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Safety bolts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Data ring protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Open/close the upper front ring segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Opening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Closing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Edge protective strips. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Error message telegram structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2 _______ XRS __________________________________________________________ 21
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Definitions and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Problem isolation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Generator oscillator procedure (GenOSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
XDC/Tube . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
XDC/Tube Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
XDC/Tube test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
High voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
HV troubleshoot test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
TSG high voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
HV plugs with arcing tracks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
HV plug installation at HV sockets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
High voltage tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Filament (FIL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
TSG filament . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Filament . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Anode rotation (RAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
TSG Anode Rotation (RAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Single pulse test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Single pulse test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Single pulse test diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
MVT cable check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Performing the MVT cable check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Arcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Check/adjust the tube oil pressure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
XRS hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4 Table of Contents
Page 4 of 212
Switching on status indicator of XGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Measuring points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Measuring points D700, D701, D702, D703 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
LEDs on D700, D701, D702, D703 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3 _______ DMS__________________________________________________________ 64
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Safety. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Definitions and abbreviations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
TSG Image Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
TSG strong rings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
TSG sporadic strong rings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
TSG weak rings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
TSG sporadic weak rings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
TSG rings in outer slices only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
TSG Streak artifacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
TSG Dual Source problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
TSG Spatial Resolution (bad MTF results) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
TSG other artifacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Tests for Image Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
TSG DMS Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
TSG DMS Power path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
TSG UHR mechanics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Tests & Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
DAS Type not o.k. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Firmware update failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Dynamic collimation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Signals from half detector missing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Storage of Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Environmental Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Hints for defective channel detection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Distinguishing between the module and other components . . . . . . . . . . . . . . . . . . 102
How to interpret the physicists line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
4 _______ Datalink______________________________________________________ 103
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Safety. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Definitions and abbreviations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Troubleshooting Data transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
TSG Datalink. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
TSG permanent errors on DAS Controller(s) > IRS Receiver . . . . . . . . . . . . . . . . . 113
TSG data quality at Tx modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Table of Contents 5
Page 5 of 212
TSG data quality at RX modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
TSG sporadic errors in link DCON > IRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Step 1 (checking) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Step 2 (debugging) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Step 3 (localizing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Tests for data transmission. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Cleaning a fiber optic cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Data link test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
How check the transmitting antenna. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Measuring the fiber optic signal along the link . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Check the electrical RF signals at the Rx modules. . . . . . . . . . . . . . . . . . . . . . . . . 127
Check the quality of data signal (jitter) at the REC input . . . . . . . . . . . . . . . . . . . . 128
5 _______ Fastlink ______________________________________________________ 129
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Definitions and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
TSG Fastlink. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
TSG rotating fastlink connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
TSG stationary fastlink connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
TSG for connection UMAS > UMAR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
TSG for connection UMAR > UMAS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
TSG data quality at Tx modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
TSG data quality at Rx modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Tests for data transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
6 _______ CAN Bus _____________________________________________________ 149
CAN Bus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Data transfer UMAS to UMAR via CAN slip ring. . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Data transfer UMAS to UMAR via Fast Link (function pack 1: CAN over IP) . . . . . 150
TSG CAN bus (rotating part). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
TSG CAN bus to XGS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
7 _______ CANopen Bus_________________________________________________ 157
CANopen Bus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
TSG CAN open bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
CAN open external bus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
8 _______ Stop report loop_______________________________________________ 161
Stop report loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
TSG stop report loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
9 _______ Network______________________________________________________ 167
Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Ethernet switches (located in PDC_A) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
6 Table of Contents
Page 6 of 212
Troubleshooting network components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
10 ______ Rotating controller _____________________________________________ 172
Rotating controller tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
DOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
COC (Tube collimator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
11 ______ Stationary controller ___________________________________________ 174
Stationary controller tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Master stationary (MAS) test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Gantry panel control (GPC) test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Rotation control (ROT) test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Patient Handling System (PHS) test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
CPI (PMM) test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
12 ______ System test___________________________________________________ 179
System test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
DOM functional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
X-ray timeout test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Dyn. Collimation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
13 ______ Cooling System _______________________________________________ 182
Water cooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
TSG Water Cooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
14 ______ PDC_A cabinet ________________________________________________ 192
General overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Power distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Errors and troubleshooting hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Circuit breakers and relays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Residual current monitor F18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Service pushbutton S1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Relays K1, K2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Line voltage circuit breaker test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Service power socket. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
24 Volt power supply for U1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
UPS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
15 ______ Bad motor controller after corrupted FW update____________________ 208
Information for systems with SOMARIS/7, versions below VA40 . . . . . . . . . . . . . . . . . 208
Work steps for systems with SOMARIS/7, versions VA40 and higher . . . . . . . . . . . . . 209
16 ______ Changes to Previous Version ____________________________________ 210
Table of Contents 7
Page 7 of 212
17 ______ Index ________________________________________________________ 211
8 General
Page 8 of 212
1- 1General
Safety information 0
Only qualified and system-trained service staff are allowed to perform CT system installa-
tion, service, maintenance, and quality assurance. Ensure that the most recent version of
the service documentation is on hand.
To avoid any risk of injury to persons and/or damage to the system, read and observe the
General Safety Notes (TD00-000.860.01.xx.xx). Please read and observe the Prod-
uct-specific safety notes (C2-030.860.01.xx.xx) which include very important
safety-related information as well as information about handling of screws and nuts, use of
Loctite, and instructions for torque wrenches. You will find the following information in the
Product-specific safety notes.
Safety information related to the method of risk management
new link
General safety information such as the handling of service documentation, CT system
training request, X-ray protection, electrical protection, service tools... (C2-030.860.01 /
General safety warnings).
General safety information about working in the gantry with the power off/on
(C2-030.860.01 / Powering off the gantry and preparing to work on it).
Use of the patient table as lifting device for gantry part replacement (C2-030.860.01 /
Usage of the Patient Table as a Lifting Device).
Laser products (C2-030.860.01 / Laser products).
Attachment of screws and nuts, use of Loctite, adjustment instructions for the torque
wrench (C2-030.860.01 / Screw connections).
Safety warnings 0
The following safety information is an extract from the information in the Product-specific
safety notes (C2-030.860.01.xx.xx) (C2-030.860.01 / Safety information). It is mandatory
to read and observe the safety information described below.
CAUTION
[ hz_serdoc_F13G02U01M04 ]
Flammable sprays.
Risk of inflammation!
Only use approved and recommended cleaning agents
as described.
CAUTION
Handling parts of the system that may have come into con-
tact with patients may lead to infection caused by
blood-borne pathogens.
Infection caused by blood-borne pathogens!
Take appropriate precautions against exposure to
blood-borne pathogens (e.g. wear gloves).
General 9
Page 9 of 212
WARNING
High voltages and/or mechanical movements (e.g. gantry
rotation) may lead to accidents and injuries when opening
system covers.
Risk of accident or injury!
Only authorized service personnel are allowed to open
system covers.
CAUTION
Non-compliance with X-ray regulations may lead to radiation
exposure to you and/or other persons.
Risk of radiation exposure!
Observe radiation protection regulations when X-rays are
switched on, e.g. :
Never work inside the gantry room.
Do not leave the system unattended.
Make sure there isn't anyone inside the gantry room.
Ensure that personnel cannot enter the gantry room
unnoticed (e.g. lock doors, if necessary).
WARNING
Dangerous voltages are present when the system is switched
on. Dangerous voltages may be present even when the sys-
tem is switched off due to capacity power.
Risk of electric shock!
Observe power-off instructions and discharge wait
times (allow at least five minutes discharge time after
the last scan for all involved HV and UDC/UPS parts).
Secure the system against unintended switch-on (e.g.
block breaker and/or mark breaker against switch-on).
Ensure via measurements that all voltages are
switched off.
Connect the stationary and rotating parts of the gantry
to a protective conductor prior to working in the gantry.
CAUTION
Rotating parts are exposed when gantry covers are opened.
Risk of injury!
Maintain a safe distance and ensure that objects do not
come in contact with rotating parts.
10 General
Page 10 of 212
CAUTION
Unfixed parts/cables during gantry rotation.
Make sure that all parts and cables are mounted prop-
erly before starting rotation.
CAUTION
Temperature of tube and/or tube cooling device parts may be
above 70C (with Straton up to 130C).
Risk of burns!
Avoid contact with oil and exposed parts of X-ray tube
and cooling device.
Wait until tube and cooling device parts are chilled
down.
General 11
Page 11 of 212
Information for switching off the gantry power 1.1
Always read and observe the switching-off/-on instructions described in the Prod-
uct-specific safety notes (C2-030.860.01.xx.xx) (C2-030.860.01 / Product-specific
safety notes).
In the individual Replacement of Parts sections, always refer to the switching-off/-on
worksteps given in the instructions.
To reach system standby status with the panels removed (rear ring removed), install a
CB (cover bridge #8904752) with switched-off system. After SYS/ON, an Init/Resum-
ing of the system is performed and the system will reach standby status.
12 General
Page 12 of 212
Service push-button S1 in PDC 1.2
Fig. 1: Service push-button S1
Pos. 1 Service push-button S1
Pos. 2 Push-button
General 13
Page 13 of 212
Safety bolts 1.3
Front safety bolt > located at the bottom right gantry front
Fig. 2: Front rotation safety bolt - unlock
position

Fig. 3: Front rotation safety bolt - lock
position

Lock gantry rotation
Press bolt slightly to the right (left image, item 1) to release the bolt lock (left image,
item 2).
Press bolt lock towards the gantry (left image, item 2) and move the safety bolt to the
left until the bolt is in lock position.
Make sure that the bolt lock (left image, item 2) moves towards the table
side (forced by the spring of the locking mechanism). This ensures that
the rotation lock position is fixed and secured.
Unlock gantry rotation
Press bolt slightly to the left (right image, item 1) to release the bolt lock (right image,
item 2).
Press bolt lock (right image, item 2) towards the gantry and move the safety bolt to
the right until the bolt is in unlock position.
Make sure that the bolt lock (right image, item 2) moves towards the table
side (forced by the spring of the locking mechanism). This ensures that
the rotation lock position is fixed and secured.
14 General
Page 14 of 212
Rear safety bolt
Fig. 4:
Rear rotation safety bolt (item 1) located between XGR A and HV-tank A at the
rear of the gantry.
Lift bolt and turn it 90 degrees to bring it into the lock or unlock position.
Make sure that the bolt is really at the correct (lock/unlock) posi-
tion. If the bolt accidentally moves into the lock position during
rotation, the gantry may be damaged.
General 15
Page 15 of 212
Data ring protection 1.4
Installing the data ring protection
Fig. 5: Data ring protection
Install the 2 data ring protectors (e.g. item 1) before working at the gantry
front.
- 2 Plexiglas protectors are necessary to cover a larger area on the data ring.
- Attach them to the stationary data ring.
- Do not forget to remove the protectors before starting gantry rotation.
16 General
Page 16 of 212
Open/close the upper front ring segment 1.5
Opening 0
Release locks and attachment nuts
Fig. 6: Front top ring segment
Remove the four M13 nuts (item 2).
Loosen the 2 securing locks (arrows, 1/4 turn) using a 5 mm hexagonal
wrench key.
Pull top of ring segment out of its positioning clamps (item 3) to the outer end
stop.
General 17
Page 17 of 212
Lift the upper front ring segment to service position.
Closing 0
Remove the edge protective strips (Edge protective strips / p. 19).
Close the upper front ring segment, following in reverse order the instructions for open-
ing it.
NOTE Verify that there is enough grease in the slot of the plastic
ring. If not, add grease to the slot.
The grease seals prevent liquid from coming into the gantry.
See the SPC for the relevant material number.

Fig. 7: Upper front segment opened

Fig. 8: Supporting stand gantry lock

Lift the top segment with one hand.
Remove the supporting stand (item 2) from its parking position and extend it until it is
blocked.
Secure the supporting stand to the lock (item 3).
Go to the second support stand (do not walk between table and gantry) and secure
the second supporting stand to the lock as done before.
Install the edge protective strips (two pieces) so that the complete upper front ring
segment edge is fully covered (see (Edge protective strips / p. 19))
18 General
Page 18 of 212
Fig. 9: Park position of supporting stands
Ensure that the supporting stands are securely locked in their parking posi-
tions (arrow) before the gantry cover is closed.
Improperly parked supporting stands will lead to severe damage
of components inside the gantry!
General 19
Page 19 of 212
Edge protective strips 1.6
Install the two edge protective strips.
Fig. 10: Edge protective strip
Install the edge protective strips (two pieces) so that the complete upper front
ring segment edge is fully covered (see image).
Install the edge protective strips as soon the upper front segment is
opened.
The protective strips are delivered with the system.
20 General
Page 20 of 212
Error message telegram structure 1.7
Structure of the error message telegram, see below.
Fig. 11: Error telegram
XRS 21
Page 21 of 212
2- 2XRS
General 0
Safety 0
WARNING
Avoid accident and injury or damage to parts.
Risk of accident and injury!
Read and observe the safety information contained in
the General section of this document and/or the
Product specific safety notes.
Notes 0
This section contains information on isolating XRS problems
Section General > general information.
Section Overview > XRS Information.
Section High voltage > High voltage TSG followed by high voltage test descrip-
tions.
Section Filament > Filament TSG followed by filament test description.
Section Anode rotation > anode rotation TSG followed by RAC test description.
Section MV cable check > Single Pulse test.
Section XRS hints > XRS hints.
Section Measuring point > Table of LEDs and measuring points on XGS/XRS.
Definitions and abbreviations 0
Tab. 1 Definitions and abbreviations
Term Definition / Abbreviation
XDC X-ray deflection control
XGR X-ray generator, rotating
XGS X-ray generator, stationary
XRS X-ray system
XRT X-ray tube
XTA Tube assembly
XTC X-ray tube cooling
MVT Middle voltage transmission
22 XRS
Page 22 of 212
Prerequisites 0
Documents
n.a.
Tools and auxiliary equipment
Standard tool set
HV test plugs
HVT High voltage tank
TSG Troubleshooting Guide
Term Definition / Abbreviation
XRS 23
Page 23 of 212
Overview 2.1
The XRS section contains information on possible XRS tests and the corresponding Trou-
bleshooting Guides. With the SOMATOM Definition Flash, troubleshooting always starts by
calling up the eventlog and searching for the relevant error message. Follow the instruc-
tions given in this error message for troubleshooting. In some cases, the error message
links you to Troubleshooting Guides as described in this document. This link is normally
used if the Troubleshooting Guide is too complex or images are needed for troubleshooting.
Additionally, read the information stored in the tube history (Local Service >Report). This
information can always be useful in case of XRS problems.
Problem isolation 0
Principle problem isolation in case of XRS problems
1. Find the according error message in Eventlog
NOTE The XGR and XGS assemblies are continuously communicat-
ing using the CAN bus after the system is switched on. For
this reason, 2 error messages are usually sent to the log-
book after XRS problems. Always check both (XGS/XGR)
error messages when troubleshooting.

2. Follow the instructions given in the extended error message for troubleshooting
The information provided in the error message guides you in finding the problem.
In some cases, you are linked to the Test and Troubleshooting instructions, #
C2-030.840.01.... In this case, follow the relevant Troubleshooting Guides
described in this document.
Generator oscillator procedure (GenOSC) 0
Generator oscillator adaptation (Gen-Osc) is an automatic program. The function of the
program is to adapt the inverter frequencies. The program performs very short scans with
different inverter frequencies to find the minimum resonance point. This value is stored to
D700 in XGS.
The frequency adaptation procedure must run successfully; otherwise, XRS errors such
as UT too high or UT max errors (e.g XRS_83 error) may abort scanning. The same errors
may appear if parts of the oscillating circuit (e.g MV cable, XGS_PDC_Control, HVT / MVT)
have been replaced without performing GenOSC after the replacement. For this reason,
always use the relevant guided tour after the replacement of parts.
NOTE If GenOsc fails because of arcing, try using dummy plugs (i.e.
test plugs for HVT) and perform GenOsc again with dummy
plugs installed.

24 XRS
Page 24 of 212
XDC/Tube 2.2
XDC/Tube Test 0
INIT Tests:
During INIT, all XRT drivers of the XDC (outputs on X13 and X14) are tested in 2 steps. The
first step is an isolation check for detecting short circuits between the output wires and
ground or power (230 V). This step can detect defective driver gates within the XDC as well.
The second step activates the drivers and can detect short circuits between the output
wires or broken wires. The INIT tests have failed if any warning or error message occurs in
the Eventlog during step 1 or 2, or if the requested currents in step 2 cannot be reached.
XDC/Tube Self-Test within Service SW:
The XDC/tube self-test is basically the same as the INIT test except that the grid function
is tested as well. Depending on the actual system state, the XDC/tube self-test tolerates
some problems. Therefore, if the XDC/tube self-test fails, switch the gantry off and then on
again to initialize an INIT test.
Test results:
When the test fails, it leads to the warning message " CT_DCA/B 31" where the parameters
give information on which part of the test fails. In addition to this information, there can be
additional errors or warnings which indicate the error. Follow the instructions in the warn-
ing/error message for troubleshooting
Usage of the tests:
The XDC/Tube self-test can help detect problems in the output drivers of the XDC, prob-
lems within cabling, or problems within the tube. The test can be helpful, when the XDC
has aborted scans with the error message "CT_DCA/B 51 .." or "CT_DCA/B 50" espe-
cially when parameter 3 is 0 x 00, 0 x 01, 0 x 04, 0 x 05, 0 x 08, 0 x 09, 0 x 12, 0 x 17, 0 x
1D, 0 x 1E or 0 x 1F. Be aware that any of these errors can happen during arcing as well,
without any real HW problem within the XDC or the tube. If the INIT tests fail, you have a
problem in the XDC, cabling, or the tube. If any additional error or warning message occurs
in the Eventlog during INIT, it can be used to help detect where the problem is located. You
can disconnect the cable on the XDC (X13 and X14) and/or the tube (X8 and X4) and then
repeat the INIT test. When the additional errors/warnings disappear, you have discon-
nected the faulty part from the XDC.
Remark: Test can be used when the system is or is not in stand-by status.
XDC/Tube test 0
XDC/Tube test
Performing the filament test
1. Select Local Service > Test Tools > Tube/Generator
2. Select XDC/Tube.
3. Click GO and follow the instructions in the dialog. The test is terminated automatically.
XRS 25
Page 25 of 212
High voltage 2.3
HV troubleshoot test 0
This test tool supports the troubleshooting in case of high voltage issues. The HV trouble-
shoot test analyzes the last 1000 scans and requires at least 200 scans. Thus, for a useful
result it is a prerequisite that the system has been in normal operation for about one week
prior to using this tool. Consequently, the test tool is not suited to verify the success of
recent service work. For example: If Getter was performed before the tool is used, this fal-
sifies the result.
The test evaluates the circumstances which might have caused scan aborts due to arcings
in the tube history. Based on the test results, certain worksteps/checks are listed in a flow-
chart which follows the TSG high voltage part.
NOTE The HV troubleshooting test analyzes only arcings which
caused scan aborts. A continuous decline of the tube power
cannot be identified by this tool.

Please note the following conditions and limitations for successful use of the HV
troubleshooting test:
The HV troubleshooting test can only be used when the scan aborts caused by arcings
have occurred; otherwise misleading results may be produced.
The HV troubleshooting test analyzes the last 1000 scans. e.g. if you have tightened
the oil couplings after a first run of the tool and you run the tool again, the tool will
present the same result as before.
If less than 200 scans have been performed with a tube, the tool does not perform eval-
uation.
For meaningful results, the system must have been in normal operation for about one
week prior to using the tool! Therefore, the tool is not suitable for verifying the success
of recent service work.
TSG high voltage 0
The following high voltage TSG is used in case of high voltage problems. The TSG provides
a guide line to troubleshoot HV problems.
26 XRS
Page 26 of 212
Tab. 2 High voltage TSG
Step Action
1 Check the Eventlog for:
UT max and /or UT too high errors (e.g CT_GSA/GRA_83) or
arcing problems (CT_GSA/GRA_68)
If above-mentioned error appears > continue with item 2
In all other cases > check Eventlog for other error message instructions.
2 Perform the tube history evaluation (Local Service > Test tools >
Tube/Generator > HV troubleshoot A or B). One of the following mes-
sages (1-7) is displayed after tube history evaluation. Follow the instructions
given in the text and see flowchart (Fig. 12 / p. 29) as a guide:
1. Tube history does not contain enough scans for evaluation > no evalu-
ation possible > continue with item 3.
2. Tube history evaluation does not indicate a tube arcing problem lead-
ing to scan aborts > no XRT/XTC Problem > check Eventlog for other error
messages and follow instructions given in the message.
3. Tube history evaluation does not show a considerable number of tube
arcs > no evaluation possible > continue with item 3.
4. Tube history evaluation shows tube arcs caused by low oil-pressure >
Assure properly closed cooling hose couplings at tube and cooling unit. .
If the couplings were properly closed, replace both the tube and tube
cooling unit.
5. Tube history evaluation shows tube arcs caused by low oil-pressure or
even loss of oil
Check the gantry for oil contamination. If found, clean it, replace both the
tube and tube cooling unit and inform HSC CT.
If no oil found, assure properly closed cooling hose couplings at tube
and cooling unit
If the couplings were properly closed, replace both the tube and tube
cooling unit.
6. Tube history evaluation shows mainly one side tube arcs without cool-
ing oil-pressure correlation
Check HV plugs for burn marks (examples see (HV plugs with arcing
tracks / p. 30)
If burn marks are visible, clean the HV plugs and receptacles (inside)
with alcohol. If the problem persists, replace the tube or HV cable con-
nection to HV tank.
If no burn marks are visible, perform HVC plug tests as shown in the
flowchart (Fig. 12 / p. 29) .
7. Tube history evaluation shows tube arcs without cooling oil-pressure
correlation
Getter tube > If problem persists, replace the tube.
XRS 27
Page 27 of 212
3 Perform GenOSC (Local Service > Tune-up > Expert Mode > GenOSC).
a) if GenOSC is aborted due to a problem > continue with item 4
b) if the HV problem is not solved after GenOSC > continue with item 5.
c) if the HV problem is solved > GenOSC tables are stored in D700 XGS.
No further action is necessary.
4 Perform GenOSC with installed test plugs. See test plug installation (HVC
with plug test / p. 33).
a) if the GenOSC is still aborted > check the Eventlog for CT_GSA/GRA
messages and follow the instructions given in the error message.
b) if the GenOSC is ok > try GenOSC again with installed X-ray tube > if
the problem recurs exchange XRT (X-ray tube).
5 Perform Gettering (Local Service > Tune-up > Expert Mode > Getter).
a) if the HV problem is not solved after gettering the tube > continue with
item 6.
b) if the HV problem is solved > no further action.
6 1. Switch system to the COMP/ON status at the control box.
2. Press service switch S1 in the PDC to switch off the gantry power.
3. Switch off rotation enable switch S301.
4. Remove HV plugs from the HV tank and the HV sockets.
5. Check HV plugs for signs of arcing (black dots or stripes (HV plugs with arc-
ing tracks / p. 30)).
a) If there are any signs of arcing > continue with item 7
b) If there are no signs of arcing > continue with item 8.
7 If there are any signs of arcing on the HV plugs, HV receptacles or the insu-
lators > clean the parts with alcohol.
a) If any signs of arcing (cracks) remain > change the relevant parts.
b) If there are no signs of arcing remaining on the parts > reinstall HV plugs
using new silicon disks or insulators. Try scanning again > if the HV
problems recur continue with item 8.
8 Perform the HVC tube test (Local Service > Test Tools > Tube/Generator
> HVC tube). Follow the dialog of the HVC tube test (tube test with high volt-
age but without load).
a) If there are CT_GSA/GRA error messages found in the Eventlog > con-
tinue with item 9.
b) If there are no CT_GSA/GRA error messages found in the Eventlog >
continue with item 11.
Step Action
28 XRS
Page 28 of 212
9 Perform the HV plug test with installed dummy plugs ( #10 093 700) at the
HV sockets . Follow the dialog of the HVC plug test (Local Service > Test
Tools > Tube/Generator > HVC with plugs).
Install the HV test plugs into the HV sockets using new insulators and
tighten the HV plugs with a torque of 25 Nm.
a) If the test is aborted after 80 s by the UMAR (scan time exceeded), there
is no HV problem on generator side > change tube.
b) If there are still CT_GSA/GRA error messages found in the logbook >
continue with item 10.
10 Perform HVC plug test scans with installed dummy plugs (#1621791) at HV
tank (Local Service > Test Tools > Tube/Generator > HVC with plugs).
Follow the dialog of the HVC plug test.
a) If there are no CT_GSA/GRA error messages found in the logbook
(UMAR errors are acceptable) > change both HV cables including the
HV sockets.
b) If there are CT_GSA/GRA error messages found in the logbook >
change HVT.
11 The HV problem is related to tube load.
Possible reasons: Inverter problem, ground problem, HVT.
a) Check Eventlog for XRS errors related to inverters > if there are any, fol-
low the instructions given in the error message.
b) Check ground connections (bad contact....) of the XGS parts.
c) Perform the single pulse test.
Step Action
XRS 29
Page 29 of 212
Fig. 12: HV TSG
30 XRS
Page 30 of 212
HV plugs with arcing tracks 0
HV plugs and insulators with arcing tracks
Fig. 13: HV plug with signs of arcing
Fig. 14: HV plug with signs of arcing
Fig. 15: HV insulator with signs of arcing
XRS 31
Page 31 of 212
HV plug installation at HV sockets 0
1. Prepare the high voltage connectors and test plugs.
Fig. 16: Silicon oil on HV plugs


Check to ensure that the connector is clean and inspect it for damage.
Apply oil (supplied with the part) to the entire plug surface (left figure, item 1).
Use about half of the oil from the tube for both plugs.
Put oil into the new silicon insulator (item 2).
Install the silicon insulator part over the plugs (left figure, item 1)
Ensure there is no air left in the silicon insulator.
32 XRS
Page 32 of 212
2. Prepare the high voltage connectors.
3. Tighten the HV plugs.
High voltage tests 0
Description of available HV tests.

Fig. 19: HV sockets

Check that there is no air left in the silicon insulator.
Insert the O-ring onto the HV plug (item 1).
Put oil onto the silicon insulator (item 2).
Insert the HV plugs into the receptacles.
Verify the position of the plugs (+ or -).
Install the O-ring into the HV socket as shown (right figure, arrow).
Hand-tighten the fastening rings.
Fig. 20: Tightening the HV plugs
Tighten the HV plugs using the special tightening tool (delivered with the
system) with a torque of 25 Nm.
XRS 33
Page 33 of 212
HVC tube test
For high tension arcing or HV breakdown, the test utility HVC tube test is available in the
Tube/Generator test tools platform. The HVC tube test lets you apply high tension to the
HV circuit without tube current. No test plugs are used in this test. No radiation is released
during the test procedures. This test is performed before an HVC plug test is started
because if this test does not indicate an error, the HVC plug test does not indicate an error
either.
Prerequisites
Test needs system in the stand-by status.
Performing the HVC tube test
2. Select HVC tube.
3. Select voltage and repetitions. Follow the instructions in the dialog.
4. Click the hardware Start button at the control box.
The test runs for 80 s. The test is terminated automatically.
If the test fails, perform the HVC plug test described next to select which XRS part
is defective.
HVC with plug test
For high tension arcing or HV breakdown, the primary test utility HVC plug test is available
in the Tube/Generator test tools platform. The HVC plug test lets you apply high tension
to the HV circuit without tube current and without a connected X-ray tube. This allows the
HV circuit to be systematically reduced using test plugs to isolate a high tension error to
either the Straton MX P tube, HV cable, or HV tank. No radiation is released during this test
procedure.
Prerequisites
HV tank dummy plugs (normal type) > material number 16 21 791
HV sockets dummy plugs (mini type) > material number 10 093 700
NOTE The HVC plug test is only allowed with test plugs installed.
Tests with the installed tube can result in misdiagnosis of
errors. For a connected tube, use the HCV tube test.

Performing the HVC plug test
1. Follow the work steps followed to install the relevant test plugs in the HVT.
a) Switch system to the COMP/ON status at the control box.
34 XRS
Page 34 of 212
b) Press service hardware switch S1 in PDC.
c) Remove the lower and open the upper front ring segment. Refer to (Open/close the
upper front ring segment / p. 16)
d) Remove the plastic ring and the funnel.
e) Move the HV tank or the HV sockets to the 6 oclock position by hand.
f) Disable gantry rotation with switch S301.
g) Remove the HV plugs from the HV tank or the HV sockets and install the correct test
plugs.
HVT receptacles: When installing the test or HV plugs, new silicon disks
must be used.
h) Switch system on (S301 remains switched off).
S301 has to be switched off because during Init the Rot FW searches for an
index pulse. This behavior may result in a 360 degree rotation of the gan-
try. In this case the removed HV cables may damage parts in the gantry.
2. Select Local Service > Test Tools > Tube/Generator.
3. Select HVC with plugs.
4. Click Go on the virtual user panel. Follow the instructions in the dialog. Important work
steps are listed below:
5. Click the hardware Start button at the control box.
The test runs for 80 s. The test is terminated automatically.
> If the test fails, follow the HV Troubleshooting Guides.
NOTE New silicon disks in the HVT must be used for the HV cable
and test plugs before the plugs are installed into the compo-
nents ( HVT).

6. Reinstall all parts removed/opened previously according the original configuration.
Install the HV plugs at the HV sockets using new insulators. Tighten the HV plugs
with a torque of 25 Nm.
Install the HV plugs at the HV tank using 2 new silicon disks. Hand tighten the HV
plugs at the HV tank.
XRS 35
Page 35 of 212
Filament (FIL) 2.4
TSG filament 0
The filament function is tested during INIT (e.g COMP/ON > SYS/ON). After switching the
gantry off/on, a self test of the D770 (FIL power) in XGR is performed as step 1. In step 2,
a filament current is sent to the filament heating in XRT (X-ray tube), passing the filament
transformer at XRT. If the self test fails, the error message CT_GSA/GRA_111 (XGR FIL
Self test Error) is sent to the Eventlog.
Additionally a test utility FIL is available in the Tube/Generator test tools platform. During
the INIT filament test, the involved D 700/D 770 board components in the XGR and the
filament current to the XRT are tested (only in/out test). With the FIL test, the involved
filament components and the filament regulation function are tested. So the FIL test is a
more detailed test possibility.
Tab. 3 Filament test
Filament 0
Filament test
This test checks the principal filament function and the regulation of the filament circuit
including the power board (FIL-Power) in the XGR box, the cable connection to the XRT,
the filament transformer at XRT, and the filament heating in the tube itself. No radiation is
generated during this test procedure.
Performing the filament test
1. Select Local Service > Test Tools > Tube/Generator.
2. Select FIL
Step Action
1 Switch gantry off/on using the control box (COMP/ON > SYS/ON) to perform
an XGR INIT.
2 Check in the eventlog for the error message CT_GRA_20 or CT_GRB_20
(XGR FIL self test Error).
> if the error message was sent to the logbook during INIT > follow the Trou-
bleshooting Guides given in the error message.
> if the error message was not sent to the logbook during INIT > continue
with item 3.
3 Perform the FIL test function.
> if the FIL test fails > change 1. XRT and 2. XGR assembly
36 XRS
Page 36 of 212
Anode rotation (RAC) 2.5
TSG Anode Rotation (RAC) 0
Use this test function to verify the RAC function. There are different anode speed (Hz)
selections possible. In the Troubleshooting Guide below, 160 Hz is selected, because this
value is very stressful for the RAC function (Note: Do not use this selection in quick suc-
cession to avoid overload).
Use the RAC extended test function to check the rotating anode revolution with respect to
the time (acceleration). The following statements are possible:
No revolution > e.g rotating anode bearing defective, bad cable/plug connection,
XGR...
Revolution in the medium revolution range is too low > e.g rotating anode motor defec-
tive, XGR....
Upper revolution range not reachable > e.g rotating anode bearing defective, XGR...
Note: The system should be in stand-by status for this test.
NOTE Anode rotation on a Staton MXP tube may not be started
without a functioning and connected cooling circuit (e.g. for
troubleshooting).

Tab. 4 Anode rotation (RAC) test
Step Action
1 Perform AnodeRot Frequency Local Service > Test Tools > Tube/Genera-
tor > RAC and select 160 Hz
> if the RAC test fails > continue with item 2.
> if the RAC test is ok > no further action.
2 Perform AnodeRot Frequency Local Service > Test Tools > Tube/Genera-
tor and select the following RAC extended tests:
1. RAC anode movement test
2. RAC acceleration test
3. RAC maximum speed test
If test 1 fails > continue with item 3
XRS 37
Page 37 of 212
3 Possible cause of error: no revolution
1. Check cable connection W604/W654 between XGR (X6) > XTA (X2) for bro-
ken wire or bad contact.
2. Rotating anode motor defective > change XRT
3. XGR assembly defective > change XGR assembly.
4 Possible cause of error: revolution in the medium revolution range is too low
1. Rotating anode bearing defective > change XRT
2. XGR assembly defective > change XGR assembly.
5 Possible cause of error: upper revolution range not reachable
1. Rotating anode bearing defective > change XRT
Step Action
38 XRS
Page 38 of 212
Single pulse test 2.6
Single pulse test 0
The single pulse test allows you to identify problems from the inverter assemblies up to the
HV_Tank by triggering the inverters for a single pulse. Use the single pulse test after per-
forming the TSG High voltage as a last step or if there is IMAX / UB MAX parameter infor-
mation identified in an error message. Please use a memory oscilloscope to measure the
output of the single pulse test.
Tab. 5 Single pulse test
Prerequisites
Memory oscilloscope
Step Action
1 Perform the single pulse test with normally connected tube.
In addition to the given test result, check the UT_act value in the relevant
test message in the Eventlog.
If UT_act parameter is E: 0 x 50, 0 x 02, 0 x 57, 0 x 1B, 0 x.. 0 x.. 0 x 00,
> test was successful. No problem on inverter part.
f UT_act parameter is E: 0 x 50, 0 x 00, 0 x 4D, 0 x 09, 0 x.. 0 x.. 0 x 00,
> test was not successful. Continue with item 2.
2 Perform the single pulse test with installed test plugs (#1621791) . Follow the
dialog of the HVC plug test to install the test plugs
In addition to the given test result, check the UT_act value in the relevant
test message in the Eventlog.
If UT_act parameter is E: 0 x 50, 0 x 02, 0 x 57, 0 x 1B, 0 x.. 0 x.. 0 x 00,
> test was successful > X-ray tube problem > exchange X-ray tube.
f UT_act parameter is E: 0 x 50, 0 x 00, 0 x 4D, 0 x 09, 0 x.. 0 x.. 0 x 00,
> test was not successful. Continue with item 3.
3 Compare the output diagram of the scope, the enclosed example diagrams and
tolerance values shown below.
The time for a single pulse has to be 9 microseconds +/- 20%.
The current must have a peak value of +170A +/- 20% or -170A +/- 20% (alter-
nating).
The tube voltage (UT_act) must have a peak value above 10kV.
If the current is too high and/or the tube voltage is too low, check the
MVT and HVT cabling (short circuit)
If cabling is o.k. > replace parts in the following order:
1. MVT
2. HVT
3. Relevant inverter
XRS 39
Page 39 of 212
Performing the single pulse test
1. Move the XGS_Control assembly out of the PDC to get better access.
NOTE The power at the XGS control is 24 V and 5 V. Do not touch
any parts on the XGS control. Connect the probes only as
described below.
Use a 3 channel scope to perform the measurements below.
If only a 2 channel scope is available, measure UT_act first
and then I_load to get the necessary information.

2. Connect scope:
- Channel 1
- XGS D701 > X211 UT_act (1 V = 20KV) -> see (1/Fig. 30 / p. 54)
- ANA_GND > XGS D700 > X87 ->see (6/Fig. 29 / p. 51)
- Adjust scope to 1V/div
- Channel 2
- XGS D701 > X5 I_load (1 V = 50A) -> (1/Fig. 30 / p. 54)
- ANA_GND > XGS D700 > X87 -> see (6/Fig. 29 / p. 51)
- Adjust scope to 1V/div
- Channel 4
- XGS D700 > X104 N_Start_inv -> see (12/Fig. 29 / p. 51)
- GND > XGS D700 > X112 -> see (12/Fig. 29 / p. 51)
- Adjust scope to 5 V/div
3. Adjust scope
- Time base 20 microseconds
- Trigger channel 4 (neg. slope, single)
5. Select Unset all in the generator application.
6. Select Single Pulse
7. Select path and click GO
The test is terminated automatically.
The time for a single pulse has to be 9 microseconds +/- 20%.
The current must have a peak value of +170A +/- 20% or -170A +/- 20% (alternat-
ing).
The tube voltage (UT_act) must have a peak value above 10kV.
40 XRS
Page 40 of 212
Single pulse test diagrams 0
The first 2 images are good examples; the last 2 images are error examples.
Fig. 21: Single pulse test diagram
XRS 41
Page 41 of 212
Fig. 22: Single Pulse test diagram
Error examples
Short-circuit at the oscillating current cable (MV cable) in the HV tank
42 XRS
Page 42 of 212
Short-circuit at inverter output
XRS 43
Page 43 of 212
MVT cable check 2.7
The MV cable check is used to test the correct connection of the MV cables. The MV cables
are routed from PDC_A/B > slip ring > HVT_A/B. A wrong connection of MV cable_A and
MV cable_B destroys some XRS parts. Especially after system installation, moving the sys-
tem or changing slip ring parts, use this test to check that the connection of the MV cables
is correct. If the test is passed the MV cable connection is correct. If the test is failed, it is
mandatory to find the reason for the error.
Tab. 6 MV cable check
Performing the MVT cable check 0
2. Select MVT cable check
3. Click GO and follow the instructions in the dialog. The test is terminated automatically. If
the test fails > check the complete connection (PDC_A/B > slip ring > HVT_A/B) to find
the problem.
Step Action
1 Perform MV cable check A and B path.
1. if the test passes ok > MV cable connections path A and path B are correct.
2. if the test fails > check the complete connection from PDC_A/B over the slip
ring to HVT_A/B. Use the actual function description as connection refer-
ence.
44 XRS
Page 44 of 212
Arcing 2.8
The Arcing test is used from the lab to simulate arcings to verify that the FW/SW reaction
due to arcings is correct. This test is not service-relevant.
XRS 45
Page 45 of 212
Check/adjust the tube oil pressure 2.9
The expansion vessel for the following measurement can be ordered from service stock.
The part number for the vessel is: 10610161.
Allow the system to cool down for at least 10 minutes after the last scan. During the
cooling time, the system must be switched on.
Be aware that some system components may be very hot: the Straton tube, XTC,
etc. may reach temperatures up to 130 degrees Celsius.
Wait until the tube and the cooling system have cooled down, then switch the system to
COMP/ON status at the control box.
Switch off the gantry power using the S1 service button in PDC A.
Remove the gantry lower front ring segment.
Turn the gantry by hand until the Straton MX P tube (A or B) is in the 6 oclock position.
Secure against unintended rotation by using the front safety bolt.
Prepare the expansion vessel.
Open the quick coupling and disconnect the lower oil hose at the tube. Connect the oil
hose from the expansion vessel to the empty quick coupling of the tube.
NOTE The pressure indicator at the expansion vessel shows the
actual pressure in the oil circuit after the oil hose from the
expansion vessel has been connected.

Fig. 25: Adjusting unit for expansion membrane
Install the adjustment handle (item 1) on the expansion vessel.
- Press the button (item 2) to lock the thread rod on the membrane.
- Hand-tighten the two screws of the adjustment thread rod (item 3).
46 XRS
Page 46 of 212
Check/adjust the oil pressure.
Fig. 26: Adjusting the tube pressure
Using the expansion handle (item 1), check the pressure at the pressure indi-
cator (item 2) attached to the expansion vessel.
The correct pressure is 1.25 bar (+/- 0.05 bar) + the altitude correction factor
taken from the following table.
The goal of the pressure adjustment is to have the correct oil pres-
sure for all operating conditions. If the pressure is too low, arcs
may occur during scans using the fastest anode rotation (e.g 160
Hz).
If the system is located at a higher altitude than sea level > add the following
correction factor to the sea level pressure (see following table).
For example, if the altitude is 1000 m -> the correction value is 0.12 bar.
Altitude [m] Difference [bar]
0 0.00
500 0.06
1000 0.12
1500 0.17
2000 0.22
2500 0.27
3000 0.31
3500 0.35
4000 0.39
4500 0.43
5000 0.47
XRS 47
Page 47 of 212
Unlock the safety bolt for gantry rotation.
Rotate the gantry by hand and check for unusual noise.
Close all covers opened before.
Switch on circuit breakers F2, F3, F5, F6, F7, and F11 in the PDC A and F2 in the PDC
B.
First switch the F2, F3, F5, F6 circuit breakers to the 0 position and then to the
1 position.
Switch the system to the SYSTEM/ON status at the control box.
If the pressure is not correct, adjust the membrane position using the adjust-
ment handle (item 1).
After the pressure adjustment is finished, remove the expansion vessel
(remove the oil quick-snap connection to the XRT).
Attach the second oil hose from the XTC again to the tube.
48 XRS
Page 48 of 212
XRS hints 2.10
The following information is a summary of troubleshooting hints obtained through experi-
ence.
Tab. 7 XRS hints
Step Action
1 XGS_PDC control assembly controls the complete switching-on process of
most system parts. If this part becomes defective, the system components
do not switch on. For troubleshooting and to ensure that the system compo-
nents are switched on again (in case the control assembly is defective) per-
form the follow work steps:
1. Check if all necessary voltages are available on XGS A/B > all green power
supply LEDs on D790 must lit.
If not > check/change XGS power supply.
2. Exchange the XGS_PDC control in the PDC in accordance with the
Replacement of parts PDC instructions. After replacement, use the guided
tour to perform necessary Tune-up steps.
3. After replacement of the XGS_control, make sure that the dongle plug
(including the 120-ohm CAN bus resistor) is installed at plug X3.
2 The inverter 1 and inverter 3 cable connections can be exchanged for trouble-
shooting (both inverters are identical).
1. Remove inverter plug X23 (inverter 1) and X43 (inverter 3) from the
XGS_PDC_Control backplane.
2. Install inverter plug X23 (inverter 1) in the X43 backplane plug and X43
(inverter 3) in X23 backplane plug on the XGS_PDC_Control backplane.
If the error moves with the inverter > inverter is defective.
If the error does not move with the inverter > inverter and inverter
cable ok, check for other problems such as the cable connection,
ground connection, or check for other error messages returned
along with the inverter error message. Follow the instructions
given in this message.
XRS 49
Page 49 of 212
Switching on status indicator of XGS 2.11
The seven-segment display on XGS board D700 (see image below) indicates the XGS sta-
tus from system switch-on up to scan execute. This information can be used for trouble-
shooting.
Fig. 27: D700 measuring points and LED status
50 XRS
Page 50 of 212
Fig. 28: XRS Status
XRS 51
Page 51 of 212
Measuring points 2.12
Measuring points D700, D701, D702, D703 0
D700 measuring points
Fig. 29: D700 main board
Tab. 8 Oscillating current and dose act. measuring points
Tab. 9 Supply voltage measuring points
item signal name short name valid
at
Description measur-
ing point
2 I_load_INV3 I_L_Inv3 XGS Oscillating current inverter 3 /
1 V = 50 A.
X77
2 Dose_act Dose_act XGR Actual dose value from fastlink
1 V = 13.107 value
* other similar values with
D703 Fastlink control register
selectable.
X76
at
Description measur-
ing point
3 P15V P15V XGS + 15-V Voltage supply X69
3 N15V N15V XGS -15-V Voltage supply X71
3 UDC UDC Sporadic error voltage X73
52 XRS
Page 52 of 212
Tab. 10 Ground measuring points
Tab. 11 HW interrupt for ignition pulses main inverter
NOTE The following measuring points are not implemented any
more in newer systems. Nevertheless, the signals can still be
measured on XGS D701 or D703 (see following pages).

Tab. 12 Tube voltage measuring points
3 VCC VCC XGS + 5-V Voltage supply X75
3 ANA_GND ANA_GND XGS analog ground X78
3 GND GND XGS ground X80
at
Description measur-
ing point
4 VCC VCC XGS + 5-V voltage power supply X75
4 ANA_GND ANA_GND XGS analog ground X78
at
Description measur-
ing point
5 S1 S1 XGS Ignition switch: HW interrupt of
the ignition pulses from the
main inverter. Normal position
is off - V162 must be off. No
function in XGR. Normal posi-
tion is off.
n.a.
at
Description measur-
ing point
6 P_UT act P_UT act XGR Positive tube voltage 1 V = 10
kV.
X81
6 N_UT act N_UT act XGR Negative tube voltage 1 V = 10
kV.
X83
6 UT_act UT_act XGR Tube voltage 1 V = 20 kV. X85
6 ANA_GND ANA_GND XGR analog ground X87
at
Description measur-
ing point
XRS 53
Page 53 of 212
Tab. 13 IT act. measuring points
Tab. 14 Service switch
Tab. 15 IT act. measuring points
Tab. 16 FPGA voltage measuring points
Tab. 17 FPGA voltage measuring points
at
Description measur-
ing point
7 MA_meas_1 1 XGR IT_act measurement point 1
for ampere meter.
X61
7 MA_meas_2 IT_nom XGR IT_act measurement point 2
for ampere meter.
X59
Item Signal
name
short name valid
at
Description Measur-
ing point
8 S5 S5 XGR Switch must be on for IT_act
measurements using an
ampere meter at measuring
points X46, X48, X50, X59,
X61. LED V202 is on the when
the switch is activated. Normal
position is off.
n.a.
at
Description measur-
ing point
9 IT_act IT_act XGR actual tube current X48
9 IT_nom IT_nom XGR Nominal tube current X50
9 ANA_GND ANA_GND XGR analog ground X46
at
Description measur-
ing point
10 VCC3.3 VCC3.3 XGS + 3.3-V I/O voltage FPGA X20
10 VCCINT VCCINT XGS + 1.5-V core voltage X44
at
Description measur-
ing point
11 S2 S2 XGS
XGR
Service switch: Switch has no
function at this time. Neverthe-
less, the switch must be in the
off position. LED V6 must be
off.
n.a.
54 XRS
Page 54 of 212
Tab. 18 FPGA digital out
Tab. 19 FPGA digital out
D701 HVC board measuring points
Fig. 30: D701 measuring points
Item signal name short name valid
at
Description measur-
ing point
12 N_Start_FIL
_INV
FIL XGR Start FIL inverter (low active).
Can only be used in XGR.
X100
12 N_Start_RA
C_INV
RAC XGR Start RAC inverter (low active).
Can only be used in XGR.
X102
12 N_Start_HV
_INV
INV XGS Start HV inverter (low active). X104
12 XC XC XGS XC signal (X-ray request) X106
12 XRAY_on X-ray XGS X-ray on signal (> 20 kV) X108
12 INV_Fault Inv_err XGS Summary error HV inverter
Can only be used in XGS.
X110
12 GND GND XGS
XGR
Ground X112
Item signal name short name Description measur-
ing point
13 S3/S4 n.a. DIP switches for debug and configura-
tion of the FPGA - not for service use.
n.a.
XRS 55
Page 55 of 212
Tab. 20 D701 HVC board measuring points
D702 FIL/RAC board
Tab. 21 D702 FIL measuring points
at
Description measur-
ing point
1 UT_act UT_act XGS Actual tube voltage (from rotat-
ing part over fastlink) 1 V = 20
kV
X211
1 U_control U_con XGS Set value for kV regulator X216
1 I_load_act I_L_A XGS Actual oscillating current. 1 V =
50 A
X215
1 USTU USTU XGS Set value for kV regulator.
(Voltage control cycle). -5 V ...
0 V
X208
1 I_load_nom I_L_N XGS Nominal oscillating current. 1
V = 50 A
X207
1 UDC_act UZ_act XGS Actual intermediate circuit volt-
age
X210
1 ANA_GND A_GND XGS analog ground X209
1 I_load I_load XGS Oscillating current. 1 V = 50 A X5
1 UT_nom UT_nom XGS Nominal tube voltage X204
1 USTI USTI XGS Set value for kV regulator (cur-
rent regulator circuit) 0 - 5 V
X203
1 Upre_con Upre XGS Set value for kV regulator (pre-
liminary control) 0 - 5 V
X201
at
Description mea-
suring
point
D702 IT_act IT_act XGR actual tube current
max. 80 mA > 1 V = 100 mA
<80 mA > 1 V = 80 mA
X18
D702 IF_act_1 IF_act_1 XGR actual filament heating 1
1 V = 0.273 A
X19
1 V = 0.273 A
X20
56 XRS
Page 56 of 212
Tab. 22 D702 RAC measuring points
D732 HV acquisition
HVT (high voltage tank) measuring points
Tab. 23 D732 HVT measuring points
1 V = 0.273 A
X21
D702 ANA_GND A_GND XGR analog ground X17
board signal name short name valid
at
Description mea-
sur-
ing
point
D702 Test_DAC_1 DAC_1 XGS FPGA controlled debug DAC X10
D702 Test_DAC_2 DAC_2 XGS FPGA controlled debug DAC X11
D702 Res_sin sin XGS Resolver Sine Signal X12
D702 Res_cos cos XGS Resolver Cosine Signal X13
D702 RAC_P3 P3 XGS RAC Current Phase 3 (1 V =
40 A, Offset 2.5 V)
X14
40 A, Offset 2.5 V)
X15
40 A, Offset 2.5 V)
X16
D702 ANA_GND ANA_GND XGS analog ground X17
at
Description mea-
suring
point
D732 ANA_GND ANA_GND XGR analog ground X12
D732 P_UT_act P_UT_act XGR Tube voltage (pos.) (1 V = 10
kV)
X13
D732 N_UT_act N_UT_act XGR Tube voltage (neg.) (1 V = 10
kV)
X14
at
Description mea-
suring
point
XRS 57
Page 57 of 212
LEDs on D700, D701, D702, D703 0
D700 LED status
Fig. 31: D700 measuring points and LED status
Tab. 24 D700 main board
board signal name valid at Description LEDs
D700 S_FIL_INV XGR Start FIL Inverter. Only used in XGR. V7
D700 S_RAC_INV XGR Start RAC Inverter. Only used in XGR. V8
D700 S_HV_INV XGR/XGS Start HV Inverter (at XGR signal
delayed due to transport (fastlink) delay.
V9
D700 Cycle LED XGR/XGS FPGA Life Cycle LED V10
D700 XC XGR/XGS XC signal from system V11
D700 XRAY_On XGR/XGS X-ray On Signal (UT_act > 20 kV) V12
D700 INV_Err XGS Inverter Error V13
D700 FPGA_Err XGR/XGS Error Interrupt from FPGA V14
D700 MB 1000 mA XGR IT_act measurement range 1000 mA V15
D700 MB 100 mA XGR IT_act measurement range 100 mA
(amplification *10)
V16
D700 MB 25 mA XGR IT_act measurement range 25 mA
(amplification *40)
V17
D700 D_UT XGR Delta UT_act monitoring V18
58 XRS
Page 58 of 212
D701 HVC board
D702 FIL/RAC
D700 STOP XGR/XGS Stop report loop V20
D700 UT_MAX XGR UT_act max. monitoring V21
D700 A XGR/XGS System A on System B off V23
D700 rot XGR/XGS rotating on, stationary off V24
D701 LED 1 n.a. is not in use V205
D701 LED 4 n.a. HVC Error Interrupt V208
D702 n.a. XGR FPGA out LED 0lim_1: Lim regulator
FIL_1 active
LED_0
D702 n.a. XGR FPGA out LED 1 20peak_1: Peak regu-
lator FIL_1 active
LED_1
D702 n.a. XGR FPGA out LED 2 20STOP_FIL/
STOP_RAC.
LED_2
D702 n.a. XGR FPGA out LED 3 20RAC_State_0. LED_3
D702 n.a. XGR FPGA out LED 4 20RAC_State_1 LED_4
D702 n.a. XGR FPGA out LED 5 20HALL_A LED_5
D702 n.a. XGR FPGA out LED 6 20HALL_B LED_6
D702 n.a. XGR FPGA out LED 7 20FIL_Error_Int /
RAC_Error_Int
LED_7
XRS 59
Page 59 of 212
D703 XG board
D704 dongle board
Tab. 28 D704 dongle board
D790 PDC board
Fig. 32: D790 signal LEDs
Item signal name valid at Description LEDs
D703 LinkErr XGS/XGR Link Error LED[5]
D703 LightErr XGS/XGR Light Error LED[4]
D703 CfgErr XGS/XGR Config Error (FPGA not programmed) LED[3]
D703 DefCfg XGR xray_and_not_door (XGR) LED[2]
D703 RunCfg XGS door closed (XGS) LED[1]
D703 Prg XGR door closed (XGR via Fastlink) LED[0]
D703 LED 1 XGS XGS_off (XGS indication when starting
inverter)
LED[6]
D703 LED 2 XGS/XGR LifeCycle (flashes if FPGA is loaded) LED[7]
D704 VCC XGS/XGR Power supply 5 V V1
D704 P_15V XGS/XGR Power supply 15 V V2
60 XRS
Page 60 of 212
Tab. 29 D790 PDC board LEDs
D790 P_24V_SNT XGS P_24V from switched power supply
(only used for relays, feedback, and
fans)
V1
D790 VCC_SNT XGS VCC (5 V) from switched power supply V2
D790 VCC3.3 XGS FPGA IO voltage (3.3 V) V3
D790 LED morse XGS FPGA Lifecycle LED (if LED flashes >
FPGA is loaded and is functioning)
V4
D790 P_15V_SNT XGS P_15V from switched power supply V5
D790 VCC_INT XGS FPGA core voltage (1.5 V) V6
D790 N_15V_SNT XGS N_15V from switched power supply V7
D790 P_15V_SNT
_AUX
XGS P_15V from switched power supply for
inverter and fans.
V8
XRS 61
Page 61 of 212
Fig. 33: D790 PDC board signal LEDs
D790 Main_Sw XGS PDC Main Switch Breaker Signal V105
D790 Cooling_CB XGS Cooling Unit Breaker Signal V117
D790 XGS XGS XGS Breaker Signal V116
D790 PHS_CB XGS PHS Circuit Breaker Signal V138
D790 Gan_Stat XGS Gantry Stationary Breaker Signal V144
D790 Gan_Rot XGS Gantry Rotating Breaker Signal V143
D790 UPS XGS UPS Breaker Signal V157
D790 Insul_Power XGS Insulation Power Breaker Signal V158
62 XRS
Page 62 of 212
D790 Cooling XGS Cooling Unit Signal V106
D790 PHS XGS PHS Signal
LED off > trigger off and feedback off;
LED on > trigger and feedback on; LED
flashing > trigger and feedback different
V118
D790 L2_Perm_Ga
ntry
XGS L2 Gantry Signal
V119
D790 Charg_XGR XGS Charging XGR Signal
V139
D790 PWR_XGR XGS Power XGR Signal
V145
D790 IRS XGS IRS Signal
V146
D790 ICS_Ether XGS ICS Signal
V160
D790 Charg_XGS XGS Charging XGS Signal
V159
D790 PWR_XGS XGS Power XGS
V107
D790 Temp_Trans XGS Temp Transformer Signal V120
D790 Power_CTRL XGS Power Control Signal V121
XRS 63
Page 63 of 212
D790 Diff_Sw XGS Diff Switch Signal V140
D790 Volt_Prot XGS Voltage Protection Signal V147
D790 Current Loop XGS Current Loop Signal V148
D790 Door XGS Door switch Signal
LED On: Door open (in PDC_B always
on)
V162
D790 Fan Mode XGS Fan Mode
LED On: low noise mode (15 V)
V161
64 DMS
Page 64 of 212
3- 3DMS
General 0
Safety 0
WARNING
Avoid accidents and injury or damage to parts.
NOTE Follow ESD guidelines when handling the DMS.

NOTE Always close DMS covers prior to rotating the gantry!

Notes 0
NOTE There are 2 Scatter monitors on each module of the Definition
Flash.(Fig. 34 / p. 77)

The following table shows the used DMS modules depending on DMS type:
1. Before starting troubleshooting, be sure you troubleshoot the right area.
- To distinguish between the DMSs and IRS, check the data path first
- To distinguish between DMS A and DMS B, run the DMS tests and check if the
errors are related to DMS A or DMS B.
- To distinguish between DMS A and DMS B, especially if image quality problems
appear in Dual source modes, it is useful to use the 20 cm water phantom approx.
10cm excentrically.
- To distinguish between module and module cable, it is possible to swap the whole
module cable with a neighboring one.
If the error moves when swapping the whole cable, the problem is related to the mod-
ule cable.
DMS type Spare part module
DMS A 10393100 10393079
DMS B 10393150 10393079
DMS A 10393200 10393091
DMS B 10393210 10393091
DMS 65
Page 65 of 212
- To distinguish between module and backplane, it is possible to cross the module
cable at the backplane
NOTE A second peak may appear in the displayed plot (e.g. in sig-
nal value) with module cables crossed or swapped. This is
normal if no new calibration (e.g. a new Checkup or
Setup/Calibration) has been performed prior to starting a
new scan.

If the error moves when crossing the module cables at the backplane, the problem is
related to the module or module cable.
2. If possible, use the test modes with rotation for troubleshooting especially in case of
noise problems.
n.a.
Prerequisites 0
1. Check environmental conditions (especially in case of weak rings)
2. Check for objects in the scan field, e.g., contrast agent, labels,...
3. Try and reproduce an image the customer has complained about using the same
parameters
4. Use ROI/Ring and note the positions as a reference for the position expected to contain
the defect (two positions are possible).
66 DMS
Page 66 of 212
TSG Image Quality 3.1
This chapter provides a basic overview of different types of image quality problems and a
useful way for starting troubleshooting.
General 0
NOTE Most of the image quality problems are related to defective
channels within a detector module. That is why troubleshoot-
ing should start with defective channel detection. This chap-
ter is sorted for different types of image quality problems and
should guide you. The DMS tests are described later in this
chapter.

Possible reasons for ring and band (mostly 4, 8, or 16 channels) artifacts are:
Defective detector element
Defective detector cable
Defective backplane
Insufficient calibration (e.g. contrast agent at plexiglas ring)
Insufficient tune-up tables
Problem with balancing (reconstruction)
Insufficient environmental conditions
Defective IRS
Bands covering 16 channels might be caused by the incorrect Z-position of one mod-
ule. Run Z-position check of module.
NOTE Problems related to a single slice appear as permanent rings
in sequence modes, and as partial rings in spiral scans.

Possible reasons for streak artifacts are:
Defective detector module
Patched channels
Alignment adjustment
Tube arcing
Possible reasons for other artifacts, e.g. pattern in image, inhomogeneous areas
are:
The tube
The tube-side collimator
UHR comb
The tube cooling system
DMS 67
Page 67 of 212
The DMS power supply
NOTE If the DMS covers and parts have to be removed during trou-
bleshooting, follow the instructions in the Replacement of
Parts section for detailed information on how to remove and
install DMS parts. Never start gantry rotation with the DMS
covers removed.

TSG strong rings 0
In most cases we suspect that the detector module is defective.
NOTE Offset/noise values of an entire backplane that are out of tol-
erance indicate a defective DAS Controller or the cable
between the DAS Controller and the signal backplane
(black/blue) cable. Handle these cables carefully.

Tests which typically show problems in case of strong rings are:
Offset Value
Signal value
Start troubleshooting as follows:
Tab. 33 TSG
Step Action
1 Use ROI/Ring to determine the area of the defect in the customer image
2 Check for entries of defective channels in the reports. Refer to the section for
defective channel detection.
3 Compare the entries in reports to the channels you found with ROI/Ring.
a) if entries are related to the customer image -> patch out the channel
manually. Refer to the section for defective channel detection.
b) If no channel is related to the customer image, -> continue with step 4.
4 Run the defective channel detection in the Tune up platform.
a) if problem is solved -> Perform scans with the 20cm water phantom
(also excentrically) to check the image quality.
b) if not o.k., e.g., too many bad channels found, -> continue with step 5.
5 Run Guided Tour for image quality.
a) If there are errors found in one or more tests, -> continue with step 6.
6 If only one channel is found to be defective, -> patch out the channel man-
ually and check reports to see whether the defect has remained in the
system.
68 DMS
Page 68 of 212
TSG sporadic strong rings 0
Ask the customer to perform a Checkup in case of problems.
Tab. 34 TSG
7 If neighboring channels, channels in detector centers, or channels which
cannot be patched out are defective, -> continue with step 8.
8 Cross the module data cable on the backplane with the neighboring
module cable to distinguish between the module and the backplane.
Close all DMS covers.
Repeat the tests which showed errors before and check if the error moved.
a) If the error is still in the initial position -> replace the backplane.
b) If the error moves to a neighboring slot -> module or module cable
defective, continue with step 9.
9 Swap the complete module data cable with the neighboring module data
cable to distinguish between the module and the module data cable.
Repeat the tests which showed errors before and check if the error moved.
a) If the error is still in the initial position -> replace the module.
b) If the error moved to a neighboring slot -> replace the module cable.
10 Check the cables DCON => backplanes.
Especially if the errors are related to an entire backplane, -> check/swap
the black-blue cables between the DAS Controller and the signal back-
planes. Handle these cables gently!
Step Action
Step Action
1 Ask the customer to save the image in case of problems.
a) The image is important for further evaluations with ROI /Ring.
2 Ask the customer to perform a check-up in case of problems.
a) This particular (automatically generated) check-up table can be used for
further defective channel evaluations.
3 Use the ROI/Ring to determine the area of the defect in the customer image.
4 Check for entries of sporadic channels in the reports. Refer to the section for
DMS 69
Page 69 of 212
TSG weak rings 0
A ring is visible in homogeneous areas such as the cerebrum, even if the difference com-
pared to the neighboring channel is very small.
In most cases we expect the stability of the element affected to be insufficient.
Tests which typically show problems in case of weak rings:
BaseCal stability
Signal linearity
a) If sporadic entries are related to the customer image -> patch out the
channel manually. Refer to the section for defective channel detection.
a) if problem is solved, -> Perform scans with the 20cm water phantom
(also excentrically) to check the image quality.
b) If not o.k., e.g., too many defective channels are found, -> continue with
step 7.
a) If there are errors found in one or more tests, -> continue with step 8.
b) If no errors are found, -> continue with step 9.
8 If one channel is indicated as defective, -> patch out the channel manu-
ally.
9 Use reports and check for irregularities within the tests, especially in the area
of the defect in the customer image.
If irregularities are present, cross the module data cable on the backplane
with neighboring module data cable.
Repeat the tests which showed irregularities before.
a) Check reports again. If irregularities moved for 16 channels, -> replace
the module including the module cable/s.
b) If no difference is visible, swap back the data cable and close all DMS
covers.
c) Run a Checkup and check Reports for defective channels again.
10 Contact HSC for further steps.
Step Action
70 DMS
Page 70 of 212
Tab. 35 TSG
TSG sporadic weak rings 0
In case of sporadic weak rings, perform TSG weak rings first.
Additionally, start troubleshooting as follows:
Step Action
1 Check environmental conditions
2 Ensure that the DMS was powered on overnight.
3 Check that the Tune-up was performed correctly (use Report function).
4 Use ROI/Ring to find out the area of the defect in the customer image
5 Check for entries of sporadic channels in the reports. Refer to the section for
a) If entries are related to the customer image, -> patch out the channel
manually. Refer to the section for defective channel detection.
a) Compare test outputs to channels you found in the customer image with
the ROI/Ring function.
b) If only one channel is defective, -> patch out the channel manually.
c) If neighboring channels, channels in detector centers, or channels which
cannot be patched out are defective, -> continue with step 8.
8 Cross the module data cable on the backplane with the neighboring module
data cable.
Repeat the tests which showed errors before and check if errors move.
a) If the error is still in the initial position -> swap back data cable and con-
tinue with step 9.
b) If the error moved to the neighboring slot, -> module or module data
cable unstable/defective, continue with step 9 and step 10 prior to
replacing the module.
9 Check the power path. Refer to TSG DMS Power Path
a) If the power path and the DMS Power supply are o.k., -> continue with
step 10.
10 Perform Guided Table Generation in Tune up platform.
Note: Table Generations are performed.
a) If still not o.k. -> contact HSC for further steps.
DMS 71
Page 71 of 212
Tab. 36 TSG
TSG rings in outer slices only 0
Rings visible in the outermost slices may occur only in case of collimation problems.
Tab. 37 High voltage TSG
Step Action
1 Ask the customer to save the image in case of problems.
a) The image is important for further evaluations.
2 Ask the customer to perform a checkup in case of problems.
a) This particular checkup table can be used for further basecal evaluations.
3 Use the ROI/Ring to determine the area of the defect in the customer image.
4 Run the DMS Test Offset Value and check for irregularities in the offset and
noise plots.
5 Perform the BaseCal Stability Test. A difference between a satisfactory and
unsatisfactory Basecal table will show the problem.
a) If only one channel is noted, -> patch out the channel manually.
b) If neighboring channels, channels in detector centers, or channels which
cannot be patched out are noted -> replace the corresponding mod-
ule.
Step Action
a) If more channels or an entire row of channels are out of tolerance, ->
continue with step 2.
b) If only one channel is defective, -> continue with step 5.
2 Run Module Z-Alignment.
a) If out of tolerance, check the mechanical positioning of the module. Refer
to the replacement of parts section for instructions.
b) If in tolerance, -> continue with step 3.
Additionally, run modes with 24 x 1.2 mm and 32 x 0.6 mm to check if the
error occurs at the same physical slice position.
3 Run Z-Adjust in the Tune up platform.
a) If out of tolerance, troubleshoot the tube collimator.
b) If in tolerance, repeat defective channel detection. Additionally, con-
tinue with step 4.
72 DMS
Page 72 of 212
TSG Streak artifacts 0
1. Intermittent streaks tangential to a circle might be caused by a defective module
Tab. 38 TSG
2. Streaks tangential to a circle may be caused by unstable detector channels.
These kind of errors can also be caused by bad contact of the module data cables. Check
these cables during troubleshooting (reconnecting and swapping the data cables).
Tab. 39 TSG
3. Fine streak artifacts not correlated tangentially to any circle may be caused by incorrect
alignment.
4 Check slice thickness to ensure Constancy.
a) Run Quality Constancy, check results for slice measurement.
5 Run TSG strong rings
Step Action
Step Action
Step Action
2 Check if there are adjacent patched channels and continue with step 3.
3 Check reports for defective channels.
a) If -> must be changed is written in the reports, replace the correspond-
ing module.
b) If -> critical or is written in the reports, compare the entries to the area
of defect in the image. If this is identical, replace the module. If not ->
continue with step 4.
DMS 73
Page 73 of 212
Tab. 40 TSG
4. streak artifacts not correlated to any object may also be caused by tube arcing.
Tube arcing
Check the tube history for this particular scan to see if tube arcing was detected.
Getter tube
TSG Dual Source problems 0
Notes:
Image quality problems in dual source modes appear most often as a band in the area
where the scan field of the DMS B is extended by the outer channels of DMS A. In dual
source modes the inner area of the scan field are measured by both DMSs, the outer
area of the scan field is measured by DMS A only. Measure the HU in the area of the
band. Especially in case of a high absorption (obese patients), a high difference in HU
can be measured in the inner and outer area of the scan field.
NOTE For troubleshooting dual source problems, it is very helpful
to use the 20cm water phantom positioned approx. 10 cm
excentrically.


Step Action
1 Run a MTF measurement in quality constancy and check for tolerances.
a) If in tolerance, -> continue with step 2 and step 4.
b) If slightly out of tolerance, -> continue with step 2.
c) If results are not plausible, go directly to step 3.
d) If only UHR modes are out of tolerance, -> continue with step 4.
2 Run the focus alignment check in the Tune up platform.
a) Continue with Focus Alignment in the Tune up platform.
Note: Continue with Focus Alignment as well, if the Focus Alignment
check is in tolerance. If Focus Alignment fails, -> continue with step 3.
3 Troubleshoot tube collimator (PSD) and Focus deflection.
4 Run comb ali.
5 Run TSG weak rings.
74 DMS
Page 74 of 212
Tab. 41 TSG
TSG Spatial Resolution (bad MTF results) 0
Step Action
1 Check if the problem is caused by one of the DMSs, or if the problem
appears only in dual source modes.
a) Run single source modes (B-modes) in the Rot mode platform and use
the 20 cm water phantom (also excentrically). If the images are free of
artifacts, -> DMS B is ok. If the images show artifacts, troubleshoot the
DMS B first. Refer to the corresponding TSG in this document.
b) Run single source modes (A-modes) in the Rot mode platform and use
the 20 cm water phantom (also excentrically). If the images are free of
artifacts, -> DMS A is ok. If the images show artifacts, troubleshoot the
DMS A first. Refer to the corresponding TSG in this document.
c) Run dual source modes (A/B-modes) in the Rot mode platform and use
the 20cm water phantom positioned approx. 10cm excentrically. If arti-
facts appear in the area where DMS A adds DMS B data, -> the problem
is related to dual source modes only. Continue with step 2.
2 Check if the problem is caused by incorrect scatter radiation correction.
a) Run a dual source mode (A/B-modes) in the Rot mode platform with
Cross Scat selected (use the 20cm water phantom positioned approx.
10cm excentrically).
b) Run a dual source mode (A/B-modes) in the Rot mode platform with
Cross Scat deselected (use the 20cm water phantom positioned approx.
10cm excentrically).
With Cross Scat selected, the critical area (at approx. 32 cm) must look
more homogeneous. If no difference is visible, the correction is wrong
or not working. -> Continue with step 3.
3 Run quality constancy and check homogeneity.
a) If homogeneity is out of tolerance -> Run Water Scaling for the corre-
sponding DMS (A or B).
4 Perform Guided Table Generations in the Tune up platform. Call HSC for
further advice.
Note: Table Generations for DMS A and DMS B are performed. (approx. 2
hours)
a) If still not o.k. -> contact HSC for further steps.
DMS 75
Page 75 of 212
Tab. 42 TSG
TSG other artifacts 0
Pattern across the entire image
Perform tests or test images with and without X-ray to find out if the problem is related to
radiation. Additionally, run Guided Tour for image Quality.
If the problem is related to radiation:
- Check (replace) tube
- Check (replace) tube collimator
If the problem is not related to radiation:
- Check the DMS power supply
- Check the modules at slots 1 and 46 (air slice normalization)
Inhomogeneous areas
To identify the source of the problem, evaluate the BaseCal values (contact CS HSC).
The reasons for inhomogeneous areas in the image (with radiation) are mainly:
Defective BaseCal tables (visible mainly in the cerebrum sequence):
If calibration was performed with an absorber (contrast media) in the scan field:
The artifact is stable (in the same image area) in all images.
Check the reports for entries.
(Options > Service > Local Service > Reports )
Clean the plastic ring and check for other absorbers in the scan field.
Repeat calibration.
Inhomogeneous slices
If the mean value (of the same image area) differs from slice to slice :
Step Action
1 Run a MTF measurement in quality constancy and check for tolerances.
a) If slightly out of tolerance, -> continue with step 2.
b) If the results are not plausible, continue directly with step 3.
c) If only UHR modes are out of tolerance, -> continue with step 4.
2 Run Foc. Align. check in the Tune up platform.
a) Continue with Focus Alignment in the Tune up Platform.
Note: Repeat Focus Alignment as well, if the Focus Alignment check is
in tolerance. If focus alignment fails, -> continue with step 3.
3 Troubleshoot the tube including the tube collimator and the regulation circuit.
4 Run Comb Ali in the Tune up platform.
76 DMS
Page 76 of 212
Check the modules of slots 1 and 46 in DMS A (air slice normalization)
NOTE The task of air slice normalization is to equalize all slices.
Some of the channels of the modules in the first and last slot
(1 and 46 in DMS A) are used to calculate a mean value for
each slice. All slices are now compared and equalized.

Poor image quality due to wrong scan parameter or usage
There are also non-technical reasons for certain types of image quality problems.
Windmill artifact
If you browse through a stack of images, the image contains an artifact that moves like
a windmill. It is especially visible at the edges of bones.
Windmill artifacts occur due to undersampling or interpolation.
Compare the pitch used with the Siemens default values.
Check if the reconstructed slice width is 1.25 times the collimated slice width.
Involve Applications in troubleshooting
Artifacts due to patient positioning or use of positioning aids. (mainly streaks)
Head:
Check to see if the correct head holder was being used.
Body:
When using the CT-slicker, bend the edges down and glue them to the table
Tests for Image Quality 0
This chapter provides a list of all software tools available for handling DMS problems.
ROI/Ring
Scope
The ROI function (region of interest) is used to calculate the mean value and the stan-
dard deviation of a user-defined area.
The Ring function shows the correlation of a position in an image to 2 possible chan-
nels in the DMS that have been involved in creating data at that position.
How to find it
Options > Service > Local Service > Test Tools > ROI/Ring
DMS 77
Page 77 of 212
How to use
1. Select the desired order for sorting the images in the list box by activating the corre-
sponding radio button. (You may have to wait.)
2. Mark the image of your choice in the list box. Select the image by double-clicking or use
the Load Loid button.
The image will be displayed
The Switch to File Chooser button enables loading of images from different locations.
3. Select the radio button Ring
4. Use the left mouse button to move the ring to the desired position.
Use the center mouse button for windowing.
Read out the 2 possible channels (channel1, channel2) causing the problem.
Use this information as the basis for additional troubleshooting.
Defective channel detection
The software automatically detects bad channels. This includes also the scatter moni-
tors attached to the modules (see item 1). The scatter monitors are no separate spare
part. In case of a defective scatter monitor, replace the module. In DMS A 46 modules and
in DMS B 30 modules with 16 channels each are installed. If a scatter monitor is defective,
that is shown in the Defective channel history.
The following image shows the scatter monitors installed at the first Version of modules:
(Spare part compl. module: 10393081)
Fig. 34: Scatter monitors at detector module
The following image shows the scatter monitors installed at the newer Version of modules:
(Module kit compl. 10393079)
78 DMS
Page 78 of 212
Fig. 35: Scatter monitors at new type of detector modules
The center of the DMS and the first and last slot (used for air slice normalization) have to
have no defective channels. In all other slots, a certain number of defects is allowed.
1. Event Log
Critical defects are also written in the Event Log message: CT_TUN_164.
2. Check for allowed defects under Reports
- Using the Report function:
Options > Service > Local Service > Reports > Tune Up > Table Generations >
Def Channels.
NOTE If you find =>must be changed within the reports, the
defect cannot remain in the system and the module has to be
replaced.Critical modules shall only be replaced if these
modules cause artifacts. Tolerable modules are not to be
touched. Always compare the entries within the defective
channel history to the area in the image with the quality prob-
lem.

Shows status of last defective channel detection during check up.
- Options > Service > Local Service > Reports > Def. Chann. History.
A history of all channels that have been patched or unpatched is shown.
- Smart detection to eliminate sporadic channels
If a defective channel is detected during checkup, the stability value for the corre-
sponding channel is set to 50 and the channel is patched out.
If this channel is still defective during the next checkup, the stability value changes
from 50 to 100 and is still patched out.
If the channel is ok again, it is still patched out, but the value decreases from 100 to
90 ...80...70... and so on, during every following checkup until 0 is reached and the
channel is unpatched.
If the channel is bad again, the stability value increases by 50 (to a maximum of
100).
DMS 79
Page 79 of 212
- If no defect corresponds to the customer image, run the automatic defective channel
detection in the Tune-up platform. Refer to Defective channel detection in tune up
platform (item 3)
- If a scatter monitor is broken, it is indicated as S-Mon under Collimation and the
number of the corresponding module is displayed under Channel
3. Performing Defective Channel Detection in the Tune up Platform
- Select Local Service > TuneUp > Expert Mode > Defective Channels.
- Remove all absorbers.
- Select Scan Mode
- Click Auto.
To repeat automatic detection in case of unstable / implausible results, repeat the
procedure with the auto button.
- You will be asked to accept the current calibration.
- Click Save.
The IRS tables are transferred to the IRS.
If you click Cancel, no modifications to the tune-up and IRS tables will be stored.
- Check the Reports to determine whether a defect has been found and successfully
patched out.
- The program is not sensitive enough to detect all kinds of defects. If a defect is not
found during the procedure, the DMS tests are necessary.
NOTE If a defect was found and successfully patched out during
the procedure, the images must be free of artifacts now.

4. Editing the correction tables
- Select Local Service > TuneUp > Expert Mode > Defective Channels.
- Click the button for the desired detector slot.
Remark: A segment containing unsatisfactory elements is marked in red.
- After a while, the user interface will show the corresponding channel / slice matrix.
Now select the desired channel and slice. Select the element with the left mouse
and click it. The color will change from green to red.
Left-click to remove an unsatisfactory channel entry. The color will change from
red to green.
- Click save after modifications.
- Click save after modifications.
- For additional information regarding defective channel detection, refer to Hints for
Common for all tests which provide a plot function
NOTE The following is a plot from a Somatom Definition. The DMS
A in the Somatom Definition Flash has 736 channels, and the
DMS B has 480 channels.

80 DMS
Page 80 of 212
Fig. 36: Example of Relative Signal Value DMS A in error condition
Common for all tests which provide a plot function for the results:
- The button Show Plot shows the graphical output of the table.
Select all slices via Show All, none via Hide All, or a single slice via the list box.
Zoom in (or out via Survey) using the left mouse button. Mark the area of interest
while holding down the left button. Then press Zoom In .
Position the cursor at the desired location and wait for the display of:
- channel
- slice
- value at that position
The button Statistic displays the following for all slices: Minimum, Maximum, Mean,
and StdDev.
The min. and max. values are shown only if the checkbox Y-Auto Scale is not
marked.
DMS 81
Page 81 of 212
- The button Extract to file is used to store the result of the test to
c:\Somaris\ service\extract\DmsTestExtract.txt
Remark: If you want to store more than one file, you have to manually change the file
name.
- The display of the tolerances in the plot may be switched on or off using the
checkbox for Tolerance
Tolerances are available for all test results.
NOTE The Tolerance limits are indicated by red lines in the plot.

As a result, test result pages display the following at the top of each page: OK for tests
passed or Not OK for tests failed.
In case of values out of tolerance, the slice and channel are output.
Click the channel number and read out: Channel xxx and Slot xx.
Guided Tour for image quality
Scope
The Guided Tour is an automatic sequence containing most of the DMS tests available
at the system.
How to find it
Options > Service > Local Service > Test Tools > Image Quality
How to use
1. Press Go
NOTE Offset value starts automatically after pressing the Go But-
ton.

2. Wait for Press START key to appear and then press the Start button.
3. Wait for the results.
- Check if the test results match the artifact which you localized before with ROI/Ring.
Return to the TSG image quality.
Offset Value
Scope
This test is used to check the mean values and noise without X-ray.
How to find it (if not using the guided tour)
Options > Service > Local Service > Test Tools > DMS > Offset Value
82 DMS
Page 82 of 212
How to use
1. Select the desired mode.
2. Press Go
3. Wait for the result
Replace modules that exceed the threshold
4. Description of the result page
The results of the test are shown in two tables:
- Offset Value
- Offset noise
Both tables show Slice, Minimum, Maximum and Test Result.
Use the Show Plot button to display the plots.
Signal value
Scope
This test is used to check the mean values and noise with X-ray.
Different collimations are used.
Options > Service > Local Service > Test Tools > DMS > Signal Value
How to use
1. Select the desired mode
3. Description of the result page
The results of the test are shown in three tables:
- first table: Relative Signal Value
The result shows the averaged signal of the channels in relation to the neighborhood.
This table shows Slice, Minimum, Maximum, and Test Result.
- second table: Relative Standard Deviation
In addition, the monitor value is shown.
- third table: Absolute Signal Value
In addition, the monitor value is shown.
Common for all tables is:
DMS 83
Page 83 of 212
- The button Show Plot graphically displays the table.
It is possible to select all slices via Show All, none via Hide All, or a single slice via a
checkbox. It is also possible to Zoom In (or out via Survey) by using the left mouse
button. Mark the area of interest while holding down the left button
The button Statistic displays the following for all slices: Minimum, Maximum, Mean,
and StdDev.
The checkbox Y-AutoScale allows automatic scaling of the Y-axis.
- For values out of tolerance, slice and channel are output.
Click the channel number and read out: Channel xxx and Slot xx.
- The button Extract to file is used to store the result of the test to disk.
BaseCal Stability
Scope
The main function of the BaseCal stability test is to subtract the last two BaseCals of
one given mode in order to find unstable channels.
The structure of the BaseCal names is:
basecal_slice_ tube voltage_ scantime_ focus size_algorithmn_organ_focus type.
They are stored in c:\Somaris\service\datastore\icstables
Options > Service > Local Service > Test Tools > Sys. Test > BasCal Stability
How to use
2. Use the BaseCal corresponding to the mode the customer is complaining about.
3. Press Go
The result page is shown.
Before exchanging modules, compare the result with the results of ROI/Ring to
verify whether the customers image problem has been located.
4. Activate Show Plot
Evaluate the plot
In addition to the standard functions, you can define the Segments which should
be shown.
Remark: A BaseCal is referred to as a 360 degree rotation and is divided into 10
angular segments.
84 DMS
Page 84 of 212
Signal linearity
Scope
This test performs two scans with different tube currents (100mA and 300 mA).
Subtracting the mean values of these scans shows the deviation caused by the signal
non-linearity.
In addition, you may use phantoms in the scan field to check the low signal linearity.
Options > Service > Local Service > Test Tools > DMS > Signal Lin.
How to use
1. Wait for the Press START key to appear and press the Start button
The test result page is displayed.
In case channels are out of tolerance, change the corresponding module.
2. Press Show Plot
The plot is displayed
Assignment test
Scope
The assignment test is an internal addressing test of the DAS controller and the outgo-
ing data path.
Options > Service > Local Service > Test Tools > DMS > Assignment
How to use
2. Wait for the Press START key to appear and then press the Start button
Wait for the result page
3. Activate Show Plot
A continuous staircase from upper left to lower right should be visible for all slices.
Remark: In addition to the standard function, you can define:
- Segments (frames)
and
- FFS 1, 2 or all
4. Interpretation of the result
The possibly defective part:
- DAS Controller
DMS 85
Page 85 of 212
Data Link test
Scope
The Data link test is a communication test for the data paths.
Options > Service > Local Service > Test Tools > Sys. communication > Datalink
How to use
1. For complete auto test select all modes.
2. Press Go
3. Wait for the Result and press Done or Repeat the test.
If the result is out of tolerance
Check for data transmission errors
Troubleshoot the data path
Resend
Scope
The Resend test is used to check the Data resend mechanism. Number of resends is
checked.
How to find it
Options > Service > Local Service > Test Tools > Sys. communication > Resend
How to use
1. For complete test select Detector System A and B
2. Press Go
3. Wait for the Result.
Check for DMS related errors
X-ray Path
Scope
This test involves finding any contamination in the X-ray path.
A scan is performed and the 2 focal spots are subtracted.
The plot's appearance will vary depending on the position of an object in the X-ray path.
Two peaks are displayed.
86 DMS
Page 86 of 212
- If the object is near the detector, the distance between the two peaks will be small.
- If the object is near the tube (or tube collimator), the distance between the two peaks
will be large.
Options > Service > Local Service > Test Tools > Sys. Test > X-ray Path
How to use
2. Wait for the Press START key to appear and then press the Start button.
If channels are out of tolerance, contact CS HSC for further advice.
3. Press Show Plot to see the plot
Capture the plot and supply it to CS HSC for additional evaluation.
Tube Collim. Check
Scope
This test checks the correct opening width and Z-position of the tube collimators. IRS
tables are used, which have been generated during air calibration. No scans are per-
formed during this check.
How to find it
Options > Service > Local Service > Tuneup > Expert Mode > Tube Collim. Check
How to use
1. Press Go
2. Wait until the message Tube collimator Check completed appears.
Perform a tune-up. Follow the guided tour for Tube Collimator
Troubleshoot the tube collimator and the regulation circuit (UMAR).
Focus alignment check
Scope
This test uses the ball phantom to check, if the electromagnetic focus deflection (flying
focal spot) in the PHI and in the Z-position is working properly.
How to find it
Options > Service > Local Service > Tuneup > Expert Mode > Foc.Align.check
DMS 87
Page 87 of 212
How to use
1. Select System A / System B or both in the platform.
2. Press Go
3. Select and insert phantom.
4. Press Go
5. Wait for the Press START key to appear and then press the Start button.
6. Wait for the results.
Repeat the test to find out, if the result is failing continuously.
Perform Z-Adjust and Focus Alignment and repeat the test.
Run the Guided Tour for X-ray tube Tune up.
Exchange X-Ray Tube
Note: Contact CS HSC before ordering the tube.
If the result is not plausible
Check if the Focus Alignment was performed after tube replacement.
Troubleshoot the tube collimator and focus deflection.
Module Z alignment
Scope
It is possible to locate the modules in the wrong position during replacement. An auto-
matic module position check is implemented in the guided tours. Follow the software
instructions in this case.
The Z-alignment of the module is tested by evaluating 2 air scans with different tube col-
limator positions.
How to find it
Options>Service>Local Service>Test Tools>DMS>Module Z-Align
How to use
1. Press Go
3. Press Show Plot
4. Check if there is a drop of 16 channels (use the Zoom function), especially at the posi-
tion where you performed repairs.
If yes, loosen the module exchanged previously and press it toward the rotating plane
while you are fixing the situation. Repeat the test.
88 DMS
Page 88 of 212
Analyze
Scope
Analyze is a versatile tool, used to evaluate raw data as well as header data.
The following functions are useful for field services:
- Integration time
- Dose monitor
- DMS Temperatures
- Raw Data Frequency Analysis
How to find it
Options > Service > Local Service > Test Tools > Analyze
How to use
Using the macros under Special
1. Select the radio button ICS-RawData
2. Mark the desired raw data set in the list box
3. Press Go, select Raw data under File content and Press Go again.
View is automatically selected and the plot appears.
4. Select Special
5. Mark the desired checkbox
- ReadingNo
- TubeAngle
- MaximumValue
- ErrorInfo
- CRC Error
- IntegrationTime
- Dose monitor
- DMS-Temperature 1...n
and press Go
The corresponding curve is displayed.
Using the raw data frequency analysis under Analyze
- Load a static mode with 2 x 1.0 mm. (Select small UHR Focus)
- Perform 2 scans of that mode and use the second one
DMS 89
Page 89 of 212
- Open an additional window.
- Start Options > Service > Local Service >TestTools > Analyze
- Select ICS-Rawdata, mark rotstatic.raw, and press Go.
- Select Raw data under File content and Press Go again.
- Select Tools
- Select Raw Data - Frequency Analysis and press Go
- Select the channels
Start with 305 to 368.
- Do not select the checkbox for fusing the slices.
- Do not select Separate FFS
- Select all slices
90 DMS
Page 90 of 212
Zoom in the result, if necessary.
The X-axis shows the frequency, and the Y-axis shows the amplitude.
Fig. 37: Example of raw data frequency analysis
The amplitude at the first peak (here 120 Hz) shows the quality of anode rotation
(wobbling anode). A peak does not necessarily mean that the tube has to be
replaced. Check also for tube arcing and other errors related to the tube.
The amplitude at the first harmonic shows the quality of the emitter (tube).
NOTE In addition to this test, the tube has to be checked before
making the decision to replace it.

Send the plot to CS HSC for additional evaluation.
DMS 91
Page 91 of 212
TSG DMS Components 3.2
TSG DMS Power path 0
NOTE To order the correct power supply, always select the correct
DMS type in the Spare Parts Catalog.
The newer power supply types might look slightly different
(LEDs and measurement points). The functionality is identi-
cal.

The power supplies for the DMS are located behind the metal DMS front covers. To check
the power supplies, check the LEDs at the front of the corresponding DMS.
Troubleshooting hint: If only the 24V LED at the power supply is on, the problem may be
related to the DAS Controller or an overtemperature inside the DMS. In case of overtem-
perature, troubleshoot the cooling path.
In case of 'temperature o.k.', proceed as follows:
Reload Firmware
Check the error message
Check and reconnect the cable between DCON and the signal backplane (black-blue
cable)
Replace DCON
Replace the signal backplane
Troubleshooting the power path
Measure the voltages at the front side of the power supply/ies
Power supply 10023484 (Astec):
DMS types Valid power supplies
DMS A part no. 10393100
(uses 2 power supplies)
Part no. 10023484 (Astec)
or
Part no. 07274306 (Lambda)
DMS B part no. 10393150
(uses 1 power supply)
Part no. 10023484 (Astec)
or
DMS A part no. 10393200
DMS B part no. 10393210
92 DMS
Page 92 of 212
Power supply 07274306 (Lambda):
TSG short-circuit in power supply
To track down a short circuit in the power supplies, cables, backplanes, DAS Controller, or
modules, perform the following:
Before following this advice, be sure the mains input for the DMS power supply is ok.
Tab. 43 TSG short-circuit in the DMS power path
Test point Ground Description
+24V / 4A +24_RET Right power supply: DCON +
right signal backplane.
Left power supply: left signal
backplane
POS_V_D DGND 3.3V / 20A module digital
POS_V_A AGND 3V / 72A module analog
NEG_V_A AGND -2.8V / 72A module analog
Test point Ground Description
+24V / 4A Return Power supply: DCON, right
signal backplane, left signal
backplane
POS_V_A Return 3.25V / 60A module analog
NEG_V_A Return -2.8V / 60A module analog
POS_V_D Return 3.3V / 30A module digital
Step Action
1 Check the Power LEDs on the DMS power supply.
a) If the LED +24V is off -> continue with step 2.
b) If the LED POS_V_D, POS_V_A or NEG_V_A is off -> continue
with step 5.
2 Disconnect X1 at left DMS backplane, switch the gantry off/on, and check
the DMS power supply LED +24V.
a) If the LED is off -> continue with step3
b) If +24V LED is on -> problem is related to left signal backplane half
3 Disconnect X36 at right signal backplane half, switch the gantry off/on, and
check the DMS power supply LED: +24V.
a) If the LED is off -> continue with step 4
b) If the +24V LED is on -> problem is related to right backplane half.
DMS 93
Page 93 of 212
TSG UHR mechanics 0
If there are problems with the UHR mechanics, follow the advice provided in the error mes-
sage.
To understand the function of the UHR control (Implemented at UMAR), the current applied
to the UHR motor is shown in the next figure.
UHR phi-z comb: Current measurement is not possible. Follow the mechanical checks.
Fig. 38: Current of UHR motor
To identify problems of the UHR control, you may perform the following tests:
Mechanics
Check whether the mechanics are operating smoothly by moving the UHR in and out by
hand. (remove the UHR motor to be able to move the UHR without applying too much
force)
If the mechanics are not moving smoothly:
Check for parts blocking the UHR.
4 Disconnect X500 at DCON, switch the gantry off/on, and check the DMS
power supply LED +24V.
a) If the LED is off -> check input voltage.
b) If the +24V LED is on -> problem is related to DCON.
5 Disconnect X2 on the rear side of the DMS power supply (unplug DMS
power supply), switch the gantry off/on, and check the DMS power supply
LEDs: POS_V_D, POS_V_A and NEG_V_A.
a) If the LEDs are off -> check input voltage.
b) If the LEDs: POS_V_D, POS_V_A and NEG_V_A are on -> prob-
lem is related to one of the modules on the respective backplane half. ->
Disconnect the modules to isolate the fault. Note, it is necessary to switch
the Gantry off and on again after a module is disconnected.
Step Action
94 DMS
Page 94 of 212
Service switches
Using the UHR service mode with the system in standby mode:
- Press Stop on the gantry or control box
- Switch on the service switch on the UMAR
- Press S1 (in) and S2 (out) on the UMAR to check UHR comb movement
- Press Test on the UMAR to perform a self-test
- Switch off the service switch on the UMAR
Using the UHR service mode with the system not in standby mode:
- Switch the gantry to Comp on
- Switch on the service switch on the UMAR
- Switch the gantry to Sys on
- If the ICS aborts with the message Cant continue..., press the Test button on the
UMAR prior to using S1 (in) or S2 (out)
- Switch off the service switch on the UMAR
Limit switches
If the problem is related to the limit switches:
- Check their functionality using the service switch on the UMAR and move the UHR in
and out by pressing S1 (UHR in) or S2 (UHR out). (Described above)
Ensure that MOVE LED on the UMAR is activated at both mechanical end stops.
If the LED is not activated at the end stop on one side:
Position the UHR in the middle, so that no limit switch is activated.
Use a piece of metal, e.g., a screwdriver, to check whether the limit switches are
working properly.
If the LED in the limit switch is not activating:
Check the power supply for the switch on the UHR control
Replace the corresponding limit switch
- For checking the adjustment of limit switches, refer to the document Replacement of
Parts: Gantry.
UHR motor
If the problem is related to the UHR motor:
- Check their functionality using the service switch on the UMAR and move the UHR in
and out by pressing S1 (UHR in) or S2 (UHR out). (Described above)
Observe whether the UHR is moving.
If the UHR comb is not moving:
Measure the voltage for the UHR motor on UHR control D586 J1 (power) while
they are activated via the service switches.
If the motor is not moving while voltage is present, replace the motor.
If there is no voltage, replace D586.
DMS 95
Page 95 of 212
Adjustment
To ensure the UHR is adjusted correctly in the phi-direction, perform an MTF measure-
ment.
If the results are in tolerance, the adjustment is OK.
If the results are out of tolerance, perform COMB ALI in the Tune-up platform.
If the comb is fully maladjusted, the core position can be identified by evaluating a mean
value plot of an UHR mode.
Core position check of UHR comb
If the UHR comb was largely maladjusted or the initial position was lost, you can try and
find the core position by using analyze.
Start Analyze
Options > Service > Local Service > Test Tools > Analyze
Select the radio button ICS-Tables
Mark an UHR mode BaseCal and press Go.
The plot of the BaseCal appears.
Fig. 39: Example of an UHR BaseCal plot
96 DMS
Page 96 of 212
Zoom both edges to see the channel where the UHR comb starts and ends.
Compare your results with this example showing a well-adjusted UHR.
The first channel with a higher value is channel 139
The last channel with a higher value is channel 534
Disabling the UHR comb
If a defective UHR comb prevents the system from reaching standby, the comb can be
disabled momentarily.
How to disable the UHR comb:
1. Move the comb manually to the mechanical end out of the X-ray path
2. Remove connector J7
Fig. 42: UHR connection
Pos. 1 Connector J7
Fig. 40: Zoom of lower channel side Fig. 41: Zoom of higher channel side
DMS 97
Page 97 of 212
3. After the next INIT, save the machine configuration by selecting none for UHR (see
example below)
Fig. 43: Factory-specific CT configuration
4. Save a copy of the original license.dat file
98 DMS
Page 98 of 212
5. Disable the UHR licenses by putting a # in front of the related licenses. (See example
below)
Fig. 44: License.dat
Pos. 1 License deactivation
NOTE Do not forget to restore the original configuration once the
UHR comb is working again.

DMS 99
Page 99 of 212
Tests & Hints 3.3
DAS Type not o.k. 0
Error message: DAS Type not o.k.
- most likely the ID board is defective => Contact HSC
Firmware update failed 0
Possible reasons:
- black-blue cables between DCON and signal backplanes
- DMS power supply/ies.
- DAS Controller
Test in the following order:
- Check the black-blue cables between DCON and the signal backplanes for proper
connections
- Check LEDs at the power supply/ies. All 4 green LEDs have to be on after the Firm-
ware update. During the Firmware update, the LEDs are switched off
- Check if the red LED at DCON is on. If yes, restart the Firmware update.
- Replace the DCON
Dynamic collimation 0
Indications for a wrong dynamic collimation:
- Spiral scans start or end with bright images, HU too high in this area.
- White stripes in MPR
Possible reasons:
- wrong dynamic collimation, tube collimator moves too far which results in not enough
dose.
- run the test for dynamic collimation (Dyn. Collimation / p. 180)
- follow the TSG for Dyn. collimation
Signals from half detector missing 0
Possible reason:
- black-blue cables between DAS Controller and Signal backplane defective.
100 DMS
Page 100 of 212
NOTE These 2 cables have to be handled carefully! It is recom-
mended to order such a cable as a spare. For troubleshoot-
ing purposes, the 2 cables can be swapped.

- Check cable for good contact
- Gently swap the 2 black-blue cables and check, if error moves.
- Replace the corresponding signal backplane
Storage of Test Results 0
Test results are stored in two different ways:
- As HTML files
Path:c:\Somaris\service\html\report\htmlreport
- As TXT files
Path:C:\Somaris\service\extract
- Additionally, it is sometimes helpful to use a screenshot to report the result plots:
- Activate the window you intend to capture
- Use Ctrl / PrtSc to capture the window
- Start > Programs > Accessories > Paint
- Use Edit > paste
- File > save as and use file type gif to reduce the size
Normally, HTML files are used to store test results.
However, the plots of the DMS tests are usually stored in a text file (via Extract to File
button). Please note: the file name has to be changed manually. Otherwise, the file will
be overwritten each time the softkey is used.
The file may be displayed using Excel (e.g. after manual remote transfer).
Environmental Conditions 0
Environmental conditions are a possible cause of weak ring artifacts.
Check the Somaris log for errors and warnings .
Gantry
Inside the gantry, the temperature is regulated.
To read out the actual values for temperature, use the control platform
The output of the table may be selected in decimal or hexadecimal values.
The gantry has to be in the standby mode when accessing the control system.
DMS 101
Page 101 of 212
To read out the actual temperature of the gantry, perform the following:
1. Options > Service > Local Service > Control > Table load/modify
2. Select Volatile under TABLE SOURCE.
3. In the list box TABLE NAMES select T00
4. Press Go
The parameter set for the table T00 is shown.
Use the slider to move to the desired information
- gantry temperature [degrees C]
The temperature air inlet has to be in the range of 19C +/- 1C
DMS
Environmental conditions for the DMS are:
- Temperature :
Check the Event log for errors and warnings concerning temperature problems.
If raw data is available for the images the customer is complaining about, use
Analyze to read out the temperature from the header data.
This indicates the temperature at the time of data acquisition.
Overview -Temperatures
Temperatures:
There are different limits for the internal DMS temperature (set by the UMAR).
40C - temp warning level; entry in the event log
50C - temp error level; entry in the event log; electronics are switched off.
Hints for defective channel detection 0
Additional information for defective channel detection
After part replacement (e.g. module) or if you do not succeed in removing unsatisfac-
tory channels, delete the IRS tables in the ICS as follows:
1. Go to C:\Somaris\service\datastore\icstable
2. Delete all files starting with badchannelsxxxxx
3. Start an automatic detection under service to create an actual channel status.
A partial tune-up as described in the guided tours follows.
Using Reports to view details of the Defective Channels Correction
1. Open an additional window and choose Reports .
2. From the menu bar TuneUp/QA/Tests choose:
TuneUp > Table Generation > Def. Channels
3. Double-click Report to view the results.
Detector Statistics shows all currently defective channels including scatter
monitors.
- Shows channels added by Automatic Detection and
- Manually Added/Removed
102 DMS
Page 102 of 212
Distinguishing between the module and other components 0
If one ore more broken channels have been found using the Guided Tour or other tests, you
have to find out if the problem is really caused by the module or by other components.
1. Cross the module cable on the DMS backplane with the neighboring one.
2. Close the DMS covers and repeat the test or mode that showed errors before.
If the error moves to the neighboring slot, the module or module cable is broken.
Continue with step 3.
If the error does not move, the backplane (or DAS Controller) is defective.
NOTE A second peak may appear now in the displayed plot. This is
normal with crossed/swapped module cables, if no new cali-
bration,(e.g. a new Checkup or Setup/Calibration) has been
performed prior to starting the second test run.

3. To distinguish between the module and module cable, swap the whole module cable
(not crossed) with the cable of the neighboring module. Close the DMS covers and
repeat the test or mode that showed errors before.
If the error moves to the neighboring slot, the module cable is defective.
If error does not move, the module is defective.
4. Swap module cable to its original position.
5. Run an assignment test to check the addressing of the DAS Controller.
If the assignment test fails, replace the DAS Controller.
Replace the corresponding backplane.
How to interpret the physicists line 0
To find the decoding for the physicists line, go to:
- Somaris > Help > Contents and Index and
- select the tab card Search and
- type in the physicists line
The explanation is shown
Datalink 103
Page 103 of 212
4- 4Datalink
General 0
Safety 0
WARNING
Avoid accidents and injury or damage to parts.
NOTE Follow ESD guidelines when touching parts of the data trans-
mission path.

Notes 0
3 rotating data rings are installed (one for Signal Link and two for datalink A+B). Keep this
in mind when following the TSG.
Basic function:
The DMS data paths operate at 4.25 Gbps. The connection between the DMS and the IRS
receiver is established through 2 simplex connections over rotating high speed data rings.
There is a retransmission in condition of missing packets or bad readings.
In the event log, the number of readings can be found in the information message
CT_ITX_ 2 and in the warning message CT_ITX_7.
DMS (DCON) to IRS
For DMS A data, the inner structure of the 3 rotating data rings is used. For DMS B data
the outermost structure is used. The middle structure is used for the signal link.
NOTE For troubleshooting, the A data can be sent through the B
path. > the fiber-optic cables at the Two Tx modules and at
the IRS Receiver can be interchanged to use the other path.
There is retransmission in case of missing packets or bad
readings.

LEDs on Central Units
1. Green Power: off if the power to the corresponding Tx or Rx module is missing.
2. Yellow Signal: off if no signal or a signal with low amplitude is detected.
104 Datalink
Page 104 of 212
3. Orange Sync: off or reduced intensity if sync error is detected.
LEDs for datalink on Receiver(s) in IRS
1. Yellow Ready DL: on when a mode is load
2. Red Error DL: on if unsatisfactory readings are detected. When a segment on the data
ring is defective, the LED is on synchronous to gantry rotation, depending on the
angular position of the defect.
3. Green Data DL: on if DMS is idle and dummy data or measurement data is received
4. Red NoSync DL: on if sync error is detected.
5. Red NoSignal DL: on if no optical signal or signal with low amplitude is detected.
6. Red CRC Error DL: counts unsatisfactory readings received from DCON. Reset with
next init.
NOTE The Error, No Sync, No Signal and CRC LEDs are also
switched on in case of sporadic errors for 100ms. Check
these LEDs while rotating the data ring by hand.

Abbreviations
Tx > Transmitter Electronics
Rx > Receiver Electronics
DCON > DAS Controller
Rec > Receiver in IRS
FODL1...3 > fiber optic datalink (connections for fiber-optic cables at DCON)
Prerequisites 0
For a quick check of the data path, a spare fiber-optic cable and a fiber-optic coupler
are necessary. A short and long fiber-optic cable are supplied with every system.
Use these fiber-optic cables to patch a certain segment of the data path in order to isolate
the problem.
The image below shows one of the supplied spare fiber-optic cables with its connectors
separated for simplex use.
Datalink 105
Page 105 of 212
Fig. 45: Spare fiber optic cable with coupler
Pos. 1 spare fiber optic cable
Pos. 2 coupler
Pos. 3 fiber optic connectors, separated for simplex connections
106 Datalink
Page 106 of 212
Troubleshooting Data transmission 4.1
General 0
NOTE All modules are connected to Central Units, which monitor
the function and state of the connected modules.

NOTE At the Tx and Rx modules, simplex fiber-optic connections
are used.
The supplied spare fiber-optic cables are duplex connec-
tions. To use these cables for simplex connections, separate
the cables at the connector.

Overview 0
NOTE Start troubleshooting always by doing a check the LEDs at
the Central Units and rotating the gantry by hand while doing
a check the error LED at the rear side of the IRS.

On every TX and RX - module installed in the system there is a green LED, which shows
that the TX-/RX - module is on. The LED will blink. The following image shows the location
of the LED at rotating TX-/RX modules.
Fig. 46: RX and TX modules
Pos. 1 LED at RX module ROT
Pos. 2 LED at TX modules ROT
Datalink 107
Page 107 of 212
NOTE There are 2 Central Units CU (one stationary and one rotat-
ing) which include all necessary LEDs. Also no wiring inter-
faces are used because the Tx and Rx modules are supplied
with power by the Central Units.

1. Central Unit STAT
The following components are connected to the Central Unit STAT:
- RX module STAT Data Path A
- RX module STAT Data Path B
- RX module STAT Signal Link
- Tx Module STAT Signal Link
Fig. 47: Central Unit STAT
Pos. 1 Central Unit STAT
Pos. 2 RX Module STAT Data Path A
Pos. 3 RX Module STAT Data Path B
Pos. 4 RX Module STAT Signal Link
Pos. 5 TX Module STAT Signal Link
2. RX Unit STAT2 for Data Path A + Signal Link
108 Datalink
Page 108 of 212
NOTE The Rx unit STAT2 consists of two Rx modules: the Rx mod-
ule for datalink A and the Rx module for the signal link. These
two modules cannot be interchanged for troubleshooting.
For troubleshooting functions, interchange the fiber-optical
cables at the Rx modules and check the LEDs at the central
unit STAT. Always replace the full RX UNIT STAT2 in case of
a broken Rx module.
Look at the LEDs on the Central Unit if troubleshooting a
transmission error in a CO system.

Fig. 48: RX Unit STAT2
Pos. 1 RX Unit STAT2
3. RX Unit STAT1
Datalink 109
Page 109 of 212
NOTE The RX Unit STAT1 consists of one RX module. The Rx mod-
ule for Datalink B. This module cannot be interchanged for
troubleshooting. Always replace the full Rx UNIT STAT1 in
case of a broken Rx module.
Look at the LEDs on the Central Unit if troubleshooting a
transmission error in a CO system.

Pos. 1 RX Unit STAT1 Data Path B
4. Tx module STAT
The Tx module STAT is used for the Signal Link from STAT to ROT.
NOTE The Tx module STAT is connected to the CU STAT.
Look at the LEDs on the CU for troubleshooting.

Fig. 50: TX Module STAT
Pos. 1 TX Module Stat (fastlink)
5. Central Unit ROT
The following components are connected to the Central Unit ROT:
110 Datalink
Page 110 of 212
- Tx Module ROT Data Path A
- Tx Module ROT Data Path B
- Tx Module ROT Signal Link
- RX module ROT Signal Link
Fig. 51: Central Unit ROT
Pos. 1 Central Unit ROT
Pos. 2 TX Module ROT Data Path A
Pos. 3 TX Module ROT Data Path B
Pos. 4 TX Module ROT Signal Link
Pos. 5 RX Module ROT Signal Link
6. Rx module ROT
The Rx module ROT is used for the Signal Link from STAT to ROT.
Datalink 111
Page 111 of 212
NOTE The Rx module ROT is connected to the CU ROT. The Rx
module cannot be interchanged for troubleshooting. In case
of a defective Rx module, replace the full unit (Rx module
including carrier).

Fig. 52: Rx Module ROT
Pos. 1 RX module ROT
7. Tx modules ROT
The following image shows the Tx modules Rot. One Tx module for Data Path A, one
for Data Path B and one Tx module for the Signal Link.
112 Datalink
Page 112 of 212
NOTE Look at the LEDs on the CU for troubleshooting.

Fig. 53: TX Modules ROT
Datalink 113
Page 113 of 212
TSG Datalink 4.2
Depending on the type of error, select the corresponding section.
NOTE It may be helpful to check the event log in case of missing
readings. In the event log, the number of readings can be
found in the information message CT_ITX_ 2 and in the warn-
ing message CT_ITX_7.

TSG permanent errors on DAS Controller(s) > IRS Receiver 0
Tab. 44 TSG permanent errors DCON to IRS
Step Action
1 Check the power for Tx module(s) ROT at CU ROT.
a) if the green LED is off, > Tx is module defective or power from PDR is
missing. Check power supply.
Additionally, do the Data Link Test and check gantry error monitor for
errors reported by UMAR: Power error
b) If the LED is on, continue with step 2.
2 Check signal for Tx module(s) ROT at CU ROT.
a) If one or both of the yellow LEDs are off, > missing optical signal from
DCON/s or broken/dirty fiber optic cable connections, or the Tx module
is defective. Clean the fiber-optic cable and do a check again. If LED
stays off, continue with step 3.
Additionally, do the Data Link Test and check gantry error monitor for
errors reported from UMAR: Signal error
c) if the orange Sync LED at CU ROT is on, but with reduced brightness >
check quality of signal. Refer to TSG data quality at Tx modules
3 Check output of corresponding DCON by establishing a direct connection
between DCON and Rec in IRS with the spare fiber optic cable.
a) If Red NO Signal LED on Rec is on > DCON defective.
b) if Red Link NO Signal LED on Rec turns off > DCON and Rec o.k.
Establish the original connection and interchange the Two fiber-optic
cables at the Tx input. If yellow LED for Tx module at CU ROT is on at
this time, > cable between DCON and Tx module is defective. If yellow
LED stays off > replace the Tx module.
4 Check power for the corresponding stationary Rx module (A or B) at CU
STAT.
a) if the green LED at CU STAT is off > Rx module is defective or the power
from UMAS is missing. Troubleshoot the power path first.
b) if the LED is on, continue with step 5.
114 Datalink
Page 114 of 212
TSG data quality at Tx modules 0
The orange sync LEDs at the CUs must show a noticeable increase in light intensity in an
idle system, or when plugging and unplugging the fiber-optic cable. Before starting trouble-
shooting for data quality, do the TSG for permanent errors first.
5 Check signal for the Rx module at CU STAT.
a) if the yellow LED at CU STAT is off, > missing signal from transmitter,
or rotating data ring is defective, or receiver carrier is maladjusted/defec-
tive, or Rx module is defective. Continue with step 6.
b) If the yellow LED at CU STAT is on, continue with step 7.
c) if the orange sync LED at CU STAT is on, but with reduced brightness >
check quality of signal. Refer to TSG data quality at Rx modules.
6 Check the data ring.
a) adjust the triple receiver carrier (refer to replacement of parts section)
and check the microstrip antenna. Refer to How to check the transmit-
ting antenna. If resistance of microstrip antenna is o.k > replace the Tx
module.
If resistance of microstrip antenna is not ok > replace the rotating Data
Ring.
Call HSC before replacing the Data Ring.
7 Check the connection Rx module to Rec.
a) If red Link No Signal LED at Rec is on > missing signal from Rx module,
or broken/dirty fiber optic connection, or Rec is defective. Clean the
fiber-optic cable and do a check again. If the LED is stays on, continue
with step 8.
b) If the LED is off at this time, do the data link test.
8 Use spare cable between Rx module and Rec.
a) If red Link No Signal LED at Rec is stays on > Rx module or Rec in IRS
is defective. Continue with step 9.
b) If the No Signal LED is off at this time > replace the fiber-optic cable.
9 Interchange the Two fiber-optic cables at the Rx modules or at the Rec in
IRS.
a) If the problem moves to the other slot > replace the Rx module.
b) If the error is stays at the first slot> replace the Rec.
Step Action
Datalink 115
Page 115 of 212
Tab. 45 TSG data quality at Tx modules
TSG data quality at RX modules 0
First make sure that the quality of the data signal at the Tx modules is OK (see above).
When plugging the fiber-optic cable into the Tx modules, there must be a noticeable
increase in light intensity at the orange sync LED on both, the Tx and Rx modules, in an
idle system.
Step Action
1 Unplug and plug the fiber-optic cables at the Tx modules rot.
a) if sync LED at CU ROT shows reduced intensity (e.g. due to blinking at
a high rate) > DCON output broken, or broken/dirty fiber optic connection
from corresponding DCON, or Tx module broken. Clean the fiber-optic
cable and do a check again. If the LED still shows reduced intensity, con-
tinue with step 2.
2 Check the DCON output using a spare fiber-optic cable.
a) Connect FODL1 to the corresponding Tx input with the spare cable. If the
orange LED is o.k. at this time > replace the fiber-optic cable.
b) If the orange LED still shows reduced light intensity (with spare cable
installed), > DCON or the Tx module is defective. Continue with step 3.
3 Check the DCON using the indicator on the CU ROT for the rotating fastlink
transmitter.
a) Connect FODL1 to the rotating Tx module for fastlink data using the
spare fiber-optic cable. If the sync LED for the rotating fastlink transmitter
at CU ROT also shows reduced intensity > replace DCON.
b) If sync LED for the rotating fastlink transmitter shows a noticeable
increase in light intensity> replace the Tx module.
4 Additionally, do a Data Link test.
a) Check the gantry error monitor in the Data Link test for errors reported
by UMAR: Link error. >replace the Tx module.
116 Datalink
Page 116 of 212
Tab. 46 TSG
TSG sporadic errors in link DCON > IRS 0
The following table gives step by step how to troubleshoot sporadic transmission problems.
Tab. 47 TSG
Step Action
1 Unplug and plug in the fiber-optic cables at the Tx modules.
a) if the sync LED at CU STAT for Rx module permanently shows reduced
intensity (e.g. due to blinking at a high rate) > Tx module (output) is
defective, or the rotating Data Ring is defective, or receiver carrier is mal-
adjusted/defective, or Rx module is defective. Continue with step 2.
2 Adjust the receiver carrier (refer to the replacement of parts section) and
check the microstrip antenna. Refer to How to check the transmitting
antenna.
a) If the resistance of the microstrip antenna is o.k., replace the following
parts in the order shown > 1. Tx module, 2. Receiver carrier, 3. rotating
data ring.
b) If the resistance of the microstrip antenna is not o.k. > replace the rotat-
ing Data Ring.
Tell HSC before replacing the Data Ring.
4 Additionally, do a Data Link test.
a) Check gantry error monitor in the Data Link test for errors reported by
UMAS: Link error.
b) Check for angle-dependent error distribution. If error is angle dependent
> replace the rotating data ring.
Tell HSC before replacing the Data Ring.
Step Action
1 Check indicators for sporadic errors:
a) Check for IRS warnings in the eventlog
b) Check error LED counter on Rec
For detailed instructions, Refer to (Step 1 (checking) / p. 117)
Datalink 117
Page 117 of 212
Step 1 (checking) 0
Check indicators for sporadic errors
a) Check for IRS warnings in the eventlog:
The IRS SW counts the data errors found in a scan and causes a warning message.
Check the logbook for IRS errors, only the CRC errors are significant for data transmis-
sion. Other types of errors detected by IRS, e.g. HV_DROP, are not related to data
transmission.
b) Check the event log for the number of missing readings. Helpful messages can be
found in the information message CT_ITX_ 2 and in the warning message CT_ITX_7.
Step 2 (debugging) 0
Debug for random transmission errors
a) check the data ring and the fiber-optic cables using the spare fiber-optic cable
- Disable gantry rotation
- Use the spare fiber-optic cable to connect the DCON outputs directly to the Rec
input.
- Do exactly the same (static) scan that is subject to sporadic errors with a normal con-
figuration. If the sporadic error continues, the problem is within DCON or IRS. Other-
wise, the debug procedure has to be refined.
The fiber-optic cables between DCON slip ring or between slip ring IRS can be
partially broken or have dirty ferrules in the connectors. Especially in the gantry, the
connectors can be contaminated by carbon dust from the slip ring brushes. In this
case, the signal at the fiber-optic cable output is lower than usual. However, the sig-
nal detect indicators may not trigger although the signal quality is poor. To isolate the
problem, measure the fiber-optic cable loss factors as described in the appendix and
replace the fiber-optic cable in case of higher losses. Alternatively, use the spare
2 Debug for random transmission errors:
a) Check the data ring and the fiber optic cables using the spare fiber-optic
cable.
b) Interchange the data ring channels
For detailed instructions, Refer to (Step 2 (debugging) / p. 117)
3 Localize the source of error:
a) Check for errors occurring in the DMS or IRS
b) Check for errors occurring at about the same gantry angle
c) Search for external interference as source of error
d) Search for dominant source of errors
For detailed instructions, Refer to (Step 3 (localizing) / p. 118)
Step Action
118 Datalink
Page 118 of 212
fiber-optic cable to successively patch the fiber-optic cable in question. If you get bet-
ter results (reduced number of transitory errors or no error at all), clean the ferrules or
replace the fiber.
b) interchange the data ring channels
The data path A uses same parts as data path B. For debugging, the A data can be sent
through the B path.
Interchange the fiber optic cables at the Tx modules and at the Rec to use the
other path.
Step 3 (localizing) 0
Localize the source of error
The Data Link Test automatically does a statistical analysis regarding error distribution.
Different histograms can be shown.
a) Check for errors occurring in the DMS or IRS
In case of a defective DCON or Rec, the data errors are apparently random and appar-
ently due to transmission. However, in reality the error occurs before transmission in
the DCON and after the transmission in the G-Rec. Select Bit Errors in the Data Link
Test (Data link test / p. 123) to get a histogram plot of the Bit error position within the
16-bit data word. If the errors always occur at the same Bit position(s) within the 16-bit
word, when repeating the data link test:
DCON or G-Rec defective, transmission across the Data Rings o.k.
Example for Bit Error histogram:
Fig. 54: Error bit position histogram
b) Check for errors occurring at about the same gantry angle:
Problems with the mechanical align of slip ring antennas can make sporadic errors.
Select both, Data Words Error and CRC Errors in the Data Link Test to show a histo-
gram plot of error distribution around the rotation. The Data Words Error analysis may
Datalink 119
Page 119 of 212
be slower but it does a check for every Bit error. The CRC Errors analysis does a check
only for block errors and is faster. The example below shows errors concentrated at the
same angular positions of the data ring.
Turn the gantry by hand to this angular position and check the structure for
defects and mechanical alignment. (0
o
is X-ray tube A at 3 oclock).
Example for relation between errors and rotation angle histogram:
Fig. 55: Histogram of error versus rotation angle
c) Search for external interference as source of error:
Sporadic errors in the data path may be caused by the following external factors:
- Noise caused by the frequency converter for rotation
- Noise caused by the HV Generator
- Mechanical asymmetries in the antenna system
- External equipment (e.g. therapy equipment, ovens,...)
120 Datalink
Page 120 of 212
Select both the Error Bursts and Error Free Intervals in the Data Link test to get two
histograms that plot the error distribution within the data stream (distribution of the error
burst length - EBL and error free interval - EFI).
The following 3 cases show typical histograms for different error sources:
Case 1
In this case both histograms have a Gauss (bell) shape. This suggests a periodic per-
turbation source such as the frequency inverter for gantry rotation or other power sup-
ply noise.
Check the high-power connections at the generator, the grounding connection,
and the high-power carbon brushes.
Do tests with the rotation driver disabled or without radiation to better identify the
perturbation source.
Fig. 56: Burst and EFI histogram case 1
Case 2
In this case only the burst histograms have a Gauss (bell) shape, whereas the EFI his-
togram decreases linearly. This suggests a non-periodic perturbation source such as
external equipment operated near the CT examination room that is generating power
line interference.
Check the quality of the hospital AC power cables (line transient spike analyzer)
and the grounding of the CT system as well as other hospital equipment operat-
ing nearby.
Datalink 121
Page 121 of 212
Case 3
In case burst histograms are concentrated and occur at very short burst lengths,
whereas the EFI histogram decreases linearly, this is suggestive of a defective sig-
nal-to-noise ratio at some fiber optic input or at the RF input for the Rx module.
Check the fiber-optic cables, clean the connectors, and align the receiver carrier.
d) search for dominant sources of error:
Each error source may contribute to the error budget, but only one is usually dominant.
The Data Link Test is a useful tool for finding the dominant source for errors. The RF
link across the data slip ring is subject to electromagnetic interference caused within the
gantry. Primary sources for this interference are the ring motor and its frequency
inverter as well as the high-voltage generator and power supplies on the rotating gan-
try. In order to identify the dominant source for errors, the debug strategy takes out one
or more potential sources. Accordingly, the data link test gives predefined test modes
that deal with this debug strategy. For example, to find the contribution of the X-ray gen-
erator to the error budget, do the data link test using scans without radiation.
Investigate the initial error statistics:
To get an idea about the initial error contour, do the data link test with patient-like
modes, i.e. modes that simulate a real scan. Use either topogram-like modes ("Static 0
deg, X-Ray" "Static 90 deg, X-Ray") or sequence-like modes ("Rot 0.33s, X-Ray"... "Rot
1.000s, X-Ray").
Try and identify if the errors are related to particular parameters such as rotation
speed, tube angle, etc......
Investigate the contribution of the rotation driver:
To find the contribution of the rotation driver to the error budget, do the data link test
with the predefined modes "Static X-Ray1" and "Static X-Ray2". These modes fully dis-
able rotation, including active braking. The frequency inverter is disabled through SW
and thus causes no interference at all. This is not equivalent to switching the rotation
OFF! These tests may be done only in the static mode. The gantry must be set either
through the local service platform or by hand to different angular tube positions or at
122 Datalink
Page 122 of 212
positions where previous tests showed an increased error probability. If the error statis-
tics change significantly as compared to previous tests, the dominant source for errors
is the rotation driver and investigations must be carried out accordingly.
Investigate the contribution of the X-ray generator:
To find the contribution of the X-ray generator to the error budget, do the data link test
with the predefined modes "Rot 0.33s" ... "Rot 1.000s". These modes disable X-ray
generation for different rotation speeds. Use the rotation speeds that previously
showed increased error probability. If the error statistics change significantly as com-
pared to previous tests, the dominant source for errors is the X-ray generator and inves-
tigations must be carried out accordingly.
Fine tuned investigation:
After having used the above steps, it may become obvious that other test mode(s) may
be more applicable to do a check-out a particular situation. In this case, edit the
user-defined test modes "Static20.dat" and "Rot20.dat" with or without X-ray to fit the
particular debug needs.
Datalink 123
Page 123 of 212
Tests for data transmission 4.3
Cleaning a fiber optic cable 0
The cable's performance may deteriorate because of dust or dirt covering the input core in
the cables receptacle.
Fig. 59: Cleaning optical connectors
Data link test 0
Scope
The data link test is a sequence of scan done automatically with the DMS configured to
cause test data (assignment mode). The data received are automatically analyzed in
the IRS/ICS for every incorrect Bit. Error statistics are generated that allow for locating
sources for error. If this test is successful, the transmission DMS to IRS works well.
The data link test may be done at different rotation speeds or without rotation (ROT or
STATIC modes) in the static mode with or without active braking of the gantry through
the rotation driver, with radiation at different levels of X-ray power or without X-ray.
How to find
Options > Service > Local Service > Test Tools > Sys.Communication > datalink
124 Datalink
Page 124 of 212
How to use
Do the data link test after a careful analysis of IRS logbook errors. Search for those
modes (rotation speed, X-ray power level, gantry tilt, etc.....) that are most prone to
transmission errors and test the datalink with these particular modes.
a) Press Select all, or select single modes, depending on the error pattern (e.g. rot.
speed, X-ray, etc......)
b) Press Go
c) Wait for the Press START key to come into view and then push the Start button.
If CRC errors or data errors are detected during the measurement, histogram
evaluations can be selected. The evaluations are only available in case errors
are detected (see next screenshot). For detailed data regarding the histogram
evaluations, refer to TSG sporadic errors in link DCON > IRS
Fig. 60: Data link test, possible histogram evaluations
The analysis SW will increment an error counter for each CRC error. The total number
of transmission errors is available and shown as test result. The error counter operates
over all readings into the scan that include at least five full rotations in order to find the
relationship between tube angle and error occurrence. In the case of an error counter
that is not zero, its time evolution can be plotted for all scans together with the tube
angle position as depicted below:
Datalink 125
Page 125 of 212
Fig. 61: Example of tube angle and error count versus frames
The X axis of the plot is the reading number. The vertical axis of Channel 2 (green plot) is
the number of errors. The vertical axis of Channel 1 (yellow plot) is the angular tube position
(0...360
o
C) as explained below.
Selectively check or uncheck the channel 1,2 checkboxes to change the vertical scale.
The gantry error monitor
The power, signal, and link errors reported by the Tx and Rx electronic modules in the slip
ring are monitored dynamically during the scan by the UMAR on the rotating gantry and by
the UMAS on the stationary gantry. These errors are the same debug signals that are indi-
cated by the green, yellow and orange LEDs available on both Rx and Tx modules. Both
UMAR and UMAS HW count the number of times these errors were activated during the
scan (error counter) as well as how long the errors were active during the scan (error time).
This feature is useful for identifying transitory errors that occur due to loose contacts
caused by mechanical vibrations during rotation that are otherwise not detectable.
Gantry angle
(deg)
0 30 60 90 120 150 180 210 240 270
Tube position
(x oclock)
from the front
3 4 5 6 7 8 9 10 11 12
Tube position
from the front
East
(right)
South
(bot-
tom)
West
(left)
North
(up)
126 Datalink
Page 126 of 212
Appendix 4.4
How check the transmitting antenna 0
The structures of the data rings can be measured with a digital multimeter. The figure below
shows how to measure the innermost rotating data ring. The structures can be measured
at the termination (see image below), and next to the transmitter shifted by 180 degrees
(same test points at opposite side of data ring). The results may be slightly different ~1
Ohm
1. Use a digital multimeter to measure the resistance at the following test points:
Fig. 62: Measurement Points
Measure between Nominal value
TP1 and TP3 92 Ohm +/- 1 Ohm
TP1 and Ground 51 Ohm +/- 0.5 Ohm
Datalink 127
Page 127 of 212
NOTE Measuring the resistance is important to find an interrupt or
short-circuit in the structure. The nominal values must serve
as a guideline. If the measured values are out of tolerance,
tell HSC before replacing the data ring.

Measuring the fiber optic signal along the link 0
The fiber-optic cable power at both outputs of DCON and at the fiber optic output of the slip
ring Rx module have to be high enough for reliable data transmission. The fiber-optic
receivers in the UMAR, slip ring Tx, and G-REC have built-in signal level detectors that
report an error when the signal falls below a safe minimum level. However, for error identi-
fication it is important to know if the problem is the incoming signal or the receiving part
itself. It may be possible that the power supplied via fiber optic cable to the input is high
enough, however, the fiber optic receptacle in the receiver module is covered with dust or
dirt, and the incoming light does not reach the destination. The fiber optic signal can be
measured at any point in the link using an optical power meter (e.g. the HP 8410A or HP
8153A). The power level of the fiber optic cable must be a minimum of -9 dBm avg. at 850
nm into a 62.5/125 MMF fiber optic cable.
The modulation signal (fiber optic cable extension ratio) can be optimally measured with an
oscilloscope and a fiber optic probe, e.g. Tektronix 6701B. The signal amplitude is typically
400W.
Note: A fiber optic cable installed in the gantry is difficult to measure with the above instru-
ments unless the cable is fully released from the gantry cable harness. To prevent this oper-
ation, you may use the spare fiber optic cable and the adapter to extend a cable end up to
the measuring instrument. Consider more loss in the spare cable to correct the last result.
Check the electrical RF signals at the Rx modules 0
The Rx modules receive RF signals through the capacitive coupling between the transmit-
ting rotating slip antenna and the stationary receiving segment antenna. The RF coupling
condition depends on the mechanical tolerances. The tests below have to be done by man-
ually rotating the gantry 360 degrees.
Turn the gantry by hand, check the status of the LEDs at the CUs for Tx and Rx modules.
Continue as described below.
Causes why signal detect LED for Rx module at CU is off:
Tx module defective (output)
Slip ring antenna system is defective or align is necessary
128 Datalink
Page 128 of 212
Rx module (input) is defective
Check the Tx module output:
Interchange the fiber optic inputs of the 2 stationary Rx modules and check if the status of
the signal LEDs for the Rx modules changes at the CU ROT. Additionally, replace the cor-
responding Tx module with a new one.
Check the slip ring antenna system:
Refer to How to check the transmitting antenna. For alignment instructions, refer to the
replacement of parts section, replacing the receiver carriers
Check the quality of data signal (jitter) at the REC input 0
Note: If the IRS is energized and the FPGA devices on the Rec are configured, the yellow
DL Ready LED is blinking. If not, troubleshoot the IRS.
1. Do the Data Link test with the Service Platform and check the CRC error sum and data
error sum counters.
2. Alternatively load a scan to start the Error indicators at G-REC. The green DL Data LED
must be on.
Errors are detected by the Recs, if the DL Error LED is on or blinking, and if the 8-Bit
error counter increments.
3. In case of transmission errors, refer to TSG permanent errors DAS controllers > IRS
Receiver.
Fastlink 129
Page 129 of 212
5- 5Fastlink
General 0
Safety 0
WARNING
Avoid accident and injury or damage to parts.
NOTE Follow the ESD guidelines when touching data transmission
parts.

Notes 0
This chapter contains data on how to troubleshoot the fastlink connections and the fastlink
paths.
NOTE All fastlink ports at the UMAR/UMAS and at the correspond-
ing connected components are compatible. By using a patch
cable, every port can be connected to any other port to do a
check of transmit and receive functions.
Every fastlink port has minimum 2 LEDs that show the
receive status. It is always important to do a check of the
LEDs at both components to find out if the problem is related
to a transmit problem of the first component, or a receive
problem of the other component.

The following Troubleshooting Guides (TSGs) are included in this chapter:
1. Direct fastlink connections in rotating part of gantry
All rotating components connected to the fastlink are connected through the UMAR
2. Direct fastlink connections in the stationary part of the gantry
All stationary components connected to the fastlink are connected through the UMAS
3. Transmission path UMAS to UMAR
Data transmission between UMAS and UMAR is done through the stationary transmitter,
the stationary data ring, and the rotating receiver assembly.
4. Transmission path UMAR to UMAS
Data transmission between UMAR and UMAS is done through the rotating transmitter, the
rotating data ring, and the stationary receiver assembly.
130 Fastlink
Page 130 of 212
Tx module> Transmitter electronics module
Rx module > Receiver electronics module
CU STAT> Central unit stationary
CU ROT> Central Unit rotating
Prerequisites 0
For a quick check of the signal link, a spare fiber optic cable and a fiber optic coupler
are necessary. A short and long fiber optic cable are supplied with every system.
Use these fiber optic cables to patch a certain segment of the data path in order to isolate
the problem.
NOTE At the Tx and Rx modules, simplex fiber optic connections
are used. Components to and from UMAR/UMAS use duplex
connections.
The supplied spare fiber optic cables are duplex connec-
tions. To use these cables for simplex connections, separate
the cables at the connector.

The image below shows one of the supplied spare fiber optic cables with its connectors
separated for simplex use.
Fig. 63: Spare fiber optic cable with coupler
Pos. 1 spare fiber optic cable
Pos. 2 coupler
Pos. 3 fiber optic connectors, separated for simplex connections
Fastlink 131
Page 131 of 212
TSG Fastlink 5.1
Depending on the error message, select the corresponding TSG.
NOTE Start troubleshooting always by doing a check the LEDs at
the Central Units and at the connected components while
rotating the gantry by hand.

Information:
On every TX and RX module installed in the system there is a green LED, which shows
that the TX-/RX module is on. The LED will blink. The following image shows the location
of the LED at rotating TX-/RX modules.
Fig. 64: RX and TX modules
Pos. 1 LED at RX module ROT
Pos. 2 LED at TX modules ROT
Doing a quick check of the Fastlink:
The fastlink test within the Service Platform is a quick check for the fastlink path.
Select: Local Service>Sys.Communication>Fastlink
This test has to pass without any errors determined by the counters.
If errors are found with this test, refer to TSG for the fastlink connections in this section.
Using the ping command:
The connection from the host to the UMAS (Ethernet) has the IP address: 192.168.184.4
The connection from the host to the UMAR (Ethernet+Fastlink) has the IP address:
192.168.184.132
132 Fastlink
Page 132 of 212
NOTE There are 2 Central Units CU (one stationary and one rotat-
ing) which include all necessary LEDs. The Tx and Rx mod-
ules are supplied with power by the Central Units. The
following images will help you identify the components of the
signal link.

TSG rotating fastlink connections 0
The following explains the rotating fastlink connections and the LEDs which are useful error
indicators.
1. Central Unit ROT
The following components are connected to the Central Unit ROT:
- Tx Module ROT Data Path A
- Tx Module ROT Data Path B
- Tx Module ROT Signal Link
- RX module ROT Signal Link
Fig. 65: Central Unit ROT
Pos. 1 Central Unit ROT
Pos. 5 RX Module ROT Signal Link
2. Rx module ROT
The Rx module ROT is used for the Signal Link from STAT to ROT.
Fastlink 133
Page 133 of 212
NOTE The Rx module ROT is connected to the CU ROT. The Rx
module cannot be interchanged for troubleshooting. In con-
dition of a defective Rx module, replace the full unit (Rx mod-
ule including carrier).
Look at the LEDs on the CU if troubleshooting the RX mod-
ule.

Fig. 66: Rx Module ROT
Pos. 1 RX module ROT
134 Fastlink
Page 134 of 212
3. Tx modules ROT
The following image shows the Tx modules rot, one Tx module for Data Path A and one
for data path B and one Tx module for the Signal Link.
Fig. 67: TX Modules ROT
LEDs on UMAR
1. NoSD: On if no optical signal or signal with low amplitude is detected
2. Error: On , if Sync or CRC error detected
LEDs on XDC
1. NO SIG: On if no optical signal or signal with low amplitude is detected
2. Error: On if Sync or CRC error detected
LEDs on tube collimator
1. FL Sig: On if no optical signal or signal with low amplitude is detected
2. FL Err: On if Sync or CRC error detected
LEDs on left backplane DMS
1. COM_BUS: Green if a correct fastlink protocol is received.
Red if fastlink protocol is not correct.
Fastlink 135
Page 135 of 212
Tab. 48 TSG rotating fastlink connections
TSG stationary fastlink connections 0
The following figure shows the stationary fastlink connections and the LEDs which are use-
ful error indicators.
1. Central Unit STAT
The following components are connected to the Central Unit STAT:
Step Action
1 Check the red NoSD and Error LED at the UMAR and at the connected com-
ponent (e.g. tube collimator, XDC).
a) If one or both LEDs (Error and NoSD) are on or blinking at UMAR
or/and at the connected component > clean the fiber optic cable. Refer
to Cleaning a fiber optic cable. If LEDs stay on, continue with step 2.
2 Switch off and on the gantry at the control box.
a) If LEDs are still on or blinking, continue with step 3.
3 Check the UMAR by interchanging the connectors.
a) Interchange the fastlink connector at the UMAR with the neighboring
one. If the error moves to the neighboring slot, > UMAR o.k., the fiber
optic cable or the connected component is defective. Interchange the
connectors to their original positions and continue with step 4.
b) If the error does not move to the other slot, > UMAR defective.
4 Check the connection using a spare fiber optic cable.
a) Connect the corresponding slot of the UMAR to the connected compo-
nent with the spare fiber optic cable. If LEDs stay on > replace the con-
nected component.
Before replacing the component, connect the component to any other
fastlink port with the spare fiber optic cable, and check the LEDs to vali-
date the defect.
b) if LEDs are off at this time > cable between UMAR and component
defective.
136 Fastlink
Page 136 of 212
- RX module STAT Data Path A
- RX module STAT Data Path B
- RX module STAT Signal Link
- Tx Module STAT Signal Link
Fig. 68: Central Unit STAT
Pos. 1 Central Unit STAT
Pos. 3 RX Module STAT Data Path B
Pos. 5 TX Module STAT Signal Link
2. RX Unit STAT2 for Data Path A + Signal Link
Fastlink 137
Page 137 of 212
NOTE The Rx unit STAT2 consists of two Rx modules: the Rx mod-
ule for datalink A and the Rx module for the signal link. These
two modules cannot be interchanged for troubleshooting.
For troubleshooting functions, interchange the fiber optic
cables at the Rx modules and do a check of the LEDs at the
central unit STAT. Always replace the full RX UNIT STAT2 in

Pos. 1 RX Unit STAT2
3. Rx Unit STAT1 (datalink B)
The RX Unit STAT1 consists of the RX module STAT for Data Path B.
NOTE The RX Unit STAT1 consists of one RX module. The Rx mod-
ule for Datalink B. This module cannot be interchanged for
troubleshooting. Always replace the full Rx UNIT STAT1 in

Pos. 1 RX Unit STAT1 Data Path B
138 Fastlink
Page 138 of 212
4. Tx module STAT
The Tx module STAT is used for the Signal Link from STAT to ROT.
NOTE The Tx module STAT is connected to the CU STAT.

Fig. 71: TX Module STAT
Pos. 1 TX Module Stat (fastlink)
LEDs on UMAS
1. NoSD: On if no optical signal or signal with low amplitude is detected
LEDs on XGS in PDC (D703)
1. Light Err: On if no optical signal or signal with low amplitude is detected
2. Link Err: On , if Sync or CRC error detected
LEDs on PHS (LMAS)
1. Transceiver Signal detect: On if no optical signal or signal with low amplitude is
detected
2. Receive Error: On , if Sync or CRC error detected
LEDs for fastlink on Receiver(s) in IRS
1. Yellow Ready: is not in use
2. Red Error: is not in use
3. Green Data: is not in use
4. Red No Sync: on , if sync error is detected.
5. Red No Signal: On if no optical signal or signal with low amplitude is detected
6. Red CRC Error: on unless correct CRC is detected.
NOTE The Error, No Sync, No Signal and CRC LEDs are also
switched on in case of sporadic errors for 100ms. Check
these LEDs while rotating the data ring by hand.

Fastlink 139
Page 139 of 212
Tab. 49 TSG stationary fastlink connections
TSG for connection UMAS > UMAR 0
NOTE To find angle-dependent problems, turn the gantry by hand
and check the error LED at UMAR. If the LED is on for spec-
ified angular positions, check the data ring first.

The following explains the LEDs which are useful error indicators.
LEDs on CU STAT for stationary Tx module:
1. Power: Off if power to the Tx module is missing.
2. Signal: Off if no signal or signal with low amplitude is detected
3. Sync: Off or decreased intensity (blinking) if Sync or CRC error is detected
LEDs on CU ROT for rotating Rx module:
3. Sync: Off or decreased intensity if Sync or CRC error is detected.
Step Action
1 Check the red NoSD and Error LED at the UMAS and at the connected com-
ponent.
a) If one or both LEDs (Error and NoSD) are on or blinking at UMAS
or/and at the connected component > clean the fiber optic cable. Refer
to Cleaning a fiber optic cable. If LEDs stays on, continue with step 2.
2 Switch off and on the gantry at the control box.
a) If LEDs stay on or blinking, continue with step 3.
3 Check the UMAS by interchanging connectors.
a) interchange the fastlink connector at the UMAS with the neighboring one.
If the error moves to the other slot, > UMAS o.k., the fiber optic cable or
the connected component is defective. Interchange the connectors to
their original positions and continue with step 4.
b) If the error does not move to the other slot, > UMAS defective
4 Check the connection using a spare fiber optic cable.
a) Connect the corresponding slot of the UMAS to the connected compo-
nent with the spare fiber optic cable. if LEDs stay on > Replace the
connected component.
Before replacing the component, connect it to any other fastlink port with
the spare fiber optic cable, and check the LEDs to validate the defect.
b) if LEDs are off at this time > cable between UMAS and component
defective
140 Fastlink
Page 140 of 212
LEDs on UMAR
1. NoSD: On if no signal or signal with low amplitude is detected
Tab. 50 TSG fastlink path UMAS to UMAR
Step Action
1 Check all fastlink indicators (LEDs) in the path UMAS>UMAR.
a) if one or more LEDs in the path are not in the idle state, continue with
step 3.
b) if all LEDs are idle, continue with step 2.
2 Check output of UMAS by establishing a direct connection between UMAS
and UMAR with a spare fiber optic cable.
a) If Red NoSD and Error LED at UMAR are on > UMAS defective.
Before replacing the UMAS, connect UMAS to any other fastlink port with
b) if Red NoSD and Error LED at UMAR are off > UMAS and UMAR o.k.
Establish the original connection and continue with step 3.
3 Check power for stationary Tx module at CU STAT.
a) If the green LED at CU STAT is off, > Tx module is defective or power
from UMAS is missing. Check the power path.
4 Check the signal for the stationary Tx module at CU STAT.
a) If the yellow LED is off at CU STAT, > missing signal from UMAS or bro-
ken/dirty fiber optic cable connection, or Tx module is defective. Clean
the fiber optic cable. Refer to Cleaning a fiber optic cable. If yellow LED
stays off, > connect the UMAS and Tx module with the spare fiber optic
cable. If the problem is not related to the cable, establish the original con-
nection.
b) If the orange sync LED at CU STAT is on , but with decreased bright-
ness > check the quality of the signal. Refer to TSG data quality at Tx
modules.
c) If all LEDs are on, continue with step 5.
5 Check the power for the Rx module at CU ROT.
a) If the green LED at CU ROT is off, > Rx module is defective or power
from UMAR is missing. Troubleshoot the power path first.
Fastlink 141
Page 141 of 212
TSG for connection UMAR > UMAS 0
NOTE The UMAR>UMAS path uses the middle structure of the rotat-
ing data ring. To isolate the data ring, the outer or inner struc-
ture (DMS A/B path) can be used temporarily. Use the Tx
module and Rx module of the DMS data path, and temporarily
establish fastlink connections to do a check of the data ring
(use the spare fiber optic cables).

LEDs on CU ROT for rotating Tx module:
3. Sync: Off or decrease intensity (blinking) if Sync or CRC error is detected
LEDs on CU STAT for stationary Rx module:
6 Check signal for the Rx module at CU ROT.
a) if the yellow LED at CU ROT is off,> missing signal from transmitter, or
stationary data ring defective, or rotating receiver carrier is defective.
b) if the orange sync LED at the CU ROT is on, but with decreased bright-
ness > check the quality of the signal. Refer to "TSG data quality at Rx
modules"
7 Check the stationary data ring
a) Measure the resistance of the stationary data ring. Refer to How to
check the transmitting antenna.. If resistance not o.k., replace the data
ring.
Tell HSC before replacing the data ring.
b) Adjust the rotating receiver carrier. If the error stays, continue with step 8.
8 Check the connection from Rx to UMAR.
a) If the red LEDs at the UMAR are on > missing signal from Rx module,
or broken/dirty fiber optic connection, or UMAR is defective. Clean the
fiber optic cable. Refer to Cleaning a fiber optic cable. If the LEDs stay
on, establish the original connection and continue with step 9.
9 Use the spare fiber optic cable between Rx module and UMAR.
a) If red LEDs at UMAR stay on > Rx module or UMAR defective. Continue
with step 10.
b) If the error LED is off at this time > Replace the fiber optic cable.
Step Action
142 Fastlink
Page 142 of 212
3. Sync: Off or decreased intensity if Sync or CRC error is detected.
LEDs on UMAS
1. NoSD: On if no signal or signal with low amplitude is detected
2. Error: On , if Sync or CRC error is detected
Tab. 51 TSG fastlink path from UMAR to UMAS
Step Action
1 Check all fastlink indicators (LEDs) in the path UMAR>UMAS
a) if one or more LEDs in the path are not in the idle state, continue with
step 3.
b) If all LEDs are idle, continue with step 2.
2 Check the output of UMAR by establishing a direct connection between
UMAR and UMAS with a spare fiber optic cable.
a) If Red NoSD and error LED at UMAS are on > UMAR defective.
Before replacing the UMAS, connect UMAS to any other fastlink port with
b) If Red NoSD and Error LED at UMAR are off > UMAS and UMAR o.k.
Establish the original connection and continue with step 3.
3 Check the power at the CU ROT for the rotating Tx module.
a) If the green LED at CU ROT is off, > Tx module is defective or power
from UMAR is missing. Check the power path.
4 Check signal for the Tx module at CU ROT.
a) If the yellow LED is off at CU ROT, > missing signal from UMAR, or bro-
ken/dirty fiber optic cable connection, or Tx module is defective. Clean
the fiber optic cable. Refer to Cleaning a fiber optic cable. If yellow LED
stays off, connect the UMAR and the Tx module with the spare fiber
optic cable. If the problem is not related to the cable, establish the original
connection and continue with step 5.
b) if the orange Sync LED at CU ROT is on, but with decreased brightness
> check quality of signal. Refer to TSG data quality at Tx modules.
5 Check the power for the Rx module at the CU STAT.
a) if the green LED at CU STAT is off > Rx module is defective or the power
from UMAS is missing. Troubleshoot the power path.
Fastlink 143
Page 143 of 212
TSG data quality at Tx modules 0
Two Tx modules are used for fastlink data transmission: one stationary Tx module for the
uplink to the rotating part, and one rotating Tx module for the downlink from the rotating to
the stationary part. Before starting troubleshooting for data quality, do the TSG for the
fastlink connections first.
6 Check signal for the Rx module at CU STAT.
a) if the yellow LED at CU STAT is off > missing signal from transmitter, or
rotating data ring is defective, or stationary receiver carrier is defective.
b) if the orange Sync LED at CU STAT is on, but with decreased bright-
ness > check quality of signal. Refer to "TSG data quality at Rx modules"
7 Check the rotating data ring (fastlink path). Refer to How to check the trans-
mitting antenna" and readjust the stationary receiver carrier.
a) Measure the resistance of the rotating data ring (fastlink uses the outer-
most structure). If resistance not o.k. > replace the data ring.
b) Adjust the stationary receiver carrier. If the error stays, continue with step
8.
8 Check the connection from stationary Rx module to UMAS.
a) If the red error LEDs at UMAS are on > missing signal from Rx module,
or broken/dirty fiber optic connection, or UMAS is defective. Clean the
fiber optic cable. Refer to Cleaning a fiber optic cable. If the LEDs at
UMAS stay on, establish the original connection and continue with step
9.
9 Use a spare fiber optic cable between stationary Rx module and UMAS.
a) If the red LEDs at UMAS stay on > Rx module or UMAS is defective.
b) If the LEDs are off at this time > Replace the fiber optic cable.
Step Action
144 Fastlink
Page 144 of 212
Tab. 52 TSG data quality at Tx modules
TSG data quality at Rx modules 0
First make sure that the quality of the data signal at the Tx module is OK (see above). When
plugging the fiber optic cable into the Tx module, there must be a noticeable increase in
light intensity at the orange Sync LED on both the Tx and Rx modules. This condition can
change at different gantry angular positions.
Step Action
1 Unplug and plug in the fiber optic cables at the Tx module.
a) if the sync LED at corresponding CU shows decreased intensity (e.g. due
to blinking at a high rate) > UMAR/UMAS output broken, or broken/dirty
fiber optic connection from UMAR/UMAS, or Tx module is broken. Clean
the fiber optic cable. Refer to Cleaning a fiber optic cable. If the LED still
shows decreased intensity, continue with step 2.
2 Check the UMAR/UMAS output using a spare fiber optic cable.
a) Connect UMAR/UMAS to the corresponding Tx with the spare fiber optic
cable. If the orange LED is o.k. at this time > replace the fiber optic
cable between UMAR/UMAS and the Tx module.
b) if the orange LED at corresponding CU still shows decreased light inten-
sity (with spare cable installed), > UMAR/UMAS or Tx module defective.
3 Check the UMAR/UMAS output using the indicator on any other Tx module.
a) Connect UMAR/UMAS to any other TX module within the system, using
the spare fiber optic cable. If the sync LED at the temporarily used Tx
module also shows decreased intensity > replace UMAR/UMAS.
b) If the sync LED at the CU of the temporarily used Tx module shows a
noticeable increase in light intensity> replace the corresponding Tx
module.
Fastlink 145
Page 145 of 212
Tab. 53 TSG
Tests for data transmission 0
Cleaning a fiber optic cable
The cable's performance can degrade because of dust or dirt covering the input core in the
cables receptacle.
Step Action
1 Unplug and plug in the fiber optic cables at the corresponding Tx module.
a) if the sync LED for the Rx module shows decreased intensity (e.g. due to
blinking at a high rate) at the corresponding CU > Tx module (output) bro-
ken, or a broken data ring, or a broken Rx module, or the receiver carrier
is defective. Continue with step 2.
2 Check the RX modules.
a) Interchange the corresponding Rx module with any other Rx module
(e.g. spare module) and do a check of the sync LED at the CU. If the error
moved to the temporarily used Rx module, > replace the Rx module.
b) if the orange LED at the corresponding CU still shows decreased light
intensity, put the modules back as they orignally were and continue with
step 3.
3 Check the data ring. Refer to How to check the transmitting antenna, and
readjust the receiver carrier (refer to the replacement of parts section).
a) If resistance of the microstrip antenna is o.k., replace the parts in the fol-
lowing order, after adjusting the receiver carrier > 1. Tx module, 2.
receiver carrier, 3. rotating data ring.
b) If the resistance of the microstrip antenna is not o.k. > replace the rotat-
ing Data Ring.
146 Fastlink
Page 146 of 212
Fig. 72: Cleaning optical connectors
How to check the transmitting antenna
The structures of the data rings can be measured with a digital multimeter. The figure below
shows how to measure the innermost rotating data ring. The structures can be measured
at the termination (see image below), and next to the transmitter shifted by 180 degrees
(same test points at opposite side of data ring). The results can be slightly different ~1 Ohm
Fastlink 147
Page 147 of 212
1. Use a digital multimeter to measure the resistance at the following test points:
Fig. 73: Measurement Points
NOTE Measuring the resistance is important to find an interrupt or
short-circuit in the structure. The nominal values shall serve
as a guideline. If the measured values are out of tolerance,
tell HSC before replacing the data ring.

Measuring the fiber optic signal along the link
The fiber optic cable power at the fiber optic output of the slip ring Rx module has to be high
enough for reliable data transmission. The fiber optic receivers in the UMAR, slip ring Tx/Rx
modules, and UMAS have built-in signal level detectors that report an error when the signal
falls below a safe minimum level. However, for error identification it is important to know if
Measure between Nominal value
148 Fastlink
Page 148 of 212
the problem is the incoming signal or the receiving part itself. It may be possible that the
power supplied through fiber optic cable to the input is high enough, however, the fiber optic
receptacle in the receiver module is covered with dust or dirt, and the incoming light does
not reach the destination. The fiber optic signal can be measured at any point in the link
using an optical power meter (e.g. the HP 8410A or HP 8153A). The power level of the fiber
optic cable must be a minimum of -9 dBm avg. at 850 nm into a 62.5/125 MMF fiber optic
cable.
The modulation signal (fiber optic cable extension ratio) can be optimally measured with an
oscilloscope and a fiber optic probe, e.g. Tektronix 6701B. The signal amplitude is typically
400W.
Note: A fiber optic cable installed in the gantry is difficult to measure with the above men-
tioned instruments unless the cable is fully released from the gantry cable harness. To pre-
vent this operation, you can use the supplied spare fiber optic cable and the adapter to
extend a cable end up to the measuring instrument. Consider more loss in the spare cable
to correct the last result.
CAN Bus 149
Page 149 of 212
6- 6CAN Bus
CAN Bus 0
NOTE The CAN tests (Test Tools / Sys. Communication) are not reli-
able for troubleshooting the CAN bus.

CAN bus rotating part
The UMAS is the master controller for the CAN bus of the rotating part. The CAN bus con-
sists of a closed loop which is routed through certain rotating components. The terminal
resistor of the CAN bus has a value of 120 ohm and is located inside of the UMAR. The 2
wires of the loop are named CAN_L and CAN_H. The CAN bus wires CAN_L and CAN_H
are routed from the UMAS via the rear slip ring (2 tracks) to the UMAR. At the UMAR, the
CAN bus wires are routed through XGR A/B, XDC A/B and the PDR.
Because the CAN bus is a hard-wired loop connection (refer to figure), the resistance of
the loop can be measured using a multimeter. The resistance at plug X401 on cable W399
between pin 2 and 10 must be 120 +30/-10 ohm. Also check that the 2 CAN wires
(CAN_l/CAN_H) are insulated from ground. All affected CAN bus components are indi-
cated in the figure below.
Data transfer UMAS to UMAR via CAN slip ring 0
Fig. 74: CAN Bus
Pos. 1 Image only for reference, not updated when functional description is changed. For details please see functional
description.
150 CAN Bus
Page 150 of 212
Data transfer UMAS to UMAR via Fast Link (function pack 1: CAN over IP) 0
Fig. 75: Data transfer UMAS to UMAR via Fast Link
NOTE As of September 2010, systems will be delivered with VA27
software function pack 1: CAN over IP.
Activation of the CAN over IP via Fast Link requires the
dummy plugs (120 ohms) on UMAS (X401) and on UMAR
(X305).
Description of function pack 1:
During the INIT phase of UMAS and UMAR, the system
checks the data transfer via the CAN slip ring. If data transfer
via the CAN slip ring is not possible, the system is switched
to the CAN over IP mode (Fast Link connection).

CAN Bus 151
Page 151 of 212
Fig. 76: UMAS
Pos. 1 X401: Dummy plug (120 ohms)
Fig. 77: UMAR
Pos. 1 X305: Dummy plug (120 ohms)
152 CAN Bus
Page 152 of 212
TSG CAN bus (rotating part) 0
Tab. 54 CAN bus troubleshooting
Step Action
1 Switch system off and press service switch S1 in PDC-A to switch off gantry
power completely.
2 Data transfer UMAS to UMAR via Fast Link (CAN over IP):
Disconnect the dummy plugs (120 ohms) from UMAS (X401) and UMAR
(X305). Measure the internal resistance of the dummy plugs between pin 2
and pin 10. The measured resistance value must be 120 +30/-10 ohms.
Measure the resistance at the dummy plugs (120 ohms) from pin 2 and pin
10 against system ground. The resistance value must be > 10 kohms.
Data transfer UMAS to UMAR via CAN slip ring:
Remove plug X401 from UMAS. Measure the resistance at plug X401 on
cable W 399 between pin 2 and pin 10.
a) If the measured resistance value is 120 +30/-10 ohm -> wiring from plug
X401 cable W399 to the 120 ohm bus terminator inside of the UMAR is
ok -> continue with item 3.
b) If the resistance value is not 120 +30/-10 ohm -> continue with item 4.
3 (Skip this step if data transfer UMAS to UMAR is performed via Fast Link.)
Measure the resistance at plug X401 on cable W 399 from pin 2 and pin 10
against system ground.
a) If the resistance value is > 10 Kohm -> insulation on CAN_H and CAN_L
wires against system ground is ok -> no further action necessary.
b) If the resistance value is about 0 ohm -> insulation for CAN_H and
CAN_L against system ground is not ok (short circuit to ground) -> con-
tinue with item 5.
CAN Bus 153
Page 153 of 212
TSG CAN bus to XGS 0
CAN bus to XGS
The UMAS is the master controller for the CAN bus to the XGS. The CAN bus consists of
a closed loop which is routed through XGS-A in PDC-A and XGS-B in PDC-B. The terminal
resistor of the CAN bus has a value of 120 ohm and is located inside a dongle. The dongle
is plugged in at XGS-B X3. The 2 wires of the loop are named CAN_L and CAN_H. The
CAN bus wires CAN_L and CAN_H are routed from the UMAS to XGS-A and XGS-B.
Because the CAN bus is a hardwired loop connection (see drawing below) the resistance
of the loop can be measured using a multimeter. The resistance at plug X400 on the UMAS
4 Remove plug X305 from UMAR. Measure the resistance at plug X305 on the
UMAR between pin 2 and pin 10 .
a) If the resistance value is 120 +30/-10 ohm -> CAN bus connection
between plug X305 on cable W550 and plug X401 on cable W399 has a
problem.
-> check wiring from plug X305 on cable W550 to plug X1 on the slip ring
pin 2/10 for bad contact or broken wires.
-> check wiring from plug X401 cable W399 to plug X2 on slip ring pin
2/10 for bad contact or broken wires.
-> If above cable wiring is ok -> the problem is at the back slip ring (mea-
sure the continuity between plugs X1 and X2 pin 2/10 on the slip ring ,
check/change defective brushes....).
b) If the resistance value is not 120 +30/-10 ohm -> remove plugs X302,
X303, X307, X301, and X300 in sequence. At each of these plugs on the
UMAR, measure the resistance between pin 4 and 11 until 120 +30/-10
ohm can be measured.
-> If 120 +30/-10 ohm can be measured -> the CAN bus problem is
between the last plug measured and the previously measured plug ->
find by ohm measurement which part is defective and change the defec-
tive part.
5 Remove plug X305 from UMAR. Measure the resistance at plug X401 on
cable W399 pin 2/10 against system ground.
a) If the insulation problem still exists -> the insulation problem is between
plug X305 on cable W550 and plug X401 on cable W399. Remove parts
located between above mentioned plugs in sequence to find the insula-
tion problem.
b) If the insulation problem no longer exists -> the problem is somewhere in
the rotating part between UMAR and the connected components. Isolate
the problem by measuring at plug X305 pin 2/10 on UMAR to system
ground while removing plug X300, X301, X307 X303, and X302 in
sequence.
Step Action
154 CAN Bus
Page 154 of 212
between pin 2 and 10 must be 120 +30/-10 ohm. Also check that the 2 CAN wires
(CAN_l/CAN_H) are insulated from ground. All affected CAN bus components are indi-
cated in the figure below.
CAN Bus 155
Page 155 of 212
Tab. 55 CAN bus troubleshooting
Step Action
1 Switch system off and switch off system power using the onsite off/on switch
(power of XGS-A/B is switched off).
2 Remove plug X400 from UMAS. Measure the resistance at plug X400 on
cable W55 between pin 2 and pin 10.
a) If the measured resistance value is 120 +30/-10 ohm -> wiring from plug
X400 on cable W55 to the 120 ohm bus terminal at X3 on XGS B is ok
-> continue with item 3.
3 Measure the resistance at plug X400 on cable W55 from pin 2 and pin 10
against system ground.
a) If the resistance is > 10 Kohm -> insulation of CAN_H and CAN_L wires
against system ground is ok -> no further action necessary.
b) If the resistance is about 0 ohm -> insulation of CAN_H and CAN_L
against system ground is not ok (short circuit to ground) -> continue
with item 8.
4 Remove plug X4 from XGS-A. Measure the resistance at plug X4 on XGS-A
between pin 2 and pin 10.
a) If the resistance value is 120 +30/-10 ohm -> CAN bus connection
between plug X4 and X400 on cable W55 has a problem.
-> check cable W55 for bad contact or broken wires.
5 Remove plug X3 from XGS-A. Measure the resistance at plug X3 on the
cable W54 between pin 2 and pin 10.
a) If the resistance value is 120 +30/-10 ohm -> check plugs X3 /X4 on
XGS-A for bad contacts; otherwise, change XGS-A.
6 Remove plug X4 from XGS-B. Measure the resistance at plug X4 on XGS-B
between pin 2 and pin 10.
a) If the resistance is 120 +30/-10 ohm -> check cable W54 for bad contact
or broken wire; otherwise, change cable W54.
b) If the resistance is not 120 +30/-10 ohm -> continue with item 7.
156 CAN Bus
Page 156 of 212
7 Remove plug X3 (including the 120 ohm bus terminal) from XGS-B and mea-
sure the resistance at plug X3 (dongle) between pin 2 and pin 10.
a) If the resistance value is 120 +30/-10 ohm -> check plugs X3/X4 on
XGS-B for bad contacts; otherwise, change XGS-B.
b) If the resistance value is not 120 +30/-10 ohm > change dongle plug X3.
8 Remove plug X3 from XGS-A. Measure the resistance at plug X3 on cable
W54 pin 2/10 against system ground.
a) If the insulation problem still exists -> the insulation problem is between
plug X3 on cable W54 , XGS-B and dongle plug X3 on XGS-B. Remove
listed parts in sequence to isolate the insulation problem.
b) If the insulation problem no longer exists -> the insulation problem is
between plug X400 on the cable W55 and plug X3 on XGS-A. Remove
listed parts in sequence to isolate the insulation problem.
Step Action
CANopen Bus 157
Page 157 of 212
7- 7CANopen Bus
CANopen Bus 0
TSG CAN open bus 0
The UMAS is the master controller for the CANopen bus. The CANopen bus consists of a
closed loop which is routed through certain components (refer to diagram). The terminal
resistors of the CANopen bus have a value of 120 ohms and are located inside the SCR
and the PHS.
In addition, the control box is connected via a repeater (part of the UMAS board) to the
CANopen bus. Therefore, the control box contains a 120 ohm terminal resistor as well.
NOTE The CANopen bus can be checked by measuring the resis-
tance of the CANopen circuit.

Fig. 78: CAN open bus
description.
158 CANopen Bus
Page 158 of 212
Tab. 56 Sequence to measure the CANopen loop resistance:
Tab. 57 Pin list for CANopen bus
Step Action
1 Switch off the system and press the service switch S1 in PDC A to switch off
gantry power.
2 Remove one of the CANopen circuit connectors.
For troubleshooting, it is recommended to remove a CANopen circuit con-
nector located in the middle between the two terminal resistors (refer to step
18 of the CANopen pin list).
Measure the resistance in both directions from the CANopen circuit. Plug
located at the component and the plug located at the cable.
3 Measure the CANopen loop resistance between the CANopen_H pin and
the CANopen_L pin (refer to the CANopen pin list).
The resistance between the CANopen_H pin and the CANopen_L pin
must be 120 +30/-10 ohm.
4 Measure the ground resistance of the CANopen_H pin and the CANopen_L
pin against system ground.
Note: The CANopen circuit must be isolated against system ground.
The ground resistance must be greater than 10 Kohm.
5 If the measurement values (in both directions) are in tolerance, the CAN-
open circuit is o.k.
If a measurement value is out of tolerance, remove the next CANopen
connector in the direction where the measurement value is out of tolerance.
Repeat the measurements from step 4 and step 5.
Step Component Connector CANopen_H
pin
CANopen_L
pin
Remark
1 SCR X5 7 2 120 ohm
2 WCS X4 1 2
3 WCS X3 1 2
4 UMAS X472 1 2
5 UMAS X404 15 2
6 X308 15 2
7 PRR X1 15 2
8 PRR X2 15 2
9 PRL X1 15 2
10 PRL X2 15 2
11 MV45 X1 15 2
CANopen Bus 159
Page 159 of 212
12 MV45 X1 16 4
13 PRL X2 16 4
14 PRL X1 16 4
15 PRR X2 16 4
16 PRR X1 16 4
17 X308 16 4
18 UMAS X404 16 4
17 UMAS X403 15 2
18 X307 15 2
19 PFR X1 15 2
20 PFR X2 15 2
21 DF X1 15 2
22 DF X2 15 2
23 PFL X1 15 2
24 PFL X2 15 2
25 MV45 X1 15 2
26 MV45 X1 16 4
27 PFL X2 16 4
28 PFL X1 16 4
29 DF X2 16 4
30 DF X1 16 4
31 PFR X2 16 4
32 PFR X1 16 4
33 X307 16 4
34 UMAS X403 16 4
35 UMAS X471 1 2
36 PHS X702 7 2 120 ohm
CANopen bus repeater (part of the UMAS board)
37 UMAS X402 10 2
38 Control Box X1 10 2 120 ohm
Step Component Connector CANopen_H
pin
CANopen_L
pin
Remark
160 CANopen Bus
Page 160 of 212
CAN open external bus 0
NOTE The CAN open external bus can be measured in the same way
as the CAN open bus.
The wire list of the pin connection (e.g. W58) can be opened
in the function description.

Fig. 79: CAN open external
description.
Stop report loop 161
Page 161 of 212
8- 8Stop report loop
Stop report loop 0
The stop report loop is a safety mechanism. All controllers are immediately put in into the
Stop state when one of them opens the loop or if the loop is opened at any point. The oper-
ator can also open the loop by pushing one of the red STOP buttons. When the loop
opens, radiation and motion stop and all table drive button lights go out. SOMARIS soft-
ware on the ICS prompts the operator to Please click CONTINUE. If no error exists when
Continue is clicked, the stand-by state is reached again.
The loop is a hard-wired series circuit with a number of contacts (relays and switches). Sup-
plied with 24 V, DC (30 mA) via relays K8 and K6 on the UMAS. Relay K6 (Stop Hold) on
the return side is energized as long as power is available at the UMAS. The stop report loop
is first closed during Startup or reset (Continue) by firmware closing K7, which supplies K8
coil, for 100 ms. If all the stop-report contacts (controller relays and STOP buttons) are
closed during this time, K8 stays energized by its self-holding contact (normal operating
state). The firmware on all the controllers also contains a Startup routine that closes their
individual stop-report relays for the same time.
Opening any of the stop-report contacts disconnects the return path of the coil of K8 to
ground, removing power from K8 coil. K8 then holds the loop open until a Reset (Continue)
is issued from the ICS via the UMAS firmware. Whenever the loop opens, all the controller's
firmware goes into the Stop state until the Reset command arrives at the controllers (Con-
tinue). The loop is multiplexed into the fastlink communication as it goes over the slip ring.
Fig. 80: Definition Flash stop report loop
description.
162 Stop report loop
Page 162 of 212
NOTE ADAPTERS ARE REQUIRED TO TROUBLESHOOT (see Note
below). For sporadic problems, an oscilloscope is also
required.

TSG stop report loop 0
First, make sure the loop is open. (Other problems can cause Continues or keep the
table drive buttons from lighting up.) Look at the SR Closed yellow LED on the UMAS - it
is OFF if the loop is open. Try Setup/Continue and a cold system restart. If the loop is per-
manently open, troubleshoot according to the following process.
1. PERMANENTLY open stop report loop: This method is described in the following
TSG. First, order the material numbers below, or obtain breakout boxes (see NOTEs
below). The test adapter is inserted into the loop at each UMAS/UMAR connector in
sequence. A bridge on the adapter simulates a closed loop on that component. If the stop
report loop is closed (system reaches stand-by state) after power on (because of the
bridged test adapter). The problem is on the component where you installed the test
adapter. If the stop report loop still does not close, the particular component behind the test
adapter is OK. Therefore the adapter is then moved to the next location.
NOTE To troubleshoot the stop report loop, the following SUB-D
test adapter plugs are needed (male and female) . You can
order the following adapters from stock:
99 00 101 -- 15 pin Sub-D plugs M/F
99 00 127 -- 25 pin Sub-D plugs M/F
46 83 314 --- 9 pin Sub-D plugs M/F
If the above adapters are not available, Breakout Boxes can
be used as a substitute (local source). Make sure that you
obtain the types that allow individual pins on the connectors
to be bridged/jumpered.
If you use a BoB, you may also need up to 6 pln gen-
der-changers. 2 each for 9-, 15-, and 25-pin SUB-D connec-
tors (1 male/male and 1 female/female each), to adapt to the
plug polarities.

Page 163 of 212
Fig. 81: Example of Breakout Box (BoB) with Leads to Bridge/Jumper Pins
Fig. 82: UMAS showing Stop Report Connections
NOTE Extreme care must be taken that ONLY the correct pins are
bridged, as described in the text below. Bridging the incor-
rect pins risks serious damage to the hardware when power
is applied!

Page 164 of 212
NOTE Switch off the UMAS power (with fuse F303 in right gantry
stand). When you install and remove a test adapter at the
UMAS.
Use the Control Box Computer On button when working at
the UMAR.
Failure to do so can risk serious damage to the hardware!

Tab. 58 Stop report troubleshooting for SOLID problem
Step SOLID PROBLEM -- Actions
Follow the below given test steps
A Check Eventlog for fastlink problems between UMAR and UMAS (MAR/MAS
error messages).
If there are fastlink problems > follow Troubleshooting Guide given in the error
message.
If there no fastlink problems > continue with step B.
Page 165 of 212
B Install the test adapters between the following connectors at the UMAS or
UMAR. Bridge the pins at the test adapter as described below to simulate a
closed loop at the adapter location. Note: Do not forget to connect the
removed plug to the test adapter.
1. UMAS X403 (loop pin1 to pin 14 on the test adapter). If the stop report loop
is closed after switch on > problem in front cover stop report loop > con-
tinue with step C.
If the stop report loop is NOT closed after power-on > continue with item 2.
is closed after switch on > problem in the control box stop report loop >
continue with item D.
If the stop report loop is NOT closed after power-on > continue with item 3.
3. UMAS X404 (check if the stop report loop at rotating part is closed by mea-
surement). Install SUB_D test adapter between X404 connector. Close ser-
vice switch S8 on UMAS: K8 contact is bypassed, and 24 VDV (30 mA) is
supplied to the stop report loop.
Measure if approx. 18 V, DC can be measured at pin 1 of the Sub-D plug.
- if approx. 18 V, DC can be measured > stop report loop of rotating part is
closed > continue with item 4.
- if approx. 0V can be measured > stop report loop of rotating part is not
closed > continue with item 7.
is closed after switch on > problem in rear cover stop report loop > con-
tinue with item E.
If the stop report loop is NOT closed after power-on > continue with next
step..
5. UMAS X400 (loop pin 1 to pin 9 on the test adapter). If the stop report loop
is closed after power-on > problem in XGS A or B stop report loop path
> continue with next step
6. XGS A X3 (loop pin1 to pin 9 on the test adapter). If the stop report loop is
closed after switch on > problem in XGS B
If the stop report loop is not closed after switch on > problem in XGS A
7. UMAR X302 (loop pin 1 to pin 9 on the test adapter). If the stop report loop
is closed after power-on > problem in XGR A stop report loop.
If the stop report loop is not closed after switch on > continue with next step..
is closed after power-on > problem in XDC A stop report loop.
is closed after power-on > problem in XGR B stop report loop.
If the stop report loop is not closed after switch on > continue with next step..
is closed after power-on > problem in XDC B stop report loop.
Page 166 of 212
C Remove UMAS X403 (to panels, display, MV45, wiring). Measure the resis-
tance of the stop report loop.
a) Measure the resistance from pin 1 to 14 (0 ohm) and
between ground and pins 1 and 14 (> 10 kohms).
D Remove UMAS X402 (to panels, display, MV45, wiring). Measure the resis-
E Remove UMAS X404 (to optional panels, MV45, wiring). Measure the resis-
The rear control panels (MV45) are optional. If they are not
installed, a different cable connects the gantry to the MV45.
Network 167
Page 167 of 212
9- 9Network
Network 0
Ethernet switches (located in PDC_A) 0
Fig. 83: Location of Ethernet switches within PDC
Pos. 1 External switch
Pos. 2 Internal switch
Fig. 84: LEDs and connections of Ethernet switch
168 Network
Page 168 of 212
Tab. 59 Description of LEDs SysKonnect switch from January 2007
Name Color Status Description
Power Green Off
On
Power off
Power on
SPD/LNK/ACT
Yellow
Yellow
Green
Green
Off
On
Blinking
On
Blinking
No link established
1GBit/s link established, no data has been trans-
ferred
1GBit/s link established and data has been trans-
ferred
10 or 100 MBit/s link established, no data has
been
transferred
10 or 100 MBit/s link established and data has
been
transferred
FDX/HDX
Green
Off
On
Operation in half-duplex mode
Operation in full-duplex mode
Network 169
Page 169 of 212
Troubleshooting network components 0
Overview
Fig. 85: Network components
170 Network
Page 170 of 212
IP addresses of internal components
Troubleshooting the ICS - IRS connection
Test the network connection with Service SW in Somaris/7
1. Select Local Service > Test Tools > IRS > HW Test > network
2. Click Go to start the test
3. If the message IRS HW test failed" appears, check the event log for further infor-
mation.
Troubleshooting network components with the help of Local HW Tests
Component IP address
ICS 192.168.184.1
IRS 192.168.184.2
GSV (UMAS) 192.168.184.4
PDC (UPS) 192.168.184.10
KVMoverIP 192.168.184.12
Step Action
1 Start the Local HW Test.
2 Click Config within the Local Hardware Test window to open the Config-
uration settings.
Fig. 86: Configuration settings
3 Deselect Enable to modify the IP addresses.
Network 171
Page 171 of 212
4 Enter the IP address of the tested component in the Destination IP field and
the transfer rate in the min MByte/sec field.
Fig. 87: Setting IP addresses
5 Click Apply and close the window.
6 In the Local Hardware Test window, select Network and click Start.
7 Check for errors in the Message window.
8 In case of an error, check the affected Ethernet path as follows:
a) Check the LEDs on the transmitting or receiving component and the Eth-
ernet switch within the PDC_A.
b) Check the Ethernet switch by using a different port.
Step Action
172 Rotating controller
Page 172 of 212
10- 10Rotating controller
Rotating controller tests 0
DOM 0
The DOM (Dose Modulation) function is an FW part located on the UMAR. With this test,
the function of the Dose Modulation Control on UMAR is tested. During the test, a self test
of the DOM controller is performed via the test interface.
DOM TSG
Tab. 60 DOM test
Performing the DOM test
1. Select Local Service > Test Tools > Rot. Controller > DOM
2. Select relevant tests.
COC (Tube collimator) 0
Tube collimator test function
The COC test is divided in 4 different test possibilities
1. PHI - Z - monitor Signal test - (only lab)
2. PHI - Z - monitor Signal test - (only lab)
3. Collimator Init test - performs an Init run of the collimator jaws. Additionally, the
encoder offset values of the two jaws are shown and written into the COC table of the
ICS. Repetitions can be selected to detect sporadic problems.
4. Test of movable radiation filters - the tests move the different filters to their in/out end
position. The out/in positions are indicated by 2 LEDs located at the TCO front cover.
Repetitions can be selected to detect sporadic problems.
The above tests can also be used if the gantry has not reached standby status. For trou-
bleshooting, use the Troubleshooting Guide below.
Step Action
1 Perform the DOM test as described below.
2 If the test fails > check/reload FW > Local service > Control > Firmware update.
3 If the test fails again, change UMAR.
Rotating controller 173
Page 173 of 212
Tube collimator TSG
Tab. 61 Tube collimator TSG
Performing the COC test
1. Select Local Service > Test Tools > Rot. Controller > COC
2. Select relevant tests.
Step Action
1 Perform COC test: Local Service > Test Tools > Rot. Controller > COC.
Select the following tests
Collimator test A/B
Cardio Wedge filter test A/B
Body Wedge filter test
Tin filter test
a) Check to see whether the collimator jaws are moving.
b) Check to see whether the position LEDs of the wedge/tin filters are alternately
switching on/off when the in/out end position is reached:
TCO A/B: Cardio wedge filter LED -> F1 POS 1 or F1 POS 2.
TCO A: Body wedge filter LED -> F2 POS 1 or F2 POS 2 or TCO B: Tin
filter LED -> F2 POS 1 or F2 POS 2.
- if the above conditions are fulfilled > all COC test results are successful -> TCO
is OK.
- if the TCO jaws are not moving or seem to move incorrectly -> continue with
item 2.
- if TCO wedge or tin filter LEDs are not alternately switching on/off -> continue
with item 3.
2 Perform COC test A or B > 5 times.
Compare the 5 jaw 1 values.
If the difference between several encoder offset values is 3 or smaller ->
TCO is OK.
If the difference of the jaw 1 value is 4 or 5 > repeat COC test > if the
difference does not change and COC error messages are found in the
Eventlog > replace TCO A or B
If the difference of the jaw 1 value is more than 5 > replace TCO A or B
Compare the 5 jaw 2 values and follow the same conditions as with jaw 1.
3 Select some repetitions in the COC filter test and check the Eventlog for error
messages (supply power, ....) which appeared during the filter test.
If error messages are found > continue troubleshooting as described in the
extended error message.
174 Stationary controller
Page 174 of 212
11- 11Stationary controller
Stationary controller tests 0
The system has to be in the standby mode to perform the following controller tests.
Prerequisites 0
n.a.
Master stationary (MAS) test 0
1. Select Local Service > Test Tools > stat.Controller > MAS
2. Select one or all MAS tests.
3. Click Go.
Fig. 88: MAS Test
- Footswitch test: Tests the function of the footswitch
- Speed test for cooling fan: The fan rotation speed can be set from 0% to 100%.
This test can be used to determine noise at a certain fan rotation speed.
- Open stop report: This test has the same function as S8 on the UMAS.
- Close stop report: This test has the same function as S8 on the UMAS.
Stationary controller 175
Page 175 of 212
Gantry panel control (GPC) test 0
1. Select Local Service > Test Tools > stat.Controller > GPC.
2. Select one or all GPC tests.
3. Click Go.
Fig. 89: GPC Test
Rotation control (ROT) test 0
1. Select Local Service > Test Tools > stat.Controller > ROT.
2. Select one or all ROT tests.
Page 176 of 212
3. Click Go.
Fig. 90: ROT Test
Patient Handling System (PHS) test 0
1. Select Local Service > Test Tools > stat.Controller > PHS.
2. Select one or all PHS tests.
Stationary controller 177
Page 177 of 212
3. Click Go.
Fig. 91: PHS Test
CPI (PMM) test 0
1. Select Local Service > Test Tools > stat.Controller > CPI.
2. Select PMM test.
Page 178 of 212
3. Click Go.
Fig. 92: CPI Test
System test 179
Page 179 of 212
12- 12System test
System test 0
DOM functional 0
The IEC 30 cm water phantom is used for the dose modulation test. After the phantom is
positioned correctly, 2 measurements are performed. The first measurement is performed
without dose modulation, the second with dose modulation. After each measurement the
effective mAs-product is read from the generator table (control table). The images are
reconstructed and displayed. After reconstruction, a ROI is positioned in each image and
the noise is retrieved. A computation regarding the noise and mAs-product of both images
determines whether the dose modulation works correctly or not. If tube arcing occurred,
the test is not valid and must be repeated.
Function The DAS controller generates a DOM data frame for use in dose modulation func-
tions. A DOM frame is a compressed version of any IRS reading sent to UMAR via Fastlink.
The UMAR builds an angular attenuation profile used to modulate on-line the dose profile
(Dose) applied to the patient. From the dose profile, the filament data are calculated and
sent via Fastlink to the XGR (FilPower). Most of the DOM function in UMAR is software.
Remark: Test requires the system to be in stand-by status.
DOM functional TSG
Tab. 62 DOM functional TSG
Performing the test
1. Select Local Service > Test Tools > Sys Tests > DOM Functional
2. Select relevant parameters.
If a test fails, follow the TSG described next.
Step Action
1 Perform the Dom functional test 5 times.
> if the test is out of tolerance at least 3 times > continue with item 2.
> if the test is not out of tolerance at least 3 times > no action necessary
2 Perform the DOM test Local Service > Test Tools > Rot. Controller > DOM
> if the DOM test is out of tolerance > change UMAR
> if the DOM test is ok > continue with item 3.
3 Check image quality from normal scans without the selected DOM function.
> if the image quality is ok > UMAR <-> DMS communication ok > continue with
item 4.
> if the image is not ok > troubleshoot fastlink communication UMAR > DMS .
4 Troubleshoot fastlink communication UMAR > XGR .
180 System test
Page 180 of 212
X-ray timeout test 0
This test checks if the scan is switched off after 108% scan time. Normally a scan is
switched on/off only from the XC (X-ray release) signal, which is sent at the beginning of
the scan from UMAR to XGS/XGR. For safety reasons, a timer in XGS/XGR is started as
soon as the radiation is switched on (> 20 kV) triggered from the XC signal. If the XC signal
is not switched off before the internal XGS/XGR timer exceeds its 108% limit, the scan is
switched off by the internal timer. If the test fails at CT_GSA/GRA_113 (XGR Scan Time
Exceeded) is sent to the Eventlog.
Remark: Test requires the system to be in stand-by status.
X-ray timeout TSG
Tab. 63 X-ray timeout TSG
Performing the test
1. Select Local Service > Test Tools > Sys Tests > XRay Timeout
2. Select relevant parameters.
If a test fails, follow the TSG described next.
Dyn. Collimation 0
In short spirals, a significant fraction of the dose is normally applied during the overscan
phases at the beginning and end of the scan. A dynamic shutter can drastically reduce this
overscan dose. Effective dynamic shutter requires collimator plates each capable of fully
closing the aperture and moving at considerable speed. The only way to prove that the
blades are moving correctly in time is to measure the dose length product. With this test,
the correct function of the dynamic collimation is checked so that the raw data are checked
for expected values after a spiral scan. If the expected values are within tolerance, it is an
indication that the dynamic collimation is functioning (blades of TCO are moving correctly).
If not, troubleshooting has to start as described below.
Remark: Test requires the system to be in stand-by status
Step Action
1 Check the Eventlog for the CT_GSA/GRA_113 error message. Follow the
instructions given in the extended error message.
System test 181
Page 181 of 212
Dyn. Collimation TSG
Tab. 64 X-ray timeout TSG
Performing the test
1. Select Local Service > Test Tools > Sys Tests > Dyn Collimation
2. Select parameters (RotSpeed, pitch, table movement, granularity use default)
Step Action
1 Perform Dyn. Collimation test (see below) > perform 1 test with minimum and 1
test with a maximum of parameters (granularity > use default). The test result is
displayed in a table which is shown after the end of the test.
> if the test is not successful (one or more red bars) > save raw data file (E:ser-
vice/icsraw > DynCol.raw) onto CD and send it to HSC. HSC forwards it to the
lab > continue with item 2.
> if the test is successful (grey or green bars) > dynamic collimation is ok. No
further action.
2 Follow the TCO Troubleshooting Guide > (COC (Tube collimator) / p. 172)
182 Cooling System
Page 182 of 212
13- 13Cooling System
Water cooling 0
General 0
The water cooling system provides heat dissipation for the gantry electronics and X-ray
tube. The 3-way bypass valve on the incoming cold water and the variable-speed fan reg-
ulate the internal air temperature of the gantry. Both are controlled from the Electronics Box
containing control boards and connected to sensors for the water and air. The Electronics
Box connects to the system by the CANopen bus. The fan assembly contains its own Fan
Motor Control Board which connects to the Electronics Box. The fan in the lower-right gan-
try stand cools all rotating parts; there are no other fans in the rotating gantry.
A condensate-collection system collects condensed water below the radiator and automat-
ically pumps it away to a drain. The condensate pump connects electrically to the electron-
ics box.
If the temperature in the gantry or the temperature of the incoming water exceeds limits,
the Electronic Box issues messages to the UMAS.
For sites using the Water-Air Split Cooling Unit, an interface to it is provided on the elec-
tronics box (X6).
The following diagrams are from the Function Description.
Cooling System 183
Page 183 of 212
Fig. 93: Water cooling overview
184 Cooling System
Page 184 of 212
Fig. 94: Water circuit
Cooling System 185
Page 185 of 212
Fig. 95: Electrical circuit
TSG Water Cooling 0
General troubleshooting process steps:
1. If possible, try to determine if the problem is EXTERNAL or INTERNAL to the gantry.
Check the eventlog. Current Cooling State shown in Table T00, and LEDs on the Elec-
tronics Box. If the problem appears to be external, seek possible resolution in Hospi-
tal/Facility-Chilled Water System or with Split Air/Water Unit (Option). Continue to
evaluate the internal gantry conditions if the external ones are verified as OK or cannot
be determined immediately.
2. If the problem is INTERNAL to the gantry, look at the eventlog. Current Cooling State
shown in Table T00, observe the LEDs on the Electronics Box. Use the laptop service
connection to the Electronics Box described below.
3. Replace suspected defective parts.
Information sources
The following sources of information about the source for cooling problems are available:
186 Cooling System
Page 186 of 212
1. Messages in the eventlog:
Review the eventlog for warning and error messages from the WCS, and troubleshoot
based on these errors. You can filter the eventlog on the text COOLING to see only cool-
ing errors.
If you cannot access the eventlog for any reason, you can connect a service lap-
top directly to the Cooling Electronics Box (# 4 below).
The following 2 INFORMATION messages in the eventlog are useful to determine possible
changes in the cooling conditions. Even if there are no warning or error messages.
NOTE These messages are INFORMATION-priority. Switch on the
INFO messages to display them in the eventlog.
Also, they are only generated when a certain amount of
change has occurred. For a readout of the current state of
these values, see Step 2, Table T00 shown below.

Message about the ENVIRONMENT/PRIMARY SIDE:
Cooling System 187
Page 187 of 212
Fig. 96: Message MAS220
Message about the COOLING SECONDARY (GANTRY) SIDE:
Fig. 97: Message MAS212
To determine what value is being displayed, look at the P1 value in the actual message
shown in the eventlog. Find this HEX number on the list of Parameter 1: Supervision ID
numbers in the expanded message (above). P3 & P4 show the actual value in HEX.
NOTE It is necessary to convert HEX to decimal to read the value.
Use the Windows Calculator in the Scientific mode (WinXP
Programs > Accessories > Calculator > View > Scientific).
Click HEX button to enter the values of P3 and P4, then press
DEC button. Remember that temperature values are given in
1/10th degree (e.g., 247 = 24.7 degrees C).

188 Cooling System
Page 188 of 212
2. Current system cooling status using table T00:
Using the Service Software function Control > Table Load/Modify, open table T00 from
Volatile. The current state of the various sensors is shown in the data fields of T00. Com-
pare the current state to the nominal values shown in the following screenshot to determine
if the actual values displayed reveal any strong deviations.
NOTE DO NOT change the values in any of the tables!

Fig. 98: T00 table for water cooling
Cooling System 189
Page 189 of 212
3. LEDs on WCS electronics box:
The 3 LEDs at the left side of the Electronics Box are status indicators. In the normal mode
of operation, only the green LED (H1) flash. The yellow LED (H2) is illuminated if a warning
(e.g. temperature out of tolerance) occurs. And also briefly lights whenever the control
board is switched on (initialization). During an error condition (e.g., fan error), the red LED
(H3) is on continuously.
4. Additional information: Laptop service connection to electronics box
NOTE All messages mentioned below are sent to the Eventlog.
Use the laptop connection only if you are familiar with a ter-
minal emulator program.

Note: All messages mentioned below are also sent to the Eventlog. Use the Laptop con-
nection only if you are familiar with a terminal emulator program.
Connect the laptop PC serial port to the Service connector. On the Electronics Box with a
null-modem cable and running a terminal emulator program such as HyperTerminal.
Example:
>sta
>UpTm: 54:46 C:1 E:0 LE:250 I/Yf:6000/290 LA:200 I/Ym:0/0 Pos:0WE:
100 WA:150 FS:584
The number after the letter E: indicates the warning or error message code.
E:0 indicates no warning or error.
Warning Alarms (YELLOW LED on Electronics Box illuminated):
190 Cooling System
Page 190 of 212
Error Alarms (RED LED on electronics box illuminated):
Code Warning messages via the laptop
10 /
110
Cooling unit exhaust air temperature (into gantry) to low
Control valve - electrical connection is faulty - Check wiring connection at
valve.
Control Valve is not working - Try turning the valve knob manually, see if it
responds by returning to its original position. If so, probably OK (repeat
several times). If it does not return to its original position, replace valve drive
unit, electronics box, sensors, valve.
11 /
111
Exhaust air temperature of cooling unit (into gantry) is too high
Same cause/action as code 10 above.
20 /
120
Hospital supply water temperature is too low (<4 degrees C)
Look for a thermometer on the hospital incoming water lines and verify that
the coolant is 4-12 degrees C. Contact hospital facility engineers if out of
range. If the hospital water supply is OK, check/replace sensor for incoming
water temperature.
21 /
121
Hospital supply water temperature is too high (greater 12 degrees C)
Look for a thermometer on the hospital incoming water lines and verify that
the coolant is 4-12 degrees C. Contact hospital facility engineers if out of
range. Check if the hospital water is filtered, and if so, check if the water filter
is clogged (briefly open bypass valve). If the hospital water supply is OK,
check sensors for the hospital water temperature and flow. Shut off incoming
water valve (red handle 90 degrees) and monitoring the sensors with Table
Load/Modify of Table T00: temperature and flow indications respond.
30 /
130
Gantry temperature is too low (< 22 degrees C).
Gantry temperature regulation is not working properly. Replace: control
valve drive / control valve, electronics box, sensors.
31 /
131
Gantry temperature is too high (>30 degrees C).
Gantry temperature regulation is not working properly. Verify the sensor con-
nection (if not connected, this error results). Replace: control valve drive /
control valve, electronics box, sensor, fan (if not blowing).
Cooling System 191
Page 191 of 212
Code Warning messages via the laptop
210 Error in fan controller
Fan connection to the electronics box is not connected. Check the electrical
connection between fan and Electronics Box (connectors 1X1 and 1X2).
Fan bearing has seized. Check that the fan rotor turns easily - DISCON-
NECT FAN POWER before touching the fan blades.
Controller or fan has failed - replace fan assembly.
220 Spirit level in condensate pan is too high
Check spirit level in condensate pan, function of the condensate pump and
switch, and make sure that the clear hoses are OK. Verify the electrical con-
nection of condensate pump to Electronics Box (connector 1X3).
230 Fan speed too low
Check connection between electronics box and fan (connectors 1X1 and
1X2). Replace Electronics Box, fan assembly.
1010 /
1011
Sensor R1 error: exhaust air temperature to gantry
Check/replace sensor R1, connector 2X4.
1020 /
1021
Sensor R2 error: air inlet temperature from gantry
1050 /
1051
Sensor R3 error: water outlet temperature or flow
Verify the proper temperature and adequate flow of incoming hospital water.
1060 /
1061
Sensor R4 error: water inlet temperature
Verify the proper temperature of incoming hospital water. Check/replace
sensor R4, connector 2X4.
192 PDC_A cabinet
Page 192 of 212
14- 14PDC_A cabinet
General overview 0
The PDC can be divided into 3 separate functions:
Power distribution located in the lower part of the PDC
XGS located in the upper part of the PDC
UPS located at the lower right (standard component in the PDC)
The PDC cabinet is always delivered with the power matching transformer T1:
Transformer T1 adapts the on-site line voltage (380 V to 480 V) to internal 400 V.
Fig. 99: PDC cabinet - overview
Pos. 1 Schematic overview
Pos. 2 Detailed overview
PDC_A cabinet 193
Page 193 of 212
Power distribution 14.1
The power distribution in the PDC cabinet distributes the line voltage power at the required
adapted voltages to all system components and their subsystems.
Errors and troubleshooting hints 0
As a result, an error in the power distribution can generate various errors at different system
components. Refer to the following table for actions based on the type of error.
Tab. 65 Table of possible errors and hints
Error Cause Action
Complete
system
does not
come up
(UPS may
supply
power to
ICS/IES/IR
S for ~30
minutes)
F1 tripped Switch ON circuit breaker F1 and monitor its function.
If F1 does not trip again:
RCD F18 (yellow box) detected >50% leakage
current once.
- Check for unstable facility incoming power
- Check on-site cabling
- Check cabling in PDC
- Check cabling from the PDC to the subsystems
- See also (Residual current monitor F18 / p. 199)
If F1 trips again:
RCD F18 (yellow box) detects >50% leakage cur-
rent continuously.
- Check ALARM LED (yellow) at F18 (LED does
not blink, only goes ON for a short time).
- Check for unstable facility incoming power
- Check on-site cabling.
- Check cabling in PDC
- Check cabling to sub-systems
Relay K2 is faulty (T1 temperature sensing)
- Check LED on K2 while switching ON F1
T1 transformer temperature is too high, holding
K2 off (T1 Temp switch or wiring open).
Overcurrent between F1 and T1, e.g. faulty isola-
tion, short circuit at connection terminal T1.
F20 tripped 24-V power supply U1 is faulty; see (24 Volt power supply
for U1 / p. 204) for more information.
194 PDC_A cabinet
Page 194 of 212
No function
in individ-
ual system
compo-
nents
Circuit breaker
for the compo-
nent is tripped
Switch ON the circuit breaker for the system component
and monitor its function. If the circuit breaker trips again,
the power input of the component is defective. Trouble-
shoot the component.
Relay for the
component is
not switching
on
Check where the supply voltage of the relay comes
from (in the Function Description) and determine what
circuit breakers or other relays supply it.
ICS, IES,
IRS, UMAS
not coming
on
UPS not com-
ing on
Check if the UPS power switch is on (LEDs on front of
UPS).
Check F10 (UPS Input) and F16 (UPS Output).
Check whether the circuit breakers at the back of the
UPS have tripped; see (Fig. 110 / p. 207).
See (UPS / p. 206) for more information.
LEDs OFF
at all pro-
tection
devices
(Pos. 8 in
(Fig. 100 /
p. 195)
F12 tripped Switch ON circuit breaker F12 and monitor its function:
If F12 does not trip again
Test function of F18 with the TEST switch.
Check LEDs of K1, K2, K12, F18.
If F12 trips again
Check cabling and components that are con-
nected to K1, K2, K12, F18, shunt trips at certain
circuit breakers.
Error Cause Action
PDC_A cabinet 195
Page 195 of 212
Overview 0
Fig. 100: Power distribution in PDC_A - overview
Pos. 1 Fuses F1, F2, F4, F5, F6, F3 (from left to right)
Pos. 3 Relays K24, K23, K22, K21, K20, K19, K18, K17, K16, K15, K14, K11, K7, K6, K5 (from left to right)
Pos. 4 Relays K25, K10, K9, K8, K3 (from left to right)
Pos. 5 24 Volt power supply for U1
Pos. 6 Fuses F7, F8, F9, F10, F11, F12, F13, F14, F15, F16, F17, F20, F21, F22 (from left to right)
Pos. 7 Overvoltage protection
Pos. 8 Residual current monitor F18; relays K2, K1
Pos. 9 Line voltage terminal for on-site power cable
Pos. 10 Service power socket X140, X141; power sockets X108, X109 for Ethernet switches
Pos. 11 Transformer T1
Pos. 12 UPS incl. accumulator pack (behind cover)
Pos. 13 External Ethernet switch
Pos. 14 Internal Ethernet switch
Circuit breakers and relays 0
Refer to (Fig. 101 / p. 198) for the locations of the circuit breakers and protection
devices.
Refer to (Fig. 102 / p. 199) for the location of the relays.
196 PDC_A cabinet
Page 196 of 212
Refer to (Fig. 100 / p. 195) for a general overview of the location of the circuit breakers
and relays.
Notes
Check by measuring the voltage at the connection point of every component/ subcom-
ponent to see whether:
- The component/ sub-component does not work.
- The supply voltage for a certain component / subcomponent is missing.
- A corresponding error message is generated.
The following table shows the circuit breakers, relays, and connection points required to
switch ON/OFF and to protect some system components independently:
Tab. 66 Circuit breakers and relays - primary
Tab. 67 Circuit breakers and relays - secondary
Connected load Circuit breaker via relay Connection /check point
Entire PDC F1
1
, F18
2
1. Line voltage circuit breaker
2. Only active if F12 (secondary) is ON
n.a. Pin 2/4/6 of F1
XGS F2 n.a. Pin 1/3/5
Connected load Circuit breaker via relay Connection /check point
All sub-systems
/components
F4 n.a. Pin 1/3/5
UPS input F10 n.a. X108, Pin A1, A2 (N)
Patient table PHS F7 K7 X101, Pin 1, 2 (N)
Cooling unit
1
1. Integrated in gantry
F3 K11 X103, Pin A1, A2, A3, B1 (N)
Gantry, stationary
part
F6 n.a. X100, Pin A1, A2, A3, B1 (N)
2
2. Note: Pin B3 is still under voltage via the UPS although F6 has tripped or is switched OFF
Gantry, rotating part F5 K8
3
, K9 /K10
4
3. Switches permanent power for rotating part of the gantry
X102, Pin A1, A2, A3, B1 (N)
Service socket
5
(230 V, AC)
F9 n.a. X140, L1/N
X141, L1/N
REPO contact F20 K3 X20, Pin 5.1/5.2
Service socket
6
(230 V, AC)
F21 K5 X111, Pin 1/2 (N)
PDC_A cabinet 197
Page 197 of 212
Tab. 68 Circuit breakers and relays - components supplied by the UPS
4. Charge circuit for rotating generator
5. Type: Schuko
6. Type: Schuko
Connected component Circuit breaker via relay Connection /check
point
All components
(connected to the UPS)
F16 n.a. X109, Pin A1, A2
Ethernet power socket_1
1
1. Type: Schuko
F11 K3 X106, Pin L1/N
Ethernet power socket_2
2
2. Type: Schuko
F17, F14 K3, K5 X107, Pin L1/N
ICS F17, F13 K3, K5 X104, Pin 1/2
IES F17, F14 K3, K5 X110, Pin 1/2
IRS F17, F15 K3, K6 X105, Pin A1, A2
UMAS F11 K3 X100, Pin B3, B1
Power supply XGS F11 K3 X003, Pin 2/3/4 (PE)
Power supply 15/24 V for
XGS_Control
F22 K3 X159, L/N
(shutter receptacle)
198 PDC_A cabinet
Page 198 of 212
Fig. 101: Circuit breakers and protection devices in PDC - locations
Pos. F1 (circuit breaker)
Pos. S1 (service push-button)
Pos. Designation from left to right: F7/F8/F9/F10/F11/F12/F13/F14/F15/F16/F17/F20/F21/F22 (circuit breakers)
Pos. F19 (varistors and overvoltage protection)
Pos. F18 (residual current monitor)
Pos. K2 (coupling relay)
Pos. K1 (time relay)
PDC_A cabinet 199
Page 199 of 212
Fig. 102: Relays in PDC - locations
Pos. 1 Relays K24/K23/K22/K21/K20/K19/K18/K17/K16/K15/K14 (from left to right)
Pos. 2 K11
Pos. 3 K7
Pos. 4 K6
Pos. 5 K5
Pos. 6 K25
Pos. 7 K10
Pos. 8 K9
Pos. 9 K8
Pos. 10 K3
Residual current monitor F18 0
F18 is a residual current monitor. It monitors the 3 input phases of the system via T2 (cur-
rent transformer) for symmetry. The resulting current of the 3 phases and the correspond-
ing neutral (to and from the system) must be zero.
If the resulting current exceeds a certain value, the power supply is switched OFF via
the current circuit breaker F1.
A warning is generated if 50% of the error current is present for at least 2 sec.
Refer to (Fig. 103 / p. 200) for illustration of F18.
Refer to (Fig. 100 / p. 195) for a general overview of the location of F18.
200 PDC_A cabinet
Page 200 of 212
Tab. 69 Residual current monitor F18
Fig. 103: Residual current monitor F18
Pos. 1 TEST button
Pos. 2 LED ON (green)
Pos. 3 LED ALARM (yellow)
Pos. 4 RESET button
Service pushbutton S1 0
Refer to (Fig. 100 / p. 195) for a general overview of the location of S1.
Refer to (Fig. 104 / p. 201) for the illustration of S1.
The PDC has a service push button S1 that switches OFF the following circuit breakers
remotely:
F6/ F11 (stationary part of the gantry; including UMAS)
F5 (rotating part of the gantry)
F2 (stationary generator XGS)
F3 (cooling unit)
Indicator Status Function
LED ON ON Monitor in operation.
LED ALARM BLINKING Leakage current is 50%.
OFF Leakage current is < 50%.
Test switch PUSHED Generates a leakage current into T2 and must switch
OFF circuit breaker F1 immediately.
Reset switch PUSHED ALARM LED can be reset with the RESET switch to
check if the error is reproducible.
PDC_A cabinet 201
Page 201 of 212
F7 (patient table)
- F7 enables (F1 must be switched ON) and allows the patient table to be used as a lift-
ing device while replacing components of the rotating gantry. Collision protection is
disabled!
NOTE When switched OFF via the S1 push button, manually switch
on each of the above-mentioned circuit breakers in the PDC.

Fig. 104: Service push-button S1
Pos. 2 Push-button
WARNING
Use of the service-enable switch (table) disables collision
protection.
Be careful when moving the table.
Relays K1, K2 0
Refer to (Fig. 100 / p. 195) for a general overview of the location of K1 /K2.
Refer to (Fig. 105 / p. 202) for the illustration of K1 /K2.
202 PDC_A cabinet
Page 202 of 212
Tab. 70 LEDs of K1, K2 - normal operational status
Fig. 105: Relays K1/K2 - Status LED
Pos. 1 Coupling relay K2
Pos. 2 Time relay K1
Pos. 3 Status LED
Line voltage circuit breaker test 0
Refer to (Fig. 106 / p. 203) for the illustration of F1.
Refer to (Fig. 100 / p. 195) for a general overview of the location of F1.
Refer to (Fig. 105 / p. 202) for the illustration of K1 /K2.
The following test description contains a general test of the
Line voltage circuit breaker
Leakage current
LED Green Yellow Yellow Function
K1 n.a. OFF OFF Time delay relay
K2 n.a. ON n.a. Relay
PDC_A cabinet 203
Page 203 of 212
Test description:
1. Switch on the power using the on-site ON/OFF switch.
Make sure all computers (ICS, IRS, and IES) are switched OFF.
Make sure F12 is switched ON; otherwise, line voltage circuit breaker F1 cannot
be deactivated remotely.
2. Check the status of the K1 /K2 LEDs .
If one of the LEDs has the incorrect status, switch the power OFF and ON using
the onsite ON/OFF switch. If the problem persists, check all the wiring or the func-
tion of certain relays.
3. If the status of the LEDs is o.k., press the test button of F18 and hold for at least 1 s.
The line voltage circuit breaker F1 must trip off to the middle position Tripped.
4. To switch on line voltage circuit breaker F1, first move the circuit breaker to the OFF
position and then to the ON position (requires extended pressure).
5. Check the status of the K1 /K2 LEDs again.
NOTE If circuit breaker F12 is switched off, line voltage circuit
breaker F1 cannot be deactivated remotely.

Fig. 106: Circuit breaker F1
Pos. 1 ON position
Pos. 2 OFF position
Pos. 3 TRIPPED position
Circuit breaker F12 (task)
Refer to (Fig. 107 / p. 204) for the illustration of F12.
204 PDC_A cabinet
Page 204 of 212
Refer to (Fig. 100 / p. 195) for a general overview of the location of circuit breaker termi-
nals F7 to F20.
Circuit breaker F12 supplies the following parts:
Voltage for F18
Current loop around transformer T1
Temperature safeguard for transformer within T1
Shunt trips at circuit breakers F1, F2, F3, F5, F6, F7, F11
Fig. 107: Breaker F12 - location
Pos. 1 Breaker F12
Service power socket 0
Power sockets (X140, X141) are available in the PDC to connect electrical service devices.
Refer to (Fig. 100 / p. 195) to see the location of X140, X141.
24 Volt power supply for U1 0
Refer to (Fig. 108 / p. 205) for the illustration of the 24-V power supply.
Refer to (Fig. 100 / p. 195) for a general overview of the location the 24-V power supply.
Tab. 71 LEDs of 24-V power supply
Tasks
Provides the extended voltage, e.g., for radiation warning indicator.
Is the power supply for the UPS REPO relay.
Indicator Color Status Function
LED DC ON Green ON DC is available.
LED ALM Red ON DC overload
PDC_A cabinet 205
Page 205 of 212
Tab. 72 Measurement points of 24-V power supply
Tab. 73 Troubleshooting 24-V power supply
Fig. 108: 24 Volt power supply for U1
Pos. 1 24 V power supply
Pos. 2 AC input
Pos. 3 DC 24 Volt output
Pos. 4 LED DC ON (green)
Pos. 5 LED ALM (red)
Voltage designation Measurement point
AC (input 230 V, AC) L / N
DC (output 24 V, DC) +V / -V
LED Status Possible cause Action
DC ON
ALM
OFF
ON
Short circuit or overload at
output (pos. 3 in
(Fig. 108 / p. 205))
1. Disconnect all external loads at
X20, except EPO.
2. Check function of the LEDs.
3. Check the connected load and
wiring if there is no change to the
LED status.
If no error can be deter-
mined in the connected
load and wiring, relay K3
could be faulty.
DC ON
ALM
OFF
OFF
No AC input at connector
L/N, pos. 2 in
(Fig. 108 / p. 205).
Check if F20 is tripped.
AC input is present. Power supply is faulty.
206 PDC_A cabinet
Page 206 of 212
UPS 0
For troubleshooting, it is not required to bypass.
1
the UPS manually. An automatic bypass
function is provided by the UPS and is executed automatically in case of an internal error.
This mode is indicated with a yellow LED at the UPS display.
Refer to (Fig. 109 / p. 206) for the illustration of the UPS.
Refer to (Fig. 100 / p. 195) for a general overview of the location of the UPS.
Fig. 109: UPS - with and without cover
Pos. 1 UPS with cover
Pos. 2 UPS unit
Pos. 3 Accumulator unit
Pos. 4 UPS without cover
Pos. 5 Accumulator packs
Pos. 6 Safety clamp
Status of the LEDs
1. Check the status of the LEDs on the UPS display as follows:
Tab. 74 UPS - LED status
1. Bypass means: INPUT and OUTPUT are bridged (dynamic bypass)
LED Status
AC INPUT ON
Battery OFF
UPS ON ON
PDC_A cabinet 207
Page 207 of 212
2. If LED AC INPUT or LED UPS ON is in status OFF
Check circuit breaker F10 (UPS input).
Check whether the circuit breakers (pos. 1) at the back of the UPS have tripped.
Fig. 110: Breakers - back of UPS
Pos. 1 Breakers
NOTE Use the operator manual from the UPS manufacturer (deliv-
ered with the CT system) for additional detailed information
and troubleshooting.

Battery symbol All LEDs are ON
1
Balance symbol First LED is ON
2
1. The accumulator level indicators display the
approximate accumulator capacitance at all
times.
2. The load level indicators display the approxi-
mate electrical load placed upon the UPS at all
times.
LED Status
208 Bad motor controller after corrupted FW update
Page 208 of 212
15- 15 Bad motor controller after corrupted FWupdate
Information for systems with SOMARIS/7, versions below VA40 0
If an update of the motor controller or its configuration file is aborted part way through (due
to interruption of power supply, a dropped FastLink connection, etc.), the frequency con-
verter will no longer be reachable. No service measure is available in the field to solve the
problem. The frequency converter has to be replaced.
Bad motor controller after corrupted FW update 209
Page 209 of 212
Work steps for systems with SOMARIS/7, versions VA40 and
higher 15.1
If the update of a motor controller is interrupted, it is possible to re-install the firmware.
To start a new update, switch the system off and then on again:
1. Switch the system to the COMP/ON status at the control box.
2. Switch the system to the SYSTEM/ON status at the control box.
3. To load the firmware, run the tune-up sequence for the affected controller under Local
Service > Tune-up > FRU Replace.
210 Changes to Previous Version
Page 210 of 212
16- 16Changes to Previous Version
Chapter Change Reason
3
Disabling of the UHR comb and service
switches added
TD_Charm_11561
3
Information about new DMS type and table
added
Change_537863
3
Troubleshooting of DMS power supplies cor-
rected/extended
TD_Charm_11562
Index 211
Page 211 of 212

17Index
H hz_serdoc_F13G01U03M01 . . . . . . . . . 9
hz_serdoc_F13G01U05M03 . . . . . . . . . 9
hz_serdoc_F13G01U06M01 . . . . . . . . . 9
hz_serdoc_F13G01U11M01 . . . . . . . 201
hz_serdoc_F13G01U12M0321, 64, 103, 129
hz_serdoc_F13G01U13M02 . . . . . . . . . 9
hz_serdoc_F13G02U01M01 . . . . . . . . 10
hz_serdoc_F13G02U01M04 . . . . . . . . . 8
hz_serdoc_F13G05U01M04 . . . . . . . . 10
hz_serdoc_F13G07U01M01 . . . . . . . . . 8
212 Index
Page 212 of 212

C2-030 840 01 08 02 PDF

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

C2-030 840 01 08 02 PDF

Enviado por

Direitos autorais:

Formatos disponíveis

Siemens, 2009

- For internal use only - All documents may only

Start troubleshooting as follows:

Você também pode gostar