Virtual ORD syntax

The general syntax for a virtual ord uses a specialized form.

The ORD syntax is:

<ord to VirtualGateway>|virtual:/virtualPath where:

virtualPath represents some hierarchy of virtual components and child properties.

For example, for BacnetVirtualComponents, the general virtual path syntax is:

<ord to VirtualGateway>|virtual:/objectType_Instance/propertyName

Or in the special case of an arrayed property:

<ord to VirtualGateway>|virtual:/objectType_Instance/propertyName/elementN

where N is the property array index.

For specific virtual ord details, refer to the corresponding driver document.

Note: In Niagara 4, virtual components in a NiagaraNetwork use a much simpler virtual ord syntax than in previous releases, due to a new virtual cache mechanism. Much information that was formerly in the virtualPath portion of the ord syntax now resides in this cache.

On Px pages, virtual components, which build on standard Baja virtual component syntax further append facets and config flags. This creates complex ords that the station automatically resolves when you drag a virtual onto a Px page. As a result, you may notice a very wide Make Widget window.

For example, a single ord may look like this:

station:|slot:/Drivers/NiagaraNetwork/J202_TestG/virtual|virtual:/
Drivers;d;c;driver%3aDriverContainer/M2mIoNetwork;d;c;nrio%3aM2mIoNetwork/
LocalIo16;d;c;nrio%3aNrio16Module/points;f;c;nrio%3aNrio16Points/
RTU1;d;c;nrio%3aNrio16PointFolder/Inputs1;d;c;nrio%3aNrio16PointFolder/
ui1%242dReturnAir;d;c;control%3aNumericPoint|slot:out$3bf$3bp$3bbaja$253aSta
tusNumeric$3b267$3bunits$253du$253afahrenheit$253b$25baF$253b$2528K$2529$253
b$252a0$252e5555555555555556$252b255$252e37222222222223$253b$257cprecision$2
53di$253a1$257cmin$253dd$253a$252dinf$257cmax$253dd$253a$252binf$257cnVirtua
lW$253db$253atrue/value

Obviously, such ORDs are difficult to decipher and safely change in a text editor. The Baja text property editor within the Px Editor normalizes the ORD portion to appear like other component ORDs.