BACnet Is Not Working

If BACnet is not working, then follow the steps below to troubleshoot the problem.

1. Verify that BACnet is enabled as described in Add a BACnet Interface.
   
   

2. Verify that both BACnet enable checkboxes (shown above) are checked, that the Router Configuration device instance is unique (defaults to 20039), and that the Server Configuration (network number that defaults to 8888) are unique in the  BACnet network. If you are using a BACnet tool to look at LON and Modbus devices, then the Server Configuration Starting Device Instance needs to be unique in the  BACnet network.
   
   

3. Verify that the Router Configuration table Network Numbers match what is used for the BACnet networks. This Network Number may not be used for device discovery. Some BACnet features may not work if this is set up incorrectly.
   
   

4. If BACnet was not enabled prior to importing BAC, BTM, or DTP files with BAC and BTM files, then you need to enable BACnet and may need to re-import these files.
   
   

5. Verify that the BACnet service is running by issuing the following console/SSH command (depends on SmartServer version):

   1. For SmartServer release 4.0 and higher, look for bacnet.
      SmartServer release 4.0 and higher

      sudo smartserverctl status

   2. For SmartServer 3.6 and prior releases, look for echbacnet.
      SmartServer 3.6 and prior releases

      sudo supervisorctl status

Instructions are based on BACnet Client or BACnet Server:

BACnet Client – real BACnet devices and you use the SmartServer CMS to read and write to BACnet devices.

1. Verify that BACnet is enabled.
   
   

2. If not, installing BAC files (or DTP files that include BAC files) prior to enabling BACnet will cause the files to never get processed. You will need to re-import the BAC files after enabling the SmartServer for BACnet.
   
   

3. If you manually imported the BAC files, then determine whether these files worked before.
   
   

4. If you are using CMS device discovery, then it may take 10-30 minutes after the CMS Devices widget Discover button () indicates that device discovery completed before all the background processing of new devices is fully done. Therefore, you may not see some devices appearing immediately after device discovery, but appearing later.
   
   

5. Discovered BACnet device BAC files are located in the following folder: /var/apollo/data/bacnetrouter/res. The number of BAC files depends on the number of devices and whether the devices have unique datapoint lists. 

   1. Copy any *.bac to your PC in case you need to contact EnOcean Support.
      
      

6. Determine whether the number of BAC files in the folder above matches the number BACnet device types you see in the CMS Device Types widget.
   
   

7. Check if any BACnet devices show up using MQTT console/ssh command. Press CTRL-C to exit.

   mosquitto_sub -v -t glp/0/+/fb/dev/bacnet/+/if/#

    

8. Verify if datapoint events are working using MQTT console/ssh commands (press CTRL-C exit command):

   1. Show all datapoints (any protocol) with datapoint name "temperature"
      Example SSH/console command to see "Temperature" datapoint updates

      mosquitto_sub -v -t glp/0/+/ev/data/# | grep "temperature/value"

   2. Example SSH/Console command to see same BACnet datapoint from a single device

      mosquitto_sub -v -t glp/0/+/ev/data/# | grep "dev/bacnet/4/if/Temperature/0"

BACnet Server – use a BACnet tool to read and write to LON and Modbus devices that are connected to a SmartServer.

1. Verify that you imported BACnet Type Map (BTM) files for each device type (one per program ID) after you enabled BACnet in the BACnet Configuration page. You must enable BACnet before importing the BTM files.
   
   

2. If you do not see LON/Modbus devices in the BACnet tool, then it is possible that the BTM file is incorrect. You can use the BTM creation tool (a web page that creates BTM files). Once these files are created, you can edit the file and then import the new file into the SmartServer CMS.