On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting probe communication, scan trigger, cable, connection, docking, or control issues preventing bladder scan capture.
Step-by-Step Troubleshooting
Ensure Patient Safety First
Do not troubleshoot the bladder scanner while it is actively being used for patient assessment.
Action:
- Remove the scanner from patient use if the probe does not communicate, the scan button does not respond, or scan results cannot be trusted.
- Use another bladder scanner or alternate approved clinical method if bladder volume measurement is needed.
Expected outcome: Patient care is not delayed or based on unreliable scan data.
Why it matters: A failed probe or scan trigger can prevent accurate bladder volume measurement and may affect care decisions.
Verify the Reported Problem
Confirm exactly what is failing before assuming a probe defect.
Action:
- Power on the PadScan HD system.
- Attempt a scan using normal workflow.
- Observe whether the probe is not detected.
- Observe whether the scan trigger does not respond.
- Observe whether the scan starts but immediately stops.
- Observe whether the system displays a probe communication message.
- Observe whether the probe works intermittently.
- Observe whether the issue occurs only when the cable is moved.
Expected outcome: The failure mode is clearly identified.
If the scanner operates normally during testing, document that the issue could not be duplicated and return the device only if it passes functional checks.
Check Battery Charge and System Power
Low battery or unstable power can cause communication or scan initiation problems.
Action:
- Confirm the scanner has adequate battery charge.
- Connect the unit to its charger or power adapter if available.
- Allow the device to charge briefly if the battery is low.
- Restart the scanner and retest the probe.
Expected outcome: The scanner powers normally and the probe responds to scan commands.
If the problem resolves after charging, document low battery or power-related behavior and stop.
Inspect the Probe and Cable Externally
Probe communication failures are commonly caused by damaged cable strain relief, connector damage, or fluid contamination.
Action:
- Inspect the probe body for cracks, impact damage, loose housing, or signs of fluid intrusion.
- Inspect the cable along its full length for cuts, kinks, pulled insulation, or crushed areas.
- Check the probe strain relief at both ends.
- Do not flex or stress a visibly damaged cable during patient-use testing.
Expected outcome: The probe and cable appear physically intact.
If damage is found, remove the device from service and send it for repair or probe replacement evaluation.
Check the Probe Connection
A loose or partially seated probe connector can prevent communication with the scanner.
Action:
- Power the scanner off.
- Inspect the probe connector and scanner-side port for bent pins, debris, corrosion, gel residue, or liquid contamination.
- Reseat the connector fully if it is designed to be user-accessible.
- Power the scanner back on and retest.
Expected outcome: The scanner recognizes the probe and scan trigger operation returns.
If reseating the probe resolves the issue, document the loose connection and stop.
Check for Gel, Fluid, or Debris Around the Probe and Connector
Bladder scanners are frequently exposed to gel and cleaning fluids, which can affect probe buttons or connector contacts.
Action:
- Inspect the probe face, trigger area, connector area, and cable entry points.
- Clean external surfaces according to facility-approved cleaning procedures and manufacturer-compatible disinfectants.
- Allow the probe and connector area to dry fully before retesting.
Expected outcome: The probe communicates normally and the scan trigger responds.
If contamination was present and cleaning resolves the issue, document the finding and stop.
Test the Scan Trigger or Button Response
The scan trigger may be stuck, damaged, or non-responsive even if the probe itself is detected.
Action:
- Press the scan trigger several times and feel for normal movement.
- Check whether the button feels stuck, soft, cracked, loose, or inconsistent.
- Attempt a scan using any available on-screen scan control if the model supports it.
Expected outcome: The scan trigger responds consistently and starts the scan.
If the on-screen control works but the physical trigger does not, suspect probe trigger or button hardware failure and remove the device from service.
Restart the System
A software lockup may prevent the scanner from recognizing the probe or accepting scan input.
Action:
- Power the scanner off using the normal shutdown process.
- Wait briefly.
- Power the scanner back on.
- Allow the system to fully boot before testing the probe.
Expected outcome: Probe communication and scan function return after restart.
If the problem resolves after reboot, document the lockup behavior and monitor for recurrence.
Check Docking, Charging, or Data Cradle Behavior
If the PadScan HD system uses a dock, cradle, or charging base, poor docking contact may contribute to power or communication problems.
Action:
- Inspect the dock or cradle for damaged pins, debris, loose fit, or charging failure.
- Confirm the scanner charges normally when docked.
- Remove and reseat the unit in the dock.
- Retest after confirming stable power.
Expected outcome: The scanner charges normally and probe operation is stable.
If the scanner does not charge or power remains unstable, troubleshoot the charging system before replacing the probe.
Compare With a Known-Good Probe or Scanner, If Available
Swapping known-good accessories helps isolate whether the fault follows the probe or stays with the scanner.
Action:
- If another compatible PadScan HD probe is available, connect it to the scanner.
- If another compatible scanner is available, test the suspect probe on that unit.
- Only use compatible equipment approved by your facility and manufacturer configuration.
Expected outcome:
- If the problem follows the probe, suspect probe/cable/trigger failure.
- If the problem stays with the scanner, suspect scanner-side port, interface, or internal hardware failure.
- If the known-good setup works, document the isolated failed component and remove it from service.
Check for Recent Drops, Cleaning Events, or Repairs
Intermittent probe problems often follow impact damage, liquid exposure, or recent service activity.
Action:
- Ask clinical staff whether the scanner was recently dropped, cleaned heavily, had gel spilled on it, or had the probe disconnected.
- Review recent work order history for repeated probe, trigger, power, or communication complaints.
Expected outcome: Recent events help explain the failure and guide escalation.
If the issue began after a drop or fluid exposure, remove the device from service for inspection.
Perform a Basic Functional Test
Before returning the scanner to service, confirm it can complete a normal scan workflow.
Action:
- Power on the scanner.
- Confirm the probe is detected.
- Start a scan using the trigger.
- Verify the system captures and displays a bladder scan result or expected test behavior.
- Confirm no communication error returns.
Expected outcome: The scanner completes a normal scan sequence without probe or trigger failure.
If the device passes, document testing and return it to service.
If the Problem Persists
If probe communication or scan trigger failure continues after checking power, battery charge, cable condition, connector seating, contamination, docking, restart behavior, and known-good accessory comparison, 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 inspection.
Do not continue repeated bedside testing if the probe is intermittent. Knowing when to stop is proper troubleshooting, especially when the device may provide unreliable patient assessment data.
Clinical Use Tip
Do not troubleshoot probe communication or scan trigger problems during an active patient scan. Move clinical staff to another working bladder scanner first. A bladder scanner that intermittently fails to scan should not be trusted for patient-care decisions until the fault is resolved and the device passes functional testing.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported that the Caresono PadScan HD probe would not communicate and the scan trigger would not start a bladder scan."
Cause
What was observed during troubleshooting.
Example:
"Found the probe connector partially seated with gel residue around the connector area, preventing reliable probe communication."
Resolution
What action was taken.
Example:
"Cleaned the external connector area, reseated the probe connection, restarted the scanner, and verified successful scan trigger operation during functional testing."
Helpful Details to Include (If Known)
- Alarm behavior or exact probe communication message displayed, if any
- Accessories swapped, including known-good probe or scanner comparison
- Power behavior, including battery level, charger use, docking, or charging behavior
- Environmental factors, including recent drop, cleaning, gel, fluid, or debris exposure
- Indicator lights, probe detection status, scan trigger response, cable condition, and connector condition
- Final device status, including returned to service, removed from service, labeled Out of Service, or sent for repair
Final Thought
Probe communication and scan trigger failures should be handled logically and safely. Start with power, battery, cable, connector, contamination, and restart checks before suspecting internal failure. If the scanner cannot reliably detect the probe or start a scan, remove it from service and document the complaint, cause, and resolution clearly.
That is successful troubleshooting.