Skip to main content

Live timing feed connection

The live connection is used to read data from a timing and scoring server during a session. To connect to a live connection the “Connect” button on the Data tab of the ribbon bar should be used.

There are 3 types of live connection possible with HH Timing:

  • Socket connection
  • HTML scraping
  • FTP server

This section will explain each type of connection. The connection protocol and all related options and settings are defined in the Championship project item.

Socket Connections

A socket connection is the most common connection method. In this case, the user should normally just supply the host name and port number of the timing and scoring server. This information should be provided by the timing organization for the championship.

HTML Scraping

The HTML scraping connection is generally used for championships that do not provide an official data feed. The protocol works by reading a website with timing data at fixed intervals and determining the timing data based on the changes in the website each time it is read.

When connecting with an HTML scraping protocol a browser window will open at the URL that is defined in the championship project item. This browser can be used to navigate through menus if required to get to the correct website view. The browser should not be closed while data is being read from the website. Often the HTML scraping protocols have some weaknesses and inaccuracies as this is not a supported operation and some of the data has to be estimated by HH Timing.

For carrying out post-race analysis in series where HTML scraping is the only way to get live data, importing the post-session data supplied by the organizer is suggested.

FTP Server

The FTP Server connection is used when the timing and scoring server is implemented as a FTP server. So far this is only used for the official Blancpain timing service. From a technical perspective using an FTP Server for live timing data is a relatively poor option however, there is one advantage. As the data is stored in a file structure all previously published data can be access no matter when you connect during a session. This means if you connect to a session late or have a computer crash, you can still retrieve all missed session data.