Refine
Document Type
Language
- English (3)
Has Fulltext
- no (3)
Publication reviewed
- begutachtet (2)
- nicht begutachtet (1)
Institute
The functional mock-up interface (FMI) for co-simulation (CS) aims to provide a generic representation of dynamic system models, which can be coupled for co-simulations. A system model con-forming to FMI is called a functional mock-up unit (FMU). Being a standardised interface FMI for CS defines not only the required structure of FMUs but also provides an application programming interface (API) for coupled integration of FMUs in a support-ing simulation environment. FMI for CS is an exten-sion of FMI for Model Exchange (ME), which is mainly intended to provide standardised model descriptions. Since this work is focused on co-simulation the indicating suffix shall be omitted such that FMI stands for FMI for CS. FMI facilitates enhanced simulation workflows through better exchange of models between de-partments and vendors. While a growing number of vendors seeks to adopt FMI, the compliance of integration environments and FMUs to the FMI standard gains in significance. Only fully compliant simulation environments and FMUs reliably yield simulation results that aid actual design decisions. The intention of this work is to develop a proper means to detect ambiguities and errors in imple-mentations of FMI 1.0. The task is twofold in that both FMUs and integration environments using these FMUs may violate constraints given by the FMI standard. This work will focus on the role of integration environments.
Fueled by the continuous, rapid progress within microelectronics, ever more intelligent and intricate functions are realized in mechatronic systems. To control the complexity associated with such designs, modelbased control design methods are increasingly adapted in industry. Despite Modelica’s obvious suitability to
efficiently create appropriate high fidelity system models, the utilization of Modelica for developing discrete control functions is not yet wide spread. Adoption of Modelica for this task offers the potential for a seamless development methodology from the logical virtual model down to the technical system architecture, with corresponding traceability and maintainability benefits.
This contribution will specifically address this potential and propose a Modelica sub- and superset adequate for use within the development of safety-relevant control applications.
This work gives an introduction into possible tool qualification approaches, and then proposes a generic approach to tool qualification using a Tool Validation Suite Approach. Here “tool” is usually used in the sense of “integrated code generator tool with target compiler“. Central to the Validation Suite Approach is the use of an Automated Test Environment with capability of automatic execution of large numbers of test cases. The presentation also provides the results of an effort to systematically gather and structure all relevant requirements on a Validation Suite from existing and upcoming standards in a generic Validation Suite Requirement Catalogue ([5], attached after this article). The presentation provides examples of the various requirements and different requirement classes and explains the role of the requirement catalogue in the Validation Suite approach. Further the contribution presents the steps according to this Validation Suite Approach to tool qualification which will lead to tool qualification and if desired certification. It outlines how assessment of a specific tool validation suite against the requirements may progress. The remainder of the presentation describes the role of validation suite operation and maintenance activities and re-qualification of tools which have been previously qualified, and gives experience and status of the currentwork. The presentation is outlined in the following sections. The topics covered in this paper include • Description of validation suite approach • Goals • Benefits of approach, • Issues to solve • Elements of validation suite • Role of test environment