I really can't tell where the problem is but OnStepX had changes to the sync commands ahead of 10.20a so who knows.

More detailed command logging... even enabling logging in OnStepX (on a different serial interface than this is talking across) might shed some light on it.

I see weaknesses in the Sync :CM# command return and added code to the master to "harden" it against that. Not sure there is a problem but it's not impossible.

Read More...

The latest release of OnStepX is version 10.20a:
github.com/hjd1964/OnStepX/releases

If using later than that you are running something significantly less proven.

Also, make sure DEBUG mode (Extended.config.h) is disabled if using a serial/USB for comms.
Also, make sure you flash according to the OnStep Group Wiki instructions (else the ESP32S might be crashing for all I know.)

If none of that does it post some INDI logs to the OnStep Group.

Read More...

In OnStepX it is an Config.h option to automatically load the alignment model at boot (default OFF):
#define ALIGN_MODEL_MEMORY ON

If you are not using that option you must Park before powering off to retain the pointing model. If you fail to park you can still UnPark from Home to recover the model.

If is normal behavior for OnStepX at boot to indicate the Park position, even before UnParking IF the date/time is known.

Read More...