Dear all,
thank you for advancing this matter!
I have similar issus with my Sesto Senso. Therefore I started a while ago this topic:
www.indilib.org/forum/ekos/4641-sesto-senso-in-ekos.html#35281. In the meantime I tried a lot, Jasem did some Team-Viewer-Sessions etc. Result was that it still does not work (my one always focusses in and does not stop at the desired position; it can only be stopped manually), but it seems that the INDI-Driver works correct. Because of this Jasem and I get in contact with PrimaLuceLab. So they know about the problem, but (at the moment) they don't have an idea what the reason for the problem is. I hope that they will jump in now and and help to solve this issue.
In addition to the aforementioned, I noticed the following
1.
The INDI-Driver seems to not read out the correct maximum position of the Sesto Senso. In my case it is (depending on the respective calibration with the PrimaLuceLab Software) somewhat about 80.000. The value displayed in the INDI-Control-Panel is somewhat above 2.000.000 (!).
2.
When the Sesto Senso is focussing in / has manually stopped in the INDI-Control-Panel next to firmeware is not displayed "2.1" (which is the actual firmware / the firmware I have installed) but wired characters (something like "x&%!"). After reconnecting the Sesto Senso "2.1" is shown again.
3.
The Sesto Senso works under ASCOM, but after using it in Ekos I have the reinstall the firmware and recalibrate it. Otherwise it will not work under ASCOM.
4.
It seems that for some users the Sesto Senso works with INDI. My impression is that only Sesto Senso users who have firmware 2.1 installed have the described issues. But I am not sure at this point.
I hope this helps. Please tell me if I could do something to assist in this matter (I am not a programmer / software guy).
Best
Nils