I have encountered Temperature out of bounds messages in many cases in my models, especially with heat-pumps. The ways to eliminate such problems are manyfold. Successfull approaches have been:
- run the model with extensive output on various variables that can help to understand how the model
behaves, and may explain where the excessive temperatures come from; I usually use ResultsViewer
to diagnose the origin of the problem
- Check: does your model converge at all ? - Then the output is not reliable
- Are you able to eliminate all other warnings in the err-file, or at least to justify ignoring them;
(have you chosen the all/extra warnings for output ?)
- non-convergence can be due e.g. to badly chosen setpoints or setpoint managers, bad sizing assumptions
- You could also selectively switch off/on heating or cooling components in order to analyze under which conditions
your model converges and does not run into temperatures out of bounds.
- controlling the behaviour of the system can be improved by replacing conventional schedules by EMS-driven
schedules: By implementing a logic for deploying heating/cooling components I have also been able to
eliminate Temperature-out-of-bounds messages.
