Search Results

The Electro Gyro-Cator allows a driver to monitor his progress, plot and follow courses to a destination, select alternate routes, and drive more safely on unfamiliar roads or at night. Employing a sealed helium gas-rate gyro, the Electro Gyro-Cator offers visual display (CRT display) of a car's present location, direction and route, with overlay maps for fast, simple route selection and monitoring. The primary elements of the unit include trip and direction sensors, a 16-Bit central processing unit, a CRT display screen and a collection of transparent overlay maps fitted to the screen.

An essential feature of the Audi Quattro permanent four-wheel drive system is in the inter-axle differential located on the hollow output shaft in the gearbox: the drive is taken from this differential forward to the front differential through the inside of the hollow shaft, and rearward to a propellor shaft driving the rear differential. The major advantages in everyday driving include improved traction and a reduced tendency toward throttle induced changes of attitude. The greater traction allows not only better progress in difficult road conditions; it also gives better acceleration in difficult traffic situations, such as when joining a busy main road. The more easily predictable handling response to throttle changes means that Quattro vehicles have better tracking stability. Altogether, the active safety and "roadability" are considerably improved.

Electronic control units (ECUs) offer a modular, networked approach to real time machine control and diagnostics. Software embedded in these controllers offer agile and customizable solutions because of the intimate relationship with the ECU hardware and its inputs/outputs. In an idealistic view, embedded software should support the machine's life - 30 years or longer. Developing and maintaining software for these systems requires a strategy. A framework demonstrating common building blocks and long-term centralized support for ECUs on a machine is presented. This strategy reduces the detailed knowledge of the specific machine controls needed by ECU developers and provides the components and infrastructure key to extending the life and functionality of the ECU.

This paper presents an overview of the evolution & revolution of automotive E/E architectures and how we at Bosch, envision the technology in the future. It provides information on the bottlenecks for current E/E architectures and drivers for their evolution. Functionalities such as automated driving, connectivity and cyber-security have gained increasing importance over the past few years. The importance of these functionalities will continue to grow as these cutting-edge technologies mature and market acceptance increases. Implementation of these functionalities in mainstream vehicles will demand a paradigm shift in E/E architectures with respect to in-vehicle communication networks, power networks, connectivity, safety and security. This paper expounds on these points at a system level.

The testing system developed will decrease the time and the costs involved in evaluating cylinder head valve bridge designs. The test uses actual data generated from engine testing to recreate the valve bridge cracks that occur during dynamometer and vehicle testing. This paper focuses on the system description, the test development, design modifications, and the test results obtained. Testing shows that this method correctly separates valve bridge designs by test cycle life using statistical methods. It is a cost effective and timely alternative to dynamometer testing.

This work deals with the CAE simulation of the behaviour of a belt employed in a CVT transmission of a large displacement scooter engine. Both FEM and MBS simulations were performed, in order to estimate the dynamic loads acting on the component and the stress state the belt is subject to. The MBS simulations were backed up by simple FEM tests performed in order to estimate the elastic properties of elementary portions of the belt. The MBS system comprised the belt and the two pulleys. As a result, the force components the pulleys exert on the belt were calculated. FEM non-linear analyses were performed in order to estimate the stress state the belt experiences. The belt's both manufacturing and working conditions were simulated.

Sensitivity analysis is a usual method to evaluate how “sensitive” is a product performance to changes in its design variables. This type of analysis identifies the critical variables related to product performance and other aspects that may have less demanding manufacturing controls. This paper presents a case study in the automotive market, applying the 1-D dynamic modeling as an auxiliary tool to the sensitivity analysis. The objective of this procedure is to reduce physical prototypes tests. This evaluation, if taken during preliminary design of the system, could give competitive advantages, with a reduction in product development cycle time and cost.

It is well known that backpressure is one of the important parameters to be minimised during the exhaust system development. Unfortunately, during the first phases of an engineering process of a new engine, engine prototypes are not available yet. Due to this the exhaust system backpressure is generally evaluated using simulation software, and/or measuring the backpressure by a flow rig test at room temperature. Goal of this paper is to compare exhaust backpressure results obtained respectively: i) at the room temperature flow rig; ii) at the engine dyno bench; iii) by simulation with one of the most common 1D fluidodynamics simulation tool (Gt-Power). A correlation of the three different techniques is presented.

This SAE Aerospace Standard (AS) contains requirements for a digital time division command/response multiplex data bus, for use in systems integration that is functionally similar to MIL-STD-1553B with Notice 2 but with a star topology and some deleted functionality. Even with the use of this document, differences may exist between multiplex data buses in different system applications due to particular application requirements and the options allowed in this document. The system designer must recognize this fact and design the multiplex bus controller (BC) hardware and software to accommodate such differences. These designer selected options must exist to allow the necessary flexibility in the design of specific multiplex systems in order to provide for the control mechanism, architectural redundancy, degradation concept, and traffic patterns peculiar to the specific application requirements.

This SAE Aerospace Standard (AS) contains requirements for a digital time division command/response multiplex data bus, for use in systems integration that is functionally similar to MIL-STD-1553B with Notice 2 but with a star topology and some deleted functionality. Even with the use of this document, differences may exist between multiplex data buses in different system applications due to particular application requirements and the options allowed in this document. The system designer must recognize this fact and design the multiplex bus controller (BC) hardware and software to accommodate such differences. These designer selected options must exist to allow the necessary flexibility in the design of specific multiplex systems in order to provide for the control mechanism, architectural redundancy, degradation concept, and traffic patterns peculiar to the specific application requirements.

Model-based software development is a well-established software development process and recognized by ISO26262 [1] as allowing for highly consistent and efficient development. Nevertheless, enhancing a model-based development process in such a way that it is compliant with the ISO26262 safety standard is a challenging task. To achieve ISO26262 compliance, the development team of a safety-related software project faces a multitude of additional requirements for the development process without a corresponding increase of the project budget to fulfill them. The fact that many of the requirements of ISO26262 are defined in a very generic way such that an interpretation is required further hampers their implementation. We propose a 10-step strategy to achieve an ISO26262 compliant model-based software development process. This strategy relates ISO26262 requirements with state-of-the art methods and approaches currently used for model-based software development.

Abstract The ASTM D130 was first issued in 1922 as a tentative standard for the detection of corrosive sulfur in gasoline. A clean copper strip was immersed in a sample of gasoline for three hours at 50°C with any corrosion or discoloration taken to indicate the presence of corrosive sulfur. Since that time, the method has undergone many revisions and has been applied to many petroleum products. Today, the ASTM D130 standard is the leading method used to determine the corrosiveness of various fuels, lubricants, and other hydrocarbon-based solutions to copper. The end-of-test strips are ranked using the ASTM Copper Strip Corrosion Standard Adjunct, a colored reproduction of copper strips characteristic of various degrees of sulfur-induced tarnish and corrosion, first introduced in 1954. This pragmatic approach to assessing potential corrosion concerns with copper hardware has served various industries well for a century.

Two Cummins B5.9L engines were fueled with 100% biodiesel in excess of 48 months by the Agricultural Engineering Department at the University of Missouri-Columbia. The engines used to power Dodge pickups. The engine lubricating oil was sampled at 1000 mile intervals for analysis. Statistical analysis of the engine lubricating oil indicated that the wear metal levels in the lubricating oil were normal. A reduction in power was noted when the engines were tested using a chassis dynamometer. The 1991 pickup has been driven 110,451 km and the 1992 pickup has been driven approximately 177,022 km. The pickups averaged 6.9 km/L. Engine fuel efficiency and material compatibility issues are addressed in the paper.

This standard covers un-shielded (JUTP) and shielded (STP) balanced single twisted pair jacketed data cable intended for use in surface vehicle cables for 1 Gb/s ethernet applications. The tests in this standard are intended to qualify cables for normal operation in an automotive environment while maintaining the necessary electrical properties for reliable data transmission.

This standard covers un-shielded (JUTP) and shielded (STP) balanced single twisted pair jacketed data cable intended for use in surface vehicle cables for 1000BASE-T1 ethernet PHY (1 Gb/s) applications. The tests in this standard are intended to qualify cables for normal operation in an automotive environment while maintaining the necessary electrical properties for reliable data transmission.