Component orientated modelling provides a convienent method of clicking on components to bring up a dialog of parameters to control that components behaviour. As model size and component count increases however, it is often more desirable to collate information from several different places so that data can be controlled...
Archive for category: Concepts and methods
This is a glossary of terms used when talking about Dymola and Modelica. Class All of the following are defined as a Modelica Class: Record – used to define data structures Block – fixed causality normally used within control systems Types – can be used to extend built-in types....
Component and system models can be defined once and then reused for different types of analysis. This is achieved by simply changing the boundary conditions that we impose on the model. Symbolic manipulation automatically rearranges the model equations. The example below illustrates how a hybrid powertrain model can be...
The possibilities for model reuse extend beyond running time domain simulations. It is possible to reuse models so that they can derive component parameters or the required control inputs to meet the targets set for the overall system. The example model below is able to determine the torque converter...
Looking for something?
- Rationalisation of Bus and Sub-bus signals in the Engines library 10th August 2018
- LCV2018 – 12th & 13th September, Millbrook Proving Ground 6th August 2018
- Using External Data Sources in Your Dymola Model via ExternData 3rd August 2018
- Introduction of new engine modelling features for real time applications and controller design 30th July 2018
- CIOReview Present 10 Most Promising Dassault Systèmes Solution Providers – 2018 24th July 2018
- Decouple blocks and model parallelisation 20th July 2018
- Output Data Organization – Part 2 13th July 2018
- Modifications introduced in Modelica 3.4 9th July 2018