On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Addresses probe detection failures caused by connection issues, port damage, or software recognition faults before assuming internal system failure.
Step-by-Step Troubleshooting
Ensure Patient Safety
- Remove the probe from any patient.
- If imaging is urgent, transition the patient to another system.
Inspect Probe Connection
- Examine the probe connector for bent or broken pins, debris, or moisture.
- Expected outcome: Clean, intact connector with no visible damage.
Verify Port Integrity
- Inspect the ultrasound system port for bent pins, debris, or corrosion.
- Expected outcome: Port appears intact and clean.
Swap Probe / Port
- If possible, connect a known-good probe to the port, or connect the suspect probe to a different system.
- Expected outcome: Determines whether the issue is probe-specific or port-specific.
Check Cable and Locking Mechanism
- Ensure probe cable is fully seated and locking latch is engaged.
- Expected outcome: Probe securely connected; system may now recognize the probe.
Power Cycle System
- Turn off the ultrasound, wait 30–60 seconds, and power it back on.
- Expected outcome: System initializes probe recognition sequence.
Software Recognition / Self-Test
- Run the system’s built-in probe self-test or diagnostics if available.
- Expected outcome: Probe passes or fails test; logs may indicate connection errors.
Observe Indicator Lights / Messages
- Look for system warnings, error codes, or status lights on port or probe.
- Expected outcome: Confirms whether the system detects the probe or port fault.
If the Problem Persists
External causes have been ruled out; the port or probe is likely damaged.
- Remove the system from service.
- Label the probe or system port as Out of Service.
- Send for repair or bench evaluation.
Clinical Use Tip
Never troubleshoot probes while actively imaging a patient.
Always have a backup system or probe available to avoid delaying patient care.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Probe not recognized on Canon Aplio system; error message displayed."
Cause
What was observed during troubleshooting.
Example:
"Inspection revealed bent pins in the system port and possible probe connector wear."
Resolution
What action was taken.
Example:
"System removed from service, labeled Out of Service, and sent to biomedical repair for port evaluation."
Helpful Details to Include (If Known)
- Which probe and port were tested
- Indicator lights or error messages observed
- Any unusual sounds, heat, or odor
- Final device status (e.g., removed from service, pending repair)
Final Thought
Always prioritize patient safety and use a logical troubleshooting sequence from simple external checks to escalation. Proper documentation ensures repeatable, safe, and accountable clinical engineering practice.
That is successful troubleshooting.