Overview
This page presents information on how to work with the Asset Tree. It will also show one of ways one can create some custom graphics objects, like DataGrid Tables and Text Output, which will map automatically to the selected asset in the tree.
For an a more advanced example on how the Asset Tree can be used in solutions, go to Self-Aware Asset Displays.
| Info |
|---|
On this page:
| Table of Contents | ||
|---|---|---|
|
Configuring the Asset Tree
Configuration Workflow
The Asset Tree configuration is located at Unified Namespace → Asset Tree.
The Asset Tree has pre-defined folders:
- BaseTags: All local tags created in the solutions that were not placed in any folders (levels) are automatically placed in this folder.
- ExternalTags: When creating ExternalTags connections, they are automatically included in this folder, so you can easily browse the dynamic contents of the remote system.
The typical action when configuration the asset tree are:
- Create a new folder: Folders allow you to organize, group and create hierarchies for your assets. Click the new Asset Folder icon to create one or right click the Asset Tree.
- Create new Tags: After selecting a folder, use the New Tag toolbar button or right-click menu, to create a new tag inside that folder.
- Move Tags to selected folders: Just drag tags from the BaseTags folder — or other location — to the desired placement level at the tree.
- Insert Remote assets: If there is a ExternalTags connection defined, you can insert specific assets from the external system in the asset tree.
The image below describes an example of a solution's hierarchy.
By right-clicking any folder or tag, you can also rename it directly from the Asset Tree. You can copy/paste an entire folder or just one Asset from one folder to another. By doing so, all Tags (and their Alarms, Historian, and Device configurations) will be copied as well.
You can also have the same name Tag in more than one folder.
Once your solution is running, you will be able to monitor the Tag values directly from the Asset Tree through the Value column.
You can add Dynamic Data from the ExternalTags inside your treeview structure. For more information, please refer to the ExternalTags External TagProviders documentation.
Asset Tree on displays
Once your Asset Tree is defined, you'll be able to see it in the Draw Environment, on the right-side of the screen, where you can drag them into any display.
Add the component to your display, and customize it according to the settings described below. Does this still exist in v10?
The parameters are described as follows:
| AssetsControl Configuration | |
|---|---|
| ControlName | Element's reference name so its properties can be accessed and manipulated in CodeBehind. |
| SelectedAsset | Tag that will be receiving the selected Asset Name in Runtime as a String. |
| Selected Path | ------------------- |
| Initial Path | ------------------- |
| Branch Filter | ------------------- |
| Attribute Filter | ------------------- |
| Blinding | Select OneWay or TwoWay or OneWay to Source. |
| SelectedLevel | Tag that will be receiving the selected Level Name in Runtime as a String. |
| Show Only Tags | Flag that indicates if the Asset Tree will display only Tags or other project objects (such as Displays). |
| Show 'Root Tags' On Root | By default, all common type Tags (Integer, Digital, Text, etc) are added to the Root. By unchecking this option you can filter these elements out. |
| Expand Tags | Flag that indicates if multi-level Tags can be expanded (Templates, Arrays). If unchecked, only the main Tag will be in the Asset Tree. |
| Show Client Tags | Flag to define if client domain Tags will be displayed in Runtime. If unchecked, only server domain Tags will show up. |
| Show 'LinkedTags Sources' on root | ------------------- |
| Prefer Display Text | Flag to indicate if the text that will show up in the Tree is the TagName or its Alias (defined in Unified Namespace > Asset Tree > DisplayText). If checked and the column is empty, the TagName will be used. |
| Localizable | If checked, Tag Names (or aliases) can be translated to different languages according to your project dictionary's settings. |
CodeBehind and IO Components
You can also access the Asset elements from the CodeBehind by navigating through the TagNamespace. IntelliSense will display the Tags and their respective Levels.
Similar to the ExternalTags approach, the elements from the Asset View can be accessed with the syntax: ASSET(”? CompleteAssetName ?”) either in a TextBox element or the CodeBehind.
Runtime Behavior
In runtime, your Asset Tree and its components will look like the image below.
The IO element mapped with the ASSET(” CompleteAssetName ”) syntaxwill be resolved similar to the TK.GetObjectValue and will display the current value of the specific Tag it was mapped to.
The SelectedAsset and SelectedLevel Tags will also change according to the element you click on.
In this section:
| Page Tree | ||||
|---|---|---|---|---|
|