On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting RF coil overload, coil not recognized, coil element dropout, or coil communication faults before escalating to MRI service.
Step-by-Step Troubleshooting
Ensure Patient Safety First
If the coil fault occurs during patient setup or scanning, stop the exam only when it is safe to do so.
Remove the patient from the scanner before troubleshooting coils, table connectors, or RF accessories.
Expected outcome: The patient is safe, and troubleshooting is performed without risk of patient injury or repeat exposure to a known equipment fault.
Confirm the Exact Coil Fault
Review the message shown at the MRI host or operator console.
Identify whether the issue is:
- RF coil overload
- Coil not recognized
- Coil ID error
- Coil element dropout
- Coil communication failure
- Fault only with one specific coil or scan protocol
Expected outcome: The failure pattern is understood before parts are swapped or the issue is escalated.
Verify the Correct Coil Is Selected and Properly Positioned
Confirm the coil being used matches the anatomy and selected exam.
Check that the coil is seated correctly around the patient area and is not twisted, folded, pinched, or placed incorrectly.
Expected outcome: The system recognizes the intended coil and the error clears.
If this resolves the issue, document the positioning correction and stop.
Check for Obvious Coil Cable or Connector Problems
Inspect the coil cable, connector shell, strain relief, and visible pins or contact areas.
Look for:
- Bent or damaged connector pins
- Cracked connector housing
- Loose strain relief
- Cable kinks or compression damage
- Fluid contamination
- Signs of overheating or odor
Expected outcome: No visible damage or contamination is present.
If damage, fluid intrusion, burning smell, or heat is found, remove the coil from service and escalate.
Reseat the Coil Connection
Disconnect and reconnect the RF coil at the appropriate table or interface connection point.
Ensure the connector is fully seated and latched if applicable.
Expected outcome: A loose or partially seated coil connection is corrected, and the system recognizes the coil.
If this resolves the issue, perform a functional check before returning the coil to service.
Test with a Known-Good Compatible Coil
Use a known-good coil that is compatible with the Skyra and the same exam type, when available.
Do not force connectors or use incompatible coils.
Expected outcome:
- If the known-good coil works, the original coil is suspect.
- If the known-good coil also fails, the issue may involve the table interface, coil port, RF chain, or system communication.
Test the Suspect Coil on Another Compatible Connection or Setup
If safe and available, try the suspect coil on another compatible port, table position, or approved configuration.
Expected outcome:
- If the coil fails in multiple valid setups, the coil is likely faulty.
- If the fault follows one table connector or interface location, the system-side connection may be suspect.
Check for Coil Overload Conditions
For RF coil overload messages, confirm the patient setup and protocol are appropriate.
Check for:
- Incorrect coil selection
- Patient positioned too close to the coil housing or cable path
- Coil cable looped or routed improperly
- Excessive SAR protocol selection
- Metallic objects, ECG leads, monitoring cables, or conductive loops near the RF field
- Coil padding or accessories placed incorrectly
Expected outcome: External setup conditions that can contribute to RF overload are corrected.
If the warning clears after correcting setup, repeat only an appropriate safety-verified test before returning to clinical use.
Inspect Table Coil Interfaces and Docking Area
With the patient removed and the system safe to access, inspect the table coil connection area.
Look for:
- Debris in connector areas
- Damaged contacts
- Loose table interface panels
- Evidence of fluid contamination
- Table positioning or docking issues that may affect communication
Expected outcome: No visible system-side connector issue is found.
If contamination, damage, or table interface abnormality is found, remove the affected setup from service and escalate.
Check Whether the Fault Is Protocol-Specific
Ask the technologist whether the issue occurs:
- On every sequence
- Only on high-SAR sequences
- Only on a specific anatomy protocol
- Only with one patient setup
- Only after the coil has been used for a period of time
Expected outcome: A repeatable pattern is identified.
If only one protocol causes overload warnings, involve MRI applications support or Siemens service before repeated clinical use.
Power Cycle Only When Appropriate
If the coil is properly connected, no damage is seen, and the issue appears to be a temporary communication fault, perform a controlled system restart according to site procedure.
Do not repeatedly reboot as a substitute for troubleshooting a recurring coil fault.
Expected outcome: A temporary communication fault clears and does not return during verification.
Perform a Verification Scan or Approved QA Check
After any correction, perform an approved coil check, phantom scan, or site-specific MRI QA test.
Confirm:
- Coil is recognized
- Expected coil elements are active
- No overload warning appears
- Image quality is acceptable
- No abnormal heat, odor, or cable movement is present
Expected outcome: The coil and system pass verification before being returned to clinical service.
If the Problem Persists
If the RF coil overload, recognition, or communication fault continues after checking setup, coil positioning, connectors, cable condition, compatible coils, table interfaces, and protocol behavior, common external causes have been ruled out.
The affected coil, table interface, or MRI system should be removed from service as appropriate, labeled Out of Service, and sent for Siemens service evaluation or qualified bench/system troubleshooting.
Knowing when to stop is proper troubleshooting. MRI RF coil faults can involve patient safety risk, image quality risk, RF chain issues, or internal communication failures that should not be worked around.
Clinical Use Tip
Do not troubleshoot RF coils while a patient is inside the bore unless the action is limited to safe operator-level positioning. Remove the patient first before disconnecting coils, inspecting cables, or changing coil configurations.
Move the patient to a backup device first when continued imaging or therapy continuity is required.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"MRI technologist reported that the Siemens MAGNETOM Skyra displayed a coil communication fault and would not recognize the selected body array coil."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found the coil connector was not fully seated at the table interface; no visible cable damage, contamination, heat, or connector damage was observed."
Resolution
What action was taken.
Example:
"Reseated the coil connector, verified proper coil recognition, completed an approved test scan without recurrence, and returned the coil/system to service."
Helpful Details to Include (If Known)
- Exact coil fault message displayed
- Coil name and serial number if available
- Exam type or protocol being used
- Whether fault was overload, recognition, element dropout, or communication related
- Whether the issue followed the coil or stayed with the table/interface
- Coil connector and cable condition
- Table interface condition
- Whether another compatible coil was tested
- Whether abnormal heat, smell, fluid, or visible damage was present
- Whether a phantom, QA, or verification scan passed
- Final device and coil status
Final Thought
MRI coil troubleshooting should stay patient-safety focused and logic-based. Start with setup, coil selection, cable routing, connector seating, and visible damage before suspecting deeper RF or system faults. When a fault repeats or involves overload, heat, damage, or unreliable recognition, removing the coil or system from service is the safest and most professional decision.
That is successful troubleshooting.