Functional View object (FnctView)

The Functional View (FnctView) object type represents a container allowing organizing and structuring the individual BACnet objects of a Functional Unit. A Functional Unit refers to a logical component representing an encapsulated application unit. A control program includes the control logic of the functional unit. Within the control program, functions access the corresponding BACnet objects by referencing the corresponding View Node Items. This indirection allows engineering the interface of the functional unit by configuring and modifying the relations of the corresponding View Node Items without updating the respective control program references. The FnctView object node type is always Functional.

The FnctView 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.

  • "Object access level" is a configuration property which can only be set up offline (ABT, application configuration).
  • "Object access level" is evaluated by client applications such as Technical Operator, DB-Import, and APOGEE Point Team mapping.

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.

Configuration extension

 

 

"Configuration extension" uniquely identifies the respective BA-Configuration-Extension-XX of a BA-Functional-View-Node-Object.

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.

Comment

A string of printable characters whose content is not restricted. (property is only used in ABT Pro)

Version

Version of a copied object (copied from a library). (property is only used in ABT Pro)

Library reference

Source of a copied object (copied from a library). (property is only used in ABT Pro)