Search Results

During the production controller and software development process, one critical step is the controller and software verification. There are various ways to perform this verification. One of the commonly used methods is to utilize an HIL (hardware-in-the-loop) test bench to emulate powertrain hardware for development and validation of powertrain controllers and software. A key piece of an HIL bench is the plant dynamics model used to emulate the external environment of a modern controller, such as engine (ECM), transmission (TCM) or powertrain controller (PCM), so that the algorithms and their software implementation can be exercised to confirm the desired results. This paper presents a 6-speed automatic transmission plant dynamics model development for hardware-in-the-loop (HIL) test bench for the validation of production transmission controls software. The modeling method, model validation, and application in an HIL test environment are described in details.

In this paper, we proposed a distributed Engineering Computer Aided Learning System. Instead of attending engineering teaching sessions, engineering students are able to interact with the software to gain the same amount of teaching materials. Besides, they will interact with other engineering students from other Engineering schools. The proposed software has the ability to examine the student step by step to reach certain goals. The training and the examination will be different based on the student level and his learning process. Using this system the role of excellent professor can be achieved. The software will have two sessions, i.e. test session and learning session. The software provides the capability of knowledge sharing between multi schools and different educational systems that can provide the students with a large set of training materials. The system was built using JAVA programming language.

Production software validation is critical during software development, allowing potential quality issues that could occur in the field to be minimized. By developing automated and repeatable software test methods, test cases can be created to validate targeted areas of the control software for confirmation of the expected results from software release to release. This is especially important when algorithm/software development timing is aggressive and the management of development activities in a global work environment requires high quality, and timely test results. This paper presents a hardware-in-the-loop (HIL) test bench for the validation of production transmission controls software. The powertrain model used within the HIL consists of an engine model and a detailed automatic transmission dynamics model. The model runs in an OPAL-RT TestDrive based HIL system.

Microprocessors and microcontrollers are now widely used in automobiles. Microprocessor systems contain sources of interrupt and interrupt service routines, which are software components executed in response to the assertion of an interrupt in hardware. A major problem in designing the software of microprocessor systems is the analytical treatment of interrupt latency. Because multiple interrupt service routines are executed on the same CPU, they compete for the CPU and interfere with each other's latency requirements. Here, interrupt latency is defined as the delay between the assertion of the interrupt in hardware and the start of execution of the associated interrupt service routine. It is estimated that 80% of intermittent bugs in small microprocessor software loads are due to improper treatment of interrupts. Until this work, there is no analytic method for analyzing a particular system to determine if it may violate interrupt latency requirements.

In this paper, we review existing software safety standards, guidelines, and other software safety documents. Common software safety elements from these documents are identified. We then describe an adaptable software safety process for automotive safety-critical systems based on these common elements. The process specifies high-level requirements and recommended methods for satisfying the requirements. In addition, we describe how the proposed process may be integrated into a proposed system safety process, and how it may be integrated with an existing software development process.

The demand for drive-by-wire, pre-crash warning and many other new features will require high bandwidth from the future in-vehicle networks. One way to satisfy the high bandwidth requirement of future vehicles is to use a higher bandwidth bus or multiple busses. However, the use of a higher bandwidth bus will increase the cost of the network. Similarly, the use of multiple buses will increase cost as well as the complexity of wiring. Thus, neither option is a viable solution. Another option could be the development of a higher layer protocol to reduce the amount of data to be transferred. The higher layer protocol could be acceptable provided it does not increase the message latencies. The cost of implementing the protocol will be marginal because it can be done by making changes in software. Various data reduction protocols are available in the literature. We have made changes in the existing data reduction protocols to improve the performance of the protocol.

The Hotelling multivariate control chart and the sample generalized variance |S| are used to monitor the mean and dispersion of vehicle build vision data including the pallet information to identify the non-conforming pallets that are used in body shops of FCA US LLC assembly plants. An iterative procedure and the Gaussian mixture model (GMM) are used to rank the non-conforming or bad pallets in the order of severity. The Hotelling multivariate T2 test statistic along with Mason-Tracy-Young (MYT) signal decomposition method is used to identify the features that are affected by the bad pallets. These algorithms were implemented in the Advanced Pallet Analysis module of the FCA US software Body Shop Analysis Toolbox (BSAT). The identified bad pallets are visualized in a scatter plot with a different color for each of the top bad pallets. The run chart of an affected feature confirms the bad pallet by highlighting data points from the bad pallet.

Robust Engineering techniques developed by Taguchi have traditionally applied to the optimization of engineering designs. Robust Engineering methods also may be applied to software testing of ECU algorithms. The net result is an approach capable of improving the software algorithm in one of two ways. First the approach can identify the range of areas which prove problematic to the software such that a robust solution may be developed. Conversely, the approach can be used as a general strategy to verify that the software is robust over the range of inputs tested. The robust engineering methods applied to software testing utilize orthogonal array experiments to test software over a range of inputs. The actual software trials are best performed in the simulation environment and also via automated test hardware in the loop configurations in realtime. This paper outlines a process for applying Robust Engineering methods to software testing.

This paper will address the electronic development in the wireless industry and compare it to the electronic development in the automotive industry. The wireless industry is characterized by rapid, dramatic high tech changes with a less than two-year cycle time and an equivalent life cycle. The automotive electronics industry is working toward reducing the typical 2 to 3 year development cycle down 1 to 2 years but with a life cycle of 10 years or more. In addition to realizing the electronic development benefits seen in the wireless industry, the automotive industry places significantly more emphasis on the quality and reliability aspects of their designs as many of them are targeted toward, or interface with, safety critical applications. One of the lessons learned from the wireless industry is the development process; where the hardware selection process can be accomplished in a virtual environment in conjunction with concurrent software development.

This paper describes a new tool to capture cylinder pressure information, calculate combustion parameters, and implement control algorithms. There are numerous instrumentation and prototyping systems which can provide some or all of this capability. The Cylinder Pressure Development Controller (CPDC) is unique in that it uses advanced high volume automotive grade circuitry, packaging, and software methodologies. This approach provides insight regarding the implementation of cylinder pressure based controls in a production engine management system. A high performance data acquisition system is described along with a data reduction technique to minimize data processing requirements. The CPDC software architecture is discussed along with model-based algorithm development and autocoding. Finally, CPDC calculated combustion parameters are compared with those from a well established combustion analysis system and thermodynamic simulations.

In future, updating various software modules in vehicles on a regular basis will be required for various reasons such as update functionalities in the existing system, add new functionalities, remove software bugs, update navigation map etc. For updating software to a large number of vehicles, remote updating using mobile multicasting would be the most efficient and economic than unicast updating in service station. However, the security requirement of multicast communication, i.e., confidentiality and integrity of the information transmitted and authenticity of the group members, is challenging. In this paper, we investigate issues in designing key management architectures for secure multicast network, particularly for remote software update in future vehicles. Vehicular software distribution network is considered as wireless network where vehicles are connected to the software distributors through base stations.

A new inter-disciplinary degree program has been developed at Lawrence Technological University: the Master of Science in Mechatronic Systems Engineering Degree (MS/MSE). It is one of a few MS-programs in mechatronics in the U.S.A. today. This inter-disciplinary program reflects the main areas of ground vehicle mechatronic systems and robotics. This paper presents areas of scientific and technological principles which the Mechanical Engineering, Electrical and Computer Engineering, and Math and Computer Science Departments bring to Mechatronic Systems Engineering and the new degree program. New foundations that make the basis for the program are discussed. One of the biggest challenges was developing foundations for mechanical engineering in mechatronic systems design and teaching them to engineers who have different professional backgrounds. The authors first developed new approaches and principles to designing mechanical subsystems as components of mechatronic systems.

The purpose of the Institute for Manufacturing Research (IMR) is to enhance Wayne State University's existing technological strength in the areas of manufacturing research which have demonstrated potential benefits for the State's economy. IMR's faculty conduct basic and applied research in selected areas of manufacturing science. The research programs within the Institute are broadly interdisciplinary and industrially interactive, and are organized around the following areas: materials development, modification, and nondestructive evaluation; software technology for manufacturing and engineering; and product reliability and machine tool research. Faculty from eight departments within the Colleges of Science and Engineering participate in IMR.

A requirement of many modern safety-critical automotive applications is to provide failsafe operation. Several analysis methods are available to help confirm that automotive safety-critical systems are designed properly and operate as intended to prevent potential hazards from occurring in the event of system failures. One element of safety-critical system design is to help verify that the software and microcontroller are operating correctly. The task of incorporating failsafe capability within an embedded microcontroller design may be achieved via hardware or software techniques. This paper surveys software failsafe techniques that are available for application within a microcontroller design suitable for use with safety-critical automotive systems. Safety analysis techniques are discussed in terms of how to identify adequate failsafe coverage.

With the inception of model-based design and automatic code generation, many organizations are developing controls and diagnostics algorithms in model-based development tools to meet customer and regulatory requirements. Advances in model-based design have made it easier to generate C code from models and help software engineers streamline their workflow. Typically, after the software has been developed, the models are handed over to a calibration team responsible for calibrating the features to meet specified customer and regulatory requirements. However, once the models are handed over to the calibration team, the calibration engineers are unaware of how to calibrate the features because documentation is not available. Typically, model documentation trails behind the software process because it is created manually, most of this time is spent on formatting. As a result, lack of model documentation or up-to date documentation causes a lot of pain for OEM’s and Tier 1 suppliers.

The explosion of big data has created challenges for both cloud-based systems and Autonomous Vehicles (AVs) in data collection and management. The same challenges are now being realized in developing databases for integrated sensors, streaming, real-time and on-demand services in AVs. With just one AV expecting to generate over 30 Terabytes of data a day, modern NoSQL databases provide opportunities to horizontally scale AV data seamlessly. NoSQL provides solutions designed to accommodate a wide variety of data models such as, key-value, document, column and graph databases. Key-value stores are by nature scalable, fast processing, and distribute horizontally. These databases are tasked with handling several data types including IoT, radar, lidar, ultra-sonic sensors, GPS, odometry, and sensor data while providing streaming and real-time services. NoSQL can store and utilize structured, semi-structured, and unstructured data necessary for multimedia storage needs.