Professional Documents
Culture Documents
Us17-101 840 01 14 02
Us17-101 840 01 14 02
Troubleshooting Guide
System
System Troubleshooting
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, 2016” 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 Medical Solutions USA Inc. - USA
Siemens Healthcare Diagnostics Inc. - USA and/or
Siemens Healthcare Diagnostics Products GmbH - Germany
1 Troubleshooting Guide 7
1.1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1.1 Acronyms and Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2 Basic Troubleshooting Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.3 Boot Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3.1 Viewing the Bootup Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.3.2 Shortcut to Service Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2 Troubleshooting Flowcharts 23
5.1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
6.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
6.2 BIOS Settings -- MBM200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
6.2.1 Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
6.2.2 Advanced. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
6.2.3 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
6.2.4 Server Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
6.2.5 Boot Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
6.2.6 Boot Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
6.3 BIOS Settings -- MBM3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
6.3.1 Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
6.3.2 Advanced. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
6.3.3 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
6.3.4 Server Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
6.3.5 Boot Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
6.3.6 Boot Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
6.4 Upgrade BIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
6.4.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
6.4.2 Verify BIOS Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
6.4.3 Install BIOS Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
1.1 Purpose
A system can fail in a number of ways exhibiting various symptoms. Each case can have
unique circumstances relating to the failure. This document offers an approach to isolat‐
ing faults on the basis of the symptoms seen. To accomplish this, flowcharts can be used
to assist in diagnosing the system failures.
This document begins with a list of acronyms and basic troubleshooting steps, followed
by the normal boot sequence, and various troubleshooting techniques. Effective system
troubleshooting uses the ( Troubleshooting Flowcharts / Page 24) . It guides the user
through a series of functional tests and diagnostic suggestions.
Acronym/Term Definition
AC AC tray; also referred to as PSAC Tray
ADC Analog Control Doppler
aperture number of active transducer elements, or transducer width, dur‐
ing transmit or receive
apodization amplitude weighting function applied across the active trans‐
ducer aperture
beamformer electronics responsible for combining signals (receive or trans‐
mit) from each transducer element into a single acoustic vector
axial direction along the acoustic vector
B-mode two dimensional brightness mode display
BC-mode B-mode with a color flow ROI
BE backend or Backend Board
BMC Baseboard Management Controller
BP Backplane
BP-mode B-mode with power mode ROI
CB CW Beamformer Board
CDC Clock Doppler and Control
CLA transducer curved linear array transducer
CP Control Panel
CW or CW Doppler continuous wave Doppler
Acronym/Term Definition
DICOM Digital Imaging Communications in Medicine
ECG electrocardiogram
EM E Module
ensemble set of color flow vectors from a single direction used to estimate
flow
FOV field-of-view
FP Front Panel
IMGF Image Former
HDD Hard Disk Drive
HW Hardware
HW/HW IDD specifies signal characteristics of hardware-to-hardware interfa‐
ces
MBC Mother Board Carrier
MBM Mother Board Module
M-mode Motion Mode
MPE MP Extension
MPI Micro Pinless Interface
OCP Over Current Protection
OS Operating System
OVP Over Voltage Protection
LA transducer linear array transducer
PA transducer phased array transducer: element spacing is no greater than
half-wavelength
PPM Physio Module
PSM Power Supply Module
PW or PW Doppler pulsed wave Doppler
RAD Realtime Analog Data Control
RTC Real Time Controller
SAPP Spectral, Audio, Physiological Processor
Acronym/Term Definition
SW Software
TRB Transmit and Receive Board
TGC time gain compensation
TSC Toyon Streaming Controller
Vortal Main image screen that includes the menu bars on left and right
and image area in the center.
When the AC power is first applied to the system and 5V-SB is present, the Baseboard
Management Controller (BMC) on the Mother Board requires 20-30 seconds to initialize.
During this time, the system status LED will blink, alternate between amber and green,
and the power button functionality of the control panel is disabled, preventing the CPU
from powering up. Once the BMC initialization has completed, the status LED will stop
blinking and power button functionality is restored and can be used to turn on the sys‐
tem.
1. 10 seconds for CP power switch backlighting delay time is not tied with the MBM initiation step since CP receives its
power directly from PSM. This delay happens due to the behavior of the CP firmware.
T=0 Seconds Press Power On S1200BTL LEDs: LED2 indicates S1200BTL BIOS
from CP to motherboard POST;
LED1 is Off .
power on the voltages regula‐
CPU boot de‐
system. LED2 turns tors are func‐
vice;
green. tional. MBM200
LAN on. Start OS;
LAN LED blinks
green. Start Services;
Start ODT, firm‐
ware loading;
Start ACQ serv‐
ices;
Start Rendering
services;
Start ACQ UI;
T = ~72 sec‐ T = ~95 sec‐ Black screen Computer BIOS Computer BIOS
onds onds. statrts.
T = ~128 sec‐ T = ~151 sec‐ System sends CP back light Low lwevel serv‐
onds onds out the "ACU‐ flashes once. ices starts.
SON SC2000" Display lights up.
splash screen
with progress
bar.
T= ~130 sec‐ T = ~155 sec‐ Imaging Screen (also called Vortal) Boot up comple‐
onds onds ted.
1. 10 seconds for CP power switch backlighting delay time is not tied with the MBM initiation step since CP receives its
power directly from PSM. This delay happens due to the behavior of the CP firmware.
2. If the breaker has only been on for a couple seconds before the Power button is pressed, then it will be approximately 40
seconds until the beeps are heard. If the Power button is pressed after the breaker has been on for 30 seconds or more,
then the beeps will occur approximately 16 seconds after the Power button is pressed.
If errors occur during the following steps, use this table to identify which modules are re‐
sponsible. If necessary, contact the local UPTIME Service Center for help.
2. As soon as the Progress bar is seen, move the mouse curser to the progress bar area,
at the far left side of the bar.
Fig. 1: Splash Screen -- Progress Bar Shown
3. Press and hold "CTRL+ALT", and press the "Select" key on the Control Panel. A small
window, “Startup Shutdown Monitor,” will be displayed. This will minimize the pro‐
gress bar splash screen so startup activity can be seen. Note that the splash screen can
be moved at this point by single clicking on it with the mouse and dragging it.
Fig. 2: Startup Shutdown Monitor Window
4. (Visible only for systems with SW before VA35A) Click "Show Processes". The detailed
system process list will be shown.
Fig. 3: Detailed System Process List
5. (Visible only for systems with SW before VA35A) Click "Show Processes" again. The
window will return to show the splash screen.
6. With the mouse cursor in the progress bar area, press "CTRL+ALT", and click "Select"
from the Control Panel. The display will return to the boot up screen. This will again
maximize the splash screen.
Fig. 4: Splash Screen -- More Advanced Progress Bar
The Service Portal will be shown. Enter the service mode from here.
Mode Condition
Standby AC power plugged in, circuit break on, cooling fan in‐
side is operational, 5V standby output voltage on.
Supplies 5V to CP.
Power Off AC power plugged in, circuit breaker off, cooling fan
inside is operational, no output voltage.
Power Up Pressing the Control Panel button to power on, enable
voltage (Motherboard on first, then other parts of the
system are enabled).
Reset The Control Panel power button is held five (5) sec‐
onds to hard shutdown (SW shutdown last case would
not happen).
Run Mode After power up, all systems are operational and the
PPS (programable power supply sending voltage to
transducer head) are all operational.
Power Failure One element of the power supply fails.
These LEDs shall unambiguously show the cause of the shutdown whether it occurs from
“Run mode” or at “Startup”.
Power Supply LED Status “OK” means 2 green LEDs. Any other condition is “Not OK’.
3.2 Electrical
Vin Frequency 47 63 Hz
3.2.4 DC Outputs
Clean/DIgital Outputs
The sum of all errors shall be less than “Min -> Max” values in Table 4. Individual contribu‐
tors shall not exceed the following limits:
n Voltage setpoint accuracy; refer to table below
n 0.5% for a temperature range of 25°C ± 25°C
Output Setpoint (1) Min. (V) Nom. (V) Max. (V) Remote OVP (3) OCP (3)
Sense
Digital
P2V5_Digital 1% +2.43 +2.50 +2.57 Yes Latched Latched
Clean
N106V_Clean -1/+3% -102.82 -106.00 -111.30 Limit (4) Recovers
PPS
VXMT (2) 2% +30.00 Variable +210.00 Recovers
Notes:
1. Setpoint is percent of Nom.
2. Setpoint is percent of control voltage.
3. Resistor changeable setpoint.
4. Limit to maintain safe operating condition. Must attempt restart every 1 to 2 seconds.
Latched: the power supply must be power cycled to enable it to go to normal function
again; the circuit breaker turns off. Wait at least one (1) minute before powering up
again.
Non latch: if the voltage fails, the system will not shut down automatically. This protects
the system from fan noise generation.
Recovers: it will not kill the power supply and will recover once the issue has been re‐
solved.
Clean Latched
N12V_Clean - 12V 115% - 135% Table 6 115% - 150%
Digital Recovers
P106V +106V < 120% (6) Table 6 110% - 150%
PPS
Notes:
1. % of Nominal Voltage except Fan_Voltage use max (28V).
2. The OVP sense circuitry and reference must be separate and distinct from the regula‐
tor control circuitry and reference. No single point fault should cause an OV (Over
Voltage) condition on any outputs.
3. If the DC output has Remote Sense capability, the OVP monitor must sense the load
voltage, the same voltage seen by the normal remote sense.
4. Initial Turn on into system load and capacitance will not cause an OCP.
5. Base on “Max Load” Table 6.
6. The P106V_Clean and N106V_Clean outputs are designed such that a short in the ser‐
ies regulator can not cause the output to exceed 120% of rated voltage (127 VDC).
Clean
P2V3_Clean 10% 10 12 28 30% 3% 10%
PPS
VXMT 0 (180 W) (200 W)
1. % of Op (Output) Load
2. % of “Max Load”, step load from “Max Load” to (“Max Load” - “Transient Load%” then:
step load from (“Max Load” - “Transient Load%” to “Max Load”
Period 100ms, Transient load slew rate is 1A/iSec.
3. % of voltage output values before “Transient Load”.
4. Overshoot
a. Upon application or removal of Vac in, or assertion/de-assertion of PS_ON*.
b. Voltage of opposite polarity shall not be present on any output during turn on or
turn off.
c. The overshoot must not create an OVP/OCP Fault.
5. Supports Current Transient of 2.5A of 500ms max.
6. Starting surge of 3 amps for 8 seconds.
7. Starting surge on Fan_Voltage is an additional 10A for two seconds, due to fan mo‐
tors. The output is L-C filtered. Filter component values of approximately 240uH and
10000uF (Comer frequency = n100Hz) should be adequate. total output power will
not exceed 45W.
The PPS uses a charge pump between input and output capacitors to effectively reuse
charge and reduce power consumption.
The output is programmable via a 10-bit serial DAC between 0 and 255V. The active
range is + 30V to + 210V. Outside of the active range PPS specification is not specified,
however DAC codes below 30V must result in 30V or less output, DAC codes above 210V
must result in 210V or greater output.
It is desirable to extend range beyond active range but not mandatory. Specification may
be de-rated outside of active range.
For interleaved imaging, the PPS is able to jump between any two output voltages in less
than 800us (in active range). Interleaving may occur at up to a 60Hz rate. A minimum of
time (about 15 percent) is spent changing output voltages, leaving 85% available for
transmitting and receiving ultrasound information. To accomplish this, the PPS must
source and sink approximately 26A for 1ms, far in excess of its "long term" current limit,
repetitively at up to a 60Hz rate.
The PPS input is of 340VDC. All switching of the PPS is synchronized to an external clock.
Power down the system completely before setting the switch for the OEM power outlet.
Digital
2.5V 3.3V 5.1V 5.1V Stdby 12V 12V_Per Fan
(5V) (5V)
CP x x
Fan Tray x
FPD x x
Gel Warmer
MBM x x x x
MPI x x x
PPM x
RAD x x x
TRB0 x x x
TRB1 x x x x
TRB2 x x x
TRB3 x x x
Clean
-106V -12V -5.7V 2.3V 5.5V 13V 106V
MPI x x x x x x
RAD x x x
TRB0 x x x x x x
TRB1 x x x x x x x
TRB2 x x x x x x
TRB3 x x x x x x
PPS Accessory
Vxmt
MPI x
TRB2 x
TRB3 x
Gel Warmer x
Accessory Outlets x
1. From the Imaging Screen, put the mouse over the wrench icon in the upper-right-
hand corner. From the menu, select Service Portal. The service Authentication win‐
dow appears. Log in to the Local Service screen.
Fig. 23: syngo Service Login Screen
2. Enter the service access key and click OK. The Service access key is a 20-digit alphanu‐
meric password. The first 14 digits are placed in the first field and the last six are
placed in the second field. Clicking the Set as Default box will save only the first 14
digits upon reboot. The final six must be entered manually after each entrance to the
local service page. If the Set as Default box is not checked, the entire access key must
be re-entered on reboot.
5. The Transducer Warning Message appears reminding the user to remove any trans‐
ducers from the ACUSON SC2000 system prior to running any diagnostics. Click OK on
the message to continue.
Fig. 26: Transducer Warning Message
6. The Legacy TestTools window allows access to higher level FRU tests, including the E
Module board level tests (transmit, receive, memory and power supply), Control Panel
test (control panel button and self test), and Power Supply (PSM) test. In addition, it
allows access to conduct a System Level Diagnostics and Confidence Check.
Fig. 27: Diagnostic Selection Window
7. Select the appropriate test by clicking the desired box(s) and click Start to run the
tests. An Estimated Time counter shows the approximate time needed to complete
each diagnostic test. The counter will count down during the tests.
Fig. 28: Legacy Diagnostic Selection Window
8. The system will automatically check to see if imaging is turned off. If not, the system
will switch off imaging. A message will be shown in the bottom left corner of the win‐
dow indicating that imaging is shutting down. The test(s) selected will then proceed
automatically, and the time counter for the test will begin.
Fig. 29: Diagnostics -- Shutting Down Imaging
Some test timers may not accurately display remaining test time. For example, the timer
may count down to zero, then reload to 1:58 and continue the countdown. This cycle
might continue again. This will be fixed in later SW revisions.
9. After the tests are completed, scroll to the bottom of the scroll box and check the sta‐
tus of the tests.
Fig. 30: Legacy Diagnostic Selection Window - Check Status Shown
10. If the test fails, a Test Execution Summary of the failure can be reviewed by clicking
the Details button at the bottom of the window.
Fig. 31: Test Execution Summary Window
1. In the upper right corner, select Reports. This will display the Report Files page.
2. Click Test Results to display a directory of results.
3. Find and click Test Results.htm in the Hierarchal listing to show a detailed report
of the test, which may be used for further troubleshooting.
4. If multiple TestResults.htm items appear in the log, use the date and time to de‐
termine which summary is the most recent.
If the E Module test or any of the board tests fails, scroll through the test results to iden‐
tify which module/board is the root cause.
If the first time the user clicks on the Summary File rather than the Test Results file, due
to the sync issue, the Summary File may not be found. Select the Test Results file first,
then select the Summary File. The Summary File will be displayed properly.
A total of 10 Test Report files will be maintained -- five with details in html format, and
five in summary. If a new test report arrives, the oldest file will be automatically re‐
moved. Those Test report files are included in SaveLog under \SaveLog\ServiceDiagRe‐
sults.
In rare cases, the Test Summary may not be found. This is due to a delay in generating
the report file when it is large. If that happens, just wait for a few minutes, then select
the Test Summary.
6. To shutdown the system, click the Shutdown System button. To restart the system,
click Restart System.
Fig. 32: Test Execution Summary -- Shutdown and Restart Buttons
The Voltages and Temperature of internal components can be tested using this window.
The following components can be tested:
n Power Supply Module (PSM)
n RAD Board
n TRB Boards
n MPI Board
n PPM
n Control Panel
Do not select ALL TRBs at one time. Selecting all will yield errors. Select TRB 0, 1, and/or
2, only.
3. The test will start, and the Total Time of the test as well as Remaining Time will be
displayed.
4. At the completion of the test, the test results (PASS/FAIL) will be displayed in the Re‐
sult: field at the bottom of the page.
5. To see details of the test results, click the Details button. The Test Execution Sum‐
mary window will be displayed.
Fig. 34: Power and Temperature Monitor Test Summary Screen
Note that previous results can be chosen so that current results can be compared with
past values, to note trends or discrepancies.
Note: Due to the limitation of the test script, if the test failed at the first attempt, this
could be a false failure. In case the test failed at the first attempt, perform the test again.
If it fails again, this will be a true failure.
This section describes what board or part is tested when a particular Diagnostic Test is se‐
lected. Also, minimum hardware required for each test is provided.
This test requires the RAD board, thee (3) TRB boards, four (4) MPE boards, and MPI board
installed.
MPI Interface
The test starts with initialization of the MPI FPGA to set it to acknowledge state. RX tests
on MPE calnode for RX gain for all channels; then it runs the TX tests on MPE for all chan‐
nels; then it obtains the MPI P/N.
MPI Memory
The MPI Memory test starts with initializing the MPI, then tests the MPI Data Bus and Reg‐
isters.
MPI Ref/Power
The MPI Ref/Power test starts with the initialization of the MPI, then displays the fix Volt‐
age; displays the switched Voltage; displays the switched Voltage of MP1/2/3, and dis‐
plays the temperatures.
TRB Transmit
TRB Transmit test starts with a check to see if the TRB 0/1/2 board is installed or not. If
installed, the test then runs the TRB analog transmit test for the TRB in that slot number. .
TRB Receive
TRC Receive test starts with a check to see if TRB 0/1/2 board installed or not. If installed,
the test then runs TRB analog B mode receive gain test for each channel for the TRB in
that slot number.
The TRB Receive Test also tests the analog Doppler signal Receive path from the TRB to
the RAD South. This test uses MPE cal node, and TRB0 channels 4 to 63; TRB1 channels 64
to 127; TRB2 channels 128 to 191.
TRB Memory
The TRB Memory test starts with a check to see if TRB 0/1/2 board is installed or not. If
installed, the test then runs TRB RAM test for the TRB in that slot number.
TRB Ref/Power
TRB Ref/Power test starts with a check to see if TRB 0/1/2 board is installed or not. If instal‐
led, the test then runs TRB voltage monitor and temperature monitor test for the TRB in
that slot number. Voltage and then temperature are checked against low/high limits.
RAD Memory
RAD Memory test starts with checking to see if TRB 0/1/2 board is installed or not. If instal‐
led, then the test runs forced diag initialization, then it tests RAD South and North.
RAD Ref/Power
RAD Ref/Power test starts with a check to see if TRB 0/1/2 board is installed or not. If in‐
stalled, the test then runs RAD South voltage monitor and temperature monitor test, then
RAD North voltage monitor and temperature monitor test. Voltage and temperature are
checked against Low/High limits
4.2.2 SignalPathControl
SignalPathControl tests requires that a RAD board, four (4) MPE boards, an MPI board, and
all lower numbered slots have TRB(s) installed.
Fig. 37: SignalPathControl Screen
The tests are structured from the most basic to most complex. Select the test(s) to exe‐
cute. Execution of tests will be carried out starting with the most basic test in the selec‐
tion, but not necessarily in the order of selection.
While executing the selected chain of tests, the system will stop the execution of the test
when a first failure is reached and the results will be reported.
4.2.3 EnhancedSignalPath
EnhancedSignalPath adds additional interactive tests, and provides a detailed interactive
location of failures.
To run these tests effectively requires some knowledge of hardware; test cases can be in‐
terdependent and a specific test sequence is required.
To use the Enhanced Signal Path UI, it is important to note with following:
1. Since the flow of control is from left to right in the diagram above, the boards need to
be tested in order from left to right.
This statement is true for ( Fig. 39 Page 69). For the actual UI, the flow is right to left.
2. It is important to note that the FPGA on the MPI board controls upstream communica‐
tion. Failure in the MPI (FPGA) may give the appearance of Rx/Tx failure on the TRB’s.
The MPE board very infrequently fails.
Fig. 40: Enhanced Signal Path Test Order Sequence
Usually if any partial board test fails the board needs to be replaced; however, in case of a
Control Panel (CP) failure, check cabling.
In case of RAD failure, if the RAD and everything below fails, the root cause is likely to be
the mother board or the RAD.
In case of TRB’s failure, run the tests in the order indicated in ( Fig. 40 Page 70).
n If tests in Block 1 fail, replace the specific TRB.
n If tests in Block 2 fail, replace the specific TRB.
n If tests in Block 3 fail, replace the specific MPI.
n If tests in Block 4 fail, replace the specific TRB.
The Transducer Diagnostic tests the health of the 4Z1c Transducer. The diagnostic tests
for array healthiness and coolant status for the transducer. A report is generated and in‐
cluded in the Savelog.zip file. The transducer can be checked remotely.
The test reports can be used for comparison, and only the same type of test can be used
for comparison. The test reports are named with "PS" for Port Selection,"DE" for Dead Ele‐
ments, and "CS" for Coolant Status.
The Transducer Diagnostic tests can only be performed on an MPI5 board. If the system
does not have the MPI5 board, (MPI5 Board M/N 10434283 is included in the Service
Spare Part M/N 10040600 rev. 08) these diagnostic tests cannot be performed. The MPI5
board has been implemented in forward production since January 19, 2010.
Each 4Z1C Dead Elements Test and Coolant Status Test will run for about 30 minutes,
and there is no "Abort" status available during the test. Do NOT switch off the system
during the transducer test!
Z6Ms Transducer Diagnostics Tests provide Dead Element, Power, and Pulse Echo testing.
This test menu also includes the ability to perform a Firmware upgrade to the transducer
if required.
Ensure that the transducer element head is clean before performing the tests. Gel or any
other material will cause false failures.
Test Procedure:
Only one (1) of the tests can be performed at one time. The system must be rebooted
between tests.
6. Click Start.
7. When the test is complete, the results will be displayed (Pass or Fail).
Fig. 49: Result: Pass or Fail
The Dead element Testing, Power Testing, or Pulse echo Testing cannot be tested in se‐
quence. The system requires a boot between each test.
1. Place a USB Flash Drive in one (1) of the Control Panel USB ports.
2. Click Details, and then click Save. The Save dialog will be displayed.
Fig. 50: Details > Save
3. Click Save As from the Save dialog drop down button. A Windows Explorer menu will
be displayed.
4. In the Windows Explorer menu, navigate to the USB Flash Drive and click Save.
Fig. 52: Windows Explorer > Save
Passive Transducer Diagnostics can be used to test every transducer in the system with
the exception of the 4Z1C and Z6Ms transducers. This test can also be performed remote‐
ly.
Passive Transducer diagnostics are available on systems at VB10C and higher with a Level
7 Service Key.
Ensure that the transducer element head is clean before performing the tests. Gel or any
other material will cause false failures.
Test Procedure:
1. Attach a transducer.
2. Remove all other transducers.
3. Clean the element head.
4. Click the connected port (Left Port [MP-1], Middle Port [MP-2], or Right Port [MP-3]).
5. Click Clean lens.
6. Type the transducer serial number.
7. Click Start.
8. When the test is complete, the results will be displayed (PASS or FAIL).
9. Click Details for complete diagnostic information.
10. When testing is complete the test results can be saved to a USB Flash Drive.
1. Place a USB Flash Drive in one (1) of the Control Panel USB ports.
2. Click Details, and then click Save. The Save dialog will be displayed.
Fig. 54: Details > Save
3. Click Save As from the Save dialog drop down button. A Windows Explorer menu will
be displayed.
Fig. 55: Save Dialog > Save
4. In the Windows Explorer menu, navigate to the USB Flash Drive and click Save.
Fig. 56: Windows Explorer > Save
In case any hardware failure is suspected, run the Power Temp Tests first to get a rough
idea where the failure might be, then run the EnhancedSigalPath test and the FRU Isola‐
tion test to narrow down the problem..
In case of persistent fan noise problem, check the hardware temperature sensor status.
Refer to ( Appendix G: Service Tools / Page 138).
(For SW Version 3.0 and above) Temperature Monitoring provides a graphical means to
monitor temperatue trends in various system items.
This page generates a graphical representation of the temperature of different boards
(TRB0, TRB1, TRB2, TRB3, RAD, MBM, MPI, PSM, CP) in the SC2000 system.
There are dropdowns to choose the board and dates for which the data is available. The
data is obtained from parsing the “SystemThermalLog_xxxxxx.csv” file in the location “C:
\Ddt\log”. The file gets updated every three (3 ) seconds. The graph shown is an averaged
out value for the entire data available for that day. There will not be any display of graphs
if the files are missing or corrupted.
(For SW Version 3.0 and above) This window is similar to the Temperature Monitoring
window. Here it shows the fan speed in RPM by parsing the log file “SystemFanSpee‐
dLog_xxxxx.csv” in the location “C:\Ddt\log”. The graph shown is an averaged out value
for the entire data available for that day. There will not be any display of graphs if the files
are missing or corrupted.
The Service Log provides a list of important events which have occurred on the system.
The most recent events are at the top of the list.
This window parses the file “C:\Ddt\log\HwSysServiceLog.log” and shows them in a tabula‐
ted manner. A component in the background runs periodically collecting and processing
different log files and dumps it to this log file. It gives the Service Engineer notice of any
board failures, temperature spike, system health, or any other imminent failure. There
will not be any display of tables if the files are missing or corrupted or empty.
This is a “read-only” list, in that it does not provide a method to click an item and see
details or to open an individual log.
5.1.1 Overview
Use the following table to decode error messages, which are of the format: UsAcquisi‐
tionHw_xx_yyyy.
1 PacCwOverloadEr‐ This error log indicates a fault con‐ PAC faults can be caused by faulty
ror dition for 4Z1c transducer when transducers (bad PAC or channel
the CW transmit voltage exceeds a shorts), faulty system power supply,
check value produced by a redun‐ or faulty MPI. Verify that the problem
dant voltage regulator. recurs in a transducer known to be
good. If it does, run power supply di‐
agnostics (PSM smb monitor test) and
MPI diagnostics (MPI smb monitor
test).
2 PacPwOvervolta‐ This error log indicates a fault con‐ PAC faults can be caused by faulty
geError dition for 4Z1c transducer when transducers (bad PAC or channel
the PW transmit voltage exceeds a shorts), faulty system power supply,
check value produced by a redun‐ or faulty MPI. Verify that the problem
dant voltage regulator. recurs in a transducer known to be
good. If it does, run power supply di‐
agnostics (PSM smb monitor test) and
MPI diagnostics (MPI smb monitor
test).
3 PacPwPowerLimi‐ This error log indicates a fault con‐ PAC faults can be caused by faulty
tError dition for a 4Z1c transducer when transducers (bad PAC or channel
the PW power dissipation exceeds a shorts), faulty system power supply,
limit threshold. or faulty MPI. Verify that the problem
recurs in a transducer known to be
good. If it does, run power supply di‐
agnostics (PSM smb monitor test) and
MPI diagnostics (MPI smb monitor
test).
5 PacPwPowerSup‐ This error log indicates a fault con‐ PAC faults can be caused by faulty
plyHeadroomError dition for a 4Z1c transducer when transducers (bad PAC or channel
the system-generated Vpps is too shorts), faulty system power supply,
low to support the programmed PW or faulty MPI. Verify that the problem
transmit voltage. recurs in a transducer known to be
good. If it does, run power supply di‐
agnostics (PSM smb monitor test) and
MPI diagnostics (MPI smb monitor
test).
6 PacMultipleErrors This error log indicates multiple si‐ PAC faults can be caused by faulty
multaneous fault conditions occur‐ transducers (bad PAC or channel
ring in a 4Z1c transducer. shorts), faulty system power supply,
or faulty MPI. Verify that the problem
recurs in a transducer known to be
good. If it does, run power supply di‐
agnostics (PSM smb monitor test)
and MPI diagnostics (MPI smb moni‐
tor test).
8 RadVxtSoftware‐ This fault occurs when the upper 8 This fault would most likely indicate a
Fault bits do not match the complement s/w fault. Otherwise the RAD would
of the lower 8 bits of a VXT DAC be the most likely FRU.
register write and the VXT DAC
Fault Mode bit is 0 (Diagnostic Reg‐
ister). This condition will also write
all zeros the VXT DAC. This bit is
cleared once the fault condition has
been removed.
9 RadVxtDacHard‐ This fault indicates a difference be‐ This fault would indicate a RAD board
wareFault tween VXT DAC and VXT Redundant problem.
DAC that is greater than approxi‐
mately 200mV.
Hardware prob‐ 13 MpiHwError The software has encountered an Replace the MPI board. Save error
lems error while programming the MPI logs and provide to factory.
hardware.
14 TrbHwError The software has encountered an Replace the TRB board. Save error
error while programming the TRB logs and provide to factory.
hardware.
15 AcdHwError The software has encountered an Replace the ACD board. Save error
error while programming the ACD logs and provide to factory.
hardware.
16 RtcHwError The software has encountered an Replace the RAD board. Save error
error while programming the RTC logs and provide to factory.
hardware.
Imageformer 17 ifHwError The software has encountered an Replace the RAD board. Save error
hardware prob‐ error while programming the IF logs and provide to factory.
lem hardware.
19 TscHwError The software has encountered an Replace the RAD board. Save error
error while programming the TSC logs and provide to factory.
hardware.
20 PebHwError The software has encountered an Replace the RAD board. Save error
error while programming the PEB logs and provide to factory.
hardware.
Power supply 21 PpmHwError The software has encountered an Replace the PPM board. Save error
problem error while programming the PPM logs and provide to factory.
hardware.
DSP error mes‐ 28 RtcError An error has been encountered in Run diagnostics on the associated
sages (often an the RTC. This error could be attrib‐ hardware. Save error logs and return
imageformer uted to hardware problems associ‐ them to the factory.
stall) ated with the RAD board, TRB's,
MPI, voltage supply PPS, or back‐
plane connectivity. This error could
also be attributed to software is‐
sues such as logic errors, timing er‐
rors, or protocol errors.
Probe errors 30 ProbeIdStatusTi‐ This situation occurs when the soft‐ If the situation occurs continuously,
meout ware times out waiting for re‐ then run diagnostics associated with
sponse on read back of transducer the MPI board.
port status information. This situa‐
tion is expected to occur with some
transducer port and user transducer
selection scenarios. If the problem
occurs continuously, then this
could indicate a problem with the
MPI board.
32 PrototypeProbe This log indicates the transducer in Take this information into account
use had a serial number that indica‐ when analyzing other errors associ‐
ted it was considered a prototype ated with this transducer.
for this release of software.
33 ProbeEmThermal‐ This situation is reported when the Run PSM diagnostics to verify 12V
Fault fixed temperature threshold is ex‐ dirty power supply is working proper‐
ceeded within the electronics mod‐ ly. Perform Cooling diagnostic test on
ule of the 4Z1C. This situation may transducer.
indicate a problem with the cooling
mechanism of the transducer.
34 TeeHomingError This log indicates that the system If no other answer is available: Test
was unable to home the TEE probe probe with all three ports of system.
or verify that the transducer homed Test system with known-good probe
correctly. and/or test probe on another system
to isolate whether probe or system is
at fault. If system fault is suspected,
run diagnostics associated with the
MPI board.
35 ProbeFixedTher‐ This situation is reported when the Run diagnostics associated with RAD
malFault fixed temperature threshold is ex‐ board and MPI board.
ceeded at the transducer lens or ar‐
ray. The system response to the
lower, programmable threshold
should prevent this situation from
occurring, so under normal condi‐
tions this situation should not oc‐
cur. If this situation does occur, it
indicates a possible problem with
hardware (RAD or MPI boards) or
with system software programming
or operation.
37 ProbeThermal‐ This situation is reported when the If the log is occurring more frequently
Pause programmable temperature thresh‐ than expected, then run the cooling
old is exceeded at the transducer diagnostic test on the transducer.
lens or array. This situation is ex‐
pected to occur under normal oper‐
ating conditions when the trans‐
ducer is imaging in air. If the log oc‐
curs more frequently than expec‐
ted, then that may indicate a prob‐
lem with the transducer cooling
mechanisms.
6.1 Overview
This section provides the current BIOS Settings for the ACUSON SC2000 system. Two (2)
sections are included - one for BIOS Settings for systems with an MBM200, and one for
systems with an MBM3.
To enter BIOS, perform the following steps:
1. Power cycle the system and wait until three (3) faint beeps coming from the MBM are
heard.
For the MBM3, these beeps occurs approximately 67 seconds after the power button
on the control panel was pressed.
For the MBM200, these beeps occurs approximately 18 seconds after the power but‐
ton on the control panel was pressed.
2. Press the <F2> key every two (2) seconds, three (3) or four (4) times. Wait for the
splash screen time out to occur (the splash screen timer is set to 300 seconds). The
BIOS window will be displayed.
3. At the top of the BIOS screen, the Menu tabs are located. Use the tab key to navigate
to the various menu tabs. Use the up/down arrows to navigate to menu items in each
menu tab.
4. Use the “+ / -” keys to change the value of an item.
5. Press <ENTER> to select a field.
6. Press <F10> to Save and Exit.
6.2.1 Main
6.2.2 Advanced
6.2.3 Security
Boot Option #4 [[Internal EFI Set system boot order by selecting the boot op‐
Shell ]]] tion for this position.
Network Device
Order
Hard Disk Order
CDROM Order
Add EFI Boot Op‐
tion
Delete EFI Boot
Option
6.3.1 Main
6.3.2 Advanced
PCI Configuration
Memory Mapped [2.50GB] Select the start of the reserved memory region
I/O Start Address for memory mapped I/O space that ends at
4GB.
Warning: Depending on the system configura‐
tion, this option may impact the amount Sys‐
tem memory detected by an OS without Physi‐
cal Address.
Extension (PAE) support.
Memory Mapped [Disabled] Enabled or disable memory mapped I/O of 64-
I/O above 4GB bit PCI devices to 4GB or greater address space.
Audio Device [Enabled] Onboard audio controller.
Onboard NICI ROM [Enabled] Load the embedded option ROM for the on‐
board network controller.
Warning: If [Disabled] is selected.NIC1 can not
be used to boot or wake the system.
Onboard NIC2 [Enabled] Load the embedded option ROM for the on‐
ROM board network controller.
Warning: If [Disabled] is selected.NIC2 can not
be used to boot or wake the system.
NICI MAC Address [00xxxxxxxxxx]
NIC2 MAC Address [00xxxxxxxxxx]
System Acoustic and Performance Con‐ View/Configure system acoustic and perform‐
figuration ance information and settings
Throttling Mode [Closed Loop] Open Loop does not reply on a thermal sensor
on the board and sets up a static level which
equates to a fixed bandwidth.
Closed Loop will allow the system to achieve
higher performance by monitoring System
temps and adjusting bandwidth.
Set Fan Profile [Performance] [Performance] - Fan control providers primary
system cooling before attempting to Throttle
memory.
[Acoustic] - The system will favor using throt‐
tling of memory over boosting fans to cool the
system if thermal thresholds are met.
Altitude [301m - 900 m] [300m or less] (900ft or less) Optimal perform‐
ance setting near sea level.
[301m - 900m] (900ft - 2950 ft) Optimal per‐
formance setting at moderate elevation.
[Higher than 900m (Higher than 2950 ft) Opti‐
mal performance setting at high elevation.
6.3.3 Security
6.4.1 Prerequisites
n BIOS_MBM200_0.0.7 DVD disk (BIOS Version 30)
n Blank USB thumb drive
n MBM200 system.
NOTICE
Boot Up Problems May Occur
Ensure all external USB devices are removed from the system before going in‐
to the BIOS window.
a) Power cycle the system when beeps from the MBM module are heard, tap the F2
key every couple of seconds for at least 10 seconds. Wait for the splash screen to
go away, and the Intel BIOS setup window to be shown.
This may take up to five (5) minutes for the splash screen to go away and the BIOS
window to be shown.
b) Tab over to the Boot Option and make sure Boot Option #1 is set to Matchi‐
taDVD-RAM or TEAC BD-W26ss...
c) Ensure that Boot Option #2 is set to “P2: INTEL SSD...” or “P2: KINGSTON
SVP100S29...”.
e) Press F10 to save the settings, press F10 again, then click Save Changes and Exit.
The system will reboot to imaging after save and exit.
It will take several minutes for the system BIOS flash to complete after the reboot.
4. A message will be displayed indicating that the BIOS will be upgraded. Click Continue.
Fig. 68: BIOS Installation Message
5. A message will be displayed indicating that the BIOS version information is being re‐
trieved.
Fig. 69: Rerieving System BIOS Information
If booting from an MBM3 system, the installation will automatically be aborted and the
sytem will shut down.
6. If the system BIOS is already up-to-date, there will be a message indicating that the
user can proceed with installation or cancel. The BIOS installation MUST be run twice,
so ensure that this has been done. If not, continue with the BIOS installation.
Fig. 71: BIOS Version Already Up-to-date
7. If the system BIOS has a different version than one on disk (which is the latest BIOS
version), the installation will automatically run after 10 seconds.
Fig. 72: System BIOS is Different Version than on Disk
8. Insert a USB thumb drive in a USB port located on the right side of the control panel.
9. The BIOS installation will start. The installation takes approximately 10 minutes to
complete.
Fig. 73: BIOS Installation Starting
10. If the installation is successful, a message indicating successful installation will be dis‐
played.
Fig. 74: Successful BIOS Software Installation
7.1 Overview
This section provides keyboard shortcuts for the ACUSON SC2000 system.
Tab. 11 SC2000 Keyboard Shortcuts
8.1 Overview
When the Firewall is "On", the following network ID exceptions will need to be set, so that
remote service can access the ultrasound scanner or workplace.
The detailed exceptions IP and subnet mask information are:
n 194.138.36.80/255.255.255.240,
n 194.138.39.16/255.255.255.248,
n 194.138.243.176/255.255.255.248,
n 129.73.116.88/255.255.255.248,
8.2 Procedure
1. Open a Windows Explorer window by performing the following steps.
For ACUSON SC2000 System:
a) Select Local Service, or hover over the wrench icon in the upper, right corner, and
select Service Portal from the drop-down menu.
b) In the Service Portal main screen, enter the service key.
c) Click System Tools to expand the menu list.
d) Select Escape to OS.
e) In the Features dropdown box, select NT command Interpreter, then type Ex‐
plorer in the Parameters field. Click Execute.
a) On the computer keyboard, press the Windows key + e. The Window Explorer
window will open. (Note: The Windows key is located between the Ctrl and Alt
keys.)
b) In the Windows Explorer window, navigate to Control Panel. Click to open.
c) In Control Panel window, navigate to Windows Firewall. Double-click to open.
2. Confirm the firewall status.
3. In the Exceptions tab, scroll down the list to locate “Web Server (HTTP)”. Check the
box, if not checked, and then click Edit. The “Edit a Port” window will open.
Fig. 81: Exceptions -- Web Server (HTTP)
5. Check "Custom List", and add the exceptions according to the IP and subnet mask in‐
formation.
Fig. 82: Change Scop -- Custom List; Add Exceptions
9.1 Overview
In some cases, there is a problem and the Service Mode cannot be accessed normally. For
example, the system cannot boot to Imaging, and therefore, the Service Wrench icon
does not display. A service tool CD can be generated and used to bypass Imaging and go
directly to the Service Software page.
This procedure describes how to generate and use this tool, the US2003.dat disk.
9.2 Procedure
Perform the following steps to generate a US2003.dat disk.
1. Launch Notepad on the personal computer (laptop or desktop) using one of the two
methods below.
- From the Task Bar, navigate to Start > Programs > Accessories > Notepad.
- From the Task Bar, navigate to Start > Run. Type Notepad, and click OK.
2. When Notepad launches, create a text file with only one line: US2003.dat
3. Save this text file with the name "US2003.dat".
Fig. 83: US2003.dat Service Tool
The contents of the file are not important, only the name is important (US2003.dat).
Peform the following steps to use the US2003.dat service tool disk.
a) Align the unlocked position indicator and the arrow on the connector with the tri‐
angle on the Service ID Probe.
This tool checks the system’s hardware compatibility with the software version that is run‐
ning on the system and then displays the software and hardware confidence.
The following figures show how the result is displayed on a system. It displays green if
the hardware and software are supportive and compatible to each other. It displays red if
the installed hardware and software are not supportive or are incompatible to each other.
The FPD includes a microphone, located at the top center of the display. The FDP module
provides a fixed gain microphone pre-amplifier. The audio and sync connector is a shiel‐
ded RJ45 jack type. The audio and sync connector pin out are:
Pin 1 = TMDS 100KHz Clock+, for Clock sync to ultrasound system;
Pin 2 = TMDS 100KHz Clock- , for Clock sync to ultrasound system;
Pin 3 = No Connect;
Pin 4 = TMDS 16MHz Clock+ for Clock sync to ultrasound system;
Pin 5 = TMDS 16MHz Clock-, for Clock sync to ultrasound system;
Pin 6 = No Connect;
Pin 7 = Microphone, for Voice of ultrasound system annotation;
Pin 8 = Microphone Return, for return for microphone.
The FPD Power connector is a retained Moles 6-pin right angel Dual Row with PCB mount‐
ing. The voltage is DC 12V.
The pins are numbered in a clockwise rotation. Pin 1 is located at the top left, followed by
pin 2, 3, 4, 5 in the first row. The last one, which is located in the second row, right cor‐
ner, is pin 9.
11.1 Overview
There may be different causes for the system running slowly. Perform the steps in the fol‐
lowing sections to help speed the system’s response times.
a) Select Local Service, or hover over the wrench icon in the upper, right corner, and
select Service Portal from the drop-down menu.
b) In the Service Portal main screen, enter the service key.
c) Click System Tools to expand the menu list.
3. Drag the top window out of the way to display the Disk Defragmenter window behind
the top window.
4. Follow the on-screen commands to perform Disk Defragmentation.
a) Select Local Service, or hover over the wrench icon in the upper, right corner, and
select Service Portal from the drop-down menu.
b) In the Service Portal main window, enter the service key.
c) Click System Tools to expand the menu list.
e) In the Features dropdown box, select NT command Interpreter, then type Ex‐
plorer in the Parameters field. Click Execute.
2. Drag the top window out of the way to display the Explorer Window behind the top
window.
3. From My Computer, right-click Manage. The Computer Management window will
be displayed.
10. Confirm that the Current Transfer mode is "Ultra DMA Mode 5".
11. Click OK, then close all windows.
12. Exit the service mode.
12.1 Overview
The following error applies to ACUSON SC2000 Work Place, HP computers ONLY.
Problem:
Sporadically, the user is unable to log in to the Service portal of the ACUSON SC2000WP
HP computer. There is an error message displayed as shown in the figure below, or the
service portal window displays “Page cannot be displayed”. This is an intermittent issue.
Solution:
Reboot the system and log in as Administrator.
2. LAN1 is used for network connections, and LAN2 is used for CARTO communcation.
Use the LAN1 connection.
c) Select NT command Interpreter in the Features dropdown list, then type "Explor‐
er" in the parameters field, and click Execute.
d) Drag the top service window to the bottom to display the Windows explorer win‐
dow, and drill down to folder My Computer > Control Panel > Network Connec‐
tions.
e) Verify that there is a LAN1 connection listed. Note its device name.
13.2 Wireshark
Wireshark is a Network Protocol Analyzer than captures network traffic for analysis.
Fig. 105: WireShark
The new window may be displayed behind the existing windows. It may be necessary to
move the top windows so that the Wireshark window can be seen.
3. Click on the Protocols list in the left-hand pane of the Preferences dialog box.
4. Select TCP, from that list.
5. Turn off (deselect) the Validate the TCP checksum if possible: option.
Fig. 107: Wireshark – Network Protocol Analyzer: TCP Menu Window
The new window may be displayed behind the existing windows. It may be necessary to
move the top windows so that the new window can be seen.
Fig. 109: Wireshark – Network Protocol Analyzer: Capture Options Menu Window
Fig. 110: Wireshark – Network Protocol Analyzer: Capture Options Menu Window (IP Address)
10. Type host (lower case) followed by the system's IP address in the Capture Filter box.
Example: host 10.2.20.11
This will limit capture traffic to and from this system.
Use the lower case as indicated (host). "HOST x.x.x.x" will not work.
Fig. 111: Wireshark – Network Protocol Analyzer: Capture Options Menu Window (Capture Filter)
11. Place a USB memory stick drive into a Control Panel USB Port.
Fig. 112: User Interface USB Ports
13. Uncheck "Use pcap-ng format". This will allow DICOM Analyzers such as DVTk tools to
parse the capture file.
Fig. 114: Wireshark - Network Protocol Analyzer: Capture Options Menu Window (Uncheck Use pcap-ng format)
Wireshark Capture mode initiates and displays the Captured Packets window.
Fig. 116: Wireshark – Network Protocol Analyzer: Captured Packets Window (inactive)
19. After the system completes the image transfer, click Stop on the Wireshark Capture
Mode window.
Fig. 118: Wireshark – Network Protocol Analyzer: Captured Packets Window (Stop)
20. Click File > Save As, and save the capture to the USB memory stick drive. Type a Cap‐
ture File Name with a .cap suffix. For example, capture.cap. Click OK.
21. Remove the USB memory stick drive from the system and insert it into your computer.
Verify that the Wireshark .cap file is present.
14.1.1 Symptom
Check the following symptoms.
1. From the system display the following message may be seen during boot up:
Fig. 120: ACUSON SC2000 Process Monitor Error Message
2. From the rear of the system, the red LED may stay lit on the lower half of the RAD
board (south side).
3. To confirm, check the ODT log to see whether it has any indication of a RAD board
issue or not.
4. The ODT log file is located under C: \Store\log\. Look for the most current Log file fold‐
er, and locate the current ODT_Log.
Fig. 121: ODT_log
If the RAD board was not initiated, the ODT log indicates an error on opening the driver
handle for PEB, RTC and TSC FPGA.
INFO: Running as a service.
INFO: service_main(), TS: 47656
INFO: httpTask [enter], TS: 47703
TIMESTAMP: Wed Jan 11 15:58:45 2012
Unable to open the Ultrasound driver handle for PEB in attepm = 1 at tick: 47765
Unable to open the Ultrasound driver handle for PEB in attepm = 2 at tick: 48765
Unable to open the Ultrasound driver handle for PEB in attepm = 3 at tick: 49765
openUltrasoundDriverHandles -- Error on: PEB bar 0
Unable to open the Ultrasound driver handle for RTC in attepm = 1 at tick: 50765
Unable to open the Ultrasound driver handle for RTC in attepm = 2 at tick: 51765
Unable to open the Ultrasound driver handle for RTC in attepm = 3 at tick: 52765
openUltrasoundDriverHandles -- Error on: RTC bar 0
Unable to open the Ultrasound driver handle for TSC in attepm = 1 at tick: 53765
Unable to open the Ultrasound driver handle for TSC in attepm = 2 at tick: 54765
Unable to open the Ultrasound driver handle for TSC in attepm = 3 at tick: 55765
Exception in httpTask
Closing log file
5. Also, check the Device Manager to determine if the ACUSON SC2000 system sees the
RAD board through the PCT-E express bus or not.
If the PEB FPGA, RTC FPGA and TSC FPGA can be seen, the RAD board is OK.
Fig. 122: RAD Board OK
If the PEB FPGA, RTC FPGA and TSC FPGA cannot be seen, the RAD board is corrupted.
14.1.2 Cause
When installing or re-installing the system software, some firmware may need to be re‐
loaded to boards. If the system was powered off during the RAD firmware reloading, it
will cause corruption on RAD board
14.1.3 Action
When it has been confirmed that the RAD board has been corrupted, replace the RAD
board.
14.2.1 Symptom
When accessing the AutoReport, a "Permission denied" error will be seen.
Fig. 124: Maintenance Menu Items
14.2.2 Cause
The AutoReport Message ID field should not have more than 10 digits. If it has 11 digit sor
more, the "Permission denied" error will be displayed.
14.2.3 Action
If the error happens, perform the following steps:
5. Drag the top service window to the bottom to display the Windows explorer window,
and drill down to folder:
C:\Program Files\Siemens\syngo\OperationalManagement\Autoreport\work
Fig. 130: Report (.rcf) File -- 0KB File Size
14.3.1 Symptom
The picture below shows that with the 9L4 transducer, the right side of the image is dark‐
er, which indicates that the TRB may have problem. Since the yellow "A", which indicates
the TRB0 board, is located at left side of image, there is a possibility that TRB2 is failing.
Fig. 131: 9L4 Transducer Shown
14.3.2 Cause
TRB board may be defective, not seated properly, or the backplane board may have issues
with its connectors.
14.3.3 Action
Re-seat the boards, and/or move the TRB to different slots.
If the problem persists with the same slot, it indicates the problem is with the backplane
board.
If the problem appears to persist with the TRB board, run TRB diagnostics and replace the
defective board if it is necessary.
14.4.1 Symptom
Error is seen on P3V3 voltage when running the Service Diagnostics for PPM (Patient
Physio Module).
14.4.2 Action
Run the test again to confirm a real failure within the same boot cycle. If no failure oc‐
curs, then it is deemed to be the false failure.
14.5.1 Symptom
The DVR Unit Front Panel buttons are locked when the DVR UI is invoked the very first
time. Only certain keys like Power, Media and Eject button would work.
14.5.2 Cause
This was the Key Inhibit requirement. The keys are inhibited because if the user presses
the keys on the unit directly, the UI and the DVR could be out of sync. There is no firm‐
ware setting to not do the Key Inhibit as the command is being sent from the Software.
When the DVR is restarted the Key Inhibit is reset and the invoking of the UI again would
inhibit the keys.
14.5.3 Action
This was for initial installation.. Once that is done all the required functionalities can be
accessed from the UI for daily use, without the need to access the front panel of the DVR.
14.6.1 Symptom
The "HWSyscooling" was working in VA20A, but is does not work in VA20C and VA30A.
14.6.2 Action
To display the “HWSyscooling”, use the following steps as a workaround.
4. Select Bedrock Shell from the Features dropdown menu, then click Execute. A DOS
window will display..
5. Type ShowSC2000Desktop and then press Enter.
6. Reboot the system.
7. Enter the Service Mode again, and navigate to System Tools > EscapeToOS.
8. Select Bedrock Shell from the Features dropdown menu, then click Execute. A DOS
window will display.
9. Type cmd in the DOS window.
10. Type c:\Ddt\bin\HwSysCooling.exe, then press Enter. The HW System Cooling
Status will be shown.
11. After evaluation, enter the Service Mode again, and navigate to System Tools > Esca‐
peToOS.
12. Select Bedrock Shell from the Features dropdown menu, then click Execute. A DOS
window will display.
13. Type HideSC2000Desktop, then press Enter.
14. After script executes, the system will automatically shut down.
15. Power on the system. It will boot directly to Imaging.
When a user clicks the icon, a pop-up message will appear providing more details about
the incident.
Fig. 136: Message Minder Message Window
16.1 Overview
If an external monitor is going to be used on a system with a Kortek Monitor, then an
HDMI to DVI converter will need to be installed.
If this converter is not used, the auxiliary monitor may display only a black screen, or may
display a blurry and broken image, or it may display a diagnostic message about an in‐
compatible video format.
The recommended engineering-approved converter is HDMI to DVI+Digital Audio Con‐
verter: Model 1312, manufactured by Audio Authority.
The converter is not a spare part and cannot be ordered. It will need to be purchased.
The HDMI to DVI converter is not required for systems with an EIZO monitor.
1. Install the HDMI cable to the HDMI output of the I/O Module, and plug the cable into
the HDMI to DVI Converter.
2. Install the DVI cable to the output of the HDMI to DVI Converter and plug the DVI cable
to the auxiliary monitor DVI Input.
Fig. 138: HDMI to DVI Cable Connections
17.1 Overview
There are vertical artifacts in color doppler with 4V1c and 4Z1c transducers connected,
visible in the image when the J45 network cable is connected
To fix this, a Ferrite Core needs to be attached to the J45 network cable.
18.1 Overview
The MBM200 module performs a major role in the functionality of the ACSUON SC2000
system. There are LED indicators located in the back of MBM200, which are visible after
removing the rear plastic cover. These LEDs provide indications of the health of the sys‐
tem.
The following figure shows what the LED normal conditions are with the power on.
At Standby, no LED light will be on, but the power button on the control panel will be lit.
Fig. 140: MBM200 LED - Standby Status
19.1 Overview
There are multiple causes for problems with DVD drive functionality. The failure reasons
vary from a simple cable misconnection to control panel issues. The following procedure
is designed to help isolate faulty parts associated with DVD drive functionality.
19.2 Troubleshooting
Perform the following initial steps to isolate DVD Drive issues:
19.2.3.1 Workflow
700MB CD media
4.7GB formatted single layer DVD –R media
8.5GB dual layer media/DVD +R
1. Press the Power button on the Control Panel to power off the system.
2. Select OK to shut down the system, wait for the system to power down completely.
3. Switch the Main Circuit Breaker to the OFF position.
4. Disconnect the system power cable from its external power source.
5. Ensure the wheel locks are in the locked position.
6. Maintain a minimum of 3.5 feet (1 meter) clearance while working on the system.
WARNING
The system contains hazardous voltages that can range from 90 VAC to 264 VAC
and cause serious injury or death.
Only authorized service personnel are permitted to remove protective covers
and access the energized components of this system.
19.2.3.6 Procedure
2. Loosen the four (4) captive screws which secure the Control Panel Assembly to the
Control Panel base.
Fig. 142: Control Panel Attachment Screws
3. Lift the Control Panel Assembly up, supporting the Control Panel Assembly with one
(1) hand. Remove the cables from the underside of the Control Panel Assembly.
Fig. 143: Control Panel Assembly Being Removed
4. Unplug the square USB cable from the DVD Drive and replace it with the long USB ca‐
ble
Fig. 144: Control Panel DVD Drive Connection
5. Pull the replacement USB cable out so it extends from the front of the system, and
then gently place the Control Panel Assembly down.
Fig. 145: DVD Drive USB Cable Extended out of Control Panel
8. Perform the following tests on the Siemens laptop. This will test DVD Drive functional‐
ity. If the DVD Drive passes all tests, the problem might originate from the Control
Panel or software.
DVD or CD medias ejec‐ 1. Open Windows Explorer on the lap‐ No error occurs Pass
tion test top.
2. Right clink the DVD/CD icon, select Fail
Eject to check if the DVD drive’s basic
handshake with laptop is functional.
Single layer DVD Writ‐ Copy minimum 10MB image data from No error occurs Pass
ing Test HDD to a 4.7GB formatted single layer
DVD –R media
Fail
Dual layer DVD Writing Copy minimum 10MB image data from No error occurs Pass
Test HDD to 8.5GB dual layer media/DVD +R
Fail
CD media Writing Test Copy minimum 10MB image data from No error occurs Pass
HDD to a 700MB CD media.
Fail
3. In the Service Portal main window, log into Service. Enter the service key, then click
Login.
4. Click System Tools.
5. In the dropdown menu, click EscapeToOs.
6. In the Features dropdown box, select NT command Interpreter, then type Explor‐
er ↵ in the Parameters field. Click Execute.
7. In the Windows Explorer window, navigate to My Computer.
8. Check the assigned ID for the DVD-RAM drive.
Fig. 146: My Computer > DVD-RAM Drive
2. Navigate to Storage > Disk Management. Select CD-ROM and click Change Drive
Letter and Path.
Fig. 148: Manage > Change Driver Letter and Paths..
4. Verify that the assigned DVD Drive ID has changed to E by navigating to Windows Ex‐
plorer and confirming the ID change.
20.1 Overview
Perform the following test to determine if there are any defective transducer elements.
20.1.1 Procedure
1. Prepare the ultrasound perfect reflection material (Knife or other metal).
2. Spread Ultrasound transmission gel over the elements.
3. Scan over the reflection material.
4. Check if there are any depleted strip images which are caused by the defective probe
elements.
21.1 Overview
If windows fail during boot, it may be necessary to remove the syngo splash screen and
view the error messages.
21.1.1 Procedure
1. As soon as a system boot-up starts, wait for (five) 5 second until the Siemens Logo
displays in the system.
2. At the same time, press the top + middle button on the left side of Korkek monitor for
10 seconds.
Change(s) Description
Revision 06 Updated BIOS information in Appendix D
Added Appendix F: Firewall Exceptions
Revision 01 Initial Release
healthcare.siemens.com/services
siemens.com/healthcare