This page describes different software tools which provide PC control of your OAT, camera and other devices.
In exceptional cases, the computer may not see the OAT connected via USB. The first thing to check is that the USB cable used is of sufficient quality (some cables shipped from China with the motherboard can cause problems). Test if the cable allows you to use it with another verified device (printer etc). If the cable is OK, you need to make sure that the necessary drivers are installed on the PC. This should be done when installing the Arduino IDE and after connecting and loading some script into the motherboard, if you are using only VS and platformio you may need to install the CH340 driver.
OATControl is a remote control tool developed by the OAT team. It allows tools for calibration and basic control of the OpenAstroTracker.
In order to control OAT from a Windows PC, you need to download and isntall OATControl:
ASCOM is a many-to-many and language-independent architecture, supported by most astronomy devices which connect to Windows and now Linux and MacOS computers.
Many (if not even most) astrophotography tools are built on top of ASCOM. These are mostly tools for automation of devices like mounts, guiding cameras, main cameras, optical filters, sensors, observatories etc. Some of these tools control only one part of astrophotography setup, others allow complete automation of all the devices and sequencing session. The main benefit of the ASCOM architecture is that it acts as an interface between devices and software tools. This way a device supported by ASCOM is also supported by all the software tools around it.
In order to connect OAT through ASCOM, you need to download and install
NOTE: You might need to scroll a bit for the ASCOM Drivers, since we release new OATControl version way more often than new ASCOM Driver versions)
If you successfully installed the drivers, you should be able to see "OpenAstroTracker" in any astronomy program's mount/telescope chooser.
The following describes how to configure your OAT to be used remotely with any computer running compatible INDI software, so long as it can connect to the Astroberry's wireless hotspot. For example, you can have your OAT and Pi outside in the cold, while you're inside on your computer of choice and control everything remotely using the Astroberry's INDI services. Think of the Astroberry as a server that you're connecting to rather than a Desktop you're accessing remotely.
This guide is NOT how to use Astroberry as the main interface via it's remote desktop functionality - as such, using it in this way is nearly identical - you're just not doing some weird remote desktop thing. I do not recommend using it in this way because it's weird.
"KStars is free, open source, cross-platform Astronomy Software. It provides an accurate graphical simulation of the night sky, from any location on Earth, at any date and time. The display includes up to 100 million stars, 13,000 deep-sky objects,all 8 planets, the Sun and Moon, and thousands of comets, asteroids, supernovae, and satellites. For students and teachers, it supports adjustable simulation speeds in order to view phenomena that happen over long timescales, the KStars Astrocalculator to predict conjunctions, and many common astronomical calculations.
For the amateur astronomer, it provides an observation planner, a sky calendar tool, and an FOV editor to calculate field of view of equipment and display them. Find out interesting objects in the "What's up Tonight" tool, plot altitude vs. time graphs for any object, print high-quality sky charts, and gain access to lots of information and resources to help you explore the universe!" -- KStars Website
"Included with KStars is the Ekos Astrophotography suite, a complete astrophotography solution that can control all INDI devices including numerous telescopes, CCDs, DSLRs, focusers, filters, and a lot more - Basically everything the OAT and everything on it. Ekos supports highly accurate tracking using online and offline astrometry solver, autofocus and autoguiding capabilities, and capture of single or multiple images using the powerful built in sequence manager." -- KStars Website
"Astroberry is ready to use system for Raspberry Pi for controlling all your astronomy equipment. You can remotely control your telescope, focuser, camera and much more! All of these with just a small and portable single board computer. Take a sit at your desk and manage your equipment located in the backyard or hundreds kilometers away."
NOTE: This guide assumes that you already have OAT running on an Arduino Mega or ESP32 and that you know how to install various operating systems on a Raspberry Pi. You should already have KStars installed as well, which is easily done on any OS. The configuration of Ekos is the same regardless of the system you're on.
Finally, head to the Capture options tab and check the following
You may now click "Close" at the bottom, as you're ready to start using KStars and EKos to do your imaging.
Using the software is a bit out of scope here, but basically you can now right-click on a celestial object in the main KStars window and select "LX200 GPS > Goto", and the OAT will slew to the object and begin tracking it. From there, you can use the Camera tab on the Ekos window to begin taking exposures. There are many youtube videos on the subject.
By default images are captured in FITS format and saved to the Pi, not your computer nor the camera SD card - this is configurable in the Camera, or CCD, tab in Ekos. I recommend running KStars on the same computer you will use for image processing, and saving "client side" as that will save you a good amount of time.
A bulk of Ekos features are geared toward running a full on Observatory, which is quite impressive, but mostly useless with the OAT - unless you've built a dome and all that whizbang stuff.
I use this setup with an 8g Raspberry Pi 4. It will likely work fine with a 3 if you're not running the application on the Pi's desktop (weird)
You can also connect to the Astroberry via VNC, and run KStars from there - but it then becomes a local configuration (weird)
You may also connect this way via the web front end by clicking the big "Connect" button in the center of the screen on the Web Frontend (weird)