On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Startup failure, frozen boot screen, incomplete initialization, power issues, or software hang conditions on a MOBILETT Mira mobile X-ray system.
Step-by-Step Troubleshooting
Ensure Patient Safety First
Remove the MOBILETT Mira from clinical use if it will not fully boot or freezes during startup.
Action:
- Use another mobile X-ray unit for patient imaging.
- Do not attempt patient exams with a system that has not completed startup, self-checks, or normal readiness checks.
Expected outcome: Patient imaging is transferred to a known-working unit.
Why it matters: A mobile X-ray system that freezes during startup may not be able to complete exposure control, image acquisition, safety interlock checks, or system communication checks.
If this resolves the clinical need, continue troubleshooting only after the unit is away from patient care.
Verify the Reported Startup Behavior
Confirm exactly what the unit is doing before assuming a failed computer, battery, or generator problem.
Action:
Power the unit on and observe the startup sequence.
Document whether the issue is:
- No power at all
- Display remains blank
- System begins booting then freezes
- Siemens logo or startup screen remains displayed
- Touchscreen or workstation does not respond
- Error message appears during startup
- Unit shuts down or restarts by itself
- Boot issue only happens on battery power
- Boot issue only happens while plugged into AC power
Expected outcome: The failure mode is clearly identified and can be compared against power, battery, display, software, or internal system causes.
If the unit boots normally after a restart and no errors return, perform a functional check before returning it to service.
Check for Obvious Physical or Environmental Issues
Look for external conditions that could prevent safe startup.
Action:
Inspect the unit for:
- Impact damage
- Loose panels
- Damaged power cord
- Damaged plug
- Liquid intrusion
- Signs of overheating
- Burning smell
- Unusual fan noise
- Blocked vents
- Debris around the base or workstation area
Expected outcome: No obvious unsafe condition is present.
If there is liquid intrusion, burning smell, unusual heat, smoke, or visible electrical damage, stop troubleshooting, remove the unit from service, label it Out of Service, and send it for repair evaluation.
Verify AC Power Source
A poor outlet or weak AC connection can cause startup failure, charging problems, or unstable boot behavior.
Action:
- Plug the MOBILETT Mira into a known-good hospital-grade outlet.
- Confirm the outlet has power using an outlet tester or another known-working device, according to facility policy.
- Check that the power cord is fully seated at the wall and at the unit, if externally accessible.
- Avoid power strips or questionable extension cords.
Expected outcome: The unit receives stable AC power.
If the system boots normally on a known-good outlet, document the original outlet issue and notify facilities or the appropriate department.
Inspect the Power Cord and Plug
A damaged cord may allow partial power, intermittent charging, or unstable startup.
Action:
Inspect the AC cord for:
- Cuts
- Crushed insulation
- Bent plug blades
- Loose strain relief
- Signs of heat damage
- Intermittent connection when gently moved
Expected outcome: Cord and plug are intact and safe to use.
If the cord or plug is damaged, remove the unit from service until the cord issue is corrected and electrical safety can be verified.
Allow the System to Charge Before Retesting
If the battery is deeply discharged, the unit may not boot properly or may freeze during startup.
Action:
- Connect the MOBILETT Mira to AC power.
- Allow the unit to charge for a reasonable period according to facility practice.
- Observe charging indicators or power status indicators.
- After charging, attempt startup again.
Expected outcome: The unit powers on and completes startup normally.
If the unit boots only after charging, document battery condition, run time concerns, and whether the issue repeats.
If the unit still will not boot while connected to known-good AC power, continue troubleshooting.
Compare Startup on AC Power Versus Battery Power
Separating AC and battery behavior helps narrow the cause.
Action:
- Attempt startup while connected to AC power.
- Then, if safe and the battery has sufficient charge, attempt startup on battery power.
- Observe whether the freeze or failure happens in one condition or both.
Expected outcome:
- Boots on AC but not battery: suspect low battery, failed battery pack, charging issue, or battery communication issue.
- Boots on battery but not AC: suspect AC input, charger, power cord, or power supply path.
- Fails on both: suspect internal power, workstation, software, control system, or communication issue.
If the issue is isolated to battery or charging behavior, document that clearly for repair follow-up.
Perform a Controlled Power Cycle
A temporary software hang may clear after a controlled restart.
Action:
- Shut the unit down using the normal shutdown method if the controls respond.
- If the system is frozen and normal shutdown is not possible, follow facility-approved power-down practice for this model.
- Wait long enough for the system to fully power down.
- Reconnect AC power and restart the unit.
Expected outcome: The system completes startup without freezing.
If the unit starts normally, continue with a functional check before returning it to service.
If the startup freeze returns, continue troubleshooting.
Check Display and User Interface Response
A startup issue may actually be a display, touchscreen, or workstation interface issue.
Action:
Observe whether the unit appears powered even if the screen is blank or frozen.
Check for:
- Power indicator lights
- Fan activity
- Drive or system sounds
- Backlight on the display
- Touchscreen response
- Keyboard, mouse, or control panel response, if applicable
- Any external monitor output, if supported by facility process
Expected outcome: Determine whether the entire system is failing to boot or only the user interface is not responding.
If the unit appears to power normally but the display remains blank or frozen, remove it from service and send for repair evaluation.
Check for Startup Error Messages
Startup faults may point toward a failed subsystem, safety interlock, communication issue, detector problem, generator fault, or workstation error.
Action:
- Record the exact displayed message.
- Do not paraphrase the error.
Note when it appears:
- Immediately after power-on
- During system initialization
- During workstation startup
- During detector connection
- During generator readiness
- After user login
Expected outcome: The exact fault information is captured for repair, vendor support, or service history review.
If the message identifies a specific subsystem, troubleshoot only external and safe items related to that subsystem before escalating.
Remove Nonessential External Accessories
A connected accessory or peripheral may cause startup delay, communication timeout, or software hang.
Action:
Disconnect nonessential external accessories, if safe and allowed by local procedure.
Check items such as:
- USB devices
- External keyboard or mouse
- Network cable, if connected
- Barcode scanner
- External storage device
- Nonessential detector accessories
Restart the system.
Expected outcome: The unit boots normally without the accessory connected.
If removing an accessory allows normal boot, inspect or replace the accessory and document the finding.
If the problem persists, continue troubleshooting.
Verify Detector and System Communication State
Some mobile X-ray systems may delay or hang during startup if detector communication, registration, or wireless connection fails.
Action:
- Check whether the detector is installed, charged, and properly seated or stored.
- Verify that the detector battery is not depleted.
- Confirm that any detector compartment, latch, or docking connection appears normal.
- Restart the unit and observe whether startup freezes during detector initialization.
Expected outcome: Detector-related startup delay or communication failure is either ruled out or identified.
If the unit boots after removing or reseating a detector according to facility procedure, document the detector serial number and behavior.
Check Network Conditions if Startup Freezes During Login or Worklist Loading
A unit may appear frozen if it is waiting for network, user authentication, worklist, or PACS communication.
Action:
Determine whether the freeze occurs before or after the operating software loads.
If it freezes during login, worklist loading, or network connection:
- Check wireless signal availability.
- Confirm the correct network profile is being used.
- Compare with other mobile imaging units in the same area.
- Try booting in an area with known-good wireless coverage.
- Check whether other devices are having PACS, RIS, worklist, or network issues.
Expected outcome: Network-related delay is distinguished from a true boot failure.
If the system boots normally in a known-good wireless area, document the network location and notify the appropriate IT/PACS support team.
Check for Repeated Freezing at the Same Startup Point
A consistent freeze point usually indicates a repeatable system, software, storage, communication, or subsystem initialization problem.
Action:
Restart the system and observe whether it freezes at the same screen, message, or startup percentage.
Record:
- Screen text
- Error message
- Time from power-on to freeze
- Whether fans or indicators remain active
- Whether the touchscreen responds
- Whether the issue changes on AC versus battery
Expected outcome: A repeatable symptom pattern is documented for repair escalation.
If the freeze happens at the same point every time, stop repeated restarts and escalate.
Perform Basic Functional Check if Startup Completes
If the unit boots successfully after troubleshooting, verify that it is safe before returning it to service.
Action:
Confirm:
- System reaches normal ready state
- Touchscreen responds
- User login works
- Battery status is acceptable
- Detector is recognized
- Network/worklist connection works, if applicable
- No active faults remain
- Drive/brake functions are normal
- Exposure readiness checks pass according to facility policy
Expected outcome: The system is confirmed ready for clinical use.
If any readiness check fails, remove the unit from service.
If the Problem Persists
If the MOBILETT Mira still will not boot, repeatedly freezes, shuts down during startup, displays persistent startup errors, or only operates under limited power conditions, common external causes have been ruled out.
The device should be:
- Removed from service
- Labeled Out of Service
- Sent for repair or bench evaluation
Possible internal causes may include power supply failure, battery/charger faults, workstation computer failure, storage or software corruption, internal communication failure, generator initialization fault, display/control failure, or system controller problems.
Knowing when to stop is proper troubleshooting. Repeated power cycling without progress can waste time, risk further system instability, and delay patient care.
Clinical Use Tip
Do not troubleshoot a frozen or non-booting mobile X-ray system while it is needed for an active patient exam. Move the exam to another unit first, then troubleshoot the MOBILETT Mira only when it is safe and removed from patient care.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported the Siemens MOBILETT Mira would not complete startup and remained frozen on the boot screen."
Cause
What was observed during troubleshooting.
Example:
"Verified the unit froze during system initialization on both AC power and battery after testing a known-good outlet and checking the power cord."
Resolution
What action was taken.
Example:
"Removed the unit from service, labeled it Out of Service, documented the startup freeze behavior, and sent it for repair evaluation."
Helpful Details to Include (If Known)
- Whether the outlet was tested
- Whether the unit was on AC power, battery power, or both
- Battery charge level or charging indicator behavior
- Exact startup screen or error message
- Whether the display was blank, frozen, or responsive
- Whether fans, lights, or sounds were present
- Whether the issue occurred before or after user login
- Whether detector communication appeared during startup
- Whether network/worklist loading was involved
- Any unusual heat, smell, noise, or shutdown behavior
- Final device status
Final Thought
A MOBILETT Mira that will not boot or freezes during startup should be approached logically: protect the patient first, verify power and external conditions, separate AC from battery behavior, check accessories and network-related delays, and then escalate when the issue remains repeatable. Clear CCR documentation helps repair teams reproduce the failure and prevents unsafe return to service.
That is successful troubleshooting.