Search Results

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.

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.

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.

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.

This paper discusses the standards that can currently be applied to production code generators and examines five standards in detail: OSEK/VDX, MISRA C, ISO/IEC 15504 (SPiCE), which is compared to ‘CMM for Software’, and IEC 61508. The issues involved in meeting these standards or integrating them in production code generators are discussed. The suitability of automatic production code generation in safety-critical applications is described, taking the TargetLink production code generator from dSPACE as an example.

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.

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.

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.

Hardware-in-the-loop (HIL) testing is an indispensable tool in the software development process for electronic control units (ECUs) and Logical Replaceable Units (LRUs) and is an integral part of the software validation process for many organizations. HIL simulation is regarded as the tried-and-tested method for function, component, integration and network tests for the entire system. Using the Model based design approach has further enabled improved and faster HIL implementations in recent years. This paper describes the changing requirements for HIL simulation, and how they need to be addressed by HIL technology. It also addresses the challenges faced while setting up a successful HIL system: namely the division of tasks, the total cost of ownership, budget constraints and tough competition and the adaptability of a HIL simulator to new demands. These requirements are discussed using a dSPACE HIL system architecture that was designed from the ground-up to address these needs.

The number of electrical and electronic components in modern vehicles is constantly growing. Increasingly, functionalities are being distributed across several electronic control units (ECUs). While suppliers themselves are responsible for ensuring that individual ECUs function properly, only the OEM can test distributed functions. Moreover, with the volume of testing steadily growing, automated sequences are absolutely essential. To test electronic networks in the vehicle, Ford Europe is using platform-based hardware-in-the-loop simulation with integrated failure insertion. The company is setting up a uniform, project-independent procedure, from standardized test definition to automated test sequences on a virtual vehicle, right through to structured evaluation.

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.

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.

This paper describes a new production code generator that meets both the requirements of code developers for efficient and reliable production code, as well as the desire of system engineers to establish a control design process based on simulation models that double as executable specifications for the ECU software. The production code generator supports automatic scaling, generates optimized fixed-point C code for microcontrollers like the Motorola 683xx, Siemens C16x, and Hitachi SH-2, and produces ASAP2 [1] calibration information. Benchmark results show that the autogenerated code can match or even exceed the efficiency of typical handwritten production code. Code quality is assured by design and by systematic, automatic, and extremely comprehensive test procedures.

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.

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.

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.