My Android App provides a list of addresses in its connection activity to accomplish this setup. Once paired there is sometimes a unique Bluetooth Address that must be set in the application that will be talking to OnStep.Other devices/operating systems have similar facilities for pairing. The typical Android phone or tablet has a Bluetooth pairing facility in the settings menu to accomplish this. Each Bluetooth Client must be paired with the Server.

Workarounds range from modifying h/w to disable the mechanism to using other connection methods.Ī basic direct wireless connection is Bluetooth/Serial. Sometimes this causes problems, sometimes not.

In the case of my ASCOM driver it takes steps (and has additional user settings) to prevent this from happening in most cases but due to the near infinite variety of boards/knockoffs/etc. This is due to the automatic firmware upload mechanism designed for the Arduino IDE.

Tip: some boards are prone to being reset when opening the USB/Serial port.

By default OnStep uses 9600 baud, though some devices disregard the baud rate and communicate at much higher speeds (Teensys, some STM32.).

This connection is generally regarded as reliable and fast (low latency.).

Note however using ASCOM or INDI overcomes this limitation and allows sharing the one connection.

This allows for only one application to connect at a time.

This is usually how the OnStep ASCOM driver talks to OnStep and is often the same serial port where you uploaded the OnStep Sketch to.

The basic connection is on OnStep's USB/Serial port. This section provides an overview of how applications on the various supported devices connect to OnStep and how to configure those connections.

Telescope control with stellarium