Skip to content

Clarification Needed on Effective/ Actual Setpoints #669

@connorjcantrell

Description

@connorjcantrell

The terms "effective setpoint" and "actual setpoint" seems to a lack of consensus on their meaning and/or purpose. Additionally, they are often used interchangeably, leading to potential confusion and misinterpretation.

I personally consider effective and actual setpoint to be equivalent to each other, therefore I will refer to "Effective Setpoint" from this point forward.

Current Understanding:

  • The effective setpoint refers to the "current" (active) setpoint in operation
  • It represents the setpoint value that the system is currently using to control its processes

Example:
A control system might have multiple setpoints, such as Occupied, Unoccupied, Standby, etc. At any given time, the effective setpoint would be the specific value from one of these setpoints depending on the mode that the system is currently using to maintain control.

It's important to note that the Effective Setpoint may not always be a static value directly taken from a predefined setpoint (Unoccupied, Occupied, Standby, etc.). In more advanced systems, and effective setpoint could be dynamically adjusted based on other inputs or conditions. Nonetheless, an Effective Setpoint is typically it's own Analog Value in a Bacnet network.

Blank diagram (1)

Gratned, this is just my own interpretation. I would like to hear differing perspectives and try to reach consensus on the definition of Effective/ Actual Setpoint.

  • Are Effective and Actual Setpoint equivalent?
  • Is Effective Setpoint simply the current setpoint being used by the control process?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions