Yes, that's one of the main points of using Modelica, that you can create parts and connect them together. There's already a big standard library available that contains all the parts you list, see the Modelica library in OMEdit.

perost wrote:

Yes, that's one of the main points of using Modelica, that you can create parts and connect them together. There's already a big standard library available that contains all the parts you list, see the Modelica library in OMEdit.

Thank you for your answer.

Is it better to learn codeing or the "drag and drop"-method?

Hello!

Your issue seems to have some relation to the difficulties I am experiencing as a new modelica user.

A lot of examples within the OMNotebook has you create a class to model whatever situation you're dealing with, then create more classes that are needed for further iterations. I found that you cannot "lump" in all of the classes together within the "Text View" of the OMEdit interface, but have to create different classes and keep them separate in different models located underneath the modelica libraries menu. I'd love to hear your input on this.

Also, the I believe it's more useful learning the coding back end of the software. Most of the tutorials from the OMNotebook and external sources give practice via coding, not "drag and dropping".

Hope this helps, let me know what you think.