Network Setup

Network Setup

This chapter guides you through the practical setup of your Local Area Network (LAN), device IP addressing, and the software configuration required for proper data routing.

Configure JudoNet to Send Data

JudoNet must be properly configured for UDP data flow to Judo Graphics. 
  1. Open the JudoNet application. 
  2. Select the Server: Locate the "JudoManager Servers" section. Find your active event server in the list and select it.

  1. Activate the Network: Scroll down to the "UDP Send Interfaces" menu and select the specific Network Interface Card (NIC) connected to the event LAN. If you have multiple NICs, verify you are selecting the correct one by checking its IP address. Click the toggle switch under "Action" to turn that specific connection green (active). 
  1. Enable the Broadcast: Locate the row of checkboxes near the top of the screen and check the box to enable "Broadcast UDP to Graphics".

Note: If no interface is selected, or if the Broadcast UDP to Graphics box is unchecked, no data will be sent.
  1. Verify the Scoreboards: Look at the "Scoreboards" section. Make sure the toggle switch next to your active mat (e.g., Mat 2) is turned on and the "Connection" indicator is glowing green. At the bottom left of the scoreboard box, "All IPs" associated with the scoreboard are listed (select only one if multiple are listed). Check the Time: ΔT indicator in the bottom right corner—it must be green to confirm the scoreboard's time is synchronized.

Data and Video Flow

To ensure a stable live production, it is crucial to understand how and where data travels across your network. The system architecture relies on specific protocols and network ports (refer to the Data Flow diagram):
  1. Live Video Path: Cameras capture the action and send the video feed to your Video mixer PC (OBS/vMix) via SDI cables and a capture card.
  2. Mat Data Feed: The Scoreboard application sends live contest data to the JudoNet distributor via Websocket over TCP port 855.
  3. Local Data Distribution: JudoNet acts as the central hub, converting the incoming data and broadcasting it to the CGplay controller interface via UDP port 5000.
  4. Server and External Data: The CGplay interface fetches specific competition assets using secure HTTPS connections. The source of this data depends on the event type:
    1. For National events: Medalists, logos, and competition data are all fetched directly from the local JudoManager server.
    2. For IJF events: Competition data and logos are fetched from the local JudoManager server, while medalist data and competitor statistics are fetched externally from the JudoBase Cloud API.
  5. Graphics Rendering: CGplay sends execution commands to the CasparCG rendering engine via TCP port 5250.
  6. Live Video Output: CasparCG generates the final graphics with a transparent background (alpha channel) and sends them to the Video mixer PC via Network NDI, which is then streamed to YouTube/Mux.

IP Scheme Example

(Example Subnet: 172.20.1.0/24 with Router at 172.20.1.1)
If you are assigning static IPs manually instead of using a DHCP router, you can use the standard numbering scheme outlined below. This standard scheme supports up to 9 mats. Events with 10 or more mats will require expanding the Scoreboard IP range.

Role

Device

Suggested IP

Configuration Notes

Central Database

JudoManager server

172.20.1.2

Internet + Local. Connects to Scoreboards, JudoNet, and CG.

Data Distributor

JudoNet

172.20.1.10

Internet + Local. Enable "Broadcast UDP to Graphics".

Upstream Data

Scoreboard PCs

172.20.1.11–.19

Local. Leave Gateway/DNS blank (or configure Windows Firewall block if using DHCP). No internet.

Mat Accessories

Contest Order / Coach Assistant

172.20.1.20–.29

Supplemental mat displays.

Graphics & Replay

CGplay, CasparCG, FairReplay, Cutter

172.20.1.30–.39

Local network required. Internet access is required for IJF events and optional for National events.

Video Mixer

vMix / OBS Streamer

172.20.1.60-.69

Internet + Local. Ingests SDI matrix cameras + CG NDI.

Operator Checklists

Pre-Event Network Checklist

IPs are assigned and documented for the crew. 
Windows network profile is set to Private. 
Windows Firewalls are configured to allow UDP, NDI, and TCP port traffic. 
Ping tests between all critical computers are successful. 
IJF Events Only: Verify the Graphics PC has active internet access to reach the JudoBase API. 
Verify that all computers are configured to the exact same Time Zone. 

Game-Day Network Check (Right before going live)

The system time is perfectly synchronized across all machines. 
Start a test contest on the mat. 
Verify JudoNet is receiving live packets. 
IJF Events Only: Trigger a test H2H (Head-to-Head) or Prediction graphic to confirm the system is successfully fetching live data from the cloud. 
Confirm the CG graphics are updating in real-time on your monitors. 
Verify your NDI discovery and audio/video sync on the Video mixer PC.

Operational Best Practices

  1. Document Everything: Document your IP addressing scheme on a physical sheet kept at the control desk.
  2. Create Your Own Network Bubble: Keep all your core production computers plugged directly into your own dedicated event switch. While you must connect your switch to the venue's network to get internet access, never plug your computers directly into the venue's wall ports.
  3. The Diagnostic/Reference Laptop: Keep one "network known-good" laptop nearby that has administrator access and NDI Tools installed. If something crashes (for example, the graphics computer stops receiving data), you can quickly swap the network cable to this laptop to figure out if the problem is in the network or the graphics computer.

FAQ

  1. How do I test my IPs and network connection? Use the Windows Command Prompt. Type ipconfig to verify your computer's current IP address (look for IPv4 Address). To test the connection to another machine, type ping followed by the target IP (e.g., ping 172.20.1.2). If you see reply times in milliseconds (ms), your connection is established.


  1. What happens if my Graphics PC and the JudoNet PC accidentally have the same IP address? This creates an IP Conflict and disrupts network communication for both machines. This usually happens when an operator manually types in a static IP that the router has already given to another device. Ensure every machine has a unique IP.
  2. Can CGplay, CasparCG, and JudoNet run on the same computer without IP and port conflicts? Yes. These applications can run on the same computer without IP or port conflicts, provided that the required ports are not already being used by another application and the correct UDP send interface is enabled in JudoNet.
    1. No IP conflicts: Applications running on the same computer share the computer’s IP address. This does not create an IP conflict. An IP conflict occurs only when another device on the LAN uses the same IP address.
    2. No port conflicts: JudoNet sends UDP data to destination port 5000, while CGplay listens for that data on UDP port 5000. CGplay sends commands to CasparCG over TCP port 5250. These sending and receiving roles do not conflict.
    3. Local communication: When CGplay and CasparCG run on the same computer, their TCP connection can use the local loopback address (127.0.0.1). However, JudoNet UDP broadcasting still uses the selected network interface and must remain enabled and correctly configured.
  3. My graphics look great on my own monitor, but the Video mixer PC operator says the NDI video feed is lagging and dropping frames over the network. Why? If the video is lagging but the data is fine, it is almost always a network bandwidth bottleneck. Pushing a live, transparent 1080p50 video feed over NDI requires massive data throughput. Ensure your Graphics PC is plugged directly into a Gigabit port on the network switch and that you are using a high-quality Cat6 network cable. Never run your NDI video through a cheap, unpowered Ethernet splitter or a 100Mbps port.