OTDR WizardSign in

Reference · 6 min read

OTDR event table explained

Updated

An OTDR event table lists every point along the fibre where the trace changes: connectors, splices, bends and the fibre end. For each event it gives the distance from the start, the length of fibre before it, the loss across the event, its reflectance, the attenuation of the fibre leading to it, and the cumulative loss up to that point. Read together with the trace, it tells you where a link loses light and whether each part is within your limits.

One trace, one table

A 1310 nm trace from an EXFO MaxTester 730C, 7.502 km long. Point at an event number on the chart or a row of the table to see them linked.

example2-exfo-maxtester730c
  • 1310 nm
  • 10 ns pulse
  • IOR 1.4677
  • 7.50 km
Key events detected in example2-exfo-maxtester730c
#kmTypeLossRefl.
10.000Reflective—-44.96
20.150Reflective0.65-34.81
33.739Reflective—-17.25
43.913Reflective—-57.07
57.328Reflective—-49.86
67.502Fibre end—-39.45

Distance in km from the launch point. Loss and reflectance in dB.

EXFO MaxTester 730C, 1310 nm
Total loss
1.91 dB
ORL
19.9 dB
Events
6

The same events in the viewer’s event table, with each column numbered:

#TypeDistance kmSection kmLoss dBRefl. dBAtt. dB/kmCumulative loss dB
1Reflective0.0000——-44.96—0.00
2Reflective0.15030.15030.65-34.810.6870.76
3Reflective3.73923.5889—-17.250.3221.91
4Reflective3.91250.1733—-57.07—1.91
5Reflective7.32753.4150—-49.86—1.91
6Fibre end7.50180.1743—-39.45—1.91
Event table for EXFO MaxTester 730C, 1310 nm.
  1. Type: what kind of event it is; see event types.
  2. Distance: from the launch point to the event, in km. The launch point is where the measured fibre starts, after any launch cable the instrument was told to skip.
  3. Section: the length of fibre between the previous event and this one.
  4. Loss: the loss across this event alone, in dB. A dash means the OTDR did not measure one, as at the fibre end.
  5. Refl.: reflectance, how much light the event sends back, in dB. Only reflective events have one.
  6. Att.: attenuation of the section before this event, in dB/km. A value with * was measured from the trace because the file did not store one.
  7. Cumulative loss: the fibre and event losses added up from the launch point to this event; see how it is calculated.

Red values are outside your pass/fail limits, and the row number is circled in red.

Event types

TypeWhat it usually isOn the trace
ReflectiveA connector, a mechanical splice, or a break with a clean endA spike up, then a step down
Non-reflectiveA fusion splice, or a bendA step down with no spike
GainerA splice between fibres with different backscatterA step up; the true loss needs a test from the other end
Fibre endThe end of the fibre, or a breakA spike, or a drop to the noise floor

The type comes from the event code stored in the file for every event, for example 1F9999LS:

  • The first character says whether the event is non-reflective (0), reflective (1) or saturated reflective (2, so strong that the receiver was overloaded).
  • The second character says who placed it: F found by the instrument’s analysis, A added or M moved by the user, E end of fibre. Added and moved events are marked Manual in the viewer.
  • The rest is a landmark number, or 9s when no landmark is used.

A gainer is a non-reflective event whose stored loss is negative. It is not a real gain of light: the fibre after the splice simply scatters more light back than the fibre before it.

Reading this example

  • Event 1 at 0.0000 km is the connector at the start of the fibre. Its reflectance is -44.96 dB, well within −35 dB.
  • Event 2 at 0.1503 km is a connector with 0.65 dB loss and -34.81 dB reflectance. Both are above the default limits (0.50 dB and −35 dB), so the connector likely needs cleaning or re-terminating. The section before it is 0.1503 km at 0.687 dB/km: high, but shorter than 500 m, so it is not judged.
  • Event 3 at 3.7392 km reflects strongly (-17.25 dB). A reflectance that high usually means an open or badly mated connector, or an air gap.
  • The sections before events 2 and 3 have an attenuation stored by the OTDR. For the later sections the file stores none, and none could be measured cleanly from the trace, so their Att. is a dash.
  • The cumulative loss reaches 1.91 dB at the fibre end, and the OTDR measured 1.91 dB end to end.

How cumulative loss is calculated

For each event, from the start of the fibre:

Cumulative loss = previous cumulative loss + section length × section attenuation + event loss

The fibre end adds the last section but has no event loss of its own. Sections without a stored or measured attenuation add nothing, which is one reason the result can differ from the instrument’s own end-to-end figure. Cumulative loss vs total loss works through two real files.

Where the values come from

Every value in the table is read from the KeyEvents block of the SOR file, and converted the same way for every brand:

ColumnStored asConverted to
DistanceTravel time in units of 100 psMetres, using the group index; see how distance is calculated
Section–Difference between this event’s distance and the previous one
LossdB × 1000dB
Refl.dB × 1000dB; a few instruments store it as a positive number, and the viewer shows it as negative
Att.dB/km × 1000, for the fibre leading into the eventdB/km; if it is 0 and the section is at least 200 m, it is measured from the slope of the trace and marked *
Cumulative loss–Calculated as above

The SOR file parameters page covers the rest of the file.

Common questions

Why does the first event have a loss, or no loss?

The first event is the instrument’s own connector or the launch point. Some OTDRs measure its loss, some store 0, and with a launch cable it is the connector at the far end of the launch cable. Treat its value as an indication only, unless you tested with a launch cable at both ends.

Why is a connector listed as non-reflective?

A very good connector, such as an angled (APC) one, may reflect so little that the instrument finds no spike and classes it as a splice-type event. Its loss is still checked, against the splice limit.

Why is the loss of the last event missing?

At the fibre end there is nothing after the event to measure a step down to, so the loss is not defined. Its reflectance is still shown.