FiberLinkWhen a power meter reads lower than you hoped at a drop, that single number is answering two separate questions at once — and they have opposite fixes. Separating them is the whole job.
Question one — delta: how far is the measured power from what the design predicted at this exact node? Question two — range: does the measured power land inside the receiver's usable window at all? A reading can fail one, the other, both, or neither, and each combination points somewhere different.
Delta: measured vs the design prediction
Delta is the difference between what you measured and what the plan said you should measure at that node. If your design predicts −16.6 dBm at Drop 01 and the meter reads −16.9 dBm, your delta is −0.3 dB. That is noise. Nobody splices for 0.3 dB.
If the same node reads −22.4 dBm, delta is −5.8 dB, and that is a fault. Something between the last known-good point and here is eating power that the design never accounted for: a bad fusion splice, a dirty or damaged connector endface, a macrobend where someone over-tightened a cable tie, a splitter that isn't the ratio the drawing claims, or simply more fiber in the ground than the plan says.
Delta points upstream. It is a fault-finding number. A large negative delta means go look at the physical plant between here and the last node that measured clean.
Range: measured vs the receiver window
Range asks a completely different question: forget the design — can the equipment at this endpoint actually work with this much light?
Every ONU/ONT has a working window with a floor and a ceiling. Below the floor (sensitivity) the receiver cannot recover the signal. Above the ceiling (overload) you saturate it, which is a real and frequently forgotten failure — a short drop straight off a shallow split can genuinely deliver too much power.
Range points at the plan. A range failure with a healthy delta means nothing is broken: the network is performing exactly as designed, and the design was wrong. That is a splitter ratio, a split point, or a reach problem — not something you fix with a splice kit.
Range only applies at endpoints.
Judging a transmitter or a mid-span splice against an ONU receiver window is meaningless — those components were never supposed to land inside it. Only endpoints get the range check; everything else is judged on delta alone.
Reading the four combinations
Take the two answers together and the diagnosis falls out:
| Delta | Range | What it means |
|---|---|---|
| Pass | Pass | Healthy. Record it and move on. |
| Fail | Pass | A fault upstream, with margin still in hand. Find it before it drifts further. |
| Pass | Fail | Built as designed; the design does not close. Re-plan the split. |
| Fail | Fail | A fault that has already pushed the link out of service. Fix the plant first, then re-check the margin. |
Why "it's a bit low" is not a diagnosis
The failure mode this replaces is the familiar one: a technician reads −24 dBm, decides it "seems low," and either starts hunting a fault that does not exist or signs off a link that was already outside spec. Both cost a day.
A −24 dBm reading is fine on a design that predicted −23.8 dBm into a Class C+ receiver. The same −24 dBm is a hard fail on a design that predicted −17 dBm. The number alone means nothing without the prediction next to it — which is precisely why the comparison belongs at the node, in the field, at the moment you take the reading.
Set your tolerance before you measure
Delta needs a threshold: how many dB of drift counts as a fault rather than as normal variation? Too tight and every reading is a false alarm; too loose and you sign off real damage.
Around 2 dB is a common working figure for a link that was carefully characterised — it absorbs meter calibration differences, connector repeatability and temperature, without hiding a bad splice. Decide it once for the job, then apply it consistently to every reading, so pass and fail mean the same thing across the whole build.
Log the reading where the design lives
All of this only works if the prediction and the measurement sit in the same place. A meter reading written on the back of a drawing, to be compared against a spreadsheet back at the office, is a comparison that mostly does not happen.
FiberLink keeps the design on the phone you already carry into the field. Tap a node, enter what the meter reads, and the verdict appears as you type — delta and range judged separately, with the pass/fail criteria you chose recorded alongside the number. Tag the reading with a GPS fix so the next crew can find the exact node, and export the whole network as a PDF where every node carries its design value, its measured value and its status.
Do the comparison at the node, not at the office.
FiberLink logs a reading against the design and returns pass, marginal or fail on the spot — with the math visible line by line. Get it free on Google Play →
The short version
One reading, two questions. Delta compares against the design and finds faults. Range compares against the receiver and finds planning mistakes. Check both, keep them separate, and a number that used to be ambiguous tells you exactly which tool to pick up next.