On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshoots missing endoscopic video caused by display power, input selection, loose connections, endoscope recognition, cabling, or output configuration.
Step-by-Step Troubleshooting
1. Protect the Patient and Restore Visualization
If visualization is lost during a procedure, do not continue troubleshooting while the patient depends on the affected system. Notify the clinical team and transition to a verified alternate visualization pathway.
Expected outcome: Patient care continues with reliable imaging before technical troubleshooting proceeds.
2. Determine What Is Actually Missing
Identify whether:
- The monitor itself is blank.
- The monitor displays menus but no endoscopic image.
- One display is blank while another works.
- Recorded video is missing but live video is present.
- The processor does not recognize the endoscope.
- The image appears briefly and disappears.
Expected outcome: The problem is isolated to image generation, video routing, or display output.
3. Verify Monitor Power and Input
Confirm the display is powered and shows its own status or menu.
Verify the selected input matches the video connection from the EVIS X1 system.
If multiple monitors are used, compare them.
Expected outcome: The display is powered and selected to the correct input. If correcting the monitor input restores the image, verify stability and stop troubleshooting.
4. Inspect External Video Cables
Inspect the accessible video cable path between the processor and monitor for:
- Loose connectors.
- Damaged cables.
- Bent connector shells.
- Strain.
- Incorrect port selection.
- Adapters or extenders in the signal path.
Reseat accessible connections and use a known-good compatible cable where available.
Expected outcome: Video cabling is secure and intact. A cable substitution that restores the image identifies the external cause.
5. Confirm Endoscope Recognition
Verify that the processor recognizes the connected endoscope.
If recognition is absent or intermittent, address the connection problem before troubleshooting video output further.
Expected outcome: The scope is recognized consistently. If scope recognition restores image output, perform final verification.
6. Check Illumination
Confirm the scope is receiving usable illumination. A dark image due to absent light can be mistaken for missing video.
Avoid looking directly into illuminated optical outputs.
Expected outcome: The scope has illumination and the display receives video. If illumination is the only missing function, troubleshoot the light pathway separately.
7. Compare Another Video Output or Display
If the system provides more than one approved output pathway, compare a second known-good monitor or output where available.
Do not change restricted configuration settings.
Expected outcome: The test identifies whether the failure follows the monitor/cable path or remains with the processor output.
8. Remove Nonessential Video Accessories
Temporarily bypass external recorders, converters, routing equipment, capture devices, or other nonessential video accessories where practical.
Connect the processor through the simplest approved path to a known-good display.
Expected outcome: A stable image appears through the direct video path. If so, the removed accessory or routing path is the likely cause.
9. Verify Normal System Configuration
Check user-accessible video output and display settings against the facility's known working configuration.
Do not enter unauthorized service menus or make undocumented configuration changes.
Expected outcome: Video settings match the expected clinical configuration.
10. Perform Final Functional Verification
Verify:
- Stable live image.
- Correct display routing.
- Normal scope recognition.
- Required monitor outputs.
- Recording output if used.
- No intermittent blanking during normal cable movement.
Expected outcome: All required video paths function consistently. If confirmed, troubleshooting can stop.
11. Escalate if No Video Remains
If a known-good scope, monitor, and video cable do not restore video, or all available processor outputs remain absent, stop external troubleshooting.
Expected outcome: The affected processor or video component is removed from service for qualified evaluation.
If the Problem Persists
External monitor power, input selection, video cabling, scope recognition, illumination, and optional routing equipment have been ruled out. Remaining possibilities may involve internal video processing, output circuitry, configuration, software, 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.
After repair, confirm the complete visualization pathway before return to service.
Clinical Use Tip
Verify the complete path from endoscope to processor to clinical display; a powered monitor alone does not confirm that usable patient visualization is available.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"OR staff reported the EVIS X1 processor was operating but the primary monitor displayed a black screen."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found the monitor was selected to an inactive video input."
Resolution
What action was taken.
Example:
"Selected the correct input and verified stable endoscopic video, normal scope recognition, and uninterrupted display output."
Helpful Details to Include (If Known)
- Which displays were affected.
- Monitor power status.
- Selected display input.
- Video cable type and condition.
- Endoscope recognition status.
- Illumination status.
- Known-good monitor or cable results.
- External recorder or router involvement.
- Results before and after correction.
- Final device status.
Final Thought
Secure alternate visualization first, then isolate the display, cable, scope, and processor pathway from simplest to most complex before assuming an internal video failure, and document the verified result.
That is successful troubleshooting.