On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshoots startup, power, boot, and self-test problems caused by external power, connections, accessories, configuration, or environmental conditions.
Step-by-Step Troubleshooting
1. Protect the Patient and Maintain Procedural Continuity
Do not troubleshoot an unreliable EVIS X1 system while it is actively required for visualization during a patient procedure. If the system fails during use, notify the clinical team and transition to a verified alternate visualization system according to facility procedure.
Inspect for smoke, unusual odor, excessive heat, liquid intrusion, damaged housings, or obvious electrical damage. Immediately remove the equipment from service if any of these conditions are present.
Expected outcome: The patient is supported by reliable equipment and the EVIS X1 can be evaluated without affecting care. If physical or electrical damage is found, stop troubleshooting and remove the affected equipment from service.
2. Confirm the Exact Startup Failure
Determine whether the processor:
- Shows no signs of power.
- Powers on but the display remains blank.
- Begins startup and freezes.
- Restarts repeatedly.
- Stops during its normal startup checks.
- Behaves differently with connected accessories removed.
Record any exact message displayed rather than summarizing it.
Expected outcome: The failure is reproduced and classified as a power, boot, restart, or startup-check problem.
3. Verify AC Power
Confirm the power cord is fully seated at the processor and approved power source. Inspect the cord and plug for damage.
Verify the outlet or equipment power distribution source with an appropriate tester or known-good device when permitted. If the system is connected through a cart, power strip, isolation device, or UPS, verify that component is energized and functioning.
Expected outcome: Reliable AC power reaches the processor. If correcting the outlet, cord, or power-distribution problem restores normal startup, verify operation and stop troubleshooting.
4. Inspect External System Connections
Power the system down safely and inspect accessible external cables and connectors between the processor, display, light source or associated modules, and other system components.
Look for:
- Loose connectors.
- Partially inserted plugs.
- Bent or damaged connector shells.
- Pin contamination where externally visible.
- Cable strain.
- Incorrectly routed or disconnected system cables.
Reseat only user-accessible connections intended for routine connection and disconnection.
Expected outcome: All required external connections are secure and undamaged. If reseating a loose connection restores normal booting, continue to final verification.
5. Isolate External Accessories
Disconnect nonessential external accessories such as recording devices, network connections, USB peripherals, auxiliary displays, printers, or other optional equipment where safe and appropriate.
Restart the processor with only the minimum required equipment attached.
Expected outcome: The processor completes startup with essential components only. If it does, reconnect accessories individually to identify the external device or connection causing the problem.
6. Check Endoscope and Peripheral Influence
If the startup failure occurs only when a particular endoscope or peripheral is attached, power the system down and inspect that accessory and its connector.
When available, compare operation using a compatible known-good accessory approved for the system.
Expected outcome: The processor starts normally with known-good accessories. If one accessory consistently causes the failure, remove that accessory from service rather than assuming the processor has failed.
7. Check Ventilation and Environment
Confirm ventilation openings are unobstructed and that the processor is not packed tightly against other heat-producing equipment.
Check for:
- Excessive ambient heat.
- Blocked vents.
- Dust accumulation externally.
- Equipment stacked in a way that restricts airflow.
- Recent movement, cleaning, or fluid exposure.
Do not open the chassis for internal inspection.
Expected outcome: The system has adequate airflow and no obvious environmental condition explains the startup problem.
8. Perform a Controlled Restart
After external power, accessories, and environmental causes have been checked, perform a normal shutdown and restart using approved controls.
Avoid repeated rapid power cycling.
Expected outcome: The processor completes its normal startup sequence without freezing, restarting, or reporting a fault. If it does, proceed to final verification and stop troubleshooting.
9. Perform Final Functional Verification
Reconnect required system components and verify:
- Normal processor startup.
- Stable image generation.
- Endoscope recognition.
- Required display output.
- Light and accessory operation as applicable.
- No repeated restart or startup fault.
Perform any facility-required electrical safety or functional checks before returning equipment to service.
Expected outcome: The complete system starts and operates consistently under normal configuration.
10. Escalate if Startup Remains Unreliable
If the processor remains dead, freezes, restarts, or cannot complete startup after external causes are ruled out, discontinue external troubleshooting.
Expected outcome: The processor is removed from clinical availability and referred for qualified bench or manufacturer-level evaluation.
If the Problem Persists
Common external power, connection, accessory, peripheral, and environmental causes have been ruled out. The remaining possibilities may involve internal power conversion, cooling, processor hardware, software, configuration, or another service-level condition.
The affected equipment should be:
- Removed from service.
- Labeled Out of Service.
- Sent for repair or bench evaluation.
- Evaluated using appropriate Olympus documentation and approved test equipment.
- Repaired or configured only by qualified personnel.
Do not proceed into internal board-level repair or unauthorized service functions. After corrective work, complete appropriate functional and safety testing before return to clinical use.
Knowing when to stop external troubleshooting is part of proper troubleshooting.
Clinical Use Tip
Loss of endoscopic visualization can immediately affect procedural safety; ensure alternate visualization is available before troubleshooting during an active case.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported the EVIS X1 video processor would power on but repeatedly stopped during startup."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found an external recording device connected to the processor was associated with the startup failure."
Resolution
What action was taken.
Example:
"Disconnected the faulty peripheral, confirmed repeated normal processor startups and system operation, and referred the peripheral for separate evaluation."
Helpful Details to Include (If Known)
- Exact startup symptom or displayed message.
- AC source tested.
- Power cord condition.
- Cart or power-distribution status.
- Connected endoscope and accessories.
- Optional peripherals disconnected during testing.
- Any restart or freeze behavior.
- Ventilation condition.
- Results with known-good accessories.
- Final functional test result.
- Final device status.
Final Thought
Protect the patient first, verify power and external connections before assuming an internal processor failure, escalate when startup remains unreliable, and document the complaint, cause, correction, and final verification clearly.
That is successful troubleshooting.