Issue
Bacnet 3rd party controller will not respond to Find New Bacnet Devices (Who-Is/I-Am), so will not come online to Continuum
Environment
Bacnet
MSTP
Continuum
Cause
Some 3rd party bacnet devices can be setup as master or slave. If the bacnet 3rd party bacnet device is setup as a slave device, it will not respond to the mstp token, therefore will not respond to the Who-Is broadcast and will not be able to communicate on the mstp network.
The BACnet MS/TP protocol does not allow a slave only device to respond to a "Who-Is" broadcast.
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.
Slave only devices cannot come online and will require a 3rd party interface to convert to a protocol that can be directly supported by Continuum.
Examples of BACnet MSTP Slaves that are known not to respond to a 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.
Additional Note
In SmartStruxure a "slave only" MSTP device can ba manually created.
