Virtuals troubleshooting
This topic addresses typical issues when working with virtual components.
The virtual gateway in my Supervisor NiagaraNetwork reports {fault}.
The virtual gateway in a Supervisor station may be disabled or even in fault. Confirm that virtuals are licensed for your Supervisor station, confirm that Virtuals Enabled on the NiagaraNetwork Property Sheet is enabled (true), and check the Last Failure Cause on the virtual gateway (Virtual node under the NiagaraStation.
I want to configure a controller station to support virtuals. The Last Failure Cause under my NiagaraStation reports Niagara Virtual Components are not licensed.
A virtual gateway may report a fault status because, even though the station’s Virtuals Enabled property is set to true, the host controller running this station may not be licensed for virtuals.
The values displayed for the components under a NiagaraStation do not look right.
If you are engineering a job while still configuring a remote station that is modeled by a NiagaraStation in the local NiagaraNetwork, you may need to right-click on the Virtuals node and click to update the data from the remote station.