SGP and SestoSenso2 temperature sensor issue

Hello there,

I am currently still using Sequence Generator Pro version 3 and am actually quite happy with it.

For months I have been using the FocusMotor Sesto Senso 2 via the ASCOM driver from Primaluce without any problems.

Yesterday I updated the Sesto Senso ASCOM driver to the latest version and since then there has been a problem with SGP no longer being able to read the temperature on the FocusMotor. This does not happen immediately, but sometimes after a few seconds and sometimes after a few minutes. The log then shows the following:

[04/23/24 10:32:19.236][DEBUG][Main Thread][NONE] Connecting ASCOM focuser…
[04/23/24 10:32:19.582][DEBUG][Main Thread][NONE] Focuser supports temperature
[04/23/24 10:32:19.582][DEBUG][Main Thread][NONE] Current temperature reports: 8.31
[04/23/24 10:32:19.652][DEBUG][Main Thread][NONE] Focuser reports Max Increment as: 63974
[04/23/24 10:32:19.652][DEBUG][Main Thread][NONE] Focuser reports max steps as: 63974
[04/23/24 10:32:19.687][DEBUG][Main Thread][NONE] Focuser reports step size as 0.0700000002980232 microns
[04/23/24 10:32:22.066][DEBUG][Main Thread][NONE] Connecting ASCOM rotator…
[04/23/24 10:33:33.931][DEBUG][Main Thread][NONE] PopulateDataModel: Transferring view to the data model…
[04/23/24 10:33:33.940][DEBUG][MF Update Thread][NONE] Performing serialize…
[04/23/24 10:40:22.710][DEBUG][MF Update Thread][NONE] ASCOM Focuser: Error in GetTemperature. : Exception has been thrown by the target of an invocation. (System.Runtime.InteropServices.COMException (0x80040400): Focuser/Temperature probe not connected is not implemented in this driver.)
at System.RuntimeType.InvokeDispMethod(String name, BindingFlags invokeAttr, Object target, Object args, Boolean byrefModifiers, Int32 culture, String namedParameters)
at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object providedArgs, ParameterModifier modifiers, CultureInfo culture, String namedParams)
at s9.get_Temperature()
at s2.lo()

A test with another sequencer software (N.I.N.A), however, shows no problem with the temperature at the motor focus, the value is still reliably displayed there.

My question - does anyone here also use a Sesto Senso 2 with SGP3? Is there a similar problem or even a solution?

I am grateful for any feedback.

Best regards

I don’t have an easy answer for you, but, I can say that the error you pasted above is issued by the driver itself and, because of that, PL may have input or guidance for you here.

Thanks for your feedback and the info.
I have already opened a case with PL, but unfortunately I have not yet received a reply.