ndd Medical EasyOne Series

Wireless / Bluetooth Connectivity Failure

On this page

Asset Type

Pulmonary Function Tester

Manufacturer

ndd Medical

Model

EasyOne Series

What This Guide Helps With

Identifies causes of failed wireless or Bluetooth connection including pairing issues, interference, settings misconfiguration, or device communication faults.

Step-by-Step Troubleshooting

Ensure Patient Safety First

Expected Outcome: Safe environment for troubleshooting without impacting patient care.

Verify Reported Issue and Device Behavior

Expected Outcome: Consistent failure confirms a true connectivity issue.

Why: Helps rule out temporary communication drops or user workflow interruption.

Confirm Bluetooth / Wireless is Enabled on Device

Expected Outcome: Device is visible to other systems during scan.

Why: Disabled wireless settings are a common and easily missed cause.

Verify Receiving Device (PC / Tablet) Settings

Expected Outcome: Receiving device detects available Bluetooth devices.

Why: Connectivity issues may originate from the host system, not the spirometer.

Remove and Re-Pair Device

Expected Outcome: Successful pairing and stable connection.

Why: Corrupt or outdated pairing records commonly cause connection failures.

Check for Interference or Range Issues

Expected Outcome: Improved connection stability when closer and in low-interference environment.

Why: Bluetooth is sensitive to environmental interference and distance.

Inspect for Multiple Device Conflicts

Expected Outcome: Device becomes available for new connection.

Why: Many Bluetooth devices only support one active connection at a time.

Verify Software / Application Status

Expected Outcome: Software recognizes and communicates with the device.

Why: Software misconfiguration or crashes can block communication.

Check Battery Level and Power Stability

Expected Outcome: Stable connection after ensuring sufficient power.

Why: Wireless modules may malfunction or disable under low power conditions.

Perform Full Device Restart

Expected Outcome: Connection restores after reset.

Why: Resolves temporary communication or firmware-related glitches.

If the Problem Persists

If all external causes have been ruled out, the issue is likely related to internal wireless hardware or firmware failure.

Remove the device from service, label it Out of Service, and send for repair or bench evaluation.

Knowing when to stop prevents unnecessary risk and wasted troubleshooting time.

Clinical Use Tip

Do not attempt to troubleshoot wireless connectivity while a patient test is in progress.

Always move the patient to a functioning device before proceeding.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Staff reported EasyOne spirometer would not connect to tablet via Bluetooth."

Cause

What was observed during troubleshooting.

Example:
"Corrupt Bluetooth pairing and device previously connected to another workstation."

Resolution

What action was taken.

Example:
"Removed old pairing, restarted devices, and successfully re-paired spirometer to tablet."

Helpful Details to Include (If Known)

Final Thought

Wireless issues are often caused by simple configuration or pairing problems rather than hardware failure. Following a structured, external-first approach ensures efficient troubleshooting while maintaining patient safety and minimizing downtime. Proper documentation supports faster resolution if escalation is required.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide