Skip to content
ChronoFEED TABLEAU Help

Connecting TABLEAU to FINISH

A giant screen in the arena, on the track network: TABLEAU finds FINISH on its own. A scoreboard for families at the club house, on the other side of town: it goes through your Redis server.

Example: the Coupe Hollywood at the Starford oval. The FINISH computer is called “FINISH-Starford” (192.168.10.20). The “ECRAN-PUBLIC” computer is connected to the giant screen; a second scoreboard runs at the Bobines Volantes club house, over the Internet.

1. On the track network

  1. Check the FINISH broadcast

    In FINISH, Broadcast module: Announce FINISH on the network every 2 s and IP (TCP) are ticked by default; give it a meaningful name, “FINISH-Starford”.

  2. Launch TABLEAU

    On ECRAN-PUBLIC, launch ChronoFEED-TABLEAU. Nothing to enter: it listens for the FINISH announcement and connects to it.

    Control panel (F2), CONNECTION section: “Connected to 192.168.10.20 · 0 race(s) in progress · … batches” and “FINISH clock: +2 ms ± 1 ms”. The log says “FINISH found: FINISH-Starford (192.168.10.20:8210)”. In FINISH, ECRAN-PUBLIC appears among the connected clients.

  3. A race on the screen

    Load a race in FINISH (500 m Women — P03).

    It appears on the scoreboard right away (the athletes, their starting colours); at the start the clock runs, and at each passing the laps and the standings follow. When it becomes run in FINISH, it leaves the screen.

  4. Full screen

    F11 (or double-click): the scoreboard fills the screen with no border, and stays that way at the next startup. If you keep the panel, detach it onto another screen (Detach).

2. Two FINISH on the same network

Two tracks, two FINISH: the panel says “2 FINISH found: choose below.” and offers one button per FINISH. Click yours: it is remembered by its name, even if its address changes. To change later: Choose another FINISH at next launch, then restart TABLEAU.

If the network blocks the announcement (firewall, segmented network), enter the address of the FINISH computer in FINISH server: it takes effect at the next startup.

3. A remote scoreboard, through Redis

  1. On the FINISH side

    FINISH publishes to your Redis server (Broadcast → Redis (remote scoreboards and archive)), space “hsk-starford”. Create a read-only Redis account for the scoreboards.

  2. Choose Redis mode

    At the club house, in the TABLEAU panel: Connection mode → Redis (remote scoreboard).

  3. This scoreboard's credentials

    Server (host), Port, Encrypted connection (TLS), User (optional) “tableau-maison”, Password, Space (the same as in FINISH) “hsk-starford”. Test the connection, then Save and connect.

    “Credentials saved on this station, encrypted by Windows.” then “Connected through Redis to "FINISH-Starford" (…) · …”. The password will never be shown again.

CONNECTIONReceive FINISH (live races)
Connected through Redis to "FINISH-Starford" (redis.exemple.org) · 2 race(s) in progress · 3,412 batchesFINISH clock: +38 ms ± 21 ms
Clock through Redis: medium accuracy, running clocks may be off by about 21 ms.Display delay: 800 ms
Connection modeFINISH on the local networkRedis (remote scoreboard)
Choose another FINISH at next launch
The credentials of your Redis server stay on this station, encrypted by Windows. A read-only account is enough for a scoreboard.Server (host)redis.exemple.orgPort6380Encrypted connection (TLS)User (optional)tableau-maisonPassword A password is saved on this station.Space (the same as in FINISH)hsk-starford
Test the connectionSave and connect
Credentials saved on this station, encrypted by Windows.
The club house scoreboard, connected through Redis (example server).

Through Redis, a withdrawn race leaves the screen with the latency of the link (usually 50 to 200 ms). The clock goes over the Internet: if the panel warns in orange that running clocks may be off, the final time is still right (it comes from FINISH); only the running clock is less accurate. Athlete photos also arrive through Redis.

4. If the scoreboard shows nothing

What you seeWhat to do
“Starting…” that goes onThe announcement does not arrive: same network? firewall on the computer? Enter the FINISH address and restart.
“Not connected (…)”Is FINISH running, with its TCP broadcast ticked? Is port 8210 open?
Connected, but the screen is emptyNo race loaded in FINISH; or the race's Broadcast box is unticked in FINISH; or the view for the moment does not allow the race's state (Race states shown).
The screen seems to lag behindA scenario button (even the one for the moment shown) asks FINISH again for the complete state.
“FINISH is not followed (box unticked)”Tick Receive FINISH (live races).