Search Results

In the automotive industry, the piezo-based in-cylinder pressure sensor is getting commercialized and used in production vehicles. For example, the pressure sensor offers the opportunity to design algorithms for estimation of engine emissions, such as soot and NO , during a combustion cycle. In this paper a zero-dimensional NO model for a diesel engine is implemented that will be used in real time. The model is based on the thermal NO formation and the Zeldovich mechanism using two non-geometrical zones: burned and unburned zone. The influence of EGR on combustion temperature was modeled using a well-known thermodynamic identity where specific heat at constant pressure is included. Specific heat will vary with temperature and the gas composition. The model was implemented in LabVIEW using tools specific for an FPGA (Field-Programmable Gate Array).

Due to the continuously increasing number of electronic control units (ECUs) in modern cars, and their growing complexity, automated tests not only of single ECUs but also of interconnected ECUs have become an important step in the development of automotive electronics. These tasks require new test systems. This paper describes the problems engineers face when developing and testing today's car electronics, as well as a high-end hardware-in-the-loop (HIL) tool set (hardware, software, models) applied to the testing of four networked ECUs for engine management, vehicle dynamics control, automatic transmission, and an active suspension system. The tool set comprises general features needed for HIL tests, like automated code generation for real-time models using MATLAB/Simulink and a comprehensive set of dedicated hardware (processor and I/O hardware).

Biofuel can enable a sustainable transport solution and lower greenhouse gas emissions compared to standard fuels. This study focuses on biodiesel, implemented in the easiest way as drop in fuel. When mixing biodiesel into diesel one can run into problems with solubility causing contaminants precipitating out as insolubilities. These insolubilities, also called soft particles, can cause problems such as internal injector deposits and nozzle fouling. One way to overcome the problem of soft particles is by filtration. It is thus of great interest to be able to quantify fuel filters’ ability to intercept soft particles. The aim of this study is to test different fuel filters for heavy-duty engines and their ability to filter out synthetic soft particles. A custom-built fuel filter rig is presented, together with some of its general design requirements. For evaluation of the efficiency of the filters, fuel samples were taken before and after the filters.

Model-based software development is increasingly being used to develop software for electronic control units (ECUs). When developing safety-related software, compared to non-safety-related software development, additional requirements specified by relevant safety-standards have to be met. Meeting these requirements should also be considered to be best practices for non-safety-related software. This paper introduces a model-based reference workflow for the development of safety-related software conforming to relevant safety-standards such as IEC 61508 and ISO 26262. The reference workflow discusses requirements traceability aspects, software architecture considerations that help to support modular development and ease the verification of model parts and the code generated from those model parts, and the selection and enforcement of modeling and coding guidelines.

Automotive manufacturers and suppliers of electronic control units (ECUs) will be challenged more and more in the future to reduce costs and the time needed for ECU development. At the same time, increasing requirements concerning exhaust gas emissions, drivability, onboard diagnostics and fuel consumption have led to the growing complexity of modern engines and the associated management systems. As a result, the number and complexity of control parameters and look-up tables in the ECU software is increasing dramatically. Thus, in powertrain applications especially, calibration development has become a time-consuming and cost-intensive stage in the overall ECU development process. This paper describes the current situation in calibration development and shows how the new dSPACE Calibration System will face this situation. It provides an overview of the main benefits of the tool, which has been designed in close cooperation with calibration engineers.

Due to the rapidly increasing number of electronic control units (ECUs) in modern vehicles, software and ECU testing plays a major role within the development of automotive electronics. To ensure effective as well as efficient testing within the whole development process, a seamless transition in terms of the reusability of tests and test data as well as powerful and efficient means for developing and describing tests are required. This paper therefore presents a new integration approach for modern test development and test management. Besides a very easy-to-use way of describing tests graphically, the main focus of the new approach is on the management of a large number of tests, test data, and test results, allowing close integration into the automotive development processes.

The emission control in heavy-duty vehicles today is based on predefined injection strategies and after-treatment systems such as SCR (selective catalytic reduction) and DPF (diesel particulate filter). State-of-the-art engine control is presently based on cycle-to-cycle resolution. The introduction of the crank angle resolved pressure measurement, from a piezo-based pressure sensor, enables the possibility to control the fuel injection based on combustion feedback while the combustion is occurring. In this paper a study is presented on the possibility to control NOx (nitrogen oxides) formation with a crank angle resolved NOx estimator as feedback. The estimator and the injection control are implemented on an FPGA (Field-Programmable Gate Array) to manage the inherent time constraints. The FPGA is integrated with the rest of the engine control system for injection control and measurement.

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.

The technological development in the field of automotive electronics is proceeding at almost break-neck speed. The functions being developed and integrated into cars are growing in complexity and volume. With the increasing number and variety of sensors and actuators, electronics have to handle a greater amount of data, and the acquisition and generation of I/O signals is also growing in complexity, for example, in engine management applications. Moreover, intelligent and complex algorithms need to be processed in a minimum of time. This all intensifies the need for Rapid Control Prototyping (RCP), a proven method of decisively speeding up the model-based software development process of automotive electronic control units (ECUs) [1],[2]. All these demanding tasks, including connecting sensors and actuators to the RCP system, need to be performed within a standard prototyping environment.

Hardware-in-the-loop (HIL) testing is used by commercial vehicle original equipment manufacturers (OEMs) in several fields of electronics development. HIL tests are a part of the standard development process for engine and machine control systems. For electronic control units (ECUs), not only the HIL test of the hardware but also the controller software validation is very important. For hardware diagnostics validation, a dynamic simulation of the real system could be omitted and an open-loop test of the controller is sufficient in most cases. For most controller software validation including OBD (on-board diagnosis) tests, detailed but real-time capable models have to be used. This article describes the needs and challenges of models in hardware-in-the-loop (HIL) based testing, taking into account the wide range of commercial and off-highway vehicles.

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.

Power dense internal combustion engines (ICEs) are interesting candidates for onboard charging devices in different electric powertrain applications where the weight, volume and price of the energy storage components are critical. Single-cylinder naturally aspirated two-stroke spark-ignited (SI) engines are very small and power dense compared to four-stroke SI engines and the installation volume from a single cylinder two-stroke engine can become very interesting in some concepts. During charged conditions, four-stroke engines become more powerful than naturally aspirated two-stroke engines. The performance level of a two-stroke SI engines with a charging system is less well understood since only a limited number of articles have so far been published. However, if charging can be successfully applied to a two-stroke engine, it can become very power dense.

Model-based software development and automatic code generation have become increasingly established in recent years. The automotive industry has widely adopted and successfully deployed these methods in many different series production programs worldwide. This brought various benefits, such as a reduction in development times, improved quality due to more precise specifications, and early verification and validation by means of simulation. At the same time, more and more safety-related and safety-critical systems have been - and will be -introduced into modern vehicles. Common examples are active front steering, adaptive cruise-control, and integrated chassis control. This leads to the question, if and how model-based design and automatic production code generation can be applied to the development of safety-critical systems.

Today, hardware-in-the-loop (HIL) simulation is common practice as a testing methodology for electronic control units (ECUs). An essential criterion for the efficiency of an HIL system is the availability of powerful test automation having access to all of its hardware and software components (including I/O channels, failure insertion units, bus communication controllers and diagnostic interfaces). The growing complexity of vehicle embedded systems, which are interconnected by bus systems (like CAN, LIN or FlexRay), result in hundreds or even thousands of tests that have to be done to ensure the correct system functionality. This is best achieved by automated testing. Automated testing usually is performed by executing tests on a standard PC, which is interconnected to the HIL system. However, higher demands regarding timing precision are hard to accomplish. As an example, ECU interaction has to be captured and responded to in the range of milliseconds.

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 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.

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.

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.

In-cylinder flow measurements, conventional swirl measurements and CFD-simulations have been performed and then compared. The engine studied is a single cylinder version of a Scania D12 that represents a modern heavy-duty truck size engine. Bowditch type optical access and flat piston is used. The cylinder head was also measured in a steady-flow impulse torque swirl meter. From the two-dimensional flow-field, which was measured in the interval from -200° ATDC to 65° ATDC at two different positions from the cylinder head, calculations of the vorticity, turbulence and swirl were made. A maximum in swirl occurs at about 50° before TDC while the maximum vorticity and turbulence occurs somewhat later during the compression stroke. The swirl centre is also seen moving around and it does not coincide with the geometrical centre of the cylinder. The simulated flow-field shows similar behaviour as that seen in the measurements.

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.