On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting dockable table, eDrive, docking, movement, or table communication faults before escalating for MRI service repair.
Step-by-Step Troubleshooting
Ensure Patient Safety First
If the table fault occurs with a patient on the table, stop table movement and follow the site’s MRI patient safety procedure.
Remove the patient from the scanner only when it is safe to do so and with clinical/MRI staff assistance.
Expected outcome: Patient safety is protected before troubleshooting begins.
Confirm the Reported Fault
Ask MRI staff what happened and when the fault appeared.
Check whether the issue involves:
- Table will not dock
- Table will not undock
- eDrive does not respond
- Table movement is slow, interrupted, or unavailable
- Scanner does not recognize the table
- Error appears at the console during table positioning
Expected outcome: The failure mode is clearly identified before further checks.
Check for Obstructions Around the Table and Docking Area
Inspect the table base, floor path, docking rails, table lock area, and scanner entrance for physical obstructions.
Look for linens, pads, coils, straps, patient positioning aids, cables, or floor debris interfering with docking or movement.
Expected outcome: Table path and docking area are clear.
If obstruction removal resolves the issue, return the system to service after confirming normal table operation and stop troubleshooting.
Verify the Table Is Properly Aligned for Docking
Confirm the table is straight, centered, and positioned correctly at the magnet docking point.
A dockable MRI table may fail to communicate or lock if it is mechanically misaligned.
Expected outcome: Table docks smoothly and is recognized by the system.
If proper alignment resolves the fault, document and stop.
Inspect Docking Contacts and External Connection Points
Visually inspect the table docking interface for obvious damage, contamination, bent pins, loose covers, or foreign material.
Do not probe internal contacts or disassemble the docking assembly.
Expected outcome: Docking interface appears clean, intact, and mechanically normal.
If contamination is safely removable using approved site practice, clean externally and retest.
Check Table Locking and Latching Behavior
Confirm the table physically locks into the docked position.
Listen and feel for normal engagement without forcing the table.
Expected outcome: Docking latch engages normally and the console recognizes the docked table.
If the latch does not engage, do not force the table. Remove it from service for repair evaluation.
Verify eDrive Controls Are Not Damaged or Stuck
Inspect the eDrive controls, handles, buttons, and table movement controls for damage, fluid intrusion, stuck switches, or abnormal resistance.
Expected outcome: Controls move normally and are not physically damaged.
If a control is stuck, damaged, or contaminated, remove the table from service.
Check Emergency Stop and Table Stop Conditions
Confirm no emergency stop, table stop, or safety stop has been activated.
Reset only according to approved site procedure and MRI department workflow.
Expected outcome: Safety stop condition clears and table movement becomes available.
If the fault clears after resetting a stop condition, verify normal movement before returning to service.
Check Console Messages and System Status
Review the MRI operator console for table, docking, eDrive, communication, or positioning messages.
Record the exact wording of the error.
Expected outcome: Error message is documented and helps determine whether the issue is table-side, docking-side, or system communication related.
Power Cycle Only When Clinically Appropriate
If MRI staff confirms the scanner is not in use and no exam is active, perform an approved system/table restart workflow according to site procedure.
Do not interrupt an active scan or patient exam.
Expected outcome: Temporary communication faults may clear after a controlled restart.
If the fault clears, verify docking, undocking, table movement, and console recognition before return to service.
Try a Controlled Dock / Undock Test
With no patient present, test normal docking and undocking.
Confirm:
- Table moves smoothly
- eDrive responds normally
- Docking latch engages
- Console recognizes table position
- No new error appears
Expected outcome: Table communication and movement functions operate normally.
If the table fails during testing, remove it from service.
Check for Recent Events or Environmental Causes
Ask whether the issue began after:
- Table impact
- Moving the table between rooms
- Coil or accessory change
- Floor cleaning
- Fluid spill
- Power interruption
- Recent service activity
Expected outcome: Recent events may explain an external or mechanical cause.
Do Not Continue Use if Table Position Is Unreliable
If the table position, docking state, or communication status cannot be trusted, do not release the system for patient scanning.
Expected outcome: MRI staff are not relying on a table that may fail during positioning or patient handling.
If the Problem Persists
If the dockable table, eDrive, or table communication fault remains after external checks, common causes have been ruled out.
The issue may involve the docking interface, table control electronics, position sensing, communication cabling, eDrive control assembly, or scanner-side table interface.
The device should be:
- Removed from service
- Labeled Out of Service
- Reported to MRI service support or Siemens Healthineers service
- Sent for repair or formal bench/system evaluation as appropriate
Knowing when to stop is proper troubleshooting. Do not force table movement, bypass safety interlocks, or continue clinical use when table position or communication is unreliable.
Clinical Use Tip
Do not troubleshoot table movement or docking faults with a patient on the table unless the immediate goal is safe patient removal. Move the patient to a backup device or safe alternate workflow first, protect therapy continuity, and once the patient is safe, perform troubleshooting with the table unloaded and MRI staff present.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"MRI staff reported the MAGNETOM Vida dockable table would not dock and the console displayed a table communication fault."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found no obstruction in the table path, but the table was not consistently recognized after repeated dock/undock testing."
Resolution
What action was taken.
Example:
"Removed the MRI system/table from service, labeled it Out of Service, documented the console error, and escalated to Siemens service for table communication evaluation."
Helpful Details to Include (If Known)
- Exact console error message
- Whether the table failed to dock, undock, move, or communicate
- Whether eDrive controls responded
- Whether the table was loaded or unloaded
- Whether emergency stop or table stop was active
- Docking latch behavior
- Visible damage to docking contacts or table base
- Recent table impact, cleaning, spill, or power interruption
- Whether a restart changed the fault
- Alarm behavior
- Accessories swapped
- Power behavior
- Environmental factors
- Indicator lights
- Final device status
Final Thought
MRI table faults should be handled carefully because table position, docking status, and patient movement are directly tied to patient safety. Start with simple external checks, verify the fault without forcing movement, and escalate when table communication or position feedback cannot be trusted. Clear CCR documentation helps MRI service identify the failure quickly and supports safe return-to-service decisions.
That is successful troubleshooting.