About adding a Hierarchy

The hierarchy children are added to the Hierarchy node based on the relations of that object with the other objects in the station logic. Due to the LevelDef’s in a hierarchy definition, the children of an object shown in the hierarchy may differ from the actual children of that object as set up in the station logic. So adding a Hierarchy node to the web chart enables you to plot a different set of points based on the navigation as specified by the hierarchy definition.

In Niagara 4.3, when adding a Hierarchy node to a webChart, the chart looks for the furthest point of that object and if the hierarchy child objects (the furthest descendants) on the controller have histories, the chart attempts to resolve the history and use it to initialize the webChart.

NOTE: In order to detect the matching history, the history must be already imported or exported from the controller to the Supervisor.

Figure 11. Adding Hierarchies to a webChart

By default, if there is no point to plot under the hierarchy child, the chart pulls across the n:history tag information of that hierarchy child.

About adding a Hierarchy

Figure 11. Adding Hierarchies to a webChart

Related Links