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.
Some lifehack here guys, especially as a temporarily solution...
If you happened to realize, you need a longer mounting plate, the common 2040 aluminum profile works quite well, for the purpose., just
Some lifehack here guys, especially as a temporarily solution...
If you happened to realize, you need a longer mounting plate, the common 2040 aluminum profile works quite well, for the purpose., just
Last year I made an equatorial mount using Harmonic reducer.Tested recently, The test was conducted recently, the following are the details and test results of the equatorial mount
Please see
Last year I made an equatorial mount using Harmonic reducer.Tested recently, The test was conducted recently, the following are the details and test results of the equatorial mount
Please see
Amazon,
https://www.amazon.com/gp/product/B07MHNWY2P/ref=ppx_yo_dt_b_asin_title_o05_s00?ie=UTF8&psc=1
https://www.amazon.com/gp/product/B07DQ93FYT/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1
Don
Amazon,
https://www.amazon.com/gp/product/B07MHNWY2P/ref=ppx_yo_dt_b_asin_title_o05_s00?ie=UTF8&psc=1
https://www.amazon.com/gp/product/B07DQ93FYT/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1
Don
Very nice build - thank you for sharing the information! I am looking to upgrade a manual EQ5 to OnStep and I knew there were some great examples in the showcase, but I hadn't been back recently
Very nice build - thank you for sharing the information! I am looking to upgrade a manual EQ5 to OnStep and I knew there were some great examples in the showcase, but I hadn't been back recently
Thanks a lot! This is exactly I wanted.
this will be helpful to track how mine maxesp3 responds to future possible updates of the firmware code.
thanks.
+Plamen
Thanks a lot! This is exactly I wanted.
this will be helpful to track how mine maxesp3 responds to future possible updates of the firmware code.
thanks.
+Plamen
Open the OnStep.ino file, scroll down a page or so, and look at these values:
#define FirmwareVersionMajor 5
#define FirmwareVersionMinor 0
#define FirmwareVersionPatch "f"
Open the OnStep.ino file, scroll down a page or so, and look at these values:
#define FirmwareVersionMajor 5
#define FirmwareVersionMinor 0
#define FirmwareVersionPatch "f"
Thanks Khalid,
probably I did not express myself clearly.
Let say that I just downloaded a version of onstep code right now and have not uploaded to the controller yet and the code is still in my
Thanks Khalid,
probably I did not express myself clearly.
Let say that I just downloaded a version of onstep code right now and have not uploaded to the controller yet and the code is still in my
If you mean: "what version is my controller running now", then yes.
If you have WiFi and use the web interface, it will be displayed on the Status page.
The Android app also shows it (press the "i"
If you mean: "what version is my controller running now", then yes.
If you have WiFi and use the web interface, it will be displayed on the Status page.
The Android app also shows it (press the "i"
Hello every everyone,
Does anybody knows a simple way to know what version Onstep code (freshly downloaded) was prior uploading on the Onstep Hardware controllers ?
Thanks
+Plamen
Hello every everyone,
Does anybody knows a simple way to know what version Onstep code (freshly downloaded) was prior uploading on the Onstep Hardware controllers ?
Thanks
+Plamen
Hi Chris,
great documentation! Thank you very much. Based on this, I decided to disasemble the mount and do at lease some improvements (e.g. cleaning; new grease; replace ball bearings,...). After
Hi Chris,
great documentation! Thank you very much. Based on this, I decided to disasemble the mount and do at lease some improvements (e.g. cleaning; new grease; replace ball bearings,...). After
I've built a MaxESP3, based on the ESP-WROOM-32 (Node-MCU), 38-pin board. I got it working with the SHC controller (same board), but the motors would only move if I selected a speed of 8X or slower.
I've built a MaxESP3, based on the ESP-WROOM-32 (Node-MCU), 38-pin board. I got it working with the SHC controller (same board), but the motors would only move if I selected a speed of 8X or slower.
This is the 4.x branch.
Perhaps Howard should change the branch name from just "beta" to "beta (4.x)"
https://github.com/hjd1964/OnStep/archive/beta.zip
This is the 4.x branch.
Perhaps Howard should change the branch name from just "beta" to "beta (4.x)"
https://github.com/hjd1964/OnStep/archive/beta.zip
Hi,
The Wiki for the FYSTC S6 contains the following advice.
"To use the FYSETC S6 board, you need to use the latest master version of OnStep (4.7d or later)"
Hi,
The Wiki for the FYSTC S6 contains the following advice.
"To use the FYSETC S6 board, you need to use the latest master version of OnStep (4.7d or later)"
In addition to the above, or even before that, try to adjust the backlash in OnStep.
During daylight, and with the highest magnification, and tracking off, manually slew to a far away land object.
In addition to the above, or even before that, try to adjust the backlash in OnStep.
During daylight, and with the highest magnification, and tracking off, manually slew to a far away land object.
Exactly. And all other (non TMC) step stick drivers I know of don't factor in the RMS current (*0.71) with their Vref formulas, so I adopted the convention here that TMC drivers use Vref = Imax for
Exactly. And all other (non TMC) step stick drivers I know of don't factor in the RMS current (*0.71) with their Vref formulas, so I adopted the convention here that TMC drivers use Vref = Imax for
Thanks a lot!
I will try both... reducing mechanical backlash by adjusting mount AND balancing the wheight.
and just for curiosity... what do you think is a reasonable value for guiding deviation
Thanks a lot!
I will try both... reducing mechanical backlash by adjusting mount AND balancing the wheight.
and just for curiosity... what do you think is a reasonable value for guiding deviation
