As previously mentioned, virtual components can be used to show real-time values in Px views—at least when all the rich features of proxy points are not required.

A virtual gateway cannot have its “own” Px view, but you can use its child virtual components in Px views for other components, for example on the device component itself, or its Points extension, and so on.

The only persisted (permanent) record of such a virtual component is its ord in the Px binding to it, which uses a “Virtual ord syntax” that includes the virtual gateway within it (and activates it at runtime). This ord is automatically resolved when you drag a virtual component onto the Px page, and make your selection in the popup Px “Make Widget” dialog, as shown in the Bacnet example in Figure 35.

Depending on driver, Px usage details may differ for virtual components. For example, usage of Niagara virtual components in Px views includes special considerations. For details, see Niagara virtuals in Px views.

For complete details on Px views and widget editing, see the “About Px Editor” section in the User Guide.