Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Location:


<WorkspaceDirectory>\DataFiles\xio.BACnet.ObjectDefinitions.dat


The BACnet interface provides the opportunity to read and write BACnet Objects and their BACnet Properties. 
The structure of the BACnet object definition file is as follows:

' BACnet object configuration file
' DeviceId;ObjectId;ObjectType;ObjectName;WritePriority;PollingInterval;Persistent;Historical;Synchronize;COVType
257653;0;Binary Input;BINARY_INPUT_0;15;5000;F;F;F
257653;0;Binary Output;BINARY_OUTPUT_0;15;5000;F;T;F
2098178;1;Analog Input;B'AI1;15;5000;F;T;F
2098178;1;Analog Output;B'AO1;15;5000;F;F;F
2098178;1;Analog Value;B'AVAL1;15;5000;F;F;F
2098178;1;Binary Value;B'BVAL1;15;5000;F;F;F
2098178;2;Accumulator;B'ACC1;15;5000;F;F;F
2098178;2;Pulse Converter;B'PC1;15;5000;F;F;F
2098178;1;Multi-State Input;B'MSI1;15;5000;F;F;F
2098178;1;Multi-State Output;B'16;15;5000;F;F;F
2098178;1;Multi-State Value;B'17;15;5000;F;F;F
Each line – except comment lines that start with ' – defines a single BACnet object.
! The BACnet object definitions within this file can automatically be set by using the BACnetExplorer. Therefore, editing it manually is not necessary in general.






1DeviceId
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.
2ObjectId
This parameter refers to the BACnet Object ID of the defined object.
3ObjectType
This attribute defines the BACnet Object type.
4ObjectName
This identifier specifies the BACnet Object Name of the BACnet Object.
5WritePriority
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.
6PollingInterval
If the object does not support Change of Value (COV) subscription, this parameter defines the interval (in ms) which is used to poll the object's present value. "'0"' deactivates polling for this object.
7Persistent
This parameter specifies whether the value of the datapoint is persistent (restored from the database after server start up ) or not.
8Historical
This parameter specifies whether historical values of the datapoint are stored within the database or not.
9Synchronize
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.
10COV Type
This parameter specified the type of COV subscription that shall be used for the given object. "'Unconfirmed"' uses unconfirmed COV subscription, "'Confirmed"' uses confirmed COV subscription, and "'Disabled"' deactivates COV subscription at all. The default value (emtpy value) is "'Unconfirmed"'.
11Proprietary properties
This column is used to specify the properties of proprietary object types that shall be shown as Server Items. It is a comma separated list E.g. 6704,6708
12Proprietary data types

13Proprietary access

  • No labels