AMBR can integrate with building management systems using a BACnet/IP connection over ethernet/RJ45 to each AMBR on-site.
Before you start
Confirm you’ve completed the installation of your system at your site, which means you’ve installed your various fixtures, advanced load controllers or smart drivers and sensors. You’ve confirmed your network has power and the lights are on.
Confirm that an Amatis representative secured your site, moving all devices to the site-specific communication channel.
- A high-speed Internet connection, via WiFi or cellular, configured for DHCP
- Access to Ethernet and electrical outlets, within 200 feet of your site’s Amatis Border Router (AMBR).
- Provide these instructions to your site’s IT personnel to ensure AMBR is able to establish an Internet connection
1. Commission your site and configure the control scenes that you wish to trigger from BACnet.
You’ll need to fully commission your Amatis lighting controls site with the Amatis App to accommodate the local functionality and building automation system functionality. You’ll configure location settings to execute the desired control strategies in your space. Scenes are added to your location as location settings are configured.
2. Obtain the linkIDs of each scene you want to report to BACnet.
- Navigate to Scenes in the main left-hand menu in the Amatis App.
- Each scene has a 3-digit LinkID. Print out this list so you have it handy.
3. Log into the local IP address of your AMBR.
- If you’re not familiar with IP scanners, we recommend Angry IP Scanner for desktop or FING from your mobile device.
- Type in “LMBR-last four digits on your AMBR sticker.local/BACnet.php”
- Type in a BACnet object ID of your choice.
4. Check the points you wish to monitor or adjust via BACnet.
- Upon checking, “OK” will show in the command window
- Refresh the page to show the linkID that correlates with your selections
5. Restart your BACnet to apply any changes. This may take ~5 minutes.
6. Reload the logs by clicking on them to confirm BACnet is running.
7. Generate "BACnet Protocol Implementation Conformance Statement" or epics.
- The epics are what you can expect to see if you discover this device.
- Limit BACnet integration to 1,000 points
- All points are type analog value
- All points are read-write
- BACnet is a slave to the wireless network. If the end device is not reporting data, neither will BACnet
- We DO NOT recommend COV, query points no more than once a minute
- For multi-AMBR installations, each individual AMBR will need a BACnet object ID.