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 | ΔT: how far that scoreboard's clock differs from JudoNet's — see Scoreboard time. |
| 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 not currently sending packets and not ignored. It also asks first, and tells you how many it is about to forget.
A live connection does not make a board safe, and a dropped one does not put it at risk. What is tested is whether a packet has arrived in the last four seconds — a board sends about five times a second, so four seconds is twenty missed sends — and not whether the connection is up.
- A board whose connection dropped a moment ago but was sending is kept.
- A board holding an open but silent connection is forgotten.
The second case is the one to watch, because that row looks connected right until it is removed. The rule is about data arriving, not about the connection: a mat that is quiet is a mat that is not being recorded, whatever its connection light says.
Read the count carefully, because nothing here tells you which boards. The confirmation gives a number, not a list, and there is no per-board indicator for whether packets are arriving — the connection light is deliberately not that signal. The closest thing is the alert for a board that is reachable but sending nothing, and that appears only for boards that are enabled and not ignored, so a board you have disabled and which has gone quiet shows nothing at all — and that is exactly the board this button takes.
A disabled board receives and then discards. The packets arrive and are counted — the Connection dot stays green and the i packet detail keeps filling in — and only afterwards is everything done with them skipped: nothing recorded, nothing relayed, nothing sent on. So a disabled board looks entirely alive here while storing and forwarding nothing, which is the trap described above seen from the other side. Arriving is the only thing this button tests, so a disabled board that is connected and sending is kept like any other. It is the disabled and quiet one that has no indicator anywhere and is removed regardless.
If the number is higher than the count of mats you know to be idle, cancel, and find out which one it means before pressing it again.
A scoreboard that disappears on its own is not the same thing — for a month. 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.
After a month away, it is forgotten from disk as well. It then returns as a newly discovered scoreboard — disabled, and therefore relaying nothing — exactly as if someone had pressed Remove. The same month applies to a single address: one not seen for a month is dropped from a scoreboard whose other addresses are untouched. That is a narrower thing than the whole record being forgotten, and it can happen to a scoreboard that has otherwise been working all along.
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.
An address that has dropped to the back of the queue
If an address is dialled for ten minutes with nothing accepting a connection there, it is set aside: JudoNet stops preferring it, and dials it only when no other address of that mat is left to try. After thirty minutes it returns to the ordinary rotation. In the address list it appears struck through and red, and hovering it gives the reason:
Nothing is accepting a connection at this address, so it is only tried when no other address is left.
The strike-through lifts when the address is next actually tried, normally within seconds of those thirty minutes. It can be later: while a mat is connected on one of its addresses JudoNet does not dial the others at all, so an address still marked after thirty minutes is not a board to go and check — it is one JudoNet has correctly not tried yet, because it is busy reading the mat.
An address that worked earlier can be set aside. What is measured is an unbroken run of ten minutes of dialling that nothing answered, so the clock starts afresh every time the address does answer. A mat that was being read all morning and stops being read after lunch has its address set aside ten minutes later, exactly as an address that never worked would — which is what lets the rest of this page's recoveries reach it. Until August 2026 one connection exempted an address for as long as JudoNet kept running, and the mat that broke mid-competition was the one case none of them could help.
Set aside is an ordering, not a ban. JudoNet never stops dialling a mat that has an address at all. A set-aside address is still dialled when there is nothing better — see When every address of a mat is set aside — because a contest that is not relayed cannot be relayed afterwards.
The tick is the part to read carefully. A set-aside address is still selected — nothing has been disabled and there is nothing to re-enable. An address you unticked yourself looks similar, because it is also red, but it is not struck through. That strike is the whole difference: red on its own only means "not the address the connection is on". An unticked address shown in italics is a third case, described under An address JudoNet dials although you unticked it.
Waiting is the right response. The recovery is automatic, and a board whose websocket server came up late is picked up without anyone restarting JudoNet. Ten minutes is far longer than any handshake and falls inside the warm-up before an event, so a board that is merely slow to start serving will not trip it.
What setting an address aside is for is speeding up the ones left. JudoNet dials one of a board's addresses every five seconds and takes them in turn, so on a board with three enabled addresses each is tried only once every fifteen seconds. An address that has been set aside drops out of that rotation while any other address is available: once two dead addresses are out of the way, the remaining one is tried every five seconds instead of every fifteen, and reconnects sooner because they stopped taking their turn. That is the practical cost of leaving addresses enabled that a board cannot be reached on — they take their turn anyway — and the reason for selecting only the address JudoNet is actually using.
That is also the whole of the gain, and it is why setting an address aside stops short of a ban: there is nothing to speed up on a mat with no other address to give the ticks to.
The same event is raised in Alerts and Errors, naming both the board and the address:
Scoreboard 'PC-Mat7': address 172.20.1.242 has been dialled repeatedly with nothing accepting a connection there, so it has been set aside for now. Check the board is running and reachable at that address.
This is a different thing from the month-long forgetting described under Removing a scoreboard. That expires an address by the calendar and takes it off the mat's address list; setting one aside changes only the order it is dialled in, is measured in dials rather than days, and is undone the moment something answers there.
An address JudoNet dials although you unticked it
If no ticked address can be reached, JudoNet dials the unticked ones too rather than leaving the mat unread. The address appears in italics, and hovering it says so:
Being dialled although switched off: no address that is switched on could be reached, so this one is being tried. Your setting has not been changed.
The same thing appears in Alerts and Errors, so it is visible without opening the mat card:
Scoreboard 'PC-Mat7': no address that is switched on could be reached, so address 172.20.1.243 is being dialled even though it is switched off. Your setting has not been changed; tick it if you want it dialled normally.
Your setting really is untouched. The checkbox stays clear, and what JudoNet has recorded about that address is unchanged — this is a response to a mat nobody is reading, not a decision JudoNet has made on your behalf. As soon as a ticked address can be reached again, JudoNet goes back to using it and the italics and the alert row both come off.
Why it exists. A scoreboard PC travels between venues and its address changes with the network it is on. An address you sensibly unticked at one venue — the wrong network there — can be the only address the board answers on at the next one. Without this, JudoNet would honour that decision at every venue for ever, dial nothing that works, and the mat would never be read, with nothing on screen explaining why: a board listed, discovered and silent. A contest that is not relayed cannot be relayed afterwards.
When it happens. Two ways, and the second is the fast one:
- Every ticked address has been dialled for ten minutes without anything accepting a connection, so all of them are set aside — the case described in the previous section. If the unticked addresses are dead too, see When every address of a mat is set aside.
- The board announces itself from an unticked address, and JudoNet has not reached that mat on any address since it started. JudoNet acts on the announcement on its next dial, within seconds, rather than waiting out the ten minutes. This is the usual case when setting up at a new venue, and it is deliberately limited to it: once a mat has been reached, an address that announces itself is worse evidence than the address that was carrying data a moment ago, and jumping to it would abandon a board that is merely between contests. A mat that was working earlier and then stopped therefore takes the ten-minute route above, not this one.
What to do about it. Tick the address if it is the one you want used — that is the tidy end state, and it stops the alert. If it is not, find out why nothing answers on the address you did tick; the italics are telling you that address is not working, as much as they are telling you about the one being dialled instead.
An unticked address being dialled is still set aside after ten minutes if nothing accepts a connection at it, exactly as a ticked one is, and drops behind the others in the same way. That is not reported as a problem with your setting, because it is not one — it is the only case where an address is set aside and you are told nothing about it.
When every address of a mat is set aside
Ten minutes of dialling with nothing answering anywhere leaves a mat with every address set aside, ticked and unticked alike. JudoNet goes on dialling them. With nothing better to prefer it works through the set-aside addresses instead — ticked ones first, unticked ones only if the mat has no ticked address at all — so a mat that has any address is always being dialled, and a board that starts serving is picked up within seconds rather than after a wait.
Until August 2026 this was the one case where JudoNet stopped: a mat in this state was dialled nothing at all for thirty minutes. Mid-contest that is unrecoverable, and it is why the behaviour changed.
The mat card shows every address struck through, and Alerts and Errors carries one row for the mat:
Scoreboard 'PC-Mat7' has not been reached: every one of its addresses has been dialled and nothing accepted a connection. JudoNet is still trying. Check the board is running and reachable at the address shown.
If the mat has no ticked address, you get the message about that instead, because ticking one is still the useful thing to do:
Scoreboard 'PC-Mat7' is not being dialled: none of its addresses are enabled. Tick one in its address list to connect it.
What to do about it. This one is about the board, not about JudoNet's settings: nothing is listening on any address the mat knows. Check the scoreboard software is running, check the machine is on the same network, and check the address it actually has now — see Troubleshooting. The strike-through on every row is telling you the addresses have all been tried, not that JudoNet has given up.
A different scoreboard at the same address
JudoNet recognises a scoreboard by its machine id, not by its address. So if a packet arrives from a known address carrying a different machine id — a scoreboard PC that was replaced or reimaged and kept the old address — JudoNet treats that as the machine at this address having changed.
What follows is deliberate and complete. The old scoreboard is dropped from the list, its connection is closed, and what was stored for it is forgotten. An error is recorded against it first:
Different MachineId detected on this IP. Expected 1a2b3c4d, received 9f8e7d6c.
The replacement then appears as a newly discovered scoreboard — disabled, and therefore relaying nothing — until someone enables it.
Swapping a scoreboard PC and keeping its address is not a transparent replacement. The old row vanishes, a new disabled row takes its place, and that mat is not recorded until it is enabled. This is the same ending as Remove, reached without anyone pressing anything.
Scoreboard time
ΔT is not the scoreboard's clock. It is the difference between that scoreboard's clock and JudoNet's own, in seconds, and the dot beside it is green while the difference is under 0.8 seconds. TZ mismatch! on a row is the separate case of a scoreboard announcing a different time zone than JudoNet's.
Neither affects what JudoNet records. Every packet is stamped with JudoNet's own clock at the moment it arrives, and everything JudoNet reports is derived from that stamp — the start and finish of each contest, the moment a contest is archived, and what the Video CutterV2 cuts. A scoreboard whose clock is minutes out still produces perfectly correct contest times; its ΔT goes red, and nothing else changes.
So the clock that has to be right is JudoNet's, and JudoNet looks after that one itself — see Time, and why it matters so much.
Sync the scoreboard clocks the day before anyway. Nothing downstream of JudoNet depends on it, but a red ΔT on every mat is noise you will have to look past when something real goes wrong, and each packet carries the scoreboard's own timestamp inside it for whatever reads it later.
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, amber, grey or red — see What the status dot means below. |
| 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.
What the status dot means
The dot asks two questions about a server, and only turns green when both are answered.
Announced means JudoNet has heard that machine on the network. Answered means JudoNet then asked it what it is and got a reply — which is how JudoNet learns whether it is a JudoManager or a Judobase back end, and which competition is open on it. A machine can announce itself perfectly and never answer: it used to look exactly like a working one, with a green dot, an empty API interface column and no SELECT button, and nothing on the page saying why.
| Dot | The server is | What to do |
|---|---|---|
| Green | Announced, answering, and a competition is open on it. | Nothing. This is the only state you can press SELECT on. |
| Amber | Announced, and unusable. | Hover the row for the reason in one sentence, or use the warning triangle beside the dot to open the steps. There are four causes, below. |
| Grey | Announced, and not asked yet. | Nothing. It lasts under a second, and it is not a fault. |
| Red | Not announcing. It was seen earlier and has stopped. | Check the machine is switched on and on the same network. Use Delete to take an old one off the list. |
Amber has four causes, and each needs something different done about it:
- It is not answering — JudoNet asked and nothing came back.
- It is too old — JudoNet asks over an interface that arrived in JudoManager 7.1.9.5, so an older machine is never asked at all.
- Its version cannot be read — the announcement is malformed, so JudoNet cannot even tell whether asking would work.
- It has no competition open — it answers perfectly and has nothing to send data to. On a setup morning this is the ordinary state of the hall.
Only the not-answering dot blinks, slowly, so you can find the row in a full table. It is the one cause that can clear itself without anybody doing anything. The other three wait on a person — upgrading a machine, repairing an install, opening a competition — and their dots sit still, because a dot that moved while you waited would be suggesting the wrong thing.
A server that has answered before gets fifteen seconds of not answering before its dot turns amber. Announcements arrive every few seconds and JudoNet asks on each one, so without that pause a single dropped reply would flick a healthy server amber and back, which teaches you to distrust the dot faster than having no dot at all. A server that has never answered goes amber on the first attempt: that is not a blip.
Only the server you selected raises an alert. When it stops answering, a message joins the rest on Alerts and Errors and the red banner appears: The selected server '…' is announcing itself but is not answering. It cannot currently be used to send data to the online platform. Either fix that machine or select a different one; the alert clears by itself the moment it answers again.
The other rows stay silent however many of them are amber. At a venue most of the JudoManager machines on the network belong to other people, and an alert for each would bury the ones that take a mat off the air.
UDP Send Interfaces
Every network connection on the JudoNet PC is listed here, and you can switch UDP sending on or off for each. UDP is how JudoNet puts live data onto the local network — it sends without waiting for a reply, so nothing at the other end confirms receipt.
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, and the build it is running — see below. |
| 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. |
Which build each instance is running
Under each machine's name, in small grey text, is the build that instance is running. It is a second line inside the Name cell rather than a column of its own, and hovering it shows Version.
That makes an upgrade legible at a glance. Roll a new build out across several machines and the grid shows you, from one column, which ones have taken it and which are still behind — a machine still on a build from three months ago sits in the list beside one updated this morning, and the difference is the number under its name.
Every JudoNet has always announced its build; older versions of this page simply had nowhere to show it. So a build appearing here does not mean that instance was upgraded — it means this page now reads something the instance was already sending.
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. Every 30 seconds JudoNet pings two addresses — Google's 8.8.8.8 and its own time.fairreplay.com — and plots the average of the replies.
You can show the last 15 minutes, the last 30 minutes, or no limit — which means everything JudoNet still holds, and it holds one hour. Readings older than that are discarded, so the widest view is an hour however long the service has been running.
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.