A set of examples illustrating when special attention has to be paid
Extends from Modelica.Icons.ExamplesPackage (Icon for packages containing runnable examples).
Name | Description |
---|---|
MeasuringTemperature | Differences between using one port with and without explicit junction model and two port sensors for fluid temperature measuring |
MomentumBalanceFittings | Illustrating a case in which kinetic terms play a major role in the momentum balance |
Differences between using one port with and without explicit junction model and two port sensors for fluid temperature measuring
This model demonstrates the differences that occur when using one- and two-port temperature sensors with and without explicit junction models. As shown in the next figure, the same system is shown in 3 different variations. In all cases exactly the same fluid system is defined. The only difference is how the temperature is measured:
A pre-defined mass flow rate is present so that fluid flows from the reservoir to the tanks and after 0.5 s the mass flows from the tanks to the reservoir. The reservoir has a temperature of 500C whereas the tanks have an initial temperature of 200C and of 800C. The initial height of the tanks is made in such a form that fluid always flows out of the cold tank. When the fluid flows from the reservoir to the tanks, then it mixes with the cold tank and enters the hot tank. When the fluid flow from the tanks to the reservoir, then the cold and hot water from the two tanks first mixes and the flows to the reservoir.
A one-port sensor measures the mixing temperature at a connection point. Therefore T_onePort.T (the blue curve in the figure below) is the temperature of the mixing point. A two-port sensor measures the temperature at the upstream side. Therefore T_twoPort.T (the red curve in the figure below which is identical to the green curve) shows first the temperature of the reservoir and then the mixing temperature when fluid flows from the tanks to the reservoir. The same is measured with T_junction.T (the green curve below), because the one-port sensor is connected between the mass flow source and the junction and since the mixing takes place in the junction, the same situation is present as for T_twoPort.T.
Extends from Modelica.Icons.Example (Icon for runnable examples).
Illustrating a case in which kinetic terms play a major role in the momentum balance
This example shows the use of a sudden expansion / contraction model, which is connected to two boundary conditions prescribing static pressure. Notice that the prescribed static pressure on the right boundary is higher than on the left one. Still, the fluid flows from left to right.
The reason for this is that the boundary conditions model infinite reservoirs with an infinite diameter and thus zero flow velocity. The sudden expansion model does however have two ends with finite diameters, and, as explained in the Overview of the Users' Guide, the momentum balance is not fulfilled exactly for this type of connections. Using a simple connect()
-statement, the difference of the kinetic terms is neglected, which is not reasonable in the present model: At the left boundary condition it is zero, and on the left side of the sudden expansion it has a non-zero value. It is not reasonable to neglect it in the shown model, because there is little friction and therefore these kinetic effects dominate. Consequently, only modelling these effects explicitly leads to the correct results.
To do so, two additional sudden expansions / contractions are included in the model. The diameter is set to inf
close to the boundaries and the proper values close to the original model. These additional components now introduce exact momentum balances and the results are as expected.
The total pressures offer an additional perspective on the model. After setting the parameter show_totalPressures
on the Advanced tab of the AbruptAdaptor
s to true
, the total pressures are included in said models and may be plotted. This allows to confirm that the total pressure always reduces along the flow direction, even in the upper model.
Extends from Modelica.Icons.Example (Icon for runnable examples).
Automatically generated Thu Dec 19 17:20:09 2019.