On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting failed rescue-data downloads caused by infrared alignment, IrDA hardware, computer settings, software access, device power, or communication-mode problems.
Step-by-Step Troubleshooting
1. Ensure Patient Safety First
Do not perform rescue-data transfer troubleshooting while the AED Plus is assigned as the only available defibrillator for an active patient-care area.
Before beginning:
- Remove the AED from active clinical service.
- Provide another verified AED for emergency coverage.
- Confirm that no patient is connected to the electrodes.
- Preserve the AED and associated rescue information according to facility post-event procedures.
Expected outcome: Emergency response coverage remains available, and troubleshooting can be completed without affecting patient care.
If the device is needed for another emergency, stop troubleshooting and return a verified replacement AED to service.
2. Confirm the Exact Failure
Determine which part of the transfer is unsuccessful:
- The computer does not detect the AED.
- The AED does not enter communications mode.
- The application remains waiting for a device.
- The transfer begins but stops or times out.
- No rescue event is found.
- Data transfers but cannot be opened.
- The wrong rescue event appears.
Record any displayed computer message, audible AED prompt, progress-bar behavior, software name, and software version.
Expected outcome: The failure is narrowed to AED communication, infrared hardware, software, data availability, or file access.
3. Verify the AED’s Basic Condition
Inspect the AED Plus before attempting another transfer.
Check for:
- A normal readiness indicator before removal from service
- Adequate battery condition
- Physical damage to the housing or infrared communication area
- Contamination, labels, tape, or residue covering the infrared window
- Evidence of liquid intrusion, impact, unusual heat, or odor
Clean only the exterior using approved methods. Do not insert tools into openings or disassemble the AED.
Expected outcome: The AED is externally intact, adequately powered, and its infrared communication window is unobstructed.
If the device displays a service condition or cannot power reliably, stop and send it for bench evaluation.
4. Confirm Compatible ZOLL Software Is Being Used
Verify that the workstation is running a facility-approved ZOLL application that supports rescue-event data from the AED Plus.
ZOLL currently lists RescueNet EventSummary as supporting AED Plus clinical-event data. Older environments may use ZOLL Data Retriever or another supported ZOLL data-management application.
Confirm:
- The application opens without errors.
- The logged-in account has permission to run the software.
- The correct device type or infrared transfer option is selected.
- The workstation meets the software’s compatibility requirements.
- Endpoint security has not blocked the application or its device driver.
Expected outcome: The approved ZOLL application is operating normally and is configured for an AED Plus infrared transfer.
If the software will not launch or is not approved for the workstation, correct the computer issue before troubleshooting the AED further.
5. Verify the Infrared Adapter
Inspect the workstation’s IrDA adapter or integrated infrared port.
Confirm:
- The adapter is securely connected.
- Windows recognizes the adapter without a warning symbol.
- The correct driver is installed.
- The infrared port is enabled.
- No USB extension, docking station, or hub is causing an intermittent connection.
- The adapter is not being used by another application.
Disconnect and reconnect the adapter. When practical, connect it directly to another known-good USB port and allow the operating system to recognize it fully.
Expected outcome: The infrared adapter appears normally in the operating system and remains connected without errors.
If the adapter is not recognized, test with a known-good compatible IrDA adapter before suspecting the AED. ZOLL states that an IrDA device is required for infrared communication with the AED Plus.
6. Align the Infrared Ports Correctly
Position the AED Plus so its infrared window directly faces the workstation’s infrared port or external IrDA reader.
Ensure:
- The infrared windows face each other.
- There is a clear line of sight.
- Neither device is moving.
- The distance is close enough for reliable communication.
- Bright sunlight or intense direct lighting is not striking the infrared windows.
- No equipment or cable blocks the signal path.
Do not hold the AED by hand during the transfer. Place both devices on stable surfaces.
Expected outcome: The infrared transmitter and receiver remain directly aligned throughout the communication attempt.
ZOLL’s transfer instructions require the AED Plus infrared port to be aligned with the workstation’s infrared port or reader.
7. Start the Transfer in the Correct Sequence
Using the approved data application:
- Select the infrared transfer method.
- Initiate the application’s upload or data-retrieval function.
- Press and hold the AED Plus On control.
- Continue holding it until the AED announces: “Non-rescue mode. Communications established.”
- Keep the AED and infrared reader aligned while the progress bar advances.
ZOLL indicates that a transfer may take approximately 30 seconds to several minutes, depending on the record size.
Expected outcome: The AED enters non-rescue communications mode, the software recognizes it, and transfer progress begins.
If the AED begins normal rescue operation instead of communications mode, stop the attempt, confirm the button sequence, realign the ports, and retry once.
8. Allow the Transfer to Finish Without Interruption
Once the upload begins:
- Do not move the AED or infrared adapter.
- Do not close the application.
- Do not remove the IrDA adapter.
- Do not allow the workstation to sleep or lock.
- Do not start another transfer simultaneously.
- Observe whether progress consistently stops at the same point.
Expected outcome: The transfer completes and the rescue event appears in the application.
If communication fails only when either device is moved, repeat the transfer with improved physical support and alignment.
9. Test the Computer Side With Known-Good Equipment
When available, perform controlled substitution testing:
- Attempt to read another compatible ZOLL AED using the same workstation and IrDA adapter.
- Attempt to read the affected AED Plus using another approved workstation or known-good IrDA adapter.
Interpret the results:
- Another AED also fails on the original workstation: suspect the adapter, driver, software, permissions, or computer configuration.
- The affected AED transfers successfully on another workstation: suspect the original computer environment.
- Other AEDs transfer successfully, but the affected AED Plus fails on multiple approved setups: suspect an AED communication or stored-data issue.
Expected outcome: The failure is isolated to the AED, infrared adapter, workstation, or software environment.
10. Confirm That Rescue Data Is Available
Verify with the reporting department or clinical team that the AED Plus was actually activated during the reported event.
Document:
- Approximate date and time of use
- Whether the lid was opened or the device was powered on
- Whether electrodes were connected to a patient
- Whether rhythm analysis occurred
- Whether CPR feedback or shock delivery occurred
- Whether a later activation may have overwritten or replaced the expected record
Do not clear, delete, or overwrite rescue data while troubleshooting. Preserve any available files before changing software, reinstalling applications, or performing additional device tests.
Expected outcome: The expected rescue event is confirmed as likely present, or the absence of a downloadable record is explained.
11. Verify the Downloaded Record
After a successful transfer:
- Open the event using the approved ZOLL application.
- Confirm the AED serial number.
- Confirm the rescue date and approximate event time.
- Verify that ECG, event markers, CPR information, and shock information display when available.
- Save or export the record to the approved secure location.
- Follow facility procedures for releasing the information to the clinical quality or risk-management team.
Expected outcome: The correct rescue event is readable, identifiable, and securely preserved.
If the transfer completes but the file remains unreadable on more than one approved workstation, preserve the original data and escalate to ZOLL technical support or the responsible data-system administrator.
12. Restore and Verify AED Readiness
After troubleshooting:
- Exit communications mode.
- Return the AED to its normal closed and ready condition.
- Verify the readiness indicator.
- Confirm the electrodes and accessories are correctly connected and stored.
- Confirm no service message or abnormal tone is present.
- Perform only the operational verification permitted by facility policy and manufacturer instructions.
- Return the AED to service only when readiness is confirmed.
Expected outcome: The AED is either returned to service in a verified ready condition or clearly removed from service for repair.
If the Problem Persists
If the AED Plus will not enter communications mode or transfer data after verifying power, infrared alignment, IrDA hardware, software operation, workstation settings, and transfer sequence, common external causes have been ruled out.
The issue may involve the AED’s infrared communication circuitry, stored rescue record, software compatibility, or another internal fault.
The device should be:
- Removed from service
- Labeled Out of Service
- Replaced with another verified AED
- Sent for repair or bench evaluation
- Escalated to ZOLL technical support when rescue-data recovery is required
Do not open the AED or attempt internal communication-board repair without authorized service documentation, training, and appropriate test equipment.
Knowing when to stop substitution testing and escalate the device is proper troubleshooting.
Clinical Use Tip
Never delay CPR, rhythm analysis, or defibrillation to retrieve rescue data. Move patient care to another verified device first and troubleshoot infrared communication only after the AED is safely removed from clinical use.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported that rescue-event data could not be downloaded from the ZOLL AED Plus through the infrared connection."
Cause
What was observed during troubleshooting.
Example:
"The workstation’s IrDA adapter was recognized intermittently and lost communication when the transfer began."
Resolution
What action was taken.
Example:
"Replaced the defective IrDA adapter, realigned the AED infrared window, successfully downloaded and verified the rescue event, and confirmed the AED readiness indicator before return to service."
Helpful Details to Include (If Known)
- AED serial number
- Approximate rescue date and time
- Readiness indicator condition
- Battery condition
- AED audible prompts
- Whether communications mode was announced
- ZOLL application and version
- Workstation identification
- IrDA adapter manufacturer and model
- Infrared adapter recognized by Windows
- Alignment and distance tested
- Known-good adapter or workstation tested
- Transfer progress or failure point
- Rescue event found and verified
- Unusual heat, smell, contamination, or damage
- Final device status
- Data provided to the appropriate clinical department
Final Thought
Rescue-data transfer problems should be approached by protecting patient coverage, preserving the event record, and isolating the AED from the infrared adapter, software, and workstation. Logical substitution testing prevents unnecessary AED repair, while timely escalation protects valuable clinical data. Clear CCR documentation establishes what failed, what was tested, whether the rescue information was recovered, and whether the AED was safe to return to service.
That is successful troubleshooting.