Indycar
Championship Configuration
MyLaps RIS Server is now the unique protocol to connect to the timing feed in Indycar. The Multiloop Timing protocol is no longer available.
To connect live you will have to create a championship configuration with the following parameters.
- Protocol - MyLaps RIS Server
- Host - 172.30.16.25 (track) | 64.85.132.67 (remote)
- Username -Provided by Indycar
- Password - Provided by Indycar
- DataSet Name - Depending on the series you want to follow
- Indycar
- INDY NXT
- Session - Leave blank to get the current/latest
- Read Session History
- True will read the full history of the current session when you connect
- False to disable
- Read Telemetry
- True will read and save the telemetry from the feed
- False to disable
- Telemetry Host - 170.30.16.63 (track) | 64.85.132.31 (remote) you must have both Read Telemetry = True and the IP address populated to initialize the telemetry reading
- Save Telem Raw Messages
- True will save the incoming raw telemetry messages. This will enable the session to be replayed with the telemetry data, but has no impact on being able to view the data after the session. Saving this data will make your project use more disk space.
- False to disable, and decrease the size of your project.
- Save Telem Data
- True will save the incoming telemetry data in your database. This will enable loading telemetry data in the data viewer, or exporting telemetry data.
- False to disable, and decrease the size of your project.
The Save Telem Raw Messages and Save Telem Data settings can be used to manage the project size. Project size can grow quickly when storing the telemetry data for all cars. Consider your requirements of the telemetry data when setting these. If the telemetry data is only needed to show the position of the cars on the track maps, then setting both of these to False will allow the track map to function properly live, and minimize the project size.
- Please note that at the moment, when connecting mid-session with the option Read History set to True, the Race Control Messages are not retrieved. The replays from the remote database do not display these messages since they were recorded with the option set to True.
- The Race Control Messages are not yet available on the cloud feed.
Session Names
If you want to redownload data throughout the weekend you can use the following session names.
Indycar Road Course
| Session Name | Note |
|---|---|
| Practice 1 | Never active live |
| Practice 1 - All Cars | |
| Practice 1 - Group A | |
| Practice 1 - Group B | |
| Practice 2 | Never active live |
| Practice 2 - All Cars | |
| Practice 2 - Group B | |
| Practice 2 - Group A | |
| Qualifications | Never active live |
| Qualifications - Segment 1 / Group 1 | |
| Qualifications - Segment 1 / Group 2 | |
| Qualifications - Segment 2 / Top 12 | |
| Qualifications - Segment 3 / Firestone Fast 6 | |
| Warm-up | |
| Race |
Indycar Oval
| Session Name | Note |
|---|---|
| Practice 1 | |
| Qualifications | |
| Practice High Line | |
| Practice Final | |
| Race |
Indy NXT
| Session Name |
|---|
| Practice 1 |
| Practice 2 |
| Qualifications - Group 1 |
| Qualifications - Group 2 |
| Race |
Track Map
The track map should be selected for each configuration (ALT or RACE). Indycar track maps can be found under the Indycar folder:
GPS positioning
Starting in 2026, Indycar will provide GPS positioning live. This can be used to position car on the Full Track Map. to do so, the Car Position Mode should be set to GPS:
Please note that to get the GPS Positioning, you will need to set the "Read Telemetry" option to "True" in the Championship Configuration :
Extrapolated positioning
The other option for the Full Track Map is to use the extrapolation method based on sector crossing. For this, the best option to select is the Auto Extrapolated for the Car Position Mode.
Create Custom Sectors
Users 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: I3 ;I4 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.
- The name of any of the additional sectors can not be the same as any of the sectors in the main feed.
- 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.
Speed Traps for Custom Sectors
HH Timing can create speed traps for any of the custom sectors. A third argument can be entered after the START and END loops that define the custom sector, which is the distance (in meters) between the timing loops separated by a semi-colon. StartLine1;EndLine1;Distance (in m)
Pit Commit for Indy
This option was created to remove cars from the track map that are on the pit commit or pit out blend. The car will disappear from the track map and show on a different line at the bottom of the screen. The goal being to better handle traffic in practice.
Distance-based races
Races can be of three types:
- Time
- Distance
- Time and Distance
The settings need to be set in the Session settings session in the backstage option:
Now the session clock can show the lap information instead of the time:
This is done by choosing the Lap# or Laps to Go as the Clock mode in the option of the Session Clock:
The strategy overview can also be shown using the lap number:
This is done by selecting the Distance Mode option under Strategy Overview:
Tire compound
The colors for tire compound can now be controlled within the software. This can be found under the Strategy Overview option in the backstage under Tyre Specification Colours:
By default the colors follows the Indycar convention:
The tire compound can be shown on the Main Scoreboard using the StintTyres column:
The same information can be found in the Car Scoreboard --> Stint:
In addition, the compound information can be displayed in the strategy overview:
To configure the line you see on the strategy overview, You need to go to Select Parameters:
By default, the tyres will be displayed as BLACK=USED and RED=NEW. You can display them by compound color by selecting the option:
By selecting only the Tyre Used, you can easily see all cars in the field:
Qualifying Scoreboard
In display under the Other Scoreboards there are two differents scoreboard that can be used.
Indy 500 Qualifying Scoreboard
This is specific scoreboard designed for the Indy 500 specific qualifying system.
Oval Qualifying Scoreboard
For all other Oval qualifying the regular Oval Qualifying Scoreboard can be used.
Weather info
The weather information from the feed will now be displayed using the Weather Conditions control:
The unit scheme can be changed from Imperial to Metric in the backstage option under General:
Telemetry Export
A telemetry export module is included inside HH Timing under the Data Tab:
- Export Directory: folder where the data will be exported to (each car is exported to a dedicated sub folder)
- Export Type: file format(s) to be exported
- Export Source: this is legacy from Multiloop - not needed for RIS
- Export Interval [min]: the interval of the auto export
- Use Time Of Day To Link Laps: this should be set to false starting in 2026. If it is false the telemetry data is exported based on the automatic link with the lap that is created when running live. If true, the software will look at the time of the lap and the timestamps of each data point to associate the data to the lap. This option should not be needed from 2026 onwards.
- the export can done at any time, even live during a session
- it is exporting one file per lap and there is one folder per car
- the best lap is marked with a # at the end of the file name
- for the PDS the file needs to be viewed vs distance in PI Toolbox