Skip to content
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

Chilled Beams #725

Open
wants to merge 11 commits into
base: master
Choose a base branch
from
41 changes: 41 additions & 0 deletions ontology/yaml/resources/HVAC/entity_types/ABSTRACT.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -5454,6 +5454,47 @@ RDC:
implements:
- MONITORING

CHWZOUC:
description: "Chilled water valve control with occupied/unoccupied setpoints and temperature monitoring."
is_abstract: true
opt_uses:
- chilled_supply_water_temperature_sensor
uses:
- chilled_water_valve_percentage_command
- zone_air_temperature_sensor
- zone_air_occupied_temperature_setpoint
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Kind of odd seeing occupied temp setpoint and unoccupied cooling setpoint. shouldnt they both be cooling setpoints?

- zone_air_unoccupied_cooling_temperature_setpoint
implements:
- CONTROL

PERHWZOUC:
description: "Perimeter heating water valve control with occupied/unoccupied setpoints and temperature monitoring."
is_abstract: true
opt_uses:
- perimeter_heating_supply_water_temperature_sensor
- perimeter_heating_water_valve_percentage_sensor
uses:
- perimeter_heating_water_valve_percentage_command
- zone_air_temperature_sensor
- zone_air_occupied_temperature_setpoint
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same comment as above, except heating. id expect these to match.

- zone_air_unoccupied_heating_temperature_setpoint
implements:
- CONTROL

ZTOUC:
description: "Zone air temperature unoccupied/occupied control."
is_abstract: true
opt_uses:
- zone_air_relative_humidity_sensor
- zone_occupancy_status
uses:
- zone_air_temperature_sensor
- zone_air_occupied_temperature_setpoint
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

its odd to me that you have differentiated heating and cooling setpoints for unoccupied times, but there are no equivalent differentiations for occupied setpoints.

in general, we see either a single setpoint that changes based on mode, or we see two effective setpoints (for cooling and for heating) that change based on occ/unocc status. what is the context for this weird configuration?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There were no heating/cooling setpoints for occupied mode. Unit runs in either cooling or heating mode while zone is occupied and controls to the occupied setpoint. In unoccupied mode the heating/cooling valves modulate to maintain the zone between the unoccupied heating/cooling setpoints.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can this be fixed? this inconsistency between control in occupied and unoccupied mode is highly irregular.

otherwise, these will need to be modeled separately (e.g. zone temp and occ setpoint together in one abstract type, and zone temp and unoccupied setpoints together in another -- then a single type can implement both pieces of functionality in some non-canonical way, since this is very irregular).

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see this pretty frequently in terminal units where there is a single setpoint during occupied hours, but during unoccupied hours there is a night setback for both heating and cooling. Do they need to be separated into separate abstract types?

- zone_air_unoccupied_heating_temperature_setpoint
- zone_air_unoccupied_cooling_temperature_setpoint
implements:
- OPERATIONAL

RFSS:
description: "Basic combination of return fan run command and status (start/stop)."
is_abstract: true
Expand Down
28 changes: 28 additions & 0 deletions ontology/yaml/resources/HVAC/entity_types/CHB.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
# Copyright 2020 Google LLC
#
# Licensed under the Apache License, Version 2.0 (the License);
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# https://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an AS IS BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

########################
### Canonical Types ###
########################

CHB_ZTOUC_CHWZOUC_PERHWZOUC_CO2M_RMM:
description: "Chilled beam with perimeter heating, CO2 and run mode monitoring."
is_canonical: true
implements:
- CHB
- ZTOUC
- CHWZOUC
- PERHWZOUC
- CO2M
- RMM
6 changes: 6 additions & 0 deletions ontology/yaml/resources/HVAC/entity_types/GENERALTYPES.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -372,3 +372,9 @@ CRREF:
is_abstract: true
implements:
- EQUIPMENT

CHB:
description: "Tag for chilled beams."
is_abstract: true
implements:
- EQUIPMENT
9 changes: 9 additions & 0 deletions ontology/yaml/resources/fields/telemetry_fields.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -1561,3 +1561,12 @@ literals:

## New fields for seismic detector
- seismic_alarm

## New fields for chilled beams
- zone_air_occupied_temperature_setpoint
- zone_air_unoccupied_cooling_temperature_setpoint
- perimeter_heating_water_valve_percentage_sensor
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will this ever exist independently of another valve?

if we know the device lives on a perimeter then would heating_water_valve_percentage_... be sufficient?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Potentially there could be other heating valves, like reheat or four pipe chilled beams.

- perimeter_heating_water_valve_percentage_command
- perimeter_heating_supply_water_temperature_sensor


1 change: 1 addition & 0 deletions ontology/yaml/resources/subfields/subfields.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -170,6 +170,7 @@ descriptor:
ozone: "Highly reactive gaseous compound comprised of three oxygen atoms."
particle: "A very fine clump of solid matter."
outside: "Process or measurement of local atmospheric conditions."
perimeter: "The outermost parts or boundary of an area or object (e.g. a zone)"
phase: "A phase of three-phase power distribution systems."
phase1: "The first (nominally A) phase of three-phase power distribution systems."
phase2: "The second (nominally B) phase of three-phase power distribution systems."
Expand Down