Getinge Servo-i

Battery Not Charging or Short Runtime

On this page

Asset Type

Ventilator

Manufacturer

Getinge

Model

Servo-i

What This Guide Helps With

Troubleshooting battery charging failures, reduced backup time, battery alarms, or unexpected shutdown caused by power, seating, battery condition, or charging-system problems.

Step-by-Step Troubleshooting

1. Ensure Patient Safety First

Do not troubleshoot a suspected battery or power-backup failure while the Servo-i is actively supporting a patient.

Expected outcome: The patient is safely supported without relying on a ventilator that may lose power unexpectedly.

Continue Clinical Engineering troubleshooting only after the Servo-i has been removed from patient use.

2. Confirm the Reported Battery Problem

Determine whether the reported issue is:

Record the displayed alarm or message exactly.

Expected outcome: The failure is clearly identified before components are exchanged.

3. Verify the AC Power Source

Connect the Servo-i directly to a known-good hospital-grade outlet.

A ventilator cannot charge its batteries properly if external power is missing or unstable.

Expected outcome: The Servo-i consistently recognizes AC power. If normal charging resumes, allow the battery to charge and complete verification before returning the device to service.

4. Inspect the Power Cord and AC Inlet

Remove the device from AC power and inspect:

Test with a known-good compatible power cord when permitted by facility policy.

Expected outcome: AC power remains stable with the replacement cord. If the cord caused the problem, replace it and stop troubleshooting after completing functional and safety verification.

5. Check Battery Installation and Recognition

With the ventilator safely removed from patient use:

Expected outcome: The installed battery appears normally in the power-status information. If reseating restores recognition, continue with charging and runtime verification.

6. Review Battery Status and Messages

Observe the battery and power information displayed by the Servo-i.

Look for:

Allow time for the displayed status to update after installing a battery or connecting external power.

Expected outcome: Each installed battery is recognized and shows a normal charging state. Record any battery-specific warning before proceeding.

7. Allow an Adequate Charging Period

Leave the ventilator connected to stable AC power long enough for the installed batteries to charge.

Charging time and available backup time can vary with battery condition, installed options, ventilator settings, and battery temperature.

Expected outcome: Battery capacity increases and reaches an acceptable level. If capacity does not increase, continue troubleshooting.

8. Compare Battery Modules When Available

When more than one approved battery module is available, exchange one battery at a time with a known-good compatible module.

Expected outcome:

If a defective battery is identified, remove it from use and process it according to facility battery-replacement and recycling procedures.

9. Perform a Controlled Runtime Test

After charging, connect the Servo-i to an approved test lung and configure it according to the facility’s battery-performance test procedure.

Do not use an active patient to test battery capacity.

Expected outcome: The ventilator transfers to battery power without interruption and provides runtime that meets the applicable service requirement.

If runtime is short with one battery only, replace that battery. If runtime remains short with known-good batteries, escalate for bench evaluation.

10. Check Battery Age and Service History

Review the battery label, installation date, maintenance history, and previous runtime-test results.

Look for:

Rechargeable batteries lose capacity with age and use even when they remain recognizable and appear to charge.

Expected outcome: Batteries with poor capacity, excessive age, damage, or failed testing are replaced according to approved service procedures.

11. Complete Operational and Safety Verification

After correcting the problem:

Expected outcome: The Servo-i operates reliably on AC and battery power without unexplained alarms or interruptions.

If the Problem Persists

If the Servo-i will not recognize or charge known-good batteries, repeatedly changes power sources, or fails the controlled runtime test, common external causes have been ruled out. The failure may involve the battery interface, charging circuit, AC power supply, internal wiring, or power-management electronics.

The ventilator should be:

Do not continue repeated discharge testing or begin unapproved internal disassembly. Knowing when to stop and escalate is proper troubleshooting.

Clinical Use Tip

Never depend on a Servo-i with uncertain battery capacity for patient transport. Move the patient to another verified ventilator before testing batteries, disconnecting AC power, or exchanging power components.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Respiratory therapy reported that the Getinge Servo-i displayed low battery capacity and operated for only several minutes after AC power was disconnected."

Cause

What was observed during troubleshooting.

Example:
"Battery runtime testing found that one installed battery module failed to retain adequate capacity, while a known-good battery charged and operated normally."

Resolution

What action was taken.

Example:
"Removed the degraded battery from service, installed an approved replacement, verified charging and AC-to-battery transfer, completed the pre-use check, and returned the ventilator to service."

Helpful Details to Include (If Known)

Final Thought

Battery troubleshooting must protect the patient first and then proceed logically through the outlet, power cord, battery seating, charging status, battery condition, and controlled runtime testing. Escalating a Servo-i that cannot reliably maintain backup power prevents an avoidable loss of ventilation, while complete CCR documentation establishes exactly what was reported, found, and corrected.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide