ICU Medical Plum 360: troubleshooting and error codes
The ServiceForge knowledge base holds 137 documented symptoms for the ICU Medical Plum 360, with 197 ranked causes, 173 diagnostic checks with test points and expected values, and 164 error codes. Each symptom below shows its causes and the first check; the rest is one connection away. Connect ServiceForge to your AI
Symptoms
Alarm N101: No action timeout patient safety
Multiple variants of N101 timeout alarms when operator does not respond within specified time (15 seconds to 2 minutes). LCD displays 'No Action Alarm!' with context-specific prompt.
Ranked causes
- 1. Operator inaction timeout during standby selection (occasional)
- 2. Operator inaction during program confirmation (titration) (occasional)
- 3. Operator inaction after rate recalculation alert (occasional)
- 4. Operator inaction during stop line selection (occasional)
- 5. Operator inaction during start line selection (occasional)
- 6. Operator inaction on program confirmation (new program) (occasional)
- 7. Operator inaction with soft limit override pending (rare)
- 8. Operator inaction when both lines stopped (occasional)
- 9. Operator inaction when Line A stopped (occasional)
- 10. Operator inaction when Line B stopped (occasional)
10 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Proximal occlusion test fails patient safety
Proximal occlusion test does not pass during PVT
Ranked causes
- 1. Closed proximal clamp (common)
- 2. Cassette not properly primed (occasional)
- 3. Defective cassette (occasional)
- 4. Dirty sensor pin (occasional)
- 5. Defective APP PWA (rare)
Verify proximal clamp is open
- Test point
- Proximal clamp on administration set
- Expected
- Clamp fully open; fluid flows freely
2 more checks with pass and fail actions, 5 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Proximal occlusion test failure
Proximal occlusion alarm triggered during functional test procedure
Ranked causes
- 1. Closed proximal clamp (common)
- 2. Cassette not properly primed (common)
- 3. Defective cassette (occasional)
- 4. Dirty sensor pin (occasional)
- 5. Defective APP PWA (rare)
5 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Alarm N160: Line B VTBI complete patient safety
LCD displays variants of 'Line B VTBI complete'. Line B delivery finished under different CCA or current CCA; action required.
Ranked causes
- 1. Line B piggyback delivery complete under prior CCA with no Line A delivery (occasional)
- 2. Line B complete under prior CCA with concurrent Line A delivery (occasional)
- 3. Line B piggyback delivery complete under current CCA with no Line A (occasional)
- 4. Line B concurrent delivery complete under current CCA (occasional)
4 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Distal occlusion test fails patient safety
Distal occlusion test does not pass during PVT
Ranked causes
- 1. Cassette not properly primed (common)
- 2. Defective cassette (occasional)
- 3. Dirty sensor pin (occasional)
- 4. Defective APP PWA (rare)
Re-prime cassette
- Test point
- Cassette inlet/outlet
- Expected
- No air bubbles visible; fluid flows smoothly
3 more checks with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Distal occlusion test failure patient safety
Distal occlusion detection test fails during performance verification test
Ranked causes
- 1. Cassette not properly primed (common)
- 2. Defective cassette (common)
- 3. Dirty sensor pin (occasional)
- 4. Defective infusion mechanism (occasional)
Verify cassette priming
- Test point
- Cassette fluid pathway
- Expected
- Cassette fully primed without air pockets
2 more checks with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Alarm loudness test fails
Alarm loudness test does not pass during PVT
Ranked causes
- 1. Defective CPU (occasional)
- 2. Defective peripheral assembly (occasional)
- 3. Defective piezo alarm assembly (rare)
Replace CPU PWA
- Test point
- CPU module
- Expected
- Alarm sounds at correct volume during test
2 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Alarm loudness test failure
Piezo alarm does not produce expected volume level during functional test
Ranked causes
- 1. Defective CPU (rare)
- 2. Defective peripheral assembly (rare)
- 3. Defective piezo alarm assembly (rare)
3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Delivery accuracy test fails patient safety
Delivery accuracy test does not pass during PVT
Ranked causes
- 1. Set not properly primed (common)
- 2. Damaged or faulty cassette (occasional)
- 3. Defective infusion mechanism assembly (rare)
Re-prime cassette
- Test point
- Cassette inlet/outlet
- Expected
- No air bubbles; fluid flows at proper rate
1 more check with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Delivery accuracy test failure
Infused volume does not match programmed dose during accuracy test
Ranked causes
- 1. Set not properly primed (common)
- 2. Damaged or faulty cassette (common)
- 3. Defective infusion mechanism assembly (occasional)
3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Distal air-in-line test fails patient safety
Distal air-in-line test does not pass during PVT
Ranked causes
- 1. Defective special cassette (common)
- 2. Dirty sensors (occasional)
- 3. Defective APP PWA (rare)
Replace special cassette
- Test point
- Air-in-line sensor cassette slot
- Expected
- New cassette installed; test passes
1 more check with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Distal air-in-line test failure
Air detected in distal line during functional test procedure
Ranked causes
- 1. Defective special cassette (occasional)
- 2. Dirty sensors (occasional)
- 3. Defective APP PWA (rare)
3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Proximal air-in-line test fails patient safety
Proximal air-in-line test does not pass during PVT
Ranked causes
- 1. Defective special cassette (common)
- 2. Dirty sensors (occasional)
- 3. Defective APP PWA (rare)
Replace special cassette
- Test point
- Air-in-line sensor cassette slot
- Expected
- New cassette installed; test passes
1 more check with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Proximal air-in-line test failure
Air detected in proximal line during functional test procedure
Ranked causes
- 1. Defective special cassette (occasional)
- 2. Dirty sensors (occasional)
- 3. Defective APP PWA (rare)
3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Proximal occlusion or air on Line A during delivery patient safety
Proximal occlusion or air detected on Line A during delivery using negative or peak detection algorithm.
Ranked causes
- 1. Kinked proximal Line A (common)
- 2. Closed clamp on Line A (occasional)
- 3. Excessive air creating backpressure (occasional)
Inspect Line A for kinks
- Test point
- Line A tubing
- Expected
- Tubing straight, unkinked, not clamped
3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Unrestricted flow test fails patient safety
Unrestricted flow test does not pass during PVT
Ranked causes
- 1. Cassette not properly seated (common)
- 2. Defective cassette (occasional)
- 3. Defective or dirty valve pins (occasional)
Reseat cassette
- Test point
- Cassette slot
- Expected
- Cassette fully seated
1 more check with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Unrestricted flow test failure patient safety
Unrestricted flow test fails; pump does not deliver fluid freely
Ranked causes
- 1. Cassette not properly seated (common)
- 2. Defective cassette (common)
- 3. Defective or dirty valve pins (occasional)
Verify cassette seating
- Test point
- Cassette insertion area
- Expected
- Cassette fully inserted and locked
1 more check with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Alarm N161: Line A VTBI complete patient safety
LCD displays variants of 'VTBI Completed Line A'. Line A delivery finished under prior or current CCA; action required.
Ranked causes
- 1. Line A complete under prior CCA with concurrent delivery still active (occasional)
- 2. Line A delivery complete under current CCA (occasional)
2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Battery current out of range high voltage
Average battery current during operation exceeds safe limits; power supply or load circuit failure detected
Ranked causes
- 1. Power supply current limiting circuit failure or excessive device load (occasional)
- 2. Infusion mechanism draw excessive current (occasional)
Power cycle infuser
- Test point
- Power switch
- Expected
- Device powers on; no over-current alarm after 30 seconds
2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Battery not detected high voltage
Battery not recognized by power supply circuit; loose connection, corrosion, or battery failure
Ranked causes
- 1. Loose battery connector or corrosion on battery terminals (common)
- 2. Defective battery or cable (occasional)
Verify battery connector seating
- Test point
- Battery connector terminals
- Expected
- Connectors fully seated with no gaps; clean terminals
2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Battery trickle charge current high after full charge high voltage
Battery trickle charging current exceeds expected value after full charge is reached
Ranked causes
- 1. Defective or worn battery (common)
- 2. Power supply sensing circuit failure (occasional)
Verify battery fully charged
- Test point
- Battery charge indicator display
- Expected
- Charge indicator shows full (typically 10 bars)
2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Cassette alarm test fails
Cassette alarm test does not pass during PVT
Ranked causes
- 1. Cassette not properly seated (common)
- 2. Defective cassette (occasional)
Reseat cassette
- Test point
- Cassette seating
- Expected
- Cassette fully inserted and locked
1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Cassette test failure patient safety
Faulty cassette, proximal occlusion, or air detected during cassette integrity test at startup
Ranked causes
- 1. Defective or incompatible cassette (occasional)
- 2. Proximal occlusion or air in cassette (common)
Run cassette test
- Test point
- Cassette with administration set installed
- Expected
- Cassette test passes without fault indication
2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Cassette test failure
Faulty cassette, proximal occlusion, or air detected during cassette integrity test. Alarm N251 displayed.
Ranked causes
- 1. Occluded proximal line (common)
- 2. Faulty cassette (occasional)
Open and close cassette door to retry test
- Test point
- Cassette door
- Expected
- Test completes without error
4 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Distal occlusion during delivery patient safety
Distal occlusion detected using peak detection algorithm during infusion delivery. Alarm N186 displayed.
Ranked causes
- 1. Kinked or occluded distal line (common)
- 2. N192 alarm active for 60+ seconds without pressure drop (occasional)
Inspect distal IV line
- Test point
- Patient IV line and site
- Expected
- No kinks or occlusions visible
2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Infuser settings improperly configured
Device settings or drug library is improperly configured causing operation failures
Ranked causes
- 1. Non-recoverable software or drug library update failure (occasional)
- 2. Invalid network security certificates or WebConfig password loss (occasional)
Verify reset completion and factory defaults applied
- Test point
- Biomed settings screen
- Expected
- Infuser settings restored to factory defaults, drug library restored
2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Proximal line occlusion not detected patient safety
Alarm does not sound or message does not flash when proximal tubing is clamped during infusion
Ranked causes
- 1. Occlusion sensor defective (common)
- 2. Alarm circuit malfunction (occasional)
Select Line A
- Test point
- Line A selection
- Expected
- Line A selected on delivery screen
5 more checks with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Proximal occlusion on Line A patient safety
Blockage detected on secondary port (Line A) during backpriming, cassette integrity test, or delivery
Ranked causes
- 1. Line clamped or syringe lacks free space (common)
- 2. Excessive air creating backpressure in cassette (occasional)
Verify secondary line is unclamped
- Test point
- Secondary port (Line A)
- Expected
- Line unclamped and free to flow
1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Self-test fails
Device self-test fails to complete after power on/reset cycle
Ranked causes
- 1. Cassette not properly installed (common)
- 2. Defective CPU PWA (occasional)
Inspect cassette seating and reinstall
- Test point
- Cassette slot
- Expected
- Cassette fully seated with no gaps
1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
ADC test error during power-on self-test
ADC test failure during power-on initialization. Alarm E300 displayed.
Ranked causes
- 1. CPU or ADC circuit failure (rare)
Power cycle the infuser
- Test point
- Power switch
- Expected
- Device powers on without ADC error
3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
ADC test error during power-on self-test caution
Analog-to-Digital Converter test failure during infuser initialization
Ranked causes
- 1. CPU PWA failure or configuration error (occasional)
Power cycle infuser
- Test point
- Power switch
- Expected
- Device powers off then on; self-test completes without error
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Alarm N102: Programming not complete patient safety
LCD displays 'Programming not complete! Action required!' No operator input for 2 minutes after power-on or with cassette installed/program confirmed.
Ranked causes
- 1. Inaction during initial setup after power-on or program confirmation (occasional)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Alarm N103: Data cleared, reprogramming required patient safety
LCD displays 'Data was cleared. Re-enter all programming'. Retention memory (SEEP) corruption detected; delivery parameters lost.
Ranked causes
- 1. Retention memory (SEEP) corrupted (rare)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Alarm N104: Callback to Line B patient safety
LCD displays 'Callback to Line B! Silence audio to clear.' Line B infusion complete; alerts operator to check line or replenish.
Ranked causes
- 1. Line B VTBI reached 0 in piggyback/concurrent mode (common)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Alarm N105: Callback to Line A patient safety
LCD displays 'Callback to Line A! Silence audio to clear.' Line A infusion complete; alerts operator to check line or replenish.
Ranked causes
- 1. Line A VTBI reached 0 in multistep therapy (common)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Alarm N106: Bolus complete on Line B patient safety
LCD displays 'Bolus complete on Line B! Silence audio to clear.' Bolus delivery on Line B finished with nurse callback configured.
Ranked causes
- 1. Bolus delivery on Line B completed (common)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Alarm N107: Bolus complete on Line A patient safety
LCD displays 'Bolus complete on Line A! Silence audio to clear.' Bolus delivery on Line A finished with nurse callback configured.
Ranked causes
- 1. Bolus delivery on Line A completed (common)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Alarm N108: Cassette door opened during delayed start
LCD displays 'Door opened! Delayed Start! Close Door'. Cassette door was opened while infusion in Delayed Start state.
Ranked causes
- 1. Cassette door opened during Delayed Start state (occasional)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Alarm N56: Battery insufficient capacity
LCD displays 'Keep Plugged into AC! Service battery / replace pump.' Battery charge is depleted or failed.
Ranked causes
- 1. Battery does not have sufficient capacity (common)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Alarm N57: Battery or charger failure
LCD displays 'Keep Plugged into AC! Service battery / replace pump.' Battery or charger did not respond to charger voltage pin state.
Ranked causes
- 1. Battery or charger did not respond to VFLOAT pin state (common)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Alarm N58: Low battery level
LCD displays 'Low Battery! Plug into AC power!' Battery charge is low but not yet depleted.
Ranked causes
- 1. Battery charge level is low (common)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Alarm volume control not working
Volume control knob on rear of infuser does not change alarm loudness when rotated
Ranked causes
- 1. Volume potentiometer defective (occasional)
Rotate volume control clockwise
- Test point
- Volume control knob on rear panel
- Expected
- Alarm loudness increases
1 more check with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Audio alarm failure (piezo) caution
Piezo alarm is off but sensed as on, or on but sensed as off. Alarm E301 displayed.
Ranked causes
- 1. Piezo alarm malfunction (rare)
Power cycle and listen for alarm tone
- Test point
- Piezo speaker
- Expected
- Alarm sounds when triggered
4 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Audio alarm piezo failure caution
Piezo speaker malfunction detected during self-test; alarms will not produce audible alert
Ranked causes
- 1. Defective piezo alarm speaker or CPU control circuit (occasional)
Power cycle infuser
- Test point
- Power switch
- Expected
- Self-test completes; audio alarm sounds during test
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Audio PAUSED button not muting alarm
Pressing AUDIO PAUSED does not silence alarm while message continues to flash on display
Ranked causes
- 1. Audio mute circuit defective (occasional)
Press AUDIO PAUSED button during alarm
- Test point
- AUDIO PAUSED softkey
- Expected
- Alarm sound stops immediately; alarm message continues flashing on display
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Battery ADC at high or low limit
Alarm E447 triggered; battery voltage measurement at the extreme edges of valid range
Ranked causes
- 1. Battery condition abnormal (occasional)
Measure battery voltage
- Test point
- Battery terminals
- Expected
- Within specified range
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Battery charge current high after 6 hours high voltage
After six hours of charging, battery charge current remains above expected value indicating charging circuit or battery failure
Ranked causes
- 1. Defective battery or power supply charging circuit (occasional)
Monitor charge current during 6-hour charging cycle
- Test point
- Battery during AC charging in Standby
- Expected
- Charge current drops below expected threshold by 6 hours
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Battery charge current too high after 6 hours
After 6 hours of charging, battery charge current is above expected value. Alarm E328 displayed.
Ranked causes
- 1. Defective battery or charging circuit (occasional)
Monitor charging current at 6-hour mark
- Test point
- Battery charging circuit
- Expected
- Charge current within specification at 6 hours
4 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Battery charging current failure
Charging current does not drop below end-of-charge threshold within 8 hours. Alarm E321 displayed.
Ranked causes
- 1. Defective battery or charging circuit (occasional)
Discharge battery to 5 or fewer bars
- Test point
- Battery charge indicator
- Expected
- Indicator displays 5 bars or less
1 more check with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Battery charging current failure high voltage
Charging current does not drop to expected threshold within six to eight hour charging cycle
Ranked causes
- 1. Battery charging circuit failure or defective battery (occasional)
Verify charging current drops after 8 hours AC charging
- Test point
- Battery during charging in Standby mode
- Expected
- Charging current below end-of-charge threshold after 8 hours
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Battery current out of range (excessive draw)
Average battery current out of range or current limiting circuitry failure. Alarm E320 displayed.
Ranked causes
- 1. Power supply failure or hardware excessive current draw (rare)
Power cycle the infuser
- Test point
- Power supply output
- Expected
- Device powers on without current error
5 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Battery depleted
Infuser running on battery power with voltage below depleted battery threshold. Alarm N252 displayed.
Ranked causes
- 1. Battery voltage too low (common)
Check power source connection
- Test point
- AC power inlet
- Expected
- AC power connected and stable
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Battery depleted caution
Infuser running on battery power below depleted battery threshold; must be plugged into AC immediately
Ranked causes
- 1. Insufficient battery charge for continued operation (common)
Verify AC power connection
- Test point
- Power inlet and mains outlet
- Expected
- AC power cable connected to live outlet
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Battery not detected
Battery not detected due to loose connections, pinched conductors, corrosion, or battery failure. Alarm E326 displayed.
Ranked causes
- 1. Loose or corroded battery connection (common)
Visually inspect battery connections
- Test point
- Battery terminals and connectors
- Expected
- Connections tight, no corrosion, no pinched wires
1 more check with pass and fail actions, 7 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Battery over-voltage input asserted high voltage
Battery voltage regulation circuit detected over-voltage condition; charging circuit malfunction
Ranked causes
- 1. Charging circuit regulator failure or external over-voltage source (occasional)
Power cycle infuser
- Test point
- Power switch
- Expected
- No over-voltage alarm after self-test
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Battery over-voltage on input pin high voltage
Battery over-voltage input pin asserted. Defective charging circuit. Alarm E324 displayed.
Ranked causes
- 1. Charging circuit failure (rare)
Power cycle the infuser
- Test point
- Charging circuit
- Expected
- Device powers on without over-voltage error
3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Battery trickle charge current too high
Battery fully charged but trickle charge current above expected value. Defective or worn battery. Alarm E323 displayed.
Ranked causes
- 1. Defective or worn battery or sensing circuit failure (occasional)
Measure trickle charge current after full charge
- Test point
- Battery charging circuit
- Expected
- Trickle current within specified range
4 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Battery voltage exceeds expected limit
Battery voltage greater than expected limit. Defective sensing circuit. Alarm E325 displayed.
Ranked causes
- 1. Defective battery or sensing circuit (occasional)
Measure battery voltage at terminals
- Test point
- Battery terminals
- Expected
- Voltage within specification
4 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Battery voltage greater than expected limit high voltage
Measured battery voltage exceeds safe operating maximum; sensing circuit or battery failure
Ranked causes
- 1. Battery defective or over-charged; sensing circuit failure (occasional)
Verify battery voltage is within limits
- Test point
- Battery connector on power supply PWA
- Expected
- Voltage within nominal range (typically 10-12 V for lithium battery)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Battery zero reference ADC out of range high voltage
Battery voltage reference measurement circuit malfunction detected during self-test
Ranked causes
- 1. Power supply measurement circuit failure (occasional)
Power cycle infuser
- Test point
- Power switch
- Expected
- Self-test passes; no ADC error on startup
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
More symptoms
- Battery zero reference out of range
- Broken distal pin detected during cassette test
- Calibration: Delivery accuracy
- Calibration: Display backlight intensity
- Calibration: Display contrast
- Cassette door opened during delivery
- Cassette door opened during delivery
- Cassette not properly installed
- CPU timer 1 and 2 mismatch during self test
- CPU timer and RTC mismatch during self test
- CRC failure on drug library
- Critical data verify error
- Critical data verify error
- Defective cassette
- Display backlight failure
- Display backlight failure
- Display controller IC error
- Display Controller IC error
- Display not clear or pixels damaged
- Display test fails
- Display test failure
- Distal air detected
- Distal air exceeds threshold
- Distal air sensor detects liquid with no cassette or sensor off
- Distal air-in-line not detected
- Distal occlusion detected
- Distal occlusion with auto-restart configured
- Electrical safety test fails
- Electrical safety test failure
- Error writing or reading SCP registers
- Fatal software failures
- Generic I/O valve motor error
- Generic L/S valve motor error
- Generic plunger motor error
- Incorrect FLASH memory type on CE module
- Infuser settings reset to factory defaults (software v15.1 and earlier)
- Infuser settings reset to factory defaults (software v15.11 and later)
- Key held down for 2+ consecutive minutes
- Keypad buttons not responding
- Keypad functional test failure
- Keypad locked due to inadvertent input during delivery
- Keypad locked during delivery interruption
- Keypad test fails
- LCD bias out of range during self test
- Library key error
- Network configuration failure
- Network reset to factory defaults
- Power hold signal stuck
- Pressure sensor fails during delivery mode
- Pressure sensor out of range while sensor off
- Proximal air detected
- Proximal air in lines exceeds threshold
- Proximal air on Line A exceeds threshold
- Proximal air on Line B exceeds threshold
- Proximal air sensor self test fails or detects liquid with cassette removed
- Proximal air-in-line not detected
- Proximal occlusion on Line A during startup
- Proximal occlusion on Line B
- Proximal occlusion on Line B during delivery
- Pump positioned too high above patient
- Pump positioned too high above patient
- Pumping does not resume after line unclamped
- Real-time clock failure or invalid date/time
- ROM checksum failure during self test
- SCP register read/write error
- SEEP block corrupted
- SEEP calibration data CRC error
- SEEP write verify read back error
- Software attempting write to non-existent SEEP address
- Software stack memory overflow
- Unrestricted flow alarm
- Unrestricted flow during cassette removal
- Unrestricted flow from infusion mechanism
- Unrestricted flow occurs
- Volume infused and program delivery rate mismatch
- Watchdog time limit out of range during power-on self test
- Write with verify read back failure during power-on self test
77 more symptoms with ranked causes and checks are in ServiceForge. Connect ServiceForge to your AI
Error codes
| Code | Meaning | Trigger | Severity |
|---|---|---|---|
E300 | ADC test error during power-on self-test and initialization | Analog-to-digital converter test fails during device startup | error |
E300 | ADC test error during power-on self-test | Analog-to-Digital Converter test fails during device initialization | error |
E301 | Audio alarm (piezo) failure | Piezo speaker detection fails; sensor reports piezo off when on or on when off | error |
E301 | Audio alarm (piezo) failure detected | Piezo alarm state mismatch: piezo off but sensed on, or on but sensed off | error |
E302 | Display backlight failure (CCFT tube voltage out of range) | Backlight CCFT tube voltage not in expected operating range | error |
E302 | Display backlight (CCFT tube) failure | Backlight voltage measured outside expected operating range during self-test | error |
E320 | Battery current out of normal operating range | Average battery current measurement exceeds safe limits during operation | error |
E320 | Battery current out of range; excessive current draw detected | Average battery current exceeds limits or current limiting circuitry failure detected | error |
E321 | Battery charging current did not drop below threshold after 8 hours | Charging current remains above end-of-charge threshold after 8-hour charge cycle | error |
E321 | Battery charging current failure after long charge cycle | Charging current fails to drop below end-of-charge threshold within 8 hours or below 1 ampere within 6 hours | error |
E322 | Battery zero reference ADC out of correct range | Battery voltage reference measurement fails during power-on self-test | error |
E322 | Battery zero reference outside correct ADC count range | Battery voltage reference point fails ADC calibration check during power-up | error |
E323 | Battery trickle charge current above expected after full charge | Trickle charge current exceeds threshold after battery reaches full charge | error |
E323 | Battery trickle charge current above expected value when fully charged | Trickle charge current exceeds acceptable level after battery reaches full charge | error |
E324 | Battery over-voltage input pin asserted | Battery voltage regulation detects over-voltage condition on input monitoring pin | error |
E324 | Battery over-voltage input pin asserted | Battery over-voltage protection input pin has been triggered | critical |
E325 | Battery voltage exceeds expected operating limit | Measured battery voltage greater than upper specification limit | error |
E325 | Battery voltage measured above safe operating maximum | Measured battery voltage exceeds upper safety limit during power-on self-test | error |
E326 | Battery not detected by power supply circuit | Battery presence not recognized during power-on self-test; no connection detected | error |
E326 | Battery not detected by system | Battery voltage or presence signal not detected during startup or during operation | error |
E328 | Battery charge current too high after 6 hours of charging | Charging current measured at 6-hour mark exceeds expected value | error |
E328 | Battery charge current remains high after 6-hour charging | After 6 hours of charging, battery charge current measured above expected threshold | error |
E340 | SCP (SPI controller) register read/write error | Error detected when writing to or reading from SCP control registers during self-test | error |
E340 | Error reading or writing SPI controller registers during power-up | SPI controller register test fails during power-on CPU initialization | error |
E341 | Critical data verification error in infusion mechanism | Data structure in infusion mechanism or control system fails CRC/parity check | error |
E341 | Critical data verify error during power-on | Stored critical data fails checksum or integrity verification during self-test | error |
E342 | Display Controller IC communication error | Display controller integrated circuit fails to respond or communicate with CPU during self-test | error |
E342 | Display controller IC error or communication failure | Display controller integrated circuit detects internal error or fails communication test | error |
E343 | Distal air sensor detects liquid with no cassette or when sensor OFF | Air detector sees liquid when cassette not inserted or sensor is disabled | critical |
E343 | Distal air sensor detects liquid with no cassette or sensor off | Sensor detects liquid when cassette absent or sensor disabled | error |
E344 | Distal air sensor self test ongoing with cassette inserted or sensor out of range | Self test active while cassette present or sensor out of range | error |
E344 | Distal air sensor self test error | Self-diagnostic failing while cassette is inserted or sensor is out of range after power-on | critical |
E345 | Pressure sensor out of range while OFF | Pressure sensor reading out of spec when disabled | critical |
E345 | Pressure sensor out of range while sensor off | Sensor reports out-of-range values during disabled state | error |
E346 | Pressure sensor fails during delivery mode | Sensor malfunction detected while infuser actively delivering | error |
E346 | Pressure sensor fails during delivery | Pressure sensor malfunction while pump actively infusing | critical |
E347 | Watchdog timer limit exceeded during boot | CPU watchdog timer out of range during power-on self test | critical |
E347 | Watchdog time limit out of range during power-on self test | Watchdog timer measurement exceeds valid range at startup | error |
E378 | Generic I/O valve motor error | Motor fails to respond or stalls during operation | error |
E378 | Generic I/O valve motor error | I/O valve motor fails during control test | critical |
E379 | Generic L/S valve motor error | Load/sense valve motor fails during control | critical |
E379 | Generic L/S valve motor error | Load/supply valve motor fails or stalls | error |
E380 | Generic plunger motor error | Plunger motor fails to respond or stalls | error |
E380 | Generic plunger motor error | Plunger drive motor malfunction | critical |
E430 | Proximal air sensor detects liquid inappropriately | Air detector sees liquid with no cassette or when sensor disabled | critical |
E430 | Proximal air sensor detects liquid with no cassette or sensor off | Sensor detects liquid when cassette absent or sensor disabled | error |
E431 | Proximal air sensor self test fails or detects liquid with cassette removed | Self test ongoing with cassette inserted or liquid detected when cassette removed | error |
E431 | Proximal air sensor self test fails | Proximal sensor self-diagnostic fails or detects liquid when cassette removed | critical |
E432 | Pressure sensor out of range while disabled | Proximal pressure sensor reading out of spec when OFF | critical |
E432 | Pressure sensor out of range while sensor off | Sensor reports out-of-range during disabled state | error |
E433 | Proximal pressure sensor failed during delivery mode | Sensor failure detected while infuser in active delivery | error |
E433 | Proximal pressure sensor failed during delivery | Proximal pressure sensor malfunction while pump in delivery mode | critical |
E434 | Memory verify error during self test | Write and read-back mismatch during power-on self test | critical |
E434 | Write with verify read back failure during power-on self test | Memory write verification fails at startup diagnostics | error |
E435 | Real-time clock failure or invalid date/time during power-on self test | Current date or time invalid, or RTC malfunction detected | error |
E435 | Real-time clock or date/time invalid | RTC circuit fails or date/time value corrupt during boot self test | critical |
E436 | ROM checksum failure | ROM code CRC mismatch during power-on self test | critical |
E436 | ROM checksum failure during power-on self test | ROM data integrity check fails at startup | error |
E437 | Various fatal software failures | Multiple software error conditions detected | critical |
E437 | Fatal software failure | Multiple firmware errors or exception caught by watchdog | critical |
E438 | Software stack memory overflow | Stack pointer exceeded memory bounds | critical |
E438 | Software stack memory overflow | Software stack exceeds available memory space | error |
E439 | Key held or activated for 2+ consecutive minutes | Any keypad key continuously pressed for ≥2 minutes | error |
E439 | Key stuck or held for 2+ minutes | Any button continuously pressed for at least 2 consecutive minutes | critical |
E440 | Power hold signal stuck | Power control latch failed to release during shutdown sequence | critical |
E440 | Power hold signal stuck | Power circuit stuck in hold state during shutdown | critical |
E443 | LCD bias out of range during power-on self test | Display bias voltage outside valid range at startup | error |
E443 | LCD bias voltage out of range | Display bias supply voltage out of spec during power-on self test | critical |
E444 | CPU timer and RTC time mismatch | System timer and real-time clock readings differ during self test | critical |
E444 | CPU timer 2 and RTC measured times mismatch during power-on self test | CPU timer 2 and real-time clock measurements do not match | error |
E445 | Real-time clock time invalid during power-on self test | RTC time value out of valid range at startup | error |
E445 | Real-time clock time invalid during boot | RTC returns invalid date/time value during power-on self test | critical |
E446 | CPU timer 1 and 2 time mismatch | Two independent CPU timer outputs diverge during boot self test | critical |
E446 | CPU timer 1 and timer 2 measured times mismatch during power-on self test | Internal timer measurements do not match | error |
E447 | Battery ADC value at high or low limit of range | Battery voltage measurement at extreme edge of valid range | warning |
E447 | Battery ADC value at limit | Battery voltage reading at high or low threshold during self test | critical |
E448 | SEEP write verify error | SEEP (Storage Element Electrical Programmable) memory write-back verification fails | critical |
E448 | SEEP write verify read back error | Secondary EEPROM write verification fails | error |
E449 | SEEP calibration data CRC error | Secondary EEPROM calibration data integrity check fails | error |
E449 | SEEP calibration CRC error | Calibration data stored in SEEP fails integrity check | critical |
E451 | Volume and rate delivery mismatch | Calculated delivered volume does not match programmed delivery rate | critical |
E451 | Volume infused and program delivery rate mismatch | Measured infused volume does not match programmed rate | error |
E453 | SEEP block corrupted | Secondary EEPROM block data corrupted | error |
E453 | SEEP block corrupted | SEEP data block fails integrity check during memory test | critical |
E454 | Invalid SEEP write address | Software attempts to write to non-existent SEEP memory location | critical |
E454 | Software attempting write to non-existent SEEP address | Firmware attempts memory write outside valid address space | critical |
E455 | Incorrect FLASH non-volatile memory type on CE module | CE module contains incompatible or incorrect flash memory | error |
E455 | Incorrect FLASH memory type on CE module | FLASH chip on CE module does not match expected type or is missing | critical |
E456 | Library key error | Drug library encryption key validation fails | critical |
E456 | Library key error | Drug library key validation fails | error |
E457 | CRC failure on drug library | Drug library data integrity check fails | error |
E457 | Drug library CRC failure | Drug library data integrity check fails during startup | critical |
E458 | Broken distal pin detected | Distal cassette pin broken during self test or cassette insertion test | critical |
E458 | Broken distal pin detected during cassette test | Cassette self test detects broken or missing distal pin | error |
N101 | No action timeout alarm (multiple contexts) | Operator fails to respond within 15 seconds to 2 minutes to on-screen prompt | warning |
N101 | Timeout on titration confirmation with standby option | No operator action for 30 seconds; standby possible | warning |
N101 | Delivery start not completed | No operator action for 15 seconds after pressing START hardkey | warning |
N101 | Timeout on new program confirmation with standby option | No operator action for 2 minutes; standby possible | warning |
N101 | Timeout on Line A stop requiring clear or restart | No operator action for 2 minutes after Line A stopped | warning |
N102 | Programming not complete after power-on | No operator input for 2 minutes after power-on in Clinical mode | warning |
N102 | Programming not complete | No operator input for 2 minutes after power-on in Clinical mode or with cassette installed | warning |
N103 | Data cleared; reprogramming required | Retention memory (SEEP) corruption detected; autoclear activated | error |
N103 | Delivery parameters corrupted and cleared | Corruption of retained delivery parameters detected | error |
N104 | Callback alarm triggered on Line B completion | Line B VTBI reaches 0 with callback configured | info |
N104 | Callback to Line B | Line B VTBI reaches 0 (Loading Dose or multistep delivery step) with Callback configured | info |
N105 | Callback to Line A | Line A VTBI reaches 0 (Loading Dose or multistep delivery step) with Callback configured | info |
N105 | Callback alarm triggered on Line A completion | Line A VTBI reaches 0 with callback configured | info |
N106 | Bolus delivery complete on Line B | Bolus delivery completes on Line B with callback configured | info |
N106 | Bolus complete on Line B | Bolus delivery completes on Line B with Nurse Callback configured | info |
N107 | Bolus complete on Line A | Bolus delivery completes on Line A with Nurse Callback configured | info |
N107 | Bolus delivery complete on Line A | Bolus delivery completes on Line A with callback configured | info |
N108 | Cassette door opened during delayed start | Cassette door opened while infusion in Delayed Start | error |
N108 | Cassette door opened during Delayed Start | Cassette door opened while infusion in Delayed Start state | warning |
N160 | Line B VTBI completed | Line B delivery VTBI reaches 0 under prior or current CCA | info |
N160 | Line B VTBI complete in prior CCA with concurrent delivery | Line B delivery complete from different CCA; Line B concurrent | info |
N160 | Line B piggyback delivery complete | Line B piggyback delivery complete; no Line A programmed | info |
N161 | Line A VTBI complete in prior CCA | Line A delivery complete from different CCA | info |
N161 | Line A VTBI completed | Line A delivery VTBI reaches 0 under prior or current CCA | info |
N180 | Distal occlusion detected | Distal occlusion detected during backprime or cassette check | error |
N180 | Distal occlusion detected | Distal blockage while attempting backprime or during cassette check | warning |
N183 | Proximal occlusion detected on Line B | Proximal occlusion on Line B during cassette integrity test | error |
N183 | Proximal occlusion detected on Line B | Proximal blockage on secondary line during cassette integrity test (peak detection algorithm) | warning |
N184 | Proximal occlusion detected on Line A | Proximal blockage on primary line during backprime (negative detection algorithm) | warning |
N184 | Proximal occlusion detected on Line A | Proximal occlusion on Line A during backprime | error |
N185 | Proximal occlusion detected on Line A during cassette integrity test (peak detection) | Cassette integrity test detects proximal occlusion on Line A | warning |
N185 | Proximal occlusion on Line A at startup | Proximal blockage on primary line during cassette integrity test (peak detection algorithm) at startup | warning |
N186 | Distal occlusion during delivery with auto-restart exhausted | Distal blockage during delivery after maximum auto-restarts exhausted or auto-restart disabled; or N192 active for 60 seconds without pressure drop | error |
N186 | Distal occlusion detected during delivery after maximum auto-restarts | Peak detection algorithm detects distal occlusion and maximum auto-restarts have occurred or auto-restart is off | warning |
N187 | Pump mounted too high above patient causing distal occlusion | Negative detection algorithm detects distal occlusion due to pump height | warning |
N187 | Pump positioned too high above patient | Distal occlusion detected during delivery (negative detection algorithm) | warning |
N188 | Proximal occlusion detected on Line B during delivery | Proximal blockage on Line B during delivery (negative detection algorithm) | warning |
N188 | Proximal occlusion detected on Line B (negative detection algorithm) | Negative detection algorithm detects occlusion on Line B during delivery | warning |
N189 | Proximal occlusion detected on Line B (peak detection algorithm) | Peak detection algorithm detects occlusion on Line B during delivery | warning |
N189 | Proximal occlusion on Line B during delivery | Proximal blockage on Line B during delivery (peak detection algorithm) | warning |
N190 | Proximal occlusion detected on Line A during delivery | Proximal blockage on Line A during delivery (negative detection algorithm) | warning |
N190 | Proximal occlusion or air detected on Line A during delivery (negative detection) | Negative detection algorithm detects occlusion or air on Line A during infusion | warning |
N191 | Proximal occlusion or air detected on Line A during delivery (peak detection) | Peak detection algorithm detects occlusion or air on Line A during infusion | warning |
N191 | Proximal occlusion or air detected on Line A during delivery | Proximal blockage or air on Line A during delivery (peak detection algorithm) | warning |
N192 | Distal occlusion paused with auto-restart enabled | Distal occlusion detected (peak detection algorithm) with auto-restart enabled and max retries not yet reached | warning |
N192 | Distal occlusion detected; auto-restart configured and in progress | Peak detection algorithm detects distal occlusion with auto-restart enabled and retry attempts remaining | warning |
N230 | Cumulative proximal air from both lines exceeds threshold | Cumulative air detected at proximal sensor from Line A and Line B combined | warning |
N230 | Cumulative proximal air detected on Lines A and B | Cumulative proximal air from Line A and Line B combined exceeds air detection threshold | warning |
N231 | Proximal air bolus detected on Line B | Single air bolus at proximal sensor on Line B exceeds air detection threshold | warning |
N231 | Proximal air on Line B exceeds threshold | Single air bolus at proximal sensor in Line B exceeds detection threshold | warning |
N232 | Proximal air on Line A exceeds threshold | Single air bolus at proximal sensor in Line A exceeds detection threshold | warning |
N232 | Proximal air bolus detected on Line A | Single air bolus at proximal sensor on Line A exceeds air detection threshold | warning |
N233 | Cumulative air detected at distal sensor | Cumulative air at distal sensor exceeds air detection threshold | warning |
N233 | Cumulative distal air exceeds threshold | Cumulative air detected at distal sensor exceeds threshold | warning |
N234 | Single distal air bolus exceeds threshold | Single air bolus at distal sensor exceeds detection threshold | warning |
N234 | Single air bolus detected at distal sensor | Single air bolus at distal sensor exceeds air detection threshold | warning |
N250 | Cassette door opened during delivery | Cassette door opened while infusion is running | warning |
N250 | Cassette door opened during active infusion | Cassette door was opened while infusion delivery was running | info |
N251 | Cassette integrity test failed | Cassette test detected fault, occlusion, or air during startup integrity check | warning |
N251 | Cassette test failure detected | Faulty cassette, proximal occlusion, or air detected during cassette integrity test | error |
N252 | Battery voltage depleted below safe level | Infuser running on battery power with voltage below depleted threshold | critical |
N252 | Battery depleted; infuser on battery power with low voltage | Infuser running on battery and voltage drops below depleted battery threshold | critical |
N255 | Keypad locked; STOP or door open attempted during lock | Keypad was locked when STOP softkey or cassette door open event occurred during delivery | info |
N255 | Keypad locked during delivery interruption | Keypad lock active when [STOP] pressed or cassette door opened during delivery | info |
N56 | Battery insufficient capacity | Battery charge capacity is depleted or battery has failed | error |
N56 | Battery does not have sufficient capacity | Battery lacks adequate charge capacity | warning |
N57 | Battery or charger did not respond to charger voltage pin state | Charger voltage pin state (VFLOAT) not recognized | error |
N57 | Battery or charger VFLOAT pin state failure | Battery or charger did not respond to charger voltage pin state signal | error |
N58 | Low battery level | Battery charge level drops below operational threshold | warning |
N58 | Battery charge level is low | Low battery charge detected | warning |
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.