DIY Rotator ASCOM driver won't connect, although working in other apps

[Glenn Newell]

This is reproducible

I am running Version 1.10 BETA008 x86 and also tried Version 1.9 x64 and x86

As far as I know I have met prerequisites. All other gear is working

Description:

ASCOM Platform 6.4 SP1

All ASCOM diagnostics pass (except AstroUtilTests - ##### NOT Matched - DeltaUT1)

Rotator Drivers (Server and Direct) show correctly in ASCOM Profile Manager with parameter values

Rotator Server dirvers works correctly (and simultaneously in PHD2 and SGP)

Can't connect with NINA, even though properties dialog works (Server, Optec ASCOM server as hub, or direct drivers)

Logs attached

FYI I do have the C# source code for this driver.

Expected behavior

Rotator Server Driver connects and operates Rotator (simultanously from PHD2 AND NINA)

Actual behavior

Nina can’t connect to the driver even though it works correctly in other apps and properties dialog comes up in NINA

‌

‌

[Stefan B]

Hi,

accroding to the log the error is inside the driver. “The RPC Server is unavailable”. This is often an indication that a firewall is blocking the attempt to communicate with a server.

[Glenn Newell]

Since it is working in PHD2 and SGP, does that imply I need to look at firewall rules for NINA? Can you please be more specific on firewall rules?

Thanks

‌

[Glenn Newell]

FYI turning the windows defender firewall completely off did not change the symptoms. Still no connection from NINA but other apps can connect.

[Stefan B]

All i can say is that this issue arises on Driver Level. Could also be related to Nina running in x64 or having the connection in a separate Task.

[Stanley Dimant]

I had the same issue with EQMOD and I had to change the network I am in to Private Network in Windows. Try that.

[Stefan B]

Problem occurrs on driver level. Nothing on nina side that could fix this, as it just talks to the ascom interface.