Search Results

Today's automotive software integration is a static process. Hardware and software form a fixed package and thus hinder the integration of new electric and electronic features once the specification has been completed. Usually software components assigned to an ECU cannot be easily transferred to other devices after they have been deployed. The main reasons are high system configuration and integration complexity, although shifting functions from one to another ECU is a feature which is generally supported by AUTOSAR. The concept of a Virtual Functional Bus allows a strict separation between applications and infrastructure and avoids source code modifications. But still further tooling is needed to reconfigure the AUTOSAR Basic Software (BSW). Other challenges for AUTOSAR are mixed integrity, versioning and multi-core support. The upcoming BMW E/E-domain oriented architecture will require all these features to be scalable across all vehicle model ranges.

Technological advancement in the automotive industry necessities a closer focus on the functional safety for higher automated driving levels. The automotive industry is transforming from conventional driving technology, where the driver or the human is a part of the control loop, to fully autonomous development and self-driving mode. The Society of Automotive Engineers (SAE) defines the level 4 of autonomy: “Automated driving feature will not require the driver to take over driving control.” Thus, more and more safety related electronic control units (ECUs) are deployed in the control module to support the vehicle. As a result, more complexity of system architecture, software, and hardware are interacting and interfacing in the control system, which increases the risk of both systematic and random hardware failures.

a practice-oriented approach for an accelerated product development and product design process for mechatronic systems is presented. The handling of complex and versatile product data to perform this process is shown in the area of electrical drives and actuators in cars. It is discussed, how the coordination of all the necessary disciplines as development, design, testing field, specification and release management should be software supported and PDM integrated. The advantages and benefits of the presented methods are shown on particular examples. The necessary software modules are introduced, showing that the realized solution gives both opportunities - the integration into a PDM backbone and at the same time an independent communication within department and/or company. The practical way, to realize the expert-specific needs of the development department, which is not possible with a general PDM system is pointed out.

This paper presents new comfort and convenience features in the luxury segment and focuses especially on Comfort Access and iDrive. The Comfort Access System offers the customer the possibility of unlocking the vehicle without active use of a key, of starting the engine and at the end of the journey of locking the car again. The aim of the iDrive concept was to enable intuitive operation of the various functions with simultaneously improved ergonomics. Both, a monitor and a controller with its variable haptic are the concept’s innovation. In addition, this paper also discusses future ECU (Electronic Control Unit) networks for body electronics. The focus is on package-driven ECU network architecture, having many functions developed by different suppliers on a single ECU.

Current implementations of vision-based Advanced Driver Assistance Systems (ADAS) are largely dependent on real-time vehicle camera data along with other sensory data available on-board such as radar, ultrasonic, and GPS data. This data, when accurately reported and processed, helps the vehicle avoid collisions using established ADAS applications such as Forward Collision Avoidance (FCA), Autonomous Cruise Control (ACC), Pedestrian Detection, etc. Vehicle to Vehicle (V2V) and Vehicle to Infrastructure (V2I) over Dedicated Short Range Communication (DSRC) provides basic sensory data from other vehicles or roadside infrastructure including position information of surrounding traffic. Exchanging rich data such as vision data between multiple vehicles, and between vehicles and infrastructure provides a unique opportunity to advance driver assistance applications and Intelligent Transportation Systems (ITS).

Robert Bosch GmBH proposed in 2012 a new version of communication protocol named as Controller area network with Flexible Data-Rate (CANFD), that supports data frames up to 64 bytes compared to 8 bytes of CAN. With limited data frame size of CAN message, and it is impossible to be encrypted and secured. With this new feature of CAN FD, we propose a hardware design - CAN crypto FPGA chip to secure data transmitted through CAN FD bus by using AES-128 and SHA-1 algorithms with a symmetric key. AES-128 algorithm will provide confidentiality of CAN message and SHA-1 algorithm with a symmetric key (HMAC) will provide integrity and authentication of CAN message. The design has been modeled and verified by using Verilog HDL – a hardware description language, and implemented successfully into Xilinx FPGA chip by using simulation tool ISE (Xilinx).

Handling characteristics, ride comfort and active safety are customer relevant attributes of modern premium vehicles. Electronic control units offer new possibilities to optimize vehicle performance with respect to these goals. The integration of multiple control systems, each with its own focus, leads to a high complexity. BMW and ITK Engineering have created a tool to tackle this challenge. A simulation environment to cover all development stages has been developed. Various levels of complexity are addressed by a scalable simulation model and functionality, which grows step-by-step with increasing requirements. The simulation environment ensures the coherence of the vehicle data and simulation method for development of the electronic systems. The article describes both the process of the electronic control unit (ECU) development and positive impact of an integrated tool on the entire vehicle development process.

The individual development process for distributed, communicating electronic control units hinders the integration of Automotive systems and increases the overall costs. In order to facilitate such applications, services and protocols for Communication, Network Management, and Operating System must be standardized. The aim of the OSEK project is to work out a respective specification proposal in cooperation with several car manufacturers and suppliers. This will permit a cost-effective system integration and support the portation of system functions between different electronic control units.

The Formula SAE® rules require the use of a 20mm intake restrictor. The presence of the restrictor necessitates the design or retuning of fuel and spark strategies that, in turn require the use of a programmable engine control unit (ECU). This paper describes a process used to establish the fuel and spark strategies for a standard production motorcycle engine operating with a restricted air intake. Honda 600cc engines were controlled by three different ECUs: a Haltech, DTA and an “in-house” ECU. Simple calculations of injection duration are suggested to provide a baseline fuel map from which the engine could be started, and then fuel maps are tuned by experiment. Similar baseline numbers for ignition timing are given.

Motivated by experiences in the Formula SAE® competition, an engine control unit (ECU) was designed, developed and tested at Oakland University. A systems approach was taken in which the designs of the electronic architecture and software were driven by the mechanical requirements and operational needs of the engine, and by the need for dynamometer testing and tuning functions. An ECU, powered by a 68HC12 microcontroller was developed, including a four-layer circuit board designed for EMC. A GUI was written with Visual C++® for communication with a personal computer (PC). The ECU was systematically tested with an engine simulator, a 2L Ford engine and a 600cc Honda engine, and finally in Oakland's 2004 FSAE vehicle.

Increasing demand for dynamically controlled safety features, passenger comfort, and operational convenience in upper class automobiles requires an intensive use of electronic control units including software portions. Modeling, simulation, rapid prototyping, and verification of the software need new technologies to guarantee passenger security and to accelerate the time-to-market of new products. This paper presents the state-of-the-art of the design methods for the development of electronic control unit software at BMW. These design methods cover both discrete and continuous system parts, smoothly integrating the respective methods not merely on the code level, but on the documentation, simulation, and design level. In addition, we demonstrate two modeling and prototyping tools for discrete and continuous systems, namely Statemate and MatrixX, and discuss their advantages and drawbacks with respect to necessary prototyping demands.

This paper proposes a new nonlinear model predictive control (NMPC) for autonomous vehicle path tracking problem. The vehicle is equipped with active rear steering, allowing independent control of front and rear steering. Traditional NMPC, which runs at fixed sampling rate, has been shown to provide satisfactory control performance in this problem. However, the high throughput of NMPC limits its implementation in production vehicle. To address this issue, we propose a novel event-triggered NMPC formulation, where the NMPC is triggered to run only when the actual states deviate from prediction beyond certain threshold. In other words, the event-triggered NMPC will formulate and solve a constrained optimal control problem only if it is enabled by a trigger event. When NMPC is not triggered, the optimal control sequence computed from last NMPC instance is shifted to determine the control action.

This paper presents the challenges in automotive electronics. Considering the deficiencies of the current ECU (electronic control unit) design process, a new design process is outlined. This design process mainly focuses on the independence of the ECU hardware architecture development and the software function development.

Casting is the ability to let users transfer their favorite videos, music, movies, etc. from their phone to a chosen display. This functionality has become very popular these days, and to the user, it is as simple as clicking a button. This “simple” task is a complex system that requires various independent sources to communicate efficiently and effectively to produce a robust and reliable output. The sending and receiving devices are required to be on the same network - which involves reliable and secure connection. This allows the sending of the URL of the chosen feature to the server provider, which will then connect to the receiver embedded electronics where the authentication process that protects Digital Rights Management (DRM) is established. In the era of developing autonomous and luxury vehicles, this technology has the potential to add a new dimension of in-vehicle entertainment that could come very close to the home experience.

The permanently increasing number of convenience and safety functions leads to higher complexity of in-car electronics and the rapidly growing amount of sensors, actuators and electronic control units places higher demands on high- speed data communication protocols. Safety-critical systems need deterministic protocols with fault-tolerant behavior. The need for on-board diagnosis calls for flexible use of bandwidth and an ever-increasing number of functions necessitates a flexible means of extending the system. None of the communication solutions available on the market until now (like CAN or TTP) have been able to fulfill all these demands. To solve these problems, BMW together with several semiconductor companies has developed a new protocol for safety-critical applications in automotive vehicles.