If licensed and running as a BACnet server (typically in addition to a BACnet client), in a few cases it may be needed to make some configuration changes under the Bacnet Comm: Server component.
The Bacnet Comm: Server component has a “Worker” child to queue and process server messages (responses to requests from BACnet clients). In AX-3.8,
an additional “Confirmed Worker” child now separately handles “confirmed type” messages, for example event (alarm) notifications.
A “Worker Pool” component is also available in the AX-3.8 bacnet palette, which you can paste as a child under a Worker.
If a station operates as a BACnet server with a large number of BACnet clients, configuration changes to one or both workers may be beneficial. For related details, see Bacnet Workers.
In some cases, job circumstances require a remote BACnet client to have the ability to reboot the Niagara host (running the station). If so, you must change the “Reinitialize Allowed” property of the Bacnet Comm: Server component—which
is hidden, by default. If you clear the “Hidden” config flag for this property from the Server’s slot sheet, you can change its value
from false to true.
In the Server layer component, this “Reinitialize Allowed” property must be set to true to support any of the following:
-
A remote BACnet client to reinitialize the station (in most cases, this results in a host reboot).
-
Server-side support of “backup and restore” functions from a remote BACnet Workstation client, conforming to BACnet DM-BR-B BIBB.
This requires AX-3.2 or higher. In addition, you may wish to adjust related properties in the BacnetNetwork’s LocalBacnetDevice.
See Local Device backup and restore properties.