Converting bound ORDs to tag-based NEQL ORDs
Improve the reusability of a Px view that contains bound ORDs by converting the slot path ORDs to tag-based NEQL ORDs.
Prerequisites:
-
- You have a component that has an existing Px view with bound ORDs assigned to it. The component on which a Px view is placed is referred to as the base component.
- You have more than one component configured with tags and relations.
Perform the following steps:
- Open the Px Editor view for an existing Px view.
- In the Bound Ords pane, click
(Neqlize Ords) to convert the Slot Path Ords to tag-based NEQL Ords and open the Neqlize Ords window.NOTE: When editing a Px file, the Neqlize Ords button is disabled as is the Relativize Ords button. Both of these buttons become enabled when editing the graphic on a component running in a station. The Neqlize Ords button will also be disabled if connected to an older station or a station that does not have the tagdictionary module installed (the automatic conversion cannot be done in that case and the single scheme will be missing which will prevent the Neqlize Ords from working).In the example below, the highlighted row shows that the conversion process found the NumericWritable2 point has the
hs:equipRefrelation that traverses from the base component to that point, and the point has thea:tag2tag applied. It is this tag/relation combination that distinguishes that component from all the other components. The conversion process then pipes on thesingle:scheme to get the single point from the query result. - Click OK to save the selected converted Ords and close the window.
After saving the converted Ords, the Px view can be reused on a different base component and the bound component can be named
differently and be positioned anywhere in the station, as long as there is a set of tags to identify the component, and a
relation to get from the base component to the bound component.
Example
Additional details on this example:
- The first four rows were previously converted to NEQL query ords. The Before Ords in the second and fourth rows still resolve. They are not selected (the After Ord is the same as the Before Ord) because they are already NEQL query Ords, but the Path column still shows the component the query resolves to.
- The first row does not resolve to any component because the tags have changed since that NEQL query Ord was converted. Note that Path column displays any errors encountered during conversion.
- The 3rd row no longer resolves to a single component only and more tagging is required to distinguish the component from other components.
- The fifth and sixth rows are slot paths that are able to be converted to NEQL query ords. The fifth row is a descendant only- there are no relations between the base and that bound component. The sixth row is for a component that is not a descendant of the base component but is the endpoint of a relation on the base component. Any rows where the Before Ord does not start with neql that can be successfully converted are automatically selected (indicated with a checkmark).
- The seventh through ninth rows are for slot path bound ords that failed to be converted to NEQL query ords. The seventh row is for a component that is the endpoint of a relation on the base component but does not have a set of tags that distinguishes it from other endpoints. The eighth row is for a component that is not a descendant of nor an endpoint of a relation on the base component.