On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
DRX detector connection, charging, pairing, or recognition problems caused by power, dock, battery, wireless, or configuration issues.
Step-by-Step Troubleshooting
Ensure Patient Safety First
Do not troubleshoot the DRX detector during an active patient exam if imaging cannot be completed safely.
Action:
- Remove the room from clinical use if the detector is unavailable, intermittently dropping connection, or not charging.
- Direct staff to another radiographic room or backup detector if patient imaging is urgent.
- Do not continue repeated exposure attempts if the detector is not properly recognized.
Expected outcome: Patient care continues using a reliable imaging setup before troubleshooting begins.
Why it matters: A detector communication or charging issue can delay imaging, cause repeat exams, or interrupt urgent care.
Verify the Reported Problem
Confirm whether the issue is connection, charging, pairing, or image acquisition related.
Action:
- Ask staff what they observed:
- Detector not detected by the system
- Detector will not pair
- Detector battery not charging
- Detector connects but drops offline
- Detector appears charged but is not available for imaging
- Check the workstation or console for detector status messages.
Expected outcome: The failure type is clearly identified before replacing parts or escalating.
If the detector is now recognized and ready for use, document the condition and stop.
Confirm the Correct Detector Is Being Used
Verify that the detector belongs to the DRX-Evolution room or is assigned for use with that system.
Action:
- Check the detector ID, room assignment, or asset tag.
- Confirm staff did not bring in a detector from another room or portable system.
- Compare the detector shown on the console with the physical detector being used.
Expected outcome: The system is attempting to connect to the correct detector.
Why it matters: DRX detectors may look similar, but the system may only recognize detectors configured or paired to that room.
If the correct detector is selected and the system connects normally, stop.
Check Detector Battery Status
Confirm the detector has enough battery charge to power on and communicate.
Action:
- Check the detector battery indicator if available.
- Place the detector into the approved charger or docking location.
- Allow the detector to sit long enough to show charging activity.
- If a spare compatible battery is available and approved for that detector, swap batteries and retest.
Expected outcome: The detector shows charge activity and powers on normally.
If the detector powers on and reconnects after charging or battery replacement, document the issue and stop.
Inspect the Detector Charging Dock or Charger
Check for simple charging failures before assuming the detector battery is bad.
Action:
- Confirm the charger or dock is plugged into a working outlet.
- Check for charger indicator lights.
- Inspect the dock contacts for debris, fluid, damage, bent pins, or poor alignment.
- Reseat the detector or battery fully in the charger.
- Test the outlet with another device or outlet tester if appropriate.
Expected outcome: The charger powers normally and the detector or battery makes solid contact.
If charging resumes after reseating, cleaning external contacts, or changing outlets, stop.
Inspect the Detector Externally
Look for physical damage that may prevent charging, pairing, or wireless communication.
Action:
- Inspect the detector housing for cracks, swelling, loose covers, fluid intrusion, damaged contacts, or missing labels.
- Check for signs of impact or being dropped.
- Smell for burning or unusual electrical odor.
- Feel for abnormal heat.
Expected outcome: No visible damage, overheating, fluid exposure, or unsafe condition is present.
If damage, heat, smell, or fluid intrusion is found, remove the detector from service and do not continue troubleshooting.
Restart the Detector and Imaging Workstation
Clear temporary communication or software lockup conditions.
Action:
- Power the detector off if possible.
- Restart the DRX-Evolution workstation or acquisition console according to site procedure.
- Power the detector back on after the system is fully available.
- Attempt detector connection again.
Expected outcome: The detector reconnects and appears available for imaging.
If the detector reconnects after restart, document the reset and return the system to service after a functional check.
Check Wireless Network or Detector Communication Status
Determine whether the detector is failing because of a wireless communication problem.
Action:
- Confirm the room’s wireless detector communication hardware is powered.
- Check for disconnected network cables, loose access point power, or damaged antenna hardware if externally visible.
- Look for recent network, room, or IT changes.
- Confirm other room network functions are working, such as worklist or PACS connectivity, if applicable.
Expected outcome: The room network and detector communication path appear active.
Why it matters: A detector may be functional but unavailable if the wireless path or room network is down.
If a room network issue is found, escalate to the appropriate imaging IT, network, or service support team.
Attempt Detector Reselection or Re-Pairing Only If Site-Approved
Use only normal operator-level or Clinical Engineering-approved pairing steps.
Action:
- Open the detector management or detector selection screen if accessible.
- Confirm the detector is listed.
- Select the correct detector if it is available but not active.
- Attempt pairing only if your site allows Clinical Engineering to perform this function without vendor service access.
Expected outcome: The detector pairs or becomes available for imaging.
Do not force service-level pairing, configuration changes, or calibration steps unless trained and authorized.
If the detector pairs successfully and passes a test image or room readiness check, stop.
Test With a Known-Good Compatible Detector or Battery If Available
Isolate whether the problem follows the detector, battery, charger, or room.
Action:
- Place a known-good compatible detector into the room workflow if your site allows detector sharing.
- Test the suspect detector in an approved charger or compatible room if permitted.
- Swap only approved batteries, chargers, or accessories.
Expected outcome:
- If the known-good detector works, the issue likely follows the original detector or its battery.
- If no detector connects, the issue may be with the room system, wireless communication, or configuration.
- If the suspect detector fails everywhere, the detector likely requires repair.
If the issue is isolated clearly, document the result and escalate the failing component.
Check for Recent Drops, Fluid Exposure, or Cleaning Issues
Ask staff whether the detector was recently dropped, cleaned heavily, or exposed to fluid.
Action:
- Inspect the detector bag, cover, charging contacts, and seams.
- Check whether disinfectant residue or moisture is present near contacts or battery areas.
- Confirm the detector was allowed to dry before charging or use.
Expected outcome: No evidence of fluid contamination or handling damage is present.
If fluid exposure or impact damage is suspected, remove the detector from service for repair evaluation.
Perform a Safe Functional Check
After correction, confirm the system is ready before returning it to clinical use.
Action:
- Verify the detector shows connected or ready status.
- Confirm battery level is acceptable.
- Confirm the detector remains connected for several minutes.
- Acquire a test image only if allowed by site procedure and radiation safety policy.
- Confirm images transfer normally to the workstation.
Expected outcome: The DRX-Evolution recognizes the detector, detector status remains stable, and image acquisition is functional.
If the detector passes the functional check, return the system to service.
If the Problem Persists
If the DRX detector still will not connect, charge, or pair after checking battery status, charger power, dock contacts, detector selection, workstation restart, network communication, and known-good accessories, common external causes have been ruled out.
The detector or room communication system should be:
- Removed from service
- Labeled Out of Service
- Sent for repair, vendor service, or bench evaluation
Do not continue repeated pairing attempts, service-level configuration changes, or internal detector repair unless trained and authorized. Knowing when to stop is proper troubleshooting.
Clinical Use Tip
Do not troubleshoot detector connection or charging problems while an active patient exam is waiting on that same room unless the patient is safe and the imaging need is not urgent. Move the patient to another room or use a backup detector first.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Radiology reported the Carestream DRX-Evolution detector would not connect to the room and was not available for imaging."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found the detector battery was fully discharged and the charging dock was not powered due to a loose power connection."
Resolution
What action was taken.
Example:
"Reseated the charger power cord, confirmed charging indicator activity, allowed the detector to charge, verified detector connection at the workstation, and returned the room to service."
Helpful Details to Include (If Known)
- Outlet tested
- Charger or dock indicator light status
- Detector battery level
- Detector ID or asset tag
- Whether the detector was recognized by the workstation
- Whether pairing was attempted
- Any wireless or network messages
- Whether another detector or battery was tested
- Signs of damage, fluid exposure, unusual heat, or odor
- Final detector and room status
Final Thought
DRX detector troubleshooting should move from safety to simple external causes first: battery charge, charger power, dock contact, detector selection, workstation status, and wireless communication. If those checks do not restore normal operation, escalation is appropriate. Clear CCR documentation helps show what was ruled out and prevents repeat troubleshooting from starting over.
That is successful troubleshooting.