Views on Niagara virtuals

Niagara virtual components provide a subset of the views as normal components, where the default Property Sheet view and Category Sheet view (for security) provide the most utility—see Security and Niagara virtuals. Special “manager” views on virtuals are not available.

Because of the transient (non-persisted) nature of virtuals, the other common types of views on Niagara virtuals can be summarized as follows:

Wire Sheet — not available, as links to/from any virtual components are not supported.
Slot Sheet — available, but little practical application—as any changes made to slots (config flags, new slot, etc) are not persisted.
Link Sheet — not available, as links to/from any virtual components are not supported.

Creating a Px view directly on a Niagara virtual or the Niagara Virtual gateway (using “New View” from the right-click Workbench menu), is not supported/available. However, you can create such Px views on other persisted components in the station, for example on Folder or IconFolder components, and then add Px widgets with Niagara virtual component bindings. See Niagara virtuals in Px views.

Property sheet access of any Niagara virtual provides a “Virtual Info” slot at the top of the view, see the section About Virtual Info.

About Virtual Info

In addition to the “Virtual Info” properties available on a Niagara Virtual device extension, each child Niagara virtual has a “Virtual Info” container with five read-only status properties (Figure 124).

Figure 124. Virtual Info properties on any Niagara virtual component

Virtual Info properties are in addition to the properties of the target source component, and include:

Virtual Status

For any Niagara virtual component, this is status of that virtual—not to be confused with whatever status the source (remote station) component may currently have. This status always appears on property sheets with a “vStatus” descriptor.

For example, a virtual for a proxy point may have an “ok” virtual status, yet show an “Out” with a status of “down”. Virtual status may initially show with a status of “stale,” before changing to “ok”.
Type Specification

Reflects the moduleName:componentType used for representing the Niagara virtual, for example in the property sheet view for that component.
Slot ORD

The complete slot path to the remote source component (relative to that station’s slot hierarchy), where the leading “root” portion is station:│slot:
Last Failure Cause

The last unsuccessful attempt (if any) to activate this virtual component is explained in this text string property. May be blank if no previous unsuccessful attempt has occurred.
Where a “Niagara virtual to virtual” path is used, a past unsuccessful attempt may include information about the comm error, for example:
```
Station Err: (J7_Bnet_36 -> J202_TestW) {down}
```
Gateway

The “handle” ord of the virtual gateway within the station’s virtual component space.

Note that additional “spy” page information for Niagara virtuals is also available for any station. For more details, see Spy page diagnostics.”