This is an old revision of the document!


startSectionEdit: $data "plugin_wrap_start" is NOT an array! One of your plugins needs an update.
startSectionEdit: $data "plugin_wrap_end" is NOT an array! One of your plugins needs an update.
startSectionEdit: $data "plugin_wrap_start" is NOT an array! One of your plugins needs an update.
startSectionEdit: $data "plugin_wrap_end" is NOT an array! One of your plugins needs an update.
startSectionEdit: $data "plugin_wrap_start" is NOT an array! One of your plugins needs an update.
startSectionEdit: $data "plugin_wrap_end" is NOT an array! One of your plugins needs an update.
startSectionEdit: $data "plugin_wrap_start" is NOT an array! One of your plugins needs an update.
startSectionEdit: $data "plugin_wrap_end" is NOT an array! One of your plugins needs an update.
startSectionEdit: $data "plugin_wrap_start" is NOT an array! One of your plugins needs an update.
startSectionEdit: $data "plugin_wrap_end" is NOT an array! One of your plugins needs an update.
startSectionEdit: $data "plugin_wrap_start" is NOT an array! One of your plugins needs an update.
startSectionEdit: $data "plugin_wrap_end" is NOT an array! One of your plugins needs an update.
startSectionEdit: $data "plugin_wrap_start" is NOT an array! One of your plugins needs an update.
startSectionEdit: $data "plugin_wrap_end" is NOT an array! One of your plugins needs an update.
startSectionEdit: $data "plugin_wrap_start" is NOT an array! One of your plugins needs an update.
startSectionEdit: $data "plugin_wrap_end" is NOT an array! One of your plugins needs an update.

Runs

Runs are the core of TestLogger as runs are used to store data from test and race days. You can enter a new run by selecting Run from “New” menu.

New run page loads all necessary data automatically from latest run user has entered for selected car. This makes it faster to enter new runs. If track type is outdoors and coordinates have been defined then TestLogger will fetch current weather data automatically.

Format of New run page varies depending on different parameters. For example laptimes import availability, track type and car class effects the input form.

Basic data

In basic information you can enter car, track, date, time, tags, weather information, track condition and grip. Air temperature is in Celsius degrees. Weather condition and wind speed is not available if track type is indoor.

Run data

For run information you can enter data in three different ways. It is possible to enter summary of the run, import laptimes or manually enter laptimes.

Summary view

Manual laptimes view

Lap times import from Mylaps

Lap times import from MyRCM

Summary

For summary you must enter laps driven, total time for driven laps, best laptime and mistakes in seconds. For the mistakes there is no exact way to do it. It's completely up to you to decide that how many mistakes you did in the run and how much you lost time for those mistakes.

Manually enter laptimes

Import laptimes

Currently it is possible to import laptimes only from Mylaps practice and MyRCM.

Mylaps import

For Mylaps practice import you need to select the Mylaps track ID in the track settings.

Additionally you need to set car transponder in the car settings. Same transponder number can be used for several cars, but be careful if you are using the same transponder with different cars (especially on the same day) that you will import the correct sessions to TestLogger.

When importing laptimes from Mylaps you need to select the Mylaps session first. After selecting the session Testlogger will bring a list of laptimes.

Below the laptimes there is an option to merge sessions. For example you have two short sessions in Mylaps and you would like to merge those together in TestLogger. It is done by selecting the second session from the list and will add the new laptimes from second sessions after the laps of first session. Testlogger won't organize the laptimes by the time of the day.

When importing laptimes from Mylaps practice, please make sure you have correct car, track and date selected. Otherwise the tool can't import data. Testlogger uses those parameters to fetch data from Mylaps Practice.

MyRCM import

To enable MyRCM import you must create a new session. In the session you need to define correct MyRCM event. TestLogger will fetch list of events based on selected date. Additionally the correct transponder number must defined in car settings.

After Session is created, all MyRCM heats needs to be saved to TestLogger separately. So create new run as usual. Check that car, track and date are matching the session information. If everything is working properly, then you should see a dropdown list of your heats in Run data section. Select the run you want to import and then save run as usual.

When importing laptimes from MyRCM practice, please make sure you have correct car, track and date selected. Otherwise the tool can't find correct data.

Performance of the MyRCM is not great at the moment. Fetching import data can take up to 20 seconds depending on the event size.

CSV Import

It is possible to import data via CSV file. Select CSV import tab and paste the content of csv file to the text area. After pasting click Import. Currently only Sanwa M12 file format is supported.

Setup information

In setup information you can enter the used setupsheet In the same section it is possible to enter feelings about the car or driving.

Setup sheet can be selected from dropdown and it's possible to edit/make a new revision of the setup with edit button. It is also possible to view the selected setup.

Tire information

Under setup sheet it's possible to select the tires used in the run. For some classes (currently 1/12 onroad, 1/10 onroad and 1/8th onroad) there are additional options like tire diameter, tire additive amount and tire additive time.

Comments

Last field is run comments and it used for free comments.