On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting failed or intermittent Wi-Fi or cellular communication caused by signal, network access, configuration, location, account, or persistent device-side faults.
Step-by-Step Troubleshooting
1. Ensure Patient Safety First
Do not perform extended connectivity troubleshooting while the LIFEPAK CR2 is required for emergency response or active patient care.
Keep another verified AED immediately available if the affected unit’s overall readiness is uncertain. Do not delay defibrillation or patient care because of a wireless communication problem.
Expected: Patient care remains supported by a ready, verified defibrillator.
Why it matters: A connectivity failure may affect remote monitoring, readiness reporting, updates, or event-data transfer without necessarily proving that the AED’s therapy function has failed. Treat device readiness and network connectivity as separate concerns until verified.
If the immediate safety concern is resolved, continue troubleshooting in a controlled Clinical Engineering environment.
2. Confirm the Exact Failure Mode
Determine what staff or the AED management system is actually reporting.
Check whether:
- Wi-Fi alone is failing
- Cellular alone is failing
- Both communication paths are unavailable
- Communication is intermittent
- The AED appears offline in LIFELINKcentral
- The problem began after relocation
- The problem began after a network or password change
- Only one physical location is affected
- Readiness information is stale rather than completely absent
Expected: The failure is narrowed to a specific communication path and symptom.
If the issue is limited to one path while the alternate path communicates normally, document that distinction and troubleshoot only the affected path.
3. Verify Overall AED Readiness
Inspect the LIFEPAK CR2 for its normal readiness indication and check for any abnormal visual or audible condition.
Confirm externally that:
- The device is not showing an obvious readiness fault
- The battery is installed correctly
- Required electrodes are present and connected as intended
- There is no visible physical damage
- There is no unusual heat, odor, moisture intrusion, or impact damage
Expected: The AED appears otherwise ready and the complaint remains isolated to connectivity.
If the AED shows a separate readiness problem, remove it from service and address that condition before treating the issue as network-only.
4. Confirm the Installed Connectivity Configuration
Verify that the specific LIFEPAK CR2 unit is actually equipped and configured for the communication method being tested.
Do not assume every CR2 has identical connectivity capability.
Confirm through available asset records, deployment documentation, or the organization’s AED management configuration whether the unit is expected to use:
- Wi-Fi
- Cellular service
- Both Wi-Fi and cellular connectivity
Expected: The tested communication method matches the unit’s actual configuration.
If the unit was never provisioned for the reported connection method, correct the deployment record or escalate for proper configuration rather than diagnosing a hardware failure.
5. Check Physical Location and Signal Conditions
Evaluate the AED at its normal installed location.
For Wi-Fi, look for:
- Weak coverage
- Recent relocation
- Metal cabinets or enclosures
- Basement or interior-room placement
- Building renovations
- Access-point changes
- Large obstructions near the AED
For cellular-equipped units, look for:
- Poor indoor cellular coverage
- Shielded rooms
- Underground locations
- Dense structural barriers
- A recent move to a low-signal area
Stryker’s pre-implementation guidance specifically recommends checking Wi-Fi signal strength at the intended AED location with another wireless device.
Expected: Adequate signal is available where the AED is deployed.
If moving the AED temporarily to a known-good coverage area restores communication, stop. The likely cause is environmental coverage, not confirmed internal device failure.
6. Compare With a Known-Good Network Device
At the same location, test the intended Wi-Fi network using an approved known-good device such as a facility-managed laptop, tablet, or phone.
Confirm:
- The expected SSID is visible
- The network is operational
- Signal strength is reasonable
- Other approved devices can communicate
Expected: The local wireless environment is verified independently of the AED.
If other devices also fail, stop troubleshooting the CR2 and escalate the network problem to IT or the responsible infrastructure team.
7. Check for Recent Network Changes
Ask IT or review change records for recent changes involving:
- SSID name
- Wi-Fi password or security key
- Authentication method
- Access-point replacement
- Network segmentation
- Firewall rules
- Internet access
- Site relocation
- Wireless security policy
Expected: The AED’s stored configuration remains compatible with the current network.
If a network change occurred, update or reprovision the AED only through the approved Stryker-supported wireless setup process and facility change-control practices.
8. Verify Wi-Fi Network Compatibility and Access
For a Wi-Fi complaint, confirm with IT that the intended network is appropriate for the LIFEPAK CR2 deployment.
Check externally for:
- Correct network name
- Correct credentials
- Sufficient coverage
- Internet access where required
- No captive portal requiring browser acceptance
- No unapproved access-control change blocking the device
Stryker provides a dedicated LIFEPAK CR2 wireless setup guide and recommends configuring Wi-Fi-capable units with a Wi-Fi network, including models that also have cellular capability.
Expected: The intended Wi-Fi environment supports the configured AED connection.
If IT identifies a network-side block, correct the infrastructure issue and retest before suspecting AED hardware.
9. Recheck the Approved Wireless Configuration
Using the facility’s authorized process and Stryker’s supported wireless setup workflow, confirm that the unit is associated with the intended Wi-Fi configuration.
Do not guess credentials or perform undocumented configuration changes.
Check for:
- Wrong SSID
- Outdated password
- Configuration for a previous site
- Incorrect deployment profile
- Incomplete provisioning
Expected: The AED has the correct approved wireless configuration.
If correcting the configuration restores communication, stop. Document the configuration mismatch and successful reconnection.
10. Determine Whether the Failure Is Location-Specific
When permitted by facility policy, test communication from another location with known-good coverage.
Expected: The result helps distinguish environmental coverage from a device-specific fault.
Works in alternate location: Suspect local signal, access-point, or network coverage.
Fails in all known-good locations: Continue troubleshooting.
Wi-Fi works but cellular does not: Focus on cellular coverage, provisioning, or service status.
Cellular works but Wi-Fi does not: Focus on local Wi-Fi configuration or infrastructure.
If the problem is clearly location-specific, stop and escalate to the appropriate network or facilities team.
11. Check LIFELINKcentral Status
Verify whether the affected LIFEPAK CR2 is properly represented in the organization’s LIFELINKcentral AED Program Manager environment.
Check for:
- Correct device association
- Expected location
- Last communication time
- Stale status information
- Device replacement not reflected in the account
- Duplicate or incorrect asset assignment
Stryker states that connected CR2 units can communicate through Wi-Fi or cellular networks with LIFELINKcentral for remote AED monitoring and related connectivity functions.
Expected: The physical AED and cloud-management record correspond correctly.
If the problem is an account, assignment, or portal-management issue, correct or escalate that issue rather than replacing hardware.
12. Evaluate a Cellular-Only Failure
For a CR2 configuration equipped with cellular connectivity, determine whether the failure persists in a location with known-good cellular coverage.
Check for:
- Failure only inside one building
- Failure in basement or shielded areas
- Recent relocation
- Prolonged offline status despite adequate coverage
- Wi-Fi functioning normally while cellular remains unavailable
Expected: Environmental cellular coverage is ruled in or out.
If cellular communication fails consistently across known-good coverage locations, suspect provisioning, service, or internal communication hardware and escalate appropriately.
13. Perform Only Approved Non-Patient Reconnection Actions
If permitted by current Stryker instructions and facility policy, perform the supported reconnection or wireless setup action for the LIFEPAK CR2.
Do not:
- Open the enclosure
- Access internal radio hardware
- Modify antennas
- Bypass security controls
- Perform undocumented resets
- Alter network protections to force connectivity
Expected: Communication is re-established through an approved process.
If communication returns, verify stable status reporting before returning the AED to normal deployment.
14. Verify Sustained Communication
Do not close the work order after a single brief connection.
Confirm that:
- The expected online status returns
- The management platform receives current information
- Communication remains stable
- The unit does not immediately return offline
- The physical deployment location still has adequate coverage
Expected: Connectivity remains stable and the AED’s remote status is current.
If the issue is resolved, stop troubleshooting and document the result.
15. Compare With a Known-Good CR2 When Available
If another similarly configured LIFEPAK CR2 is available, compare behavior without changing internal components.
Use the same general environment and approved infrastructure.
Expected: The comparison helps isolate device-specific versus site-wide failure.
Both units fail: Suspect infrastructure, coverage, or service.
Only the original unit fails: Suspect unit-specific configuration, provisioning, or internal communication fault.
If the original unit alone continues to fail after approved external checks, stop and escalate.
If the Problem Persists
If signal availability, local infrastructure, network configuration, deployment records, approved setup, location effects, and management-platform status have been checked, common external causes have been ruled out.
The problem may involve:
- Persistent device communication hardware failure
- Internal wireless subsystem fault
- Cellular provisioning or service issue
- Corrupted or unresolved device configuration
- Account-side provisioning requiring Stryker support
- Another internal fault requiring authorized evaluation
The device should be:
- Removed from service when readiness or dependable deployment status cannot be assured
- Labeled Out of Service
- Replaced with a verified ready AED
- Sent for repair, bench evaluation, or authorized Stryker support
Do not open the enclosure or continue into unsupported internal radio, antenna, or board-level repair.
Knowing when to stop after external causes have been ruled out is proper troubleshooting.
Clinical Use Tip
Never delay emergency defibrillation because Wi-Fi, cellular service, or remote monitoring is unavailable.
A connectivity problem is not the time to troubleshoot on an active patient. Use the AED immediately when clinically required according to approved response procedures, and investigate connectivity only after patient care is secured.
If overall device readiness is uncertain, replace the unit with another verified ready AED before troubleshooting.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Staff reported the LIFEPAK CR2 was offline in LIFELINKcentral and was not maintaining Wi-Fi communication from its assigned location."
Cause
What was observed during troubleshooting.
Example:
"Verified the AED was otherwise ready; local Wi-Fi signal at the installed cabinet was inadequate, while communication returned in a known-good coverage area."
Resolution
What action was taken.
Example:
"Removed the AED from the poor-coverage location for testing, confirmed stable communication in a known-good area, coordinated network coverage correction, and verified current online status before return to service."
Helpful Details to Include (If Known)
- AED readiness indication checked
- Battery and electrodes externally inspected
- Wi-Fi, cellular, or both identified
- Exact failure behavior documented
- SSID verified
- Network credentials/configuration reviewed
- Signal strength checked at deployment location
- Known-good wireless device compared
- Alternate location tested
- Recent network changes reviewed
- LIFELINKcentral last communication checked
- Cellular coverage evaluated
- Approved reconnection/setup attempted
- Indicator lights or audible alerts documented
- Unusual heat, smell, moisture, or physical damage noted
- Final device status documented
Final Thought
For LIFEPAK CR2 connectivity failures, protect patient readiness first, then separate device condition from network availability. Check location, signal, infrastructure, configuration, and management-platform status before suspecting internal failure. Escalate when external causes are ruled out, and document the complaint, verified cause, and final resolution clearly.
That is successful troubleshooting.