Hi Jasem,

With sesto senso2 I still have the problem that the driver crashes. This is what I find in the log file:

[2022-12-18T15:42:39.587 CET DEBG ][ org.kde.kstars.indi] - Sesto Senso 2 : "[DEBUG] <REQ> {\"req\":{\"get\":{\"MOT1\":{\"ABS_POS\":\"\"}}}} "
[2022-12-18T15:42:39.623 CET DEBG ][ org.kde.kstars.indi] - Sesto Senso 2 : "[DEBUG] <RES> {\"res\":{\"get\":{\"MOT1\":{\"ABS_POS\":0}}}} "
[2022-12-18T15:42:39.623 CET DEBG ][ org.kde.kstars.indi] - Sesto Senso 2 : "[DEBUG] <REQ> {\"req\":{\"get\":{\"MOT1\":\"\"}}} "
[2022-12-18T15:42:39.700 CET DEBG ][ org.kde.kstars.indi] - Sesto Senso 2 : "[DEBUG] <RES> {\"res\":{\"get\":{\"MOT1\":{\"SUBMODEL\":\"SESTOSENSO2\",\"NTC_T\":\"32.49\",\"BKLASH\":0,\"CAL_STATUS\":\"stop\",\"CAL_MAXPOS\":172541,\"CAL_BKLASH\":100,\"CAL_MINPOS\":0,\"CAL_HOMEP\":1000,\"CAL_NUMOF\":0,\"CAL_DIR\":\"normal\",\"LASTDIR\":0,\"HOLDCURR_STATUS\":1,\"COMPENSATI "
[2022-12-18T15:42:39.855 CET INFO ][ org.kde.kstars.ekos.focus] - "Idle."
[2022-12-18T15:42:39.867 CET INFO ][ org.kde.kstars.ekos] - "Sesto Senso 2 focuser is online."
[2022-12-18T15:42:39.917 CET DEBG ][ org.kde.kstars.indi] - Removing device "Sesto Senso 2"
[2022-12-18T15:42:39.919 CET DEBG ][ org.kde.kstars.indi] - INDIListener: Removing device "Sesto Senso 2"
[2022-12-18T15:42:39.919 CET INFO ][ org.kde.kstars.ekos] - "Sesto Senso 2 is offline."
[2022-12-18T15:42:39.920 CET DEBG ][ org.kde.kstars.indi] - Removing managed driver "Ekos Remote Host"
[2022-12-18T15:42:39.922 CET DEBG ][ org.kde.kstars.indi] - INDIListener: Removing client manager for server localhost @ 7624
[2022-12-18T15:42:39.922 CET DEBG ][ org.kde.kstars.ekos] - Resetting Ekos Manager...
[2022-12-18T15:42:39.930 CET INFO ][ org.kde.kstars.ekos] - "INDI services stopped."

As you can see the last json response is truncated. I don't think this is caused by the indi driver. The fixes I posted before worked around this problem for SPEED and ABS_POS
by requesting only the information (ABS_POS or SPEED) that was really needed instead of requesting all information on MOT1 and extracting in the indi driver the parameters of interest.
I think this is needed here as well.

Hope this helps,
Camiel

Read More...