Stryker Neptune Surgical Fluid Management System

“Canister Full” or Level Sensor Errors

On this page

Asset Type

Surgical Fluid Management System

Manufacturer

Stryker

Model

Neptune

What This Guide Helps With

This guide addresses situations where the Stryker Neptune displays a “Canister Full” message or generates level sensor–related errors even when the canister is not actually full.

These issues are commonly caused by float obstruction, improper canister seating, sensor misalignment, residual fluid contamination, or connection problems—not immediate internal board failure. This guide walks through logical external checks first before escalating.

Step-by-Step Troubleshooting

Ensure Patient Safety First

Confirm the Message and Current Setup

Why this matters: Identifying the affected canister prevents unnecessary removal of all containers and helps isolate the issue.

Inspect the Canister Fluid Level

Why this matters: The simplest cause of a “Canister Full” message is an actually full container.

Remove and Re-seat the Canister

Why this matters: Improper seating can prevent proper engagement of the level sensor mechanism and trigger false alarms.

Inspect the Float Mechanism

Why this matters: A stuck float will continuously signal “full” even when the canister is empty.

Inspect Sensor Contact Area

Why this matters: Fluid intrusion or contamination at the sensor interface can create false level readings.

Swap Canisters Between Positions

Why this matters:

Power Cycle the Unit

Why this matters: Temporary sensor logic faults can clear during reboot.

Check for Signs of Fluid Intrusion

If the Problem Persists

If:

Then the issue is likely internal (sensor failure, wiring issue, or control board fault).

At this point:

Knowing when to stop external troubleshooting and escalate is proper Clinical Engineering practice.

Clinical Use Tip

Never troubleshoot canister or level sensor errors while the system is actively connected to a surgical field.

If the alarm occurs during a procedure:

Patient safety always overrides troubleshooting speed.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
“Unit displaying ‘Canister Full’ alarm immediately after new empty canister installed.”

Cause

What was observed during troubleshooting.

Example:
“Level sensor falsely detecting full condition in port #2. Float mechanism moved freely. Error remained with port after canister swap.”

Resolution

What action was taken.

Example:
“Removed unit from service. Labeled Out of Service. Sent to shop for sensor evaluation and repair. Backup unit provided to OR.”

Helpful Details to Include

Final Thought

Level sensor alarms are often simple mechanical or contamination issues rather than immediate electronic failure. Start with the canister, float, and seating. Confirm with logical swaps. Escalate appropriately when the fault follows the port rather than the container.

Structured troubleshooting protects patients, reduces downtime, and prevents unnecessary part replacement.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide