Page Comparison

...

The BACnet driver also implements the BACnet Server interface. This definition file is used to configure the mapping of Server Items to BACnet objects. Each valid configuration line represents one mapping and thus creates one BACnet object within the NETx Server.
The structure of the BACnet mapping definition file is as follows:' BACnet mapping definitions file
' ItemId;ObjectName;Relinquish-default;COV Increment;
NETx\XIO\KNX\BROADCAST\03/0/010;Light1;false
NETx\XIO\Modbus\Controller1\Input Registers\5000;EnergieValue1;0;0,5

Info
Each line – except comment lines that start with ' – defines a single BACnet mapping and thus one create BACnet object.

Col#	Parameter	Description	Scope	Unit	Default value
1	ItemId	The ItemID of the Server Item that shall be mapped to a BACnet Object.	ItemID	None
2	ObjectName

Here the

The BACnet object name for the newly created BACnet object

has to be defined

. Note that the BACnet object name must be unique within the server.

The object name is optional – if not defined

If omitted, the ItemID is used as object name.	String	None	ItemID
3	Relinquish-default

This optional parameter de- fines

Specifies the relinquish-default

properties

property of the BACnet object. This value is used by the server in case all BACnet priorities are set to NULL.	any	None	0
4	COV Increment

COV Increment is an optional parameter which defines

Specifies the minimum data change that is needed to send BACnet Change-of-Value notifications. If omitted, any data change is transmitted.	Number	None	0
5	Object type

Here,

Specifies the type of the BACnet object

type can be specified that is used to map the server item. If not specified or if the parameter is left empty

. If omitted, the NETx BMS Core Server automatically detects the BACnet object type that fits best to the used Server Item.	BACnet type	None	empty
6	Object ID

Here,

Specifies the

BACnet

Object ID of the created BACnet object

can be specified

. The Object ID and the

object

Object type must be unique within the NETx BMS Core Server. If

not specified or if the parameter is left empty

omitted, an auto-increment ID is used.	BACnet Object ID	None	empty
7	Units			None
8	State Text	Comma-separated list of texts that are mapped to BACnet properties active-text,inactive-text.	String,String	None	empty
9	Description	Text that are mapped to BACnet property description.	String	None	empty

After start-up, the NETx BMS Core Server writes a list of all created BACnet into the following log file:
<WorkspaceDirectory>\LogFiles\xio.BACnet.ObjectList.log

The structure of this file is as follows:' BACnet Object List Wed Jul 02 09:44:33 2014
' Object ID;Object Type;Object Name;Item ID
123123;Device;NETx BMS Server;
0;Binary Input;KNX Dimmer A - Status;NETx\XIO\KNX\192.168.1.36\05/0/001

Info
Each line – except comment lines that start with ' – corresponds to one created BACnet object.

Col#	Name	Description
1	Object ID

This is the

BACnet Object ID of the created BACnet object.
2	Object type

Here, the

BACnet

object

Object type of the created object is listed.
3	ObjectName

This is the

BACnet

object

Object name of the newly created BACnet object.
4	ItemId

This is the

ItemID of the Server Item that is linked to the created BACnet Object.

Versions Compared

Old Version 8

New Version Current

Key