On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Identifies common external causes of probe connection errors, including cabling, port, and software issues.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Confirm no patient is connected to the system.
- Expected outcome: Safe environment for troubleshooting.
Power Cycle the System
- Turn off the DC Series unit, wait 30 seconds, then power on.
- Expected outcome: Clears temporary system glitches that can prevent probe recognition.
Inspect Probe and Cable
- Check for visible damage: kinks, frays, bent pins, or cracks.
- Expected outcome: Identify obvious physical faults; damaged probes must not be used.
Reconnect Probe Securely
- Remove and reconnect the probe to the port. Ensure a firm, fully seated connection.
- Expected outcome: Re-establish proper electrical and data connection.
Try an Alternate Port (if available)
- Move the probe to a different compatible port on the DC Series system.
- Expected outcome: Determine if the original port is faulty.
Swap with a Known Good Probe
- Connect a functioning probe to the same port.
- Expected outcome: Confirms whether the system or original probe is at fault.
Check Software / Probe Recognition
- Navigate to the system’s probe management or settings menu. Confirm probe is detected and firmware is compatible.
- Expected outcome: Software updates or mismatched firmware may cause recognition errors.
Inspect Indicators and Alarms
- Observe system messages, alarms, or warning icons during probe connection.
- Expected outcome: Provides clues for specific error codes or system responses.
If the Problem Persists
External checks completed; issue may be internal (port electronics or probe failure).
Actions:
- Remove device from service.
- Label “Out of Service.”
- Send for bench repair or manufacturer evaluation.
Knowing when to stop prevents unsafe troubleshooting and protects the system.
Clinical Use Tip
- Never attempt probe troubleshooting while scanning a patient.
- Move the patient to another device first.
- Always verify the system is powered down or in a safe mode before reconnecting probes.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported probe not recognized on the DC Series system."
Cause
What was observed during troubleshooting.
Example:
"Probe connection error confirmed; no physical damage found, system did not detect probe."
Resolution
What action was taken.
Example:
"Probe reconnected, alternate port tested, problem persisted; device sent for repair."
Helpful Details to Include (If Known)
- Ports tested: Yes
- Cables swapped: Yes
- Alarms/alerts: “Probe Not Detected”
- Indicator lights: Probe port LED status normal
- Device status: Out of Service
Final Thought
Patient safety is the priority. Logical, stepwise troubleshooting rules out simple causes before escalation. Proper documentation ensures accurate communication for repair and continued clinical readiness.
That is successful troubleshooting.