Search Results

The paper describes the development of a vehicle stability indicator based on the correlation between various current vehicle chassis sensors such as hand wheel angle, yaw rate and lateral acceleration. In general, there is a correlation between various pairs of sensor signals when the vehicle operation is linear and stable and a lack of correlation when the vehicle is becoming unstable or operating in a nonlinear region. The paper outlines one potential embodiment of the technology that makes use of the Mahalanobis distance metric to assess the degree of correlation among the sensor signals. With this approach a single scalar metric provides an accurate indication of vehicle stability.

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.

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.

As automotive electronic control systems continue to increase in usage and complexity, the challenges for developing automotive diagnostics also increase. Reduced development cycle times, the increased significance of diagnostics for safety critical systems, and the integration of vehicle systems across multiple control systems all add to the tasks of developing diagnostics for the automobiles of today and tomorrow. Addressing automotive diagnostics now requires the Tier 1 supplier to utilize a formal diagnostic development methodology. There are also opportunities for Tier 1 suppliers to add value by developing vehicle-level supervisory diagnostic strategies, in addition to subsystem and system-level diagnostic strategies. There is also a prospect to provide strategies and tools to enhance service at the vehicle level. This paper proposes an approach for Tier 1 suppliers to address diagnostic and service issues at the component, system, and vehicle level.

The paper describes a new strategy for real-time sensor diagnostics that is based on the statistical correlation of various sensor signal pairs. During normal fault-free operation there is a certain correlation between the sensor signals which is lost in the event of a fault. The proposed algorithm quantifies the correlation between sensor signal pairs using real-time scalar metrics based on the Mahalanobis-distance concept. During normal operation all metrics follow a similar pattern, however in the event of a fault; metrics involving the faulty sensor would increase in proportion to the magnitude of the fault. Thus, by monitoring this pattern and using a suitable fault-signature table it is possible to isolate the faulty sensor in real-time. Preliminary simulation results suggest that the strategy can mitigate the false-alarms experienced by most model-based diagnostic algorithms due to an intrinsic ability to distinguish nonlinear vehicle behavior from actual sensor faults.

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.