In order to appreciate how design problems may be modelled, it is useful to consult a range of examples. To this end ESP-r incorporates preconstructed models of incremental complexity that may be loaded, examined and simulated. Some of the simpler models are presented here.
Several modelling case studies are also available which illustrate the application of modellng and simulation to real buildings.
For training purposes it is useful to begin with a minimal problem description and then progressively add features and complexity to more closely represent the observed reality. The following image shows a wireframe view of a single thermal zone with a list of its surfaces and attributes. Such a model is used to help users appreciate the underlying model data.
The intention of this 3 zone model is to allow users to explore how simple models may be extended over time to address specific issues as they arise. The following image shows the model before and after the addition of shading obstructions.
The ESP-r training directory includes the above model /usr/esru/esp-r/training/3z_bld) with several variant configurations located within the cfg subdirectory follows.
building_basic, the basic three zone model
building_bls, with blind shutter control
building_shd, with shading
building_shd_vwf, as building_shd with explicity view factors
building_mass_a, a basic building with infiltration air flow
building_mass_b, with infiltration and pening doors
building_mass_c, with infiltration and opening windows
The constructions for each models are defined in the file building.mlc while alternative control definitions are located in the cfg directory as files
building.ctl, reception and office heating system control
pre-heat.ctl, all zone heating with pre-heat period
temp-match.ctl, match temperature of other zones to that prevailing in the reception
building_mass_b.ctl, heat reception only
building_w.ctl, as building.ctl but with window control
building_s.ctl, window control only, no heating
building_basic
Three zone building with
ideal control, scheduled air flow (default treatments). Purpose is to look at
the added topology definitions required of a multi-zone problem. Building_basic
makes use of most of the basic descriptive files.
building_bls
In the case of building_bls blind shutter control has been added to the
office. To access this supply the name building_bls for the problem name and
the relevant information will be loaded. Note that building_bls now references
office.utl which in turn references office.bls.
building_shd
This is the basic building with addional details of obstructions and the
inclusion of a shading database for the reception. Shading has been calculated
for the reception (surfaces south west glz_s door_w) for the period January
- December. Note that file building_shd now references reception_shd.utl rather
than reception.utl.
building_shd_vwf
In the case of building_shd_vwf the model was made more robust by upgrading
the default area weighted viewfactors between surfaces in the reception with
viewfactors calculated by a ray-tracing method. The actual calculations are
performed by the shapefactor program. Note that the problem file building_shd_vwf
now references reception_shd_vwf.utl.
building_mass_a
The basic building with air movement restricted to flows via crack openings
(under doors and around windows) in the occupied spaces. Separately, the roof
is vented by soffit and ridge vents. Use the configuration control file building.ctl_w
which provides 1kW to the reception and office.
building_mass_b
A variation in base case with the addition of a component `door' between
the rooms in the mass flow network. Use the configuration control (ctl/building_mass_b.ctl)
which supplies 2kW heat to the reception but nothing to the office. During simulation
notice how the air movement between the rooms provides much of the heating to
the office.
building_mass_c
This variation add control of window openings to the previous network. If
you are running a summer simulation use building_s.ctl, if a winter simulation
use building_w.ctl.
Air flow networks
The base case air flow network is described in building.mfn_a and contains four boundary nodes (north, east, south, west) and three nodes (roof, recep, offic) which match the thermal zones. Air flow components (drcrk, wincrk, soffit, roofv) define the flow restrictions. The flow paths are between each zone and the outside via window cracks and between the two occupied rooms via a crack under the door. The roof space has two flow paths to the outside - one through the soffit and one by way of the roof vent.
The air flow network with window control is building.mfn_c. The control is made via a configuration control file. A window in the reception is assumed to open if the room temperature rises above 20°C. A similar set of paths is defined for the office.
During a summer simulation see how flow is restricted to the cracks in the windows until the room warms and then the window opens, flow is allowed and then when the temperature drops below 20°C the window closes. In the results analysis you will probably detect a sawtooth pattern as the windows open and close. The decision to open or close the cracks in the windows until the room warms and then the window opens, flow is allowed and then when the temperature drops below 20°C the window closes. In the results analysis you will probably detect a sawtooth pattern as the windows open and close. The decision to open or close the window is only taken once per timestep and you should experiment with different simulation timesteps to see how this ventilation control changes.
Two other configuration control files are provided for this 3-zone problem.
(1) pre-heat.ctl
This file provides for a typical daily 3-period control schedule.
Control schedule for all three zones:
00.00 - 09.00 preheat
09.00 - 18.00 ideal control
18.00 - 24.00 free-float
(2) temp_match.ctl
This file provides for a temperature matching control strategy whereby a zone's air temperature is controlled to follow that of another zone (the reception in this case).Control schedule for office and roof:
00.00 - 24.00 match Zone_1 air temperature.
Simulation can be used to explore the potential for novel energy conservation approaches. In this case the example model deals with a two level detached domestic dwelling with a conservatory used to preheat the ventiliation air.
Simulation the model was used to explore alternative environmental control strategies for office buildings. The model was established to support a natural ventilation study.
This example demonstrates the simulation of a combined building and plant model. This plant model corresponds to a packaged air handling unit.
* PRE-HEAT CONTROL.
Sensor Location: pre-heater exit.
Sensed Variable: dry bulb temperature.
Actuator Location: pre-heater.
Actuated Variable: flux.
Control Law: proportional.
Proportional Band. 2 deg C.
Output Range: 0.0 -> 3.5 kW.
Control Period: 07.00 -> 18.00
* HUMIDIFIER CONTROL.
Sensor Location: humidifier exit.
Sensed Variable: dry bulb temperature.
Actuator Location: humidifier.
Actuated Variable: moisture injection.
Control Law: proportional.
Proportional Band. 12% RH.
Output Range: 0.001 -> 0.005 kg/kg.da.
Control Period: 07.00 -> 18.00
* COOLING COIL CONTROL.
Sensor Location: coiling coil exit.
Sensed Variable: dry bulb temperature.
Actuator Location: coiling coil.
Actuated Variable: flux.
Control Law: proportional.
Proportional Band. 2 deg C.
Output Range: 0.0 -> 1.0 kW.
Control Period: 07.00 -> 18.00
* RE-HEAT CONTROL.
Sensor Location: re-heater exit.
Sensed Variable: dry bulb temperature.
Actuator Location: re-heater.
Actuated Variable: flux.
Control Law: proportional.
Proportional Band. 2 deg C.
Output Range: 0.0 -> 3.5 kW.
Control Period: 07.00 -> 18.00
Several other control strategies are available for use with this model:
ahu_flow.on-off-ctl, basic on/off control of the re-heat coil.
ahu_flow.prop-ctl, basic proportional control of humidity and temperature.
ahu_flow.PI-ctl, proportional + integral control of temperature.
When undertaking simulations it is advisable to keep the time step small (<3min) to ensure control system stability.