Search Results

The safety monitor is a high integrity control that monitors the health and performance of safety related computer controlled functions in vehicles. The integrity of the safety monitor code is critical to the overall performance of the control software. Traditionally, once monitor requirements are understood, then the safety monitor is hand coded or created in a modeling environment. New practices such as ISO 26262 prescribe formal or semiformal methods are used against certain classes of foreseeable faults. Recently, a new tool, which is capable of auto-generating C-code based on safety monitor formal functional requirements is available from BTC Company. Ford Motor Company investigated the tool using an application example from a powertrain control feature safety monitor.

Lookup tables and functions are widely used in real-time embedded automotive applications to conserve scarce processor resources. To minimize the resource utilization, these lookup tables (LUTs) commonly use custom data structures. The lookup function code is optimized to process these custom data structures. The legacy routines for these lookup functions are very efficient and have been in production for many years. These lookup functions and the corresponding data structures are typically used for calibration tables. The third-party calibration tools are specifically tailored to support these custom data structures. These tools assist the calibrators in optimizing the control algorithm performance for the targeted environment for production. Application software typically contains a mix of both automatically generated software and manually developed code. Some of the same calibration tables may be used in both auto generated and hand-code [ 1 ] [ 2 ].

Automotive manufacturers continue to move further toward powertrain electrification. There are already many hybrid electric vehicles on the market that are based on a variety of system architectures. Ford Motor Company has investigated a new Dual Drive configuration that promises to overcome some of the attribute deficiencies associated with current architectures. The primary objective of this development project was to demonstrate the fuel economy potential of this system in a vehicle. To accomplish this objective, the team used an internally developed, formal Controls Development Process (CDP) for the control system design and validation. This paper describes the development of the vehicle control system in the context of this process.

Through the use of hybrid technology, Ford Motor Company continues to realize enhanced vehicle fuel economy while meeting customer performance and drivability targets. As is characteristic of all Ford Hybrid Electric Vehicles (HEVs), the basis for resolving these competing requirements resides with its Vehicle System Control (VSC) strategy. This strategy implements complex high-level executive controls to coordinate and optimize the desired operational state of the major HEV powertrain subsystems. To ensure that the VSC software meets its intended functionality, a software validation process developed at Research and Advanced Engineering has been integrated as part of the vehicle controls development process. In this paper, this VSC software validation process implemented for a next generation hybrid powertrain is presented. First, an overview of the hybrid powertrain application and the VSC software architecture is introduced.