(AX-3.2 or later) The BacnetVirtualGateway is the Bacnet driver implementation of the Baja Virtual Gateway. A virtual gateway
is a component that resides under the station’s component space (Config), and acts as a gateway to the station’s “virtual component space.” Note other object spaces are Files and History. For a general explanation about Baja virtual components, refer to “About virtual component spaces” in the Drivers
Guide.
Starting in AX-3.2, each BacnetDevice and BacnetWsDevice has its own BacnetVirtualGateway, at the same level as its device extensions (Points, Schedules, and so on). Accessing components under the gateway dynamically adds them as “virtual points” while they are subscribed, but they exist only in memory (are not persisted in the station database like proxy points). When virtual points become unsubscribed, they are automatically cleaned up from the station database.
The “virtual point” level under a BacnetVirtualGateway varies as follows:
-
In AX-3.3 and later, expanding a BacnetVirtualGateway results in that device’s BACnet objects to be listed underneath. Each is a BacnetVirtualObject that contains a number of BacnetVirtualProperty components to represent its properties. Thus, virtual points are at the “object, property level.”
-
In AX-3.2 (only), expanding a BacnetVirtualGateway results in that device’s BACnet objects to be listed underneath as BacnetVirtualComponent components, where each has a property sheet that shows all the values for the BACnet object’s properties. Thus, virtual points are at the “object level.”
For more details, see Bacnet virtual points.