Search Results

Electronic Control Units (ECUs) are typically programmed using external programming devices - frequently called Diagnostic Testers. We propose a system and software architecture that requires no Diagnostic Tester for ECU (re)programming. ECU (re)programming is instead managed by an on-board software component, the Flashware-Reprogramming-Controller. It can reside in any ECU that has sufficient memory and processing power as well as good connectivity to internal networks and external sources from which to receive the software to be installed. Appropriate choices could be modern telematic devices. A second co-located on-board software component - the Installation-Configuration-Controller - is used to supervise the installation of new software releases and to validate their integrity after installation. The proposed architecture can be used for software download into ECUs in development, end-of-line production and after sales.

Two active boom noise damping techniques using a Helmholtz resonator-based compensator and a lead compensator called a positive pressure feedback have been developed at the University of Dayton [1]. The two damping techniques are of feedback type and their compensators can be implemented in software or hardware (using inexpensive operational amplifiers). The active damping system would rely on a speaker, a low-cost microphone, two accelerometers, and an electronic circuit (or a micro-controller) to add damping to the offending low-frequency vibroacoustic modes of the cavity. The simplicity of the active boom noise damping system lends itself to be incorporated into a vehicle's sound system. The Helmholtz resonator-based strategy is implemented on a Dodge Durango sport utility vehicle. The control scheme adds appreciable amount of damping to the first cavity mode and the first structurally induced acoustic mode of the cabin.

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.