SharpCap Forums

Hi Robin,

This is 2 times I am obliged to rollback version of the 6/01/25 because all other versions including the last one from 21/01 make my focuser to be not responding when doing a multistar focus adjustment. I have a message that the focuser take too long to settle , waiting 5s more , but it never finish and autofocus is canceled.

When I return to version of the 6/01 everything is working perfect.

Please advise
Olivier

Hi Olivier,

yes, that message comes from a recently introduced check that is supposed to spot situations where the focuser ASCOM driver is misbehaving - it is expecting the focuser to switch from the 'Moving' to 'Not Moving' state within a few seconds of reaching the target position. There are some focuser drivers out there that seem to sometimes get stuck with the 'Moving' state set, which was causing the focuser scan to get stuck indefinitely.

I must admit I wasn't expecting that change to affect the normal focuser usage, only expecting it to help deal with errors. I can see one possible way that it might cause issues - if you have a large backlash correction set up and the focuser happens to report the exact target position on the way towards the backlash correction - that could trigger the 5s limit to start counting too soon. I think I can correct that for the next update and we will see if that fixes it - otherwise I may need a full log with additional focuser communications logging turned on. Interestingly, I have been using my ZWO EAF with recent versions with no problems, so it may well be specific settings are needed in the focuser or the SharpCap focus settings for the problem to happen.

cheers,

Robin

Hi Robin,
the last version you did seems to have fix the issue

Cheers
Olivier

Hi,

good to hear - it turned out that the problem was related to being in a UTC+XXh time zone and a bug in the code mixing up the local time and the UTC time when checking to see if the focuser had been given enough time to settle. That's now fixed

cheers,

Robin