Search Results

Nowadays automobiles are getting smart and there is a growing need for the physical behavior to become part of its software. This behavior can be described in a compact form by differential equations obtained from modeling and simulation tools. In the offline simulation domain the Functional Mockup Interface (FMI) [3], a popular standard today supported by many tools, allows to integrate a model with solver (Co-Simulation FMU) into another simulation environment. These models cannot be directly integrated into embedded automotive software due to special restrictions with respect to hard real-time constraints and MISRA compliance. Another architectural restriction is organizing software components according to the AUTOSAR standard which is typically not supported by the physical modeling tools. On the other hand AUTOSAR generating tools do not have the required advanced symbolic and numerical features to process differential equations.

As automobiles become increasingly smarter, the need to understand within the automotive software the physical behavior of its parts is growing as well. The laws of physics governing such behavior are mostly formulated as differential equations, which today are usually created or obtained from various modeling tools. For solving them, the tools offer several solvers to satisfy the requirements of different problems. E.g. simple and fast explicit low order solvers for non-stiff problems and more complex implicit solvers for stiff problems. Though the modeling and code generation features as available in such tools are desirable for embedded automotive software, they cannot be used directly due to special restrictions with respect to hard realtime constraints. One such restriction is the organization of automotive software in components complying with the AUTOSAR standard which is not widely supported by the modeling tools.