Search Results

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.

Accurate evaluation of vehicles' transient total power requirement helps achieving further improvements in vehicle fuel efficiency. When operated, the air-conditioning (A/C) system is the largest auxiliary load on a vehicle, therefore accurate evaluation of the load it places on the vehicle's engine and/or energy storage system is especially important. Vehicle simulation models, such as "Autonomie," have been used by OEMs to evaluate vehicles' energy performance. However, the load from the A/C system on the engine or on the energy storage system has not always been modeled in sufficient detail. A transient A/C simulation tool incorporated into vehicle simulation models would also provide a tool for developing more efficient A/C systems through a thorough consideration of the transient A/C system performance. The dynamic system simulation software MATLAB/Simulink® is frequently used by vehicle controls engineers to develop new and more efficient vehicle energy system controls.

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.

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.

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.

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.

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.

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).

A fixed-base driving simulator with a 14-degree of freedom vehicle dynamics model was used to compare the lane tracking performance of test subjects using a joystick steering controller to that using a conventional steering wheel. Three driving situations were studied: a) straight-line highway driving, b) winding road driving (country road), and c) evasive maneuvering - a double lane change event. In addition, three different joystick force-feedback settings were evaluated: i) linear force feedback, ii) non-linear, speed sensitive force feedback and iii) no force feedback. A conventional steering wheel with typical passenger car force feedback tuning was used for all of the driving events for comparison.

Evolutionary Operation (EVOP) experimental design using Sequential Simplex method is an effective and robust means for determining the ideal process parameter (factor) settings to achieve optimum output (response) results. EVOP is the methodology of using on-line experimental design. Small perturbations to the process are made within allowable control plan limits, to minimize any product quality issues while obtaining information for improvement on the process. It is often the case in high volume production where issues exist, however off-line experimentation is not an option due to production time, the threat of quality issues and costs. EVOP leverages production time to arrive at the optimum solution while continuing to process saleable product, thus substantially reducing the cost of the analysis.

A motorized throttle model has been developed in block diagram form (Simulink®). Its primary input is the control signal to the throttle motor's electrical H-driver. The model's primary output is throttle position sensor signal. The model's utility for vehicle and engine simulations is proved with validation data. While a DC motor actuated positioning device is well known, special attention is paid to modeling subtle but significant physical characteristics. Further, the model is structured to overcome numerical simulation issues. The laboratory environment that connects a Powertrain Control Module (PCM) to vehicle powertrain simulation hardware is diagramed. This paper is useful to those modeling this and similar actuators as it points out pitfall avoidance for real time simulation issues. It avoids reliance on difficult-to-measure characteristics that cloud validation validity.

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.

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.

This paper discusses the development of combination vehicle stability program (CVSP) at Visteon. It will describe why stability control is needed for combination vehicles and how the vehicle stability can be improved. We propose and evaluate controller structures and design methods for CVSP. These include driver's intent identification, combination vehicle status estimation and control, and fault detection / tolerance. In this paper, the braking and steering dynamics of car-trailer and tractor-semitrailer combinations, and the brake systems which should be used extensively to increase the stability of combination vehicles are presented. Also our development platform is introduced and the combination vehicle simulation results are presented. The definition of combination vehicles in this paper includes car-trailer and commercial tractor-semitrailer combinations since their vehicle dynamics are based on the same equations of motion.

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.

Data design is a very critical step in the model-based software development process. This paper discusses the importance of a data dictionary in modeling, automatic code generation and in creating model dependency graphs.