Since I aquired an Losmandy G11 mount without any goto provision I decided to create my own solution. I was a bit reluctant to use a Gemini, mainly because of the cost, but also due to the reliability since the servo motors are somewhat prone to failure. I also like to have complete control over the software/firmware so that no "show stopper" issues will ever be a problem for me. Looking around the 'net I saw other goto systems that seemed capable, but either they had needlessly complex hardware or were commercial systems that cost about twice what they should.
OnStep is a computerized goto system, usually for stepper motor equipped mounts though any step/dir interface motor driver (including servo) should work. It was designed, from the beginning, as a more or less general purpose system and provisions were made in the firmware to allow for use on a variety of mounts including Equatorial and Alt/Az (GEM, Fork, Dobsonian, etc.) It uses an LX200 like computer command set with a few extensions to suit hand controller-less operation.
There's a telescope hand controller App for Android (free in the Google Play Store,) an option to control through a website (Smart Web Server,) and a dedicated physical hand controller (Smart Hand Controller.) Or, on a PC there's ASCOM and INDI drivers for control. These options allow you to setup and control OnStep using a wide range of software including my Sky Planetarium, Cartes du Ciel, Stellarium, SkySafari, KStars, PHD2, etc. You can see most of the control possibilities in the diagram below:
Also, please visit my StellarJourney.comsite for updates, links toOnStep resources, my other astronomy software, or to see someImages taken with the assistance of my OnStep operated mounts.
If you find OnStep useful and would like to show your appreciation and support please consider making asmall monetary donation. This keeps me motivated and helps cover expenses associated with my projects.
Thanks this gives some insight, i will give it a try with and without. From previous trying i know the exact steps to mess up the guiding so testing it with and without is not really an issue. Will
Thanks this gives some insight, i will give it a try with and without. From previous trying i know the exact steps to mess up the guiding so testing it with and without is not really an issue. Will
It's been present for a long long time, there as a backup if the new mode switching design (post release-3.16) proved to have issues.
Not really 100% knowing what the issue is, I'm not sure if its the
It's been present for a long long time, there as a backup if the new mode switching design (post release-3.16) proved to have issues.
Not really 100% knowing what the issue is, I'm not sure if its the
One more post then i will shut up :')
I see that MODE_SWITCH_BEFORE_SLEW was added since patch E and i see the question down here in the topic to test with it.
I am a bit confused if i need to
One more post then i will shut up :')
I see that MODE_SWITCH_BEFORE_SLEW was added since patch E and i see the question down here in the topic to test with it.
I am a bit confused if i need to
Missed your post :)
i was just browsing the GitHub, will flash the new version tomorrow and test as soon as we have clear sky's again (Bought a new camera so slim chance that will be this year :') )
Missed your post :)
i was just browsing the GitHub, will flash the new version tomorrow and test as soon as we have clear sky's again (Bought a new camera so slim chance that will be this year :') )
Maybe add a bit more info here:
This happens for me when slewing in NINA using NSEW buttons and with the polar alignment plugin, this weirdly also ignores all limits of the mount (have not figured
Maybe add a bit more info here:
This happens for me when slewing in NINA using NSEW buttons and with the polar alignment plugin, this weirdly also ignores all limits of the mount (have not figured
if that was directed at me:
FysETC S6 v2.0 board with currently 4.24E on it.
other data:
#define AXIS1_DRIVER_MODEL TMC5160_VQUIET
#define AXIS1_DRIVER_MICROSTEPS 32
#define
if that was directed at me:
FysETC S6 v2.0 board with currently 4.24E on it.
other data:
#define AXIS1_DRIVER_MODEL TMC5160_VQUIET
#define AXIS1_DRIVER_MICROSTEPS 32
#define
What is your setup in terms of hardware, software and which version of firmware? We are trying to get a sense of how narrow or broad this issue may be. Thanks
Dave
What is your setup in terms of hardware, software and which version of firmware? We are trying to get a sense of how narrow or broad this issue may be. Thanks
Dave
One last piece of advice: don't bother with a finder scope, or even a red dot finder. Instead, learn how to use plate solving. And learn drift alignment in PhD2 if you don't have direct access to
One last piece of advice: don't bother with a finder scope, or even a red dot finder. Instead, learn how to use plate solving. And learn drift alignment in PhD2 if you don't have direct access to
I was up until 4am imaging the Hubble nebula, and then the flame nebula. Of coarse last night everything played perfectly. Nina/phd2/onstep guided perfectly every time. I even spent about an hour
I was up until 4am imaging the Hubble nebula, and then the flame nebula. Of coarse last night everything played perfectly. Nina/phd2/onstep guided perfectly every time. I even spent about an hour
Hello
Seems increasing to 18v the power supply did the trick!!! Also Dec is actually 90 degree not zero on the mount this is why pointed abnormal. I also adjusted the tensioning in the belt. Every
Hello
Seems increasing to 18v the power supply did the trick!!! Also Dec is actually 90 degree not zero on the mount this is why pointed abnormal. I also adjusted the tensioning in the belt. Every
I've found it to be imperative to deselect "Enable Serial Port DTR Control" within the OnStep ASCOM driver on certain WeMos ESP32 boards. About half of mine work fine with the defaults,
I've found it to be imperative to deselect "Enable Serial Port DTR Control" within the OnStep ASCOM driver on certain WeMos ESP32 boards. About half of mine work fine with the defaults,
Hi
I'm using WeMos D1 ESP32 ESP-32 CH340 WiFi Bluetooth UNO R32 Development Board with CNC V3 Shield
ESP32 by Espressif Systems, 1.04.
Bluetooth app works but when I try to connect via Ascom
Hi
I'm using WeMos D1 ESP32 ESP-32 CH340 WiFi Bluetooth UNO R32 Development Board with CNC V3 Shield
ESP32 by Espressif Systems, 1.04.
Bluetooth app works but when I try to connect via Ascom
