Buildings.Obsolete.Fluid.Movers.Validation

Obsolete validation models

Information

This package contains obsolete validation models.

Extends from Modelica.Icons.ExamplesPackage (Icon for packages containing runnable examples).

Package Content

Name	Description
PowerEuler	Power calculation comparison among three mover types, using Euler number computation for m_flow and dp
PowerExact	Power calculation comparison among three mover types, using exact power computation for m_flow and dp
PowerSimplified	Power calculation comparison among three mover types, using simplified power computation for m_flow and dp

Buildings.Obsolete.Fluid.Movers.Validation.PowerEuler

Power calculation comparison among three mover types, using Euler number computation for m_flow and dp

Buildings.Obsolete.Fluid.Movers.Validation.PowerEuler

Information

This example is identical to Buildings.Obsolete.Fluid.Movers.Validation.PowerSimplified, except that the efficiency of the flow controlled pumps pump_dp and pump_m_flow is estimated by using the Euler number and its correlation as implemented in Buildings.Fluid.Movers.BaseClasses.Euler.

The figure below shows the approximation error for the power calculation where the speed y differs from the nominal speed y_nominal.

Extends from Buildings.Obsolete.Fluid.Movers.Validation.PowerSimplified (Power calculation comparison among three mover types, using simplified power computation for m_flow and dp).

Parameters

Type	Name	Default	Description
MassFlowRate	m_flow_nominal	3	Nominal mass flow rate [kg/s]
Stratos30slash1to8	per		Pump performance data
Generic	perPea	perPea(final powerOrEfficien...	Peak condition

Modelica definition

model PowerEuler "Power calculation comparison among three mover types, using Euler number computation for m_flow and dp" extends Buildings.Obsolete.Fluid.Movers.Validation.PowerSimplified( pump_dp(per=perPea), pump_m_flow(per=perPea)); parameter Buildings.Fluid.Movers.Data.Generic perPea( final powerOrEfficiencyIsHydraulic=per.powerOrEfficiencyIsHydraulic, final etaHydMet= Buildings.Fluid.Movers.BaseClasses.Types.HydraulicEfficiencyMethod.EulerNumber, final etaMotMet= Buildings.Fluid.Movers.BaseClasses.Types.MotorEfficiencyMethod.NotProvided, final peak=Buildings.Fluid.Movers.BaseClasses.Euler.getPeak( pressure=per.pressure, power=per.power)) "Peak condition"; end PowerEuler;

Buildings.Obsolete.Fluid.Movers.Validation.PowerExact

Power calculation comparison among three mover types, using exact power computation for m_flow and dp

Buildings.Obsolete.Fluid.Movers.Validation.PowerExact

Information

This example is identical to Buildings.Obsolete.Fluid.Movers.Validation.PowerSimplified, except that the performance data for the flow controlled pumps pump_dp and pump_m_flow contain the pressure curves and efficiency curves. The plot below shows that this leads to a computation of the power consumption that is identical to the one from the speed controlled pump pump_y.

Extends from Buildings.Obsolete.Fluid.Movers.Validation.PowerSimplified (Power calculation comparison among three mover types, using simplified power computation for m_flow and dp).

Parameters

Type	Name	Default	Description
MassFlowRate	m_flow_nominal	3	Nominal mass flow rate [kg/s]
Stratos30slash1to8	per		Pump performance data

Modelica definition

model PowerExact "Power calculation comparison among three mover types, using exact power computation for m_flow and dp" extends Buildings.Obsolete.Fluid.Movers.Validation.PowerSimplified( pump_dp(per=per), pump_m_flow(per=per)); end PowerExact;

Buildings.Obsolete.Fluid.Movers.Validation.PowerSimplified

Power calculation comparison among three mover types, using simplified power computation for m_flow and dp

Buildings.Obsolete.Fluid.Movers.Validation.PowerSimplified

Information

This example compares the power consumed by pumps that take three different control signals. Each pump has identical mass flow rate and pressure rise.

Note that for the instances Buildings.Fluid.Movers.FlowControlled_dp and Buildings.Fluid.Movers.FlowControlled_m_flow, we had to assign the efficiencies (otherwise the default constant efficiency of 0.7 would have been used). In these models, the power consumption is computed using similarity laws, but using the mass flow rate as opposed to the speed, because speed is not known in these two models. This is an approximation at operating points in which the speed is different from the nominal speed y_nominal because similarity laws are valid for speed and not for mass flow rate.

The figure below shows the approximation error for the power calculation where the speed y differs from the nominal speed y_nominal.

Extends from Modelica.Icons.Example (Icon for runnable examples).

Parameters

Type	Name	Default	Description
MassFlowRate	m_flow_nominal	3	Nominal mass flow rate [kg/s]
Stratos30slash1to8	per		Pump performance data

Modelica definition

model PowerSimplified "Power calculation comparison among three mover types, using simplified power computation for m_flow and dp" extends Modelica.Icons.Example; package Medium = Buildings.Media.Water "Medium model"; parameter Modelica.Units.SI.MassFlowRate m_flow_nominal=3 "Nominal mass flow rate"; parameter Buildings.Fluid.Movers.Data.Pumps.Wilo.Stratos30slash1to8 per "Pump performance data"; Buildings.Fluid.Movers.SpeedControlled_y pump_y( redeclare package Medium = Medium, per=per, use_riseTime=false, energyDynamics=Modelica.Fluid.Types.Dynamics.SteadyStateInitial) "Pump with normalised speed y as control signal"; Buildings.Fluid.Movers.FlowControlled_dp pump_dp( redeclare package Medium = Medium, redeclare Buildings.Fluid.Movers.Data.Pumps.Wilo.Stratos30slash1to8 per( pressure(V_flow={0,0}, dp={0,0}), etaHydMet=Buildings.Fluid.Movers.BaseClasses.Types.HydraulicEfficiencyMethod.Efficiency_VolumeFlowRate, etaMotMet=Buildings.Fluid.Movers.BaseClasses.Types.MotorEfficiencyMethod.Efficiency_VolumeFlowRate, efficiency(V_flow={0}, eta={0.3577}), motorEfficiency(V_flow={0}, eta={1})), use_riseTime=false, m_flow_nominal=m_flow_nominal, energyDynamics=Modelica.Fluid.Types.Dynamics.SteadyStateInitial) "Pump with pressure rise as control signal"; Buildings.Fluid.Movers.FlowControlled_m_flow pump_m_flow( redeclare package Medium = Medium, m_flow_nominal=m_flow_nominal, redeclare Buildings.Fluid.Movers.Data.Pumps.Wilo.Stratos30slash1to8 per( pressure(V_flow={0,0}, dp={0,0}), etaHydMet=Buildings.Fluid.Movers.BaseClasses.Types.HydraulicEfficiencyMethod.Efficiency_VolumeFlowRate, etaMotMet=Buildings.Fluid.Movers.BaseClasses.Types.MotorEfficiencyMethod.Efficiency_VolumeFlowRate, efficiency(V_flow={0}, eta={0.3577}), motorEfficiency(V_flow={0}, eta={1})), use_riseTime=false, energyDynamics=Modelica.Fluid.Types.Dynamics.SteadyStateInitial) "Pump with mass flow rate as control signal"; Buildings.Fluid.Sources.Boundary_pT bou( nPorts=3, redeclare package Medium = Medium) "Pressure source"; Buildings.Fluid.FixedResistances.PressureDrop[3] res( redeclare each package Medium = Medium, each m_flow_nominal=m_flow_nominal, each dp_nominal=40000) "Flow resistance"; Buildings.Fluid.Sources.Boundary_pT sink( nPorts=3, redeclare package Medium = Medium); Modelica.Blocks.Sources.Ramp y( y(unit="1"), duration=100, startTime=10, height=(3400 - 2400)/3040, offset=2400/3040) "Ramp for pump normalised speed control signal"; Modelica.Blocks.Sources.RealExpression dpSet(y=pump_y.port_b.p - pump_y.port_a.p) "Pressure rise across pump"; Modelica.Blocks.Sources.RealExpression m_flowSet(y=pump_y.port_a.m_flow) "Pump mass flow rate"; Modelica.Blocks.Routing.Multiplex3 result; equation connect(bou.ports[1], pump_y.port_a); connect(pump_dp.port_a, bou.ports[2]); connect(pump_m_flow.port_a, bou.ports[3]); connect(pump_y.port_b, res[1].port_a); connect(pump_dp.port_b, res[2].port_a); connect(pump_m_flow.port_b, res[3].port_a); connect(sink.ports[1:3], res.port_b); connect(m_flowSet.y, pump_m_flow.m_flow_in); connect(result.u1[1], pump_y.P); connect(result.u2[1], pump_dp.P); connect(result.u3[1], pump_m_flow.P); connect(dpSet.y, pump_dp.dp_in); connect(y.y, pump_y.y); end PowerSimplified;