CodingBox Documentation

Fibre plant faults and how they show up

Most fibre "outages" are not broken fibres. They are a fingerprint on a connector, a cable tie pulled tight, a patch cord of the wrong type, a splice done in the rain, a connector left uncapped in a dusty room — small mechanical facts that cost decibels. This page lists the plant faults by how often they happen, gives for each the symptom at the transceiver, the signature on the instruments and the fix, and adds the seasonal and slow faults that monitoring catches before users do.

The fault list

#FaultHow commonLoss causedWhere
1Contaminated connector endfacemost common by far (> 50 % of tickets)0.5–3 dB, or intermittentany mating; especially rarely-touched panel ports and module receptacles
2Macrobendvery common0.5–10 dB, wavelength-dependentcable ties, panel doors, slack loops, bent patch cords behind racks
3Wrong fibre or connector typecommon at installation2–20 dB, or no link62.5 vs 50 µm, SMF vs MMF, APC vs UPC, MPO polarity
4Damaged endface (scratch, chip)common0.3–2 dB + reflectionsmated without cleaning, dirt ground in
5Bad spliceoccasional0.3–1 dB, or high reflectance (mechanical)field splices in bad conditions, mis-cleaved
6High reflectanceoccasional0–1 dB but laser instability, BERopen or air-gap connectors, mechanical splices, damaged UPC
7Crushed or kinked cableoccasional1–20 dB or breakdoors, heavy cables on top, rodents, construction
8Water in closure / water peakrare but slow0.5–2 dB rising at 1383 nm and 1550+flooded manholes, cracked closures; old fibre with hydrogen ageing
9Fibre breakraretotaldigging, rodents, ice, vehicle strikes
10Excess connector count / wrong designdesign errorbudget exhaustedtoo many panels, cassettes
11Overload (not a plant fault)occasionalerrors with strong signallong-reach module on short link (Link budget)

Symptoms at the transceiver

DDM / link observationLikely plant fault
Rx power 1–3 dB below the link passport, one directiondirty or scratched connector on the Tx side of that direction, or a bend in that fibre
Rx power down symmetrically both directionsbend or crush of the duplex cord, common panel, or fibre attenuation increase (water)
Rx fine at 1310 (LR) but poor at 1550 (ER) on the same fibremacrobend — loss grows with wavelength (Attenuation)
Rx −40 dBm / no light one directionbreak, disconnected, Tx/Rx swapped at one end, wrong panel port
Rx good, link flaps or errorsreflectance (laser instability), dispersion, or a connector making intermittent contact (Link flapping)
Loss worse in cold weathermicrobending from cable contraction, gel stiffening; ice loads
Loss worse in heat / rainclosure ingress, thermal expansion pulling a splice tray
New link 5+ dB above design losswrong fibre type, mode mismatch, mis-referenced test
MPO link: some lanes downpolarity method mismatch, or one fibre of the trunk damaged (Breakout & MPO)

Bench-side first steps: No link, Physical mismatches.

Instrument signatures

FaultOTDRLSPMInspection scopeVFL
Dirty connectorreflective event with excess loss (0.5–3 dB), often high reflectancetotal loss above designcontamination in zone A/B
Macrobendnon-reflective step; loss at 1550/1625 ≫ 1310loss wavelength-dependentred glow at the bend through the jacket
Wrong fibre typestep at the joint (2–4 dB for 62.5→50); different backscatter slopelarge lossdifferent core size visible
Bad fusion splicenon-reflective step > 0.3 dB (average both directions)
Mechanical splice / air gapreflective event, reflectance −35 … −45 dBsmall loss
Damaged endfacereflective, moderate lossscratches/chips in zone A
Crushlocalized step, may be reflective; sometimes distributed lossglow if severe
Water / hydrogen ageinguniform slope increase, strongest at 1383 and > 1550 nmloss at 1550 up, 1310 less
Breakend-of-fibre spike or noise at a distance shorter than the routeno lightglow at the break if within metres
Ghostreflective spike beyond real events at multiples of a distance

Instrument use and trace reading: Testing and measurement.

Fix per fault

FaultFixPrevent
Contaminationinspect, clean (dry click cleaner; wet-dry for oils), re-inspect both sidescaps on everything, clean before every mating, no touching ferrules
Macrobendre-route, loosen ties, radius ≥ 30 mm; use G.657 cords in tight spacescable management with bend guides
Wrong typereplace cord/plant with the right type; mode-conditioning cords are a 1G-only workaroundcolour discipline: yellow/blue = SMF UPC, green = APC, aqua = OM3/OM4
Damaged endfacereplace the connector (re-terminate or new cord)clean, inspect, don't force
Bad splicere-splice; check cleaver, electrodes, fibre prepqualified splicers, indoor or tented work
Reflectancereplace air-gap/mechanical parts with fusion or APC; cap open portsAPC on PON/DWDM/analog; never leave unmated UPC in path
Crushreplace the cable section; add protectionroute away from doors and heavy cable
Waterdry and reseal closure; replace fibre with water damageIP68 closures, drainage, inspection schedule
BreakOTDR locate → splice or replace sectionroute diversity, marking, permits
Designreduce connector count, cassettes → direct splices, longer-reach opticsbudget review before purchase

Slow faults and monitoring

SignalCauseDetection
Rx power drifting down 0.1 dB/monthconnector contamination, closure ingress, fibre ageingDDM trend with a baseline (Monitoring)
Seasonal ±1 dB swingtemperature effects on outdoor plantacceptable if margin ≥ 3 dB; record it
Loss increases after works nearbynew bend or crushcompare with passport; OTDR against installation trace
Tx power falling at the far endfar module ageing, not plant (Tx bias & ageing)Tx DDM and bias trends
FEC correctable errors rising with stable powerreflectance or dispersion growth (rare) or module degradationFEC counters (VDM & FEC metrics)

The triage order

  1. Compare with the passport (Rx now vs Rx at commissioning) at both ends.
  2. Which direction? One direction bad → look at that direction's Tx end connectors and fibre; both → common elements.
  3. Swap the module with a known-good one for 5 minutes — plant or module.
  4. Inspect and clean every accessible connector in the path.
  5. LSPM the link at two wavelengths; compare with the installation report.
  6. OTDR from the end with the bad direction; find the event.
  7. Fix, re-test, update the passport.

In CodingBox

Step 3 is where the bench comes in: a module read in CodingBox with normal Tx power, sane thresholds and a plausible Rx from a reference source is proven good, and the plant is the suspect. Recording the module's DDM at commissioning gives the passport that step 1 needs (DDM in the app, Code database).

Preventing these faults and recovering from the big ones — maintenance cycle, monitoring, spares, the restoration process: Maintenance and restoration; working on the plant safely — laser classes, live fibre, glass, site hazards: Safety and handling.