XP00-000 840 04 01 02
XP00-000 840 04 01 02
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
1 General Information 4
2 Error Diagnostics 14
3 Tools 38
1.5.1 Definitions
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
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.
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.
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.
2.1.4.1 Event Log Viewer (can be selected in the Local Service Browser Menu)
2.1.4.2 Event Log Viewer (can be selected in the Local Service Browser using the Test Tools
Button)
The event log viewer analyzes the saved application messages (AppEventLog.txt file).
All saved application event log files can be opened.
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.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
- Check BIOS entries
- Checks on the operating system level (Windows log files)
- Checks on the application software level (ASPIA log files)
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.
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.
If the BIOS log memory is empty and minidump files have been created, a Windows XP
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. 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.
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”.
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.
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:
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.
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.
Troubleshooting:
Files “*_AppEventLog.txt”, “ASP_FRC_*” have to be analyzed.
“ASP_BIC_E_10103, (ASP_BIC_PERFORMANCE_ERROR)
The imaging hardware has stopped because of performance issues”
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.
One or more of the following error messages are registered before error message
ASP_BIC_E_10103 is saved to the flight recorder file.
“ASP_FIS_W_8070, (ASP_FIS_MIP_BUFFER_OVERRUN_OCCURED_WARNING
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.”
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.
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.
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:
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.
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.
Troubleshooting:
Files “*_AppEventLog.txt” and “ASP_FRC_*” have to be analyzed.
“ASP_BIC_E_10105, (ASP_BIC_HARDWARE_DEVICE_PROBLEM)
EMV problem or a connection between some hardware components is missing.”
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.
Cause of error:
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.
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.
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.”
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:
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.
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.”
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.
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.
.
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 After the error analysis, reset and save the BIOS settings previously noted.
Fig. 10: DIFS tool BIOS log display
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.
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
Initial publication.
healthcare.siemens.com/services
siemens.com/healthineers