72
RANGE: LENGTH
• Too Short: you will not capture the entire ber length
• Too Long: trace will be squashed to left side of Screen
• Good Range: 1.5 to 2 times length of actual ber
PULSE WIDTH:
• Too Narrow: trace disappears into noise oor before end of ber is reached
• Too Wide: events can not be resolved
• Good Pulse Width: Events can be seen and trace is smooth
AVERAGES:
• Too Few: Trace is noisy, trace oor is too high
• Too Many: Trace is smooth but wastes time
• Good Number of Averages: smooth trace
Test in feet or meters?
If you know your ber distances in feet, it may be benecial to measure distances to events/faults
in feet.
Fiber loss specications are given in dB/km. Therefore it is often benecial to measure bers in
meters/kilometers when loss results are required.
A: Yes. In this case, the M310 will add a 0 dB loss event at 1310 and report the new event as a
macrobend, assuming the loss at 1550 nm is ≥0.2 dB.
Q:
How is a micro- or macrobend reported?
A: Micro/macrobends are indicated in the event table with an event type displayed as “ ”.
FAQs
Tips: Expert OTDR Setup
To Next Page
Loading...
Need help?
General
