Search Results

Electronic control units (ECUs) offer a modular, networked approach to real time machine control and diagnostics. Software embedded in these controllers offer agile and customizable solutions because of the intimate relationship with the ECU hardware and its inputs/outputs. In an idealistic view, embedded software should support the machine's life - 30 years or longer. Developing and maintaining software for these systems requires a strategy. A framework demonstrating common building blocks and long-term centralized support for ECUs on a machine is presented. This strategy reduces the detailed knowledge of the specific machine controls needed by ECU developers and provides the components and infrastructure key to extending the life and functionality of the ECU.

Papers in the session cover zero-dimensional, one-dimensional, and quasi-dimensional models for simulation of SI and CI engines with respect to: engine breathing, boosting, and acoustics; SI combustion and emissions; CI combustion and emissions; fundamentals of engine thermodynamics; numerical modeling of gas dynamics; thermal management; mechanical and lubrication systems; system level models for controls; and system level models for vehicle fuel economy and emissions predictions.

Papers in the session cover zero-dimensional, one-dimensional, and quasi-dimensional models for simulation of SI and CI engines with respect to: engine breathing, boosting, and acoustics; SI combustion and emissions; CI combustion and emissions; fundamentals of engine thermodynamics; numerical modeling of gas dynamics; thermal management; mechanical and lubrication systems; system level models for controls; and system level models for vehicle fuel economy and emissions predictions.

It is well known that backpressure is one of the important parameters to be minimised during the exhaust system development. Unfortunately, during the first phases of an engineering process of a new engine, engine prototypes are not available yet. Due to this the exhaust system backpressure is generally evaluated using simulation software, and/or measuring the backpressure by a flow rig test at room temperature. Goal of this paper is to compare exhaust backpressure results obtained respectively: i) at the room temperature flow rig; ii) at the engine dyno bench; iii) by simulation with one of the most common 1D fluidodynamics simulation tool (Gt-Power). A correlation of the three different techniques is presented.

A 10 KWe dual-mode space power system concept has been identified which is based on INEL's Small Externally-fueled Heat Pipe Thermionic Reactor (SEHPTR) concept. This power system will enhance user capabilities by providing reliable electric power and by providing two propulsion systems; electric power for an arc-jet electric propulsion system and direct thrust by heating hydrogen propellant inside the reactor. The low thrust electric thrusters allow efficient station keeping and long-term maneuvering. The direct thrust capability can provide tens of pounds of thrust at a specific impulse of around 730 seconds for maneuvers that must be performed more rapidly. The direct thrust allows the nuclear power system to move a payload from Low Earth Orbit (LEO) to Geosynchronous Earth Orbit (GEO) in less than one month using approximately half the propellant of a cryogenic chemical stage.

Model-based software development is a well-established software development process and recognized by ISO26262 [1] as allowing for highly consistent and efficient development. Nevertheless, enhancing a model-based development process in such a way that it is compliant with the ISO26262 safety standard is a challenging task. To achieve ISO26262 compliance, the development team of a safety-related software project faces a multitude of additional requirements for the development process without a corresponding increase of the project budget to fulfill them. The fact that many of the requirements of ISO26262 are defined in a very generic way such that an interpretation is required further hampers their implementation. We propose a 10-step strategy to achieve an ISO26262 compliant model-based software development process. This strategy relates ISO26262 requirements with state-of-the art methods and approaches currently used for model-based software development.