OnStepX.. problem with ESP32+CNC3

[bojan]

Anyone tried this combination with success?
I have connection to ASCOM driver problem...

[bojan]

Because there is some possible issues with ESP32 controller (documented here, I tried STM32.. Same result.

Anybody went through this or similar experience, and how the problems were resolved?
Thanks in advance,

Bojan

[bojan]

"Problem" solved..
I had to enable the mount with :
#define AXIS1_DRIVER_MODEL GENERIC //
#define AXIS2_DRIVER_MODEL GENERIC //
Now it connects to ASCOM, however Autostart is NOT supported for ALTAZ mounts.. so I still need my mobile to start tracking (and operate mount).
Good enough :-)

[bojan]

There is a new version of OnStepX (10.17f).

When RTC is present in the system, Autostart works OK (when enabled in config.h).
This feature is very useful if a simple, no fuss configuration is needed.
As to "good enough" alignment, I need only to point scope to AZ=0° and level it horizontally, then apply the power (or press Reset button).
With encoders present, that is all I need for visual session with good tracking (correction/pointing can be done with mob app)



EDIT:

When RTC is NOT present in the system, Autostart works OK now (when enabled in config.h.. befor it was not working in some cases, discussed in Wiki).

[AstroViking (Steve)]

It's great to see this project making progress, Bojan. I haven't touched that sort of hardware since my Uni days, and don't have enough free time to get back into it. Maybe when I retire...

[bojan]

Originally Posted by AstroViking

.... Maybe when I retire...

That will be too long :-)

[ChrisV (Chris)]

So was it complicated getting onstepX going compared to the old version??

I've been running v4.24 on a minPCB but was considering onstepX on the maxPCB4

[bojan]

Not really..

My biggest problem was the naming of the stepper model.

In 4.24, definition :

"#define AXIS1_DRIVER_MODEL OFF "
meant system would output just Pulse and Dir signals to external Stepper controller-driver without microstepping control.

In OnStepX, "OFF" means no output... and as spurious consequence, no connection to comp via ASCOM platform.

Once that was sorted wit help of OnStep developers, the rest was straightforward.
I also intend to test OnStepX with STM32 (Blue Pill.. very cheap, ~2$) . However this may not work because the flash memory may be too small..

But for 4.24, 128k is large enough.

[sfarndell (Scott)]

Glad you got this sorted. I've made a few STM32 blue pill controllers, but the memory is a bit small and Onstepx won’t run on it. The better, easier version is the Fysetc E4 as it’s mostly plug n play, uses a 32 bit board (allowing faster sewing), with minimal configuration required. It costs only $20-30 more for a lot less time a few dollars more when all the bits are added up bit will save a lot of time and energy overall. I recommend adding the RTC module too as it keeps excellent time and, if you don't relocate your scope often, makes setup quick without the need to pfaff about with entering date and time every time you start up.

[bojan]

Actually, OnStepX with basic configuration (2 axis, RTC, BT, with optional encoders (and WiFi in ESP8266 controller), no derotator, no focuser) fits into STM32.
This is good for me because I already have two such controllers (in handpads, with stepper drivers in the mount (EQ6, dob), connected by 25 wire cable), and all I wanted was autostart for dob and motors OFF for EQ6 (both not supported in 2.222 and 4.2.4).

[bojan]

And I tested OnStepX with STM32F103 processor (Blue Pill).. all works OK, f/w takes 99% of flash space...

[bojan]

Originally Posted by bojan

And I tested OnStepX with STM32F103 processor (Blue Pill).. all works OK, f/w takes 99% of flash space...

However, when I tied to activate PEC functionality, it was refusing to slew and/or sync to object..

So I replaced original processor (F103) with pin-compatible but larger ROM/RAM version (F303).



Now the slews and sync OK, and expect PEC will be working correctly as well.

[wasyoungonce (Brendan)]

I’m enjoying reading about onstep stuff. Really is growing and has a future.

Thanks. Keep it up I may have to give it a nudge at this rate

Cheers

Bren

[bojan]

Brendan,
Very true. Many people think (and with good reason!) this is the ideal (and only) solution for DIY scopes and retrofits.. it uses low cost and various h/w (Arduino) and open-source f/w - the best possible combination.
Myself, I tried many systems in the past (Bartels, Soundstepper, AstroEQ, PICGoTo etc..), and now I have OnStep on both my EQ6, EXOS-II, and Dob.. and I retrofitted my friend's Nexstar mount (MEGA+RAMPS14).

For my dobson mount, at first I went from Bartels to OnStep because one of the Fujitsu st1000 tablets that was running Bartels started to freeze, so I decided to better replace it with more available hardware running OnStep (Arduino MEGA was my first choice then, now I have it on ESP32).

Sometimes I had problems (most of them were me not reading docs on Wiki carefully enough!), but the support from OnStep community was always great and everything was usually sorted after couple of posts on forum.