Two FINISH and one EVENT on the same database

Three computers on the same network and the same PostgreSQL server: one FINISH on the photo finish, one FINISH on the transponders, and EVENT in the race office. Heats go through no file at all; each system writes its times, and EVENT sees them all.

Computer	Software	Role
SERVEUR-PISTE (192.168.1.10)	PostgreSQL	The shared database, running for the whole event.
FINISH-PF	FINISH	Photo finish (and photocell).
FINISH-TR	FINISH	Transponders; it computes the live positions.
SECRÉTARIAT	EVENT	Entries, heats, standings, broadcast to TABLEAU.

1. The server and the database

Install the server (once)
On the server computer, follow the procedure in the Database window (SettingsDatabase, “Install a PostgreSQL server: steps” section, Copy the text): PostgreSQL, the ChronoFEED account and database, opening it to the venue network, the firewall, a fixed address. Allow about twenty minutes.
Connect each computer
On all three computers: SettingsDatabase, “A network server” section: address 192.168.1.10, port 5432, database and account given during installation, password. Test the connection, then Use this server. Close the program and restart it.

EVENT's status bar says “Database: server 192.168.1.10”.

2. The two FINISH

The overall standings in the database
On each FINISH: SettingsOverall standings, Keep the general classification in the database. Only one computer computes the live positions: a transponder computer always tries to be that one; on FINISH-PF, leave This computer computes the live positions (master) unticked.
Load the competition
Once EVENT has sent the heats (step 3): on each FINISH, FileLoad a competition from the database… and choose “Coupe Hollywood longue piste”.

Both computers see the same races, with their groups (G1…), positions and colors.
Choose the races and follow the schedule
When loading, the window Choose the events to load lists the events of the competition: here both computers time the same races, keep them all checked. (To share the event — women on one computer, men on the other — each FINISH checks its own; the choice is remembered and FileChoose the events… changes it.) Tick FileAutomatic synchronization on each FINISH.

The races are in the order of EVENT's schedule (numbered 1, 2, 3…). When the office moves a heat in the schedule, both lists put it back in its place at the next reread, between two races; a loaded or started race does not move.

3. EVENT in the race office

Send and keep automatic sending on
Banner: Send to FINISH, Automatic sending.

A heat changed in EVENT is sent automatically two seconds later; a series of drag-and-drops makes only one sending.
Let EVENT read FINISH again
EVENT reads FINISH again every 30 seconds while the event workspace is displayed (and when the Line-up module opens): athletes changed in FINISH before the start, started heats, results. Read FINISH again does it right away.

Under the banner title: “FINISH read again at 10:42:15: up to date.”, or what was taken back.
Settle a difference
If a FINISH and EVENT both changed the same heat, the Differences between EVENT and FINISH window shows both line-ups. For each heat: Keep EVENT, Take FINISH or Later; or Keep EVENT for all / Take FINISH for all, then Apply.

4. The times of the two systems

Each FINISH writes the column of its own technology in the overall standings, and only if it is empty or still contains what it had put there: no computer overwrites the other, nor a time entered in EVENT. In EVENT, Standings tab › Overall standings, each lap tile has a PF row and a TR row (and PC, MAN if there are any); FIN is the time FINISH selects: that of the master computer's technology, otherwise the priority set in EVENT (SettingsOverall standings, Provisional time: preferred system). See Follow the race.

Reference: Send to FINISH, Read FINISH again, Automatic sending, Database.