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
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.
============== 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
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.
don't worry, if we work on it it is because we like it
I hope your 90kg EQ Fork mount project will finish earlier as my Observatory.
I started building the observatory mi 2018 and now I am only changing the whole shape.
Now it is a cylinder with flat roof (slightly sloped).
It will change to a real dome so it is much work but this is the fact,
a project is always a big step at the beginning and later on an a lot of little improvements here and there ...
Some on hardware and consequently the firmware and so on.
here a snapshot of the work in progress ...
No the observatory is controlled by custom hardware github.com/azwing/Observatory
built around Arduino Mega ...
I use Indi's Dome Scripting interface.
The reason why I change the Shape from Cylinder to Dome is that I have not to adapt coordinates transformations already done by Ekos.