-
Notifications
You must be signed in to change notification settings - Fork 153
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
Issue3027 wet coil sensible heat #3049
Conversation
Files were added manually to exclude the large file Buildings/Resources/Data/Fluid/HeatExchangers/Examples/WetCoilCounterFlowPescribedBoundary.dat
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think removing heaConVapCoi
is the right thing to do. (The following insight is derived from Heat Transfer by A.F. Mills Chapter 7).
An energy balance for an element of condensate has:
(+) Enthalpy entering from condensate drip from above elements due to gravity.
(+) Enthalpy entering from condensation from air.
(-) Enthalpy leaving from condensate drip to below elements due to gravity.
(-) Conduction through the thickness of the condensate element due to the difference between T_sat and T_coil. This last part hinders condensation some since it effectively adds a thermal resistance between the coil surface and the bulk moist air.
Thus, it is not correct to have the heat of condensation sensibly added to the coil frame explicitly. I may suggest adding a line in the documentation about how the model does not explicitly consider the film thickness. In reality, this thickness is not negligible, as there's research on hydrophobic coatings to quickly remove condensate layers to improve overall heat transfer coefficients, though in practice its hard to keep these coatings clean and intact. But, this coil model's overall heat transfer coefficient is parameterized with a nominal UA anyway, which I think would include whatever heat transfer coefficient a user wants to define at nominal conditions.
@dhblum : Thanks, I will merge it for the 9.0.0 release, and also update on the |
This closes #3027
@dhblum : Can you please look at the new formulation of Buildings/Fluid/HeatExchangers/BaseClasses/HexElementLatent.mo
@SenHuang19: FYI, this should resolve the issue you reported. Can you test on your larger example? As a hack, all you would need to do is delete the instance
heaConVapCoi
inHexElementLatent
.We plan to include it in the 9.0.0 release that is scheduled for this Tuesday if this solves the issue.