Medline BioCon 700 / 750 Series

Asset Type

Bladder Scanner

Manufacturer

Medline

Model

BioCon 700 / 750 Series

What This Guide Helps With

Troubleshooting an absent, intermittent, or unreliable probe connection caused by seating, connector contamination, cable damage, probe failure, or scanner-side faults.

Step-by-Step Troubleshooting

1. Ensure Patient Safety First

Do not troubleshoot an unresolved probe or scan-head connection failure while relying on the BioCon scanner for a clinical bladder-volume assessment.

Move the patient to another verified bladder scanner or appropriate clinical assessment method before continuing.

Expected: Patient care is not dependent on a scanner with an unreliable probe connection.

Why it matters: The BioCon platform depends on the ultrasound probe to acquire the information required for bladder-volume measurement. Medline identifies a replacement probe specifically for the BioCon 700 and 750 platforms.

If transferring to another device resolves the immediate clinical concern, continue troubleshooting only in a controlled Clinical Engineering setting.

2. Confirm the Exact Failure Behavior

Power on the scanner and determine what Clinical Engineering can reproduce:

• Probe not detected
• No scan response when scanning is initiated
• Intermittent probe recognition
• Connection lost when the cable is moved
• Absent or abnormal prescan image
• Failure only after startup
• Hardware, maintenance, or self-diagnostic indication
• Device recognizes the probe but scanning remains abnormal

Document the exact behavior rather than recording only “probe bad.”

Expected: The complaint is narrowed to a reproducible connection, cable, probe, or scanner-side symptom.

If the probe operates normally and repeated scans are stable, the issue may have been transient. Document testing and stop.

3. Perform a Controlled Restart

Shut down the scanner normally.

Allow the device to fully power down, then restart it and observe whether the probe is recognized consistently.

Expected: The probe initializes and remains available after startup.

Why it matters: A controlled restart helps distinguish a temporary initialization or communication problem from a repeatable hardware fault.

If restart restores normal operation, perform repeated functional scans before returning the device to service. If the issue does not recur and testing passes, document the result and stop.

4. Inspect the Probe and Scan Head Externally

Examine the complete probe assembly for:

• Cracked housing
• Separation at seams
• Impact damage
• Loose components
• Signs of fluid intrusion
• Damaged strain relief
• Cable cuts or crushing
• Severe twisting or kinking
• Unusual heat
• Burnt odor
• Evidence of improper cleaning or chemical damage

Do not continue using a visibly compromised probe.

Expected: The probe housing and cable are intact with no obvious condition that could compromise reliable operation.

Medline markets a dedicated replacement probe for the BioCon 700 and 750, supporting probe substitution as an appropriate external troubleshooting step rather than assuming immediate console failure.

If physical damage is found, remove the affected probe or scanner from service as appropriate and stop.

5. Inspect the Probe Connection Point

With the device safely removed from patient use, inspect the accessible probe connection area.

Check for:

• Incomplete seating
• Loose connection
• Debris
• Dried gel
• Cleaning residue
• Moisture
• Bent or damaged accessible contacts
• Cracked connector housing
• Mechanical looseness

Do not insert metal objects into the connector and do not force a damaged connection.

Expected: The connection area is clean, dry, mechanically intact, and capable of secure engagement.

If contamination is present, clean only according to approved facility and manufacturer-compatible practices, allow the area to dry fully, reconnect, and retest.

If this restores stable probe recognition, document the corrective action and stop.

6. Disconnect and Reseat the Probe Connection Where User-Accessible

If the installed configuration provides a user-accessible probe connection, disconnect it only after the scanner is safely powered down and removed from clinical use.

Inspect the connection, then reconnect it fully without forcing it.

Restart the scanner and check recognition.

Expected: The probe is consistently recognized after proper reseating.

If reseating resolves the issue, perform repeated functional checks and stop once reliable operation is verified.

If the connection is not intended for routine user or field disconnection, do not force access or proceed into internal disassembly.

7. Check for Cable-Position Sensitivity

With the scanner in a controlled bench setting, observe operation while gently repositioning the probe cable through normal ranges of movement.

Pay particular attention near:

• Probe strain relief
• Connector strain relief
• Areas showing previous compression
• Frequently flexed cable sections

Do not sharply bend, twist, or stress the cable.

Expected: Probe recognition and scanning remain stable during ordinary cable positioning.

If recognition repeatedly drops at a particular cable position, suspect an intermittent probe cable or connection fault.

Remove the affected assembly from service and stop.

8. Test With a Known-Good Compatible Probe

When an approved known-good BioCon 700/750-compatible probe is available, substitute it for comparison.

Medline lists a replacement probe for the BioCon 700 and 750 bladder scanners, making controlled probe substitution a strong isolation step.

Retest:

• Startup recognition
• Scan initiation
• Prescan behavior where applicable
• Repeated scan stability
• Cable-position stability

Expected: A known-good compatible probe operates consistently.

Interpret the result logically:

• Known-good probe works: Original probe or cable assembly is strongly suspect.
• Known-good probe also fails: Scanner-side connector, communication, or internal hardware becomes more likely.
• Both probes are intermittent: Investigate scanner-side connection integrity and escalate.

If the known-good probe resolves the problem and required functional testing passes, replace or quarantine the defective probe, document the result, and stop.

9. Cross-Test the Suspect Probe When Appropriate

If another compatible, verified BioCon 700/750 unit is available and facility procedures permit, test the suspect probe on that known-good platform.

Expected: The cross-test helps determine whether the problem follows the probe.

Interpretation:

• Failure follows the probe: Probe or cable assembly is likely defective.
• Probe works normally on another compatible unit: Original scanner-side connection or internal circuitry becomes more likely.
• Results remain inconsistent: Remove the questionable equipment from service pending further evaluation.

Do not use a patient to perform comparative troubleshooting.

10. Evaluate Scan Function After Connection Is Restored

A probe that is merely “detected” should not automatically be considered functional.

After stable recognition is restored, verify appropriate operation using an approved functional-check method, test object, phantom, or facility procedure.

For the BioCon 700, Medline lists a calibration kit among available accessories.

Check for:

• Stable scan initiation
• Repeatable acquisition
• Reasonable image or targeting behavior
• No connection dropouts
• No abnormal hardware indications
• Consistent repeated results under the approved test method

Expected: The probe remains connected and the scanner performs repeatably.

If connection is restored but functional performance remains abnormal, do not return the scanner to service solely because the probe is detected.

11. Review Self-Diagnostic or Hardware Indications

If the scanner displays a hardware, maintenance, or diagnostic indication, record the exact message and determine whether it persists with:

• Restart
• Connection reseating
• Known-good compatible probe
• Verified external condition

The BioCon 750 is described as providing built-in self-diagnostic capability intended to alert users to hardware or maintenance issues.

Expected: A transient external issue clears after correction; a repeatable diagnostic fault remains reproducible.

Do not repeatedly clear or ignore a persistent hardware indication.

12. Perform Final Reproducibility Testing

Before return to service, complete several repeated functional cycles.

Verify:

• Probe recognized after startup
• No intermittent disconnect
• Scan command responds normally
• Functional test is repeatable
• Cable movement within normal handling does not interrupt operation
• No abnormal messages
• No unusual heat, odor, or sound

Expected: The scanner performs consistently across repeated tests.

If the issue recurs even once during final testing, do not return the device to clinical use.

If the Problem Persists

If the probe remains undetected, intermittently disconnects, fails with a known-good compatible probe, or produces persistent hardware indications after external checks, common external causes have been ruled out.

The issue is likely related to the probe assembly, scanner-side connector, internal communication path, or another internal hardware fault.

The device should be:

• Removed from service
• Labeled Out of Service
• Sent for repair or controlled bench evaluation

Do not proceed into unsupported internal connector, board-level, or component-level repair without appropriate service documentation, authorization, and post-repair verification.

Knowing when to stop is proper troubleshooting.

Clinical Use Tip

Never troubleshoot an intermittent bladder-scanner probe on an active patient. Move the patient to another verified device first, then reproduce the failure under controlled conditions.

A probe that reconnects after cable movement should not automatically be considered repaired. Intermittent faults can return during clinical use.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Clinical staff reported that the BioCon 750 intermittently failed to recognize the scan probe and would not reliably initiate bladder scans."

Cause

What was observed during troubleshooting.

Example:
"Inspection and substitution testing found that the connection failure followed the original probe assembly, while a known-good compatible probe remained stable."

Resolution

What action was taken.

Example:
"Removed the defective probe from service, installed a verified compatible replacement probe, completed repeated functional scans without disconnects, and returned the scanner to service."

Helpful Details to Include (If Known)

• Exact probe-related symptom documented
• Startup recognition checked
• Probe housing inspected
• Probe cable inspected
• Strain relief inspected
• Connection point inspected
• Connection reseated
• Cable-position sensitivity checked
• Known-good compatible probe tested
• Suspect probe cross-tested
• Self-diagnostic behavior documented
• Functional test or approved phantom check completed
• Repeated scans completed
• Unusual heat or smell checked
• Final device status documented

Final Thought

Probe connection failures should be isolated logically from the outside inward. Protect the patient first, inspect the probe and cable, verify connection integrity, substitute known-good accessories when available, and escalate when the fault points toward scanner-side or internal hardware. Clear CCR documentation preserves the evidence behind the repair decision.

That is successful troubleshooting.