Modelica

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

NewtonCoolingWithBlocks

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Block Diagram Components - S0 - DISO

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Block Diagram Components - SO - SISO

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

SysPhS vs Modelica: If you redeclare a PhSConstant (Modelica parameter) as a PhSVariable (Modelica variable) Modelica still treats it as a 'parameter'. You can end up with an unbalanced system with one equation too many!

ThirdSpeciesWolf

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

The targeting of the Modelica and Simulink simulation language families by the SysML Extension for Physical Interaction and Signal Flow Simulation (SysPhS) encourages development of SysML models aligned with known practices for a wide class of problems!

FoxRabbitWithInit

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Interaction - Predation

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

SinkOrSource - Reproduction - Starvation

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

SysPhS-1.1: Does not support Modelica's encapsulated enumeration.

Lotka-Volterra Equations Revisited - RegionalPopulation

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Lotka-Volterra Equations Revisited - FlowingSpecies

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

SysPhS-1.1: Does not support Modelica's conditional declaration form.

UngroundedGearComparison - comparison

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

GroundedGear - comparison

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

SMD_WithBacklash

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

SMD

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Compliant - RotationalInertia - Spring - Damper - Ground

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Basic Rotational Components - TwoFlange

Gallery

Tutorial

Section

Slide kind

This is why we want to work with across variables that have not been overly differentiated.

Source

An essential point here is that differentiation is lossy. If we know position, we can easily express velocity. But if we only know velocity, we cannot compute position without knowing an additional integration constant.

Source

If we had chosen velocity (the derivative of position with respect to time), then we would have been in the awkward situation of trying to describe the behavior of a spring in terms of velocities, not positions.

Source

So, for example, we chose position for translational motion because position is used in describing the behavior of a spring (i.e., Hooke’s law).

Source

The second constraint is that the across variable should be the lowest order derivative to appear in any of our constitutive or empirical equations in the domain.

Source

The reason for this constraint is that the through variable will be used to formulate generalized conservation equations in our system. As such, it is essential that the through variables be conserved quantities.

Source

The first constraint is that the through variable should be the time derivative of some conserved quantity.

Source

You may have seen a similar table before with slightly different choices. For example, you will sometimes see velocity (in ) chosen as the across variable for translational motion. The choices above are guided by two constraints.

Source

The following table covers four different engineering domains. In each domain, we see the choice of through and across variables that we will be using along with the SI units for those quantities.

Source

In this section, we’ll discuss relatively simple engineering domains. These are ones where a connector deals with only one through and one across variable. Conceptually, this means that only one conserved quantity is involved with that connector.

Source

As we will see in many of the examples to come, there are many different types of relationships between the through and across variables (Ohm’s law being just one of many).

Source

These flows are usually the result of some difference in the across variables across a component model. For example, current flowing through a resistor is in response to a voltage difference across the two sides of the resistor.

Source

The second class of variables we will discuss are “through” variables (also called flow variables). Flow variables normally represent the flow of some conserved quantity like mass, momentum, energy, charge, etc.

Source

Typical examples of across variables, that we will be discussing shortly, are temperature, voltage and pressure. Differences in these quantities typically lead to dynamic behavior in the system.

Source

The first class of variables we will discuss are “across” variables (also called potential or effort variables). Differences in the values of across variables across a component are what trigger components to react.

Source

In order to understand one specific class of connector semantics, it is first necessary to understand a bit more about acausal formulations of physical systems. An acausal approach to physical modeling identifies two distinct classes of variables.

Source

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

TwoPin - SwitchedRLC

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Resistor - Capacitor - Inductor - StepVoltage - Ground

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Electrical Components - TwoPin

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

AmbientConvectionCapacitance (combined)

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Cooling

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

AmbientCondition

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

MagicDraw/Cameo v19SP3: vs SysPhS-1.1: Modelica export: Direct binding from a PhSVariable value property within a FlowProperty of a Port to an inner value property does not flatten. WORKAROUND: Use an intermediate constraint property.

Convection

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

CoolingToAmbient

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

ThermalCapacitance - Adiabatic

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Thermal Connectors

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Graphical Connectors

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

SysML vs Modelica: GOTCHA: Terminology: A 'connector' in Modelica is equivalent to the Type of a Port in SysML. A Connector in SysML-1.x is equivalent to a 'connect(source,target)' in Modelica.

Block Connectors

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Fluid Connectors - ThermoFluid

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Fluid Connectors - Compressible

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

MagicDraw/Cameo: Modelica export: Need environment option to disable generation of layout annotations (not just on individual export dialog)

Fluid Connectors - Incompressible

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

SimpleDomains - Thermal

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

SimpleDomains - Rotational

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

SimpleDomains - Translational

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

SimpleDomains - Electrical

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Hysteresis - ChatteringControl

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

MagicDraw/Cameo v19SP3+SysPhS-1.1: On export to Modelica sometimes repeats parts of an equation into an extending model.

Speed Measurement - SampleAndHold

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Switched RLC Circuit - SwitchedRLC

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

MagicDraw/Cameo v19SP3+SysPhS-1.1: Does not cleanly export INLINE Modelica 'if/then/else' statements (a.k.a. "switching" form)

State Event Handling - Decay1

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Bouncing Ball

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

MagicDraw/Cameo v19SP3+SysPhS-1.1: Does not cleanly export Modelica 'when/then' statements

Cooling Revisited - NewtonCoolingSteadyThenDynamic

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Cooling Revisited - NewtonCoolingDynamic

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Lotka-Volterra Systems - QuiescentModelWithModifications

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Lotka-Volterra Systems - QuiescentModelUsingStart

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Lotka-Volterra Systems - ClassicModel

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

A Mechanical Example - SecondOrderSystem

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

An Electrical Example - RLC1

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

SysPhSLibrary and ISO-80000 ModelLibrary: Some ValueType names and Unit symbols are not Modelica-friendly

SysPhS-1.1: Does not support Modelica's 'min' or 'max' on type declarations

MagicDraw/Cameo v19SP3: SysPhS: If you have a custom ValueType it MUST extend Real either directly or indirectly or it will not be seen on export to Modelica.

Getting Physical - NewtonCoolingWithTypes

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Getting Physical - NewtonCoolingWithDefaults

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

SysPhS-1.1: Does not support Modelica's 'experiment' annotations

SysPhS-1.1: Does not support Modelica's 'initial equation'. WORKAROUND: One can often achieve the same by directly setting a default on a variable and/or by using additional variables/parameters with 'start' and additional equations.

Simple First Order System - FirstOrderSteady

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Simple First Order System - FirstOrderInitial

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Simple First Order System - FirstOrder

Gallery

Tutorial

Section

Slide kind

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

09. Architectures [TODO]

08. Subsystems [TODO]

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

07. Components [MOST]

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Slides in this section

If you want to navigate the entire section including the additional explanatory text click on the title link of the first slide to view the full slide page, then use the next links to move through the slide pages. If you just want to view the slide images only in sequence, click on any slide to view it larger in a viewer, then click again to move through each slide in this tutorial trail section.

Thermal Connectors

ThermalCapacitance - Adiabatic

AmbientConvectionCapacitance (combined)

Electrical Components - TwoPin

Resistor - Capacitor - Inductor - StepVoltage - Ground

TwoPin - SwitchedRLC

Basic Rotational Components - TwoFlange

Compliant - RotationalInertia - Spring - Damper - Ground

SMD

SMD_WithBacklash

GroundedGear - comparison

UngroundedGearComparison - comparison

Lotka-Volterra Equations Revisited - FlowingSpecies

Lotka-Volterra Equations Revisited - RegionalPopulation

SinkOrSource - Reproduction - Starvation

Interaction - Predation

FoxRabbitWithInit

ThirdSpeciesWolf

Block Diagram Components - SO - SISO

Block Diagram Components - S0 - DISO

NewtonCoolingWithBlocks

MultiDomainControl

06. Connectors

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Slides in this section

SimpleDomains - Electrical

SimpleDomains - Translational

SimpleDomains - Rotational

SimpleDomains - Thermal

Fluid Connectors - Incompressible

Fluid Connectors - Compressible

Fluid Connectors - ThermoFluid

Block Connectors

Graphical Connectors

05. Packages [NOT COVERED]

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

04. Functions [NOT COVERED]

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

03. Vectors and Arrays [NOT COVERED]

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

02. Discrete Behavior

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Slides in this section

Cooling Revisited - NewtonCoolingDynamic

Cooling Revisited - NewtonCoolingSteadyThenDynamic

Bouncing Ball

State Event Handling - Decay1

Switched RLC Circuit - SwitchedRLC

Speed Measurement - SampleAndHold

Hysteresis - ChatteringControl

01. Basic Equations

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Slides in this section

Simple First Order System - FirstOrder

Simple First Order System - FirstOrderInitial

Simple First Order System - FirstOrderSteady

Getting Physical - NewtonCoolingWithDefaults

Getting Physical - NewtonCoolingWithTypes

An Electrical Example - RLC1

A Mechanical Example - SecondOrderSystem

Lotka-Volterra Systems - ClassicModel

Lotka-Volterra Systems - QuiescentModelUsingStart

Lotka-Volterra Systems - QuiescentModelWithModifications

TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica]

Jump to first slide

Simple First Order System - FirstOrder

Sections

03. Vectors and Arrays [NOT COVERED]

04. Functions [NOT COVERED]

05. Packages [NOT COVERED]

TRAIL: SysPhS-1.1 Annex A examples in MagicDraw/Cameo SysML vs Modelica (Wolfram SystemsModeler)

08. Subsystems [TODO]

09. Architectures [TODO]

SysPhS-1.1 vs Modelica: On export the SysPhS signal flow Port types are flattened to remove the FlowProperty (rSig, iSig, or bSig). In the exported Modelica code you'll only ever see the Port names.

Wolfram SystemModeler: Not clear how to draw a connect that already exists in the Modelica code

MagicDraw/Cameo v19SP3 vs SysML&SysPhS: Export to Modelica: The exported layout annotations appear to be completely broken (at least vs Wolfram SystemModeler) just de-select generation of them on export.

GOTCHA: MagicDraw SysML/Cameo 19SP3: Export to Modelica: The name of a redefining Property must be exactly the same as the Property it redefines or it will not export properly!

Webel vs SysPhS-1.1: Annex A.5: Humidifier: Where ValueTypes involving litre are defined, the Unit symbol "L" is used rather than the Modelica-preferred "l" (in combination with an explicit additional unit converter).

Modelica: Units: Uses 'l' for litre, rather than 'L'.

Wolfram SystemModeler: On Mac the Unit Conversions dialog is under SystemModeler -> Preferences -> Global -> Unit Conversion (rather than under Tools -> Options)

Wolfram SystemModeler: GOTCHA: The conversion dialog will not offer the Add Unit Conversion button unless there is not already an existing conversion in BOTH directions.

Webel vs SysPhS-1.1: Annex A.5: Humidifier: The water temperature from TemperatureIncreaseConstraint and HeatingCalculationConstraint starts at 0 °C (should probably be the environment temperature 20 °C). Needs an additional parameter and initial value.

Webel vs SysPhS-1.1: Annex A.5: Humidifier: Where custom ValueTypes are defined, Modelica-friendly Unit symbols are used. Examples: "m3" not "m^3"; "degC" not "°C"; "J/(K.L)" (full stop as multiplier) not "J/(K⋅L)"; (EXCEPT "L" for litre not "l").

A.5 Humidifier: Value property defaults table

Gallery

Tutorial

Section

TRAIL: SysPhS-1.1 Annex A examples in MagicDraw/Cameo SysML vs Modelica (Wolfram SystemsModeler)

Slide kind

MagicDraw/Cameo: table

SysML/SysPhS-1.1: Anonymous Property or Action names may not be an option if: You are exporting to Modelica or Simulink; You absolutely need names for generated query reports (such as generated Interface Control Documents).

A.5 Humidifier: Scenario block overview BDDs: 96 to 102

Gallery

Tutorial

Section

Slide kind

TRAIL: SysPhS-1.1 Annex A examples in MagicDraw/Cameo SysML vs Modelica (Wolfram SystemsModeler)

Export to Modelica and execution of the SysML/SysPhS block HumidifierSystem_S1

Gallery

Tutorial

Section

Slide kind

TRAIL: SysPhS-1.1 Annex A examples in MagicDraw/Cameo SysML vs Modelica (Wolfram SystemsModeler)

MagicDraw/Cameo: If you drag a Behavior from the model browser onto the SYMBOL of a State (that does not already own the Behavior) and set it as an 'entry', 'doActivity', or 'exit' Behavior a "wrapper" Behavior owned by the State will be created.

MagicDraw SysML/Cameo 19SP3: GOTCHA: If you drag a Behavior from the model browser onto the 'entry', 'doActivity', or 'exit' field in a specification dialog of a State it WILL BECOME OWNED by the State (which "steals ownership")!

REFERENCE: A.5 Humidifier: Webel: Block overview

Gallery

Tutorial

Section

Slide kind

TRAIL: SysPhS-1.1 Annex A examples in MagicDraw/Cameo SysML vs Modelica (Wolfram SystemsModeler)

Modelica does not support comparison of Real values using == outside of functions (so not directly inside state machines)

MagicDraw/Cameo v19SP3 vs SysML&SysPhS: GOTCHA: Will NOT correctly export a SysML-1.6 «~interfaceBlock» to Modelica (but does cope with a tilde ~ prefix in the name of a plain InterfaceBlock)

MagicDraw/Cameo vs SysML&SysPhS: GOTCHA: Will NOT export a non-normative System «system» block to Modelica, it only recognises a plain Block «block»!

Export to Modelica and execution of the SysML/SysPhS block ConnectedTanks

Gallery

Tutorial

Section

Annex A.4: Hydraulics

Slide kind

TRAIL: SysPhS-1.1 Annex A examples in MagicDraw/Cameo SysML vs Modelica (Wolfram SystemsModeler)

Export to Modelica and execution of the SysML/SysPhS block TestBed for SignalProcessing

Gallery

Tutorial

Section

Annex A.3: Signal Processor

Slide kind

TRAIL: SysPhS-1.1 Annex A examples in MagicDraw/Cameo SysML vs Modelica (Wolfram SystemsModeler)

SysML/SysPhS + Modelica: The variable 'time' is known to Modelica and need not be explicitly declared as a constraint parameter for a Constraint on a SysML ConstraintBlock

Export to Modelica and execution of the SysML/SysPhS block Circuit

Gallery

Tutorial

Section

Annex A.2: Electric Circuit

Slide kind

TRAIL: SysPhS-1.1 Annex A examples in MagicDraw/Cameo SysML vs Modelica (Wolfram SystemsModeler)

Modelica versions of the ElectricCircuit (with and without overlapping connect lines)

Gallery

Tutorial

Section

Annex A.2: Electric Circuit

Slide kind

electrical circuit diagram

electrical schematic

lumped element model

modelica patch diagram

TRAIL: SysPhS-1.1 Annex A examples in MagicDraw/Cameo SysML vs Modelica (Wolfram SystemsModeler)

Jump to first slide

Figure 37: Electric circuit example (MOCKUP)

Sections

Annex A.2: Electric Circuit

Annex A.3: Signal Processor

Annex A.4: Hydraulics

Annex A.6: Cruise Control System [TODO]

SysPhS-1.1: p.38: 10.9.4 Modelica modeling, signal flow: Modelica code: the equation 'der(velocity)=(u-springcst*position)/m;' should use variable 'mass' not 'm'

Figure 36: Elements for vector signal flow

Gallery

Tutorial

TRAIL: SysPhS-1.1 specification body figures in MagicDraw/Cameo SysML vs Modelica [using Wolfram SystemsModeler]

Section

Slide kind

11.5.2 Platform profile: This subclause defines stereotypes that Subclause 11.3 applies to the base classes and properties (including ports) of its blocks, to specify which library elements of Modelica and Simulink correspond to them.

Source

TRAIL: SysPhS-1.1 specification body figures in MagicDraw/Cameo SysML vs Modelica [using Wolfram SystemsModeler]

Figure 35: Simulation platform stereotypes

Gallery

Tutorial

Section

Slide kind

TRAIL: SysPhS-1.1 specification body figures in MagicDraw/Cameo SysML vs Modelica [using Wolfram SystemsModeler]

Figure 32: Elements for signal flows of electrical quantities [additional]

Gallery

Tutorial

Section

Slide kind

TRAIL: SysPhS-1.1 specification body figures in MagicDraw/Cameo SysML vs Modelica [using Wolfram SystemsModeler]

11.3 Component behavior - Electrical components

Gallery

Tutorial

Section

Slide kind

TRAIL: SysPhS-1.1 specification body figures in MagicDraw/Cameo SysML vs Modelica [using Wolfram SystemsModeler]

Concerning definitions: "a connector end" vs "a connector between 2 ends" vs "connection" vs "connect" in various technologies

Modelica: GOTCHA: Sometimes the name 'p' is used for any Pin (such as on Ground) and sometimes 'p' is used for a specifically PositivePin (as opposed to 'n' for NegativePin).

Modelica: Naming convention: Why does the OnePort family of electrical components have 2 Pins? Where is the "one port"?

11.3 Component behavior - Logical components

Gallery

Tutorial

Section

Slide kind

TRAIL: SysPhS-1.1 specification body figures in MagicDraw/Cameo SysML vs Modelica [using Wolfram SystemsModeler]

11.3 Component behavior - Routing components

Gallery

Tutorial

Section

Slide kind

MINI TRAIL: Some recommended tools for getting started with Model-Based Systems Engineering with SysML and simulation with Modelica and/or Simulink

SysPhS-1.1: p.60: table for routing components: row for Switch: equivalents Modelica.Blocks.Logical.Switch (for Modelica) and Switch (for Simulink) missing

SysPhS-1.1: Use of 'Criteria = u2~=0' for Simulink for Real.Routing.Switch::u2 inconsistent with BooleanInput of control port Modelica.Blocks.Logical.Switch::u2

SysPhS-1.1 (and MDSysML/Cameo 19SP3 SysPhSLibrary): Use of RealSignalInElement for Real.Routing.Switch::u2 inconsistent with BooleanInput of control port Modelica.Blocks.Logical.Switch::u2

SysPhS-1.1: SourceAndSink.Clock does not have 'offset' or 'startTime' to match Modelica's Clock

SysPhS-1.1: p.57: Table 11.3.2.5 Mathematical components: Modelica Parameters for the Subtraction row should indicate (k1 and) k2 required to achieve subtraction via Math.Add (or the correct exported values should be explained).

MDSysML/Cameo: SysPhSLibrary: GOTCHA: You must set the additional 'k2' parameter for Modelica to be minus to achieve subtraction

SysPhS-1.1: p.57: GOTCHA: Table 11.3.2.5 Mathematical components: Mathematical.Subtraction maps to Math.Add (in Modelica) and Sum (in Simulink)

External simulation: Languages and tools: SysML vs SysPhS vs Modelica vs Simulink

Gallery

Tutorial

Section

As of 2021-01-11 OpenModelica no longer has DMG install bundles for Mac, and currently does NOT install on Mac Big Sur using MacPorts!

The following Modelica code corresponds to Figure 29.

Source

TRAIL: SysPhS-1.1 specification body figures in MagicDraw/Cameo SysML vs Modelica [using Wolfram SystemsModeler]

Figure 29: State machine in SysML

Gallery

Tutorial

Section

Slide kind

SysML StateMachine Diagram

The following Modelica code corresponds to Figure 28. It has a type Force, which extends Real, and the unit symbol N assigned to it.

Source

Modelica data types can be subtyped to add a unit symbol. The interpretation of this symbol is not defined in Modelica.

Source

TRAIL: SysPhS-1.1 specification body figures in MagicDraw/Cameo SysML vs Modelica [using Wolfram SystemsModeler]

Figure 28: Units in SysML

Gallery

Tutorial

Section

Slide kind

It has a model B with a val component. The val component has a start value of 10. A class A is defined with a component b of type B. A component modification indicates that the start value of b.val is 20.0.

Source

The following Modelica code corresponds to Figure 15 [ERROR].

Source

SysML default and initial values correspond to start values of Modelica components. Start values are marked as fixed, requiring the values be set at the beginning of the simulation (otherwise, simulators only take the values as suggestions ...)

Source

TRAIL: SysPhS-1.1 specification body figures in MagicDraw/Cameo SysML vs Modelica [using Wolfram SystemsModeler]

Figure 27: Default values and initial value in SysML

Gallery

Tutorial

Section

Slide kind

SysPhS-1.1: p.42: 10.9.8 Modelica modeling, physical interaction: Modelica code has 'forcediff=springcstlengthchg;' should be 'forcethru=springcstlengthchg;'

GOTCHA: MagicDraw SysML/Cameo 19SP3: Export to Modelica: 'entry', 'doActivity', or 'exit' Behaviors of a State must be directly owned (not just "wrapped") or they won't be seen on export!

f1 is replaced by p1.f, v1 is replaced by p1.lV, x is replaced by lengthchg, k is replaced by springcst, v is replaced by velocitydiff, f is replaced by forcethru, v2 is replaced by p2.v, and f2 is replaced by p2.f.

Source

The following Modelica code corresponds to Figure 26. It has five equations from the SysML constraint block. SysML parameter names are replaced in the Modelica equations according the bindings in Figure 14 [ERROR]:

Source

(and flow properties in SysML property paths leading to PhSVariables on conserved quantity kinds are omitted in Modelica, see Subclause 10.7.8).

Source

In a SysML block with constraint properties, the constraints correspond to the same equations in Modelica ... except the SysML parameters in those equations correspond in Modelica to the properties they are bound to in SysML

Source

TRAIL: SysPhS-1.1 specification body figures in MagicDraw/Cameo SysML vs Modelica [using Wolfram SystemsModeler]

Figure 26: Constraint block for physical interaction in SysML

Gallery

Tutorial

Section

Slide kind

SysPhS-1.1: p.38: 10.9.4 Modelica modeling, signal flow: Modelica code: the keyword should be 'equation' not 'equations'.

SysML parameter names are replaced in the Modelica equations according to the bindings in Figure 13 [ERROR]: f is replaced by u, pos is replaced by y, x is replaced by position, k is replaced by springcst, v is replaced by velocity, m is replaced by mass.

Source

The following Modelica code corresponds to Figure 25. It has three equations from the constraint block.

Source

In a SysML block with constraint properties, the constraints correspond to the same equations in Modelica ... except the SysML parameters in those constraints correspond in Modelica to the properties they are bound to in SysML.

Source

TRAIL: SysPhS-1.1 specification body figures in MagicDraw/Cameo SysML vs Modelica [using Wolfram SystemsModeler]

Figure 25: Constraint block for signal flow in SysML

Gallery

Tutorial

Section

Slide kind

TRAIL: SysPhS-1.1 specification body figures in MagicDraw/Cameo SysML vs Modelica [using Wolfram SystemsModeler]

Figure 24: Connectors in SysML

Gallery

Tutorial

Section

Slide kind

TRAIL: SysPhS-1.1 specification body figures in MagicDraw/Cameo SysML vs Modelica [using Wolfram SystemsModeler]

Figure 23: Ports for physical interaction in SysML

Gallery

Tutorial

Section

Slide kind

TRAIL: SysPhS-1.1 specification body figures in MagicDraw/Cameo SysML vs Modelica [using Wolfram SystemsModeler]

Figure 22: Ports for signal flow in SysML

Gallery

Tutorial

Section

Slide kind

TRAIL: SysPhS-1.1 specification body figures in MagicDraw/Cameo SysML vs Modelica [using Wolfram SystemsModeler]

SysPhS-1.1: p.28: 10.6.3 Modelica modeling: An assigned value “...” is shown for v3 in the Modelica code but none is shown in the SysML model in 'Figure 21: PhSVariables and PhSConstant in SysML' (and “...” is not compatible with Real).

MagicDraw SysML/Cameo: 19SP3: Does not seem to support export to Modelica from a Package [use a SysML Block as root instead]

Figure 17: Package and model in SysML

Gallery

Tutorial

Section

Slide kind

Figure 1: Simulation stereotypes

TRAIL: SysPhS-1.1 specification body figures in MagicDraw/Cameo SysML vs Modelica [using Wolfram SystemsModeler]

Jump to first slide

Sections

MagicDraw SysML/Cameo: SysPhS: Export to Modelica: It does not seem to matter whether you give the language of Constraints as 'Modelica' or 'sysphs' (although SysPhS specifies a restricted SysPhS expression grammar)

MagicDraw SysML/Cameo: GOTCHA: Export to Modelica only includes owned Constraints (not just applied Constraints) under the 'equation' export

SysPhS-1.1: p.32: 10.7.8 Modelica modeling, physical interaction: Type Real for 'f' and 'lV' in example Modelica code for Spring do not correspond to 'Figure 23: Ports for physical interaction in SysML', should be Force and Velocity.

SysPhS-1.1: p.30: 10.7.4 Modelica modeling, signal flow: Example Modelica code for Spring corresponding to 'Figure 22: Ports for signal flow in SysML' is invalid [should probably be 'input Real u;' and 'output Real y;' not 'in ...' and 'out ...']

SysPhS: GOTCHA: By default PhSConstant maps to a Modelica parameter (not to a Modelica constant)

By default, Modelica properties are continuous. PhSVariables with isContinuous=true correspond to continuous components, PhSVariables with isContinuous=false correspond to discrete components, and PhSConstants correspond to parameter variables.

Source

10.6.3 Modelica modeling: The variability of Modelica properties are of four kinds: continuous, discrete, parameter, and constant.

Source