Group Member object (GrpMbr)
The Group Member (GrpMbr) object type represents a container that allows for the distribution of common group data and for the collection of individual group member data by a Group Manager. The group membership of a Group Member object may be configured by means of the properties Group category and Group number. The group membership may be changed by modifying the Group number in the engineering system or online in the runtime system. The Category text property that has no semantic meaning may be used in a client to display the domain and purpose of the group category. Zero, one, or more Group Member objects may exist for a particular Group category and Group number. However, a Group Member object presumes the existence of a corresponding Group Manager object. The GrpMbr object properties are:
✳ Indicates a Siemens proprietary property.
Group category ✳ |
|
|
|---|---|---|
"Group category" allows the room automation station to differentiate between independent application domains such as setpoint grouping, occupancy grouping, blind grouping, and lighting grouping. | ||
Group category number ✳ |
|
|
|---|---|---|
"Group category number" identifies a particular group within a group category such as setpoint group 1 and 2, or lighting group 3, 6, and 7. | ||
Group number ✳ |
|
|
|---|---|---|
"Group number" allows for the configuration of a particular membership within a "Group category", such as setpoint control 1 or 2, or lighting control 1 or 2.
| ||
Group member tag ✳ |
|
|
|---|---|---|
"Group member tag" defines an individual semantic meaning of a group member within its current group membership. The individual members of a particular grouping can be tagged with an individual group member tag in order to distinguish group members within a group, or to address objects of a particular group member. Example: segment(left), segment(central), segment(right) | ||
Context reference ✳ |
|
|
|---|---|---|
"Context reference" indicates the reference to the surrounding application context of a BA-Group-Manager-Object or BA-Group-Member-Object. | ||
Group manager reference ✳ |
|
|
|---|---|---|
"Group manager reference" indicates the reference to the BA-Group-Manager-Object of the group configured in "Group category" and "Group number". If "Group number" is modified, the Group-Member-Object will clear "Group manager reference" and ascertain the reference to the new BA-Group-Manager-Object. | ||
Group manager context ✳ |
|
|
|---|---|---|
"Group manager context" indicates the reference to the surrounding application context of the BA-Group-Manager-Object of the group configured in "Group category" and "Group number". If "Group number" is modified, the Group-Member-Object will clear "Group manager context" and ascertain the reference to the new BA-Group-Manager-Object. | ||
State flag ✳ |
|
|
|---|---|---|
"State flag" represents four boolean flags ("Out of service", "Overridden", "Fault", "In-Alarm") that indicate the general status of an object. | ||
Reliability |
|
|
|---|---|---|
'Reliability' indicates whether the property value 'Present value' is reliable. If the 'Present value' is not reliable, the property 'Reliability' indicates the cause of the fault and the bit "Fault" of the state indication is set to 'True'. In a normal case, the property 'Reliability' is set to "No fault". | ||
Property ID: 103 | ||
Out of service |
|
|
|---|---|---|
"Out of service" allows decoupling the object from being modified by a control program, system program or peripheral device.
| ||
Property ID: 81 | ||
Related object reference ✳ |
|
|
|---|---|---|
"Related object reference" includes an ordered list of Object-Property-References. | ||
Related object reliability ✳ |
|
|
|---|---|---|
"Related object reliability" includes an ordered list of Reliability-Values. | ||
Group operation ✳ |
|
| |
|---|---|---|---|
"Group operation" includes an ordered list of operations and indicates the operation to be performed on the respective Object-Property-Reference. Range: write, update, read | |||
Write | Write or release the referenced target object property when receiving a distribute-Group-Data from a BA-Group-Manager-Object with the value and priority included in Common-Group-Data. | ||
Update | Update the referenced target object property when receiving a distribute-Group-Data from a BA-Group-Manager-Object with the value included in Common-Group-Data. The referenced target object has to be located on the same Building Automation Device. | ||
Read | Read the referenced target object property and send property value changes as Collected-Member-Data to the BA-Group-Manager-Object to collect group member data. | ||
Group data tag ✳ |
|
|
|---|---|---|
"Group data tag" identifies and labels the system-wide application-oriented purpose and usage of a common group value (Value, Priority, Reliability). Example: 1: Outside temperature; 2: Setpoint heating; etc. | ||
Substitute value ✳ |
|
|
|---|---|---|
"Substitute value" includes an ordered list of Default-Value.
| ||
Substitute priority ✳ |
|
|
|---|---|---|
"Substitute priority" includes an ordered list of Default-Priority.
| ||
Collected data sequence number ✳ |
|
|
|---|---|---|
"Collected data sequence number" indicates the current sequence number used by the BA-Group-Member-Object to label the last collected data message. | ||
Event state |
|
|
|---|---|---|
"Event state" provides a way to determine if this object has an active event state associated with it. The "Event state" property indicates the event state of the object. Changes in the "Event state" property to the value FAULT are considered to be fault events. If the object does not support intrinsic reporting, then the value of this property is NORMAL. | ||
Property-ID: 36 | ||
Object access level ✳ |
|
| ||
|---|---|---|---|---|
"Object access level" defines the instance-specific object access level. "Object access level" is used for generic filtering and processing an object by a client application.
| ||||
Access level | Name | Description | ||
7 | Basic operation | Access to BACnet objects and properties for a room user e.g. data points visible on a room unit. | ||
6 | Standard operation | Access to BACnet objects and properties for standard operation and monitoring (daily business), .e.g. room and plant information on a management station. | ||
5 | Extended operation | Access to BACnet objects and properties for extended operation and monitoring such as network and device objects. All I/Os are visible | ||
4 | Administrator | Not used by HQ solutions yet. | ||
3 | Basic service | Access to BACnet objects and properties used for commissioning, e.g. configuration value extensions, I/O extensions, etc. | ||
2 | Extended service | Not used by HQ solutions yet. | ||
1 | Internal | Access to all BACnet objects and properties for very specialized actions e.g. during development. | ||
Object usage ✳ |
|
|
|---|---|---|
"Object usage" indicates whether the object is used or unused. The "Object usage" property can hide or display respective objects and their functionality in a client. For example, room functionality can be marked for flexible room arrangements as used/unused. An object that is marked as unused behaves as if the object does not exist. | ||
Property ID: 4930 | ||
Description |
|
|
|---|---|---|
"Description" is a string of printable characters whose content is not restricted. | ||
Object name |
|
|
|---|---|---|
"Object name" represents a name for the object that is unique internetwork-wide. The minimum length of the string is one character. The set of characters used in the "Object name" are restricted to printable characters. | ||
Object identifier |
|
|
|---|---|---|
"Object identifier" is a numeric code that is used to identify the object. It must be unique internetwork-wide. | ||
Object type |
|
|
|---|---|---|
"Object type " indicates membership in a particular object type class. E.g. "Analog input", "Binary output", "Event enrollment", "Trend log", etc. | ||
Building automation profile ✳ |
|
|
|---|---|---|
"Building automation profile" is an enumeration that indicates a particular type of Siemens proprietary object. Siemens objects are based on standard BACnet objects. For example, Siemens Analog Input, Analog Output, Analog Calculated Value, and Analog Configuration Value are based on standard Analog Input, Analog Output, and Analog Value BACnet objects. | ||
Profile name |
|
|
|---|---|---|
"Profile name" indicates the name of an object profile to which this object conforms. To ensure uniqueness, a profile name must begin with a vendor identifier code followed by a dash. All subsequent characters are administered by the organization registered with that vendor identifier code. The vendor identifier code that prefixes the profile name indicates the organization that publishes and maintains the profile document named by the remainder of the profile name. | ||