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 for stepper motor equipped mounts. 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 (GEM, Fork, etc.) and Alt/Az (Dobsonian, etc.) It uses an LX200 like computer command set with a few extensions to suit hand-controllerless operation.
In addition to the wide range of software supported through it's ASCOM driver, many software packages work directly with it's LX200 protocol. These include Cartes du Ciel, Stellarium, SkySafari, etc.
There are hand-controller Apps for Android and iOS devices available in the Google Play Store and Apple App Store (both are free). These allow you to Un-park or Align the mount to get going, then startup SkySafari (for example) and connect (using Bluetooth or IP) to have a full planetarium type control application... All from a cell-phone or tablet.
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 consider donating code to the project (if capable,) or perhaps a language translation, or new celestial object catalog for the SHC, or a small monetary donation which can be put toward covering my expenses associated with this project.
There's plenty similar code in OnStep except I do the math correctly.
Don't use this form, it will fall down (after several days) due to overflow:
if((ledState == HIGH) && (currentMillis -
There's plenty similar code in OnStep except I do the math correctly.
Don't use this form, it will fall down (after several days) due to overflow:
if((ledState == HIGH) && (currentMillis -
As Markus said: if you get the MKS Gen-L, you don't need the RAMPS board, since the MKS Gen-L has everything that is on RAMPS built in (driver sockets for motors, ...etc.)
Regarding the power, you
As Markus said: if you get the MKS Gen-L, you don't need the RAMPS board, since the MKS Gen-L has everything that is on RAMPS built in (driver sockets for motors, ...etc.)
Regarding the power, you
The OCG now has support for the TMC5160. The compiler will issue a warning that the default for IRUN is 600mA, with the name of the exact parameter. The user then has to go edit that parameter to
The OCG now has support for the TMC5160. The compiler will issue a warning that the default for IRUN is 600mA, with the name of the exact parameter. The user then has to go edit that parameter to
The original G11 drivers use a frontal side RJ, power, etc connectors and I would like to know if anyone here have builded the controller box using such connectors configuration.
Thanks
Andre
The original G11 drivers use a frontal side RJ, power, etc connectors and I would like to know if anyone here have builded the controller box using such connectors configuration.
Thanks
Andre
Hi,
The MINPCB1 PCB for the EM10 has the connectors to be plugged on the board frontal side (not at the side such as 90 degree connectors).
Does anyone have the RJs, USB and power connector components
Hi,
The MINPCB1 PCB for the EM10 has the connectors to be plugged on the board frontal side (not at the side such as 90 degree connectors).
Does anyone have the RJs, USB and power connector components
Below is how I see it, at least for a TA drive with a "sliding pivoting arm" i.e. the screw is fixed (at both ends) relative to the axis and the arm travels along it. I'm no expert on TA's but I also
Below is how I see it, at least for a TA drive with a "sliding pivoting arm" i.e. the screw is fixed (at both ends) relative to the axis and the arm travels along it. I'm no expert on TA's but I also
James,
Looking at the motors (NEMA 34), I think these are the largest I've seen for OnStep over the past 3 years or so.
Can you share what the mount is, and what OTA (or radio?) it will carry?
James,
Looking at the motors (NEMA 34), I think these are the largest I've seen for OnStep over the past 3 years or so.
Can you share what the mount is, and what OTA (or radio?) it will carry?
In another thread Markus wrote:
Markus,
Did you refresh your OnStep version from the latest master?
It has a change for not using Serial3 as a command port, and that allows it to work for the GPS.
In another thread Markus wrote:
Markus,
Did you refresh your OnStep version from the latest master?
It has a change for not using Serial3 as a command port, and that allows it to work for the GPS.
The default Config.h has all the I* parameters set to OFF.
If this works, with a compile warning, then I can add the TMC5160 without having to ask for the values for each of the I* values.
Should
The default Config.h has all the I* parameters set to OFF.
If this works, with a compile warning, then I can add the TMC5160 without having to ask for the values for each of the I* values.
Should
Hi All…
I am setting up a workaround for the PARK/UNPARK crash in Kstars/EKOS and trying to find a suitable and reliable LIMIT I can set that say, stops tracking or even better auto parks
Hi All…
I am setting up a workaround for the PARK/UNPARK crash in Kstars/EKOS and trying to find a suitable and reliable LIMIT I can set that say, stops tracking or even better auto parks
Hello Piers,
Yes it's a big project. During the Covid-19 pandemic here I am working in isolation, also partly for personal reasons.
I stand on the shoulders of all who have gone before and I hope to
Hello Piers,
Yes it's a big project. During the Covid-19 pandemic here I am working in isolation, also partly for personal reasons.
I stand on the shoulders of all who have gone before and I hope to
Hello Howard,
I think I see it now. Essentially you have moved theta onto the numerator on the LHS of the equation; this means that you never have a divide by nearly/equal to zero problem.
Thanks,
Hello Howard,
I think I see it now. Essentially you have moved theta onto the numerator on the LHS of the equation; this means that you never have a divide by nearly/equal to zero problem.
Thanks,
Hello Howard,
Yes that's pretty much it. But you can also predict to the nearest centisecond how long it will take to traverse a given angular distance.
So you can switch from the default track clutch
Hello Howard,
Yes that's pretty much it. But you can also predict to the nearest centisecond how long it will take to traverse a given angular distance.
So you can switch from the default track clutch
Hello Howard,
Still digesting some of the earlier comments, but the tan(theta)/theta function worries me a bit as both tan(theta) and theta go to zero, while the ratio analytically goes to 1, I doubt
Hello Howard,
Still digesting some of the earlier comments, but the tan(theta)/theta function worries me a bit as both tan(theta) and theta go to zero, while the ratio analytically goes to 1, I doubt
for my piece of mind, I immediately changed to TMC5150 and it still works...
I also tried the GPS change to RX3 again without success. #define SERIAL_A_BAUD_DEFAULT 19200 //
for my piece of mind, I immediately changed to TMC5150 and it still works...
I also tried the GPS change to RX3 again without success. #define SERIAL_A_BAUD_DEFAULT 19200 //
