Location: <WorkspaceDirectory>\DataFiles\xio.BACnet.ObjectDefinitions.dat
The BACnet interface provides the opportunity to read and write BACnet Objects and their BACnet Properties.
The BACnet object definitions within this file can automatically be set by using the BACnetExplorer. Therefore, editing it manually is not necessary in general.
The structure of the BACnet object definition file is as follows:
| Col# | Parameter | Description | Scope | Unit | Default |
|---|---|---|---|---|---|
| 1 | DeviceId | The BACnet Device ID of the device which holds the BACnet Object. This name must match the device ID used in the BACnet device configuration. | |||
| 2 | ObjectId | This parameter refers to the BACnet Object ID of the defined object. | |||
| 3 | ObjectType | This attribute defines the BACnet Object type. | BACnet Object type | ||
| 4 | ObjectName | This identifier specifies the BACnet Object Name of the BACnet Object. | |||
| 5 | WritePriority | Here, the default write priority de- fined in the BACnet configuration file can be overwritten for each individual object. If not specified, the default write priority is used. As an alternative, a list of write priorities (separated by ",") can be specified, too. For each defined write priority, the server creates two additional server item – one for writing the datapoint value with the specified priority and one for resetting the priority again. Using this mechanism, multiple BACnet priorities can be used at the same time. | 16 | ||
| 6 | PollingInterval | If the object does not support Change of Value (COV) subscription, this parameter defines the interval which is used to poll the object's present value. A value of 0 deactivates polling for this object. | ms | 5000 | |
| 7 | Persistent | This parameter specifies whether the value of the datapoint is persistent (restored from the database after server start up ) or not. | F | ||
| 9 | Synchronize | If this parameter is set to "T", the value is synchronized between the main and backup server (if present). This will work only if synchronize is enabled in the NMESH configuration of the NETx BMS Core Server. | T | ||
| 10 | COV Type | Specifies the type of COV subscription that shall be used for the given object. |
| Unconfirmed | |
| 11 | Proprietary properties | This column is used to specify the properties of proprietary object types that shall be shown as Server Items. Properties must be identified by their name (e.g. "present-value"; a full list of supported types can be found here). A proprietary property ist specified by "Proprietary_<Prop ID>" (e.g. "Proprietary_6704"). To specify multiple properties, a comma separated list has to be used (e.g. "Proprietary_6704,present-value,Proprietary_6710"). | A comma-separated list of the following
| ||
| 12 | Proprietary data types | Within this column, the data types of proprietary properties have to be specified. A comma separated list has to be used if multiple properties are used. The length of the list must be equal to the list used in column "Proprietary properties". For standard properties, the list entry can be left empty (e.g. "Boolean,,Unsigned Int") | A comma-separated list of the following:
| ||
| 13 | Proprietary access | Within this column, the access rights of proprietary properties have to be specified. A comma separated list has to be used if multiple properties are used. The length of the list must be equal to the list used in column "Proprietary properties". For standard properties, the list entry can be left empty (e.g. "R,,RW") | A comma-separated list of the following
|