On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Addresses unresponsive user controls caused by startup state, loose connections, contamination, damaged peripherals, software freezes, or external accessory problems.
Step-by-Step Troubleshooting
1. Protect the Patient and Stop Using Unreliable Controls
Do not continue a clinical procedure using controls that are frozen, intermittent, or generating unintended commands.
If the affected interface is required for imaging, movement, radiation control, or patient-related workflow, move the procedure to another verified system when necessary.
Expected outcome: Patient care does not depend on unreliable system controls.
2. Identify the Exact Interface Failure
Determine whether the problem affects:
- Touchscreen only.
- Keyboard only.
- A specific control panel.
- Individual buttons.
- All controls.
- One workstation.
- Controls only after startup.
- Controls after a system or software freeze.
Confirm whether any alternate control interface still works.
Expected outcome: The failure is isolated to one peripheral, one interface, or the complete system.
3. Inspect the Affected Control Surface
Check the touchscreen, keyboard, or control panel for:
- Fluid contamination.
- Adhesive residue.
- Dirt or debris.
- Physical damage.
- Cracked surfaces.
- Stuck keys.
- Objects resting against controls.
Clean only with approved methods and remove anything causing unintended contact.
Expected outcome: The control surface is clean, intact, and mechanically unobstructed. If normal response returns, verify operation and stop.
4. Verify External Peripheral Connections
Inspect accessible connectors and cables for the affected keyboard, control module, monitor, or related peripheral.
Look for:
- Loose connectors.
- Bent or damaged connector shells.
- Pinched cables.
- Damaged strain relief.
- Connections disturbed by equipment relocation.
Reseat accessible connections when permitted.
Expected outcome: The peripheral is securely connected and recognized.
5. Check for a Single Failed Peripheral
If the problem is limited to a keyboard or another externally replaceable approved control accessory, compare with a known-good compatible accessory when available.
Do not substitute unapproved consumer peripherals unless explicitly allowed for the system.
Expected outcome: A defective external peripheral is isolated or ruled out.
6. Verify the System Is Not Still Initializing
If controls are unresponsive during startup, allow normal initialization to finish.
Determine whether the interface becomes functional once the complete system is ready.
Expected outcome: Controls respond normally after initialization. If so, no further troubleshooting is required beyond verification.
7. Check for Software Freeze Versus Hardware Failure
Observe whether:
- The pointer or on-screen indicators move.
- Other controls still respond.
- Images or system status continue updating.
- Only one application area is frozen.
- The entire system is unresponsive.
Avoid rapidly pressing multiple controls, which can make the condition harder to assess.
Expected outcome: The issue is characterized as a local peripheral problem or broader system freeze.
8. Perform One Controlled Restart
If no physical problem is found and the system appears frozen, use the normal controlled shutdown process if possible.
Restart the system and allow complete initialization.
Avoid repeated forced power cycles.
Expected outcome: The touchscreen, keyboard, and control interfaces initialize and respond normally.
9. Perform Full Control Verification
Before returning the Cios Spin to service, test the affected interface and other safety-relevant controls.
Verify:
- Touch commands register correctly.
- Keyboard input is accurate.
- Buttons do not stick or double-trigger.
- Controls remain responsive.
- No unintended commands occur.
- Imaging and positioning workflows can be completed normally.
Expected outcome: All required controls operate reliably and consistently. Troubleshooting can stop.
10. Escalate Persistent or Intermittent Control Failure
Remove the system from service if:
- Controls remain frozen.
- Touch input is inaccurate or erratic.
- Buttons trigger intermittently.
- Multiple interfaces stop responding.
- The system repeatedly freezes.
- A known-good external peripheral does not correct the issue.
Do not disassemble touch displays, control panels, internal computers, or interface boards without qualified service authorization.
Expected outcome: An unreliable control interface is prevented from returning to clinical use.
If the Problem Persists
After contamination, physical obstruction, accessible cables, external peripherals, startup state, and controlled restart have been ruled out, remaining causes may involve touchscreen electronics, control interfaces, internal cabling, embedded computing, application software, or service-level configuration.
The Cios Spin should be:
- Removed from service.
- Labeled Out of Service.
- Sent for repair or bench/service evaluation.
- Evaluated using Siemens Healthineers documentation and approved test equipment.
- Repaired or configured only by qualified personnel.
Complete control-interface, movement, imaging, exposure-control, and other applicable functional verification before return to clinical service.
Knowing when to stop external troubleshooting is proper troubleshooting.
Clinical Use Tip
Intermittent controls are not acceptable simply because they respond after repeated attempts; verify consistent response before returning the C-arm to use.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Staff reported the Cios Spin keyboard stopped responding while the touchscreen continued to function."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found the external keyboard connection partially disengaged at the workstation."
Resolution
What action was taken.
Example:
"The connection was reseated and secured, keyboard entry and system controls were repeatedly tested, and normal operation was verified."
Helpful Details to Include (If Known)
- Interface affected.
- Specific keys or controls affected.
- Touchscreen contamination.
- Physical damage.
- Cable and connector condition.
- Known-good peripheral test.
- Other controls still functional.
- Startup versus mid-use failure.
- Restart results.
- Intermittent behavior.
- Final functional verification.
- Final device status.
Final Thought
Protect the patient from unreliable control behavior, eliminate simple physical and connection causes first, verify consistent response after correction, and escalate persistent interface failures rather than working around them.
That is successful troubleshooting.