Live data
Live data is the main screen. It shows every device JudoNet can see on the network, what each one is doing, and anything that needs attention.
It is the page to leave open during a competition. Everything here updates by itself.
The page has seven sections, described below in the order they appear: Scoreboards, JudoManager Servers, UDP Send Interfaces, JudoNet Services, FairReplay Recorders, Network Check and Alerts and Errors.
Scoreboards
The scoreboards are where all the data comes from, so this is the section that matters most.
When the service starts, JudoNet listens for scoreboards announcing themselves on the network and lists everything it hears. Scoreboards it has seen before keep the state you last gave them.
A scoreboard JudoNet has never seen before starts out disabled. Nothing it sends is stored or forwarded — you can watch it, and that is all.
This is deliberate. A venue network may have scoreboards belonging to another hall, a spare machine, or somebody testing. Enabling everything automatically would put unwanted data into a live competition.
Enabled and connected are different things
Each scoreboard row shows two things that are easy to mix up. The distinction that matters is that one is something you decide, and the other is something JudoNet reports.
| What it means | Green | Grey or red | |
|---|---|---|---|
| Enable switch — you set this | Whether JudoNet uses this scoreboard's data. Its tooltip reads Enable this Scoreboard / Disable this Scoreboard. | Enabled — data is being stored and forwarded | Grey — disabled, JudoNet is only watching |
| Connection — JudoNet reports this | Whether JudoNet can currently reach the scoreboard. Labelled Connection; it is a dot, and it is not clickable. | Connected | Red — not connected |
So a red Connection dot is a fault — the scoreboard is unreachable. A grey Enable switch is not a fault — it simply has not been enabled yet, which is the normal state for a scoreboard JudoNet has just discovered.
The two combinations worth recognising:
- Enabled, but Connection red — you have switched it on and JudoNet cannot reach it. See a scoreboard appears but sends nothing.
- Disabled, but Connection green — JudoNet is connected and can see everything this scoreboard sends, and is deliberately ignoring all of it. If this mat should be in use, enable it.
That second case is the one that catches people out: everything looks healthy, and nothing is being recorded.
If the Enable switch is faded and will not move, you have read-only access — see access tokens.
What each row tells you
| Part of the row | What to check |
|---|---|
| Mat | Which mat this scoreboard claims. Exactly one scoreboard per mat. |
| Computer name | The scoreboard PC's name. Every PC on the network needs a unique one. |
| Enable switch | Enabled (green) or disabled (grey). This is the control you click. |
i button | Opens the packet detail for the contest running right now. |
| Connection | Green if JudoNet is connected to it, red if not. An indicator, not a control. |
| IP addresses | Every address that scoreboard has. Only one should be selected. |
| Time | The clock on the scoreboard PC. |
| Contest information | The display mode, the clock, the competitors and the scores as they are right now. |
| Connect / Disconnect | Drops or re-establishes the connection to that scoreboard. |
| Remove | Forgets this scoreboard and everything configured for it. Asks first — see Removing a scoreboard. |
Removing a scoreboard
Remove does not simply tidy the list. It discards what JudoNet has stored for that scoreboard — whether it was enabled, and which of its addresses you selected — and it works whether the scoreboard is offline or streaming normally.
It asks before doing anything, and the message says what will happen:
Remove Scoreboard "PC-Mat3"? Its settings are forgotten. If it is still on the network it returns as newly discovered - disabled, and therefore not relaying.
The second half is the part worth reading. A scoreboard that is still switched on announces itself again within seconds, so its row reappears looking present and connected — but it comes back as a newly discovered scoreboard, which means disabled, and a disabled scoreboard relays nothing. Nothing warns you: that mat simply stops being recorded until someone enables it again.
Remove inactive, above the list, does the same thing to every scoreboard that is neither running nor ignored. It also asks first, and tells you how many it is about to forget.
A scoreboard that disappears on its own is not the same thing. One that stops announcing itself is dropped from the list after about a minute, and that keeps its settings — when it comes back it is still enabled and still relaying, with nothing for you to do. Only Remove and Remove inactive forget what was configured.
Two scoreboards on one mat
If two scoreboards claim the same mat, JudoNet shows a duplicate-mat warning.
This has to be resolved, not ignored. JudoNet has no way of knowing which of the two is the real mat 3, so the timings recorded for that mat cannot be trusted. Either change the mat setting on one of the scoreboard PCs, or remove the one that should not be there.
More than one IP address
A scoreboard connected to two networks at once — typically cable and Wi-Fi — announces itself on both, and all its addresses are listed. Select the one on the network JudoNet is actually using.
Turn Wi-Fi off on scoreboard PCs. A scoreboard on two networks is the most common cause of a connection that keeps dropping and reconnecting, because JudoNet and the scoreboard may not agree about which route to use.
Scoreboard time
The scoreboard's own clock is shown here, and it matters: JudoNet records contest timings using times the scoreboard reports. If a scoreboard's clock is wrong, that mat's contests are archived at the wrong moment and the Video CutterV2 cuts the wrong part of the recording.
Sync the scoreboard clocks the day before. They do not need to be perfect — small differences are harmless — but they should not be minutes out.
A scoreboard that stops announcing itself is dropped from the list after about a minute, and an individual address after about 75 seconds. A scoreboard vanishing from the list therefore means it has genuinely stopped talking, not that the page is confused.
How many scoreboards across
The chooser above the list sets how many scoreboards sit side by side, from one to four. It is a maximum, not an instruction: a card needs roughly 450 pixels to show both names, the scores and the clock, so on a narrower window JudoNet lays out fewer columns than you asked for rather than squeezing them until something is unreadable. Widen the window and the rest appear.
The choice is remembered in the browser you made it in, so a second machine watching the same JudoNet has its own.
JudoManager Servers
This section lists the JudoManager desktop machines on the network, and is where you tell JudoNet which competition is running.
Press SELECT on the right server. Only one can be selected at a time; the selected one is marked in blue.
Selecting a server does more than pick a name — it configures JudoNet's API settings to match that server automatically, including whether it uses the JudoManager or Judobase back end. You should not need to touch those settings by hand.
| Column | Meaning |
|---|---|
| Status | Green: connected. Red: not reachable — check the service is running on that PC, and that it answers a ping. |
| Name | The server PC's name. |
| IPs | Every address that server has. |
| Competition | The competition currently open on it. Check this is the right one. |
| Version | The JudoManager version. It should match across all JudoManager machines at the venue. |
| Time sync | Time OK, Sync Time! or TZ mismatch! |
| API interface | JM (JudoManager) or JB (Judobase). Shown for information; set automatically. |
| Delete | Removes an offline server from the list. |
It is normal for several JudoManager servers to appear — any PC running the JudoManager desktop with its service active shows up. At a competition you would normally have one main server and one backup, and select the main one.
TZ mismatch! means the server's time zone differs from JudoNet's, which is a different problem from the clock being wrong. If you correct the time zone on the JudoManager server and the warning persists, the JudoManager service has to be restarted before it takes effect.
UDP Send Interfaces
Every network connection on the JudoNet PC is listed here, and you can switch UDP sending on or off for each.
Most of the time this needs no attention. It matters in one case: at least one interface must have UDP sending enabled or the Broadcast UDP to Graphics and Broadcast UDP to FR switches have nothing to send through, and will silently do nothing.
No alert is raised for this. JudoNet takes each packet off the queue and only then discovers there is nowhere to send it, so the queues themselves empty normally and read zero.
It does now show in one place: the No interface column on Queue Status counts exactly these packets. If CG - JudoGraphics or FairReplay is receiving nothing, check that column, then come back here.
If the JudoNet PC has several network connections — a venue network and a separate production network, say — this is where you stop broadcasts going out of the wrong one.
Open Network Adapters
The button beside this list opens Windows' Network Connections on the JudoNet PC, so you can check an adapter without hunting through Windows settings.
Two things about it look like faults and are not:
- It opens on the JudoNet PC, not on the computer you are browsing from. If you have the page open from another machine, the request is refused and nothing happens. JudoNet will not open windows on a PC at the other end of a network connection, so use it at the JudoNet PC itself.
- It needs JudoNet Monitor running on that PC. JudoNet runs as a Windows service, and a service cannot put a window on screen — it asks the monitor to do it. With the monitor closed, nothing opens.
Like every control that changes something, it also needs you to be signed in.
JudoNet Services
Other JudoNet instances on the network, including the one you are looking at, which is marked Currently Opened.
| Column | Meaning |
|---|---|
| Name / IPs | Which machine it is. |
| Connected? | Whether this is the instance you are viewing. |
| Time sync | Time OK, Sync Time! or TZ mismatch! |
| Connection | Online or offline. |
| Master switches | A tick for each switch that instance has enabled. |
This is the section that catches out multi-JudoNet setups.
If two instances both have Store Online, Display Online, Broadcast UDP to Graphics or Broadcast UDP to FR enabled, the conflicting row turns orange with an asterisk by its name — hover for the detail.
Everything sent twice arrives twice. Fix it by switching the extras off on all but one instance. A backup JudoNet should normally have Store Locally only.
FairReplay Recorders
The FairReplay Recorders on the network, if the venue is using the FairReplay video system.
| Column | Meaning |
|---|---|
| Name / Machine Id / IPs | Which recorder it is. |
| Version | Its software version. |
| Session | The recording session currently open on it. |
| Status | Inputs recording out of inputs open — see below. |
| Time sync | Time OK, Sync Time! or TZ mismatch! |
| Connection | Online or offline. |
The Status figure reads as recording / open, and the colour is what to look at:
| Colour | Meaning |
|---|---|
| Green | Every open input is recording — for example 4/4. All well. |
| Red | Fewer are recording than are open — for example 1/4. Something is not being recorded. |
| Grey | No inputs are open, so nothing is recording. |
A red status here means video is being lost right now. It is one of the few things on this page worth interrupting somebody for, because the recording cannot be recovered afterwards.
Network Check
A graph of how long the venue network takes to reach the outside world. JudoNet pings two well-known addresses every 30 seconds and plots the average.
You can show the last 15 minutes, the last 30 minutes, or everything since the service started.
A flat, low line is healthy. A rising line means the venue's internet is congested or failing, which shows up as data reaching the online platform late — or, if it gets bad enough, as a growing backlog on Queue Status.
This graph measures the internet connection, not the local network. Scoreboards and recorders are on the local network and are unaffected by it. A bad graph with healthy scoreboards means uploads will suffer while local recording carries on normally.
Alerts and Errors
Everything JudoNet has noticed: clocks drifting, devices disappearing, connection failures.
When something is wrong, a red banner appears at the top of the page with a Show Alerts button that jumps here. The banner stays as long as at least one alert is unresolved.
| Icon | Meaning |
|---|---|
| Red circle | Still happening. |
| Green | It fixed itself — for example a scoreboard that dropped out and came back. |
The X at the end of a row acknowledges an alert and removes it from the list. Once everything is resolved or dismissed, the red banner disappears.
An alert leaves with its scoreboard. When a scoreboard is removed — by you, or by JudoNet dropping it after a minute of silence — any alert about it goes from this list too, rather than staying red for a machine JudoNet is no longer watching. If that machine comes back and drops out again, it raises a fresh alert.
Clear the list before the competition starts. Alerts left over from setting up make it much harder to notice something new going wrong during the event.