This model describes a fan or pump with prescribed head. The input connector provides the pressure rise from the inlet to the outlet.
See the User's Guide.
If use_inputFilter=true
, then the parameter dp_nominal
is
used to normalize the filter. This is used to improve the numerics of the transient response.
The actual pressure raise of the mover at steady-state is independent
of the value of dp_nominal
. It is recommended to set
dp_nominal
to approximately the pressure raise that the mover has during
full speed.
Parameter prescribeSystemPressure
can be used to control the mover such that the pressure
difference set point is obtained across two points
in the system, instead of across the fan.
This allows an efficient implementation of
static pressure reset controllers.
A measurement of the pressure difference between the
two points in system then needs to be connected
to RealInput dpMea
.
This functionality is demonstrated in
Buildings.Fluid.Movers.Validation.FlowControlled_dpSystem.
m_flow_nominal
.not use_powerCharacteristic
with the enumerations
Buildings.Fluid.Movers.BaseClasses.Types.HydraulicEfficiencyMethod
and
Buildings.Fluid.Movers.BaseClasses.Types.MotorEfficiencyMethod.final massDynamics=energyDynamics
.y_start
which is not used because dp_start
is used.prescribeSystemPressure
.filteredSpeed
to use_inputFilter
.min
attribute as otherwise numerical noise can cause
the assertion on the limit to fail.heads
.PartialFlowMachine
.
This is for
#417.
use_powerCharacteristics
and power
from the performance data record per
because
Buildings.Fluid.Movers.FlowControlled_dp
and
Buildings.Fluid.Movers.FlowControlled_m_flow
fix the flow rate or head, which can give a flow work that is higher
than the power consumption specified in this record.
Hence, users should use the efficiency data for this model.
The record has been moved to
Buildings.Fluid.Movers.Data.SpeedControlled_y
as it makes sense to use it for the movers
Buildings.Obsolete.Fluid.Movers.FlowControlled_Nrpm
and
Buildings.Fluid.Movers.FlowControlled_y.assert(dp_in >= 0, ...)
to assert(dp_in >= -0.1, ...)
.
The former implementation triggered the assert if dp_in
was solved for
in a nonlinear equation since the solution can be slightly negative while still being
within the solver tolerance.