sudo apt-add-repository ppa:mutlaqja/ppa sudo apt-get update && sudo apt-get install libindi
This driver supports older Astro-Physics mounts (GTOCP2 or before). It can work for later mount models, but for such models, it's better to use other drivers with more functionality.
Current features of the driver:
When using the driver for the first time, ensure to set the correct port under the Connections tab. The primary and secondary telescope (if exists) aperture and focal lengths must also be set in the Options tab. If you do not have a secondary telescope, just put the same numbers as the primary there and click Set.
It is also necessary to set the geographic location and park position in the Site Management tab.
Do not try parking the mount until this position is defined!
Use a park azimuth of "0" and a park altitude equal to your latitude.
The "Default" button should pre-populate these fields with the proper values based on the geographic location you have specified.
Be sure to save these options using the "Save" button on the Options tab or else the changes will be loss when the driver is closed.
On connection, the mount must be initialized to set values for the date, time, location, etc.
There are two types of initialization:
When connected to the mount for the first time after powering on the mount use the COLD initialization option.
Use a WARM initialization if connecting to a mount which has already been initialized once using the COLD initialization and has NOT been powered down.
The mount will assume it is starting in the PARK3 park orientation - this is with the scope pointing at the pole and the counterweight straight down.
These are defined in this document from Astro-Physics: PARK POSITIONS
You must put the scope in this position when connecting to the mount!
The main control tab is where the primary control takes place.
To track an object, enter the equatorial of date (JNow) coordinates and press Set. The mount shall then slew to an object and once it arrives at the target location, it should engage tracking at the selected tracking rate which default to Sidereal tracking. Slew mode is different from track mode in that it does not engage tracking when slew is complete. To sync, the mount must be already tracking. First change mode to Sync, then enter the desired coordinates then press Set. Users will seldom use this interface directly since many clients (e.g. KStars) can slew and sync the mount directly from the sky map without having to enter any coordinates manually.
The Abort Motion button can be used to stop the mount at any time.
Four tracking modes are supported: Sidereal, Solar, Lunar, and Custom. When using Custom mode, the rates defined in Track Rates shall be used.
Tracking can be enganged and disenganged by toggling the Tracking property.
Mount parking and unparking is controlled by the Parking property.
The Use Pulse Cmd property can be enabled to guide the mount through the communications interface and eliminates the requirement of using an ST-4 cable to guide the mount.
The Firmware property shows the detected firmware version of the mount controller.
The Options tab is used to set debugging and other configuration options, as well as being able to load and save configurations.
If a dome is used in conjunction with the mount, a policy can be set if parking the mount or dome can interfere with the safety of either. For example, you might want to always park the mount before parking the dome, or vice versa. The default policy is to ignore the dome.
Under motion control, manual motion controls along with speed and guide controls are configured.
Time, Location, and Park settings are configured in the Site Management tab.
You can park the telescope by clicking on Park on the Main Control tab. If the telescope is already parked, click the park button to unpark it. You cannot perform any motion unless the telescope is first unparked!
Guide related option:
Slew Accuracy: Since legacry driver cannot know from the controller when the slew operation completed successfully, the driver employs another approach to determine when the slew is complete. By default, the drivers calculates the difference between the current mount position versus the target position. When the difference is within the Slew Accuracy threshold (default 3 arcminutes), it considers the slew to be complete. It is recommended to leave the value as-is.
If you find a bug, please report it at INDI's bug tracking system at GitHub.