BACnet.Protocol.ObjectTypes.DatePatternValue (bacstack v0.1.0-dev.1)

Copy Markdown View Source

The Date Pattern Value object holds a single recurring date pattern expressed with the rich BACnet date wildcards. It is the pattern version of the simple BACnet.Protocol.ObjectTypes.DateValue object.

The object can be made commandable via a priority array so that the effective pattern itself can be overridden by operators or other logic. It is a pure data holder; its present_value is the pattern definition and has no direct effect until referenced by another object or used by logic.

Object Description (ASHRAE 135)

The Date Pattern Value object type defines a standardized object whose properties represent the externally visible characteristics of a named data value in a BACnet device.

Date Pattern objects can be used to represent multiple recurring dates based on rules defined by the pattern of individual fields of the date, some of which can be special values like "even months", or "don't care".

Behaviour and Operation

Date Pattern Value objects hold a single recurring date pattern (using the full BACnet wildcard rules). They are passive data holders. A BACnet device can use a Date Pattern Value object to make any kind of date data value accessible to other BACnet devices.

The pattern itself (present_value) can be written directly unless the object has been made commandable with a priority array. In the commandable case, the effective pattern is taken from the priority array / relinquish default and direct writes to present_value are not permitted.

Evaluation of the pattern against the current date is performed by consumers of the object (i.e. the device clock and schedule engine), not by the value object itself. The object simply stores and exposes the pattern definition.

Developer Implementation Notes (geared to device server / application authors)

The generated code handles storage + basic mechanics (validation, implicit_relationships, readonly annotations as hints to your server, etc.). You must drive "special" live properties and side effects yourself, analogous to maintaining present_value on inputs via update_property/3 (never direct mutation). Read notes below + generated tables for details.

Special / live properties and expected developer behaviour

  • present_value: The recurring date pattern. Dev must: Writers (app or clients) set the pattern (directly or via priority if commandable). Consumers (your custom logic) read it and evaluate it using the standard wildcard rules. The object does not evaluate; it just holds the definition.

  • priority_array, relinquish_default: Optional commandability. Dev must: Same rules as other commandable values: use set_priority/3 etc. for sources

  • status_flags, out_of_service, reliability: Dev must: out_of_service allows forcing a pattern for test, if not commandable. Reliability for bad source of the pattern value. in_alarm/fault/out_of_service bits of status_flags auto-managed.

Commandability and Priority Arrays

Value objects can have a priority_array (making them commandable).

Examples

Creating a Date Pattern Value:

iex> {:ok, dpv} = BACnet.Protocol.ObjectTypes.DatePatternValue.create(100, "Recurring", %{present_value: %BACnet.Protocol.BACnetDate{year: :unspecified, month: :unspecified, day: :unspecified, weekday: :unspecified}}); dpv.object_name
"Recurring"

See Also

The following part has been automatically generated.

Click to expand This module defines a BACnet object of the type `date_pattern_value`. The following properties are defined: | Property | Revision | Required | Readonly | Protected | Intrinsic | |----------|----------|----------|----------|-----------|-----------| | description | | | | | | | event_state | | | | | | | object_instance | | X | X | | | | object_name | | X | X | | | | out_of_service | | | | | | | present_value | | X | | | | | priority_array | | | X | | | | profile_location | 19 | | | | | | profile_name | | | | | | | reliability | | | | | | | reliability_evaluation_inhibit | | | | | | | relinquish_default | | | | | | | status_flags | | X | X | | | | tags | 19 | | | | | The following properties have additional semantics: | Property | Has Default | Has Init | Implicit Relationships | Validators | Annotations | |----------|-------------|----------|------------------------|------------|-------------| | profile_location | | | | Fun | `revision: 19` | | reliability | | | reliability_evaluation_inhibit | | | | tags | | | | | `revision: 19` | The following table shows the default values and/or init functions: | Property | Default Value | Init Function | |----------|---------------|---------------|

Summary

Types

common_object_opts()

Common object options for creation - all are optional.

object_opts()

Options accepted when creating or configuring a Date Pattern Value object.

property_name()

Available property names for this object.

property_update_error()

The structure for property errors.

t()

Represents a Date Pattern Value object. All keys should be treated as read-only, all updates should go only through update_property/3.

Functions

add_property(object, property, value)

Adds an optional property to an object. Remote objects can not be mutated using this operation.

create(instance_number, object_name, properties \\ %{}, opts \\ [])

Creates a new object struct with the defined properties. Optional properties are not created when not given, only required, given and dependency properties are created. Properties with a value of nil are ignored.

get_all_properties()

Auto generated function to get the names of all properties this object supports.

get_annotation(name)

Auto generated function to get the annotations for the given property name.

get_annotations()

Auto generated function to get the list of annotations for each property.

get_cov_properties()

Auto generated function to get the names of properties used for COV reporting.

get_intrinsic_properties()

Auto generated function to get the names of intrinsic properties.

get_object_identifier(object)

Get the BACnet object identifier.

get_optional_properties()

Auto generated function to get the names of optional properties.

get_priority_value(object)

Get the active priority value from the priority array, or nil.

get_properties(object)

Get the list of properties the object has.

get_properties_type_map()

Auto generated function to get a map of property name to type.

get_property(object, property)

Get a property's value from an object.

get_protected_properties()

Auto generated function to get the names of protected properties.

get_readonly_properties()

Auto generated function to get the names of readonly properties.

get_required_properties()

Auto generated function to get the names of required properties.

has_priority_array?(object)

Checks whether the given object has a priority array.

has_property?(object, property)

Checks if the given object has the given property.

property_writable?(object, property)

Checks if the given property is writable.

remove_property(object, property)

Removes an optional property from an object. This function is idempotent. Remote objects can not be mutated using this operation.

set_priority(object, priority, value)

Sets the given priority in the priority array of an object. This function also updates the present value.

supports_intrinsic()

Auto generated function to check whether the object type supports intrinsic reporting.

update_property(object, property, value)

Updates a property of an object. To update the priority array, use set_priority/3 instead.

Types

common_object_opts()

@type common_object_opts() ::
  {:allow_numeric_constants, boolean()}
  | {:allow_unknown_properties, boolean()}
  | {:ignore_unknown_properties, boolean()}
  | {:revision, BACnet.Protocol.Constants.protocol_revision()}
  | {:skip_property_validation_remote_object, boolean() | :value}

Common object options for creation - all are optional.

  • allow_numeric_constants - Constants are atoms and thus unknown constants or vendor extensions are integers and thus are rejected. Enabling this option will allow integers (non_neg_integer()) for properties with a Constants.type() spec.
  • allow_unknown_properties - Properties that are unknown to the object implementation are usually rejected. With this option, unknown properties (numeric identifiers usually means we dont know them) are accepted and put into a separate map. This does mean we can not validate or write them. Types of the values can be anything at this point. While you can read unknown properties with atom or integer as property identifier, you can only remove numeric unknown property identifiers from an object. Property identifiers of type atom are only accepted, if it is a remote object (object implementation is only enforced if it is a local object). Numeric property identifiers are accepted regardless of remote object or not. For remote objects, this means you have to write "raw values" (usually Encoding structs).
  • ignore_unknown_properties - Properties that are unknown to the object implementation are usually rejected. With this option, unknown properties get ignored, as if they were not specified.
  • revision - The BACnet protocol revision to check required properties against. Optional properties are regardless of revision available. See BACnet.Protocol.Constants.protocol_revision/0 for the available revisions.
  • skip_property_validation_remote_object - Skips property validation for remote objects. Sometimes it is possible that the value is invalid as per BACnet specification (i.e. value 0 for a multistate object), but you still want those to be represented. Value true neither type nor value are validated. Value :value means the type is still validated and only the value validator is not run (if present). The property's validator_fun will also be skipped.

object_opts()

@type object_opts() :: common_object_opts()

Options accepted when creating or configuring a Date Pattern Value object.

property_name()

@type property_name() ::
  :description
  | :event_state
  | :object_instance
  | :object_name
  | :out_of_service
  | :present_value
  | :priority_array
  | :profile_location
  | :profile_name
  | :reliability
  | :reliability_evaluation_inhibit
  | :relinquish_default
  | :status_flags
  | :tags

Available property names for this object.

property_update_error()

@type property_update_error() ::
  {:error,
   {error :: atom(),
    property :: BACnet.Protocol.Constants.property_identifier()}}

The structure for property errors.

t()

@type t() :: %BACnet.Protocol.ObjectTypes.DatePatternValue{
  _metadata: internal_metadata(),
  _unknown_properties: %{
    optional(atom() | non_neg_integer()) =>
      term()
      | BACnet.Protocol.ApplicationTags.Encoding.t()
      | [BACnet.Protocol.ApplicationTags.Encoding.t()]
  },
  description: String.t() | nil,
  event_state:
    BACnet.Protocol.Constants.event_state()
    | (reserved_or_vendor_extension :: non_neg_integer())
    | nil,
  object_instance: non_neg_integer(),
  object_name: String.t(),
  out_of_service: boolean() | nil,
  present_value: BACnet.Protocol.BACnetDate.t(),
  priority_array:
    BACnet.Protocol.PriorityArray.t(BACnet.Protocol.BACnetDate.t()) | nil,
  profile_location: String.t() | nil,
  profile_name: String.t() | nil,
  reliability:
    BACnet.Protocol.Constants.reliability()
    | (reserved_or_vendor_extension :: non_neg_integer())
    | nil,
  reliability_evaluation_inhibit: boolean() | nil,
  relinquish_default: BACnet.Protocol.BACnetDate.t() | nil,
  status_flags: BACnet.Protocol.StatusFlags.t(),
  tags: BACnet.Protocol.BACnetArray.t(BACnet.Protocol.NameValue.t()) | nil
}

Represents a Date Pattern Value object. All keys should be treated as read-only, all updates should go only through update_property/3.

Properties which are for Intrinsic Reporting are nil, if disabled. If Intrinsic Reporting is enabled on the object, then the properties can not be nil.

For commandable objects (objects with a priority array), the present value property is protected.

Functions

add_property(object, property, value)

@spec add_property(t(), BACnet.Protocol.Constants.property_identifier(), term()) ::
  {:ok, t()} | property_update_error()

Adds an optional property to an object. Remote objects can not be mutated using this operation.

Please note that properties of services can not be dynamically added and instead the object must be newly created using create/4.

create(instance_number, object_name, properties \\ %{}, opts \\ [])

@spec create(
  non_neg_integer(),
  String.t(),
  %{optional(property_name() | atom() | non_neg_integer()) => term()},
  [object_opts() | internal_metadata()]
) :: {:ok, t()} | property_update_error()

Creates a new object struct with the defined properties. Optional properties are not created when not given, only required, given and dependency properties are created. Properties with a value of nil are ignored.

Only properties that are required for specific services (i.e. Intrinsic Reporting) are automatically created.

get_all_properties()

@spec get_all_properties() :: [BACnet.Protocol.Constants.property_identifier()]

Auto generated function to get the names of all properties this object supports.

get_annotation(name)

@spec get_annotation(property_name()) :: [term()]

Auto generated function to get the annotations for the given property name.

get_annotations()

@spec get_annotations() :: [{name :: property_name(), values :: [term()]}]

Auto generated function to get the list of annotations for each property.

get_cov_properties()

@spec get_cov_properties() :: [BACnet.Protocol.Constants.property_identifier()]

Auto generated function to get the names of properties used for COV reporting.

get_intrinsic_properties()

@spec get_intrinsic_properties() :: [BACnet.Protocol.Constants.property_identifier()]

Auto generated function to get the names of intrinsic properties.

get_object_identifier(object)

@spec get_object_identifier(t()) :: BACnet.Protocol.ObjectIdentifier.t()

Get the BACnet object identifier.

get_optional_properties()

@spec get_optional_properties() :: [BACnet.Protocol.Constants.property_identifier()]

Auto generated function to get the names of optional properties.

get_priority_value(object)

@spec get_priority_value(t()) ::
  {priority :: 1..16, value :: BACnet.Protocol.BACnetDate.t()} | nil

Get the active priority value from the priority array, or nil.

get_properties(object)

@spec get_properties(t()) :: [BACnet.Protocol.Constants.property_identifier()]

Get the list of properties the object has.

get_properties_type_map()

@spec get_properties_type_map() :: map()

Auto generated function to get a map of property name to type.

get_property(object, property)

@spec get_property(
  t(),
  BACnet.Protocol.Constants.property_identifier() | non_neg_integer()
) ::
  {:ok, term()} | property_update_error()

Get a property's value from an object.

get_protected_properties()

@spec get_protected_properties() :: [BACnet.Protocol.Constants.property_identifier()]

Auto generated function to get the names of protected properties.

Protected is an annotation and the object modules prevent writing to this property directly in code. The protected properties are either written on creation or updated automatically depending on other properties being written to. Some properties are only written once at creation and never updated.

get_readonly_properties()

@spec get_readonly_properties() :: [BACnet.Protocol.Constants.property_identifier()]

Auto generated function to get the names of readonly properties.

Readonly is only an annotation that the property should be write protected on the BACnet side, there is no actual write protection in the object. This is a hint to the device server. If you need actual write protection, see protected.

get_required_properties()

@spec get_required_properties() :: [BACnet.Protocol.Constants.property_identifier()]

Auto generated function to get the names of required properties.

has_priority_array?(object)

@spec has_priority_array?(t()) :: boolean()

Checks whether the given object has a priority array.

has_property?(object, property)

@spec has_property?(t(), BACnet.Protocol.Constants.property_identifier()) :: boolean()

Checks if the given object has the given property.

See BACnet.Protocol.ObjectsUtility.has_property?/2 for implementation details.

property_writable?(object, property)

@spec property_writable?(t(), BACnet.Protocol.Constants.property_identifier()) ::
  boolean()

Checks if the given property is writable.

Check BACnet.Protocol.ObjectsUtility.property_writable?/2 for a basic run-down.

remove_property(object, property)

@spec remove_property(
  t(),
  BACnet.Protocol.Constants.property_identifier() | non_neg_integer()
) ::
  {:ok, t()} | property_update_error()

Removes an optional property from an object. This function is idempotent. Remote objects can not be mutated using this operation.

Please note that properties of services can not be dynamically removed and instead the object must be newly created using create/4. Required properties can not be removed.

set_priority(object, priority, value)

@spec set_priority(t(), 1..16, BACnet.Protocol.BACnetDate.t() | nil) ::
  {:ok, t()} | property_update_error()

Sets the given priority in the priority array of an object. This function also updates the present value.

supports_intrinsic()

@spec supports_intrinsic() :: boolean()

Auto generated function to check whether the object type supports intrinsic reporting.

update_property(object, property, value)

@spec update_property(t(), BACnet.Protocol.Constants.property_identifier(), term()) ::
  {:ok, t()} | property_update_error()

Updates a property of an object. To update the priority array, use set_priority/3 instead.