Search Results

Historically, whenever the automotive solutions’ state of art reaches a saturation level, the integration of new verticals of technology has always raised new opportunities to innovate, enhance and optimize automotive solutions. The predictive powertrain solutions using connectivity elements (e.g., navigation unit, e-Horizon or cloud-based services) are one of such areas of huge interest in automotive industry. The prior knowledge of trip destination and its route characteristics has potential to make prediction of powertrain modes or events in certain order and therefore it can add value in various application areas such as optimized energy management, lower fuel consumption, superior safety and comfort, etc.

Nowadays automobiles are getting smart and there is a growing need for the physical behavior to become part of its software. This behavior can be described in a compact form by differential equations obtained from modeling and simulation tools. In the offline simulation domain the Functional Mockup Interface (FMI) [3], a popular standard today supported by many tools, allows to integrate a model with solver (Co-Simulation FMU) into another simulation environment. These models cannot be directly integrated into embedded automotive software due to special restrictions with respect to hard real-time constraints and MISRA compliance. Another architectural restriction is organizing software components according to the AUTOSAR standard which is typically not supported by the physical modeling tools. On the other hand AUTOSAR generating tools do not have the required advanced symbolic and numerical features to process differential equations.

The introduction of new emission legislation and the demand of increased power for small two-wheelers lead to an increase of technical requirements. Especially for single cylinder engines with high compression ratio the transient behavior close to idling is challenging. The demand for two-wheeler specific responsiveness of the vehicle requires low overall rotational inertia as well as small intake manifold volumes. The combination with high compression ratio can lead to a stalling of the engine if the throttle opens and closes very quickly in idle operation. The fast opening and closing of the throttle is called a throttle blip. Fast, in this context, means that the blipping event can occur in one to two working cycles. Previous work was focused on the development of a procedure to apply reproducible blipping events to a vehicle in order to derive a deeper physical understanding of the stalling events.

The increasing complexity of automotive functions which are necessary for improved driving assistance systems and automated driving require a change of common vehicle architectures. This includes new concepts for E/E architectures such as a domain-oriented vehicle network based on powerful Domain Control Units (DCUs). These highly integrated controllers consolidate several applications on different safety levels on the same ECU. Hence, the functions depend on a strictly separated and isolated implementation to guarantee a correct behavior. This requires middleware layers which guarantee task isolation and Quality of Service (QoS) communication have to provide several new features, depending on the domain the corresponding control unit is used for. In a first step we identify requirements for a middleware in automotive DCUs. Our goal is to reuse legacy AUTOSAR based code in a multicore domain controller.

The Side View Assist is the World’s first rider assistance system for two-wheelers. This is a Blind Spot Warning system, which uses four ultrasonic sensors to monitor the surrounding of the rider. Whenever there is a vehicle (i.e. a car, truck, or another motorbike) in the rider’s blind spot, the technology warns the rider with an optical signal close to the mirror. This will allow the rider to avoid a collision when changing lanes. In the current vehicle application, Side View Assist is active at speeds ranging from 25 to 80 kilometers per hour and supports riders whenever the difference in relative speed to other road users is small. The system helps to improve safety especially in cities, where heavy traffic makes it necessary to change lanes more often. Originally such systems have been developed for cars and different system solutions for cars have been in serial production for several years. The challenge was to adapt these systems so they would work for two-wheelers as well.

In the low-cost segment for 2-Wheelers legislative, economic and ecologic considerations necessitate a reduction of the emissions and further improvement in fuel consumption. To reach these targets, the commonly used carburetors are being replaced by engine management systems (EMS). One option to provide these systems for acceptable and attractive system costs is to save a sensor device and to substitute its measure by an estimation value. In many motorcycles the rotor of the vehicle's alternator is rigidly attached to the crankshaft. Therefore, the voltage and current signals of the alternator contain information about the engine's speed, which can be retrieved by evaluating these electric signals. After further processing of this information inside the electronic control unit (ECU), the absolute crankshaft position can be obtained. A high-resolution speed signal without mechanical distortions like tooth errors is gained, whose signal quality equals the one of a common speed sensor.

Automotive vehicles today consist of very complex network of electronic control units (ECU) connected with each other using different network implementations such as Controller Area Network (CAN), FlexRay, etc. There are several ECUs inside a vehicle targeting specific applications such as engine, transmission, body, steering, brakes, infotainment/navigation, etc. comprising on an average more than 50 ECUs executing more than 50 million lines of software code. It is expected to increase exponentially in the next few years. Such complex electric/electronic (E/E) architecture and software calls for a comprehensive, flexible and systematic development and validation environment especially for a system level or vehicle level development. To achieve this goal, we have built a virtual multi-ECU high fidelity cyber-physical multi-rate cosimulation that closely resembles a realistic hardware based automotive embedded system.

With the increasing complexity of electronic vehicle systems, one particular “gap” between function development and ECU integration becomes more and more apparent, and critical; albeit not new. The core of the problem is: as more functions are integrated and share the same E/E resources, they increasingly mutually influence and disturb each other in terms of memory, peripherals, and also timing and performance. This has two consequences: The amount of timing-related errors increases (because of the disturbance) and it becomes more difficult to find root causes of timing errors (because of the mutual influences). This calls for more systematic methods to deal with timing requirements in general and their transformation from function timing requirements to software architecture timing requirements in particular.

Current exhaust gas emission regulations can only be well adhered to through optimal interplay of combustion engine and exhaust gas after-treatment systems. Combining a modern diesel engine with several exhaust gas after-treatment components (DPF, catalytic converters) leads to extremely complex drive systems, with very complex and technically demanding control systems. Current engine ECUs (Electronic Control Unit) have hundreds of functions with thousands of parameters that can be adapted to keep the exhaust gas emissions within the given limits. Each of these functions has to be calibrated and tested in accordance with the rest of the ECU software. To date this task has been performed mostly on engine test benches or in Hardware-in-the-Loop (HiL) setups. In this paper, a Software-in-the-Loop (SiL) approach, consisting of an engine model and an exhaust gas treatment (EGT) model, coupled with software from a real diesel engine ECU, will be described in detail.

More electronic vehicle functions lead to an exponentially growing degree of software integration in automotive ECUs. We are seeing an increasing number of ECUs with mixed criticality software. ISO26262 describes different safety requirements, including freedom from interference and absence from error propagation for the software. These requirements mandate particular attention for mixed-criticality ECUs. In this paper we investigate the ability to guarantee that these safety requirements will be fulfilled by using established (deadline monitoring) and new error detection mechanisms (execution time monitoring). We also show how these methods can be used to build up safe and efficient schedules for today's and future automotive embedded real time systems with mixed criticality software.

Today, knock control is part of standard automotive engine management systems. The structure-borne noise of the knock sensor signal is evaluated in the electronic control unit (ECU). In case of knocking combustions the ignition angle is first retarded and then subsequently advanced again. The small-sized combustion chamber of small two-wheeler engines, uncritical compression ratios and strong enrichment decrease the knock tendency. Nevertheless, knock control can effectuate higher performance, lower fuel consumption, compliance with lower legally demanded emission limits, and the possibility of using different fuel qualities. The Knock-Intensity-Detector 2 (KID2) and the Bosch knock control tool chain, based on many years of experience gained on automotive engines, provides an efficient calibration method that can also be used for two-wheeler engines. The raw signal of the structure-borne noise is used for signal analysis and simulation of different filter settings.

The increasing number of electronic control units (ECUs) in vehicles leads to more and more complex systems with a steadily growing demand for data exchange. This growth includes the number of bus participants, the amount of data and hence the data transfer rates. In addition, the trend towards car-to-x connectivity reinforces the need for new in-vehicle communication solutions. Since the early 1990s Controller Area Network (CAN) is the most widely used powertrain bus system. Since 2000 FlexRay is used in addition to CAN in the premium segment. For classic powertrain applications, the data transfer rates of these bus systems are sufficient; however the utilization is sometimes difficult and gateways are often required. For new applications like hybrid and electric vehicles and the next generation of external communication applications (e.g. telematics services) new concepts based on the existing bus systems or completely new solutions are needed.

AUTOSAR (AUTomotive Open System ARchitecture) is a worldwide standard for automotive basic software in line with an architecture that eases exchange and transfer of application software components between platforms or companies. AUTOSAR provides the standardized architecture together with the specifications of the basics software along with the methodology for developing embedded control units for automotive applications. AUTOSAR matured over the last several years through intensive development, implementation and maintenance. Two main releases (R3.2 and R4.0) represent its current degree of maturity. AUTOSAR is driven by so called core partners: leading car manufacturers (BMW, Daimler, Ford, GM, PSA, Toyota, Volkswagen) together with the tier 1 suppliers Continental and Bosch. AUTOSAR in total has more than 150 companies (OEM, Tier X suppliers, SW and tool suppliers, and silicon suppliers) as members from all over the world.

With the development of start stop technology to improve fuel economy and to reduce carbon dioxide (CO2) emissions, the information of State of Charge (SOC) of the battery is highly desirable. Recent days the battery sensors are used in mid-segment and luxury automobiles that monitors the current, voltage and temperature of the battery and calculates the charge model and sends the information via CAN or LIN. These dedicated sensors are intended to perform various functions other than basic start stop. Hence these sensors are proven to be expensive for emerging market, which is intended to perform only basic start stop as the market is looking for a low cost solution. Bosch- India has developed and implemented a novel idea of bringing a low cost and reliable battery charge detection algorithm that can be realized within the Electronic Control Unit (ECU) without a dedicated sensor.

Developers of safety-critical real-time systems have to ensure that their systems react within given time bounds. Ideally, the system is designed to provide sufficient computing power and network bandwidth, is cost efficient and provides the necessary safety level. To achieve this goal, three challenges have to be addressed. First, it must be possible to account for timing during early development stages in the architecture exploration phase. Second, during software development, timing behavior and the effects of software changes on timing must be observable. Third, there must be a technology for formally verifying the final timing behavior for industry-size applications. In this article we present a comprehensive methodology for dealing with timing which addresses all three issues based on state-of-the-art commercial tools.

The development of vehicle communication networks is challenged not only by the increasing demand in data exchange and required data rate but also the need to connect the vehicle to external sources for personal connectivity of driver and car to infrastructure applications. Solutions are required to master complexity of in-vehicle communication networks, e.g. diagnostic access, flashing of Electronic Control Units, the data backbone connecting the vehicle domains and the data transfer of cameras. Safety (data transfer) and security (violation) issues of the communication networks gain more importance especially by introducing interfaces to external sources either via mobile devices or by connecting the vehicle to other external sources, e.g. Internet and Car to Infrastructure applications. The Internet Protocol (IP) appears to be an ideal solution to address these challenges, especially in connection with an Ethernet physical layer for fast data transfer.

The release of ISO 26262 is only about three months after the 2011 World Congress. However, there are still some contentious aspects that can introduce challenges or cause a disproportionate effort. In this paper, we will show how to avoid these problems. ISO 26262 provides a detailed method for classifying the Automotive Safely Integrity Level (ASIL) of in-vehicle electronic systems. However, the ASIL value for a specific function/product can vary significantly across the industry. Applying a lower level than the industry norm can cause substantial liability problems. Applying a higher level can initiate an “arms race” with competitors. This is particularly true if there are no vehicle-related reasons for choosing the higher level or if it doesn't make the product any safer. To encourage international harmonization, this paper will define ASIL classifications for the main automotive components. Most functions/products are currently being developed using parts of existing products.

In order to master the increasing complexity of electrical/electronic (E/E) systems in vehicles, E/E architecture design has become an established discipline. The task of the E/E architecture design is to come up with solutions to challenging and often contradictory requirements such as reduced cost and increased flexibility / scalability. One way to optimize the E/E architecture in terms of cost (electronics & wiring harness) is to integrate functions. This can be done by either combining functions from multiple ECUs into a single ECU or by introducing Domain Control Units. Domain Control Units provide the main software functionality for a vehicle domain, while relegating the basic functions of actuator control to connected intelligent actuators. Depending on the different market segments (low price, volume and premium) and the different vehicle domains, the actual usage of Domain Control Units can be quite different and sometimes questionable.

In this article a new zero-dimensional model is presented for simulating the cylinder pressure in direct injection diesel engines. The model enables the representation of current combustion processes considering multiple injections, high exhaust gas recirculation rates, and turbocharging. In these methods solely cycle-resolved, scalar input variables from the electronic control unit in combination with empirical parameters are required for modeling. The latter are adapted automatically to different engines or modified applications using measured cylinder pressure traces. The verification based on measurements within the entire operating range from engines of different size and type proves the universal applicability and high accuracy of the proposed method.

Bosch Automotive Semiconductor Unit investigated destroyed semiconductor devices (ASIC) from electronic control unit complaints, which failed due to electrical overstress. It turned out that failure fingerprints could only be reproduced by semiconductor operation far beyond spec limits. One main failure mechanism is caused by hot plugging and bad or late ground connection. In today’s cars some applications are still active for minutes after ignition switch off. So, currents of several amps are delivered and in a typical production or garage environment, hot plugging cannot be avoided completely. Bosch suggests introducing extended ground pins to get an enforced switch on/off sequence during plugging. This poka yoke protection principle is successfully used in other industries for a long time and should now come into cars.