At 589:1 and 532:1 I'd expect the typical 400 step NEMA17 motors to do the job... https://www.omc-stepperonline.com/nema-17-stepper-motor/Dual-Shaft-Nema-17-Bipolar-09deg-44Ncm-6248ozin-168A-28V-42x42

Yes and I'd like to keep it that way. Having this information spread out on individual Wiki pages and repeated over and over just creates an error prone maintenance nightmare. There is generic guidanc

#EQ5

Let me be more clear, make sure the following options in Config.h are disabled as shown below: #define AXIS1_DRIVER_STATUS OFF #define AXIS2_DRIVER_STATUS OFF

I think it's been noted before that TMC5160 (and TMC2130?) driver status doesn't work on the S6 for whatever reason.

So I placed my GPS on a somewhat similar MaxSTM3 and setup with PPS etc. It still works perfectly in my tests. My guess is that this is an unforeseen problem with how the Encoders/OnStep/GPS interact.

#fysetc

The code waits for GPS PPS sync (if PPS is enabled) and/or also waits for date/time/location good indication from the GPS library and sets those values. Without GPS I can test similar by not setting t

#fysetc

Not supported in OnStep.

#tmc2209

I don't but I do test from time to time and just did so again. Windows 10 and the very latest NINA x64. It works fine here. Now this wasn't with the OnFocus ASCOM driver, which is basically obsolete;

I just use an Arduino library to read the GPS so it's a "black box" as far as I'm concerned; but I always assumed this was a hardware/low-level firmware problem specific to the S6.

#fysetc

Yes still in NV/EEPROM and will still be parked even if the unpark failed (regardless of the mount shown at home.) Once the date/time are set you should be able to unpark.

#fysetc

Just understand that you have to jumper/wire the stepper driver mode control pins to a header on the board (for SPI etc.) or you will be stuck in one microstep mode. An relatively easy way is with eba

#tmc2209

If it were me I'd shoot for a little more than 20:1 at the pulley. If that's not doable you can always test, then swap the motors for ~50:1 if not satisfied. Keeping in mind that a 3D printed pulley i

Sounds like a h/w problem.

At startup OnStep will attempt to unpark the mount in a special mode that just sets the location but doesn't start tracking, if fails since the date/time hasn't been set yet. If it didn't fail you wou

#fysetc

Documented with the 3D panels... https://onstep.groups.io/g/main/files/3D-printables/Board%20enclosures%20%28Cases%29/MaxPCB%20Version%202%20front%20and%20back%20panels

The error comes from drivers. If this is going to be an issue I can exclude that status bit from triggering the stop, for now simply disable the status feature.

I haven't used GX12's but rather more expensive DIN connectors. Have to say I have a set and next controller build will try them, what I have been using are overkill. At the motor itself I use motors

STEPPERONLINE model 17HM19-1684S works just fine at 12V also.

Many years ago I had a Mega2560/OnStep with DRV8825's to 0.9A NEMA17 motors for my G11. I tested everything on the bench and it worked nicely. Took that and installed with those cables and was confuse

Just noticed this... the support isn't designed for a "Generic F401CE" board. It's for the "BlackPill F401CC" and very likely the smaller memory of a CC vs. a CE makes no difference (as even 256KB is