On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Identifies external causes of system freezing or lost PC communication such as cable issues, software crashes, power interruptions, or USB/serial connection problems.
Step-by-Step Troubleshooting
1. Ensure Patient Safety First
- Confirm the device is not actively being used on a patient
- Move testing to another spirometer if needed
Expected Outcome: Safe troubleshooting environment without impacting patient care.
2. Observe System Behavior
- Determine if the issue is complete system freeze (no response)
- Check for intermittent freezing
- Identify if there is loss of communication with PC/software
Expected Outcome: Clear understanding of whether this is a software, communication, or hardware-related issue.
Why: Helps guide whether to focus on connections, software, or system stability.
3. Perform a Controlled Restart
- Close the spirometry software (if responsive)
- Reboot the PC or device properly
Expected Outcome: System returns to normal operation.
Why: Temporary software crashes are common and often resolved with a restart.
4. Verify Physical Connection to PC
- Check all communication cables (USB or serial)
- Ensure fully connected at both ends
- Confirm no looseness or visible damage
- Disconnect and reconnect firmly
Expected Outcome: Stable connection restores communication with the software.
Why: Loose or faulty cables are a common cause of connection loss.
5. Check USB Port / Communication Port
- Try a different USB port on the PC
- Avoid using USB hubs if possible
- Confirm the device is recognized by the PC
Expected Outcome: Device appears correctly in the system and reconnects to software.
Why: Faulty ports or hubs can interrupt communication.
6. Confirm Software is Running Properly
- Restart the spirometry application
- Check for error messages or frozen screens
- Verify the correct device is selected within the software
Expected Outcome: Software communicates properly with the spirometer.
Why: Incorrect device selection or software lockup can mimic hardware issues.
7. Check PC Performance and Background Processes
- Close unnecessary applications
- Check if PC is slow, lagging, or overloaded
Expected Outcome: Improved system responsiveness and stable operation.
Why: Low system resources can cause software freezing or communication drops.
8. Inspect Power Stability
- Ensure the device and PC are connected to stable power
- Check for loose power cords or intermittent power
Expected Outcome: Consistent power prevents unexpected disconnects or freezes.
Why: Power interruptions can cause communication loss or system instability.
9. Test with Known Good Cable (if available)
- Swap the communication cable with a known working one
Expected Outcome: If resolved, original cable was faulty.
Why: Cable failure is a common and easily overlooked issue.
If the Problem Persists
If all external connections, software conditions, and power sources have been verified, the issue is likely internal (interface board, communication module, or software corruption).
Remove the device from service, label it Out of Service, and send for repair or bench evaluation.
Clinical Use Tip
Do not attempt to troubleshoot communication or software issues while testing a patient. Always transition to another device before troubleshooting.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Spirometry system freezing during testing and losing connection to PC software."
Cause
What was observed during troubleshooting.
Example:
"Loose USB communication cable intermittently disconnecting device from PC."
Resolution
What action was taken.
Example:
"Reseated and secured USB cable; verified stable communication and normal operation."
Helpful Details to Include (If Known)
- USB/communication cable condition and connection status
- PC responsiveness during issue
- Error messages or freeze behavior
- Ports tested or changed
- Power stability verified
- Final device status (operational or removed from service)
Final Thought
Software and communication issues are often caused by simple external factors like cables, ports, or system performance. A structured approach ensures patient safety, minimizes downtime, and avoids unnecessary escalation. Proper documentation supports long-term reliability and repeat troubleshooting success.
That is successful troubleshooting.