(Optional) Setting up the BACnet Server

Owned by Nina Cardillo
Last updated: 11-Jul-2024
2 min read
BACnet Router and Server Configuration is available with SmartServer 2.5 and higher.

Using the SmartServer BACnet Server, you can provide a BACnet interface to any field devices available on your SmartServer, independent of the protocols used to communicate with the devices. As a result, you can provide a BACnet interface to EnOcean, LON, LoRaWAN, and Modbus devices that you have provisioned on your SmartServer.  You can also provide a customized BACnet interface to BACnet devices that you have provisioned on your SmartServer.

This section consists of the following:

Configuring the SmartServer BACnet Server

To configure the SmartServer BACnet Server, follow these steps:

  1. Create the BACnet Type Map (BTM) file for the interface. See (Optional) Creating a BACnet Type Map (BTM).

  2. Set up BACnet as described in Add a BACnet Interface.

  3. Open the SmartServer CMS.

  4. Click the Import / Export button () on the CMS dashboard.




    The Import / Export dialog appears.



  5. Drag a BACnet type map (.btm) file to the Drop Files to Import or Browse box, or click Browse to browse for the file on your web browser host.



  6. Click Import.

Interacting with BACnet Devices from a BACnet Workstation

Once you have enabled BACnet and imported BACnet type maps (.btm) for your devices, you can interact with the devices from a BACnet workstation. Below is an example of the YABE (Yet Another BACnet Explorer) tool interacting with EnOcean devices using the BACnet Server on a SmartServer. See (Optional) Using YABE and Foreign Device Registration for more information.


YABE tool user interface


You can also use the SmartServer BACnet Server to provide an interface to intrinsic reporting for the BACnet objects configured in the server. In addition, you can use the BACnet Server to interface with the IAP scheduler and calendar using BACnet Scheduler and BACnet Calendar objects.  The BACnet Server automatically creates BACnet Scheduler and BACnet Calendar objects for any schedules defined by IAP applications or the CMS Calendar widget.