On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting failed software updates or configuration transfers caused by battery level, USB media, file naming, file compatibility, access, or connection problems.
Step-by-Step Troubleshooting
1. Ensure Patient Safety First
Do not perform software updates, configuration transfers, or USB troubleshooting while the AED is assigned to an active patient or emergency response.
Before beginning:
- Remove the AED from active clinical service.
- Provide another verified AED for coverage.
- Confirm that no patient is connected to the defibrillation pads.
- Do not connect the AED USB port to a computer or other device while the pads are connected to a patient.
Expected outcome: Emergency response coverage remains available, and the AED can be evaluated without affecting patient care. ZOLL specifically warns against USB connection while the pads remain connected to a patient.
2. Record the Exact Failure
Repeat the transfer only far enough to identify and document:
- The complete displayed message
- Whether the failure involves software, clinical configuration, Wi-Fi configuration, or certificates
- Whether the USB device icon appears
- The current software version, when available
- Whether the failure occurred before, during, or after restart
- Whether another AED accepted the same file
Expected outcome: The troubleshooting path is based on the actual failure rather than a general report.
3. Confirm the Correct Transfer Method
Use a USB flash drive for configuration transfers and software imports.
Configuration files cannot be transferred between AEDs through Wi-Fi. ZOLL identifies configuration export and import as USB functions.
Expected outcome: The selected method matches the type of file being transferred.
If configuration transfer was being attempted through Wi-Fi, switch to the approved USB method and retry. If successful, stop.
4. Check Battery Capacity Before a Software Update
Verify that the installed battery has more than 30% remaining capacity.
The AED will not permit a software update when battery capacity is below 30%.
If battery capacity is low:
- Install a verified battery with adequate capacity.
- Confirm that the AED starts normally.
- Restart the update from the beginning.
Expected outcome: The software-update option is available and the update can proceed without a low-battery interruption.
If this resolves the problem, complete post-update testing and stop.
5. Inspect the USB Connection Externally
Remove the USB flash drive and inspect:
- The flash drive connector
- The AED USB receptacle
- The rear connector area
- The USB cover, if applicable
- Evidence of bent contacts, contamination, moisture, or physical damage
Do not insert tools into the port or attempt internal connector repair.
Reinsert the flash drive fully and confirm that the USB-device icon appears on the display after entering AED Management mode.
Expected outcome: The AED recognizes the USB flash drive.
If no USB icon appears, test with another known-good compatible flash drive. If neither drive is recognized, remove the AED from service for bench evaluation.
6. Verify USB Flash-Drive Compatibility
Use a known-good USB flash drive that is compatible with USB 1.1 or USB 2.0. ZOLL specifies USB 1.1 or 2.0 compliance for file import and export.
Also confirm that the drive:
- Has sufficient free storage space
- Is readable by a workstation
- Does not contain obvious file-system errors
- Is not write-protected
- Is not being connected through an adapter or hub
For export failures, an empty known-good drive is preferred.
Expected outcome: The AED detects reliable removable media with enough available space.
If replacing the flash drive resolves the issue, verify the completed transfer and stop.
7. Confirm the Correct File Is Present
For configuration import, verify that the USB drive contains the intended .ini configuration file.
For software updates, verify that:
- The update package came from an authorized ZOLL source.
- The package is specifically intended for the ZOLL AED 3.
- The file has not been manually modified.
- All required package contents were copied completely.
- The file was not extracted or renamed contrary to ZOLL instructions.
An “Unable to save file to device” message may indicate that the required configuration file is not present on the USB drive.
Expected outcome: The USB drive contains the correct and complete file for the selected import type.
If the file is missing or questionable, obtain a clean authorized copy and retry.
8. Check the Configuration Filename
Verify that a configuration filename:
- Ends in .ini
- Contains no spaces
- Has not had its extension changed
- Has not been unintentionally duplicated, such as configuration.ini.ini
ZOLL directs that configuration filenames intended for import must not contain spaces.
Expected outcome: The AED can locate and interpret the configuration file.
If correcting the filename resolves the issue, verify the transferred settings and stop.
9. Enter AED Management Mode Correctly
With the USB drive inserted:
- Press and hold the On/Off button for more than five seconds.
- Confirm that the USB icon appears.
- Select the Device Configuration icon.
- Select Supervisor Access.
- Enter the authorized supervisor passcode.
- Select Import Files.
- Choose Configuration, System Software, or Root Certificates, as applicable.
Supervisor access is required to import files from a USB flash drive.
Expected outcome: The correct import option becomes available and the desired file is selectable.
If access cannot be obtained, verify the approved passcode through the facility AED-program administrator. Do not repeatedly guess or bypass access controls.
10. Select the Correct Configuration Category
When importing a configuration, confirm that the intended option is selected:
- Clinical Configuration
- Wi-Fi Configuration
- Both, when appropriate
A selected item should display a green check before confirmation.
Expected outcome: The AED imports the intended settings rather than an unselected or incorrect configuration category.
If the device reports that no files were selected, return to the selection screen, select the appropriate item, and retry.
11. Match the Error Message to the External Cause
Use the displayed message to guide the next action:
Unable to save files:
Confirm the USB drive is fully inserted and has enough free space.
Requested file cannot be found:
Confirm that the correct file is present and that the USB drive is recognized.
Requested file is out of date:
Obtain a configuration version compatible with the receiving AED.
Requested file contains invalid data:
Replace it with a verified, unmodified source file.
Requested file is corrupted:
Delete the questionable copy and obtain a fresh authorized file.
Configuration files unavailable:
Confirm that an exportable configuration exists on the source AED.
ZOLL associates these messages with USB recognition, file presence, compatibility, validity, and corruption problems.
Expected outcome: The transfer completes after the specific external file or media condition is corrected.
12. Do Not Interrupt a Software Update
After confirming a software update, allow the process to finish without:
- Removing the battery
- Removing the USB drive
- Pressing the power button
- Attempting another operation
- Assuming the blank display indicates failure
ZOLL states that the screen may go blank, the AED will restart, and the process may take up to five minutes. Power must not be removed during this period.
Expected outcome: The AED restarts normally after completing the update.
If the device does not restart after the stated update period, do not repeatedly power-cycle it. Remove it from service and escalate for technical evaluation.
13. Verify Successful Completion
Confirm that the AED reports the appropriate successful-transfer message, such as:
- Files transferred successfully
- The expected software-update completion and restart
- Successful certificate storage, when applicable
Then verify:
- The expected software version
- Date and time
- Clinical configuration settings
- Adult and child-mode settings
- Audio and language settings
- Wi-Fi configuration, when transferred
- Readiness indicator
- Successful self-test
- Pads and battery status
Expected outcome: The AED is correctly configured, passes its self-test, and returns to a ready condition.
If any critical setting is incorrect or the readiness indicator does not show normal status, keep the AED out of service.
14. Compare With a Known-Good Combination
When available, isolate the failure by testing:
- The same USB drive and file on another compatible AED 3
- A known-good USB drive on the affected AED
- A newly exported configuration from a verified source AED
- A fresh authorized software package
Interpret the results:
- One USB drive fails on multiple AEDs: suspect the drive or files.
- Multiple known-good drives fail on one AED: suspect the AED USB interface or internal software.
- One configuration fails while another imports: suspect file compatibility or corruption.
- The update fails at the same point repeatedly: stop and escalate.
Expected outcome: The failure is isolated to the file, USB media, configuration compatibility, or AED.
If the cause is isolated and corrected, repeat the transfer once and complete verification.
If the Problem Persists
If the AED still cannot recognize known-good USB media, repeatedly rejects verified compatible files, freezes during import, fails to restart, or does not pass its post-update self-test, common external causes have been ruled out.
The device should be:
- Removed from service
- Labeled Out of Service
- Replaced with another verified AED
- Sent for repair or bench evaluation
- Referred to ZOLL Technical Support when file compatibility, software recovery, or authorization is uncertain
Do not attempt repeated software reloads, internal USB-port repair, unauthorized firmware recovery, or board-level troubleshooting. Knowing when to stop is proper troubleshooting.
Clinical Use Tip
Never update or reconfigure the AED while it is the only available defibrillator for a clinical area. Establish replacement coverage before taking it out of service.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported that the ZOLL AED 3 would not accept a software update or configuration file from the USB flash drive."
Cause
What was observed during troubleshooting.
Example:
"Inspection found that the configuration filename contained spaces and the original flash drive was not consistently recognized by the AED."
Resolution
What action was taken.
Example:
"Copied the verified .ini file without spaces to a known-good USB 2.0 drive, completed the import, verified settings, and confirmed a successful self-test and normal readiness indicator."
Helpful Details to Include (If Known)
- Exact displayed error message
- Original and final software versions
- Battery-capacity indication
- USB icon present or absent
- USB-drive type and capacity
- Alternate USB drive tested
- Filename and file extension checked
- Configuration source identified
- File compatibility confirmed
- Supervisor access successful
- Update duration and restart behavior
- Readiness-indicator condition
- Self-test result
- Final device status
Final Thought
Safe software troubleshooting requires reliable emergency coverage, correct files, compatible USB media, adequate battery capacity, and uninterrupted installation. Documenting the precise cause and final verification supports future AED readiness.
That is successful troubleshooting.