Containers: Difference between revisions
mNo edit summary |
|||
| Line 4: | Line 4: | ||
==Phylosophy of containers== | ==Phylosophy of containers== | ||
The datapoint hierarchy is | The datapoint hierarchy is based on containers. Containers are logical parent nodes of physical datapoints or other containers. | ||
[[Image:Tree_popup_newContainer.png|left|frame]] In tree use popup menu to create a new container. | They inherit the status of their children datapoints. | ||
[[Image:Tree_popup_newContainer.png|left|frame]] In tree view use the popup menu to create a new container. | |||
<br style="clear: both" /> | <br style="clear: both" /> | ||
==Physical containers== | ==Physical containers== | ||
[[Image:Tree_newcontainer.png|left|frame]] Physical container is distinguished from logical container | [[Image:Tree_newcontainer.png|left|frame]] Physical container is distinguished from logical container what it also defines the communication protocol features of corresponding subsystem(s). | ||
Optionally you can define its communication parameters after creation of the container. It containes parameters about IP address, subsystem type, port number... After this you can import datapoints under this container as children nodes. | |||
<br style="clear: both" /> | <br style="clear: both" /> | ||
| Line 18: | Line 19: | ||
==Datapoint reorganization== | ==Datapoint reorganization== | ||
Datapoints can be defined under a physical container. By default the import procedure is automatic. | |||
Sometimes the inherited datapoint hierarchy is not convenient to manage, since all datapoints are on the same hierarchy level. | |||
Important: | |||
[[Image:Tree_splitwindow.png|left|frame]] | The imported datapoints can be arranged under logical containers within other - "parent" - containers. | ||
[[Image:Tree_movedatapoint.png|left|frame]] In datapoint tree | Any datapoint can be moved under any logical container. | ||
In any logical container you can mix different types of datapoints without any restriction. | |||
Important: The datapoints are also linked to its original physical container programmatically. During a subsequent metafile import datapoints that have already been moved to an other (logical) container are also updated. The metafile imports should always be initiated in its original physical container. | |||
[[Image:Tree_splitwindow.png|left|frame]] Split your tree window. This makes it easier to drag&drop datapoints beetwen containers.<br style="clear: both" /> | |||
[[Image:Tree_movedatapoint.png|left|frame]] In datapoint tree view drag&drop one or more datapoints from under a physical container to a logical container. Child nodes of the selected datapoints will also be moved to the new location. Logical containers will inherit the status of their new chidren datapoints. | |||
<br style="clear: both" /> | <br style="clear: both" /> | ||
____ | |||
==Dedicated containers== | ==Dedicated containers== | ||
[[Image:Tree_container_set_dedicated_.png|left|frame]] | [[Image:Tree_container_set_dedicated_.png|left|frame]] In tree view right click on the container and from the popup menu select '''Edit container...'''. Check the "Dedicated" checkbox on the form.<br style="clear: both" /> | ||
[[Image:Tree_dedicated_button.png|left|caption]] | [[Image:Tree_dedicated_button.png|left|caption]] On hte bottom of the event list window a container will appear. It will contain small lamps that reflect to the event categories and behave as collective signals of the children nodes of the corresponding container. Its caption is inherited from the first two letter of its container. | ||
<br style="clear: both" /> | <br style="clear: both" /> | ||
Revision as of 06:37, 5 October 2016
| Language: | English • magyar |
|---|
Next chapter-> Datapoint definition
Phylosophy of containers
The datapoint hierarchy is based on containers. Containers are logical parent nodes of physical datapoints or other containers. They inherit the status of their children datapoints.
In tree view use the popup menu to create a new container.
Physical containers
Physical container is distinguished from logical container what it also defines the communication protocol features of corresponding subsystem(s).
Optionally you can define its communication parameters after creation of the container. It containes parameters about IP address, subsystem type, port number... After this you can import datapoints under this container as children nodes.
Logical containers
When you create a logical container leave the communication parameters blank. You can create a free topology of logical containers. Under a certain container you can create an another one as its child.
Datapoint reorganization
Datapoints can be defined under a physical container. By default the import procedure is automatic. Sometimes the inherited datapoint hierarchy is not convenient to manage, since all datapoints are on the same hierarchy level.
The imported datapoints can be arranged under logical containers within other - "parent" - containers. Any datapoint can be moved under any logical container. In any logical container you can mix different types of datapoints without any restriction.
Important: The datapoints are also linked to its original physical container programmatically. During a subsequent metafile import datapoints that have already been moved to an other (logical) container are also updated. The metafile imports should always be initiated in its original physical container.
Split your tree window. This makes it easier to drag&drop datapoints beetwen containers.
In datapoint tree view drag&drop one or more datapoints from under a physical container to a logical container. Child nodes of the selected datapoints will also be moved to the new location. Logical containers will inherit the status of their new chidren datapoints.
____
Dedicated containers
In tree view right click on the container and from the popup menu select Edit container.... Check the "Dedicated" checkbox on the form.
On hte bottom of the event list window a container will appear. It will contain small lamps that reflect to the event categories and behave as collective signals of the children nodes of the corresponding container. Its caption is inherited from the first two letter of its container.
Next chapter-> Datapoint definition
| Language: | English • magyar |
|---|