For example, the BacnetAwsDevice enhances the regular BacnetDevice by replacing the Config property with an AWS version that enables creating and deleting objects.

For convenience, the palette in the bacnetOws and bacnetAws modules provide all available components, including all the shared bacnet components (except server-related ones).

The network component and a few others differ between 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. The bacnetAws palette provides additional components, which are not found in the bacnet module.

Server-side (BACnet export) components found in the bacnet palette are missing, as neither the BACnet AWS Supervisor nor the BACnet OWS Supervisor are licensed for server operation. Also, there is no MstpPortunder the NetworkPorts folder. (This port type is valid only for QNX-based hosts.

The various Bacnet manager views in the palette simplify component creation, enforcing proper component hierarchy. For example, the Bacnet Aws Config Manager view on the Config device extension of a BacnetAwsDevice discovers the appropriate types of Config objects to represent BACnet objects (including added ones).

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