On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide helps troubleshoot the COMMUNICATION FAILED error on the GE Healthcare OEC 9900 Series C-Arm. This condition occurs when communication between the workstation and C-Arm is lost long enough for the system watchdog to time out. When this happens, future X-rays are disabled and the system may not be safe or reliable for clinical imaging until the communication fault is cleared and verified.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Remove the C-Arm from patient use if the error appears during setup, startup, positioning, or a clinical procedure.
- Stop attempting X-ray exposure if communication is unreliable or future X-rays are disabled.
- Notify clinical staff that the system should not be used until the communication fault is cleared.
- Use another C-Arm or approved imaging method if imaging is needed immediately.
Verify the Reported Error and Behavior
- Confirm that the displayed message reads COMMUNICATION FAILED.
- Observe when the error appears, such as during bootup, after the workstation starts, after the C-Arm starts, after connecting the workstation to the C-Arm, or intermittently during use.
- Confirm whether future X-rays are disabled after the message appears.
- Document any other startup errors, blank displays, reboot loops, or abnormal system behavior.
Power Cycle the System Correctly
- Power the system off.
- Wait at least 5 seconds.
- Restart the C-Arm and workstation normally.
- Allow the full boot sequence to complete before attempting additional use.
- If the error clears, perform functional checks before returning the device to service.
Check the Workstation-to-C-Arm Interconnect Cable
- Inspect the interconnect cable between the workstation and C-Arm.
- Look for loose connections, bent pins, damaged connector shells, cable strain, cuts, kinks, crushed sections, or poor seating at either end.
- Disconnect and reconnect the cable only if allowed by facility procedure and system condition.
- Confirm that the cable is fully seated and visibly undamaged.
Confirm Both System Sections Are Powered and Booting Normally
- Verify that both the workstation and C-Arm power up normally.
- Check for normal startup screens, expected indicator lights, abnormal boot delays, repeated restarts, blank workstation display, or the C-Arm failing to complete startup.
- Confirm that no unrelated power or boot failure appears before the COMMUNICATION FAILED message.
Check for Startup Sequence or Connection Timing Issues
- Restart the system using the normal facility startup process.
- Avoid unplugging or reconnecting cables while the system is booting unless required by service procedure.
- Confirm that the workstation and C-Arm are allowed to initialize normally before clinical use.
Inspect for External Damage or Recent Movement
- Ask staff whether the system was recently moved, bumped, transported, stored, or cleaned.
- Inspect the workstation, C-Arm base, cable path, and connector areas for physical damage.
- Pay close attention to areas where cable strain, impact, or connector damage could interrupt communication.
Identify Whether the Failure Is Intermittent or Constant
- Observe whether the error appears immediately every time, only after movement, when the cable is flexed, after the system has been powered on for a while, or randomly during use.
- Treat an intermittent issue as a possible cable, connector, or physical connection problem.
- Treat a constant issue as a possible communication path, boot, ARCNET, or software-related failure.
Escalate for Service-Level Communication Troubleshooting
- If power cycling and external cable checks do not resolve the issue, suspect a device-level communication fault.
- Possible deeper causes may include ARCNET communication failure, boot communication problems, corrupted persistent object files, or software-related faults.
- Do not proceed into board-level or software-level repair unless trained and authorized.
If the Problem Persists
If COMMUNICATION FAILED continues after power cycling, checking the workstation-to-C-Arm interconnect cable, confirming both system sections boot normally, ruling out startup sequence issues, and checking for obvious external damage, remove the device from service.
At that point, the likely external causes have been ruled out and the system should be treated as having a device-level communication, ARCNET, boot, or software-related fault.
- Remove the C-Arm from service.
- Label the device Out of Service.
- Send the device for repair, bench evaluation, or qualified service support.
Clinical Use Tip
Never troubleshoot this error on an active patient. Move the patient to a backup C-Arm or approved alternate imaging method first, then troubleshoot the OEC 9900 only after it has been removed from clinical use.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"GE OEC 9900 Series C-Arm displayed COMMUNICATION FAILED. Staff reported communication was lost between the workstation and C-Arm, and future X-rays were disabled."
Cause
What was observed during troubleshooting.
Example:
"COMMUNICATION FAILED error confirmed. System was power cycled, workstation-to-C-Arm interconnect cable was inspected, both system sections were checked for normal startup, and error returned after restart."
Resolution
What action was taken.
Example:
"Powered system off for greater than 5 seconds and restarted. Checked external interconnect cable, connector seating, startup behavior, and visible damage. Error persisted. Removed device from service, labeled Out of Service, and sent for repair evaluation."
Helpful Details to Include (If Known)
- Alarm behavior
- Accessories swapped
- Power behavior
- Environmental factors
- Indicator lights
- Final device status
Final Thought
COMMUNICATION FAILED should be treated as a system communication safety fault, not a simple operator issue. Start with patient safety, confirm the exact message, check power and external connections, then escalate when the error persists. Clear CCR documentation shows whether the failure was corrected externally or requires deeper service evaluation.
That is successful troubleshooting.