I have not used the FYSTEC, but if it has bluetooth connectivity you can use and adroid app to send the serial commands over bluetooth.

Just another idea to try.

play.google.com/store/apps/details?id=de...hl=en_US&gl=US&pli=1

Thanks for the idea, but the BT also cannot be used unless I buy and connect it.

The FYSETC S6 definitely has a serial port. I know, because I am the one who ported OnStep to it.

DFU is only used when flashing the firmware to the board. Once that is done, and you power cycle the board, you should have a serial port over USB, provided that you followed the steps that are on the OnStep Wiki correctly.

One possibility is to add the commands that Alain detailed to the OnStep Python API . Then, since you use Linux, you will have Python on it, and you can run the API from the command line.

But this is temporary. The bug needs to be fixed regardless, as Alain outlined.

@ Martha,

Found the issue and will push the changes to Indi in the next few hours.
Unfortunately since you use Astroberry I don't know by when the new revision will be available.
Usually it takes some days until releases are available for Ubuntu but for other distros ... don't know.
I use only Git
Really strange nobody complained before for this bug. It was a double inversion so that it could work or not depending on the values .

Yes, and yes.

You can install it from a terminal using:

Myself, I use picocom, which can be installed as above but substitute picocom for minicom.

To enter the above commands, you need to do the following:

Once you are there, you can enter the commands, e.g.

:GU#

Will return some status code.

You can then try :Sh and :So commands as Alain outlined.

Actually the Python API already does set the horizon and overhead limits using the :Sh and :So commands. So no changes needed in the code.

But you need to edit examples/config.py and enter your location, time, ...et.c as well as the above limits under this section:

Khalid,

pull request issued but seems CI checks all fail.
Most probably not because of my change but the process hangs ...
As usual I have the code on github.com/azwing/indi

@Martha
Concerning the Fysetc S6, I confirm Khalids statement.
I simply do not remember if the port is /dev/ttyAMA or /dev/ttyUSB but since you connect to OnStep via Indi it should be visible in the Connection pane in control panel.

@Khalid and Martha

Fix is merged into Indi Master

@ Alain and Khalid,

Thank you for fast reaction, I didn't expect that I can indicate a never discovered problem. I'm going to wait patiently for the new INDI version while I'll improve mechanics of my mount.

I'll try to communicate with my board from the Astroberry ASAP and will let you know.

BTW, what do you think, why the problem was never indicated? Is it related to a quite rare configuration like EQ fork mount based on OnStep @ RPi (Linux, INDI) ?

Best regards,
Martha

Martha,
============== Bug discovery
we lack people like you that discover and highlight bugs.
We are very few people actively working on the Indi driver so it makes it difficult sometimes to follow all the variants that Onstep offers.

example: I have limited resources to platforms (I use Fysetc S6, BluePill, BlackPill, Teensy 3.2 / 3.5 andd Arduino Mega)
from a devices point of view I have only one Telescope, one Focuser, not Weather or other (Nice to Have) so testing is sometimes not easy.
So having feedback from users is important.
============== Why it has never been identified
My opinion about the fact it was never discovered is that this is rarely used.
I believe I used it one time when I wrote the driver and made some tests (most probably at 3 in the morning and asleep:-)
Ususally thes values never should be touched once a system is running and in OnStep it is stored in EEprom and read/write in EEprom is limited in number of cycles.
So it is better to set it once in firmware config and leave it ...
but this is only my opinion ...
============== Communication with Astroberry
I suppose you have access to Astroberry via ssh.
so it could be an alternative to compile Indi from source

@ Alain, Khalid and all involved guys

Thank you very much for so wide (in total) response. I appreciate your work, the OnStep hardware team's work and the KStars-Ekos team's work - all is unpaid and consumes your private time.
I don't complain, I just want to know what's going on.

My problem is that I have built a demanding 90kg EQ fork mount that took me half a year and it still requires some improvement that I do for another year. If something doesn't work properly I cannot know whether it's my fault in the construction or the system generates something unexpected. Believe me please, nobody can answer the questions then. It's nothing surprising, a huge majority of OnStep users use it with modified factory-made mounts. When I ask questions, some of them sit somewhere in the dark corner and very seldom participate in a discussion. Others keep silent, because it's not their problem, I perfectly know it.

So, thank you for your readiness for instant support, if needed.

I wish you long health and pleasure that I hope comes from your volunteer job.

If you get a package built of KStars in the next week or so, then that should solve your problem, and don't bother with minicom, picocom, the OnStep Python API ...etc.

But if you do not get it soon, then try one (or more) of the above workarounds.