PROFESSIONAL MOTORSPORT

SIMULATION SOFTWARE

*.bin / *.bmsbin / *.xrk / *.mat / *.csv

Printscreen of the LapSim GUI with the load data option selected

In order to generate a driving line and/or validate the correlation of the simulation model with the real vehicle, you need to load the on-car recorded data into LapSim.

A Bosch *.bin or *.bmsbin file, as well as a AIM *.xrk file can be directly loaded into LapSim.

Data from other data systems can be done by either a *.mat or a *.csv export. LapSim selects the loading routine dependent on the file extension. The different *.csv formats are identified by the information in the first line of the *.csv file.

Enables post processing of the on-car recorded data

Printscreen of the LapSim Setupoverview GUI while loading when there is no vehicle setup present in the workspace
Printscreen of the LapSim Setupoverview GUI when there is a vehicle setup selected

In order to post process the data, LapSim asks you to combine the on-car recorded data file with setup file describing the vehicle which created the data.

Hereby more information can be subtracted out of the data and the created data lap in LapSim can directly be compared to a later generated simulation lap.

After you have selected a setup file, the main parameters are shown in the setup overview menu. If they are appropriate, click the "SET_UP O.K. Continue..." button.

Channel names are unfortunately not standardized

Printscreen of the LapSim data trace selection menu with no data trace selected

Unfortunately the names for the different channels are not standardized. So it is necessary to have menu where you define which channel name belongs to a certain variable.

LapSim will remember the used names and will select them automatically the next time you open a data file.

Printscreen of the LapSim data trace selection menu with almost all the data traces selected

In order to load a data file, you need to select at least lateral and longitudinal acceleration as well as one (front) wheel speed.

When you select a channel, the data trace will be shown in the graph on the bottom right.

In order to get a detailed correlation with simulation model, it is necessary to load as many traces as specified in this menu as possible.

Printscreen of the LapSim data trace selection menu with almost all the data traces selected

Please check the direction with the acceleration channels. Furthermore you can select whether suspension travel is calibrated at the wheel or at the spring. There is the option to measure heave (central element) in combination with ARB roll instead of individual wheels. Last option is to define whether rebound travel is negative or positive

Printscreen of the LapSim data trace selection menu with overview of the laps in the data file

Finally if the data file contains more than one lap, you should select the lap you wish to load. LapSim automatically selects the fastest lap.

Pressing "Ctrl" button in combination with selecting a lap in the listbox, enables you to select multiple laps in one go. Selecting an already selected lap, deletes this lap from the selected list.

Selecting a lap without the "Ctrl" button engaged, will reduce the list to only the last selected lap.

Direct load and driving line based on GPS data

Printscreen of the LapSim data trace selection menu when AiM *.xrk file is loaded with no data trace selected

AiM *.xrk files can be loaded in a similar manner like the Bosch *.bin and *.bmsbin files.

The biggest difference with the Bosch data file, is that an AiM *.xrk file always has GPS data available, which in case of the AiM file will always be used to calculate the driving line. Since the name of the GPS channels is standardized, so you do not need to specify them.

Because the driving line is calculated out of the GPS data, you can even load the data without specifying any channel name.

Printscreen of the LapSim data trace selection menu showing the track lay-out when AiM *.xrk file is loaded

if you select "no signal" in any listbox, the graph will show you the calculated driving line out of the GPS.

In this manner you can check if the driving line is appropriate for making a simulation.

As an example you can see in the figure on the right the driving line of the in-lap.

You need a WinDarab V7 license to load *.bmsbin

Printscreen of Error 19 message in LapSim

You can directly load BOSCH *.bin and *bmsbin files into LapSim. Just a matter of selecting the right channel names for the several traces. There is however one big but.

If you want to load a WinDarab V7 generated *bmsbin data file, you need the same WinDarab license on your computer as the WinDarab license which created the data.

Directory WinDarab License

Printscreen of help menu of LapSim with Directory Windarab license highlighted

And even if you have the right license on your computer, LapSim must know where to find this WinDarab license.

Printscreen of help menu of LapSim with Directory Windarab license selected after the directory has changed

You can specify the directory LapSim should look for. For this select option "WinDarab Installation Directory", in the help menu.

A new screen appears, stating the current WinDarab directory where LapSim looks for the WinDarab license.

Click on the button to alter the directory and subsequently select a different one.

In order to let the change come to effect, LapSim needs to be closed which you can do by pressing the button.

Two different formats readible by LapSim

The first format is a structure where each data trace has a field 'Value', 'Time' and 'Units'. LapSim can cope with different logging frequencies for the several traces.

The second readable format is where each data trace has either two columns or two rows. Whereas the first column / row contains the time stamp and the second row contains the corresponding value of the variable.

LapSim assumes that the export contains only the data of 1 lap.

AIM *.csv LapSim export is the same

Printscreen of the header of a Motec *.csv export

If the data file you selected has the extension *.csv and LapSim finds the word "Motec" in the first line, it assumes that the file is a standard Motec *.csv export.

LapSim assumes that the channel names are defined on line 14 and that the data itself starts at line 18.

There must be a "Time" trace and preferably also a "Distance" trace.

Please be aware that in case of a *.csv file, LapSim will load the complete file, not only the traces you selected like with a *.bmsbin or *.xrk file.

This means that if you make an export of ALL your channels, the *.csv file becomes unnecessary big but more important it will almost certainly become too big for LapSim to load and will lead to a crash of the program.

So please take the time to select only those channels for export which can be loaded into LapSim! And please limit the frequency rate of the export to 50 or 100 [Hz].

Enabling you to load any data

Printscreen of the header of a universal *.csv export capable of being loaded in LapSim

If LapSim opens a *.csv data file and finds in the first line the word "Time" in combination with either "Distance" or "LapDist" it assumes that it is a universal *.csv data file format.

LapSim assumes that in this case the data will start at the second line.

Please be aware that in case of a *.csv file, LapSim will load the complete file, not only the traces you selected like with a *.bmsbin or *.xrk file.

This means that if you make an export of ALL your channels, the *.csv file becomes unnecessary big but more important it will almost certainly become too big for LapSim to load and will lead to a crash of the program.

So please take the time to select only those channels for export which can be loaded into LapSim! And please limit the frequency rate of the export to 50 or 100 [Hz].