PLC Splitter PDL: Build a Polarization Acceptance Test

Summary: A PLC splitter polarization dependent loss test changes the input state of polarization while measuring each output channel, then reports the maximum insertion-loss variation over the sampled states. The test must cover the specified wavelength range and every required channel; one favorable polarization state is not enough.

The sample measurements below are hypothetical. They illustrate calculation and record design, not Liqiba factory data or a product guarantee. Use the purchase specification and the applicable standard edition for acceptance.

Define PDL separately from insertion loss and uniformity

Insertion loss describes optical loss under stated conditions. Uniformity compares output channels. Polarization-dependent loss, or PDL, is the change in insertion loss as the input state of polarization changes. A splitter can have acceptable average loss yet excessive PDL on one channel.

ITU-T G.671 defines optical-component parameters including PDL and provides application-related values for PON branching components. Values in a standards table belong to its stated application and conditions; they are not automatically the purchase limit for every splitter.

Create the measurement chain

Use a stable source, polarization controller or scrambler, reference path, compatible connectors and a calibrated detector system. Allow the equipment and device to stabilize. Clean and inspect interfaces, prevent cable movement during the scan, and keep launched power within the linear range of every detector.

A continuous polarization scan is preferable to a few arbitrary manual states because the true maximum and minimum may lie between them. EXFO’s component-test platform describes simultaneous insertion-loss and PDL measurement over wavelength, illustrating the type of controlled method used for component characterization.

Calculate every channel before summarizing

For one output channel at one wavelength, PDL equals the largest measured insertion loss minus the smallest measured insertion loss across the polarization states. Retain the channel result with the raw extrema and scan information. Do not average all channels first; that can hide a single failure.

Our PLC splitter uniformity guide explains channel spread, while the cascaded splitter budget guide shows how component losses accumulate in a network. PDL is an additional uncertainty contributor, not a replacement for either calculation.

Set coverage and decision rules

Specify connectorized or bare-fiber reference planes, wavelengths, optical band, scan method, detector range, temperature, sample plan and channel-level limit. For broadband qualification, a result at one wavelength cannot represent the entire passband.

Estimate uncertainty from source stability, reference repeatability, connector reconnection, detector linearity and polarization coverage. Define a guard band when results near the limit require a conservative decision. A rounded display value should not determine acceptance if the unrounded result and uncertainty change the conclusion.

Worked channel-level PDL worksheet

Assume a 1×4 splitter is scanned through a validated set of polarization states at one specified wavelength. The table lists hypothetical minimum and maximum insertion loss for each channel.

If a hypothetical channel limit were 0.20 dB, channel 3 would require disposition. That limit is only an example; use the agreed specification, band, temperature and uncertainty rule.

Turn the method into a procurement specification

A useful request for quotation identifies the application, fiber type, connector or cable construction, operating wavelengths, environmental range, installation method and the evidence required at delivery. It separates mandatory acceptance limits from preferences. Asking only for “high quality” leaves supplier and buyer with different interpretations; a measurable requirement gives both parties the same decision point.

Record units, reference conditions and rounding rules. State whether a value is maximum, typical or informational, and whether it applies to every unit, a sample or a type test. Where a standard defines a method but the project chooses the limit, cite both separately. The project owner should resolve conflicts among the drawing, purchase order, product data sheet and field procedure before work starts.

For relevant products, use the commercial PLC splitter manufacturer page. Send the route, interface or test details with the inquiry so the proposed construction can be checked against the actual application rather than selected by a generic label.

Build an auditable acceptance record

The record should connect the asset identifier to the instrument, settings, operator, date, reference method and result. Preserve native test files when the instrument creates them; a screenshot alone can hide settings or event detail. Photographing labels and end positions can reduce later ambiguity, but photographs do not replace optical or mechanical evidence.

Use a defined disposition for a result near or beyond the limit: verify identification, inspect the setup, repeat only under the written repeatability rule, and then accept, rework or escalate. Do not keep testing until one favorable reading appears. If uncertainty is material, use a guard band or engineering review established before testing.

After installation, keep the approved design value, as-built value and any deviation together. That baseline supports troubleshooting after moves, adds or environmental changes. It also prevents a later team from treating a planning calculation as factory data or a field observation as a universal product specification.

Common mistakes to prevent

Do not rotate one patch cord by hand and call the resulting variation a complete PDL test. Avoid unstable source power, detector saturation, dirty connectors and moving fan-out fibers during the scan. Do not report only the best channel or an average that conceals the worst output.

Another frequent error is copying a number from a different cable, splitter, connector or instrument. Manufacturer limits depend on construction and test conditions. Confirm the exact data sheet and revision. When a worked value in this article is used, retain its assumptions and replace them with project values before making a purchase or acceptance decision.

Finally, keep safety and handling instructions in the work package. Optical fibers create sharp fragments; live systems may carry invisible radiation; pulling and test equipment can store mechanical energy. Qualified personnel should follow the site procedure, product instructions and applicable regulations.

Use a pre-work review and hold point

Before installation or testing begins, review the latest drawing, bill of materials, product revision and acceptance procedure with the people who will perform the work. Confirm which document controls if values disagree. Assign a unique identifier to the link or component and place that identifier on the worksheet, instrument file and any photograph. This prevents a technically correct result from being attached to the wrong asset.

Create a hold point before concealed work is closed or an irreversible change is made. Check the physical routing, labels, connector condition, test reference and recorded settings. If the result is abnormal, pause while the relevant section remains accessible. The hold point should identify who can release the work and what evidence is required.

Evaluate changes after delivery

Transport, storage and installation can change condition after a supplier’s outgoing inspection. Define which checks occur at receipt, before installation and after completion. Keep packaging damage, seal condition and storage observations with the receiving record. Do not treat a factory certificate as proof that later field handling caused no change.

When a repair, reroute or replacement occurs, update both the technical record and configuration drawing. Reuse the same measurement method where practical so results remain comparable. If a new instrument or procedure is necessary, document the difference instead of presenting unlike measurements as a continuous trend. A clear change history makes future fault isolation faster and supports fair supplier discussions.

Archive superseded worksheets without deleting them, mark the approved revision clearly, and give field teams read access to the version that governs their work.