Broadcast
What FINISH sends, and to whom: the state of each race in progress (standings, laps, times), to the TABLEAU displays, to the speech synthesis of VOICE and to any client on the network. FINISH sends the full state when a client arrives, then only the changes.
| Product | Workstation | Link | Address | Channels | Since | Batches | KB | Pending | Clock (ms) |
|---|---|---|---|---|---|---|---|---|---|
| TABLEAU | ECRAN-PUBLIC | TCP | 192.168.1.21 | all | 13:30 | 1,284 | 412 | 0 | +2 |
| VOICE | SONO | TCP | 192.168.1.22 | all | 13:31 | 1,280 | 405 | 0 | −1 |
- The broadcast status and Restart broadcast.
- The announcement: clients find FINISH on their own.
- The TCP transport, used by almost all clients.
- Accept ChronoFEED-SIM.
- The connected clients.
A race is broadcast only if its Broadcast box is checked (race sheet) and as long as it is loaded, in progress or finished: a raced race leaves the displays immediately. Transports add up; changing a setting restarts only the transport concerned. See the scenario Broadcast to TABLEAU and VOICE.
Restart broadcast
Where: Broadcast, at the top
Stops and restarts all transports (TCP, UDP, database, announcement, Redis). Clients reconnect on their own and receive the full state. Next to it: “Broadcast:” and the active transports (“TCP :8210 · announcement · clock :8213”), or “Stopped”.
Announce FINISH on the network every 2 s
Where: Broadcast, Announcement (discovery) card; checked by default
Displays, VOICE and SIM find FINISH on their own (UDP, port 8212), with no address to type. The announcement contains no password. Two FINISH computers on the same network (two tracks) both announce themselves: the client offers the list and remembers the chosen name.
Name displayed by clients
Where: Broadcast, Announcement card
The name of this FINISH in the clients (the computer name by default). Give a meaningful name (“FINISH-Starford”) when several FINISH computers share the network: this is the name each client uses to find its own, even if the address changes.
IP (TCP)
Where: Broadcast; checked by default
One connection per client: each receives the full state, then only the changes; a slow client does not slow down the others. Guaranteed delivery, athlete photos, filtering by channels. The default choice (port 8210).
Accept ChronoFEED-SIM
Where: Broadcast, Simulator (ChronoFEED-SIM) card; unchecked by default
Lets a SIM connect to this FINISH and simulate its races, whatever the mode (competition, training, demo). Unchecked, it is refused (the log and this page say so). A connected SIM is shown in the status bar (“SIM connected”, orange background). For tests without hardware only: uncheck it during a competition.
UDP
Where: Broadcast
A single send for all screens (datagrams under 1200 bytes; the full state is resent every 2 s). Multicast (recommended) or Broadcast, and the port (8211). For broadcast protocol clients that listen over UDP; TABLEAU and VOICE do not receive over UDP (they connect over TCP, or through Redis for a remote display).
Multicast group
Where: Broadcast, UDP card
The group address (239.255.82.10 by default): UDP clients must listen to the same one.
Database (PostgreSQL)
Where: Broadcast
The changes are also sent through the database (LISTEN / NOTIFY on the “chronofeed_diffusion” channel): for a client that has access to the database but not to the display network. It receives only the changes. TABLEAU and VOICE do not use it.
Redis (remote scoreboards and archive)
Where: Broadcast
For a TABLEAU on another network, anywhere in the world, and to keep the results in the cloud. You provide your own Redis server; your credentials stay on this computer, encrypted by Windows. Redis receives the same batches as the other transports, through a queue: slow or cut off, it slows nothing down. Test the connection, Save, then the status (“Connected to … · space “…” · N batches published · remote scoreboards: …”).
Server (host)
Where: Broadcast, Redis card
The address of your Redis server, and its port. Below: User (optional) (ACL account of Redis 6 and later; empty: the default account) and Password (never displayed or written to the log; empty: keep the saved one).
Encrypted connection (TLS)
Where: Broadcast, Redis card
Almost all cloud Redis services require it. Uncheck it only for a server on your own network.
Space (your organization or your track)
Where: Broadcast, Redis card
All your Redis keys start with “chronofeed:space:”. Remote displays enter the same space.
Synchronize all
Where: Broadcast, Redis card, “Archive the results in Redis”
Each raced race is kept in your Redis, as readable JSON (as it happens, and through a check pass every ten minutes). The button runs the pass on demand: it goes through the whole database and writes what is missing or has changed, in the background (timing continues); Cancel stops it. Also remove the races missing from this database: by default, a race in the archive that is not in this database is kept (another season); checked, it is removed. How long data is kept depends on your server: enable its persistence and the “noeviction” policy.
Connected clients (TCP and Redis)
Where: Broadcast, at the bottom
The ChronoFEED products connected to this FINISH (displays, voice, simulator), with their computer, the link (TCP or Redis), the address, the requested channels, the connection time, the batches and kilobytes sent, what is pending, the catch-ups, the clock gap with FINISH and its accuracy (FINISH is the clock master: clients compute the timer from the start time). The button disconnects a client (it will reconnect).
Trackside changes (MAPPING)
Where: Broadcast, above the trackside stations (below the connected clients); OFF by default
Lets a trackside ChronoFEED-MAPPING station change the assigned transponders. Each station must be accepted: its request appears at the top of the window (“Accept”, “Refuse”); without an answer within 5 minutes, it expires and nothing changes. Accepted stations are listed here, each with “Withdraw access”. Each change is shown at the top of the window and written to the log.
OFF: FINISH refuses every request and every change from trackside. Switching to OFF withdraws the access of all stations: after switching back to ON, each one must ask again and be accepted again. The setting is kept from one launch to the next; each ON / OFF switch is written to the log.