Fluke CertiFiber Pro and OptiFiber Pro Testing
CertiFiber Pro, OptiFiber Pro and FiberInspector tools answer different questions. OLTS measures end-to-end loss and length, OTDR characterizes events along the link, and inspection determines connector end-face condition.
Treat components, installation and evidence as one system
Choose a supported architecture from application, capacity, environment, pathway, lifecycle and acceptance requirements—not a single part number.
Define the acceptance method
Specify fiber type, connector, wavelengths, reference method, test direction, encircled-flux requirements, polarity and pass/fail budget. Decide whether OLTS alone, OLTS plus OTDR, or additional MPO inspection is required. Do not substitute an OTDR estimate for a specified loss test.
Let the application drive the limit. The optics the client intends to run, the link length and the connector count set the budget the results will be measured against, and the client’s own standard may be tighter. Confirm the test kit carries the right modules, adapters and reference cords for that fiber and connector.
- Fiber and connector type
- Wavelengths and directions
- Reference method and budget
- OLTS/OTDR/inspection scope
Set references and launch conditions
Use qualified reference cords, clean interfaces and perform the documented set-reference procedure. Verify test-reference cords after reference and whenever results become suspect. Configure launch/receive fibers and OTDR settings for the link, connector and event resolution needed.
Reference cords are the component to be strict about. A cord that looks identical can carry a different polish, core size or end-face condition and shift every result taken against it, so buy and retire them deliberately and keep the inspection scope with the kit. Note the polarity and bend limits the reference setup depends on.
- Qualified reference cords
- Set-reference verification
- Launch/receive setup
- Cleanliness control
| Tool | Primary answer | Not a substitute for |
|---|---|---|
| CertiFiber Pro | End-to-end loss and length | Required OTDR event record |
| OptiFiber Pro | Event location and characterization | Specified OLTS insertion loss |
| FiberInspector | End-face condition | Optical performance test |
| LinkWare | Results and reporting | Correct field procedure |
Inspect, test and diagnose
Inspect before every connection, clean correctly and reinspect. Run loss and length at the required wavelengths and directions. Use OTDR traces to locate connectors, splices, bends or breaks and compare events with the as-built route. Resolve negative-loss artifacts and unexpected events rather than hiding them.
Locking limit selection, wavelengths and direction into the tester at the start keeps results on a single basis; changing them mid-job leaves earlier links hard to defend. Save the native tester files and OTDR traces, not only PDF summaries, and flag links passing close to their budget, with unexplained events, for a named owner and a retest date.
- Inspect-clean-inspect
- Loss and length tests
- Event-table/trace review
- Polarity and route comparison
Reconcile records and exceptions
Match every strand, direction and wavelength to the panel schedule. Preserve native LinkWare results and OTDR traces, not only PDFs. Document reference method, instruments, modules, calibration, cords, limits and exclusions so another qualified tester can reproduce the acceptance process.
A strand recorded under one panel ID in the results and another on the field tag is one way a closeout package falls apart. Walk the panel schedule against the saved records, list tester and module serials with calibration dates and the results-software version, and point the client at the manufacturer’s current download page.
- Strand and direction mapping
- Native OLTS/OTDR files
- Instrument/calibration record
- Owned exceptions and retest
How we plan and deliver the work
The final design depends on site conditions, existing systems, client policies and the selected manufacturer or platform.
Pick the test
Decide whether the question is end-to-end loss, event location or end-face condition, then choose the matching instrument.
Set the reference
Set references with the correct method and launch cords, and confirm the tester limits match the link being certified.
Inspect and measure
Inspect and clean each end face, then run the loss or event trace on every link in the schedule.
Reconcile results
Compare results against the acceptance limits, retest failures after cleaning, and note remaining exceptions with their cause.
Information to gather before design
Test results are only meaningful when the acceptance method, limits and reference conditions were agreed before the first link was measured.
- Acceptance standard or limits to apply
- Fiber type and connector style per link
- Link count and end locations
- Whether OTDR traces are required
- File format the owner wants delivered
Frequently asked questions
These are common planning questions. A site-specific answer should be confirmed during discovery and design.
Does an OTDR certify insertion loss by itself?
Use the test method required by the specification; OLTS is normally used for end-to-end loss.
Why inspect before connecting?
Contamination can damage interfaces and create unreliable loss or reflectance.
Should fiber be tested in both directions?
Follow the specified standard, method and event-averaging requirement.
What files should the owner receive?
Native OLTS results, OTDR traces, reports, strand maps and instrument records.
Manufacturer software, firmware and technical files remain on the manufacturer’s official website. We do not mirror firmware files locally.
Set an Acceptance Test Plan for Your Links
When an acceptance limit is never written down, the argument happens after the testing instead of before it. Link count, fiber type, connector style and the standard the project is held to start that conversation, and the reference method and file deliverables get settled before testing begins.