From Stellarium Wiki
Revision as of 22:45, 8 August 2006 by Johannes
This page lists telescope control drivers and their compatibility with various models.
|Make||Model||Operating System||Server (see note 1)||Status||Notes|
|Meade||Autostar||Windows||TelescopeServerLx200.exe||Supported||see note 2, please send a logfile!|
|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|
- The telescope server program (short: Server) is a stand alone program that can operate exactly one telescope, and can 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. Cross hair appears and telescopeserverLX200.exe polls telescope but the telescope fails to move when request is made. This has been tested on three different installations. Has anyone else checked this it could be a difference with the 494 controller that is not on the 496/7. B.G