Puritan Bennett 980

Low Exhaled Tidal Volume or Low Minute Volume Alarm

On this page

Asset Type

Ventilator

Manufacturer

Puritan Bennett

Model

980

What This Guide Helps With

Troubleshooting low exhaled volume alarms caused by circuit leaks, disconnections, obstructions, accessories, alarm settings, reduced test-lung volume, or expiratory measurement problems.

Step-by-Step Troubleshooting

1. Ensure Patient Safety First

Do not troubleshoot a low exhaled tidal volume or low minute volume alarm while the Puritan Bennett 980 is actively supporting a patient.

Expected outcome: The patient is safely supported without relying on the affected ventilator.

Continue Clinical Engineering troubleshooting only after the PB980 has been removed from patient use.

2. Identify the Exact Alarm

Review the active alarm banner and alarm log. Determine whether the PB980 reports:

The PB980 activates the low exhaled tidal-volume alarms when measured mandatory or spontaneous exhaled volume is at or below its corresponding alarm limit. The low exhaled total minute-volume alarm occurs when measured mandatory and spontaneous minute volume is at or below the configured limit.

Expected outcome: The exact alarm type and any associated alarms are documented.

If the alarm occurred because the displayed exhaled volume legitimately fell below an appropriately configured limit, stop and return the clinical assessment to respiratory therapy.

3. Review Alarm Limits and Ventilator Settings

With the ventilator connected to an approved test lung, verify:

Do not change alarm limits solely to silence the alarm. Compare the settings with the reported clinical configuration or facility-approved test setup.

Expected outcome: The alarm limit is appropriate for the intended test conditions and is not inadvertently set above the expected exhaled volume.

If correcting an incorrectly entered setting resolves the alarm and the ventilator passes functional testing, stop.

4. Inspect the Complete Patient Circuit

Examine the inspiratory and expiratory limbs from the ventilator to the patient connection.

Look for:

Reconnect or replace suspect components using compatible parts.

Expected outcome: The circuit is fully connected, correctly assembled, unobstructed, and free of visible leaks.

If replacing or reseating the circuit resolves the alarm, complete operational testing and stop.

5. Inspect the Test Lung or External Load

Confirm that the test lung:

Substitute a known-good test lung when available.

Expected outcome: The ventilator delivers repeatable breaths and the exhaled volume remains above the configured alarm limits.

If the alarm disappears with the known-good test lung, the original test lung or external load was the cause. Stop.

6. Check the Exhalation Filter and Condensate Collection Components

Inspect the exhalation filter, condensate vial, filter adapter, and nearby connections.

Verify that:

Replace a wet, damaged, contaminated, or suspect filter with an approved compatible filter.

Expected outcome: Exhaled gas flows through a properly installed and unobstructed exhalation assembly without leakage.

If filter replacement resolves the alarm, perform functional verification and stop.

7. Inspect Humidification and Added Accessories

Check any humidifier, nebulizer, suction adapter, flow sensor, sampling line, closed-suction system, or specialty connector installed in the circuit.

Look for:

Temporarily remove nonessential accessories and test using a basic approved circuit and test lung.

Expected outcome: The alarm clears when a leaking, obstructed, or incorrectly installed accessory is removed or replaced.

If the basic circuit operates normally, identify and replace the defective accessory before returning the ventilator to service.

8. Compare Inspired and Exhaled Volume Measurements

Observe the displayed inspired tidal volume, exhaled tidal volume, total respiratory rate, minute volume, airway pressure, and leak information.

Determine whether:

The manufacturer identifies leaks and obstructions as possible causes of low exhaled mandatory tidal volume. During pressure-based ventilation, changes in resistance or compliance can also reduce measured tidal volume even when the selected pressure is achieved.

Expected outcome: The pattern indicates whether the issue is associated with delivery, leakage, obstruction, settings, or exhaled-volume measurement.

9. Check for Circuit Obstruction or Excessive Resistance

Inspect for resistance caused by:

Replace suspect components rather than attempting to clean or modify disposable circuit parts.

Expected outcome: Airflow is unrestricted and delivered and exhaled volumes remain stable.

If removing the obstruction resolves the alarm, complete operational testing and stop.

10. Perform a New Circuit Test When Appropriate

After replacing the circuit, filter, humidification components, or major accessories, perform the manufacturer-defined circuit test or system check required for that configuration.

Use:

Do not perform the test with a patient attached.

Expected outcome: The circuit test completes successfully without leaks, compliance errors, or resistance-related failures.

If the circuit test fails repeatedly with a known-good circuit, remove the ventilator from service.

11. Test With a Known-Good Circuit Configuration

Install a known-good:

Repeat ventilation using controlled, documented settings.

Expected outcome: Exhaled tidal volume and minute volume remain stable and above their alarm limits.

If the ventilator works with the known-good configuration, replace the defective external component and document the finding.

12. Evaluate for an Expiratory Measurement or Internal Flow-System Problem

Suspect an internal problem when:

Do not disassemble the breath-delivery unit, exhalation module, flow sensors, or internal pneumatic components unless trained, authorized, and following the applicable service documentation.

Expected outcome: External causes have been ruled out and the unit is identified for formal bench evaluation.

If the Problem Persists

If the alarm continues after verifying settings, circuit integrity, filters, accessories, test lung, and circuit-test results, the problem is likely associated with the exhalation flow-measurement system, internal pneumatic components, calibration, or ventilator electronics.

The ventilator should be:

The PB980 operator’s manual includes low exhaled mandatory tidal volume, low spontaneous tidal volume, and low total minute volume among the alarms evaluated during formal alarm testing.

Knowing when to stop external troubleshooting is proper Clinical Engineering practice.

Clinical Use Tip

Never dismiss a low exhaled volume alarm as a faulty ventilator until the patient has been clinically assessed. Reduced tidal or minute volume may reflect disconnection, leakage, obstruction, altered lung mechanics, apnea, or reduced respiratory effort.

Move the patient to another verified ventilator before Clinical Engineering testing whenever dependable ventilation cannot be assured.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Respiratory therapy reported repeated low exhaled tidal volume and low total minute volume alarms during operation of the Puritan Bennett 980."

Cause

What was observed during troubleshooting.

Example:
"Inspection found a loose connection at the exhalation filter assembly that allowed circuit leakage and reduced measured exhaled volume."

Resolution

What action was taken.

Example:
"Reseated the exhalation assembly, replaced the filter, completed the circuit test, and verified stable tidal and minute-volume measurements using a test lung."

Helpful Details to Include (If Known)

Final Thought

Low exhaled volume alarms require both clinical caution and logical equipment troubleshooting. Protect the patient first, verify settings and external breathing-circuit components, reproduce the issue safely, and escalate when measurements remain unreliable. Clear CCR documentation supports safe return to service and future repair decisions.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide