OnStepX Telescope Controller

What is OnStepX?

OnStepX is the advanced version of the OnStep computerized telescope controller with support for both stepper motors (step/dir interface) and servo motors (PD or II interface using AB quadrature or CW/CCW or Pulse/Dir encoders.)

It supports:

• Telescope Mount control (Alt/Azm and Equatorial GEM/Fork.) Optional support for Eq mounts with Tangent Arm Declination. Usually the Goto capability is enabled, but that's optional as well for those who just want basic mount control.
• Telescope Rotator control (including Alt/Azm de-rotation.)
• Telescope Focuser control (up to 6 focusers so it can handle collimation as well as focusing.)
• Telescope Accessory control (combination of up to 8 dew-heaters, switches, analog PWM.)

Features

OnStepX supports a wide variety of connection options. Several serial "command channels" can be utilized. One of the these is normally devoted to a USB connection and for the other(s) choose from the following:

• Bluetooth
• ESP8266 WiFi
• Arduino M0/Ethernet Shield
• Even another USB port or RS232 serial isn't very difficult to add.

In the case of running OnStepX on an ESP32 it can provide its own Bluetooth or WiFi IP command channels without additional hardware by simply activating the feature in OnStepX.

Other software in the OnStep ecosystem include:

• an ASCOM driver (with IP and Serial support),
• an Android App useable over WiFi or Bluetooth equipped Phones/Tablets,
• a "built-in" website (on the Ethernet and/or WiFi device),
• a full planetarium program that controls all features (Sky Planetarium).

ASCON

In the early days of computer-assisted astronomy, devices came with their own "computer control" (usually ASCII over RS-232).One such protocol was the so-called LX-200 standard, derived from the commands published by Meade Instruments Corporation for use with their Meade LX-200 series of telescopes. The LX-200 protocol was copied by other mount makers so their mounts would run with apps that spoke "LX200". But each mount maker eventually customized their mount's ASCII commands because their mounts had unique features, so these protocols diverged and became unique. Other high-end mounts had their own unique ASCII or TCP/IP protocols from the outset. A few kept their control protocol private and provided their own apps (software hand boxes or planetariums) completely locking out others from controlling the mount.