Page 64 - ATZ WORLDWIDE

DEVELOPMENT MOTOR SPORT

Generally speaking, simulation permits a WHEN ONE RACE ENDS, races, but within a shorter period of time.
high level of test coverage and thorough ANOTHER BEGINS In the case of functional software
screening of new system approaches updates, the steps are as follows:
prior to setting up actual prototypes. The preparation for each LMP1 race can – Analyse the previous race as well as
The key factors for good integration be seen as an individual development the upcoming race from the previous
into development activities include a process. Hardware changes between races season to identify potential for
sensible choice of model complexity and are only possible to a limited extent, but it improvement for the next race.
an established catalogue of objective test is possible to develop and introduce new – Develop potential for improvement iden-
criteria and key figures that make it software functions, FIGURE 3. This is why tified in the simulation. To that end, the
possible to compare measurement and similar steps are followed as during the control system software is linked to vari-
simulation. series production process between the ous simulation environments as Soft-
ware-in-the-Loop (SiL). On the one
hand, recorded track data can be loaded
into the software to analyse direct
changes to the previous version based
on track data. On the other hand, the
software can be linked to the dynamic
simulation model to evaluate variants in
the closed control loop based on individ-
ual manoeuvres or lap time simulations.
– Test the newly developed software ver-
sion on various levels. New functions
are always tested on the Hardware-in-
the-Loop (HiL) test bench. This ensures
that the functionality is also provided
on the target hardware in the compiled
state. In addition, innovations are
tested on the driving simulator as part
of the race preparations. This ensures
that the desired influences on handling
FIGURE 2 Central simulation environment as project platform (© Porsche) are working correctly in the closed con-
trol loop. As a side effect, the test on
the driving simulator in a realistic envi-
ronment also checks the functional
robustness. The driving simulator also
makes it possible to develop the appli-
cation of the software based on the
data gathered and subjective driver
evaluation in rapid iteration steps.
Updates, which to a large extent are
directly linked to the hardware, will
continue to be released on drive test
benches as well as during test drives on
the test track where necessary.

BOOST STRATEGY ON THE
DRIVING SIMULATOR
The 2016 season race in Mexico is a con-
crete example of the process and the inte-
gration of the development tools as part of
the race preparations. The WEC was held
in Mexico for the first time in 2016, which
meant that none of the competitors had
any experience on the race track. This
made the importance of the simulation
tools more evident than in other races.
A key issue as part of the race prepara-
tion is the development of the boost strat-
FIGURE 3 Steps during the software development process between races (© Porsche) egy. It defines the permitted amount of
62