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.
Take a look at the under $20 Makerbase MKS TinyBee: w/ESP32 MCU & Wifi WEB Control. Support for 5 external drivers. The layout looks less constrained.
GitHub page.
Take a look at the under $20 Makerbase MKS TinyBee: w/ESP32 MCU & Wifi WEB Control. Support for 5 external drivers. The layout looks less constrained.
GitHub page.
Maybe I should changethe values of the resistors (12k,8.1k,3.3k,100k) to have a proper digitallevel.
Why does it useSchottky diodes, shouldn't they be zener diodes, to protect against voltage peak?
Maybe I should changethe values of the resistors (12k,8.1k,3.3k,100k) to have a proper digitallevel.
Why does it useSchottky diodes, shouldn't they be zener diodes, to protect against voltage peak?
I assume you have the jumper that enables MISO comms positioned properly and that nothing else is enabled that would try to use that same pin (AUX2 aka GPIO4.)
Otherwise you could really disable
I assume you have the jumper that enables MISO comms positioned properly and that nothing else is enabled that would try to use that same pin (AUX2 aka GPIO4.)
Otherwise you could really disable
You don't, one GPIO device is supported.
Depends... but common settings are #ifndef bracketed so that Config.h takes precedence, for others it could go the other way
You don't, one GPIO device is supported.
Depends... but common settings are #ifndef bracketed so that Config.h takes precedence, for others it could go the other way
Hi Howard,
That was an improvement, I now get no errors when upload/compiling. All my Aux highside/lowside drivers show up in the "aux" tab. Making progress!
But, I still have the axis1&2
Hi Howard,
That was an improvement, I now get no errors when upload/compiling. All my Aux highside/lowside drivers show up in the "aux" tab. Making progress!
But, I still have the axis1&2
Hello,
i have an eqm 35 pro and planning to replace the gears with pulleys and belts.
How can i choose the correct pulleys taking into account the existing ones? what do i have to check?
if there a
Hello,
i have an eqm 35 pro and planning to replace the gears with pulleys and belts.
How can i choose the correct pulleys taking into account the existing ones? what do i have to check?
if there a
It's also possible that the Android screen class interface used to create the submenu icon/callback that is used currently in the app just isn't compatible with 4.4.4, which was released on Halloween
It's also possible that the Android screen class interface used to create the submenu icon/callback that is used currently in the app just isn't compatible with 4.4.4, which was released on Halloween
That should give you access to 4 unused pins...
I guess the thing to do would be to use 2 of the four for SERIAL_B (SWS) then the other 2 for PEC and Limit (freeing up the TE and TB for thermistors)
That should give you access to 4 unused pins...
I guess the thing to do would be to use 2 of the four for SERIAL_B (SWS) then the other 2 for PEC and Limit (freeing up the TE and TB for thermistors)
Jak,
To determine which wires make up the two phases on a four wire stepper motor you could use an ohmmeter but lacking that, here is a foolproof method:
Unplug your stepper motor
Rotate the motor by
Jak,
To determine which wires make up the two phases on a four wire stepper motor you could use an ohmmeter but lacking that, here is a foolproof method:
Unplug your stepper motor
Rotate the motor by
I think that is correct. The Config.defaults.h file has a section that shows all the options (the underlying WiFi code is identical between SWS, OCS, and OnStepX):
// ESP32 virtual serial IP command
I think that is correct. The Config.defaults.h file has a section that shows all the options (the underlying WiFi code is identical between SWS, OCS, and OnStepX):
// ESP32 virtual serial IP command
Perhaps this adapter can free up the extra SDCard pins:
https://www.aliexpress.com/item/1005002624888242.html
How are the command channels enabled in STA mode with DHCP? Like this in
Perhaps this adapter can free up the extra SDCard pins:
https://www.aliexpress.com/item/1005002624888242.html
How are the command channels enabled in STA mode with DHCP? Like this in
Keep your configuration files (everything except OnStepX.ino from the OnStepX directory) but delete all other OnStepX files.
Download and unzip again (into an /OnStepX directory) and copy the
Keep your configuration files (everything except OnStepX.ino from the OnStepX directory) but delete all other OnStepX files.
Download and unzip again (into an /OnStepX directory) and copy the
Notice the capitalization and look at line 80 here as it doesn't match, so not the same source code:
https://github.com/hjd1964/OnStepX/blob/main/src/telescope/mount/st4/St4.cpp
Notice the capitalization and look at line 80 here as it doesn't match, so not the same source code:
https://github.com/hjd1964/OnStepX/blob/main/src/telescope/mount/st4/St4.cpp
The E4 unfortunately "wastes" already scarce ESP32 pins on the (unused) sdcard...
What it comes down to is there is only one serial port interface and normally it's used to provide the USB connection.
The E4 unfortunately "wastes" already scarce ESP32 pins on the (unused) sdcard...
What it comes down to is there is only one serial port interface and normally it's used to provide the USB connection.
As far as I know SWS is not built into OnStepX, at least the reference page
https://onstep.groups.io/g/main/wiki/30066
does not mention anything....
However, you can
As far as I know SWS is not built into OnStepX, at least the reference page
https://onstep.groups.io/g/main/wiki/30066
does not mention anything....
However, you can
