Stryker Neptune 3

Weak Suction, No Suction, Or Suction Drops During Use

On this page

Asset Type

Surgical Fluid Management System

Manufacturer

Stryker

Model

Neptune 3

What This Guide Helps With

Troubleshooting weak, missing, or dropping suction caused by setup, tubing, filter, tank, docking, or external connection issues.

Step-by-Step Troubleshooting

Ensure Patient Safety First

Action: If suction is weak, absent, or dropping during a procedure, notify clinical staff immediately and provide alternate suction if needed.

Expected outcome: The patient and procedure are supported by reliable suction before troubleshooting continues.

Why it matters: Suction loss during surgical use can affect fluid removal, visualization, and procedural safety.

If alternate suction restores safe clinical operation, continue troubleshooting the Neptune only when it is safe to do so.

Verify the Reported Suction Problem

Action: Confirm the exact symptom:

Expected outcome: The failure pattern is confirmed before parts are replaced or the device is removed from service.

Why it matters: A single-port issue often points to tubing, accessories, or setup. A whole-system issue may involve vacuum generation, tank status, filters, or internal failure.

Confirm the Device Is Not in Active Alarm or Fault Condition

Action: Check the Neptune 3 display for alarms, fault messages, tank full warnings, filter warnings, docking-related issues, or system status messages.

Expected outcome: Any obvious system condition affecting suction is identified.

Why it matters: The unit may reduce or stop suction if it detects a tank, filter, airflow, or system condition that prevents safe operation.

If an alarm clearly explains the issue, correct the alarm condition first, then recheck suction.

Check Power and Startup Status

Action: Confirm the unit is powered on, fully booted, and not operating on an unstable power source. Verify the power cord is secure and the outlet is functional.

Expected outcome: The Neptune 3 powers up normally and remains on without interruption.

Why it matters: Power interruptions or incomplete startup can cause suction complaints that appear mechanical but are actually power-related.

If power correction restores suction, document the issue and stop.

Check Suction Settings

Action: Verify the suction level is set appropriately for the intended use and that the selected suction mode or control setting matches the clinical setup.

Expected outcome: The displayed suction setting matches the expected clinical demand.

Why it matters: Low settings, incorrect mode selection, or an unintended control change can be mistaken for device failure.

If correcting the setting restores suction, perform a functional check and stop.

Inspect the Suction Tubing Setup

Action: Trace the suction path from the patient-side accessory back to the Neptune. Look for:

Expected outcome: Tubing is open, properly connected, and not physically restricted.

Why it matters: Tubing restrictions are one of the most common external causes of weak or dropping suction.

If correcting the tubing restores suction, document the tubing issue and stop.

Check the Suction Accessory or Handpiece

Action: Inspect the suction wand, smoke evacuator accessory, fluid collection accessory, or surgical handpiece being used with the system.

Check for:

Expected outcome: The patient-side accessory allows clear flow.

Why it matters: A blocked accessory can make the Neptune appear to have weak suction even when the rover is functioning normally.

If swapping the accessory restores suction, document the accessory as the cause and stop.

Check for Loose or Leaking Connections

Action: Inspect all tubing and canister-style connections for poor fit, missing seals, cracked connectors, or loose adapters.

Expected outcome: The suction path is sealed and does not leak air.

Why it matters: Suction depends on an intact vacuum path. Air leaks reduce effective suction at the surgical field.

If reseating or replacing a connector restores suction, document the connection issue and stop.

Check the Fluid Collection Level and Tank Status

Action: Verify the rover is not full, near full, or reporting a tank level issue. Confirm the fluid level display makes sense compared with actual use.

Expected outcome: The tank has available capacity and the level sensing appears reasonable.

Why it matters: A full or incorrectly sensed tank may cause suction to reduce, stop, or alarm.

If the tank is full, have the rover exchanged, emptied through the proper docking process, or handled per facility procedure. Stop troubleshooting once suction is restored.

Inspect the Filter Status

Action: Check for any filter warning, airflow restriction message, or visibly saturated/incorrectly installed filter.

Expected outcome: Filters are installed correctly, dry where applicable, and not blocked.

Why it matters: Restricted airflow can reduce suction strength or cause suction to drop during use.

If filter replacement or proper installation restores suction, document the filter condition and stop.

Check for Liquid or Debris in the Wrong Area

Action: Look for signs of fluid spillover, residue, or contamination around external connection points, inlet areas, tubing ports, or filters.

Expected outcome: External ports and accessible connection areas are clean, dry, and unobstructed.

Why it matters: Fluid or debris in the suction pathway can restrict flow and may indicate improper setup, overfill, or contamination.

If fluid intrusion is suspected beyond normal external cleaning, remove the device from service for bench evaluation.

Test With Known-Good Tubing and Accessory

Action: Remove the current clinical tubing/accessory setup and test suction using known-good tubing and an appropriate test setup.

Expected outcome: Suction performance improves if the original tubing or accessory was the problem.

Why it matters: This separates a Neptune issue from a disposable or setup issue.

If suction is normal with known-good tubing, return the device only after confirming the clinical setup problem has been corrected.

Check Whether the Issue Is Port-Specific

Action: If the Neptune has multiple suction connections available, compare suction behavior between available ports using the same known-good tubing setup.

Expected outcome: All active ports should behave consistently.

Why it matters: One weak port may indicate a local obstruction, damaged connector, or port-specific issue. Weak suction on all ports points toward a broader system issue.

If one port remains weak or nonfunctional, remove the device from service for repair evaluation.

Check for Docking or Waste Transfer-Related Conditions

Action: Confirm the rover was properly docked, drained, and prepared for use before the case. Check for any recent docking, drain, or waste transfer issue reported by staff.

Expected outcome: The rover is ready for use and not carrying over a prior waste transfer problem.

Why it matters: If the system was not properly emptied or reset after docking, suction performance may be affected during the next use.

If docking or waste transfer failure is suspected, remove the rover from service until the docking issue is corrected.

Listen for Abnormal Operating Sounds

Action: During a safe test, listen for unusual motor noise, pulsing, rattling, excessive strain, or no motor activity when suction is requested.

Expected outcome: The unit sounds consistent and responds normally when suction is activated.

Why it matters: Abnormal noise or no vacuum response after external causes are ruled out may indicate internal vacuum, motor, valve, sensor, or control failure.

If abnormal internal operation is suspected, stop troubleshooting and escalate.

Perform a Final Functional Check

Action: After any correction, verify suction using a safe test setup before returning the unit to clinical use.

Expected outcome: Suction is stable, alarms are clear, tubing connections remain secure, and the unit performs as expected.

Why it matters: A temporary improvement is not enough. The device must demonstrate stable suction before returning to service.

If suction is restored and stable, document the corrective action and return the unit per facility process.

If the Problem Persists

If weak suction, no suction, or suction drop continues after checking power, settings, tubing, accessories, filters, tank status, docking history, and external connections, the common external causes have been ruled out.

The issue may involve an internal vacuum system fault, sensor problem, valve restriction, control issue, or fluid contamination beyond basic troubleshooting.

The device should be removed from service, labeled Out of Service, and sent for repair or bench evaluation.

Knowing when to stop is proper troubleshooting. Do not continue using a Neptune 3 with unreliable suction, especially in a surgical environment.

Clinical Use Tip

Do not troubleshoot suction loss on an active patient unless clinical staff have already secured alternate suction and it is safe to continue. For surgical cases, patient safety and procedure continuity come first. Move suction support to another device before performing extended troubleshooting.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"OR staff reported the Stryker Neptune 3 had weak suction and suction dropped during fluid collection."

Cause

What was observed during troubleshooting.

Example:
"Found suction tubing partially kinked behind the rover and one tubing connection not fully seated."

Resolution

What action was taken.

Example:
"Rerouted tubing, secured the connection, verified stable suction with known-good tubing, and returned the unit to service."

Helpful Details to Include (If Known)

Final Thought

Weak suction on a Neptune 3 should be approached logically. Start with patient safety, then rule out setup, tubing, accessory, filter, tank, docking, and connection problems before suspecting internal failure. If suction remains unreliable after external checks, remove the device from service and document the complaint, cause, and resolution clearly.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide