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.
Again, I saw one issue that would definitely cause this to not work:
You need to remove the second occurrence of #define SERIAL_C_BAUD_DEFAULT as OFF disables the command channel. Just delete that
Again, I saw one issue that would definitely cause this to not work:
You need to remove the second occurrence of #define SERIAL_C_BAUD_DEFAULT as OFF disables the command channel. Just delete that
For persons who can't do programing of Arduino, it would be helpful if you could give me some information about Config.h for connecting OnStep and SHC via UART.
I would be very grateful if you could
For persons who can't do programing of Arduino, it would be helpful if you could give me some information about Config.h for connecting OnStep and SHC via UART.
I would be very grateful if you could
Peter, You need to figure out the motor specs before you do anything about drivers. I've seen Nema23 with nominal current from 0.4A all the way up to 6A.
In case if you don't have specs for the motor,
Peter, You need to figure out the motor specs before you do anything about drivers. I've seen Nema23 with nominal current from 0.4A all the way up to 6A.
In case if you don't have specs for the motor,
With DIP switches you can only use single microstepping mode all the time. For example, if you use 1/32, you will have decent resolution but your max GoTo speed will be very slow (for example 0.5
With DIP switches you can only use single microstepping mode all the time. For example, if you use 1/32, you will have decent resolution but your max GoTo speed will be very slow (for example 0.5
I tested with ohmmeter and result is 220ohm and I found this spec:
Voltage : 12 VDC
Number of Phase : 4
Moderating Ratio : 1/64
Step Angle : 5.625°/64
Frequency : 100Hz
DC resistance : 200Ω±7%
I tested with ohmmeter and result is 220ohm and I found this spec:
Voltage : 12 VDC
Number of Phase : 4
Moderating Ratio : 1/64
Step Angle : 5.625°/64
Frequency : 100Hz
DC resistance : 200Ω±7%
On Mon, Apr 18, 2022 at 07:19 PM, OuttaControl wrote:
but as a proof of concept and better than hand adjustingRegarding concept, I can tell you that our final conclusion was that hand adjustment was
On Mon, Apr 18, 2022 at 07:19 PM, OuttaControl wrote:
but as a proof of concept and better than hand adjustingRegarding concept, I can tell you that our final conclusion was that hand adjustment was
Mega 2560 is way to slow for fixed microstep drivers, but if you manage to modify TB6600 to do microstepping mode changing (i.e 1/32 for tracking and 1/8 for GoTo) it can work reasonably fast and
Mega 2560 is way to slow for fixed microstep drivers, but if you manage to modify TB6600 to do microstepping mode changing (i.e 1/32 for tracking and 1/8 for GoTo) it can work reasonably fast and
Thanks indeed ,
Miguel is it combatable with OnStep ?? As I mention I have uploaded to the Mega2560 without error I mean here the pins between Mega5260 a TB6600 ??
Thanks indeed ,
Miguel is it combatable with OnStep ?? As I mention I have uploaded to the Mega2560 without error I mean here the pins between Mega5260 a TB6600 ??
Sorry I do not speak English.
I attach my schematic and a photo of my device
It was the first one I did. Correct operation but poor performance.
Today I have the Wemos 32 with CNC v4 very little work
Sorry I do not speak English.
I attach my schematic and a photo of my device
It was the first one I did. Correct operation but poor performance.
Today I have the Wemos 32 with CNC v4 very little work
The 5150 is good for a maximum of 3A (3000mA). So 1.8A is OK, but generally we run the drivers a 40-50% of max. Your pusing the motor at 60% of max.
What is the max amperage of the motor?
Have to set
The 5150 is good for a maximum of 3A (3000mA). So 1.8A is OK, but generally we run the drivers a 40-50% of max. Your pusing the motor at 60% of max.
What is the max amperage of the motor?
Have to set
Sounds like you have backlash in axis. It's a mechanical issue. First you need to measure how much backlash in acr-seconds you have and then you can compensate for it in app settings so behavour you
Sounds like you have backlash in axis. It's a mechanical issue. First you need to measure how much backlash in acr-seconds you have and then you can compensate for it in app settings so behavour you
