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

Tpkd day2 new telemetry name #436

Open
wants to merge 14 commits into
base: master
Choose a base branch
from

Conversation

terryterpt
Copy link
Contributor

Added new point name for chiller, cooling tower and pump

Copy link
Collaborator

@tasodorff tasodorff left a comment

Choose a reason for hiding this comment

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

Please provide feedback on the comments, certain usage is unclear.

ontology/yaml/resources/fields/telemetry_fields.yaml Outdated Show resolved Hide resolved
ontology/yaml/resources/fields/telemetry_fields.yaml Outdated Show resolved Hide resolved
ontology/yaml/resources/fields/telemetry_fields.yaml Outdated Show resolved Hide resolved
ontology/yaml/resources/fields/telemetry_fields.yaml Outdated Show resolved Hide resolved
ontology/yaml/resources/fields/telemetry_fields.yaml Outdated Show resolved Hide resolved
ontology/yaml/resources/fields/telemetry_fields.yaml Outdated Show resolved Hide resolved
ontology/yaml/resources/fields/telemetry_fields.yaml Outdated Show resolved Hide resolved
ontology/yaml/resources/fields/telemetry_fields.yaml Outdated Show resolved Hide resolved
ontology/yaml/resources/fields/telemetry_fields.yaml Outdated Show resolved Hide resolved
- compressor_power_sensor
- refrigerant_open_percentage_sensor
- standby_compressor_status
- pump_speed_mode
Copy link
Collaborator

Choose a reason for hiding this comment

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

states?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

i have changed to speed_mode, as this is referred to a component of a device which has states of MANUAL & AUTO.

Copy link
Collaborator

@tasodorff tasodorff left a comment

Choose a reason for hiding this comment

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

Please provide some comments on the fields involving load. I am not following the meaning.

ontology/yaml/resources/fields/telemetry_fields.yaml Outdated Show resolved Hide resolved
ontology/yaml/resources/fields/telemetry_fields.yaml Outdated Show resolved Hide resolved
ontology/yaml/resources/fields/telemetry_fields.yaml Outdated Show resolved Hide resolved
Copy link
Collaborator

@tasodorff tasodorff left a comment

Choose a reason for hiding this comment

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

I have left a lot of comments; I am not convinced most of these points are needed, particularly alarms and the various valve open/closed points; are there not fields that tell us the position of the valve as OPEN/CLOSED?

If this is something we should discuss in a meeting, reach out; I would prefer to purge this list of anything that is unnecessary, and reduce the number of bespoke types and fields that will likely not be reused.

@@ -120,3 +120,17 @@ CDWS_US_MTV_2081_1:
- return_water_isolation_valve_status_3
- supply_water_isolation_valve_status_4
- return_water_isolation_valve_status_4


CDWS_TPKD:
Copy link
Collaborator

Choose a reason for hiding this comment

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

if you remove condensing_water_ can most of this not be modeled with existing abstract types? It is fine if it is not canonical, but most of the fields on here can be covered by proper abstract types.

- run_mode

CH_SS_TPKD:
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. Is the only thing on here that can be modeled as an abstract type really SS?

ontology/yaml/resources/fields/telemetry_fields.yaml Outdated Show resolved Hide resolved
ontology/yaml/resources/fields/telemetry_fields.yaml Outdated Show resolved Hide resolved
ontology/yaml/resources/fields/telemetry_fields.yaml Outdated Show resolved Hide resolved
ontology/yaml/resources/fields/telemetry_fields.yaml Outdated Show resolved Hide resolved

- motor_energy_sensor
- motor_frequency_sensor
- heat_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.

what is the context for this?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

heat_percentage_sensor - Motor Heat Load (Motor heat loss, calculated by output mechanical power from the input electrical power)

Copy link
Collaborator

Choose a reason for hiding this comment

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

wouldnt this be in units of power then? something like heat_loss_thermal_power_sensor?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The unit is percent %

Copy link
Collaborator

Choose a reason for hiding this comment

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

can the existing efficiency_percentage_sensor be used instead?

ontology/yaml/resources/fields/telemetry_fields.yaml Outdated Show resolved Hide resolved
Comment on lines 850 to 885
- condensing_return_water_isolation_control_status:
- LOCAL
- REMOTE
- condensing_return_water_isolation_closed_alarm:
- ACTIVE
- INACTIVE
- condensing_return_water_isolation_open_alarm:
- ACTIVE
- INACTIVE
- condensing_return_water_isolation_reset_alarm:
- ACTIVE
- INACTIVE
- condensing_return_water_isolation_simulation_command:
- ON
- OFF
- condensing_return_water_isolation_alarm:
- ACTIVE
- INACTIVE
- condensing_supply_water_isolation_alarm:
- ACTIVE
- INACTIVE
- condensing_supply_water_isolation_closed_alarm:
- ACTIVE
- INACTIVE
- condensing_supply_water_isolation_open_alarm:
- ACTIVE
- INACTIVE
- condensing_supply_water_isolation_reset_alarm:
- ACTIVE
- INACTIVE
- open_command:
- ON
- OFF
- condensing_supply_water_isolation_valve_run_command:
- ON
- OFF
Copy link
Collaborator

Choose a reason for hiding this comment

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

i am not convinced any of these are needed; some are malformed; some seem unnecessary outside the BMS. what is the use case for them?

Copy link
Contributor Author

@terryterpt terryterpt Feb 15, 2022

Choose a reason for hiding this comment

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

  • condensing_return_water_isolation_closed_alarm
  • condensing_return_water_isolation_open_alarm
  • condensing_return_water_isolation_reset_alarm
  • condensing_return_water_isolation_simulation_command
  • condensing_supply_water_isolation_closed_alarm
  • condensing_supply_water_isolation_open_alarm
  • condensing_supply_water_isolation_reset_alarm
  • condensing_return_water_isolation_alarm
  • condensing_supply_water_isolation_alarm

The points stated above are not necessary so they are removed. The rest of the points should stay as they are isolation value points that can be used to verify why chiller cannot run (if chiller is turned on by mistake)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

There is also no such point name called "condensing_supply_water_isolation_valve_run_command", so it is removed as well

ontology/yaml/resources/fields/telemetry_fields.yaml Outdated Show resolved Hide resolved
@tasodorff
Copy link
Collaborator

@Terry-Ter please see my comments regarding the different fields that look unnecessary. Can you please provide an update?

@terryterpt
Copy link
Contributor Author

@tasodorff I have updated the pull request with the changes for the comments, please review it. Thank you!

Copy link
Collaborator

@tasodorff tasodorff left a comment

Choose a reason for hiding this comment

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

More comments and clarifications required.

ontology/yaml/resources/HVAC/entity_types/ABSTRACT.yaml Outdated Show resolved Hide resolved
ontology/yaml/resources/HVAC/entity_types/ABSTRACT.yaml Outdated Show resolved Hide resolved
- condensing_water_isolation_valve_percentage_sensor

PSMC:
Copy link
Collaborator

Choose a reason for hiding this comment

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

Several questions here:

  1. What kind of pump is this supposed to be? Is it a spray pump? A sweeper pump? Simply calling it pump isn't sufficient.
  2. You have defined speed_mode, which implies its a speed (see here for an example). Looks like you really mean to use control_mode, so this needs to be changed.
  3. You use speed_frequency_setpoint but I think you mean command.
  4. If this is really just speed control for a thing, please follow precedent. See here for an example of how to model speed control.

In general, this appears to be something like VSC, which already exists. I don't know that this type is necessary. Can you please explain?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It is for the chill water pump
The pump_speed_mode is changing the mode between auto and manual, i will change to control mode
The pump_speed_frequency_setpoint is to the user input to set the 0-50Hz which is the speed of pump

Copy link
Collaborator

Choose a reason for hiding this comment

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

you will model chilled water pumps on their own (they are not integral to a device, so you dont need to use the pump subfield. We know its on a pump because its the run command on a pump entity.

They type you are describing seems to be this. Please check and adjust.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The PSMC abstract type has been removed and the PMP types are updated

- pump_speed_frequency_setpoint

CRWISVC:
Copy link
Collaborator

Choose a reason for hiding this comment

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

CWRISOVM2X, to indicate it is actually two sets of valves.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

CRWISVC has been changed to CWRISOVM2X

Copy link
Collaborator

Choose a reason for hiding this comment

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

i dont see the changes reflected here. please make sure the PR is up to date.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Changes has been pushed to the PR

ontology/yaml/resources/HVAC/entity_types/ABSTRACT.yaml Outdated Show resolved Hide resolved
- SS
- PSMC
- VSFC
- CHWISVPCM
Copy link
Collaborator

Choose a reason for hiding this comment

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

same question as above -- they have automatic valves isolating individual pumps?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes, the pump and the valve is inline

########################

TK_TPKD:
description: "Tpkd water tank."
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is this a single tank with three sets of alarms at different positions in the tank? If this were three separate tanks they should be modeled independently.

If this really is one tank, it is probably good to create an abstract type for this. How about something like this:

WLAM:
  description: "Water level alarm monitoring, generally for a water tank."
  is_abstract: true
  uses:
  - water_high_level_alarm
  - water_low_level_alarm
  - water_overflow_level_alarm

WLAM3X:
  description: "Water level alarm monitoring, generally for a water tank with three independent sets of alarms."
  is_abstract: true
  uses:
  - water_high_level_alarm_1
  - water_high_level_alarm_2
  - water_high_level_alarm_3
  - water_low_level_alarm_1
  - water_low_level_alarm_2
  - water_low_level_alarm_3
  - water_overflow_level_alarm_1
  - water_overflow_level_alarm_2
  - water_overflow_level_alarm_3

TK_WLAM3X:
  description: "A water tank with three sets of alarms for high, low, and overflow alerting."
  implements:
  - TK
  - WLAM3X

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The abstract type has been created

ontology/yaml/resources/fields/telemetry_fields.yaml Outdated Show resolved Hide resolved

- motor_energy_sensor
- motor_frequency_sensor
- heat_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.

wouldnt this be in units of power then? something like heat_loss_thermal_power_sensor?

ontology/yaml/resources/fields/telemetry_fields.yaml Outdated Show resolved Hide resolved
@tasodorff
Copy link
Collaborator

@Terry-Ter is there an update for this?

@tasodorff
Copy link
Collaborator

@Terry-Ter please advise on updates

@mschulze17 mschulze17 added info requested from creator Waiting on PR creator to respond to request for further info and removed info requested from creator Waiting on PR creator to respond to request for further info labels May 24, 2022
@terryterpt
Copy link
Contributor Author

heat_percentage_sensor unit is %

Copy link
Collaborator

@tasodorff tasodorff left a comment

Choose a reason for hiding this comment

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

Gave partial review, but the PR is still not updated. Please update the PR (make sure your local changes are reflected here) and see the additional comments I've made. Once those are all complete, I will review again.

ontology/yaml/resources/HVAC/entity_types/ABSTRACT.yaml Outdated Show resolved Hide resolved
ontology/yaml/resources/HVAC/entity_types/ABSTRACT.yaml Outdated Show resolved Hide resolved
- condensing_water_isolation_valve_percentage_sensor

PSMC:
Copy link
Collaborator

Choose a reason for hiding this comment

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

you will model chilled water pumps on their own (they are not integral to a device, so you dont need to use the pump subfield. We know its on a pump because its the run command on a pump entity.

They type you are describing seems to be this. Please check and adjust.

- pump_speed_frequency_setpoint

CRWISVC:
Copy link
Collaborator

Choose a reason for hiding this comment

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

i dont see the changes reflected here. please make sure the PR is up to date.

ontology/yaml/resources/HVAC/entity_types/ABSTRACT.yaml Outdated Show resolved Hide resolved
- condensing_return_water_isolation_valve_status_1
- condensing_return_water_isolation_valve_status_2
- condensing_return_water_isolation_valve_mode
Copy link
Collaborator

Choose a reason for hiding this comment

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

which valve though? you list two. which does it apply to?

- condensing_return_water_isolation_valve_mode

CSWISVC:
Copy link
Collaborator

Choose a reason for hiding this comment

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

the adjustments need to be made still. please ensure this PR is up to date with your local changes.

ontology/yaml/resources/HVAC/entity_types/ABSTRACT.yaml Outdated Show resolved Hide resolved
- condensing_supply_water_isolation_valve_status_1
- condensing_supply_water_isolation_valve_status_2
- condensing_supply_water_isolation_valve_mode
Copy link
Collaborator

Choose a reason for hiding this comment

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

unless you can designate which valve it belongs to, this should be removed.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

it is used for both valves

@charbull
Copy link
Collaborator

charbull commented Nov 7, 2022

@Terry-Ter @tasodorff any updates on this?
@mschulze17 fyi

@terryterpt
Copy link
Contributor Author

Hi Trevor, I have updated the PR for your review, my apologizes on the late update.

@cstirdivant cstirdivant added the Ontology Model Extensions or edits to the ontology model label Jan 12, 2024
@shambergoldstein
Copy link
Collaborator

@terryterpt are the changes in this PR still needed?

@terryterpt
Copy link
Contributor Author

terryterpt commented Oct 28, 2024

Hi @shambergoldstein , yes this PR is still needed

Copy link
Collaborator

Choose a reason for hiding this comment

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

all fields must have states or value ranges, plese adjust accordingly

ontology/yaml/resources/fields/telemetry_fields.yaml Outdated Show resolved Hide resolved
@@ -735,6 +783,9 @@ literals:
- STANDBY
- battery_charge_percentage_sensor
- brightness_percentage_command
- speed_mode:
Copy link
Collaborator

Choose a reason for hiding this comment

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

field has since been added, please add to the states on the existing one as needed and remove this one from PR

ontology/yaml/resources/fields/telemetry_fields.yaml Outdated Show resolved Hide resolved
ontology/yaml/resources/fields/telemetry_fields.yaml Outdated Show resolved Hide resolved
Copy link
Collaborator

@shambergoldstein shambergoldstein left a comment

Choose a reason for hiding this comment

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

Added some comments/requests. In general these files are pretty outdated due to how old the PR is. Please update the branch, resolving any conflicts with the existing files to date, and revisit the more recently added fields and types to see if they can be used in place of some of the ones you have added here.

Copy link
Collaborator

Choose a reason for hiding this comment

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

TK already exists in the global namespace, please remove

Copy link
Collaborator

Choose a reason for hiding this comment

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

TANK.yaml has since been added, please move this type there if needed and remove this file

@@ -104,5 +106,7 @@ volume:
- liters
time:
Copy link
Collaborator

Choose a reason for hiding this comment

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

these have since been added, please remove

@@ -47,6 +48,7 @@ flowrate:
- kilograms_per_hour
frequency:
- hertz: STANDARD
- revolutions_per_minute
Copy link
Collaborator

Choose a reason for hiding this comment

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

this exists under rotationalvelocity, please remove

@@ -37,6 +37,7 @@ energy:
- kilowatt_hours
- megawatt_hours
- therms
- newton_meters
Copy link
Collaborator

Choose a reason for hiding this comment

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

this exists under torque, please remove

@@ -756,6 +807,15 @@ literals:
- position_status
- condensing_water_valve_percentage_sensor
- entering_cooling_coil_temperature_sensor
- condensing_supply_water_isolation_valve_open_status
Copy link
Collaborator

Choose a reason for hiding this comment

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

does the device have a singulary valve status that provides OPEN/CLOSED as its states that can be used in place of these?

- condensing_supply_water_isolation_valve_closed_status
- condensing_supply_water_isolation_valve_open_command
- condensing_supply_water_isolation_valve_closed_command
- entering_chilled_water_temperature_sensor
Copy link
Collaborator

Choose a reason for hiding this comment

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

is this the same as chilled_return_water_temperature sensor?

- condensing_supply_water_isolation_valve_open_command
- condensing_supply_water_isolation_valve_closed_command
- entering_chilled_water_temperature_sensor
- leaving_chilled_water_temperature_sensor
Copy link
Collaborator

Choose a reason for hiding this comment

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

is this the same as chilled_supply_water_temperature sensor?

- condensing_supply_water_isolation_valve_closed_command
- entering_chilled_water_temperature_sensor
- leaving_chilled_water_temperature_sensor
- compressor_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.

compressor_speed_percentage_sensor already exists, please remove

@@ -695,6 +700,49 @@ literals:
- PRESENT
- ABSENT

# Added for TPKD day2
- condensing_supply_water_isolation_valve_mode:
Copy link
Collaborator

Choose a reason for hiding this comment

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

Are these points necessary to bring in? We should be able to tell from the command and status if the valve is in manual override.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
info requested from creator Waiting on PR creator to respond to request for further info Ontology Model Extensions or edits to the ontology model
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants