There are at least three frozen Worker slots under a BacnetNetwork, as follows:
-
At least two Worker slots directly for a BacnetNetwork.
By default, these BacnetNetwork worker slots have the “hidden” flag set. To see/access them as shown above, you must first unhide (clear this flag) from the network’s slot sheet.
-
Worker — “Worker Thread Name” property value of
BacnetNetwork:workerThis worker processes most BACnet client read messaging.
-
Write Worker — “Worker Thread Name” property value of
BacnetNetwork:writeWorkerThis worker processes most BACnet client write messaging.
-
COV Worker (AX-3.8 only) “Worker Thread Name” property value of
BacnetNetwork:covWorker. This worker processes most BACnet client COV messaging.
-
-
At least one visible slot under the Bacnet Comm, Server component.
-
Worker — has “Worker Thread Name” property value of
server:workerThis worker processes most BACnet server messaging.
-
Confirmed Worker (AX-3.8 only) — has “Worker Thread Name” property value of
server:confirmedWorker
In a AX-3.8 station with both Server workers, “Worker” processes unconfirmed server messaging, e.g. “Who-Is” and “Who-Has” responses or unconfirmed COV server messaging. Whereas, “Confirmed Worker” handles all confirmed server messaging, including event (alarm) notifications, confirmed COV, and so on. Separate workers help to prevent certain confirmed event notifications from blocking the processing of all incoming requests to the BACnet server layer.
-
