www.spacelabshealthcare.com
5-22
91390
QUBE
TROUBLESHOOTING
System Software Failure Window Shown Immediately After
System Startup
If the monitor completes the System Startup sequence, but fails to
enter the user interface, it shows the System software failure.
Review error log for further details window. Refer to Figure 5-16.
Figure 5-16 System Software Failure Window
This failure is caused when the (internal) USB Flash Drive on the
Power Supply PCBA is corrupted or unformatted.
1 Access the Boot Menu (Refer to Figure 5-3). Select E - error log
functions...
2 Scroll through the errors. Find the system software failure entry.
If the error listed Refers to Directory /slh0/usr/apps/ not found
(Refer to Figure 5-17), the internal USB Flash Drive is corrupted.
Figure 5-17 Error Log Entry for System Software Failure
3 Return to the Boot Menu, and then choose f- format USB file
system. If the drive formats without errors, do a cold boot and
retest the system. Data stored in the internal Flash Drive is lost
during the format process, and must be reentered into the
monitor. This data includes any Customized Trends created in the
Clinical backend menu, and DNA™ (Citrix®) Application Server
certificates.
4 If the system still fails to boot, replace in order:
1 USB Flash Drive PCBA
2 Power Supply PCBA
3 CPU PCBA
This failure can also be caused when there is a version mismatch
between the app.bin and the fd_image.bin sectors of the Flash ROM
in the CPU. This only occurs during a software update by a
Spacelabs Healthcare Field Service Engineer.
1 Access the Boot Menu (Refer to Figure 5-3). Select E- error log
functions...
2 Scroll through the errors. Find the system software failure entry.
If the error listed refers to app.bin build ID does not match
information found in fd_image.bin (Refer to Figure 5-18), the
To Next Page
Loading...
