Fiber Testing Field Guide

Why we test fiber

Before you ever pick up an OTDR, you need to know why you're testing. It sounds obvious, but it's the thing new techs skip, and it's the thing that determines everything else you do that day. The reason you're out there decides which tests you run, which direction you shoot, how careful you have to be with your numbers, and what counts as a pass. Show up without knowing the why and you'll either over-test a simple job or under-test one that mattered.

Here are the reasons we go out and test, and what each one actually asks of you.

Finding damage

There's an outage. A fiber's cut, maybe a contractor put a backhoe through it, maybe a storm took down a span. The network's down and the clock's running. Your only job here is distance. You need to know how far it is to that cut so you can dispatch a crew to the right spot and get it repaired. You're not chasing pretty numbers, you're not running the full battery. You shoot one direction, you read the distance to the break, you call it in. Fast and dirty is the right move.

Acceptance testing

This is where you prove the work was done right. The construction crew, the installers, the splicers all did their job, and now you're the one showing the engineering team that the fiber meets spec and is ready to go into service. This is the full battery and it's where you slow down and get it right. Every number matters here because your signature is what puts the link in service.

Incoming reel testing

You've got a new reel of cable that needs to be checked before it goes in the ground. This is a simple one. You're confirming the cable's good, the length matches the reel tag, and nothing got damaged in shipping or handling. You want to catch a problem now, while the cable's still on the reel and easy to deal with, not after it's plowed in and spliced.

Troubleshooting degraded service

This one's different from a hard cut. The fiber's still lit, the customer's still up, but something's wrong. High error rates, intermittent drops, a link that passed at turn-up and is slowly getting worse. You're hunting a soft fault, reflectance creeping up at a connector, a macrobend where somebody stepped on a drop, water working its way into a splice. This takes more patience than a clean cut because the trace doesn't hand you the answer.

Restoration verification

After a repair, you shoot the link again to confirm the new splice is in spec before you close the job. Some techs fold this into acceptance testing, but in the field it's its own moment, and it's worth treating that way. Don't pack up until the repair reads clean.

Baseline documentation

This is the one techs skip and regret later. At turn-up, you shoot a clean reference trace and you keep it. Two years from now when something drifts, that baseline is what you compare against. Without it you're guessing whether that 0.3 dB event was always there or showed up last week.

The tools and tests, and when each one earns its keep

You've got a range of tools, and part of being good at this is knowing which one the job actually calls for. Pulling out the OTDR for every task is like grabbing a torque wrench to hang a picture. Here's what's in the kit and when each one is the right call.

Red light test (visual fault locator)

The simplest test there is. You shine a red laser down the fiber and look at the other end to see if it comes through. If light comes out the far end, you've got continuity. It's also great up close for finding a break or a bad bend in a patch cord or a splice tray, because the light leaks out red right at the fault and you can see it with your eye. No numbers, no loss measurement, just a yes or no on continuity and a quick way to eyeball a problem you can get your hands on. Keep one in your pocket.

Light source and power meter

These are two separate instruments, and on their own they're your everyday field loss tools. You put a known light source on one end of the fiber and read the power meter at the other end, and the difference tells you the loss. It's manual, it's often a two-tech job with one person at each end, and it's the right tool for a quick single-wavelength loss check, troubleshooting a span, verifying a patch cord, or confirming continuity when you want a real number and not just a yes or no.

One method worth knowing, especially on fiber-to-the-home builds: you can put a light source on a dark network to simulate light, then walk the power meter to the terminals and verify loss at each one. On an FTTH build there's often no active light on the network yet because the techs are still splicing it together, so there's nothing live to measure against. Dropping a source on at the head end gives the splicing crew something to read against at the taps and terminals as they go, so they can confirm their work before the network's ever turned up.

OLTS (optical loss test set)

This is the same idea taken up to certification grade. Technically an OLTS is still a light source and a power meter, but instead of two loose instruments and two techs, it's a pair of integrated units that talk to each other. They handshake, run the test bidirectionally, hit multiple wavelengths automatically, store the results, and give you a documented pass or fail against a loss budget. This is the acceptance-grade tool. When you need the true end-to-end loss and ORL on a link you're putting your name to, this is what you reach for.

The OLTS measurement is the accurate one for both loss and ORL, and here's why. You're sending from one unit and measuring on a separate unit at the far end, so you're reading the light that actually made it all the way through the fiber. That's a true, direct measurement of what the link delivers. The OTDR, by contrast, never gets a real signal to the far end and back. It measures the light that reflects and scatters back to the OTDR and calculates loss from that return. It's a clever measurement and an incredibly useful one, but it's an inference, and inferences can be fooled. When you need the real loss and ORL numbers, the OLTS is the one to trust.

OTDR

This is the one that maps the whole link. Instead of just giving you a single end-to-end loss number, the OTDR sends pulses down the fiber and listens to what comes back, and from that it builds a picture of every event along the span, every splice, every connector, every bend, and tells you where each one is and how much loss or reflectance it has. This is what locates a fault, characterizes every splice, and shows you the shape of the link. It's the most powerful tool in the bag and also the easiest one to misread, which is why so much of this guide is about how to actually interpret what it shows you.

Traffic identifier

This clamps onto a bare fiber and tells you whether there's live traffic on it without breaking the connection. Two big uses. First, before you cut or disconnect anything, you clamp it on to make sure you're not about to take down a live customer. Second, paired with a light source, it's how you find the right fiber in a fat bundle. You put a tone or a signal on the source end, walk to the other end, and clamp around fibers until you find the one carrying it. Saves you from guessing and from cutting the wrong strand.

Why OLTS and OTDR go together for acceptance

Here's the thing a lot of techs miss. The OTDR and the OLTS don't measure the same thing, and one can pass while the other fails. The OLTS gives you the true end-to-end loss and ORL because it's an actual source-to-meter measurement, while the OTDR's numbers are built from the light reflecting back to it and can be thrown off by things like mismatched fiber or gainers at a splice. For acceptance testing you run both, because the OLTS confirms the link's real loss budget while the OTDR proves every individual event along the way, every splice, connector, and bend, is in spec and where it should be. A pass on one is not a pass on the job.

CD and PMD (chromatic dispersion and polarization mode dispersion)

These two only come up on long-haul, high-speed routes, and as a field tech you may never touch them, but you should know what they are and why the engineers ask for them. Chromatic dispersion is the spreading of the light pulse over distance because different wavelengths travel at slightly different speeds. PMD is a similar smearing caused by the fiber's own imperfections and stress affecting different polarizations of light. On a short link none of this matters. On a long, fast link it absolutely does, because too much of either one blurs the pulses into each other until the receiver can't tell them apart. The engineers use CD and PMD numbers to pick the right optics for the route, deciding what data rates the fiber can support and whether they need compensation built in. You're gathering the data; they're making the optics decision off it.