On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide assists Clinical Engineering in troubleshooting Jaeger Medical Vyntus pulmonary function testing systems that experience software freezes or lose communication with the connected PC. Because the Vyntus platform relies heavily on a host computer for operation, many issues originate from external factors such as USB or network communication problems, PC performance issues, or software instability rather than internal device failure.
The goal is to check common external causes first before assuming hardware failure.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Before troubleshooting, ensure the pulmonary function test is not actively being performed.
- If the system froze during testing, the patient should be safely disconnected and testing moved to another device if available.
Check for Complete Software Freeze
- Determine whether the Vyntus software interface is fully frozen or partially responsive.
- Attempt to move the mouse and select menus.
- Check if the PC desktop is still responsive.
- Observe whether error messages are displayed.
- This helps determine if the issue is with the software application or the entire PC.
Verify PC Power and Performance
- Because Vyntus systems depend on the connected workstation, PC issues can cause the software to freeze.
- Check for:
- High CPU or memory usage
- Windows error messages
- Unresponsive desktop
- Other applications running in the background
- If the PC appears unstable, rebooting the workstation may resolve the issue.
Inspect USB and Interface Connections
- Vyntus systems typically communicate with sensors and modules through USB or interface hubs.
- Check the following:
- USB cables between the Vyntus hardware and PC
- Loose or partially disconnected cables
- Damaged USB ports
- Interface hub power (if present)
- If possible, reseat the USB cables and confirm the connections are secure.
Check Module Power Indicators
- Verify that the Vyntus hardware modules have power.
- Look for:
- Status LEDs on the flow module or body box interface
- Indicator lights on USB interface devices
- Any unusual blinking patterns or absence of lights
- Loss of power to a module can cause the PC software to freeze while waiting for a response.
Restart the Vyntus Software Application
- If the PC remains responsive but the Vyntus software is frozen:
- Close the Vyntus application
- Reopen the software
- Verify that the system reconnects to the hardware modules
- Many freezes are resolved with a simple application restart.
Perform a Controlled System Restart
- If the software cannot be closed or the PC is unresponsive:
- Restart the PC
- Allow the Vyntus hardware modules to power cycle during the restart
- Launch the software again and verify that the system reconnects to the hardware
- Restarting both the PC and device interface can reestablish communication.
Verify Device Detection After Restart
- Once the system is restarted:
- Launch the Vyntus software
- Confirm that the system detects connected hardware modules
- Attempt a calibration or test to verify communication
- If the software fails to detect the device after restart, a communication issue may still exist.
Check Network Connectivity (If Applicable)
- Some Vyntus systems communicate with hospital networks or patient databases.
- Verify:
- Ethernet cable connections
- Network access
- Software login capability
- Network instability can sometimes cause application delays or freezes.
If the Problem Persists
If the above checks have been completed and the software continues to freeze or the PC cannot maintain communication with the Vyntus hardware, common external causes have likely been ruled out.
The issue may involve:
- Internal interface hardware
- Flow module communication electronics
- USB interface boards
- Software corruption or configuration issues
At this point the device should be:
- Removed from service
- Labeled Out of Service
- Sent for bench evaluation or manufacturer service
Recognizing when troubleshooting has reached the limit of external checks is an important part of proper Clinical Engineering practice.
Clinical Use Tip
Never attempt to troubleshoot a pulmonary function testing system while it is connected to a patient. If a freeze occurs during testing, the patient should be safely disconnected and moved to another system before troubleshooting begins.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
“User reported the Vyntus pulmonary function testing system froze during testing and the software stopped responding. PC displayed no communication with the flow module.”
Cause
What was observed during troubleshooting.
Example:
“Inspection revealed the Vyntus software was frozen while the PC remained operational. USB communication between the Vyntus hardware module and workstation was briefly lost.”
Resolution
What action was taken.
Example:
“USB connections were reseated and the PC was restarted. The Vyntus software relaunched successfully and the system reconnected to the hardware. Calibration was completed and the unit was returned to service.”
Helpful Details to Include (If Known)
- PC reboot performed
- USB cables inspected and reseated
- Hardware indicator lights observed
- Software error messages present or absent
- Device detection after restart
- Calibration test results
- Final device status
Final Thought
Pulmonary function testing systems such as the Vyntus series rely heavily on stable communication between hardware modules and the host PC. Most freezes or connection losses are caused by external communication or software issues rather than internal device failure. Logical troubleshooting, starting with simple connection and PC checks, helps resolve many problems quickly while ensuring patient testing is not interrupted unnecessarily.
That is successful troubleshooting.