Telescope Compatibility - Revision history

Didgeweb: Undo revision 12311 by Thebig-J (talk)

2012-07-05T03:51:33Z

Undo revision 12311 by Thebig-J (talk)

Thebig-J: Blanked the page

2012-07-04T19:12:31Z

Blanked the page

Barrykgerdes: /* Supported by the Telescope Control plug-in */

2011-08-25T03:26:02Z

Supported by the Telescope Control plug-in

Daggerstab: /* Supported by the Telescope Control plug-in */ + Sky-Watcher SynScan

2010-03-23T19:23:59Z

Supported by the Telescope Control plug-in: + Sky-Watcher SynScan

Daggerstab: the link is a bit of overkill

2010-03-16T18:22:31Z

the link is a bit of overkill

Daggerstab: splitting into two sections

2010-03-16T17:36:03Z

splitting into two sections

Rengolin: fixing name

2009-12-03T19:13:11Z

fixing name

Rengolin: skymax using nexstar

2009-12-03T19:12:21Z

skymax using nexstar

Pkubanek: add TelescopeServerRTS2 models

2009-09-03T00:25:42Z

add TelescopeServerRTS2 models

Jp perroud at 20:33, 7 July 2009

2009-07-07T20:33:25Z

← Older revision	Revision as of 03:51, 5 July 2012
Line 1:	Line 1:
	+	{{solar warning}}

	+	<span style="color: red; font-weight: bolder">Please read the explanation on the [[Telescope Control]] page first.</span>
	+
	+	This is an incomplete, badly maintained list of the telescopes, telescope mounts and other hardware that can be controlled by Stellarium without the help of third-party software.
	+
	+	== Supported by the Telescope Control plug-in ==
	+	:''Main page: [[Telescope Control plug-in]]''
	+
	+	The Telescope Control plug-in supports two classes of telescopes: telescopes compatible with the Meade LX200 (the Meade Autostar controller) and telescopes compatible with the Celestron NexStar. All devices listed in the "Device model" list are convenience definitions using one of the two classes.
	+
	+	The Telescope Control plug-in should work with:
	+	* Any telescope compatible with the '''Meade LX-200'''/Meade Autostar controller
	+	** the '''Meade ETX-70''' with the #494 Autostar controller and the #506 Connector Cable Set. It is a bit slow, so its default setting of "Connection delay" is 1.5 seconds instead of 0.5 seconds.
	+	** the '''Losmandy G11 (with gemini)''' telescope mount
	+	** the '''Wildcard Innovations Argo Navis''' Digital Telescope Computer (an advanced digital setting circle). Just don't forget to set it to Meade compatibility mode and set the baud rate to 9600B. [http://www.iceinspace.com.au/forum/showpost.php?p=554948&postcount=18]
	+	* Any telescope compatible with the '''Celestron NexStar'''
	+	** the '''Sky-Watcher SynScan AZ''' GOTO mount, used in a number of telescopes (a list is available at [http://www.opticalvision.co.uk/astronomical_telescopes/sky-watcher/sysncan_az_go-to_computerised_telescopes Optical Vision's website]). "SynScan" is also the name of the hand controller used in other Sky-Watcher GoTo mounts eg EQ6, HEQ5-Pro etc, and it seems that any mount that uses a SynScan controller version 3.0 or greater is supported by Stellarium, as it uses the NexStar protocol.
	+
	+	== Supported by the old telescope servers ==
	+	:''Main page: [[Telescope Control (client-server)]]''
	+
	+	The telescope server program (short: server) is a stand-alone program that can operate exactly one telescope, and can simultaneously serve one or many clients (like Stellarium). The terms server and client refer to the respective role in TCP/IP communication.
	+
	+	{\| cellpadding=2 border=1
	+	\| '''Make''' \|\| '''Model''' \|\| '''Operating System''' \|\| '''Server''' (see note 1) \|\| '''Status''' \|\| '''Notes'''
	+	\|-
	+	\| Meade \|\| Autostar \|\| Linux \|\| TelescopeServerLx200 \|\| style="background:orange" \| '''Untested''' \|\|
	+	\|-
	+	\| Meade \|\| Autostar \|\| Windows \|\| TelescopeServerLx200.exe \|\| style="background:green" \| '''Supported''' \|\| see note 2
	+	\|-
	+	\| Meade \|\| Autostar \|\| MacOS X \|\| TelescopeServerLx200 \|\| style="background:orange" \| '''Untested''' \|\| currently source code only
	+	\|-
	+	\| Meade \|\| LX200 \|\| Linux \|\| TelescopeServerLx200 \|\| style="background:green" \| '''Supported''' \|\| Original reference implementation, used by the developer
	+	\|-
	+	\| Meade \|\| LX200 \|\| Windows \|\| TelescopeServerLx200.exe \|\| style="background:green" \| '''Supported''' \|\| Original reference implementation, seems to work well with different kinds of Windows
	+	\|-
	+	\| Meade \|\| LX200 \|\| MacOS X \|\| TelescopeServerLx200 \|\| style="background:orange" \| '''Untested''' \|\| currently source code only
	+	\|-
	+	\| Losmandy \|\| G11 \|\| Linux/Windows \|\| TelescopeServerLx200(.exe) \|\| style="background:green" \| '''Supported''' \|\| successfully used by some guy in the forum
	+	\|-
	+	\| Celestron \|\| NexStar \|\| Linux/Windows \|\| TelescopeServerNexStar(.exe) \|\| style="background:orange" \| '''Untested''' \|\| by Michael Heinz
	+	\|-
	+	\| Celestron \|\| NexStar \|\| Mac \|\| TelescopeServerNexStar \|\| style="background:green" \| '''Supported''' \|\| by Michael Heinz
	+	\|-
	+	\|-
	+	\| SkyWatcher \|\| SkyMax 127 GOTO \|\| Linux \|\| TelescopeServerNexStar \|\| style="background:green" \| '''Supported''' \|\| by Renato Golin
	+	\|-
	+	\|-
	+	\| Astelco \|\| full range (OpenTPL) \|\| Linux, Solaris \|\| TelescopeServerRTS2 \|\| style="background:green" \| '''Supported''' \|\| see note 3
	+	\|-
	+	\|-
	+	\| CAHA \|\| 1.23m \|\| Solaris \|\| TelescopeServerRTS2 \|\| style="background:green" \| '''Supported''' \|\| see note 3
	+	\|-
	+	\|-
	+	\| Software Bisque \|\| Paramount \|\| Linux \|\| TelescopeServerRTS2 \|\| style="background:green" \| '''Supported''' \|\| see note 3
	+	\|-
	+	\|-
	+	\| Astrolab \|\| various custom models \|\| Linux \|\| TelescopeServerRTS2 \|\| style="background:green" \| '''Supported''' \|\| see note 3
	+	\|-
	+	\|}
	+
	+	===Notes===
	+	# The name of the binary should uniquely identify the telescope communication protocol it is using for communicating with the telescope. Naming convention for programmers: The name of the driver refers to the ''class'' in the driver source code. This is usually similar to the name of the resulting binary (program), but to be certain, look inside the .hpp file which is used to make the binary. It might be a good idea to adopt the convention of making the resulting binary have the same name as the driver class.
	+	#Autostar ETX70 with 494 controller and 506 cable. The original telescopeserverLX200.exe was too fast for the slow link connection to the 494 controller. The problem has been repaired with the latest version of TelescopeServerLx200.exe. To get a smoother move of the cross hair edit the time delay in the config.ini file from 500000 to 1500000. B.G
	+	#RTS2: for RTS2 models, you will need RTS2 driver. You can obtain it from [[http://rts2.org]].
	+
	+	[[Category:Telescope Control]]
	+	[[Category:Telescope]]

← Older revision		Revision as of 19:12, 4 July 2012
Line 1:		Line 1:
−	~~{{solar warning}}~~

−	~~<span style="color: red; font-weight: bolder">Please read the explanation on the [[Telescope Control]] page first.</span>~~
−
−	~~This is an incomplete, badly maintained list of the telescopes, telescope mounts and other hardware that can be controlled by Stellarium without the help of third-party software.~~
−
−	~~== Supported by the Telescope Control plug-in ==~~
−	~~:''Main page: [[Telescope Control plug-in]]''~~
−
−	The Telescope Control plug-in supports two classes of telescopes: telescopes compatible with the Meade LX200 (the Meade Autostar controller) and telescopes compatible with the Celestron NexStar. All devices listed in the "Device model" list are convenience definitions using one of the two classes.
−
−	~~The Telescope Control plug-in should work with:~~
−	* Any telescope compatible with the '''Meade LX-200'''/Meade Autostar controller
−	** the '''Meade ETX-70''' with the #494 Autostar controller and the #506 Connector Cable Set. It is a bit slow, so its default setting of "Connection delay" is 1.5 seconds instead of 0.5 seconds.
−	** the '''Losmandy G11 (with gemini)''' telescope mount
−	** the '''Wildcard Innovations Argo Navis''' Digital Telescope Computer (an advanced digital setting circle). Just don't forget to set it to Meade compatibility mode and set the baud rate to 9600B. [http://www.iceinspace.com.au/forum/showpost.php?p=554948&postcount=18]
−	* Any telescope compatible with the '''Celestron NexStar'''
−	** the '''Sky-Watcher SynScan AZ''' GOTO mount, used in a number of telescopes (a list is available at [http://www.opticalvision.co.uk/astronomical_telescopes/sky-watcher/sysncan_az_go-to_computerised_telescopes Optical Vision's website]). "SynScan" is also the name of the hand controller used in other Sky-Watcher GoTo mounts eg EQ6, HEQ5-Pro etc, and it seems that any mount that uses a SynScan controller version 3.0 or greater is supported by Stellarium, as it uses the NexStar protocol.
−
−	~~== Supported by the old telescope servers ==~~
−	~~:''Main page: [[Telescope Control (client-server)]]''~~
−
−	The telescope server program (short: server) is a stand-alone program that can operate exactly one telescope, and can simultaneously serve one or many clients (like Stellarium). The terms server and client refer to the respective role in TCP/IP communication.
−
−	~~{\| cellpadding=2 border=1~~
−	~~\| '''Make''' \|\| '''Model''' \|\| '''Operating System''' \|\| '''Server''' (see note 1) \|\| '''Status''' \|\| '''Notes'''~~
−	\|-
−	~~\| Meade \|\| Autostar \|\| Linux \|\| TelescopeServerLx200 \|\| style="background:orange" \| '''Untested''' \|\|~~
−	\|-
−	~~\| Meade \|\| Autostar \|\| Windows \|\| TelescopeServerLx200.exe \|\| style="background:green" \| '''Supported''' \|\| see note 2~~
−	\|-
−	~~\| Meade \|\| Autostar \|\| MacOS X \|\| TelescopeServerLx200 \|\| style="background:orange" \| '''Untested''' \|\| currently source code only~~
−	\|-
−	~~\| Meade \|\| LX200 \|\| Linux \|\| TelescopeServerLx200 \|\| style="background:green" \| '''Supported''' \|\| Original reference implementation, used by the developer~~
−	\|-
−	~~\| Meade \|\| LX200 \|\| Windows \|\| TelescopeServerLx200.exe \|\| style="background:green" \| '''Supported''' \|\| Original reference implementation, seems to work well with different kinds of Windows~~
−	\|-
−	~~\| Meade \|\| LX200 \|\| MacOS X \|\| TelescopeServerLx200 \|\| style="background:orange" \| '''Untested''' \|\| currently source code only~~
−	\|-
−	~~\| Losmandy \|\| G11 \|\| Linux/Windows \|\| TelescopeServerLx200(.exe) \|\| style="background:green" \| '''Supported''' \|\| successfully used by some guy in the forum~~
−	\|-
−	~~\| Celestron \|\| NexStar \|\| Linux/Windows \|\| TelescopeServerNexStar(.exe) \|\| style="background:orange" \| '''Untested''' \|\| by Michael Heinz~~
−	\|-
−	~~\| Celestron \|\| NexStar \|\| Mac \|\| TelescopeServerNexStar \|\| style="background:green" \| '''Supported''' \|\| by Michael Heinz~~
−	\|-
−	\|-
−	~~\| SkyWatcher \|\| SkyMax 127 GOTO \|\| Linux \|\| TelescopeServerNexStar \|\| style="background:green" \| '''Supported''' \|\| by Renato Golin~~
−	\|-
−	\|-
−	~~\| Astelco \|\| full range (OpenTPL) \|\| Linux, Solaris \|\| TelescopeServerRTS2 \|\| style="background:green" \| '''Supported''' \|\| see note 3~~
−	\|-
−	\|-
−	~~\| CAHA \|\| 1.23m \|\| Solaris \|\| TelescopeServerRTS2 \|\| style="background:green" \| '''Supported''' \|\| see note 3~~
−	\|-
−	\|-
−	~~\| Software Bisque \|\| Paramount \|\| Linux \|\| TelescopeServerRTS2 \|\| style="background:green" \| '''Supported''' \|\| see note 3~~
−	\|-
−	\|-
−	~~\| Astrolab \|\| various custom models \|\| Linux \|\| TelescopeServerRTS2 \|\| style="background:green" \| '''Supported''' \|\| see note 3~~
−	\|-
−	\|}
−
−	~~===Notes===~~
−	# The name of the binary should uniquely identify the telescope communication protocol it is using for communicating with the telescope. Naming convention for programmers: The name of the driver refers to the ''class'' in the driver source code. This is usually similar to the name of the resulting binary (program), but to be certain, look inside the .hpp file which is used to make the binary. It might be a good idea to adopt the convention of making the resulting binary have the same name as the driver class.
−	#Autostar ETX70 with 494 controller and 506 cable. The original telescopeserverLX200.exe was too fast for the slow link connection to the 494 controller. The problem has been repaired with the latest version of TelescopeServerLx200.exe. To get a smoother move of the cross hair edit the time delay in the config.ini file from 500000 to 1500000. B.G
−	~~#RTS2: for RTS2 models, you will need RTS2 driver. You can obtain it from [[http://rts2.org]].~~
−
−	~~[[Category:Telescope Control]]~~
−	~~[[Category:Telescope]]~~

@@ Line 13: / Line 13: @@
 * Any telescope compatible with the '''Meade LX-200'''/Meade Autostar controller
 ** the '''Meade ETX-70''' with the #494 Autostar controller and the #506 Connector Cable Set. It is a bit slow, so its default setting of "Connection delay" is 1.5 seconds instead of 0.5 seconds.
-** the '''Losmandy G11''' telescope mount
+** the '''Losmandy G11 (with gemini)''' telescope mount
 ** the '''Wildcard Innovations Argo Navis''' Digital Telescope Computer (an advanced digital setting circle). Just don't forget to set it to Meade compatibility mode and set the baud rate to 9600B. [http://www.iceinspace.com.au/forum/showpost.php?p=554948&postcount=18]
 * Any telescope compatible with the '''Celestron NexStar'''
-** the '''Sky-Watcher SynScan AZ''' GOTO mount, used in a number of telescopes (a list is available at [http://www.opticalvision.co.uk/astronomical_telescopes/sky-watcher/sysncan_az_go-to_computerised_telescopes Optical Vision's website]). "SynScan" is also the name of the hand controller used in other Sky-Watcher GoTo mounts, and it seems that any mount that uses a SynScan controller version 3.0 or greater is supported by Stellarium, as it uses the NexStar protocol.
+** the '''Sky-Watcher SynScan AZ''' GOTO mount, used in a number of telescopes (a list is available at [http://www.opticalvision.co.uk/astronomical_telescopes/sky-watcher/sysncan_az_go-to_computerised_telescopes Optical Vision's website]). "SynScan" is also the name of the hand controller used in other Sky-Watcher GoTo mounts eg EQ6, HEQ5-Pro etc, and it seems that any mount that uses a SynScan controller version 3.0 or greater is supported by Stellarium, as it uses the NexStar protocol.
 == Supported by the old telescope servers ==

@@ Line 16: / Line 16: @@
 ** the '''Wildcard Innovations Argo Navis''' Digital Telescope Computer (an advanced digital setting circle). Just don't forget to set it to Meade compatibility mode and set the baud rate to 9600B. [http://www.iceinspace.com.au/forum/showpost.php?p=554948&postcount=18]
 * Any telescope compatible with the '''Celestron NexStar'''
 == Supported by the old telescope servers ==

@@ Line 15: / Line 15: @@
 ** the '''Losmandy G11''' telescope mount
 ** the '''Wildcard Innovations Argo Navis''' Digital Telescope Computer (an advanced digital setting circle). Just don't forget to set it to Meade compatibility mode and set the baud rate to 9600B. [http://www.iceinspace.com.au/forum/showpost.php?p=554948&postcount=18]
 * Any telescope compatible with the '''Celestron NexStar'''

@@ Line 1: / Line 1: @@
 {{solar warning}}
-This page lists telescope control drivers and their compatibility with various models.
+<span style="color: red; font-weight: bolder">Please read the explanation on the [[Telescope Control]] page first.</span>
 {| cellpadding=2 border=1
@@ Line 42: / Line 61: @@
 |}
+===Notes===
-==Notes==
+# The name of the binary should uniquely identify the telescope communication protocol it is using for communicating with the telescope. Naming convention for programmers: The name of the driver refers to the ''class'' in the driver source code. This is usually similar to the name of the resulting binary (program), but to be certain, look inside the .hpp file which is used to make the binary.  It might be a good idea to adopt the convention of making the resulting binary have the same name as the driver class.
-#The telescope server program (short: Server) is a stand alone program that can operate exactly one telescope, and can simultanousely serve one or many clients (like stellarium). The terms ''server'' and ''client'' refer to the respective role in TCP/IP communication. The name of the binary should uniquely identify the telescope communication protocol it is using for communicating with the telescope. Naming convention for programmers: The name of the driver refers to the ''class'' in the driver source code. This is usually similar to the name of the resulting binary (program), but to be certain, look inside the .hpp file which is used to make the binary.  It might be a good idea to adopt the convention of making the resulting binary have the same name as the driver class.
 #Autostar ETX70 with 494 controller and 506 cable. The original telescopeserverLX200.exe was too fast for the slow link connection to the 494 controller. The problem has been repaired with the latest version of TelescopeServerLx200.exe. To get a smoother move of the cross hair edit the time delay in the config.ini file from 500000 to 1500000. B.G
 #RTS2: for RTS2 models, you will need RTS2 driver. You can obtain it from [[http://rts2.org]].
-[[Category:Telescope Control]][[Category:Telescope]]
+[[Category:Telescope Control]]

@@ Line 26: / Line 26: @@
 |-
 |-
-| SkyMax || 127 GOTO || Linux || TelescopeServerNexStar || style="background:green" | '''Supported''' || by Renato Golin
+| SkyWatcher || SkyMax 127 GOTO || Linux || TelescopeServerNexStar || style="background:green" | '''Supported''' || by Renato Golin
 |-
 |-

@@ Line 24: / Line 24: @@
 |-
 | Celestron || NexStar || Mac || TelescopeServerNexStar || style="background:green" | '''Supported''' || by Michael Heinz
 |-
 |-

← Older revision		Revision as of 20:33, 7 July 2009
Line 31:		Line 31:
	#Autostar ETX70 with 494 controller and 506 cable. The original telescopeserverLX200.exe was too fast for the slow link connection to the 494 controller. The problem has been repaired with the latest version of TelescopeServerLx200.exe. To get a smoother move of the cross hair edit the time delay in the config.ini file from 500000 to 1500000. B.G		#Autostar ETX70 with 494 controller and 506 cable. The original telescopeserverLX200.exe was too fast for the slow link connection to the 494 controller. The problem has been repaired with the latest version of TelescopeServerLx200.exe. To get a smoother move of the cross hair edit the time delay in the config.ini file from 500000 to 1500000. B.G

−	[[Category:Telescope Control]]	+	[[Category:Telescope Control]][[Category:Telescope]]