Skip to main content

MyLaps X2 Server

This protocol is used mainly at tests where no official timing is provided. HH Development distributes a stand alone application that connects to the server and transforms the loops crossing information into messages that are interpreted by HH Timing. The application can be downloaded from here:

Operation​

The tool is divided into three main sections:

Settings​

This section mananges all the information required to process the loop crossings

Cars:​

Enter the basic information of the car (number, category, manufacturer) and the transponder id. There is not limit in the amount of cars in the configuration.

SF Lines:​

List the name of the Start/Finish loops (both on track and in pits).

In Pits SF Lines:​

List the name of the Start/Finish loops located in the pit lane. If no dedicated SF loop is available in the pit lane, the Pit In line can be used instead.

Pit In Lines:​

List the name of the pit entry loops.

Pit Out Lines:​

List the name of the pit exit loops.

Sectors:​

List the track sectors. Each sector is defined by an entry timing loop and an exit timing loop.

note

Use the +/- buttons on top of each section to add or remove items

Timing​

In this section, all the information required to connect to the X2 server is defined.

X2 Server:​

Host:​

Network Address of the X2 Server

User Name and Password:​

Login credentials for the X2 Server

Timing:​

Session Start Time:​

Date and time of the start of the Session

Output Port:​

This is the port that HH Timing will use to connect to the tool. The Server Status field below indicates whether the port was successfully acquired at startup.

Server Status:​

Indicates whether the processing server started successfully on the configured Output Port. If the status shows Failed to start, the port is already in use by another process — change the Output Port value and restart the application.

Session:​

Type:​

Sets the session type: Practice or Race. This is used to correctly interpret the timing data received from the X2 server and send it in the correct format to HH Timing clients.

Manual Name:​

Optional name to assign to the session. If set, this name will be used instead of the name received from the X2 server.

Skip X2 cars:​

When enabled, cars that are defined in the X2 server but not in the local configuration will be ignored and not forwarded to HH Timing.

Data​

If the connection is succesful, this section will display the current session information and the history of the loops crossings.

Session:​

Name:​

The name of the current session as defined in the Timing Tab.

Time:​

Current Elapsed Time (based on Session Start Time + last crossing).

Passings:​

List of all loop crossings received since the application started, displayed in chronological order.

Server Connection​

To connect to the timing server use the buttons in the ribbon bar

In the bottom left part of the software there is a connection indicator. If the connection it succesful it will turn green

It the connection fails it will turn red

Timing Connection​

To connect to the tool create a championship configuration with HH Timing protocol with the following parameters:

  • Host: Network address of the X2 application (localhost if running in the same computer)
  • Port: Output Port of the X2 application