How to Configure Master/Slave
Author Message
eLapsRaceTiming Offline

Posts: 60
Joined: Jul 2014
Reputation: 0
Post: #1
Information How to Configure Master/Slave
The Master / Slave functionality allows several separate race timing computers running e-Laps to be connected together and controlled via one computer. This way you can synchronise the computers (start, restart, advance race etc.) when running a race event. Multiple timing computers provides a failsafe backup in case one computer fails.

Master / Slave functionality is found on the Network Setup page (7th Menu item), and then clicking the Master / Slave tab.

[Image: MasterSlave_PreferencesTab.JPG]

To connect the separate computers, one system must be configured as the 'Master', the others are configured as 'Slave'. To prevent errors from occurring, configure only ONE master system.

In order for the Master to identify and connect to Slave systems efficiently, the Master computer should be connected first... then connect Slave systems one at a time.

Configure each system to be a Master or Slave computer by clicking the Master / Slave button, and then click the On / Off button. These 'slide' buttons display their active setting as being bolded and enabled buttons.

[Image: MasterSlave_Buttons.JPG]

When the slave computer is first connected, the Slave button will turn Orange as shown in the following screen shot:

[Image: MasterSlave_slavepending.JPG]

At this point the slave computer is awaiting connection with the master computer.

Once a connection between Master and Slave is made, the computers should look like the following screen shots:

[Image: MasterSlave_masterConnected.JPG]

[Image: MasterSlave_slaveConnected.JPG]

The IP address shown in the Connections list displays the network computers that are connected to the local system. For example, in the screen shots above, the Master system is connected to a Slave system with an IP address of The Slave system is connected to a Master system with an IP address of

Once the two computers are connected, they are effectively synchronised... i.e. when the Start button is clicked on the master computer, the Start button is clicked on the slave computer.

Synchronised actions include: Start race, Pause Race, Stop Race, Restart race, Finalise Race, Skip Race, Delay Final, and Advance race (moving to next race when a race is complete).

The Master system has the added ability to transfer its database to any of the Slave systems. This way any race configurations can be transferred quickly and easily from the Master to it's Slaves.

Database transfer is performed as follows:

On the Master system, click an IP address in the Connection list to enable the 'Transfer DB to Slave' button. Click this button to begin the transfer process.

[Image: MasterSlave_masterTransfer.JPG]

A "Sending Database" (Master system) or "Receiving Database" (Slave system) pop up form will appear on both the Master and the Slave systems... the Master pop up (with progress bar) is shown below:

[Image: MasterSlave_masterTransferPopUp.JPG]

This form displays a 'Starting in [ x ]' seconds countdown. During this count down time the database transfer can be cancelled by either the Master or the Slave.

Once the transfer starts, the progress is displayed (Master system only) on the pop up form. Once the transfer is complete, the pop up form will close automatically.

The Slave system will be prompted to be restarted. This way, upon restart, the database changes will be loaded correctly.

e-Laps Race Timing Software
The next evolution in race control event management software
(This post was last modified: 14-Feb-2016 02:59 PM by eLapsRaceTiming.)
19-Aug-2014 09:15 PM
Find all posts by this user

Forum Jump: