100% found this document useful (1 vote)
800 views46 pages

XP00-000 840 04 01 02

Uploaded by

bashir3047
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
100% found this document useful (1 vote)
800 views46 pages

XP00-000 840 04 01 02

Uploaded by

bashir3047
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 46

ARCADIS

Troubleshooting Guide
System
Imaging System (ASPIA)
2 Document Version / Disclaimer / Copyright

Document Version
Siemens reserves the right to change its products and services at any time.
In addition, manuals are subject to change without notice. The hardcopy documents cor‐
respond to the version at the time of system delivery and/or printout. Versions to hard‐
copy documentation are not automatically distributed.
Please contact your local Siemens office to order a current version or refer to our website
http://www.healthcare.siemens.com.

Disclaimer
Siemens provides this documentation “as is” without the assumption of any liability under
any theory of law.
The content described herein shall be used by qualified personnel who are employed by
Siemens or one of its affiliates or who are otherwise authorized by Siemens or its affiliates
to use such documents.
Assemblers and other persons who are not employed by or otherwise directly affiliated
with or authorized by Siemens or one of its affiliates are not entitled to use this documen‐
tation without prior written authority.

Copyright
“© Siemens, 2014” refers to the copyright of a Siemens entity such as:
Siemens Healthcare GmbH - Germany
Siemens Aktiengesellschaft - Germany
Siemens Shenzhen Magnetic Resonance Ltd. - China
Siemens Shanghai Medical Equipment Ltd. - China
Siemens Healthcare Private Ltd. - India
Siemens Medical Solutions USA Inc. - USA
Siemens Healthcare Diagnostics Inc. - USA and/or
Siemens Healthcare Diagnostics Products GmbH - Germany

ARCADIS XP00-000.840.04.01.02 Page 2 of 46 © Siemens, 2014


03.14 CS PS SP Restricted
Table of Contents 3

1 General Information 4

1.1 Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4


1.2 Product Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3 Purpose of this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.4 Scope of this document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.5 Definitions and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.5.1 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.5.2 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.6 Required Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2 Error Diagnostics 14

2.1 Notes regarding Error Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14


2.1.1 Display of Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.1.2 Error Message Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.1.3 Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.1.4 Log Files Service Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.1.5 Note regarding consequential errors . . . . . . . . . . . . . . . . . . . . . . 17
2.1.6 Display of multiple error messages . . . . . . . . . . . . . . . . . . . . . . . . 18
2.2 Host - Imaging PC Communication Error Diagnosis . . . . . . . . . . . . . . . . . . . 19
2.2.1 Error messages only appear on the base unit treatment panel . . 19
2.3 Imaging PC (ASPIA) Error Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.3.1 Reading the BIOS Log Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.3.2 BIOS Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.4 Windows XP Operating System Error Messages . . . . . . . . . . . . . . . . . . . . . . 25
2.4.1 The task cards are only displayed on one monitor.. . . . . . . . . . . . 25
2.4.2 Imaging PC starts with Error Messages, Minidump Files have 26
ben Created . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5 Imaging PC Software (ASPIA) Error Messages . . . . . . . . . . . . . . . . . . . . . . . . 30
2.5.1 Sporadic ASP_BIC_E_10103 error messages . . . . . . . . . . . . . . . . . 30
2.5.2 Sporadic ASP_BIC_W_10104 and ASP_BIC_E_10106 error mes‐ 31
sages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5.3 Sporadic ASP_BIC_E_10105 error message. . . . . . . . . . . . . . . . . . 33
2.5.4 Investigate other Sporadic Error Messages by Error Pattern . . . . . 35

3 Tools 38

3.1 Tools for Error Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38


3.1.1 BIOS Log Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.1.2 Log Viewer in ASPIA (Imaging PC). . . . . . . . . . . . . . . . . . . . . . . . . 40

4 Changes to previous version 44

5 List of Hazard IDs 45

© Siemens, 2014 XP00-000.840.04.01.02 Page 3 of 46 ARCADIS


Restricted 03.14 CS PS SP
4 1 General Information

1.1 Safety Information


Follow the general safety information and the product-specific safety information found
in the system Startup and Replacement of Parts instructions, See the CB-Doc for the sys‐
tem.

ARCADIS XP00-000.840.04.01.02 Page 4 of 46 © Siemens, 2014


03.14 CS PS SP Restricted
General Information 1 5

1.2 Product Information


The ARCADIS family comprises three different C-arm systems:
n ARCADIS Varic
 A mobile, multi-functional C-arm for universal use.
n ARCADIS Orbic
 An isocentric mobile C-arm with optional 3D imaging.
n ARCADIS Avantic
 A multi-functional C-arm for a broad application spectrum..
AN ARCADIS system comprises a monitor trolley and a base unit (C-arm), connected to
one another by means of the monitor cable.

Fig. 1: Base unit (Host) Fig. 2: ARCADIS monitor trolley

These two units are divided into the following components:


Tab. 1 Overview of Components

Base unit (Host) Monitor trolley


1 Single tank 1 Monitor trolley (mechanics)
2 I.I. TV unit 2 Imaging system PC (ASPIA PC)
3 C-arm 3 TFT monitors
4 C-arm bearing 4 Keyboard and mouse
5 Horizontal unit 5 UPS (uninterruptible power supply)
6 Lifting column 5 ON/OFF assembly
7 Mobile frame
8 C-arm cable

© Siemens, 2014 XP00-000.840.04.01.02 Page 5 of 46 ARCADIS


Restricted 03.14 CS PS SP
6 1 General Information

Base unit (Host) Monitor trolley


9 Treatment panel
10 Electronics box

An overview of system assemblies is also available in the respective circuit diagram.


 See the CB-Doc for the system.
Appropriate error messages are displayed on the treatment panel (base unit) and/or mon‐
itor (trolley) should there be a component failure or malfunction. The error messages en‐
able you to identify the affected components and the cause of the error.
Successful troubleshooting includes the determination of the cause and the location.
As such, detailed system knowledge is not only required, it is a prerequisite.

ARCADIS XP00-000.840.04.01.02 Page 6 of 46 © Siemens, 2014


03.14 CS PS SP Restricted
General Information 1 7

1.3 Purpose of this Document


This document serves as a troubleshooting guideline for the ARCADIS systems, and pri‐
marily describes error diagnostics for the imaging chain (Gigalink camera and Imaging
PC).
It presents the procedures for identifying the cause of the failure.
Error diagnostics are based on system error messages and additional investigations.
The document does not describe system functions and in no way claims to be complete.
The document is intended for the Customer Support Engineer (CSE) trained in the instal‐
lation and maintenance of ARCADIS systems.

© Siemens, 2014 XP00-000.840.04.01.02 Page 7 of 46 ARCADIS


Restricted 03.14 CS PS SP
8 1 General Information

1.4 Scope of this document


This document is released as a manual for error diagnostics on ARCADIS systems (ARCA‐
DIS Varic, ARCADIS Orbic, ARCADIS Avantic).

ARCADIS XP00-000.840.04.01.02 Page 8 of 46 © Siemens, 2014


03.14 CS PS SP Restricted
General Information 1 9

1.5 Definitions and Abbreviations

1.5.1 Definitions

ARCADIS System The ARCADIS system has 2 components:


- C-arm
- Monitor trolley
Basic unit C-arm without monitor trolley
The main components of the C-arm are the generator
and single tank with tube assembly collimator, the X-ray
image intensifier with digital camera and TV iris dia‐
phragm, the controller (host), and the power supply units
necessary to power these components.
The C-arm cannot operate without the monitor trolley.
Electronics box Housing in the base unit where the
electronics assemblies are installed and wired.
Generator The generator consists of the controller and the power
section to generate the energy required for the X-ray
tube assembly.
With ARCADIS Avantic, the generator also includes the ro‐
tating anode starter (D115).
Single tank The single tank includes the X-ray tubes, high-voltage
generation, the transformers for the heating circuit, and
the required actual value recordings for the tube current,
high voltage, and heating current.
The ARCADIS Avantic single tank also includes the motor
drive (stator) for the X-ray tube rotating anodes.
X-ray tube assembly / tube assem‐ Single tank
bly
SIREPHOS Brand name of the single tank used in the ARCADIS Varic
and ARCADIS Orbic systems.
POWERPHOS Brand name of the single tank used in the ARCADIS Avan‐
tic system.
X-ray tube Vacuum component for generating X-radiation, built into
the ARCADIS system single tank.
Tube assembly collimator Electromechanical assembly for collimating the single
tank useful beam cone.
X-ray image intensifier (I.I.) X-ray beam receptor that converts X-rays to light and
generates an image at the I.I. output window.

© Siemens, 2014 XP00-000.840.04.01.02 Page 9 of 46 ARCADIS


Restricted 03.14 CS PS SP
10 1 General Information

Digital camera / camera Digital camera to convert the image on the I.I. output
window into digital signals, and transmission of the data
to the ASPIA PC.
TV iris / TV iris diaphragm Iris diaphragm to adapt the I.I. digital camera brightness.
Host Electrical assembly in the base unit to control unit func‐
tions.
The term Host also refers to board D1 built into the base
unit.
Monitor Trolley The line power supply (power-up circuit), Imaging PC,
and two LCD monitors are the main components of the
monitor trolley.
The monitor trolley has limited functions without the C-
arm (image postprocessing and archiving of saved pa‐
tient data).
Trolley Monitor Trolley

ASPIA Name of the ARCADIS system image postprocessing soft‐


ware, including the syngo user interface and syngo func‐
tions.
Imaging PC / ASPIA PC PC, including hardware and software for image postpro‐
cessing
ON/OFF assembly Power supply unit, including ARCADIS system power on
process controller
Live monitor Left monitor installed on the monitor trolley.
During active radiation, the current X-ray image appears
on this monitor.
Additional functions - refer to the operator manual.
Reference monitor Right monitor installed on the monitor trolley.
During active radiation, this monitor can display an X-ray
image that was previously generated and saved as a ref‐
erence image.
Additional functions - refer to the operator manual.
CIPP board The CIPP board primarily contains the digital camera con‐
nection to the PC via a Gigalink interface.
.
Gigalink Camera - Imaging PC image data interface with syngo AS‐
PIA. The Gigalink interface works via coaxial cables. The
CIPP board contains the receiver interface.
Minidump Memory map after an unexpected Windows XP crash.

ARCADIS XP00-000.840.04.01.02 Page 10 of 46 © Siemens, 2014


03.14 CS PS SP Restricted
General Information 1 11

1.5.2 Abbreviations

SW Software
HW Hardware
PC Personal Computer
BIOS Basic Input / Output System (PC)
OS Operating System
For ARCADIS systems: WINDOWS XP Prof.
APP Application
RAM Imaging PC working memory
(Random Access Memory)
PROM / EPROM / Imaging PC nonvolatile memory
Flash EEPROM For example, BIOS storage.
(Programmable Read Only Memory /
Eraseable Programmable Read Only Memory /
Flash Electrical Eraseable Read Only Memory)
CIPP / CIPP Board Camera Interface and Pre-Processing Board
PC Board
Board that receives digitally transmitted camera signals
DVP3 / DVP3 Board Digital Video Processing Version 3 Board
PC board with image postprocessing functions: noise sup‐
pression, edge enhancement, digital circle display.
GK Graphics Card (PC Board)
Main Board Main Board of the Imaging PC (PC Board)
D1 System control board.
See also Host
I.I. X-ray beam receptor that converts X-rays to light and
generates an image at the I.I. output window.
CB-Doc Computer Based Documentation
Application interface to product-relevant technical docu‐
mentation for CSEs.
CSE Customer Support Engineer. Sometimes called Service
Engineer or Technician.
DIFS Tool Diagnostic software for the Imaging PC.
Brand name of the single tank used in the ARCADIS Avan‐
tic system.

© Siemens, 2014 XP00-000.840.04.01.02 Page 11 of 46 ARCADIS


Restricted 03.14 CS PS SP
12 1 General Information

RxD Serial interface - data receiver


(Receive Data)
TxD Serial interface - data transmitter
(Transmit Data)

ARCADIS XP00-000.840.04.01.02 Page 12 of 46 © Siemens, 2014


03.14 CS PS SP Restricted
General Information 1 13

1.6 Required Documents


CB Doc for the particular system.

© Siemens, 2014 XP00-000.840.04.01.02 Page 13 of 46 ARCADIS


Restricted 03.14 CS PS SP
14 2 Error Diagnostics

2.1 Notes regarding Error Diagnostics

2.1.1 Display of Error Messages


The error message can be displayed on the base unit treatment panel and/or the TFT
monitor on the monitor trolley.
n If serial communication between the Host (base unit) and Imaging PC (monitor trol‐
ley) is not functioning, the Host (base unit) 4-digit error messages are displayed on
the treatment panel only.
 Example:
Error 0001 displays on the base unit treatment panel only, because communi‐
cation to the Imaging PC via the serial interface is not possible without the Host
software being loaded.
n The TFT monitor on the monitor trolley displays both the error messages of the Host
(base unit) and those of the Imaging PC (monitor trolley).
 The TFT monitor displays error messages as text.

2.1.2 Error Message Coding


The error messages are coded as follows:
n ASP_XXX_Y_ZZZZ

ASP ASPIA Software


XXX Component MSP: Host error message (ARCADIS Avantic)
MSY: Host error message (ARCADIS Varic / Orbic)
GEP: Generator error message (ARCADIS Avantic)
GEN: Generator error message (ARCADIS Varic / Orbic)
ASM: ASPIA software error message
BIC: ASPIA software imaging chain error message
FIS: ASPIA software imaging chain error message
(flight recorder entries only)
Y Error category I: Information
W: Warning
E: Error
ZZZZ Error number Multiple digit error number.

ARCADIS XP00-000.840.04.01.02 Page 14 of 46 © Siemens, 2014


03.14 CS PS SP Restricted
Error Diagnostics 2 15

Example: ASP_MSP_E_4500
 MSP = ARCADIS Avantic base unit error message
 E = Error
 4500= Host reports that a communication error with the Imaging PC has occurred.

2.1.3 Log Files


All error messages are saved to log files.
 Application messages
 Imaging PC operating system messages (component error / driver error).
 Flight recorder files that were recorded in real time.

2.1.3.1 Application messages


Application messages are saved to file AppEventLog.txt.

2.1.3.2 Imaging system operating system messages


Messages from the Imaging PC operating system (component or driver messages) are
saved to file SysEventLog.txt.

2.1.3.3 Flight Recorder


The flight recorder is active during ASPIA software run time.
The flight recorder is designed as a ring memory, and is limited to a size of 9 MByte.
New messages overwrite the oldest messages of the ring memory (FIFO principle).
The content of the flight recorder ring memory is saved to the hard drive after switching
on, before shutting down, and when a severe software error occurs.

Please note:

 Critical information could be overwritten and lost if the log files, including the flight re‐
corder data, are not saved in a timely manner after a severe error.

© Siemens, 2014 XP00-000.840.04.01.02 Page 15 of 46 ARCADIS


Restricted 03.14 CS PS SP
16 2 Error Diagnostics

2.1.4 Log Files Service Functions

2.1.4.1 Event Log Viewer (can be selected in the Local Service Browser Menu)

Fig. 3: Event Log Viewer (Local Service Browser Menu)

The event log viewer analyzes the event log file.


The event log viewer always displays the current content of the application event log.

2.1.4.2 Event Log Viewer (can be selected in the Local Service Browser using the Test Tools
Button)

Fig. 4: Event Log Viewer (Local Service Browser Test Tools)

The event log viewer analyzes the saved application messages (AppEventLog.txt file).
All saved application event log files can be opened.

ARCADIS XP00-000.840.04.01.02 Page 16 of 46 © Siemens, 2014


03.14 CS PS SP Restricted
Error Diagnostics 2 17

2.1.4.3 Flight Recorder Viewer (can be selected in the Local Service Browser using the Test
Tools Button)
The flight recorder viewer analyzes flight recorder data (current data that data saved with
Save Log).

2.1.5 Note regarding consequential errors


Please note that many error messages are classified as consequential errors during error
diagnosis.
For example
ASP_MSP_E_4500
ASP_MSY_E_4500
ASP_MSP_E_4131
ASP_MSY_E_4131
ASP_ASM_E_69
ASP_ASM_E_70
 The chronologically next error messages from the log files have to be taken into
account for the error diagnosis.

© Siemens, 2014 XP00-000.840.04.01.02 Page 17 of 46 ARCADIS


Restricted 03.14 CS PS SP
18 2 Error Diagnostics

2.1.6 Display of multiple error messages


If multiple error messages are output and displayed on the TFT monitor, open the list of
messages by clicking the "All/First" button in the message box.
 The error messages are then displayed in a list.
The sequence depends on the workflow.
Scroll in the display window.
Fig. 5: Example of system messages

ARCADIS XP00-000.840.04.01.02 Page 18 of 46 © Siemens, 2014


03.14 CS PS SP Restricted
Error Diagnostics 2 19

2.2 Host - Imaging PC Communication Error Diagnosis

2.2.1 Error messages only appear on the base unit treatment panel

As presented in prior section "Display of Error Messages", error messages are only dis‐

 played on the base unit treatment panel if there is a problem in communication between
the Host and Imaging PC. In this case begin troubleshooting on the Imaging PC to ensure
there is no problem here.

Error profile:
The Host error messages are displayed on the base unit treatment panel only.
Troubleshooting:
Check cabling
Fig. 6: Serial interface Host D1 - Imaging PC D66

 Monitor cable connector X10


 D1.X5
 D66.X5
 D66.X8
 Imaging PC COM1
Additional possible causes of error
 Switching power supply M14 (D1 power supply)
 Board D1
 CIPP board D66, built into the Imaging PC.
 Imaging PC

© Siemens, 2014 XP00-000.840.04.01.02 Page 19 of 46 ARCADIS


Restricted 03.14 CS PS SP
20 2 Error Diagnostics

2.3 Imaging PC (ASPIA) Error Diagnosis


The Imaging PC diagnosis is divided into three steps:


- Check BIOS entries
- Checks on the operating system level (Windows log files)
- Checks on the application software level (ASPIA log files)

2.3.1 Reading the BIOS Log Memory


Download the DIFS tool available on the CS intranet and burn the isodata to CD using a
burning program.

For newer PC types, use a newer version of the DIFS tool.


When using the DIFS tool for PC diagnosis, please note that the tool sometimes detects
 incorrect PC errors. This occurs for example when hardware is missing or when using a
version of the DIFS tool that is not appropriate for the PC hardware
(example: the fan is not working, because this PC type does not have a fan).

Insert the burned CD in the CD/DVD drive of the Imaging PC.


Select the BIOS, move the CD/DVD drive to the top position in the boot sequence, and
start the Imaging PC.
Using the DIFS tool that has started. display and evaluate the BIOS log memory.

2.3.2 BIOS Error Messages

2.3.2.1 Imaging PC Shuts down during BIOS Boot Phase


The BIOS log memory cannot be read.
Troubleshooting:
Disconnect each USB device in sequence, and try to start the PC each time.
 The PC starts and does not shut down. The last USB component disconnected is
defective.
 PC continues to shut down even after disconnecting all USB devices: PC defective.
Error correction:
Replace the defective component (USB component or PC).

2.3.2.2 Sporadic SW error messages, BIOS log memory not empty


The BIOS log memory has one or more entries.
Troubleshooting:
Read the BIOS log memory entries.

ARCADIS XP00-000.840.04.01.02 Page 20 of 46 © Siemens, 2014


03.14 CS PS SP Restricted
Error Diagnostics 2 21

After each entry, decide which component is to be replaced.

1. UNCORR_MEM_ERR
An uncorrectable RAM error has occurred.
2. CORR_MEM_ERR
A correctable RAM error has occurred.
3. MEM_ECC_SINGLE
Uncorrectable RAM errors have occurred.
4. PCI ERR ON PCI SLOT x (x stands for the faulty PCI interface)
PC CIPP board, DVP3 board, or graphics board defective, or there are contact problems
Error correction:

1. UNCORR_MEM_ERR:
 Are RAM storage modules available as spare parts for this type of PC?
Yes: Replace the RAM storage module.
No: Replace the PC.
2. CORR_MEM_ERR
 Are there less than 10 CORR_MEM_ERR entries?
There is no need to replace the RAM storage modules or the PC because of
these entries.
Look for other causes of the sporadic SW error messages.
 Are there more than 10 CORR_MEM_ERR entries?
If RAM storage modules are available as spare parts, replace the RAM storage
modules. Otherwise, replace the PC.
3. MEM_ECC_SINGLE
 Are RAM storage modules available as spare parts for this type of PC?
Yes: Replace the RAM storage module. No: Replace the PC
4. PCI ERR ON PCI SLOT x (x stands for the faulty PCI interface)
 Only the CIPP board is delivered as a spare part. Replace the CIPP board.
 If the error occurs again, replace the PC.
If uncorrectable RAM errors occur, the imaging software has to be fully reinstalled after

 replacing the defective components because it is highly likely that the data on the PC are
corrupt. Recovery software installation should be performed only if the recovery DVD
was created prior to the occurrence of the uncorrectable RAM errors.

© Siemens, 2014 XP00-000.840.04.01.02 Page 21 of 46 ARCADIS


Restricted 03.14 CS PS SP
22 2 Error Diagnostics

2.3.2.3 Sporadic SW error messages, BIOS log memory is empty.


The PC should be examined on the OS (Windows XP) level.
 See section 1.4

2.3.2.4 BIOS incorrect


Date, time, boot sequence, or other BIOS settings are incorrect.
The Imaging PC starts with error messages.
The system does not boot.
Troubleshooting:
Check the BIOS settings.

1. The BIOS battery is empty if the BIOS log memory has the following entries:
BAT_VOLT_OUT_OF_RANGE
ERR_CONFIG_FAILED
ERR_CMOS_CHECKSUM
 Check the BIOS battery.
2. The BIOS log memory does not have the entries listed above
 Check the BIOS battery in this case as well.
Error correction:
Read and evaluate the BIOS log memory.

1. Does the BIOS log memory contain one or more of these entries?
BAT_VOLT_OUT_OF_RANGE
ERR_CONFIG_FAILED
ERR_CMOS_CHECKSUM
 Replace the BIOS battery.
 Load the BIOS settings according to the BIOS installation instructions
(see the CB-Doc for the system).
2. The BIOS log memory does not have any of the entries listed above?
 Measure the BIOS battery voltage while installed (under load).
Replace the BIOS battery if the voltage is less then 3.0 V.
 Load the BIOS settings according to the BIOS installation instructions
(see the CB-Doc for the system).

 If the PC loses the BIOS settings several times over a period of time (days / weeks/ several
months), replace the PC.

ARCADIS XP00-000.840.04.01.02 Page 22 of 46 © Siemens, 2014


03.14 CS PS SP Restricted
Error Diagnostics 2 23

2.3.2.5 PC crashes sporadically, BIOS log memory is empty.


Check whether "Mini*.dmp" files are saved in the directory C:\Windows\Minidump or C:
\WINNT\Minidump (depending on the Imaging PC ASPIA software version). (* = place‐
holder for string with date and time the minidump file was saved).

If the BIOS log memory is empty and minidump files have been created, a Windows XP

 operating system error has occurred.


See section "OS Error Messages".

No minidump files have been saved:


Troubleshooting:

1. Check graphics card cooling (fan function)


2. Check PC cooling (fan function)
3. Check the reset button on the trolley.
4. Check power-up circuit D50 / wiring / uninterruptible power supply (UPS).
Error correction:
For

1. Cooling the graphics card:


 Replace the PC.
2. Cooling the PC:
 Check whether the defective fan is available as a spare part.
Yes: Replace the fan
No: Replace the PC
3. Reset button on the trolley:
 Repair or replace the reset button or its wiring.
4. Power-up circuit M50
 Replace defective part.

2.3.2.6 Windows XP operating systems does not start, BIOS log memory is empty.
BIOS message "Operating System not found" (or similar)
Troubleshooting:

1. Check the boot sequence in BIOS


2. System hard drive C defective?
3. Operating system not installed?
Error correction:

© Siemens, 2014 XP00-000.840.04.01.02 Page 23 of 46 ARCADIS


Restricted 03.14 CS PS SP
24 2 Error Diagnostics

1. Boot sequence:
 Open BIOS and check the boot sequence.
If incorrect, reload BIOS according to the BIOS installation instructions, or reset.

 If the PC loses the BIOS settings several times over a period of time (days / weeks/ several
months), replace the PC.

2. System hard disk:


 Open BIOS and check whether the system hard drive (drive C:) is detected in
BIOS.
If so, reload BIOS according to the BIOS installation instructions, or reset. Test
the system hard drive with the DIFS tool.
 Then test the hard drive with the DIFS tool.
If the system hard drive is working, reload the software with the clone DVD ac‐
cording to the clone software installation instructions.
If the hard drive does not work or if the error is not corrected by installing the
clone SW, replace the PC.
3. Operating system not installed:
 Open BIOS and check whether the system hard drive (drive C:) is detected in
BIOS.
If so, load BIOS according to the BIOS installation instructions, or reset.
 Then test the hard drive with the DIFS tool.
If the system hard drive is working, reload the software with the clone DVD ac‐
cording to the clone software installation instructions.
If the hard drive does not work or if the error is not corrected by installing the
clone SW, replace the PC.

ARCADIS XP00-000.840.04.01.02 Page 24 of 46 © Siemens, 2014


03.14 CS PS SP Restricted
Error Diagnostics 2 25

2.4 Windows XP Operating System Error Messages

2.4.1 The task cards are only displayed on one monitor.


The Imaging PC starts, including the syngo application software, but syngo is only dis‐
played on one monitor.
Troubleshooting:

1. Check the monitors (power switch / power cable / line power (power-up circuit))
2. Check the video cabling between the PC and monitors.
3. If there is a video splitter, check the cabling between the Imaging PC, the video split‐
ter(s), and the monitors. In addition, check the video splitter power supply (Y cable
connected to the PC PS2 socket).
4. Check the graphics card
Error correction:
for:

1. Monitors:
 Reestablish the power supply to the monitors.
A Standby LED that is off on a dark monitor, even though power is being sup‐
plied, indicates a defective monitor.
To check, switch off the system and exchange the monitor cables of both mon‐
itors. Then switch the system on again.
Replace the defective monitor.
If the dark monitor is in standby after being switched on, the video signal is
missing.
See the video cabling or graphics card.
2. Video cabling
 Check the video cabling including any video adapters.
The video cabling is described in the system circuit diagram.
Repair the video cabling if necessary.
3. Video cabling, including video splitter and video adapter
 Check the power supply (Y cable) and video splitter.
Check the video cabling including the adapters and video splitter.
Repair the power supply or video cabling if necessary.
The video cabling is presented as a schematic in the system circuit diagram.
The video cabling (including video splitter) of the Gen 1 systems is described in
the "Video Splitter" instructions. See the CB-Doc “Installation” “Options”.
The video cabling (including video splitter) of the Gen 2 systems is described in
the "Standard monitor carriage" instructions. See the CB-Doc “Installation” -
“Options”.

© Siemens, 2014 XP00-000.840.04.01.02 Page 25 of 46 ARCADIS


Restricted 03.14 CS PS SP
26 2 Error Diagnostics

4. Graphics card:
 Check the graphics card setting (analog or digital output / dual monitor opera‐
tion / resolution 1280 x 1024 pixels).
End the syngo application on the Imaging PC and start the Imaging PC in Win‐
dows XP mode.
The steps required can be found in the ARCADIS GEN2 “Standard Monitor Car‐
riage” installation instructions.
See the CB-Doc ARCADIS Gen2, “Installation “Options ARCADIS ...” Standard
monitor carriage”.
 If the graphics card can be switched back to dual monitor mode and the correct
1280 x 1024 pixel resolution, no additional measures are required.
 Replace the PC if the graphics card cannot be switched back to dual monitor
mode or if a video signal does not appear at the 2nd video output despite the
switch.

2.4.2 Imaging PC starts with Error Messages, Minidump Files have ben Cre‐
ated
The BIOS log memory shows nothing peculiar.
Evaluate the system event log files (“*_SysEventLog.txt”).
The system event log files contain the following entries:
Troubleshooting:
Evaluation of the “*_SysEventLog.txt” file.

1. “22-Nov-12 13:02:56 1001 Save Dump n/a The computer has rebooted from a bug‐
check.
The bugcheck was: 0x100000ea (0x8a254998, 0x8a320948, 0xb84e3cb4,
0x00000001).
A dump was saved in: C:\WINNT\Minidump\Mini102913-01.dmp”
(the most important failure-specific information is highlighted)
The defective component can be identified by analyzing this information.
The analysis of the minidump file (in this example the file “Mini102913-01.dmp”) re‐
quires in-depth knowledge of the operating system can should be performed by SW
developers.
2. “1500 LDM n/a Disk group YI7k025385Dg=: Disabled by errors”.
The raid controller or hard drives connected to the raid controller are defective.
3. “51 Disk n/a An error was detected on device \Device\Harddisk*\D during a paging op‐
eration”
(* = 1,2 or 3, depending on the defective hardware)
Check the hard drive to main board plug connection.
The hard drive controller or one of the hard drives is defective.

ARCADIS XP00-000.840.04.01.02 Page 26 of 46 © Siemens, 2014


03.14 CS PS SP Restricted
Error Diagnostics 2 27

4. “108 nv n/a The driver nv4_disp for the display device \Device\Video0 got stuck in an
infinite loop”
(“nv4_disp” can vary depending on the graphics card installed)
The graphics card or main board is defective.
5. “7 Cdrom n/a The device, \Device\CdRom0, has a bad block.”
The CD/DVD blank inserted in the CD ROM drive is defective.
6. “9 atapi n/a The device, \Device\IdePort0, did not respond within the timeout period.”
The CD ROM drive does not react within the time set in the operating system.
Check the CD/DVD drive cable to the main board.
7. “E (save date / time) 12 PlugPlay Manager n/a The device (CD/DVD drive name) disap‐
peared from the system without first being prepared for removal.”
The CD ROM drive is no longer recognized by the operating system.
Check the CD/DVD drive cable to the main board.
8. “29 cidre2 n/a <I>Cidre2: Interrupt Storm .....CidreDpcForlsr </I>”
Sporadic contact problems occur between the camera and CIPP board.
Check the camera, connection cables from the camera to the CIPP board, camera plug
contacts, C-arm cable, X10, X11 (if present), CIPP board D66.X2, D66.X5, and CIPP
board. Also check the coaxial cable from the camera to the CIPP board to ensure the
bending radius is not too small or for squeezing of the cable (within plug connection
X10 / X11 as well).
9. “E (save date / time) 12 PlugPlayManager n/a The device ‘CIPP’... disappeared from the
system without first being prepared for removal.”
CIPP board (D66) or main board of the Imaging PC defective, or there are contact
problems.
Check whether the CIPP board is inserted correctly; pull and reinsert if necessary.
10. “E (save date / time) 12 PlugPlayManager n/a The device ‘DVP3’... disappeared from
the system without first being prepared for removal.”
DVP3 board or main board of the Imaging PC defective, or there are contact problems.
Check whether the DVP3 board is inserted correctly; pull and reinsert if necessary.
11. Partition E:\ (image data) does not exist or has been shifted.
If the Imaging PC software was installed prior to the error occurring, the error may be
caused by an additional USB drive (USB HDD or USB memory stick) connected during
the software installation.
Hard drive was not detected by the BIOS.
Possible Imaging PC hardware error.
Error correction:
for:

© Siemens, 2014 XP00-000.840.04.01.02 Page 27 of 46 ARCADIS


Restricted 03.14 CS PS SP
28 2 Error Diagnostics

1. 22-Nov-12 13:02:56 1001 Save Dump n/a The computer has rebooted from a bug‐
check.
The bugcheck was: 0x100000ea (0x8a254998, 0x8a320948, 0xb84e3cb4,
0x00000001).
A dump was saved in: C:\WINNT\Minidump\Mini102913-01.dmp
 The PC must be replaced.
Minidump files were generated by the operating system when a hardware or software

 component was not functioning correctly. If the main memory can be identified as the
cause of the failure, the entire Imaging PC software has to be reinstalled because the PC
data may be corrupt.

2. “1500 LDM n/a Disk group YI7k025385Dg=: Disabled by errors”.


 The PC must be replaced.
3. “51 Disk n/a An error was detected on device \Device\Harddisk*\D during a paging op‐
eration”
 If the plug connections between the hard drive and main boards can be local‐
ized as the cause of the error, reload the Imaging PC software because corrupt
data cannot be ruled out.
 The PC has to be replaced if the plug connections from the hard drive to the
main board were OK.
4. “108 nv n/a The driver nv4_disp for the display device \Device\Video0 got stuck in an
infinite loop”
 The PC must be replaced.
5. “7 Cdrom n/a The device, \Device\CdRom0, has a bad block.”
 Remove the CD/DVD blank from the drive.
 If it occurs again, try a CD/DVD blank from another manufacturer.
6. “9 atapi n/a The device, \Device\IdePort0, did not respond within the timeout period.”
 No components have to be replaced if the plug connections between the
CD/DVD drive and the main board can be localized as the cause of the error.
 Replace the CD/DVD drive. If unsuccessful, replace the PC.
7. “E 20-Oct-10 19:26:44 12 PlugPlay Manager n/a The device (CD/DVD drive name) dis‐
appeared from the system without first being prepared for removal.”
 No components have to be replaced if the plug connections between the
CD/DVD drive and the main board can be localized as the cause of the error.
 Replace the CD/DVD drive. If unsuccessful, replace the PC.
8. “29 cidre2 n/a <I>Cidre2: Interrupt Storm .....CidreDpcForlsr </I>”
 If the contact problems can be localized, repair or replace the corresponding
contacts, or replace the corresponding cable.
 If the contact problems cannot be localized, replace the CIPP board. Replace
the camera as well if needed.

ARCADIS XP00-000.840.04.01.02 Page 28 of 46 © Siemens, 2014


03.14 CS PS SP Restricted
Error Diagnostics 2 29

9. “E (save date / time) 12 PlugPlayManager n/a The device ‘CIPP’... disappeared from the
system without first being prepared for removal.”
 No additional measures are required if the Imaging PC functions after remov‐
ing/inserting the CIPP board.
 If multiple corresponding entries have already been found (within several days
or weeks), replace the CIPP board or Imaging PC.
10. “E (save date / time) 12 PlugPlayManager n/a The device ‘DVP3’... disappeared from
the system without first being prepared for removal.”
 No additional measures are required if the Imaging PC functions after remov‐
ing/inserting the DVP3 board.
 If multiple corresponding entries have already been found (within several days
or weeks), replace the Imaging PC.
11. Partition E:\ (image data) does not exist or has been shifted.
 If a USB drive or USB memory stick was inserted during software installation,
remove them and repeat the software installation.
 If the drive was not detected by the BIOS, the BIOS can be reset to default val‐
ues if necessary. Reload the BIOS according to the BIOS installation instruc‐
tions. Once drive E:\ is visible again, the Imaging PC software has to be reloa‐
ded.
 Otherwise replace the Imaging PC.

© Siemens, 2014 XP00-000.840.04.01.02 Page 29 of 46 ARCADIS


Restricted 03.14 CS PS SP
30 2 Error Diagnostics

2.5 Imaging PC Software (ASPIA) Error Messages

2.5.1 Sporadic ASP_BIC_E_10103 error messages


Cause of error:
This error message occurs when the camera image data reach the CIPP board with a delay
of more than 0.3 milliseconds.

Troubleshooting:
Files “*_AppEventLog.txt”, “ASP_FRC_*” have to be analyzed.

2.5.1.1 Error ASP_BIC_E_10103 in file “*_AppEventLog.txt”:


The following entry is in file “*_AppEventLog.txt”:

“ASP_BIC_E_10103, (ASP_BIC_PERFORMANCE_ERROR)
The imaging hardware has stopped because of performance issues”

Consequential errors that could occur with this error:


ASP_ASM_E_69
ASP_ASM_E_19
ASP_MSP_E_4500
ASP_MSP_E_4131
ASP_MSY_E_4500
ASP_MSY_E_4131

Cause of error:
Defective CD/DVD blank in the CD/DVD drive.

Error correction:
Remove the defective CD/DVD blank from the CD/DVD drive.
Deleting the burn job and create it again.

2.5.1.2 Imaging chain error in file “ASP_FRC_*”

 One or more of the following error messages are registered before error message
ASP_BIC_E_10103 is saved to the flight recorder file.

One or more of the following entries are in file “ASP_FRC_*”:

“ASP_FIS_W_8070, (ASP_FIS_MIP_BUFFER_OVERRUN_OCCURED_WARNING

ARCADIS XP00-000.840.04.01.02 Page 30 of 46 © Siemens, 2014


03.14 CS PS SP Restricted
Error Diagnostics 2 31

A buffer overrun has been detected while waiting for the arrival of a new frame.”

“ASP_FIS_W_8066, (ASP_FIS_MIP_HIG_IMAGE_INPUT_LATENCY
The images delivered by the hardware are received too slowly by the transfer channel.”

“ASP_FIS_W_8064,
A timeout occurred while waiting for a frame from the DVP board.”

“ASP_FIS_W_13043”
A high display latency has been detected, Not all previous images have been processed.”

Additional consequential errors that could also be registered:


ASP_FIS_E_8093
ASP_FIS_W_8091
ASP_FIS_E_33004

Cause of error:
CIPP board or DVP3 board
Possibly the PC main board or HDD as well.

Error correction:
Replace the CIPP board.
Replace the Imaging PC.

2.5.2 Sporadic ASP_BIC_W_10104 and ASP_BIC_E_10106 error messages

 When the base unit is connected to the monitor trolley (plug X10 is connected) assess
message ASP_BIC_W_10104 as an error message.

Cause of error:
The error message occurs when the camera - CIPP board - DVP3 board connection is bro‐
ken.

Troubleshooting:
Files “*_AppEventLog.txt”, “ASP_FRC_*”, and if necessary “*_SysEventLog.txt” as well have
to be analyzed.

The following entries are in file “*_AppEventLog.txt”:


“ASP_BIC_W_10104, (ASP_BIC_CONNECTION_MISSING_WARNING)

© Siemens, 2014 XP00-000.840.04.01.02 Page 31 of 46 ARCADIS


Restricted 03.14 CS PS SP
32 2 Error Diagnostics

Connection to device is missing. (DVP, CAMERA, BASE DEVICE).”


“ASP_BIC_E_10106, (ASP_BIC_CONNECTION_MISSING_ERROR)
The connection between some hardware components is missing.”

One or more of the following entries are in file “ASP_FRC_*”:

ASP_FIS_E_26048 (ASP_FIS_CIP_CAMERA_NOT_CONNECTED)”.
No Camera is connected to the CIPP Board.
ASP_FIS_E_26049 (ASP_FIS_CIP_DVP3_BOARD_NOT_CONNECTED)
No DVP board is connected to the CIPP board.
ASP_FIS_E_26050 (ASP_FIS_CIP BASE_DEVICE_NOT_CONNECTED)
No base device connected to the CIPP board.

Cause of error:

1. The base unit (Host, D1) is not connected to the monitor trolley (CIPP board).
2. The camera - CIPP board connection is not OK (D66.X4 - (X11, if present) - X10 - Host
D1.X1 Host D1.X2 - camera M4.X1 - M4.X2).
Check the cabling.
3. The CIPP board and DVP3 board are not connected to one another (ribbon cable).
Check the ribbon cable for proper installation.
4. The CIPP board or DVP3 board is defective.
5. The camera has no power supply.
Check power supply unit M13, check the power supply unit NM13 - C-arm cable - cam‐
era M4.X1 cabling, check the camera (LED).
6. The camera is defective.
Check the camera.

Error correction:

1. Establish the base unit - monitor trolley connection.


If an error occurs when the base unit and monitor trolley are connected, check the
connection cables between D1 and the CIPP board (internal and monitor cable), and
repair or replace.

 If necessary, restart the system.

2. Repair the cabling between the camera and CIPP board. Replace the cable if defective.
3. No additional measures are required if the ribbon cable between the CIPP board and
DVP3 board was the cause of the error.

ARCADIS XP00-000.840.04.01.02 Page 32 of 46 © Siemens, 2014


03.14 CS PS SP Restricted
Error Diagnostics 2 33

4. If the CIPP board is defective, replace it. Otherwise replace the PC.
5. Repair the camera power supply or replace the defective cable or power supply unit.
6. Replace the camera.

2.5.3 Sporadic ASP_BIC_E_10105 error message


Cause of error:
The error message occurs when the camera - triaxial cable - CIPP board connection has a
problem.

Troubleshooting:
Files “*_AppEventLog.txt” and “ASP_FRC_*” have to be analyzed.

The following entries are in file “*_AppEventLog.txt”:

“ASP_BIC_E_10105, (ASP_BIC_HARDWARE_DEVICE_PROBLEM)
EMV problem or a connection between some hardware components is missing.”

One or more of the following error occur:


ASP_ASM_E_69
ASP_ASM_E_19
ASP_MSP_E_4500
ASP_MSP_E_4191
ASP_MSY_E_4500
ASP_MSY_E_4191.

Continue by looking for the following error messages in file “*_AppEventLog.txt”:


“ASP_GEP_W_5172 (ASP_GEP_MSG_GE_EXT_72_L_WARNING_P_ARC”
Generator arcing tube (positive HV transformer)”
“ASP_GEP_W_5173 (ASP_GEP_MSG_GE_EXT_73_L_WARNING_N_ARC”
Generator arcing tube (negative HV transformer)”

One or more of the following entries are in file “ASP_FRC_*”:

ASP_FIS_E_26046 (ASP_FIS_CIP_INVALID_HARDWARE_EVENT_WATCHDOG_OBJECT)”.
An invalid “CIPP Hardware Event” watchdog instance has been found.
ASP_FIS_E_26047 (ASP_FIS_CIP_TOO_MANY_HARDWARE_EVENTS)
The CIPP Board has detected too many hardware events. The event buffer is too small to
obtain all of them.

© Siemens, 2014 XP00-000.840.04.01.02 Page 33 of 46 ARCADIS


Restricted 03.14 CS PS SP
34 2 Error Diagnostics

ASP_FIS_E_26051 (ASP_FIS_CIP CHECK_CONNECTION_FAILED)


Unable to check the given CIPP board connection.
ASP_FIS_W_33003 (ASP_FIS_NFC_CIPP_HARDWARE_EVENT)
Notification: A hardware event has been detected by the CIPP board. HW Event : %1.

Cause of error:

1. If one of the two entries


“ASP_GEP_W_5172 (ASP_GEP_MSG_GE_EXT_72_L_WARNING_P_ARC” or
“ASP_GEP_W_5173 (ASP_GEP_MSG_GE_EXT_73_L_WARNING_N_ARC”
appears multiple times, and if the entered E_10105 error messages are related to
them chronologically, the E_10105 error messages can be traced back to X-ray tubes
that are no longer fully high-voltage resistant (arcing). Check the generator ground
connections, the SIREPHOS/ POWERPHOS, and the ground connections of the triaxial
cable to rule out EMC effects.
2. The base unit (Host, D1) is not connected to the monitor trolley (CIPP board).
3. The camera - CIPP board connection is not OK. Check the cabling between the camera
and CIPP board.

 The continuity of the triaxial cable can be checked with a multimeter. However, the mul‐
timeter cannot check the high-frequency behavior of the triaxial cable.

The triaxial cable between the camera and CIPP board is bent or pinched.
The triaxial cable shielding is missing or not connected to ground.
4. The camera has no power supply. Check the power supply unit, cabling, and camera.
5. The camera is defective.
6. The CIPP board is defective.

Error correction:

1. If sporadic tube arcing bothers the customer, replace the X-ray tube as well.
2. Establish the base unit - monitor trolley connection.
If an error occurs when the base unit and monitor trolley are connected, check the tri‐
axial cable between the camera and the CIPP board (internal and monitor cable), and
repair or replace.

 If necessary, restart the system.

3. Repair the cabling between the camera and CIPP board. Replace the cable if defective.
4. Repair the camera power supply or replace the defective cable or power supply unit.
5. Replace the camera.

ARCADIS XP00-000.840.04.01.02 Page 34 of 46 © Siemens, 2014


03.14 CS PS SP Restricted
Error Diagnostics 2 35

6. Replace the CIPP board.

2.5.4 Investigate other Sporadic Error Messages by Error Pattern


Read the BIOS log memory with the DIFS tool.
 The BIOS log memory is empty.
Files “*_AppEventLog.txt” and “ASP_FRC_*” have to be analyzed.

2.5.4.1 Pattern ASP_ASM_E_30, ASP_ASM_W_26, ASP_ASM_E_70


Cause of error:
The DVP3 board cannot be addressed.

Troubleshooting:
The following error messages can be seen in file “*_AppEventLog.txt”:
“ASP_ASM_E_30
Some Components are not ready for startup”
“ASP_ASM_W_26
The execution of the function tried to execute has failed.”
ASP_ASM_E_70
Internal Imaging System error occurred.”

The consequential error occurs:


“ASP_BSC_E_87
An internal error occurred during communication to Main system.”

One or more of the following entries are in file “ASP_FRC_*”:


“ASP_FIS_E_5011, (ASP_FIS_NPM_OPEN_DVP3_FAILED)
Viprox refused to open a connection to the DVP3 board.”
“ASP_FIS_E_8061, (ASP_FIS_MIP_OPEN_DVP3_FAILED)
Viprox refused to open a connection to the DVP3 board.
“ASP_FIS_E_26046”

If one of the messages listed above is saved to the corresponding log files, the DVP3
board is defective (contact problems in the PCI bus plug connection) or the main board is
defective.

Error correction:

© Siemens, 2014 XP00-000.840.04.01.02 Page 35 of 46 ARCADIS


Restricted 03.14 CS PS SP
36 2 Error Diagnostics

1. Check that the DVP3 board is inserted correctly in the PCI slot; pull and reinsert the
DVP3 board.
 No additional measures are necessary if the error does not occur again.
 However, if the error occurs again after a period of time (days / weeks), replace
the PC.
2. Replace the Imaging PC.

2.5.4.2 Pattern ASP_BIC_E_11026, ASP_BIC_E_11023, ASP_BIC_E_2002


Cause of error:
The CIPP board cannot be addressed.

Troubleshooting:
The following error messages can be seen in file “*_AppEventLog.txt”:
“ASP_BIC_E_11026
Some Problem accessing the camera interface and pre-processing hardware has been de‐
tected.”
“ASP_BIC_E_11023
Some problem coordinating the actions of image chain sub-components has been detec‐
ted.”
ASP_BIC_E_2002
A function call to the interface of the hardware image chain failed.”

One or more of the following entries are in file “ASP_FRC_*”:


“ASP_FIS_E_26045, (ASP_FIS_CIPP_OPEN_CIPP_FAILED)
Unable to open a handle to the CIPP board.”
“ASP_FIS_E_23038, (ASP_FIS_API_OPEN_CIPP_FAILED)
Unable to open a connection to the CIPP board.”

If one of the messages listed above is saved to the corresponding log files, the CIPP board
is defective (contact problems in the PCI bus plug connection) or the main board is defec‐
tive.

Error correction:

1. Check that the CIPP board is inserted correctly in the PCI slot; pull and reinsert the CIPP
board.
 No additional measures are necessary if the error does not occur again.
 However, if the error occurs again after a period of time (days / weeks), replace
the PC.

ARCADIS XP00-000.840.04.01.02 Page 36 of 46 © Siemens, 2014


03.14 CS PS SP Restricted
Error Diagnostics 2 37

2. Replace the Imaging PC.

© Siemens, 2014 XP00-000.840.04.01.02 Page 37 of 46 ARCADIS


Restricted 03.14 CS PS SP
38 3 Tools

3.1 Tools for Error Diagnostics

3.1.1 BIOS Log Memory

3.1.1.1 Reading the BIOS log memory using the BIOS function
n Select the BIOS (press F2 when booting, the enter the BIOS password).
n In BIOS select the Advanced menu.
n Select and open the DMI Event Logging submenu.
Fig. 7: Select BIOS log memory

n If there are no entries in the BIOS log memory, “no event log records found” is dis‐
played.
n If there are entries in the BIOS log memory they are shown.
.

ARCADIS XP00-000.840.04.01.02 Page 38 of 46 © Siemens, 2014


03.14 CS PS SP Restricted
Tools 3 39

Fig. 8: BIOS log memory empty Fig. 9: BIOS log memory error display

3.1.1.2 Read the BIOS log memory with the DIFS tool.

The BIOS of the Imaging PC has to be changed so that the bootable CD or bootable USB
stick starts.
 Record the original BIOS settings.
Reset and save the correct BIOS settings after using the DIFS tool.

n Change the PC in the BIOS to start the bootable DIFS tool.


n Insert the DIFS tool and boot it.
n Once the DIFS tool has performed the PC examination, select the <ESC> key to go to
the DOS level.
n Then enter the command bioslog -read.
n The result is displayed on the monitor.

© Siemens, 2014 XP00-000.840.04.01.02 Page 39 of 46 ARCADIS


Restricted 03.14 CS PS SP
40 3 Tools

n After the error analysis, reset and save the BIOS settings previously noted.
Fig. 10: DIFS tool BIOS log display

3.1.2 Log Viewer in ASPIA (Imaging PC)


The ASPIA (Imaging PC) Local Service Browser contains several tools for analyzing log
files.

ARCADIS XP00-000.840.04.01.02 Page 40 of 46 © Siemens, 2014


03.14 CS PS SP Restricted
Tools 3 41

n Application Event Log Viewer


You can reach the viewer after opening the local service browser.
Fig. 11: Event Log Viewer

The viewer only displays the current application and system messages.
n Test Tools
Using the Test Tools button, you can open the following log files using the viewer:
 Application Event Log
 System Event Log
 Workflow Event Log
 Flight Recorder Log
Both current and archived log files can be opened.

3.1.2.1 Application Event Log


The image shows the event log viewer application interface.

© Siemens, 2014 XP00-000.840.04.01.02 Page 41 of 46 ARCADIS


Restricted 03.14 CS PS SP
42 3 Tools

The messages saved in the ” *_ApplicationEventLog.txt” files are shown.


Fig. 12: Application Event Viewer section

3.1.2.2 System Event Log


The messages saved in the ” *_SystemEventLog.txt” files are shown in the viewer.

3.1.2.3 Workflow Event Log


The messages saved in the ” *_WorkflowEventLog.txt” files are shown.

3.1.2.4 Flight Recorder Log


The messages saved in the “ASP_FRC_*” are shown.
Fig. 13: Flight Recorder Log Viewer section

ARCADIS XP00-000.840.04.01.02 Page 42 of 46 © Siemens, 2014


03.14 CS PS SP Restricted
Tools 3 43

The flight recorder is a very fast tool that captures all events when suing the system. The
events are kept in a small buffer in the main memory. The buffer content is only written
to the hard drive when:

 n

n
the system is restarted (not "resume")
the system is shut down (not hibernate)
n writing and saving a developer save log was initiated manually
n severe errors have occurred

© Siemens, 2014 XP00-000.840.04.01.02 Page 43 of 46 ARCADIS


Restricted 03.14 CS PS SP
44 4 Changes to previous version

Initial publication.

ARCADIS XP00-000.840.04.01.02 Page 44 of 46 © Siemens, 2014


03.14 CS PS SP Restricted
List of Hazard IDs 5 45

There are no Hazard IDs in this document.

© Siemens, 2014 XP00-000.840.04.01.02 Page 45 of 46 ARCADIS


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

healthcare.siemens.com/services

Siemens Healthineers Headquarters


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

Print No.: XP00-000.840.04.01.02 | Replaces: n.a.


Doc. Gen. Date: 03.14 | Language: English
© Siemens Healthcare GmbH, 2014

siemens.com/healthineers

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy