DEV Community

Dheeraj Ramasahayam
Dheeraj Ramasahayam

Posted on

Fusion splice loss: what the 0.03 dB on the splicer screen actually means

Fusion splice loss: what the 0.03 dB on the splicer screen actually means

Part 8 of the series "Data center field notes" — field notes from real break-fix work.

The splicer finishes the arc, the screen shows 0.03 dB, and the instinct is to call it good and move on. That number is not a measurement. It is the splicer's estimate of the loss, judged from the fiber image: how well the cores aligned, how clean the cleaves were. The real measurement comes later, on the OTDR trace or the span test. The estimate is still useful, but only if you read it the right way: against the loss budget for that span, not against a number you memorized, and with a clear rule for when to cut the splice and do it again.

What the splicer actually estimates

A fusion splicer does not measure light passing through the joint. It looks at the two fiber ends — core alignment, cleave angle, any chips or dirt on the end-face — and estimates the loss that joint should cause. A clean, square cleave with the cores dead-on gives a low estimate; a chipped cleave or a slight offset gives a higher one. That is why the estimate can change when you re-splice the same two fibers: nothing about the fiber changed, only the quality of the ends you presented to the arc. Treat the number as a screen at the tray, not as the record. The number that goes in the ticket as proof is the OTDR loss step or the span test, measured after the splice is protected and the tray is closed.

This is the read I use after 200+ splices — single-mode and multimode, stripped, cleaned, and cleaved by hand, fused, protected in trays and enclosures, and validated with Fluke testing and OTDR and VFL checks.

Read it against the budget, not against a universal number

There is no pass/fail number for a single splice. The span's loss budget is the pass/fail line: add up the fiber attenuation for the distance, the connector losses, and every splice on the span, and compare the total to the budget. A 0.08 dB splice can be fine on a short span with budget to spare and a fail on a long span that is already near its limit. The same estimate means different things on different jobs, which is why a tech who memorizes "0.05 is good, 0.10 is bad" will pass splices that fail the span and re-do splices that were fine. Before you start splicing, know the budget for the span and how much of it is already spoken for by the other splices and connectors. Then each estimate gets judged against what is left.

The re-splice decision: cleave first, always

When the estimate comes back high against the budget, the first suspect is the cleave, not the splicer. Cut the splice, and inspect both ends before you touch anything else: cleave angle, chips on the edge, dirt on the end-face. Then re-strip, clean, and cleave both fibers and re-fuse. In most cases the second estimate drops sharply, because the first cleave was the problem.

If the estimate stays high after a clean re-cleave, stop burning splices on the same joint and widen the check: are the two fibers the same type — single-mode to single-mode, multimode to multimode, same core size? Is the alignment actually seating, or is the fiber slipping in the holder? Are the electrodes worn, giving a weak or uneven arc? A high estimate that survives a good re-cleave is the splicer telling you something about the fiber or the machine, and re-fusing the same ends a third time will not fix it.

Single-mode vs multimode: what "good" looks like

The estimate behaves differently by fiber type, and so does the proof. On single-mode, the core is 9 microns and alignment is everything — a small offset is a real loss, so the estimate is sensitive and the OTDR will show a clean loss step at the splice point. On multimode, the core is 50 or 62.5 microns and the splice is more forgiving of alignment, but the estimate is also less precise, and the OTDR trace can show a gainer — a step that looks like gain rather than loss — depending on which direction you shoot the trace. That is why a multimode splice is proven by shooting the OTDR from both ends and averaging, not by trusting one direction. Whatever the type, the rule is the same: the estimate screens the splice at the tray, the OTDR step and the span test prove it.

Protect it: a good splice pinched in a tray is a bad splice

The splice is not finished when the estimate looks good — it is finished when it is protected. Slide the splice into its sleeve, seat it in the tray, and close the enclosure without pinching or bending it. A splice pinched by a tray lid or bent around a tight corner in the tray will test fine at the splicer and fail on the OTDR later, because the loss is in the protection, not the joint. Route the fiber into the tray with its minimum bend radius respected, secure the sleeve in its slot, and leave the service loop coiled so the next move in the rack does not tug the splice. The tray is where good splices go to die if it is closed carelessly — check the routing before the lid goes on, not after the ticket is closed.

Validate: OTDR, VFL, and the span test

Three checks, in order. First, the OTDR trace: shoot the span and look for the loss step at the splice point — the step size is the measured loss of that splice, and it is the number that belongs in the record. Second, the visual fault locator for a quick visible check: light leaking at the splice point means a gross fault, and it is visible in seconds. Third, the span test with a light source and power meter, or a Fluke test set: total span loss against the budget, which is the only check that proves the link as a whole. The splicer estimate, the OTDR step, and the span test answer three different questions — was the joint clean, how much does this splice lose, does the span pass — and a splice is only done when all three are recorded.

The ticket line

The splice is part of the plant, so it belongs in the ticket record. The minimum useful line:

Tray 3, slot 7 ↔ Panel B tray 1,
SM OS2, splicer estimate 0.03 dB,
OTDR loss step 0.04 dB at 212 m,
span test -2.1 dB vs 3.0 dB budget: PASS.
Enter fullscreen mode Exit fullscreen mode

The shape to copy: splice location (tray and slot), fiber type, splicer estimate, OTDR loss step with distance, and the span test against the budget. Five fields, and the next person on the ticket knows where the splice is, what the machine thought of it, what it actually measures, and whether the span passes — without opening the tray to find out.

A question for you

When a splice estimate comes back high, what do you check first — and have you ever had a splice that looked perfect on the splicer screen and failed on the OTDR later? What was actually wrong with it?

Top comments (0)