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.
Here's another chart where i picked data to match the angular range, scale, and style of the Hackaday article. It's easy to see this motor/driver is more accurate than any of the ones they tested:
Here's another chart where i picked data to match the angular range, scale, and style of the Hackaday article. It's easy to see this motor/driver is more accurate than any of the ones they tested:
Here's the form I plan to present the data in.
This example is just the "unloaded" data, I still need to get my weights measured/established before doing the other measurements for this motor. Note
Here's the form I plan to present the data in.
This example is just the "unloaded" data, I still need to get my weights measured/established before doing the other measurements for this motor. Note
Here's the CAD of my test fixture, this is already printed and working (including a slightly hacked OnStep software stack to gather data.) My 200K count Gurley encoder goes on one side and the
Here's the CAD of my test fixture, this is already printed and working (including a slightly hacked OnStep software stack to gather data.) My 200K count Gurley encoder goes on one side and the
I would like to expand on the information presented in this useful article: "How Accurate Is Microstepping Really?" to include a wider range of stepper motors, stepper drivers, drive currents, decay
I would like to expand on the information presented in this useful article: "How Accurate Is Microstepping Really?" to include a wider range of stepper motors, stepper drivers, drive currents, decay
I’ve had a look at the wiki about correcting for alignment errors using the Refine Polar Alignmenf function in the Android app. I know I’m going to have large pointing errors as I don’t have a
I’ve had a look at the wiki about correcting for alignment errors using the Refine Polar Alignmenf function in the Android app. I know I’m going to have large pointing errors as I don’t have a
Correct. This is as designed. It is because the supply voltages and grounds, being derived from two different sources (one being the PCB supply via the DC-to-DC regulator, the other being via the PC
Correct. This is as designed. It is because the supply voltages and grounds, being derived from two different sources (one being the PCB supply via the DC-to-DC regulator, the other being via the PC
If I look on the PCB I only see an connection from CP2102 to STM32 (TX,RX). And GND of course. That means the plugged STM32 have no power supply (3,3V or 5V) from the CP2102. But power supply for
If I look on the PCB I only see an connection from CP2102 to STM32 (TX,RX). And GND of course. That means the plugged STM32 have no power supply (3,3V or 5V) from the CP2102. But power supply for
I posted a few post down about this but wanted to start a new thread. What I would like to do is provide all CGE owners an option to keep their mounts when the electronics die. I found this group by
I posted a few post down about this but wanted to start a new thread. What I would like to do is provide all CGE owners an option to keep their mounts when the electronics die. I found this group by
Or components on the board, such as the female headers.
This is easy to rule out. Just disconnect the wires going from the slide switch to the headers on the STM32, and use the jumper that came with
Or components on the board, such as the female headers.
This is easy to rule out. Just disconnect the wires going from the slide switch to the headers on the STM32, and use the jumper that came with
I can't help you there. I have not built my STM32 board yet but I have constructed both the mini and max
At least you know that the STM BP and CP2012 work. That says the problem is on the board
I can't help you there. I have not built my STM32 board yet but I have constructed both the mini and max
At least you know that the STM BP and CP2012 work. That says the problem is on the board
Using a magnifying lens, look for solder bridges between adjacent pins on the female headers.
Or solder bridges on the PCB itself.
Then, with all power disconnected, test continuity between each two
Using a magnifying lens, look for solder bridges between adjacent pins on the female headers.
Or solder bridges on the PCB itself.
Then, with all power disconnected, test continuity between each two
The STM32 flashing works as following (at least in my case). The STM32 Board has to unplugged from the PCB. Then the CP2102 has to connected with the STM32 directly. This pins has to connected
The STM32 flashing works as following (at least in my case). The STM32 Board has to unplugged from the PCB. Then the CP2102 has to connected with the STM32 directly. This pins has to connected
So comparing these two options are not very different in price:
1. $14 stepper motor and $15 tmc5160 drivers = $29,
2. $33 MKS-SERVO42B-Nema17-Closed-Loop-Stepper (the link I posted above to BG
So comparing these two options are not very different in price:
1. $14 stepper motor and $15 tmc5160 drivers = $29,
2. $33 MKS-SERVO42B-Nema17-Closed-Loop-Stepper (the link I posted above to BG
