TECHNICAL SELECTION NOTES · UPDATED 2026-10-13

Why OTDR Length Differs from Cable Markings: IOR, Helix Factor and Datums

An OTDR converts propagation time into distance using the configured group index. A helix correction may convert fiber distance to cable distance. Align wavelength, IOR, correction and span datums before comparing markings or assembly dimensions; a discrepancy alone does not establish a delivery shortage.

Direct answer

An OTDR converts propagation time into distance using the configured group index. A helix correction may convert fiber distance to cable distance. Align wavelength, IOR, correction and span datums before comparing markings or assembly dimensions; a discrepancy alone does not establish a delivery shortage.

Identify the span being measured

An assembly drawing, cable-jacket marking difference and OTDR fiber distance may use three different datums. For preterminated trunks or test cords, define the comparison in the drawing and test plan before comparing numbers.

EXFO's AXS-100 manual explains time-of-flight conversion using IOR. Its MAX-700 manual distinguishes wavelength-specific group index from the helix factor accounting for fiber-to-cable length differences. These references establish principles and named-instrument settings, not universal software menus or correction algorithms.

How IOR affects distance

Before cable-length correction, distance can be understood as L = c × t / (2 × n_g). Here c is vacuum light speed, t is round-trip pulse time and n_g is group index at the test wavelength. The factor of two accounts for the round trip.

For unchanged flight time, a larger configured n_g gives a shorter distance. Obtain the fiber manufacturer's applicable value instead of making another fiber's default a contractual datum.

ComparisonConditions to alignFirst investigation
Two OTDR resultsWavelength, IOR, correction and span endpointsSettings and reanalysis history
OTDR versus markingsFiber-to-cable correction and marking locationsCable construction and marking convention
OTDR versus assembly sizeMechanical datums and optical spanConnectors, branches and added test leads
Two fiber distancesFiber type, settings and endpointsRouting, excess fiber and splice construction

A reproducible settings example

This is a calculation, not a measured product or recommended setting. Assume actual group index 1.468 at the chosen wavelength, configured index 1.460, identical endpoints and no helix correction.

ItemAssumption or calculationInterpretation
Actual fiber span1000 mGiven for this example
Displayed distance1000 × 1.468 / 1.460, approximately 1005.48 mConversion of the same flight time
DifferenceApproximately 5.48 m or 0.548%Group-index setting alone
Excluded effectsEndpoint selection, instrument accuracy and cable correctionNot a complete uncertainty budget

The example explains a setting effect. It proves neither overdelivery nor shortage and does not establish a universal 0.548% tolerance.

Helix correction and service slack

The fiber path inside a cable can differ from the jacket path. A helix factor addresses that construction difference, using the applicable cable information and instrument definition. It does not automatically remove an external rack service loop. Do not adjust it merely to make an unexpected result match an order length.

Retain raw traces, IOR, wavelength, helix factor and software revision. Preserve both files and the reason when reanalysis changes distance. Consistent original settings make before-and-after comparisons meaningful.

Put dimensional acceptance in the purchase specification

For short jumpers, define connector measurement datums, the physical measurement state and length tolerance. Dimension trunk and branches separately. Review whether the OTDR can resolve those short spans; displayed decimal places alone do not establish capability.

Identify launch and receive leads and the tested span separately in the optical record. The drawing determines delivered mechanical dimensions; the agreed test plan determines optical-span acceptance.

Procurement FAQ

  1. Can factory-default IOR remain unchanged? Check it against the fiber manufacturer's model and wavelength values.
  2. Must 1310 nm and 1550 nm use identical IOR? Follow wavelength-specific fiber information and instrument requirements.
  3. Can a helix factor compensate for service slack? Do not mix construction correction with an externally reserved cable length.
  4. Do extra meters prove an inaccurate delivery? Align endpoints, added leads and settings before applying the dimensional acceptance method.
  5. Can OTDR replace a ruler for short jumpers? Review capability and contractual datums; display resolution does not establish dimensional accuracy.

Related products and reading

Product pages describe configuration scopes. Supply, drawings and performance require project-specific confirmation.

Contact an engineer

Prepare both-end interfaces, drawings or existing test records and contact an engineer to discuss assembly requirements and verification boundaries.

Sources and review date

Sources checked on 2026-10-13. Third-party references explain technology and specific examples, not ARRANEX performance or certification. Purchasing tables are review recommendations; example assumptions apply only to the calculations.

Sources checked: 2026-10-13

RFQ / ENGINEERING REVIEW

Send what you know. We will help define the rest.

Interfaces, fiber count, application, environment, quantity or a drawing are enough to start.

Open email to inquire

Send to: xsconcom@gmail.com · Your email app opens. Review the message and send it there.

Drawings, BOMs and existing samples are welcome
Talk to an engineer