Search Results

Vehicle Infrastructure Integration (VII) is an initiative of the US Department of Transportation to provide communications among vehicles and between vehicles and roadside infrastructure in order to increase the safety and productivity of transportation systems. It makes use of but is not restricted to the 5.9 GHz Dedicated Short Range Communication (DSRC) spectrum. There are 3 major categories of applications for VII - Highway Safety, Vehicular Mobility, and Consumer & Commercial Services. There are currently approximately 42,000 traffic fatalities a year in the United States. Reducing deaths, injuries and property damage is of the highest priority in the development of VII applications. Electronic Brake Warning, Signal Phase and Timing, and Collision Detection are among the applications dedicated to improving highway safety. Increasing traffic volume is outpacing the addition of new roadway capacity, resulting in increasing delays, congestion and frustration.

The FCC allocated the 5.9 GHz spectrum to enhance the safety and productivity of the nations transportation system. Dedicated Short Range Communication (DSRC) is a medium range wireless communication protocol that supports vehicle-to-vehicle, vehicle-to-roadside, and roadside-to-vehicle communication. It enables both public safety and licensed private transactions. DSRC contrasts cellular and Wi-Fi by providing fast acquisition, low latency communication in a relatively close communication range. IEEE is developing the Wireless Access in Vehicular Environment (WAVE) communication standards to provide the groundwork for DSRC and enable seamless, interoperable services. The WAVE architecture includes IEEE P1609.1 (Application layer), IEEE P1609.2 (Security layer), IEEE P1609.3 (Network layer), IEEE P1609.4 (Upper MAC Layer), and IEEE 802.11p (Lower MAC and Physical layers).

Audio playbacks are mechanisms which read data from a storage medium and produce commands and signals which an audio system turns into music. Playbacks are constantly changed to meet market demands, requiring that the control software be updated quickly and efficiently. This paper reviews a 12 month project using the MATLAB/Simulink/Stateflow environment for model-based development, system simulation, autocode generation, and hardware-in-the-loop (HIL) verification for playbacks which read music CDs or MP3 disks. Our team began with a “clean slate” approach to playback architecture, and demonstrated working units running production-ready code. This modular, layered architecture enables rapid development and verification of new playback mechanisms, thereby reducing the time needed to evaluate playback mechanisms and integrate into a complete infotainment system.

The technological and process developments within the semiconductor industry during the past two decades has led to significant advancements in the complexity, functionality and performance of standard devices, such as microprocessors, digital signal processors, memories and custom Application Specific Integrated Circuits (ASICs). Field Programmable Gate Array (FPGA) suppliers have taken advantage of these developments to offer device configurations that can include millions of programmable gates integrated with megabytes of internal memory and processor cores in package profiles and temperature ranges suitable for a variety of applications. The combination of reusable intellectual property, low unit costs and relative ease of implementation has led to increased FPGA usage in the automotive industry. Engineers are turning to FPGA solutions to enable the required features and functions not currently available with standard components.

Since the end of the 1990s, model-based development processes have increasingly been adopted for the development of automotive embedded control software. One of the main goals of this approach is a reduction of project development time. This reduction is achieved through the use of executable modeling and autocoding. Due to the current constraints for a majority of embedded controllers on microprocessor memory and throughput, efficient production-quality code can not be generated from an executable model with the push of a button. The autocoding process requires manual setting of the software properties for the model's blocks and components by a software professional. Once the code is generated, code verification is needed. Although in many cases autocode generation and verification stages take less time to execute as compared to handcoding techniques, they still require substantial time to perform.