An open log of what's shipping. The free OTDR tools and field guides get worked on constantly — here's what's new, and a bit of the why.
Everything here is built by a working fiber tech, in the field and after hours. New features usually come straight from a problem on a real job. If there's something you need a tool to do, tell me — that's how most of this got made.
Drop a file that isn't an OTDR trace — like a Viavi loss-test result that shares the same file type — and the analyzer now tells you in plain English what the file actually is and what to open instead, rather than a cryptic error.
New here? Your first custom chart PDF is on us — the discount applies automatically at checkout, no code to remember.
Look up a specific cable size — say an 864-fiber chart — and the builder now opens with that chart already built, so you're one step from your download instead of starting from scratch.
Scan a count sheet with your phone and the page now scrolls straight to your finished chart. A few folks were scanning, scrolling the wrong way, and never seeing the chart they'd built — fixed.
Fix a folder of OTDR files at once: set the cable ID and site names one time and apply them to every file, auto-increment fiber numbers across the batch, rename the files to match their identifiers, and download the lot as a single ZIP. What used to be a one-file-at-a-time slog is now a couple of minutes.
The story behind the trace editor — a real day lost to traces that came back with no cable ID or site names — and how to fix that in your browser instead of retesting. Read it →
The trace editor now edits Cable ID, Fiber ID, and site names in EXFO .trc (AppReg) files and Viavi ONA-800 / T-BERD traces, on top of .sor and .msor. Each format was validated against the real manufacturer software so the edited files open clean.
A cleaner mobile layout for the analyzer and viewer, and every script and library is now served from our own domain — nothing loads from a third-party CDN, so your files and your browsing stay on your device.
What's actually inside a hyperscale data center, and why the splicing and testing work is moving from rural FTTH builds to the data center floor. Read it →