On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting probe recognition, probe port, connector, seating, and transducer communication faults before repair escalation.
Step-by-Step Troubleshooting
Ensure Patient Safety First
Confirm the ACUSON Juniper is not being used on an active patient before troubleshooting the probe connection.
If the issue occurs during an exam, have clinical staff stop the study, move the patient to another ultrasound system if needed, and preserve any completed images according to department workflow.
Expected outcome: The patient is not delayed or scanned with an unreliable probe connection.
Confirm the Exact Probe Complaint
Ask the operator what happened and when the issue appeared.
Determine whether the problem involves:
- Probe not detected
- Probe detected intermittently
- Wrong probe type displayed
- Image unavailable after probe selection
- Probe disconnects when cable is moved
- One probe failing on one port
- Multiple probes failing on the same port
- All probes failing on the system
Expected outcome: The issue is narrowed to a probe, port, connector, cable, or system-level recognition problem.
Check for Active Error Messages
Review the on-screen message, probe selection screen, and system status indicators.
Note whether the system reports a probe connection fault, unsupported probe, unavailable probe, or no transducer connected.
Expected outcome: The error message helps separate a physical connection issue from a compatibility or software recognition issue.
Verify the Probe Is Fully Seated
Power the system to a safe idle state and confirm the probe connector is fully inserted and locked into the probe port.
Do not force the connector. The probe should seat smoothly and lock securely.
Expected outcome: A loose or partially seated probe is corrected. If the probe is recognized after reseating, verify imaging function and stop.
Inspect the Probe Connector Externally
Remove the probe and inspect the connector pins, locking mechanism, shell, and strain relief.
Look for bent pins, missing pins, debris, fluid residue, cracked housing, damaged latch components, or signs of impact.
Expected outcome: Visible connector damage is identified before suspecting an internal system fault.
Inspect the Probe Cable and Transducer Housing
Check the full probe cable length for cuts, crushed sections, sharp bends, exposed shielding, swelling, or strain relief separation.
Inspect the transducer head for cracks, fluid intrusion, delamination, or evidence of being dropped.
Expected outcome: A physically damaged probe is removed from service and not reused on patients.
Check the Probe Port for Debris or Damage
Inspect the ACUSON Juniper probe port externally for debris, bent contacts, damaged latch points, liquid residue, or foreign material.
Do not insert tools into the connector or attempt deep cleaning beyond approved external cleaning practices.
Expected outcome: Port damage or contamination is identified. If the port appears damaged, remove the system from service and escalate.
Try a Known-Good Probe on the Same Port
Connect a known-good, compatible Siemens probe to the same probe port.
Expected outcome:
- If the known-good probe works, the original probe is likely defective or incompatible.
- If the known-good probe also fails, the port or system may be the cause.
Try the Suspect Probe on Another Available Port
If the system has another compatible probe port available, connect the suspect probe to that port.
Expected outcome:
- If the probe works on another port, the original port may be faulty.
- If the probe fails on multiple ports, the probe or probe connector is suspect.
Confirm Probe Compatibility
Verify that the probe model is approved for use with the ACUSON Juniper and the installed software configuration.
A probe may physically connect but still fail recognition if it is unsupported, not enabled, damaged, or not compatible with the system software.
Expected outcome: Compatibility is confirmed before hardware failure is assumed.
Restart the Ultrasound System
If no patient is active and the probe and port appear externally normal, perform a controlled system restart.
After restart, reconnect the probe and check whether it appears in the probe selection menu.
Expected outcome: A temporary software or initialization issue clears. If the probe is recognized and imaging is stable, document the restart and functional check.
Check Whether the Issue Is Intermittent
With the probe connected and selected, gently position the cable in a neutral, stress-free position.
Do not aggressively flex or twist the cable. Observe whether recognition drops out with normal handling.
Expected outcome: Intermittent connection behavior is identified safely. A probe that disconnects during normal handling should be removed from service.
Perform a Basic Imaging Verification
If the probe is recognized, confirm that the probe produces an image using an approved phantom or non-patient test method per site practice.
Check for image dropout, missing elements, excessive noise, or abnormal artifacts.
Expected outcome: Probe recognition and basic imaging function are both verified before returning the system to clinical use.
Review Recent Events
Ask whether the probe was recently dropped, cleaned, soaked incorrectly, repaired, moved between rooms, or connected after a software update.
Expected outcome: A recent handling, cleaning, compatibility, or configuration change may explain the recognition fault.
Do Not Continue Using an Unreliable Probe
If the probe is intermittently recognized, physically damaged, or produces unstable images, remove the probe from service even if it occasionally works.
Expected outcome: Clinical staff do not rely on a probe that may disconnect or fail during an exam.
If the Problem Persists
If the probe, connector seating, visible probe condition, port condition, compatibility, and restart have been checked and the fault remains, common external causes have been ruled out.
The ACUSON Juniper or the affected probe should be:
- Removed from clinical use
- Labeled Out of Service
- Sent for Clinical Engineering bench evaluation or vendor repair
- Tested with known-good probes and ports before parts are replaced
Knowing when to stop is proper troubleshooting. Do not attempt internal probe port repair, connector disassembly, or board-level repair during clinical troubleshooting.
Clinical Use Tip
Do not troubleshoot probe recognition faults on an active patient. If probe detection is unstable during an exam, move the patient to another available ultrasound system or probe first, then troubleshoot only when the system is safe to evaluate.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Ultrasound staff reported that the ACUSON Juniper would not recognize the selected probe during exam setup."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found the probe was not detected on multiple ports, while a known-good compatible probe was recognized normally."
Resolution
What action was taken.
Example:
"Removed the suspect probe from service, labeled it Out of Service, verified the ACUSON Juniper recognized a known-good probe, and sent the failed probe for repair evaluation."
Helpful Details to Include (If Known)
- Probe model and serial number
- Probe port used
- Whether the issue followed the probe or stayed with the port
- Exact error message displayed
- Whether a known-good probe was tested
- Whether the suspect probe was tested on another port
- Connector condition
- Cable and strain relief condition
- Any visible fluid, debris, bent pins, or physical damage
- Whether the system was restarted
- Whether basic imaging was verified
- Alarm behavior
- Accessories swapped
- Power behavior
- Environmental factors
- Indicator lights
- Final device and probe status
Final Thought
Probe recognition issues should be approached logically: protect the patient first, confirm the complaint, inspect the probe and port externally, compare with a known-good probe, and escalate when the fault points to a damaged probe, failed port, or internal system problem. Clear CCR documentation helps show what was tested, what was ruled out, and why the device or probe was returned to use or removed from service.
That is successful troubleshooting.