Example Data Table
| Measured time | Time type | n | Offset (m) | Slack (%) | Output | Estimated distance to event |
|---|---|---|---|---|---|---|
| 10 µs | Round-trip | 1.468 | -2.0 | 5 | m | ~ 1,019.6 m (offset + slack applied) |
| 3.4 µs | Round-trip | 1.468 | 0.0 | 0 | m | ~ 347.2 m (raw estimate) |
Formula Used
The estimate is based on signal time-of-flight in the fiber. OTDR timing is commonly measured as a round-trip time (out-and-back), so the one-way time is half of the displayed value.
- v = c / n (or v = c × VF)
- t₁ = t / 2 for round-trip OTDR time
- Distance (m) = v × t₁
- Adjusted = (Distance + Offset) × (1 + Slack%/100)
Use the refractive index or velocity factor from the cable specification for your wavelength.
How to Use This Calculator
- Read the event marker time from your trace and select its unit.
- Choose whether your time is round-trip (typical) or one-way.
- Enter either refractive index (n) or velocity factor (v/c).
- Add any known offset for launch leads, patch cords, or datum shift.
- Apply a slack percentage to estimate installed route length.
- Click Calculate, then export CSV or PDF for the job file.
For best results, keep instrument settings consistent and use the correct cable spec values.
Technical Article
1) Why OTDR Distance Estimates Matter
In fiber construction, the fastest way to locate a splice, bend, or break is to convert OTDR event time into a practical distance. This calculator turns time-of-flight into a field-ready estimate so crews can reference duct bank chainage, manholes, handholes, and route markers without re-measuring the entire run.
2) Inputs That Drive Accuracy
The most important input is the propagation speed in the fiber. You can provide either refractive index (n) or velocity factor (v/c). For many single‑mode fibers near 1550 nm, n is often around 1.468, giving a velocity factor near 0.681–0.682. Enter the value that matches your cable data sheet for the test wavelength.
3) Round‑Trip vs One‑Way Time
OTDR traces usually report a round‑trip time (out and back). The calculator converts that to one‑way time by dividing by two, then multiplies by fiber velocity. For example, a 10 µs round‑trip reading corresponds to about 5 µs one‑way. At roughly 204,000,000 m/s in glass, that yields close to 1.02 km.
4) Applying Offsets and Slack Allowance
Field conditions add short lengths that can shift the “dig point”: launch fibers, patch leads, and panel routing. Use the offset to correct the raw distance (positive adds, negative subtracts). Slack percentage then estimates installed route length, accounting for loops and routing. A 5% slack on 1,000 m becomes 1,050 m.
5) Quality Checks Before You Export
Validate the selected wavelength, confirm the correct time unit, and ensure the time type matches the instrument display. Compare the final distance against known span lengths between structures. If results look high or low, recheck n/VF and any offsets. When satisfied, export CSV or PDF for as‑built documentation.
FAQs
1) Is OTDR time always round‑trip?
Most OTDRs show round‑trip time because the instrument measures the return signal. If your device provides one‑way distance directly, select “One‑way” time type or use the reported time accordingly.
2) Should I use refractive index or velocity factor?
Use whichever your cable specification provides. Both represent the same concept: light speed reduction in fiber. If you know n, the calculator derives speed. If you know VF, it uses that directly.
3) What wavelength should I select?
Select the wavelength used during the trace (e.g., 1310 or 1550 nm). Cable refractive index and attenuation vary with wavelength, so matching the test wavelength improves consistency in reports.
4) How do I choose an offset value?
Use offset to correct known measurement shifts, such as launch leads, patch cords, or a reference datum change. If the OTDR starts after a launch cable, use a negative offset to remove that extra length.
5) What slack percentage is reasonable?
It depends on construction standards and route complexity. Straight duct runs may use 1–3%. Routes with multiple structures and loops may need 3–8% or more. Use project specifications where available.
6) Why does my estimate differ from route drawings?
Drawings often show horizontal alignment, while fiber follows actual routing with bends, trays, and slack loops. Differences also come from using an incorrect n/VF, unit mismatch, or unaccounted launch/receive fibers.
7) Can this replace OTDR distance calibration?
No. This is a practical estimator for field use. For formal acceptance testing, calibrate instrument settings, use the correct index for the cable and wavelength, and follow your test standard and project procedures.