On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting probe recognition, probe communication, scan failure, or scanner-to-probe connection issues on the Verathon BladderScan i10.
Step-by-Step Troubleshooting
Ensure Patient Safety First
Do not troubleshoot probe communication issues during an active patient scan if results may be needed for care decisions.
Action:
- Remove the BladderScan i10 from clinical use if the probe is not recognized, scan cannot start, or communication errors repeat.
- Use another bladder scanner or approved clinical assessment method if bladder volume information is needed.
Expected outcome: Patient care is not delayed or based on an unreliable scan attempt.
Why it matters: A bladder scanner that cannot communicate with the probe may fail to acquire valid images or may interrupt the exam.
Verify the Reported Problem
Confirm the exact behavior before assuming probe or scanner failure.
Action:
- Power on the BladderScan i10.
- Check whether the device displays a probe communication error, probe not detected message, scan unavailable condition, or missing probe indicator.
- Ask clinical staff when the issue occurs: at startup, when attempting to scan, after the probe was dropped, after cleaning, after charging or cart docking, or intermittently during use.
Expected outcome: The failure pattern is confirmed and documented.
If the probe is recognized after restart and scanning works normally, document the temporary communication issue and return the device to service only after functional testing.
Inspect the Probe and Cable Externally
Check for obvious physical damage.
Action:
- Inspect the probe housing for cracks, impact marks, loose seams, damaged lens surface, fluid intrusion, or missing labels.
- Inspect the cable, strain relief, and connector area for cuts, kinks, crushed sections, exposed conductors, or looseness.
Expected outcome: Probe and cable appear physically intact.
If physical damage, fluid intrusion, or cable strain relief damage is found, remove the unit from service and send it for repair evaluation.
Check the Probe Connection
Confirm the probe is properly connected to the scanner or cart interface as applicable.
Action:
- Power the unit off.
- Disconnect and reconnect the probe connection fully.
- Ensure the connector is seated straight and secure.
- Do not force the connector if resistance is abnormal.
- Power the unit back on and check whether the probe is recognized.
Expected outcome: The scanner detects the probe and allows scanning.
If the issue resolves, perform a test scan or approved functional check, document the reseated connection, and stop.
Inspect Connector Pins and Contact Surfaces
Look for external connector problems that could block communication.
Action:
- Inspect the probe connector and scanner-side connector for bent pins, debris, corrosion, moisture, gel, dried cleaner, or damaged contacts.
- Use only approved cleaning methods for external surfaces.
- Allow any recently cleaned parts to dry completely before retesting.
Expected outcome: Connectors are clean, dry, undamaged, and able to make reliable contact.
If pins are bent, contacts are damaged, or corrosion is present, remove the device from service for repair.
Confirm the Probe Is Correct for the Scanner
Make sure the connected probe belongs with the BladderScan i10 system.
Action:
- Check that the probe is a compatible Verathon BladderScan i10 probe.
- Verify the probe has not been swapped from another model or system.
- Compare asset tags or department labels if multiple bladder scanners are in use.
Expected outcome: The scanner and probe are correctly matched.
If the probe is mismatched, reconnect the proper probe and retest.
Restart the Scanner
Clear a possible temporary software or communication lockup.
Action:
- Power the BladderScan i10 completely off.
- Wait briefly.
- Power it back on.
- Allow the system to fully boot before attempting a scan.
Expected outcome: The scanner initializes normally and recognizes the probe.
If the issue resolves, complete a functional check and document the restart.
Check Battery and Power Status
Low or unstable power can contribute to startup or accessory communication issues.
Action:
- Confirm the scanner has adequate battery charge.
- Connect the unit to its charger or docking station if available.
- Verify charging indicators or power status.
- Retest probe recognition after the unit has stable power.
Expected outcome: The scanner powers normally and maintains probe communication.
If the unit only recognizes the probe while connected to power, document battery or power-related behavior and evaluate the battery/charging system separately.
Check for Moisture or Cleaning-Related Issues
Probe communication problems may occur after cleaning if moisture enters or remains around the connector.
Action:
- Ask whether the issue started after cleaning or disinfection.
- Inspect for wet connector areas, residue, or excessive liquid exposure.
- Allow the device and probe exterior to dry fully before reconnecting.
Expected outcome: No moisture or residue is present near the probe connection.
If the issue resolves after drying, educate staff on proper cleaning precautions and document the finding.
Test With Known-Good Accessories if Available
Use substitution to isolate the issue without opening the device.
Action:
- If your facility has another compatible BladderScan i10 probe or scanner, test the suspected probe on a known-good scanner or test a known-good probe on the affected scanner.
- Follow facility policy for accessory swapping and asset tracking.
Expected outcome:
- If the suspected probe fails on another scanner, the probe is likely faulty.
- If a known-good probe fails on the affected scanner, the scanner-side connection or internal electronics may be faulty.
- If both work after reconnection, the issue may have been a seating or contamination problem.
- If substitution identifies a faulty component, remove the affected component from service and send for repair or replacement.
Perform a Functional Scan Check
Do not return the scanner to service based only on the error disappearing.
Action:
- Perform an approved test scan or functional verification according to department practice.
- Confirm the probe is recognized, scan initiates normally, image acquisition proceeds, and the result displays without communication errors.
Expected outcome: The BladderScan i10 completes a scan without probe recognition or communication errors.
If the scan completes normally and the issue does not recur, return the device to service and document the verification.
If the Problem Persists
If the BladderScan i10 still reports probe not recognized or probe communication error after checking power, probe seating, connectors, cleaning residue, compatibility, restart behavior, and known-good substitution if available, common external causes have been ruled out.
The device should be removed from service, labeled Out of Service, and sent for repair, probe replacement evaluation, or bench service.
Do not continue troubleshooting into internal electronics unless authorized by service documentation and facility policy. Knowing when to stop is proper troubleshooting.
Clinical Use Tip
Do not troubleshoot a probe communication problem while clinical staff are depending on that scanner for an active patient decision. Move to another bladder scanner or approved backup method first, then troubleshoot the affected unit when patient care is protected.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported the Verathon BladderScan i10 displayed a probe communication error and would not start a bladder scan."
Cause
What was observed during troubleshooting.
Example:
"Inspection found the probe connector was not fully seated and had dried gel residue around the connector area."
Resolution
What action was taken.
Example:
"Cleaned the external connector area, reseated the probe, restarted the scanner, completed a functional scan check, and returned the unit to service."
Helpful Details to Include (If Known)
- Outlet or charger tested
- Battery level at time of failure
- Exact error message displayed
- Whether issue occurred at startup or during scan
- Probe connector condition
- Cable and strain relief condition
- Presence of gel, cleaner residue, moisture, or corrosion
- Whether restart changed the behavior
- Whether known-good probe or scanner was tested
- Final device status
- Whether the device was returned to service or sent for repair
Final Thought
Probe communication issues should be approached logically: protect the patient first, verify the reported problem, check the probe, connector, power, cleaning residue, and compatibility before assuming internal failure. If the scanner cannot reliably recognize the probe after external checks, remove it from service and escalate for repair. Clear CCR documentation helps show exactly what was checked and why the final decision was made.
That is successful troubleshooting.