Datapoint definition - Revision history

SWNadmin2: /* SIEMENS Algorex datapoint import */

2021-04-12T07:17:17Z

SIEMENS Algorex datapoint import

← Older revision		Revision as of 07:17, 12 April 2021
Line 15:		Line 15:
	First you should create an Algorex container (see: [[Containers]]).		First you should create an Algorex container (see: [[Containers]]).
	For import, right-click on a physical container and select "update from metafile". Select the relevant metafile. After import the Algorex datapoint structure appears in the datapoint tree.		For import, right-click on a physical container and select "update from metafile". Select the relevant metafile. After import the Algorex datapoint structure appears in the datapoint tree.
	During the next metafile import ~~those~~ datapoints ~~are overwritten what are~~ changed in the latest metafile. Deleted datapoints will also be deleted.		During the next metafile import the datapoints, which were changed in the latest metafile, are overwritten. Deleted datapoints will also be deleted.
	The datapoint's name won't change if it was renamed at the management system level. Those datapoints can be highlighted by the corresponding icons in the tree.		The datapoint's name won't change if it was renamed at the management system level. Those datapoints can be highlighted by the corresponding icons in the tree.
	<br style="clear: both" />		<br style="clear: both" />

SWNadmin2: /* SIEMENS Algorex datapoint import */

2021-04-12T07:13:00Z

SIEMENS Algorex datapoint import

← Older revision		Revision as of 07:13, 12 April 2021
Line 14:		Line 14:
	[[Image:Tree_popup_updatefrommetafile.png‎‎\|left\|frame]]Algorex metafile can be generated via the CC11li32.EXE metafile generator, which is provided by SIEMENS in the Algorex editor package.		[[Image:Tree_popup_updatefrommetafile.png‎‎\|left\|frame]]Algorex metafile can be generated via the CC11li32.EXE metafile generator, which is provided by SIEMENS in the Algorex editor package.
	First you should create an Algorex container (see: [[Containers]]).		First you should create an Algorex container (see: [[Containers]]).
	~~During~~ import right-click on a physical container and select "update from metafile". Select the relevant metafile. After import the Algorex datapoint structure appears in the datapoint tree.		For import, right-click on a physical container and select "update from metafile". Select the relevant metafile. After import the Algorex datapoint structure appears in the datapoint tree.
	During the next metafile import those datapoints are overwritten what are changed in the latest metafile. Deleted datapoints will also be deleted.		During the next metafile import those datapoints are overwritten what are changed in the latest metafile. Deleted datapoints will also be deleted.
	The datapoint's name won't change if it was renamed at the management system level. Those datapoints can be highlighted by the corresponding icons in the tree.		The datapoint's name won't change if it was renamed at the management system level. Those datapoints can be highlighted by the corresponding icons in the tree.

SWNadmin2: /* SIEMENS Algorex datapoint import */

2021-04-12T07:12:24Z

SIEMENS Algorex datapoint import

← Older revision		Revision as of 07:12, 12 April 2021
Line 12:		Line 12:

	==SIEMENS Algorex datapoint import==		==SIEMENS Algorex datapoint import==
	[[Image:Tree_popup_updatefrommetafile.png‎‎\|left\|frame]]Algorex metafile can be generated via the CC11li32.EXE metafile generator, ~~what~~ is provided by SIEMENS in the Algorex editor package.		[[Image:Tree_popup_updatefrommetafile.png‎‎\|left\|frame]]Algorex metafile can be generated via the CC11li32.EXE metafile generator, which is provided by SIEMENS in the Algorex editor package.
	First you should create an Algorex container (see: [[Containers]]).		First you should create an Algorex container (see: [[Containers]]).
	During import right-click on a physical container and select "update from metafile". Select the relevant metafile. After import the Algorex datapoint structure appears in the datapoint tree.		During import right-click on a physical container and select "update from metafile". Select the relevant metafile. After import the Algorex datapoint structure appears in the datapoint tree.
Line 26:		Line 26:
	[[Image:Tree_DeviceNodes.png‎\|left\|frame]] Under an Algorex physical container the Device nodes are showing the protocols' features. They list the control units and the lantronix too. There you can see the address of the control units imported under a container.		[[Image:Tree_DeviceNodes.png‎\|left\|frame]] Under an Algorex physical container the Device nodes are showing the protocols' features. They list the control units and the lantronix too. There you can see the address of the control units imported under a container.
	<br style="clear: both" />		<br style="clear: both" />

	==SIEMENS Sinteso datapoint import==		==SIEMENS Sinteso datapoint import==
	Sinteso editor can generate a Sibx.xml file that contains the datapoint structure of the entire site. Right-click on the Sinteso physical container and select "import from metafile". After successful import the Sinteso datapoint structure appears in the tree.		Sinteso editor can generate a Sibx.xml file that contains the datapoint structure of the entire site. Right-click on the Sinteso physical container and select "import from metafile". After successful import the Sinteso datapoint structure appears in the tree.

SWNadmin2 at 11:42, 5 October 2016

2016-10-05T11:42:06Z

← Older revision		Revision as of 11:42, 5 October 2016
Line 5:		Line 5:
	__TOC__		__TOC__

	Datapoint definition can be done in two ways:		Datapoint definition can be done in two ways. You can:
	# ~~Automatic~~ import of a specific subsystem's metafile		# Automatically import a specific subsystem's metafile
	# ~~Manual definition of~~ datapoints		# Manually define the datapoints

	Different subsystems require their own method.		Different subsystems require their own method.

SWNadmin2 at 11:39, 5 October 2016

2016-10-05T11:39:51Z

← Older revision		Revision as of 11:39, 5 October 2016
Line 5:		Line 5:
	__TOC__		__TOC__

	Datapoint definition can ~~happen basically~~ two ~~different way~~:		Datapoint definition can be done in two ways:
	# Automatic import of a specific subsystem metafile		# Automatic import of a specific subsystem's metafile
	# Manual ~~datapoint~~ definition		# Manual definition of datapoints

	Different subsystems require ~~diferent methods~~.		Different subsystems require their own method.

	==SIEMENS Algorex datapoint import==		==SIEMENS Algorex datapoint import==
	[[Image:Tree_popup_updatefrommetafile.png‎‎\|left\|frame]]Algorex metafile ~~is produced by~~ CC11li32.EXE metafile generator, ~~that~~ is a SIEMENS ~~product and included~~ in the Algorex editor package.		[[Image:Tree_popup_updatefrommetafile.png‎‎\|left\|frame]]Algorex metafile can be generated via the CC11li32.EXE metafile generator, what is provided by SIEMENS in the Algorex editor package.
	First an Algorex container ~~should be created~~ (see: [[Containers]]).		First you should create an Algorex container (see: [[Containers]]).
	During import ~~just~~ right-click on a physical container and select update from metafile. ~~Pick up~~ the relevant metafile. After import the Algorex datapoint structure appears in the datapoint tree.		During import right-click on a physical container and select "update from metafile". Select the relevant metafile. After import the Algorex datapoint structure appears in the datapoint tree.
	During ~~subsequent~~ metafile import ~~only~~ those ~~datapoint~~ are overwritten ~~that really~~ changed in the latest metafile. Deleted ~~datapoint~~ will also be deleted.		During the next metafile import those datapoints are overwritten what are changed in the latest metafile. Deleted datapoints will also be deleted.
	~~Datapoint~~ name ~~will never~~ change if it was renamed in the management system level. ~~Such~~ datapoints can be highlighted by icons in the tree.		The datapoint's name won't change if it was renamed at the management system level. Those datapoints can be highlighted by the corresponding icons in the tree.
	<br style="clear: both" />		<br style="clear: both" />
	[[Image:Tree_updatemeta_parameters.png‎\|left\|frame]]		[[Image:Tree_updatemeta_parameters.png‎\|left\|frame]]
	~~Before import some parameter has~~ to be set:		Some parameters have to be set before importing:
	* Device address: control unit address.		* Device address: control unit's address.
	* Sub-Line(Hi): in case of UDS1100 is to be set 0		* Sub-Line(Hi): in case of UDS1100 is to be set 0
	* Sub-Line(Lo): in case of UDS1100 is to be set 1.		* Sub-Line(Lo): in case of UDS1100 is to be set 1.
	<br style="clear: both" />		<br style="clear: both" />
	[[Image:Tree_DeviceNodes.png‎\|left\|frame]] Under an Algorex physical container the Device nodes ~~shows~~ the ~~protocol~~ features. They list the control units and the lantronix ~~also~~. There you can see the address of control units ~~that are~~ imported under a container.		[[Image:Tree_DeviceNodes.png‎\|left\|frame]] Under an Algorex physical container the Device nodes are showing the protocols' features. They list the control units and the lantronix too. There you can see the address of the control units imported under a container.
	<br style="clear: both" />		<br style="clear: both" />
	==SIEMENS Sinteso datapoint import==		==SIEMENS Sinteso datapoint import==
	Sinteso editor can generate a Sibx.xml file that ~~contain~~ the datapoint structure of entire site. ~~Just right~~-click on physical container ~~of Sinteso~~ and select import from metafile. After import the Sinteso datapoint structure appears in the tree.		Sinteso editor can generate a Sibx.xml file that contains the datapoint structure of the entire site. Right-click on the Sinteso physical container and select "import from metafile". After successful import the Sinteso datapoint structure appears in the tree.

	==SD3 fire control panel datapoint import==		==SD3 fire control panel datapoint import==
	SD3 use Jbus to communicate with a host system. JBUS has to be enabled in SD3 panel. Lantronix device server is used to convert RS422 line to ethernet and convert JBUS data communication to TCP/IP. During commissioning the SD3 datapoints are downloaded from the control unit through JBUS. First you have to properly ~~configure~~ both Lantronix and JBUS. ~~Then~~ enable the communication in SIWENOID and the datapoints ~~and its~~ hierarchy is automatically uploaded from SD3 panel and inserted into the tree of application. This is called initialization.		SD3 use Jbus to communicate with the host system. JBUS has to be enabled at the SD3 panel. A Lantronix device server is used to convert RS422 line to ethernet, and convert JBUS data communication to TCP/IP. During commissioning the SD3 datapoints are downloaded from the control unit through JBUS. First, you have to configure properly both Lantronix and JBUS. Second, enable the communication in SIWENOID and the datapoints with their hierarchy are automatically uploaded from the SD3 panel and inserted into the tree view of the application. This is called initialization.
	<br style="clear: both" />		<br style="clear: both" />


	''Previous chapter-> [[Containers]] / Next chapter-> [[Datapoint settings]]''		''Previous chapter-> [[Containers]] / Next chapter-> [[Datapoint settings]]''

	[[Category:Commissioning]]		[[Category:Commissioning]]

SWNadmin2 at 10:46, 10 April 2013

2013-04-10T10:46:05Z

← Older revision		Revision as of 10:46, 10 April 2013
Line 33:		Line 33:
	<br style="clear: both" />		<br style="clear: both" />

	~~==CCTV DVR definition==~~
	~~<br style="clear: both" />~~

	''Previous chapter-> [[Containers]] / Next chapter-> [[Datapoint settings]]''		''Previous chapter-> [[Containers]] / Next chapter-> [[Datapoint settings]]''

	[[Category:Commissioning]]		[[Category:Commissioning]]

SWNadmin2: /* IP camera definition */

2013-04-10T10:45:46Z

IP camera definition

← Older revision		Revision as of 10:45, 10 April 2013
Line 31:		Line 31:
	==SD3 fire control panel datapoint import==		==SD3 fire control panel datapoint import==
	SD3 use Jbus to communicate with a host system. JBUS has to be enabled in SD3 panel. Lantronix device server is used to convert RS422 line to ethernet and convert JBUS data communication to TCP/IP. During commissioning the SD3 datapoints are downloaded from the control unit through JBUS. First you have to properly configure both Lantronix and JBUS. Then enable the communication in SIWENOID and the datapoints and its hierarchy is automatically uploaded from SD3 panel and inserted into the tree of application. This is called initialization.		SD3 use Jbus to communicate with a host system. JBUS has to be enabled in SD3 panel. Lantronix device server is used to convert RS422 line to ethernet and convert JBUS data communication to TCP/IP. During commissioning the SD3 datapoints are downloaded from the control unit through JBUS. First you have to properly configure both Lantronix and JBUS. Then enable the communication in SIWENOID and the datapoints and its hierarchy is automatically uploaded from SD3 panel and inserted into the tree of application. This is called initialization.
	~~<br style="clear: both" />~~

	~~==IP camera definition==~~

	<br style="clear: both" />		<br style="clear: both" />

SWNadmin2 at 08:32, 6 June 2012

2012-06-06T08:32:47Z

← Older revision		Revision as of 08:32, 6 June 2012
Line 30:		Line 30:

	==SD3 fire control panel datapoint import==		==SD3 fire control panel datapoint import==
			SD3 use Jbus to communicate with a host system. JBUS has to be enabled in SD3 panel. Lantronix device server is used to convert RS422 line to ethernet and convert JBUS data communication to TCP/IP. During commissioning the SD3 datapoints are downloaded from the control unit through JBUS. First you have to properly configure both Lantronix and JBUS. Then enable the communication in SIWENOID and the datapoints and its hierarchy is automatically uploaded from SD3 panel and inserted into the tree of application. This is called initialization.
	<br style="clear: both" />		<br style="clear: both" />

	==IP camera definition==		==IP camera definition==

	<br style="clear: both" />		<br style="clear: both" />

	==~~IP camera~~ definition==		==CCTV DVR definition==

	<br style="clear: both" />		<br style="clear: both" />

SWNadmin2 at 07:58, 6 June 2012

2012-06-06T07:58:13Z

← Older revision		Revision as of 07:58, 6 June 2012
Line 28:		Line 28:
	==SIEMENS Sinteso datapoint import==		==SIEMENS Sinteso datapoint import==
	Sinteso editor can generate a Sibx.xml file that contain the datapoint structure of entire site. Just right-click on physical container of Sinteso and select import from metafile. After import the Sinteso datapoint structure appears in the tree.		Sinteso editor can generate a Sibx.xml file that contain the datapoint structure of entire site. Just right-click on physical container of Sinteso and select import from metafile. After import the Sinteso datapoint structure appears in the tree.

			==SD3 fire control panel datapoint import==

			<br style="clear: both" />

			==IP camera definition==
			<br style="clear: both" />

			==IP camera definition==

			<br style="clear: both" />

	''Previous chapter-> [[Containers]] / Next chapter-> [[Datapoint settings]]''		''Previous chapter-> [[Containers]] / Next chapter-> [[Datapoint settings]]''

	[[Category:Commissioning]]		[[Category:Commissioning]]

SWNadmin2 at 17:55, 10 May 2011

2011-05-10T17:55:12Z

← Older revision		Revision as of 17:55, 10 May 2011
Line 2:		Line 2:

	''Previous chapter-> [[Containers]] / Next chapter-> [[Datapoint settings]]''		''Previous chapter-> [[Containers]] / Next chapter-> [[Datapoint settings]]''

			__TOC__

	Datapoint definition can happen basically two different way:		Datapoint definition can happen basically two different way: