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.
As Howard said, OnStep cannot use the UART interface.
You can still use the TMC2209, but you are limited to microstepping of: 64,32,16,or 8.
Not a real limitation though, since it covers the range we
As Howard said, OnStep cannot use the UART interface.
You can still use the TMC2209, but you are limited to microstepping of: 64,32,16,or 8.
Not a real limitation though, since it covers the range we
But they don’t handle hardware directly. I’ve exactly the same setup with my RP4. Think about OnStep as the electronics integrated inside your mount. The ASIAir will connect to your mount, not
But they don’t handle hardware directly. I’ve exactly the same setup with my RP4. Think about OnStep as the electronics integrated inside your mount. The ASIAir will connect to your mount, not
Thanks, that explains it. Being from the engineering world I guess I never thought about it that way. Minor revisions were always 01 thru 99. Now that I think about it that was only for readability.
I
Thanks, that explains it. Being from the engineering world I guess I never thought about it that way. Minor revisions were always 01 thru 99. Now that I think about it that was only for readability.
I
If you hoped to use an example of a camera/guider controller on an RPi as to why a GoTo mount controller could be the same, I hope you also recognize the irony of that statement.
If you hoped to use an example of a camera/guider controller on an RPi as to why a GoTo mount controller could be the same, I hope you also recognize the irony of that statement.
Hi together,
I just finished converting my Orion XT10 Dobsonian to a GOTO with OnStep. First of all thanks for this great piece of Software to everyone who is involved in this.
From mechanical point
Hi together,
I just finished converting my Orion XT10 Dobsonian to a GOTO with OnStep. First of all thanks for this great piece of Software to everyone who is involved in this.
From mechanical point
Ok, let me qualify that last statement. OnStep does not support UART mode for any TMCxxxx driver.
I also have no plans to add that feature at this time.
Ok, let me qualify that last statement. OnStep does not support UART mode for any TMCxxxx driver.
I also have no plans to add that feature at this time.
Are you sure ? What is purpose of upper pins then? I watched lot of tutorials people connecting exact same drivers via uart on SKR.1.3 and 1.4 but not on MKS Gen L...
Are you sure ? What is purpose of upper pins then? I watched lot of tutorials people connecting exact same drivers via uart on SKR.1.3 and 1.4 but not on MKS Gen L...
For some unknown reason I am not getting the needs >= 4.7 message and spiral is working. I have no clue why since It went from fail to working without changing anything. I am starting to question my
For some unknown reason I am not getting the needs >= 4.7 message and spiral is working. I have no clue why since It went from fail to working without changing anything. I am starting to question my
Hi to all i really hope that someone could help me.
I bought MKS Gen L v1.0 board and fysetc TMC2209 v3 stepper drivers.
Problem is i dont know how to connect them in UART i tried everything and watch
Hi to all i really hope that someone could help me.
I bought MKS Gen L v1.0 board and fysetc TMC2209 v3 stepper drivers.
Problem is i dont know how to connect them in UART i tried everything and watch
I don't understand your motivations. What OnStep does, in the end, is controlling some pieces of hardware (motors). Here perfect timing and a simpler execution path is the goal. And for this,
I don't understand your motivations. What OnStep does, in the end, is controlling some pieces of hardware (motors). Here perfect timing and a simpler execution path is the goal. And for this,
I was thinking of writing all the code from scratch in python or even reUse the C code but yeah the Arduino Libs used will be a major undertaking, I understand these are two very different universe
I was thinking of writing all the code from scratch in python or even reUse the C code but yeah the Arduino Libs used will be a major undertaking, I understand these are two very different universe
I rather meant that in the future we should make the numbers explicit so no confusion can ever occur.
That is also why I advocate purely numeric version numbers (e.g. 042101 rather than 4.21b), which
I rather meant that in the future we should make the numbers explicit so no confusion can ever occur.
That is also why I advocate purely numeric version numbers (e.g. 042101 rather than 4.21b), which
So you are saying the app was checking for version 4.07 or greater? I am still trying to understand what the logic behind this is. 4.21 is not greater than 4.7 this is what Martin reports in the first
So you are saying the app was checking for version 4.07 or greater? I am still trying to understand what the logic behind this is. 4.21 is not greater than 4.7 this is what Martin reports in the first