On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshoots unstable or abnormal images caused by endoscope condition, video cabling, display settings, contamination, connection problems, or interference.
Step-by-Step Troubleshooting
1. Protect the Patient and Determine Whether Imaging Is Clinically Reliable
If flicker, color distortion, noise, or artifacts interfere with safe visualization, remove the system from active patient use and provide a verified alternate scope or video system.
Expected outcome: Clinical decisions are not based on unreliable imaging.
2. Characterize the Image Problem
Determine whether the abnormality is:
- Constant or intermittent.
- Present on one scope or all scopes.
- Present on one monitor or all displays.
- Triggered by cable movement.
- Limited to a section of the image.
- Related to illumination level.
- Present in saved recordings as well as live video.
Expected outcome: The symptom pattern helps isolate the affected portion of the imaging chain.
3. Inspect the Distal End and External Optical Surfaces
Check the endoscope for external contamination, residue, moisture, or visible damage that could affect image quality.
Use only approved handling and cleaning practices.
Expected outcome: Accessible optical surfaces are clean and undamaged. If proper cleaning restores the image, verify performance and stop troubleshooting.
4. Verify Endoscope Connection
Inspect and reseat the scope connection using normal connection procedures.
Look for contamination, moisture, connector damage, or strain.
Expected outcome: The scope remains securely recognized and image artifacts do not change with normal movement.
5. Compare a Known-Good Endoscope
Connect a compatible known-good scope under the same processor and display conditions.
Expected outcome: If the image becomes normal with the known-good scope, the original scope is isolated as the likely source and should be removed from service.
6. Compare the Display Path
Check whether the artifact appears on another approved monitor or output.
Inspect external video cables and replace a suspect cable with a known-good equivalent where available.
Expected outcome: The test isolates the issue to the display/cabling path or confirms that the abnormal image originates earlier in the system.
7. Check Monitor Settings
Compare brightness, contrast, color, image mode, and other user-accessible monitor controls to a known working display configuration.
Avoid undocumented service adjustments.
Expected outcome: The monitor is configured normally. Incorrect display settings are corrected without altering restricted calibration parameters.
8. Check for Electrical or Environmental Interference
Observe whether the artifact appears only when nearby powered equipment is operating.
Inspect cable routing for unnecessary proximity to damaged power cords, motors, electrosurgical equipment, or other potential interference sources.
Do not defeat grounding or safety protections.
Expected outcome: External interference is either eliminated or ruled out.
9. Check System Modes and User-Accessible Image Settings
Confirm that the selected imaging mode or image enhancement setting matches expected clinical use.
Do not treat an intentionally selected image-processing mode as a hardware fault.
Expected outcome: The processor is using the intended user-accessible imaging configuration.
10. Perform Final Functional Verification
Verify the image remains:
- Stable.
- Properly colored.
- Free from abnormal noise.
- Free from intermittent flicker.
- Consistent across required monitors.
- Stable during normal scope and cable movement.
Expected outcome: Image quality remains acceptable and reproducible. If so, troubleshooting can stop.
11. Escalate Persistent Image Abnormalities
If multiple known-good scopes and displays show the same artifact, or the abnormality remains after external connections and settings are verified, stop external troubleshooting.
Expected outcome: The affected processor or imaging component is referred for qualified service evaluation.
If the Problem Persists
Scope condition, optical cleanliness, external video cables, monitor settings, display hardware, and environmental interference have been checked. Remaining possibilities may include internal image processing, camera electronics, scope electronics, processor hardware, software, or calibration-related conditions.
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.
Return to service only after normal image quality is demonstrated under the complete clinical configuration.
Clinical Use Tip
Image artifacts can hide or mimic clinical findings; do not permit continued use when image quality is unreliable for the intended procedure.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Staff reported intermittent flicker and color distortion on the EVIS X1 image during setup."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found the abnormality followed one external video cable while the processor and endoscope operated normally with a known-good cable."
Resolution
What action was taken.
Example:
"Replaced the defective video cable and verified stable color and artifact-free imaging on the clinical monitor."
Helpful Details to Include (If Known)
- Type and location of image artifact.
- Endoscope used.
- Whether multiple scopes were tested.
- Monitor or output affected.
- Cable movement effect.
- Known-good video cable result.
- Known-good display result.
- Environmental equipment operating nearby.
- Image mode or relevant setting observed.
- Final image quality.
- Final device status.
Final Thought
Unreliable imaging should be taken seriously: isolate the scope, cable, monitor, settings, and environment before assuming internal failure, verify the corrected image, and document the result clearly.
That is successful troubleshooting.