Validation of Automated Driving Function Based On
Validation of Automated Driving Function Based On
Abstract: With the increasing complexity of automated driving features, it is crucial to adopt inno-
vative approaches that combine hardware and software to validate prototype vehicles in the early
stages of development. This article demonstrates the effectiveness of a Vehicle-in-the-Loop (ViL)
testbed in conducting dynamic tests of vehicles equipped with highly automated driving functions.
The tests are designed to replicate critical driving scenarios from real-world environments on the
ViL testbed. In this study, the Apollo platform is utilized to develop an automated driving function
that can perceive the surrounding traffic in a virtual environment and generate feasible trajectories.
This is achieved with the help of a multibody simulation platform. The control commands from the
simulated driving function are then transmitted to the real vehicle to execute the planned action. The
results demonstrate that critical traffic scenarios can be replicated more safely and repeatedly on the
ViL testbed. Meanwhile, the Apollo-based driving function can effectively and comfortably cope
Citation: Li, H.; Makkapati, V.P.;
with critical scenarios. Importantly, this study marks a significant milestone for the Apollo platform
Wan, L.; Tomasch, E.; Hoschopf, H.;
as it is implemented in a real-time system and tested on a ViL testbed.
Eichberger, A. Validation of
Automated Driving Function Based on
the Apollo Platform: A Milestone for
Keywords: Apollo platform; vehicle-in-the-loop; automotive engineering; virtual simulation
Simulation with Vehicle-in-the-Loop
Testbed. Vehicles 2023, 5, 718–731.
https://doi.org/10.3390/
vehicles5020039 1. Introduction
Academic Editor: Mohammed
As automotive electrical and electronic technology advances, the complexity of auto-
Chadli motive network topologies increases, necessitating real-world vehicle testing to optimize
and validate ECU (electronic control unit) functionality. With the rising demand for Highly
Received: 26 May 2023 Automated Driving (HAD), validating the relevant system presents a significant challenge.
Revised: 6 June 2023 It requires complete vehicle and ECU network coverage while ensuring the safety and effi-
Accepted: 12 June 2023
ciency of verification procedures. Thus, scenario-based proving-ground tests are no longer
Published: 16 June 2023
sufficient as they cannot provide the complex and dynamic environment necessary for
comprehensive validation. Simulated scenario-based validation has emerged as a dominant
solution, known as X-in-the-loop (XiL), and is used throughout the automotive develop-
Copyright: © 2023 by the authors.
ment process. The authors of [1] provide a detailed presentation of simulation methods
Licensee MDPI, Basel, Switzerland. for each stage of the V-model. They suggest that X-in-the-loop (XiL), hardware-in-the-loop
This article is an open access article (HiL), driver-in-the-loop (DiL), and vehicle-in-the-loop (ViL) solutions are the most com-
distributed under the terms and prehensive solutions for software decisions, controller actuation and sensor perception
conditions of the Creative Commons validation of advanced driver assistance systems (ADAS). However, the HiL system has
Attribution (CC BY) license (https:// significant maintenance and modification requirements and often uses non-mass-produced
creativecommons.org/licenses/by/ wiring harnesses, resulting in electromagnetic interference issues. DiL evaluates vehicle-
4.0/). human interaction and is suitable for assessing ADAS function and comfort and driver
reaction. ViL bridges the gap between all previous solutions and enables integrated vehicle
testing in a virtual environment.
Innovation in ViL technology has been ongoing for over two decades since the pio-
neering solution provided by TNO Automotive [2]. In the current state of the art, ViL-based
testing approaches are diverse. Despite the long-standing development of ViL technology,
there have been limited reviews or surveys conducted on relevant applications. A classifica-
tion system is proposed based on the implemented technology of testing to better illustrate
the current state of the art, as below:
• Closed-Area Testing: In contrast to open-road testing, closed-area testing is considered
a safer alternative. Generally, a GPS-equipped test vehicle drives within a test field
and maps its position to the simulation environment in real-time [3]. In the context
of ADAS testing, the sensory information generated by the simulated scenario is
transmitted in a suitable format to the relevant ECUs or real sensors on the test vehicle
to trigger the ADAS functions [4]. As a result, the real-time system must perform
optimally and is subdivided into a cloud-based system and an on-board real-time
system. For the former, the back-end achieves remote control of the vehicle through
communication technology (e.g., LTE-V or 5G) [5–7]. However, due to the ease of
integration, the majority of the technical implementation is carried out using the on-
board real-time system. The in-vehicle system achieves synchronization between the
road logic, traffic scenarios and the vehicle’s position, thereby enabling the generation
of synthetic sensory data that can trigger actual sensors and elicit appropriate reactions
from real vehicles [8–10]. Despite the wide usage of closed-area testing, it is not
without its limitations. One such limitation is the need for a substantial investment in
a large open area. Additionally, high dynamic testing can still pose hazards, and the
vehicle under test (VUT) trajectory remains uncontrollable [11].
• Chassis Dynamometer Testing: To compensate for the huge waste of space in closed-
area testing and to ensure a certain degree of high dynamic testing, a roller testbed
test has been used in several studies. This is essentially a rolling road that measures
the power output of the engine while the vehicle’s wheels are turning. For example,
a series of groundbreaking investigations are presented in [2,12]. Subsequently, the
use of simulation software to create a virtual environment was demonstrated to be
a more efficient approach for validation in [13–15]. A co-simulation framework has
been proposed to enhance the simulation scenario, enabling sensor stimulation on the
testbed [16,17]. Although this type of bench was initially designed for emission tests,
it has been extended to validate ADAS and can facilitate sensor stimulation due to its
cost-effectiveness.
• Powertrain Testbed Testing: A roller testbed is no longer sufficient for achieving highly
dynamic manoeuvres; hence, the powertrain testbed was introduced. Powertrain
setups connect each wheel hub to a dyno simulating driving resistance at each wheel.
To achieve comparable results with a rolling test rig, an additional rolling resistance
simulation and an accurate tire simulation are required. For example, a distinctive
feature of the test bench described in [18,19] is the integration of the alignment of
torque simulation units, which employ wheel actuators to generate the corresponding
aligning torque through a mechanical connection. The KS-R2R (road-to-rig) [20]
technology differs from current approaches in that it employs complete wheel models
instead of solely relying on tire models [21,22]. These models utilize torque as input
and speed as an output, aligning more closely with the natural sequence of cause and
effect. In the field of ADAS testing, a common approach is to use sensor stimulation as
a solution, which has been widely adopted in many works [18,21,23–25]. In contrast
to previous approaches that utilized sensor stimulation for ADAS validation, [22]
provides an abstract representation of real sensors and ADAS functionality. This
supports the development of ADAS functionality by demonstrating its feasibility
in prototype vehicles during the functional concept phase. Overall, the powertrain
testbed is not only capable of achieving highly dynamic manoeuvres but is also highly
Vehicles 2023, 5 720
2. System Design
The ViL simulation system comprises two main components: a simulation platform
and a vehicle under test. For the simulation part, KS Tornado (automation software
from KS engineers) [26] acts as the main GUI, which interfaces with Carmaker from IPG
Automotive and the real-time system KS ADAC (Advanced Data Acquisition and Control),
which controls the KS-R2R testbed. The virtual vehicle environment inclusive of the
vehicle, traffic scenario and road model is built in CarMaker from IPG Automotive and the
visualization of virtual scenarios is also supported. Moreover, vehicle dynamics, sensor
models and Apollo functions are integrated into CarMaker by utilizing S-functions and
APIs in Simulink. The resulting model is then translated into C-code and embedded into
the Xpack4 real-time system from IPG Automotive, which is capable of processing data at
a rate of 1 kHz. Additionally, the employed mathematical models for loaded tires and the
testbed are implemented in KS ADAC, which runs at a frequency of 5 kHz. It is important
to note that the Testbed model is solely employed for offline simulations and does not
encompass the online tests discussed in this paper. The EtherCAT technology [27] achieves
real-time performance and topology flexibility between ADAC and Xpack4 to enable a
co-simulation system.
Eventually, the vehicle under test (VUT) is fixed on the KS-R2R testbed using special
testbed wheels with lead-through shafts, and a driving robot manipulates the measured
quantities to match the driving manoeuvre preset in the simulation according to the KS
ADAC control commands. Meanwhile, the real-time dynamics and operational status of the
VUT on the testbed can also be transmitted back to CarMaker via KS-ADAC, allowing them
to be read in CarMaker. This enables the virtual simulation scenario to reflect the actions
and reactions of the actual VUT, thus creating a closed-loop system. The architecture of
the entire ViL system is elaborated in Figure 1. Therefore, the introduction of subsequent
sections all revolve around this basic ViL architecture. Section 3.1 of this study presents the
introduction of the Restbus Simulation (RBS) for the testbed, focusing on its implementation
and functionality. Section 3.2 provides details on the configuration and setup of the testbed
for conducting the simulations. The successful implementation of the sensor model is
demonstrated in Section 4.1, while Section 4.2 showcases the successful integration and
operation of the Apollo function within the simulation environment. Lastly, Section 4.3
introduces the virtual scenario that serves as the case study for this research.
Vehicles 2023, 5 721
3. Vehicle-in-the-Loop Testbed
The modified VUT on the testbed requires a novel powertrain bench to achieve
highly dynamic manoeuvres and reduce the simulation-to-reality gap. Consequently, to
adequately satisfy our testing prerequisites, it is crucial to undertake modifications to the
vehicle bus system. Furthermore, the novel testbed offers the possibility of conducting
authentic on-road driving scenarios on the engine, powertrain, and tire dynamics.
is accurately reflected in the real vehicle. Therefore, the gateways responsible for data
transmission retrieve the relevant signals from the simulation in real-time and modify them
on the FlexRay bus to align with the desired test conditions.
Figure 2. Electrical/electronic architecture of the vehicle under test with signal manipulation for
testing and simulation purposes.
in Apollo. Therefore, the power-consuming EM planner (see [34]) is replaced with a lattice
planner (see [35]) to achieve a more stable and smooth planning process. The basic principle
involves scattering path points ahead of the vehicle and connecting discrete points with
fifth-order polynomials to construct a grid. The path cost for each edge in the graph is
calculated using the overall objective function, which is a linear combination of smoothness,
obstacle avoidance, and reference line cost. After calculating the cost of each possible path
and distinguishing them, as shown in Figure 4, with different colours, the path with the
minimum cost and the corresponding speed is selected and sent to the control module.
Application of this concept enables more reasonable decisions to be made for overtaking or
following while also planning for trajectory and speed.
In [36], the authors present an introduction to the lateral and longitudinal control
strategy employed in Apollo. Specifically, the linear quadratic regulator (LQR) controller
is used to generate the optimal steering command based on the current vehicle state and
planned trajectory. The use of an LQR controller for lateral control ensures that the vehicle
can accurately follow the desired trajectory while maintaining stability and smoothness
in the control input. Additionally, the longitudinal controller in Apollo utilizes a two-
stage proportional–integral–derivative (PID) controller for station and speed control, as
well as a throttle/brake calibration table. It receives planned trajectories, localization
information, and vehicle motion data to generate appropriate throttle and brake commands
for the vehicle.The displacement PID controller takes the desired and current position
information as inputs and forwards the speed compensation to the subsequent speed PID
controller. At this stage, the speed and planned velocity compensation serve as inputs
for generating acceleration compensation, which is passed through calibration tables.
Overall, The trajectory controller in the system is responsible for generating steering angle
commands to the real vehicle that maintain the vehicle’s position on the planned path,
while the speed controller regulates the vehicle’s speed by modulating the throttle and
brake pedals in percentage activity.
5. Case Studies
The ViL testbed allows for highly accurate and repeatable testing of ADAS functions
in a controlled and repeatable environment. It also provides greater flexibility for function
integration and sensor model implementation. By creating digital twin-based test scenarios,
the ViL testbed can evaluate critical cases in a safer manner, reducing the risks associated
with real-world testing. Furthermore, the reproducibility and comprehensive data collection
capabilities of the testbed enable a more accurate and detailed analysis of the performance
of ADAS functions.
Vehicles 2023, 5 726
In order to reduce the intricacy of the trajectory analysis, subsequent analyses of the
results employed the Frenet coordinate system, where S represent the longitudinal distance
along the route, and L indicates the lateral deviation according to the reference line. The
reference line for this system is established based on the centerline of the starting lane of
the ego car. To analyze and compare the driving reaction of the Apollo automated driving
system and a human driver in response to a target vehicle manoeuvre, the trajectories
of the three entities are plotted in Figure 6. The identical analytical methodology is also
implemented in Section 5.2.
The simulation results of the trajectory in Figure 6, presented in the S-L coordinate,
reveal that the Apollo-based driving function demonstrates driving behaviour comparable
to that of a human driver before the 10-s mark, particularly in terms of longitudinal and
lateral displacement. This similarity is achieved by setting the initial conditions in the
test bench to match the driving conditions in a real-world scenario, providing a solid
foundation for evaluating subsequent Apollo decisions. Between the time interval of 10 to
13 s, a noticeable difference arises in the decision-making of the human driver, who opts
to decelerate from 77 km/h to approximately 60 km/h in response to the presence of the
truck ahead. In contrast, the Apollo-based driving function maintains a predetermined
cruising speed during the same time interval and does not proactively respond to the
presence of the forward truck. However, the Apollo automated driving system and the
human driver exhibit similar driving behaviour in response to a target car manoeuvre,
with a lane change after 13 s. However, the decisions of the two diverge after 16 s, with
the human driver preferring to remain in the new lane. In contrast, the Apollo system,
guided by a single-reference line, actively returns the vehicle to the original lane after
completing the lane change, which causes a 1 m offset in the L-direction trajectory due
to the comfort weight constraint. Additionally, the velocity plot shows that the human
driver decelerates significantly in response to a sudden speed reduction of the car in front,
Vehicles 2023, 5 727
while the Apollo system only slightly decelerates at the beginning of the lane change to
maintain comfort. Nonetheless, the final simulation results confirm that the automated
driving system can effectively handle emergency avoidance scenarios. However, further
calibration and planning strategies are required to enhance the system’s ability to learn
from human driving behaviour. The time interval between 15 and 18 s is particularly
notable for assessing lateral controllability. Excessive lateral displacement has the potential
to mitigate risks, but it may also introduce discomfort for passengers. This aspect warrants
further investigation in future research endeavours.
Figure 6. Evasive lane change scenario: comparing the response of the Apollo automated driving
system and a human driver to a target vehicle manoeuvre.
The present study aims to validate Apollo’s decision on speed planning for a high-
speed collision scenario. In this real accident scenario, the human driver’s lack of timely
reaction to potential danger often leads to collisions. Figure 8 shows the motion process
of the target car five seconds before the collision. During the initial four-second period,
both the trajectory of the Apollo-based driving function and the human driver exhibit
comparable behaviour. This alignment of trajectories serves as a suitable starting point
for testing subsequent manoeuvres. The velocity profile indicates that the human driver
realized the need to slow down only 0.8 s before the collision, which was already too late.
Such accidents are often caused by distraction of the driver’s attention. The analysis of
the trajectory in the L-direction shows that the human driver exhibited abnormal driving
behaviour characterized by lane departure during the time interval of 0–4 s before the
occurrence of the accident. In contrast, the Apollo-based driving function effectively
maintained the vehicle’s position in the middle of the road due to the proper weighting of
the centre line constraints of the lane. Additionally, the target car begins to move towards
the left lane from 2.5 s onwards. In contrast, Apollo’s speed planning module predicted
the target car’s motion in the adjacent lane and initiated a slow deceleration to adjust the
distance between the cars. When the front car invaded the ego car lane at 3 s, the ego car
decelerated at a rate of approximately −7 m/s2 to avoid a collision. At the end of 5 s, a safe
distance of 10 m is maintained from the target car, as shown in the S-direction plot. This
demonstrates the benefit of automated driving, which continuously monitors the road and
ensures safety, unlike a human driver prone to distraction and delayed reaction to potential
dangers.
Figure 8. Preventing collisions scenario: comparing the response of the Apollo automated driving
system and a human driver to a target vehicle manoeuvre.
Vehicles 2023, 5 729
6. Discussion
In this study, we introduce and test an Apollo-based HAD function on the ViL testbed,
marking a significant milestone in implementing this HAD function within a real-time
simulation system. Two scenarios are successfully replicated, rear-end collision prevention
and evasive lane change, on the testbed, showcasing the potential of digital twin-based
simulation testing. However, it is essential to note that the current Apollo system lacks
the comfort aspect exhibited by human drivers, particularly in the case of evasive lane
change, where human drivers demonstrate better speed control and lane change path
comfort. Calibration of the Apollo system parameters emerges as a potential avenue for
future research. Nonetheless, the excellent performance in rear-end collision prevention
highlights the system’s reliable response to critical situations. The reliance on sensor
perception allows for early detection of potential risks, with Apollo reacting appropriately.
Overall, the proposed simulation framework depicted in Figure 1 exhibits robust reliability
in executing Apollo-based driving functions and offers flexibility for future extensions. The
ViL setup is able to replicate highly dynamic driving scenarios which cannot be replicated
on public roads but also maybe not on proving grounds because of the high speeds which
makes it complicated to maintain safety.
7. Conclusions
This study presents the development of a co-simulation framework to construct a com-
plete vehicle simulation environment using a ViL testbed. The experimental results reveal
that the inclusion of the complete vehicle within the simulation environment enhances the
realism of the testing setup, thereby potentially facilitating future virtual homologation
efforts, and HAD functions should be tested on the full vehicle level. The ViL testbed pro-
vides a viable option to balance virtual validation and real-world testing, which mitigates
potential risks associated with public road testing. The successful re-engineering of the
Apollo automated driving system and its implementation on the ViL bench showcases
the possibility of testing future SAE Level 4 fuctions not yet implemented in the vehicle
under test. This achievement validates the feasibility of running complex systems on
real-time platforms. Furthermore, scenario-based simulations have demonstrated Apollo’s
competence in responding to real-life hazardous situations, highlighting its potential to
enhance road safety. This study emphasizes the significance of full vehicle testing and
provides a reliable and safe testing platform for developing HAD functions.
In our future work, Apollo systems will continue to be optimized and enhanced, particu-
larly by enhancing the trajectory planning module to better emulate human driver behaviour.
Furthermore, the incorporation of more complex traffic flow scenarios to validate and test the
efficiency of Apollo on the ViL testbed is intended.
Author Contributions: Conceptualization, H.L., V.P.M., E.T. and A.E.; methodology, H.L., V.P.M.,
E.T. and A.E.; software, H.L., V.P.M., E.T., L.W. and A.E.; validation, H.L., V.P.M., E.T., L.W. and A.E.;
formal analysis, H.L., V.P.M., E.T., H.H., L.W. and A.E.; investigation, H.L., V.P.M., E.T., H.H., L.W.
and A.E.; resources, H.L., V.P.M., E.T., H.H., L.W. and A.E.; data curation, H.L., V.P.M., E.T., L.W.
and A.E.; writing—original draft preparation, H.L., V.P.M., E.T., L.W. and A.E.; writing—review and
editing, H.L., V.P.M., E.T., L.W. and A.E.; visualization, H.L., V.P.M., E.T., L.W. and A.E.; supervision,
A.E.; project administration, A.E. All authors have read and agreed to the published version of
the manuscript.
Funding: Open Access Funding by the Graz University of Technology. This activity is part of the
research project InVADE (FFG nr. 889349) and has received funding from the program Mobility
of the Future, operated by the Austrian research funding agency FFG. Mobility of the Future is
a mission-oriented research and development program to help Austria create a transport system
designed to meet future mobility and social challenges.
Institutional Review Board Statement: Not applicable.
Informed Consent Statement: Not applicable.
Vehicles 2023, 5 730
References
1. Magosi, Z.F.; Li, H.; Rosenberger, P.; Wan, L.; Eichberger, A. A Survey on Modelling of Automotive Radar Sensors for Virtual Test
and Validation of Automated Driving. Sensors 2022, 22, 5693. [CrossRef] [PubMed]
2. Verhoeff, L.; Verburg, D.; Lupker, H.; Kusters, L.J. VEHIL: A full-scale test methodology for intelligent transport systems, vehicles and
subsystems. In Proceedings of the IEEE Intelligent Vehicles Symposium 2000 (Cat. No. 00TH8511), Dearborn, MI, USA, 5 October 2000;
pp. 369–375.
3. Bhadani, R.K.; Sprinkle, J.; Bunting, M. The cat vehicle testbed: A simulator with hardware in the loop for autonomous vehicle
applications. arXiv 2018, arXiv:1804.04347.
4. Miquet, C. New test method for reproducible real-time tests of ADAS ECUs: “Vehicle-in-the-Loop” connects real-world vehicles
with the virtual world. In 5th International Munich Chassis Symposium 2014: Chassis. Tech Plus; Springer: Wiesbaden, Germany,
2014; pp. 575–589.
5. Che, X.; Li, C.; Zhang, Z. An Open Vehicle-in-the-Loop Test Method for Autonomous Vehicle; EasyChair: Manchester, UK, 2019.
6. Fayazi, S.A.; Vahidi, A.; Luckow, A. A Vehicle-in-the-Loop (VIL) verification of an all-autonomous intersection control scheme.
Transp. Res. Part C Emerg. Technol. 2019, 107, 193–210. [CrossRef]
7. Gelbal, Ş.Y.; Tamilarasan, S.; Cantaş, M.R.; Güvenç, L.; Aksun-Güvenç, B. A connected and autonomous vehicle hardware-in-
the-loop simulator for developing automated driving algorithms. In Proceedings of the 2017 IEEE International Conference on
Systems, Man, and Cybernetics (SMC), Banff, AB, Canada, 5–8 October 2017; pp. 3397–3402.
8. Tettamanti, T.; Szalai, M.; Vass, S.; Tihanyi, V. Vehicle-in-the-loop test environment for autonomous driving with microscopic
traffic simulation. In Proceedings of the 2018 IEEE International Conference on Vehicular Electronics and Safety (ICVES), Bogota,
Colombia, 14–16 November 2022; pp. 1–6.
9. Drechsler, M.F.; Sharma, V.; Reway, F.; Schütz, C.; Huber, W. Dynamic vehicle-in-the-loop: A novel method for testing automated
driving functions. SAE Int. J. Connect. Autom. Veh. 2022, 5, 367–380. [CrossRef]
10. Chen, Y.; Chen, S.; Xiao, T.; Zhang, S.; Hou, Q.; Zheng, N. Mixed test environment-based vehicle-in-the-loop validation-a new
testing approach for autonomous vehicles. In Proceedings of the 2020 IEEE Intelligent Vehicles Symposium (IV), Las Vegas, NV,
USA, 19 October–13 November 2020; pp. 1283–1289.
11. Ferguson, D.; Howard, T.M.; Likhachev, M. Motion planning in urban environments. In The DARPA Urban Challenge: Autonomous
Vehicles in City Traffic; Springer: Berlin/Heidelberg, Germany, 2009; pp. 61–89.
12. Verbürg, D.; van der Knaap, A.C.; Ploeg, J. Developing and testing intelligent vehicles. In Proceedings of the IEEE Intelligent
Vehicle Symposium (IV’2002), Versailles, France, 18–20 June 2002; pp. 1–8.
13. Gietelink, O.; Ploeg, J.; Schutter, B.; Verhaegen, M. Testing advanced driver assistance systems for fault management with the
VEHIL test facility. In Proceedings of the 7th International Symposium on Advanced Vehicle Control, Arnhem, The Netherlands,
23–27 August 2004; pp. 579–584.
14. Albers, A.; Düser, T. A new process for configuration and application of complex validation environments using the example of
vehicle-in-the-loop at the roller test bench. In Proceedings of the ASME International Mechanical Engineering Congress and
Exposition, Vancouver, BC, Canada, 12–18 November 2010; Volume 44489, pp. 807–816.
15. Albers, A.; Düser, T. Implementation of a vehicle-in-the-loop development and validation platform. In Proceedings of the FISITA
World Automotive Congress, Budapest, Hungary, 30 May–4 June 2010; Volume 2010.
16. Solmaz, S.; Holzinger, F. A novel testbench for development, calibration and functional testing of ADAS/AD functions. In
Proceedings of the 2019 IEEE International Conference on Connected Vehicles and Expo (ICCVE), Graz, Austria, 4–8 November
2019; pp. 1–8.
17. Qin, Y.; Tang, A.; Jia, J.; Wan, L.; Zhao, H.; Long, Y. Research on Radiated Immunity Test Methods for ADAS Functions
Considering Vehicle In-the-Loop. World Electr. Veh. J. 2022, 13, 211. [CrossRef]
18. Diewald, A.; Kurz, C.; Kannan, P.V.; Gießler, M.; Pauli, M.; Göttel, B.; Kayser, T.; Gauterin, F.; Zwick, T. Radar target simulation
for vehicle-in-the-loop testing. Vehicles 2021, 3, 257–271. [CrossRef]
19. Rautenberg, P.; Kurz, C.; Gießler, M.; Gauterin, F. Driving Robot for Reproducible Testing: A Novel Combination of Pedal and
Steering Robot on a Steerable Vehicle Test Bench. Vehicles 2022, 4, 727–743. [CrossRef]
Vehicles 2023, 5 731
Disclaimer/Publisher’s Note: The statements, opinions and data contained in all publications are solely those of the individual
author(s) and contributor(s) and not of MDPI and/or the editor(s). MDPI and/or the editor(s) disclaim responsibility for any injury to
people or property resulting from any ideas, methods, instructions or products referred to in the content.