Do not upgrade your focuser to the latest firmware, as that will break compatibility with KStars - EKOS.

Thanks for the heads-up but can you elaborate a bit more on what does or does not happen with the latest firmware?

Thanks.

Well if you update the firmware in the ESATTO, it throws back an error when INDI tries to get info about the current position. The driver continuously re-tries to get the data. You cannot move the focuser in INDI at all.

2022-10-30T04:12:11: [ERROR] Failed to find property: FnRUN_ACC
2022-10-30T04:12:11: [WARNING] Failed to process position response: _STEP170196 (11 bytes)
2022-10-30T04:12:11: [INFO] Sesto Senso 2 is online.
2022-10-30T04:12:11: [INFO] Sesto Senso 2 is online. Getting focus parameters...
2022-10-30T04:12:11: [INFO] Firmware version: 3.3.05

I believe they changed something in the command structure with the new ESATTO firmware as it now has a backlash function built into the firmware.

I asked primalucelabs to send me the command set to see what's going on with it.

Unfortunately i recently did the firmware update and now have the same error. Is there already a solution to this problem?

I have gotten zero response from PrimeLuceLabs about sending the new command structure. I have several esattos and I would like to make the Driver compatible with the new and old firmware.

Have you tried to downgrade the firmware? I have not tried that yet, and I don't even know if it's possible to do so.

Yes, unfortunately I have had the same experience that primalucelab does not respond to support requests. Very sad for such a company.

I have now been able to downgrade the firmware to version 1.3 and it looks like it will work again with indi.

I had to download the FOCUSER Manager and the ESATTO firmware 1.3. at the bottom of the page. This allows me to downgrade the firmware.
eu.primalucelab.com/info/downloads.html

Hi, I had the same problem with my Sesto Senso2 after upgrading the firmware to the one included with Play 1.4.4.
I fixed it by adding the property name in the command string that is send to the focusser for ABS_POS, SPEED, and NTC_T.
Somehow, the focusser response is truncated when the property name is not included in the command string.

Where did you do that? In the INDI Driver? Maybe I can modify the ESATTO driver as well.

If you have a patch to fix this, let us know and we'll apply to INDI. I requested doc update from Primaluce and still waiting for it.

In sestosenso2.cpp I changed line 1552, to the following
1550 bool CommandSet::getAbsolutePosition(char *res)
1551 {
1552 return sendCmd("{\"req\":{\"get\":{\"MOT1\":{\"ABS_POS\":\"\"}}}}", "ABS_POS", res);
1553 }

Similarly on line 1557
1555 bool CommandSet::getCurrentSpeed(char *res)
1556 {
1557 return sendCmd("{\"req\":{\"get\":{\"MOT1\":{\"SPEED\":\"\"}}}}", "SPEED", res);
1558 }

While debugging I also noticed that the focusser response was truncated when requesting the NTC temperature.
Although the NTC_T property was not in the truncated part and the function worked, I changed line 1649 too:
1647 bool CommandSet::getMotorTemp(char *res)
1648 {
1649 return sendCmd("{\"req\":{\"get\":{\"MOT1\":{\"NTC_T\":\"\"}}}}", "NTC_T", res);
1650 }

There might be more routines with the same problem but I haven't noticed them. I don't know whether
older firmware has a problem with these changes.

Hi,

Do you use the Linear 1 Pass focus algorithm with the Esatto? Reason I'm asking is that some other folks have reported errors with Linear 1 Pass / Esatto which we haven't worked out yet and I was wondering if its related to this problem or something else?

I was one of the ones having trouble with linear 1 pass and the esatto. I did not update to the new firmware due to Sonny’s warning. I am running the prior version. There does seem to be something funky about how the esatto handles backlash, hopefully the new firmware fixes that, once it is supported by indi.