Upload robot run data, visualize performance, and diagnose failures.
Built for FLL and LEGO Pybricks teams that want a clearer way to debug drive consistency, gyro behavior, battery sag, and attachment timing from CSV or JSON logs.
Drag in a Pybricks CSV or JSON run log. Required fields are validated before the dashboard opens.
Try the analyzer before collecting your own robot telemetry.
No telemetry loaded yet. Try a demo run or upload a file.
| Step | Start | End | Duration | Warning |
|---|
This is a best-effort diagnosis based on telemetry patterns. Always check the robot physically too.
Some failures look the same in telemetry. A bad start position, a code bug, wheel slip, and a bumped attachment can create similar graphs. Use these notes to capture what a student or coach saw during the run.
Add each robot run, put the missions in the order your robot attempts them, and mark what worked. The app will look for patterns like "everything worked until mission 4" or "the same mission fails every time."
This is not proof. It is a best-effort explanation that combines mission results, telemetry, notes, and repeated patterns.
Paste or upload your Pybricks code in the Codex Prompt tab. These checks look for patterns in the code style and combine them with run outcomes.
Upload your Pybricks robot code here. The app will combine your code, the current telemetry run values, and the diagnosis into one prompt you can paste into another Codex chat that edits or creates your robot code.
This offline page can attach the video file name and your notes to the prompt. It cannot truly analyze video by itself. If the next Codex chat supports video/image uploads, upload the video there too and paste this prompt beside it.
No video selected.