TraceLogic parses standard .SOR files (the Bellcore SR-4731 standard) plus extended formats from the major manufacturers.
Confirmed supported
- EXFO — including FTBx-735, FTBx-740C, MaxTester, FTB-1, FTB-2, FTB-4 Pro
- Viavi (formerly JDSU) — MTS-2000, MTS-5800, MTS-6000, T-BERD series
- Anritsu — MT9085, MT9090, MU909014
- AFL Telecommunications — Noyes M-Series, OFS series, FlexScan FS200
- Yokogawa — AQ7280, AQ1000, AQ1200
- Fluke Networks — OptiFiber Pro
If your OTDR exports .SOR files following the Bellcore SR-4731 standard, TraceLogic will read them.
What we extract from every SOR file
- All trace events with distances, losses, reflectances
- Pulse width and averaging time
- Wavelength (1310, 1550, 1625 nm — all common variants supported)
- Cable section attenuation
- IOR and range
- Equipment metadata (mainframe ID, optical module, operator)
EXFO-specific richer support
For EXFO files we also parse the proprietary block to extract:
- Direction (A→B vs B→A) — critical for accurate BiDi pairing
- Operator name per direction
- Fibre and cable identifiers
- Location A and Location B
- Test date with timezone
- Pass/fail thresholds set on the device
If you're using EXFO equipment, the dashboard reports will closely match what FastReporter would generate — by design.
File format I don't see
If you have an OTDR not on this list that exports .SOR files, give it a try — most "generic" SOR exports work fine. If you hit issues, email info@tracelogicpro.co.uk with a sample file and we'll take a look.
What we DON'T support
- Proprietary non-SOR formats (some older OTDRs use .trf, .sor.xz, vendor-specific binary)
- Live OTDR control (we're a post-acquisition analysis tool, not a control plane)
- Direct USB/Bluetooth import from the OTDR (use the OTDR's file export to .SOR, then open in TraceLogic — via Files, AirDrop, email attachment, or in-app picker)