On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting pad connection errors, pad not detected alerts, or inability of AED to recognize electrode pads due to cable, connector, or pad issues.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- If the AED is in use or needed for patient care, immediately switch to another AED if available
- Do not delay resuscitation due to equipment troubleshooting
Expected: Patient care is not interrupted
Why it matters: AED failure during an emergency is critical and time-sensitive
Verify the Reported Issue
- Power on the AED and observe for:
- “Check pads” or similar voice/text prompts
- Visual indicators of pad connection failure
Expected: Error is clearly present and reproducible
Why it matters: Confirms a true connection issue vs. user error
Check Pad Connector Seating (Most Common Cause)
- Inspect the pad cable connection at the AED
- Ensure connector is fully inserted
- Remove and firmly reseat the connector
Expected: AED recognizes pads once properly seated
Why it matters: Loose or partially connected cables are the most frequent cause
Inspect Pads for Expiration or Damage
- Verify expiration date
- Inspect adhesive surface and gel condition
- Look for dried, cracked, or damaged pads
Expected: Pads are within date and in good condition
Why it matters: Expired or dried pads may not be detected or function properly
Check Pad Packaging and Storage Condition
- Ensure pads were stored sealed and properly
- Look for signs of moisture, heat exposure, or compromised packaging
Expected: Pads are intact and properly stored
Why it matters: Environmental damage can affect conductivity and detection
Inspect Cable and Connector for Damage
- Look for cuts, kinks, or exposed wiring
- Check connector pins for bending or contamination
Expected: Cable and connector are intact with no visible damage
Why it matters: Physical damage interrupts signal between pads and AED
Try a Known Good Set of Pads
- Replace with a new or known working pad set
Expected: AED recognizes pads immediately
Why it matters: Quickly isolates whether issue is with pads vs. device
Check Internal Pad Connection Port (External Inspection Only)
- Inspect AED pad port for debris or obstruction
- Do not insert tools or attempt internal repair
Expected: Port is clean and unobstructed
Why it matters: Debris can prevent proper electrical contact
Power Cycle the AED
- Turn device off (if applicable) and back on
- Reconnect pads during restart
Expected: System reinitializes and detects pads
Why it matters: Clears temporary detection faults
If the Problem Persists
If pads are confirmed good and connections are secure, the issue is likely internal (pad detection circuitry or connector failure).
Remove the AED from service. Label as Out of Service and send for repair or bench evaluation.
Knowing when to stop prevents unnecessary risk and ensures reliable emergency equipment.
Clinical Use Tip
Never troubleshoot an AED during an active cardiac event. Always move the patient to a functioning unit first, then evaluate the faulty device.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"AED reports 'check pads' and does not recognize connected pads."
Cause
What was observed during troubleshooting.
Example:
"Faulty or expired electrode pads preventing proper detection by AED."
Resolution
What action was taken.
Example:
"Replaced pads with new set; device tested and returned to service."
Helpful Details to Include (If Known)
- Pad expiration date checked
- Pads swapped with known good set
- Connector reseated
- Cable condition inspected
- Indicator lights or voice prompts observed
- Port inspected for debris
- Final device status (returned to service or sent for repair)
Final Thought
AED reliability is critical for patient survival. Always start with simple connection and pad checks before suspecting internal failure. Prioritize patient safety and document findings clearly to support rapid resolution and readiness.
That is successful troubleshooting.