# Fiber Optic Cable Length from OTDR Distance Calculator > Source: https://netray.co/tools/fiber-optic-cable-length-from-otdr-distance-calculator > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Turn an OTDR distance into physical cable length with a helix factor, and see the one-way and round-trip propagation delay. ## Category industry-templates ## Industry Fiber Optics ## Audience - Fiber optic technician - Outside plant engineer - Test engineer ## Tool **Kind:** calculator **Inputs:** #### OTDR distance to end **Key:** otdr_dist **Type:** number **Default:** 12500 **Min:** 0 **Step:** 10 **Unit:** m **Help:** Reading at the far end event with the index set as below. #### Group index (IOR) used **Key:** ior **Type:** number **Default:** 1.4682 **Min:** 1.3 **Max:** 1.6 **Step:** 0.0001 **Help:** Use the value from the fiber datasheet at the test wavelength. #### Helix (excess fiber) factor **Key:** helix **Type:** slider **Default:** 1 **Min:** 0 **Max:** 5 **Step:** 0.1 **Unit:** % **Help:** Fiber length is often a little longer than the cable. Check the cable maker's data. #### Slack and service loops **Key:** slack **Type:** number **Default:** 60 **Min:** 0 **Step:** 5 **Unit:** m **Help:** Total coiled slack included in the measured length. **Outputs:** #### Fiber length (OTDR) **Key:** fiber_len **Expr:** otdr_dist **Format:** number **Description:** Distance in meters along the fiber as measured. #### Sheath length including slack **Key:** cable_len **Expr:** otdr_dist / (1 + helix / 100) **Format:** number **Primary:** true **Description:** Approximate cable length after removing excess fiber. #### Route length excluding slack **Key:** route_len **Expr:** max(otdr_dist / (1 + helix / 100) - slack, 0) **Format:** number **Primary:** true **Description:** Approximate route distance for records. #### One-way delay **Key:** delay_us **Expr:** otdr_dist * ior / 299.792458 **Format:** decimal **Description:** Microseconds, from length times index divided by c. #### Round-trip delay **Key:** rtt_us **Expr:** 2 * otdr_dist * ior / 299.792458 **Format:** decimal **Description:** Microseconds, useful for latency budgets. **Chart:** #### Cable length vs helix factor **Type:** line **X:** helix **From:** 0 **To:** 5 **Steps:** 25 **Series:** - cable_len - route_len **Disclaimer:** Results are estimates. The correct group index and helix factor come from the fiber and cable data sheets. Always verify the sheath markings on the cable for contractual length. ## Content **Intro:** An OTDR measures optical distance along the fiber, not the length of the cable on the drum or in the duct. This calculator converts one to the other and gives propagation delay for latency work. **Sections:** #### How to use the calculator **Body:** Enter the OTDR distance to the far end event, the group index set in the instrument, the helix factor for the cable design, and the total slack in the route. The outputs show the estimated sheath length, the route length without slack, and the one-way and round-trip delay. Use the chart to see how the helix assumption changes length. **Bullets:** - Use the group index in the OTDR for the wavelength used - Slack includes loops at splice points and at both ends - Cross-check with the sheath markings when you can #### The formulas behind it **Body:** An OTDR computes distance from time of flight, so distance equals speed of light in the fiber times time, and the speed in the fiber is c divided by the group index. If the IOR in the instrument differs from the true value, the displayed distance is off by the same ratio. Cable length is the fiber length divided by one plus the excess fiber fraction, since fiber in loose tube or ribbon designs follows a slight helix. Delay is length times index divided by c, about 4.9 microseconds per kilometer for a typical single mode fiber. #### Worked example **Body:** With 12,500 m on the OTDR, an index of 1.4682, a 1 percent helix and 60 m of slack, the sheath length is about 12,376 m and the route length about 12,316 m. One-way delay comes to roughly 61 microseconds. If the true index were 1.4680 instead of 1.4682, the length error would be on the order of 2 m over this span, small compared to the helix and slack effects. #### Common mistakes **Body:** Leaving the instrument at a default index for a different fiber type, ignoring helix and slack when comparing to the as-built route length, and using OTDR distance for contractual cable length without checking sheath marks. Remember also that the OTDR dead zone and the launch cable shift the start of the measurement. Subtract the launch fiber length if it is included in the reading. **Cta:** If your as-built lengths and cable drums live in your ERP, we can help reconcile OTDR data with inventory and project records. **Faq:** #### What group index should I use? **Answer:** Use the group index from the fiber data sheet for the test wavelength. Many single mode fibers are near 1.466 to 1.468 at 1310 nm and 1550 nm, but the exact value varies by manufacturer. #### Why is the OTDR length longer than the cable length? **Answer:** Because fiber is usually slightly longer than the sheath, due to helix in loose tube or stranded designs, and because slack loops and splice coils add length that is not on the route. Index settings also affect the reading. #### Can I use this for latency estimates? **Answer:** Yes. The delay output uses the fiber length times the group index divided by the speed of light. Add equipment latency separately. Delay rises with route length, not straight line distance. #### How accurate is the result? **Answer:** It is an estimate. Accuracy depends on the index, helix and slack inputs, and the instrument's distance resolution. Use sheath markings for contractual cable length. ## Search terms otdr distance to cable length, fiber length vs cable length, index of refraction otdr setting, helix factor fiber cable, fiber propagation delay calculator, otdr group index, fiber optic cable length calculator, otdr length correction --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json