|⚠||WARNING: Stellarium CANNOT prevent your telescope from being pointed at the Sun.||☀|
If you abuse this feature to point your telescope to the sun and ruin your telescope, your eyes, your children's eyes or whatever, then this is not our fault, but yours.
Please read the explanation on the Telescope Control page first.
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 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. 
- Any telescope compatible with the Celestron NexStar
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.
|Make||Model||Operating System||Server (see note 1)||Status||Notes|
|Meade||Autostar||Windows||TelescopeServerLx200.exe||Supported||see note 2|
|Meade||Autostar||MacOS X||TelescopeServerLx200||Untested||currently source code only|
|Meade||LX200||Linux||TelescopeServerLx200||Supported||Original reference implementation, used by the developer|
|Meade||LX200||Windows||TelescopeServerLx200.exe||Supported||Original reference implementation, seems to work well with different kinds of Windows|
|Meade||LX200||MacOS X||TelescopeServerLx200||Untested||currently source code only|
|Losmandy||G11||Linux/Windows||TelescopeServerLx200(.exe)||Supported||successfully used by some guy in the forum|
|Celestron||NexStar||Linux/Windows||TelescopeServerNexStar(.exe)||Untested||by Michael Heinz|
|Celestron||NexStar||Mac||TelescopeServerNexStar||Supported||by Michael Heinz|
|SkyWatcher||SkyMax 127 GOTO||Linux||TelescopeServerNexStar||Supported||by Renato Golin|
|Astelco||full range (OpenTPL)||Linux, Solaris||TelescopeServerRTS2||Supported||see note 3|
|CAHA||1.23m||Solaris||TelescopeServerRTS2||Supported||see note 3|
|Software Bisque||Paramount||Linux||TelescopeServerRTS2||Supported||see note 3|
|Astrolab||various custom models||Linux||TelescopeServerRTS2||Supported||see note 3|
- 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 [].