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.
Sorry, you already said it does not show up there in the device manager.
Are you certain that you never tried to program it before setting the starting address? If you did that once you have
Sorry, you already said it does not show up there in the device manager.
Are you certain that you never tried to program it before setting the starting address? If you did that once you have
The updated the package in the old github location. You're seeing that because the board manager is following both it internal Arduino URL and the URLs in the additional board managers in the
The updated the package in the old github location. You're seeing that because the board manager is following both it internal Arduino URL and the URLs in the additional board managers in the
Odd that they decided to make 2.0.0 a completely different board manager instead of just an update. Forces you to uninstall one before installing the other as new.
I've got both URLs in my
Odd that they decided to make 2.0.0 a completely different board manager instead of just an update. Forces you to uninstall one before installing the other as new.
I've got both URLs in my
That is interesting. Here is what I am getting:
I'm not sure if that is a problem or not. But since the link to the library source is the same (at least the same as I have in my environment), it
That is interesting. Here is what I am getting:
I'm not sure if that is a problem or not. But since the link to the library source is the same (at least the same as I have in my environment), it
I can confirm that the new STM32 package is not compatible with OnStep (5.1v). I removed 1.9.0 and installed 2.0.0 (being careful to update the batch file address) and it did not work in at least two
I can confirm that the new STM32 package is not compatible with OnStep (5.1v). I removed 1.9.0 and installed 2.0.0 (being careful to update the batch file address) and it did not work in at least two
Those LEDs only show the 5V and 3.3V buses have power on them. If you add the tracking LED, that will show you when OnStep gets through it initialization.
No point to that FYSETC addon... it is for
Those LEDs only show the 5V and 3.3V buses have power on them. If you add the tracking LED, that will show you when OnStep gets through it initialization.
No point to that FYSETC addon... it is for
Since you are using monitor commands try setting:
#define TRACK_AUTOSTART ON
in config.h. You need to either do that or go thru the commands to imitate a normal OnStep startup before the
Since you are using monitor commands try setting:
#define TRACK_AUTOSTART ON
in config.h. You need to either do that or go thru the commands to imitate a normal OnStep startup before the
Good advice was given about that, you might be able to get away with plugging in and it kind of working without cutting CLK but it's not the way to go.
AFAIK V1.2 of the Bigtree 5160 supposedly has
Good advice was given about that, you might be able to get away with plugging in and it kind of working without cutting CLK but it's not the way to go.
AFAIK V1.2 of the Bigtree 5160 supposedly has
Back of a MaxSTM board here (MaxESP3 is the same for our purposes.) The squiggly lines represent the motor coils, two per motor with the lines leading toward the adjacent related terminals, I think
Back of a MaxSTM board here (MaxESP3 is the same for our purposes.) The squiggly lines represent the motor coils, two per motor with the lines leading toward the adjacent related terminals, I think
the motor that was moving was on axis 1, and I had not cut the clk or connected clk to ground on axis 1. axis 2 doesn't move at all. So now I think I cut the clk pin for nothing and now I need a new
the motor that was moving was on axis 1, and I had not cut the clk or connected clk to ground on axis 1. axis 2 doesn't move at all. So now I think I cut the clk pin for nothing and now I need a new
I'm just getting even more confused.😤
I added the second stepper motor to the board, and then they started vibrating when I put it into tracking. It didn't really show any signs of movement, though
I'm just getting even more confused.😤
I added the second stepper motor to the board, and then they started vibrating when I put it into tracking. It didn't really show any signs of movement, though
In the boards manager there is a dropdown with previous versions in it. Find your 'esp32' board manager in the 'all' type, select the version you want from there and the install button right beside
In the boards manager there is a dropdown with previous versions in it. Find your 'esp32' board manager in the 'all' type, select the version you want from there and the install button right beside
I'm on 1.9.0, perhaps this link still works:
https://github.com/stm32duino/BoardManagerFiles/raw/master/STM32/package_stm_index.json
Who knows, but lets just say it wouldn't be a great surprise if
I'm on 1.9.0, perhaps this link still works:
https://github.com/stm32duino/BoardManagerFiles/raw/master/STM32/package_stm_index.json
Who knows, but lets just say it wouldn't be a great surprise if
That's not a very robust implementation. It might work for a few insertions but will fail after relatively few cycles.
If there is enough headroom for the stepstick modules with the 'tuning fork'
That's not a very robust implementation. It might work for a few insertions but will fail after relatively few cycles.
If there is enough headroom for the stepstick modules with the 'tuning fork'
