Nellcor Libra: troubleshooting and error codes
The ServiceForge knowledge base holds 55 documented symptoms for the Nellcor Libra, with 114 ranked causes, 128 diagnostic checks with test points and expected values, and 56 error codes. Each symptom below shows its causes and the first check; the rest is one connection away. Connect ServiceForge to your AI
Symptoms
Inaccurate pulse oximetry sensor measurement patient safety
SpO2 reading or pulse signal affected by sensor application, ambient conditions, or patient factors
Ranked causes
- 1. Incorrect sensor application (common)
- 2. Sensor placed on extremity with blood pressure cuff or line (common)
- 3. High ambient light (common)
- 4. Excessive patient activity (common)
- 5. Dark skin pigment or external coloring (occasional)
- 6. Poor peripheral perfusion (occasional)
Verify sensor application
- Test point
- Sensor site
- Expected
- Sensor properly and securely applied per Directions for Use
3 more checks with pass and fail actions, 6 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Questionable readouts of patient physiological measurements patient safety
Patient data readings appear unreliable, inaccurate, or wrongly tagged; patient data missing from records.
Ranked causes
- 1. Sensor not attached correctly (common)
- 2. Faulty sensor (occasional)
- 3. Electromagnetic interference (occasional)
- 4. Ambient light interfering with proper sensing (occasional)
- 5. Coin cell battery was removed from Main board (rare)
Verify sensor attachment and position
- Test point
- Sensor on patient and cable connections
- Expected
- Sensor properly attached and making good contact
4 more checks with pass and fail actions, 6 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
USB data port does not function properly
USB data port connection fails or does not transfer data correctly to PC or external device.
Ranked causes
- 1. USB cable not firmly connected (common)
- 2. Covidien bridge driver corrupted (occasional)
- 3. Mismatched baud rates between monitoring system and PC (occasional)
- 4. Mismatched COM port between PC and HyperTerminal (occasional)
- 5. USB port damaged (rare)
Verify USB cable connection
- Test point
- USB cable and port connections
- Expected
- Cable fully inserted and firmly seated
4 more checks with pass and fail actions, 5 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
No SpO2 level or pulse rate displayed patient safety
Device cannot obtain SpO2 measurement or pulse rate; sensor message occurs
Ranked causes
- 1. Sensor not connected firmly (common)
- 2. Incompatible or defective sensor (occasional)
- 3. Extended or non-approved cable used (occasional)
- 4. High ambient light interference (occasional)
Verify sensor cable connection at sensor port
- Test point
- Pulse oximetry sensor port on front panel and sensor connector
- Expected
- Cable firmly seated in port and connected to sensor
2 more checks with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Pulse signal loss patient safety
Loss-of-pulse signal detected; no signal reaching monitor
Ranked causes
- 1. Sensor applied too tightly (common)
- 2. Blood pressure cuff inflation on same extremity (common)
- 3. Arterial occlusion proximal to sensor (rare)
- 4. Poor peripheral perfusion (occasional)
Assess sensor tightness
- Test point
- Sensor site
- Expected
- Sensor firmly applied but not occluding circulation
1 more check with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
System consumes battery power with AC connected
Monitoring system drains battery power even when AC power cord is connected.
Ranked causes
- 1. AC power cord not properly seated (common)
- 2. Faulty power source (occasional)
- 3. Faulty power cord (occasional)
- 4. Charger board or Power board malfunction (rare)
Verify AC power cord connections
- Test point
- Power cord at wall outlet and device inlet
- Expected
- Both connections fully seated
3 more checks with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Battery Charge Indicator not lit
Battery charge indicator light does not illuminate when power is connected.
Ranked causes
- 1. AC power cord disconnected (common)
- 2. Battery missing or defective (occasional)
- 3. Failed charger (occasional)
Verify AC power connection
- Test point
- AC power cord and wall outlet
- Expected
- AC cord fully connected at both ends
2 more checks with pass and fail actions, 5 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Date and time incorrect on LCD and in trend data download patient safety
System displays incorrect date and time on LCD screen and in downloaded trend data.
Ranked causes
- 1. Date and time not set correctly during installation (common)
- 2. Coin cell battery depleted or removed (occasional)
- 3. Coin cell battery tab does not provide firm contact (rare)
Check current date/time setting
- Test point
- SERVICE Menu date/time display
- Expected
- Date and time set correctly per facility locale format
2 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Display does not function properly or looks distorted
LCD display shows distorted image, garbled text, or improper rendering of information.
Ranked causes
- 1. Electromagnetic interference (occasional)
- 2. LCD cable disconnected or improperly connected (common)
- 3. Main board is malfunctioning (rare)
Identify and isolate EMI sources
- Test point
- Equipment in vicinity of monitor
- Expected
- No active electrosurgical devices or cell phones nearby
2 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Inaccurate SpO2 measurements patient safety
SpO2 reading does not match expected clinical value or varies unexpectedly
Ranked causes
- 1. Patient physiological interference (common)
- 2. Sensor applied too tightly or left too long on one site (occasional)
- 3. High ambient light conditions (occasional)
Inspect sensor site for skin integrity and correct positioning
- Test point
- Applied sensor site on patient
- Expected
- Intact skin, appropriate tension, secure adhesion, proper positioning per Directions for Use
2 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Message: Abnormally shut down last time
System displays message indicating abnormal shutdown occurred on previous operation.
Ranked causes
- 1. System opened and harnesses disconnected (occasional)
- 2. Depleted battery (occasional)
- 3. Battery disconnected while powered on (occasional)
Power cycle system and verify POST
- Test point
- System startup sequence
- Expected
- Normal POST completion without error messages
3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
No sound during POST
Speaker produces no audio output during power-on self-test sequence.
Ranked causes
- 1. Speaker harness loose or disconnected (common)
- 2. Speaker is malfunctioning (occasional)
- 3. Main board is malfunctioning (rare)
Verify speaker connector seating
- Test point
- Speaker connector on Main board
- Expected
- Connector fully engaged and seated
2 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Nurse call system connection failure patient safety
Nurse call port does not successfully communicate alarm to nurses' station
Ranked causes
- 1. Nurse call cable not properly connected (common)
- 2. Nurse call system not responding to alarm (occasional)
- 3. Audible alarm turned off (common)
Verify audible alarm is enabled
- Test point
- Monitoring system audible alarm setting
- Expected
- Audible alarm enabled
7 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Power system not operating correctly patient safety
Monitoring system does not power on, Battery Charge Indicator does not light, or system does not turn off properly
Ranked causes
- 1. AC power not connected or power source faulty (common)
- 2. Battery not charging or Battery Charge Indicator malfunction (occasional)
- 3. Power button stuck or unresponsive (rare)
Verify AC power connection and Battery Charge Indicator status
- Test point
- Battery Charge Indicator LED
- Expected
- Lit (amber/yellow) when connected to AC power
4 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
SpO2 sensor messages or disconnection patient safety
System displays sensor-related messages including SpO2 Pulse Search, Sensor Off, Cable Disconnect, or Signal Artifact Detected messages.
Ranked causes
- 1. Sensor disconnected from cable or monitoring system (common)
- 2. Sensor detached from patient (common)
- 3. Unable to get reliable readings due to skin contamination or motion (common)
Verify sensor and cable connections
- Test point
- Sensor connector and cable connections at device
- Expected
- All connections fully seated and secure
2 more checks with pass and fail actions, 5 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
System does not power on with battery only
Monitoring system does not turn on when Power On/Off button is pressed with battery power only.
Ranked causes
- 1. Power On/Off button not held long enough (common)
- 2. Battery not properly seated (occasional)
- 3. Battery depleted or defective (common)
Verify button press duration
- Test point
- Power On/Off button
- Expected
- Button held for 2 seconds minimum
2 more checks with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
System does not respond to Power On/Off button with AC and battery
Monitoring system with battery installed and connected to AC power does not respond when Power On/Off button is pressed.
Ranked causes
- 1. Power On/Off button not held long enough (common)
- 2. Failed Power board (rare)
- 3. AC power interference (occasional)
Verify button press duration
- Test point
- Power On/Off button
- Expected
- Button held for 2 seconds minimum
2 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Alarm audio pause function not working
Audio paused button does not silence alarm tone or alarm does not remain silent for set interval
Ranked causes
- 1. Audio pause interval not properly configured in SERVICE Menu (common)
- 2. Audio pause button hardware or firmware malfunction (occasional)
Audio pause interval configuration
- Test point
- SERVICE Menu AUDIO ALARM PAUSED setting
- Expected
- 30 seconds
2 more checks with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Alarm audio reminder not sounding
Alarm audio reminder tone does not sound after configured interval when alarms are disabled
Ranked causes
- 1. Audio reminder interval not properly set in SERVICE Menu (common)
- 2. Firmware or audio circuit malfunction (rare)
Audio reminder interval setting
- Test point
- SERVICE Menu ALARM AUDIO REMINDER setting
- Expected
- 3 minutes
1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Alarm volume cannot be adjusted
Alarm volume dots do not change or alarm tone volume does not vary with volume setting selection
Ranked causes
- 1. Alarm volume control circuit malfunction (occasional)
- 2. Audio amplifier failure (rare)
Alarm volume setting display
- Test point
- OPTIONS Menu Volume Alarm Volume screen
- Expected
- Dots display from 1 to 8, default 5
2 more checks with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Audio alarm does not pause for specified time
Audio alarm pauses for incorrect duration compared to institutional default settings configured in the system.
Ranked causes
- 1. Institutional defaults not set correctly (occasional)
- 2. Audio Paused button activator on Main board malfunctioning (rare)
Verify institutional defaults setting
- Test point
- SERVICE Menu default settings
- Expected
- Pause duration matches institutional requirement
1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Battery status not indicated correctly during battery operation
Battery charge level indicator does not display correctly when operating on battery power.
Ranked causes
- 1. Battery is defective (occasional)
- 2. Main CPU or sub-CPU failure (rare)
Verify battery installation and condition
- Test point
- Battery compartment and battery
- Expected
- Battery properly installed and functional
1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Blank display after normal POST
LCD display remains blank or inactive after successful power-on self-test.
Ranked causes
- 1. LCD cable disconnected (common)
- 2. LCD is damaged (occasional)
Verify LCD cable connection
- Test point
- LCD connector on Main board
- Expected
- Cable fully seated and secured
1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: Automatic wavelength and LED intensity adjustment
System automatically selects coefficients for red LED wavelength and adjusts LED light intensity to compensate for tissue thickness variations during SpO2 measurement
Ranked causes
- 1. LED wavelength variation between sensors (common)
- 2. Tissue thickness differences affecting light intensity (common)
Observe plethysmographic waveform during automatic calibration
- Test point
- Display
- Expected
- Waveform may briefly display flat line during calibration
2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Firmware download error or technical system error
Error code starting with 'E' appears on LCD display indicating firmware or system error.
Ranked causes
- 1. Firmware not loading correctly (occasional)
- 2. Monitoring system is malfunctioning (rare)
Record exact error code displayed
- Test point
- LCD error code display
- Expected
- Error code clearly visible and readable
3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Key beep volume cannot be adjusted
Key beep tone does not vary in volume when selection dial is used or volume control does not respond
Ranked causes
- 1. Key beep volume control not properly configured (common)
- 2. Audio output circuit malfunction (occasional)
Key beep volume setting display
- Test point
- OPTIONS Menu Volume Key Beep Volume screen
- Expected
- Dots display from 1 to 7, default 4
2 more checks with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Low or critically low battery condition
Battery charge is depleted or critically low during battery-powered operation.
Ranked causes
- 1. Monitoring system run on battery for full lifespan (common)
- 2. Battery not recharging (occasional)
Assess battery usage time
- Test point
- System operation duration on battery
- Expected
- Within expected battery life for model
2 more checks with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Monitoring system is frozen patient safety
System does not respond to input and operation is halted.
Ranked causes
- 1. Reset needed (common)
- 2. Main board malfunction (rare)
Attempt forced system reset
- Test point
- Power On/Off button
- Expected
- System powers off after 15 seconds
2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
No response when control buttons are pressed
Control buttons on front panel do not respond to user input; system does not recognize button presses.
Ranked causes
- 1. Possible misplacement of buttons (occasional)
- 2. Button activators on Main board malfunctioning (rare)
Verify button placement in bezel
- Test point
- Front panel button positions
- Expected
- All 3 buttons properly positioned in bezel housing
1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Pulse tone volume cannot be adjusted
Pulse tone does not sound with heartbeats or volume cannot be varied between settings
Ranked causes
- 1. Pulse volume control not properly configured or enabled (common)
- 2. Heart rate detection or pulse output circuit malfunction (occasional)
Pulse tone sounds with heartbeats
- Test point
- Monitor speaker and heart rate detection
- Expected
- Pulse tone audible with each detected heartbeat
3 more checks with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
SpO2 and pulse rate values unstable or unreasonable patient safety
Oxygen saturation and pulse rate readings do not stabilize or show abnormal values when sensor applied to live subject
Ranked causes
- 1. Sensor not properly attached or patient movement (common)
- 2. Signal processing or sensor malfunction (occasional)
System stabilization time
- Test point
- Monitor display
- Expected
- SpO2 and PR values stabilize within 15 to 30 seconds
1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
System does not respond to jog dial operation
Jog dial control input does not produce any response or navigation change in the system.
Ranked causes
- 1. Jog dial is malfunctioning (occasional)
- 2. Encoder on Main board is malfunctioning (rare)
Visually inspect jog dial
- Test point
- Jog dial control
- Expected
- No visible damage or stuck condition
1 more check with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Audio alarm cannot be paused
Audio alarm output cannot be silenced or paused by pressing the audio pause button.
Ranked causes
- 1. Main board is malfunctioning (rare)
Press Audio Paused button
- Test point
- Audio Paused button control
- Expected
- Alarm pauses or silences when button pressed
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Battery charge time excessive
Battery Charge Indicator does not change to green within expected timeframe or battery not fully charging
Ranked causes
- 1. Battery requires complete charge/discharge cycle to restore capacity (occasional)
Verify battery charge time and indicator status
- Test point
- Battery Charge Indicator LED and charging time
- Expected
- Indicator changes to green: 4 hours for 5-hour battery, 8 hours for 10-hour battery
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Battery charge time not reaching completion
Battery Charge Indicator does not change to green within expected timeframe during charging
Ranked causes
- 1. Battery requires complete charge/discharge cycle to restore normal capacity (occasional)
Monitor Battery Charge Indicator color during charging
- Test point
- Battery Charge Indicator
- Expected
- Green after charging completion hours, 4 hours for 5-hour battery; 8 hours for 10-hour battery
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Button press does not emit tone patient safety
Pressing Power On/Off button or other buttons produces no audible tone (neither valid nor invalid tone)
Ranked causes
- 1. Speaker failure or audio circuit malfunction (unknown)
Press Power On/Off button and listen for tone
- Test point
- Speaker output
- Expected
- Audible tone (either valid or invalid)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Buzzer sounds during POST, EEE910 indicated on LCD
System emits buzzing sound during POST and displays error code EEE910 on LCD screen.
Ranked causes
- 1. CPU is malfunctioning (rare)
Disconnect speaker and retry POST
- Test point
- Speaker connector and Main board
- Expected
- POST completes without buzzing or EEE910 error
1 more check with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Coin cell battery replacement patient safety
Date and time settings reset after replacing the coin cell battery on the Main board; patient data integrity may be compromised
Ranked causes
- 1. Coin cell battery depleted or removed (unknown)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Earth leakage current exceeds limit high voltage
Electrical safety analyzer detects excessive leakage current from device chassis to earth ground during IEC60601-1 earth leakage test
Ranked causes
- 1. Power supply leakage or insulation degradation (unknown)
Measure earth leakage current in normal condition
- Test point
- AC power ground path
- Expected
- 500 microamps or less
- Tools
- Electrical safety analyzer
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Enclosure leakage current exceeds limit high voltage
Electrical safety analyzer detects excessive ungrounded enclosure current between case and earth during IEC60601-1 enclosure leakage test
Ranked causes
- 1. Case insulation or shielding degradation (unknown)
Measure enclosure leakage current in normal condition
- Test point
- Enclosure to earth
- Expected
- 100 microamps or less
- Tools
- Electrical safety analyzer, foil
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Indicator or display element does not light patient safety
One or more display indicators or elements fails to illuminate during power-on
Ranked causes
- 1. Display or indicator failure (unknown)
Observe all indicators and display elements during POST
- Test point
- Software version display, SpO2 alarm indicator, pulse rate alarm indicator
- Expected
- All indicators light for approximately 2 seconds
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
LCD visibly cracked or broken
LCD display panel shows visible physical damage including cracks or breaks.
Ranked causes
- 1. Physical damage to LCD (common)
Inspect LCD for cracks or damage
- Test point
- LCD display panel surface
- Expected
- No visible cracks, breaks, or physical damage
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
LED intensity not controlled properly
LED brightness does not modulate as sensor clip opens/closes, indicating microprocessor control failure
Ranked causes
- 1. Microprocessor not controlling LED intensity (unknown)
LED brightness when sensor fully open
- Test point
- Adult finger sensor
- Expected
- Brightly lit
3 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Nurse call port resistance incorrect
Resistance measurements between nurse call port pins do not match expected values for the system state
Ranked causes
- 1. Nurse call port malfunction or connector fault (unknown)
Measure resistance between pins 2 and 3 when system is powered off
- Test point
- Nurse call connector pins 2 and 3
- Expected
- Open
5 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Patient leakage current exceeds limit patient safety
Electrical safety analyzer detects excessive leakage from patient connection (SpO2 sensor) to earth ground
Ranked causes
- 1. Patient connector insulation degradation or internal leakage (unknown)
Measure patient leakage current in normal condition
- Test point
- SpO2 sensor to earth
- Expected
- 10 microamps or less
- Tools
- Electrical safety analyzer, test cable
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Patient leakage current with mains voltage exceeds limit patient safety
Electrical safety analyzer detects excessive leakage when 110% mains voltage is applied between patient connection and earth
Ranked causes
- 1. Patient connector isolation failure under fault voltage (unknown)
Measure patient leakage current with mains voltage, normal polarity
- Test point
- SpO2 sensor to earth
- Expected
- 50 microamps or less
- Tools
- Electrical safety analyzer, test cable
1 more check with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
POST takes longer than expected to complete
POST sequence duration exceeds normal time
Ranked causes
- 1. Normal POST duration variance (occasional)
Time the POST sequence duration
- Test point
- From Power On/Off button press to main monitoring screen display
- Expected
- Approximately 13 seconds
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Power-On Self-Test (POST) fails or displays error
Error message appears during POST sequence instead of completing normally with pass tone and main monitoring screen
Ranked causes
- 1. POST sequence interrupted or incomplete (unknown)
Verify AC power connection and indicators
- Test point
- AC power source, AC Indicator, Battery Charge Indicator
- Expected
- AC Indicator and Battery Charge Indicator are lit
2 more checks with pass and fail actions are in ServiceForge. Connect ServiceForge to your AI
Pulse rate alarm limit adjustment needed patient safety
Caregivers need to adjust pulse rate (PR) alarm thresholds. Display flashes on yellow background when pulse rate is outside alarm limits. Rates outside 20-250 bpm range displayed as 0 or 250.
Ranked causes
- 1. Pulse rate alarm limits require adjustment per patient needs (common)
Verify current pulse rate alarm limit settings displayed as smaller values
- Test point
- Pulse Rate (PR) numerical area
- Expected
- Current upper and lower alarm limit settings visible to left of dynamic pulse rate value
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
SatSeconds alarm option configuration patient safety
SatSeconds alarm option manages frequency of SpO2 alarm limit violations. Higher value setting results in less frequent alarms.
Ranked causes
- 1. SpO2 alarm frequency requires adjustment using SatSeconds setting (occasional)
Confirm SatSeconds alarm option is available in ALARM LIMITS Menu
- Test point
- ALARM LIMITS Menu options
- Expected
- SatSeconds Alarm option present in menu selection
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
SatSeconds alarm triggers during SpO2 desaturation patient safety
Patient SpO2 drops 10% below lower alarm threshold (85% to 75%) and remains below threshold for 2.5 seconds, triggering SatSeconds alarm when limit is set to 25
Ranked causes
- 1. SpO2 saturation below alarm threshold for duration exceeding SatSeconds limit (common)
Verify SpO2 value relative to lower alarm threshold
- Test point
- Patient SpO2 reading
- Expected
- SpO2 above lower alarm threshold (e.g., >85% if threshold set to 85%)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Speaker does not sound during power-on patient safety
POST pass tone is inaudible after pressing Power On/Off button; alarm warning sounds remain inaudible
Ranked causes
- 1. Speaker obstructed or blocked (common)
Verify speaker is unobstructed and clean
- Test point
- Speaker outlet
- Expected
- Speaker free of debris and blockage
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
SpO2 alarm limit adjustment needed patient safety
Caregivers need to adjust SpO2 alarm thresholds from default values. Changes take effect until modified again or power cycle occurs. SpO2 value flashes on yellow background when saturation is outside alarm limits.
Ranked causes
- 1. SpO2 alarm limits require adjustment per patient needs (common)
Verify current SpO2 alarm limit settings displayed as smaller values
- Test point
- SpO2 numerical area
- Expected
- Current upper and lower alarm limit settings visible to left of dynamic SpO2 value
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
SpO2 and pulse rate alarm inhibition patient safety
Option to inhibit audible alarms for SpO2 and/or pulse rate alarm limit violations while maintaining visual monitoring.
Ranked causes
- 1. Alarm inhibition required per clinical protocol (occasional)
Verify alarm inhibit icon is accessible in ALARM LIMITS Menu
- Test point
- ALARM LIMITS Menu
- Expected
- Alarm inhibit icon available for SpO2 and pulse rate selection
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
System does not power on with AC power only
Monitoring system does not turn on when Power On/Off button is pressed with AC power connected but no battery installed.
Ranked causes
- 1. No battery installed (common)
Verify battery installation
- Test point
- Battery compartment
- Expected
- Battery installed and properly seated
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Error codes
| Code | Meaning | Trigger | Severity |
|---|---|---|---|
E.00.0001 | USB not recognized during firmware download | Firmware download initiated with USB connection not properly recognized | error |
E.00.0002 | Section.muf file corrupt or not found | Firmware download process cannot locate or verify Section.muf file integrity | error |
E.00.0003 | Ver.muf file corrupt or not found | Firmware download process cannot locate or verify Ver.muf file integrity | error |
E.00.0004 | Update.muf file corrupt or not found | Firmware download process cannot locate or verify Update.muf file integrity | error |
E.00.0005 | Binary file corrupt or not found | Firmware download process cannot locate or verify firmware binary file integrity | error |
E.01.0003 | Boot download failed | System failed to download boot firmware to memory | error |
E.01.0005 | Burn boot failed | System failed to write (burn) boot firmware to Flash memory | error |
E.01.0007 | Boot data between SDRAM and FLASH do not match | Data verification after firmware download found mismatch between RAM and Flash storage | error |
E.02.0003 | Main download failed | System failed to download main firmware to memory | error |
E.02.0005 | Burn main failed | System failed to write (burn) main firmware to Flash memory | error |
E.02.0007 | Main data between SDRAM and FLASH do not match | Data verification after firmware download found mismatch between RAM and Flash storage | error |
EEE001 | SpO2 module RAM error | SpO2 sensor module detected error in RAM during self-test or operation | error |
EEE002 | SpO2 module ROM/code integrity error | SpO2 sensor module detected error in firmware or program code integrity | error |
EEE003 | SpO2 module bad CRC in communications | SpO2 sensor module detected cyclic redundancy check error in communication data | error |
EEE004 | SpO2 module bad communication message | SpO2 sensor module received malformed or invalid communication message | error |
EEE005 | SpO2 module communication error; incorrect value | SpO2 sensor module communication returned unexpected or out-of-range value | error |
EEE006 | SpO2 module calibration (offset) failure | SpO2 sensor module calibration procedure failed during initialization | error |
EEE009 | SpO2 module syntax communication error | SpO2 sensor module detected syntax error in received communication data | error |
EEE010 | SpO2 module sensor error | SpO2 sensor module detected error condition in sensor itself during operation | error |
EEE012 | SpO2 module other hardware problem | SpO2 sensor module detected unspecified hardware error condition | error |
EEE017 | SpO2 module indicator that sensor appears defective | SpO2 sensor module detected characteristics suggesting sensor is defective or malfunctioning | warning |
EEE050 | SpO2 module intermittent error | SpO2 sensor module detected intermittent fault condition during operation | warning |
EEE051 | SpO2 module digital communication error | SpO2 sensor module detected error in digital communication protocol or line | error |
EEE255 | SpO2 module invalid jumper selection | SpO2 sensor module detected invalid jumper configuration during initialization | error |
EEE256 | SpO2 module beginning of packet missing | SpO2 sensor module received communication packet without proper start marker | error |
EEE257 | SpO2 module packet start (SID) missing | SpO2 sensor module received packet without start ID (SID) field | error |
EEE258 | SpO2 module packet length error | SpO2 sensor module received packet with incorrect or mismatched length field | error |
EEE259 | SpO2 module message length error | SpO2 sensor module received message with incorrect length field or data | error |
EEE260 | SpO2 module packet contains unsupported key | SpO2 sensor module received packet with command or key not supported by module firmware | warning |
EEE261 | SpO2 module packet CRC error | SpO2 sensor module detected cyclic redundancy check error in packet data | error |
EEE262 | SpO2 module end of packet missing | SpO2 sensor module received packet without proper end marker or terminator | error |
EEE263 | SpO2 module packet contains undefined key | SpO2 sensor module received packet with unrecognized command or data key | warning |
EEE264 | SpO2 module corrupted variable | SpO2 sensor module detected data corruption in module variable or memory location | error |
EEE265 | SpO2 module memory overflow | SpO2 sensor module memory allocation exceeded available space | error |
EEE266 | SpO2 module bad pointer | SpO2 sensor module detected invalid memory pointer or address during operation | error |
EEE267 | SpO2 module parameter value out of range | SpO2 sensor module received or generated parameter value outside acceptable limits | warning |
EEE268 | SpO2 module reset detected | SpO2 sensor module detected unexpected reset or restart during normal operation | warning |
EEE269 | SpO2 module unexpected value | SpO2 sensor module received value inconsistent with expected data or state | warning |
EEE270 | SpO2 module time out | SpO2 sensor module operation timed out waiting for expected event or response | warning |
EEE271 | SpO2 module not ready/not initialized | SpO2 sensor module not properly initialized or not ready for operation | warning |
EEE272 | SpO2 module double fault | SpO2 sensor module detected multiple simultaneous fault conditions | critical |
EEE273 | SpO2 module data out of range error | SpO2 sensor module measured or received data value outside valid sensor range | error |
EEE274 | SpO2 module incompatible digital sensor | SpO2 module detected digital sensor that is incompatible with module firmware | error |
EEE275 | SpO2 module incorrect registration number | SpO2 sensor module detected sensor with incorrect or mismatched registration identification | error |
EEE276 | SpO2 module sensor read failure | SpO2 module unable to read data from connected sensor during operation | error |
EEE277 | SpO2 module sensor signature verification failure | SpO2 module unable to verify or authenticate sensor identity and credentials | error |
EEE281 | SpO2 module overflow/underflow | SpO2 module internal buffer or calculation resulted in data overflow or underflow condition | error |
EEE282 | SpO2 module sensor activation failure | SpO2 module unable to activate or initialize sensor connection | error |
EEE283 | SpO2 module sensor write failure | SpO2 module unable to write data to sensor memory or configuration | error |
EEE284 | SpO2 module both HW and SW ECG triggers received | SpO2 module received conflicting hardware and software ECG trigger signals simultaneously | warning |
EEE285 | SpO2 module host attempted read/close of sensor trend before successful open | SpO2 module received read or close command for sensor trend data file not yet opened | warning |
EEE286 | SpO2 module host attempted redundant open of sensor trend | SpO2 module received second open command for sensor trend data file already open | warning |
EEE287 | SpO2 module sensor trend data unavailable for reading by host | Host system requested sensor trend data that is not available or accessible | warning |
EEE288 | SpO2 module no more sensor trend data available for reading by host | Host system has read all available sensor trend data and reached end of data | info |
EEE289 | SpO2 module sensor private label/host sensor key incompatible | SpO2 module detected incompatibility between sensor private label and host system key | error |
EEE804 | SpO2 module communication error | SpO2 sensor module detected general communication error during operation | 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.