Each BTL-certified BACnet Supervisor type (OWS, AWS) uses much of the same software as the regular BACnet driver, based on the (core) bacnet module. Other modules “extend” for enhanced operations.

For convenience, the palette in the bacnetOws and bacnetAws modules include all available components, including all the bacnet components (except server-related ones). The palette for the bacnetOws and bacnetAws modules are shown expanded in Table A.1 below, with most items unchanged from the bacnet palette not expanded.

As shown above, the network component and a few others are different in the bacnetOws and bacnetAws modules, often with a different default view. For example, there is a Bacnet Aws Device Manager view and a Bacnet Ows Device Manager view on the two types of network and device folder components. The bacnetAws palette provides additional components, not found in the bacnet module.

Note that “server side” components found in the bacnet palette are missing, as currently neither the BACnet AWS Supervisor nor the BACnet OWS Supervisor are licensed for server operation. Also, there is no “Mstp” port under the NetworkPorts folder—a port type valid only for QNX-based JACE hosts.

As usual, you seldom need to work from the palette when engineering a BACnet AWS Supervisor or BACnet OWS Supervisor station. Instead, the various Bacnet manager views simplify component creation, enforcing proper component hierarchy. For example, the Bacnet Aws Config Manager view on the Config device extension of a BacnetAwsDevice provides a “Discover” routine, finding the appropriate types of Config objects to represent discovered BACnet objects (including “added” ones).

The Bacnet Aws Config Manager is also unique in that you can add and delete BACnet objects in the selected device—providing that the device supports these BACnet services.

Different AWS and OWS manager views are explained in other subsections of this appendix.