Search Results

Interior permanent magnet machines are being widely used in hybrid vehicles owing to their compact size and high power density. Vehicle level application requires the motor to operate at high speed beyond the base speed of the motor. This is accomplished through flux weakening control. Nonfunctioning of inverter switches and/or gate driver circuit during flux weakening could give rise to a potential fault scenario called Un-Controlled Generation (UCG). This paper gives a detailed background of UCG and its impact on the high voltage and propulsion systems. In further sections the details related to modelling and analysis of UCG will be discussed. Finally, the paper will conclude with simulation results and comparison of the results with motor dynamometer test data.

Future automobiles are required to support an increasing number of complex, distributed functions such as active safety and X-by-wire. Because of safety concerns and the need to deliver correct designs in a short time, system properties should be verified in advance on function models, by simulation or model checking. To ensure that the properties still hold for the final deployed system, the implementation of the models into tasks and communication messages should preserve properties of the model, or in general, its semantics. FlexRay offers the possibility of deterministic communication and can be used to define distributed implementations that are provably equivalent to synchronous reactive models like those created from Simulink. However, the low level communication layers and the FlexRay schedule must be carefully designed to ensure the preservation of communication flows and functional outputs.

Current development processes for automotive Electronic Control System (ECS) architectures have certain limitations in evaluating and comparing different architecture design alternatives. The limitations entail the lack of systematic and quantitative exploration and evaluation approaches that enable objective comparison of architectures in the early phases of the design cycle. In addition, architecture design is a multi-stage process, and entails several stakeholders who typically use their own metrics to evaluate different architecture design alternatives. Hence, there is no comprehensive view of which metrics should be used, and how they should be defined. Finally, there are often conflicting forces pulling the architecture design toward short-term objectives such as immediate cost savings versus more flexible, scalable or reliable solutions. In this paper, we propose the usage of a set of metrics for comparing ECS architecture alternatives.

To cope with the increasing number of advanced features (e.g., smart-phone integration and side-blind zone alert.) being deployed in vehicles, automotive manufacturers are designing flexible hardware architectures which can accommodate increasing feature content with as fewer as possible hardware changes so as to keep future costs down. In this paper, we propose a formal and quantitative definition of flexibility, a related methodology and a tool flow aimed at maximizing the flexibility of an automotive hardware architecture with respect to the features that are of greater importance to the designer. We define flexibility as the ability of an architecture to accommodate future changes in features with no changes in hardware (no addition/replacement of processors, buses, or memories). We utilize an optimization framework based on mixed integer linear programming (MILP) which computes the flexibility of the architecture while guaranteeing performance and safety requirements.

The automotive system domain are in increasing motivation with benefits by using the x-by-wire technologies, which employ new electronic devices to provide for automobile system more facilities during processes at development, production, usability and maintenance. Considering at automobile user domain point of view, the next generation of automobiles can give users more comfort, safety and flexibility. However, for the safety critical applications at automobiles have as requirements the use of distributed embedded systems and fault tolerance methodologies where in communication infrastructure need to offer fault-tolerance communication services. Several researches regards fault tolerance communication systems for automotive domain are now in progress and a strong convergence in use of the Flexray technology is noted for the automotive community. The Flexray is one of the communication systems that had been proposed and available at AUTOSAR standard.

An outer loop guidance architecture was designed to control autonomous aerial refueling mission from the trail aircraft side. The design utilized bank, yaw rate, velocity and climb rate commands implemented using a previously developed adaptive trajectory concept. The concept was based on position error feedback that was used to control trail aircraft overshoot and tracking about the lead aircraft refueling point. To demonstrate this application, an open loop linear trail aircraft model at a given flight condition was selected. Inner loop control laws were designed using Linear Quadratic Regulator feedback controller and Balanced Deviation theory. The outer loop guidance architecture was then added to implement the application. The performance of the system was then evaluated for a selected position error, and disturbance.

Reductions of hardware costs as well as implementations of new innovative functions are the main drivers of today's automotive electronics. Indeed more and more resources are spent on adapting existing solutions to different environments. At the same time, due to the increasing number of networked components, a level of complexity has been reached which is difficult to handle using traditional development processes. The automotive industry addresses this problem through a paradigm shift from a hardware-, component-driven to a requirement- and function-driven development process, and a stringent standardization of infrastructure elements. One central standardization initiative is the AUTomotive Open System ARchitecture (AUTOSAR). AUTOSAR was founded in 2003 by major OEMs and Tier1 suppliers and now includes a large number of automotive, electronics, semiconductor, hard- and software companies.

The AUTomotive Open System ARchitecture (AUTOSAR) Development Partnership has published early 2008 the specifications Release 3.0 [1], with a prime focus on the overall architecture, basic software, run time environment, communication stacks and methodology. Heavy developments have taken place in the OEM and supplier community to deliver AUTOSAR loaded cars on the streets starting 2008 [2]. The 2008 achievements have been: Improving the specifications in order to secure the exploitation for body, chassis and powertrain applications Adding major features: safety related functionalities, OBD II and Telematics application interfaces.