On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting MRI coil recognition, coil connection, coil element dropout, or scan-start failures caused by external coil or setup issues.
Step-by-Step Troubleshooting
Ensure Patient Safety First
If the issue occurs during patient setup or scanning, stop the exam only when clinically safe and follow MRI department workflow.
Remove the patient from the bore or move to a safe position before handling coils, cables, table connections, or accessories.
Expected outcome: The patient is not exposed to unnecessary delays, repositioning risk, or unsafe coil handling.
Confirm the Reported Coil Issue
Ask MRI staff which coil was in use and what symptom occurred.
Common reports may include:
- Coil not detected
- Coil element missing
- Coil element failed
- Coil cannot be selected
- Exam will not start
- Poor signal from one area of the image
- Error appears after patient positioning
Expected outcome: The failure is tied to a specific coil, coil port, exam setup, or scan protocol.
Check Whether the Correct Coil Is Being Used
Verify that the selected coil matches the exam type, body region, patient position, and protocol.
Confirm that the coil is compatible with the MAGNETOM Aera system and not intended for another scanner or platform.
Expected outcome: The coil and exam setup match the intended clinical use.
If the wrong coil was selected or positioned, correct the setup and retest. If this resolves the issue, return the device to service.
Inspect the Coil Exterior
Remove the coil from patient use and visually inspect it in a safe MRI area.
Look for:
- Cracked housing
- Damaged strain relief
- Bent connector pins
- Loose connector shell
- Fluid intrusion
- Burn marks
- Unusual odor
- Damaged labels or missing coil ID markings
Expected outcome: No obvious physical damage is found.
If physical damage, overheating, fluid exposure, or connector damage is found, remove the coil from service and send it for repair evaluation.
Check Coil Connector Seating
Disconnect and reconnect the coil using normal operator-level handling only.
Ensure the connector is fully seated and latched as designed.
Do not force the connector.
Expected outcome: The scanner recognizes the coil after a clean reconnection.
If reseating the connector resolves the issue, perform a basic function check or phantom/QA verification per site process before returning the coil to use.
Inspect the Table or Coil Port Connection Area
Check the table connection interface and coil ports for visible debris, bent contacts, loose hardware, fluid, or signs of wear.
Do not insert tools into the connector or attempt internal port repair.
Expected outcome: The connection area appears clean, dry, and undamaged.
If the table port or connector area appears damaged, remove the affected port or scanner from clinical use as appropriate and escalate for service.
Try a Known-Good Coil on the Same Port
Use a known-good compatible coil and connect it to the same table or system port.
Expected outcome: The known-good coil is recognized normally.
If the known-good coil works, the original coil is more likely the problem.
If the known-good coil also fails on the same port, suspect a table, port, system interface, or software recognition issue.
Try the Suspect Coil on a Known-Good Port or Setup
If the coil design allows connection to another appropriate port or setup, test the suspect coil there.
Expected outcome: The suspect coil is either recognized or fails consistently.
If the coil fails in multiple valid setups, remove the coil from service and send it for repair evaluation.
Check for Coil Element Dropout During QA or Phantom Testing
If the coil is recognized but image quality is poor, perform a controlled phantom or coil QA check according to department workflow.
Look for:
- Missing signal from one coil section
- Shading
- Localized noise
- Intermittent signal loss
- Repeatable artifact tied to the same coil element
Expected outcome: All expected coil elements contribute normally.
If a specific element repeatedly fails, remove the coil from clinical use and document the failed element behavior.
Confirm Protocol and Coil Selection Settings
Review whether the exam card, coil selection, patient orientation, and scan setup are appropriate.
Incorrect coil selection or patient orientation can make a good coil appear unavailable or produce poor signal.
Expected outcome: The system setup matches the physical coil and patient positioning.
If correcting the protocol or coil selection resolves the issue, document the setup correction and return the device to use.
Restart the System Only if Operationally Appropriate
If multiple coils are not recognized or the scanner interface appears stuck, coordinate with MRI staff before restarting the host or scanner software.
Do not interrupt active clinical use without department approval.
Expected outcome: Temporary software recognition faults clear after restart.
If the issue clears after restart, perform a verification scan or QA check before returning to normal use.
Review Error Pattern and Scope
Determine whether the issue affects:
- One coil only
- One coil port only
- One table position only
- Multiple coils
- Multiple exams
- Recognition only
- Image quality only
- Intermittent movement-related failures
Expected outcome: The fault is narrowed to coil, cable/connector, table interface, software recognition, or internal system fault.
Remove Any Suspect Coil from Service
If a coil is intermittently recognized, has failed elements, shows damage, or causes repeatable artifacts, label it Out of Service.
Do not return an intermittent MRI coil to clinical use based only on one successful reconnect.
Expected outcome: Unreliable coil performance is prevented from affecting patient imaging.
If the Problem Persists
If basic coil setup, connector seating, port checks, protocol selection, and known-good coil comparison do not resolve the issue, common external causes have been ruled out.
The problem may involve the coil electronics, coil ID circuit, table interface, receiver chain, system software, or internal RF pathway.
The affected coil or scanner should be:
- Removed from service as appropriate
- Labeled Out of Service
- Escalated for Siemens service, repair, or bench evaluation
- Verified with QA before return to clinical use
Knowing when to stop is proper troubleshooting. MRI coil and RF-chain faults should not be pushed into repeated clinical use when recognition or signal reliability is uncertain.
Clinical Use Tip
Do not troubleshoot MRI coils on an active patient unless the situation is controlled and clinically safe. Move the patient away from the affected setup first, then check coil connections, ports, and recognition status. A coil that is intermittently recognized should be treated as unreliable until verified.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"MRI staff reported that the Siemens MAGNETOM Aera head/neck coil was not recognized during patient setup and the exam could not proceed."
Cause
What was observed during troubleshooting.
Example:
"Troubleshooting found the coil failed recognition on a known-good table port while another compatible coil was recognized normally."
Resolution
What action was taken.
Example:
"Removed the suspect coil from service, labeled it Out of Service, notified MRI staff, and escalated the coil for repair evaluation."
Helpful Details to Include (If Known)
- Coil name and serial number
- Exam type being performed
- Exact error message
- Whether the issue was recognition, element dropout, or image artifact
- Whether the coil was reseated
- Whether a known-good coil was tested
- Whether the issue followed the coil or stayed with the port
- Table port or connection used
- Any visible coil or connector damage
- Phantom or QA result, if performed
- Whether the issue was intermittent or repeatable
- Alarm behavior
- Accessories swapped
- Power behavior
- Environmental factors
- Indicator lights
- Final device or coil status
Final Thought
MRI coil troubleshooting should move from safe patient handling to simple external checks before suspecting internal RF or system faults. A logical comparison between the suspect coil, a known-good coil, and the connection port helps prevent unnecessary scanner downtime while still protecting patient safety and image quality. Clear CCR documentation also helps service teams identify whether the issue follows the coil, the port, or the scanner.
That is successful troubleshooting.