Containers - Revision history

SWNadmin2: /* Dedicated containers */

2021-04-12T07:07:00Z

Dedicated containers

← Older revision		Revision as of 07:07, 12 April 2021
Line 31:		Line 31:
	==Dedicated containers==		==Dedicated containers==
	[[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_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]] 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.		[[Image:Tree_dedicated_button.png\|left\|caption]] On the 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" />

SWNadmin2: /* Datapoint reorganization */

2021-04-12T07:03:31Z

Datapoint reorganization

← Older revision		Revision as of 07:03, 12 April 2021
Line 20:		Line 20:
	==Datapoint reorganization==		==Datapoint reorganization==
	Datapoints of subsystems can be defined under a physical container. Most of the time the import procedure (from a metafile) is automatic.		Datapoints of subsystems can be defined under a physical container. Most of the time the import procedure (from a metafile) is automatic.
	Sometimes the inherited datapoint hierarchy is not arranged properly at the level of the supervisory system, ~~since all~~ datapoints ~~are on~~ the ~~same hierarchy level~~.		Sometimes the inherited datapoint hierarchy is not arranged properly (illustrative) at the level of the supervisory system. To get a properly transparent, logical datapoint hierarchy, the datapoints from the physical containers can be moved under the logical containers. Any datapoint can be moved under any logical container. In a logical container you can mix different types of datapoints without any restriction.

	~~The imported datapoints can be arranged under logical containers within other - "parent" - containers.~~		Important: The datapoints are also linked to their original physical container. 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.
	~~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:Engarbofa.jpg‎‎‎‎\|left\|frame]] Split your tree window. This makes it easier to drag&drop datapoints beetwen containers.<br style="clear: both" />		[[Image:Engarbofa.jpg‎‎‎‎\|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.		[[Image:Tree_movedatapoint.png‎‎‎\|left\|frame]] In datapoint tree view drag one or more datapoints from a physical container, and drop them to a logical container. Child nodes of the selected datapoints will also be moved to the new location. Logical containers will now inherit the status of their new chidren datapoints.
	<br style="clear: both" />		<br style="clear: both" />

SWNadmin2: /* Datapoint reorganization */

2021-04-12T06:50:45Z

Datapoint reorganization

← Older revision		Revision as of 06:50, 12 April 2021
Line 19:		Line 19:

	==Datapoint reorganization==		==Datapoint reorganization==
	Datapoints can be defined under a physical container. ~~By default~~ the import procedure is automatic.		Datapoints of subsystems can be defined under a physical container. Most of the time the import procedure (from a metafile) is automatic.
	Sometimes the inherited datapoint hierarchy is not ~~convenient to manage~~, since all datapoints are on the same hierarchy level.		Sometimes the inherited datapoint hierarchy is not arranged properly at the level of the supervisory system, since all datapoints are on the same hierarchy level.

	The imported datapoints can be arranged under logical containers within other - "parent" - containers.		The imported datapoints can be arranged under logical containers within other - "parent" - containers.

SWNadmin2: /* Logical containers */

2021-04-12T06:38:07Z

Logical containers

← Older revision		Revision as of 06:38, 12 April 2021
Line 15:		Line 15:

	==Logical containers==		==Logical containers==
	[[Image:Tree_newlogcontainer.png‎‎\|left\|frame]]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~~.		[[Image:Tree_newlogcontainer.png‎‎\|left\|frame]]When you create a logical container, the communication parameters have to be left blank. An arbitrary topology can be created of logical containers. Under a selected logical container an another one can be created in any number and depth.
	<br style="clear: both" />		<br style="clear: both" />

SWNadmin2: /* Physical containers */

2021-04-12T06:30:46Z

Physical containers

← Older revision		Revision as of 06:30, 12 April 2021
Line 10:		Line 10:

	==Physical containers==		==Physical containers==
	[[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).		[[Image:Tree_newcontainer.png‎\|left\|frame]] Physical container can be distinguished from a logical container, it features the communication protocol and the settings 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.		Optionally you can define the communication parameters after creating the container. These are parameters about IP address, subsystem type, port number... Datapoints from the subsystems' metafile can be imported under the physical container, as the physical containers children nodes.
	<br style="clear: both" />		<br style="clear: both" />

SWNadmin2: /* Phylosophy of containers */

2021-04-12T06:17:09Z

Phylosophy of containers

← Older revision		Revision as of 06:17, 12 April 2021
Line 4:		Line 4:

	==Phylosophy of containers==		==Phylosophy of containers==
	The ~~datapoint hierarchy~~ is based on containers. Containers are logical parent nodes of physical datapoints or other containers.		The tree structure of the data points is based on containers. The containers are not data points of the physical subsection. Containers are logical parent nodes of physical datapoints or other containers.
	~~They~~ inherit the status of their ~~children~~ datapoints.		The containers always inherit the status of their childrens datapoints.
	[[Image:Tree_popup_newContainer.png‎\|left\|frame]] In tree view use the popup menu to create a new container.		[[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" />

SWNadmin2: /* Datapoint reorganization */

2019-08-07T12:38:24Z

Datapoint reorganization

← Older revision		Revision as of 12:38, 7 August 2019
Line 27:		Line 27:

	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.		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:Engarbofa.jpg‎‎‎‎\|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.		[[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" />

SWNadmin2 at 06:37, 5 October 2016

2016-10-05T06:37:23Z

← Older revision		Revision as of 06:37, 5 October 2016
Line 4:		Line 4:

	==Phylosophy of containers==		==Phylosophy of containers==
	The datapoint hierarchy is ~~container~~ based. Containers are ~~not associated with subsystem datapoints. They are simply~~ parent nodes of physical datapoints or other containers. ~~Containers~~ inherit the status of their children datapoints.		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 ~~that~~ it also defines the communication protocol features of corresponding subsystem~~/subsystems~~.		[[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).
	~~When you create a container optionally~~ you can define its communication parameters. It containes parameters about IP ~~addr~~, subsystem type, port number... ~~Then~~ you can import datapoints under this container as children nodes.		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==
	~~Under~~ a physical container ~~you can define datapoints~~. ~~In most case it~~ is ~~done by an~~ automatic ~~import procedure~~. ~~In many case~~ the inherited datapoint hierarchy is not as convenient ~~as it should be~~ on ~~management system~~ level.		Datapoints can be defined under a physical container. By default the import procedure is automatic.
	~~To achieve a user friendly datapoint hierarhy it is possible to move the datapoint from a physical container into a~~ logical ~~container~~. Any ~~datapoints~~ can be moved under any logical container. ~~Under a certain~~ logical container you can mix different ~~type~~ of datapoints without any restriction.		Sometimes the inherited datapoint hierarchy is not convenient to manage, since all datapoints are on the same hierarchy level.
	Important: ~~Programatically the~~ datapoints are linked to its original physical container ~~too~~. ~~Consequently during~~ a subsequent metafile import~~, those~~ datapoints ~~are also refreshed~~ that have already been moved to an other logical container. ~~Thus the~~ metafile imports should always be initiated in its original physical container.
	[[Image:Tree_splitwindow.png‎‎‎‎\|left\|frame]] ~~For your convenient first split~~ your tree window. This makes it easier to drag&drop ~~datapoint~~ beetwen containers.<br style="clear: both" />		The imported datapoints can be arranged under logical containers within other - "parent" - containers.
	[[Image:Tree_movedatapoint.png‎‎‎\|left\|frame]] In datapoint tree, drag one or more ~~datapoint~~ under a physical container ~~and drop them into~~ a logical container. ~~Children~~ nodes of the selected ~~datapoint~~ will also be moved to the new location. Logical containers will inherit the status of their new chidren datapoints.		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]] ~~Using~~ popup menu ~~of a container in tree view,~~ select '''Edit container...''' ~~In the dialog mark~~ the "Dedicated" checkbox.<br style="clear: both" />		[[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]] ~~A container will appear on the~~ bottom of event list window. It will ~~contains~~ 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.		[[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" />

SWNadmin2: /* Phylosophy of containers */

2016-10-04T11:01:15Z

Phylosophy of containers

← Older revision		Revision as of 11:01, 4 October 2016
Line 4:		Line 4:

	==Phylosophy of containers==		==Phylosophy of containers==
	The datapoint hierarchy is based ~~on containers~~. Containers are not associated with subsystem datapoints. They are simply parent nodes of physical datapoints or other containers. Containers inherit the status of their children datapoints.		The datapoint hierarchy is container based. Containers are not associated with subsystem datapoints. They are simply parent nodes of physical datapoints or other containers. Containers inherit the status of their children datapoints.
	[[Image:Tree_popup_newContainer.png‎\|left\|frame]] In tree use popup menu to create a new container.		[[Image:Tree_popup_newContainer.png‎\|left\|frame]] In tree use popup menu to create a new container.
	<br style="clear: both" />		<br style="clear: both" />

SWNadmin2 at 14:12, 1 April 2011

2011-04-01T14:12:35Z

← Older revision		Revision as of 14:12, 1 April 2011
Line 1:		Line 1:
			{{Languages\|Containers}}

	''Next chapter-> [[Datapoint definition]]''		''Next chapter-> [[Datapoint definition]]''