Search Results

Automatic code generation from models is actively used at Caterpillar for powertrain and machine control development. This technology was needed to satisfy the industry's demands for both increased software feature content, and its added complexity, and a short turn-around time. A pilot development effort was employed initially to roll out this new technology and shape the deployment strategy. As a result of a series of successful projects involving rapid prototyping and production code generation, Caterpillar will deploy MathWorks modeling and code generation products as their department-wide production development capability. The data collected indicated a reduction of person hours by a factor of 2 to 4 depending on the project and a reduction of calendar time by a factor of greater than 2. This paper discusses the challenges, results, and lessons learned, during this pilot effort from the perspectives of both Caterpillar and The MathWorks.

The adoption of simulation is critical to reducing development time and enhancing system robustness for Advanced Driver Assistance Systems (ADAS). Automotive companies typically have an abundance of real data recorded from a vehicle which is suitable for open-loop simulations. However, recorded data is often not suitable to test closed-loop control systems since the recorded data cannot react to changes in vehicle movement. This paper introduces a methodology to create virtual driving scenarios from recorded vehicle data to enable closed-loop simulation. This methodology is applied to test a lane centering application. A lane centering application helps a driver control steering to stay in the current lane and control acceleration and braking to maintain a set speed or to follow a preceding vehicle. The driver’s vehicle is referred to as the ego vehicle. Other vehicles on the road are referred to as target vehicles.

This paper presents the business purpose, software architecture, technology integration, and applications of the Cummins Vehicle Mission Simulation (VMS) software. VMS is the value-based analysis tool used by the marketing, sales, and product engineering functions to simulate vehicle missions quickly and to gauge, communicate, and improve the value proposition of Cummins engines to customers. VMS leverages the best of software architecture practices and proven technologies available today. It consists of a close integration of MATLAB and Simulink with Java, XML, and JDBC technologies. This Windows compatible application software uses stand-alone mathematical models compiled using Real Time Workshop. A built-in MySQL database contains product data for engines, driveline components, vehicles, and topographic routes. This paper outlines the database governance model that facilitates effective management, control, and distribution of engine and vehicle data across the enterprise.

When developing production software for fixed-point Engine Control Units (ECUs), it is important to consider the transition from floating-point to fixed-point algorithms. Systems engineers frequently design algorithms in floating-point math, usually double precision. This represents the ideal algorithm behavior without much concern for its final realization in production software and hardware. Software engineers and suppliers in mass production environments, however, are concerned with production realities and often need to convert these algorithms to fixed-point math for their integer-only hardware. A key task is to design scale factors that maximize code efficiency by minimizing the bytes used, while also minimizing quantization effects such that the fixed-point algorithms match the floating-point results within an acceptable numerical margin.

This paper will discuss the issues associated with the creation of embedded software for automotive electronic control systems and show how these issues can be addressed using model-based methods to design, test and implement these systems. Model-based methods are already in use for many automotive applications, and there are potentially many more areas where they could be used, especially as the number and complexity of automotive embedded control systems increase. This paper will cite several examples of the successful use of model-based design.

With the introduction of new technologies ranging from developing new alternative energy vehicles to passive and active safety systems, the automakers are responding to the increased complexity of the control system by embracing Model Based Design (MBD) and Auto-code Generation (ACG) tools for control system design. This translates into lower development costs, higher quality and faster time-to-market. The Ford Motor Company production hybrid group launched a pilot project to study the feasibility of using MBD to speed up the development and testing of the next generation Torque Monitor software. This software uses a custom data storage format, called Double Store Variable (DSV) format, for all the critical signals. Each variable contains two fields, one for storing the actual data and the second for storing a transformed copy (e.g. one's complement) of the data. This allows the software to detect run-time corruption of the data in real-time.

Software developed for safety-critical systems needs to be of high integrity. Special precautions and development steps are needed for high-integrity software that are not required for other software, although many would argue that they should be. Examples include language subsets, Verification and Validation (V&V), inspections, requirements traceability, documentation, and structural test coverage. Production code generation supports these activities by providing a complete software engineering development environment using models to specify the software. The models can then be tested and stressed within boundaries of the modeling environment. The tests and results can then be reused and applied to the generated code. This paper describes high-integrity code development techniques and shows how they can be automated and applied at the model level, improving quality while shortening design cycles.

When developing software it is important to consider process, methods, and tools. For safety-critical software, standards such as IEC 61508 are often used to impose additional constraints on the development process and require the production of verification evidence and other artifacts. These constraints and artifacts are needed whether or not the design and code were produced manually or via tool automation. This paper discusses the usage of Production Code Generation for safety-critical software development.