On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting BBS Revolution wireless scanner connection issues caused by battery, docking, Bluetooth connection, range, or console power problems.
Step-by-Step Troubleshooting
Ensure Patient Safety First
Confirm the scanner is not being used for an active patient assessment.
If staff need an immediate bladder volume, provide another verified bladder scanner or follow the department’s backup process.
Expected outcome: Patient care is not delayed while Clinical Engineering evaluates the scanner.
Confirm the Reported Connection Problem
Ask staff what they observed:
- Scanner does not connect after being removed from dock
- Console does not wake up
- Scanner button does not initiate scan
- Blue scanner LEDs do not become solid
- Scanner connects intermittently
- Console does not display scan result
- Scanner was found away from the console or not charged
Expected outcome: The failure mode is clearly identified before troubleshooting.
Verify Console Power and Battery Status
Check whether the console powers on and whether the console battery is low.
Connect the console to a known-good AC outlet and allow it to charge if the battery indicator is low. BD documentation notes the console should be connected to AC power daily, and a red battery indicator means the device should be connected to AC for at least two hours.
Expected outcome: Console power is stable and not preventing wireless communication.
If restoring AC power resolves the issue, stop and document the outlet, cord, or charging-related cause.
Check Scanner Battery and Docking Position
Dock the wireless scanner into the console and verify that yellow lights appear on the scanner, indicating it is charging.
Confirm the scanner is seated in the correct orientation. If the scanner is docked backwards, the scanner will not charge, and the console may show a rotating or blinking scanner icon.
Expected outcome: Scanner charging indication is present.
If the scanner was docked incorrectly and begins charging after repositioning, allow adequate charge time, retest, and stop if the connection returns.
Wake the Scanner Properly
Remove the scanner from the dock and press the scanner button.
Wait for the blue LEDs to become solid, which indicates a successful Bluetooth connection according to the BD operating information.
Expected outcome: Scanner wakes and establishes communication with the console.
If the blue LEDs become solid and scanning works, document as a scanner sleep or low-power recovery issue.
Check Wireless Range and Location
Keep the scanner and console close together during testing.
The BBS Revolution uses a wireless scanner and display console, with scan results transferred wirelessly to the console. BD in-service material lists the wireless connection range as approximately 33 ft / 10 m.
Expected outcome: Scanner connects reliably when tested near the console.
If the scanner only fails at distance, document range, wall, room, or interference concerns rather than replacing parts immediately.
Inspect the Scanner and Console Dock Area
Look for external damage, fluid residue, dried gel, cracked housing, damaged charging contacts, loose dock fit, or debris preventing full seating.
Clean external surfaces according to facility-approved cleaning procedures. Do not scrape, pry, or disassemble the dock or scanner.
Expected outcome: Scanner seats fully and charges without obstruction.
If cleaning and proper seating restore connection, stop and document the finding.
Power Cycle the System
With the scanner docked, power the console down if possible, disconnect AC briefly, then reconnect AC and power the console back on.
Remove the scanner and press the scanner button to reattempt connection.
Expected outcome: Console and scanner reinitialize and reconnect.
If a temporary software or communication lockup clears after restart, document the power cycle and verify repeated successful connection.
Verify Scanner-to-Console Pairing Behavior
Confirm the scanner belongs with that console and was not swapped from another BBS Revolution unit.
If multiple units are in the area, check asset tags and physical pairing history. A wireless scanner from another cart may not communicate as expected with the current console.
Expected outcome: The correct scanner is being tested with its intended console.
If the wrong scanner was docked or mixed between units, return components to the correct asset and retest.
Check for Intermittent Connection
Perform several dock-undock and scan-start attempts near the console.
Watch for inconsistent LED behavior, delayed connection, scanner shutting off quickly, console failing to wake, or connection dropping after movement.
Expected outcome: Connection is repeatable and stable.
If the issue is intermittent but repeatable, remove the unit from service for bench evaluation.
Inspect for Signs of Damage or Contamination
Check the scanner face, housing, button, LEDs, console dock, display, AC adapter, and charging cord.
Look for:
- Cracks
- Loose scanner button
- Missing or inconsistent LEDs
- Liquid intrusion signs
- Damaged dock contacts
- Bent or loose charging connection
- Unusual heat or smell
Expected outcome: No visible damage or unsafe condition is present.
If damage, overheating, liquid intrusion, or unsafe charging behavior is found, stop troubleshooting and remove the device from service.
Perform a Functional Connection Check
After charging, remove the scanner, confirm connection LEDs, perform a test scan according to facility policy, and verify that the console displays the result.
Expected outcome: Scanner connects, scan initiates, and result transfers to the console.
If connection and result transfer are normal after external checks, return the unit to service per department procedure.
If the Problem Persists
If the scanner still will not connect after confirming console power, AC charging, correct docking, scanner charge status, range, proper scanner-console pairing, and external condition, common external causes have been ruled out.
The issue may involve an internal scanner battery, Bluetooth communication fault, charging dock fault, console communication board issue, or software/firmware problem.
The device should be:
- Removed from service
- Labeled Out of Service
- Sent for repair or bench evaluation
Knowing when to stop is proper troubleshooting. Do not continue repeated bedside troubleshooting when the scanner cannot reliably connect and transfer results.
Clinical Use Tip
Do not troubleshoot wireless connection problems during an active patient scan if the result is clinically needed. Move staff to another verified bladder scanner first, then evaluate the suspect unit away from patient care.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Nursing reported that the BD BBS Revolution wireless scanner would not connect to the console after being removed from the dock."
Cause
What was observed during troubleshooting.
Example:
"Scanner was found docked backwards and was not charging; yellow charging lights were not present until the scanner was reseated correctly."
Resolution
What action was taken.
Example:
"Repositioned scanner in the dock, confirmed charging indication, allowed unit to charge, verified blue connection LEDs, completed functional scan transfer, and returned device to service."
Helpful Details to Include (If Known)
- Console connected to AC power
- Outlet tested or swapped
- Console battery status
- Scanner charging lights present or absent
- Scanner docked correctly or backwards
- Blue LED connection behavior
- Scanner-to-console distance during failure
- Whether scanner was mixed with another console
- Any visible damage, gel residue, or liquid contamination
- Whether power cycle restored connection
- Final device status
Final Thought
Wireless connection issues on the BBS Revolution should be approached logically: protect patient care first, then verify power, charge status, docking position, scanner wake-up, range, and external condition. If the scanner still will not connect after those checks, remove it from service and escalate for repair with clear CCR documentation.
That is successful troubleshooting.