Reference · 8 min read
SOR file parameters explained
A SOR file stores its settings in named blocks defined by Telcordia SR-4731 (the Bellcore OTDR data format). GenParams describes the fibre and the job, SupParams the instrument, FxdParams the measurement settings, KeyEvents the events and DataPts the trace. Most values are stored as whole numbers in fixed units, such as 100 picoseconds for time or thousandths of a dB for loss. This page lists every parameter the viewer shows in its Parameters tab, where it comes from and how it is converted.
How values are stored
- Text fields are fixed or zero-terminated strings. Empty fields, and fields holding only
0(as some instruments write), are shown as a dash. - Numbers are integers with an implied unit. A value of 0, or 65535 in a 16-bit field, means the instrument did not set it, and is shown as a dash rather than as zero.
- Time along the fibre is stored in units of 100 ps (0.1 ns) and turned into distance with the group index; see how OTDR distance is calculated.
- Dates are seconds since 1 January 1970, UTC.
The Acquisition group of a file from an EXFO MaxTester 730C:
Acquisition
- Date
- 2020-06-13 14:12 UTC
- Actual wavelength
- 1312.9 nm
- Pulse width
- 10 ns
- Fibre length (end event)
- 7.502 km
- Acquisition range (scan window)
- 10.000 km
- Sample spacing
- 0.319 m
- Data points
- 31343
- Group index
- 1.46770
- Backscatter coefficient
- -79.4 dB
- Averages
- 1012
- Averaging time (raw value)
- 10
- Launch offset
- 0.0 m
- Noise floor
- -46.12 dB
- Loss threshold
- 0.020 dB
- Reflectance threshold
- —
- End-of-fibre threshold
- 5.000 dB
- Trace type
- ST
- Distance units
- mt
Fibre
From the GenParams (general parameters) block. These are entered by the technician on the instrument, or filled in by the job set-up.
| Parameter | Meaning | Stored as | Shown as |
|---|---|---|---|
| Cable ID | Identifier of the cable under test | Text, cable_id | As stored |
| Fibre ID | Identifier of the fibre within the cable, often a fibre number | Text, fiber_id | As stored |
| Fibre type | ITU-T fibre recommendation | Number, fiber_type, e.g. 652 | G.652; G.652 is standard single-mode, G.657 bend-insensitive, G.655 non-zero dispersion-shifted |
| Nominal wavelength | Wavelength the test was set to | Number in nm, nominal_wavelength | e.g. 1310 nm. Used for the pass/fail attenuation limit |
| Start location | Where the test was launched from, e.g. an ODC or exchange | Text, originating_location | As stored |
| End location | Where the fibre ends, e.g. an ODP or customer | Text, terminating_location | As stored |
| Cable code | Cable type or construction code | Text, cable_code | As stored |
| Operator | Name or ID of the person who tested | Text, operator | As stored |
| Comment | Free text from the instrument | Text, comment | As stored |
GenParams also holds the user offset (the length of launch cable to skip), which the viewer shows as Launch offset in the Acquisition group.
Acquisition
From the FxdParams (fixed parameters) block, plus the user offset from GenParams and the point count from DataPts. These are the settings of the measurement itself.
| Parameter | Meaning | Stored as | Shown as |
|---|---|---|---|
| Date | When the trace was taken | Seconds since 1970, date_time_stamp | 2019-09-30 09:27 UTC |
| Actual wavelength | The laser’s calibrated wavelength | 0.1 nm, actual_wavelength | e.g. 1310.0 nm, or 1551.2 nm for a laser slightly off nominal |
| Pulse width | Length of each light pulse. Short pulses resolve close events; long pulses reach further | ns, pulse_widths_used | e.g. 10 ns, or several values if the file holds more than one |
| Fibre length (end event) | Distance to the fibre end | Calculated from the end event’s time | km, 3 decimals |
| Acquisition range (scan window) | How far the instrument was set to measure, usually longer than the fibre | 100 ps units, acquisition_range | km. Not the fibre length |
| Sample spacing | Distance between two trace points, so the distance resolution of the trace | Time for 10,000 points in 100 ps units, data_spacing | m, e.g. 0.319 m |
| Data points | Number of samples in the trace | Count, in the DataPts block | As stored |
| Group index | The fibre’s group index of refraction (IOR), used to turn time into distance | × 100,000, group_index, e.g. 146800 | 1.46800. If the file has none, 1.468 is used and the viewer says so |
| Backscatter coefficient | How much light the fibre scatters back for a reference pulse; used to work out reflectance | −0.1 dB units, backscatter_coefficient | e.g. −80.0 dB |
| Averages | How many measurements were averaged into the trace. More averages give a smoother trace and a lower noise floor | Count, number_of_averages | As stored |
| Averaging time (raw value) | Averaging time, as an alternative to the number of averages | Defined as 0.1 s units, averaging_time | Shown raw, because instruments do not all use the defined unit |
| Launch offset | Length of launch cable the instrument skips, so that distances start at the fibre under test | 100 ps units, user_offset in GenParams | m |
| Noise floor | Level below which the trace is noise | −0.001 dB, noise_floor_level | dB. Events beyond the point where the trace reaches it cannot be measured |
| Loss threshold | Smallest loss the analysis reports as an event | 0.001 dB, loss_threshold | dB, e.g. 0.050 dB. Smaller splices are not in the event table |
| Reflectance threshold | Weakest reflection the analysis reports | −0.001 dB, reflectance_threshold | dB, e.g. −65.0 dB |
| End-of-fibre threshold | Loss that the analysis treats as the end of the fibre | 0.001 dB, end_of_fibre_threshold | dB, often 3.000 dB |
| Trace type | Kind of trace | Two letters, trace_type | ST standard one-way trace; others mark bidirectional, reference, difference or reversed traces |
| Distance units | Unit the instrument displayed | Two letters, units_of_distance | mt metres, km, ft feet, kf kilofeet, mi miles. Distances in the viewer are always metres and km |
Instrument
From the SupParams (supplier parameters) block, written by the instrument itself.
| Parameter | Meaning | Stored as |
|---|---|---|
| Supplier | Maker of the OTDR, e.g. EXFO, Anritsu, Noyes | Text, supplier_name |
| Mainframe | Model of the main unit, e.g. MaxTester 730C or FTB-4 | Text, otdr_mainframe_id |
| Mainframe serial | Serial number of the main unit | Text, otdr_mainframe_sn |
| Module | Model of the plug-in OTDR module, if any, e.g. FTBx-730C | Text, optical_module_id |
| Module serial | Serial number of the module | Text, optical_module_sn |
| Software | Firmware or software version that saved the file | Text, software_revision |
| Other | Anything else the maker adds, such as a calibration date | Text, other |
The maker and model also appear in PDF reports and in the Summary sheet of an Excel export, so a result can be traced back to the instrument that took it.
File
From the Map block, the Cksum block and the viewer’s own checks.
| Parameter | Meaning |
|---|---|
| SOR revision | Version of the format, e.g. 2.00. Version 2 is used by current instruments; version 1 files are not read yet |
| Blocks | Names of the blocks in the file, in order, as listed in the Map block |
| Proprietary blocks | Number of vendor-specific blocks. They are kept in the file and in JSON exports, but their contents are not decoded |
| Distance check | The viewer compares the slope of the trace with the attenuation the OTDR stored. A ratio near 1.00× confirms the distance scale; files that need it are rescaled ×2 or ×½, with a note |
| Checksum | The CRC-16 checksum stored in the Cksum block. Valid means it matches; not matched is common because instruments compute it in slightly different ways, and does not on its own mean the file is damaged |
Events and trace
The two remaining blocks are shown elsewhere in the viewer:
- KeyEvents holds one record per event (number, travel time, loss, reflectance, attenuation of the fibre before it, event code and comment) plus the end-to-end loss and optical return loss of the whole fibre. See the OTDR event table explained.
- DataPts holds the trace: the number of points and one value per point, in units of −0.001 dB (scaled by a stored scale factor). The viewer draws it as the trace and the Excel export can list it point by point.
Corrections the viewer may apply
When a file is incomplete or uses an unusual convention, the viewer corrects it and says so in a note at the top of the Parameters tab:
- No group index: 1.468 is used.
- A time scale that does not match the stored attenuation: distances are scaled ×2 or ×½.
- Reflectance stored as a positive number: shown as negative dB.
- Attenuation stored as 0 on a section of 200 m or more: measured from the trace and marked
*.