PlotJuggler use cases and workflows: PX4 ULog flight analysis, robot debugging, run-to-run regression comparison, telemetry review and hardware signal correlation.
This site’s top bar has promoted a small USB logic analyzer alongside PlotJuggler for a while, without ever explaining why the two belong in the same sentence. This post is that explanation. The short version: robot logs tell you what the software believed happened, and a logic analyzer tells you what the hardware actually did…
You are a test engineer. A subsystem test finished an hour ago, the results sit in files — a CSV export here, a ULog there, an MCAP recording from the rig — and someone needs a verdict before the next test slot. The usual detour is Python: load each file, remember each format’s quirks, write…
“Did the firmware change make the robot better or worse?” is one of the most common questions in robotics — and one of the worst answered, because the before and after runs usually live in different files, recorded at different times, and get eyeballed in different tools. PlotJuggler 4 was built with this comparison in…
Most robot bugs are not found by staring at code. They are found by watching what the robot actually did — which means a recording, a timeline, and a disciplined way of moving from “it behaved strangely” to the minute, then the second, then the signal where behaviour diverged. This workflow uses PlotJuggler as the…
After a PX4 flight, the fastest honest route from “something felt wrong” to a cause is a repeatable post-flight workflow in PlotJuggler: load the ULog file, plot the signals that describe that kind of problem, derive the quantities the raw log does not show directly, and save the view so the next flight is reviewed…
Analyze hardware signals like a pro. DSLogic is the perfect companion for PlotJuggler.