About Dymola Behavior Modeling

The Dymola Behavior Modeling app is used to create and manage dynamic functional and logical behaviors, models, and dynamic behavior libraries.

This page discusses:

Access

You can access a behavior representation through two contexts:

  • From the Functional & Logical Design app.
  • By opening or creating a behavior representation or behavior library.

In both cases, the behavior representation is edited with the Dymola Behavior Modeling app.

See Entering the Dymola Behavior Modeling App.

Behavior Representation

The behavior representation describes, in a formal language, the execution of a function or logical component.

A behavior content is stored:

  • in a behavior library: such behavior content can be reused in any behavior library or functional or logical behavior.

    See the Working with Behavior Libraries section.

  • in a functional or logical behavior: aggregated to a functional or logical component in the Functional & Logical Design app.

    See the Working with Behaviors section.

Behavior Diagram

A behavior is represented by a diagram showing the components, their ports, and the relations between them. These components are edited through the diagram layer, the browsers, and editors.

Each component (representing the instantiation of a Modelica class) constituting the diagram have variables or parameters in their description that position and dimension it on the diagram layer.

Modelica Classes

Modelica is the language used to define dynamic behaviors. In the Modelica language, the basic structuring element is called a class.

See the Managing Classes chapter.

Components and Connectors

Classes are instantiated to create components. Components appear in the Component Browser.

See the Managing Components chapter.

Modelica Language

Modelica is an object-oriented modeling language for the modeling of large, complex, and heterogeneous physical systems. It is suited for multidomain modeling, for example for the modeling of mechatronics systems within automotive, aerospace and robotics applications. Such systems are composed of mechanical, electrical, and hydraulic subsystems, as well as control systems.

General equations are used for modeling of the physical phenomena. The language has been designed to allow tools to generate efficient code automatically. The modeling effort is thus reduced since model components can be reused, and tedious and error-prone manual manipulations are not needed.

The development and promotion of Modelica is organized by the nonprofit Modelica Association. Modelica language specifications, free Modelica libraries, and Modelica simulation tools are available on their website www.modelica.org.

Export of Behaviors to 3D XML

You can export references containing behaviors in a 3D XML format.

Exportable Behaviors

You can export to 3D XML the following references containing behaviors:

  • Functional references with dynamic behaviors
  • Logical references with dynamic behaviors
  • Dynamic behavior libraries.

Important:
  • These references are exported in a "With Authoring Data" mode (the "For Review" mode is not available).
  • You can export behavior references (with all their representations), but you cannot export their representations alone.

For general information about exporting, see

  • (for export to 3D XML): 3DEXPERIENCE Native Apps: Native Apps Common Services: Importing and Exporting: Exporting Data to 3D XML: Exporting Data to 3D XML Files
  • (for export to other formats): 3DEXPERIENCE Native Apps: Native Apps Common Services: Importing and Exporting: Exporting Objects to Other Formats.

Exported Content

When exporting a behavior reference, you export:

  • its dynamic components
  • instantiated components (from other behavior libraries)
  • behavior libraries containing the instantiated components.