On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Addresses probes not being detected due to connection issues, port selection, probe faults, or system recognition errors before assuming internal failure.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Remove the probe from the patient and move to another functioning system if needed.
- Never troubleshoot probe recognition on an active patient.
Verify System Power and Boot State
- Confirm the system is fully powered on and has completed boot-up.
- Partial boot or software lag can prevent probe detection.
- Expected Outcome: System is fully operational with no startup errors.
Check Probe Connection at the Port
- Disconnect and firmly reconnect the probe to the system port.
- Ensure the connector is fully seated and locked.
- Look for bent pins, debris, or fluid contamination.
- Expected Outcome: Probe is securely connected with no visible damage.
Try a Different Probe Port
- Move the probe to another available port on the system.
- This helps determine if the issue is port-specific.
- Expected Outcome:
- If recognized → original port may be faulty
- If not recognized → continue troubleshooting
Test with a Known Good Probe
- Connect a known working probe to the same port.
- This isolates whether the issue is with the probe or system.
- Expected Outcome:
- If new probe works → original probe likely faulty
- If neither works → possible system or port issue
Inspect Probe Cable and Strain Relief
- Run your hand along the cable checking for:
- Cuts, kinks, or soft spots
- Loose strain relief at connector
- Expected Outcome: No physical damage that could interrupt signal communication.
Check System Probe Selection / Activation
- Verify the system recognizes the probe in the UI:
- Open probe selection menu
- Confirm correct probe type is selected (if manual selection required)
- Expected Outcome: Probe appears in system interface when connected.
Reboot the Ultrasound System
- Power cycle the system completely.
- Clears temporary communication faults
- Expected Outcome: Probe is recognized after restart.
Check for Error Messages or Alerts
- Observe any system messages related to probe failure or port errors.
- Note exact wording for documentation
- Expected Outcome: No persistent hardware error messages.
Inspect for Environmental or Contamination Issues
- Check for gel, fluid, or debris in probe ports.
- Clean per manufacturer-approved methods if needed
- Expected Outcome: Clean, dry connection interface.
If the Problem Persists
If all probes fail across ports or a known good probe is not recognized, common external causes have been ruled out. The issue is likely internal (probe port board, system electronics, or probe failure).
Remove the device from service, label it Out of Service, and send for repair or bench evaluation.
Clinical Use Tip
Always transfer the patient to another functioning ultrasound system before troubleshooting. Probe recognition issues can delay care and should never be addressed during active scanning.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Ultrasound probe not recognized when connected to system."
Cause
What was observed during troubleshooting.
Example:
"Faulty probe connector identified after testing with known good probe."
Resolution
What action was taken.
Example:
"Removed defective probe from service and sent for repair; system verified operational with alternate probe."
Helpful Details to Include (If Known)
- Probe ports tested
- Known good probe used
- Connector condition (pins, debris, fluid)
- Error messages observed
- System reboot performed
- Final device/probe status
Final Thought
Probe recognition issues are often caused by simple connection or probe faults rather than system failure. A structured, step-by-step approach ensures patient safety, avoids unnecessary downtime, and supports accurate repair decisions. Proper documentation also helps track recurring probe or port issues across the fleet.
That is successful troubleshooting.