DOCSLIB.ORG

Translating Simulink Models to Modelica Using the Nsp Platform

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Translating Simulink Models to Modelica Using the Nsp Platform Translating Simulink Models to Modelica using the {\NSP} Platform TranslatingTranslating Simulink Simulink Models Models to Modelica to Modelicausing the {\NSP} using Platform the Nsp Platform Chancelier, Jean-Philippe and Furic, Sébastien and Weis, Pierre 1 2 2 841 Jean-Philippe Chancelier Sébastien Furic Pierre Weis 1Université Paris-Est, CERMICS (ENPC), 77455 Marne-la-Vallée 2, France, [email protected] 2 Inria Paris, 2 rue Simone Iff, 75589 Paris, France & Université Paris-Est, CERMICS (ENPC), 77455 Marne-la-Vallée 2, France {sebastien.furic,pierre.weis}@inria.fr Abstract blocks. Up to our knowledge this work remains the most advanced effort in that direction. It is however no We present a new Simulink (Simulink) to Modelica (Mod- longer maintained. In the Scicos software environment, elica) translation chain embedded into Nsp. Translated the Coselica library offers signal models to allow users models can be edited (original Simulink diagrams are pre- to better exploit Modelica from within Scicos by propos- served through translation) and simulated. This transla- ing a large set of Modelica submodels in the same spirit as tion chain makes use of the Simport tool, originally de- the standard Modelica library (MSL). Many Simulink-like signed to translate Simulink models to Scicos models, and blocks are also available in Coselica. also relies on Modelicac, i.e. Scicos’ Modelica companion The approach presented here differs from Mike compiler. Dempsey’s and Dirk Reusch’s approaches in that trans- Using some examples, we demonstrate the effective- lation of original blocks is not attempted on a one-to-one ness of the translation process and detail some techni- basis. Instead, we use a two steps translation process: the cal aspects of it. This new Nsp feature extends Nsp’s first step translates the Simulink model into an equivalent simulation capabilities and makes it a reference platform Scicos native model; the second step translates the Scicos for users looking for means to simulate Simulink models native model to Modelica code. within a Modelica framework. Resulting Modelica code To handle the initial Simulink to Scicos translation, can even be exported to other Modelica compatible tools. we use an external tool named Simport: it translates a Keywords: Nsp; Simulink; Modelica Simulink model by translating each block in the original Simulink model with one or several blocks of the Scicos 1 Introduction native block library, so that original semantics is preserved Nsp is a Matlab-like numerical environment which can run with a high degree of confidence. the Scicos modeling environment, a Simulink-like block For the second step, we developed a set of Nsp special diagram editor and simulator. purpose compilation routines to translate Scicos blocks to From 2003 to 2008, in the course of funded projects genuine Modelica blocks. When a Scicos block has a di- SimPA and SimPA2, a Modelica compiler named Modeli- rect Coselica equivalent, the compilation routine simply cac has been developed allowing Scicos to handle genuine emits thre corresponding Coselica block; when there is Modelica models. This integration of Modelica within no Coselica equivalent, the compilation routine generates Scicos has been the subject of several papers published an entirely new block containing ad-hoc Modelica code at the Modelica conference (Nikoukhah and Najafi, 2008; to handle the Scicos block behavior. Using this compile- Nikoukhah and Furic, 2009). The purpose of using Mod- time Modelica code generation and the two steps transla- elica is to serve as a high-level description language to tion process was the key ideas to fill the huge semantic gap extend Scicos expressiveness: Modelica allows users to between Simulink and Modelica. compose “acausal” models where the original environ- We give in this paper a detailed description of this new ment forced users to describe their models as block dia- translation chain hosted by the Nsp environment. grams. 2 Involved Tools In this paper we focus on a new application of Modelica within Scicos under Nsp, that is as a target language for As mentioned above, the translation chain relies on a com- Simulink model translation. bination of several tools. We give hereafter a short de- Several Simulink to Modelica translation tools have al- scription of each of them. ready been proposed in the past, we mention in partic- 2.1 Nsp, a Programming Environment for Nu- ular Mike Dempsey’s Simelica and AdvancedBlocks li- brary (Dempsey, 2003) and Dirk Reusch’s Coselica ini- merical Applications tiative (Reusch). AdvancedBlocks was a fairly complete Nsp (Nsp) is a mature Matlab-like Scientific Software library of Modelica blocks which allowed users to use Package developed under the GPL license. Nsp features Modelica blocks as a one-to-one replacement for Simulink a high-level, safe imperative programming language with DOI Proceedings of the 13th International Modelica Conference 841 10.3384/ecp19157841 March 4-6, 2019, Regensburg, Germany Translating Simulink Models to Modelica using the {\NSP} Platform automatic memory management. This language can be produces a Scicos model data structure. Second, using used interactively, giving users an easy access to efficient Nsp scripts we are able to convert, in a Scicos model data numerical routines; It can also be used as a more conven- structure, some Scicos blocks to Modelica blocks. tional programming language to extend Nsp’s capabilities. In the conversion process from Simulink to Modelica, Nsp contains internally a class system with simple in- the scicos compiler/scheduler also plays a key role. It heritance and interface implementation. When used as an infers dimensions and types used in the Modelica blocs. interactive computing environment, it comes with online This is quite an exciting feature since it gives the possibil- help facilities and an easy access to GUI facilities and ity to have Modelica blocks for which the associated Mod- graphics. elica model is not a fixed Modelica class but a specific one A large set of libraries are available and it is moreover adapted to specific dimensions and types generated on the easy to implement new functionalities. External libraries fly. can also be used: this requires writing some wrapper code (also called interface) to live in harmony with Nsp’s inter- 2.3 Modelicac, a Simple Yet Useful Modelica nal state. The interface mechanism can be either static or Compiler dynamic. By using dynamic functionalities one is able to Development of Modelicac started in 2003 as a joint work build toolboxes. between Inria and TNI-Valiosys (now Dassault Systèmes) Nsp shares many traits with other Matlab-like Scientific in the course of the SimPA (SIMulation pour le Procédé Softwares such as Matlab, Octave, ScilabGtk (ScilabGtk; et l’Automatique) french funded project. The goal was to Campbell et al., 2006), and also with scripting languages make Scicos compatible with a significant subset of the such as Python. Modelica language in order for users to be able to de- The main toolbox used in this work is Scicos that we scribe complex hybrid models without having to resort to describe now. low-level block diagram descriptions. Indeed, building a 2.2 Scicos, a Block Diagram Modeler and Sim- block diagram from a physical model requires 1)perform- ing a complete analysis of physical phenomena into play ulator (to determine which elementary blocks to use in the dia- Scicos (Scicos) is a graphical dynamical system modeler gram), and 2)determining how data flows between blocks and simulator originally developed in the Metalau project (to connect elementary blocks together). On the other at INRIA, Paris-Rocquencourt center. With Scicos, users hand, Modelica tools considerably ease physical model can create block diagrams to model and simulate the dy- construction by automatically analysing the overall struc- namics of hybrid dynamical systems and compile models ture of physical models described in a much more user- into executable code. Scicos is used for signal process- friendly way: familiar physical components (e.g. springs, ing, systems control, queuing systems, and to study phys- transistors, hydraulic pumps, etc.) can be used to build ical and biological systems. Extensions allow generation models. Translation from this high-level description to of component-based modeling of electrical and hydraulic low-level data flow is performed automatically in a quite circuits using the Modelica language. satisfactory way, which frees users from a painful work. We consider in this paper the Scicos/Nsp version of Sci- Moreover, even slight modifications of physical models cos maintained and developed at ENPC. Scicos/Nsp is a may require considerable changes in corresponding block- Nsp toolbox and runs in the Nsp environment. Having ac- diagram descriptions; this is not the case with a high-level cess to Nsp functions when designing simulation models description. is of great importance. In its initial version, Modelicac essentially focussed on Scicos users often needs to use Nsp functions such as the “continuous part” of hybrid models. This mainly com- those dedicated to filter design for signal processing or prises differential equations and event-trigerring mecha- controller design in the construction of simulation mod- nisms (e.g. , “when equations”). Difference equations els. Nsp’s programming language can be used for batch were however also be described, although with many re- processing of multiple simulation tasks, and more gener- strictions, because the idea was to discourage users from ally, models designed by Scicos can be used as functions writing discrete equations in Modelica. Indeed, Scicos is in Nsp. Nsp’s graphical facilities can be used for post pro- primarily a hybrid modelling environment and, in particu- cessing simulation results. But the integration of Scicos lar, it handles discrete, event-trigered changes, much more and Nsp goes beyond that. The Scicos editor is entirely robustly than Modelica because of its synchronous roots. written in Nsp’s language.
Load more

Recommended publications
  • Applying Reinforcement Learning to Modelica Models
    ModelicaGym: Applying Reinforcement Learning to Modelica Models Oleh Lukianykhin∗ Tetiana Bogodorova [email protected] [email protected] The Machine Learning Lab, Ukrainian Catholic University Lviv, Ukraine Figure 1: A high-level overview of a considered pipeline and place of the presented toolbox in it. ABSTRACT CCS CONCEPTS This paper presents ModelicaGym toolbox that was developed • Theory of computation → Reinforcement learning; • Soft- to employ Reinforcement Learning (RL) for solving optimization ware and its engineering → Integration frameworks; System and control tasks in Modelica models. The developed tool allows modeling languages; • Computing methodologies → Model de- connecting models using Functional Mock-up Interface (FMI) to velopment and analysis. OpenAI Gym toolkit in order to exploit Modelica equation-based modeling and co-simulation together with RL algorithms as a func- KEYWORDS tionality of the tools correspondingly. Thus, ModelicaGym facilit- Cart Pole, FMI, JModelica.org, Modelica, model integration, Open ates fast and convenient development of RL algorithms and their AI Gym, OpenModelica, Python, reinforcement learning comparison when solving optimal control problem for Modelica dynamic models. Inheritance structure of ModelicaGym toolbox’s ACM Reference Format: Oleh Lukianykhin and Tetiana Bogodorova. 2019. ModelicaGym: Applying classes and the implemented methods are discussed in details. The Reinforcement Learning to Modelica Models. In EOOLT 2019: 9th Interna- toolbox functionality validation is performed on Cart-Pole balan- tional Workshop on Equation-Based Object-Oriented Modeling Languages and arXiv:1909.08604v1 [cs.SE] 18 Sep 2019 cing problem. This includes physical system model description and Tools, November 04–05, 2019, Berlin, DE. ACM, New York, NY, USA, 10 pages. its integration using the toolbox, experiments on selection and in- https://doi.org/10.1145/nnnnnnn.nnnnnnn fluence of the model parameters (i.e.
    [Show full text]
  • Reusing Static Analysis Across Di Erent Domain-Specific Languages
    Reusing Static Analysis across Dierent Domain-Specific Languages using Reference Attribute Grammars Johannes Meya, Thomas Kühnb, René Schönea, and Uwe Aßmanna a Technische Universität Dresden, Germany b Karlsruhe Institute of Technology, Germany Abstract Context: Domain-specific languages (DSLs) enable domain experts to specify tasks and problems themselves, while enabling static analysis to elucidate issues in the modelled domain early. Although language work- benches have simplified the design of DSLs and extensions to general purpose languages, static analyses must still be implemented manually. Inquiry: Moreover, static analyses, e.g., complexity metrics, dependency analysis, and declaration-use analy- sis, are usually domain-dependent and cannot be easily reused. Therefore, transferring existing static analyses to another DSL incurs a huge implementation overhead. However, this overhead is not always intrinsically necessary: in many cases, while the concepts of the DSL on which a static analysis is performed are domain- specific, the underlying algorithm employed in the analysis is actually domain-independent and thus can be reused in principle, depending on how it is specified. While current approaches either implement static anal- yses internally or with an external Visitor, the implementation is tied to the language’s grammar and cannot be reused easily. Thus far, a commonly used approach that achieves reusable static analysis relies on the trans- formation into an intermediate representation upon which the analysis is performed. This, however, entails a considerable additional implementation effort. Approach: To remedy this, it has been proposed to map the necessary domain-specific concepts to the algo- rithm’s domain-independent data structures, yet without a practical implementation and the demonstration of reuse.
    [Show full text]
  • Introduction to Dymola
    DYMOLA AND MODELICA Course overview DAY 1 Dymola and Modelica I • Introduction Dymola, Modelica, Modelon • Lecture 1 Overview of Dymola and Physical modeling . Workshop 1 Workflow of modeling physical systems in Dymola • Lecture 2 Simulation and post-processing with Dymola . Workshop 2 Simulating and analyzing a physical system • Lecture 3 Configure system models . Workshop 3 Creating a reconfigurable system DAY 2 Dymola and Modelica I • Lecture 4 Modelica I – Writing Modelica models . Workshop 4a Cauer low pass filter using Electric Library . Workshop 4b A moving coil using Magnetic, Electric and Translational mechanics libraries . Workshop 4c Temperature control using Heat transfer Library • Lecture 5 Understanding equation-based modeling . Workshop 5 Defining boundary conditions • Lecture 6 Trouble shooting and common pitfalls . Workshop 6 Common pitfalls DAY 3 Dymola and Modelica II • Lecture 7 Modelica II – Advanced features . Workshop 7 Implementing a solar collector • Lecture 8 Working with the Modelica Standard Library . Workshop 8a Lamp logic using StateGraph II . Workshop 8b Suspension linkage using MultiBody mechanics • Lecture 9 Hybrid modeling . Workshop 9a Hybrid examples . Workshop 9b Hammer impact model . Workshop 9c Designing a thermostat valve DAY 4 Dymola and Modelica II • Lecture 10 Efficient and reconfigurable modeling . Workshop 10 Creating a system architecture based on templates and interfaces • Lecture 11 Model variants and data management . Workshop 11 Creating a data architecture and adaptive parameter interfaces • Lecture 12 FMI technology . Workshop 12a Import and Export FMUs in Dymola . Workshop 12b FMI with Excel . Workshop 12c FMI with Simulink DAY 5 Dymola and Modelica II • Lecture 13 Workflow automation and scripting . Workshop 13 Automated sensitivity analysis • Lecture 14 Dymola code with other tools .
    [Show full text]
  • Automated Annotation of Simulink Generated C Code Based on the Simulink Model
    DEGREE PROJECT IN COMPUTER SCIENCE AND ENGINEERING, SECOND CYCLE, 30 CREDITS STOCKHOLM, SWEDEN 2020 Automated Annotation of Simulink Generated C Code Based on the Simulink Model SREEYA BASU ROY KTH ROYAL INSTITUTE OF TECHNOLOGY SCHOOL OF ELECTRICAL ENGINEERING AND COMPUTER SCIENCE Automated Annotation of Simulink Generated C Code Based on the Simulink Model SREEYA BASU ROY Master in Embedded Systems Date: September 25, 2020 Supervisor: Predrag Filipovikj Examiner: Matthias Becker School of Electrical Engineering and Computer Science Host company: Scania CV AB Swedish title: Automatisk Kommentar av Simulink Genererad C kod Baserad på Simulink Modellen iii Abstract There has been a wave of transformation in the automotive industry in recent years, with most vehicular functions being controlled electron- ically instead of mechanically. This has led to an exponential increase in the complexity of software functions in vehicles, making it essential for manufactures to guarantee their correctness. Traditional software testing is reaching its limits, consequently pushing the automotive in- dustry to explore other forms of quality assurance. One such technique that has been gaining momentum over the years is a set of verification techniques based on mathematical logic called formal verification tech- niques. Although formal techniques have not yet been adopted on a large scale, these methods offer systematic and possibly more exhaus- tive verification of the software under test, since their fundamentals are based on the principles of mathematics. In order to be able to apply formal verification, the system under test must be transformed into a formal model, and a set of proper- ties over such models, which can then be verified using some of the well-established formal verification techniques, such as model check- ing or deductive verification.
    [Show full text]
  • Lecture #4: Simulation of Hybrid Systems
    Embedded Control Systems Lecture 4 – Spring 2018 Knut Åkesson Modelling of Physcial Systems Model knowledge is stored in books and human minds which computers cannot access “The change of motion is proportional to the motive force impressed “ – Newton Newtons second law of motion: F=m*a Slide from: Open Source Modelica Consortium, Copyright © Equation Based Modelling • Equations were used in the third millennium B.C. • Equality sign was introduced by Robert Recorde in 1557 Newton still wrote text (Principia, vol. 1, 1686) “The change of motion is proportional to the motive force impressed ” Programming languages usually do not allow equations! Slide from: Open Source Modelica Consortium, Copyright © Languages for Equation-based Modelling of Physcial Systems Two widely used tools/languages based on the same ideas Modelica + Open standard + Supported by many different vendors, including open source implementations + Many existing libraries + A plant model in Modelica can be imported into Simulink - Matlab is often used for the control design History: The Modelica design effort was initiated in September 1996 by Hilding Elmqvist from Lund, Sweden. Simscape + Easy integration in the Mathworks tool chain (Simulink/Stateflow/Simscape) - Closed implementation What is Modelica A language for modeling of complex cyber-physical systems • Robotics • Automotive • Aircrafts • Satellites • Power plants • Systems biology Slide from: Open Source Modelica Consortium, Copyright © What is Modelica A language for modeling of complex cyber-physical systems
    [Show full text]
  • Introduction to Simulink
    Introduction to Simulink Mariusz Janiak p. 331 C-3, 71 320 26 44 c 2015 Mariusz Janiak All Rights Reserved Contents 1 Introduction 2 Essentials 3 Continuous systems 4 Hardware-in-the-Loop (HIL) Simulation Introduction Simulink is a block diagram environment for multidomain simulation and Model-Based Design. It supports simulation, automatic code generation, and continuous test and verification of embedded systems.1 Graphical editor Customizable block libraries Solvers for modeling and simulating dynamic systems Integrated with Matlab Web page www.mathworks.com 1 The MathWorks, Inc. Introduction Simulink capabilities Building the model (hierarchical subsystems) Simulating the model Analyzing simulation results Managing projects Connecting to hardware Introduction Alternatives to Simulink Xcos (www.scilab.org/en/scilab/features/xcos) OpenModelica (www.openmodelica.org) MapleSim (www.maplesoft.com/products/maplesim) Wolfram SystemModeler (www.wolfram.com/system-modeler) Introduction Model based design with Simulink Modeling and simulation Multidomain dynamic systems Nonlinear systems Continuous-, Discrete-time, Multi-rate systems Plant and controller design Rapidly model what-if scenarios Communicate design ideas Select/Optimize control architecture and parameters Implementation Automatic code generation Rapid prototyping for HIL, SIL Verification and validation Essentials Working with Simulink Launching Simulink Library Browser Finding Blocks Getting Help Context sensitive help Simulink documentation Demo Working with a simple model Changing
    [Show full text]
  • FMI Target for Simulink Coder, It Is Now Possible to Export Models from Simulink to Any Platform That Supports Fmus for Co-Simulation
    Supporting your vision Cross-Platform Modeling with FMI Target for Simulink® Coder™ Open technology standards for an integrated product lifecycle Engine Transmission Thermal EV/HV Chassis Compo- Models Models Systems Models nents Models Functional Mock-Up Interface The challenge for manufacturers of complex machinery that heavily rely on components from suppliers is the seamless exchange of data and specifications during the development. The same holds true for large corporates with multiple R&D departments at various locations using several development tools due to different objectives. Those challenges include different programming languages from the various tools, the lack of standardized model interfaces and the concerns for the protection of intellectual property. The development of the Functional Mock-up Interface (FMI) has enabled software-, model- and hardware-in-the-loop simulations with dynamic system models from different software environments. With the FMI Target for Simulink Coder, it is now possible to export models from Simulink to any platform that supports FMUs for Co-Simulation. FMI for Co-Simulation The goal is to couple two or more models with solvers in a co-simulation environment. The data exchange between subsystems is restricted to discrete communication points. The subsystems are processed independently from each other by their individual solvers during the time interval between two communication points. Master algorithms control the synchronization of all slave simulation solvers and the data exchange between the subsystems. The interface allows for both standard and advanced master algorithms, such as variable communication step sizes, signal extrapolation of higher order and error checking. FMI Target for Simulink® Coder™ FMI for Co-Simulation For the exchange of models across different platforms, the FMI Target for Simulink Coder enables the export of models from Simulink as FMUs for Co-Simulation.
    [Show full text]
  • Making Simulink Models Robust with Respect to Change Making Simulink Models Robust with Respect to Change
    Making Simulink Models Robust with Respect to Change Making Simulink Models Robust with Respect to Change By Monika Jaskolka, B.Co.Sc., M.A.Sc. a thesis submitted to the Department of Computing and Software and the School of Graduate Studies of McMaster University in partial fulfillment of the requirements for the degree of Doctor of Philosophy Doctor of Philosophy (December 2020) McMaster University (Software Engineering) Hamilton, ON, Canada Title: Making Simulink Models Robust with Respect to Change Author: Monika Jaskolka B.Co.Sc. (Laurentian University) M.A.Sc. (McMaster University) Supervisors: Dr. Mark Lawford, Dr. Alan Wassyng Number of Pages: xi, 206 ii For my husband, Jason iii Abstract Model-Based Development (MBD) is an approach that uses software models to describe the behaviour of embedded software and cyber-physical systems. MBD has become an increasingly prevalent paradigm, with Simulink by MathWorks being the most widely used MBD platform for control software. Unlike textual programming languages, visual languages for MBD such as Simulink use block diagrams as their syntax. Thus, some software engineering principles created for textual languages are not easily adapted to this graphical notation or have not yet been supported. A software engineering principle that is not readily supported in Simulink is the modularization of systems using information hiding. As with all software artifacts, Simulink models must be constantly maintained and are subject to evolution over their lifetime. This principle hides likely changes, thus enabling the design to be robust with respect to future changes. In this thesis, we perform repository mining on an industry change management system of Simulink models to understand how they are likely to change.
    [Show full text]
  • Modeling and Simulation in Scilab/Scicos Mathematics Subject Classification (2000): 01-01, 04-01, 11 Axx, 26-01
    Stephen L. Campbell, Jean-Philippe Chancelier and Ramine Nikoukhah Modeling and Simulation in Scilab/Scicos Mathematics Subject Classification (2000): 01-01, 04-01, 11 Axx, 26-01 Library of Congress Control Number: 2005930797 ISBN-10: 0-387-27802-8 ISBN-13: 978-0387278025 Printed on acid-free paper. © 2006 Springer Science + Business Media, Inc. All rights reserved. This work may not be translated or copied in whole or in part without the written permission of the publisher (Springer Science+Business Media, Inc., 233 Spring Street, New York, NY 10013, USA), except for brief excerpts in connection with reviews or scholarly analysis. Use in connection with any form of information storage and retrieval, electronic adaption, computer software, or by similar or dissimilar methodology now known or hereafter developed is forbidden. The use in this publication of trade names, trademarks, service marks, and similar terms, even if they are not identified as such, is not to be taken as an expression of opinion as to whether or not they are subject to proprietary rights. Printed in the United States of America. (BPR/HAM) 9 8 7 6 5 4 3 2 1 springeronline.com Preface Scilab (http://www.scilab.org) is a free open-source software package for scientific com- putation. It includes hundreds of general purpose and specialized functions for numerical computation, organized in libraries called toolboxes that cover such areas as simulation, optimization, systems and control, and signal processing. These functions reduce consid- erably the burden of programming for scientific applications. One important Scilab toolbox is Scicos. Scicos (http://www.scicos.org) provides a block-diagram graphical editor for the construction and simulation of dynamical sys- tems.
    [Show full text]
  • A Modelica Power System Library for Phasor Time-Domain Simulation
    2013 4th IEEE PES Innovative Smart Grid Technologies Europe (ISGT Europe), October 6-9, Copenhagen 1 A Modelica Power System Library for Phasor Time-Domain Simulation T. Bogodorova, Student Member, IEEE, M. Sabate, G. Leon,´ L. Vanfretti, Member, IEEE, M. Halat, J. B. Heyberger, and P. Panciatici, Member, IEEE Abstract— Power system phasor time-domain simulation is the FMI Toolbox; while for Mathematica, SystemModeler often carried out through domain specific tools such as Eurostag, links Modelica models directly with the computation kernel. PSS/E, and others. While these tools are efficient, their individual The aims of this article is to demonstrate the value of sub-component models and solvers cannot be accessed by the users for modification. One of the main goals of the FP7 iTesla Modelica as a convenient language for modeling of complex project [1] is to perform model validation, for which, a modelling physical systems containing electric power subcomponents, and simulation environment that provides model transparency to show results of software-to-software validations in order and extensibility is necessary. 1 To this end, a power system to demonstrate the capability of Modelica for supporting library has been built using the Modelica language. This article phasor time-domain power system models, and to illustrate describes the Power Systems library, and the software-to-software validation carried out for the implemented component as well as how power system Modelica models can be shared across the validation of small-scale power system models constructed different simulation platforms. In addition, several aspects of using different library components. Simulations from the Mo- using Modelica for simulation of complex power systems are delica models are compared with their Eurostag equivalents.
    [Show full text]
  • OMG Sysphs: Integrating Sysml, Simulink, Modelica And
    OMG SysPhs: Integrating SysML, Simulink, Modelica and FMI | ref.: 3DS_Document_2015 | ref.: 2/13/20 | Confidential Information | Information | Confidential Nerijus Jankevicius Systèmes CATIA | No Magic Dassault © INCOSE IW, Torrance, Jan 27, 2020 3DS.COM System Model as an Integration Framework © 2012-2014 by Sanford Friedenthal SysML as co-simulation environment 35 Reduce and standardize mappings 4 Unified Physics Domain Flowing Substance Flow rate Potential to flow Electrical Charge Current Voltage Hydraulic Volume Volumetric flow rate Pressure Rotational Angular momentum Torque Angular velocity Translational Linear momentum Force Velocity Thermal Entropy Entropy flow Temperature flow rate = amount of substance/time flow rate * potential = energy / time = power The Standard : SysPhs •SysPhS - https://www.omg.org/spec/SysPhS/1.0 • SysML Mapping to SiMulink and Modelica • SysPhS profile • SysPhS library Simulation profile Modelica vs Simulink • Modelica • SiMulink • Language is better suited for physical • Language is well-suited for control modeling (plant) algorithMs • Object oriented approach for • TransforMational seMantics of signals modeling physical and signal processing coMponents (Mechanical, electrical, etc.) • Causal seMantics (inputs -> outputs) • Causal and A-Causal seMantics • Well integrated into the “MATLAB (equations) universe” • Open standard (of the textual • Widely used in industry (standard de- language) facto) • Multi tool support (although DyMola • Many existing tool integrations is doMinant) • Code generation to
    [Show full text]
  • TPT Tutorial
    Time Partition Testing Systematic automated testing of embedded systems PikeTec GmbH, http://www.piketec.com There are only a few tools for testing embedded systems in the automotive domain. Their function usually lies in the test-management or automation of tests by means of test scripts. Time Partition Testing (TPT) noticeably exceeds this. It combines a systematic and very graphic modelling technique for test cases with a fully automatic test execution in different environments and automatic test evaluation in a unique way. In doing so, TPT even supports testing of control systems. Time Partition Testing (TPT) was developed to graphically and compactly model tests of embedded systems – especially those with continuous behaviour –, to automate those tests and to offer a systematic that supports the tester in selecting an ideal amount of test cases. The intuitive graphic modelling technique for test cases, the mechanisms for the structuring of complex test problems, the simple integration in any test- bench and a number of additional interesting features makes TPT a unique test solution. All this has contributed to TPT becoming the central testing tool in a large number of development projects at car manufacturers and suppliers and has become an integral part of the process chain. Embedded systems TPT is specialized on testing embedded systems whose inputs and outputs can be represented as signals. Most control systems belong to this system class. The implementation language of the embedded system (e.g. ‘C’ code, C++, MATLAB/Simulink/Stateflow, Statemate or a combination of multiple languages) is irrelevant for TPT. TPT does not require a particular implementation language.
    [Show full text]