On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting failed network communication or data export caused by disconnected cables, inactive ports, configuration errors, removable media, or external system problems.
Step-by-Step Troubleshooting
1. Ensure Patient Safety First
Do not interrupt ventilation or restart the Puritan Bennett 980 while it is actively supporting a patient solely to troubleshoot a communication problem.
- Confirm that ventilation, monitoring, and alarms remain functional.
- Notify respiratory therapy and the clinical team that networked data, charting, or exported records may be unavailable.
- Use the facility’s approved alternate documentation method until communication is restored.
- Move the patient to another verified ventilator before performing any action that could interrupt ventilation.
Expected outcome: Patient ventilation remains uninterrupted while the communication problem is evaluated safely.
Continue Clinical Engineering troubleshooting only when the device can be evaluated without placing the patient at risk.
2. Identify the Exact Communication Failure
Determine which function is affected:
- Network connection to a clinical information system
- Connection to a device-integration gateway
- Serial data output
- Ethernet communication
- USB data export
- Screen capture or trend export
- Software or service data transfer
- Intermittent communication rather than complete loss
Record any displayed message, interface status, failed export notification, or downstream system alarm.
Expected outcome: The affected interface and failure pattern are clearly identified.
If the issue involves only one external destination, begin with that connection rather than assuming the ventilator has failed.
3. Confirm Normal Ventilator Operation
Verify that:
- The ventilator completes startup normally.
- The graphical user interface is responsive.
- No system diagnostic, hardware, or software fault is displayed.
- Ventilation and alarms operate normally on an approved test setup.
A broader startup or software problem may prevent communication interfaces from operating correctly.
Expected outcome: The problem is isolated to communication or data export rather than general ventilator operation.
If the ventilator shows other operational failures, remove it from service and address those failures first.
4. Inspect External Communication Connections
Inspect all applicable external connections for:
- Loose or partially inserted plugs
- Disconnected Ethernet or serial cables
- Bent pins or damaged connector shells
- Broken locking tabs
- Cable strain near the connector
- Contamination, corrosion, or liquid residue
- Cables connected to the wrong port
- Unsupported adapters or extension cables
Reseat each connection only after confirming that doing so will not disrupt active patient care.
Expected outcome: All cables are correctly connected and free of visible damage.
If reseating a loose cable restores communication, verify stable data transfer and stop.
5. Verify the Correct Interface and Cable Type
Confirm that the connected cable and interface match the hospital integration design.
Check whether the system is intended to use:
- Ethernet networking
- A serial communication interface
- A vendor-approved gateway
- A USB storage device
- Another approved external data interface
Do not assume that a cable fitting physically means it is wired, configured, or supported correctly.
Expected outcome: The ventilator is connected through the intended port using the correct cable and approved interface equipment.
If the wrong cable, adapter, or port was used, correct the connection and retest.
6. Test the External Cable
Replace the communication cable with a known-good cable of the same approved type.
For Ethernet connections, confirm that:
- The cable is fully seated at both ends.
- The connector latch holds securely.
- The wall jack, switch port, or integration-device port is known to be functional.
For serial connections, confirm that:
- The correct cable wiring or pin configuration is being used.
- Any required locking screws are secured.
- No unsupported null-modem adapter, converter, or extension is installed.
Expected outcome: Communication returns with a known-good cable, identifying the original cable as the cause.
If the replacement cable does not restore communication, continue.
7. Check the External Network or Integration Device
Inspect the connected external equipment, such as:
- Network switch
- Wall jack
- Bedside device gateway
- Data acquisition unit
- Serial-to-network converter
- Clinical information system interface
- Integration server connection
Confirm that the external device has power and shows its expected status indicators.
Connect the PB980 to a known-good approved network or gateway port when facility policy permits. Alternatively, connect a known-good compatible device to the original port to determine whether the external infrastructure is functioning.
Expected outcome: The problem is isolated either to the ventilator or to the external network and integration path.
If another device also fails on the same connection, escalate the network or integration issue to the responsible IT or clinical systems team.
8. Verify Network Configuration
Coordinate with the facility’s IT or device-integration team to confirm the assigned network configuration.
Check, as applicable:
- IP address
- Subnet mask
- Gateway
- Port or destination settings
- Device identifier
- Duplicate IP address
- Required network segment or VLAN
- Approved interface protocol
- Integration-server destination
- Firewall or access-control changes
Do not change network parameters without authorization and documented configuration information.
Expected outcome: The ventilator’s communication settings match the approved hospital integration configuration.
If correcting an authorized configuration error restores communication, verify data receipt at the destination and stop.
9. Confirm Destination-System Status
Verify that the receiving system is available and actively accepting data.
Ask the responsible support team to confirm:
- The interface server is online.
- The ventilator is assigned to the correct bed or location.
- The device is registered in the integration platform.
- The receiving interface has not been disabled.
- No interface queue, service, certificate, or server error is present.
- Recent network or software changes have not interrupted communication.
A ventilator may transmit correctly while the downstream system fails to display or store the information.
Expected outcome: The receiving system is confirmed operational or identified as the cause.
If the downstream system is responsible, document the finding and transfer the incident to the appropriate support group.
10. Evaluate USB Data Export Separately
When the reported problem involves USB export:
- Confirm that the USB device is approved by facility policy.
- Inspect the USB connector for damage or contamination.
- Confirm that the storage device has available space.
- Remove unsupported files or partitions when permitted.
- Try a known-good compatible USB storage device.
- Allow the ventilator sufficient time to recognize the device.
- Follow the on-screen export process without removing the drive prematurely.
Do not connect an unknown or unapproved USB device to the ventilator.
Medtronic previously issued a PB980 software update addressing external USB-drive performance and its potential effect on graphical user interface operation. Software revision and applicable field actions should therefore be verified when USB behavior is abnormal.
Expected outcome: The ventilator recognizes the approved storage device and completes the export successfully.
If one USB device works and another does not, remove the incompatible or failed storage device from use.
11. Perform a Controlled Restart When Safe
If the communication interface remains unresponsive and the ventilator is not supporting a patient:
- Record current settings and the reported condition.
- Disconnect it from clinical use.
- Shut down the ventilator normally.
- Wait for shutdown to complete.
- Restart the device.
- Confirm that startup completes without errors.
- Recheck the communication interface.
Do not repeatedly power-cycle the ventilator.
Expected outcome: A temporary software or interface-state problem clears and communication resumes.
If communication returns, perform repeated connection or export checks before returning the ventilator to service.
12. Check Software Revision and Service History
Review the ventilator’s:
- Installed software revision
- Previous communication-related repairs
- Open manufacturer field actions
- Recent software updates
- Recent network or integration changes
- USB-related history
The PB980 has had manufacturer software updates affecting external USB-drive behavior, so outdated software or incomplete field-action implementation should be considered during evaluation.
Do not install or alter ventilator software unless authorized, trained, and following current manufacturer service documentation.
Expected outcome: The software revision and field-action status are confirmed current or referred for authorized correction.
13. Verify Communication Before Return to Service
After correcting the problem:
- Reconnect the approved cable or storage device.
- Confirm stable communication over multiple checks.
- Verify that the destination receives the correct device data.
- Confirm that exported files can be opened by the approved system.
- Inspect the interface for intermittent loss when the cable is gently repositioned.
- Confirm normal ventilator operation and alarm functionality.
- Complete any required functional verification.
Expected outcome: Communication remains reliable and the ventilator passes all required return-to-service checks.
If communication remains intermittent or cannot be verified, do not return the ventilator to service.
If the Problem Persists
If known-good cables, external ports, approved media, configuration settings, receiving systems, and a controlled restart have been checked, common external causes have been ruled out.
The failure may involve an internal communication interface, connector assembly, software fault, or electronic hardware problem.
The ventilator should be:
- Removed from service
- Labeled Out of Service
- Sent for authorized repair or bench evaluation
- Referred to Medtronic technical support when required
Do not open the ventilator or perform board-level troubleshooting without current service documentation, proper training, and authorization.
Knowing when external troubleshooting is complete and escalation is required is proper Clinical Engineering troubleshooting.
Clinical Use Tip
A communication failure may not stop ventilation, but it can interrupt charting, remote data visibility, alarm distribution, or clinical workflow. Never allow network availability to substitute for direct observation of the ventilator and patient.
Do not restart, disconnect, or reconfigure a PB980 while it is supporting a patient unless the patient has first been safely transferred according to facility procedure.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Respiratory therapy reported that the Puritan Bennett 980 was ventilating normally but no patient data appeared in the device-integration system."
Cause
What was observed during troubleshooting.
Example:
"Inspection found a damaged Ethernet cable locking tab that allowed the connector to intermittently disconnect from the ventilator."
Resolution
What action was taken.
Example:
"Replaced the Ethernet cable, verified stable network communication and data receipt at the integration system, completed functional checks, and returned the ventilator to service."
Helpful Details to Include (If Known)
- Ventilator software revision
- Exact interface affected
- Ethernet, serial, or USB connection used
- Displayed message or export error
- Communication status indicators
- Outlet and ventilator power status
- Cable inspected and reseated
- Known-good cable tested
- Wall jack or switch port tested
- Gateway or integration device status
- IP address and network configuration verified
- Duplicate IP check completed
- Destination server status
- USB manufacturer, capacity, and format
- Known-good USB device tested
- Controlled restart performed
- Manufacturer field-action status
- Intermittent or continuous failure
- Final device status
Final Thought
Patient safety comes first even when the ventilator continues operating normally. A logical evaluation should separate the ventilator, cable, network, removable media, and receiving system before internal failure is suspected. Proper escalation prevents unnecessary disassembly, while complete CCR documentation preserves the technical findings and final equipment status.
That is successful troubleshooting.