Skip to content

heat pump forced stop time #1566

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
icupeiro opened this issue Dec 10, 2021 · 8 comments
Open

heat pump forced stop time #1566

icupeiro opened this issue Dec 10, 2021 · 8 comments

Comments

@icupeiro
Copy link
Contributor

icupeiro commented Dec 10, 2021

heat pumps/chillers normally have a minimum forced stop time (e.g. 5-10minutes) when the compressor is turned off to avoid damages due to continuous on/off

IBPSA.Fluid.HeatPumps.BaseClasses.PartialWaterToWater does not have this feature

This could be added as a parameter e.g. in the component IBPSA.Fluid.HeatPumps.Compressors.BaseClasses.TemperatureProtection

@FWuellhorst
Copy link
Contributor

As a note, this could be related to #1576. We already developed several safety controls in the AixLib (operational envelope/temperature protection, minimal runtime, minimal off-time, starts per hour, etc.).

@mwetter
Copy link
Contributor

mwetter commented Jan 28, 2022

@icupeiro : Let's see if the protection from #1576 should be added, or if alternatively a simple timer should be added that if set to 0, will be conditionally removed.

@FWuellhorst
Copy link
Contributor

This is a feature in the new hp models, still relevant for the water-to-water models? @mwetter @icupeiro ?

@icupeiro
Copy link
Contributor Author

Hi @FWuellhorst thanks for bringing this back

When I opened this issue, I gave it for granted that this minimum forced stop (or start) time was a must in all heat pumps. I think I was a bit naive in that regard at the time

what I see in the heat pumps I have encountered so far (after all these years since I opened the issue, now with a bit more of commercial experience) is that the feature can or cannot be there, i.e. depends on the manufacturer. So for me this is an optional asset to have. This also happens in any kind of large equipment such as air handling units and large hydraulic pumps.

When the safety forced stop/start time is there, this is a thing less to worry about (or at least you may tackled it different)
When is not, you have to really take it into account into your control actions to avoid wear and tear (which may be challenging in the case of continuous optimal controllers)

The message I want to convey is that the forced start/time should not be restricted only to the heat pump model, but to other equipment as well, and it should be optional since I found many pieces of equipment that does not include this feature.

Whether to include this feature within each relevant component model (such as pumps, heat pumps, boilers, etc...), or as an independent block that the modeler uses it externally, is a discussion where I do not have a strong opinion

@FWuellhorst
Copy link
Contributor

@icupeiro thanks for the insight. I agree that adding such an option to other equipment could benefit transfer to practice. The blocks implemented for the heat pump are rather general, so as long as the input is relative between 0 and 1 and there is a boolean indicating if the device is on or off it could be reused in other components, as well.
And it is optional for the heat pump models already, so it would be in line with your experience.

@mwetter
Copy link
Contributor

mwetter commented Mar 3, 2025

@FWuellhorst : Which "water-to-water " models do you mean? The model HeatPumps.ModularReversible.LargeScaleWaterToWater already has this option.

@FWuellhorst
Copy link
Contributor

I meant the models around AixLib.Fluid.HeatPumps.ReciprocatingWaterToWater.

@mwetter
Copy link
Contributor

mwetter commented Mar 4, 2025

I think adding these safety features would be an improvement of the model.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants