Mount Setup - Revision history

Leonardo: /* Voyager Location Cache Manager */

2024-05-25T17:19:49Z

Voyager Location Cache Manager

Leonardo: /* Voyager Location Cache Manager */

2023-06-01T13:04:11Z

Voyager Location Cache Manager

Leonardo: /* Voyager Location Cache Manager */

2023-06-01T13:02:34Z

Voyager Location Cache Manager

Leonardo: /* Voyager Location Cache Manager */

2023-06-01T13:02:03Z

Voyager Location Cache Manager

Leonardo: /* Latitude / Longitude /Elevation -> Source */

2023-06-01T12:59:14Z

Latitude / Longitude /Elevation -> Source

Leonardo at 12:58, 1 June 2023

2023-06-01T12:58:29Z

Leonardo: /* Latitude / Longitude /Elevation -> Source */

2023-06-01T12:53:35Z

Latitude / Longitude /Elevation -> Source

Leonardo: /* Latitude / Longitude /Elevation -> Source */

2023-06-01T12:52:13Z

Latitude / Longitude /Elevation -> Source

Leonardo: /* Latitude / Longitude Position Override */

2023-06-01T12:37:52Z

Latitude / Longitude Position Override

Leonardo: /* Management */

2022-12-21T21:54:26Z

Management

@@ Line 195: / Line 195: @@
 An empty spaces or a - chars means empty cache, do at least one connection to the mount.
-{{Note|If you are using Mount control/driver like location source the location data will be retrieved in anycase at each connection of the mount in Voyager and the cache will be refreshed with the just readed values.}}
+{{Note|If you are using Mount control/driver like location source the location data will be retrieved in anycase at each connection of the mount in Voyager and the cache will be refreshed with the just readed values.}}{{Note|RoboOrbits take advantage of the Location cache to calculate the actual coordinates of a Dynamic Targets.}}
 {{Note|RoboOrbits take advantage of the Location cache to calculate the actual coordinates of a Dynamic Targets.}}
 =Other Setup Pages=
 <categorytree mode="pages" depth="1">Setup</categorytree>

← Older revision		Revision as of 13:04, 1 June 2023
Line 190:		Line 190:

	[[File:Immagineaa.png]]		[[File:Immagineaa.png]]
		+
		+	In order from the left : latitude, longitude, elevation in meters.
		+
		+	An empty spaces or a - chars means empty cache, do at least one connection to the mount.

	{{Note\|If you are using Mount control/driver like location source the location data will be retrieved in anycase at each connection of the mount in Voyager and the cache will be refreshed with the just readed values.}}		{{Note\|If you are using Mount control/driver like location source the location data will be retrieved in anycase at each connection of the mount in Voyager and the cache will be refreshed with the just readed values.}}

@@ Line 187: / Line 187: @@
 If you are using the fixed override flag in Voyager setup the cache is filled with the fixed location data.
-What is stored in Voyager Location Cache is reported in the status bar of the main Voyager window:
+What is stored in Voyager Location Cache is reported in the status bar of the [[Main Window|main Voyager window]]:
 [[File:Immagineaa.png]]

@@ Line 185: / Line 185: @@
 At first connection with the mount (if you have selected like location suorce the mount control/driver) Voyager will store in a permanent cache the location data that can be available for Voyager features also if you do not have the setup connected.
-If you are using the fixed override flag in Voyager setup the cache is filled with the fixed location data.{{Note|If you are using Mount control/driver like location source the location data will be retrieved in anycase at each connection of the mount in Voyager and the cache will be refreshed with the just readed values.}}
+If you are using the fixed override flag in Voyager setup the cache is filled with the fixed location data.
 {{Note|RoboOrbits take advantage of the Location cache to calculate the actual coordinates of a Dynamic Targets.}}
 =Other Setup Pages=

@@ Line 143: / Line 143: @@
 ** '''Longitude:''' Longitude of location expressed in DD MM SS (use E/W to invert the numeric value)
 ** '''Elevation :''' Elevation in meters of the Location
-* '''(*) Mount Control/Driver (Setup must be connected in Voyager):'''  Voyager will get informations about location directly from the mount control/driver. The get information Voyager need the setup is connected in Voyager. This mode benefit of the new cache location manager introduce with Voyager 2.3.8b.
+* '''(*) Mount Control/Driver (Setup must be connected in Voyager):'''  Voyager will get informations about location directly from the mount control/driver. The get information Voyager need the setup is connected in Voyager. This mode benefit of the new cache location manager introduce with Voyager 2.3.8b. See [[Mount Setup#Voyager Location Cache Manager|here]] about.
 {{Note|To apply changes to the Location configuration box you MUST restart Voyager or disconnect and reconnect the Setup. Without this action Voyager can continue to read the old settings.}}{{Note|If you use TheSkyX like mount control be sure that yoy location in use are the correct one and correctly filled.}}{{Note|About Elevation, some driver do not report any information about elevation. For example the iOptron mount drivers. In this case Voyager will retrieve a o meters value from the driver. Voyager can work without problem about, but if you are using dinamic target you can evaluate to have the elevation in place using the Use fixed data flag providing in Voyager latitude, longitude and elevation.}}
 == Custom Horizon ==

@@ Line 135: / Line 135: @@
 ==Latitude / Longitude /Elevation -> Source==
-If your mount driver doesn't report information about Latitude and Longitude or if you want to override the driver info you can input the location latitude and longitude directly here ion Voyager. Data from mount about this 2 values will be ignored.
+Please select the source of Mount Location for Voyager. Voyager need Latitude, Longitude and Elevation to work properly. If your mount driver doesn't report information about Latitude and Longitude or if you want to override the driver info you can input the location latitude and longitude directly here ion Voyager. Data from mount about this 3 values will be ignored.
 [[File:Immaginefevvdvsd.png]]
-{{Note|If you use TheSkyX like mount control in Voyager we suggest to use this way for manage the latitude and longitude data !}}
+* '''(*) Use This Fixed Data:'''  Voyager will override mount data with the data filled.
 == Custom Horizon ==
 Manage here azimuth and altitude table data to create your custom horizon.{{Note|The Features is used only by Voyager Advanced and Full during the RoboTarget scheduling process}}

@@ Line 134: / Line 134: @@
 <br />{{Note|'''DANGER:''' Voyager cannot guarantee that the tracking status will be restored to the previous values when the mount is reconnected. If a sequence is executed, activate the tracking control watchdog in the configuration. A lot of attention in using this flag activated with the mount connected to Voyager, in the observatory and with closed roof, risk of collisions. Be sure you have parked and driver itself not unpark at connect.}}<br />
-==Latitude / Longitude Position Override==
+==Latitude / Longitude /Elevation -> Source==
 If your mount driver doesn't report information about Latitude and Longitude or if you want to override the driver info you can input the location latitude and longitude directly here ion Voyager. Data from mount about this 2 values will be ignored.

@@ Line 42: / Line 42: @@
 *'''Precision Pointing Max Allowed Error''':  Maximum allowed error distance in arc-seconds when performing a [[Plate Solve Setup#Precision Pointing|precision pointing]] action
 *'''Use the best performance after finished pointing retries''':  Precision pointing will be done up to three times in an attempt to achieve an error less than the Precision Pointing Max Allowed Error.  If the error is still larger than the max allowed, if this setting is not checked, precision pointing will end with an ERROR condition.  If this setting is checked, the error will be accepted and precision pointing ends with an OK status.
-*'''Not Sync (Pointing Model Running)''':  Do not send sync commands to the mount after a [[Plate Solve Setup#Precision Pointing|precision pointing]] action.  You may prefer this choice if your mount is maintaining its own pointing model and you do not wish to add more sync points to it.  In this case, Voyager will use offsets to move the mount to fix errors found during the [[Plate Solve Setup#Precision Pointing|precision pointing]] operation.  Some mounts that maintain their own pointing model may need you to set a flag in the mount's software to allow Voyager to add new points to the model to refine pointing precision.  Consult your mount's documentation to determine if this is the case.{{Note|(*) Voyager by default Sync Mount on Solved Point. Be sure this is right for your mount if you have a model pointing !! For PARAMOUNT mounts remove the flag to avoid firmware model corruption.}}
+*'''Not Sync (Pointing Model Running)''':  Do not send sync commands to the mount after a [[Plate Solve Setup#Precision Pointing|precision pointing]] action.  You may prefer this choice if your mount is maintaining its own pointing model and you do not wish to add more sync points to it.  In this case, Voyager will use offsets to move the mount to fix errors found during the [[Plate Solve Setup#Precision Pointing|precision pointing]] operation.  Some mounts that maintain their own pointing model may need you to set a flag in the mount's software to allow Voyager to add new points to the model to refine pointing precision.  Consult your mount's documentation to determine if this is the case.{{Note|(*) Voyager by default Sync Mount on Solved Point. Be sure this is right for your mount if you have a model pointing !! For PARAMOUNT mounts do not remove the flag to avoid firmware model corruption.}}
 *'''UnPark on Connect''':  Issue an UnPark command after connecting the mount
 *'''Track on Connect''':  Issue a command to begin sidereal tracking after connecting the mount