Search Results

The development of perception functions for tomorrow’s automated vehicles is driven by enormous amounts of data: often exceeding a gigabyte per second and reaching into the terabytes per hour. Data is typically gathered by a fleet of dozens of mule vehicles which multiply the data generated into the hundreds of petabytes per year. Traditional methods for fueling data-driven development would record every bit of every second of a data logging drive on solid-state drives located on a PC in the vehicle. Recorded data must then be exported from these drives using an upload station which pushes to the data lake after arriving back at the garage. This paper considers different techniques for curating logged data.

In recent years, the concept of hybrid test systems consisting of real and virtual parts emerged in the aerospace industry. The concept features a communication infrastructure that provides the standardized transport mechanisms required for interoperability. For example, this allows system integrators to easily reuse and exchange laboratory tests means, even if they originate from different suppliers. The “Virtual and Hybrid Testing Next Generation” (VHTNG) research project aims at creating a standard for such an infrastructure. One central aspect is the unified monitoring and control of the test equipment. So far, VHTNG has primarily focused on monitoring and controlling related aspects of the test bench in a local environment. However, recent events have repeatedly shown that it becomes increasingly important to monitor and control test benches remotely.

This paper presents a demonstrator developed in the European CleanSky2 project MISSION (Modelling and Simulation Tools for Systems Integration on Aircraft). Its scope is the development towards a seamless integrated, interconnected toolchain enabling more efficient processes with less rework time in todays, highly collaborative aerospace domain design applications. The demonstration described here, consists of an open, modular and multitool platform implementation, using specific techniques to achieve fully traceable (early stage) requirements verification by virtual testing. The most promising approach is a model based integration along the whole process from requirements definition to the verified, integrated (and certified) system. Extending previous publications in this series, the paper introduces the motivation and briefly describes the technical background and a potential implementation of a workflow suitable for that target.

In the aerospace industry, methods for virtual testing cover an increasing range of test executions carried out during the development and test process of avionics systems. Over the last years, most companies have focused on questions regarding the evaluation and implementation of methods for virtual testing. However, it has become more and more important to seamlessly integrate virtual testing into the overall development process. For instance, a company’s test strategy might stipulate a combination of different methods, such as SIL and HIL simulation, in order to benefit from the advantages of both in the same test process. In this case, efforts concentrate on the optimization of the overall process, from test specification to test execution, as well as the test result evaluation and its alignment with methods for virtual testing.

Hybrid test systems are gaining more and more significance in the aerospace industry. At the heart of these systems is a standardized communication infrastructure. There are many challenges when designing the communication infrastructure. For example, it requires very specific knowledge to boot a hybrid system, manage its configuration process, and start and stop the execution of applications, such as simulations, panels or recorders. Likewise, when testers use a heterogeneous test environment, they cannot commit themselves too much to every single test means and its special characteristics. Nevertheless, testers must always be able to monitor and control every test system. This means, they must be able to determine the current overall system status and the current status of its components and parts. Examples for this are hardware components, such as real-time processors and I/O boards, as well as software applications, such as real-time simulations models on the test system.

The application of a communication infrastructure for hybrid test systems is currently a topic in the aerospace industry, as also in other industries. One main reason is flexibility. Future laboratory tests means (LTMs) need to be easier to exchange and reuse than they are today. They may originate from different suppliers and parts of them may need to fulfill special requirements and thus be based on dedicated technologies. The desired exchangeability needs to be achieved although suppliers employ different technologies with regard to specific needs. To achieve interoperability, a standardized transport mechanism between test systems is required. Designing such a mechanism poses a challenge as there are several different types of data that have to be exchanged. Simulation data is a prominent example. It has to be handled differently than control data, for example. No one technique or technology fits perfectly for all types of data.

This paper presents an overview of a project called “Modelling and Simulation Tools for Systems Integration on Aircraft (MISSION)”. This is a collaborative project being developed under the European Union Clean Sky 2 Program, a public-private partnership bringing together aeronautics industrial leaders and public research organizations based in Europe. The provision of integrated modeling, simulation, and optimization tools to effectively support all stages of aircraft design remains a critical challenge in the Aerospace industry. In particular the high level of system integration that is characteristic of new aircraft designs is dramatically increasing the complexity of both design and verification. Simultaneously, the multi-physics interactions between structural, electrical, thermal, and hydraulic components have become more significant as the systems become increasingly interconnected.

Increasing productivity along the development and verification process of safety-related projects is an important aspect in today’s technological developments, which need to be ever more efficient. The increase of productivity can be achieved by improving the usability of software tools and decreasing the effort of qualifying the software tool for a safety-related project. For safety-critical systems, the output of software tools has to be verified in order to ensure the tools’ suitability for safety-relevant applications. Verification is particularly important for test automation tools that are used to run hardware-in-the-loop (HIL) tests of safety-related software automatically 24/7. This qualification of software tools requires advanced knowledge and effort. This problem can be solved if a tool is suitable for developing safety-related software. This paper explains how this can be achieved for a COTS test automation tool.

Hardware-in-the-loop (HIL) testing is indispensable in the software development process for control units and has been an integral part of the software development process for years. Large HIL systems for integration tests are used to test the correct behavior of distributed functions and the communication between the control units. The vast development programs that are involved require building duplicates of such test systems or parts of them, due to the fact that the tasks are distributed between different companies or different departments within a company. However, there is an alternative to duplicating a test system. Instead of using a cloned system, coupling HIL systems over large distances is an alternate approach. This paper presents what requirements this coupling must fulfill and and describes a path-breaking method to fulfill them. In addition, results of an implementation are shown.

To make the development of complex aircraft systems manageable and economical, tests must be performed as early as possible in the development process. The test goals are already set in advance before the first hardware for the ECUs exists, to be able to make statements about the system functions or possible malfunctions. This paper describes the requirements on and solutions for test systems for ECUs that arise from these goals. It especially focuses on how a seamless workflow and consistent use of test systems and necessary software tools can be achieved, from the virtual test of ECUs, which exist only as models, up to the test of real hardware. This will be shown in connection with a scalable, fully software-configurable hardware-in-the-loop (HIL) technology. The paper also covers the seamless use of software tools that are required for HIL testing throughout the different test phases, enabling the reuse of work products throughout the test phases.

Model-based development is the established way of developing embedded control algorithms, especially for safety-critical applications. The aim is to improve development efficiency and safety by developing the software at a high abstraction level (the model) and by generating the implementation (the C code) automatically from the model. Although model-based development focuses on the models themselves, downstream artifacts such as source code or executable object code have to be considered in the verification stage. Safety standards such as ISO 26262 require upper bounds to be determined for the required storage space or the execution time of real-time tasks, and the absence of run-time errors to be demonstrated. Static analysis tools are available which work at the code level and can prove the absence of such errors. However, the connection to the model level has to be explicitly established.

Embedded software in the car is becoming increasingly complex due to the growing number of software-based controller functions and the increasing complexity of the software itself. Model-based development with Simulink combined with TargetLink for automatic code generation helps significantly to improve the quality of the embedded software. The development of large-scale Simulink models in distributed teams is a challenging task, especially when developing safety-critical software that must fulfill requirements stated in the ISO 26262 [1] safety standard. In practice, many questions on how to avoid the pitfalls of distributed model-based development remain open, such as how to define an appropriate model architecture, handle model complexity, and achieve compliance with ISO 26262. The intent of this paper is threefold. Firstly, we summarize those requirements of ISO 26262 that are relevant for developing complex software in a distributed environment.

The essential task of a battery management system (BMS) is to consistently operate the high-voltage battery in an optimum range. Due to the safety-critical nature of its components, prior testing of a BMS is absolutely necessary. Hardware-in-the-loop (HIL) simulation is a cost-effective and efficient tool for this. Testing the BMS on a HIL test bench requires an electronics unit to simulate the cell voltages and a scalable real-time battery model. This paper describes a HIL system that enables comprehensive testing of BMS components. Hardware and software solutions are proposed for the high requirements of these tests. The individual components are combined to make a modular system, and safety-critical aspects are examined. The paper shows that the system as developed fulfills all the requirements derived from the different test scenarios for BMS systems.

Automotive technology is rapidly changing with electrification of vehicles, driver assistance systems, advanced safety systems etc. This advancement in technology is making the task of validation and verification of embedded software complex and challenging. In addition to the component testing, integration testing imposes even tougher requirements for software testing. To meet these challenges dSPACE is continuously evolving the Hardware-In-the-Loop (HIL) technology to provide a systematic way to manage this task. The paper presents developments in the HIL hardware technology with latest quad-core processors, FPGA based I/O technology and communication bus systems such as Flexray. Also presented are developments of the software components such as advanced user interfaces, GPS information integration, real-time testing and simulation models. This paper provides a real-world example of implication of integration testing on HIL environment for Chassis Controls.

Hardware-in-the-loop (HIL) simulation in the development and test process of vehicle dynamics controllers requires a real-time tractor-trailer simulation model. The hitch coupling must be numerically stable to ensure real-time simulation for various driving maneuvers, particularly at the vehicle's handling limits. This paper presents a robust implementation of tractor-trailer coupling. The equation of motion is formed using a novel formulation which is a combination of Jourdain's Principle and the Articulated Body Algorithm. The paper shows that a robust model for a real-time tractor-trailer simulation can be achieved with the proposed method. Moreover, the approach presented is suitable for modular modeling, is successfully implemented and can also be used as a basis for flexible system definition with an adjustable number of trailer axles.

Model-based development and autocoding have become common practice in the automotive industry over the past few years. The industry is using these methods to tackle a situation in which complexity is constantly growing and development times are constantly decreasing, while the safety requirements for the software stay the same or even increase. The debate is no longer whether these methods are useful, but rather on the conditions for achieving optimum results with them. From the experiences made during the last decade this paper shows some of the key factors helping to achieve success when introducing or extending the deployment of automatic code generation in a model-based design process.

Function models have a well-established position in automotive software development. Formal system models, on the other hand, are rare. This article describes the various aspects of function and system models, focusing mainly on AUTOSAR-compatible models. It also depicts the challenges for future overall models that combine the function models and the system model, and the resulting benefits, such as early system verification via PC-based simulations.

Over the last few years the introduction of explicit system and software architecture models (e.g. AUTOSAR models) has led to changes in the automotive development process. The ability to simulate these models on a PC will be decisive for the acceptance of such approaches. This would support the early verification of distributed ECU and software systems and could therefore lead to cost savings. This paper describes an implementation of such an approach which fits into current development processes.

This paper will first introduce and classify the basic principles of architecture-driven software development and will briefly sketch the presumed development process. This background information is then used to explain extensions which enable current behavior modeling and code generation tools to operate as software component generators. The generation of AUTOSAR software components using dSPACE's production code generator TargetLink is described as an example.

The importance of electronics, especially software, has greatly increased over the last few years. Efforts to maintain a high level of software quality have made testing an important part of the development process. With the advent of model-based development, testing methods can be used not only on code level, but also on model level. Next to test execution itself, test development is seen as the most time- and cost-intensive part of the testing process. This paper outlines and classifies current approaches to model-based test development, with the aim of providing guidelines for test developers for choosing the method best suited to the type of system under test and the test objective.