Driving simulators are extending the OEM’s traditional systems integration capabilities into the digital realm, combining tools and models from different suppliers to create virtual cars.

Vehicle OEMs rely on component suppliers to contribute their expertise to new products, but the car makers skilfully integrate the different elements and put the brand’s unique stamp on the finished design. That could mean finessing their signature ride and handling behavior, evolving intuitive HMI and cabin controls or, increasingly, ensuring ADAS technologies work seamlessly to enhance active safety.

But as the volume of sensors and software in vehicles increases, it’s become important, and sometimes necessary, to perform that integration in the virtual world. The development challenges of software-defined vehicles can result in physical prototypes appearing at a later stage in the program than was previously the case. Disciplines in which tuning on the proving ground was the norm, such as vehicle dynamics, increasingly turn to driver-in-the-loop (DIL) simulators as a means of proving out their designs and setups before physical cars are available to drive.

But OEMs should not have to abandon their traditional engineering tools just because they’re now testing their vehicles on virtual tracks. Cruden believes that a DIL simulator adds value if it can integrate multiple tools in a simple, standard and open way – whether it’s a tire model, a sensor simulation for ADAS, an acoustics development package or something else. By integrating the engineering tool chain and bringing together different models from different suppliers in the simulator, a driver can experience, and give feedback on, an integrated solution that would otherwise be offered only in a real car.

Simulator control software, such as Cruden’s Panthera, has two main purposes. The first is to manage what the driver experiences – the visual cues, motion, steering inputs, audio and more. But to accurately reproduce the vehicle in the virtual world, Panthera’s other function is just as critical: how it integrates with different engineering tools, including vehicle models through a simplified interface based on a software development kit (SDK).

Let’s take tire models as an example of the integration process. Models have become a required submission from would-be tire suppliers so that OEM engineers can conduct both offline and online (DIL) simulations and ensure the vehicle’s suspension and tire perform as a cohesive unit. Often this work extends beyond a Pacejka model for primary ride evaluations into more complex models like FTire to support research into secondary ride, for which it is crucial to communicate higher-frequency inputs from a detailed model of the road surface.

“The first step is to integrate the tire model into the OEM’s vehicle model,” explains Dennis Janssen, Cruden’s Panthera development team lead. “We then connect that vehicle model to Panthera. For that we have the SDK and ePhyse, our external physics model protocol. Specifically for the road interaction, it might also query SISTer (Server for Interaction with Surfaces & Terrains).”

SISTer determines how the tire contact patch interacts with the road – either by multisampling with up to 49 intersection queries per wheel, or by driving directly on a dense point set with a spatial density down to 10 mm. SISTer responds to the queries of the vehicle model in less than 1 ms, preserving the immersion of the virtual driving experience. By off-loading the tire-road interaction from the vehicle model, driving on high-fidelity road surfaces does not require additional computational power from the computer running the vehicle model.

According to Janssen, the SDK-based integration process should take days not weeks and may be accomplished by OEM engineers rather than Cruden specialists, depending on their experience.

“If an OEM engineer is capable in MATLAB Simulink, for example, then they should be able to do it themselves,” he continues. “With the SDK, we take away the detail of how Panthera communicates and how the integration works under the hood. Vehicle model specifics, such as what type of signals need to be available, are in the documentation. To route the signals from your vehicle model to Panthera, you just use the SDK and the functions we provide.”

It's a similar process to integrate a sensor model for ADAS simulations, whether the goal is to develop a new sensor using a physics-based model – running in co-simulation in a version of the virtual world tailored to the sensor’s input needs – or an ADAS controller and the HMI around it. In the latter case, the simulator can supply ground-truth information to the controller such as lane width and the position of surrounding traffic – information over which it already has full control. Adds Janssen, “It’s a different type of information being sent, but at a high level, the communication between simulator and models, and the functions we provide to achieve it, are the same.”

Acoustics engineering tools can also be integrated with a driving simulator to facilitate transfer path analysis. Sounds from the OEM’s own prototype or competing cars can be replayed in the simulator and the noise levels tweaked until the acoustics engineers pin down their targets for a new model. Again, the integration process is similar to what we’ve already seen for other tools.

“Because the SDK provides access to every signal living inside Panthera – whether it’s throttle position, engine rpm, vehicle speed, the surface that the car is driving on, or even the position and speed of surrounding vehicles – all of it can be made available to any type of tool,” says Janssen. “And once the acoustics engineering tool has been integrated with the simulator, the process does not need to be repeated for each new vehicle being evaluated.”

Whatever the integration need, Cruden believes its Panthera SDK provides a powerful interface between engineering tools and the heart of the driving simulator. This standardized, rapid approach – including the option to establish FMI interfaces – helps vehicle OEMs to create an integrated simulation ecosystem of their favourite tools. In turn, this enables them to develop better vehicles, faster and at reduced cost.

For more information, please contact Dennis Marcus via d.marcus@cruden.com or on +31 20 707 4646.

‍

Links to subsequent articles will be added below as they are published.

View all articles in our Tool Integration series of articles:

Article 1: Driving simulator and third-party engineering tool integration

Article 2: Four wheels good: Vehicle model integration for dynamics and more

Article 3: Hard decisions made easier: hardware-in-the-loop testing with DIL simulation

Article 4: In search of perfect harmony: HMI testing in a driving simulator

Article 5: New Panthera Corebox is at the heart of tool integration

Article 6: Standard interfaces for non-standard simulators

Article 8: Tool Integrations - Data acquisition

‍