Patient monitors · Qube family

Spacelabs Qube Mini: troubleshooting and error codes

The ServiceForge knowledge base holds 24 documented symptoms for the Spacelabs Qube Mini, with 72 ranked causes, 48 diagnostic checks with test points and expected values, and 50 error codes. Each symptom below shows its causes and the first check; the rest is one connection away. Connect ServiceForge to your AI

Symptoms

Power-ON diagnostic test failure

One or more diagnostic tests fail during system startup; errors logged in System Startup screen upper portion

Ranked causes

1. CPU malfunction or communication error (unknown)
2. DRAM read/write failure (unknown)
3. Real-time clock not running (unknown)
4. GDS SRAM read/write failure (unknown)
5. Video memory or controller failure (unknown)
6. Ethernet register communication failure (unknown)
7. Flash memory checksum error (unknown)
8. Touchscreen controller failure (unknown)
9. Audio codec register failure (unknown)

First check

Access Boot menu during system startup

Test point: System startup sequence
Expected: Boot menu accessible before 4-3-2-1 countdown ends

1 more check with pass and fail actions, 9 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Barcode scanner, keyboard, printer, or mouse not functioning

USB peripherals (scanner, keyboard, printer, mouse) do not operate

Ranked causes

1. Barcode scanner not in keyboard entry mode (common)
2. USB peripheral defective (occasional)
3. USB connector on Interconnect PCBA damaged (occasional)
4. Interconnect PCBA failure (occasional)
5. CPU PCBA failure (rare)
6. SDLC PCBA failure (rare)

First check

Configure barcode scanner to keyboard entry mode

Test point: Barcode scanner settings
Expected: Scanner set to keyboard entry mode

2 more checks with pass and fail actions, 6 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Ethernet network link not functional

Monitor does not communicate on Ethernet network; green link LED not lit or not blinking

Ranked causes

1. Ethernet cabling or network switch malfunction (common)
2. Monitor Ethernet network configuration incorrect (occasional)
3. Interconnect PCBA Ethernet interface failure (occasional)
4. CPU PCBA failure (rare)
5. SDLC PCBA failure (rare)

First check

Verify green link LED on Ethernet connector

Test point: RJ45 connector LED
Expected: Green LED lit (link established) and blinking (network activity)

2 more checks with pass and fail actions, 5 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

POD does not sign on when installed in monitor

Patient observation device (POD) fails to establish communication with monitor

Ranked causes

1. +5 VDC supply to POD is absent (common)
2. SDLC communication link failure (occasional)
3. POD Interface Cable damaged or disconnected (occasional)
4. POD Interface PCBA failure (occasional)
5. CPU PCBA failure (rare)

First check

Connect known good POD to monitor and test sign-on

Test point: POD module bay
Expected: POD signs on and communicates normally

2 more checks with pass and fail actions, 5 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Touchscreen unresponsive

Display present but touchscreen does not respond to input

Ranked causes

1. Touchscreen requires calibration (common)
2. Internal touchscreen cable loose or disconnected (occasional)
3. Front-End LCD/Touchscreen assembly failure (occasional)
4. Wireless/Touch PCBA failure (rare)
5. CPU PCBA failure (rare)

First check

Calibrate touchscreen via Diagnostic or Biomed menu using mouse

Test point: Touchscreen calibration interface
Expected: Touchscreen accepts calibration input and responds normally after completion

1 more check with pass and fail actions, 5 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Unit powers on but fails system startup

ON/OFF switch illuminates and system begins startup but does not complete boot or reach user interface; display may be blank

Ranked causes

1. Flash ROM boot sector corruption (occasional)
2. NVRAM configuration corrupted (occasional)
3. System voltage out of tolerance (occasional)
4. Power-on diagnostics failure (occasional)
5. CPU PCBA failure (rare)

First check

Access Extended Diagnostics via touchscreen or mouse

Test point: Touchscreen/mouse input
Expected: Extended Diagnostics menu appears

6 more checks with pass and fail actions, 5 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Battery not recognized or fails to charge

Monitor does not detect battery presence or battery does not charge despite recognition

Ranked causes

1. Battery Connector PCBA physically damaged (occasional)
2. Battery defective (common)
3. SDLC PCBA failure (occasional)
4. CPU PCBA failure (rare)

First check

Inspect Battery Connector PCBA for physical damage

Test point: Battery Connector PCBA
Expected: No physical damage visible

1 more check with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

High-pitched tones heard and no display present patient safety

System emits two-frequency high-pitch tone (System Failure Alarm) with no visible output on display; alarm indicates loss of CPU communication or power supply fault

Ranked causes

1. Serial communication loss between main CPU and Always-On CPU (occasional)
2. Main CPU detected fault and triggered safety circuit (occasional)
3. Always-On CPU (power supply) detected fault and triggered safety circuit (occasional)
4. AC mains loss or battery depleted (common)

First check

Access error log for alarm trigger cause

Test point: Error log via Boot Menu
Expected: Error entry identifying CPU, Always-On CPU, or battery failure

4 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

Unit does not power on

AC-mains indicator does not illuminate when external power connected; ON/OFF switch does not illuminate when pressed; no startup sequence begins

Ranked causes

1. External power supply not functioning (common)
2. Power DC-IN cable failure (common)
3. SDLC PCBA input power circuits failure (occasional)
4. Power PCBA or CPU PCBA failure (occasional)

First check

Verify external power supply output

Test point: Power supply green LED
Expected: Green LED illuminates

2 more checks with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Power-ON self-test failure or incorrect LED behavior

Power button does not illuminate, AC mains LED not lit, battery LED off when battery present, or battery LED blinking at high rate

Ranked causes

1. Power supply not connected or connector loose (common)
2. Power jack defective or connector loose (occasional)
3. Battery cannot complete full charge cycle (occasional)

First check

Verify AC mains LED illuminates

Test point: Front bezel AC mains LED
Expected: Lit when plugged into AC power

3 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

System software failure window shown after startup

Monitor completes system startup sequence but fails to enter user interface and displays System Software Failure window with error details

Ranked causes

1. Internal USB Flash drive corrupted or unformatted (common)
2. USB Flash drive PCBA hardware failure (occasional)
3. CPU PCBA failure (occasional)

First check

Check error log for directory not found entry

Test point: Error log via Boot Menu, Directory /slh0/usr/apps/
Expected: Error entry '0x00fe0400: MonInit System software failure: Directory /slh0/usr/apps/ not found'

1 more check with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Boot menu access failure or display malfunction

Cannot access Boot menu during startup or display is non-functional; diagnostic information cannot be retrieved

Ranked causes

1. Countdown 4-3-2-1 completed before Boot menu key sequence entered (common)
2. Touchscreen display non-functional or unresponsive (occasional)

First check

Monitor display functional during power-ON countdown

Test point: Video output
Expected: 4-3-2-1 countdown visible on screen

1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

ECG module not recognized or LEADS OFF displayed without cause patient safety

ECG parameter key appears with ??? symbol and LEADS OFF message when no patient cable connected, or ECG count and lead information not displayed when patient simulator connected

Ranked causes

1. ECG module inserted without patient cable (normal during module insertion verification) (common)
2. ECG module not communicating with monitor after patient cable connection (occasional)

First check

Verify ECG module insertion

Test point: ECG parameter display area
Expected: ECG parameter key with ??? symbol and LEADS OFF message

1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Module does not sign on when installed in monitor bay

Patient module fails to establish communication with monitor when inserted into module bay

Ranked causes

1. SDLC PCBA failure (common)
2. CPU PCBA failure (occasional)

First check

Verify module is fully seated in monitor module bay

Test point: Module Bay connection
Expected: Module fully inserted and mechanically locked

2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

Module signs on but parameters do not function patient safety

Module communicates with monitor but parameter data (e.g. ECG) is not transmitted or displayed

Ranked causes

1. SDLC PCBA failure preventing data transmission (common)
2. CPU PCBA failure (occasional)

First check

Verify module cable connections between module bay and CPU PCBA

Test point: Module bay SDLC connectors and internal data cables
Expected: All connections fully seated and undamaged

2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

Monitor fails power-on diagnostics

Monitor does not pass self-test at startup; requires manual diagnostic execution

Ranked causes

1. Software or hardware fault identified in self-test (unknown)
2. Display failure preventing diagnostic menu access (occasional)

First check

Verify serial port is configured for DIAGNOSTICS mode

Test point: Serial port setting
Expected: DIAGNOSTICS

2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

Xhibit Central Monitor displays busy message patient safety

Xhibit Central Monitor shows 'Data not available - [bedname] busy' instead of monitor data

Ranked causes

1. Monitor has reached maximum of eight simultaneous client connections (common)
2. Xhibit Central Monitor is on different subnet with lower priority (occasional)

First check

Review Linked Network Devices in System Info

Test point: Biomed menu System Info > Links
Expected: Eight or fewer active client connections listed

1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Calibration: Touchscreen

Recalibrate touchscreen controller and reset monitor

Ranked causes

1. Touchscreen calibration drift or inaccuracy (occasional)

First check

Access Boot Menu

Test point: Boot Menu main screen
Expected: Boot Menu displayed

1 more check with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Cybersecurity logs not received by log server

Monitor fails to transmit cybersecurity event logs to network log server

Ranked causes

1. Log Server configuration in Biomed menu is incorrect or outdated (common)

First check

Verify Log Server Setup configuration in Biomed menu

Test point: Biomed menu Log Server Setup
Expected: IP address, Port Number, SSL Certificate, SSL Key match IT-provided values

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

Enter Boot Menu during startup

Access Boot menu to run extended diagnostics or view error logs during 4-3-2-1 countdown

Ranked causes

1. Need to access Boot menu diagnostics or configuration (common)

First check

Turn on monitor and watch for 4-3-2-1 countdown

Test point: display during startup
Expected: countdown visible

1 more check with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Extended Diagnostics access

Need to run extended diagnostic tests beyond Power-ON tests to isolate hardware issues

Ranked causes

1. Power-ON diagnostic inconclusive or needs detailed analysis (occasional)

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

Monitor startup sequence incomplete or diagnostic menu not displayed

Diagnostic menu fails to display after power ON or monitor keys do not appear on right side of screen

Ranked causes

1. Internal firmware or initialization error detected during power-ON (rare)

First check

Verify Diagnostic menu displays after power ON

Test point: Monitor display
Expected: Diagnostic menu appears after power ON button press

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

Power cycling results in loss of patient data patient safety

Patient data is lost when monitor is powered off and on

Ranked causes

1. Patient data not backed up to persistent storage before power loss (unknown)

System software version mismatch failure

Monitor fails power-on diagnostics; error log shows app.bin build ID, version, or checksum does not match fd_image_c.bin

Ranked causes

1. app.bin, bootrom.bin, and fd_image_c.bin are different versions (common)

First check

Access Boot Menu and review error log for software failure entry

Test point: Error Log E- functions
Expected: Entry showing app.bin mismatch with fd_image_c.bin

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

Error codes

Code	Meaning	Trigger	Severity
`01030000`	Diagnostics passed	All diagnostic tests passed successfully	info
`01030001`	Diagnostics failed; degraded performance	Diagnostic test failure detected	error
`01030002`	Critical failure	Critical diagnostic test failure	critical
`01030003`	Cannot diagnose at this boot stage	Diagnostics unable to run at boot	unknown
`01030100`	Diagnostics Port Test failed	Diagnostic port communication failure	critical
`01030200`	8260 Test failed	8260 device test failure	critical
`01030201`	8260 SCC Transmit failed	Serial Controller Chip transmit failure	critical
`01030202`	8260 SCC configuration not recognized	Serial Controller Chip configuration error	critical
`01030300`	DRAM Test failed	Dynamic RAM test failure	critical
`01030301`	DRAM Test cannot allocate memory	DRAM memory allocation failure	critical
`01030400`	GDS RAM Test failed	Graphics Display System RAM test failure	critical
`01030500`	FLASH ROM Test failed	Flash ROM test failure	critical
`01030501`	FLASH ROM boot larger than Flash	Boot code size exceeds Flash memory	critical
`01030502`	FLASH ROM app larger than Flash	Application code size exceeds Flash memory	critical
`01030503`	FLASH ROM boot checksum error	Boot code checksum verification failed	critical
`01030504`	FLASH ROM app checksum error	Application code checksum verification failed	critical
`01030505`	FLASH ROM read/write memory test error	Flash memory read/write test failure	critical
`01030600`	Power Subsystem Test failed	Power supply test failure	critical
`01030601`	VIN out of spec	Input voltage exceeds acceptable range	critical
`01030602`	VCOM out of spec	Negative voltage supply out of range	critical
`01030603`	18V out of spec	18 V supply voltage out of range	critical
`01030604`	12V out of spec	12 V supply voltage out of range	critical
`01030605`	5V out of spec	5 V supply voltage out of range	critical
`01030606`	3.3V out of spec	3.3 V supply voltage out of range	critical
`01030607`	3.3V always on supply out of spec	3.3 V always-on supply voltage out of range	critical
`01030608`	-12V out of spec	Negative 12 V supply voltage out of range	critical
`01030609`	Battery A temp out of spec	Battery A temperature exceeds acceptable range	warning
`0103060B`	Power PCB temp out of spec	Power board temperature exceeds acceptable range	unknown
`0103060C`	Cannot communicate with battery A	Battery communication failure detected	critical
`0103060E`	Wrong chemistry for battery A	Battery chemistry mismatch detected	warning
`01030610`	Wrong voltage for battery A	Battery voltage out of specification	warning
`01030A00`	Video Test failed	Video system test failure	critical
`01030A03`	Video configuration not recognized	Video hardware configuration error	critical
`01030A04`	Video DRAM failure	Video memory test failure	critical
`01030A05`	Video could not detect H-sync signal	Horizontal sync signal not detected	critical
`01030A06`	Video could not detect blue video signal	Blue video signal not detected	critical
`01030D00`	Cannot access AUDIO device registers	Audio device register access failure	critical
`01030D01`	Could not open audio device	Audio device initialization failure	critical
`01030D02`	Audio device did not respond correctly	Audio device communication failure	critical
`01030D03`	Audio Loopback test failed	Audio loopback test failure	critical
`01030E00`	NVRAM Test failed	Non-volatile RAM test failure	critical
`01030E01`	NVRAM Clock not running	NVRAM clock stopped or defective	critical
`01030E02`	NVRAM checksum error	NVRAM data checksum verification failed	critical
`01030E03`	NVRAM read/write memory test failed	NVRAM read/write test failure	critical
`0x00fe014b`	CMOS Error Log initialized	CMOS error log initialization	info
`0x0100006f`	User reset monitor	Manual reset initiated by user	info
`0x010000ad`	Interrupt Broadcast Storm over	Network broadcast storm condition cleared	warning
`0x010001a6`	Local clock adjusted to time master	Time synchronization drift detected	info
`0x01000212`	Touchscreen calibration complete	Touchscreen calibration procedure completed	info
`Power-ON diagnostic failure (unspecified code)`	One or more hardware subsystems failed self-test during system startup	System power-ON or cold boot; automatic diagnostic execution	error

Likely causes and actions for each code are in ServiceForge. Connect ServiceForge to your AI

Community

0 fixes logged by technicians through their AI, with outcomes, for this model.

ServiceForge knowledge base record. Field-unverified unless technicians confirmed it. A teaching summary of the record, not a service manual. Export 2026-10-14.