16. Devices

  • Telescope

  • Cameras

  • Focusers

  • Filter wheels

  • Auxiliary

  • Adaptive optics

  • Weather stations

  • Covers & light sources

  • Domes

  • Controllers

  • Spectrographs

16.1. Mounts

Following mounts are supported in StellarMate:
  • Celestron

  • SkyWatcher

  • Astrophysics

  • Omegon

  • Vixen

  • IOptron

  • Meade

  • Orion

Mount Name

Driver Executable

10 Micron

indi_lx200_10micron

AHP GT Mount

indi_ahpgt_telescope

AOK Skywalker

indi_lx200aok

LX200 FS2

indi_lx200fs2

Astrotrac 360

indi_astrotrac_telescope

Avalon StarGo

indi_lx200stargo

Paramount

indi_paramount_telescope

BRESSER Messier EXOS-2 EQ GoTo

indi_bresserexos2

Celestron GPS

indi_celestron_gps

CRUX TitanTCS

indi_crux_mount

Digital Setting Circle

indi_dsc_telescope

Explore Scientific PMC-Eight

indi_pmc8_telescope

HEQ-5 MCU Update

indi_lx200basic

iOptron HC8406

indi_ioptronHC8406

LX200 Basic

indi_lx200basic

Pegasus NYX-101

indi_lx200_pegasus_nyx101

OpenAstroTech

indi_lx200_OpenAstroTech

Losmandy

indi_lx200gemini

LittleFoot Vpower

indi_lx200basic

Planewave

indi_planewave_telescope

Pulsar2

indi_lx200pulsar2

Rainbow

indi_rainbow_telescope

SkyAdventurer GTi

indi_skyadventurergti_telescope

SkyCommander

indi_skycommander_telescope

SkySafari

indi_skysafari

SkySensor2000PC

lx200ss2000pc

Star Adventurer 2i WiFi

indi_staradventurer2i_telescope

STAR2000

indi_star2000

SynScan Legacy

indi_synscanlegacy_telescope

Takahashi Temma

indi_temma_telescope

TeenAstro Mount

indi_lx200_TeenAstro

Telescope Scripting Gateway

indi_script_telescope

ZWO AM5

indi_lx200am5

16.1.1. Celestron

Before connecting to your mount 1. Ensure the mount firmware is the latest as provided by your manufacturer. 2. Ensure mount has proper and suffcient power to operate. This is often a primary source of issues connecting to mounts. 3. Read the mount manual and learn about the mount startup or Home Position. This is the mechanical position the mount must be in before you turn on the power to the mount. This basically falls under three categories:

Equatorial Mount: Telescope should be looking at the Celestial Pole (Polaris for the Northern Hemisphere) with counter-weights down. Alt-Az Mount: Telescope should parallel to the ground looking exactly North (for Northern Hemisphere) or South (for Southern hemisphere). Alt-Az Mount on Wedge: Telescope should be looking at Celestial Equator due South (for Northern Hemisphere) or Celestial Equator Due North (for Southern hemisphere).

  1. Decide on how you will connect to the mount. Is it using a cable to the handset? or cable directly to the mount? WiFi? Bluetooth?

  2. If connecting over WiFi, then ensure the device where you are running the INDI driver (e.g. Raspberry PI4) is on the same network as your mount so they can communicate with each other. Such mounts can be configured to run in two modes:

    Mount Wireless Hotspot Mode: The mount hotspot acts as the router and you can connect your devices to the mount’s own network (e.g. your Raspberry PI and iPad). Mount Wireless Station Mode: The mount joins an existing WiFi network (e.g. your home WiFi network or StellarMate hotspot). The IP address assigned to the mount is determined by your router. It is best to know the IP address assigned to the mount so that you can enter it in the IP address field in the driver Connection tab. However, this is not strictly necessary since the driver can automatically scan the local network for mounts, albeit this operation may take a few minutes to complete whereas if the IP address is known beforehand then the connection is immediate.

Selecting the correct driver Selecting the appropiate driver for your mount usually depends on two factors: 1. Mount model. 2. Naming Convention: Driver labels can indicate which communication method they use

HC: Hand Controller or Hand Set (e.g. Celestron Advanced VX HC) Wired: AUX/PC Port (e.g. Celestron Advanced VX Wired) WiFi: WiFi connection (e.g. Celestron Advanced VX WiFi)

  1. Connection method (AUX Port, PC Port, Handset, WiFI, ..etc).

Mount

Driver

Connection Method

Comments

Advanced AVX

Celestron GPS

Serial-to-USB

Older Nexstar HCs come with RJ9 plug. You need Serial-to-USB adapter cable from HC to PC/Device. Modern Nexstar HCs come with USB Type-B port that you can connect directly via a USB cable to your device (no serial to USB adapter is required).

When connecting via Nexstar Handset (HC), there is a single driver (Celestron GPS). The rest of the drivers (e.g. Celestron CPC..etc) are aliases to the base Celestron GPS driver.

You must power and align your mount using the handset using any supported alignment method (e.g. SkyAlign). Without aligning your mount first, the driver will not connect to the handset.

Advanced AVX WiFi

Celestron WiFi

WiFi

WiFi drivers automatically try to connect to the mount over WiFi (Default IP address 1.2.3.4 using TCP port 2000). If your mount is using a different IP address, set it in the Connection tab of the INDI driver.

Handset is not required and no alignment is necessary before establishing connection to the mount.

If using a Wedge, make sure to only select “Evolution WiFi Wedge” driver.

CGEM / CGEM II WiFi

Celestron WiFi

WiFi

Same as above

CGX / CGX-L WiFi

Celestron WiFi

WiFi

Same as above

Evolution WiFi

Celestron WiFi

WiFi

Same as above

Advanced AVX

Celestron AUX

Wired

Wired AUX or PC Port (located on top of the base of the scope). Under driver Connection tab: Set Connection Mode to Serial. Set Port Type to AUX/PC.

Handset is not required and no alignment is necessary before establishing connection to the mount.

CGEM / CGEM II

Celestron AUX

Wired

Same as above

CGX / CGX-L

Celestron AUX

Wired

Same as above

CPC

Celestron AUX

Wired

Same as above

Advanced VX

Celestron AUX

Wired

Same as above

CGEM II Wired

Celestron AUX

Wired

Same as above

CGX Wired

Celestron AUX

Wired

Same as above

16.1.2. SkyWatcher

All SkyWatcher & Orion Mounts, including EQMod driver.

Before connecting to your mount Ensure the mount firmware is the latest as provided by your manufacturer. Ensure mount has proper and suffcient power to operate. This is often a primary source of issues connecting to mounts. Read the mount manual and learn about the mount startup or Home Position. This is the mechanical position the mount must be in before you turn on the power to the mount. This basically falls under two categories: Equatorial Mount: Telescope should be looking at the Celestial Pole (Polaris for the Northern Hemisphere) with counter-weights down. Alt-Az Mount: Telescope should parallel to the ground looking exactly North (for Northern Hemisphere) or South (for Southern hemisphere). Decide on how you will connect to the mount. Is it using a cable to the handset? or cable directly to the mount? WiFi? Bluetooth? If connecting over WiFi, then ensure the device where you are running the INDI driver (e.g. Raspberry PI4) is on the same network as your mount so they can communicate with each other. Such mounts can be configured to run in two modes: Mount Wireless Hotspot Mode: The mount hotspot acts as the router and you can connect your devices to the mount’s own network (e.g. your Raspberry PI and iPad). Mount Wireless Station Mode: The mount joins an existing WiFi network (e.g. your home WiFi network or StellarMate hotspot). The IP address assigned to the mount is determined by your router. It is best to know the IP address assigned to the mount so that you can enter it in the IP address field in the driver Connection tab. However, this is not strictly necessary since the driver can automatically scan the local network for mounts, albeit this operation may take a few minutes to complete whereas if the IP address is known beforehand then the connection is immediate. Selecting the correct driver Selecting the appropiate driver for your mount usually depends on two factors:

Mount model. Connection method (Cable, WiFI, Bluetooth..etc).

Mount

Driver

Connection Method

Comments

HEQ5

EQMod Mount

EQDirect Cable

This cable is a DIRECT cable from mount to your device. No handset is connected nor required in this setup. Astroshop.eu EQDirect Cables. OPT Corp EQDirect Cables.

EQ6

EQMod Mount

EQDirect Cable

Same as above

EQ6R Pro

EQMod Mount

EQDirect Cable

Same as above

AZ-EQ5

EQMod Mount

EQDirect Cable

Same as above

AZ-EQ6 Pro

EQMod Mount

EQDirect Cable

Same as above

EQ8

EQMod Mount

EQDirect Cable

Same as above

EQ8 Pro

EQMod Mount

EQDirect Cable

Same as above

EQ3 Pro

EQMod Mount

EQDirect Cable

Same as above

EQM-35 Pro

EQMod Mount

EQDirect Cable

Same as above

Orion Sirrius

EQMod Mount

EQDirect Cable

Same as above

Orion Atlas

EQMod Mount

EQDirect Cable

Same as above

HEQ5

EQMod Mount

Bluetooth

Use a Bluetooth adapter from Mount to your device. You must pair and trust the Bluetooth dongle first from your PC/Device. The dongle should create a serial port (e.g. /dev/rfcomm0) that you need to select when connecting to the mount.

Quite a few EQMod Bluetooth dongles have been obsoleted. Therefore, it is generally NOT recommended to connect to your Mount using bluetooth.

EQ6

EQMod Mount

Bluetooth

Same as above

EQ6R Pro

EQMod Mount

Bluetooth

Same as above

AZ-EQ5

EQMod Mount

Bluetooth

Same as above

AZ-EQ6 Pro

EQMod Mount

Bluetooth

Same as above

EQ8

EQMod Mount

Bluetooth

Same as above

EQ8 Pro

EQMod Mount

Bluetooth

Same as above

EQ3 Pro

EQMod Mount

Bluetooth

Same as above

EQM-35 Pro

EQMod Mount

Bluetooth

Same as above

Orion Sirrius

EQMod Mount

Bluetooth

Same as above

Orion Atlas

EQMod Mount

Bluetooth

Same as above

HEQ5

EQMod Mount

Synscan Wifi Adapter

Select Network in EQMod Connection tab. Ensure IP address is correct before establishing connection to the mount.

Do not use EQMod Mount driver to connect to any Alt-Az mount via the dongle, EQMod Mount driver can only operate Equatorial Mounts.

EQ6

EQMod Mount

Synscan Wifi Adapter

Same as above

EQ6R Pro

EQMod Mount

Synscan Wifi Adapter

Same as above

AZ-EQ5

EQMod Mount

Synscan Wifi Adapter

Same as above

AZ-EQ6 Pro

EQMod Mount

Synscan Wifi Adapter

Same as above

EQ8

EQMod Mount

Synscan Wifi Adapter

Same as above

EQ8 Pro

EQMod Mount

Synscan Wifi Adapter

Same as above

EQ3 Pro

EQMod Mount

Synscan Wifi Adapter

Same as above

EQM-35 Pro

EQMod Mount

Synscan Wifi Adapter

Same as above

Orion Sirrius

EQMod Mount

Synscan Wifi Adapter

Same as above

Orion Atlas

EQMod Mount

Synscan Wifi Adapter

Same as above

AZ-GTi WiFi (With Equatorial Wedge)

AZ-GTi Equatorial WiFi

WiFi

AZ-GTi mount must be running firmware v3.37+ (Right ARM, AZ/EQ Dual Mode).

AZ-GTi

AZ-GTi Wired

WiFi

WIRED cable from AZ-GTi RJ12 port to USB. For Equatorial mode, AZ-GTi mount must be running firmware v3.37+ (Right ARM, AZ/EQ Dual Mode).

AZ-GTi (Alt-Az)

SkyWatcher Alt-Az WiFi

WiFi (Native)

WiFi Native is the WiFi that comes with the mount built-in without any external adapters.

All SkyWatcher Dobsonian GOTOs

SkyWatcher Alt-Az WiFi

WiFi (Native)

Same as above

All Orion Dobsonian GOTOs

SkyWatcher Alt-Az WiFi

WiFi (Native)

Same as above

Any SkyWatcher/Orion with Synscan Handset (HC)

Synscan

Serial-to-USB

Older Synscan HCs come with RJ11 plug. You need Serial-to-USB adapter cable from HC to PC/Device. Modern Synscan HCs come with USB Type-B port that you can connect directly via a USB cable to your device (no serial to USB adapter is required).

Synscan driver offers a limited subset of features compared to other drivers. If possible connect using EQDirect cable or WiFi.

SkyWatcher Virtuoso

SkyWatcher Virtuoso

WiFi

SkyWatcher Star Adventurer 2i Pro

SkyWatcher Star Adventurer

WiFi

SkyWatcher Star Adventurer 2i WiFi

SkyWatcher Star Adventurer

WiFi

Same as above

SkyWatcher Star Adventurer 2i Pro

SkyWatcher Star Adventurer

USB

Direct USB cable from Mount to PC/Device.

SkyWatcher Star Adventurer 2i WiFi

SkyWatcher Star Adventurer

USB

Same as above

SkyWatcher Star Adventurer

SkyWatcher Star Adventurer

NA

This driver is the INDI Telescope Simulator. It can be used just as a placeholder if you have the older non-GOTO Star Adventurer mount.

16.1.3. Astrophysics

INDI Library supports Astrophyics range of mounts. Due to the evolution of AP mounts over the years, the protocol used to communicate with the mount naturally evolved. INDI provides three drivers you can select from to best suit your mount.

How is meridian flip handled? The meridian flip feature is handled by the AstroPhysics GTO controller. The INDI driver does not handle that logic for these mounts. For this to work properly you would need to be sure to do the following:

The controller has to be initialized with the proper location and time (daylight savings set appropriately, UTC offset, etc.)

If you have a good polar alignment then a one star sync is needed or if you have a rough polar alignment then a 2 star sync will do. This initialization is done with the hand control or the INDI driver when using your client (e.g. KStars) so be sure you have all the proper settings in the client. Once this is done properly then your mount will do a meridian flip after it receives a goto command and the object has crossed the meridian. For example if you were imaging an object and during the exposure it crossed the meridian and you have the setting in you client (e.g. the Ekos image tab) set to flip meridian if HA>0 then before the next exposure starts a new goto command is issued to the same object by the client and the mount will know to flip as the controller handles the logic.

Mount

Driver

Devices

Comments








16.1.4. Omegon

Omegon mounts are a collection of Alt-Az and Equatorial mounts for visual observation and astrophotography.

Mount

Driver

Devices

Comments

EQ500X

indi_eq500x_telescope

16.1.5. Vixen

Mount

Driver

Devices

Comments

Starbook

indi_starbook_telescope

16.1.6. IOptron

  1. Which driver is right for my mount?

Due to the many versions of Hand Controller (HC) and RS232 Command Set versions for all the iOptron mounts released, it can be confusing to select which driver

is appropiate for your mount.

  1. Why are the mount GOTOs offset by one hour?

Make sure to turn OFF Daylight Saving (DST) setting in the mount hand set (HC). It must be off at all times.

  1. Why dithering causes big jumps in RA and DE?

Make sure to turn OFF Periodic Error Correction (PEC) in the handset.

  1. Why is the mount not performing meridian flip as expected?

You have to let the mount track some time AFTER CROSSING MERIDIAN, otherwise MF is not going to happen. In iOptron driver, the Meridian Behaviour setting Flip or Stop does not matter here, since Meridian Flip will be triggered by the client (e.g. Ekos); but the Limit you set does matter. Basic rule is:

0 < Client Limit < Mount Limit

Example: set Client (e.g. Ekos) to trigger MF 3° after crossing the meridian, and set mount limit to 6° after crossing meridian. You must set the 6° in the iOptron INDI driver.

Ekos limit should be greater than 0, because Ekos and mount must exactly agree on which side on the meridian we are: allowing to track some degree after crossing it, relaxes the precision needed and accounts for small difference in models and approximations between Ekos and mount firmware.

Mount limit should be greater then Ekos limit, because some time is usually needed to complete the running capture when filp time occurs (should be: MOUNT LIMIT - EKOS LIMIT > LONGEST EXPOSURE PLANNED). And MOUNT LIMIT should be small enough to avoid the mount smashing your equipment on a tripod leg.

Mount

Driver

Connection Method

Comments

iOptronV3

indi_ioptronv3_telescope

Serial-to-USB

Direct connection from mount to device

GotoNova 8400 Kit

lx200gotonova

Serial-to-USB

The driver supports the following Gotonova 8400 based controllers

CEM60

indi_ieq_telescope

Serial-to-USB

Firmware 140807 and later

CEM60-EC

indi_ieq_telescope

Serial-to-USB

Firmware 140807 and later

iEQ45 Pro

indi_ieq_telescope

Serial-to-USB

Firmware 140807 and later

iEQ45 Pro AA

indi_ieq_telescope

Serial-to-USB

Firmware 140807 and later

ZEQ25

indi_lx200zeq25

Serial-to-USB

Direct connection from mount to device

SmartEQ

indi_lx200zeq25

Serial-to-USB

Same as above

iEQ30

indi_lx200zeq25

Serial-to-USB

Same as above

iEQ45 EQ/AA

indi_lx200zeq25

Serial-to-USB

Same as above

16.1.7. Meade

INDI supports all Meade mounts via a number of drivers tailored to each model family (Classic, GPS..etc). The only mount that is NOT support is Meade LS since it uses a serial chip that fails to work with Linux & MacOS. There is no support from Meade on Meade LS.

Mount

Driver

Devices

Comments

LX200 Autostar

indi_lx200gps

ETX LX50 LX90 LX200

LX200 16

indi_lx200_16

LX200 Classic

indi_lx200classic

LX200 GPS

indi_lx200gps

16.1.8. Orion

Mount

Driver

Connection Method

Devices

Comments

SynScan

indi_synscan_telescope

Serial-to-USB

Snoop devices
GPS

Dome

16.2. Cameras

CCDs, Autoguiders & Webcams

Cameras

Driver

Devices

Comments

Altair

indi_altair_ccd

Apogee CCD

indi_apogee_ccd

Atik

indi_atik_ccd

Nightscape 8300 CCD

indi_nighscape_ccd

GPhoto CCD

indi_gphoto_ccd

FLI CCD FLI CFW FLI PDF

indi_fli_ccd

indi_fli_wheel indi_fli_focus

INova

indi_nova_ccd

V4L2 CCD

indi_v4l2_ccd

Lacerta MGen Autoguider

indi_mgenautoguider

Meade DSI Pro (I/II)

indi_dsi_ccd

MI CCD

indi_mi_ccd

Pentax DSLR (Native)

indi_pentax

PlayerOne CCD

indi_palyerone_ccd

QHY CCD

indi_qhy_ccd

QSI CCD

indi_qsi_ccd

RPI Camera

indi_rpicam

SBIG CCD

indi_sbig_ccd

SVBony

indi_svbony_ccd

Toupcam

indi_toupcam_ccd

V4L2 CCD (Duplicate)

indi_v4l2_ccd

INDI Webcam

indi_webcam_ccd

ASI CCD

indi_asi_ccd

16.3. Focusers

Devices

Driver

Comments

Focusers

Focusers

ActiveFocuser

indi_activefocuser_focus

Armadillo/Platypus

indi_armadillo_focus/

Astroberry Focuser

indi_rpifocus

AstroLink 4

indi_astrolink4

Astromechanics

indi_astromechfoc

Baader SteelDrive

indi_steeldrive_Focus

Bee Focuser

indi_beefocus

Celestron SCT

indi_celestron_sct_focus

DeepSkyDad FP1

indi_deepskydad_fp1

DeepSkyDad FR1

indi_deepskydad_fr1

DeepSkyDad AF1

indi_deepskydad_af1_focus

DeepSkyDad AF2

indi_deepskydad_af2_focus

DeepSkyDad AF3

indi_deepskydad_af3_focus

FLI CCD FLI CFW FLI PDF

indi_fli_ccd indi_fli_wheel indi_fli_focus

CCD Driver: indi_fli_ccd, Filter Wheel Driver:

indi_fli_wheel, Focuser Driver: indi_fli_focus

FocusLynx

indi_lynx_focus

Integra

indi_integra_focus

JMI MOTOFOCUS

indi_lx200classicautostar

SmartFocus

indi_smartfocus_focus

Lacerta MFOC

indi_lacerta_mfoc_focus

Meade 1206 Primary Mirror Focuser

indi_lx200classic

LX200 Autostar

indi_lx200autostar

MoonLite

indi_moonlite_focus

myFocuserPro2

indi_myfocuserpro2_focus

Nightcrawler

indi_nightcrawler_focus

Gemini Focusing Rotator

indi_gemini_focuser

Optec TCF-S

indi_tcfs_focus/indi_tcfs3_focus

Pegasus DMFC

indi_dmfc_focus

Pegasus Falcon

indi_falcon_rotator

RainbowRSF

indi_rainbowrsf_focus

RBFocus

indi_rbfocus_focus

nFocus

indi_nfocus

Rigelsys nFrame

indi_nframe_rotator

Rigelsys nStep

indi_nstep_focus

RoboFocus

indi_robo_focus

Seletek Rotator

indi_seletek_rotator

Sesto Senso

indi_sestosenso_focus

FCUSB

indi_fcusb_focuser

USBFocusV3

indi_usbfocusv3_focus

ASI EAF

indi_asi_focuser

16.4. Filter Wheels

Filter wheels

Driver

Devices

Comments

FLI CCD FLI CFW FLI PDF

indi_fli_ccd

indi_fli_wheel indi_fli_focus

Optec IFW

indi_optec_wheel

QHY CCD

indi_qhy_ccd

QSI CCD

indi_qsi_ccd

Quantum Wheel

indi_quantum_wheel

Baader SBIG CCD

indi_sbig_ccd

Starlight Xpress Filter Wheel

indi_sx_wheel

TruTech

indi_trutech_wheel

XAGYL Wheel

indi_xagyl_wheel

ASI EFW

indi_asi_wheel

16.5. Auxiliary

Auxiliary devices, spectrometers, sensors, encoders, switches, motor..etc

CCDs, Autoguiders & Webcams

Auxialiaries

Driver

Devices

Comments

AstroLink 4

indi_astrolink4

Astromechanics LPM

indi_astromech_lpm

DeepSkyDad FP1

indi_deepskydad_fp1

GPSD

indi_gpsd

GPS NMEA

indi_gpsnmea

GPUSB

indi_gpusb

Java Raspberry Pi GPIO

i4jRaspberryPiGPIODriver

MyDCP4ESP32

indi_mydcp4esp32

Pegasus UPB

indi_pegasus_upb

Seletek

I4JSeletekDriver

SQM

indi_sqm_weather

USB_Dewpoint

indi_usbdewpoint

Watchdog

indi_watchdog

16.6. Adaptive Optics

Optics

Driver executable

Devices

Comments

Starlight Xpress AO

indi_sx_ao

16.7. Weather Stations

Weather stations, cloud & rain detectors…

Stations

Driver

Devices

Comments

AAG Cloud Watcher

indi_aagcloudwatcher

Vantage

indi_vantage_weather

MBox

indi_mbox_weather

Sky Quality Meter-LU

I4JSQMDriver

WeatherMeta

indi_meta_weather

Weather Safety Proxy

indi_weather_safety_proxy

Weather Watcher

indi_weatherwatcher

WeewxJSON

indi_weewx_json

16.8. Covers & Light Sources

Dust Covers & Flat Light Sources

Sources

Driver

Devices

Comments

Wanderer Cover V3

indi_wanderer_cover

FlipFlat

indi_flipflat

SnapScap

indi_snapcap

ALTO

indi_alto

GIOTTO

indi_giotto

16.9. Domes

INDI Dome support includes all observatory enclosures of different designs such as roll-off roofs, regular domes, and clamshell-style domes.

To implement your own roll-off roof driver, here are the basic requirements: Hardware 1. AC/DC Motor: The motor must be electronically controllable either via a relay or a controller board (Arduino..etc). The only controls needed are start/stop and direction control (CW and CCW). In INDI, a fully opened roof is considered Unparked, while a fully closed roof is considered Parked. Anything between these two (partially open) is considered an Unknown state. 2. Limit switches: Fully closed and fully opened limit switches are required in order to sense when the roof is fully opened and closed. These limit switches serves two purposes:

  1. Cut off power to motor once limit is reached.

  2. Sense when roof is parked or unparked.

Therefore, Motor + 2 limit switches is all you need to have a working roll-off roof hardware system to be used with INDI.

Software The roll-off roof requires an INDI driver so that it can be controlled from any INDI-compatible client. You can either use the Dome Scripting Gateway driver or customize the sample INDI roll-off driver to fit your needs. The Dome Scripting Gateway driver relies on executing Python scripts to command actions for Open and Close. It is recommended to use this driver if you have limited programming expereince but can manage to write simple Python script to control your motor.

Customizing the INDI Roll-off driver is optimal if you know some rudementary C++. Here are some real-world examples of roll-off drivers to get you started:

Aldi Roof Driver: The roof is powered by a 550W electric hoist purchased from Aldi. The arduino controls 4 relays connected to the hoist’s hand controller which override the manual switch. The indi driver comminicates with the arduino using the frimata protocol. Ikarus Observatory Driver: Using Digital Loggers Din Relay, Limit switches, Raspberry PI Arduino Roll Off Driver: It is a INDI rolloff roof driver and includes two examples of Arduino programs communicating over USB. The driver is packaged as a third party driver but haa not been included with the standard distribution. The Arduino code needs to be modified to match the motor control selected, the INDI driver should work once installed. Odroid INDI Roof: This indi driver is used to control an observatory box. It is just a very compact box with an automated lid, opened by two linear actuators, 2 micro-switches act as position sensors (open/close). The all lot is powered by an Odroid-C1 and a standard 8 relays board.

Dome Slaving** Dome slaving refers to the dome slit synchronization with the telescope position as the mount traverse across the sky. The dome slit follows the telescope whether is is slewing from one object to another, or while tracking. When tracking, the dome would move when the difference between its current and target postion exceeds the Autosync Threshold parameter, which default to 0.5 degree. Therefore, the dome calculates its target position every second, but only commands motion when the difference exceeds the autosync threshold.

You can slave the dome to the mount by setting the required slaving parameters:

  1. Radius is for the radius of the dome in meters.

  2. Shutter width is the clearance of the shutter of the dome in meters

  3. N displacement is for North displacement. If telescope is not in its ideal central position this parameter allows to configure how much it is displaced from the center. Displacement to north are positive, and to south are negative.

  4. E displacement is for East displacement. Similar as the above, displacement to east are positive, and to west are negative.

  5. Up displacement is for displacement in the vertical axis. Up is positive, down is negative.

  6. OTA offset is for the distance of the optical axis to the crossing point of RA and DEC. In fork mount this is generally 0, but for German like mounts is the distance from mount axis cross to the center line of the telescope. West is positive, east is negative.

After settings the parameters above, go to Options tab and click Save in Configurations so that the parameters are used in future sessions. You can also set the Autosync threshold which is the minimum distance autosync will move the dome. Any motion below this threshold will not be triggered. This is to prevent continuous dome moving during telescope tracking.

Dome is not correctly slaving 1. Make sure that the dome azimuth movement and position are correct and repeatable. If the azimuth is incorrect or not repeatable you will never get a good sync. Good means to withing a couple of degrees. 2. Align the mount. For a celestron GEM that’s polar aligned a quick align should be good enough but once again you can’t get a good sync without a good alignment. Within a degree should do. 3. Set the dome radius to a sensible value, Do not change it again. 4. Set the mount to hour angle 6h, declination 90. This is the Align position, looking at the pole with the counterweight shaft down. In this position the OTA offset will have no effect on the dome azimuth, not will the NS position of the mount. 5. Adjust the mount EW offset until the scope is looking through the centre of the dome slit. 6. Move the mount so the counterweight shaft is horizontal and the OTA is looking at the Southern horizon. In this position the main things that affect where the dome needs to be are the EW mount offset and the OTA offset.

We have already set the EW offse so set the OTA offset. Try this with the mount on both side of the meridian and iterate as required to get the scope able to see out in both cases. set the scope so it is looking at the East or west horizon, this should be with the dec counterweight shaft pointing down. Adjust the Ns offset so the OTA can see out. Do this both looking East and West.

Debugging Calculations Ferran Casarramona, the developer of the Dome Slaving routine, wrote a spreadsheet to debug the calculations. You can make a copy and play with it to see how parameters affects the outcome.

You can enter the values in blue cells, and output are in the orange cells. You enter your telescope parameters, and your latitude. Also enter target declination and target hour angle (angular distance to the meridian, in hours).

Domes

Driver

Devices

Comments

DDW Dome

indi_ddw_dome

Baader Dome

indi_baader_dome

DragonFly Dome

indi_dragonfly_dome

NexDome Beaver

indi_nexdome_beaver

MaxDomeII

indi_maxdomeii

NexDome

indi_nexdome

Rigel Dome

indi_rigel_dome

ScopeDome

indi_scopedome_dome

Talon6

indi_talon6

16.10. Controllers

Joysticks & Game pads

Controllers

Driver

Devices

Comments

Joystick

indi_joystick

16.11. Spectrographs

Spectrographs, radio and optical

Spectrograph

Driver

Devices

Comments

RTL-SDR

indi_rtlsdr