Cios

Troubleshooting Instructions – System

Troubleshooting Guide

siemens-healthineers.com
 Document Version
Siemens Healthcare GmbH reserves the right to change its products and services at any time.
In addition, manuals are subject to change without notice. The hard copy documents correspond 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 Healthineers office to order a current version or refer to our website http://
www.siemens-healthineers.com.

Disclaimer
Siemens Healthcare GmbH 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 Healthcare
GmbH or one of its affiliates or who are otherwise authorized by Siemens Healthcare GmbH 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 Healthcare GmbH or one of its affiliates are not entitled to use this documentation without prior
written authority.

Copyright
“© Siemens Healthineers, 2020” refers to the copyright of a Siemens Healthineers entity such as:

Siemens Healthcare GmbH - 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

Siemens Healthcare Diagnostics Products GmbH - Germany

Corindus Inc. - USA

Page 2 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 Table of contents

1 General Information 6
1.1 General information 6
1.1.1 General 6

2 Service Restrictions 7
2.1 Service Restrictions 7
2.1.1 Option Wi-Fi, FLC IP address for “DICOM Net” 7
2.1.2 OpenApps, error after “AutoLic” 7
2.1.3 Restore of network settings failed 7
2.1.4 Error message after service session 8
2.1.5 PMS/Tune-up/Additional Tools/Manual Calibration (FD) 8
2.1.6 FL-C Watchdog appears during system startup (...system busy..) 8
2.1.7 FD calibration lost, detector data missing, I0 calibration missing after connecting
wrong C-arm 9
2.1.8 Navigation system network configuration, Save and Exit button not available 9
2.1.9 Images for left and right monitors are swapped (VA20 only) 9
2.1.10 Images for left and right monitors are swapped (VA30 only) 10

3 Service login 11
3.1 Service login, specific information 11
3.1.1 Service application cannot be started because TUI is not active 11
3.1.2 Service application switched to background 11
3.1.3 Service login with Russian keyboard on TUI 11

4 X-ray generation 12
4.1 Abbreviations Generator 12
4.2 Overview of Polydoros M25 cabinet (Spin, Alpha) 13
4.3 Overview of Polydoros M3 cabinet (Fusion, Connect, Flow) 14
4.4 Overview of D80 (Main Control) Switches, Polydoros M25 15
4.5 Overview of D819 (ESL) Switches, Polydoros M25 16
4.6 Overview of D80 (main control) switches, Polydoros M3 17
4.7 D80 7-Segment Display 18

5 TUI 20
5.1 TUI 20
5.1.1 Introduction and HW overview 20
5.1.2 SW Overview 21
5.1.3 Troubleshooting/helpful hints and background information 25

6 Imaging chain overview 31

6.1 Cios system VA20 31
6.1.1 Detailed image chain error messages 31
6.1.2 Instructions for image chain (FD-based) 31
6.2 Cios Alpha VA30, Cios Spin, Cios Flow 33
6.2.1 Instructions for image chain 33

7 Detector, Manual Defect Tool (only for VA30 systems) 35

7.1 Type of detector installed 35
7.2 Using the detector defect tool 35
7.3 Current manually flagged pixels 35
7.4 Detector mode for an acquired image 36
7.5 Manual defect calibration workflow was successful, but the defect is still visible 37
7.6 It is not possible to save the external defect map because it is not accepted 37

Cios | Troubleshooting Guide – Restricted – Page 3 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
Table of contents

7.7 Exporting the image data from the system 38

7.8 Deleting obsolete FD data 39

8 CoCa board (only available with FD systems until SW VA20) 41

9 Collimator 42

10 Switch-on sequence, power-on unit 43

10.1 Switch-on sequence, power-on unit 43
10.2 Power-on unit 44

11 Event log; File and Image Tools; Reports 47

11.1 Log files 47
11.2 Export the log files to the USB device by right-clicking the (i)-button. 47
11.3 Export logfiles or “Service Images” with “File and Image Tools”: 48
11.4 Service images, SRS transfer 49
11.5 Acsos.NT trace tool 50
11.6 Event log, File & Image Tools 50
11.6.1 Function Description 50
11.6.2 Opening the event log 51
11.6.3 Handling the event log 51
11.7 Reports 56

12 Test tools 58
12.1 AXCS Tests 58
12.2 Monitoring 59
12.3 3D visualization 59
12.4 Diagnostics, FD-based systems until SW VA20 61
12.5 Diagnostics, FD-based systems from SW VA30 63
12.6 Diagnostics, I.I.-based systems 64

13 XCU, AP-IDs 66
13.1 AXCS connection 66
13.1.1 There are three additional ways to measure the AXCS connection. 66
13.1.2 AP-IDs hex / dec: 66
13.1.3 “Ping” to Ethernet address via CMD shell 67
13.2 XCU, factory reset 67

14 FLC PC Troubleshooting 68
14.1 DIFS Tool and HDD Defragmentation 68

15 MCU; MCU_Ext.; D142; CAN I/O 69

15.1 MCU, 7-segment display 69
15.1.1 7-segment display explanation 69
15.2 MCU, ext., schematic (example Cios Alpha) 71
15.3 MCU, factory reset 72
15.4 MCU, fuses and troubleshooting 72
15.5 D142, LED status 75
15.5.1 D142 LED status explanation (vertical movement) 75

16 Radiation triggering 77
16.1 Radiation triggering 77
16.1.1 Requirements regarding radiation triggering 77

Page 4 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 Table of contents

17 CAN bus 78
17.1 CAN bus wiring 78

18 Remote Update Handling (RUH) 80

18.1 Update installation failed - system is blocked 80
18.2 “Fallback solution” if update installation failed and system is blocked 82

19 AX DICOM Tool 87
19.1 AX DICOM tool, anonymization process 87

20 Changes to previous version 91

Cios | Troubleshooting Guide – Restricted – Page 5 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
1 General Information

1 General Information
1.1 General information

1.1.1 General

1.1.1.1 Abbreviations

DICOM Digital Imaging and Communications in Medicine

EHC Ethernet HID converter

TUI Touch user interface (TCP, CCP, RCP)

TCP Trolley control panel

CCP C-arm control panel

RCP Remote control panel

ESU Energy storing unit

FL-C Fluorospot Compact

FD Flat detector

AXCS network Cios internal network

UPS Uninterruptible power supply unit

OGP Organ program

1.1.1.2 General safety information

NOTICE

Risk of death, injury, or material damage!

Non-compliance can lead to death, injury, or material damage.

Please note:

◆ The product-specific safety notes in the technical documentation,

◆ the general safety information in the document “Medical Products; Safety Information; General Safety
Notes“ (TD00-000.860.01.xx),
◆ the local safety guidelines.
◆ the safety information in SP00-000.860.02...

Page 6 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 2 Service Restrictions

2 Service Restrictions
2.1 Service Restrictions

2.1.1 Option Wi-Fi, FLC IP address for “DICOM Net”

Function FLC IP address for “DICOM Net” needs to be changed because same IP address is
already used by the hospital

Problem FLC IP address adaption via PMS is not possible.

Work-around Adaption of the FLC IP address is possible via FLC registry entry.
Check SKB or contact the HSC for detail information.

SW Version VA30B

Sporadic No

2.1.2 OpenApps, error after “AutoLic”

Function Error message 03-72 after performing “AutoLic” in service application

Problem With software VA30B, the AppHost license is available but the AppHost PC is dis‐
connected.
When performing the “AutoLic” procedure, the "AppHost Access (key)” will be set to
"Yes" in the system configuration and the error message 03_72 appears after each
restart.

Work-around Set under Service>Configuration>System>System Configuration “AppHost Access

(key)” to “No”, then perform “Config Check” / “Auto Conf” and reboot the system.

SW Version VA30B

Sporadic No

2.1.3 Restore of network settings failed

Function Restore of network settings

Problem After a restore of the network settings, the service login is not possible because
some LAN settings are not restored correctly. As a consequence, the TCP - pXCU
communication is interrupted and the “Service” tab card is not available.

Work-around When performing a restore of the imaging system (including the network settings),
reboot the systems twice after the restore.
If the imaging system restore (including the network settings) has already failed:
Connect a USB keyboard to the trolley USB connector and press key combination
<CTRL>-<Shift>-M> to display the “Service” tab card on the monitor.
Log in into Service, perform a restore of the network settings again (subfolder of
the imaging system) and restart the system twice.

Cios | Troubleshooting Guide – Restricted – Page 7 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
2 Service Restrictions

SW Version VA10, VA20

Sporadic Yes

2.1.4 Error message after service session

Function Service software is active, log off the service application

Problem After the service software is closed, the error message “243_402 - Disk almost full”
appears on the monitor.

Work-around After service has been performed, this error message can be ignored. Solved with
VA30B

SW version VA10, VA20

Sporadic No

2.1.5 PMS/Tune-up/Additional Tools/Manual Calibration (FD)

Function Service software, manual calibration (FD)

Problem The manual calibration tool has not yet been approved for use in the field and
therefore may not be used.

Workaround If you experience defective pixels, lines, or columns after a service calibration,
please save the images showing the defect in DICOM format and contact your local
uptime center. Solved with VA30C

SW version VA10, VA20, VA30B

Sporadic No

2.1.6 FL-C Watchdog appears during system startup (...system busy..)

Function Software catalog, download package -> SDGuiCatalog

Problem Software catalog, download package -> SDGuiCatalog crashed after a couple of
minutes. FL-C Watchdog appears during a new system startup

Work-around Workaround is not required because this workflow is not being used

SW version VA30C

Sporadic No

Page 8 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 2 Service Restrictions

2.1.7 FD calibration lost, detector data missing, I0 calibration missing after

connecting wrong C-arm

Function Detector not calibrated

Detector data missing
I0 calibration missing (only for 3D systems)

Problem System was started with the wrong C-arm connected to the trolley. After the right
C-arm is connected, the FD data and I0 calibration are gone.

Workaround Restart the system twice.

Delete the wrong FD data with SSW > Backup & Restore > Delete FD Data

SW version VA30

Sporadic No

2.1.8 Navigation system network configuration, Save and Exit button not
available

Function Configuration of network for navigation system

Problem In SSW- FL-C Service- Configuration- Navigation System, no network is selected.

Changing is impossible because the Save button is not available. The Exit button is
also not available.

Workaround Copy the following configuration manually from "C:\Service\WEB-INF\con‐

fig\default\common\NavigationSystemConfig.xml” to "C:\Service\WEB-INF\con‐
fig\NavigationSystemConfig.xml"

SW version VA30

Sporadic No

2.1.9 Images for left and right monitors are swapped (VA20 only)

Function Configuring the graphics card

Problem The images for the left and right monitors are swapped. This can happen when the
monitor is replaced, if the PC contacts are bad, when the software is reloaded, etc.

Workaround Change the setting under Control Panel > NVIDIA control panel > Display > Set Up
Multiple Displays.
Monitor 1 needs to appear on the left with a “*”, and monitor 2 needs to appear on
the right. You can drag and drop the monitors to the right places. Right click on
monitor 1 and select "Make Primary."
Accept the changes by clicking Apply and then OK.
Reboot the system.

SW Version VA20

Sporadic Yes

Cios | Troubleshooting Guide – Restricted – Page 9 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
2 Service Restrictions

2.1.10 Images for left and right monitors are swapped (VA30 only)

Function Configuring the monitor

Problem The images for the left and right monitors are swapped. This can happen when the
monitor is replaced, if the PC contacts are bad, when the software is reloaded, etc.

Workaround Change the setting under FLC Service > System > System Settings > Monitor Con‐
figuration.
Click "Initialize and swap displays", confirm the window, and then reboot the system.

SW Version VA30

Sporadic Yes

Page 10 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 3 Service login

3 Service login
3.1 Service login, specific information

3.1.1 Service application cannot be started because TUI is not active

Condition The TUI is not booting and therefore the “Data System” cannot be opened on the
TUI. The subsequent service application cannot be opened.

Solution 1. Click the left navigation bar of the live monitor to set the focus to the correct
(monitor) control area.
2. Connect a USB keyboard to the trolley USB connector and press key combination
<Ctrl>-<Shift>-<M> to open the “Service” and “Settings” tab cards on the monitor.

3.1.2 Service application switched to background

Condition The service UI is open and has been switched to the background

Solution Bring the Service UI to the front again:

1. With the <Alt>-<TAB> keys, which are enabled in Service mode.
or
2. Click the “Exam” / “Service” toggle button on the left monitor.

3.1.3 Service login with Russian keyboard on TUI

Condition Service login with Russian keyboard layout on TUI is obscured because of Russian
(Cyrillic) TUI layout.

Solution To get Latin characters on the Russian (Cyrillic) TUI layout, use the shortcuts
CTRL+ALT and CTRL+ALT+SHIFT to switch to the Latin characters.

Cios | Troubleshooting Guide – Restricted – Page 11 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
4 X-ray generation

4 X-ray generation
4.1 Abbreviations Generator

Fig. 1:

Page 12 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 4 X-ray generation

4.2 Overview of Polydoros M25 cabinet (Spin, Alpha)

Fig. 2: M25 cabinet

Cios | Troubleshooting Guide – Restricted – Page 13 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
4 X-ray generation

4.3 Overview of Polydoros M3 cabinet (Fusion, Connect, Flow)

Fig. 3: M3 cabinet

Page 14 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 4 X-ray generation

4.4 Overview of D80 (Main Control) Switches, Polydoros M25

Fig. 4:

Cios | Troubleshooting Guide – Restricted – Page 15 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
4 X-ray generation

4.5 Overview of D819 (ESL) Switches, Polydoros M25

Fig. 5:

Page 16 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 4 X-ray generation

4.6 Overview of D80 (main control) switches, Polydoros M3

Fig. 6: D80 Polydoros M3

Cios | Troubleshooting Guide – Restricted – Page 17 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
4 X-ray generation

4.7 D80 7-Segment Display

Fig. 7: left digit

Page 18 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 4 X-ray generation

Fig. 8: right digit

Cios | Troubleshooting Guide – Restricted – Page 19 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
5 TUI

5 TUI
5.1 TUI

5.1.1 Introduction and HW overview

The next generation of TUIs (xCP2/ATLAS) will be available in 2017.

As in the specified spare parts list, the next-generation TUI system requires software version VA20D or higher.

The older TUI version (xCP1/Q7) can be combined with the new generation TUI and is compatible with all
system software versions.

• The following images provide a summary of the aforementioned components and their location in the Cios
system (FD-based system is shown):

Fig. 9: Control Panels and EHC overview

Page 20 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 5 TUI

5.1.2 SW Overview

5.1.2.1 Platform Status Information Page

The platform status information page is Cios specific. It covers TUI-specific information as well as
communication status details available via network. The following diagram provides an overview of the
platform status information page. It does not to offer an in depth-diagnosis function for the system. Its main
task is to give a quick overview of the system's component connection status, which can provide a good, first
indication of where to look for a failure.

Fig. 10: Cios platform status information page

1 Indicates the type of TUI, possibilities are: TCP/CCP/RCP

2 Shows the TUI GUI build version
3 Shows the current GUI language and keyboard layout
4 Indicators for main system components with (A)XCS interface: grey: status unknown; green: component
is online; red: component has changed to offline
5 Closes the window and returns to TUI
6 Enters the RSC Diagnosis screen

Cios | Troubleshooting Guide – Restricted – Page 21 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
5 TUI

• The following components are covered in the information display:

– TCP/CCP/RCP (ApID 0x5A/0x5B/0x5C) - IP address TCP/CCP/RCP: 10.1.1.5/10.1.1.6/10.1.1.7.

– The connection between the TUI and EHC - IP address EHC: 10.1.1.116.

– The TUI interface (part of XCU) (ApID 0x5D).

– The RSC of the TCP/CCP/RCP (ApID 0xBE/0xBF/0xC0).

– The REP error processing component (part of XCU) (ApID 0x60).

– The XCU (ApID 0xF0) - IP address 10.1.1.24.

– The FL-C (ApID 0xF3) - IP address 10.1.1.25.

– The generator interface (part of MCU) (ApID 0x50).

– The CCU collimator control (part of MCU) (ApID 0x21).

– ACSOS (typically not present, only for development) (ApID 0x62 & 0x63).

– The SCU or MCU (ApID 0x20).

– The OCU for hand switch / foot switch control (part of MCU) (ApID 0x22).

– The PMS service software (part of FL-C) (ApID 0x61).

– The VCU for the video manager control (part of XCU) (ApID 0xEA).

– The DCU (part of MCU) (ApID 0x28).

– The TUI-EX that controls the TUI HW buttons and LEDs (part of MCU) (ApID 0x32).

Other components with no native (A)XCS interface like CoCa, XDR, collimator and detector cannot be
covered with this functionality currently. A green dot indicates only that a component has correctly
connected to the system network - it does not guarantee that the component is error-free.

5.1.2.2 Diagnosis

• The diagnosis is TUI-specific and offers in-depth status and testing capabilities relevant for the TUI and EHC.
>> As long as the diagnosis is active, the TUI SW is offline (has sent TURN_OFF signal) - this is normal and not
an error.

Main Screen

The RSC diagnosis main screen contains the following main functions (example xCP2/ATLAS):

Page 22 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 5 TUI

Fig. 11: TUI Diagnosis

1. The HW signature display for the "left front controller" module containing all HW buttons and LEDs to the
left of the touchscreen. The following values are typical: TCP: 0x0 or N/A; CCP/RCP: 0x2 (Cios Alpha/Spin)
or 0x3 (Cios Fusion/Flow)
2. Control panel role, typical ones are: TCP, CCP or RCP

3. Update the SW locally from a USB stick plugged into one of the ports on the right side (only relevant if an
FTP download is not possible). See the “Download” section (“SW update via USB stick” chapter) within this
document for further details.

4. The HW signature display for the "right front controller" module containing all HW buttons and LEDs to the
right of the touchscreen. The following values are typical: TCP: 0x0 or N/A; CCP/RCP without joypad module:
0x0 or N/A; CCP/RCP with joypad module: 0x2 (Cios Alpha/Spin)

5. Update the SW from the system's FTP server (must run on the FL-C or a PC with IP address 10.1.1.25) (only
relevant if a normal download via PMS is not possible).

6. Display of all kinds of TUI-specific HW and SW versions. The main version of the image is displayed under
"OS image version" (xCP1 = Q7; xCP2 = ATLAS)

7. Toggles all connected LEDs (CCP/RCP/joypad only) to "on" or "off".

8. Starts the HW button self-test (for details see the “Button self-test” chapter).

9. Performs a touchscreen calibration (for details see the “Touchscreen calibration & test” chapter).

10. Starts the monitor test (for details see the “Monitor test” chapter).

11. Starts a touchscreen drawing test (for details see the “Touchscreen calibration & test” chapter).

Cios | Troubleshooting Guide – Restricted – Page 23 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
5 TUI

12. Increase backlight brightness for testing.

13. Decrease backlight brightness for testing (as soon as the RSC diagnosis is exited, the default value is applied
again).
14. Starts the PCU stability test (for details see the “Stability and cooling test” chapter).

15. Plays an audio jingle to test the sound HW of the control panel.

16. Reboots the control panel.

17. Resets the control panel to factory defaults (backup/restore is not required since all control panel-specific
parameters, like language, are automatically applied each time the system boots).
18. Electrical input: Nominal 24Vdc / Fan Speed only with TCP available.

19. Graphical display of the control panel - if a button is pressed on the CCP/RCP or joypad, it is graphically
displayed in the form of a red rectangle (only one button may be pressed in this specific test). If a button
module is not available, the respective button display is grayed out.

20. EHC-specific information (animated heartbeat, firmware version, and serial number) (this information is
displayed only on the TCP, which is the EHC master controller.

The new generation TUI (xCP2 /ATLAS) contains additional live monitoring of the 24V power supply and of
the TCP fan speed in the diagnostic screen.

–> A malfunction is indicated with a yellow warning triangle in the diagnostic screen.

5.1.2.3 Access to the SW diagnosis functions

• The RSC diagnosis can be entered via PMS. See the PMS documentation for a "how-to".

• If the PMS is not available or you want to enter the platform status information page, perform the following
steps:

– Start the TUI.

– Open the virtual keyboard.

– Press the following keys at a 1s rate.

– ALT press → ALT release → CTRL press → CTRL release → SHIFT press → SHIFT release → CAPS LOCK press
→ CAPS LOCK release.

>> This works only on a TCP - if no TCP is present in the system, the key combination does not work.

– If the key combination was correct, a jingle sound is played; if the combination did not work, wait for 10
seconds and repeat the procedure. If it still does not work, close the virtual keyboard, wait for 10s and
repeat the procedure.

• Now you are in the platform status information page. To enter the RSC diagnosis press the "TUI diagnosis"
button in the bottom, right side of the dialog box.

Page 24 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 5 TUI

5.1.3 Troubleshooting/helpful hints and background information

Q: When the system starts, all LEDs on the TUI flash continuously. What does this mean?

A: The button self-test detected a pressed HW button during startup that could be a user fault or a HW
defect (broken button, defect electronics, etc.). Go to the RSC diagnosis page and check the control
panel diagram for a button marked with a red rectangle (indicates the button causing the failed
self-test - if more buttons are affected only the last button in the self-test cycle is shown) and perform
a button self-test cycle. If the error continues or occurs sporadically, the control panel must be
replaced due to a HW defect.
If a HW button failure is permanent, it is normal for a control panel to switch off after boot-up to
avoid system malfunction. The Cios also works with a switched off control panel (its emergency
stop is still functional), however some movement functions will not work if a CCP is broken and the
customer has no RCP. In this case the control panel must be replaced.

Q: The touchscreen accuracy is bad. How can it be improved?

A: The touchscreen uses a 5-wire resistive single touch with good robustness and low drift of the
accuracy over time. Nevertheless, accuracy can degrade slightly after long usage or suboptimal
initial calibration. Perform a touch calibration via the RSC diagnosis page - typically a 9-point cali‐
bration is sufficient. Afterwards test the touch calibration with the RSC diagnostics. If the result is
still bad, try a 16-point calibration - use an object with a small tip (but no sharp objects like a
screwdriver!) to touch on the displayed calibration dots in the center as accurately as possible. If
accuracy remains bad after additional calibration cycles or quickly degrades again, replace the con‐
trol panel.

The calibration accuracy is specified to be within 1.5% - this means that a delta of approx. 5 mm between
the touched point and detected coordinates is possible and does not indicate a failure.

Q: The TUI display seems inhomogeneous, flickers or shows other distortions. The display seems to
have pixel errors. Can this be changed?

A: Typically this is a very unlikely error, however go to the RSC diagnosis page and try the monitor test.
The test contains some special test images in the basic colors and black/white to detect inhomo‐
geneous backlight illumination and pixel errors. To test the stability of the monitor for high fre‐
quency images, there are three special test images with vertical/horizontal lines and a black/white
checkerboard image. If the monitor has a problem, you should see distortions in this test.

Q: The RSC diagnosis shows one or more yellow warning signs. What should I do?

A: The RSC diagnosis has built-in logic to detect abnormal configurations or HW faults. A yellow warn‐
ing sign can indicate a
• Version mismatch (try upgrading the SW)
• A HW problem (e.g. temperature too high → internal TUI cooling problem → HW exchange!)
• A cabling problem (e.g. network link has not synchronized with 1GBit/s → check cables, especially
network)

If the warning sign still displays, please contact your service representative or development to discuss further
action.

Q: A joypad is connected to the CCP/RCP but the graphical display in the RSC diagnosis shows it grayed
out. Or the HW buttons/LEDs on the joypad do not work correctly. What needs to be done?

Cios | Troubleshooting Guide – Restricted – Page 25 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
5 TUI

A: Has the control panel been "cold" started after attaching a joypad? The joypad connector does not
support hot-plugging like the USB and will recognize the joypad only after a cold initialization.
If the error continues after a cold restart: power down the control panel, detach the joypad and
check the cable. Is it plugged in correctly and has it locked or is it not completely in place? Is pin 1
located correctly (see labeling on the joypad cable and control panel housing), or has the joypad
cable been plugged in upside down (only possible with brute force)? After correctly plugging in the
cable, re-attach the joypad and cold boot the affected control panel.

Q: The control panel does not play sounds. What is wrong?

A: Most likely the sound volume has been set to a very low value in the PMS. Go there and check. If
the volume is set to a medium/high value and you still do not hear anything go the RSC diagnosis
and perform the audio test. If the jingle does not play, the TUI is defective and must be replaced.

Q: Some HW buttons seem to not work correctly. What is wrong?

A: Go to the RSC diagnosis screen and press each button. The graphical display should clearly indicate
which button is pressed, without flickering, and the button event counter should increment
smoothly and regularly as long as the button is pressed. If not and the button is part of the joypad,
try re-attaching the joypad and then perform a cold reboot. If this does not help, a HW defect is
likely - replace the HW.
During this test, avoid pressing emergency stop while pressing other buttons, otherwise the display
might indicate only a pressed emergency stop button. Remember, the RSC can display only one
pressed button at a time. This limitation does not affect the system itself; it applies only to the
button test.

Q: The control panel behaves strangely, crashes, gets very hot, etc. The touchscreen does not react
after a certain period of time. Can I do something about it?

A: Execute the stability/cooling test In the RSC diagnosis screen for 3h. If normal temperatures or CPU
calculation errors occur (all indicated by yellow warning signs), replace the control panel. For the
TCP, also check that the fan on the backplate is working (be careful. The TCP can get quite hot on
the back plate without the fan). The device will function without one but its lifetime is decreased.

Q: The control panel seems slow. Is this normal?

A: Typically this is caused by system communication problems and not by the control panel itself.
However in certain constellations, the network link to the control panel might not have synchron‐
ized with one GBit/s or might have bit errors on the IP level. Bad cabling in the system is the cause.
To check this, go to the RSC diagnosis screen and watch for yellow warning signs in the network
section on the right side. If the link speed is below GBit/s or in/out errors occur, there is some cabling
fault. Replacing the control panel will most likely not cure the problem - do so only if the system
cabling is really OK.

Q: The control panel boots but remains at 20% for more than 1 minute while booting. Additionally it
can show some green graphic artifacts at the top, left corner of the start screen. What does that
mean?

A: Check if a bootable USB stick has been plugged into the service terminal on the right side. If yes,
remove it and restart. If the problem continues, the file system has a serious issue and cannot load
the operating system. Consider replacing the control panel. Although there is a procedure to recover
the file system, replacing the device is sensible since HW problems are likely. Typically the file system
is read-only and should not be damageable at all.

Page 26 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 5 TUI

Q: The control panel boots but remains at 60% for more than 2 minutes while booting. What does that
mean?

A: A serious error occurred during main component initialization - a download or access to RSC diag‐
nosis is not yet possible.
Check the joypad cabling.
Another reason for this error can be network problems.
Check to make sure the Ethernet cable to the affected control panel is securely plugged into the
XCU or the MCU Ethernet switch.
If this does not help, consider replacing the control panel.

Q: The control panel boots but remains at 80% for more than 2 minutes while booting or suddenly
restarts after a few minutes. What does that mean?

A: The control panel cannot find the network link or the XCU - it tries several times. If it fails continu‐
ously it reboots itself and tries again. Depending on the constellation, it may emit a chirping sound
before rebooting. The control panel itself is not faulty since it finished up to 80% of its boot-up.
However, check the cabling and verify that the XCU is online.

Q: The control panel boots but remains at 95% for more than 3 minutes while booting. What does that
mean?

A: The control panel itself is not faulty since it finished up to 95% of its boot-up. It is waiting for
initialization by the XCU. Check the cabling and verify that the XCU is online (you can use the
platform status information page).

Q: The virtual keyboard is not available on the TUI. What is the reason?

A: It is not possible to connect to the EHC. Check the platform status information page. The link to the
EHC must be green. If it is red, try to ping the EHC from the FL-C (ping 10.1.1.116). If the ping does
not work, check the cabling.
If the EHC is still not recognized and cannot be pinged at 10.1.1.116, change the RJ45 connector
on the XCU temporarily. This might be necessary since the MAC discovery function is slow on some
Ethernet switching and 10Mbit/s devices like the EHC. It might take some time to recognize the EHC
with a new firmware version. Replacing the connectors manually triggers the discovery. If every‐
thing works, re-establish the original cable configuration.

Q: I want to use the virtual keyboard to access the FL-C BIOS but the control panel keyboard is not ready
when I start the system. How can I enter the BIOS?

A: After the system has booted, perform a warm-start of the FL-C only - then you can enter the BIOS
since the control panel and EHC are already functional. You might need to unlock the control panel
to allow the necessary key (combination), like F2, to enter the BIOS. For how to unlock the control
panel, see the next question.

Q: I want to use the virtual keyboard in the FL-C BIOS or other "non-Windows" environments that expect
an English keyboard layout. Unfortunately the keyboard is localized to "non-English" and I do not
get the characters I type. I'm also missing some important keys like DEL, and some combinations
like CTRL+ALT+DEL do not work. What can be done?

Cios | Troubleshooting Guide – Restricted – Page 27 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
5 TUI

A: The virtual keyboard in customer mode has fewer buttons than in service mode and also filters out
many key combinations that would allow the customer to take unauthorized control of the system.
Currently the following combinations are blocked in customer mode:
"CTRL + ALT + DEL"
"ALT + F4"
"F2" (BIOS access on Fujitsu computers)
"CTRL + SHIFT + ESC"
"CTRL + ESC" "ALT + TAB"
"SHIFT + ALT + TAB"
"ALT + ESC"
"CTRL + ALT + CAPS LOCK
"CAPS LOCK + CTRL + ALT
"F11"
"F8" (Windows Safe Mode)
"CTRL + C" (RAID BIOS access)
"F12"
"ALT + F2" (FLASH BIOS)
"CTRL + D" (IE)
"CTRL + E" (IE)
"CTRL + I" (IE)
"CTRL + J" (IE)
"CTRL + N" (IE)
"CTRL + W" (IE)
"ALT + SHIFT" (language change)
"CTRL + ALT + ESC"

For full access, go to the virtual keyboard on the TUI and press the following keys at a 1s rate: ALT press →
ALT release → CTRL press → CTRL release → SHIFT press -> SHIFT release → ALT press → ALT release.
This works only if a TCP is present in the system and online - the key combination itself can be typed on any
available control panel.
The keyboard is now unlocked, offering addition keys such as DEL. Additionally you can switch it to English
layout for non-Windows environments on the fly by pressing the language button at the top left of the
keyboard.
After rebooting or closing the keyboard, it is automatically locked again. You cannot permanently unlock
the keyboard. If you closed an unlocked keyboard, you might need to enter the key combinations shown
twice.

Q: The control panel does not start (no screen displays, no green on indicator on CCP/RCP). What is
wrong?

A: Check the cabling; is the control panel supplied with 24V (±20%)? Are all fuses on the system side
OK? If yes, replace the control panel.

Page 28 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 5 TUI

Q: Are there any serviceable parts inside the control panel? Do I have to open the control panel housing?
What should I do with the interfaces on the right side?

A: No, there are no fuses or batteries that would require checking or replacement. The housing can
be opened only by the supplier with a special tool (do NOT try it or damage may result). - only the
side cover can be opened by the service technician or in the factory. During service you need check
only the touchscreen calibration. Repeat if necessary. Also check that the back on the back plate of
the TCP is working. If it is broken, replace the TCP.

The electrical interfaces on the right interface are typically not relevant for service operations with the VA10/
VA20 release (might change with later releases). Do not try to connect a USB keyboard/mouse to these
connectors. You will not damage anything but neither will it work. Neither can you enter the BIOS, which
is password-protected and has no relevant functionality for the service technician. The other interfaces, like
the HDMI connector, are also for future use.

Q: The RCP cable is broken; can I replace it in the field?

A: Unfortunately not - do NOT try to open the six screws on the backplate of the control panel - the
terminal below will not allow a cable exchange. If the cable is broken, replace the RCP. The connector
design on the C-arm side is flexible, however, and cable damage is unlikely. The cable was also
selected to withstand rough handling quite well, so it would take some time and very rough han‐
dling to damage it.

Q: The RCP/CCP/TCP got wet; is it damaged?

A: No, the RCP/CCP are designed to support IP65; the front of the TCP is designed to support IP54. It
is very unlikely for the device to sustain damage due to spilled liquids.

Q: Someone dropped the RCP. It seems OK, but what has to be tested to be sure?

A: The RCP is designed for rough handling, so damage is unlikely as long as the screen/touchscreen is
not shattered. The steps for a minimal function test are described in the "installation procedure"
section.

Q: I tried to perform a download, but the TUI showed a dialog with an error message/warning indicating
that the download did not work. What should I do now?

A: Obviously the FTP server is unreachable (running on FL-C - 10.1.1.25) or the TUI SW home directory
on the FL-C (typically C:\addon\TUI\TCP or CCP or RCP) is empty or files are missing. The download
stopped to avoid corruption of the control panel. Make sure that the download infrastructure is
working and retry. You can also abort the download by pressing the corresponding button on the
TUI - afterwards the TUI reboots with the old SW.

Q: I have interrupted a download to the TUI. Is it broken now?

A: No, the TUI has an automatic error detection function and MD5 checksum verification of a download
before it is applied to the internal flash file system- this prevents permanent application of a broken
or incomplete download. Just restart the control panel and retry. No file system or operating system
damage will occur.
Download interruptions to the EHC must be avoided - the EHC can be damaged since it has no
download error protection.

Cios | Troubleshooting Guide – Restricted – Page 29 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
5 TUI

Q: What is exactly is updated during a SW download to the control panel?

A: The TUI SW and the whole operating system (Windows CE) is updated - the system BIOS of the
control panel is not updated. However the BIOS does not typically change over time. If an update
is ever required, it is done by special image for a bootable USB stick that is made available from
development.

Q: The RCP cable/connector seems to not lock completely on the RCP interface at the C-arm and can
be pulled out with a fair amount of force. Is it broken?

A: No - the cable interface on the C-arm is designed to automatically release if a force of approx. 30
N or more pulls the cable in the axial direction. Additionally the female connector at the C-arm is
flexible and can be pulled out if a strong force is applied to the RCP cable. Both measures should
prevent damage to the RCP cable/interface if the customer applies high force to the cable.

Q: At a minimum, which control panels are required to operate the Cios system?

A: Basically, one control panel (out of three) is sufficient. If motorized movements must be controlled,
at least one CCP or RCP is required (TCP is not sufficient). If the EHC is missing, all the functions that
require a keyboard do not work (e.g. patient registration except Emergency, Annotation/Measure‐
ment, HIPAA Login, etc.)

Q: I have made some TUI specific settings (language, volume, etc.) in the PMS and forgot to attach the
RCP to the system during this process. Do I have to go to the customer again and repeat the settings
to update the RCP with the new settings?

A: No. The RCP gets its settings automatically via the network during each boot-up.

Q: What is the default network speed for the control panels and EHC?

A: The control panels operate at 1000 Mbit/s full duplex; the EHC operates at 10Mbit/s half duplex.
Note: If an Ethernet speed problem is detected, a corresponding warning APID240 ID9601 will be
shown in the eventlog.

Page 30 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 6 Imaging chain overview

6 Imaging chain overview

6.1 Cios system VA20

6.1.1 Detailed image chain error messages

Message Reason Action

1 Buffer fill level has reached alarm level Image chain aborted X-ray because the Check the disk drive
imaging system could not retrieve the
images fast enough
- The disk drive may be full or fragmented

2 Buffer fill level has reached critical Imaging system aborted X-ray because Check the disk drive
level the imaging system could not retrieve the
images fast enough. - The disk drive may
be full or fragmented

3 Detector disconnected Connection between FD and CoCa board Check cabling / connectors
interrupted- Cable break- Connector
loose

4 CIIF disconnected Connection between XDR board and Check cabling / connectors
CoCa board interrupted- Cable break-
Connector loose

5 Could not connect to CoCa: Device Connection to CoCa board could not be Check the cabling and connec‐
not ready established - Ethernet connection inter‐ tors. Check the CF card on the
rupted - CF card not correctly plugged in CoCa board to make sure it is
- CF-card defective locked into place properly. Try
replacing the CoCa board, and
then perform a restore.

6 Port disabled Following error from no. 3, 4, or 6

7 The previous calibration not finished The calibration was aborted Perform complete service cali‐
correctly bration again

8 Invalid interface version Inconsistent SW level IC/FL-C Reinstallation and restore

9 Inconsistent configuration image Inconsistent SW level IC CoCa configura‐ SW update for CoCa board
chain <-> detector tion
Reinstallation and restore

6.1.2 Instructions for image chain (FD-based)

6.1.2.1 LED status on FD

• red: No connection to CoCa

• green: Connection ok

Cios | Troubleshooting Guide – Restricted – Page 31 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
6 Imaging chain overview

6.1.2.2 CoCa Board

• 16 bit stream-based processing

• FD controller software

• Conditioning pipeline

• Minor calibration tasks

6.1.2.3 LED status on Coax

• blinking = Connection ok

• dark = No connection to XDR

6.1.2.4 Image Chain Software

• Component drivers (for GPU, XDR, Coca)

• Workflow control (acquisition, replay)

• Real-Time display & preview images (TUIs)

• DICOM rendering (no patient data, no transfer)

6.1.2.5 Buffered Transfers

1. XDR to RAM

2. RAM to GPU

on GPU: DEXI calculation & temporal signal processing

3. GPU to RAM: handover to FL-C application

on GPU: application-based rendering & display

6.1.2.6 XDR board (no ext. status LED):

• 16 bit real-time image receiver, 4 PCIe

• Up to 512 MB RAM for image buffering

• 1.2 GBit/s input link from CoCa board (Coax)

• Pixel streaming architecture

• Line-based error correction

6.1.2.7 GPU processing & display

• 32 bit floating point pipeline

• Real-time DEXI calculation

• Parallel: RAM transfers & application-based rendering

• Constant time display (<=30 fps)

Page 32 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 6 Imaging chain overview

Fig. 12: Image Chain

6.2 Cios Alpha VA30, Cios Spin, Cios Flow

6.2.1 Instructions for image chain

6.2.1.1 LED status on FD (behind cover)

• red: No connection

• green: Connection OK

6.2.1.2 Image Chain Software

• Component drivers

• Workflow control (acquisition, replay)

• Real-Time display & preview images (TUIs)

• DICOM rendering (no patient data, no transfer)

Cios | Troubleshooting Guide – Restricted – Page 33 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
6 Imaging chain overview

6.2.1.3 Buffered Transfers

1. Ethernet to RAM

2. RAM to GPU

on GPU: DEXI calculation & temporal signal processing

3. GPU to RAM: handover to FL-C application

on GPU: application-based rendering & display

6.2.1.4 GPU processing & display

• 32-bit floating point pipeline

• Real-time DEXI calculation

• Parallel: RAM transfers & application-based rendering

• Constant time display (<=30 fps)

Fig. 13: ImageChain_VA30_

Page 34 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 7 Detector, Manual Defect Tool (only for VA30 systems)

7 Detector, Manual Defect Tool (only for

VA30 systems)
7.1 Type of detector installed
If multiple detectors can be selected when you open the calibration mode and you are not sure which one is
currently installed, use the FD-Info Tool.

• Start the SSW.

• From the FL-C SSW, select <Test Tools> .

• From Test Tools, select <FD-Info> ( Page 35, Fig. 14) (1).

>> A detector information page showing the serial number of the currently installed detector will open.

Fig. 14: FD-Info

7.2 Using the detector defect tool

The manual defect tool may only be used with VA30 systems.

Before using the manual defect tool, make sure that a normal FD calibration does not solve the issue.

7.3 Current manually flagged pixels

• Start the SSW.

• From the FL-C SSW, select <Tune-up> .

• Click <Manual Calibration> in the section “Additional Tools”.

>> ManualDefectTool window will open.

Cios | Troubleshooting Guide – Restricted – Page 35 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
7 Detector, Manual Defect Tool (only for VA30 systems)

• Click <Open External> ( Page 36, Fig. 15) (2) in the Defect Map ( Page 36, Fig. 15) (1) menu.

Fig. 15: Open external

• The currently flagged pixels are visible.

• To set and clear detector defects, please follow the description in the Online Help VA30C instructions:
<Online Help VA30>-<Tune-up>-<Additional Tools>-<Manual Calibration>-<Flag the Defects>

7.4 Detector mode for an acquired image

Generally, it is not possible to extract this defect map information from an FL-C image. If you still know the
system setting for the image, you can refer to the table below. Note that for mid-dose levels, the FD mode is
ambiguous. The color coding in the tables denotes the modes between which the defect map information can
be shared.

For the 976x976 images, the 1952x1952 modes can also be selected in the menu. Make sure you don’t
select the wrong matrix size! Select a mode with the same matrix size as the opened image (see the window
title).

Page 36 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 7 Detector, Manual Defect Tool (only for VA30 systems)

Fig. 16: Detector mode

7.5 Manual defect calibration workflow was successful, but the defect is still
visible
In rare cases additional defects that were not visible during the previous test can now be visible. If they are
close to the previous defect, it may seem that flagging of the defects did not work. If this is the case, you can
save the new image and repeat the procedure with the new image.
You can also use the Manual Defect Tool to open several FL-C images one after the other. When you do this,
the image windows will be synchronized which allows you to check whether it is the same defect or not. If
the flat field image used to flag the defect was a DICOM image, then it might be flipped or rotated relative to
the pixel matrix of the detector. Then the wrong pixels were flagged, and no change is visible. In this case try
to produce an FL-C image that shows the defect and repeat the procedure.

If this behavior occurs after you used an FL-C image, confirm that the defects are properly flagged in the external
defect map ( Page 35 Current manually flagged pixels).

If this is the case, please contact the RSC/HSC and provide the information as described in ( Page 37 It is not
possible to save the external defect map because it is not accepted).

7.6 It is not possible to save the external defect map because it is not accepted
The FD calibration only allows defects if they are within specification. For example, touching rows or columns
are not accepted. You should always flag only necessary pixels to make sure that you don’t create a situation
that is out of specification.

If it is still not accepted after the visible defects have been manually flagged, you can check if there are flagged
defect clusters or adjacent lines from previous manual calibrations which might be not need to be flagged.
You can select them directly in the defect map and right-click on “Clear Defects” to remove them from the
defect map.

Click on Calibration > Acceptance Check to check the defect map again and view a summary report showing
the type of defect that is out of specification (not OK).

If multiple defects are visible, it makes sense to add them one by one followed by an acceptance check to find
out which is the one that causes the problem. If

If the acceptance test is passed, follow the description in the Online Help VA30C instructions: <Online Help
VA30>-<Tune-up>-<Additional Tools>-<Manual Calibration>

Cios | Troubleshooting Guide – Restricted – Page 37 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
7 Detector, Manual Defect Tool (only for VA30 systems)

Fig. 17: Defect statistics

If removing the defects does not solve the issue and defects are still visible in the flat field image, the detector
may have to be replaced. Please contact the HSC and provide the following input.

• The FL-C image showing the defect.

• Image data - see the relevant section for information regarding export of this data

• Defect type (single pixel, row or column) you want to add.

• Coordinates of the defect you want to add (shown on the bottom left of the manual defect tool window,
when you hover over the defect with the mouse cursor)

7.7 Exporting the image data from the system

The FL-C service includes a functionality for exporting the image data. This set of data will provide information
that is necessary for a detailed analysis if problems occur during the performance of the manual calibration.

To export the data, proceed with the following steps:

• Start the SSW.

• From the FL-C SSW, select <File&Image Tools>.

• Click <Log & Config Files> ( Page 39, Fig. 18) (1) in the File&Image Tools menu.

• Select <Imaging Data> ( Page 39, Fig. 18) (2) in the upper File Type selection menu.

>> The file size will be in the range of 700 MB per detector that is installed on the FL-C.

• Click <Save> ( Page 39, Fig. 18) (3).

Page 38 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 7 Detector, Manual Defect Tool (only for VA30 systems)

Fig. 18: Export image data

7.8 Deleting obsolete FD data

If the detector is replaced, the calibration information will not be deleted automatically. Normally it is not
necessary to manually delete these files. In some situations, e.g. when you need to make image data backups,
you might want to delete them to reduce the file size of the backup.

• Start the SSW.

• From the FL-C SSW, select <Backup & Restore>.

• Click <Delete FD Data> ( Page 40, Fig. 19) (1) in the FD menu.

>> A list of all installed detectors will be displayed.

• Check all detectors ( Page 40, Fig. 19) (2) you want to delete from the FL-C.

Cios | Troubleshooting Guide – Restricted – Page 39 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
7 Detector, Manual Defect Tool (only for VA30 systems)

• Click <Go> to start the clean-up.

Fig. 19: Delete FD data

Page 40 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 8 CoCa board (only available with FD systems until SW VA20)

8 CoCa board (only available with FD

systems until SW VA20)
CoCa board, 7 segment digits

“0-” Idle state; during startup: FLC not yet connected to the CoCa board; in operational mode: only
during state transitions from “1 0” to “2 0” and vice versa.

“1 0” Ready for X-Ray (in the normal situation, this should be the display in S1 outside of the acquis‐
ition sequences).

“1 1” X-Ray Running (during acquisition in the patient mode).

“2 0” Ready for Service (should be seen during FD calibration and in SW patches).

“2 1” Acquisition during calibration procedure (such as thermal calibration, delta calibration).

“X Y” During a software upgrade from CoCa, depending on the current patch status (on the "0 0" to
"1 0") the counters run through; counters "0 7", "0 8" and "0 9" are critical; they take a long
time and power may not be switched off during this phase (even better: never switched off
during the upgrade).

“- -” CoCa goes into this status following an upgrade. If “- -” is displayed, then either reboot the
system or disconnect X10. Note: “- -” is also displayed when the download screen in the service
application is exited.

In addition, there are ". " symbols between the numbers, e.g. "0.-" or "1.0" that display whether data are
currently being read from the archive, written to the archive, or are to be transferred via the telegram interface.

If the CoCa board experiences a hardware problem:

The 7-segment display can show other undefined 7-segment symbols during the system start-up. These
symbols are not shown in the table above.

Cios | Troubleshooting Guide – Restricted – Page 41 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
9 Collimator

9 Collimator
Collimator LEDs

Green Red Usage

1Hz Off Firmware Download.

On On Collimator Boot-Up (for a short period of time after reset).

5 Hz Off Pre-operational.

On Off Operational.

n.a. Single CAN Error / Wrong baud rate.

Flash

5 Hz Double Guarding Error.

Flash

On On BUSOFF.

Page 42 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 10 Switch-on sequence, power-on unit

10 Switch-on sequence, power-on unit

10.1 Switch-on sequence, power-on unit

Steps Possible Errors Solution

1 Plug trolley into socket System not configured for Change tabs of transformer (Xn) to correct voltage
this voltage

2 Start button glows No voltage at socket

No voltage at power on unit Check entrance fuse Xn

Reset button error (LED in Check connections of reset button, change reset button,
power on unit) change reset button cabling

3 Press start button

4 Components are supplied

with power

5 Monitors switch on Monitors stay black Check if FL-C boots

Check power/video plugs

Check voltage on monitors

Check if hardware switch on monitors is switched on

If you have a video manager system, check the video

manager and its licensing

6 FL-C boots FL-C does not boot FL-C PC is not switched on if LED bar and start button on
the front of the PC are not illuminated

Press reset button

Check reset button & cabling

Check if UPS is switched on

Check plugs of UPS and FL-C PC

Check Plugs of Monitors

Check the cabling, is the control panel supplied with 24

V (± 20%)? Are all fuses on system

7 TCP boots Stays black OK? If so, the control panel must be replaced

Hangs at 20% File system error at TCP → replace TCP

Hangs at 60% Check cabling → if OK, then replace TCP

Hangs at 80% and 90% Check the cabling and if the XCU is online (you can use
the platform status information page)

Cios | Troubleshooting Guide – Restricted – Page 43 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
10 Switch-on sequence, power-on unit

10.2 Power-on unit

Switch-on (Normal mode)

• When the power connector is plugged in, LEDs D23, D24, and D32 light up.

• Immediately after power is switched on, LEDs D20 and D27 light up.

• Approx. 1 or 2 sec. after switching on power, the D16 LED goes on, followed immediately by the D20 LED.
Switch-off

• When the power goes off, LEDs D20 and D27 go off immediately.

• The D16 switches off as soon the PC shuts down.

• Shortly after the D16 switches off, the D14 goes off.

• When the D16 switches off, the red D22 LED lights up for 8 seconds.

• When the power connector is unplugged, LEDs D23, D24, and D32 go off.

If the system is switched on again while the red D22 LED is still on, then the D16 and D20 LEDs light up after
the D22 LED goes off.

Power on unit D55, description of LEDs

LED Color Description

D14 green Power supply, UPS circuit

D16 green .Indicates that the UPS output voltage (230 V) is switched through to the components.

D20 green +3.3 V (UPS). Goes on when the UPS output voltage (230 V) is present on the D55
board. An electronic fuse is used for the voltage.

D21 green PC1 on. Indicates that the FL-C is connected to D55.X14 and is switched on.

D22 red Blocks the PC from switching back on. Goes on approx. 8 sec. (16 sec.) after the end
of shutdown.

D23 green +24 V. Goes on when the line power voltage is present on the power on unit.

D24 green +3.3 V. Goes on when the line power voltage is present on the power on unit.

D27 green Site on. Goes on when the status of the system is "on" (same as the LED in the trolley
power off switch).

D32 green +15 V. Goes on when the line power voltage is present on the power on unit.

D51 green PC2 on. Indicates that an optional PC is connected to D55.X17 and is switched on.

Page 44 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 10 Switch-on sequence, power-on unit

Fig. 20: Power on D55

Description of errors

Possible Cause(s)

D23 and D32 do not light - Line power input voltage is missing.
up
- F1 and/or F2 fuses on D56 defective. - F4 fuse on the D55 defective.

D24 does not light up - Line power input voltage is missing.

- F1 and/or F2 fuses on D56 defective. - F10 fuse on the D55 defective.

D20 does not light up - The UPS output voltage not present.
- Connector for the output of the UPS not plugged in.

D21 does not light up - Connector on D55.X14 not plugged in.

- Cable to D55.X14 on the FL-C not plugged in.

D51 does not light up - Connector on D55.X17 not plugged in.

- Cable to D55.X17 from an optional PC not plugged in on the PC

D22 is lit continuously - Reset switch on D55.X12 not connected.

- Wiring of the reset switch in the trolley defective.

D16 does not light up - Line power input voltage is missing.

- F1 and/or F2 fuses on D56 defective. - F10 fuse on the D55 defective.

The yellow warning lamp -The UPS input voltage is missing.

with the battery symbol on
- Connector for the input of the UPS not plugged in. -F8 fuse on the D55
the UPS goes on when
defective.
power is switched on and
an audible signal sounds.

Generator power supply - F5 fuse on the D55 defective.

missing.

Main unit power supply - F6 fuse on the D55 defective.

missing.

Cios | Troubleshooting Guide – Restricted – Page 45 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
10 Switch-on sequence, power-on unit

Possible Cause(s)

Power supply for the com‐ - F7 fuse on the D55 defective.

ponents in the trolley miss‐
ing.

Page 46 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 11 Event log; File and Image Tools; Reports

11 Event log; File and Image Tools; Reports

11.1 Log files

Make sure always to provide time stamp information for the error and customer workflow whenever logfiles
are requested by RSC or HSC.

Location of the most relevant logfiles:

• C:\FLC\FLCompact\Log

– C:\FLC\FLCompact\Log\IC

– C:\FLC\FLCompact\Log\IC\backup

• C:\FLC\FLCompact\CrashDumps

• C:\FLC\FLCompact\Log_FlightRecorder (see note below)

• Customer PEX_DB

• DICOM images in private format, which shows the actual problem

From VA20 onwards the “Log_FlightRecorder” is activated by default.

• Activation from user menu: “ALT + M”, deactivation is also “Alt + M” (confirmation window “enable/
disable XCS monitor” appears)

• Activation in Service mode: FL-C Service > Configuration > Log Level Configuration > set check box
“Flight Recorder Log Support”

FD calibration data:

• Perform a “Backup” or an “FD Backup” and export to USB stick or other device.

11.2 Export the log files to the USB device by right-clicking the (i)-button.

Fig. 21: i-button

Cios | Troubleshooting Guide – Restricted – Page 47 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
11 Event log; File and Image Tools; Reports

Fig. 22: USB_Savelogs

If “Store current logs to USB” is selected, the logs will be saved directly to the USB device; otherwise, the
logs will be sent to the “Transfer” folder and forwarded to the factory as soon as a LAN or WiFi connection
is available.

Savelog content

• FLCompact.log

• FlightRecorder.log

• IC logs

• PMS (System.caf + Reports)

• Reports (DFR, DICOM, HCC, MedHome, service, sysmgmt)

• SHARE (FDsens.aaf)

11.3 Export logfiles or “Service Images” with “File and Image Tools”:
Export logfiles

The selected files will be compressed to a ZIP file and can be transferred via RDIAG or stored to a local device.

Page 48 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 11 Event log; File and Image Tools; Reports

Service > FL-C Service > File and Image Tools > Log & Config Files > File Type “Logs”

• FLCompact application

– FlCompact.log

– FlcDicom.log

– FlcMerge.log

– FlcGear.log

– FlcSSW.log

• VDM

• Flight Recorder Continuous

• MNP

• Crush dumps

• Firewall

• Event Viewer

• TeamViewer

• Web server

• FD-specific logs

• AppHost_Imaging_System_Logs

• AppHost_Vendor_System_Logs

11.4 Service images, SRS transfer

• FL-C in user mode: Select and open a patient from the patient list.

• Press the key combination “Ctrl + t” on the TUI.

>> A message box asks you to “Export to Service Study”

• Select the relevant image(s) with a mouse click.

>> A square marker is shown in the selected image frame(s).

• Click “OK” to export the selected images to the service patient folder.

• Close the patient and log into the service application, click FL-C Service > File & Image Tools

• For “Destination” select RDIAG or CD/DVD (USB device must already be plugged-in to be indicated).

• Click the “Update Selection” button to refresh the “Image File Selection” content.

• Click “Service Images” and select the relevant image(s) with a mouse click. Multiple selections are possible
while keeping "Ctrl” pressed.

• Click “ Save”.

>> In parallel with the raw image, the image file is converted to DICOM format, with both being in an
anonymized format.

Cios | Troubleshooting Guide – Restricted – Page 49 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
11 Event log; File and Image Tools; Reports

Alternatively, you can select the “service images” also directly in service mode by using the “Exam/Service”
toggle button on the FL-C UI.

11.5 Acsos.NT trace tool

The Acsos.NT trace is only needed if requested from RSC or HSC.

Generally the error must be reproducible.

Handling of Acsos.NT trace tool

• Open the service application.

>> the Windows Start button appears.

• Click the Start button and open Windows Explorer.

• Enter the following folder:

>> C:\FLC\Addon\Acsos.NT

• Double-click "AcsosNT.exe"
>> The Acsos trace application window opens.

• The Acsos trace can be started and stopped under the "Record" tab card.

• Under the tab card "File" the current Acsos trace can be stored to a hard drive or USB device.

Workflow for Acsos.NT trace tool usage

• Start the Acsos trace and close the service application.

• Reproduce the error.

• Start Service, stop the Acsos trace and store the file.

11.6 Event log, File & Image Tools

11.6.1 Function Description

The FLUOROSPOT Compact is the central storage point for the system logs.

The event log menu allows importing, viewing, filtering, and exporting of these logs.

When the error message is underlined on the screen, it is possible to obtain more information by clicking it.

Page 50 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 11 Event log; File and Image Tools; Reports

Fig. 23: Event Explorer

Fig. 24: Additional event information pop-up window

11.6.2 Opening the event log

1. Enter the service mode.

2. Click the event log tab card.

Fig. 25: Service main page

1 Event log tab card

11.6.3 Handling the event log

When the error message is underlined on the screen, it is possible to obtain more information by clicking it.

Cios | Troubleshooting Guide – Restricted – Page 51 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
11 Event log; File and Image Tools; Reports

11.6.3.1 EventLog viewer

Three tab cards are displayed in the EventLog Viewer:

• Filter Mode

• Pattern Mode

• Pattern Messages

Mainly the Filter Mode is used for field service.

Filter mode

Using the filters

Filter Mode provides different filters that make it possible to perform a troubleshooting search. You can
combine the different filters (e.g. Time Range and APID) to perform accurate troubleshooting.

• Click the Filter Mode tab card at the top of the EventLog Viewer screen.
>> The Filter Mode screen is displayed. The event logs in the FLUOROSPOT Compact are loaded. The latest
recorded event log is displayed.

Fig. 26: Filter mode screen

Page 52 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 11 Event log; File and Image Tools; Reports

• It is possible to merge logs:

– Select multiple logs under Log Files by holding the <shift> key and left-clicking the logs.

– Click Go.
>> The merged logs are displayed.

Fig. 27: Merged logs

• Severity:

If you want to see the entire log messages, select ALL in the severity filter and click Go.

a. Select the filter to be applied:

- Error

- Recoverable

- Warning

- Information

- Action

- Telegram

- Message

- Reset

b. Click Go.

>> The actual status is displayed on the bottom left of the screen.

>> The filtered log messages are displayed.

Cios | Troubleshooting Guide – Restricted – Page 53 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
11 Event log; File and Image Tools; Reports

• Message ID:

This is the error message number, independently of the APID.

a. Select the message ID.

b. Click Go.

>> The actual status is displayed on the bottom left of the screen.

>> The filtered log messages are displayed.

• Source:

This is the APID.

a. Select the APID.

b. Click Go.
>> The actual status is displayed on the bottom left of the screen.

>> The filtered log messages are displayed.

• Message text:
This feature makes it possible to find error messages without having the ID or the APID.

a. Enter the required text.

b. Click Go.
>> The actual status is displayed on the bottom left of the screen.

>> The filtered log messages are displayed with date and time in blue on the bottom of the screen and
in bold at the top of the screen:

Fig. 28: Text search results

c. By clicking the message date and time on the bottom of the screen (displayed in blue), the corresponding
message is highlighted on the upper screen.

Page 54 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 11 Event log; File and Image Tools; Reports

• Time range:
a. Select the time range.
b. Click Go.

>> The actual status is displayed on the bottom left of the screen.

>> The filtered log messages are displayed.

Extracting the log files:

1. Click <Extract>.

>> The Extract pop-up window is displayed:

2. Select the log file extraction location by clicking Browse.

3. Select the ☑Compress checkbox to reduce the output size.

If the output location is a compressed folder (e.g. this directory has the option “compress drive to save
disk space” enabled), the “compress” option must not be selected. Otherwise, the extraction will not be
successful.

4. Click Extract.

>> The log will be extracted to the selected location.

Fig. 29: Extracting logs

11.6.3.2 Configuration of the log level in the FLUOROSPOT Compact service

The recording of the error messages depends on the configured log level.

For example, to record all errors in the event log, the log level must be set to All Events.

It is useful in case of more extensive troubleshooting.

1. Enter the service mode.

2. Go to FL-C Service > Configuration > Log Level Configuration.

3. Next to Dvp driver log level, select the log level to be recorded.

See ( Page 56, Fig. 30) [1].

Cios | Troubleshooting Guide – Restricted – Page 55 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
11 Event log; File and Image Tools; Reports

4. Click Save.

>> A new log file in which the developer level messages will be saved is generated.

Fig. 30: Log level configuration

5. Flight recorder log support is selected by default with versions VA20 and higher.

• Selected with VA20 ☑F ( Page 56, Fig. 30) (2).

11.6.3.3 Flight recorder description

The flight recorder represents an independent module that is used to log the complete AXCS telegram traffic
in the system. In addition to continuous logging of telegrams in separate log files, the current status of the
system can also be reported by certain predefined events or can be triggered by the user. These logs are stored
in separate folders.

According to the new flight recorder concept, flight recorder messages – log entries with severity "M“ – are
stored in separate flight recorder-related files and not in the application log file (FlCompact.log).
In principle, the flight recorder represents the functionality of an ACSOS trace tool. The flight recorder starts
automatically during system startup if this option was configured in FL-C Service.

Severity Type M (Monitoring): Telegram messages are logged if the flight recorder has been activated.

11.7 Reports
Export Reports

• Log-in into the service application

• At the PMS start-page click-on “Report Generation”

• Click-on the menu item “Export Reports”

• For offline medium USB or CD/DVD, connect the USB device or insert the CD/DVD into the drive.

– For USB export, insert the USB device to display a drive letter in the selection box.

– For CD/DVD export, a message appears if no medium is in the CD/DVD drive available.

• Select the export destination (USB, CD/DVD or HDD)

Page 56 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 11 Event log; File and Image Tools; Reports

• Click on “Go” to start the date export (all reports are selected as default)

• The zip file is saved under the selected location USB, CD/DVD or HDD
>> HDD export path = C:\Addon\PMS\service\reports\exported

• Select Exit to exit the screen.

Cios | Troubleshooting Guide – Restricted – Page 57 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
12 Test tools

12 Test tools
12.1 AXCS Tests
The purpose of the AXCS tests is to check the components using the AXCS communication protocol.

The tests make it possible to:

• Display the status of the components: see ( Page 58, Fig. 31) (1)

• Display the details of the components (APID): see ( Page 58, Fig. 31) (2).

• Reset some components if a malfunction occurs: see ( Page 58, Fig. 31) (3).

Fig. 31: AXCS Diagnostics

Using the AXCS tests:

1. To enter the AXCS tests:

Go to: Service > Test Tools > AXCS Test.

>> The status of the components is displayed on the screen.

>> The normal status of a component is Turn ON or Connected.

Page 58 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 12 Test tools

2. To reset a component:

• Set a checkmark ☑ (under “Reset”) for each component that needs to be reset. See ( Page 58, Fig. 31)
(3).

• Click Go.
>> The selected component is reset.
3. To view the details of a component:

• Select the corresponding ☑ checkbox.

• Click Details.

>> The result will be displayed:

Fig. 32: AXCS test details

12.2 Monitoring
See Online Help: Service -> Test Tools

Test Tools

• Main Unit Monitoring

• Controls

• Input / output

• Generator

12.3 3D visualization
See Online Help: Service -> Test Tools -> Tools

Cios | Troubleshooting Guide – Restricted – Page 59 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
12 Test tools

Fig. 33: 3D_visualization

Main functionality of the 3D analysis tool

• Load logfiles ( Page 60, Fig. 33) (1)

• Open / close 3D application ( Page 60, Fig. 33) (2)

• Speed for log scrolling ( Page 60, Fig. 33) (3)

• Selection for stopping log scrolling with “Warning” or “Error” ( Page 60, Fig. 33) (4)

• Component-specific information (Cios / Detector / Generator / User Buttons) ( Page 60, Fig. 33) (5)

• Close 3D application ( Page 60, Fig. 33) (6)

• Load system CAF file for offline use ( Page 60, Fig. 33) (7)

Page 60 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 12 Test tools

Fig. 34: 3D_View

3D view

• When the “Show/close 3D” button ( Page 60, Fig. 33) (2) is clicked, the 3D window ( Page 61, Fig. 34)
opens.

>> The customer workflow is shown with virtual animation, such as controlled motorized movements or X-
ray.

Web-based training for the 3D visualization tool is available.

The 3D visualization tool can also be used on an external PC, independently of the Cios.

In this case, the logfiles and the system CAF file of the relevant system would be needed.

12.4 Diagnostics, FD-based systems until SW VA20

See Online Help: Service > FL-C Service > Diagnostic

Cios | Troubleshooting Guide – Restricted – Page 61 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
12 Test tools

Fig. 35: FD_diagnostics

FD image diagnostics

• Select the section ( Page 62, Fig. 35) (1) of the image chain for testing.

• Click <Start> ( Page 62, Fig. 35) (2).

>> If a test image is displayed on the monitor, then the (partial) image chain test has been passed.

Page 62 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 12 Test tools

Fig. 36: Self test

Selftest CoCa / XDR board

• Select CoCa board or XDR board ( Page 63, Fig. 36) (1) for the self-test procedure.

• Click <Start> ( Page 63, Fig. 36) (2).

• Evaluate the self-test result ( Page 63, Fig. 36) (3).

• The state “PASSED” ( Page 63, Fig. 36) (4) applies for the test procedure that was just performed, not to
the test result itself.

12.5 Diagnostics, FD-based systems from SW VA30

See Online Help: Service > FL-C Service > Diagnostic > Self Test

Cios | Troubleshooting Guide – Restricted – Page 63 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
12 Test tools

Fig. 37: Self_Test

Selftest FD/ STU board

• Select “FD” or STU ( Page 63, Fig. 36) (1) for the self-test procedure.

• Click <Start> ( Page 63, Fig. 36) (2).

• Evaluate the self-test result ( Page 63, Fig. 36) (3).

• The state “PASSED” ( Page 63, Fig. 36) (4) applies for the test procedure that was just performed, not to
the test result itself.

12.6 Diagnostics, I.I.-based systems

See Online Help: Service > FL-C Service > Diagnostic

Page 64 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 12 Test tools

Fig. 38: I.I. image diagnostics

I.I. image diagnostics

• Select the section of the image chain for testing ( Page 65, Fig. 38) (1).

• Select “Test Patterns” ( Page 65, Fig. 38) (2) and “Digital” ( Page 65, Fig. 38) (3).

• Click <Start> ( Page 65, Fig. 38) (4).

>> If a test image is displayed on the monitor, then the (partial) image chain test has been passed.

The “Live Mode” and “Fluoro” image diagnostic functionalities can be used for the I.I. alignment procedure;
see “Online Help” for detailed information.

Cios | Troubleshooting Guide – Restricted – Page 65 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
13 XCU, AP-IDs

13 XCU, AP-IDs
13.1 AXCS connection

13.1.1 There are three additional ways to measure the AXCS connection.
a) TUI: “ALT press → ALT release → CTRL press → CTRL release → SHIFT press → SHIFT release → CAPS LOCK
press → CAPS LOCK release”.

The TUI then displays the node. If an Ethernet connector is disconnected, this can be seen on the TUI after 4
- 8 seconds. The list of nodes is somewhat dependent on the configuration (this is the case for many TUIs),
but otherwise, you see the generator interface, MCU, XCU, DAP interface, collimator interface and the FL-C.
You can also see the video manager interface, the other TUIs and the two/three remote service clients of the
TUIs.

b) The same thing works in PMS with "AXCS Tests"

c) As well as with ACSOS under "VIEW" -> "NET LIST"

(Each logical node is, however, monitored by the XCU. If a node fails and/or does not connect, the XCU writes
error number "7" to the log. You can search for these errors in a targeted manner in the error log, i.e. you can
search for error "7". Error 7 suggests that the SW on this node is not working correctly, because e.g. the
configuration is incorrect, the SW has not been loaded, or the HW/connection is defective.)

13.1.2 AP-IDs hex / dec:

0x10 / 16 FL-C (FD-CoCa)

0x20 / 32 Main Control Unit (MCU)

0x21 / 33 Collimator Control Unit (CCU)

0x22 / 34 Operating Control Unit (OCU)

0x23 / 35 Cassette System (CAS) (Cios Connect)

0x24 / 36 Button-Based Control Console (Cios Connect)

0x28 / 40 DAP meter

0x48 / 72 OpenApps

0x50 / 80 Generator

0x5A / 90 TCP

0x5B / 91 CCP

0x5C / 92 RCP

0x5D / 93 TUI interface

0x5E / 94 MCB

0xEA / 234 Video Manager

0xEB / 235 Litho Module

0xF0 / 240 XCU

0xF3 / 243 FL-C, Fluorospot Compact Imaging System

Page 66 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 13 XCU, AP-IDs

13.1.3 “Ping” to Ethernet address via CMD shell

10.1.1.5 TUI1

10.1.1.6 TUI2

10.1.1.7 TUI3

10.1.1.24 XCU

10.1.1.25 FL-C

10.1.1.27 MCU

10.1.1.111 Video Manager

10.1.1.116 EHC

13.2 XCU, factory reset

XCU, factory reset (only possible with VA20 and higher)

• In the unexpected case of a total loss of XCU communication over Ethernet, the XCU can be set to the factory
default settings.

>> All saved parameters, calibration data, and downloaded software packages will be erased.

>> The User File System and Application Image will be reset to the factory default settings.

Fig. 39: XCU_S7

To reset the XCU back to the factory default settings, perform the following steps:

• Switch the power off and press push button S7 ( Page 67, Fig. 39) (1) inside the XCU (through the hole
next to the Ethernet activity LEDs).

• Turn on the XCU while keeping the button pressed (until the Ethernet LEDs start indicating again).

>> A download via the PMS service page is possible again.

Cios | Troubleshooting Guide – Restricted – Page 67 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
14 FLC PC Troubleshooting

14 FLC PC Troubleshooting
14.1 DIFS Tool and HDD Defragmentation
Troubleshooting instructions are given in the Replacement of Parts document for the specific PC.

>> Navigate to: CB-Doc > Repair > System: Replacement Instructions > XXX PC

for “XXX PC,” substitute your PC model and SW version:

• Celsius W530 PC with VA20 (XPR2-000.841.10.XX.02)

• Fujitsu W520 PC (AX41-060.841.18.XX.02)

• Celsius W550 PC with VA20 (XPR2-000.841.11.XX.02)

• Celsius W550 PC with VA30 (AXS4-000.841.01.XX.02)

Page 68 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 15 MCU; MCU_Ext.; D142; CAN I/O

15 MCU; MCU_Ext.; D142; CAN I/O

15.1 MCU, 7-segment display

15.1.1 7-segment display explanation

Possible states of the 7-segment display:

• Dark

• Slow rotation of arrow counterclockwise, 1.75 seconds per revolution

• Fast rotation of arrow counterclockwise, 0.35 seconds per revolution

• Slow rotation of arrow clockwise, 1.75 seconds per revolution

• Fast rotation of arrow clockwise, 0.35 seconds per revolution

• Arrow rotation stopped

V314 V313 Speed Description

Dark Dark n.a. - boot up sequence

- no readout for about 15 seconds in boot sequence

Dark Rotates right Slowly, 1.75s - boot image active

- if no display after 15 seconds
–> no or different boot image is installed
–> or MCU is defective

Dark Rotates right Fast, 0.35s - boot image active

- connected to XCU
- no standby
- download possible

Dark Stopped n.a. - work image active

- download triggered
- if download is not triggered -> MCU error

Rotates right Rotates right Slowly, 1.75s - work image active

- connection to XCU down
- no standby
- download not possible

Rotates right Rotates right Fast, 0.35s - work image active

- connected to XCU
- standby
- download possible

Cios | Troubleshooting Guide – Restricted – Page 69 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
15 MCU; MCU_Ext.; D142; CAN I/O

V314 V313 Speed Description

Stopped Stopped n.a. - work image active

- download triggered
- if download is not triggered > MCU error

Dark Rotates left n.a. / fast, 0.35s - work image active

- S2 is pressed or MCU is defective

Tab. 1: Meanings of 7-segment displays in combination

Page 70 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 15 MCU; MCU_Ext.; D142; CAN I/O

15.2 MCU, ext., schematic (example Cios Alpha)

Fig. 40: MCUExt

Cios | Troubleshooting Guide – Restricted – Page 71 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
15 MCU; MCU_Ext.; D142; CAN I/O

15.3 MCU, factory reset

MCU, factory reset (only possible with VA20 and higher)

• In the unexpected case of a total loss of MCU communication over Ethernet, the MCU can be set to the
factory default settings.

>> All saved parameters, calibration data, and downloaded software packages will be erased.

>> The User File System and Application Image will be reset completely to the factory default settings.

To reset the MCU back to the factory default settings, perform the following steps:

• Switch the power off and press push button S2 inside the MCU (through the hole next to the Ethernet activity
LEDs).

• Turn on the MCU while keeping the button pressed (until the Ethernet LEDs or the 7-segment display starts
indicating again).

>> If one of the 7-segment displays shows a "right rotating" pattern, then the factory default procedure was
successful.

>> An application download via the PMS service page is possible again.

>> If there is a "left rotating" pattern, then the S2 switch has a defect - the MCU will need to be replaced.

15.4 MCU, fuses and troubleshooting

With MCU_HS (from SW VA20), several fuses in the MCU can be replaced if the housing of the MCU has been
opened. Refer to the “Replacement of Parts” document, “Fuses” chapter.

The following Cios Spin/Alpha MCU_HS_FI fuses can be replaced:

• F1, 250 mAT; emergency stop circuit.

>> In the case of an F1 defect, the emergency stop circuit has no voltage supply.

• F2; 3 AT; power supply

>> In the case of an F2 defect, the 24 V power supply (input) is interrupted –> no MCU functionality because
the microcontroller and FPGA have no power supply.

• F3; 250 mAT; foot switch

>> In the case of an F3 defect, the foot switch is not operational.

• F4; 250 mAT; wireless foot switch (future)

>> In the case of an F4 defect, the power supply for the wireless foot switch (future) and litho connector is
not available.

• F7; 3 AT; power supply

>> In the case of an F7 defect, the monitoring read-out of the hand switch/foot switch, emergency stop,
end switches, trap nut, and squeeze switches is not available.

• F10; 250 mAT; hand switch

>> In the case of an F10 defect, the hand switch is not operational.

Page 72 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 15 MCU; MCU_Ext.; D142; CAN I/O

The following Cios Fusion/Connect MCU_HS_EP fuses can be replaced:

• F2; 3 AT; power supply

>> In the case of an F2 defect, the 24 V power supply (input) is interrupted –> no MCU functionality because
the microcontroller and FPGA have no power supply.

• F3; 250 mAT; foot switch

>> In the case of an F3 defect, the foot switch is not operational.

• F4; 250 mAT; emergency stop circuit

>> In the case of an F4 defect, the emergency stop circuit has no voltage supply.

• F5; 250 mAT, foot switch wireless (future)

>> In the case of an F5 defect, the power supply for the wireless foot switch (future) and litho connector is
not available.

• F6; 3 AT; power supply

>> In the case of an F6 defect, the monitoring read-out of the hand switch/foot switch, emergency stop,
end switches, trap nut, and squeeze switches is not available.

• F10; 250 mAT; hand switch

>> In the case of an F10 defect, the hand switch is not operational.

The condition of the following functions can be read out with the monitoring functionality (Service/
Tests/Monitoring):

• MCU fuse for end SW trap squeeze

>> Check also connector X152 pin 2 or X151 A1/A2/A3/A4 for short circuit

• MCU fuse 24 V; ext. components 24 V

>> MCU software is not running (monitoring not available)

• MCU fuse 24 V; CAN 1

>> It is a current limitation and not a fuse (monitoring not available)

• Hand switch fuse (MCU fuse)

>> Check also connector X9 pin A1 for short circuit

• Foot switch 1 fuse (MCU fuse) (basic, extended)

>> Also check connector X101 pin A1 for short circuit

• Foot switch 2 fuse (MCU fuse) (litho connector)

>> Check also connector X102 pin A1 for short circuit

• CAN I/O fuse (note, this is independent of the MCU)

>> For the power supply of the FD user interface (only Cios Spin/Alpha)

>> There is no error message.

>> If the FD user interface is not working, check it via monitoring for input/output “CAN I/O fuse” and also
check if the 24 V power at X3 pin B6 of CanIo or CanIo_V3 is available.

>> Check the CAN bus wiring. See wiring diagram or ( Page 78 CAN bus wiring).

Cios | Troubleshooting Guide – Restricted – Page 73 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
15 MCU; MCU_Ext.; D142; CAN I/O

Topic Fuse MCU Fuse MCU Monitoring Message (event log) Remark
HS_FI HS_EP

Emergency F1 F4 n.a. 032_2093 User tried to move the The message also
stop circuit C-arm although the emergency appears if the emer‐
stop is active gency stop is not active

Power supply F2 F2 n.a. 240_6100 No response from MCU software is not

MCU running (monitoring
not available)

Foot switch F3 F3 Foot switch 1 034_1721 X-ray foot release Also check connector
fuse switch: power failure (blown X101 pin A1 for short
fuse) circuit

Foot switch F4 F5 Foot switch 2 034_1723 X-ray litho release Check also connector
wireless fuse switch: power failure (blown X102 pin A1 for short
fuse) circuit
034_1721 X-ray foot release
switch: power failure (blown
fuse)

Power supply F7 F6 MCU fuse 240_6100 No response from MCU software is not
ext. 24V; ext. MCU running (monitoring
components not available)

Hand switch F10 F10 Hand switch 034_1720 X-ray hand release Check also connector
fuse switch: Power failure (blown X9 pin A1 for short cir‐
fuse) cuit

I.I magnifica‐ n.a. F1 n.a. No message available Check connector X7 pin

tion switch 1 or 2 for the correct
I.I. mag. switching doesn’t work
(connect) level and also for short
circuit

Short circuit n.a. n.a. Main unit Fusion/Connect, during start-up Monitoring for main
24V_CAN1 "MCU fuse and operation: unit "MCU fuse 24V;
X61 pin 9 24V; CAN 1" CAN 1" is not available.
040_1003 DAP is not respond‐
ing. If an error occurs while
the system is being
Spin/Alpha, during start-up:
used, it will not be pos‐
032_2090 Failure in emerg. stop sible to continue work‐
circuit of motor power supply - ing.
no mot. move possible
–> Check the CAN bus
032_2095 Emergency stop test wiring. See wiring dia‐
failed gram or
( Page 78 CAN bus
Spin/Alpha (motorized), during wiring).
operation:
032_2014 CAN connection to
angular drive failed
032_2012 CAN connection to
orbital drive failed
032_2010 CAN connection to
vertical drive failed

Page 74 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 15 MCU; MCU_Ext.; D142; CAN I/O

Topic Fuse MCU Fuse MCU Monitoring Message (event log) Remark
HS_FI HS_EP

Fuse for end- n.a. n.a. Main unit 032_2043 Trap nut for lifting Monitoring for main
sw trap "MCU fuse for device (Fangmutter) activated unit "MCU fuse for end-
squeeze end-sw trap sw trap squeeze”. Also
squeeze" check connector X152
pin 2 or X151
A1/A2/A3/A4" for short
circuit

Internal power n.a. n.a. Main unit 032_2098 24V power-down sig‐ Monitoring for main
failure signal “internal nal missing unit “internal power fail‐
power failure ure signal"
signal"

Tab. 2: Troubleshooting

15.5 D142, LED status

15.5.1 D142 LED status explanation (vertical movement)

LED name Color Description (LED = on)

+24V green + 24V OK

+ 5V green Internal + 5V OK

CCP_REQMOV yellow Button at CCP for up/down vertical movement pressed

RCP_REQMOV yellow Button at RCP for up/down vertical movement pressed

RCP_EME1 red Emergency stop is pressed (channel 1)

RCP_EME2 red Emergency stop is pressed (channel 2)

UPPER_ENDSW red MCU reports that the upper end switch or the trap nut switch is pressed

LOWER_ENDSW red MCU reports that the lower end switch or the trap nut switch is pressed

MOVEUP blue MCU sends an upward movement command to D142

MOVEDOWN yellow On = MCU sends a downward movement command to D142

MV_EN green Movement is enabled, emergency stop is not pressed, and a movement
command is requested from a user interface

MV_UP blue Conditions for upward movement:

• Upward movement request from user interface
• End switch or trap nut switch not pressed
• MCU sends an upward movement command to D142

Cios | Troubleshooting Guide – Restricted – Page 75 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
15 MCU; MCU_Ext.; D142; CAN I/O

LED name Color Description (LED = on)

MV_DWN red Conditions for downward movement:

• Downward movement request from user interface
• End switch or trap nut switch not pressed
• MCU sends a downward movement command to D142

Tab. 3: Meanings, LED D142

Page 76 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 16 Radiation triggering

16 Radiation triggering
16.1 Radiation triggering

16.1.1 Requirements regarding radiation triggering

Before radiation can be triggered, the following requirements must be met:

• A patient, at least an emergency patient, must be created.

• An organ program must be selected.

• Sufficient hard disk space must be available for data acquisition.

• The Ready state must be signaled by a green bar in the upper left corner of the TUI screens.

• The generator must be ready for exposure:

– The 7-segment D80 display:

for Connect, Fusion: 3 and 6

for Alpha, Alpha VA30, Spin, Flow: 4 and 6 (during charging/discharging the value can also drop to 3 and
6.

• The 20 mA loop must be closed - to do so, press the radiation triggering button with the hand switch or
foot switch.

• Foot switch or hand switch pressed.

• The displays must show no errors.

• The tube must not be too hot (< 98% HU for anode, < 65˚C for housing).

• ESU (if applicable) must be loaded over the minimum threshold

• C-arm and matching trolley are connected

• System is below maximum skin dose and maximum fluoro time or the warning(s) have been confirmed

Cios | Troubleshooting Guide – Restricted – Page 77 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
17 CAN bus

17 CAN bus
17.1 CAN bus wiring

Monitoring for input/output “CAN I/O fuse” (Cios Alpha)

In the case of a failure, there is no error message.

If the FD user interface is not working, check it via monitoring for input/output "CAN I/O fuse" and also check
that the 24V power at X3 pin B6 is available.

CAN bus, Cios Alpha

Fig. 41: CAN bus, Cios Alpha

Page 78 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 17 CAN bus

CAN bus, Cios Connect

Fig. 42: CAN_Connect

CAN bus, Cios Fusion

Fig. 43: CAN bus, Cios Fusion

Cios | Troubleshooting Guide – Restricted – Page 79 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
18 Remote Update Handling (RUH)

18 Remote Update Handling (RUH)

18.1 Update installation failed - system is blocked

If for any reason the unlock procedure in chapter 18.1 does not work, perform the work steps in chapter
18.2, "Fallback solution."

Update installation failed - system is blocked

1. Rollback failed:

• If the rollback was not successful, a corresponding screen is displayed. The system is blocked and the
customer can’t operate the system.
2. Since the system is blocked, there is no chance to log on to local service.

The remedy is:

• Connect a USB keyboard to the trolley USB port.

• Switch on the system and press F12 on the USB keyboard.

• A pop-up prompting the user to enter the password appears. Enter the BIOS password and confirm with
the <ENTER> key.

>> The boot device menu appears.

• Select P1 and confirm with the <ENTER> key.

• Select Restore ( Page 80, Fig. 44) (1) and confirm by clicking <OK> ( Page 80, Fig. 44) (3).

Fig. 44: COBR menu

Page 80 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 18 Remote Update Handling (RUH)

• The source menu window then appears. Select SERVICE_PARTITION ( Page 81, Fig. 45) (1) and
confirm by clicking <OK> ( Page 81, Fig. 45) (2).

Fig. 45: Source menu

• A pop-up menu window appears. Select the latest established recovery image (the backup with the
latest time stamp (YYYYMMDD_HHMMSS) in the file name) ( Page 81, Fig. 46) (1) and confirm by
clicking <OK> ( Page 81, Fig. 46) (2).

The name of an “RUH” backup, created by the system, always includes the software version, e.g.,
BACKUP_20181018_100339–VA30B.1805....

A manually created backup can be identified, because it does not include the software version.

Manually created backups cannot be used, because they don't include the necessary “unlock file”.

Fig. 46: Backup window

Cios | Troubleshooting Guide – Restricted – Page 81 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
18 Remote Update Handling (RUH)

• A pop-up window appears. Restore is finished. Confirm by clicking <OK> ( Page 82, Fig. 47) (1).

Fig. 47: Restore finished

• The COBR menu will be displayed. Select Exit ( Page 80, Fig. 44) (2) and confirm by clicking <OK>
( Page 80, Fig. 44) (3).

• Switch on the system.

• Once the system is ready to use, please collect the necessary log files for troubleshooting.

• Open the SSW.

• Select <FL-C Service>-<System>

• Click <Explorer>

• Navigate to Service Z:\UpdateInstallationLogs\

• Copy the folder UpdateInstallationLogs to USB stick and send it for troubleshooting to the RSC/HSC.

• Only perform the steps in the “Fallback solution” chapter if this procedure doesn’t unlock the system
( Page 82 “Fallback solution” if update installation failed and system is blocked).

18.2 “Fallback solution” if update installation failed and system is blocked

Update installation failed - system is blocked
1. Rollback failed:

• If the rollback was not successful, a corresponding screen is displayed. The system is blocked and the
customer can’t operate the system.

Page 82 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 18 Remote Update Handling (RUH)

2. Since the system is blocked, there is no chance to log on to local service.

The remedy is:

• Connect a USB keyboard to the trolley USB port.

• Switch on the system and press F12 on the USB keyboard.

• A pop-up prompting the user to enter the password appears. Enter the BIOS password and confirm with
the <ENTER> key.

>> The boot device menu appears.

• Select P1 and confirm with the <ENTER> key.

• Click the cmd window with the information …Use menu to select function…

• Press Ctrl + C at the same time (on the keyboard)

>> Terminate batch job (Y/N) will be shown.

• Press Y and confirm with the <ENTER> key.

>> X:\windows\system32> will be shown.

• Write cd.. and press the <ENTER> key twice.

>> X:\> will be shown.

• Type X:\ >notepad and press the <ENTER> key

• A Notepad window will open

Fig. 48: Notepad

• Click File ( Page 83, Fig. 48) (1) and Open.

• Change “Files of Type” to All Files ( Page 83, Fig. 48) (2).

• Change “Look in” from Boot (X:) to Service (D:) ( Page 83, Fig. 48) (3).

• Open the folder “RUH_important_do_not_touch” ( Page 83, Fig. 48) (4) and delete the contents (right-
click > and delete).

• Type X:\ >exit in the cmd window and press the <ENTER> key or switch off the system.

• Switch on the system and press F12 on the USB keyboard.

Cios | Troubleshooting Guide – Restricted – Page 83 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
18 Remote Update Handling (RUH)

• A pop-up prompting the user to enter the password appears. Enter the password tcapmoc and confirm
with the <ENTER> key.

>> The boot device menu appears.

• Select P1 and confirm with the <ENTER> key.

• Select Restore ( Page 80, Fig. 44) (1) and confirm with <OK> ( Page 80, Fig. 44) (3).

Fig. 49: COBR menu

• The source menu window then appears. Select SERVICE_PARTITION ( Page 81, Fig. 45) (1) and confirm
with <OK> ( Page 81, Fig. 45) (2).

Fig. 50: Source menu

Page 84 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 18 Remote Update Handling (RUH)

• A pop-up menu window appears. Select the latest established recovery image (backup with the latest
timestamp (YYYYMMDD_HHMMSS) in the file name) ( Page 81, Fig. 46) (1) and confirm with <OK>
( Page 81, Fig. 46) (2).

The name of an “RUH” backup, created by the system, always includes the software version, e.g.,
BACKUP_20181018_100339–VA30B.1805....

A manually created backup can be identified, because it does not include the software version.

Manually created backups cannot be used, because they don't include the necessary “unlock file”.

Fig. 51: Backup window

• A pop-up window appears. Restore is finished. Confirm with <OK> ( Page 82, Fig. 47) (1).

Fig. 52: Restore finished

• The COBR menu will be displayed. Select Exit ( Page 84, Fig. 49) (2) and confirm with <OK>
( Page 84, Fig. 49) (3).

• Switch on the system.

• Once the system is ready to use, please collect the necessary log files for troubleshooting.

• Start the SSW.

• Select <FL-C Service>-<System>

• Click <Explorer>

Cios | Troubleshooting Guide – Restricted – Page 85 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
18 Remote Update Handling (RUH)

• Navigate to Service Z:\UpdateInstallationLogs\

• Copy the folder UpdateInstallationLogs to USB Memory stick, and send it for troubleshooting to the
RSC/HSC.

Page 86 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 19 AX DICOM Tool

19 AX DICOM Tool
19.1 AX DICOM tool, anonymization process

When sending an RDSR report, ensure that all sensitive patient data are anonymized.

Work steps:

• Open the link below on Internet Explorer:

>> https://intranet.for.healthineers.siemens.com/wll/0009/en/AT-RD/Tools-Reference-Page/Pages/
TRP-AX-DICOM-Tools.aspx

• Click the folder link and wait for the folder to open:

Fig. 53: AX_DICOM_Tool_00

• Copy the entire folder and save it to your local drive.

• Once the folder is saved, open AX_DICOM_Dump.exe to view the AX DICOM tool.

Cios | Troubleshooting Guide – Restricted – Page 87 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
19 AX DICOM Tool

Fig. 54: AX_DICOM_Tool_01

• Select the folder containing the RDSR report by clicking on the correct directory and providing the path of
the saved RDSR report. The selected report appears in the dialog box below.

Page 88 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 19 AX DICOM Tool

Fig. 55: AX_DICOM_Tool_02

• Select the file and select the Anonymize tab. In the profile select “Other Ima – Clear All” and click on the
Anonymize button.

Cios | Troubleshooting Guide – Restricted – Page 89 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
19 AX DICOM Tool

Fig. 56: AX_DICOM_Tool_03

• The file in the stored location will be anonymized.

Page 90 of 92 – Restricted – System | Troubleshooting Instructions

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
 20 Changes to previous version

20 Changes to previous version

Chapter 2.1.9 Chapter added: “Images for left and right monitors are swapped (VA20 only).”

Chapter 2.1.10 Chapter added: “Images for left and right monitors are swapped (VA30 only).”

Chapter 14 Chapter "FLC PC Troubleshooting" added.

Cios | Troubleshooting Guide – Restricted – Page 91 of 92

Print No. XPR2-400.840.01.13.02, Revision date: 02.23
All documents may only be used by authorized personnel for rendering
services on Siemens Healthcare Products. Any document in electronic
form may be printed once. Copy and distribution of electronic
documents and hard copies is prohibited. Offenders will be liable for
damages. All other rights are reserved.

siemens-healthineers.com

Siemens Healthineers Headquarters

Siemens Healthcare GmbH
Henkestr. 127
91052 Erlangen
Germany
Telephone: +49 9131 84-0
siemens-healthineers.com

Print No. XPR2-400.840.01.13.02 / Replaces: XPR2-400.840.01.12.02

Date of first issue: 2020 / Revision date: 02.23 / © Siemens Healthineers