Artis Zee

Artis zee
Troubleshooting Guide
System
System Troubleshooting with SW VC14
2 Document Version / Disclaimer / Copyright
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 cor‐
respond to the version at the time of system delivery and/or printout. Versions to hard‐
copy documentation are not automatically distributed.
Please contact your local Siemens office to order a 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 content described herein shall be used by qualified personnel who are employed by
Siemens or one of its affiliates or who are otherwise authorized by Siemens or its affiliates
to use such documents.
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 documen‐
tation without prior written authority.
Copyright
“© Siemens, 2009” refers to the copyright of a Siemens entity such as:
Siemens Healthcare GmbH - Germany
Siemens Aktiengesellschaft - Germany
Siemens Shenzhen Magnetic Resonance Ltd. - China
Siemens Shanghai Medical Equipment Ltd. - China
Siemens Healthcare Private Ltd. - India
Siemens Medical Solutions USA Inc. - USA
Siemens Healthcare Diagnostics Inc. - USA and/or
Siemens Healthcare Diagnostics Products GmbH - Germany
Artis zee AXA4-000.840.20.04.02 Page 2 of 318 © Siemens, 2009

11.10 CS PS AX IR/C Restricted
Table of Contents 3
1 General Remarks 7
1.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1.1 Required Aids and Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1.2 Additionally Required Documents . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2 Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2.1 General Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2.2 Product-specific Safety Information . . . . . . . . . . . . . . . . . . . . . . . 8
1.2.3 Conventions and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2.4 Tolerance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2 System Troubleshooting 14
2.1 Troubleshooting Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.1.1 Resource Monitor (Service) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.2 Dead Man’s Circuit (DMG Signal) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.3 Emergency Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.4 Quick Stop Troubleshooting guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.5 Radiation Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.5.1 Control Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2.5.2 Radiation Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.6 Dose and Dose Rate Troubleshooting Guide . . . . . . . . . . . . . . . . . . . . . . . . 35
2.7 X-Ray Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2.8 Collimator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.8.1 Collimator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.9 Image Quality Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.10 Carewatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.11 Measurement Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
2.11.1 SIRC Board in RTC (Realtime Computer) . . . . . . . . . . . . . . . . . . . . 43
3 AXCS 45
3.1 ACXS Problem Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

3.2 AXCS General Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.2.1 Servers on the AXCS network . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.2.2 Components of the AXCS Net . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.2.3 Non-AXCS Components on the AXCS network . . . . . . . . . . . . . . . 48
3.2.4 AXCS Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3.2.5 Testing the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4 CAN 51
4.1 CAN Communication and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

4.1.1 CAN Measurement Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
4.1.2 Introduction to Controller Area Network . . . . . . . . . . . . . . . . . . . 56
4.1.3 CANNET Bus Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
5 Flat Panel Detector 58
© Siemens, 2009 AXA4-000.840.20.04.02 Page 3 of 318 Artis zee

Restricted 11.10 CS PS AX IR/C
4 Table of Contents
5.1 Troubleshooting the Flat Panel Detector. . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
6 Image Quality Problems 59
6.1 Noisy Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

6.2 Geometric Disturbances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
6.3 Spots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
6.4 Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
6.5 Non-structured Disturbances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6.6 Excessive Environmental Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
6.7 Digital Image Preprocessing Samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
7 Power Distributor 89
7.1 Troubleshooting the Power Distributor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

7.2 Power Distributor (photo) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
7.3 D90 Board Component of the Power Distributor . . . . . . . . . . . . . . . . . . . . . 94
7.4 RCU Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
7.4.1 Overview of LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
7.4.2 Overview of Fuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
7.4.3 Overview of Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
7.4.4 Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
7.4.5 Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
8 Service Software Functions 100
8.1 Service Software Home Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

8.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
8.3 Backup & Restore (syngo) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
8.3.1 Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
8.3.2 Restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
8.3.3 Set Network Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
8.4 Tune Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
8.5 Report Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
8.5.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
8.5.2 Generating Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
8.5.3 Export Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
8.5.4 Reading Out Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
8.6 Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
8.6.1 Service Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
8.6.2 Control Fluoro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
8.6.3 Control Acquisition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
8.6.4 Auxiliary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
8.6.5 OGP Import/Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
8.6.6 System Backup/Restore (Acronis) . . . . . . . . . . . . . . . . . . . . . . . . . 132
8.6.7 ECC Layout Import/Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
8.6.8 Artis HW/SW inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
8.6.9 Offline SW Pkg Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
8.7 Quality Assurance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Table of Contents 5
8.8 Test Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

8.8.1 Hardware tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
8.8.2 AXCS tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
8.8.3 Third-party tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
8.8.4 Stand & table tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
8.8.5 SIRC status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
8.9 DICOM Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
8.9.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
8.9.2 Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
8.10 File & Image Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
8.10.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
8.10.2 Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
8.10.3 Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
8.11 Auto Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
8.11.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
8.11.2 Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
8.12 Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
8.12.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
8.12.2 Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
8.13 Software Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
8.13.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
8.13.2 Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
8.14 Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
8.14.1 Event Log Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
8.14.2 Filtering the Event Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
8.15 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
8.15.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
8.15.2 Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
8.16 Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
8.16.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
8.16.2 Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
9 Procedures 285
9.1 Starting the Service Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

9.2 AX Save Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
9.2.1 Saving Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
9.2.2 Event Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
9.3 Transferring the Error Log to the SRS Server . . . . . . . . . . . . . . . . . . . . . . . . 289
9.4 Software Version Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
9.4.1 Starting the Software Version Check. . . . . . . . . . . . . . . . . . . . . . . 290
9.5 Network Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
9.5.1 PING. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
9.5.2 Netstat. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
9.6 How to log in as Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
9.7 AXCS Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
9.7.1 Saving the AXCS Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
9.7.2 Converting the AXCS Trace into a Readable Format . . . . . . . . . . . 299

6 Table of Contents
9.7.3 Viewing the AXCS Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

9.7.4 Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
9.8 Getting DIPP Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
9.9 Confirmation of Adjustment using Component Reports. . . . . . . . . . . . . . . . 303
10 Changes to Previous Version 304
11 List of Hazard IDs 305
12 Index 306

General Remarks 1 7
1.1 Requirements
1.1.1 Required Aids and Tools

All tools, test equipment and aids, with the exception of the “standard service tool kit”,
are listed and specified in the Service Tools Catalogue.
n Standard service tool kit

n Torque wrench, 40 - 60 Nm
n Spirit level
n Ground wire test meter
n Line resistance test meter
n TV dynamic test
n Water pail, approx. 10 l (to fill the cooling unit)
n For floor stand: Loctite, Type 243
Tab. 1 For X-Ray Generator Service
n PTW DIADOS 97 17 612 KE999

Only where DHHS Regulations apply, required for the measure‐
ment of the skin dose rate.
(Otherwise, not required for checks during startup, only if there
are differences, and thus a readjustment is necessary)
n Spotmeter for SMfit ACT 77 52 848 GE084
(not required for the checks, only if there are differences and
thus a readjustment is necessary)
n Densitometer,e.g. X-Rite 331 97 02 416 Y1996
n Oscilloscope, e.g. Fluke ScopeMeter 199 CM 73 92 074
1.1.2 Additionally Required Documents
n System Operating Instructions

8 1 General Remarks
1.2 Remarks
1.2.1 General Safety Information

When carrying out the work steps and checks, the general safety information for medical
products must be observed.
1.2.2 Product-specific Safety Information
1.2.2.1 System
 WARNING
If there is a computer crash during “Service Radiation ON”, radiation is not auto‐
matically stopped.
 If there is a computer crash, immediately press the on-site system emergency
off switch.
 WARNING
[hm_serv_NoteProtectEyes]
Laser Class 3B units having a maximum output of 500 mW. This kind of laser is
used for the image transfer
a) from the FD to the RTC
L
b) from the RTC to the Image System.
The laser beam is invisible, dangerous to the human eye, and in some cases, to
the skin.
 Proper use must be observed.
 Required safety equipment must be used.
1.2.2.2 Angio MR Miyabi
M The safety information for AXIOM Miyabi, ( AXIOM Miyabi / AXA4-000.860.01) must be
observed.

General Remarks 1 9
1.2.2.3 Systems with Magnetic Navigation (NIOBE)
Fig. 1: Not allowed for patients with cardiac pacemaker
 WARNING
Artis zee floor MN and Artis zee biplane MN Systems with Magnetic Navigation
(NIOBE):
M The two permanent magnets are installed by the Stereotaxis Company. Magnetic
objects can be attracted by the two permanent magnets and can fly through the
air like shots.
 The safety information in the technical documents from the Stereotaxis Com‐
pany absolutely must be observed.
1.2.2.4 Control Cabinets
 WARNING
[hm_serv_LabelPowerPresent]
Even after switching off the system (Shutdown), power is still present at the con‐
trol cabinet and generator.
If not observed, death or serious bodily injury can occur.
 Observe the warning signs in the cabinets.
 Switch off the power supply to the X-ray system with the on-site on/off
switch.

10 1 General Remarks
1.2.2.5 Patient Table
Fig. 2: Lift safety stud, tilt safety brackets
2
3
When performing service work in the table, serious injury can occur if there is uninten‐
tional lowering or tilting of the table. To prevent this, it is absolutely necessary to use the
following safety aids:
n Lift Safety Stud
Move the table all the way up, insert the lift safety stud ( 1/Fig. 2 Page 10) into the
table base from the outside and secure it with 2 cotter pins ( 2/Fig. 2 Page 10).
n Safety Brackets
For tilting tables, set the max. Trendelenburg position and insert the two safety brack‐
ets ( 3/Fig. 2 Page 10). Secure the two safety brackets with 2 cotter pins each.
1.2.2.6 Generator
 WARNING
Risk of Accident!
 As a rule, measurements using the oscilloscope may be performed only with
the ground wire connected. Disconnecting the ground wire without an isola‐
tion transformer is always forbidden. The ground wire may be rendered inef‐
fective via an isolation transformer only if voltages of no more than 25 V AC
or 60 V DC can occur on metal parts that can be touched. For measurements in
which ground loops can have a disturbing effect on the measurement result,
an isolation amplifier (e.g. GOULD Contec 9000 or TEKTRONIX A6902B) must
be used.

General Remarks 1 11
1.2.2.7 X-Ray Tube Cooling System
 DANGER
Power is supplied to the cooling unit for about 20 minutes even if the system is
turned off!
 Turn off the F1 breaker at the power distributor (MD) in the system cabinet.
1.2.2.8 FD Detector
 WARNING
The FD cooling unit is supplied with line voltage and the FD with 24V DC even
when the system is switched off. To switch power of to these components:
 switch off the "FD cooling unit" F13 fuse and the "FD Power Supply" F8 fuse in
the power distributor, or
 switch off power to the complete power distributor with the F1 power switch,
or
 set the system switch to the OFF position to switch power off to all compo‐
nents in the system.
1.2.3 Conventions and Abbreviations

n In this document, table is used to mean the patient table.
n In part, the installation hardware is contained in numbered bags. The numbers listed
in the text in this document contained in square brackets, e.g. [Pos.: 1] indicate the
numbers on the accessory bags with the corresponding required materials.
n Unless otherwise stated, all dimensions in this document are in mm.
1.2.3.1 Abbreviations
CCM = Collimator Control Module

COL = Collimator
DCS = Display Ceiling Suspension
DDIS = Data Display on MTS or monitor cart
DVM = Digital voltmeter
INJ = Injector
ISK = Allen screw
KPC = Kuka PC in the Kuka control cabinet
LSS = Local System Server (System Management)

12 1 General Remarks
MC = Motor Controller
MCM = Motor Controller
MCU = Motor Control Unit
MD = Mains Distributor (power distributor)
MLC = Midsize Lab Cockpit
MNP = Managed Node Package (System Management)
PUD = Generator Polydoros A100
RAC = Rotating Anode Control
RTC = System Real Time Controller
SCM = Stand Control Module
SRS = Siemens Remote Service
SW = Wrench size
TBL = Table
TCM = Table Control Module
ULI = User Location Interface
 Abbreviations related to the Imaging System can be found in the “Imaging System Soft‐
ware Installation Guide.”
Tab. 2 System Naming
Artis Product Names Artis System Types

Artis zee Floor Artis_dF
Artis zee Ceiling Artis_dT
Artis zee Biplane Artis_dB
Artis zee Multi-purpose Artis_dMP
Artis zee Biplane MN Artis_dBMN
Artis zee Floor MN Artis_dF MN
Artis zeego Multi-axis Artis_dR
Signal name Description

GND = Ground
XRQ = Radiation request
SRV_RAD = Service radiation enable

General Remarks 1 13
Signal name Description

WD = Watchdog
Q_STP = Quick stop
PROX ... = Proximity ...
INJ_RDY = Injector ready
DM = Dead man
DMG = Dead man’s grip
EGY_REL = Emergency release
Tab. 3 Abbreviations related to the X-Ray generator
Name Description Previous name

UDC_act = Intermediate circuit voltage UZ ist
UDC_nom = Nominal intermediate circuit voltage UZ soll
IT_act = Actual tube current IRö ist
IT_nom = Nominal tube current IRö soll
UT_act = Actual tube voltage URö ist
UT_nom = Nominal tube voltage URö soll
STRT_Inv = Start main inverter SWR
ROT = Rotation of anode
SS_test on = Service switch in test position
IH_act = Actual filament heating IH ist
IH_nom = Nominal filament heating IH soll
XRAY = Radiation on
ID = Actual charge current for intermediate voltage
R+ = Positive tube voltage (1V=10kV )
R- = Negative tube voltage (1V=10kV )
1.2.4 Tolerance Data
1.2.4.1 Torque Values

A tolerance of ± 10 % is permitted for torque values.

14 2 System Troubleshooting
 DANGER
After switching off the system (shutdown), there is still voltage present in the sys‐
tem control cabinet and in the generator.
When performing service work:
 - observe the warning labels in the cabinets.
 switch power off to the radiographic system at the main on/off switch.
 All pictures shown in this document are sample pictures. They may differ from the SW
Version actually installed.

System Troubleshooting 2 15
2.1 Troubleshooting Assistance

The following table provides troubleshooting assistance for Artis zee systems.
Tab. 4 Boot Problems
Problem and Function Tests Links and Solutions

The system does not power on. n If the power on from the D90 “On button” works, continue trou‐
bleshooting in the image system ( Boot Prob‐
lems / AXA4-000.840).
n Check the power supply LEDs V 1 and V30 on the D90 board of
the power distributor. They have to be on. If not, use the
ON/OFF switch circuit wiring diagram to continue troubleshoot‐
ing. Continue troubleshooting the power distributor ( Power
Distributor / Page 89).
n Check the Power On interface in the image system.
n Check the yellow “ON_PRESSED” LED on the SIRC board. It must
be on. If it stays off, use the ON/OFF switch circuit wiring dia‐
gram to continue troubleshooting.
The system does not power off. n If the power off from the D90 “Off switch” works, continue trou‐
bleshooting in the image system.
There is a boot problem with n Continue troubleshooting the image system( Boot Prob‐
“Black screen” lems / AXA4-000.840).
 While the Imaging System is booting up, several system hardware tests are performed.
Tab. 5 Boot Problems

There is a boot problem with an n Check the error log for corresponding messages.
Error tab card during Syngo
boot
There is a boot problem Possible causes due to (refer to the corresponding troubleshooting
guide):
n Image system bootup.( Boot Problems / AXA4-000.840)
n Motor controller board boot phase (floor stand, ceiling stand).
n Motor controller board boot phase (table).
n Control module bootup.
n Examination control console boot sequence.
n Data Display boot sequence.
n X-Ray generator power unit boot phase.
n ULI board bootup.


Following bootup, the following message ap‐ n Check the event log for invalid license messages
pears: (set the Message Text filter of the Event viewer to
Fig. 3: Invalid license “invalid license” or press ctrl + f and search with
“invalid license”).
If only one or a few licenses are invalid, go to:
Service > Configuration > Licensing
Check the status of the licenses. If all licenses are
invalid, proceed with the worksteps below.
n Do a version check under:
Service > Configuration > Version Check.
If there is a missing/selected license, go to:
Configuration and press AutoLic.
Repeat the Version Check and Config Check, shut
down the system and reboot again.
n Check whether the dongle is properly connected.
n Use the key combination to enable access to Win‐
dows (see AX PASSWORD LIST, ID 13982 in the
CS Knowledge Base).
n Use the key combination <“windows” and “r”>
and enter the “cmd” command to obtain a “DOS
box”.
Enter the following line:
lmutil lmhostid -flexid
 The “Dongle ID” will appear as an output
result. This number is also printed on the
dongle. If, instead of the dongle ID, the
Host ID or another number is shown, re‐
place the dongle.
n Check system date & time.

The system is in “Bypass Mode” Missing KV /mA values means that the initial P-transfer did not com‐
The X-Ray forecast parameters plete because at least one component within the system is not
are not shown. ready. Use the AXCS test ( AXCS TEST / Page 49) to find out
which component is not ready.
n Reset the affected component.
n If there is nothing wrong in the AXCS test, look through the er‐
ror log for AX_SYC messages with the ID 3 and 4 to find out
which component has rejected the p-transfer.
n Check the service-relevant error log for component ready mes‐
sages

The data display shows “NO The system controller is down.

Communication” in the system n Refer to the RTC troubleshooting guide ( RTC Troubleshoot‐
message line. ing / AXA4-000.840.10).
The data display shows “No The AXN root of the DDIS is down.
Communication” in yellow char‐ n Reload the software to the DDIS (refer to the DDIS troubleshoot‐
acters in the system message ing guide).
line.
The data display shows The Rep is down.
“xxxxxxxxxxx” in the system n Check the AXCS network switch in the system cabinet.
message line.
n Shut down the system and start it again (be sure that the com‐
ponents have turned off).
n Check if the “REP process” is running. To do this, call up the Util‐
ities function, select the menu “Process list” and check whether
the “Rep” process is running.
If the “REP” process is running:

n Check the hardware connection to DDIS and use ping 10.1.1.8
(or 9) to verify internal AXCS connection.
n Replace the connection at the switch with a different connector.
n Use the AXCS test ( AXCS TEST / Page 49) to check whether
all components are ready.
If the “Rep” process is not running:

n Reload the system software.

The system is in “Bypass Mode” n If the Image System does not show ready, check the error log
and an AXCS component is not for more messages.
“READY” n If the ANG (Angiomatic) does not show ready, check the error
log for AX_ANG messages.
If the error message points to the power unit, continue with the
PUD troubleshooting guide.
n If the SCU (stand control unit) does not show ready, check the
error log for AX_STD messages.
n If the SYC (system controller) does not show ready, check the
error log for AX_SYC messages.
- Download the SYC SW again.
If this is unsuccessful, replace the RTC.
n If the ACU (acquisition control unit) does not show ready, check
the error log for AX_ACU messages.
- If the error message points to the image pre-processing part,
check the LED status on the DIPP board.
- Download the ACU SW.
n If the CCU (collimator control unit) does not show ready, check
the error log for AX_COL messages.
There is a message “NO XRAY, n Check the error log for more messages.
please wait,” which does not re‐
cover.
There is a radiation problem n Troubleshooting X-ray radiation release
n Troubleshooting the power unit
With any X-Ray release, the sys‐ n Check the error log to see if the problem is reported from the
tem goes into “Bypass” image system or from an RTC component.
n Troubleshooting the image system( AXIS Image System
VC14 / AXA4-000.840.19).
n Troubleshooting video pre-processing.

There is no movement n Reset the SYC system controller from the SCM by pressing the
“override” button combination, then press and release the emer‐
gency stop button.
Fig. 4: Button combination for the “Override” function.
n Check whether the control modules are integrated in the CAN

network.
n Check whether the motor controllers are ready. See the 7-seg‐
ment display at the bottom of the motor controllers. They have
to display alternatingly A0 - B0, or A1 - B1, or A2 - B2 which is in
relation to the CAN node ID.
n If there is a blinking LED at a control module, an internal CM
problem has occurred. Replace the CM.
n Check the error log for AX_SCU messages.
n Check the power supply to the motor controllers (3-phase 120 V
from power distributor).
n Continue troubleshooting the stand / table.
n Continue troubleshooting the user interface.

There is a movement problem. n If the SIRC board does not receive the DMG signal (check green
The movement has stopped and LED DM_Out), continue troubleshooting with DMG trouble‐
it is not possible to start the shooting guide.
movement again. n If the red LED "Emergency Stop" lights up on the SIRC board,
- check all red Stop buttons
- Continue troubleshooting in the emergency stop circuit; use
the circuit diagram
n If the quick stop LED lights up on the SIRC board, it could be
caused by the following:
- a collision
- activation of a limit switch
- activation of a contact safety switch
Continue troubleshooting in the quick stop circuit, use the wir‐
ing diagram.
n Analyze the error log for AX_SCU messages.
n Brief high-speed movement with an immediate stop could be
caused by a defective encoder.
n Check whether the movement command is evaluated from the
control module. See the Stand/Table Troubleshooting Guide for
the affected system:
- Patient Table ( Table Control Module / AXA4-000.840.05)
- Floor Stand ( Stand Control Module / AXA4-050.840.01)
- Second Plane ( Stand Control Module, Second Plane (biplane
systems only) / AXA4-050.840.01)
- MP ( Table Control Module / AXA4-410.840.01) and
( Stand Control Module / AXA4-410.840.01)
- Ceiling Stand ( Stand Control Module / AXA4-060.840.01)
- zeego ( No Movement with RCM / LCM is possi‐
ble / AXA4-040.840)
n Continue troubleshooting the stand / table.
n Troubleshoot the collimator and camera rotation
- Go to linearity adjustment for collimator and camera rotation.
- Check whether the reference tag is detected during the line‐
arity adjustment.

Movements can be performed, Check for error conditions that limit the movements.
but only at reduced speed. n The collision calculator has detected a possible collision.
n Only slow speed movement is allowed because of some error
conditions (e.g. a faulty position sensor, Motor encoder,...).
Continue troubleshooting the stand / table.
n If DMG is detected as active during startup, the speed is reduced
for all movements; the user is informed about the reason for the
reduced speed. Check whether the DM LED at the SIRC remains
on.
Movements can be performed, n If the Quick Stop LED lights up on the SIRC board, it could be
but only when the “override” caused by the following:
button combination is used. - possibility of a collision
Fig. 5: Button combination for the
“Override” function. - a limit switch has been reached
- Check the contact safety switches.
- Continue troubleshooting in the Quick stop circuit, use the
wiring diagram.
n A drive is beyond its SW limit. A new adjustment is recommen‐
ded.
n The collision calculator has detected a possible collision.
In this mode, the reduced over‐ - Check whether there is a real risk of collision.
ride speed is used. - Check whether the potentiometer values are correctly repor‐
ted.
- Check whether the configuration of the stand is OK.
There is jerky movement n Continue troubleshooting the stand / table
The X-Ray image has poor quali‐ n If previously recorded images are OK, continue troubleshooting
ty FD.
There is an image processing n Continue troubleshooting the image system ( Decision Find‐
problem. ing / AXA4-000.840.19).
There is a general network con‐ n General Troubleshooting of Network Problems ( Network No‐
nectivity problem. des / AXA4-000.843.04).
It is not possible to search for n Continue troubleshooting the image system ( Decision Find‐
patients at remote network no‐ ing / AXA4-000.840.19).
des with the patient browser.
It is also not possible to transfer
patient images to a remote net‐
work node.
It is not possible to send images, n Continue troubleshooting configuration network nodes ( Net‐
but the remote node is accessi‐ work Nodes / AXA4-000.843.04).
ble with ping and C_ECHO

It is not possible to transfer pa‐ n Continue troubleshooting configuration network nodes ( Net‐
tient images to a remote net‐ work Nodes / AXA4-000.843.04).
work node.
But it is possible to search for
patients at remote network no‐
des with the patient browser.
Printing images to a DICOM n Continue troubleshooting configuration network nodes ( Net‐
printer is not possible. work Nodes / AXA4-000.843.04).
Other network communications
are OK.
It is not possible to receive im‐ n Continue troubleshooting configuration network nodes ( Net‐
ages from a remote network work Nodes / AXA4-000.843.04).
node.
Other network communications
are OK.
It is not possible to receive a n Continue troubleshooting DICOM Worklist ( HIS/RIS no‐
worklist. des / AXA4-000.843.04).
There is a problem with CAN n Troubleshoot the CAN components ( CAN / Page 51).
communication. (A CAN compo‐
nent is not accessible.)
There is a problem with AXCS n Troubleshoot the AXCS components ( AXCS / Page 45).
communication.
There is a problem with the n Troubleshoot the power distributor ( Power Distribu‐
power distributor. tor / Page 89).
There is a problem with the n Troubleshoot the power distributor ( Power Distribu‐
On/Off circuit. tor / Page 89).
Use the "On/off switch circuit 1 and 2" wiring diagram for trouble‐
shooting this subject.

The Resource Monitor warning Open Local Service UI (Level 7) to enable the Service Resource Mon‐
icon appears. itor. Left click the Resource Monitor Icon (Pie chart) to view the
Fig. 6: Resource Monitor Warning Icon Service Resource Monitor. For detailed information on the Service
Resource Monitor see ( Resource Monitor (Service) / Page 24).
Temporary Storage:
Fig. 7: Resource Monitor (not enough space left for temporary storage of data)
An event message is reported in the application log as a warning,

with source CAP_RM and ID 102.
The cause is insufficient capacity of the C: drive. Typically, C:\Temp
is the source of the problem, but other folders on C: can be the
cause.
n Check the capacity of the C: drive; if needed, delete the follow‐
ing:
- C:\Temp\*.*
- C\Windows\Temp\*.*
- C:\Axiom\Axis\*.DMP
- C:\Axiom\log\*_ERR.LOG
- It may be useful to keep the most recent logs for trouble‐
shooting.
There is a problem with a serv‐ n Check for more messages in the Event log ( Event Log
ice procedure. / Page 267).

2.1.1 Resource Monitor (Service)
Fig. 8: Resource Monitor - Service
The Service mode of the Resource Monitor is available when Local Service is opened with
Level 7 or higher. Left click the Resource Monitor Icon (Pie chart) to open the Resource
Monitor window. The Resource Monitor is updated every 5 seconds.
2.1.1.1 (Data) - overview

The amount of disk space used remains the same. The numbers shown are based on the
size of the database at creation (Total) and the unused space in the database file (D:\DA‐
TABASE\***\system). This value is retrieved from Versant (database software).
The data that are stored in the system file are Patient, Study, and Series data (e.g. patient
information, DICOM values, study name, etc.). Typically, alphanumeric data
The Exchangeboard and ArchiveStore are typically at 3% when empty, SchedulerStore is
typically at 10% when empty.
When a database is corrupted, the free space in the database may not increase when Pa‐
tients/Filmsheets/ArchiveTasks are deleted/cleared.
2.1.1.2 (Blob) - overview

Because the Local, Exchangeboard and SchedulerStore databases all use the same drive
(E:\IMAGE\) for Blob storage, the 3 resources (Local/Exchange Board/Scheduler) always
show equal values.
Any files located on the E: drive will decrease the amount of free space calculated by the
Resource Monitor for the Local/Exchangeboard/Schedule (Blob).
The Blob files of the Local database are typically stored in E:\IMAGE\2..... (e.g. E:\IMAGE
\2.0.34904)
The Blob files of the Exchangeboard database are typically stored in E:\IMAGE\4..... (e.g. E:
\IMAGE\4.0.34904)

The Blob files of the SchedulerStore database are typically stored in E:\IMAGE\3..... (e.g. E:
\IMAGE\3.0.34904)
The Exchangeboard and SchedulerStore folders are typically empty when there are no
queued or pending jobs (e.g. Film sheets, Archive to Net, etc.)
2.1.1.3 Local (Data)

monitors the free space in the Versant database named Local.
The Local database in the main database for Patient and Study storage.
2.1.1.4 Local (Blob)

monitors the free space on the E: drive. The overall used space on E:\IMAGE is correctly
indicated by the % value. The actual size of each of the 3 individual types of Blobs is not
shown.
Blob data are typically generated during acquisitions, Store Fluoro, Store Monitor, Store
Ref.
2.1.1.5 Exchangeboard (Data)

monitors the free space in the Versant database named Exchangeboard.
The Exchangeboard is used for temp data when it is being transferred (e.g. film jobs)
2.1.1.6 Exchangeboard (Blob)

shown.
Blob data are temporary, typically generated during Filming, Archiving to Net.
2.1.1.7 SchedulerStore (Data)

monitors the free space in the Versant database named SchedulerStore.
The SchedulerStore is used for temp data from Modality Worklist and Pre-Registration.
2.1.1.8 SchedulerStore (Blob)

shown.
Blob data typically do not exist.(?)
2.1.1.9 ArchiveStore (Data)

monitors the free space in the Versant database named ArchiveStore.
The ArchiveStore is used for removable media.

2.1.1.10 ArchiveStore (Blob)

unknown - not used
2.1.1.11 Physical Memory

monitors the Physical memory
The values can be found as follows:
1. Press Win + r.
2. Type taskmgr in the edit box and click OK
 Windows Task Manager is shown.
3. Click the Performance tab
 The total and available physical memory are shown at the bottom of the dialog
box
Fig. 9: Physical memory - Windows Task Manager
2.1.1.12 Virtual Memory

monitors the Virtual memory
The values can be found as follows:
1. Press Win.
 The Windows Program menu is shown

2. Select Settings > Control Panel > Administrative Tools > Performance.
 The Performance window is shown.
3. Right click the right pane of the Performance window (the graph is shown here)
 The context menu is shown
4. Select Properties....
 The System Monitor Properties dialog box is shown
5. Select the General tab
6. Select Report from the View group.
7. Select the Data tab
8. Click the Add... button
 the Add Counter dialog box is shown
9. Select Memory from the Performance object dropdown box
10. Select the Select counters from list radio button
11. Select Commit Limit, press and hold the Ctrl key and select Committed Bytes
12. Click the Add button
13. Click the Close button on the Add Counter dialog box.
14. Click the Apply button on the System Monitor Properties dialog box.
15. Click the OK button on the System Monitor Properties dialog box.
 The values are shown
Total Virtual Memory = Commit Limit
Free Virtual memory = Commit Limit - Committed Bytes
2.1.1.13 C:\Temp
monitors the free space on the C: drive. Typically, C:\Temp accumulates unnecessary files.
However, there are other location on the C: drive that can fill up with unnecessary files:
n C\Windows\Temp\
typically there are no required files in this folder. The system (Win XP) may have some
files IN USE which are prevented from being deleted. This is normal.
n C:\Axiom\Axis\
typically *.DMP files can be deleted. It may be useful to keep the most recent files for
escalation if the problem continues.
n C:\Axiom\log\
typically *_ERR.LOG files can be deleted. It may be useful to keep the most recent logs
for troubleshooting.

2.2 Dead Man’s Circuit (DMG Signal)

The DM Signal remains on all Disconnect the control modules, one at a time to find out from
the time at the SIRC board. which user location the signal is coming.
Also check the DM_Signal from the foil-switch on the collision sen‐
sor from the FD.
The DM signal remains off all Look for error messages coming from an RTC component.
the time at the SIRC board.
The DM signal at the SIRC board Use the "Dead man’s Switch Circuit" Wiring Diagram to find out
lights up only if the DM_Grip where the signal got lost. The DMG signal from a control module
contact is activated from certain runs in the same cable as the CAN network wires (Pin 5).
user location(s).

2.3 Emergency Stop

Check the current path from +24V down to the SIRC board X4.2 / X5.2.
Refer to the wiring diagram, Safety circuit / Emergency stop page for the system type.
Fig. 10: Emergency stop circuit example

2.4 Quick Stop Troubleshooting guide

The quick stop LED at the SIRC board is a red LED that lights up with an active quick stop
signal.
The quick stop LEDs on the motor controller boards are green; they light up under normal
conditions and turn off with an active quick stop signal.

The quick stop signal (QStopOut) n If Emergency Stop is active, both Quick Stop LEDs are off.
on the SIRC board is continuous‐ n Check for a collision.
ly present.
n The data display will show the location where the contact safe‐
ty signal is detected.
n Check the contact safety switches. (Use the wiring diagram page
“Safety Circuit Collision Protection/ Quickstop / Contact Safety Device Safety
Circuit/ Quick stop”) .
n Press and release the contact safety switches one by one and
check the Quick stop LEDs.
With every release of a contact safety switch, the quick stop
LED has to switch off. If the LED immediately turns back on,
check another contact safety switch which might be activated
all the time and therefore latches the quick stop again.
n If the quick stop In LED is off and the quick stop Out LED on a
motor controller (MC) is on, it can be assumed that there is no
SW loaded in this MC or that the MC is defective. Start a soft‐
ware download from the SW Manager.
n Change the SIRC Board.
There is no Quick Stop (The n Check the contact safety switches.

Q_STP LED remains off ) when a n If the signal is received at the motor controller but there is no
contact safety switch is activa‐ reaction, replace the MC.
ted.
Every contact safety switch that is pressed will latch the Quick_Stop circuit. The signal
goes "Low".
Every change of the proximity status is reported via CAN to the SCU software.
If a contact safety switch changes from active to inactive, the SCU sends a Quick Stop re‐
lease. If one contact safety switch holds the quick stop and another contact safety switch
is pressed and released again, the quick stop LED will be briefly turned off and on again.
This is because release of a switch will release the quick stop but the other switch that is
still active will set the quick stop circuit again.
The quick stop signal is normally at high level.

Fig. 11: Proximity quick stop principal function diagram

2.5 Radiation Problems

Problem and FunctionTests Links and solutions
All radiation modes are faulty n Is the radiation release circuit OK? ( Radiation Re‐
lease / Page 34)
n Is the power supply OK?
n If radiation is possible with control fluoro or control exposure,
check the event log for ACU or SYC error messages. (Check also
for messages logged during the boot phase of the system.)
n If radiation is possible with dose adjustment, check the event log
for ACU or SYC error messages; if nothing is found, continue with
troubleshooting for the X-ray generator.
n Is the power unit OK? Continue troubleshooting Polydoros A100
( Problem Description / AXA4-100.840.09).
n For dose or dose rate problems, continue ( Dose and Dose Rate
Troubleshooting Guide / Page 35)
System message: n Check the event log for this message.
"No Fluoro: try again" n Check the event log for an initialization problem.
There is a problem with fluoro n To check the dose measurement circuit, it is recommended to
only start the PDA test that can be found in the service UI under Test
Tools > Hardware Tests>.
n Check the footswitch signals (use wiring diagram).
n Are the footswitch signals OK? - Check the RTC/SIRC signals (use
wiring diagram).
There is a problem with expo‐ n Check the footswitch signals by using the wiring diagram.
sure only n Are the footswitch signals OK? - Check the RTC/SIRC signals (use
wiring diagram).
There is a problem with the n Use the Control Fluoro or Control Exposure function to exclude a
dose or dose rate PUN error ( Control Fluoro / Page 123).
n Go to ( Dose and Dose Rate Troubleshooting Guide
/ Page 35).
The tube voltage is out of all n Check whether the problem is “focus-related”
proportion to the object (UT n Check the filament circuit / tube unit
too high).
With thicker objects, the mes‐
 refer to tube unit troubleshooting guide ( MEGALIX
CAT ...-121... with the Klüver Cooling Unit Troubleshoot‐
sage “dose less than 5%” is dis‐
ing / AX71-020.840.02).
played.

Radiation Function Test:

n Use Control Fluoro to test the PUN without Angiomatic regulation ( 1/Fig. 12 Page 33).
n Use Control Acquisition to test the PUN without Angiomatic regulation ( 1/Fig. 13 Page 33).
The exposure time will be 100 ms.
n Power unit tests with the service switch at D600 turned on (LED light up yellow) will disable fila‐
ment heating and disconnect the supply to the intermediate circuit.
2.5.1 Control Functions

Fig. 12: Controlled fluoroscopy
Fig. 13: Controlled acquisition

2.5.2 Radiation Release

Radiation release is possible only from one n Run the SIRC test to check the hardware connections
footswitch. ( SIRC status / Page 143) .
n Search in the Event Log for the message
AX_ACU 42. This message checks whether the hard‐
ware signal or a CAN object is missing.
There is no release signal received at the n Check the footswitch signals according to the Wiring
SIRC board. Diagram.
There is no radiation release. Check the signals at the SIRC board of the RTC (use wir‐
ing diagram).
Link to measurement examples ( SIRC Board in RTC
/ Page 43)
The XRQ signal is missing Check the DIPP (video pre-processing) for error messag‐
es and function.
A footswitch radiation release signal is received by the SIRC board as the SUM_REL signal.
Together with the XRQ signal from the video pre-processing part, the radiation will be
triggered.
The signal SWR or STRT_INV is responsible starting the high voltage inverter in the PUN.
The end of an X-Ray pulse usually is determined by the dose counter.
But the mass counter or the safety time counter can also stop an X-Ray pulse.

2.6 Dose and Dose Rate Troubleshooting Guide
 If there are dose or dose rate-related problems, it is recommended to run the dose ad‐
justment procedure for troubleshooting purposes without saving the results.
Problem Links and Solutions

The dose is too low n If this situation is constant with different dominant selections,
perform a new dose adjustment and compare the results with the
values from the previous adjustment or the original initial adjust‐
ment. There might be a difference, but the tendency should be
the same.
The dose is too high n Perform a new dose adjustment and compare the results with the
values from the previous adjustment or the original initial adjust‐
ment. There might be a difference, but the tendency should be
the same.
The dose varies or it is unsta‐ n Run the control fluoro, control exposure generator tests ( Con‐
ble. trol Functions / Page 33) . If the dose / dose rate is reproducible,
the error is not located on the power unit side.
n Run the control fluoro ( Control Functions / Page 33) generator
test and check the different profiler settings for proper function.
Follow the AX_CCU messages as well.
n Check the FD and FD power supply ( FD with System SW
VC14 / AXA4-110.840.04).
The CAREWATCH reading is n Check according to the Adjustment Instructions.
not OK.

2.7 X-Ray Generator

n Go to Troubleshooting Guide POLYDOROS A100 ( Problem Descrip‐
tion / AXA4-100.840.09).
n Go to the MEGALIX cooling system Troubleshooting Guide ( KLÜVER Cooling Unit,
Part No.: 57 64 555 / AX71-020.840.02).

2.8 Collimator
2.8.1 Collimator

There is no reaction of the col‐ n Check the collimator power supply coming from the power dis‐
limator when there is a move‐ tributor via the circuit breaker and the D90 board according to the
ment command. wiring diagram ( Power Distributor / Page 89).
n Check whether the collimator is accessible via CAN.
 Run the AXCS test ( AXCS TEST / Page 49)to determine
whether the collimator is ready.
n Reload SW to the collimator via CAN download.
 Always reload both SW packages (DSA and Standard) to
the collimator!
n If the power supply and the CAN connection / SW download are
OK, replace the collimator.
There are warning messages n Check the error log for AX_CCU and AX_CAN messages.
about dose or skin dose. - If there are messages with the ID 110, identify the cause of the
warning according to the code given in the free text [xxxx] and
the explanation listed in the information box
 Check the prefilter function with the control fluoro mode
( Control Fluoro / Page 123) . Here it is possible to set all
filters individually. Open the collimator housing and closely
watch the physical movement of the filter. Check the X-ray
image as well to verify that no filter stops somewhere be‐
tween the in and out position.
The collimator is doing contin‐ n Reload the Collimator Software via SW Manager.
uous “search runs”

2.9 Image Quality Problems

The most common image quality symptoms are:
n Image artifacts
n Noisy images
n Poor image contrast or detail

Image artifacts n First determine if the artifact moves when magnification
modes are changed.
- If so, the artifact must be on the input side of the FD,
somewhere in the beam path, tabletop, grid or input
screen. Continue troubleshooting FD ( FD with Sys‐
tem SW VC14 / AXA4-110.840.04).
Noisy Image n Dose-related problem. Measure the input dose to see if it
is within the specification.
n Noise can be either interference or quantum noise.
- Interference noise is identified by its distinct pattern
and is usually caused by poor grounding.
- Quantum noise may be caused by low light levels.
n A noisy image could be related to the DEXI Adjustment
(go to Dose adjustment FD systems ( System Dose Ad‐
justment / AXA4-000.842.08))
n FD is generating the noisy image by itself.
n Poor image contrast n Check the organ program using the exam editor.
n Poor image detail kV, Pulse width, kV filter, kV ms, kV Dose, kV Focus and
n The image brightness the image processing parameters.
is not OK n Dose, skin dose and DEXI adjustment
n Check the dose efficiency of the X-ray tube.

2.10 Carewatch
 All adjustment and replacement instructions are in the CAREWATCH documentation.

No dose area product value at n Check whether the power supply LED is on at the front panel of
system monitor the Diamentor.
- If the LED is off, check the supply voltage at the rear plug X3
(Pin 1+3 = +24V; Pin 5+9 = Ground).
n If the power supply at X3 is ok and the green “on” LED is off, then
replace the Diamentor control unit.
No dose area product value at n Check whether the ionization chamber is properly connected.
system monitor. n If the yellow HV LED on the front panel lights up, the high voltage
On the front panel of the Dia‐ for the chamber is out of tolerance and no pulses are generated
mentor the power supply LED (HV error).
is on. - If the LED remains on with detached ionization chamber
replace the Diamentor.
- If the LED goes off with a disconnected ionization chamber, the
fault is located in the cable or in the chamber
- Disconnect the ionization chamber on the collimator side to see
if the fault is located in the cable.
No dose area product value at n Check whether there is a dose reading while activating the test
system monitor. button under fluoro.
On the front panel of the Dia‐ - If there is still no reading of the dose area product value,
mentor, the power supply LED replace the Diamentor.
is on.
- If there is a reading of the dose area product value, replace the
The HV LED is off ionization chamber or the cable.
n With the 1-channel Diamentor K1-S , all signals of plug X1 are
parallel available at X2.
Dose area product value at Check the Angiomatic configuration and save the configuration
system monitor shows “???”. again.
There are no dose counts dur‐ n Check whether the Diamentor pulses are available at the Diamen‐
ing the calibration procedure tor control unit X1/2 Pin 6 and 1 and at the SIRC board (Plug X7
(with activation of test but‐ between Pin 6 and 1).
ton). Replace the Diamentor control unit.
Wrong dose area product val‐ n Perform a new adjustment.

ue on system monitor

Fig. 14: K1-S Diamentor
PTW DIAMENTOR K1-S
DK1/2.X1
Stecker 1
OUTPUT1
On HV-Error
Cal
Chamber
DK1/2.X2
Stecker 2
OUTPUT2
Test
SUPPLY
DK1/2.X3
Stecker 3

Fig. 15: Diamentor K2-S
PTW DIAMENTOR K2-S
DK1/2.X1
Stecker 1
OUTPUT1
On HV-Error
Cal A
Chamber A
DK1/2.X2
Stecker 2
OUTPUT2
Cal B
Chamber B
Test
SUPPLY
DK1/2.X3
Stecker 3
Tab. 6 DK 1/2.X1 plug / Pin allocation
Pin No. Description

1 RS422 pulse signal - output high
2 High voltage error output signal (low active)
3 Ground output signal
4 Reset - In - low
5 Power supply ground
6 RS422 pulse signal - output low
7 Reset - out
8 Reset - In - high
9 +24V DC power supply

Tab. 7 DK 1/2.X3 Plug / Pin allocation
Pin No. Description

2 Pulse signal - high
3 Shielding
4 Shielding
7 Shielding
8 Pulse signal - low

2.11 Measurement Examples
2.11.1 SIRC Board in RTC (Realtime Computer)

Fig. 16: Fluoro pulse
(1) X-RAY signal (this signal is generated if 75% of the nominal tube voltage is present)
(2) STRT_INV (this is the start and stop signal for the high voltage inverter circuit)
(3) IT_FRQ (this is the actual tube current signal after U/F conversion)
_______________________________________________________________________

Fig. 17: Exposure pulse with dose frequency

AXCS 3 45
3.1 ACXS Problem Description

There is no communication to any n Do the AXCS test ( AXCS TEST / Page 49). This test is
AXCS node. available in the service UI under “Test tools”.
n Do a check of the error log. Error messages are expected
for this group of errors.
n Do a check of the RTC power supply by using the Wiring
Diagram.
There is no communication to one n Do a check of the physical connections

AXCS node. - For more advanced troubleshooting, connect the cable
to another switch port.
n Check whether the node is accessible with a ping com‐
mand ( PING / Page 291).
n If the node works at another port, replace the switch.
n If the node is not accessible on any port, continue trouble‐
shooting for the node component.
There is no communication to an ECC n Do a check of the error log. Error messages are expected
module. for this group of errors.
n Do a check of the physical connections at the ECC, ULI
board, and RTC switch.
n For more detailed troubleshooting, connect the ECC to an‐
other switch port.
n Continue troubleshooting using the ECC Troubleshooting
Guide.
There is no communication to a data n Do a check of the error log. Error messages are expected
display. for this group of errors.
n Do a check of the physical connections at DDIS and the
RTC switch.
n For more detailed troubleshooting, connect the DDIS to
another switch port.
n Continue troubleshooting using the ECC Troubleshooting
Guide.
There is no communication to the RTC n Do a check of the error log. Error messages are expected
(but ECC and DDIS are OK) for this group of errors.
n Do the AXCS test ( AXCS TEST / Page 49).
n Use the ping command to make sure the connection with
the RTC is functional( PING / Page 291).
n Reload the RTC software.

46 3 AXCS
3.2 AXCS General Info

Every server has its own ID which is derived from the low order byte of the TCP/IP address.
Each computer system shall have exactly one server and has to determine the server ID
independently. The server IDs are always different from the AP IDs. The range is 01 to FF.
3.2.1 Servers on the AXCS network

Tab. 8 AXCS Servers and IP nodes
Server name IP Node: Remarks

RTC A 10.1.1.2
RTC B 10.1.1.3
AXIS IVS 10.1.1.4 Image Visualization System
AXIS IAS plane A 10.1.1.16 Image Acquisition System Plane A
AXIS IAS plane B 10.1.1.17 Image Acquisition System Plane B
ECC_1 (normally at table): 10.1.1.5
ECC_2 (normally at trolley): 10.1.1.6
ECC_3 (normally at control room) 10.1.1.7
DDIS 1 10.1.1.8
DDIS 2 10.1.1.9
Physiological station 10.1.1.10 Cathcor, Sensis
Workplace (3D Angio) 10.1.1.11 Syngo X Workplace (Leonardo)
Voice Control 10.1.1.12
NIOBE 10.1.1.15 also used for particle therapy
Mediguide/CAS 10.1.1.18 also used for particle therapy
 IP Node: Refer to the Wiring Diagram
3.2.2 Components of the AXCS Net

Tab. 9 AXCS main stations
Main AXCS stations Description ID (hex)

ACS_SCU Stand Control Unit 11
ACS_CCU_A Collimator Control Unit A 15

AXCS 3 47

ACS_CCU_B Collimator Control Unit B 16
ACS_ACU_A Acquisition Control Unit Plane A 21
ACS_ACU_B Acquisition Control Unit Plane B 22
ACS_DDIS_A Instance of DDIS operating on IAS_A 26
ACS_DDIS_B Instance of DDIS operating on IAS_B 27
ACS_ANG_A Angiomatic Plane A 35
ACS_ANG_B Angiomatic Plane B 36
ACS_3DQUANT 3D Quant application 37
ACS_IVS Image System 40
ACS_IAS_A 42
ACS_IAS_B 43
ACS_MANA Magnetic Navigation System for catheters 44
ACS_PHYSIO Sensis 46
ACS_PHYS_STATION Interface of Cathcor 47
ACS_WORKSTATION Optional XWP or Syngo workplace 48
ACS_PT particle therapy system (PT) 4A
ACS_3DA 3D Angio application 4B
ACS_3DCALIB 3D calibration and service functions 4C
ACS_IPILOT iPilot 4D
ACS_WS2 2. Workstation 4E
ACS_WCU Wide screen Control Unit (part of RTC A) 4F
ACS_MDG Mediguide system, Carto XP 50
ACS_ECC_1 Examination Control Console No. 1 51
ACS_VOICE voice control 54
ACS_CAS CAS application 55
ACS_DDIS_1 Data display No. 1 56
ACS_DDIS_2 Data display No. 2 57
ACS_DIS_A NLS support for message lines (plane A) 58

48 3 AXCS

ACS_DIS_B NLS support for message lines (plane B) 59
ACS_UIP default AP-ID of user interface platform 5E
ACS_REP Reporter 60
ACS_PMS Service Software Main Process 61
ACS_ACSOS_1 AXCS Analyzer Tool 62
ACS_ACSOS_2 AXCS Analyzer Tool 63
ACS_SFS support functions for PMS 65
ACS_CSF_1 Common Software Functions (part of RTC A) 66
ACS_CSF_2 Common Software Functions (part of RTC B) 67
ACS_IASD_A diagnostic IAS_A 68
ACS_IASD_B diagnostic IAS_B 69
ACS_IVS diagnostic IVS 6A
reserved 70
ACS_SYC System Controller (part of RTC A) 71
ACS_COM_IF communication interface to external systems,
74
Cathi, ALCIP
3.2.3 Non-AXCS Components on the AXCS network

There are non-AXCS devices/components connected to the AXCS network. They have IP
addresses that are specified and are not available for other uses. These devices/compo‐
nents do not communicate using AXCS protocol.
Tab. 10 Non-AXCS Components on AXCS network
Device/Component IP Node: Remarks

Name
ECC 10.1.1.100 Default when not yet configured
DDIS 10.1.1.102 Default when not yet configured
Multi Display Manager 10.1.1.103
MLC 10.1.1.104 Controller, Artis zee Cockpit
Managed switch 10.1.1.120 for Web-based GUI management, see ( Man‐
aged Network Switch / Page 142)

AXCS 3 49
Device/Component IP Node: Remarks

Name
Kuka robot control 10.1.1.129 KPC
Surgery table (Trumpf) 10.1.1.130
3.2.4 AXCS Switch

The components are connected anywhere on the connector panel.
One LED is assigned to every connection. If the LED lights up, a physical connection be‐
tween the nodes exists (Link Pulse). If intermediate blinking can be seen, it can be as‐
sumed that data are being transmitted through the connection.
For Web-based management of the AXCS switch, see ( Managed Network
Switch / Page 142).
3.2.5 Testing the Network
3.2.5.1 AXCS TEST

Prerequisite for the test:
n A service session is opened.
Select Test Tools , in the left menu list select AXCS Test.
With selection of the AXCS tests, a new frame is made using all AXCS components in the
system. The AXCS test requests the status of all AXCS components in the system. It shows
the status from the clients (Turn on, Turn Off, Ready, Not Ready) and the status from the
AXCS server (connected, disconnected).

50 3 AXCS
Fig. 18: AXCS Diagnostics
3.2.5.2 Network Test

With the Ping command, it is possible to do a check whether the nodes are reachable and
alive.
The ping instruction checks network connections to one or more remote hosts. ICMP Echo
packets are transmitted to the host, whereby echo response packages are expected as a
response. Ping waits up to 1 s after each transmitted package and outputs the number of
transmitted and received packages.
Each received package is compared with the transmitted message. The standard is, 4
echo packages with 64 bytes of data each (a repeating upper-case letter sequence) are
transmitted.
You can use the ping utility program to test the host name and the IP address of the host.
If the IP address is acknowledged, but sometimes not the host name, a name analysis
problem exists. Make sure in this case that the queried host name is in the local file of
HOST or in the DNS database.

CAN 4 51
4.1 CAN Communication and Components

Every CAN branch line has to be terminated at both ends of the line with a termination
 resistor (120 Ohm). This is done with a termination plug or jumpered on a board. If this
is not observed, communication reliability will be reduced, sporadic errors may occur or
the communication will not work at all.
Tab. 11 CAN Problem description

There is no communication to one CAN n Check the error log. Error messages are expected for
node. this group of faults.
n Check whether the control modules are configured
for the correct location (e.g. table, control room, trol‐
ley).
n Check whether the Node ID and, if applicable, the
communication Baud rate setting is ok.
n Check the voltage supply and the cabling.
n Reload the software to the CAN node.
n Check the problem listing for a more detailed prob‐
lem description.
n Use the CANNET Tool to determine whether a CAN
node is failing to respond ( CANNET Bus
Test / Page 56).
There is no communication to all CAN no‐ This problem can be caused by any component in the
des located in the same branch. branch.
n Check whether the cable connections are properly
seated.
n Disconnect /bypass the CAN components one by one
from that branch.
Make sure that the termination is always OK!
n Use the CANNET tool to determine whether the CAN
node is now responding ( CANNET Bus
Test / Page 56).

52 4 CAN

There is no communication to any CAN n Check the error log. Error messages are expected for
node. this group of faults.
n Check whether the RTC SW is in the application mode.
To do this, call up the version check and verify that
the RTC is reporting its current SW version.
n Check whether the 24 V is present on the RTC con‐
nector panel at X30 (pin 1 to pin 2)
n Check whether the 24V_OK LED at the top of the RTC
connector panel is ON (green)
n Check whether the SIRC is loaded. The display shows
00 after power-on.
n Reload the RTC software
n Check the error log. Error messages are expected for
this group of faults.
n Replace the SIRC board.
Sporadically there is no communication to n Check the event log for AX_CCU error 202 “VCI Driver
any CAN node. Error“ (App log/Warning/Developer)
- The absence of VCI Driver Error is a good indication
that the problem is on the SIRC (defective board,
cabling or connectors).
- This message is reported when the System, RTC, or
a CAN-device is powered On/Off. These can be ig‐
nored when caused by service actions.
- When the System , RTC, or CAN-device is not pow‐
ered On/Off, this message indicates a problem with
the CAN-bus (cable, connector, or CAN-device).
n Check the CAN branch line termination.
- Remove the CAN connectors labeled "in" on the
SIRC board of RTC A and the connectors labeled
"out" on the SIRC board of RTC B and measure the
resistance between pins 2 and 7. The expected
reading is 120 Ohm with about 15% tolerance.
n Check the CAN cables and sub-D connectors.
n Oscillographic CAN activity level measurement (ap‐
prox.2 V [1.5 - 3 V] differential)
( trace/Fig. 19 Page 55)
( trace/Fig. 20 Page 55)
A software download to the PUD is not n Check the 7-segment display status from D600, con‐
possible. tinue TSG Polydoros A100.
n Check the cabling and connector panel in the PUN
cabinet.

CAN 4 53

There is no communication to a control n Check the error log. Error messages are expected for
module. this group of faults.
n If there is at least one LED lit up on the control mod‐
ule, the CAN connection is ok. Continue troubleshoot‐
ing for the UI control modules.
n Check the 24V supply voltage to the module. There is
a fuse located on the ULI board to which the module
is connected (F5, F6, F7).
n Check the physical connections from the SIRC board
to the modules. Use the wiring diagram.
n Make sure that the unused CAN connectors are equip‐
ped with the correct termination plug.
n Check the CAN branch line termination.
- Remove the CAN connectors labeled "in" on the
SIRC board of RTC A and the connectors labeled
"out" on the SIRC board of RTC B and measure the
resistance between pins 2 and 7. The expected
reading is 120 Ohm with about 15% tolerance.
n Check whether the RTC SW is in the application mode;
to do this, call up the version check and verify that
the RTC is reporting its current SW version.
n Check the node ID setting after replacing a control
module (e.g. TCM).
n If the control module was replaced with another one,
the node ID has to be set and a new download is re‐
quired.
It is NOT possible to connect a Control Module straight to the RTC since there is no power supply at
the CAN connectors on the SIRC board.
There is no communication to a motor n Check the error log. Error messages are expected for
controller module. this group of faults.
to the controller. Use the wiring diagram.
n Try to reload the motor controller software. If this can
be done successfully, CAN communication is ok. Con‐
tinue troubleshooting for the particular drive (Stand
or Table TSG).

54 4 CAN

There is no communication to an ULI n Check the error log. Error messages are expected for
board. (This also means that there is no this group of faults.
footswitch control and no injector control) n Check whether the Node ID and, if applicable, the
communication Baud rate setting are ok.
to the ULI board. Use the wiring diagram
n Try to reload the ULI software. If this can be done suc‐
cessfully, CAN communication is ok. Continue trou‐
bleshooting for the ULI board.
n Replace the ULI board. (To be on the safe side, it is
possible to replace the ULI boards based on the trou‐
bleshooting results).
There is no communication to a power n Check the error log. Error messages are expected for
unit (PUD). this group of errors.
to the PUN. Use the wiring diagram.
n Check the cabling and connector panel in the PUN
cabinet.
n Try to reload the PUN software. If this can be done
successfully, CAN communication is ok. Continue us‐
ing the PUD troubleshooting guide.
n If a D600 board is replaced, check for the correct
node ID jumper settings on the board.
Sequence of the CAN download
4.1.1 CAN Measurement Examples

CAN 4 55
Fig. 19: CAN activity with correct termination
Fig. 20: CAN activity without proper termination

56 4 CAN
4.1.2 Introduction to Controller Area Network

CAN is a serial bus system especially suited for networking "intelligent" devices as well as
sensors and actuators within a system or sub-system.
The attributes of CAN are:
CAN is a serial bus system with multi-master capabilities. In other words, all CAN nodes
are able to transmit data and several CAN nodes can request the bus simultaneously. The
serial bus system with real-time capabilities is the subject of the ISO 11898 international
standard and covers the lowest two levels of the ISO/OSI reference model.
In CAN networks, subscribers or stations are not addressed in the conventional sense,
rather, prioritized messages are transmitted. A transmitter sends a message to all CAN no‐
des (broadcasting). Based on the identifier received, each node decides whether or not it
should process the message. The identifier also determines the priority that the message
has in competition for bus access.
4.1.3 CANNET Bus Test
4.1.3.1 CAN Bus Test

To start the CAN bus test, the RTC has to be in the download mode.
That is why this test is located under Configuration > Artis System > SWM RTC
Skip the RTC download and use the “>” button to get to the CAN download page.
Fig. 21: Selection of CAN download mode

CAN 4 57
Fig. 22: CAN BUS test
When the CAN is download or the CAN Bus Test is finished, the RTC has to reboot again
into its normal mode. This takes place automatically when the button “Finish” is pressed.

58 5 Flat Panel Detector
5.1 Troubleshooting the Flat Panel Detector

Go to the FD Troubleshooting Guide ( FD with System SW VC14 / AXA4-110.840.04).

Image Quality Problems 6 59
6.1 Noisy Image
 Please note that the DDO and edge enhancement window settings can lead to a differ‐
ent appearance.
Problem Links or solution

Noisy Image n Check Dose ( System Dose Adjust‐
ment / AXA4-000.842.08) and Skin Dose adjust‐
ment ( Skin dose adjust‐
ment / AXA4-000.842.08)
n Start a new DEXI adjustment
- with the 20 x 20 FD ( DEXI Adjust‐
ment / AXA4-000.842.08)
- with the 30 x 40 FD ( Dexi adjust‐
ment / AXA4-000.842.08)
n Verify OGP settings (K-Factor, EVE, and so on)

60 6 Image Quality Problems

Fig. 23: Chip-related noise n If there are line structures visible on‐
ly in individual MAPIX, this is called
chip-related noise
n In the sample image, there is a mag‐
nified view of one MAPIX with chip-
related noise and one MAPIX with
the normal structure
n These kinds of faults are not easy to
see and may be visible only in low
dose fluoroscopy
n Start a new FD calibration ( FD Cal‐
ibration / AXA4-110.842.04).
Normal MAPIX MAPIX with

Chip correlated
noise

6.2 Geometric Disturbances
ent appearance.
Problem Links or Solution

Fig. 24: MAPIX structure (1) n Use the "Block Radiation" function
and acquire a scene with dark im‐
ages. Here it is possible to see FD de‐
fects without disturbances from the
X-ray image.
n Start a new FD calibration ( FD Cali‐
bration / AXA4-110.842.04).


Fig. 25: MAPIX structure (2) n Start a new FD calibration ( FD Cali‐
bration / AXA4-110.842.04).


Fig. 26: MAPIX structure (3) non-compensated image n Start a new FD calibration ( FD Cali‐
bration / AXA4-110.842.04).


Fig. 27: Incorrect offset image Sporadic overlay of typical detector struc‐
tures.
n The problem disappears after a radia‐
tion break of min. 15 seconds.
 An incorrect (old) offset image
was used.
After the next automatic offset
calibration, which takes place
automatically during a radia‐
tion break, an up-to-date com‐
pensation image is available
and the problem will be gone.
This could happen if there was a reset
of the DIPP shortly before.
Check the event log for ACU messag‐
es just before this appearance.


Fig. 28: Incorrect calibration result “GainIma.xxx” The FD calibration always adds new de‐
fects that are found to the existing list. If
the total perhaps includes too many de‐
fects than actually exist, it is recommen‐
ded to delete all defects from of the cali‐
bration result files.
The following procedure will create a
new (empty) calibration file.
n Use the reset button in the action bar


Fig. 29: Removable grid not completely engaged In this case, the removable grid is not
completely engaged.
This is why the bottom part of the image
shows areas of different densities.


Fig. 30: Defective Viper board 1. The defective area is not of the size
and position of a Mapix.
2. The edges are very sharp and there is
no DDO effect visible.
 So it is not an FD problem!
n Carry out the RTC Dipp FRU tests,
which are available under Test Tools
> Hardware tests.
- Get a new COPRA board and find
out which of them is the defective
one by changing them one after
the other.

6.3 Spots
ent appearance.

Fig. 31: MAPIX structure and pixel (cluster) defects n Defective pixels may also appear as
blinking pixels.
bration / AXA4-110.842.03)
n Sometimes there is only a slight
chance to catch them during the FD
calibration procedures. Use "manual
calibration" described at FD adjust‐
ment procedure ( Manual FD Cali‐
bration / AXA4-110.842.03)

6.4 Lines
ent appearance.

Strongly visible line noise 1. Perform detector calibration again and check
Note: Even though line noise correction is ac‐ whether the problem is still present. Go to the
tivated, strong line noise can be seen. This is next point if still present.
probably due to chip-related noise in the de‐ 2. Check the detector power supply voltages. If out
tector, which spoils the line noise correction of specification, replace the detector power sup‐
or is due to poor calibration. ply. Go to the next check if no error is found.
3. Check the cooling water temperature. If above
(ambient_temperature - 2˚C), replace the cooling
unit. Go to the next check if no error is found.
4. Check the cooling water flow. If the flow is < 0.5 l/
min, replace the cooling unit if the problem is the
cooler. Replace the detector, if the detector is
clogged. Go to the next check if no error is found.
5. Replace the detector ( 20x20 FD and 30x40
FD / AXA4-110.841.02)


Fig. 32: Compensated image with new line defects n Start a new FD calibration ( FD Cali‐
bration / AXA4-110.842.03)


Fig. 33: Lines and spot defects Defective pixels in the DRZ may be the
reason for gray lines as shown in this
image.
Defective pixels in the DRZ may cause
incorrect line offset compensation.
Blinking pixels in the DRZ may cause
sporadic line structures in the image.
bration / AXA4-110.842.03)
n This could also be a temperature-re‐
lated problem, make sure that the
system cabinet has sufficient air
cooling.
Spot
Line


Fig. 34: Defective lines Line structures in groups of 24 lines or
multiples of 24 can be clearly assigned to
the FD.
If a line is more than 20% defective, the
entire line is marked as a defective line.
bration / AXA4-110.842.03)
n Replace the FD if the calibration re‐
sult is unacceptable ( 20x20 FD and
30x40 FD / AXA4-110.841.02)


Fig. 35: Line driver problem Line structures in one half of the FD can
be clearly assigned to the FD Thalassa
module.
n Perform a new FD calibration ( FD
Calibration / AXA4-110.842.03)
n Replace the FD if the calibration result
is unacceptable ( 20x20 FD and
30x40 FD / AXA4-110.841.02)


Fig. 36: Ablation active Measures to avoid interference caused by ablators
There is no possibility to completely avoid such types
of interference, but there are measures to minimize
the effects.
The major step is to route the cables of the inactive
electrode and the catheter as far as possible away
from the detector and to avoid looping the cables
around the detector.
Recommendations:
1. Move the ablator to the foot end. In this case, the
inactive electrode and the catheter will be routed
away from the detector automatically.
2. Route the cable of the inactive electrode on the
right site of the patient under the patient mat‐
tress.
3. Route the cable of the catheter directly to the
ablator (located at the foot end of the patient)
and avoid any loops at the detector.
Additional points having an effect on the amplitude
of the interference:
1. The amplitude of the interference also depends
on the position of the SID, which means the SID
should be as far as possible away from the patient
as well as from the ablator catheter tip and ca‐
bles.
2. In addition, there is also a major effect from the
X-ray dose that is used. The higher the X-ray dose,
the lower the interference that is applied by the
ablator.

6.5 Non-structured Disturbances
ent appearance.

Structures appear when performing long flu‐ Procedure:
oroscopy runs 1. Perform detector calibration again and check
Note: When performing long (> 10 min) low- whether the problem is still present. Go to the next
dose fluoroscopy runs without releasing the point if still present.
foot pedal, structures (Mapixes or Thalassas 2. Check the detector power supply voltages. If out of
or other) appear. This is probably due to specification, replace the detector power supply.
poor offset stability of the detector or to Go to the next check if no error is found.
poor calibration.
3. Check the cooling water temperature. If above (am‐
bient_temperature - 2˚C), replace the cooling unit.
Go to the next check if no error is found.
cooler. Replace the detector, if the detector is clog‐
ged. Go to the next check if no error is found.
FD / AXA4-110.841.02)

Structures at high doses Procedure:
Note: Structures from Mapixes or Thalassas 1. Perform the detector calibration again and check
are visible in bright parts of the image. This whether the problem is still present. Go to the next
is probably due to poor detector linearity be‐ point if still present.
tween neighboring channels or to poor cali‐ 2. Check the detector power supply voltages. If out of
bration specification, replace the detector power supply.
FD / AXA4-110.841.02)


Visible Mapixes or Thalassas Procedure:
Note: If the user complains of visible struc‐ 1. Check the detector power supply voltages. If out of
tures under conditions other than those de‐ specification, replace the detector power supply. Go
scribed in previous points. to the next check if no error is found.
FD / AXA4-110.841.02)

Fig. 37: Unstable read-out amplifier n Start a new FD calibration ( FD Cali‐
bration / AXA4-110.842.03)


Fig. 38: Non-compensated image with Mapix internal structure n Start a new FD calibration ( FD Cali‐
bration / AXA4-110.842.03)
30x40 FD / AXA4-110.841.02)


Fig. 39: Saturation of read-out amplifiers n Check dose rate adjustment ( Sys‐
tem Dose Adjust‐
ment / AXA4-000.842.06)
bration / AXA4-110.842.03)


Fig. 40: Defective upper line driver n Start a new FD calibration ( FD Cali‐
bration / AXA4-110.842.03)
30x40 FD / AXA4-110.841.02)

Fig. 41: Column noise n Start a new FD calibration ( FD Cali‐
bration / AXA4-110.842.03)
30x40 FD / AXA4-110.841.02)


Fig. 42: Defect after damage by cooling liquid n Start a new FD calibration ( FD Cali‐
bration / AXA4-110.842.03)
30x40 FD / AXA4-110.841.02)

6.6 Excessive Environmental Values
ent appearance.

Microphonic disturbance may be caused by an out-of-bal‐ Remove tube mechanically from C-bow
ance anode of the X-ray tube or by an FD which is over- to verify the source
sensitive to shock and vibrations
Noise lines could be caused in some circumstances from See "procedure to find ground loops"
ground loop connections from our system to building ( Procedure for Finding Ground
ground. See procedures to find ground loops Loops / AXA4-110.840.04)
Noise lines could be caused in some circumstances from Exclude external effects
external device, for example air handlers.
Humidity condensation may cause damage to the scintilla‐ Repeat calibration
tor. Areas of different density may be visible in an image.


Fig. 43: Temperature island Temperature differences during calibra‐
tion may show structures such as those
in the following 2 illustrations.
These structures could be normal with
DR modes below 0.500 μGy.
Allow the FD to stabilize the internal
temperature and start the calibration
again.
Fig. 44: Temperature island with annotation n Start a new FD calibration ( FD Cali‐
bration / AXA4-110.842.03).


Fig. 45: Defect after damage by cooling liquid Too many defects.
n Replace the FD.

6.7 Digital Image Preprocessing Samples

Digital Image Preprocessing samples Processing Steps
Fig. 46: Raw data image from FD with test phantom Raw image from FD
Gigalink Input at FDR board


Fig. 47: After Pixel Offset Compensation After the pixel offset correction
Subtraction of an offset picture from an
input image.
The noise in the offset picture is reduced
using a "sliding weighted average calcu‐
lation"


Fig. 48: After line noise correction Line Noise Correction (LNC)
Estimated offset for the lines is formed
from the left and right Dark Reference
Zone (DRZ)
Subtraction for every line with fixed val‐
ues


Fig. 49: After Pixel Gain Correction Pixel Gain Compensation
Pixel-by-pixel multiplication with gain im‐
age from the last calibration result


Fig. 50: After Defective Pixel Interpolation Defective Pixel Interpolation
Restoration of defective pixels from the
surrounding area.
Weighted average from up to 24 immedi‐
ately surrounding pixels

Power Distributor 7 89
7.1 Troubleshooting the Power Distributor
 Use the wiring diagram for troubleshooting the power distributor (fuse table / mains dis‐
tributor)
Tab. 12 Troubleshooting the line power distributor
Problem Links and Solution

Mains line connection Check F1 /28A slow-blow fuse
Power Supply for LUST stand Check F2/16A slow-blow fuse
Power supply for collimator A+B excluding M69 Check F3/10A slow-blow fuse
Power supply for LUST table + RCU Check F4/6A slow-blow fuse
Power supply for MCM table Check F5/6A slow-blow fuse
Power supply for AXIS / ACE / Displays Check F6/10A slow-blow fuse
Power supply for TEE Check F7/10A slow-blow fuse
Power supply for RTC A, M102 A/B, M103, 2nd DCS Check F8/10A slow-blow fuse
Power supply for RTC B, DCS, DDIS Check F9/10A slow-blow fuse
Power supply for injectors (A,B,C) Check F10/10A slow-blow fuse
Power supply 24V RTC Check F11/3A slow-blow fuse
Temperature sensors Check F12/1A slow-blow fuse
FD cooling unit A/B Check F13/6A slow-blow fuse
X-ray cooling unit A/B Check F14/6A slow-blow fuse

There are 2 line power distributor models used in VCxx systems.
Use the table matching the model.
Tab. 13 Troubleshooting with D90 board indications (new style line power distributor)
10359152 - Line power distributor

10141140 - D90 board
LED Problem Links and solutions
V1 off D90 internal 24 VDC is missing Check the F1 / 4A slow-blow fuse
V2 off Collimator A power is missing Check F15 / 6.25 A fuse
LED on the M69 power supply is missing Check the F8 slow-blow fuse
V3 off Collimator A power is missing Check F16 / 6.25 A fuse
LED on the M69 power supply is missing Check the F8 slow-blow fuse

90 7 Power Distributor

10141140 - D90 board
LED Problem Links and solutions
V7 off RTC_A 24 VDC is missing Check the F7 / 3.15 A slow-blow fuse
V8 off RTC_B 24 VDC is missing Check the F8 / 2.5A slow-blow fuse
V9 off Diamentor 24 VDC is missing Check the F9 / 500mA slow-blow fuse
V12 off ULI1 24 VDC is missing Check the F12 / 4A fuse
V18 off SSFD A/B power supply is missing Check F18 /4A slow-blow fuse
V19 off SSFD (not used) power supply is missing Check the F19 / 4A slow-blow fuse
V20 off 24 VDC is missing (supplies F7, F8) Check the F20 / 6A slow-blow fuse
V21 off 24 VDC is missing (supplies F9, F12) Check the F21 / 6.25A fuse
V23 off 24 VDC is missing (supplies F15, F16) Check the F3 / 12A fuse
Tab. 14 Troubleshooting with D90 board indications (old style line power distributor)

4775990 - D90 board
LED Problem Links and Solutions
V1 off D90 internal 24 VDC is missing Check F1 /4A slow-blow fuse
V2 off Collimator A 35 VDC is missing Check F2 /3.2A slow-blow fuse
LED on the M69 power supply is off Check F8 slow-blow fuse
V3 off Collimator B 35 VDC is missing Check F3 /3.2A slow-blow fuse
LED on the M69 power supply is off Check F8 slow-blow fuse
V4 off Reserve voltage is missing Check F4 /4A slow-blow fuse
V7 off RTC_A 24 VDC is missing Check F7 /3.2A slow-blow fuse
V8 off RTC_B 24 VDC is missing Check F8 /2.5A slow-blow fuse
V9 off Diamentor 24 VDC is missing Check F9 /1A slow-blow fuse


4775990 - D90 board
LED Problem Links and Solutions
V12 off ULI1 24 VDC is missing Check F12 /1A slow-blow fuse
V13 off ULI2 24 VDC is missing Check F13 /3.2A slow-blow fuse
V14 off ULI3 24 VDC is missing Check F14 /3.2A slow-blow fuse
V15 off Collimator A power supply is missing Check F15 /6A slow-blow fuse
V16 off Collimator B power supply is missing Check F16 /6A slow-blow fuse
V18 off SSFD A/B power supply is missing Check the F18 / 4A slow-blow fuse
V19 off not connected n.a.
V20 off 24 VDC is missing (supplies F7, F8) Check F20 /6A slow-blow fuse
V21 off 24 VDC is missing (supplies F9-F12) Check F21 /6A slow-blow fuse
Tab. 15 Power ON/OFF

The system cannot be turned on Check the V1 and V30 LEDs. Both have to be on.
When the ON button is pressed, the yellow V33 LED
indicates the status "ON_PRESSED".
Continue troubleshooting using the "power on/off"
wiring diagram .
Continue troubleshooting using the power on circuit
image system (use wiring diagrams).
The system cannot be turned off Check the V1 and V30 LEDs. Both have to be on
shortly before the power is switched off.
When the OFF button is pressed, the yellow V32 LED
indicates the status "OFF_PRESSED"
If the shutdown procedure was initiated from the
software user interface and the signal “switched off”
is not received at the D90 board, continue trouble‐
shooting in the image system with the ACE unit.
Continue troubleshooting using the "power on/off"
wiring diagram

 It is recommended to use the "On/off switch circuit control" wiring diagram for trouble‐
shooting this component.

7.2 Power Distributor (photo)

Fig. 51: Power distributor - 10359145 (VC13/14) Fig. 52: Power distributor - 10141144 (VC12)
 CAUTION
Voltages of up to 24 V can be present on the brown connectors.
Voltages from 110 to 220 V can be present on the white connectors.
 Do not touch the connectors.

7.3 D90 Board Component of the Power Distributor

With the system on, all LEDs have to be on, except for the first 4 LEDs.
Fig. 53: D90 board (10141140) of power distributor (10359145)

Fig. 54: D90 board (4775990) of power distributor (10141144)

7.4 RCU Board

1. Checking the Error Log for Service-relevant Messages
2. Check of the power supply for the power distributor (present on the X300, see corre‐
sponding Wiring Diagram)
3. Check the status LED on the RCU board.
4. Check the fuses; if applicable, replace them.
5. Check of the voltages on the rear power supplies (24 VDC and 28 VDC; adjustment is
possibly needed)
6. Start the RTC software manager in local service and perform a CAN download to these
components.
Fig. 55: RCU B Board overview
7.4.1 Overview of LEDs
LED Color Definition

V14 Green 24VDC brake power supply for LUST frequency converter
LED is on when the brakes are controlled.
V39 Green DMG_DLY; Delay dead man's circuit; delay during the
switch-off routine approx. 1 second to make braking the ro‐
bot possible.
LED is on when active
V51 Green Velocity - Orientation Tool (C-Arm, acceleration and direc‐
tion) monitoring
LED goes on only in manual mode
V37 Green Free motion active
LED goes on in the normal mode

LED Color Definition

V30 Green X-radiation
LED is on when X-radiation is ON
V35 Green Quick stop
LED is on when Quick stop is NOT active
V36 Green Dead man's circuit / DMG
LED is on when DMG is active
V40 Green Emergency Stop
LED is on when NOT active
V47 Green Contact safety device / robot switch strips, NOT C-Arm
LED is on when NO switch is active
V48 Green 24 VDC power supply
LED is on when the voltage from the 24VDC power supply is
OK, 24 VDC ± 3,5 %
V49 Green 28 VDC power supply
LED is on when the voltage from the 28VDC power supply is
OK, 28 VDC ± 3,5 %
V38 Green Quick stop override
LED is on when Override is active
7.4.2 Overview of Fuses
Error Possible Cause

Safety circuit voltage F1/2A slow-blow fuse
FD rotation voltage F2/6.3A slow-blow fuse
Collimator rotation voltage F3/6.3A slow-blow fuse
RCU board voltage F4/2A slow-blow fuse
LUST +24 VDC logic bus voltage F5/4A slow-blow fuse
ALI 2 board voltage F6/2A slow-blow fuse
RPIF board voltage F7/2A slow-blow fuse
FD lift voltage F8/10A slow-blow fuse

7.4.3 Overview of Connectors
Connec‐ Connection / Task

tor
X1 24VDC and 28VDC from power supplies
X11 KUKA control cabinet, CI3 Tech Board (Emergency Stop and
Quick Stop)
X12 KUKA control cabinet I/O board (e.g. DMG)
X300 ALI 2 board controls K1
X40 Safe RDW / free motion / Safe Stop / Velocity - Orientation Moni‐
toring Tool (C-Arm acceleration, speed and direction monitor‐
ing)
X400 Power supply for ALI 2 board (24 VDC)
X500 and LUST frequency converter (28 VDC)
X600
X41 RTC (X4) Safety Interface (safe stop)
X42 ALI 2 Board Safety Interface
7.4.4 Relay
Relevant relays on the RCU board:
Relay Definition
K4 Quick stop override; when the override
switch is pressed on the RCM, this relay
switches
K5 Contact safety device is controlled by
the RPIF board
7.4.5 Power Supplies

The power supplies for the power supplies (24 VDC and 28 VDC) are powered from the
MD (400 VAC). The 24 VDC power supply feeds the logic; the 28 VDC power supply feeds
the LUST frequency converter with voltage.
The output voltage can be adjusted using a potentiometer on the power supply (see the
Replacement Instructions).

LED Definition
Green Normal status, output voltage is present
Red ““Overload”
Possible causes:
n Short circuit at the input
n Short circuit at the output
n Power supply defective

100 8 Service Software Functions
8.1 Service Software Home Menu

Fig. 56: Syngo service homepage
The service user interface corresponds to the standard Syngo service UI. Here, the follow‐
ing functions have been taken unchanged from Syngo:
n Backup and Restore
n DICOM Tests
n File and Image Tools
n Auto Report
n Utilities
n Reports
n Help
n Software Distribution
The following syngo functions have been adapted to the requirements of Artis zee:
n Configuration
n Tune Up
n Report Generation
n Control
n Quality Assurance

Service Software Functions 8 101
n Test Tools
n Event Log
All standard service functions can be performed in this user interface. The Service UI is
remote access capable. All functions that do not generate radiation or that trigger a unit
movement can be performed via remote.
The following functions currently are not accessible via remote:

n Configuration > Artis System
- RTC SWM
-

SWM Large Display
- SWM Trumpf table
n Configuration > Artis Components
- MDM (Large Display)
- SMfit (Large Display)
There are also what are called “Factory Diagnostics” for the image system. Here, even
more diagnostic capabilities for the image system are integrated. First, the Syngo applica‐
tion must be ended to use the factory diagnostics.

8.2 Configuration
See the Configuration Guide ( Configuration Main Menu + System Op‐
tions / AXA4-000.843.04).

8.3 Backup & Restore (syngo)
 Perform the “Backup” only when the System is not in “Bypass mode”
Here you can back up predefined packages and restore the packages or groups within a
package. The backup/restore location can be a local drive, removable medium (CD/DVD)
or network drive.

This is for the syngo Backup and Restore of the system and the configuration data.
This is not the Acronis Backup and Restore of the IVS/IAS system drives.
8.3.1 Backup
8.3.1.1 Drives
Select the drive. The archive will be written to the root of the selected drive.
n [-A-] Floppy Disk
- IVS floppy drive
n [-F-] DVD
- ACE CD/DVD burner
n [-R-] DVD
- IVS CD/DVD reader
n [-C-] FIXED
- IVS system drive
n [-D-] FIXED
- IVS database drive
n [-E-] FIXED
- IVS image pixel drive
n \\10.1.1.16\DataBackup
- IAS-A Service disk - standard network drive ( Set Network Drive / Page 107)
8.3.1.2 Packages
Select the package. For details on package content, see ( Tab. 16 Page 105)
n Clone package
n Configuration
n Exam sets
n FD data
n FileExport

n Security settings
n SW distribution
8.3.2 Restore
8.3.2.1 Drives
Select the drive. The list of archives will be read from the root of the selected drive.
n [-A-] Floppy Disk
- IVS floppy drive
n [-F-] DVD
- ACE CD/DVD burner
n [-R-] DVD
- IVS CD/DVD reader
n [-C-] FIXED
- IVS system drive
n [-D-] FIXED
n [-E-] FIXED
n \\10.1.1.16\DataBackup
- IAS-A Service disk - standard network drive ( Set Network Drive / Page 107)
8.3.2.2 Archive
Select the archive. There are 7 possible types of archives (packages) to restore. Only those
on the root of the selected drive will be listed. There can be more than 1 archive of a par‐
ticular type (e.g. different date and/or time).
The format for the archive name is:
<host name>_<system serial number>_<Package>_<Date>_<Time>_ok.ar
n host name - as configured under Configuration > (Local Host) TCP/IP Lan > (Identi‐
fication) Computer name
n system serial number - as configured under Configuration > (Local Host) Site Info>
(System) Serial No

n Package - 1 of the 7 available from Backup

- ClonePackage
- Configuration
- ExamSets
- FDData
- FileExport
- Security-Settings
- SW-Distribution
n Date - format YYYYMMDD (e.g. 20090128) Year Month Day
n Time - format hhmmss (e.g. 055845, 231056) Hour Minute Second
8.3.2.3 Groups
Select the group or groups to be restored. Multiple groups can be selected. The list of
groups depends on the archive that is selected.
Tab. 16 Restore package groups
Packages
Configuration
Exam sets
FD data
Clone package
SW distribution
Security settings
Groups
All\ X X
ecc_ddis\ecc\ X
host\axiom\ X
host\ddisxp\ X
host\pms\ X
host\rep\ X
IQAP\ X
PMS_Backup_Log\ X X X
rtc_a\acu_a\ (rtc_b\acu_b\)1 X X
rtc_a\ang_a\ (rtc_b\ang_b\)1 X
rtc_a\ccu_a\ (rtc_b\ccu_b\)1 X
rtc_a\csf_a\ (rtc_b\csf_b\)1 X
rtc_a\scu\ (rtc_b\scu\)1 X
rtc_a\syc\ (rtc_b\syc\)1 X X

Packages
Configuration
Exam sets
FD data
Clone package
SW distribution
Security settings
Groups
rtc_a\wcu\ (rtc_b\wcu)1 X
Service\Applications\CorRea\ X X
Service\Applications\MBoxIntegration\ X
Service\Applications\MPPS\ X X
Service\Applications\PatientRegistration\ X X
Service\Applications\Viewer\ X
Service\Applications\WorklistResults\ X X
Service\Database\DBOffset\ X X
Service\Database\SateliteConsole\ X X
Service\DICOM\General\ X X
Service\DICOM\HISRISNodes\ X X
Service\DICOM\ImportExportDirectories\ X X
Service\DICOM\LocalNode\ X X
Service\DICOM\LUTFiles\ X X
Service\DICOM\NetworkNodes\ X X
Service\DICOM\OfflineDevices\ X
Service\DICOM\PrintDevices\ X X
Service\DICOM\StructuredReport\ X X
Service\EPRI\Server\ X X
Service\ExternalDevices\PaperPrinter\ X X
Service\ExternalDevices\PS_LUTFiles\ X X
Service\LocalHost\Modality\ X
Service\LocalHost\MonitorType\ X X
Service\LocalHost\Routing\ X X
Service\LocalHost\SiteInfo\ X X
Service\LocalHost\Users\ X

Packages
Configuration
Exam sets
FD data
Clone package
SW distribution
Security settings
Groups
Service\Security\GSMConfiguration\ X X
Service\Service\AutoTransfers\ X X
Service\Service\Eventlog\ X X
Service\Service\FTP\ X X
Service\Service\Hosts\ X X
Service\Service\Licensing\ X
Service\Service\Mail\ X X
Service\Service\SecConfig\ X X
Service\Service\SystemMgmt\ X X
Service\TCPIP\LAN-Settings\ X X
Service\TCPIP\PersistentRoutes\ X
Service\TCPIP\RAS-Settings\ X
System_Configuration\ X
UserSettings\ X X
1. only with biplane system
8.3.3 Set Network Drive

If a network drive is configured here, it will be available as a drive selection for Backup &
Restore (syngo).
The standard network drive is \\10.1.1.16\DataBackup.
Manual entry of these fields is not required. If it is not shown, use the MountBackup_Re‐
store_Drive selection under Local Service > Test Tools > Thirdparty Tests > Mount/
Unmount Backup Restore Drive to make it available. ( Mount/unmount the backup/
restore drive / Page 141)
8.3.3.1 Share Name (\\<server>\<share>)

\\10.1.1.16\DataBackup is the standard network share and is located on the IAS-A Service
Backup Restore disk.

8.3.3.2 User Name

AxServiceUser is used to access the standard network share (\\10.1.1.16\DataBackup)
8.3.3.3 Password
(See: CS Knowledge Base ID 13982, AX PASSWORD LIST)

8.4 Tune Up
See the system adjustment instructions ( Adjustments and Final Work
Steps / AXA4-000.814.31).

8.5 Report Generation
8.5.1 General
n It is recommended to run general reports whenever a new config or adjustment is per‐
formed
n The system must be “up and running” when the “Generate Reports” tool is started, this
can be found under: Local service UI, Report Generation >
8.5.2 Generating Reports

n Select Report Generation to start the program. First, the availability of the system
components is checked and displayed.
n Activate the <Start> button from the action bar to start the process to read out the
current configuration and adjustment data from the system components.
When this process has been successfully completed, OK is displayed for each compo‐
nent.
If the report generation fails, a message is displayed which informs about the prob‐
lem. If this happens, no report is created for the faulty component and the cause of
the problem must be investigated.
Fig. 57: Generate reports (not started)

n The generated reports can be viewed by under <Reports><Component Reports> .
8.5.3 Export Reports

With this function, the reports that are created can be exported either to hard disk or flop‐
py drive.
n Select <Export Reports>
n All reports are selected as a default. It is possible to select one or more groups by click‐
ing on the desired group and holding down the Control or Shift key. Click on <START>
to export the files.
n Select <Export Medium>
Reports can be exported to floppy or hard disk.
8.5.4 Reading Out Reports

n Reports exported to hard disk can be read out in the <Reports> Viewer under <Expor‐
ted Reports> <Hard Disk>.
A new report directory is created only if the time difference between 2 exported re‐
ports is one day or more. Reports generated during the same day will show only the
most recent one. All old reports are overwritten
n Reports exported to floppy can be read out on any PC running a standard MS Windows
OS (NT Explorer, Notepad).

8.6 Control
8.6.1 Service Switches

n To select the service switches, select the path Control > Service Switches
Fig. 58: Service Switches Control (biplane)
 All service switches are set back when leaving the program.
 As soon as a test image is selected, the SS switch is automatically set to <OFF>.
Switch Description
PUN HW SS: Displays the current status of the safety switch on the D30 power unit board. The switch
has to be set to "ON" for normal operation.
SIRC Radiation Enable: Displays the current status of the service switch on the RTC SIRC connection
board. The switch has to be set to "OFF" for normal operation.
SW-SS The safety breaker is switched off in the X-ray generator power unit so
there is no power supply to the inverter and therefore no high voltage.

Switch Description
Focus Focus selection for Service Radiation

CU Filter Copper pre-filtration (collimator filter) selection for Service Radiation
Voltage [kV] Voltage selection for Service Radiation
Current [mA] Tube current selection for Service Radiation
 The selection range is automatically set, depending on the radiation mode selection (Fluoro/
Exposure).
ADR Automatic dose control, which is an Angiomatic function, can be switch‐

ed on and off.
AGC Automatic gain control of the video system can either be enabled or
switched to off, whereby it then becomes manual gain.
The manual gain setting is made in the ACU A/B Component Configura‐
tion.
AGC Testmark = The location in the image for the automatic gain evaluation can be made
AGC Dominant visible with the “On” setting.
Testimage Camera = Test patterns from the camera head can be selected (if I.I. system).
Camera Test Pattern They are used to check the entire video system.
Only with I.I. Systems When a test pattern is selected, the "SS switch" is automatically turned
off.
Please note that the window settings, DDO, AGC, Global Gain, Gamma
and edge enhancement can lead to a different appearance.
n Analog Head Pattern
The analog test pattern is fed into the video system just after the CCD
chip. It is used to check the entire video system. The test pattern dis‐
play depends on the selected frame rate. For frame rates up to 15 fps,
the pattern uses the full screen. At 30 fps, the test pattern is split ver‐
tically into two parts and the two parts are also inverted. The basic
test pattern is a trapezoid from black to white and back to black.
n Digital Head Pattern
The digital head pattern is fed into the video system behind the A/D
converter. The test pattern is a ramp from white to black.

Switch Description
Test Image CCB = Test patterns can be selected from the camera control board (located in
CCB Test Pattern the RTC)
Only with I.I. Systems When a test pattern is selected, the "SS switch" is automatically switched
off.
Please note that the window settings, DDO, AGC, Global Gain, Gamma
and edge enhancement can lead to a different appearance.
n Correction Pattern
The correction pattern is fed into the video system at the input of the
CCB board. The pattern is a ramp from black to white.
n Defective Pixel Map
The defective pixel pattern is used to see the number of defective pix‐
els of the CCD chip.
Test image FD There are several test patterns available from the FD ( Test Pattern Selec‐
With FD Systems tion for FD Systems / Page 116).
Please note that window settings, DDO, AGC, Global Gain, Gamma and
edge enhancement can lead to a different appearance.
Testimage DIPP Test patterns (ramp and level) can be selected from the video processing
boards (located in the RTC) ( Test Pattern Selection for FD Sys‐
tems / Page 116).
The <Ramp> test pattern is a combination of gray values and different
ramp signals.
DIPP test patterns will work correctly only with frame rates of <7.5 F/s
If the “level” test pattern is selected, a homogeneous image is generated.
The <Level> test pattern is a homogeneous gray pattern which is adjusta‐
ble in the service software.
The signal level can be selected with the gray level setting in the next
line.
The range is between 0 (black) and 4095 (white).
This test can be used to find out whether image artifacts are caused by
postprocessing or by the acquisition components.
When a test pattern is selected, the "SS switch" is automatically switched
off.
Please note that window settings, DDO, AGC, Global Gain, Gamma and
edge enhancement can lead to a different appearance.
Gray level The gray level for the homogeneous image can be specified.
0 = max. dark, 4095 = max. bright
Note: Appearance depends on the AGC and on the Gamma selection.
Load image from disk Test patterns from the RTC. This function can be used only when images
were previously downloaded to the RTC.
When a test pattern is selected, the "SS switch" is automatically switched
off.

Switch Description
Video Output The following outputs can be selected
n AXIS
n Graphics card/bypass monitor
n RTC disk
Save image to disk Images can be saved to RTC to memory location RTC0 ....5
Gamma Video gain characteristics. γ =1 is a linear gain.
γ =0.2 is a logarithmic gain. The value behind the Gamma is the signal
peak reduction in percent.
e.g. 1/100 means a gamma of 1 and no peak reduction.
e.g. 0.6/80 means a Gamma of 0.6 and a peak reduction of 60% of a
4095 gray value. Afterwards the signal is expanded to the maximum of
4095.
CMA Grey Value Intensity of the circle overlay for the overframing factor.
CMA Ofr. Factor Overframing factor for the circle overlay.
Global Gain It is possible to set the Global Gain to “auto” or to a fixed factor for FD sys‐
tems.
For test images set global gain to 1.
DIPP Filter 1 Factor EVE filter (extended vessel enhancement)
DIPP Filter 1 Kernel Kernel size for EVE filter
MEC inhibit “ON” will inhibit the memory effect correction.
ISY Postblanking Postblanking of the image system can be switched off to see the position
of the collimator plates.
Fluoro/Exposure defines the X-ray mode which is released with start X-ray. To activate
the control switch setting, an X-ray mode is required.
Keys in the Action Bar

n Start/Stop X-ray
Enables/ disables X-ray radiation. The name of the key will toggle, depending on the
current mode.
n Exit
Exits the Service Switches dialog box and returns to the Control window. All service
switches are reset to their default values.

8.6.1.1 Test Pattern Selection for FD Systems
Fig. 59: Normal image Normal pattern
Please note that the window settings,

DDO, AGC, Global Gain, Gamma and
edge enhancement can lead to a differ‐
ent appearance.

Fig. 60: Digital static horizontal pattern Digital static horizontal pattern

ent appearance.
Fig. 61: Digital static vertical pattern Digital static vertical pattern

ent appearance.

Fig. 62: Digital dynamic horizontal pattern Digital dynamic horizontal pattern

ent appearance.
Fig. 63: Pseudo random pattern Pseudo random pattern

ent appearance.

Fig. 64: Defective pixel map (compensated) Defective pixel map

ent appearance.
Fig. 65: Static horizontal ramp from analog board Static horizontal ramp from analog
board

ent appearance.

Fig. 66: Static vertical ramp for the analog board Static vertical ramp from analog board

ent appearance.
Fig. 67: Static Mapix gray level pattern from analog board Static Mapix gray level pattern from an‐
alog board

ent appearance.

Fig. 68: Static diagonal black/white pattern from analog board Static diagonal black/white pattern
from analog board

ent appearance.

Fig. 69: Static diagonal lines from the analog board Static diagonal lines from analog board

ent appearance.
Fig. 70: Static pseudo random pattern from analog board Static pseudo random pattern from an‐
alog board

ent appearance.

Tab. 17 DIPP Test Pattern
Please note that the window settings, DDO, AGC, Global Gain, Gamma and edge en‐
hancement can lead to a different appearance.
Fig. 71: DIPP ramp test pattern Dipp test pattern
Please note that the win‐

dow settings, DDO, AGC,
Global Gain, Gamma and
edge enhancement can
lead to a different appear‐
ance.
DIPP Test Pattern “Level” will show a homogeneous image with a gray level that is de‐
fined under <level>
8.6.2 Control Fluoro

n To call up Control Fluoro, select the path Control > Control Fluoro >
 To use Control Fluoro, the service switch on the SIRC board (SRV_RAD, front-end RTC)
must be active.

Fig. 72: Fluoro Control (biplane)
Control Fluoro This mode is used to release fluoro with predefined parameters. The cur‐
rently used exam set will be replaced by a specific fluoro program for service. All parame‐
ter entries are monitored from the system control to ensure the X-ray tube will not be
overloaded.
Fluoro A/B Defines the plane where fluoro will be released. For biplane fluoro select, "Flu‐
oro A" and "Fluoro B" at the same time.
Start/Stop X-ray Key to release X-ray and disable X-ray. The name of the key will toggle,
depending on the current mode.
Exit Exits the Service Switches dialog box and returns to the Control window. All service
switches are reset to their default values.
 When all tests are completed, set the service switch on the SIRC board back to "OFF".
 In biplane systems, no B plane image should be shown if the system is in bypass.
8.6.3 Control Acquisition

This mode is used to release single shot exposures with predefined parameters. The cur‐
rently used exam set will be replaced by a specific acquisition program for service. All pa‐
rameter entries are monitored from the system control to ensure the X-ray tube will not
be overloaded.
 To use Control Acquisition, the service switch on the SIRC board (SRV_RAD, front-end
RTC) must be active.

To call up the Control Acquisition, select the path Control > Control Acquizition >.
Fig. 73: Controlled acquisition
n Set the service radiation switch on the SIRC board to “On”.

n Set the exposure parameters in the dialog box. Confirm by clicking on <Send>.
X n
Release the test exposure (100 ms test time) by clicking on <Start X-Ray>.
n If the tube current has not reached its reference value, the tube adjustment has to be
repeated.
n For low-current exposures, discharge of the total high voltage capacity can be clearly
seen after the exposure is completed.
n After the check is completed, exit the dialog box.
 When all tests are completed, set the service switch on the SIRC board back to "OFF".
 In biplane systems, no B plane image should be shown if the system is in bypass.
8.6.4 Auxiliary
8.6.4.1 AXCS Traces
 This mode is for lab use only! It is necessary to get special information to set the correct
parameter.
With the "AXCS Trace Control" tool, it is possible to record the last 1000 AXCS objects to a
readable file. It is possible to trigger a certain event or initiate an immediate trace dump.
In both cases the recorded file can be viewed in the report viewer.

To generate an AXCS Trace, perform following steps:

n Initiating an AXCS trace dump.
n Switch to "Report generation".
n Generate the AXCS trace.
n Switch to "Reports" and read the trace.
For more details, see the help for "Report Generation".
Error Number:
n Number of the error which will be used as the trigger.
n Enter max. 5 decimal places.
n Range: 0 (Default) to 65531. Error Number
Domain ID: Enter the Domain ID of the error which will be used as the trigger.
Use up to a max. of 3 characters (e.g. SCU) as the input.
Only the following Domain IDs (Error Sources) will trigger an AXCS trace:
Component Explanation
ACU Acquisition Control Unit (RTC)
ANG Angiomatic (RTC)
CCU Collimator Control Unit (RTC)
CSF Common Software Functions (RTC)
PMS Service (customer log user messages)
REP Error Reporting
SCU Stand Control Unit (RTC)
SF Support Functions (Service)
SYC System Controller (RTC)
Keys in the Action Bar

n Dump
Initiates an immediate dump of the last 1000 AXCS objects.
n Store
Stores the information of the actual entered error number and Domain ID.
 A Domain ID is necessary for this function!

n Exit
Exits "Auxiliary" and returns to the "Control" menu.
 If no more trace files are required, delete the boxes with the Error ID and Domain ID.
8.6.5 OGP Import/Export

OGPs (Organ Programs) can be imported and exported here.
8.6.5.1 Organ Program Export
Select Drive
Select the drive. The Organ Program file will be written to the root of the selected drive.
n [-A-] Floppy Disk
- IVS floppy drive
n [-C-] FIXED
- IVS system drive
n [-D-] FIXED
n [-E-] FIXED
n [-F-] DVD
- ACE CD/DVD burner
n [-R-] DVD
- IVS CD/DVD reader - not useful for export.

List of OGP Modes
Fig. 74: Example: List of OGP modes
Select the Organ Program Modes to be exported. Multiple modes can be selected. The
available modes depend on the system type and the options that are installed and config‐
ured.
List of Organ Programs - Mode: xxxx
Fig. 75: Example: List of organ programs - mode: (triplets)

Select the organ program(s) to be exported. A list of the organ programs is shown for
each OGP Mode selected in the previous menu (List of OGP Modes)
Organ programs for the Fluoro and Roadmap Modes are selected for export as triplets.
 For all others modes (e.g. DR mode, DSA mode, ...), organ programs are selected sepa‐
rately for export.
8.6.5.2 Organ Program Import
Select Drive
Select the drive. The list of Organ Program files is read from the root of the selected drive.
n [-A-] Floppy Disk
- IVS floppy drive
n [-C-] FIXED
- IVS system drive
n [-D-] FIXED
n [-E-] FIXED
n [-F-] DVD
- ACE CD/DVD burner
n [-R-] DVD
- IVS CD/DVD reader
Select File
Select the Organ Program file from the list. Only the Organ Program files on the root of
the selected drive will be listed. There can be more than 1 file (e.g. different date and/or
time).
 The details of the selected Organ Program file are shown:

Fig. 76: Example: Organ program file details
The format for the file name is:

<host name>_<system type>_<Date>_<Time>_.OGP
n host name - as configured under Configuration > (Local Host) TCP/IP Lan > (Identi‐
fication) Computer name
n system type - as configured under Configuration > System Options > System type
n Date - format YYYYMMDD (e.g. 20090128) Year Month Day
n Time - format hhmmss (e.g. 055845, 231056) Hour Minute Second

List of OGP Modes
Fig. 77: Example: List of OGP modes
Select the Organ Program Modes to be imported. Multiple modes can be selected. The
available modes depend on the contents of the OGP file to be imported.

List of Organ Programs - Mode: xxxxx
Fig. 78: Example: List of organ programs - mode: (import)
Select the organ program(s) to be replaced. A list of the organ programs is shown for
each OGP mode selected in the previous menu (List of OGP Modes). The message "OGP
Present in system" is shown if the organ program already exists in the system.
Organ programs for the Fluoro and Roadmap modes are selected for import as triplets.
 For all other modes (e.g. DR mode, DSA mode, ...), organ programs are selected sepa‐
rately for import.
8.6.6 System Backup/Restore (Acronis)

Backup and restore of the AXIS system is performed here.
n IVS (C: and D: drives)
n IAS-A/B (C: drive)
The Acronis SW performs the backup and restore.
The RTCA/B, ECC, DDIS and all components that have their data on the IVS are backed up.
During system restore, IVS restore, a first boot of the IVS after restore and a download of
the components are started automatically, so that they (e.g. RTC) get the "old" SW from
the backup date.
The files are written to the Service Backup Restore disk in the IAS A. For details, see
( System Backup/Restore / AXA4-000.816.04)

For a manual restore of the IVS/IAS-A/B using the Acronis boot CD, see:
n IVS ( Restore of the IVS (PC/System Drive replaced or corrupt Software)
/ AXA4-000.841.19)
n IAS A ( Restore of IAS A (PC/System Drive replaced or corrupt Software)
/ AXA4-000.841.19)
n IAS B ( Restore of IAS B (PC/System Drive replaced or corrupt Software)
/ AXA4-000.841.19)
Only manual backup/restore of the KPC (Zeego) using the Acronis Image Management
Console is possible. See ( KPC Backup/Restore / AXA4-000.816.04).
8.6.6.1 Backup
For details, see ( Creating a System Disk Backup / AXA4-000.816.04).
8.6.6.2 Restore
For details, see ( Restoring a System Disk Backup / AXA4-000.816.04).
8.6.7 ECC Layout Import/Export

This function is available in versions < VC14G but is not to be used because it is possible
to import incompatible ECC layouts.
In ≥ VC14G, it is removed (AX_00230371).
8.6.8 Artis HW/SW inventory

The hardware and software inventory maintained by the LSS (Local System Server) is
viewed here.
Only a basic inventory template is used to obtain system information.
Currently not used for service.
8.6.9 Offline SW Pkg Import

Import of LSS software distribution packages for the Artis system can be performed from
here. The LSS software package can be imported from a local HDD/CD/DVD/USB device.
 When a SW package is installed using this method, the BE (Backend) is not notified of
the status of the SW installation.

Fig. 79: Offline LSS SW Pkg Import mask
This function can be found under Service GUI > Control > Offline SW Pkg Import.
8.6.9.1 Drive List

Select the drive. The SW package will be read from the root of the selected drive.
n [-A-] Floppy Disk
- IVS floppy drive
n [-F-] DVD
- ACE CD/DVD burner
n [-R-] DVD
- IVS CD/DVD reader
n [-C-] FIXED
- IVS system drive
n [-D-] FIXED
n [-E-] FIXED
n [-?-] REMOVABLE
- Removable Media (e.g. USB Flash drive)
8.6.9.2 File List

Select the SW package to be imported from the drop-down list.
Only SW packages in the root directory of the selected drive will be shown (e.g. CS_Virus
Pattern_2.961.00_syngo.zip).

The page can be exited safely after “LSS Import Package extracted successfully...” is
shown in the status bar at the lower left.
Fig. 80: SD Icon in Status bar
The syngo SD icon should be shown in the right bottom of the screen within 15 minutes.
After the syngo SD icon is shown, follow the Software Distribution/Installation workflow,
see ( SD User Interface / Page 264).

8.7 Quality Assurance

Here it is possible to open different kinds of inspections. Only one inspection can be
opened at the same time.
To open another inspection, it is necessary first to lock the active inspection.
 Once an inspection is locked it cannot be changed anymore.
For further information, see the system quality assurance( Quality Assurance with Sys‐
tem SW VC14 / AXA4-000.820.08).
1. To call up the Quality Assurance Tests, select the path <Quality Assurance> .

8.8 Test Tools

Here you can perform tests and/or monitor specific realtime values
n Hardware tests
n AXCS tests
n Third-party tests
n Stand & table tests
n SIRC status
8.8.1 Hardware tests
Fig. 81: Test Tools, Hardware tests, RTC ULI 1 interface

Fig. 82: Report, Hardware Tests result, example
8.8.1.1 Combined Tests
Problem Oriented (tests)

This is a drop down list of predefined Problem Oriented tests. They are made up of indi‐
vidual or groups of tests from the Component and FRU’s columns.
For details on the FD/DIPP predefined Problem Oriented tests, see ( Hardware
Tests / AXA4-110.840.04).
Self Defined (tests)

This is a drop down list of locally created Self Defined tests. They are made up of individ‐
ual or groups of tests from the Component and FRU’s columns.
Creating a Self Defined (test):
1. Select the check boxes for 1 or more tests or group of tests

- Marking the box in the Components column selects the group of tests for that FRU.
- Marking the box in the FRU’s column selects only that test.

2. Click Save.
3. Type the name for the new Self Defined test
- It is recommended to give the test a descriptive name so that its purpose is clear.
4. Click Save.
 The new Self Defined test is selectable from the Self Defined drop down
menu.
8.8.1.2 Components
IVS Imaging App Shutdown:

The IVS application is shut down. The Local Service UI is still functional and direct access
to the IVS desktop is possible. Shutting down the IVS application is a required before start‐
ing AXIS system tests or stress tests.
For details, see ( Shutting down the IVS Application SW (via Test
Tools): / AXA4-000.840.19).
IAS-A(B) Imaging App Shutdown:

The IAS application is shut down. Direct access to the IAS desktop is possible. Shutting
down the IAS application is a required before starting AXIS system tests or stress tests.
For details, see ( Shutting down the IAS Application SW (via Test
Tools): / AXA4-000.840.19).
Diagnostics with IAS-A(B) and IVS (60s Tests):

IVS and IAS hardware as well as connections between the PCs can be tested.
For details, see ( AXIS System Tests / AXA4-000.840.19).
Diagnostic Info A100/plane A(B):

Various generator parameters are shown.
For details, see ( Diagnostic Info on POLYDOROS A100 beginning with System SW
VC12... / AXA4-100.840.09).
ECC 1(2/3):
The joystick functionality is tested. This is an interactive test which requires physical
movement of the joystick and buttons.
For details, see ( ECC Joystick Test / AXA4-000.840.07).
IAS A(B): HW inventory check:

The hardware in the IAS can be compared to the last hardware inventory snapshot or a
new hardware inventory snapshot and can be created based on the current IAS hardware.

For details, see ( AXIS Inventory / AXA4-000.840.19).
IAS A(B): XPStress test:

Stress tests can be run on the IAS hardware.
For details, see ( AXIS XP Stress / AXA4-000.840.19).
IVS: HW inventory check:

The hardware in the IVS can be compared to the last hardware Inventory snapshot or a
new hardware Inventory snapshot and can be created based on the current IVS hardware.
For details, see ( AXIS Inventory / AXA4-000.840.19).
IVS: XPStress test:

Stress tests can be run on the IVS hardware.
For details, see ( AXIS XP Stress / AXA4-000.840.19).
RTC A(B) DIPP FRU:

The DIPP hardware functionality is tested.
For details, see ( Hardware Tests / AXA4-110.840.04).
RTC A(B) Interface:

The RTC A(B) interface (i.e. SIRC board) is tested.
For details, see ( RTC A Interface Tests / AXA4-000.840.10).
Stand:
The brakes of the particular stand are tested.
For details, see ( Hardware Tests / AXA4-410.840.01).
8.8.2 AXCS tests

The status of the AXCS components is shown here (Ready, Turn on, Connected, Turn Off
and Disconnected). Details on individual components and the reset of some are possible
from this test.
For details, see ( AXCS TEST / Page 49).

8.8.3 Third-party tests
8.8.3.1 ACRONIS Image Management Console

The Acronis Image Management console is used for the backup/restore of the KPC (zee‐
go) or a manual restore of the IAS A/B.
For KPC backup/restore details, see ( Creating the KPC Backup / AXA4-000.816.04)
For IAS A/B restore details, see ( Restore of IAS A (PC/System Drive replaced or corrupt
Software) / AXA4-000.841.19) or ( Restore of IAS B (PC/System Drive replaced or cor‐
rupt Software) / AXA4-000.841.19)
8.8.3.2 Mount/unmount the backup/restore drive

The backup restore drive can be installed or removed for use in the syngo backup restore.
( Backup & Restore (syngo) / Page 103)
This has no effect on Acronis functionality.
To change the backup restore drive status from the third-party tests:
1. Select the radio button for Mount/Unmount Backup Restore Drive
2. Click on Go.
3. Select the desired function, MOUNT_BACKUP_RESTORE_DRIVE or UNMOUNT_BACK‐
UP_RESTORE_DRIVE from the drop-down list.
4. Click on Go.
 The External window will run in background pop-up window will be shown.
5. Click on OK in the pop-up window.
 The backup restore drive is installed or removed depending on which function
was selected in step 3.
6. Click on Exit twice to return to the Test Tools selection.
8.8.3.3 Can Net Test

A list of all possible CAN net nodes is shown in the cmd shell window.
In SW versions < VC14G, the cmd shell window closes automatically when complete.
 The test can be started manually (C:\AXIOM\rtc\callcannetinfor.bat). The cmd shell win‐
dow stays open when complete and waits for the press of a key to close.
To start the CAN net test from the third-party tests:

1. Select the radio button for Can Net Test
2. Click on Go.
3. Select the Can Net Test function from the drop-own list.
4. Click on Go.
 The External window will run in background pop-up window will be shown.

5. Click on OK in the pop-up window

 The CAN net nodes are shown.
6. Click on Exit twice to return to the Test Tools selection
8.8.3.4 Managed Network Switch

The AXCS network switch can be managed from here.
To start the Managed Network Switch GUI from the Third-party Tests:
1. Select the radio button for Managed Network Switch
2. Click on Go.
 A CMD window opens and a network ping to the AXCS switch is initiated.
 Connect to 10.1.1.120 window is shown and waits for a user name and a
password to be entered.
 If the ping is unsuccessful, the Connect to 10.1.1.120 window is not shown and the sys‐
tem returns to the Third-party Tests selection page.
3. Enter the required user name and password.

(See: CS Knowledge Base ID 13982, AX PASSWORD LIST)
4. Click on OK in the Connect to 10.1.1.120 window
 The Internet Explorer Web-Based Management Function window is shown.
5. Close the Internet Explorer Web-Based Management Function window to end the
session.
8.8.3.5 Trumpf service program

This program is not used. For details on troubleshooting the Trumpf table, see ( Trumpf
Table VC14 SW / AXA4-PAT.840.01).
8.8.3.6 VDX configuration

The PMM_VDX_Config application is started from here. This is the same application that
is available under Configuration > (Artis System) VDX Box Configuration.
For operational details, see ( PMM VDX Config / AXA4-000.840.19)
For configuration details, see ( VDX Box Config / AXA4-000.843.04)
8.8.4 Stand & table tests

These tests are system-specific. For details, follow the relevant link:
n Floor and Biplane Stand ( Stand & Table Tests / AXA4-050.840.01)
n MP System ( Stand Tests / AXA4-410.840.01)
n Ceiling Stand ( Test Tools / AXA4-060.840.01)
n zeego Stand ( Test Tools / AXA4-040.840.02)

n Table (Basic/Peri/Tilting/OR) ( Stand & Table Tests / AXA4-000.840.05)
8.8.5 SIRC status

The status of the AXCS components is shown (e.g. Ready, Turn On, Turn Off and Discon‐
nected).
For further information, see Test Tools SIRC Status RTC(A) ( SIRC Status Tests
/ AXA4-000.840.10).

8.9 DICOM Tests

There is a separate document available for DICOM troubleshooting.
See the DICOM Troubleshooting Guide ( Syngo DICOM Test Tools / TD00-000.840.01)
8.9.1 General
8.9.1.1 Remote Access

For most functions, DICOM Test Tools require Full Access Mode to perform remote serv‐
ice. "Verify Network" and the "Analysis" window can be started in Limited Access Mode.
Full access is necessary because some functions stop or start application processes. How‐
ever, full access disables user interaction at the customer user interface. Since certain
tests require user interaction, the DICOM Test Tools make it possible to release the cus‐
tomer user interface. This can be done via the buttons Release host and Back to full
access. An appropriate flashing message (displayed in the customer UI) indicates that
someone is logged on in “Full Access Mode”.
8.9.1.2 Layout
Fig. 83: Layout of the DICOM service menu
1. Navigation bar
2. DICOM Service and Mode selection frame (navigation frame)
3. Specific selection frame (navigation frame)
4. Function frame
5. Action bar

6. Current date and time on remote system
8.9.1.3 Features
This chapter provides an overview of the tools supported by DICOM Services.
DICOM Services
n Verify Network:
Network connection on TCP/IP level (ping) and on DICOM level (DICOM Verification (C-
ECHO)) can be tested either for a certain destination or for all configured DICOM no‐
des.
n Storage:
The trace level for the DICOM logfile (merge_stu.log) can be extended to display, e.g.,
the association negotiation (T3), the command set of a DICOM message (T7), and the
data set of a DICOM message (T2).
In addition, a test receiver may be started to capture original DICOM images on the
hard disk. A test sender can be used to check the receiving functions of the local or
remote DICOM application.
n Basic Print:
A test basic print provider may be started and images may be sent to this process. The
message transfer and the film may be displayed.
The trace level for the DICOM logfile (merge_hc.log) may be extended to display, e.g.,
n Query/Retrieve:
The trace level for the DICOM logfile (merge_stu.log) may be extended to display, e.g,
n Storage Commitment:
The trace level for the DICOM logfile (merge_stu.log) may be extended to display, e.g,
n Modality Worklist:
The trace level for the DICOM logfile (merge_HRI.log) may be extended to display,
e.g., the association negotiation (T3), the command set of a DICOM message (T7),
and the data set of a DICOM message (T2).
n Modality Performed Procedure Steps:
The trace level for the DICOM logfile (merge_HRI.log) may be extended to display,
e.g., the association negotiation (T3), the command set of a DICOM message (T7),
and the data set of a DICOM message (T2).
How to use the DICOM Service Tools

Choose the required function from the DICOM Service and Mode selection frame (2), and
select additional information (if required) from the specific selection frame (3).

Activate the configured process by clicking the Go on the Action bar (5).
The results are displayed in the function frame (4).
The Analysis platform may be activated from the Navigation bar (1). The analysis frame
layout is identical to the DICOM service platform.
Exiting the DICOM Service Tools

To exit the DICOM Test Tools, stop the last test function by clicking the Abort button in
the Action bar. Then click the Home button in the Navigation bar. An information win‐
dow appears.
 If you want to save the captured messages (including images) and logfiles, you need to
click the Cancel button.
Fig. 84: Exiting the DICOM Test Tools
8.9.2 Functions
8.9.2.1 Dicom Services

Tools are provided for the DICOM Services Verification, Storage, Storage Commitment,
Query/Retrieve, Basic Print, Modality Worklist, and Modality Performed Procedure
Steps. These tools may be selected under the DICOM Service menu item.
After you have selected a certain tool, you need to Abort it before invoking another tool
or exiting from the DICOM Test Tools.

Verify Network
Fig. 85: DICOM Verification of a single destination
Verify Network performs a TCP/IP ping. If this ping is successful, the DICOM Service DI‐
COM Verification sends a C-ECHO request to a DICOM destination process (AET) on the
local or remote system.
DICOM verification may be performed for a specific DICOM node or simultaneously for all
configured DICOM nodes (verify all AETs).
This test consists of 2 steps: the first step is the TCP/IP ping, and the second step is the C-
ECHO command on the DICOM level.
You can stop the test by clicking the Abort button in the Action bar.

Fig. 86: DICOM Verification of all AETs
n Verify all AETs:

A TCP/IP ping command and a DICOM C_ECHO command are performed automatically
for all configured DICOM nodes. If a node is not running or not accessible, you have to
wait for 30 seconds (default time).
n Timeout in sec
The default timeout for C_ECHO of 30 seconds may be changed here.
n Host Name
This field is only displayed if Verify all AETs is not selected. Select the host name of
the destination device. The device itself (own host name) may be selected as well. Af‐
ter the logical name or AET (next two buttons) is selected, the appropriate host name
will be displayed automatically.
n Logical Name
This field is only displayed if Verify all AETs is not selected. Select the logical Name of
the destination device. If the AET (next button) has been previously selected, the ap‐
propriate logical name will be displayed automatically.
n AET
Select the Application Entity Title of the destination device.
Troubleshooting Remarks
n A TCP/IP ping may fail for the following reasons:
- The remote host is turned off or not in the same network, no router is configured,
or the routing demon is not started.
- The TCP/IP address is configured incorrectly.
- A networking device (router, switch, bridge,...) denies access to the other network.

n A C-ECHO will fail for the following reasons:

- AET or port number is not configured correctly.
- The DICOM process at the remote host is not running.
- Certain products check the IP address or AET of the sending system. If the AET or IP
address of the local system is not entered correctly, DICOM verification will fail.
- The remote host does not support DICOM verification as a Service Class Provider
(see DICOM Conformance Statement).
Storage
The storage service class determines how DICOM images and other objects (waveforms,
LUTs, overlays) are sent (SCU) or received (SCP). The DICOM Standard defines several
transfer syntaxes, each of which is a set of encoding rules for communication (e.g., byte
ordering, compression).
Extend Trace Level

Fig. 87: Storage - Extended Trace menu
The DICOM implementation is based on a toolkit from Merge Technologies. This toolkit
includes a mergecom.log file designed as a ring buffer. Certain trace levels may be ena‐
bled to receive more detailed information regarding the latest DICOM communications.
The respective mergecom.log file can be displayed under Analysis at “Examine Logs -
merge_stu.log”. To interpret the log files, basic knowledge of DICOM is necessary.
Storage, Storage Commitment, and Query/Retrieve use the same mergecom.log file, as
they belong to the same syngo Service.

C:\%MEDHOME%\log\merge_stu.log Storage, Storage Commitment, and Query/

Retrieve
The Storage test tools may only be started remotely in “Full Access Mode”. In this case, no
user interaction is possible. It is therefore not possible to send / print images or to per‐
form a query request. Since these user interactions are required in order to receive the
appropriate messages in the mergecom.log files, the DICOM Test Tools provide the possi‐
bility of enabling user interaction even in full access mode.
n Release Host
Select this item in the Action bar to work with the user interface (identical to limited
access). The “Remote Access Control Window” can be iconized.
n Back to Full Access
After the images have been transferred or a Query/Retrieve has been performed, you
have to disable interactions at the user interface to perform further tasks in the DI‐
COM Test Tools.
n Transfer Syntax
This pull-down list lets you choose transfer syntaxes used for the association negotia‐
tion after restart of the DICOM processes. It provides additional troubleshooting op‐
tions since you can limit the settings for the next associations. Before selecting other
DICOM services or functions, or before finishing the DICOM Test Tools, “abort” the Ex‐
tend Trace Level function. The original transfer syntaxes will be set again.
n Merge Trace Level
The following trace levels may be enabled to provide more detailed information in the
log file merge_stu.log. This log file may be displayed under “Analysis - Examine Logs”.
See also the example of an association with trace level T2, T3, T7 and T9 in the
appendix.
- T1 This trace level does not affect the mergecom.log file.
- T2 Data Set
This trace level shows the attributes of the transferred message, e.g. the image
header attributes or the attributes within a DICOM message.
 Trace level T2 also shows patient data in the log file. For this reason, “Patient Data Ac‐
cess” is required for remote access.
- T3 Association Negotiation
Every DICOM communication starts with the association negotiation. The initiator
(SCU) sends a list of all supported image objects and transfer syntaxes to the re‐
mote system (SCP). The AETs of both systems are also displayed on the T3 level.
The SCP responds with the status (accept or reject) of the image objects and selects
one of the proposed transfer syntaxes.
- T4 Rejection of Incoming Messages
When incoming associations are automatically rejected (IP address not known), log
messages will be displayed at this trace level.
- T5 Regular and Extended Regulations
Logs messages relating to regular and extended regulations.

- T6 Mergecom Configuration Files

At this trace level, the related mergecom.ini, mergecom.pro, mergecom.app, and
mergecom.srv files will be written to the mergecom.log file. This may be helpful for
analyzing the log file, but it requires a large amount of space in the log file.
- T7 Command Set
Following the association negotiation, a command set (attributes with group 0) will
be transferred. Before sending an image, for example, the command set will tell the
remote system the type of image object (SOP Class UID such as CT, RF, ...) to be
transferred, including the UID of the image.
The response command set after each image will show the status of the transfer,
where status = 0 means a successful transfer.
- T8 Streaming Messages
Log messages relating to the streaming in and out of messages and file objects are
displayed on the T8 level.
-
T9 PDU Level
The entire DICOM association is displayed on the PDU level (Protocol Data Unit).
Each PDU with a maximum size defined during the association negotiation will be
displayed in one line. The association negotiation will be shown in greater detail.
T9 is the only way of displaying the association release request and response at the
end of an association.
Patient Data Access
In case of remote access to the DICOM Service Tools, viewing patient-relevant data
(name, id, ..) is not permitted. However, if you enable trace level T2, patient data will be
displayed in the log file. Therefore, the customer has to provide additional access rights,
allowing the service engineer to view patient-relevant data. To obtain these rights, the
service engineer has to enter his name and send a “Patient Data Access” request to the
customer's user interface.
n Please enter your name
Enter the name of the local service engineer logged in remotely who requires Patient
Data Access rights.
n Request PDA
Selecting this button initiates an additional selection item (Patient Data Access) to be
activated in the customer user interface under “Option - Remote Access”. Additionally,
the name of the service engineer will be displayed. The customer has to select this
menu item to permit trace level T2 to be activated in the log file.
Send Images
This menu item can be used to send DICOM images (stored on the hard disk via the test
receiver or, e.g., FTP) to a user-specified DICOM receiver. By sending these images to the
local DICOM receiver, you are able to import images into the database and display them
in the user interface.

Fig. 88: Storage - Send Images menu
n Transfer Syntax
This pull-down list lets you choose transfer syntaxes that will be enabled after restart
of the DICOM processes. It provides additional troubleshooting options, as you can
limit the settings for the next associations.
Before selecting other DICOM Services or functions, or before finishing the DICOM
Test Tools, “abort” the “Send Images” function. The original transfer syntaxes will be
set again.
n Image Data
Displays a list of DICOM images located in the %MEDHOME%\service\dst\img directory.
The test receivers (see Simulate/Add Local/Remote Receiver) will copy all received im‐
ages to this directory. Images copied to this directory manually (ftp) will also be dis‐
played. Certain default DICOM images will be delivered with the DICOM Test Tools for
test purposes.
n AET of Sender
The sending AET is, by default, the AET of the local storage SCP. Usually it is not neces‐
sary to change this value.
n Host Name
Host name of the destination system. The system itself (host name) may be selected
as well. When selecting the logical name or AET (next two buttons), the appropriate
host name will be displayed automatically.

n Logical Name
Select the logical name of the destination system. When selecting the AET (next but‐
ton) first, the appropriate logical name will be displayed automatically.
n AET
Select the storage AET of the destination system. Please note: The Send function will
fail, if you, e.g., select the Query/Retrieve AET of the remote system instead of the
storage AET.
n Merge Trace Level
appendix.
- T1
This trace level does not affect the mergecom.log file.
- T2 Data Set
When incoming associations are automatically rejected (IP address not known), log
messages will be displayed on this trace level.
mergecom.srv files will be written to the mergecom.log file. This may be helpful in
analyzing the log file, however, note that analysis requires a large amount of space
in the log file.
- T7 Command Set
be transferred. Before sending, for example, an image, the command set will tell
the remote system the type of image object (SOP Class UID such as CT, RF, ...) to be
transferred, including the UID of the image.
The response command set after each image will show the status of the transfer,
where status = 0 means a successful transfer.

-T9 PDU Level
displayed in one line.
The association negotiation will be shown in greater detail.
T9 provides the only possibility of displaying the Association Release request and re‐
sponse at the end of an association.
Patient Data Access
(name, id, ..) is not permitted. However, if you enable trace level T2, patient data will be
customer"s user interface.
Enter the name of the local service engineer logged in remotely who requires Patient
Data Access rights.
n Request PDA
Selecting this button initiates that an additional selection item (Patient Data Access)
will be activated in the customer user interface under “Option - Remote Access”. Addi‐
tionally, the name of the service engineer will be displayed. The customer has to se‐
lect this menu item to permit trace level T2 to be activated in the log file.
Before selecting other DICOM Services or functions, or before finishing the DICOM Test
Tools, “abort” the “Send Images” function.

Simulate Remote Receiver

Fig. 89: Storage - Simulate Remote Receiver menu
When this menu item is selected, the Test Receiver provided by the DICOM Test Tools is
started to simulate a remote DICOM receiver. You will receive a list of all DICOM AETs con‐
figured on your system. Select the AET you would like to replace with the Test Receiver.
All images sent by the local sender to this destination will be received by the Test Receiver
and stored on the hard disk in DICOM format.
Fig. 90: Storage - Simulate Remote Receiver diagram
Under analysis, the received images can be evaluated: an image header dump may be
performed, or the image can be displayed.
The received images and the log files may be removed when exiting the DICOM Service
Tools.
The storage test tools may only be started remotely in “Full Access Mode”. In this case, no
user interaction is possible, and, therefore, it is also not possible to send / print images or
to perform a query request. Since these user interactions are necessary to receive the ap‐
propriate messages in the mergecom.log files, the DICOM Test Tools provide the possibili‐
ty of enabling user interaction even in full access mode.

n Release Host
After the images have been transferred or a Query/Retrieve has been performed, this
function disables interaction at the user interface to perform further tasks in the DI‐
COM Test Tools.
n Host Name
Host name of the destination system. The system itself (host name) may be selected
as well. When selecting the logical name or AET (next two buttons), the appropriate
host name will be displayed automatically.
n Logical Name
Select the logical name of the destination system. When selecting the AET (next but‐
ton) first, the appropriate logical name will be displayed automatically.
n AET
Select the storage AET of the destination system. Please note: The Send function will
fail, if you, e.g., select the Query/Retrieve AET of the remote system instead of the
storage AET.
n Merge Trace Level
appendix.
- T1
- T2 Data Set
If incoming associations are automatically rejected (IP address not known), log mes‐
sages will be displayed on this trace level.


in the log file.
- T7 Command Set
transferred, including the UID of the image. The response command set after each
image will show the status of the transfer, where status = 0 means a successful
transfer.
-
T9 PDU Level
Patient Data Access
(name, id, ...) is not permitted. However, if you enable trace level T2, patient data will be
service engineer has to enter his name and send a "Patient Data Access" request to the
The objects (images) captured with the test receiver will normally be anonymized. If
patient-relevant data is required for troubleshooting (not anonymized), it is necessa‐
ry to obtain the “Patient Data Access” rights from the customer's user interface.
Enter the name of the remotely logged in local service engineer who requires Patient
Data Access rights.
n Request PDA
When you select this button, an additional selection item (Patient Data Access) will be
activated in the customer user interface under "Option - Remote Access". Additionally,
Before selecting other DICOM services or functions, or before finishing the DICOM Test
Tools, “abort” the “Simulate Remote Receiver” function.

Simulate Local Receiver

Fig. 91: Storage - Simulate Local Receiver menu
When this menu item is selected, a Test Receiver provided by the DICOM Test Tools is star‐
ted using the same AET and port number as the application DICOM receiver. The original
application receiver will be stopped. All images sent by remote senders will be stored in
DICOM format to the hard disk.
 None of the images received by the Test Receiver will be stored to the database. To avoid
losing images, select the AET of the sending system. All other senders will be rejected.
Fig. 92: Storage - Simulate Local Receiver diagram
The received images may be analyzed with the tools provided by “Dicom Analysis”.
The received images and the log files may be removed when exiting from the DICOM
Service Tools.
n Host Name
Host name of the sending system. For data security, only images from this AET will be
received by the Test Receiver. All other systems will be rejected. The system itself

(host name) can also be selected. When selecting the logical name or AET (next two
buttons), the appropriate host name will be displayed automatically.
n Logical Name
Select the logical name of the sending system. When selecting the AET (next button)
first, the appropriate logical name will be displayed automatically.
n AET
Select the storage AET of the sending system. Please note: The Send function will fail,
if you, e.g., select the Query/Retrieve AET of the remote system instead of the storage
AET.
n Merge Trace Level
appendix.
- T1
- T2 Data Set
in the log file.
- T7 Command Set

transfer.
-T9 PDU Level
Patient Data Access
service engineer has to enter his name and send a "Patient Data Access" request to the
The objects (images) captured with the Test Receiver will normally be anonymized.
If patient-relevant data is required for troubleshooting (not anonymized), it is neces‐
sary to obtain the “Patient Data Access” rights from the customer's user interface.
Data Access rights.
n Request PDA
When you select this button, an additional selection item (Patient Data Access) is acti‐
vated in the customer user interface under “Option - Remote Access”. Additionally, the
name of the service engineer will be displayed. The customer has to select this menu
item to permit trace level T2 to be activated in the log file.
Tools, “abort” the “Simulate Remote Receiver” function.

Additional Local Receiver

Fig. 93: Storage - Additional Local Receiver menu
This option lets you select an additional DICOM receiver that is used for test purposes on‐
ly. The AET of this test receiver has to be entered during Configuration. The Test Receiver
is listening under the port 110. It may be used to receive images from the local applica‐
tion, as well as any remote system (as long as this AET is configured there).
You can only send from specifically selected AETs. All other remote nodes can still send to
the original DICOM receiver.
None of the images received by the Test Receiver will be stored to the database. To avoid
 losing images, select the AET of the sending system. All other senders will still send to
the original local DICOM receiver.
To send to the additional Test Receiver, configure this Test Storage SCP (port: 110, AET
will be defined in the Test Tools) at the remote system (SCU).
Fig. 94: Storage - Add Local Receiver diagram
The received images may be analyzed with the tools provided by “DICOM Analysis”.

The images received and the log files may be removed when exiting from the DICOM
Service Tools.
n AET
You need to define an AET for the additional Test Receiver. At the remote system, you
need to configure this AET with the appropriate port number 110.
n Merge Trace Level
appendix.
- T1
- T2 Data Set
mote system SCP. The AETs of both systems are also displayed on the T3 level.
in the log file.
- T7 Command Set
transfer.

-
T9 PDU Level
Patient Data Access
The objects (images) captured with the Test Receiver will normally be anonymized.
If patient-relevant data is required for troubleshooting (not anonymized), it is neces‐
sary to obtain the “Patient Data Access” rights from the customer's user interface.
Data Access rights.
n Request PDA
Tools, it is necessary to “abort” the “Simulate Remote Receiver” function.
Print Devices
This menu provides tools for testing the Basic Print function of the local DICOM Basic Print
process. You may start a Test Basic Print provider, which replaces the remote Basic Print
provider (usually a laser camera). After printing a film from the user interface to the Test
Basic Print process, you can analyze the log files and display the film using the tools provi‐
ded under Analysis.

Extend Trace Level

Fig. 95: Print Devices - Extended Trace Level menu
The DICOM implementation is based on a toolkit from Merge Technologies. This toolkit
bled to receive more detailed information regarding the latest DICOM communications.
The respective mergecom.log file can be displayed under Analysis at “Examine Logs -
merge_hc.log”. To interpret the log files, basic knowledge of DICOM is necessary.
Location and name of the mergecom.log file for Basic Print:
C:\%MEDHOME%\log\merge_hc.log Basic Print (hardcopy)
The print test tools may only be started remotely in “Full Access Mode”. In this case, no
n Release Host
access). The "Remote Access Control Window" can be iconized.
After the images have been sent to the camera, disable interaction at the user inter‐
face to perform further tasks in the DICOM Test Tools.

n Transfer Syntax
This pull-down list lets you choose transfer syntaxes that will be used for the associa‐
tion negotiation after restart of the DICOM processes. It provides additional trouble‐
shooting options, as you can limit the settings for the next associations. Before select‐
ing other DICOM services or functions, or before finishing the DICOM Test Tools,
"abort" the Extend Trace Level function. The original transfer syntaxes will be set
again.
n Host Name
Host name of the camera. The system itself (host name) may be selected as well.
When selecting the logical name or AET (next two buttons), the appropriate host
name will be displayed automatically.
n Logical Name
Select the logical name of the camera. When selecting the AET (next button) first, the
appropriate logical name will be displayed automatically.
n AET
Select the AET of the camera.
n Merge Trace Level
appendix.
- T1
- T2 Data Set

in the log file.
- T7 Command Set
transfer.
-T9 PDU Level
Patient Data Access
Data Access rights.
n Request PDA

Simulate Camera
Fig. 96: Print Devices - Simulate Camera menu
When this menu item is selected, the Test Basic Print SCP provided by the DICOM Service
Tools is started in place of the Camera (remote Basic Print SCP). You will receive a list of
all configured Basic Print AETs. Select the appropriate laser camera. All films sent from the
user interface to the corresponding laser camera will then be received by the Test Basic
Print SCP.
Fig. 97: Basic Print - Simulate Camera diagram

The Test Basic Print SCP is not identical to the laser camera. As a result, its behavior may
be different from the remote Basic Print SCP.
The Print Test Tools may only be started remotely in “Full Access Mode”. In this case, no
n Release Host
After the images have been sent to the camera, disable interaction at the user inter‐
n Host Name
Host name of the camera. The system itself (host name) may be selected as well.
When selecting the logical name or AET (next two buttons), the appropriate host
name will be displayed automatically.
n Logical Name
Select the logical name of the camera. When selecting the AET (next button) first, the
appropriate logical name will be displayed automatically.
n AET
Select the AET of the camera.
n Merge Trace Level
appendix.
- T1
- T2 Data Set


in the log file.
- T7 Command Set
transfer.
-
T9 PDU Level
Patient Data Access
Data Access rights.
n Request PDA
activated in the customer user interface under "Option - Remote Access." Additionally,
Storage Commitment
Storage Commitment sends a list of image UIDs to the configured destination and waits
for the response of the remote provider.

For this service, it is only possible to extend the trace level of the appropriate merge‐
com.log file. Storage Commitment uses the same DICOM process as Storage and there‐
fore also the same log file, which is stu_merge.log. In this response, trace level T2 shows
whether or not the images were successfully stored at the destination.
Extend Trace Level

Fig. 98: Storage Commitment - Extend trance menu
This DICOM implementation is based on a toolkit from Merge Technologies. This toolkit
bled to get more detailed information regarding the latest DICOM communications. The
respective mergecom.log file can be displayed under Analysis at "Examine Logs -
merge_stu.log". To interpret the log files, basic knowledge of DICOM is necessary.
C:\%MEDHOME%\log\merge_stu. logs Storage, Storage Commitment, and Query/Retrieve
The DICOM Test Tools may only be started remotely in “Full Access Mode”. In this case, no
n Release Host


COM Test Tools.
n Transfer Syntax
shooting options, as you can limit the settings for the next associations.
Before selecting other DICOM services or functions, or before finishing the DICOM
Test Tools, "abort" the Extend Trace Level function. The original transfer syntaxes will
be set again.
n Merge Trace Level
appendix.
- T1
- T2 Data Set
in the log file.
- T7 Command Set

transfer.
-T9 PDU Level
Patient Data Access
Data Access rights.
n Request PDA
Query/Retrieve
com.log file. Query/Retrieve uses the same DICOM process as Storage and therefore also
the same log file, which is stu_merge.log. The Query request and response message at‐
tributes may be displayed on trace level T2.

Extend Trace Level

Fig. 99: Query/Retrieve - Extend trace menu
This DICOM implementation is based on a toolkit from Merge Technologies. The toolkit
respective mergecom.log file can be displayed under Analysis at “Examine Logs -
merge_stu.log”. To interpret the log files, basic knowledge of DICOM is necessary.
C:\%MEDHOME%\log\merge_stu.log1 Storage, Storage Commitment, and Query/Retrieve
n Release Host
access). The "Remote Access Control Window" can be iconized.
1. %medhome% - Depends on modality type


COM Test Tools.
n Transfer Syntax
shooting options, as you can limit the settings for the next associations.
Before selecting other DICOM services or functions, or before finishing the DICOM
Test Tools, “abort” the Extend Trace Level function. The original transfer syntaxes will
be set again.
n Merge Trace Level
appendix.
- T1
- T2 Data Set
in the log file.
- T7 Command Set

transfer.
-
T9 PDU Level
Patient Data Access
Data Access rights.
n Request PDA
Basic Worklist
com.log file. The Worklist request and response message attributes may be displayed on
trace level T2.

Extend Trace Level

Fig. 100: Basic Worklist - Extend trace menu
merge_wl.log”. To interpret the log files, basic knowledge of DICOM is necessary.
user interaction is possible, and, therefore, it is also not possible to perform a worklist re‐
quest from the user interface. Since these user interaction is necessary to receive the ap‐
propriate messages in the merge_HRl.log files, the DICOM Test Tools provide the possibili‐
n Release Host
After the Worklist request has been performed, disable interaction at the user inter‐
n Transfer Syntax

“abort” the Extend Trace Level function. The original transfer syntaxes will be set
again.
n Merge Trace Level
appendix.
- T1
- T2 Data Set
in the log file.
- T7 Command Set
transfer.

-T9 PDU Level

Patient Data Access
If the DICOM Service Tools are accessed remotely, viewing patient-relevant data (name,
id, ..) is not permitted. However, if you enable trace level T2, patient data will be dis‐
played in the log file. Therefore, the customer has to provide additional access rights, al‐
lowing the service engineer to view patient-relevant data. To obtain these rights, the
Data Access rights.
n Request PDA
Modality Performed Procedure Step

com.log file. The Worklist request and response message attributes may be displayed on
trace level T2.

Extend Trace Level

Fig. 101: Modality Performed Procedure Step - Extend trace menu
merge_HRI.log”. To interpret the log files, basic knowledge of DICOM is necessary.
user interaction is possible, and, therefore, it is also not possible to perform a worklist re‐
quest from the user interface. Since user interaction is necessary to receive the appropri‐
ate messages in the merge_HRI.log files, the DICOM Test Tools provide the possibility of
enabling user interaction even in full access mode.
n Release Host
After the Worklist request has been performed, disable interaction at the user inter‐
n Transfer Syntax

“abort” the Extend Trace Level function. The original transfer syntaxes will be set
again.
n Merge Trace Level
appendix.
- T1
- T2 Data Set
in the log file.
- T7 Command Set
transfer.

-
T9 PDU Level
Patient Data Access
Data Access rights.
n Request PDA
8.9.2.2 Dicom Analysis

The analysis tools allow for displaying and evaluating messages and images captured by
the Test Receiver (Storage, Basic Print) and displaying the appropriate mergecom.log files.
Fig. 102: Dicom Analysis menu

Dump Message
The image header information of images captured by the Test Receiver (simulate local/
remote receiver) and sent via “Export to Offline” from the own customer user interface or
copied manually into the %MEDHOME%\service\dst\img directory, will be displayed by
different header dump tools. The image has to be selected from a given selection list.
Please note that all saved files may be removed when exiting the DICOM Test Tools (se‐
lectable).
Fig. 103: Dicom Dump Message mc3list

Fig. 104: Dicom Dump Message binary

Fig. 105: Dicom Dump Message full
Verify Message
The image header information of images captured by the Test Receiver (simulate local/
remote receiver) and sent via “Export to Offline” from the own customer user interface or
copied manually to the %MEDHOME%\service\dst\img directory, will be evaluated for
DICOM conformity. Please note that not all image header attributes marked "Error" are in
violation of the DICOM Standard. For example, missing or wrong attributes will be dis‐
played even if they are optional attributes. The tool provides a means of identifying the
nature of such “Error” messages. Each indicated header attribute should also be verified
manually using the DICOM Standard.

Fig. 106: Dicom Verify Message menu
Compare Message
Two images captured by the Test Receiver (simulate local/remote receiver) and sent via
“Export to Offline” from the own customer user interface or copied manually to the
%MEDHOME%\service\dst\img directory, will be compared. The message has to be se‐
lected by the user from a given selection list.
The following example shows a possible test scenario:
n Send an image to a remote DICOM node.
n Simulate the remote node and resend the same image. This image will be stored on
the hard disk in DICOM format.
n Simulate the local receiver and send the image from the remote system to the local
system. This image will also be stored on the hard disk in DICOM format.
n Compare the sent image with the received image.

Fig. 107: Dicom Compare Message menu
Examine Logs
This menu item displays the log directory including the mergecom.log files of the appro‐
priate DICOM services. Choose the process for which you want to see the log file:
Merge log files
Application Storage SCU/SCP merge_stu.log

Test Tools Storage SCU merge_dst_sscu.log (process log:
dst_sscu_out.log)
Test Tools Storage SCP merge_dst_sscp.log (process log:
dst_sscp_out.log)
Application Storage Commitment SCU merge_stu.log
Application Query/Retrieve SCU merge_stu.log
Application Basic Print SCU merge_hc.log
Test Tools Basic Print SCP merge_dst_pscp.log (process log:
dst_pscp_out.log)

Application Worklist SCU merge_HRI.log

Application Modality Performed Procedure merge_HRI.log
Step SCU
The log file is displayed when you click the appropriate file name.
Fig. 108: Dicom Examine Logs menu
Display Image
DICOM images captured by the Test Receiver (simulate local/remote receiver) and sent via
"Export to Offline" from the own customer user interface or copied manually to the
%MEDHOME%\service\dst\img directory, will be displayed. The image has to be selec‐
ted by the user from a given selection list.

The viewer is a Java applet that does not support all types of DICOM images. If the
images cannot be displayed properly, you need to transfer them to your PC and display
them with other viewer applications, such as the MV300 Viewer.
The following images cannot be displayed:

- Monochrome 16 bit-images (data is stored as 8 bit, 10 bit ,15bit, or 16 bit data)
- Palette color images
 - Multiframe images - only the frame in the middle of the sequence will be displayed
- Images that do not have the attributes of group 2 (part 10 header for offline images)
The following images are displayed:

- Monochrome 8-bit images and 16-bit images (data is stored as 12 bit data)
- RGB images
- All types of overlay data
- JPEG compressed images
Fig. 109: Dicom Display Image menu

Fig. 110: The Dicom Display Image viewer
Display Print
With this option, the bitmaps generated by the camera simulator will be displayed on the
screen. Please note that the bitmap is exactly like the scanning array of the laser camera,
i.e., the images are mirrored, since the image is printed on the back side of the film. The
pictures are in BMP (Windows bitmap) format. They are also located in the %MEDCOM%
\service\dst\img directory, and may be copied to a floppy disk for further evalua‐
tion.

Fig. 111: Dicom Display Print menu
8.9.2.3 Merge Log File

This example shows the merge_stu.log with trace level T2, T3, T7, and T9.
1. Each DICOM communication starts with the Association Negotiation, which may
be displayed on trace level T3. The Service Class User (SCU) sends an Association Re‐
quest message to the provider and presents all supported objects with a list of pro‐
posed Transfer Syntaxes (in this case only one). Each object will be identified by a
Presentation Context ID. Additionally, the Application Entity Titles (AETs) and the
maximum Protocol Data Unit size (PDU) will be transferred.
(312) 07-21 14:58:22.84 MC3 T3: REQUEST Association Parameters:
(312) 07-21 14:58:22.84 MC3 T3: | Calling_presentation_address: cmv10001
(146.254.120.75)
(312) 07-21 14:58:22.85 MC3 T3: | Called_presentation_address:
(312) 07-21 14:58:22.85 MC3 T3: | Called_application_title: CSYNGO1
(312) 07-21 14:58:22.85 MC3 T3: | Calling_application_title: 049SA1DCDADRSP
(312) 07-21 14:58:22.85 MC3 T3: | Application_context_name:
1.2.840.10008.3.1.1.1
(312) 07-21 14:58:22.85 MC3 T3: | PDU_maximum_length: 28672
(312) 07-21 14:58:22.85 MC3 T3: | Implem_class_uid: 1.3.12.2.1107.5.8

(312) 07-21 14:58:22.85 MC3 T3: | Version_name: SNKIT_1.10

(312) 07-21 14:58:22.85 MC3 T3: | Max_operations_invoked: Not Sent
(312) 07-21 14:58:22.85 MC3 T3: | Max_operations_performed: Not Sent
(312) 07-21 14:58:22.85 MC3 T3: | PRESENTATION CONTEXTS:
(312) 07-21 14:58:22.86 MC3 T3: | (1)Pres_context_id: 1
(312) 07-21 14:58:22.86 MC3 T3: | (1)Abstract_syntax:
1.2.840.10008.5.1.4.1.1.4 (STANDARD_MR)
(312) 07-21 14:58:22.86 MC3 T3: | (1) Proposed Transfer Syntaxes:
(312) 07-21 14:58:22.86 MC3 T3: | 1.2.840.10008.1.2 (Implicit
Little Endian)
(312) 07-21 14:58:22.86 MC3 T3: | (1)SCU Role: Not sent (requestor supports SCU)
(312) 07-21 14:58:22.86 MC3 T3: | (1)SCP Role: Not sent (requestor supports SCP)
(312) 07-21 14:58:22.86 MC3 T3: | (1)No extended application info
1.2.840.10008.5.1.4.1.1.1 (STANDARD_CR)
(312) 07-21 14:58:22.87 MC3 T3: | (2)Proposed Transfer Syntaxes:
(312) 07-21 14:58:22.87 MC3 T3: | 1.2.840.10008.1.2 (Implicit
Little Endian)
(312) 07-21 14:58:22.87 MC3 T3: | (2) SCP Role: Not sent (requestor supports SCP)
........
.........
.........
1.2.840.10008.5.1.4.1.1.1.2.1 (STANDARD_MG_PROC‐
ESS)
(312) 07-21 14:58:23.02 MC3 T3: | (21)Proposed Transfer Syntaxes:
(312) 07-21 14:58:23.02 MC3 T3: | 1.2.840.10008.1.2 (Implicit
Little Endian)
(312) 07-21 14:58:23.02 MC3 T3: | (21) SCP Role: Not sent (requestor supports SCP)
2. The response of the Service Class Provider shows the objects supported (accep‐
ted) and the proposed Transfer Syntaxes to be used.
(312) 07-21 14:58:23.02 MC3 T3: RESPONSE Association Parameters:

(312) 07-21 14:58:23.02 MC3 T3: | Calling_presentation_address: cmv10001

(146.254.120.75)
(312) 07-21 14:58:23.02 MC3 T3: | Called_presentation_address:
(312) 07-21 14:58:23.02 MC3 T3: | Called_application_title: CSYNGO1
(312) 07-21 14:58:23.02 MC3 T3: | Calling_application_title: 049SA1DCDADRSP
(312) 07-21 14:58:23.03 MC3 T3: | Application_context_name:
1.2.840.10008.3.1.1.1
(312) 07-21 14:58:23.03 MC3 T3: | PDU_maximum_length: 28672
(312) 07-21 14:58:23.03 MC3 T3: | Implem_class_uid: 1.3.12.2.1107.5.9.990801
(312) 07-21 14:58:23.03 MC3 T3: | Version_name: SIEMENS_SWFVA47A
(312) 07-21 14:58:23.03 MC3 T3: | Max_operations_invoked: Not Sent
(312) 07-21 14:58:23.03 MC3 T3: | Max_operations_performed: Not Sent
(312) 07-21 14:58:23.03 MC3 T3: | PRESENTATION CONTEXTS:
1.2.840.10008.5.1.4.1.1.4 (STANDARD_MR)
(312) 07-21 14:58:23.03 MC3 T3: | (1)Result_transfer_syntax:
1.2.840.10008.1.2 (Implicit Little Endian)
(312) 07-21 14:58:23.04 MC3 T3: | (1)SCU Role: Not sent (remote accepts requestor SCU
role)
(312) 07-21 14:58:23.04 MC3 T3: | (1) SCP Role: Not sent (remote accepts requestor
SCP role)
(312) 07-21 14:58:23.04 MC3 T3: | (1)Negotiation Result: Accepted
1.2.840.10008.5.1.4.1.1.1 (STANDARD_CR)
(312) 07-21 14:58:23.04 MC3 T3: | (2)Result_transfer_syntax:
1.2.840.10008.1.2 (Implicit Little Endian)
(312) 07-21 14:58:23.04 MC3 T3: | (2)SCU Role: Not sent (remote accepts requestor SCU
role)
SCP role)
(312) 07-21 14:58:23.05 MC3 T3: | (2)Negotiation Result: Accepted
..............
..............
..............


1.2.840.10008.5.1.4.1.1.1.2.1 (STANDARD_MG_PROC‐
ESS)
(312) 07-21 14:58:23.20 MC3 T3: | (21)Result_transfer_syntax: (Implicit Big Endian)
(312) 07-21 14:58:23.20 MC3 T3: | (21)SCU Role: Not sent (remote accepts requestor
SCU role)
SCP role)
(312) 07-21 14:58:23.20 MC3 T3: | (21)Negotiation Result: REJECTED: Abstract syntax
3. After the Association Negotiation, the “Command Set” of the first object (e.g., im‐
age) will be sent and may be displayed on trace level T7. All attributes within the
Command Set belong to group 0000 and indicate which type of object will be sent
(context ID and affected SOP Class UID) and the unique object identification (Affec‐
ted SOP Instance UID)
(409) 07-21 14:58:23.34 MC3 T7: Message received on context 5
(409) 07-21 14:58:23.34 MC3 T7: Group 0x0000 Elements:
(409) 07-21 14:58:23.34 MC3 T7: (0000,0000) Group 0000 Length
(409) 07-21 14:58:23.34 MC3 T7: (1): 126
(409) 07-21 14:58:23.34 MC3 T7: (0000,0002) Affected SOP Class UID
(409) 07-21 14:58:23.34 MC3 T7: (1): 1.2.840.10008.5.1.4.1.1.2
(409) 07-21 14:58:23.34 MC3 T7: (0000,0100) Command Field
(409) 07-21 14:58:23.34 MC3 T7: (1): 1
(409) 07-21 14:58:23.35 MC3 T7: (0000,0110) Message ID
(409) 07-21 14:58:23.35 MC3 T7: (1): 0
(409) 07-21 14:58:23.35 MC3 T7: (0000,0700) Priority
(409) 07-21 14:58:23.35 MC3 T7: (1): 0
(409) 07-21 14:58:23.35 MC3 T7: (0000,0800) Data Set Type
(409) 07-21 14:58:23.35 MC3 T7: (1): 0
(409) 07-21 14:58:23.35 MC3 T7: (0000,1000) Affected SOP Instance UID
(409) 07-21 14:58:23.35 MC3 T7: (1):
1.3.12.2.1107.5.1.3.24013.4.0.2508718952428
4. On trace level T2, the “Command Set” with the additional information from the
message ID is displayed again. This ID shows the used Transfer Syntax, where
100 is equal to Implicit Value Representation, Little Endian
101 is equal to Explicit Value Representation, Little Endian
102 is equal to Explicit Value Representation, Big Endian
104 is equal to RLE
105 is equal to JPEG Baseline (lossy)

106 is equal to JPEG Extended_2_4 (lossy)

122 is equal to JPEG_Lossless_Here_14
After the Command Set, the “Data Set”, including all other attributes of the sent ob‐
ject, will be displayed. In case of an image transfer, these attributes are identical to
the image header information. In case of a Query or Worklist request, you can view
the attributes sent within these requests.
The value length will be shown within ( ) and the value itself within | |.
Command Set:
(409) 07-21 14:58:26.37 MC3 T2: Message (STANDARD_CT,C_STORE_RQ) received on
context 5
(409) Message ID: 100
(409) Service Supported: STANDARD_CT (0032)
(409) Command Supported: C_STORE_RQ
(409) Message Attributes:
(409) 0000,0000 Group 0000 Length VR: UL VM: 1
(409) (0000004) |126|
(409) 0000,0002 Affected SOP Class UID VR: UI VM: 1
(409) (0000025) |1.2.840.10008.5.1.4.1.1.2|
(409) 0000,0100 Command Field VR: US VM: 1
(409) (0000002) |1|
(409) 0000,0110 Message ID VR: US VM: 1
(409) (0000002) |0|
(409) 0000,0700 Priority VR: US VM: 1
(409) (0000002) |0|
(409) 0000,0800 Data Set Type VR: US VM: 1
(409) (0000002) |0|
(409) 0000,1000 Affected SOP Instance UID VR: UI VM: 1
(409) (0000043) |1.3.12.2.1107.5.1.3.24013.4.0.2508718952428|
Data Set:
(409) 0008,0008 Image Type VR: CS VM: 1-n
(409) (0000035) |ORIGINAL|
(409) |PRIMARY|
(409) |LOCALIZER|
(409) |CT_SOM5 TOP|
(409) 0008,0016 SOP Class UID VR: UI VM: 1
(409) (0000025) |1.2.840.10008.5.1.4.1.1.2|
(409) 0008,0018 SOP Instance UID VR: UI VM: 1
(409) (0000043) |1.3.12.2.1107.5.1.3.24013.4.0.2508718952428|
(409) 0008,0020 Study Date VR: DA VM: 1

(409) (0000008) |20000711|

(409) 0008,0021 Series Date VR: DA VM: 1
(409) (0000008) |20000711|
(409) 0008,0022 Acquisition Date VR: DA VM: 1
(409) (0000008) |20000711|
(409) 0008,0023 Image Date VR: DA VM: 1
(409) (0000008) |20000711|
(409) 0008,0030 Study Time VR: TM VM: 1
(409) (0000013) |143100.140000|
(409) 0008,0031 Series Time VR: TM VM: 1
(409) (0000013) |143145.375000|
(409) 0008,0032 Acquisition Time VR: TM VM: 1
(409) (0000013) |143203.890001|
(409) 0008,0033 Image Time VR: TM VM: 1
(409) (0000013) |143203.890001|
(409) 0008,0050 Accession Number VR: SH VM: 1
(409) (0000010) |FONo200012 |
(409) 0008,0060 Modality VR: CS VM: 1
(409) (0000002) |CT|
(409) 0008,0070 Manufacturer VR: LO VM: 1
(409) (0000007) |SIEMENS|
(409) 0008,0080 Institution Name VR: LO VM: 1
(409) (0000011) |Siemens CTE |
(409) 0008,0081 Institution Address VR: ST VM: 1
(409) (0000032) |Street\x0A/27E5E2/\x0ADistrict\x0ACountry|
(409) 0008,0090 Referring Physician's Name VR: PN VM: 1
(409) (0000061)
|RefFamNam^RefGiveNam^RefMidNam^RefTitle^RefSuf^Ref|
(409) |Pre^RefDegr|
(409) 0008,1010 Station Name VR: SH VM: 1
(409) (0000007) |F24013C|
(409) 0008,1030 Study Description VR: LO VM: 1
(409) (0000020) |Abdomen^AbdThinSlice|
(409) 0008,103E Series Description VR: LO VM: 1
(409) (0000008) |Topogram|
(409) 0008,1040 Institutional Department Name VR: LO VM: 1
(409) (0000000) <null>
(409) 0008,1050 Performing Physician's Name VR: PN VM: 1-n

(409) (0000047) |SchedPerfPhNam1^SchedPerfPhNam2^SchedPerfPhNam3|

(409) 0008,1060 Name of Physician(s) Reading Study VR: PN VM: 1-n
(409) (0000000) <null>
(409) 0008,1070 Operator's Name VR: PN VM: 1-n
(409) (0000012) |Dr. Gruening|
(409) 0008,1080 Admitting Diagnosis Description VR: LO VM: 1-n
(409) (0000015) |LWS Fehlerbild1|
(409) 0008,1090 Manufacturer's Model Name VR: LO VM: 1
(409) (0000011) |Volume Zoom|
(409) 0008,2111 Derivation Description VR: ST VM: 1
(409) (0000000) <null>
(409) 0010,0010 Patient's Name VR: PN VM: 1
(409) (0000040) |CCTJul2000^VZVA20A^SpineSSD^Dr.^CCC_(\xFF\xFF)|
(409) 0010,0020 Patient ID VR: LO VM: 1
(409) (0000009) |PatID_VZ3|
(409) 0010,0030 Patient's Birth Date VR: DA VM: 1
(409) (0000008) |19550824|
(409) 0010,0032 Patient's Birth Time VR: TM VM: 1
(409) (0000000) <null>
(409) 0010,0040 Patient's Sex VR: CS VM: 1
(409) (0000001) |F|
(409) 0010,1000 Other Patient IDs VR: LO VM: 1-n
(409) (0000000) <null>
(409) 0010,1001 Other Patient Names VR: PN VM: 1-n
(409) (0000000) <null>
.................
.................
(409) 0018,0010 Contrast/Bolus Agent VR: LO VM: 1
(409) (0000000) <null>
(409) 0018,0015 Body Part Examined VR: CS VM: 1
(409) (0000007) |ABDOMEN|
..................
(409) 0018,1000 Device Serial Number VR: LO VM: 1
(409) (0000000) <null>
(409) 0018,1020 Software Version(s) VR: LO VM: 1-n
(409) (0000007) |VA20A.1|
.................
(409) 0018,5100 Patient Position VR: CS VM: 1

(409) (0000003) |HFS|

(409) 0020,000D Study Instance UID VR: UI VM: 1
(409) (0000043) |1.3.12.2.1107.5.1.3.24013.4.0.2883410072770|
(409) 0020,000E Series Instance UID VR: UI VM: 1
(409) (0000043) |1.3.12.2.1107.5.1.3.24013.4.0.2882929363340|
(409) 0020,0010 Study ID VR: SH VM: 1
(409) (0000001) |1|
(409) 0020,0011 Series Number VR: IS VM: 1
(409) (0000001) |1|
(409) 0020,0012 Acquisition Number VR: IS VM: 1
(409) (0000001) |1|
(409) 0020,0013 Image Number VR: IS VM: 1
(409) (0000001) |1|
(409) 0020,0032 Image Position (Patient) VR: DS VM: 3
(409) (0000048) | 0|
(409) | -398|
(409) | -1|
(409) 0020,0037 Image Orientation (Patient) VR: DS VM: 6
(409) (0000096) | 0|
(409) | 1|
(409) | 0|
(409) | 0|
(409) | 0|
(409) | -1|
(409) 0020,0052 Frame of Reference UID VR: UI VM: 1
(409) (0000043) |1.3.12.2.1107.5.1.3.24013.4.0.2507320363132|
(409) 0020,0060 Laterality VR: CS VM: 1
(409) (0000000) <null>
(409) 0020,1002 Images in Acquisition VR: IS VM: 1
(409) (0000001) |0|
(409) 0020,1040 Position Reference Indicator VR: LO VM: 1
(409) (0000000) <null>
(409) 0020,1041 Slice Location VR: DS VM: 1
(409) (0000016) | -1|
(409) 0020,4000 Image Comments VR: LT VM: 1
(409) (0000000) <null>
(409) 0028,0002 Samples per Pixel VR: US VM: 1
(409) (0000002) |1|

(409) 0028,0004 Photometric Interpretation VR: CS VM: 1

(409) (0000011) |MONOCHROME2|
(409) 0028,0010 Rows VR: US VM: 1
(409) (0000002) |512|
(409) 0028,0011 Columns VR: US VM: 1
(409) (0000002) |512|
(409) 0028,0030 Pixel Spacing VR: DS VM: 2
(409) (0000032) | 1|
(409) | 1|
(409) 0028,0100 Bits Allocated VR: US VM: 1
(409) (0000002) |16|
(409) 0028,0101 Bits Stored VR: US VM: 1
(409) (0000002) |12|
(409) 0028,0102 High Bit VR: US VM: 1
(409) (0000002) |11|
(409) 0028,0103 Pixel Representation VR: US VM: 1
(409) (0000002) |0|
.................
(409) 0028,1050 Window Center VR: DS VM: 1-n
(409) (0000016) | 50|
(409) 0028,1051 Window Width VR: DS VM: 1-n
(409) (0000016) | 350|
(409) 0028,1052 Rescale Intercept VR: DS VM: 1
(409) (0000016) | -1024|
(409) 0028,1053 Rescale Slope VR: DS VM: 1
(409) (0000016) | 1.0002441|
.......................
(409) 7FE0,0010 Pixel Data VR: OW VM: 1
(409) <Callback routine>
(409) ===== End of Message ID: 100 =====
5. After each object (image), a response indicating the status of the transfer (0=suc‐
cess) will be sent from the provider. A table of the status codes is available on the
intranet at http://dicom.med.siemens.de at DICOM - Glossary&Tables.
This “Command Set” message may be displayed on T7.
(409) 07-21 14:58:29.85 MC3 T7: Message (STANDARD_CT,C_STORE_RSP) sent on
context 5
(409) 07-21 14:58:29.85 MC3 T7: Group 0x0000 Elements:
(409) 07-21 14:58:29.86 MC3 T7: (0000,0000) Group 0000 Length

(409) 07-21 14:58:29.86 MC3 T7: (1): 126

(409) 07-21 14:58:29.86 MC3 T7: (0000,0002) Affected SOP Class UID
(409) 07-21 14:58:29.86 MC3 T7: (1): 1.2.840.10008.5.1.4.1.1.2
(409) 07-21 14:58:29.86 MC3 T7: (0000,0100) Command Field
(409) 07-21 14:58:29.86 MC3 T7: (1): 32769
(409) 07-21 14:58:29.86 MC3 T7: (0000,0120) Message ID Being Responded To
(409) 07-21 14:58:29.87 MC3 T7: (1): 0
(409) 07-21 14:58:29.87 MC3 T7: (0000,0800) Data Set Type
(409) 07-21 14:58:29.87 MC3 T7: (1): 257
(409) 07-21 14:58:29.87 MC3 T7: (0000,0900) Status
(409) 07-21 14:58:29.87 MC3 T7: (1): 0
(409) 07-21 14:58:29.87 MC3 T7: (0000,1000) Affected SOP Instance UID
(409) 07-21 14:58:29.87 MC3 T7: (1):
1.3.12.2.1107.5.1.3.24013.4.0.2508718952428
6. When you turn on trace level T9, you will also see the entire association on Proto‐
col Data Unit level (PDU). This will add more information to the log file,which is help‐
ful in some special cases, e.g., if the transfer is interrupted, you can see how many
packets were successfully transferred.
The Association Release request and response can only be seen on trace level T9.
(409) 07-21 14:58:29.96 MC3 T9: PDU Type: 05 (Assoc_Rel_RQ) Received
(409) 07-21 14:58:29.96 MC3 T9: Reserved Byte: 00
(409) 07-21 14:58:29.96 MC3 T9: PDU length: 0000 0004 (4 bytes)
(409) 07-21 14:58:29.96 MC3 T9: Reserved Bytes (7-10): 0000 0000
(409) 07-21 14:58:29.96 MC3 T9: PDU Type: 06 (Assoc_Rel_RP) Sent
(409) 07-21 14:58:29.96 MC3 T9: Reserved Byte: 00
(409) 07-21 14:58:29.96 MC3 T9: PDU length: 0000 0004 (4 bytes)

8.10 File & Image Tools
8.10.1 General
8.10.1.1 Introduction
The service application File & Image Tools provides functionality for transferring file(s)
and medical image(s) from a syngo-based system to a remote computer, e.g., a remote
server or a service laptop, and vice versa. Raw data can be handled the same way as im‐
ages if they are stored as a DICOM object in the database.
8.10.1.2 Features
The File & Image Tools functionality can be divided into the following main features:
n Transfer file(s) and image(s) from the system to a remote computer and vice versa
n Extract file(s) or image(s) to be transferred
n Display the image header
n Display / modify the Transfer List of the extracted file(s) and image(s)
The following transfer modes are available:
n Transfer to system, by means of a transfer from a remote computer (e.g., Remote
Server) to the system.
n Transfer from system, by means of a transfer from the system to the remote comput‐
er.
n The Transfer Manager mechanism supports two transfer start times: immediate
(transfer begins when you select a file and then activate the transfer with the ’Go’ but‐
ton) and preferred (transfer is scheduled for a later date).
8.10.2 Functions
8.10.2.1 Start File & Image Tool

The File & Image Tool can be started from the Home menu by clicking the File & Image
Tool button. Once you have started this function, you will see the File & Image Tool
frame in the following figure. Select a command to be performed from the Source selec‐
tion box.

Fig. 112: Start the File & Image Tool
n Source
The Source selection box contains a list of applications that can be executed within
the File & Image Tools service function. When you select an item from the Source
list, the Action button is added to the Navigation frame.
n Navigation bar
- Home
Brings you back to the Home Page.
- Help
Launches the Online Help window.
8.10.2.2 Modes
The File & Image Tools function allows a bi-directional transfer of any file from the sys‐
tem to a remote location, such as a Remote Server or PC, or vice versa. A modem and
router connection is supported. User interaction takes place via the Action item and sup‐
ports two transfer modes (Transfer from system / Transfer to system).
n Configuration
Please note that the File & Image Tool requires the FTP Target information from the
remote computer. When a transfer is initiated, the remote computer data is verified in
the target list. The target list has to be configured in the Configuration menu. Please
refer to the Online Help of the Configuration/Service/FTP service function for more
information on adding or modifying FTP targets. Also, refer to the Remote Server doc‐
umentation (not part of Service Software Online Help) for detailed information re‐
garding the prerequisites for adding a system to the Remote Server.

n FTP Protocol
All transfers are based on the FTP protocol. Once a transfer is started, the system ini‐
tiates an FTP session to the remote computer and logs into the rdiagftp account. If
authentication is successful, the transfer becomes active.
When the error message A connection with the server could not be established ap‐
 pears in a pop-up window, verify that the FTP server (receiver) on the remote computer
has been started and configured properly. Also, ensure that the FTP account password
has been configured correctly.
n File Name
The transferred file name on the remote computer has the following format:
<modality><serial number>_<original filename>
Example: mr275_AcrobatInstall.log
<material-number>_<serial number>_<original filename>
Example: 01234567_275_AcrobatInstall.log
The transferred DICOM object name on the remote computer has the following for‐
mat:
<modality><serial number>_<DICOM object Loyd-number>.img
Example: mr275_2.0.21456.img
<material-number>_<serial number>_<DICOM object Loyd-number>.img
Example: 01234567_275_2.0.21456.img
 Transferred data is not encoded or compressed by the File & Image Tool transfer mech‐
anisms.
8.10.2.3 Start Time

Two transfer start times are supported by the File & Image Tools. The local or remote
user can submit a transfer start time by selecting the item When: immediately or prefer‐
red in the various Transfer menus.

Fig. 113: Start File & Image Tools
n Immediately
Starts the transfer once you select a file/image and click the Go button.
If transfer is interrupted, e.g., the communication line is hung up, the Transfer Manag‐
er will respond by re-attempting to transfer the file/image to the remote computer. In
this case, the transfer behaves like a preferred transfer.
When you start the service software as a local user, the system first establishes a con‐
nection to the remote computer. Afterwards, you can select the file to be transferred.
For remote users, the existing connection is used for file exchange.
n Preferred
Initiates an unattended batch transfer.
Once the user has initiated a preferred transfer time, a batch transfer queue is added
to the Transfer Manager, and the system will try and establish a connection to the re‐
mote computer at the pre-defined time (local time + selected hour(s)). A transfer will
be restarted automatically if the transfer was not completed successfully (e.g., the line
was disconnected, or remote access was set to “No Access”).
At first, an immediate retry is attempted 5 times. If this is not successful, the retry is
queued again after 1, 6, 12, and 24 hours or when the system is booted. The 24 hour
retry is performed for a maximum of 7 days.
The Transfer to system function is available only in connection with a Remote Serv‐
er. Refer to the Remote Server manual for information on how to add a system on the
Remote Server.
8.10.2.4 Patient Data Access

If you start the File & Image Tools/Image remotely and the Patient Data Access is disa‐
bled, the following window is displayed.

Fig. 114: Patient Data Access Request (PDA)
n Source
the File & Image Tools service function. When you select select an item from the
Source list, click the Action button to add the Patient Data Access section to the nav‐
igation frame.
n Action
The Action selection box is context-sensitive and contains all Action items available
for the selected Source. When you select an item from the Action list, the contents of
the function frame (right-hand screen) will change accordingly.
n Patient Data Access
Patient Data Access controls whether the patient name or the Loyd number is dis‐
played to select the patient images.
- Enabled
The patient name is displayed.
- Disabled
The Loyd number is displayed.
- Please enter your name
Enter your name.
- Request PDA
When you click the Request PDA (Patient Data Access) button, the request for ac‐
cessing and displaying the patient name in the function frame will be sent to the
local operator.
n Navigation bar
- Home
Brings you back to the home page.

-Help
Launches the Online Help file.
The following step-by-step instructions show the procedure to enable Patient Data Ac‐
cess.
Request from the remote user
The service technician is logged in remotely and needs to transfer images with Patient
Data Access disabled. If he continues without requesting Patient Data Access, the pa‐
tient images can be selected by the Loyd number. If the correct Loyd number is not avail‐
able, he has to submit a request for Patient Data Access to the local operator by entering
his name in the Please enter your Name field and clicking the Request PDA button.
The following pop-up window is displayed.

Acknowledgement from the local operator

The local operator can see the Patient Data Access request from the remote user in the
Remote Service Access Control Platform. When you select the Allow Patient Access
box and click the Apply button, the status information Current Patient Mode: switches
from disabled to enabled.

Fig. 117: Patient Data Access acknowledgement
The remote user will see the following pop-up window.

Fig. 118: Patient Data Access acknowledgement
When you confirm the pop-up, the following File & Image Tools/Image window will be
automatically displayed.

Fig. 119: Action items for enabled
Patient Data Access is now enabled, and patient information will be displayed. Patient
Data Access is active for the duration of the remote service session. For example, if you
exit the File & Image Tools to perform another service function and then come back to
the File & Images Tools, the Patient Data Access remains active until the remote user
closes the remote service session.
8.10.3 Source
8.10.3.1 Image
This chapter contains all Action items with regard to the transfer of DICOM Objects (e.g.,
images and raw data).
There is no difference between extracting and transferring a medical DICOM image or a
raw data object since both DICOM objects are stored in the syngo database and are trea‐
ted the same way.
Patient information can only be accessed remotely if the customer has released the Pa‐

tient Data Access. Therefore, the graphical user interface looks different depending on
whether Patient Data Access is enabled or disabled (see chapter ( Patient Data Ac‐
cess / Page 203) for more details).
 All confidential patient information is removed from the DICOM object header prior to an
image/raw data transfer or when you use the Extract only image function.

Fig. 120: Action items for enabled
n Source
the File & Image Tools service function. When you select select an item from the
Source list, click the Action button to add the Patient Data Access section to the nav‐
igation frame.
n Action
The Action selection box is context-sensitive and contains all Action items available
for the selected Source. When you select an item from the Action list, the contents of
the function frame (right-hand screen) will change accordingly.
n Patient Data Access
When the Files & Image Tools are started locally, Patient Data Access is always ena‐
bled and cannot be disabled.
n Navigation bar
- Home
- Help
Transfer from system

The Transfer from system mode transfers DICOM objects (images or raw data) from the
system to a remote computer, such as a PC or a Remote Server. Please see chapter
( Start Time / Page 202) for more details on the transfer start time (immediately or pre‐
ferred).

Fig. 121: Image Transfer from system
n Patient
The Patient selection box contains a list of all patients available on the system. When
you select an item from the patient list, the Study list is automatically updated.
n Study
The Study selection box contains a list of all studies available for the selected patient.
When you select an item from the Study list, the Series list is automatically updated.
n Series
The Series selection box contains a list of all series available for the selected study.
When you select an item from the Series list, the image thumbnails will be displayed
automatically if the Show Thumb Nails box has been checked.
n Selected Images
Here, you will find the images already selected for transfer to the remote computer.
You can select an image by clicking the image icon or the corresponding image num‐
ber.
n Images
The image icons will be displayed here. Below the image, you will find the image
number and the Loyd number. The Loyd number identifies the image in the syngo da‐
tabase. The Images menu also supports multiple selections. To make multiple selec‐
tions, press and hold the CTRL key and click the images you want to select.
n To Target
Identifies the remote computer. This is either the Remote Server identification (if you
are logged in through the Remote Server) or the remote PC identification. Targets can
be added or modified in the configuration using Service/FTP.

n Show Thumb Nails

Images are displayed as image thumbnails by default. If you expect too many images
and want to save transfer time, you can deselect this option to display the image
numbers instead of the images.
Fig. 122: Image numbers only
n When
Select the appropriate transfer start time. Either immediately (start now) or prefer‐
red (start later at 22:00). For more details on the transfer start time, see chapter
( Start Time / Page 202).
n Action Bar
- Delete
The highlighted image in the Selected Images menu will be removed from the
transfer list once Delete is clicked.
- Reset
Removes all entries from the transfer list in the Selected Images menu.
- Go
When a rather large file is transferred, a new window, which shows the file transfer
progress, is opened. Each file selection will open another window in order to trans‐
fer files in parallel.
Fig. 123: Tranfer progress
n Source File Name(s)

The path and file name(s) of the file to be transferred to the remote computer.

n Target
Identifies the remote computer. This is the Remote Server identification (if you are
logged in through the Remote Server) or the remote PC identification. Targets can be
added or modified in the configuration using Service/FTP.
n % done
Indicates the progress of the file transfer in percent.
n Retry Count
Shows the number of immediate transfer retries. The immediate transfer will be stop‐
ped after 5 attempts, and the job will be queued for a preferred transfer. Please refer
to chapter ( Start Time / Page 202) for more details on the immediately/preferred
transfer start time.
n Transfer Status
Displays the actual status of the transfer. This can be an error message or information
regarding the transfer itself.
n Abort
Aborts the file transfer function and removes it from the transfer manager queue.
Extract Only
The Extract Only function prepares images for transmission, so that they can be picked
up later on request. For this purpose, the selected images are copied to the %medhome%
\service\extract1 directory. Use the Extract List / Transfer from system (see chapter
( Extract List / Page 223)) functions to transfer the extracted images, or use the Trans‐
fer list / Show/Delete (see chapter ( Transfer List / Page 227)) function to show or de‐
lete the extracted DICOM objects.
Fig. 124: Image Extract only

n Patient
n Study
n Series
n Selected Images
Here, you will find the images already selected for the transfer to the remote comput‐
er. You can select an image by clicking the image icon or the corresponding image
number.
n Images
The image icons will be displayed here. The image number and the Loyd number are
displayed below the image. The Loyd number identifies the image in the syngo data‐
base. The Images menu also supports multiple selections. To make multiple selec‐
tions, press and hold the CTRL key and click the images you want to select.
n to Target
n Show Thumb Nails
Images are displayed as image thumbnails by default. If you expect too many images
and want to save transfer time, you can deselect this option to display the image
numbers instead of the images.
Fig. 125: Image numbers only
n Action Bar
- Delete
- Reset
Removes all entries from the transfer list in the Selected Images menu.

- Go
progress, is opened. Each file selection will open another window in order to trans‐
fer files in parallel.

n Target
n % done
n Retry Count
n Transfer Status
n Abort
Display Header
To find system errors without viewing the whole image, only the anonymous header in‐
formation of an extracted DICOM object (image or raw data) will be displayed. The extrac‐
ted header information will be displayed in a separate browser window.

Fig. 127: Image Display Header
First, select the appropriate image with the header information that you are interested in:
n Patient
n Show Thumb Nail checkbox
Images will be displayed as image thumbnails by default. If you expect too many im‐
ages and want to save transfer time, you can deselect this option to display the image
numbers instead of the image thumbnails.
n Study
n Series
n Images
The image icons will be displayed here. The image number and the Loyd number are
displayed below the image. The Loyd number identifies the image in the syngo data‐
base.
Once you click on the image thumbnail or the image number, a separate browser win‐
dow will be opened with the detailed DICOM header information.
There is a difference between how the local and the remote access mode present the
header information, as shown in the figures below. In remote access mode, the partic‐
ular patient information is anonymized to comply with legal regulations.

Fig. 128: DICOM Header Information - Local
Fig. 129: DICOM Header Information - Remote
Use the Exit button in the Navigation bar to close this window.
8.10.3.2 File
This chapter contains all Action items regarding the transfer of a File.

Only files that are not allocated by the system can be transferred. If you need to transfer
an allocated file, you need to find out which application is allocating the file. Stop that
application with the appropriate service tool.

Images and raw data cannot be transferred with the File function. Please refer to chap‐
ter ( Image / Page 207) for more details on the image transfer functions.
Fig. 130: Action items for File
n Source
list, the Action button is added to the Navigation frame.
n Action
The Action selection box is context-sensitive; it contains all Action items that are
available for the selected Source. When you select an item from the Action list, the
contents of the function frame (right-hand screen) will change accordingly.
n Navigation bar
- Home
- Help

The Transfer from system function transfers files from the system to a remote computer,
such as a PC or Remote Server. Please refer to chapter ( Modes / Page 201) for more de‐
tails on the image transfer functions.

Fig. 131: File transfer from the system
n File Type (Any File)

This selection box contains a list of the predefined options. When you select an op‐
tion, the function frame is automatically updated.
n to Target
n When
Select the appropriate transfer start time. Either immediately (start now) or preferred
(start later at 22:00). For more details on the transfer start time, refer to chapter
n Site Directory
Here you can browse through the directory structure of the system, similar to Micro‐
soft Windows Explorer.
Directories are enclosed with “<>”. Click a directory name only once to open its con‐
tents.
At least one file has to be selected before the Go button in the Navigation bar be‐
comes functional. To select a file for a file transfer, click the file to highlight it. Multi‐
ple file selections are also supported. To select multiple files, press and hold the CTRL
key and click the next file to be selected. To select a range of files, select the first file,
press and hold the SHIFT key, and click the last file to be selected.
n Filter
With this dialog box, you can filter the files to be displayed; e.g., *.txt: all files with the
extension ’.txt’ are displayed.
n Refresh
Refreshes the contents of the Site Directory.

Transfer to system
The Transfer to system function transfers files from a remote computer to the system.
All files will be transferred to the %medhome%\service\incoming 1 directory.
Make sure that the file(s) you want to transfer is/are located on the remote computer. The
file(s) must be located in the <anonymous FTP>/outgoing/<modality> (xx is the
syngo modality; it is to be replaced with the modality, for example, MR or CT) directory on
the remote computer.
Fig. 132: File transfer to the system
n File Type
This selection box cannot be changed.
n from Source
Identification of the remote computer. This must be the remote computer that you
want to transfer the files from.
n Remote Directory
Here you can browse through the directory structure of the remote computer, similar
to Microsoft Windows Explorer. As a default, the system points to the <anonymous
FTP>/outgoing/<modality> (xx is the syngo modality; it is to be replaced with the mo‐
dality, for example, MR or CT) directory on the remote computer.
tents.

n Filter
With the dialog box, you can filter the files to be displayed; e.g., *.txt: all files with the
n Refresh
Refreshes the contents of the Remote Directory.
n Go
progress, is opened. Each file selection will open another window in order to transfer
files in parallel.

n Target
n % done
n Retry Count
n Transfer Status
n Abort

Extract Only
The Extract Only function prepares files for transmission, so that they can be picked up
later on request. For this purpose, the selected files are copied to the %medhome%\serv-
ice\extract1 directory. Use the Extract List / Transfer from system (see chapter
( Extract List / Page 223)) functions to transfer the extracted files, or use the Transfer
List / Show/Delete (see chapter ( Transfer List / Page 227)) function to show or delete
the extracted files.
Images and raw data cannot be extracted using the File / Extract Only function. Please
 use Image / Extract Only (see chapter ( Image / Page 207) for more detailed informa‐
tion).
Fig. 134: File Extract Only
n File Type
This selection box cannot be changed.
n Site Directory
tents.

n Filter
n Action Bar
- Refresh
8.10.3.3 Download List

This chapter contains all Action items to display the files that have been transferred to
the system.
Fig. 135: Action items for Download List
n Source
list, the Action button is added to the navigation frame.
n Action
n Navigation Bar
- Home
Brings you back to the home page. .
- Help

Show/Delete
The Download List / Show/Delete function displays the files that have been transferred
to the system. Please refer to chapter ( Transfer to system / Page 218) for more informa‐
tion on how to transfer files to the system.
Fig. 136: Download List Show/Delete
n Site Directory
tents.
n Filter
n Action Bar
- Refresh
- Delete

8.10.3.4 Extract List

This chapter contains all Action items with respect to the Source selection Extract List.
Fig. 137: Action item for Extract List
n Source
n Action
n Navigation Bar
- Home
- Help

The Transfer from system function allows you to transfer previously extracted images,
raw data, and files from the system to a remote computer, such as a PC or Remote Server.
The information previously provided for Image / Transfer from/to system and File /
Transfer from/to system is also applicable here.

All files in the %medhome%\service\extract 1 directory will be available for selection.

Scroll up and down the menu to browse through the entire list.
Fig. 138: Extract List Transfer from system
n to Target
n When
Select the appropriate transfer start time. Either immediately (start now) or prefer‐
red (start later at 22:00). For more details on the transfer start time, refer to chapter
n Site Directory
tents.
n Filter

n Refresh
n Go
progress, is opened. Each file selection will open another window in order to transfer
files in parallel.

n Target
n % done
n Retry Count
n Transfer Status
n Abort

Show/Delete
With Show/Delete, you can display and/or delete previously extracted images, raw data,
and other files from the extract list. Refer to Image / Extract Only and File / Extract Only
for more information on extracting DICOM objects and files.
All files in the %medhome%\service\extract1 directory will be available for selection.
Scroll up and down the menu to browse through the entire list.
Fig. 140: Extract List Show/Delete
n Site Directory
soft Windows Explorer, beginning at the %medhome%\service\incoming directory.
tents.
n Filter
n Action Bar
- Refresh

- Delete
The highlighted image in the Site Directory menu will be removed from the trans‐
fer list once Delete is clicked.
8.10.3.5 Transfer List

This chapter contains all Action items with regard to the Source Transfer List.
Fig. 141: Action items for Transfer List
n Source
n Action
n Navigation Bar
- Home
- Help
Show/Delete
Show/Delete displays the transfer manager jobs pending for the specified target and may
remove these jobs from the transfer list.
To display or remove pending batch jobs for a specific target, select the appropriate pend‐
ing batch job. Only one pending batch job can be selected at a time.

Fig. 142: Transfer List Show/Delete
n Transfer Manager Queue ID

The unique location of the selected job in the transfer list.
n Entry Time
Shows the time when the queue was added to the transfer list.
Displays the path and the name of the file to be transferred to the remote computer.
n Target
n Transfer Type
Shows the type of transfer that has to be used to transfer the file.
- FTP Upload
Transfers the file from the system to the remote computer using the FTP protocol.
- FTP Download
Transfers the file from the remote computer to the system using the FTP protocol.
- Browser Remote
This mode indicates that the Transfer to system function is “browsing” or retrieving
the directory contents of the Remote Server directory.
- Mail
Mail is being sent to the remote computer using the SMTP protocol.

n Transfer Status
Indicates the progress of the transfer.
- queued
Has been added to the transfer manager queue.
- done
Has been executed successfully and will be automatically removed from the queue
after approximately 5 minutes.
- failed
When a transfer fails, the system will retry automatically. Please refer to chapter
( Start Time / Page 202) for more details on the image transfer functions.
- cancelled
If a transfer is aborted, the job will be relegated to cancelled status.
- initial
The transfer manager initializes the queue job. When the queue job is successfully
initialized, the job will be relegated to queued or active status.
- active
The queued job is executing.
- dialing
The system establishes a modem connection to the remote computer.
- connecting
The TCP/IP connection to the remote computer is being established.
- transferring
The file is being transferred (copied) to/from the remote computer.
- disconnecting
The TCP/IP connection to the remote computer is being disconnected.
- hanging up
The modem connection is being disconnected.
n Transfer Status Details
n Abort Flag
- Queued
This job is entered to the transfer manager queue.
- Aborted
The queued job will be removed from the transfer manager queue.
n Total Bytes to Transfer
Amount of bytes that have to be transferred to the remote computer.
n Actually Transferred Bytes
Total amount of bytes transferred to the remote computer.

n Retry Limit
Shows the number of retries allowed; the number has been fixed to 5 retries.
n Retry Count
Shows the number of transfer retries. The transfer will be stopped after 5 attempts.
n Transfer Time
Shows the time when the file was transferred.
n Action Bar
- Refresh
Refreshes the content of the transfer manager queue.
- Delete
The highlighted selection in the transfer manager queue will be removed from the

8.11 Auto Report

See Siemens Remote Services Configuration ( Auto Report Template configura‐
tions / AXA4-010.843.05)
8.11.1 General
AutoReport is used during various work functions:
n Once configured and enabled, AutoReport is automatically activated when the various
filter criteria are met. This supports the service person during troubleshooting. In par‐
ticular, sporadic problems can be located and reported to the Service Center.
n In addition, AutoReport can trigger a preferred file transfer to collect certain system
reports for further evaluation at the Service Center.
n The AutoReport tool can send a system report to any mail account at Service Head‐
quarters.
n FTP (File Transfer Protocol) is used for file transfer.
n SMTP (Simple Mail Transfer Protocol) is used for mail communication.
8.11.1.2 Features
AutoReport tool features:
n Sending of various notifications, from mail only to mail messages including command
output or file attachments, to a particular user at the Service Center.
n Definition of simultaneous, multiple reports.
n Monitoring of selectable files, Time Triggered and Event Triggered.
- Time Triggered means that the AutoReport application searches for a word or a
combination of words in a defined ASCII file or the event log at an adjustable time.
- Event Triggered means that AutoReport becomes active when a defined event oc‐
curs, e.g., the event DISK_FULL triggers AutoReport to send mail to Headquarters,
or when a file has changed.
n Collecting of system data at an adjustable time and sending it to Headquarters at flexi‐
ble intervals.
8.11.2 Functions
8.11.2.1 Enter AutoReport

The AutoReport can be started from the Home menu by selecting the AutoReport button.
The REPORT selection box containing the site-specific reports and the Enabling Status is
displayed.

Fig. 143: Start Auto Report Tool
n REPORT
The Report selection box contains a list of system-specific reports.
n Enabling Status
The Enabling Status selection box indicates whether the report is enabled or disa‐
bled. To change the status, you have to open the report via the REPORT selection box
and modify the Active checkbox. When this box is checked, the report is enabled.
When you click Save in the Action bar, the status under Enabling Status will be upda‐
ted.
When a report or a template form has been selected from the REPORT selection box, the
full status of the report is shown in the function frame.
Fig. 144: Example - Auto Report Template
n Active
This checkbox is used to enable or disable a report. The action takes effect when the
change is saved via the Save button in the Action bar. The status of this checkbox is
also displayed in the left frame under Enabling Status.

n Name
When the TEMPLATE has been selected, you must enter the name of the report to be
created. If you have selected an existing report and then changed the name, a new
report will be created when the Save button is clicked.
 When you rename a report, the “old” report that has been used as a template does not
get removed or modified in any way.
n Target
Displays the remote computer to which the mail is to be sent. It must be configured in
the Service Configuration function. Mail can be sent to a modality-specific account
on the Remote Server (e.g., rdiag_ct) or to a specific user (e.g., Dieter.Muster‐
mann@med.siemens.de) at the Service Center.
n Save
When you click Save in the Action bar, the changes made to the currently selected re‐
port are stored.
n Delete
The currently displayed report will be removed when you click Delete.
n Begin
The Begin selection box allows you to define the start date of the reporting period.
When using the Report TEMPLATE, the default start date is the creation date.
n End
The End selection box allows you to define the end date of the reporting period. When
using the Report TEMPLATE, the default end date is one year after the Begin date.
8.11.2.2 Sample source?

Sample source? defines the sample source and its sample mechanism. AutoReport allows
for pattern matching on an ASCII file or an event trigger.
Fig. 145: Sample Source?
n Source
You may choose between Event Log as the default or any File to be monitored. When
Event Log is selected, all events that are recorded in the event log / customer log will
be sampled and evaluated. When File is selected, pattern matching of the file con‐
tents will be performed. The file name must be entered in the Sample what? frame.
The file option only works with ASCII files.
8.11.2.3 Sample what?

1) Sample source? is set to Event Log

If the Event Log is selected in the Sample source? frame, all events that are recorded in
the event log files will be sampled and evaluated. Various filter criteria (Severity, Message
ID, Source, Domain) that are also used in the Event Log Reader application can be selec‐
ted. For detailed information on these filters, please refer to the Online Help for the
Event Log Reader.
Fig. 146: Sample what? (Sample Source: Event Log)
n Severity
Classification of the error message. Possible selections are Error, Warning, Informa‐
tion, or All.
n Search Pattern
When a text string is entered, pattern matching is performed with the message text in
the event log file. Wild cards are supported.
n Message ID
Filters on specific Message IDs in the event log file. In the example above, the Mes‐
sage ID 102, which will send a message to Headquarters when the user successfully
logs into the service software, was entered.
n Mode
Toggles between Time Triggered and Event Triggered. If Event Triggered is selected,
the AutoReport will be activated as soon as the defined event occurs; the frame Sam‐
ple when? displays Continuously only. If Time Triggered is selected, the system will
perform pattern matching at the time that has been set in the parameters in the Sam‐
ple when? frame.
n Domain
Allows you to select events from a certain domain (Application, CustomerLog, Se‐
curity, or System).
n Source
Allows you to specify different system software components, e.g., CSA_SAM (SAM ap‐
plication).
2) Sample source? is set to File
If File is selected in the Sample source? frame, the Sample what? frame displays fields that
are necessary for sampling a defined file with a particular search pattern.
Fig. 147: Sample what? (Source: File)

n File Name
Specify the name of the file which is to be sampled. Wild cards are supported.
 Directory names must be separated with a ’\’.
n Search Pattern
When no Search Pattern is entered, AutoReport will send a mail when the file has
been created or changed; otherwise, a mail will be sent when the Search Pattern has
been found by a sample.
n Mode
Toggles between Time Triggered and Event Triggered. If Event Triggered is selected,
the AutoReport will be active as soon as the defined event occurs; the Sample when?
frame displays Continuously only. If Time Triggered is selected, the system will per‐
form pattern matching at the time that has been set in the parameters in the Sample
when? frame.
n Lines
When a search pattern is entered and the Mail: with partial attachment parameter in
the Send what? frame is selected, this value defines the number of Lines to be added
to the mail. The occurrence of the Search Pattern is in the center of the added lines.
8.11.2.4 Sample when?

The sample rate (time and day) can be adjusted in the Sample when? frame. The param‐
eters depend on the mode set in the Sample what? frame.
1) Mode: Event Triggered
Fig. 148: Sample when? Event Triggered
n Continuously
Sampling is performed continuously; AutoReport starts sending the mail when the
event defined by the filters in the Sample what? frame meets the conditions.
2) Mode: Time Triggered
Fig. 149: Sample when? Time Triggered
n Continuously
Specifies a time for continuous sampling and can be adjusted with the Sample times
parameters.

n Sample times (only with Continuously)

The time when the AutoReport starts sampling, in Hours (0 - 23) and Minutes (1 -
59). If you want the AutoReport to start sampling at 3 pm, you must enter 15:00.

It is also possible to enter several sample times.
Use a semicolon (;) to separate the entered values, e.g., 14:45;15:00;15:15.
Fig. 150: Sample when? Daily, weekly, and monthly
n Daily
Select hours and minutes from the corresponding menus.
n Weekly
Select the day of week and the hours and minutes from the corresponding menus.
n Monthly
Select the day of month and the hours and minutes from the corresponding menus.
8.11.2.5 Send what?

The Send what? frame specifies the type of mails, with or without attachments, etc., to
be sent by the AutoReport tool.
Fig. 151: Send what?
n Mail
with no attachment only sends a notification mail with the name of the file that was
entered in the Sample what? frame.
with full attachment sends the whole file attached to the mail.
Partial attachment only sends those lines of the sampled file which meet the filter
criteria that were entered in the Sample what? frame.
as separate file(s) forwards the selected report file(s) to a remote computer using
FTP file transfer, and sends a mail to the remote target. In this case, the FTP target
address can be specified in a selection box. If you cannot find the proper FTP target,
you have to add the FTP target in the Service Configuration function.
as separate file(s) without mails forwards the selected report file(s) to a remote
computer using FTP file transfer, and does not send a mail to the remote target. In
this case, the FTP target address can be specified in a selection box. If you cannot find

the proper FTP target, you have to add the FTP target in the Service Configuration
function.
 The various Mail options only work with the Sample source? mode file.
n Command
The output from the executed application or DOS command entered will be added to
the mail message.
8.11.2.6 Send when?

In the Send when? frame, you can set the time to send the gathered information as a
mail message or separate file. The settings are analogous to the settings in the Sample
when? frame:
Fig. 152: Sample when?
n At once
The AutoReport is generated and sent immediately to the selected target.
n Daily
If Dailyis selected, the selection boxes Hour and Minute will appear. Select hours and
minutes from the corresponding menus.
n Weekly
If Weeklyis selected, the selection boxes Day, Hour, and Minute will appear. Select
day of week, hours, and minutes from the corresponding menus.
n Monthly
If Monthlyis selected, the selection boxes Day, Hours, and Minute will appear. Select
day of month, hours, and minutes from the corresponding menus.

8.11.2.7 Create new AutoReport
Fig. 153: Create new Auto Report
n Activate the AutoReport function in the Service Home menu.

n In the REPORT field, select the entry TEMPLATE.
n Create a representative name (e.g. display_crash) for the new job and enter it in the
Name field.
n You must now specify the various parameters of the AutoReport function for the new
job.
 The forms are fully interactive and the parameters are interdependent.
n Check and, if necessary, adjust the information entered into the Sample source?,
Sample what?, Sample when?, and Send when? fields according to your require‐
ments.
n Verify the Enabling Status, Begin, and End date of the new job and the notification
target.
n Finally, save the modified job by clicking the Save button. A message box appears to
confirm that the data was saved successfully, and the new AutoReport name immedi‐
ately appears under Enabling Status and is marked “Active” by default.
n Close the AutoReport by clicking the Home button in the Navigation bar.

8.12 Utilities
8.12.1 General
This section describes the Utilities functions.
Fig. 154: Source
The Utilities functions include:

n Escape to OS
n Send Message
n Session List
n Process List
n CompMgr List
n System
n Tune CD Burning
n Calibrate Monitor
n Database tools
n Recover CD
8.12.1.2 Features
With Escape to OS, you can enter any command at the OS level.
Send Message is useful for sending a message to the site.
The Session List provides information about the active sessions.
The Process List shows all active processes.

CompMgr List shows all active software components.

With System, you can shut down and restart the system or the application.
Tune CD Burning ensures that the customer can work properly while burning a CD.
The “Calibrate Monitor” tool adjusts the monitor for medical diagnostics.
The “Database tools” help you check and repair the database.
The “Recover CD” tool will help to recover defective CDs.
8.12.2 Functions
8.12.2.1 Escape To OS
This function enables you to execute a command-driven program on the system. It pro‐
vides the capabilities of a regular Command Prompt on the local system. Several prede‐
fined commands are available:
 CAUTION
This function is mainly used with the support of Headquarters.
 Some commands may effect the syngo functionality.
Fig. 155: Escape to OS - Commands
Most of these functions can be used without any parameters.

Use only parameters that are either supported by the Development department or are dis‐
played when you click the Go.
n NT Command Interpreter
n Check syngo Startup
n Check System Changes
n Create ServiceSaveLog
n System Information
n Directory Usage
n Check Local Hard Disks

n Show Ethernet Address

n Execute Service Program
Remote - NT Command Interpreter

Fig. 156: Escape to OS - NT Command Interpreter
Patient Data Access

To start the Escape to OS - NT Command Interpreter remotely, you need service level
“Full Access”.
When the Patient Data Access at the system is disabled, the following pop-up is dis‐
played.
Fig. 157: Patient Data Access is required
Fig. 158: For Patient Data Access your name is required
You need to enter your name. This name is used in the log file to indicate who accessed
the patient data.
This is necessary to ensure patient data security.

Fig. 159: SAM requests Patient Data Access at the remote system
SAM requests patient data access at the system and the user at the system can enable the
access.
Then, the following pop-up window is displayed:
Fig. 160: Patient Data Access changed to enabled
Local NT Command Interpreter

Escape to OS - NT Command Interpreter
Fig. 161: Escape to OS - NT Command Interpreter
NT Command Interpreter
Starts a new instance of the Windows NT command interpreter CMD.EXE. This command
interpreter accepts commands as they are typed in the Command Prompt window. Any
program can be started, even programs with a graphical user interface. The GUI, of
course, will be started on the local system only.
Helpful Commands
For network tests:

Commands at OS level Description

IPCONFIG/ALL Check the local IP configuration
PING magic1.hospital.org Check the low-level connectivity. Try using the name
first. If that fails, try the IP address. If using the IP address
also does not work, the problem is probably due to the
NIC (Network Interface Card) drivers or routing. If ping
works, but something high-level does not work, perform
a test with NBTSTAT.
NBTSTAT -c View the station-determined IP address that is associated
with a name. If the address is wrong, edit the LMHOSTS
file (check HOSTS, as well and/or WINS database); to reset
the address, use the NBTSTAT -R command.
NETSTAT -rn Determine whether the local and remote hosts have a de‐
fault gateway specified.
NSLOOKUP magic1.hospi‐ If DNS is used, find out the corresponding Internet ad‐
tal.org dress. Reverse name lookup works as well.
route Input of a static route (defines a route of a connection to
a node)
TRACERT 155.2.42.117 Trace routing to a destination host (over a maximum of
30 hops).
Various commands:

calc Start the Calculator
clipbrd.exe Start the ClopBook Viewer
compmgmt.msc Computer Manager (Services)
control Start Windows control panel
control appwiz.cpl Add/Remove Programs
control Desk.cpl Display properties
control modem.cpl Display modem settings
control srvmgr.cpl User Manager
dblist Database listing
eventvwr Start Windows Event Viewer
explorer.exe Start Windows File Explorer
ncpa.cpl Start Windows File Explorer
notepad Start the Notepad
opcagt System Management status


regedit Start the Registry Editor
rti startPmgt appl Start the application (syngo)
rti stopPmgt appl Stop the application (syngo)
shutdown -l [Administrator] shutdown of the syngo application
start Start of batch files
startcm Start Component Manager
stopcm Stop the syngo application and the Component Manager
taskmgr.exe Start Windows Task Manager
timedate Opens Date and Time Properties
type <file> Displays file content
Check syngo Startup

Fig. 162: Escape to OS - Check syngo Startup
The following items are checked and displayed: user environment, system environment,
current user, database environment, previous successful startups, and free space on disk.

Check System Changes

Fig. 163: Escape to OS - Check syngo Startup
After the first installation of the syngo software, the system will generate a checksum.
When you start this utility, the system will generate another checksum and compare it
with the previously created one.
This is a simple check to ensure that the system is not infected with viruses.
Create ServiceSaveLog
Fig. 164: Escape to OS - Create ServiceSaveLog
The description of the ServiceSaveLog is the same as for the SaveLog customer.
Please go to Back to overview and then Customer -> SaveLog.

System Information
Fig. 165: Escape to OS - System Information
System Info shows the network IP address, hostname, NT version, and service pack, as
well as the stopped and running processes.
Directory Usage
Fig. 166: Escape to OS - Directory Usage
DIRUSE displays a list of disk usage for a directory tree(s). Required parameters are listed.
To obtain the corresponding list, click Go without a parameter.

Check Local Hard Disk

Fig. 167: Escape to OS - Check Local Hard Disk
All of the system hard disks can be checked using this command.
Show Ethernet Address

Fig. 168: Escape to OS - Show Internet Address
Show Internet address will display the so-called MAC address from the Ethernet card of
the PC.

Execute Service Program

Fig. 169: Escape to OS - Execute Service Program
Execute Service Program

This command allows you to start service programs manually. It should only be per‐
formed by experienced users (developers).
8.12.2.2 Send Message
Fig. 170: Send Message - Send a message to the site.

It is possible to send a message to the customer during a remote session. The CSE simply
needs to enter a text in the message text area and click the Send button to send the mes‐
sage.
As a result, the following message box will be displayed on the console.
Fig. 171: Send message - Received message from the CSE
The message box must be confirmed by the customer by clicking the OK button. The mes‐
sage text will be logged in the event log.
8.12.2.3 Session List
Fig. 172: Session List
n Session Key
This is a session ID and does not contain the service key.

n Service Level
The service level of the remote access is displayed for each session.
n Started
The date and time at which the session is started will be displayed.
n Last Access
The date and time of the last access from each session is displayed.
n Status
Shows the actual status of a session.
n Client
Shows the IP address of the remote client.
All current sessions are displayed. Click Refresh to refresh the list.
To close all sessions, go to menu item Options -> Remote access, and switch to “no ac‐
cess”! (see also Customer UI -> Remote Service)
8.12.2.4 Process List
Fig. 173: Process List
n Pid
Displays the ID of a process.
n Process Name
Name of the running process.
n Processor Time
Estimated processor time for a certain process.
n Privileged
Load in % of the Kernel mode.

n User
Load in % of the User mode.
n Mem Usage
Memory used for certain process.
Information is provided about the currently running process. Click Refresh to refresh the
list.
8.12.2.5 CompMgr List

This function shows the currently running software components.
Fig. 174: Component Manager List
Click Refresh to refresh the list.

n Process Name
A logical name for the process or component to be used in commands and other ac‐
tions.
n Pid
The Process ID. It is 0, if the process is not running. Components obtain the Pid from
the hosting container.
n State
Current state of the component or process.
n Executable
The executable file name.
n Creation at
Specifies when a component or process is started (at_boot = after system startup,
at_startup = if user logged in).

n Lifetime
Specifies the estimated lifetime of a component or process.
n Lifetime value
A number based on the "Lifetime" parameter
Fig. 175: Component Manager List - Scolled to the right
n Faults
A count of how often a component or process was terminated. Note: It is not consid‐
ered an error if, e.g., a batch file terminates a component or process.
n Path type
Type of executable. This can either be an external, backend, or frontend executable.
n On exit
Specifies whether the component or process should be restored in case of an excep‐
tion.
n Cwd
Current working directory

8.12.2.6 System
Fig. 176: System
Here, you can shut down or restart the system or an application.
8.12.2.7 Tune CD Burning

This tool is automatically started at the time of a new installation.
This tool has to be started when a hardware part is modified or upgraded with hardware
options.
Fig. 177: Tune CD Burning
“Tune CD Burning” checks the performance of a system to ensure the data stream for CD
burning.

This information is used to ensure that the user can work properly while burning a CD.
During the burning process, data is stored at a specific location on the hard disk.
“Tune CD Burning” requires approx. 5 minutes and runs in background. The system has to
be booted after it is finished.
Fig. 178: Popup message after approx. 5 minutes.
 CAUTION
When “Tune CD Burning” is running,
 CDs may not be burned at the same time!
8.12.2.8 Calibrate Monitor

This tool calibrates the monitor for medical diagnostics.
Monitor Calibration
with Minolta Luminance Meter LS100
Fig. 179: Calibrate Monitor
Click Go to check if a monitor correction LUT is already installed.

In this case, it will be deactivated. If its file name is "%medhome%\config\common\LUT

\monitor.lut," it will be renamed "monitor.lut.bak."
A reboot will be performed.
If no LUT is installed, you must proceed with the calibration immediately.
Fig. 180: Calibrate Monitor #1
After selecting Go, the ActiveX control for receiving data from the LS100 is displayed.
Select the COM port the luminance meter is connected to, and activate this port with the
Com Port Open button.
The calibration mode of the LS100 has to be set to “PRESET”, and the measuring mode
to“ABS”. Otherwise, a warning will be displayed.

The 17 GSDF test patterns “ddl_01.dcm” to “ddl_17.dcm” must be loaded into the syngo
viewer.
To measure the luminance of the target (square region in the middle of the image), each
image must be displayed with view options “a 1:1” and “No text”.

Minimize the service UI so that only the calibration image is displayed on the screen. Only
the status window that will be displayed on the right side of the screen should remain
visible.
Click the Start button to measure the first value.
The value is displayed and may be accepted or rejected.
If the value is rejected, the last measurement will be repeated.
Next, a list of all measured values will be displayed.
If the values are accepted, they will be saved in a temporary file and a monitor correction
LUT will be calculated.
The LUT file will be saved to “%medhome%\config\common\LUT\monitor.lut” and a reboot
will be initiated to activate the monitor correction.
8.12.2.9 Database Tools

These tools are used to remove a corrupted database, which then is created new during
next application start.

Remove
Fig. 185: Utilities - Remove Database
You can select all databases or you can select only one database (store).
Enter one number (1-4) into the Parameters field and then click “Go”.
n 1 = All databases
Removes (2) Local Database, (3) Scheduler store and (4) Archive store.
n 2 = Local database
This is the database for patient images and patient data
n 3 = Scheduler store
The HIS / RIS orders will be stored to that store. If it is removed, a new store will be
created with the next HIS / RIS order.
n 4 = Archive store
When reading a CD, the data is stored to this archive store for fast read.
This store will be deleted automatically when you start the system or by using this fea‐
ture (Remove Database with parameter 4).
8.12.2.10 Recover CD
The customer is able to store several sessions on a single CD.
On rare occasions, it is possible that the newest session cannot be recorded correctly. In
this case, the entire CD is unreadable.
The CSE can use the “Recover CD” tool to create a new session with pointers to the last
“good” session and close the current session.
The last (“bad”) session will be lost, but all the others will be readable.
This procedure requires sufficient space on the CD and requires that the previous session
is still readable.

Recovery may not always be possible!

Fig. 186: Select Recover CD
Select Recover CD from the source pull-down menu.

Fig. 187: Select CD Drive to recover the CD
Select the CD burner drive to recover the CD.

8.13 Software Distribution
8.13.1 General
Software Distribution is one of the Siemens Enhanced Productivity Services which al‐
lows remote system software updates and any other kind of remote software distribution
and installation.
Software Distribution is provided by Siemens Remote Service and requires a broadband
connection to the SRS, as well as an activated System Management Package (LSS includ‐
ing MNP) in the system.
8.13.1.2 Features
Software Distribution differs slightly in how the package transfer is initiated. The software
package can be automatically pushed to each system, triggered by the Software Distribu‐
tion Server or it can be pulled by the system from the Software Distribution Server, trig‐
gered by the software catalog in the syngo service software.
The package can not only be automatically transferred to the system, it can also be silent‐
ly installed in the system without any notification, depending on the modality type. This
is allowed only for certain kinds of software packages (e.g. virus pattern updates) and re‐
quires a one-time acceptance by the user (UI checkbox), which of course, can be modified
by the user at any time.
The software catalog can be accessed during a remote session. However, "Full Access” is
required for downloads and installations.
For systems that do not have and SRS connection, it is possible to import a software
 package manually.
See ( Offline SW Pkg Import / Page 133).
8.13.2 Functions
8.13.2.1 Overview
Using the Software Distribution button from the Home Menu, the Overview Window of
the Software Catalog is automatically launched and shows the status of the actual soft‐
ware packages assigned for that system.

Fig. 188: Software Catalog Overview
If the Catalog is not up-to-date (system dependant value, e.g. 24 hours), an information
pop-up is displayed.
Fig. 189: Information catalog is not up-to-date
The catalog can be refreshed by clicking the Update Catalog button in the lower right
corner of the window. The system then retrieves the actual assigned software packages
from the Software Distribution Sever and updates the table.
The following conditions can be displayed:
n available
The software package is available for download.
n transferred
The software package has already been transferred and is ready for installation.
n transfer in Progress
The download of that particular software package is in progress.
n installed
The software package is already installed.
 If a previously installed package is uninstalled, it is relegated to transferred status.
n error
The software package has not been installed successfully.
By moving the mouse pointer over the software package name in the catalog table, a
short description of the package content is displayed in the form of a tool tip. If the pack‐
age name is clicked, a pop-up window containing a description of the package content is
shown.

In addition to the package name, the table also contains the package version, package
size, and the date of the currently shown status.
If a package is transferred and ready for installation, a notification (with a max. delay of
15min) is sent to the system user in the form of an icon in the syngo Status bar.
By clicking this icon, the so-called Software Distribution/Installation UI is displayed. This

UI is provided particularily for the system user and is further described in chapter SD User
Interface.
8.13.2.2 Download
The download of any software package, shown as available in the Overview menu, can
be started in the Download menu. The checkbox of the respective package has to be
marked and the download can be started by clicking the Download Button in the lower
right corner of the window.
 If the link to the Download menu is disabled, the catalog needs to be updated from the
Overview menu.
Multiple selections are possible to allow simultaneous downloads of several packages.

Fig. 191: SD Download Window
The progress of the download is shown in precentage in the “progress” column of the ta‐
ble. If the download finishes successfully, the job is removed from the table and the fol‐
lowing pop-up is displayed.
Fig. 192: Download Successful pop-up

Closing or leaving the Download window, for any reason, will not interrupt the current

downloads.
The frequent refreshing of the UI is normal because of the periodical query of the down‐
load progress.
All successfully downloaded software packages are stored on the system in the “sd_store”
folder.
8.13.2.3 Install
Transferred software packages can be installed from the Install menu by clicking the In‐
stall button in the “Action” column located on the right-hand side of the table.
Fig. 193: SD Install Window
If the transferred package contains a detailed description or instruction, it can be opend

by the link provided in the Info column of the table. Successfully installed packages are
removed from the table.
Software packages, which require the installation of another software package, are not
offered for installation as long as the required package has not been installed.
8.13.2.4 Uninstall
Previously installed software packages can be uninstalled from the Uninstall menu by
clicking the Uninstall button in the “Action” column located on the right-hand side of the
table. An additional pop-up asking for your approval is displayed before the action is per‐
formed. This only works if an uninstallation routine was provided by the installed soft‐
ware package.
Successfully uninstalled packages are removed from this table and are added to the table
in the Install Menu again.
 Only those software packages, which have an unistallation routine or have been instal‐
led by Microsoft Installer (MSI-packages), are displayed in the table for uninstallation .

Fig. 194: Uninstallation Info pop-up
8.13.2.5 SD User Interface

The installation of non-critical software packages can be coded to be installable by the
system user without any CSE support. As soon as those packages are completely transfer‐
red from the software distribution server to the system (push mode), the user is notified
during the system startup by a SD User Interface (pop-up) that a software package is
available for installation and the user can accept the installation or decide how to proceed
with it.
Fig. 195: Sample SD User Interface
(1) Sample SD User Interface
During normal operation, the user is informed via the icon in the syngo Status bar that a
software package has been received and is waiting for installation.

By clicking the icon, the SD User Interface is opened, so that the user can install the soft‐
ware package whenever his workflow allows it.
All the information in the UI is provided by the package itself. Without any user action,
the UI stays on the screen for a specified time period, as shown in the bottom of the UI.
After this time period elapses, the software installation request is still shown in the form
of the icon in the syngo Status bar, where it can be called up at anytime.
The action buttons available in the SD User Interface may differ depending on the pack‐
age content, e.g., a Defer button is not provided in cases of a mandatory security update,
which cannot be delayed.
Description of the action items in the SD User Interface:
n Description
Shows the detailed description of the software package content or its meaning; can
also be a complete software installation instruction.
n Install
Starts the installation of the software package. The UI, with the click of a button, then
extends to display the installation log used to follow the installation process. A pro‐
gress bar is shown as well.
Fig. 197: Installation Extended View
n Defer
The SD User Interface is closed, which means that the installation is postponed and
that the user will be requested to install the package at the next system startup or the
user can invoke it again through the icon in the Status bar.
n Defer All
If more than one package needs to be installed, several SD User Interfaces are dis‐
played consecutively. With this button, all outstanding installations are deferred.
n “Accept Silent Installation” checkbox
With this checkbox, the user can decide to no longer show the SD User Interface for
additional software packages of the current package type. This function should be
used, e.g., for frequently reoccuring virus pattern updates. The user can revoke the

approval any time via the general syngo configuration (Menu: Option/Configuration/
Software Distribution)
Fig. 198: Accept Silent Installation

8.14 Event Log
8.14.1 Event Log Overview

Fig. 199: Event log expert mode
(1) Personal filter setting

(2) Domain
(3) Message ID or text
(4) Time range
(5) Message limit
(6) Variable display
(7) “GO” for messages
8.14.2 Filtering the Event Logs

Due to the amount of events which are logged in the event log, it is advisable to filter the
log to reduce the events to the important ones. Certain filters are implemented for differ‐
ent situations and if you use a good combination of filtering you will easily find the prob‐
lem-related events.
It is also possible to set some personal filters by setting and saving using the save button
beside the filter settings.

8.14.2.1 Filtering by Date and Time

The filtering is used if you know the time frame in which the problem occurred. Usually 1
hour within the time of the occurrence is sufficient. It is possible to choose between an
absolute and a relative time range.
8.14.2.2 Filtering by ‘Domain’
The following domains are used:

Application In this group, all events from the running applications are logged.
(default) These include the syngo database and system applications. Such as
software, the hardware-related events are included, this domain is
normally used to analyze system malfunctions.
Customer Log The customer log shows the service activities that have been per‐
formed, including the remote service activities. The customer can
see the same information in the Remote Service Access Control win‐
dow.
Security Security events are logged in the security log file, e.g. attempts to
log on to the system. The trigger is normally turned off.
System Windows NT events are recorded in this log.
For system problems, it is best to exit the "domain" at the default ‘application’
8.14.2.3 Filtering by ‘Severity’
The events are divided into three "Severity" levels.

Information An "information" severity event is mainly used to log non-critical
events or status messages, e.g. successful start of a software module
(DLL), etc.
This means that these events are not normally used for analyzing
hardware problems, etc. In rare cases, it is also advisable to look at
the information events to see if the defined sequence of a system
function is performed correctly or if some events are missing.
Warning A "warning" severity event contains a possible error condition. It is
therefore necessary to take note of these events during trouble‐
shooting. Warnings can be ‘Set’ (when the condition starts, the warn‐
ing is set) and ‘Reset’ afterwards (when the condition is finished).
So it is possible to have two entries with the same events, but first a
Set followed by a Reset. If the Reset immediately follows a Set, this is
normally not an error situation. The Set/Reset text can only be
viewed if the ‘Extended’ checkbox is selected.

The events are divided into three "Severity" levels.

Error An "error" severity event is logged when a function cannot be com‐
pleted, this might include an error condition. Errors must therefore
be noted during troubleshooting.
Errors from the Source AX_xxx are normally related to real problem
situations. Errors from the ‘syngo sources’ are mainly software-rela‐
ted and therefore not particularly relevant to service.
All To display all severity events, checkmark all ‘Information’, ‘Warning’
and ‘Error’ severity events.
8.14.2.4 Filtering by ‘Source’

The source represents the software module sending the event. Most of the AX software
modules relate to a defined component, therefore this filter is used to display events from
the component which is assumed to cause the problem.
In principle, there are two groups of sources:
- AX_ SW modules, which are developed by the division
- AX- CSA_ ..., CAP_ ..., etc. software modules, which are developed by the syngo depart‐
ment
Source Software module Hardware component / related problem

field
AX_ACU Acquisition Control Unit (RTC) Injector interface
Digital Image Preprocessing FD components
(DIPP) RTC components
AX_ANG Angiomatic (RTC) X-ray components: PUD (power unit ), tube
AX_AXN AXCS network
AX_IVS Image system Image Visualization System
AX_IAS Image Acquisition System
AX_ISC Image System Common (IVS,IAS)
AX_COP COPRA boards in the IVS
AX_DEV Image System Developer
AX_CAN Controller Area Network
AX_CAT Cathcor ECG Unit (RTC) Cathcor / Sensis / ECG Interface in RTC
AX_CCU Collimator Control Unit (RTC) Collimator, Collimator Control Module
AX_CSF Common software Function (RTC) RTC / SIRC
AX_DDD DDD SW Module 3D Angio Transfer
Note: In general, the syngo events provide additional information on an existing problem, but
are not used to identify defective hardware components.


field
AX_DPP Digital Preprocessing
AX_ECC Examination Control Console
AX_KRC Kuka Robot Control Multi-axis Stand
AX_PMS Service Events from the software modules for service
AX_PUD A100 Generator Events from the generator
AX_QNT Quantification Quantification software modules
AX_REP Reporting System Software module for reporting, e.g. event re‐
porting or saving protocol files
AX_SF Support Functions Common support function, such as switch
the system ON/OFF
AX_SCU Stand Control Unit (RTC) Controls all movements from stand, table,
collimator and camera rotation components
connected via the motor controller
AX_SYC System Controller (RTC) Software module for controlling system sta‐
tus, e.g. normal or bypass operation, exam
sets
AX_TBC Table Control Trumpf table
AX_VOC Voice control
AX_WCU Wide screen Control Unit (software Multi-Display Manager
component on the RTC A)
AX_WSD MDM Service Multi-Display Manager and 56 inch Display
CAP_AN Arch Net Archiving to Net or CD
CAP_AT Application Template
CAP_CR Correct & Rearrange
CAP_DSB 3D
CAP_DVB 3D
CAP_DV 3D
CAP_EXT Application Template
CAP_FL Filming
CAP_PAGE Cap Page
CAP_PB Patient browser Database / Patient Images


field
CAP_PR Patient Registration Database
CAP_SUI Service User Interface All service activities
CAP_COM Component Manager
CAP_COMPMGR Component Manager
CAP_DB Database Database
CAP_ERH Error Handling
CAP_ERR Message Logging
CAP_GSI Graphics
CAP_HC Hardcopy Hardcopy device / interface
CAP_HRI HIS/RIS HIS / RIS Interface
CAP_IMA Image Manager Database / Patient Images
CAP_INST Installation
CAP_IP Image Processing Database / Patient Images
CAP_LM License Manager Licenses / license protected options
CAP_OSC Operation System & Communica‐
tion
CAP_PM Patient Manager Database / Patient Images
CAP_REP Auto Report Auto report / Remote diagnostics
CAP_SM Screen Management
CAP_STU Study Transfer
CAP_TF Transformer
8.14.2.5 Extended information messages

To obtain extended information relating to the messages in the list, just click on the Ex‐
tended button in the menu line. To switch back to the normal view, select Standard.
8.14.2.6 Extract error log

To extract / export the error log to a file, select the Extract button at the top right of the
screen. Insert the file name and the destination in the drop-down menu, then press Ex‐
tract.

Fig. 200: Export / Saving Event log
(1) File name:

(2) Destination

8.15 Reports
8.15.1 General
The Report function is used to get an overall overview of the actual configuration.
It provides further access to important system log files (also via remote connection) .
8.15.1.2 Features
The information and log files are clustered in groups as follows:
n SiteInfo
n Tune-Up/QA/Tests
n Startup Process
n Remote Diagnostics
n System Management
Fig. 201: Report Overview
8.15.2 Functions
8.15.2.1 Handling
n Activate the Reports button in the Service Home Menu Navigation bar to open a sepa‐
rate window. Available log files of service programs are shown in the left frame of the

opened window. You can select an entry by clicking one of the specific reports as re‐
quired.
n Activate the Help button in the Reports Navigation bar to get context-sensitive help
information.
n Activate the Exit button in the Reports Navigation bar to close the Reports window.
8.15.2.2 SiteInfo
This menu entry provides information about the license, SAM and the configuration for
this specific site.
License
Important license information is displayed, such as hardware ID, current service key, and
the status of all available application licenses.
Fig. 202: Sample - License Report
About SAM
Displays the current version of the "Service Access Manager" (SAM). The SAM controls all
the activities within the syngo service software packages and their modules.

Fig. 203: Sample About SAM
Configuration
A system configuration report is displayed. The report is divided into several options. Click
an option to obtain the corresponding information. The white arrow within the subtitle
bar brings you back to the top of the page.
Fig. 204: Configuration

 Press “Ctrl+P” to print out the content of the Configuration Report on a local or network
printer, if configured.
See the report sample of a network configuration below.

Fig. 205: Configuration - Network
Firewall
Displays the current Windows XP firewall (security) configuration. The firewall configura‐
tion displays which ports and programs are enabled on the system.
Fig. 206: Firewall Info Screen

8.15.2.3 Tune-Up/QA/Tests
This menu entry provides you with information about the status of the system with re‐
gard to:
n Tune-up
n Quality Assurance
n Test Functions (e.g. results of the latest measurements)
n Backup & Restore
n syngo startup log
Session history
Use these links for viewing the session log file. It displays the history of all measurements,
quality assurance and tests performed.
Fig. 207: Report Session History
Backup & Restore

Displays an overview of all backups performed on the system. It also provides a link to the
log file which was written during the backup routine.

Fig. 208: Backup and Restore
This report shows which files / directories were saved and which programs were execu‐
ted.
Fig. 209: Backup Log
syngo startup log

This report displays detailed information about the syngo startup.

Fig. 210: Report Startup Log
8.15.2.4 Startup Process

This menu entry provides information about the system startup processes.
Process diagnostics
The Process Diagnostics provide central access to all available startup process log files.
An overview of all the corresponding log files is displayed in the right frame of the win‐
dow. Click one of the hyperlinks to view the desired log file.
Fig. 211: Sample Process Diagnostic
This window shows the results of one process.

Fig. 212: Report Backup Log
8.15.2.5 Remote diagnostics

This menu entry provides information about the customer log file.
Customer Log
Use this link for viewing the Remote Diagnostics customer log which contains:
n Login trails
n Date and time of login
n Date and time of logout
n Who terminated the service session (local or remote service user)
n Service activities as defined within each service program

Fig. 213: Customer Log
Click the ID number for more information about this specific message.
Fig. 214: Message Description
8.15.2.6 System Management

This menu entry provides information on the System Management (MNP) installation.
Sysmgmt Diagnostics
The Sysmgmt Diagnostics provides a link to all the available MNP-related log files. The log
files are located in the c:\sysmgmt\Log directory. Those files can be remotely accessed via
this link.

Fig. 215: Sample - System Management Logs

8.16 Help
8.16.1 General
This section describes the Help function of the syngo service software package.
It provides brief information on the Help function.
8.16.1.2 Features
Fig. 216: Home Menu

Online help is not provided in VC14.
See CB-DOC for information
8.16.2 Functions
8.16.2.1 Online Help

Online help is not provided in VC14.
8.16.2.2 Documentation
CB DOC:
A pop-up window appears, when you click the Documentation button in the Navigation
bar of the Help Window or within the Home Menu under Help. A default URL address for
the Online Documentation CD-ROM is displayed. Click the OK button to start the Home
Page of the Computer-Based Documentation (CB-Doc) in a separate window.

 If you are logged in remotely, the default will automatically point to any local drive.
In either case, whether you are logged in remotely or locally at the customer site, you can
always change the default to access any other Web server on the network. To do so, you
have to change the URL address from file:///<CD drive>/default.htm to
http://<web_address>.
Fig. 217: URL for Online Documentation
8.16.2.3 Knowledge Base

This button allows access to the Knowledge Base of Medical Solutions (Customer Service)
from the system itself, by using a successfully established remote connection to the Sie‐
mens Remote Server (SRS). An additional Browser Window with Knowledge Base Login is
opened. Authentification by the Service Engineer with his own account is still required.
Fig. 218: Knowledge Base Access Window

Procedures 9 285
9.1 Starting the Service Software

To start the Service Software application, the system must be up and running.
Starting the Service Software application:
1. Move the mouse to the top of the Live Monitor until the menu is visible.
2. Left click on <Options>.
3. In the “Options” menu, click on the selection <Service>.
In “Service” menu, click on the selection <Local Service>.
Fig. 219: Control panel selection
 The Service Software window appears on the monitor.

4. To get into the Service application, a 6 digit password has to be inserted in the right
field of “Please enter password”. After typing in the password, proceed with <OK>.
Fig. 220: Service software log on window

286 9 Procedures
n If the password is correct, access is granted for the Service Software application.
Fig. 221: Syngo service homepage

Procedures 9 287
9.2 AX Save Logs
9.2.1 Saving Log Files

The *.log files are found under the <Reports> function. All activities of the system are
saved in the various *.log files. This is also where the backup *.log files are found. These
should also be saved on the backup diskette. The log files can be read using the browser
and, if necessary, can be printed out.
n Select <Reports > in the Navigation bar in the service interface.
n Select <Process Diagnostics > in the Navigation bar.
n Look for the following *.log files:
- Configuration %Date/Time%.log
- Exam Sets %Date/Time%.log
- User Settings %Date/Time%.log
n Right-click on each file and select <Save Target as... > in the context menu.
n Select the path to the diskette in the <Save as> window and save with <Save>.
 The <Save as> window appears behind all other open windows. Minimize the open win‐
dows until the window becomes visible.
9.2.2 Event Log

The event log is the central error store in the system. This is where messages from the
operating system, from the syngo and from the individual system components are log‐
ged.
The event log can be started from every window in the service software. To do this, click
on the <Event Log> button in each window of the service software.
Short description of the Log Zip Tool "AXSaveLogs.vbs"
The Log Zip tool is installed on the Artis zee system to enable automatic extraction and
compression (zip) of event logs and other logs to a specified directory in the system.
Detailed Function Description:
The following functions are performed automatically with the AXSaveLogs tool:
- with each “switch on” of the system or at 01:30 am, the event logs from the previous
day and from the current day are extracted and zipped. In addition, the files AX‐
IS_ERR.log, Dr. AXIS.log, version, Config check, Configuration Report, and some other
logs are zipped into the same file.
- All these files are zipped and saved into the file with the following naming convention:
xa100xx_tt_mm_yyyy_LogFiles.zip
- This file is saved in the directory C:\AXIOM\Log and in C:\AXIOM\Service\outgoing

288 9 Procedures
- Up to 30 files (for 30 days) are saved, so when more system power-ons are performed,
the oldest file is overwritten (ring buffer). If you switch on the system more than once a
day, the file that already exists for this day is overwritten.
- The *.zip file can be created with the following command:
C:\AXIOM\AxZipTool\AxSaveLogs.vbs
or the following key combinations:
<Ctrl> + <Alt> + s
<Ctrl> + <Shift> + l
If you have questions regarding this tool, please contact CS HSC AX

Procedures 9 289
9.3 Transferring the Error Log to the SRS Server

n Open the Service SW and select <File and Image Tools>
n Under Source, select <File>
n Under Action, select <Transfer from System>
n File Type <Any File>
n Under Site Directory <C:\AXIOM\service\outgoing>, select the desired log file.
n Start the transfer with <Go> in the Action Bar. The log file will now be transferred to
the SRS server.
Fig. 222: File and Image Tools

290 9 Procedures
9.4 Software Version Check

The current software versions of all components can be read out with the Software Ver‐
sion Check. In addition, a comparison between the read-out version with the version
saved in the system STF file is made. If a difference is found here, a warning is displayed
at the corresponding location.
9.4.1 Starting the Software Version Check

Call up the <CONFIGURATION > menu item on the Syngo Service Home page. The <Ver‐
sion Check> item is found in the Configuration navigation bar. The Version Check is star‐
ted by clicking on this menu item.
If the Version Check detects an inconsistent SW version in any subcomponent, the system
state "Inconsistent SW" is set. The system will stay in "Bypass" mode unless the inconsis‐
tent state is solved. Inconsistencies are typically created through an incomplete SW up‐
date, they can be solved by downloading the correct version onto the subcomponent.

Procedures 9 291
9.5 Network Tests
9.5.1 PING
The “PING” is used to check whether a component can be reached via the network. There
are two possible answers to the command:
n Reply; The component answers the question (“is alive”), and
n Timeout; The component cannot be reached. An answer was not transmitted within
the time window. In this instance, the configuration and the network connection for
this component must be checked.
9.5.1.1 Ping out of configuration

While doing the network configuration, it is possible to check the entered IP address with
the Test button. The system will then perform a ping to the IP address, which is shown to
the left of the Test button.
Fig. 223: Out of <configuration> <network nodes> ping using the Test button
9.5.1.2 Ping with DICOM Tests

After the selection of the configured host, use the “GO” button to start the network test.

292 9 Procedures
This ping uses the host name. The corresponding IP number is used from the “hosts file”.
This file contains the mappings of IP addresses for host names.
Each entry is kept on an individual line. The IP address is placed in the first column fol‐
lowed by the corresponding host name. The IP address and the host name are separated
by at least one space.
Fig. 224: Ping with DICOM network verification
After a successful “ping”, the higher level test “DICOM ECHO” is started automatically.
9.5.1.3 Ping Out of Hardcopy Configuration

While doing the hardcopy configuration, it is possible to check the entered address with
the Test button. The system will then perform a ping to the selected logical name.
The higher level test “DICOM ECHO” can be performed using the ’DICOM access’ Test but‐
ton.

Procedures 9 293
Fig. 225: “Ping” and “C-ECHO” under configuration for hardcopy
9.5.1.4 Ping with <Utilities><Escape to OS>
1. Call up the service software.

2. “Call up “Utilities” on the service Home page.
3. Under <SOURCE>, select “Escape to OS”.
4. Under <Commands>, select the NT Command Interpreter.
5. Enter ping and the TCP/IP number of the component in the <Parameters> input box.
(If the host name is entered, the name can also be entered in place of the IP address.
6. Click on <GO>.
Ping is also possible for AXCS components. See also ( AXCS / Page 45).
Example with the <IP number> “ping”

294 9 Procedures
Fig. 226: IP number ping
Utilities | Home | Help |
Command: NT Command Interpreter

Source
Escape to OS Parameters: Ping 157.163.196.1
Escape to OS
Pinging 157.163.196.1 with 32 bytes of data:
Reply from157.163.196.1 : bytes=31 time<10ms TTL=30
| Go | List | Abort | Clear |
Example with the <host name> “ping”

Procedures 9 295
Fig. 227: Out of <Utilities> <Escape to OS> ping
9.5.1.5 Ping parameters

The following parameters can be used together with the ping command.
ping [-t] [-a] [-n count] [-l length] [-f] [-i ttl] [-v tos] [-r count] [-s count] [[-j computer list]
| [-k computer list]] [-w timeout] destination list
Parameters
-t Pings the specified computer until interrupted.
-a Resolve addresses to computer names.
-n count Sends the number of ECHO packets specified by the count. The de‐
fault is 4.
-l length Sends ECHO packets containing the amount of data specified by
length. The default is 64 bytes; the maximum is 8192.
-f Sends a Do not Fragment flag in the packet. The packet will not be
fragmented by gateways along the route.
-i ttl Sets the Time To Live field to the value specified by ttl.
-v tos Sets the Type Of Service field to the value specified by tos.

296 9 Procedures
Parameters
-r count Records the route of the outgoing packet and the returning packet
in the Record Route field. A minimum of 1 and a maximum of 9
computers may be specified by the count.
-s count Specifies the time stamp for the number of hops specified by count.
-j computer list Routes packets via the list of computers specified by computer list.
Consecutive computers may be separated by intermediate gate‐
ways (loose source routed). The maximum number allowed by the
IP is 9.
-k computer list Routes packets via the list of computers specified by computer list.
Consecutive computers may not be separated by intermediate gate‐
ways (strict source routed). The maximum number allowed by the
IP is 9.
-w timeout Specifies a timeout interval in milliseconds. The destination list
specifies the remote computers to ping.
9.5.2 Netstat
This command is available only if the TCP/IP protocol has been installed.
9.5.2.1 Netstat parameters

netstat [-a] [-e] [-n] [-s] [-p protocol] [-r] [interval]
Parameters
-a Displays all connections and listening ports; server connections are nor‐
mally not shown.
-e Displays Ethernet statistics. This may be combined with the -s option.
-n Displays addresses and port numbers in numerical form (rather than at‐
tempting name look-ups).
-s Displays per-protocol statistics. By default, statistics are shown for TCP,
UDP, ICMP, and IP; the -p option may be used to specify a subset of the
default.
-p protocol Shows connections for the protocol specified by the protocol; the proto‐
col may be tcp or udp. If used with the -s option to display by protocol
statistics, the protocol may be tcp, udp, icmp, or ip.
-r Displays the contents of the routing table.interval. Redisplays selected
statistics, pausing several seconds between each display. Press CTRL+C to
stop redisplaying statistics. If this parameter is omitted, netstat prints the
current configuration information once.

Procedures 9 297
9.6 How to log in as Administrator

n Press Shift during the bootup phase (before Syngo screen counts up)
n User name: Administrator
n Password: (see the AX PASSWORD LIST, ID 13982 in the CS Knowledge Base)

298 9 Procedures
9.7 AXCS Trace

All AXCS objects transferred via the AXCS network are continuously stored to a ring buffer
store. The buffer holds up to 1000 objects. If needed, the current content of the buffer
(last 1000 AXCS objects) can be stored and read out or sent to the Engineering Depart‐
ment.
 AXCS trace files are also added to the axsavelog.zip file.
9.7.1 Saving the AXCS Trace

The following three options are available for generating an AXCS trace:
9.7.1.1 1. Generating an AXCS Trace using a Button in the <Control> <Auxiliary> Menu
n Open the menu located under <Control> <Auxiliary>.
n Click the <Dump> button to initiate an immediate dump of the last 1000 AXCS ob‐
jects.
 A trace file (file name: “date_timeMANUAL_TRC.trc”), which holds the last 1000
AXCS objects, is generated under C:\AXIOM\Service\Log\AxcsTrace.
9.7.1.2 2. Generating an AXCS trace using the keyboard

n Press the key combination <Ctrl> + <Shift> + <a> on the keyboard.
 A trace file (file name: “date_timeMANUAL_TRC.trc”), which holds the last 1000
AXCS objects, is generated under C:\AXIOM\Service\Log\AxcsTrace.
9.7.1.3 3. Generating an AXCS trace triggered by an error message

n Open the menu located under <Control> <Auxiliary>.
n Enter the error ID number and the Domain ID of the component that is to be used to
trigger the AXCS trace in the input boxes marked "Error Number" and "Domain ID".
Save the entries by clicking on the <Save> button.
Example:
Error number ID: 25 and Domain ID: ANG would activate an AXCS trace if the Angiomatic
error ID 25 occurs. The trace file (file name: “date_timeDomainErrorNo_TRC.trc”), which
holds the last 1000 AXCS objects, is generated under C:\AXIOM\Service\Log\AxcsTrace.
Only messages from the following sources (domain IDs) initiate triggering of an AXCS
trace:
ACU Acquisition Control Unit (RTC)

ANG Angiomatic (RTC)
CAN Controller Area Network

Procedures 9 299
CAT Cathcor ECG Unit (RTC)

CCU Collimator Control Unit (RTC)
CSF Common Software Functions (RTC)
PMS Service (customer log user messages)
PUD POLYDOROS A100
REP Error Reporting
SCU Stand Control Unit (RTC)
SYC System Controller (RTC)
9.7.2 Converting the AXCS Trace into a Readable Format

This function converts an available AXCS trace dump into a readable AXCS trace and
stores it as an HTML file under <Reports>. The prerequisite for generating a readable
AXCS trace is the availability of an AXCS trace dump.
n Open the <Report Generation>.
n Click <Generate AXCS Trace> to start the trace conversion. The progress of the con‐
version as well as the file name of the generated html file will be displayed in the
function frame.
Fig. 228: Generate AXCS Trace
n When finished, press Exit.
9.7.3 Viewing the AXCS Trace

n Open the link listed under <Reports> <Trace Files> <AXCS Trace>. At least one trace
file must be present.

300 9 Procedures
n Click the hyperlinked file name to open the trace file.

A “dumped” trace is labeled similar to “20040819121503MANUAL_TRIG.htm”
<Year><Month><Day><Time>MANUAL_TRIG.htm
An error-triggered trace is labeled similar to “20040819124317AX_SCU01220.htm”
<Year><Month><Day><Time><Domain><Error No.htm
n The time stamp of each AXCS object is a hyperlink. Activating this link opens an addi‐
tional window that shows the internal content of the AXCS object.
Examples:
Fig. 229: AXCS Trace directory
Fig. 230: AXCS trace file in html layout

Procedures 9 301
 The evaluation of AXCS traces requires specific knowledge and should be performed by
development experts.
9.7.4 Problems

Generate Reports After selection of Generate Reports, all components which are able
to provide information are listed and marked with “ready”.
If the files were successfully transferred from the components, they
are marked “OK”.
The generated reports can be viewed under Reports > Component
Reports >
Generate Reports shows warn‐ The system must be “up and running” when starting the “Generate
ings Reports” tool.
n Repeat the “Generate Reports” function again if necessary.
Generate Reports shows failures The system must be “up and running” when starting an adjustment.
n Run the AXCS test ( AXCS TEST / Page 49)and check if compo‐
nents are not ready
 If one component shows not ready, mark it and use the
Reset function
 If all components are not ready, switch off the RTC and
turn it on again
n Repeat the “Generate Reports” function again, if necessary.
Following Generate Reports, no After a new software installation, the tune-up results for FD calibra‐
tune-up results are visible tions are not visible unless a new calibration is performed.
Generate AXCS Trace If a REP_ERR event which was set as a trigger under Control > Aux‐
iliary > has occurred, an html file is created. This file contains the
last 1000 AXCS events prior to the trigger event.

302 9 Procedures
9.8 Getting DIPP Trace

The DIPP Trace is automatically generated in the RTC and transferred to the image system.
If an AXSavelog is generated, the DIPP trace is part of it ( AX Save Logs / Page 287).

Procedures 9 303
9.9 Confirmation of Adjustment using Component Reports

To verify if an adjustment has been performed, check whether the file xxx.aaf.txt has the
label “ADJUSTED” or “RESTORED”.
n These files are located under <Report Files> <Component Reports>
For example: Residual mAs results are stored under “ang_direct.aaf.txt”
Fig. 231: Component Reports (Angiomatic Reports)
Fig. 232: Component Reports (residual mAS adjustment results)

304 10 Changes to Previous Version
Version 04 versus Version 03

Tab. 18 Version Changes
Chapter Changes
General Remarks The following sections were changed:
n Remarks > Conventions and Abbreviations > Abbreviations:
( Abbreviations / Page 11)
- Added MLC = Controller Artis zee Cockpit

List of Hazard IDs 11 305
There are no Hazard IDs in this document.

306 12 Index
A About SAM Report ......................................................................................................274

Acronis
Backup .................................................................................................................. 133
Restore ..................................................................................................................133
System Backup/Restore .......................................................................................... 132
ACRONIS Image Management Console ....................................................................... 141
ADC ........................................................................................................................... 113
AGC ................................................................................................................... 113, 113
Artis HW/SW inventory ............................................................................................... 133
Auto Report ............................................................................................................... 231
Auxiliary .................................................................................................................... 125
AX Save Logs ............................................................................................................. 287
AXCS
Components ............................................................................................................46
IP nodes .................................................................................................................. 46
Non-AXCS Components ........................................................................................... 48
Problems ................................................................................................................. 45
Servers .................................................................................................................... 46
AXCS Components ....................................................................................................... 46
AXCS Servers ............................................................................................................... 46
AXCS Stations .............................................................................................................. 46
AXCS tests ................................................................................................................. 140
AXSaveLogs.vbs ......................................................................................................... 287
B Backup
Acronis ..................................................................................................................133
Backup & Restore (syngo) ...........................................................................................103
Backup & Restore Reports ...........................................................................................277
Backup (syngo) .......................................................................................................... 103
Boot problems
Black screen ............................................................................................................ 15
Error tab card .......................................................................................................... 15
sub-components ......................................................................................................15
Bypass ......................................................................................................................... 16
Bypass (momentarily) .................................................................................................. 18

Index 12 307
C Camera Test Pattern ................................................................................................... 113

CAN ............................................................................................................................. 51
CAN Introduction ......................................................................................................... 56
CAN Measurement Examples ........................................................................................54
Can Net Test .............................................................................................................. 141
Carewatch ................................................................................................................... 39
CCB Test Pattern .........................................................................................................114
CCM ............................................................................................................................ 11
CMA .......................................................................................................................... 115
COL ............................................................................................................................. 11
Collimator ....................................................................................................................37
Combined tests .......................................................................................................... 138
Component Reports ................................................................................................... 303
Configuration ............................................................................................................ 102
Configuration Report ..................................................................................................275
Control ...................................................................................................................... 112
Artis HW/SW inventory ........................................................................................... 133
Auxiliary ................................................................................................................ 125
Control Acquisition ................................................................................................ 124
Control Fluoro ....................................................................................................... 123
ECC layout import/export is ................................................................................... 133
Offline SW Pkg Import ............................................................................................133
OGP Import/Export .................................................................................................127
Service Switches ....................................................................................................112
System Backup/Restore (Acronis) ........................................................................... 132
Control Acquisition .................................................................................................... 124
Control Fluoro ............................................................................................................123
Control Functions ........................................................................................................ 33
Conventions and Abbreviations .................................................................................... 11
Creating a self defined test .........................................................................................138
Customer Log Report ................................................................................................. 280

308 12 Index
D D90 Power Distributor Board ........................................................................................ 94

DCS ............................................................................................................................. 11
DDIS ............................................................................................................................ 11
Dead Man’s Circuit ....................................................................................................... 28
Diagnostic Info A100/plane A(B) .................................................................................139
Diagnostics with IAS-A(B) and IVS (60s Tests) ............................................................. 139
Diamentor ................................................................................................................... 39
Diamentor LEDs ........................................................................................................... 39
DICOM Tests .............................................................................................................. 144
DIPP Test Pattern ................................................................................................ 114, 123
DIPP Trace ..................................................................................................................302
DM .............................................................................................................................. 13
DMG ............................................................................................................................ 13
Dose ............................................................................................................................ 35
Dose Rate .................................................................................................................... 35
DVM ............................................................................................................................ 11
E ECC 1(2/3) ................................................................................................................. 139

ECC Layout Import/Export ...........................................................................................133
EGY_REL ...................................................................................................................... 13
Emergency Stop ...........................................................................................................29
Error Log Transfer ...................................................................................................... 289
Event Log ...........................................................................................................267, 287
Extended Information ............................................................................................271
Extended Text ....................................................................................................... 271
Extract .................................................................................................................. 271
Extract logs ........................................................................................................... 271
Filtering ................................................................................................................ 267
Overview ...............................................................................................................267
Event Log Filtering ..................................................................................................... 267
Date ...................................................................................................................... 268
Date and Time ....................................................................................................... 268
Domain ................................................................................................................. 268
Severity ................................................................................................................. 268
Source ...................................................................................................................269
Time ......................................................................................................................268

Index 12 309
F FD Test Pattern .......................................................................................................... 114

Defective pixel map ............................................................................................... 119
Digital dynamic horizontal pattern ......................................................................... 118
Digital static horizontal pattern .............................................................................. 117
Digital static vertical pattern .................................................................................. 117
Normal pattern ......................................................................................................116
Pseudo random pattern ......................................................................................... 118
Static diagonal black/white pattern from analog board ........................................... 121
Static diagonal lines from analog board ................................................................. 122
Static horizontal ramp from analog board .............................................................. 119
Static Mapix gray level pattern from analog board ..................................................120
Static pseudo random pattern from analog board ...................................................122
Static vertical ramp from analog board ...................................................................120
File & Image Tools ......................................................................................................200
File and Image Transfer .............................................................................................. 289
Firewall Report ...........................................................................................................276
G Gamma ......................................................................................................................115
Global Gain ................................................................................................................ 115
GND ............................................................................................................................ 12
Gray level .................................................................................................................. 114

310 12 Index
H Hardware tests ...........................................................................................................137

Combined tests ..................................................................................................... 138
Creating a self defined test .................................................................................... 138
Diagnostic Info A100/plane A(B) ............................................................................ 139
Diagnostics with IAS-A(B) and IVS (60s Tests) ......................................................... 139
ECC 1(2/3) ............................................................................................................. 139
IAS A(B): HW Inventory check .................................................................................139
IAS A(B): XPStress test ........................................................................................... 140
IAS-A(B) Imaging App Shutdown ............................................................................139
IVS Imaging App Shutdown ................................................................................... 139
IVS: HW Inventory check ........................................................................................ 140
IVS: XPStress test ................................................................................................... 140
Problem-oriented (tests) ........................................................................................ 138
RTC A(B) Interface ................................................................................................. 140
Self defined (tests) ................................................................................................ 138
Stand .................................................................................................................... 140
Hardware Tests
RTC A DIPP FRU ...................................................................................................... 140
RTC A(B) DIPP FRU ................................................................................................. 140
RTC B DIPP FRU ...................................................................................................... 140
Help ...........................................................................................................................283
Features ................................................................................................................ 283
Functions .............................................................................................................. 283
General ................................................................................................................. 283
Online Help ........................................................................................................... 283
hm_serv_LabelPowerPresent .......................................................................................... 9
hm_serv_NoteProtectEyes .............................................................................................. 8

Index 12 311
I IAS A(B): HW Inventory check ..................................................................................... 139

IAS A(B): XPStress test ................................................................................................ 140
IAS-A(B) Imaging App Shutdown ................................................................................ 139
ID ................................................................................................................................ 13
IH ist ............................................................................................................................ 13
IH soll .......................................................................................................................... 13
IH_act .......................................................................................................................... 13
IH_nom ........................................................................................................................13
Image Quality .............................................................................................................. 21
Image Quality Problems ............................................................................................... 38
INJ ............................................................................................................................... 11
INJ_RDY ....................................................................................................................... 13
IP nodes ................................................................................................................. 46, 48
IQAP .......................................................................................................................... 136
IRö ist .......................................................................................................................... 13
IRö soll .........................................................................................................................13
ISK ...............................................................................................................................11
ISY Postblanking ........................................................................................................ 115
IT_act .......................................................................................................................... 13
IT_nom ........................................................................................................................ 13
IVS Imaging App Shutdown ........................................................................................ 139
IVS: HW Inventory check .............................................................................................140
IVS: XPStress test ....................................................................................................... 140
J Jerky movement .......................................................................................................... 21
K KPC ..............................................................................................................................11

312 12 Index
L License Report ........................................................................................................... 274

Loading Patterns from Disk .........................................................................................114
Local service .............................................................................................................. 100
............................................................................................................................. 102
Auto Report ........................................................................................................... 231
Backup & Restore (syngo) ...................................................................................... 103
Control ..................................................................................................................112
DICOM Tests ..........................................................................................................144
Event Log .............................................................................................................. 267
File & Image Tools ................................................................................................. 200
Help ...................................................................................................................... 283
Quality Assurance ..................................................................................................136
Report Generation ................................................................................................. 110
Reports ..................................................................................................................273
Software Distribution .............................................................................................260
Test Tools .............................................................................................................. 137
Tune Up ................................................................................................................ 109
Utilities ..................................................................................................................239
Log Zip Tool ............................................................................................................... 287
LSS .............................................................................................................................. 11
M Managed Network Switch .................................................................................... 49, 142

MC .............................................................................................................................. 12
MCM ......................................................................................................................12, 12
MD .............................................................................................................................. 12
MD Problems ............................................................................................................... 89
Measurement Examples ............................................................................................... 43
MLC ............................................................................................................................. 12
MNP ............................................................................................................................ 12
Mount/unmount the backup/restore drive .................................................................. 141
movement problem ..................................................................................................... 19
N Netstat ...................................................................................................................... 296

NO XRAY, please wait ...................................................................................................18
Non-AXCS Components ................................................................................................48
O Offline SW Pkg Import ................................................................................................ 133

OGP Import/Export ..................................................................................................... 127

Index 12 313
P Ping ........................................................................................................................... 291

Power On problems ..................................................................................................... 15
Problem-oriented (tests) ............................................................................................ 138
Procedure
Event Log .............................................................................................................. 287
Network Tests ....................................................................................................... 291
Process Diagnostics Report ......................................................................................... 279
PROX ........................................................................................................................... 13
PUD ............................................................................................................................. 12
Q Quality Assurance ...................................................................................................... 136

Quick Stop ................................................................................................................... 30
Q_STP .......................................................................................................................... 13

314 12 Index
R R+ ................................................................................................................................13
R- .................................................................................................................................13
RAC ............................................................................................................................. 12
Radiation Function Test ................................................................................................33
radiation problem ........................................................................................................ 18
Radiation Problems ...................................................................................................... 32
Radiation Release ......................................................................................................... 34
Remote Diagnostics Reports ....................................................................................... 280
Report Generation ......................................................................................................110
Reports ...................................................................................................................... 273
About SAM ............................................................................................................ 274
Backup & Restore ...................................................................................................277
Component ........................................................................................................... 303
Configuration ........................................................................................................ 275
Customer Log ........................................................................................................ 280
Firewall ................................................................................................................. 276
Functions .............................................................................................................. 273
General ................................................................................................................. 273
License ..................................................................................................................274
Process diagnostics ................................................................................................279
Remote diagnostics ............................................................................................... 280
Session history ...................................................................................................... 277
SiteInfo ................................................................................................................. 274
Startup Process ......................................................................................................279
syngo startup log ...................................................................................................278
Sysmgmt Diagnostics .............................................................................................281
System Management .............................................................................................281
Tune-Up/QA/Tests .................................................................................................. 277
Required Aids and Tools ................................................................................................. 7
Restore
Acronis ..................................................................................................................133
Restore (syngo) ..........................................................................................................103
ROT ............................................................................................................................. 13
RTC ..............................................................................................................................12
RTC A DIPP FRU .......................................................................................................... 140
RTC A(B) DIPP FRU ...................................................................................................... 140
RTC A(B) Interface ...................................................................................................... 140
RTC B DIPP FRU ...........................................................................................................140

Index 12 315
S Safety Information, Product-specific ............................................................................... 8

Save Logs .................................................................................................................. 287
SCM .............................................................................................................................12
Self defined (tests) ..................................................................................................... 138
Service Switches ........................................................................................................ 112
Service UI ...................................................................................................................100
............................................................................................................................. 102
Auto Report ........................................................................................................... 231
Control ..................................................................................................................112
DICOM Tests ..........................................................................................................144
Event Log .............................................................................................................. 267
File & Image Tools ................................................................................................. 200
Help ...................................................................................................................... 283
Reports ..................................................................................................................273
Test Tools .............................................................................................................. 137
Tune Up ................................................................................................................ 109
Utilities ..................................................................................................................239
Session History Report ................................................................................................277
SIRC status ................................................................................................................. 143
SiteInfo Reports ......................................................................................................... 274
Software Distribution ................................................................................................. 260
SRS .............................................................................................................................. 12
SRV_RAD ......................................................................................................................12
SS_test on ....................................................................................................................13
Stand & table tests ..................................................................................................... 142
Stand (tests) .............................................................................................................. 140
Starting the Service Software ..................................................................................... 285
Startup Process Reports .............................................................................................. 279
STRT_Inv ...................................................................................................................... 13
SW ...............................................................................................................................12
SW SS ........................................................................................................................ 112
Switch ......................................................................................................................... 49
SWR ............................................................................................................................. 13
syngo Service
syngo service ............................................................................................................. 100
............................................................................................................................. 102
Auto Report ........................................................................................................... 231
Control ..................................................................................................................112
DICOM Tests ..........................................................................................................144

316 12 Index
Event Log .............................................................................................................. 267

File & Image Tools ................................................................................................. 200
Help ...................................................................................................................... 283
Reports ..................................................................................................................273
Test Tools .............................................................................................................. 137
Tune Up ................................................................................................................ 109
Utilities ..................................................................................................................239
syngo startup log report ............................................................................................. 278
Sysmgmt Diagnostics ................................................................................................. 281
System Backup/Restore
Acronis ..................................................................................................................132
System Management Reports ..................................................................................... 281
T TBL .............................................................................................................................. 12
TCM .............................................................................................................................12
Test Pattern ............................................................................................................... 113
Test Pattern Selection for FD Systems ......................................................................... 116
Test Pattern, FD ......................................................................................................... 114
Test tools
AXCS tests ............................................................................................................. 140
Hardware tests ...................................................................................................... 137
SIRC status ............................................................................................................ 143
Stand & table tests .................................................................................................142
Third-party tests .................................................................................................... 141
Test Tools .................................................................................................................. 137
Third-party tests .........................................................................................................141
ACRONIS Image Management Console ...................................................................141
Mount/unmount the backup/restore drive .............................................................. 141
Trumpf service program .........................................................................................142
VDX configuration ................................................................................................. 142
Third-party Tests
Can Net Test ..........................................................................................................141
Managed Network Switch ......................................................................................142
Trumpf service program ............................................................................................. 142
Tune Up .....................................................................................................................109
Tune-Up/QA/Test Reports ........................................................................................... 277

Index 12 317
U UDC_act .......................................................................................................................13
UDC_nom .................................................................................................................... 13
ULI ...............................................................................................................................12
URö ist ......................................................................................................................... 13
URö soll ....................................................................................................................... 13
Utilities ...................................................................................................................... 239
UT_act ......................................................................................................................... 13
UT_nom .......................................................................................................................13
UZ ist ........................................................................................................................... 13
UZ soll ......................................................................................................................... 13
V VDX configuration ......................................................................................................142

Video Output ............................................................................................................. 115
W WD .............................................................................................................................. 13
X XRAY ........................................................................................................................... 13
XRQ ............................................................................................................................. 12
Z Zip Log File ................................................................................................................ 287

- Restricted - All documents may
only be used by authorized person‐
nel for rendering services on Sie‐
mens Healthcare Products. Any
document in electronic form may
be printed once. Copy and distribu‐
tion of electronic documents and
hardcopies is prohibited. Offenders
will be liable for damages. All other
rights are reserved.
healthcare.siemens.com/services
Siemens Healthineers Headquarters

Siemens Healthcare GmbH
Henkestr. 127
91052 Erlangen
Germany
Telephone: +49 9131 84-0
siemens.com/healthineers
Print No.: AXA4-000.840.20.04.02 | Replaces: AXA4-000.840.20.03.02

Doc. Gen. Date: 11.10 | Language: English
© Siemens Healthcare GmbH, 2009
siemens.com/healthineers

Artis Zee

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Artis Zee

Diunggah oleh

Hak Cipta:

Format Tersedia

Artis zee

Artis zee AXA4-000.840.20.04.02 Page 2 of 318 © Siemens, 2009

2.1 Troubleshooting Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.1 ACXS Problem Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

4.1 CAN Communication and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

5 Flat Panel Detector 58

© Siemens, 2009 AXA4-000.840.20.04.02 Page 3 of 318 Artis zee

5.1 Troubleshooting the Flat Panel Detector. . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

6 Image Quality Problems 59

6.1 Noisy Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

7.1 Troubleshooting the Power Distributor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

8 Service Software Functions 100

8.1 Service Software Home Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Artis zee AXA4-000.840.20.04.02 Page 4 of 318 © Siemens, 2009

8.8 Test Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

9.1 Starting the Service Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

© Siemens, 2009 AXA4-000.840.20.04.02 Page 5 of 318 Artis zee

9.7.3 Viewing the AXCS Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

10 Changes to Previous Version 304

11 List of Hazard IDs 305

Artis zee AXA4-000.840.20.04.02 Page 6 of 318 © Siemens, 2009

1.1.1 Required Aids and Tools

n Standard service tool kit

Tab. 1 For X-Ray Generator Service

n PTW DIADOS 97 17 612 KE999

1.1.2 Additionally Required Documents

n System Operating Instructions

© Siemens, 2009 AXA4-000.840.20.04.02 Page 7 of 318 Artis zee

1.2.1 General Safety Information

1.2.2 Product-specific Safety Information

1.2.2.2 Angio MR Miyabi

Artis zee AXA4-000.840.20.04.02 Page 8 of 318 © Siemens, 2009

1.2.2.3 Systems with Magnetic Navigation (NIOBE)

Fig. 1: Not allowed for patients with cardiac pacemaker

1.2.2.4 Control Cabinets

© Siemens, 2009 AXA4-000.840.20.04.02 Page 9 of 318 Artis zee

1.2.2.5 Patient Table

Fig. 2: Lift safety stud, tilt safety brackets

Artis zee AXA4-000.840.20.04.02 Page 10 of 318 © Siemens, 2009

1.2.2.7 X-Ray Tube Cooling System

1.2.3 Conventions and Abbreviations

CCM = Collimator Control Module

© Siemens, 2009 AXA4-000.840.20.04.02 Page 11 of 318 Artis zee

Tab. 2 System Naming

Artis Product Names Artis System Types

Signal name Description

Artis zee AXA4-000.840.20.04.02 Page 12 of 318 © Siemens, 2009

Signal name Description

Tab. 3 Abbreviations related to the X-Ray generator

Name Description Previous name

1.2.4 Tolerance Data

1.2.4.1 Torque Values

© Siemens, 2009 AXA4-000.840.20.04.02 Page 13 of 318 Artis zee

Artis zee AXA4-000.840.20.04.02 Page 14 of 318 © Siemens, 2009

2.1 Troubleshooting Assistance

Problem and Function Tests Links and Solutions

Tab. 5 Boot Problems

Problem and Function Tests Links and Solutions

© Siemens, 2009 AXA4-000.840.20.04.02 Page 15 of 318 Artis zee

Problem and Function Tests Links and Solutions

Problem and Function Tests Links and Solutions

Artis zee AXA4-000.840.20.04.02 Page 16 of 318 © Siemens, 2009

The data display shows “NO The system controller is down.

If the “REP” process is running: