Bacnet Server

The BACnet Server acts a BACnet router-gateway (that we can manually configure in FIN) to have virtual networks of virtual devices. This way we can have part of the database created in FIN acting like a BACnet Device.

The BACnet Server is not certified like the BACnet Client.

How to use the BACnet Server

To configure the BACnet Server, follow the below steps.

1. Enable the BACnet Server extension.

2. Select on the Settings App underneath the Advanced Apps

  • This will open a menu, and the user will need to select on the Ext option

3. A menu will appear on the right-hand side, in there the user will need to find the extension called BACnet Server

4. Once found, select on it and enable to extension by clicking on the Enable option

  • If the version number turns green or it is green it signifies that the pod is enabled

5. Then configure BACnet settings in the BACnet Global Config tool.

6. After that, the user will then be able to use the Create BACnet Devices tool to do the rest.

 

 

Supported Objects, Properties, and Services

Supported objects & properties are shown in this spreadsheet.

Supported services are shown in this spreadsheet.

BACnet Server Details

  • An object's PRESENT_VALUE is dependent on PriorityArray and RelinquishDefault properties.

  • All the project devices will be on same local network number and local bind address.

  • All the project devices should have a unique device instance number and MAC address.

  • Points with Str type and missing the enum tag, won't be added to Server Device (strings don’t exist in BACnet protocol).

  • Writing a value of 0 to any specific index of MSV will clear that index (Null).

  • When the Server is enabled, BBMD and FD are not supported and will not process local broadcast messages.

  • BACnet Client and Server cannot communicate with each other on the same PC.

  • If you have two FIN Servers, the Server Network Number has to be different.