On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Error #000000013 indicating communication failure causing loss of module connectivity, network issues, or inability to acquire or transmit patient data.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Remove the monitor from active patient use if communication or data transfer is unreliable.
- Expected: Patient monitoring safely transferred to another device.
- Why it matters: Loss of communication can affect documentation and clinical decisions.
Verify the Reported Error and Behavior
- Power on the device and confirm Error #000000013 appears. Observe:
- When the error occurs (startup vs during use)
- If modules (SpO₂, NIBP, temp) are not detected
- If network connectivity or EMR transmission fails
- Expected: Error is reproducible with clear loss of communication or module recognition.
- Why it matters: Confirms a true system-level communication fault.
Perform a Full Power Cycle
- Shut down the monitor, disconnect from AC power, and remove the battery (if accessible). Wait 60 seconds, then reconnect and power on.
- Expected: Device boots normally and error clears if transient.
- Why it matters: Clears temporary communication or initialization faults.
- If resolved → Return device to service
Check External Module Connections
- Inspect all connected modules and accessories:
- Ensure modules are fully seated and latched
- Disconnect and reconnect each module
- Inspect ports for bent pins, debris, or damage
- Expected: Modules are recognized after reseating.
- Why it matters: Loose or poor connections can trigger communication errors.
- If a specific module is not recognized → Remove it and test device without it
Isolate Accessory or Module Issues
- Remove all external modules and power on the monitor in a minimal configuration. Then reconnect one module at a time.
- Expected: Error does not appear until a faulty module is connected (if accessory-related).
- Why it matters: Helps determine if the issue is caused by an external module vs internal board.
- If error returns with a specific module → Replace that module
Check Network / Communication Interfaces (If Applicable)
- If using Ethernet or wireless connectivity:
- Inspect Ethernet cable and port
- Try a known working cable and port
- Verify network link indicators (if present)
- Expected: Stable connection without error recurrence.
- Why it matters: External communication faults can mimic internal failures.
Inspect Physical Condition of Device
- Check for:
- Signs of liquid intrusion
- Physical damage near ports or connectors
- Excessive heat or unusual odors
- Expected: No visible damage or contamination.
- Why it matters: Environmental damage can affect internal communication pathways.
If the Problem Persists
If the error continues after all external checks:
- External modules, cables, and connections have been ruled out
- Power reset did not resolve the issue
This strongly indicates an internal failure of the communications module or main board.
Action:
- Remove the device from service
- Label as Out of Service
- Send for repair or bench evaluation
Clinical Use Tip
Do not rely on a monitor that cannot communicate with its modules or network. Always transfer the patient before troubleshooting.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Device displaying Error #000000013. Modules not recognized and unable to transmit patient data."
Cause
What was observed during troubleshooting.
Example:
"Internal communication failure suspected after reseating modules, isolating accessories, and performing power reset with no resolution."
Resolution
What action was taken.
Example:
"Device removed from service, labeled out of service, and sent for repair. Verified issue not related to external modules or cabling."
Helpful Details to Include (If Known)
- Alarm behavior
- Accessories swapped
- Power behavior
- Environmental factors
- Indicator lights
- Final device status
Final Thought
Communication errors should always be approached by ruling out external modules and connections first. Persistent system errors typically indicate internal board failure and require escalation. Patient safety and accurate data flow must always be prioritized.
That is successful troubleshooting.