Packets Explorer
Everything JudoNet has stored can be looked at here. This is where you go to answer "what actually happened in that contest?" — after the fact, from the record rather than from memory.
There are three related views, reachable from each other:
| View | Shows |
|---|---|
| Packets Explorer | Individual packets — the raw detail. |
| Packets Overview | One row per display mode per contest, with durations. |
| Contest Times | One row per contest, with the timestamp of each display mode. |
Most questions are answered fastest from Contest Times, which is the summary; the Explorer is where you go when you need the detail behind it.
This page only shows what was stored. If the Store Locally master switch was off, or a scoreboard was disabled, there is nothing here for that period — not because it was lost in transit, but because JudoNet was told not to keep it.
Searching packets
You can search by:
- Contest code — the whole code, or part of it.
- From and To — a time range.
- Last 15 Minutes — a shortcut that fills the range for you. This is the one you want when something has just gone wrong.
The From and To times are in UTC, not your local time. The page says so, and it catches people out every time: in summer a contest at 14:00 local time in central Europe is at 12:00 UTC. If a search returns nothing, check this before concluding the data is missing.
Copying a contest code
Contest codes are shown in a shortened, formatted style so the table stays readable. Click one and the full code is copied to your clipboard — much safer than typing it out.
Deleting packets
There is a delete option that removes everything matching the current filter.
Deleting is permanent and there is no undo.
To make an accidental deletion impossible, you must type a randomly generated number shown on screen before the delete is accepted. That step exists precisely because this is dangerous — if you find yourself typing the number, stop and be sure.
Deleting packets destroys the record of what happened. If the Video CutterV2 has not yet cut those contests, it never will.
Packets Overview
One row per display mode per contest: when that screen appeared, when it ended, and how long it lasted.
This is the view for questions about how a contest was run — how long the introductions took, whether the operator sat on the winner screen, where the time went.
It has the same filters as the Explorer, and the same click-to-copy contest codes.
Delete All Empty removes records whose contest code is empty. Those should not occur; if you see them, something odd happened at the scoreboard.
Contest Times
One row per contest, and the most useful of the three views.
| Column | Meaning |
|---|---|
| Athletes | The white and blue competitors. |
| Mat | Where it was fought. |
| Timestamps | The moment each display mode appeared during that contest. |
These are exactly the timings the Video CutterV2 asks JudoNet for. If a contest looks wrong in the video, this is the page that tells you whether the fault is in the timings or in the cutting.
A Mode 7 timestamp of 0 means the contest has not finished. No winner has been declared yet — either it is still being fought, or the scoreboard operator never moved to the winner screen.
The second case is worth knowing about: a contest stuck without a winner is never marked finished, is never archived, and is never cut into video. If a fight is missing from the video and its Mode 7 is zero, that is the reason, and the fix is at the scoreboard.
Clicking a contest code here takes you to the Packets Explorer, already filtered to that contest.
A practical routine
When someone reports "the video for this contest is wrong":
- Contest Times — find the contest. Is Mode 7 zero? Do the timestamps look sensible?
- If the timestamps are wrong, the problem is at the scoreboard — either its clock or how it was operated. Nothing downstream can fix it.
- If the timestamps are right, the problem is in the cutting, not in JudoNet — see the Video CutterV2 troubleshooting.
- For the full detail, click the contest code to open it in the Packets Explorer.
That order matters: it separates "JudoNet recorded the wrong thing" from "JudoNet recorded the right thing and something later went wrong", which are entirely different problems with entirely different fixes.