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.com site for updates, links to OnStep resources, my other astronomy software, or to see some Images 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 a small monetary donation. This keeps me motivated and helps cover expenses associated with my projects.
|
Re: Initial OnstepX download error
Robert Benward
Howard,
That worked! Status and drives OK. Exercising the rest of the board. Thanks! Bob
|
|
|
|
not able to verify the device
Suveer Udayashankara
Hi I am having a bit of problem while verifying the code.. The Arduino ide is not able verify the code The error is : OnStep:65:10: fatal error: src/sd_drivers/Models.h: No such file or directory 65 | #include "src/sd_drivers/Models.h" | ^~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. exit status 1 src/sd_drivers/Models.h: No such file or directory But the all the path is written in the program are doing well.. But still ham getting this error.. How to tackle this issue
|
|
|
|
Re: Goto Failed in Standby
Howard Dutton
No other ideas really.
|
|
|
|
Goto Failed in Standby
Joy Clarke
Sorry I forgot to mention, if it makes any difference, that I live in New South Wales.. I allow the OnStep app to use my location to get date & time etc which works fine. Darryl.
|
|
|
|
Re: not able to verify the device
Suveer Udayashankara
Hi I am having a bit of problem while verifying the code.. The Arduino ide is not able verify the code The error is : OnStep:65:10: fatal error: src/sd_drivers/Models.h: No such file or directory 65 | #include "src/sd_drivers/Models.h" | ^~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. exit status 1 src/sd_drivers/Models.h: No such file or directory But the all the path is written in the program are doing well.. But still ham getting this error.. How to tackle this issue
On Fri, Jun 24, 2022, 05:31 Howard Dutton <hjd1964@...> wrote: On Thu, Jun 23, 2022 at 04:56 PM, Joy Clarke wrote:
|
|
|
|
Re: Goto Failed in Standby
Howard Dutton
On Thu, Jun 23, 2022 at 04:56 PM, Joy Clarke wrote:
Any suggestions.?Make sure the date/time are set.
|
|
|
|
Goto Failed in Standby
Joy Clarke
Hi, Background: My scope is a GSO 12" Dob that I have added 2 nema23 stepper motors to the mount which run along timing belting, one for alt and one for az. I am trialling a goto system from Byers using the OnStep firmware and I connect to the system via wifi. Tried using the "goto" command in the OnStep app and got the "Goto failed in standby" message. I followed the solution given by a Group member previously i.e. "press the [at home (reset)] button. I had the stepper motors off the belting and they worked when I selected the "goto" command. Put the motors back onto the belting and tried the "goto" again but got the "goto failed in standby" message again. So I went through the process again of "resetting" etc and even turned the whole system off and on again. Did the "reset" again but each time I tried after this I keep getting the "goto failed in standby" message and obviously the mount doesn't move. Any suggestions.? Darryl.
|
|
|
|
Re: Initial OnstepX download error
On Thu, Jun 23, 2022 at 12:29 PM, Robert Benward wrote:
Disabling status worked. I do not have jumpers on my board, MISO has dedicated pins, but I will go over the pinmap to see if here any conflicts. If this helps, the same board has status and drives working on 4.24C.I found the issue, probably introduced when I added TMC2209 UART support. Patched and works here now.
|
|
|
|
George Cushing
I assume you intend to keep the existing drives? Looks too tight to permit much modification. What the gear reduction between the RA drive and the worm? 
|
|
|
|
Re: FYSETC S6 Motor Lock up
George Cushing
I don't think there are many sources of inexpensive NEMA 17 step motors. The red, green, blue & black color scheme seems to be universal among them. The motor manufacturers are fairly consistent There is an A coil and a B coil. The coils are polarized so one end is "+" and the other is "-." Thus you will see this symbol which gives you most of the information you need.  Add a little color and it tells you all you need to know.  The problem arises with the driver carrier manufacturers. They can't seem to decide on a standard coding or which way is up!  Regardless of the inscriptions the hookups are all the same except the ST820. Some use the letter for the coil designation others the numeral. Most of the time, one of these will work. 
|
|
|
|
Re: android app menu button
Dave, right, might be a software problem. I'll check if there's a chance to update the OS. Maybe that helps.
|
|
|
|
Re: Initial OnstepX download error
Robert Benward
Howard,
Disabling status worked. I do not have jumpers on my board, MISO has dedicated pins, but I will go over the pinmap to see if here any conflicts. If this helps, the same board has status and drives working on 4.24C. Bob
|
|
|
|
Re: HEQ-5 conversion with OnStepX, FYSETC E4 and Nina
I examined it and It has significant drawbacks.
From what I recall the stepper drivers sockets have no mode switching at all not even SPI. It uses 3x 74HC595 SSR's (to make 24 output pins from 3 MCU pins) which X does in theory support. I think it would work and if you use TMC2209's and jumper lead the serial interfaces could be ok. Seems like a lot of hassle though.
|
|
|
|
Re: HEQ-5 conversion with OnStepX, FYSETC E4 and Nina
George Cushing
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.
|
|
|
|
Re: Plug-in interface for External stepper Drivers
mario rocha
Maybe I should change the values of the resistors (12k,8.1k,3.3k,100k) to have a proper digital level. Why does it use Schottky diodes, shouldn't they be zener diodes, to protect against voltage peak?
El lun, 20 jun 2022 a las 15:39, Robert Benward via groups.io (<rbenward=verizon.net@groups.io>) escribió: Yup. 0.75 x Vdd=~2.4V
|
|
|
|
Re: Initial OnstepX download error
Howard Dutton
On Thu, Jun 23, 2022 at 11:40 AM, Robert Benward wrote:
Any clue you can give me on the drive comms faults?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 driver status and see if it works. I made some changes recently so will test with 5160's tonight to see that its still working.
|
|
|
|
Re: Initial OnstepX download error
Robert Benward
Any clue you can give me on the drive comms faults?
|
|
|
|
Re: Initial OnstepX download error
On Thu, Jun 23, 2022 at 11:05 AM, Robert Benward wrote:
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
|
|
|
|
Re: HEQ-5 conversion with OnStepX, FYSETC E4 and Nina
George Cushing
And then there's this FYSETC SD-WIFI with Card-Reader
|
|
|
|
Re: Initial OnstepX download error
Robert Benward
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 communications error, as show in the previous post.. Drivers are not working. I am using the QHV5160, but I don't believe there is any difference from the TMC5160 communications wise, I believe it's a VM voltage rating thing. It works fine with the 4.24C SW load. I am looking in the config file but I can't find anything that might be causing the failure. Also, The hand controller pops up in the 10x mode, but that is probably my fault, I customized the guide "speeds" in the SHC SW. A couple of questions:
Regards, Bob
|
|
|