On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting coil detection, positioning, ID, or communication issues using external checks before escalation.
Step-by-Step Troubleshooting
Ensure Patient Safety First
If the issue occurs during an active scan or patient setup, stop troubleshooting at the scanner until the patient is safe.
Remove the patient from the bore if coil detection, scan setup, or communication errors prevent safe imaging.
Expected outcome: Patient care continues without relying on a coil or scanner configuration with unresolved communication errors.
Confirm the Reported Coil Issue
Ask MRI staff what error or behavior was observed.
Check whether the problem involves:
- Coil not detected
- Incorrect coil shown
- Coil ID mismatch
- Coil element failure message
- Coil communication error
- Coil position not accepted
- Scan cannot proceed after coil selection
Expected outcome: The issue is clearly identified before parts are swapped or the system is escalated.
Verify the Correct Coil Is Being Used
Confirm the coil matches the selected exam, anatomy, and protocol.
Make sure staff are not using a coil intended for a different body region, table setup, or scanner platform.
Expected outcome: The coil and protocol are compatible.
If the wrong coil or protocol was selected, correct the setup, repeat coil recognition, and stop if resolved.
Check Coil Placement and Patient Positioning
Inspect the physical coil setup.
Confirm the coil is properly seated, aligned, closed, and positioned according to normal clinical use.
Check for obvious misalignment, incomplete latching, excessive cable tension, or coil movement during table positioning.
Expected outcome: The coil is positioned correctly and is not mechanically preventing recognition or scan setup.
Inspect Coil Cable Routing
Check that coil cables are routed cleanly and are not pinched, sharply bent, stretched, twisted, or trapped under the patient, pads, table, or accessories.
Expected outcome: Coil cabling is not under stress and does not interfere with table movement or coil communication.
If cable routing was corrected and the coil is recognized normally, return the system to clinical use after functional verification.
Check Coil Connector Seating
Inspect the external coil connector and scanner/table connection point.
Reseat the coil connector fully and confirm it locks or seats as expected.
Look for bent pins, damaged connector shells, looseness, contamination, cracked strain relief, or signs of liquid exposure.
Expected outcome: The coil connection is secure and free of obvious damage.
Do not force a damaged connector into place.
Power Cycle the Coil Setup Through Normal Workflow
Remove the coil from the setup, wait briefly, reconnect it, and allow the scanner software to detect it again through the normal operator workflow.
Expected outcome: The system recognizes the coil correctly after reconnection.
If the coil ID or communication issue clears, document the reseat and verify the coil can be used successfully.
Try a Known-Good Compatible Coil, If Available
Use another compatible coil for the same scanner and exam type, if available.
Do not substitute an incompatible coil just to bypass the error.
Expected outcome: A known-good coil helps determine whether the issue follows the original coil or remains with the scanner/table connection.
If the known-good coil works, remove the suspect coil from service for evaluation.
Test the Suspect Coil on a Known-Good Setup, If Available
If operationally appropriate and allowed by site process, test the suspect coil on a known-good compatible scanner or table connection.
Expected outcome: The issue either follows the coil or remains isolated to the original scanner setup.
If the same coil fails in multiple setups, suspect coil or coil cable failure.
Check for Table or Docking-Related Issues
Confirm the patient table is docked, latched, and positioned normally.
Check whether the issue appears only after table movement, table docking, or specific table positions.
Expected outcome: The table connection and coil communication path are not being interrupted by poor docking or positioning.
Review Recent Changes
Ask whether the issue began after:
- Coil cleaning
- Coil drop or impact
- Room turnover
- Software update
- Table service
- Protocol change
- New coil installation
- Liquid spill or contrast incident
Expected outcome: Recent events help identify whether the failure is likely accessory-related, workflow-related, or system-related.
Check for Visible Coil Damage
Inspect the coil housing, padding, cable, connector, latches, and strain relief.
Look for cracks, exposed wiring, loose sections, worn labels, fluid residue, or deformation.
Expected outcome: No obvious physical damage is present.
If damage is found, remove the coil from service and do not return it to patient use.
Perform a Controlled Functional Check
With MRI staff assistance, attempt a basic coil recognition and setup check using the affected coil and a known appropriate protocol.
Confirm whether the scanner identifies the coil correctly and allows setup to proceed.
Expected outcome: Coil ID, coil element recognition, and communication are stable during setup.
If the coil is recognized and the issue cannot be repeated, return to service only after documenting the test conditions.
Escalate if Communication Errors Persist
If the coil is correctly positioned, properly connected, externally undamaged, and still fails detection or communication checks, stop external troubleshooting.
Expected outcome: The issue is treated as a possible internal coil, connector, table interface, or system communication fault requiring advanced service.
If the Problem Persists
If the MAGNETOM Sola continues to show coil positioning, coil ID, or coil communication issues after external checks, common setup and accessory causes have been ruled out.
The affected coil or scanner should be:
- Removed from clinical use as appropriate
- Labeled Out of Service
- Evaluated on the bench or escalated to Siemens service
- Kept out of patient use until coil detection and communication are verified
Knowing when to stop is proper troubleshooting. MRI coils and table communication paths are not appropriate for deep internal disassembly during basic Clinical Engineering response.
Clinical Use Tip
Do not troubleshoot coil communication problems on an active patient. Move the patient to a safe state first, especially if the issue prevents scan setup, coil selection, image acquisition, or reliable exam completion. Maintain therapy continuity by moving the patient to a backup device or alternate imaging workflow when needed.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"MRI staff reported that the MAGNETOM Sola would not recognize the selected body coil setup and displayed a coil communication issue during exam preparation."
Cause
What was observed during troubleshooting.
Example:
"External inspection found the coil connector was not fully seated at the table connection point, and the coil ID was not detected until the connector was reseated."
Resolution
What action was taken.
Example:
"Reseated the coil connector, verified proper coil recognition with MRI staff, confirmed scan setup could proceed, and returned the scanner to service."
Helpful Details to Include (If Known)
- Exact coil name or type involved
- Error message displayed
- Alarm behavior
- Accessories swapped
- Power behavior
- Environmental factors
- Indicator lights
- Whether the coil was detected incorrectly or not detected at all
- Whether the issue followed the coil
- Whether a known-good coil worked
- Connector condition
- Cable routing condition
- Table docking status
- Whether the issue occurred before or after table movement
- Any recent coil drop, cleaning, spill, or service event
- Final coil and scanner status
- Final device status
Final Thought
Coil communication issues on an MRI system should be approached logically and cautiously. Start with patient safety, then verify setup, positioning, cable routing, connector seating, and known-good accessories before assuming an internal failure. Clear documentation helps separate workflow issues from true coil or system faults and supports appropriate escalation.
That is successful troubleshooting.