Apart from the different manager views on the BacnetAwsNetwork, and device extensions Trend Logs and Config for each BacnetAwsDevice (supporting additional BACnet object types), a BacnetAwsNetwork also supports the following:
If needed, in a BacnetAwsNetwork (or BacnetOwsNetwork) you can configure for more than two processing threads for the Poll Service used by the Bacnet Comm’s network port—that is, the IpPort and/or Ethernet port. Find this on the property sheet of the Poll Scheduler component, as shown in Figure A.18.
In a regular BacnetNetwork (typically hosted by a JACE), this property is fixed (read-only) at 2 threads. In some cases with the BacnetAwsNetwork hosted by the PC platform of a BACnet AWS Supervisor (or with the BacnetOwsNetwork hosted by the PC platform of a BACnet OWS Supervisor), increasing this number over 2 may provide some performance enhancements.
For related details, see Basic Bacnet polling design.
If needed, in a BacnetAwsNetwork (or BacnetOwsNetwork) you can configure the number of processing threads to be used for proxy point writes. In a regular BacnetNetwork (typically hosted by a JACE), this is fixed at a single thread: the “writeWorker” thread.
For any Bacnet network, the “WriteWorker” component is a “hidden” slot. To access it from the property sheet, go to the network’s slot sheet and clear the hidden flag, as shown in Figure A.19.
Then from the network’s property sheet, expand the
Write Worker container for child properties.
As shown in Figure A.20, the default “Max Threads” value for the Write Worker in a BacnetAwsNetwork is 4 threads. You can adjust it upwards if needed. This may be useful if you have a large number of writable Bacnet proxy points that are configured in their tuning policy to writeOnStart.
Copyright © 2000-2014 Tridium Inc. All rights reserved.