Automotive Software Engineering

Schäuffele, Jörg; Zurawka, Thomas

doi:10.1007/978-3-658-11815-0

Cited by 36 publications

(12 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Definition 5 (Networked XiL): X-in-the-Loop (XiL) refers to model, software, processor, and hardware inthe-Loop. There are different definitions for XiL, e.g., in [32]- [35]. We define model, software, and hardware in-the-loop as follows.…”

Section: Organization Of This Articlementioning

confidence: 99%

An Architecture for Experiments in Connected and Automated Vehicles

Kloock¹,

Scheffe²,

Greß³

et al. 2023

Preprint

View full text Add to dashboard Cite

Rapid prototyping of a Networked Control System (NCS) is challenging because of the physical distribution of agents. Furthermore, experiments with NCS may be subject to external influences which prevent reproducibility. This article presents an architecture for experimental testing of NCS with focus on decision-making. Our architecture for experiments of NCS is strictly modular and hierarchical, and therefore it supports an easy and rapid exchange of each single controller as well as of optimization libraries. Additionally, the architecture synchronizes the whole network of sensors, computation devices, and actuators. Thus, it achieves deterministic and reproducible results, even for time-variant network topologies. Using this architecture, we are able to include active and passive agents and agents with heterogeneous dynamics in the experiments. The architecture also allows handling communication uncertainties, e.g., data packet drop and time delay. The resulting architecture supports performing in-the-loop tests on the model, software, and hardware levels.<br>We demonstrate the architecture in the Cyber-Physical Mobility Lab (CPM Lab) using 20 agents. The architecture can be applied to other domains. <br>

show abstract

Section: Organization Of This Articlementioning

confidence: 99%

An Architecture for Experiments in Connected and Automated Vehicles

Kloock¹,

Scheffe²,

Greß³

et al. 2023

Preprint

View full text Add to dashboard Cite

show abstract

“…This may interact with the Lubrication System DPS and the Transmission DPS. Moreover, control path models for a model-in-the-loop (MIL), software-in-the-loop (SIL), and hardware-in-the-loop (HIL) simulation 27 are generated for developing the control unit software.…”

Section: Exemplary Bev Dpssmentioning

confidence: 99%

Virtual powertrain development

Fietkau¹,

Kistner²,

Munier³

2020

Proceedings of the Institution of Mechanical Engineers, Part D:

View full text Add to dashboard Cite

This article presents the new system of virtual powertrain development introduced at Porsche AG that incorporates all phases of the development process, as well as all components and simulation disciplines. The system enables a powertrain in its entirety to be designed and tested virtually. Most activities can be planned and budgeted at the beginning of the project, and interactions that occur are systematically taken into consideration. The hardware-driven development process used until now is completely transmitted to the digital world. Powertrain development is divided into thirteen digital powertrain systems (DPSs), which contain different components and disciplines and are developed throughout the entire product development process. For each DPS, tasks, links, time schedules, reporting scopes, and responsibilities are precisely defined. Finally, a digital vehicle prototype is built from several DPSs. The results are aggregated in several stages, ensuring that core statements are consistently incorporated at all assessment levels, from the individual component to the overall vehicle. Furthermore, this article discusses in detail DPSs that are especially important for battery electric vehicles. For most of the examples, the powertrain of the Porsche Taycan is used. The Driving Performance and Load Spectra DPS provide the necessary design parameters for a new drive system. In the Electric Motor DPS, active parts of the electric motor are designed and all structural components are verified. In the Transmission DPS, all gear set parts are designed and verified. In the Cooling, Lubrication and Actuation DPS, all temperatures are calculated and the lubrication circuit is designed. The Powertrain Dynamics DPS provides information on powertrain vibrations. The article closes with a look at future development trends. The aim is not just to design and verify components but also to completely virtualize function and software development. Therefore, this article presents a system for creating and using a virtual development environment and tracking the results.

show abstract

“…However, adding functionality—paralleled by car domains that evermore correlate—ramps up complexity as well as required processing performance . Furthermore, there is a prevalent endeavor to save space and reduce weight by decreasing the number of “Electronic Control Units” (ECUs), which can be achieved by replacing them with distinctly less (but more powerful) “domain controllers” .…”

Section: Introductionmentioning

confidence: 99%

Parallelizing highly complex engine management systems

Kienberger

Schmidhuber²,

Saad

et al. 2017

Concurrency and Computation

View full text Add to dashboard Cite

Summary The automotive industry seeks to include more and more features in its vehicles. For this purpose, the necessary policy shift towards multi‐core technology is in full swing. To eventually exploit the extra processing power, there is much additional effort needed for coping with the tremendously increased complexity. This is largely due to the elaborate parallelization process that spans a vast search space. Consequently, there is a strong need for innovative methods and appropriate tools for the migration of legacy single‐core software. We use the results of a data dependency analysis performed on AUTOSAR system descriptions to determine advantageous partitions as well as initial task‐to‐core mappings. Afterwards, the extracted information serves as input for the simulation within a multi‐core timing tool suite. Here, the initial solution is evaluated with respect to proper scheduling and metrics like cross‐core communication rates, communication latencies, or core load distribution. A subsequent optimization process improves the initial solution and enables a comparative assessment. To demonstrate the benefit, we substantially expand a previous case study by applying our approach to two complex engine management systems and by showing the advantages compared to a parallelization process without preceding dependency analysis and initial partition/mapping suggestions.

show abstract

Automotive Software Engineering

Cited by 36 publications

References 0 publications

An Architecture for Experiments in Connected and Automated Vehicles

An Architecture for Experiments in Connected and Automated Vehicles

Virtual powertrain development

Parallelizing highly complex engine management systems

Contact Info

Product

Resources

About