tuesday

src/content/docs/mounts/astrotrac/astrotrac-360/astrotrac-360.md

@@ -0,0 +1,111 @@
+---
+title: Astrotrac 360
+categories: ["mounts"]
+description: Astrophysics V2
+thumbnail: ./astrotrac-360.webp
+---
+
+## Features
+
+This INDI Astrotrac driver interacts with Astrotrac mounts via WiFi. It fully supports all the mount features and provides support for a mount model powered by  [INDI Alignment Subsystem](https://www.indilib.org/api/md_libs_indibase_alignment_alignment_white_paper.html). This results in highly accurate GOTOs when used with a plate solving software (e.g. Ekos) as the driver compensates for differences between the sky and mount coordinates on the fly.
+
+Current features are:
+
+-   Goto/Slew/Sync.
+-   Park/Unpark with configurable custom parking positions.
+-   Custom tracking rates
+-   Custom acceleration rates
+-   Guiding
+-   Sidereal, lunar, solar and custom trackrates
+-   Full joystick support
+-   Mount modelling
+
+![Main Control](./images/main_control.webp)
+
+## Connectivity
+
+The driver communicates with the mount over the netwrok. Therefore, before establishing connection to the mount, you must set the mount's IP address and port in the  _Connection_  tab. Please ensure the machine running the driver is on the same network as the mount so they can talk to each other.
+
+![Connection](./images/connection.webp)
+
+Please note 2 ways to connect RA/DEC drives
+
+1.  RA power first then once on then after 15 or so seconds connect cable from RA to DEC , that should trigger the RA to configure the DEC as a DEC automatically
+2.  However with some peoples mounts that doesn’t happen due to some issue that Richard from Astrotrac does not know how to fix in which case you have to manually configure the DEC drive as a DEC drive:
+    1.  In this case you can connect the RA and DEC connecting cable before powering on everything or after it does not matter
+    2.  You then connect to the drive you will configure as a DEC drive and connect to its wifi (AstroTrac360:RA:XX.XX.XX.XX) from any device can be same or for example your phone. Navigate to the IP address via the browser and go to the console (in the UI)
+    3.  You type 1i50 and hit enter
+    4.  The drive will now disconnect itself and in a few moments will appear as AstroTrac360:DEC:XX.XX.XX.XX ( WHERE XX IS THE IP address OF YOUR DRIVE)
+    5.  Now the RA drive will be able to send commands via the cable to control the DEC drive
+
+For more information on communication with the mount, you can check a  [detailed INDI thread](https://www.indilib.org/forum/mounts/10366-astrotrac-360-indi-driver-documentation-development.html)  on the subject.
+
+## Operation
+
+By default, the mount type is set to  **German-Equatorial (GEM)**  and can be switched to  **Single-ARM**  mode if desired. This must be done  _before_  connecting to the mount.
+
+### Main Control
+
+The main control tab is where the primary control of Astrotrac 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  _rarely_  use this driver controls 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.
+
+Four tracking modes are supported: Sidereal, Lunar, Solar, 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. The units are arcseconds per second.
+
+### Options
+
+Under the options tab, you can configure many parameters before and after you connect to the mount.
+
+![Options](./images/options.webp)
+
+-   **Snoop Devices**: Indicate which devices Paramount should communicate with:
+    -   **GPS**: If using a GPS driver (e.g. INDI GPSD) then enter its name here. EQMod shall sync its time and location settings from the GPS driver.
+    -   **Dome**: If using a Dome driver, put its name here so that Dome Parking Policy can be applied.
+-   **Configuration**: Load or Save the driver settings to a file. Click default to restore default settings that were shipped with the driver.
+-   **Simulation**: Enable to disable simulation mode for testing purposes.
+-   **Debug**: Enable debug logging where verbose messaged can be logged either directly in the client or a file. If Debug is enabled, advanced properties are created to select how to direct debug output. [Watch a video on how to submit logs](https://stellarmate.com/support/logs-submission.html).
+-   #### Dome Parking Policy
+
+    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.
+
+    -   **Ignore dome**: Take no action when dome parks or unparks.
+    -   **Dome locks**: **Prevent** the mount from unparking when dome is parked.
+    -   **Dome parks**: Park the mount if dome starts parking. This will disable the locking for dome parking, EVEN IF MOUNT PARKING FAILS.
+    -   **Both**: Dome locks & Dome parks policies are applied.
+-   **Scope Properties**: Enter the Primary and Seconday scope information. Up to six different configurations for _Primary_ and Secondary _Guider_ telescopes can be saved separately, each with an optional unique label in **Scope Name** property.
+-   **Scope Config**: Select the active scope configuration.
+-   **Joystick**: Enable or Disable joystick support. An INDI Joystick driver must be running for this function to work. For more details, check the [INDI Telescope Joystick](https://stellarmate.com/support/tutorials/135-controlling-your-telescope-with-a-joystick.html) tutorial.
+
+### Motion Control
+
+![Motion Control](./images/motion_control.webp)
+
+Under motion control, manual motion controls along with speed and guide controls are configured.
+
+-   **Motion N/S/W/E**: Directional manual motion control. Press the button to start the movement and release the button to stop.
+-   **Slew Rate**: Rate of manual motion control above when 1x equals sidereal rate. This feature is currently not supported in the firmware since the slew speed is fixed to 10800 arcsec per sec.
+-   **Acceleration**: Acceleration rates per axis in arcseconds per seconds squared. The mount uses this value to accelerate from rest to the full slew speed (currently fixed at 10800 arcsecs per sec by the mount firmware).
+-   **Encoders**: Displays the current Hour-Angle (HA) and Declination (DE) axis encoder values in degrees. You can manually command the mount to move to a specific encoder position by changing this property.
+-   **Guide N/S/W/E**: Guiding pulses durations in milliseconds. This property is meant for guider application (e.g. PHD2) and not intended to be used directly.
+
+### Site Management
+
+Time, Locaiton, and Park settings are configured in the Site Management tab.
+
+![Site Management](./images/site_management.webp)
+
+-   **UTC**: UTC time and offsets must be set for proper operation of the driver upon connection. The UTC offset is in hours. East is positive and west is negative.
+-   **Location**: Latitude and Longitude must be set for proper operation of the driver upon connection. The longitude range is 0 to 360 degrees increasing eastward from Greenwich.
+-   **Parking**: By default, the parking position is when the OTA to be looking directly at the celestial pole. To restore parking position to the default value, please Default under Park option. You can set a custom parking position using two methods. The mount must be unparked before you can set a new position:
+    -   Enter the desired HA & DE encoder values for the custom parking position, then press Set and then press Write Data to save the new parking position.
+    -   Slew the mount to the desired parking position, then press Current to sync the encoders position to this value, and then Write Data to save.
+
+You can park the telescope by clicking on Park. If the telescope is already parked, click the park button to unpark it. You cannot perform any motion unless the telescope is first unparked!
+
+If you are using KStars as your INDI client, you can click on any object or location on the Sky Map and then set it as the desired parking position as illustrated below:
+
+![Site Management](./images/kstars_set_custom_park.webp)
+
+### Alignment
+
+The mount model utilized by the driver is managed by the properties in the alignment tab. Each time a sync point is added (by Plate solving software for example), the  _Current Set_  size is incremented by one. To save the list to disk so that it can be utilized in a future session, click on the  **Action to take**  dropdown and select  _Save the alignment database to local storage_  then press  **OK**  next to  _Execute Action_  property. For best results, change the  **Math Plugins**  to use the  _Nearest Math Plugin_  since it is very simple and reliable when used with plate-sovling software. For more complicated modelling, select  _SVG Math Plugin_
+
+![Alignment](./images/alignment.webp)

src/content/docs/mounts/astrotrac/astrotrac-360/astrotrac-360.yaml

@@ -0,0 +1,11 @@
+# Display Names (Human-Friendly)
+driver_name: AstroPhysics V2
+categories: ["mounts"]
+manufacturer_name: Astrotrac
+
+# Additional Metadata
+website: www.astrotrac.com
+executable: indi_astrotrac_telescope
+platforms: Linux, BSD, MacOS
+author: Jasem Mutlaq
+version: 1.0

src/content/docs/mounts/avalon-instruments/avalon-star-go/avalon-star-go.md

@@ -0,0 +1,162 @@
+---
+title: Avalon
+categories: ["mounts"]
+description: Avalon
+thumbnail: ./avalon-star-go.webp
+---
+
+## Installation
+
+The INDI Avalon StarGO driver is released as a 3rd party driver and requires INDI Library >= v1.7.5. To install the driver under Ubuntu:
+
+sudo apt-add-repository ppa:mutlaqja/ppa
+sudo apt-get update && sudo apt-get install indi-avalon
+
+## Features
+
+This INDI driver interacts with the StarGO GoTo Control System from  [Avalon Instruments](http://www.avalon-instruments.com/)  through a USB connection. It can directly drive Avalon mounts and other mounts that are controlled by StarGO.
+
+Current features are:
+
+-   Goto/Slew
+-   Slewing speeds ...
+-   Sidereal, lunar and solar trackrates
+-   Configurable custom parking positions
+-   Pulse-guiding
+-   ST4 Guiding
+-   Focussing
+
+The StarGO device also contains support for up to two stepper motors like focusers. The implementation herefore is at a very early stage.
+
+## Connectivity
+
+Currently, the INDI driver only supports connections to the StarGO Control System through a USB cable. Please connect the computer running the INDI driver via USB to the StarGO device of your mount.
+
+## Operation
+
+### Connecting the StarGO Device
+
+In order to establish the connection to the StarGO device, switch to the  **Connection**  tab and select the appropriate USB connection:
+
+![avalon connection tab](./images/avalon_connection.webp)
+
+Select the appropriate USB device where StarGO is connected to. In case the device is not visible, press **Scan Ports**. The  **Baud rate**  can be left untouched as long as  **Auto select**  is set to **Enabled**, which leads to a automatic detection of the right baud rate. Please leave the **Connection mode**  to **Serial**, changing to **Ethernet**  has no effect.
+
+Then switch to the  **Main Control**  tab and press  **Connect:**
+
+![2019 04 20 064454 972x775 scrot](https://indilib.org/images/2019-04-20-064454_972x775_scrot.png)
+
+### Main Control
+
+The main control tab is where the primary control takes place. As soon as  **Connect**  has been pressed, the entire set of option unfolds.
+
+As you may know from the Windows/ASCOM client, you need to press  **Sync home**  before the mount reacts to slewing etc. The other controls on this tab are more or less straight forward:
+
+-   **Abort motion**: stops the motion of the scope
+-   **Track mode**: set to  **sideral**  (star tracking),  **solar**  (sun tracking),  **lunar**  (moon tracking) or  **none**  (no tracking at all)
+-   **Tracking**: turn tracking on and off
+-   **Parking**: slew to the (predefined) parking position and  **park**  the scope. Remember, that you need to  **unpark** the scope before you can slew it somewhere
+-   **Pier side**: read only information on which pier side the scope is currently placed
+-   **Use pulse guiding**: in case that you want to guide through pulse guiding instead of ST4, turn this option on
+-   **Aux1 Focuser**: Enable or disable a focuser connected on the AUX1 port of the StarGO device.  **Please set to disabled as long as no focuser is present.**
+-   **Home position**: sync the current position as the home position. At the same time, the pointing model is initialized
+-   **Goto home**: slew to the home position defined above and turn off tracking
+-   **Set park**: set the current scope position as park position
+
+### Alignment
+
+Position the mount in its home position and press  **Sync Home**  on the **Main Control**  tab. Now the tracking mode is enabled and the mount can be slewed to arbitrary positions. StarGO manages its own pointing model. Each time a **Sync**  is called, StarGO adds a new entry in its pointing model.
+
+The best results can be achieved, when plate solving is used for building up an appropriate pointing model.
+
+### Options
+
+On the options tab, you can setup various debugging options and scope properties.
+
+![avalon options](https://stellarmate.com/images/devices/avalon/avalon_options.png)
+
+Most of them are straight forward and general INDI functions. Maybe some need explanation:
+
+-   **Polling**: here you define the frequency, how often the INDI client asks the INDI server for updates. 1sec is a typical value
+-   **Scope Properties**: set here the right parameters of your main scope and the guiding scope.  _Hint_: if you have  **problems with plate solving**, check here, if the values are correct.
+
+### Motion Control
+
+With this tab you can manually slew the mount in all directions at different slewing speeds.
+
+![avalon motion control](https://stellarmate.com/images/devices/avalon/avalon_motion_control.png)
+
+### Site Management
+
+On the Site Management tab you can configure the location of your scope. If you are using KStars, it is recommended to set it through the Geographic Location of KStars and configure KStars such that it updates time and site for INDI.
+
+![avalon site management](https://stellarmate.com/images/devices/avalon/avalon_site_management.png)
+
+### Guiding
+
+Don't change anything here unless you know what you are doing.
+
+![avalon guide](https://stellarmate.com/images/devices/avalon/avalon_guide.png)
+
+### RA/DEC
+
+This tab is dedicated to guiding options.
+
+![avalon ra dec](https://stellarmate.com/images/devices/avalon/avalon_ra_dec.png)
+
+-   **Autoguiding**: set the guiding speeds. For Avalon mounts, please follow the [recommendations of Avalon Instruments](http://www.avalon-instruments.com/support/13-troubleshooting/117-phd2-guide-suggested-parameters)
+-   **ST4**: enable or disable guiding through the ST4 port of your guiding camera. In case you set it to **enabled**, do not forget to connect your guiding camera with the ST4 port of the StarGO device
+-   **Meridian flip**: set the behaviour of the next slew command. If set to **auto**, the mount executes a meridian flip automatically. In case of **disabled**, no meridan flip takes place. And inversly, for **forced**  a meridian flip is executed although it was not necessary from the scope position. **If you do not know what you are doing, please leave it on auto!**
+
+### General Info
+
+This tab displays the current firmware version.
+
+![avalon general info](https://stellarmate.com/images/devices/avalon/avalon_general_info.png)
+
+**AUX1 Focuser**
+
+Here you can control a focuser connected to the **AUX 1**  port of the StarGO device.
+
+![2019 04 20 064508 972x775 scrot](https://stellarmate.com/images/2019-04-20-064508_972x775_scrot.png)
+
+With this tab you can control a focuser connected to the AUX1 port of the StarGO device:
+
+-   **Direction**: The direction in which the focuser moves when a relative position is set.
+-   **Speed**: Speed of the focuser moves (not appropriately tested yet).
+-   **Timer**: Update interval of the tab.
+-   **Absolute Postion**: Move the focuser to an absolute position.
+-   **Relative Position**: Move the focuser in or out by a given number of steps according to the direction selected above.
+-   **Abort**: Stop the movement of the focuser.
+-   **Sync**: Set the current focuser position to a defined value (e.g. set it to 0 if the focuser is entirely drawn in).
+-   **Direction**: Here you can switch the directions if your focuser operates the other way round.
+
+<!--
+
+Firmware
+
+Firmware tab displays information on the detected mount type and firmware version. Furthermore, the RA/DE steps, frequencies, and gear ratios are displayed.
+
+![eqmod firmware](https://stellarmate.com/images/devices/eqmod/eqmod_firmware.png)
+
+### Motor Status
+
+The stepper motors positions and work periods are displayed in addition to the status of each motor. If the mount is equipment with auxiliary encoders, then their position shall be displayed
+
+![eqmod motor status](https://stellarmate.com/images/devices/eqmod/eqmod_motor_status.png)
+
+### Alignment
+
+By default the alignment mode is set to N-Star, every time you perform a sync, a new sync point is added to the model. You need to save the alignment points file if you want the driver to utilize them on the next startup. You can perform all these operations in the  _Align_  tab. The EQMod driver is currently transition to the INDI Alignment Subsystem and this section shall be updated when the transition is over to avoid duplicate information.
+
+Under Options, you can select to utilize INDI's Alignment Subsystem instead of EQMod's own alignment system. However, the Alignment Subsystem is currently not stable so it is recommended to use EQMod alignment system which is on by default.
+
+### PEC
+
+PEC training works the same way as with the handcontroller. Guide on a star, engage PEC training and the firmware will wait for the mount pass the worm indexer and then records the resulting speeds in the EEPROM of the motor microcontroller. When it has finished (worm indexer) it toggles a status bit and you can see in the INDI Control panel the status of PEC training becoming green (whereas it remains busy/yellow while training).
+
+PEC/PEC training is enabled in INDI EQMod for mounts which supports it, EQ8, AZEQ5/6, EQ6R too apparently. It is a motor controller firmware feature, the INDI driver just sends the corresponding commands to start/stop PEC/PEC training and do not then bother about it. Please note that the firmware PEC+guiding may not be a good idea as the firmware changes the motor speed unconditionnally, so some guide commands may be lost.
+
+### Horizon Limits
+
+For horizon limit just slew to the points along the horizon you want to set and hit the Add current button. The order of points is significant as Horizon uses a linear approximation between them. When you have finished hit the Write File button (saved in ~/.indi/HorizonData.txt which you can manually edit also).

src/content/docs/mounts/avalon-instruments/avalon-star-go/avalon-star-go.yaml

@@ -0,0 +1,12 @@
+# Display Names (Human-Friendly)
+driver_name: Avalon StarGo
+categories: ["mounts"]
+manufacturer_name: Avalon Instruments
+
+# Additional Metadata
+executable: indi_lx200stargo
+platforms: Linux, BSD, MacOS
+author: Wolfgang Reissenberger
+version: 1.7
+
+

src/content/docs/mounts/bresser/messier-exos-2/messier-exos-2.md

@@ -0,0 +1,9 @@
+---
+title: BRESSER Messier EXOS-2 EQ GoTo
+categories: ["mounts"]
+description: BRESSER Messier EXOS-2 EQ GoTo
+thumbnail: ./messier-exos-2.webp
+---
+
+> [!NOTE]
+> There is no available documentation for this driver. Please help us document this driver by submitting a [Pull Request](https://github.com/indilib/drivers-docs).