On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Use when the system has no power, shuts down during startup, or fails to reach the normal imaging interface.
Step-by-Step Troubleshooting
1. Protect the Patient and Maintain Clinical Coverage
Remove the Resona I9 from active patient use if it cannot start reliably. Move the examination to another verified ultrasound system when patient care cannot be delayed. Do not repeatedly restart unreliable equipment while a patient depends on it.
Expected outcome: Patient care continues on functional equipment and the affected system is available for controlled troubleshooting.
2. Confirm the Reported Startup Condition
Ask staff exactly what occurred: no response at all, brief power then shutdown, startup stopping at a particular screen, repeated restart, or inability to reach the imaging application. Attempt one controlled startup if safe and observe indicators, display activity, sounds, and any displayed message.
Expected outcome: The failure is reproduced or the system completes startup normally. If startup completes repeatedly without abnormal behavior, continue with functional verification before returning the unit to service.
3. Verify AC Power
Confirm the power cord is fully seated at the system and approved facility receptacle. Inspect the cord, plug, and accessible power-entry area for damage, looseness, overheating, or contamination. Verify the receptacle using an approved electrical test method or known-good powered device according to facility practice.
Expected outcome: Reliable AC power is present and the external power connection is secure. If restoring the power connection corrects the problem and startup remains normal, troubleshooting can stop after final verification.
4. Check External Power-Related Conditions
Verify that no external power strip, disconnected isolation source, switched receptacle, or tripped facility circuit is interrupting power. If the system has been moved, determine whether the problem began after relocation.
Expected outcome: No external power-distribution condition is preventing startup.
5. Inspect Connected Accessories and External Devices
Visually inspect externally connected USB devices, network cables, peripheral equipment, and probes for obvious damage or abnormal connections. If a newly attached nonessential peripheral coincides with the failure, disconnect it only when permitted and retry startup without changing internal configuration.
Expected outcome: Startup is not being blocked by an external peripheral or damaged accessory. If removal of a nonessential external device restores reliable operation, document the finding and verify the system before use.
6. Perform One Controlled Restart
If the system is responsive enough to shut down normally, use the normal shutdown process before restarting. Avoid repeated forced power cycling. If the system is completely unresponsive, follow approved facility and manufacturer service guidance for power removal rather than repeatedly interrupting power.
Expected outcome: The system reaches its normal operating interface and remains stable. If it does, proceed to final functional verification.
7. Observe Startup for Repeatable Symptoms
Record any displayed message, startup stage, abnormal sound, fan behavior, blank display, peripheral initialization problem, or point where startup stops. Do not enter restricted service menus or alter system configuration to bypass the problem.
Expected outcome: Either startup completes normally or useful repeatable evidence is captured for escalation.
8. Perform Final Functional Verification
After successful startup, verify the user interface responds, a compatible probe is recognized, live imaging can be obtained, controls operate normally, and no abnormal warning condition returns.
Expected outcome: The Resona I9 starts consistently and performs normal basic imaging functions. If successful, troubleshooting can stop and the device may be returned to service according to facility policy.
If the Problem Persists
Common external power, connection, peripheral, and startup causes have been ruled out. A persistent failure may involve internal power distribution, computing hardware, software, display electronics, configuration, or another service-level condition.
Remove the device from service, label it Out of Service, and send it for repair or bench evaluation. Evaluate it using appropriate Mindray service documentation and approved test equipment. Internal repair, software recovery, or configuration changes should be performed only by qualified personnel.
After repair, complete applicable electrical-safety and functional return-to-service testing, including successful startup and basic imaging verification.
Knowing when to stop external troubleshooting and escalate is proper troubleshooting.
Clinical Use Tip
Do not keep a patient waiting on an ultrasound system that cannot complete a reliable startup; move the examination to another verified system.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported the Mindray Resona I9 would not complete startup and remained unavailable for imaging."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found the AC power connection at the system was not fully seated."
Resolution
What action was taken.
Example:
"Clinical Engineering secured the power connection, completed repeated normal startups, verified probe recognition and live imaging, and returned the system to service."
Helpful Details to Include (If Known)
- Whether the system was completely dead or partially powered
- Startup stage where operation stopped
- Exact displayed message
- AC receptacle verification
- Power cord and plug condition
- Recent relocation or power interruption
- External peripherals connected
- Probe recognition after startup
- Abnormal sounds, heat, odor, or damage
- Results before and after correction
- Final device status
Final Thought
Protect the patient first, verify external power and connections before assuming internal failure, confirm reliable startup with functional testing, escalate persistent faults appropriately, and document the complaint, cause, and resolution clearly.
That is successful troubleshooting.