Le Mans 24 Hours

Le Mans Track Map

The Le Mans track map can be found under WEC/Le Mans in the track item. There are a number of options for configuring the main track map display that are specific to Le Mans which are accessible from the main ribbon bar control as shown in the example below:

• Map colored by slow zones rather than normal 3 sectors

  

• Corner numbers and main sector labels can be hidden

• Slow zone and marshal posts can be shown

  

Active slow zones

Active slow zones will flash yellow when they are active on the track map.

Connection Options

Alkamel is proposing 2 different ways to connect to their feed:

• On-site
• On-cloud.

We have prepared pre-configured “championships” for each of these options that you can download and import directly into HH Timing. These can be downloaded below:

Pre-configured Championship for Download

• Al Kamel V2
• Al Kamel On Cloud

To import a championship into your project, use the Import button in the Components tab.

If HH Timing Will Not Connect to Feed

If you can not successfully connect to the feed there are two likely causes:

• Your computer can not access the timing server. This will likely be caused by an issue with your team network. If you can not "ping" the IP address of the timing server this means your computer can not access the timing data.
• You have exceeded the number of connections allowed by Al Kamel

Max number of connections reached

If you can not successfully connect to the feed and get the message in the lower-left corner of the software " Max Number of Connections Reached" this indicates you have exceeded the number of connections allocated to you from Al Kamel.

Normally for Le Mans, Al Kamel gives each team some timing connection per car, although you can pay extra for more. If you are getting the Max Number of Connections Reached message and you believe you are not exceeding your connection limit it is best to speak to Al Kamel in person. You can generally find them in the timing and scoring office which is at the pit-in end of the main pit lane building.

Timing Feed Protocol - Al Kamel V2

The Al Kamel V2 protocol is the Al Kamel JSON protocol. The main advantage of the V2 protocol from the user’s perspective is the inclusion of GPS position data in the feed. This allows the following extra features:

• The position of the cars on the Track Map can be defined by their GPS coordinates
• The path (driving lines/position) of cars can be compared
• The speed traces of cars are calculated from the position data and can be plotted.

Note

• You must obtain a username and password from Alkamel to be able to access this data. This information needs to be entered in the “Additional Options” area of the Championship Configuration in HH Timing.
• There is an option, "GPS" to record rgps (value = rgps), gps (value = gps) or nothing (value = no) from GPS data. rgps is the real value, gps an estimated value. We recommend to set this field to rgps.
• You can choose to record GPS messages in the database if you set "true" as value for Record GPS. As it will only be useful for replays, we recommend keeping the default value, false.
• Compare to previous year, sections Porsche, Ford, T6 and T7 have been removed.

GPS Track Map

For the software to render the cars on the main track map by GPS data rather than the normal interpolation method this must be specified in the main track map ribbon bar control as shown below.

Additionnal loops

In Le Mans there are a number of additional “timing loops” that are accessible by teams. Al Kamel supply the timing data from these additional timing loops in the regular data feed but in a different way, which means these loops aren't handled like "regular" loops are.

By default, HH Timing does not show all the data from the additional loops, the user can define their own custom sectors using the timing loops from x2 channel (not available in support series), using the following names:

Loop Name	x2 Channels	Slow Zone
FL		end of SZ9/ start of SZ1
SCL2		SZ1
Z4		end of SZ1/ start of SZ2
IP1		end of SZ2 / start of SZ3
S6-1	☑️	SZ3
S6-2	☑️	SZ3
Speed1		SZ3
Z12		end of SZ3 / start of SZ4
A6-1	☑️	SZ4
A6-2	☑️	SZ4
A6-3	☑️	SZ4
SCLC		SZ4
S7-1	☑️	SZ4
S7-2	☑️	SZ4
A7-1		end of SZ4 / start of SZ5
A7-2	☑️	SZ5
A7-3	☑️	SZ5
S8-1	☑️	SZ5
S8-2	☑️	SZ5
IP2		SZ5
A8-1		end of SZ5 / start of SZ6
A8-2	☑️	SZ6
A8-3	☑️	SZ6
S9-1	☑️	SZ6
S9-2	☑️	SZ6
SCLB		end of SZ6 / start of SZ7
A11-1	☑️	SZ7
A11-2	☑️	SZ7
A11-3	☑️	SZ7
PORIN		end of SZ7 / start of SZ8
POROUT		end of SZ8 / start of SZ9
PITREF		SZ9
SCL1		SZ9
FORDOUT		SZ9
PitIn
PitOut

Microsectors - Using Slow Zones as main Sectors (EXPERIMENTAL)

The use of microsectors is optional, but when available from the timing feed, they need to be entered in pairs as a semicolon/comma-separated list (and sectors will be named MS1, MS2, ..., MSx), or in a triplet with name,entry,exit.

As an example, Slow Zones can be created as Micro Sectors in Le Mans using the timing lines from the feed:

• FL to Z4
• Z4 to IP1
• IP1 to Z12
• Z12 to A7-1
• A7-1 to A8-1
• A8-1 to SCLB
• SCLB to PORIN
• PORIN to POROUT
• POROUT to FL

The micro sector string would be: SZ1,FL,Z4;SZ2,Z4,IP1;SZ3,IP1,Z12;SZ4,Z12,A7-1;SZ5,A7-1,A8-1;SZ6,A8-1,SCLB;SZ7,SCLB,PORIN;SZ8,PORIN,POROUT;SZ9,POROUT,FL

Checking with the timekeeper for the availability of timing lines for the event is necessary, as the names of loops can change over time.

The option "Use Micro Sectors As Main Sectors" should be set to true to utilize them.

Micro Sectors	SZ1,FL,Z4;SZ2,Z4,IP1;SZ3,IP1,Z12;SZ4,Z12,A7-1;SZ5,A7-1,A8-1;SZ6,A8-1,SCLB;SZ7,SCLB,PORIN;SZ8,PORIN,POROUT;SZ9,POROUT,FL
Use Micro Sectors As Main Sectors	true

Live Excel Export

• If Use Micro Sectors As Main Sectors is set to true:
  • Standard sectors S1 to S9 will correspond to your new main sectors so SZ1 to SZ9.
  • It is required to define the Number of Non-Track Sectors in the backstage option (e.g., 3):
  • 
    • Then, NTS1 to NTS3 will correspond to the original S1 to S3.
    • 
• If Use Micro Sectors As Main Sectors is not set or set to false:
  • Standard sectors remain named S1 to S3.
  • All non-track sectors, including slow zones, will appear as NTS entries (e.g., NTS1, NTS2, ...).

Create Custom Sectors

With the additional loops, the user can define custom sectors in the “Additional Options” grid of the Championship Configuration.

The sector name (chosen by the user) is defined in the first column, and the second column defines the start line and the end line for the sector, separated by a ; character (example: S9-1;A11-1 will give you the time between these two lines).

A custom sector can also be defined by the addition of several sub-sectors using the following syntax: StartLine1;EndLine1;StartLine2;EndLine2;StartLine3;EndLine3 ...etc. In that case you can easily sum non-consecutive sectors.

Any pair of loops can be used to define a custom sector, only the start(s) and end(s) loop need to be defined, the loops do not need to be consecutive.

Important

• The name of any of the additional sectors can not be the same as any of the sectors or speed traps in the main feed which are: S1, S2, S3, Speed1 (and PORSCHE, FORD, T6, T7 before 2025).
• If you make a change to the definition of the custom sectors, for these to be shown in the software the data needs to be re-processed.
• Graphs that are made that include custom sector data may need to be remade if the custom sector definition is changed.
• If CONNECTED LIVE: You will need to disconnect, replay the session you were just connected to, re-connect to the live session (do not clear scoreboard). The data that was sent while you were disconnected will not be recorded by the software. For this reason it is better to stay connected to the live session and only replay to re-process the data once the session finishes if you do not need this additional data during the session.
• If NOT CONNECTED LIVE: Just replay the session with the new sectors definition active and the new sectors will appear.
• You can only define additional sectors on a computer directly connected to Alkamel V2 Protocol (server). Client computers connected via the server mode will receive automatically the same sectors than the server.

Speed Traps for Custom Sectors

HH Timing can create speed traps for any of the custom sectors that are defined in the championship configuration. A third argument can be entered after the START and END loops that define the custom sector, which is the distance between the timing loops separated by a semi-colon. An example is shown below in the hypothetical case that custom sector AA4 has 30.7 meters between the two timing loops that define it.

Suggested Race Settings

Options considered critical for the software to operate as intended during the race are summarized below.

Session Settings in Backstage Options

Track Map Options

Select Le Mans track contour

Define the max number of laps for your class of interest. See the Track Item section for a detailed explanation of how these values are applied.

Define the average lap time in seconds of the cars/classes of interest. This is optional and only needs to be used is you prefer to have control over this, otherwise the software will use the average of the best 3 laps in the last 5 for each car as the lap time for forward projections.

Championship Options

Check these are correct:

• Host
• Port
• Championship Filter
• Tyres and Fuel in parallel

Car Following/Highlighting

See the track map highlighting section to make sure everything set to your preferences.

Miscellaneous Notes

The way HH Timing defines if a lap was under caution/slow zone/SC

• Each of the three safety cars has a number that is locked to it, either 1,2 or 3. This can be thought of in the same way as any other car number, the number is associated with the transponder physically fitted to the car.
• Please review how the championship filter is intended to be used if you are unfamiliar with it and make sure it is set correctly to avoid issues with data being blocked or support race data being included in your project.
• There can be cases when a slow zone is removed and the track goes green, however the message is not sent by the time keepers. In this case, there is no way for the software to know that the slow zone has ended. In this case the user can force the track status back to green using the green flag symbol in the lower right corner of the window.
• If you need to restart HH Timing during a session and especially during the race, there are 2 options to get back your old data:

1. You did not miss a pitstop for your car during the connection loss

   • Right-click on the session and use "Recover"

   • Wait to get back your old data.

   • Make sure the Read History option is set to false in your championship config

   • Connect again without clearing the scoreboard.

     

2. Your car did a pitstop during the connection loss

   • Make sure the Read History option is set to true in your championship config

   • Save your layout

   • Close all your controls.

     

   • Connect again clearing the scoreboard.

   • Wait session the Elapsed time to be live.

   • Open your layout.

Support

If you need any support please send messages to support@hh-dev.com as this is the fastest way for one of us to provide help.