Search Results

The complexity of automobile powertrains grows continuously. At the same time, development time and budget are limited. Shifting development tasks to earlier phases (frontloading) increases the efficiency by utilizing test benches instead of prototype vehicles (road-to-rig approach). Early system verification of powertrain components requires a closed-loop coupling to real-time simulation models, comparable to hardware-in-the-loop testing (HiL). The international research project Advanced Co-Simulation Open System Architecture (ACOSAR) has the goal to develop a non-proprietary communication architecture between real-time and non-real-time systems in order to speed up the commissioning process and to decrease the monetary effort for testing and validation. One major outcome will be a generic interface for coupling different simulation tools and real-time systems (e.g. HiL simulators or test benches).

In order to reduce development cost and time, frontloading is an established methodology for automotive development programs. With this approach, particular development tasks are shifted to earlier program phases. One prerequisite for this approach is the application of Hardware-in-the-Loop test setups. Hardware-in-the-Loop methodologies have already successfully been applied to conventional as well as electrified powertrains considering various driving scenarios. Regarding driving performance and energy demand, electrified powertrains are highly dependent on the dc-link voltage. However, there is a particular shortage of studies focusing on the verification of variable dc-link voltage controls by Hardware-in-the-Loop setups. This article is intended to be a first step towards closing this gap. Thereto, a Hardware-in-the-Loop setup of a battery electric vehicle is developed.

The growing number of passenger car variants and derivatives in all global markets, their high degree of software differentiability caused by regionally different legislative regulations, as well as pronounced market-specific customer expectations require a continuous optimization of the entire vehicle development process. In addition, ever stricter emission standards lead to a considerable increase in powertrain hardware and control complexity. Also, efforts to achieve market and brand specific multistep adjustable drivability characteristics as unique selling proposition, rapidly extend the scope for calibration and testing tasks during the development of powertrain control units. The resulting extent of interdependencies between the drivability calibration and other development and calibration tasks requires frontloading of development tasks.

New 12 V/48 V power net architectures are potential solutions to close the gap between customer needs and legislative requirements. In order to exploit their potential, an increased effort is needed for functional implementation and hardware integration. Shifting of development tasks to earlier phases (frontloading) is a promising solution to streamline the development process and to increase the maturity level at early stages. This study shows the potential of the frontloading of development tasks by implementing a virtual 48 V mild hybridization in an engine-in-the-loop (EiL) setup. Advanced simulation technics like functional mock-up interface- (FMI) based co-simulation are utilized for the seamless integration of the real-time (RT) simulation models and allow a modular simulation framework as well as a decrease in development time.

To achieve global market and brand specific drivability characteristics as unique selling proposition for the increasing number of passenger car derivatives, an objectified evaluation approach for the drivability capabilities of the various cars is required. Thereto, it is necessary to evaluate the influence of different engine concepts in various complex and interlinked powertrain topologies during engine load change maneuvers based on physical criteria. Such an objectification approach enables frontloading of drivability related engineering tasks by the execution of drivability development and calibration work within vehicle subcomponent-specific closed-loop real-time co-simulation environments in early phases of a vehicle development program. So far, drivability functionalities could be developed and calibrated only towards the end of a vehicle development program, when test vehicles with a sufficient level of product maturity became available.