Direct answer
OTDR ghosts can result from repeated travel between strong reflections, showing events where no physical connection exists. Distance multiples, peaks and loss behavior are clues, not independent proof. Review the real span, test connections and raw trace, resolve the reflection cause and retest.
A displayed peak may have no physical counterpart
VeEX's official knowledge base describes echoes caused by pulses repeatedly traveling between strong reflections. EXFO's trace-reading guide illustrates a possible echo at a multiple distance.
This matters in short-assembly tests, preterminated receiving inspection and maintenance. A false position can misdirect investigation or affect the event table. Review the physical diagram and raw trace, not only an automatically analyzed screenshot.
Signs requiring investigation
| Observation | Possible explanation | Additional evidence |
|---|---|---|
| Regular-distance peaks after a strong reflection | Repeated-travel echo | Distance datum and reflection-source positions |
| Peak beyond the physical span end | Out-of-span ghost or range-definition issue | Confirmed end, receive lead and full view |
| Reflection without corresponding loss step | Possible echo | Local trace and other-direction results |
| Software “possible echo” label | Algorithmic candidate classification | Raw data and human analysis |
| Peak with substantial loss or a physical joint | Potential real fault | Joint map, retest and location record |
These are clues. VeEX notes that out-of-span ghosts can show measurable loss, so loss presence alone does not prove a physical event.
Twice the distance is a simplified case
EXFO describes an additional round trip between the OTDR and a strong connection, producing an apparent event at twice the distance. As a calculation example, a main reflection at 100 m under one distance datum can produce a candidate echo around 200 m.
This is a hypothetical propagation example, not a measured installation. Multiple reflection sources make the geometry more complicated. Establish where the 100 m starts and whether launch fiber is included. Do not delete every 200 m peak.
Investigate in a controlled sequence
Isolate service sources under the equipment procedure, confirm ports and test leads, then inspect connections according to their instructions. Record cleaning, damage disposition or mating corrections and the retest. Do not mix APC and UPC or change interface types without approval.
| Sequence | Action | Retained evidence |
|---|---|---|
| Establish span | Check the diagram and physical end; expand the trace view | Span, launch and receive definitions |
| Review access | Verify ports, connectors, reference leads and mating | Tool and lead identities |
| Resolve reflection source | Inspect, clean or replace under the approved process | Before-and-after state |
| Retest | Keep comparable settings; use the other end when appropriate | Raw traces and parameters |
| Review events | Compare physical joints and retest changes | Classification rationale and disposition |
Hiding an event in software changes presentation, not the physical cause. Purchasing needs evidence from the retest.
Deliver an auditable report
Include assembly identity, direction, wavelength, distance settings and added test leads. Preserve original files and explain pulse-width or analysis-threshold changes.
When an echo is established, state the evidence. If unresolved, mark it for investigation and define the next check. Do not use “ghost” to dismiss a real high-reflection source. Final acceptance still follows approved loss, reflectance and mapping requirements.
Procurement FAQ
- Does a peak beyond the end prove a longer cable? Review the physical end, range and echo geometry first.
- Can a no-loss event be deleted immediately? It is a clue requiring a map, geometry and retest.
- Can automated analysis identify every ghost? Manufacturer information identifies possible misclassification; review raw traces.
- Is the issue fixed if a wider pulse hides the peak? Visibility changes do not establish that the cause was removed.
- May a report omit ghosts? Follow approved classification rules while retaining raw evidence and reasons; do not hide unresolved faults.
Related products and reading
- OTDR pulse width and dead zones
- OTDR distance datums
- OTDR launch-cable configuration
- Test reference cords
Product pages describe configuration scopes. Actual supply, drawings and performance require project confirmation.
Contact an engineer
Prepare interface drawings, port requirements or existing test records and contact an engineer to discuss fiber-assembly configuration and verification.
Sources and review date
Sources checked on 2026-10-14. Third-party references explain technology and specified configurations, not ARRANEX performance or certification. Purchasing tables are review recommendations; worked examples use stated assumptions.
Sources checked: 2026-10-14