On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
No power, no startup response, or intermittent power issues caused by external power sources, connections, or basic system faults.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- If the light source fails during a procedure, immediately transition to a backup light source or system.
- Expected: Procedure continues safely with adequate visualization
- Why it matters: Loss of illumination directly impacts visibility and patient safety
Verify the Reported Issue
- Attempt to power on the unit and observe behavior:
- No lights, no fan, no response
- Brief power then shutdown
- Intermittent or delayed startup
- Expected: Clear identification of power failure type
- Why it matters: Helps determine if issue is input power, internal protection, or load-related
Check AC Power Source (Most Common Cause)
- Verify outlet functionality using a known-good device.
- Ensure connection to a hospital-grade outlet or approved power strip.
- Expected: Confirmed stable power source
- Why it matters: Dead or unstable outlets are a frequent cause of no-power conditions
Inspect Power Cord and Connections
- Check the power cord for:
- Loose connections at wall or device
- Visible damage or fraying
- Reseat both ends securely. Replace with a known-good cord if available.
- Expected: Secure, intact power connection
- Why it matters: Damaged or loose cords prevent proper power delivery
Verify Rear Power Switch and Fuse Area
- Ensure the main power switch (if present) is in the ON position.
- Inspect the fuse holder:
- Check for blown fuse
- Reseat or replace with correct rating if needed
- Expected: Unit receives power after fuse or switch correction
- Why it matters: Blown fuses commonly occur after power surges or faults
Disconnect Accessories and Scope
- Remove all connected components:
- Light cable
- Scope
- Any external control or video system connections
- Attempt to power on with only AC power connected.
- Expected: Unit powers on if external load was causing issue
- Why it matters: Shorted accessories can prevent startup or trigger protection shutdown
Check for Overheating or Thermal Protection
- Feel for excessive heat or listen for fan inactivity.
- Allow the unit to cool for 15–20 minutes and retry.
- Expected: Unit powers on after cooling if thermal protection was triggered
- Why it matters: Overheating can cause automatic shutdown or prevent startup
Observe Indicator Lights and Fan Behavior
- During power attempt, note:
- Any LED activity
- Fan spin or lack of movement
- Clicking or abnormal sounds
- Expected: Some response indicates partial power or internal fault
- Why it matters: Helps differentiate complete power failure vs internal subsystem issue
If the Problem Persists
If all external power sources, cords, fuses, and accessories have been verified, the issue is likely internal (power supply board, internal fuse, or control circuitry).
Remove the device from service.
Label it Out of Service.
Send for repair or bench evaluation.
Knowing when to stop prevents unnecessary risk and is part of proper troubleshooting.
Clinical Use Tip
Never troubleshoot a light source while it is actively needed for a procedure. Always switch to a backup system before beginning diagnostics.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Light source would not power on during OR setup."
Cause
What was observed during troubleshooting.
Example:
"Failed AC power cord connection at device inlet."
Resolution
What action was taken.
Example:
"Reseated power cord and verified normal operation."
Helpful Details to Include (If Known)
- Outlet tested and verified
- Power cord swapped
- Fuse checked/replaced
- Indicator lights status
- Fan operation observed
- Any unusual heat, smell, or sound
- Final device status (operational or removed from service)
Final Thought
Power issues should always be approached from the outside in—starting with the simplest and most likely causes. Patient safety depends on rapid system recovery or appropriate escalation. Thorough documentation ensures clarity and supports future troubleshooting.
That is successful troubleshooting.