← Troubleshooting Guides
The Toolbox — Troubleshooting
Fiber Optics
Symptom-based diagnostic guides for fiber optic link faults, fusion splices, connector cleaning and inspection, and OTDR trace interpretation.
Fiber Optic Link
High insertion loss
Possible Causes
- •Contaminated end face
- •Damaged connector
- •Tight bend
- •Wrong fiber type
Diagnostic Steps
- 1.Inspect and clean both end faces with proper fiber cleaning tools
- 2.Re-test with optical power meter after cleaning
- 3.Check for tight bends exceeding minimum bend radius
- 4.Verify fiber type matches system requirements (single-mode vs multimode)
Intermittent loss / signal dropping
Possible Causes
- •Loose connector
- •Mechanical stress on cable
- •Thermal expansion at splice point
- •Partially cracked fiber
Diagnostic Steps
- 1.Wiggle cable at each connector while monitoring power meter — loss that changes indicates connector problem
- 2.Run OTDR to locate intermittent fault
- 3.Check cable routing for areas subject to vibration or repeated flexing
- 4.Inspect all connectors for physical damage
OTDR shows unexpected reflection
Possible Causes
- •Poor fusion splice
- •Connector with air gap
- •Fiber break
- •Connector contamination
Diagnostic Steps
- 1.Locate event on OTDR trace by distance
- 2.Clean connector at that location and re-test
- 3.If loss exceeds 0.5 dB at a connector, clean and re-test or replace
- 4.If reflection is at a splice, re-splice and re-measure
Fusion Splices
Fusion splice loss higher than expected
Possible Causes
- •Fiber end face not properly cleaved
- •Core misalignment during splicing
- •Contamination on fiber before splicing
- •Wrong splice program selected for fiber type
Diagnostic Steps
- 1.Verify cleave angle is within specification — most fusion splicers require less than 0.5° cleave angle
- 2.Re-clean fiber with IPA and lint-free wipe before re-splicing — even fingerprint oils cause high loss
- 3.Select the correct splice program for the fiber type — single-mode and multimode programs differ significantly
- 4.Re-splice and re-measure — acceptable fusion splice loss is less than 0.1 dB for single-mode
Splice splicer reports error or will not complete splice
Possible Causes
- •Poor cleave — splicer rejects bad cleave angle
- •Fiber not seated correctly in V-groove
- •Contaminated electrode tips
- •Splicer needs calibration or arc reset
Diagnostic Steps
- 1.Re-cleave the fiber — most splicer errors during the splice cycle are cleave-related
- 2.Ensure fiber is fully seated in the V-groove and the clamp is closed before initiating splice
- 3.Clean electrode tips with the electrode cleaning function in the splicer menu
- 4.Run the electrode stabilization or arc calibration routine — required periodically and after electrode replacement
Splice protection sleeve not shrinking properly
Possible Causes
- •Heat shrink oven temperature too low
- •Wrong sleeve size for fiber type
- •Sleeve not centered over splice
- •Oven heating element failing
Diagnostic Steps
- 1.Verify sleeve is the correct type for the fiber being spliced — single-mode and multimode sleeves differ
- 2.Center the splice protection sleeve over the bare fiber region before heating
- 3.Check heat shrink oven temperature setting and verify it reaches target temperature
- 4.If sleeve is bubbling or deforming, temperature may be too high — check oven calibration
Connector Cleaning & Inspection
Power meter reads low even with known-good fiber
Possible Causes
- •Contaminated connector end face
- •Scratched ferrule
- •Wrong connector type or adapter
- •APC connector mated with UPC connector
Diagnostic Steps
- 1.Inspect end face with fiber inspection microscope or video scope — contamination is invisible to the naked eye
- 2.Clean with appropriate tool — cassette cleaner for most connectors, swab and IPA for tight spaces
- 3.Verify connector type matches — SC, LC, ST, FC connectors are not interchangeable without adapters
- 4.Check for APC/UPC mismatch — APC connectors have an angled ferrule (green housing) and must not be mated with UPC connectors (blue housing)
Connector passes inspection but still shows high loss
Possible Causes
- •Sub-surface contamination not visible
- •Scratched core region
- •Chipped ferrule edge
- •Fiber not fully seated in connector ferrule
Diagnostic Steps
- 1.Use a higher magnification inspection scope — some contamination is only visible at 400× magnification
- 2.Look specifically at the core region — scratches in the cladding have minimal impact but core damage is critical
- 3.Replace connector if core is scratched or chipped — polishing a damaged ferrule rarely achieves acceptable results
- 4.Check that fiber is fully inserted into the connector body — an improperly seated fiber will show high insertion loss and high return loss
Connector return loss too low (high back-reflection)
Possible Causes
- •Flat-polished UPC connector where APC is required
- •Air gap in connector mating
- •Contamination on end face
- •Physical damage to ferrule
Diagnostic Steps
- 1.Verify the correct connector polish type — APC connectors provide 60+ dB return loss vs. 40–50 dB for UPC
- 2.Ensure connectors are fully mated and adapter is not damaged
- 3.Clean end face and re-test return loss
- 4.Replace ferrule or connector if physical damage is visible on inspection
OTDR Trace Interpretation
OTDR shows a gain spike (signal appears to increase)
Possible Causes
- •Multimode fiber section joined to single-mode
- •Larger core fiber spliced to smaller core fiber
- •OTDR artifact from ghost reflection
- •Bidirectional splice measurement average not applied
Diagnostic Steps
- 1.A gain spike is almost always a splice between different fiber types or core sizes — measure from the other end to confirm
- 2.Check fiber documentation for any fiber type changes along the route
- 3.Run the OTDR from both ends and average the splice loss — the true splice loss is the average of both directions
- 4.If a gain spike appears at a known connector location, it is likely a ghost from a strong reflection elsewhere on the trace
OTDR cannot see full length of fiber
Possible Causes
- •Range setting too short
- •High early loss masking the rest of the trace
- •Fiber break close to the launch end
- •Launch cable too short causing launch zone to overlap with first event
Diagnostic Steps
- 1.Increase OTDR range setting — set range to at least 1.5× the expected fiber length
- 2.Use a launch cable (mandrel) of at least 100–200 meters to move the launch dead zone away from the first connector
- 3.Check for a break or high-loss event near the beginning of the trace that is preventing light from reaching further
- 4.Reduce pulse width — a shorter pulse improves resolution near the launch end
Events on OTDR trace do not match physical fiber length
Possible Causes
- •Incorrect index of refraction (IOR) setting
- •Wrong fiber type selected in OTDR
- •Cable length differs from fiber length due to cabling factor
Diagnostic Steps
- 1.Verify the IOR setting matches the fiber being tested — single-mode fiber typically uses IOR of 1.4675–1.4682
- 2.Check fiber manufacturer specification for the correct IOR value
- 3.Account for the cabling factor — fiber inside a cable is slightly longer than the cable jacket due to stranding, typically 0.5–1% longer
- 4.Compare OTDR distance to known physical landmarks such as splice enclosures or hand holes to verify accuracy
Trace is noisy and events are hard to identify
Possible Causes
- •Pulse width too short for the fiber length
- •Averaging count too low
- •High loss early in the link reducing signal level
- •OTDR range set too long adding noise at the measurement distance
Diagnostic Steps
- 1.Increase pulse width — longer pulses travel further but reduce resolution near the launch end
- 2.Increase averaging count — more averages reduces noise floor but increases measurement time
- 3.Set OTDR range closer to the actual fiber length — an unnecessarily long range increases noise
- 4.If early high loss is reducing trace quality, repair that fault first then re-test the full link