Joha

Hello photon, last night I had the chance to verify the issue on the Windows 10 telescope computer. I used ASCOMProxyHub-1.0.0.3 and slightly older versions of the ASCOM and NINA software, e.g. ASCOM 6.6SP1. After updating to the versions you mention, the behavior is the same. On my Windows notebook I tested ASCOMProxyHub-1.0.0.3, NINA and ASCOM Simulator Telescope without any problems. I will try further options on the telescope computer.

Thank you very much for your interesting implementation. I would prefer to use the ASA DDM 60 with NINA for long time exposures of ~ 20 min and would need good pointing files. For short time exposures of ~ 2min I use an existing pointing file via ASCOM Device Hub. Unfortunately I get a severe error when I try to connect the ASA DDM 60 mount in NINA. The ASCOM.photonProxyHub.Hardware log says: ... 17:57:15.675 Connected Set True 17:57:15.688 Connected Set Connecting to proxy AstrooptikServer.Telescope 17:57:15.700 Connected Set Threw an exception: System.Runtime.InteropServices.COMException (0x80040154): Die COM-Klassenfactory f[FC]r die Komponente mit CLSID {99352175-9A79-4457-BFE5-05BBBB61FB5C} konnte aufgrund des folgenden Fehlers nicht abgerufen werden: 80040154 Klasse nicht registriert (Ausnahme von HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)). bei System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck) bei System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark) bei System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark) bei System.Activator.CreateInstance(Type type, Boolean nonPublic) bei System.Activator.CreateInstance(Type type) bei ASCOM.photonProxyHub.Telescope.TelescopeHardware.set_Connected(Boolean value) bei ASCOM.photonProxyHub.Telescope.Telescope.set_Connected(Boolean value) When I check the registry CLSID {99352175-9A79-4457-BFE5-05BBBB61FB5C} is not available. Looks like a component is not found / registered. Any idea how to overcome this issue - thanks.