Refine Your Search

Search Results

Viewing 1 to 11 of 11
Technical Paper

A Scalable Engine Management System Architecture for Motorcycle/Small-Vehicle Application

2008-09-09
2008-32-0054
This paper gives an overview of a scalable engine management system architecture for motorcycle and other small engine based vehicle applications. The system can accommodate any engine sizes and up to four cylinders. The architecture incorporates advanced functionalities such as oxygen sensing, closed loop fueling, wall-wetting compensation, purge control, start & idle control and deceleration fuel cut-off. Additionally, a number of vehicle-related controls are integrated in the system. Diagnostic and safety related features have also been incorporated with limp-home capability. The software architecture is compatible with different hardware solutions. The system has been implemented in several OEM vehicles around the globe and meets EURO-3 emission requirements.
Technical Paper

Test Strategy for Linux based Platforms using Open Source Tools

2016-04-05
2016-01-0053
Today open source software is widely used in different domains like Desktop systems, Consumer electronics (smart phones, TV, washing machines, camera, printers, smart watches), Automotive, Automation etc. With the increased involvement of the open source software in the different domains including the safety critical ones, there has been a requirement of the well-defined test strategy to test and verify such systems. Currently there are multiple open source tools and frameworks to choose from. The paper describes the various open source test strategies and tools available to qualify such systems, their features, maintenance, community support, advantages and disadvantages. Target audience would be the software engineers, program managers, using an open source stack for the product development.
Technical Paper

Software Validation a Vital Activity for a Mature Product Development Organization

2005-11-22
2005-01-4168
Software is today one of the most important components of electronic products. The capture and validation of the requirements makes a difference if the product will fulfill the customer's expectations or generate enormous frustration. The correct implementation of software validation makes the Product Development Organization more mature and reliable. Software validation is an opportunity for the product development team to identify if the requirements and customer expectations were achieved. It is also used to identify the risks and possible improvements to the product. Software testing is one element of a brooder topic that is often referred to as verification and validation (V&V). Verification refers to the set of activities that ensure that software correctly implements a specific function. Validation refers to a different set of activities that ensure that the software that has been built is traceable to customer requirements.
Technical Paper

An Overview of Hardware-In-the-Loop Testing Systems at Visteon

2004-03-08
2004-01-1240
This paper discusses our experiences on the implementation and benefits of using the Hardware-In-the-Loop (HIL) systems for Powertrain control system software verification and validation. The Visteon HIL system integrated with several off-the-shelf diagnostics and calibration tools is briefly explained. Further, discussions on test automation sequence control and failure insertion are outlined The capabilities and advantages of using HIL for unit level software testing, open loop and closed-loop system testing, fault insertion and test automation are described. HIL also facilitates Software and Hardware Interface validation testing with low-level driver and platform software. This paper attempts to show the experiences with and capabilities of these HIL systems.
Technical Paper

Accelerated Life Cycle Development for Electronic Throttle Control Software using Model-Based/Auto-Code Technology

2004-03-08
2004-01-0276
The purpose of this paper is to demonstrate our success in taking advantage of model-based development tools and auto-code technology to accelerate the typical life cycle development of powertrain software. In particular, we applied the technology as a clean sheet approach to Visteon's third generation Electronic Throttle Control system. In the process of applying model-based development and 100% auto-code, we identified various pitfalls and created solutions to overcome the gap between technology and development process during each phase of the entire software development life cycle. We will share our lessons learned during the requirement, design, implementation, and validation stages.
Technical Paper

Multi-Target Modelling for Embedded Software Development for Automotive Applications

2004-03-08
2004-01-0269
Manual ‘porting” of source code is often required in order to “reuse” control software in different applications with different target hardware. This process is not cost effective. Maintaining multiple “versions” of the same software also causes problems. This paper describes a way in which multiple target source code can be generated from a single model. A custom data class is developed so that it can be used to define both signal and parameter data types necessary for data dictionary-driven models. This capability allows a single model to be used to generate code for multiple target hardware architectures. A software development process using a generic model to support multiple hardware targets is compared with the hand porting process (e.g. floating-point to/from fixed-point). Auto code generation from a sample multi-target feature model will be presented. The efficiency of the auto code will also be discussed.
Technical Paper

Control Software Interface for Managing System Requirements

2004-03-08
2004-01-0363
Not all software tools are created equal and not all software tools are created to perform the same tasks. Therefore, different software tools are used to perform different tasks. However, being able to share the information between the different software tools, without having to manually re-enter (duplicate) any of the information, can save a lot of time and improve the quality of the product. The control software interface presented in this paper, allows system engineers to exchange data between software tools in an efficient manner which maximizes each tools capabilities and ultimately reduces development time and improves the quality of the product.
Technical Paper

Analytical Calculation of the Critical Speed of a Driveshaft

2005-05-16
2005-01-2310
Determination of the critical speed of a driveshaft is critical for development and validation of its design for use in a vehicle because of its destructive effects. Typical calculations to determine critical speed are either over simplistic and not very accurate or very complicated requiring CAE software and capabilities. An analytical five-section non-prismatic beam model was developed to fill in this gap. The model was developed to compute the critical speed in a worksheet and proven to be as or more accurate as utilizing FEA methods. The model worksheet calculates the critical speed for one-piece conventional driveshafts and adapted for Visteon's Slip-In-Tube (SIT) driveshafts.
Technical Paper

A Dynamic Model of Automotive Air Conditioning Systems

2005-04-11
2005-01-1884
A dynamic computer model of automotive air conditioning systems was developed. The model uses simulation software for the coding of 1-D heat transfer, thermodynamics, fluid flow, and control valves. The same software is used to model 3-D solid dynamics associated with mechanical mechanisms of the compressor. The dynamics of the entire AC system is thus simulated within the same software environment. The results will show the models potential applications in component and system design, calibration and control.
Technical Paper

Development of Modular Electrical, Electronic, and Software System Architectures for Multiple Vehicle Platforms

2003-03-03
2003-01-0139
Rising costs continue to be a problem within the automotive industry. One way to address these rising costs is through modularity. Modular systems provide the ability to achieve product variety through the combination and standardization of components. Modular design approaches used in development of vehicle electrical, electronic, and software (EES) systems allow sharing of architectures/modules between different product lines (vehicles). This modular design approach may provide economies of scale, reduced development time, reduced order lead-time, easier product diagnostics, maintenance and repair. Other benefits of this design approach include development of a variety of EES systems through component swapping and component sharing. In this paper, new optimization algorithms and software tools are presented that allow vehicle EES system design engineers to develop modular architectures/modules that can be shared across vehicle platforms (for OEMs) and across OEMs (for suppliers).
X