Search Results

During the production controller and software development process, one critical step is the controller and software verification. There are various ways to perform this verification. One of the commonly used methods is to utilize an HIL (hardware-in-the-loop) test bench to emulate powertrain hardware for development and validation of powertrain controllers and software. A key piece of an HIL bench is the plant dynamics model used to emulate the external environment of a modern controller, such as engine (ECM), transmission (TCM) or powertrain controller (PCM), so that the algorithms and their software implementation can be exercised to confirm the desired results. This paper presents a 6-speed automatic transmission plant dynamics model development for hardware-in-the-loop (HIL) test bench for the validation of production transmission controls software. The modeling method, model validation, and application in an HIL test environment are described in details.

Production software validation is critical during software development, allowing potential quality issues that could occur in the field to be minimized. By developing automated and repeatable software test methods, test cases can be created to validate targeted areas of the control software for confirmation of the expected results from software release to release. This is especially important when algorithm/software development timing is aggressive and the management of development activities in a global work environment requires high quality, and timely test results. This paper presents a hardware-in-the-loop (HIL) test bench for the validation of production transmission controls software. The powertrain model used within the HIL consists of an engine model and a detailed automatic transmission dynamics model. The model runs in an OPAL-RT TestDrive based HIL system.

The need for improved emissions control in lean exhaust to meet tightening, world-wide NOx emissions standards has led to the development of selective catalytic reduction of NOx with ammonia as a major technology for emissions control. Current systems are being designed to use a solution of urea (32.5 wt %) dissolved in water or Diesel Exhaust Fluid (DEF) as the ammonia source. While DEF or AdBlue® is widely used as a source of ammonia, it has a number of issues at low temperatures, including freezing below −12 °C, solid deposit formation in the exhaust, and difficulties in dosing at exhaust temperatures below 200 °C. Additionally creating a uniform ammonia concentration can be problematic, complicating exhaust packaging and usually requiring a discrete mixer.

In this paper, we review existing software safety standards, guidelines, and other software safety documents. Common software safety elements from these documents are identified. We then describe an adaptable software safety process for automotive safety-critical systems based on these common elements. The process specifies high-level requirements and recommended methods for satisfying the requirements. In addition, we describe how the proposed process may be integrated into a proposed system safety process, and how it may be integrated with an existing software development process.

Robust Engineering techniques developed by Taguchi have traditionally applied to the optimization of engineering designs. Robust Engineering methods also may be applied to software testing of ECU algorithms. The net result is an approach capable of improving the software algorithm in one of two ways. First the approach can identify the range of areas which prove problematic to the software such that a robust solution may be developed. Conversely, the approach can be used as a general strategy to verify that the software is robust over the range of inputs tested. The robust engineering methods applied to software testing utilize orthogonal array experiments to test software over a range of inputs. The actual software trials are best performed in the simulation environment and also via automated test hardware in the loop configurations in realtime. This paper outlines a process for applying Robust Engineering methods to software testing.

Embedded controllers and digital signal processors are increasingly being used in automotive safety critical control systems. Controller integrity is a significant concern in these systems. Over the past decade, several techniques have been published about controller safety and integrity verification. These techniques include: single processor with watchdog, dual processors, dual core processor, and asymmetric processor (intelligent watchdog). Each of these techniques have benefits, however, many new non-distributed safety-critical systems are applying the asymmetric processor technique to help verify controller integrity. This paper discusses an overview of five controller integrity techniques, and then provides a detailed discussion of an asymmetric processor approach. This paper presents two different options within the asymmetric processor approach.

This paper will address the electronic development in the wireless industry and compare it to the electronic development in the automotive industry. The wireless industry is characterized by rapid, dramatic high tech changes with a less than two-year cycle time and an equivalent life cycle. The automotive electronics industry is working toward reducing the typical 2 to 3 year development cycle down 1 to 2 years but with a life cycle of 10 years or more. In addition to realizing the electronic development benefits seen in the wireless industry, the automotive industry places significantly more emphasis on the quality and reliability aspects of their designs as many of them are targeted toward, or interface with, safety critical applications. One of the lessons learned from the wireless industry is the development process; where the hardware selection process can be accomplished in a virtual environment in conjunction with concurrent software development.

This paper describes a new tool to capture cylinder pressure information, calculate combustion parameters, and implement control algorithms. There are numerous instrumentation and prototyping systems which can provide some or all of this capability. The Cylinder Pressure Development Controller (CPDC) is unique in that it uses advanced high volume automotive grade circuitry, packaging, and software methodologies. This approach provides insight regarding the implementation of cylinder pressure based controls in a production engine management system. A high performance data acquisition system is described along with a data reduction technique to minimize data processing requirements. The CPDC software architecture is discussed along with model-based algorithm development and autocoding. Finally, CPDC calculated combustion parameters are compared with those from a well established combustion analysis system and thermodynamic simulations.

With the requirements for reducing the emissions and improving the fuel economy, the automotive companies are developing hybrid, 42 V and fuel cell vehicles. Power electronics is an enabling technology for the development of environmental friendly vehicles, and to implement the various vehicle electrical architectures to obtain the best performance. In this paper, the requirements of the power semiconductor devices and the criteria for selecting the power devices for various types of low emission vehicles are presented. A comparative study of the most commonly used power devices is presented. A brief review of the future power devices that would enhance the performance of the automotive power conversion systems is also presented.

Advances in wireless communications, model-based diagnostics, human-machine interfaces, electronics and embedded system technologies have created the foundation for a dramatic shift in the way the vehicles are diagnosed and maintained. These advances will enable vehicle diagnosis and maintenance to be performed remotely while the vehicle is being driven. There also has been recent strong consumer interest in Remote Diagnosis and Maintenance (RD&M). As a consequence, RD&M is drawing increased attention in the automotive industry. This paper provides the current status of vehicle remote diagnosis and maintenance, analyses the potential features of RD&M and their significance, and discusses how next generation automotive products could benefit from research and development in this area.

A requirement of many modern safety-critical automotive applications is to provide failsafe operation. Several analysis methods are available to help confirm that automotive safety-critical systems are designed properly and operate as intended to prevent potential hazards from occurring in the event of system failures. One element of safety-critical system design is to help verify that the software and microcontroller are operating correctly. The task of incorporating failsafe capability within an embedded microcontroller design may be achieved via hardware or software techniques. This paper surveys software failsafe techniques that are available for application within a microcontroller design suitable for use with safety-critical automotive systems. Safety analysis techniques are discussed in terms of how to identify adequate failsafe coverage.

With the inception of model-based design and automatic code generation, many organizations are developing controls and diagnostics algorithms in model-based development tools to meet customer and regulatory requirements. Advances in model-based design have made it easier to generate C code from models and help software engineers streamline their workflow. Typically, after the software has been developed, the models are handed over to a calibration team responsible for calibrating the features to meet specified customer and regulatory requirements. However, once the models are handed over to the calibration team, the calibration engineers are unaware of how to calibrate the features because documentation is not available. Typically, model documentation trails behind the software process because it is created manually, most of this time is spent on formatting. As a result, lack of model documentation or up-to date documentation causes a lot of pain for OEM’s and Tier 1 suppliers.