ZOLL Propaq MD

Battery Not Charging or Short Runtime

On this page

Asset Type

Defibrillator

Manufacturer

ZOLL

Model

Propaq MD

What This Guide Helps With

Battery does not charge, is not recognized, or provides unexpectedly short runtime due to power, battery, connection, or charging-system issues.

Step-by-Step Troubleshooting

1. Protect the Patient and Maintain Defibrillation Capability

If the Propaq MD is supporting an active patient, move monitoring or emergency-response readiness to another verified defibrillator before troubleshooting an unreliable battery system.

Do not continue depending on a unit that may unexpectedly lose power.

Expected outcome: Patient care and emergency defibrillation capability remain continuously available while the affected unit is evaluated.

2. Confirm the Reported Battery Condition

Ask clinical staff whether the problem involves:

Power the unit under controlled conditions and confirm whether the reported behavior can be reproduced.

Expected outcome: The exact battery or charging symptom is identified. If normal operation is confirmed and the complaint cannot be reproduced, document testing and continue with verification before returning the unit to service.

3. Inspect the Battery and Battery Compartment

Remove the unit from clinical use and inspect the battery externally for:

Do not use a swollen, leaking, excessively hot, or physically damaged battery.

Reseat the battery completely.

Expected outcome: The battery is intact and properly seated. If reseating restores reliable operation and charging, complete functional verification and troubleshooting can stop.

4. Verify External AC Power

Connect the approved AC power source and verify that the outlet is functional using an appropriate outlet tester or known-good powered device according to facility practice.

Inspect the power cord, adapter, and accessible connectors for damage or looseness.

Expected outcome: Reliable AC power reaches the device. If correcting the outlet, cord, or connection restores charging, verify battery charging indication and device operation before stopping troubleshooting.

5. Check Charging Indications

Observe the Propaq MD while connected to AC power and note whether normal power and battery charging indications appear.

Compare behavior with and without the battery installed when appropriate and permitted.

Do not assume a battery failure solely because runtime is poor.

Expected outcome: The device consistently recognizes the battery and indicates expected charging behavior.

6. Test With a Known-Good Compatible Battery

Install a known-good, appropriately maintained compatible battery.

Compare:

Expected outcome: If the known-good battery performs normally while the reported battery does not, remove the suspect battery from service and manage it according to the facility battery replacement process. Troubleshooting can stop after final verification.

7. Compare the Suspect Battery in Approved Charging Equipment

If appropriate approved ZOLL charging equipment is available, evaluate whether the suspect battery charges normally outside the Propaq MD.

Do not perform unauthorized battery rebuilding or cell-level repair.

Expected outcome: The test distinguishes a battery-specific problem from a device-side charging problem.

8. Evaluate Short Runtime Under Controlled Conditions

If the battery charges but runtime remains short, begin with a fully charged known-good battery and observe operation under a controlled load representative of normal device use.

Check for unexpected shutdowns, rapidly changing battery indication, or intermittent battery recognition.

Expected outcome: A known-good battery provides stable operation. If multiple known-good batteries exhibit the same abnormal behavior, device-level service evaluation is required.

9. Perform Final Functional Verification

After correcting an external cause or replacing a defective battery:

Expected outcome: The Propaq MD operates reliably from both appropriate power sources and shows normal battery behavior. Troubleshooting can stop.

10. Escalate When the Problem Remains

If the unit fails to charge or provides abnormal runtime with verified AC power and known-good batteries, do not continue external troubleshooting.

Expected outcome: The unit is removed from service for qualified bench evaluation rather than returned with an unresolved power reliability problem.

If the Problem Persists

If outlet power, external power connections, battery seating, battery condition, and known-good battery substitution have been ruled out, the remaining cause may involve the charging system, internal power path, battery sensing, configuration, or another service-level condition.

The device should be:

Following repair, complete applicable electrical safety, battery, functional, alarm, monitoring, and defibrillator return-to-service testing before clinical release.

Knowing when to stop external troubleshooting and escalate an unreliable power system is proper troubleshooting.

Clinical Use Tip

Maintain immediate access to another verified defibrillator whenever battery reliability is uncertain.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Clinical staff reported that the ZOLL Propaq MD battery discharged rapidly and the unit required frequent connection to AC power."

Cause

What was observed during troubleshooting.

Example:
"Clinical Engineering found that the reported battery had significantly reduced runtime while a known-good compatible battery operated normally."

Resolution

What action was taken.

Example:
"The degraded battery was removed from service and replaced, and the Propaq MD passed AC-power, battery-operation, charging, and functional verification."

Helpful Details to Include (If Known)

Final Thought

Protect the patient first, verify AC power and battery condition before assuming an internal charging failure, use controlled known-good substitutions, escalate unresolved power problems, and clearly document the complaint, cause, corrective action, and final verification.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide