Skip to content
Customer portal
Contact
  • There are no suggestions because the search field is empty.

Al Kamel Data Relay

The Relay converts the Al Kamel Timing Feed into a PACETEQ Feed. Various configuration options are available to ensure the resulting feed functions as intended.

The Data Relay

The PACETEQ Al Kamel Data Relay facilitates the conversion of the Al Kamel v2 Timing Protocol into the PACETEQ Timing Feed. To operate this relay, certain prerequisites must be established. Initially, the configuration file must be specified prior to initiating the Relay, and a functional connection to Al Kamel must be ensured.

Start the Data Relay

Once the configuration has been established, you may initiate the Data Relay and specify the track's timezone. Select either "AlKamel" or "Al Kamel 2" based on the desired protocol, with "Al Kamel 2" being the preferred choice in most instances. The relay can be maintained in this state for multiple sessions. To deactivate the relay, simply deselect the protocol. By selecting the Reset option, the Timing Feed will be cleared, potentially enhancing performance throughout the weekend.

 

Config

The config.txt file is located within the same folder as the Data Relay. It contains the essential components required for the Relay to operate effectively.

AlKamelServer2

Specifies the origin of the Al Kamel timing feed, which comprises an IP address or DNS followed by the port number. Al Kamel directly provides the necessary input details. For instance in this example, the IP address is "datapublisher.alkamelsystems.com" and the port is "11001".

AlKamelServer2=datapublisher.alkamelsystems.com:11001

Additional Source Feeds

In certain series, Al Kamel provides supplementary information that the Data Relay can access if required. These must be designated with a name under: AlKamel2ExtraFeeds. Subsequently, it is necessary to specify the source for this additional feed, as well as the channels to which the Relay should listen. For instance:

AlKamelServer2_FeDuels=v2duels.aks:11001
AlKamel2Feeds_FeDuels=timing,raceControl,telemEvent,attackMode

Where to send the data

To enable the Relay to determine the appropriate destination for data transmission, it is necessary to define the endpoints for both the Timing and GPS messages, if applicable. These are specified in a manner similar to the Al Kamel Server using the IP:Port format.

TimingServer=localhost:1664
GpsServer=localhost:1666

Timing Credentials

Access to the Al Kamel timing feed is secured by a password. To enable the Data Relay to interface with their protocol, it is essential to provide the appropriate Username and Password.

User=
Password=

Manual Season overwrite

The Relay communicates the session details to PACETEQ, encompassing elements such as the Series or Event Name. The Season can be manually configured using the "Season=" setting. Consequently, each incoming session will have this specified as the season in ONE TIMING or ONE RACEHUB.

Using Racing Numbers as the TLA in Endurance Racing

In endurance racing, it is common for the TLA field to be populated by the timekeeper with the names of the drivers, which may not be practical in ONE TIMING. To address this issue, the car number can be utilized as the TLA. This can be configured by setting "UseRacingNumberAsName=" to True.

Define the Track Map that ONE TIMING should display

Although Al Kamel provides a Track Name in their timing feed, it frequently does not correspond with the track name that ONE TIMING should present at an event. To address this, you may replace the Al Kamel name with the ONE TIMING name using the "Track=" setting. During each session, the Data Relay will disseminate this Track Name within the PACETEQ Timing Feed.

Use Loops?

Occasionally, Al Kamel specifies the timing loops within the feed but does not transmit any data in the timing feed itself, leading to complications downstream in ONE TIMING, such as in IMSA. These loops are enabled by default but can be deactivated if required by setting "UseLoops=" to false.

Performance Loops

In specific events such as the 24 Hours of Le Mans, the Timing Feed encompasses not only sector and loop times but also performance loops. These are not enabled by default; however, they can be activated by setting "ProcessPerformanceLoops=" to True. This activation necessitates an additional configuration, "PerformanceLoops=PerformanceLoops.LeMans2024.txt," which references a separate text file within the Relay folder. This file delineates all performance loop crossings and specifies the distance in meters from the finish line on the track.

A18-2=9.27
A18-3=138.96
S6-1=3377.3
S6-2=3407.31
A6-1=4397.76
A6-2=4417.77
A6-3=4589.86