WEC & ELMS
In WEC and ELMS, Alkamel is the timing provider.
V2 Protocol
Prior to get access to the timing data, make sure that you have contacted Alkamel:
- There is a fee that is usually a per championship fee.
- You would need to get Alkamel to enabled V2 protocol for your team.
- They should provide you with credentials.
- They should provide you a router and a WIFI antenna.
- They should also provide you with a Network configuration.
You can find specific help file for V2 protocol here.
Championship Configuration
Depending on which protocol you choose, there's 3 default championship configuration for Alkamel:
- WEC Alkamel V2 - you can use this protocol in WEC or ELMS. You will have to fill your credentials. You can add filters for WEC.
- WEC Alkamel V2 Cloud - you can use this protocol in WEC or ELMS. It will use the cloud connection. You will have to fill your credentials. You can add filters for WEC.
- ELMS Alkamel V2 - you can use this protocol in WEC or ELMS. You will have to fill your credentials. You can add filters for ELMS.
Track Limits Warning
Track Limits Warning are sent in the feed in WEC and ELMS. It will be displayed in the main scoreboard, the car scoreboard, the driver scoreboard and the Track Limit Warning display. You can find specific help file here.
Troubleshooting
If you can't connect, it may come from a network problem, from wrong credentials or because you reached the maximum number of connections.
Network problem
To check that your network configuration is correct:
- Open a command prompt and type "
- If you get a response like :Reply from 192.168.74.12: bytes=32 time=3ms TTL=64, your network configuration is correct and you should contact Alkamel to see if they activated the feed for your team.
- Otherwise type "
- If you get a response like :Reply from 192.168.74.12: bytes=32 time=3ms TTL=64, you have a DNS issue. Please check your setup with your IT department.
- Otherwise, please check your network setup with your IT department.
Wrong credentials (V2 Protocol)
Please ask Alkamel to confirm that you are using the right credentials to connect to the feed.
Number of connections
Alkamel limit the number of connection to their feed to 1 by car.
On each track, there are more timing loops that you can use to create custom sectors.
For example at Spa, there are 7 loops, FL, SCL2, IP1, PL1, IP2, PL2 and SCL1. You can create a sector from FL to SCL2 for example by adding it to the additional options of the championship configuration before connecting:
You can choose the name you want but the value should always be: Loop1;Loop2
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.
Microsectors - Using Micro Sectors as main Sectors
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. It will improve the data precision and allow for more accurate gaps on live crossing order, or gap track map, and a more precise ghost cars calculation.
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 microsector 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 |
To ensure full functionality — including features such as ghost cars — the dedicated Track Map must be used.
- If
Use Micro Sectors As Main Sectors
is set to true:Standard sectors
S1
toS9
will correspond to your new main sectors soSZ1
toSZ9
.It is required to define the Number of Non-Track Sectors in the backstage option (e.g.,
3
):- Then,
NTS1
toNTS3
will correspond to the originalS1
toS3
.
- Then,
- If
Use Micro Sectors As Main Sectors
is not set or set to false:- Standard sectors remain named
S1
toS3
. - All non-track sectors, including slow zones, will appear as
NTS
entries (e.g.,NTS1
,NTS2
, ...).
- Standard sectors remain named
List of loops per track
Aragon: FL, SCL2, INT1, INT2, VMAX2, SCL1
Bahrain: FL, SCL2, PL1, IP1, PL2, IP2, PL3, SCL1
Barcelona: FL, VMAX2, SCL2, IP1, IP2, SCL1
COTA: FL, SCL2, INT-1, PL1, PL2, INT-2, PL3, SCL1
Fuji 2024: FL, SCL2, IP1,PL1,IP2, PL2, PL3, SCL1
Fuji 2023: FL, SCL2, IP1,PL1,IP2, PL2, SCL1
Imola WEC: FL,SCL2,PL1,IP1,PL2,IP2,PL3,SCL1
Imola ELMS: FL,SCL2,IP1,IP2,SCL1 (Micro Sectors: FL,SCL2;SCL2,IP1;IP1,IP2;IP2,SCL1;SCL1,FL)
Losail: FL, SCL2, PL1, IP1, PL2, IP2, PL3, SCL1
Monza: FL, SCL2, PL1, IP1, PL2, IP2, PL3, SCL1
Portimão: FL, SCL2, PL1, IP1, PL2, IP2, PL3, SCL1
São Paulo: FL,VMAX2,PL1,SCL2,IP1,PL2,IP2,PL3,SCL1
Sebring: FL, T3, IP1-T4, T5, IP2-T6, SCL1-T7, SCL2, VM2-T9
Spa: FL, SCL2, PL1, IP1, PL2, IP2, PL3, SCL1
Mugello FL,SCL2,IP1,IP2,SCL1,Speed1,PitIn,PitOut
ELMS List of Micro-Sectors Per Track
These timing loops can be used to create custom sectors, in the additional options of the championship configuration before connecting. Here is the list of micro-sectors per track for the ELMS championship:
Track | Micro-sectors |
---|---|
Aragon | FL,SCL2;SCL2,INT1;INT1,INT2;INT2,VMAX2;VMAX2,SCL1;SCL1,FL |
Barcelona | FL,VMAX2;VMAX2,SCL2;SCL2,IP1;IP1,IP2;IP2,SCL1;SCL1,FL |
Imola | FL,SCL2;SCL2,IP1;IP1,IP2;IP2,SCL1;SCL1,FL |
Paul Ricard | FL,SCL2;SCL2,IP1;IP1,IP2;IP2,SCL1;SCL1,FL |
Portimão | FL,SCL2;SCL2,IP1;IP1,IP2;IP2,SCL1;SCL1,FL |
Spa | FL,SCL2;SCL2,IP1;IP1,IP2;IP2,SCL1;SCL1,FL |
Mugello | FL,SCL2;SCL2,IP1;IP1,IP2;IP2,SCL1;SCL1,FL |
You can choose the name you want but the value should always be: Loop1;Loop2
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.
WEC List of Micro-Sectors Per Track
These timing loops can be used to create custom sectors, in the additional options of the championship configuration before connecting. Here is the list of micro-sectors per track for the WEC championship:
Track | Micro-sectors |
---|---|
Aragon | FL,SCL2;SCL2,INT1;INT1,INT2;INT2,VMAX2;VMAX2,SCL1;SCL1,FL |
Bahrain | FL,SCL2;SCL2,PL1;PL1,IP1;IP1,PL2;PL2,IP2;IP2,PL3;PL3,SCL1;SCL1,FL |
Barcelona | FL,VMAX2;VMAX2,SCL2;SCL2,IP1;IP1,IP2;IP2,SCL1;SCL1,FL |
COTA | FL,SCL2;SCL2,INT-1;INT-1,PL1;PL1,PL2;PL2,INT-2;INT-2,PL3;PL3,SCL1;SCL1,FL |
Fuji | FL,SCL2;SCL2,IP1;IP1,PL1;PL1,IP2;IP2,PL2;PL2,PL3;PL3,SCL1;SCL1,FL |
Imola | FL,SCL2;SCL2,PL1;PL1,IP1;IP1,PL2;PL2,IP2;IP2,PL3;PL3,SCL1;SCL1,FL |
Losail | FL,SCL2;SCL2,PL1;PL1,IP1;IP1,PL2;PL2,IP2;IP2,PL3;PL3,SCL1;SCL1,FL |
Monza | FL,SCL2;SCL2,PL1;PL1,IP1;IP1,PL2;PL2,IP2;IP2,PL3;PL3,SCL1;SCL1,FL |
Portimão | FL,SCL2;SCL2,PL1;PL1,IP1;IP1,PL2;PL2,IP2;IP2,PL3;PL3,SCL1;SCL1,FL |
São Paulo | FL,VMAX2;VMAX2,PL1;PL1,SCL2;SCL2,IP1;IP1,PL2;PL2,IP2;IP2,PL3;PL3,SCL1;SCL1,FL |
Sebring | FL,T3;T3,IP1-T4;IP1-T4,T5;T5,IP2-T6;IP2-T6,SCL1-T7;SCL1-T7,SCL2;SCL2,VM2-T9;VM2-T9,FL |
Spa | FL,SCL2;SCL2,PL1;PL1,IP1;IP1,PL2;PL2,IP2;IP2,PL3;PL3,SCL1;SCL1,FL |
You can choose the name you want but the value should always be: Loop1;Loop2
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.