Distributed Emergency - Revision history

Leonardo at 08:31, 6 February 2021

2021-02-06T08:31:27Z

Leonardo at 12:59, 5 February 2021

2021-02-05T12:59:53Z

Leonardo at 12:57, 5 February 2021

2021-02-05T12:57:16Z

Leonardo: /* CLIENT Voyager DragScript Consideration */

2021-02-04T15:02:37Z

CLIENT Voyager DragScript Consideration

Leonardo: /* Personalize and Start the MASTER Voyager dedicated DragScript */

2021-02-04T14:58:22Z

Personalize and Start the MASTER Voyager dedicated DragScript

Leonardo: /* This Plugin Installation */

2021-02-04T14:57:42Z

This Plugin Installation

Leonardo: /* This Plugin Installation */

2021-02-04T14:43:14Z

This Plugin Installation

Leonardo: /* Description */

2021-02-04T14:29:11Z

Description

Leonardo: /* Some Advice about system */

2021-02-04T14:28:17Z

Some Advice about system

Leonardo: /* General Installation */

2021-02-04T14:27:23Z

General Installation

@@ Line 77: / Line 77: @@
 We inform you that using the Distributed Emergency Status potentially you cannot necessary reading the night info and running until you have SAFE the imaging.{{Note|Also if you can on the CLIENT Voyager reading weather or others source locally  we suggest to not do and using only the Distributed Emergency Status. This to avoid any glitch in system management.}}
 [[Category:Plugin]]
 [[Category:All]]
 [[Category:Manual|Lb]]

@@ Line 80: / Line 80: @@
 <categorytree mode="pages" depth="1">Setup</categorytree>
-[[Category:Setup]]
+[[Category:Plugin]]
 [[Category:All]]
-[[Category:Manual|Hj]]
+[[Category:Manual|Lb]]

← Older revision		Revision as of 12:57, 5 February 2021
Line 76:		Line 76:

	We inform you that using the Distributed Emergency Status potentially you cannot necessary reading the night info and running until you have SAFE the imaging.{{Note\|Also if you can on the CLIENT Voyager reading weather or others source locally we suggest to not do and using only the Distributed Emergency Status. This to avoid any glitch in system management.}}		We inform you that using the Distributed Emergency Status potentially you cannot necessary reading the night info and running until you have SAFE the imaging.{{Note\|Also if you can on the CLIENT Voyager reading weather or others source locally we suggest to not do and using only the Distributed Emergency Status. This to avoid any glitch in system management.}}
		+
		+	==Other Setup Pages==
		+	<categorytree mode="pages" depth="1">Setup</categorytree>
		+
		+	[[Category:Setup]]
		+	[[Category:All]]
		+	[[Category:Manual\|Hj]]

← Older revision		Revision as of 15:02, 4 February 2021
Line 71:		Line 71:

	== CLIENT Voyager DragScript Consideration ==		== CLIENT Voyager DragScript Consideration ==
−	~~Install plugin~~ (~~importing~~ the ~~new license file)~~	+	Use a DragScript in the CLIENT Voyager that manage the Events, in the Events not manage the roof but just the mount (parking) if needed.
		+
		+	We suggest to use WAIT SAFE block to read the distributed status and starting with operations.
		+
		+	We inform you that using the Distributed Emergency Status potentially you cannot necessary reading the night info and running until you have SAFE the imaging.{{Note\|Also if you can on the CLIENT Voyager reading weather or others source locally we suggest to not do and using only the Distributed Emergency Status. This to avoid any glitch in system management.}}

@@ Line 30: / Line 30: @@
 ** '''Report EXIT Status if not receive remote data for [s]:''' if the CLIENT doesn't receive any status from the MASTER Voyager an Emergency Exit status will be generate, default is 60s{{Note|This is really important to understand, if the CLIENT lost communication with MASTER Voyager the operation will be stopped on the PIER. Provide signal to alert you on the CLIENT DragScript in case of Emergency Event execution}}
 ** {{Note|All change to this settings will need a Voyager restart}}
-* Test CLIENTS connection using the ToolTip way
+* Test CLIENTS connection using the ToolTip way, ,be sure to see the info Status of each CLIENT Voyager in "Remote Dist Connected"
-** [[File:EMDISTIMg3.png]]
+**[[File:EMDISTIMg3.png]]
 ** '''LED:''' red = disconnect status or EXIT status ; yellow SUSPEND ; green SAFE ; black : Not configured
 ** '''EMERGENCY Status:''' distributed emergency status

@@ Line 18: / Line 18: @@
 * Be sure to have Application Server Active on the MASTER Voyager
 * Configure MASTER Voyager to get data from Weather system, Viking I/O system and ASCOM Safe system (one or all or at your needed). Refer to the base setup configuration of Voyager for this task
-* Configure MASTER Voyager to allow Distributed Emergency Status using the Application Server and Restart Voyager[image]
+* Configure MASTER Voyager to allow Distributed Emergency Status using the Application Server and Restart Voyager (Setup -> Tab Remote)
-** [[File:DSRemoteEMConf1.png]]
+**[[File:DSRemoteEMConf1.png]]
 ** Check the flag '''Allow Distribute Emergency Status''' to allow system works
 ** '''Each''' parameters expressed in seconds define frequency of updating of remote client status, default is 10s (Distributed Emergency status will be send to all client each 10s)
-* Configure the CLIENTS to  connect as CLIENT to the MASTER Voyager and manage and use the Distribute Emergency Status and Restart Voyager [Image]
+**{{Note|All change to this settings will need a Voyager restart}}
-* Test CLIENTS connection using the ToolTip way [image]
+* Configure the CLIENTS to  connect as CLIENT to the MASTER Voyager and manage and use the Distribute Emergency Status and Restart Voyager (Setup -> Tab Remote)
 == Personalize and Start the MASTER Voyager dedicated DragScript ==

@@ Line 12: / Line 12: @@
 * Install plugin (importing the new license file) on the MASTER Voyager will manage the Distributed Emergency Status
 * Install plugin on all the Voyager Clients will be use the Distributed Emergency Status.
 * Assure you have the MASTER Voyager and CLIENT Voyager on LAN in the same Network
 * Allow in Router policy and firewall rules to reach the port 5950 (or the port for Voyager Application server used) on The MASTER Voyager
@@ Line 17: / Line 19: @@
 * Configure MASTER Voyager to get data from Weather system, Viking I/O system and ASCOM Safe system (one or all or at your needed). Refer to the base setup configuration of Voyager for this task
 * Configure MASTER Voyager to allow Distributed Emergency Status using the Application Server and Restart Voyager[image]
 * Configure the CLIENTS to  connect as CLIENT to the MASTER Voyager and manage and use the Distribute Emergency Status and Restart Voyager [Image]
 * Test CLIENTS connection using the ToolTip way [image]

@@ Line 5: / Line 5: @@
 This plugin is useful for managing single buildings used as observatories or telescope farms where there are several Piers, each managed by its Voyager installation. There will be a Voyager master who will only deal with the centralized reading, interpretation and distribution of Emergency data that with a dedicated 24h / 24h DragScript running (included in plugin purchase) every day will take care of the opening / closing of the roof, the suspension and resume and the exit for emergency distributed to all Voyager connected.
-The connections between the Voyager distributor and the clients are self-restoring and with a fail-over system.[[File:Distributed Emergency Plugin.png|none|thumb|alt=|843x843px|An example of Distributed Emergency Plugin applied to single building for a telescope farm|link=https://wiki.starkeeper.it/index.php/File:Distributed_Emergency_Plugin.png]]
+The connections between the Voyager distributor and the clients are self-restoring and with a fail-over system[[File:Distributed Emergency Plugin.png|none|thumb|alt=|843x843px|An example of Distributed Emergency Plugin applied to single building for a telescope farm|link=https://wiki.starkeeper.it/index.php/File:Distributed_Emergency_Plugin.png]]
 ==General Installation==
 Like all [[About Plugin|Voyager's Plugin]] you must purchase it separtely and import in Voyager the new license file. Import of the new license file will unlock the features requested from plugin, a restart of Voyager application is necessary to enable plugin after license import.
@@ Line 15: / Line 14: @@
 * Assure you have the MASTER Voyager and CLIENT Voyager on LAN in the same Network
 * Allow in Router policy and firewall rules to reach the port 5950 (or the port for Voyager Application server used) on The MASTER Voyager
 * Configure MASTER Voyager to get data from Weather system, Viking I/O system and ASCOM Safe system (one or all or at your needed). Refer to the base setup configuration of Voyager for this task
 * Configure MASTER Voyager to allow Distributed Emergency Status using the Application Server and Restart Voyager[image]

← Older revision		Revision as of 14:28, 4 February 2021
Line 52:		Line 52:

	== CLIENT Voyager DragScript Consideration ==		== CLIENT Voyager DragScript Consideration ==
−	~~Install plugin (importing the new license file)~~
−
−	~~== Some Advice about system ==~~
	Install plugin (importing the new license file)		Install plugin (importing the new license file)

@@ Line 41: / Line 41: @@
 * managing the supend/resume/exit events locally to open/close the roof for all (waiting the right positon of mounts if needed)
 * run forever restarting DragScript Itself
 [[File:DSMVDistributed.png]]{{Note|Be sure to check the mount position (if for example is parked) before open/close the ROOF. We suggest to use a dedicate I/O sensor to connect to the VIKING system installed in the MASTER Voyager. The plugin doesn't check the ASCOM parking status of remote CLIENT because is considered not SAFE. }}{{Note|Manage the UNRECOVERABLE Error, this error is something that compromise the normal running of the DragScript like : problem on opening roof, problem on closing roof. In this case add your signal to be informed and check as soon as possible status of building to avoid critical damages.}}