Direct answer
Select OTDR pulse width for both reach and separation of nearby events, not simply the largest or smallest setting. Distinguish event and attenuation dead zones, retaining the actual setup and raw trace. Detecting two events does not establish that both losses can be independently quantified.
Definition: detection and loss measurement are different capabilities
Fluke Networks distinguishes event and attenuation dead zones and notes that specifications are given under stated pulse-width and reflectance conditions. Fluke dead-zone explanation
When purchasing an OTDR or reviewing an outsourced report, compare those conditions rather than only the shortest advertised dead-zone number. That number must not be applied unconditionally across a complete channel.
Pulse-width trade-offs and applications
Fluke's settings guide explains that a narrower pulse can reveal nearby events while limiting measurement reach. Its troubleshooting guide describes the trade-off between broader pulses for longer observation and larger dead zones. Fluke settings guide, Fluke troubleshooting guide
Use this review for short cabinet cords, channels with several patching points, and projects using one instrument for both short and longer routes. This guide deliberately supplies no universal nanosecond setting or minimum separation. Select parameters for the actual instrument, channel and task.
Short-link report review table
The table is a suggested procurement and acceptance framework, not guaranteed performance for any instrument.
| Task | First review | Do not infer | Suggested evidence |
|---|---|---|---|
| Separate adjacent connections | Actual pulse and reflective conditions | Two event rows mean two accurate losses | Raw trace and close-up |
| Quantify each connection | Usable backscatter before and after | Located means independently quantified | Measurement boundaries |
| Observe the complete route | Far-end signal and selected settings | The shortest pulse covers the route | Range and averaging time |
| Assess end connections | Actual launch and receive setup | Any short jumper is sufficient | Length, fiber and compensation |
| Compare reports | Wavelength, direction, settings and state | Results are automatically comparable | Setup and change record |
| Decide acceptance | Project limits and method coverage | Auto-pass includes unresolved events | Criteria and unassessed items |
Report unresolved events honestly
Draw the physical channel connections and reconcile them with the event table. If two connections have not been independently evaluated, mark them as not independently quantified. Do not split a combined result into invented individual values.
Where closer observation is needed, follow the instrument instructions when adjusting settings and retain both raw traces. If changing pulse width changes the conclusion, record why and which assessment method was used. Keeping only the more attractive result conceals the review boundary.
Retain the instrument-readable original and an accessible review output. The purchaser need not manually interpret every trace, but should be able to identify its channel, direction, setup and any connections needing additional evidence.
Launch and receive fibers are not a length-only purchase
Fluke describes launch and receive fibers as providing observation conditions around the first and last connections. Fluke troubleshooting guide
Review a proposed test assembly together with the intended OTDR setup rather than buying a fixed length in isolation. Identify fiber, interfaces, actual length, compensation boundaries and target channel. An appropriate launch setup does not establish independent quantification of every close-spaced connection farther along the route.
A minimum acceptance record package
Propose collecting the channel drawing, instrument and relevant versions, wavelength and direction, pulse width, averaging time, range, launch/receive setup, raw trace, event table, criteria and unassessed items. Where the contract also requires total insertion-loss acceptance, use the agreed method rather than substituting an event map alone.
These fields make evidence reviewable. They do not extend an instrument's capability or establish a new test requirement. Match the final method to the project's acceptance objective.
Procurement FAQ
- Does a short event dead zone guarantee accurate short-cord loss? No. Review attenuation dead zone, reflective conditions and measurement boundaries as well.
- Is the shortest pulse always best? No. Balance far-end observation with separation of nearby events.
- Can automatic mode support acceptance? Use it under the approved method, retaining actual settings and coverage rather than only a pass screenshot.
- Does a clean-looking trace prove every connection passed? Do not extend the conclusion that far. Confirm which target connections were independently assessed.
- What should a launch-assembly RFQ contain? Instrument, target channel, fiber and interfaces, intended settings, end-connection objectives and compensation boundaries.
Related configurations and guides
- OTDR launch assembly configurations
- Test reference-cord configurations
- Launch-fiber length review
- OLTS/OTDR acceptance boundaries
- Dual-wavelength bend investigation
Related product pages are configuration-review entry points, not evidence of stock or validated performance.
Sources and review boundary
- Fluke Networks: event and attenuation dead zones
- Fluke Networks: OTDR test parameters
- Fluke Networks: Troubleshooting Fiber
Sources checked on 2026-10-09. Manufacturer examples apply only to the cited products. Procurement tables and RFQ wording are suggested review frameworks, not quotations of mandatory standard clauses or ARRANEX qualification claims.
Sources checked: 2026-10-09