Issue
BACnet 3rd party controller will not respond to Find New BACnet Devices (Who-Is/I-Am), so will not come online to Continuum or EBO
Product Line
EcoStruxure Building Operation, Andover Continuum
Environment
- Building Operation Enterprise Server
- Building Operation Automation Server
- Building Operation Automation Server Premium
- Building Operation Automation Server Bundled
- Building Operation Edge Server - Standard
- Continuum Cyberstation
- Continuum bCX4040 (BACnet)
Cause
BACnet MSTP device can be master or slave. BACnet MSTP slave will only respond to a request from a master device, and will not respond to the Who-Is broadcast so it can not be discovered.
- EBO: EBO does not support slave devices. EBO does not currently have a way to statically configure MAC addresses as it relies on dynamic discovery.
- Continuum: Slave only devices cannot come online.
Resolution
- Check 3rd party device documentation or contact 3rd party device vendor for Master/Slave settings and configure for Master to communicate on a MSTP network.
- Use 3rd party interface to convert to a protocol that can be directly supported by EBO or Continuum.
Examples of BACnet MSTP Slaves that are known not to respond to EBO or Continuum Who-Is request and so not come online are:
- The Babel Buster 485XM from Control Solutions Inc is BTL listed as a BACnet Slave device , their PICs statement can be seen Here.
- Wilo pumps Interface Modules: IF-Modul BACnet & IF-Modul Stratos BACnet, their PICs statement can be seen Here.
