On this page
Asset Type
Fluoroscopy / Interventional System
Manufacturer
Model
What This Guide Helps With
Identifies external causes of CAN bus or system interconnect faults, including cabling, power instability, and module communication loss affecting system operation.
Step-by-Step Troubleshooting
1. Ensure Patient Safety First
Confirm no patient is on the table and the system is not in use.
Why: Prevents unintended motion, exposure, or system instability during troubleshooting.
2. Observe Error Messages and Affected Subsystems
Note which components are reporting faults (table, detector, generator, console).
Check for:
- Multiple subsystem failures
- Intermittent vs constant faults
Expected Outcome: Helps determine if issue is isolated or system-wide communication failure.
3. Perform a Controlled System Restart
Shut down the system using proper procedure, wait 2–3 minutes, then power back on.
Expected Outcome: Temporary communication faults may clear after reinitialization.
Why: CAN bus faults are often triggered by startup sync issues or transient errors.
4. Verify Power Stability to All System Components
Check power to:
- Workstation
- System cabinets
- Generator cabinet
- Table
Inspect breakers, power strips, and UPS (if present).
Expected Outcome: All components powered with stable indicators.
Why: Communication faults commonly occur when one subsystem loses power or boots incorrectly.
5. Inspect External Communication and Interconnect Cables
Check all visible cables between major system components:
- Cabinet-to-cabinet connections
- Table interface cables
- Detector connections
Look for:
- Loose or partially seated connectors
- Damaged or pinched cables
Reseat connections where accessible.
Expected Outcome: Restoring proper connections may re-establish communication.
6. Check for Recent Movement or Environmental Changes
Ask if:
- Equipment was recently moved
- Cleaning or construction occurred
- Cables may have been disturbed
Expected Outcome: Identifies external cause of disconnected or stressed cabling.
7. Verify No Peripheral or External Device Interference
Disconnect non-essential external devices (USB, network accessories, etc.).
Expected Outcome: Eliminates possibility of interference or bus overload from external devices.
8. Check Cabinet Doors and Interlocks
Ensure all system cabinet doors and panels are fully closed and latched.
Expected Outcome: Closed interlocks allow normal system communication.
Why: Some systems inhibit communication when safety interlocks are open.
9. Observe System Status Indicators and LEDs
Check for abnormal indicator lights on system cabinets or modules.
Expected Outcome: Identifies which module may not be communicating.
Why: CAN bus faults often originate from one non-responsive node.
10. Attempt Subsystem Isolation (If Applicable)
If a specific subsystem is identified (e.g., table or detector), power cycle only that component if safely accessible.
Expected Outcome: Isolates fault to a specific module if communication is restored or remains failed.
If the Problem Persists
If all external causes have been ruled out, the issue is likely due to an internal communication failure (CAN bus node, controller board, or internal harness).
Remove the system from service, label it Out of Service, and escalate for vendor service or advanced bench evaluation.
Knowing when to stop prevents unnecessary risk and protects system integrity.
Clinical Use Tip
Never troubleshoot communication faults during an active procedure. Move the patient to a functioning system before beginning any diagnostic steps.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"System displaying CAN bus communication errors with loss of multiple subsystem control."
Cause
What was observed during troubleshooting.
Example:
"Loose interconnect cable between system cabinets causing intermittent communication loss."
Resolution
What action was taken.
Example:
"Reseated and secured interconnect cables; system rebooted and communication restored."
Helpful Details to Include (If Known)
- Specific error codes displayed
- Subsystems affected (table, detector, generator, etc.)
- Power status of all components
- Cable condition and reseating actions
- Indicator light behavior on cabinets
- Any recent movement or environmental changes
- Final system operational status
Final Thought
CAN bus faults often appear complex but are frequently caused by simple external issues like power loss or loose connections. A structured, step-by-step approach ensures patient safety while efficiently isolating the problem. Escalating at the right time is just as important as resolving the issue.
That is successful troubleshooting.