Collection View object (ColView)
The Collection View (ColView) object type consists of a set of members that collectively represent a device. A ColView object is a generic container used to group things together.
To achieve the independency of a control program from the number of sensors and actuators used in a project, a View Node Object classified as collection is used to aggregate a varying number of objects associated by connects-Relations. Within the control program, an application-oriented function is used to iterate over the collection to compute a resulting value of all aggregated objects representing sensors or to output a common value to all aggregated objects representing actuators. A Calculated Value connected on index 1 of the collection object represents the computed value.
The Collection View object properties are:
✳ Indicates a Siemens proprietary property.
Node type |
|
|
|---|---|---|
"Node type" provides a general classification of the object in the hierarchy of objects. It is intended as a general suggestion to a client application about the contents of a "Structured view" object, and is not intended to convey an exact definition. Further refinement of classification is provided by the "Node subtype" property. | ||
Node subtype |
|
|
|---|---|---|
"Node subtype" is a string of printable characters whose content is not restricted. It provides a more specific classification of the object in the hierarchy of objects, providing a short description of the item represented by the node. | ||
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 | ||
Subordinate list |
|
|
|---|---|---|
"Subordinate list" defines the members of the current "Structured view" object. By including references to child "Structured view" objects, multilevel hierarchies can be created. If the optional device identifier is not present for a particular "Subordinate list" member, then that object must reside in the same device that maintains the "Structured view" object. If "Subordinate list" is writable it can optionally be restricted to reference-only objects in the local device. To avoid recursion, it is suggested that a single "Structured view" object should be referenced only once in the hierarchy. If the size of the "Subordinate list" array is changed, the size of the "Subordinate annotations" array, if present, is also changed to the same size. Uninitialized "Subordinate list" array elements are given the instance number 4194303. A "Subordinate list" array element whose instance number is equal to 4194303 is considered uninitialized and is ignored. | ||
Subordinate annotations |
|
|
|---|---|---|
"Subordinate annotations" defines a text string description for each member of the "Subordinate list". The content of these strings is not restricted. If the size of this array is changed, the size of the "Subordinate list" array is also changed to the same size. | ||
Subordinate attributes ✳ |
|
|
|---|---|---|
"Subordinate attributes" contains an ordered list of Item attributes characterizing each node item. | ||
Main value index ✳ |
|
|
|---|---|---|
"Main value index"allows specifying an index of the "Diagnostics values" property values. The item value is used to update the "Present value" property of the object. | ||
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. | ||
Comment |
|
|
|---|---|---|
A string of printable characters whose content is not restricted. | ||