SharpCap Forums

Hello
It's quite random, it's not systematic
http://dialou.fr/temp/sharcap/Log_2024- ... 84.log.zip
Louis

Hi Louis,

thanks for the log - it could be a timing issue that sometimes the state of the connection has updated properly by the time SharpCap checks it and sometimes it hasn't. I will investigate and see if it is possible for SharpCap to check more than once with a small delay allowed.

Robin

Hello Robin
With the latest version of SharpCap I still have the problem
Thanks for your help
Louis Joly

Hi,

at least part of that would be becaue I forgot about this one, sorry

I have now tweaked the code so SharpCap will wait a short while for the focuser to report as connected - this will be in next week's update.

cheers,

Robin

Hello Robin
Still the error with version 4.1.12221.0
Louis

Hi,

can you just confirm if you are using the latest 'Pegasus Unity' or some older version of their ASCOM driver to talk to your focuser? The name recorded in your log doesn't match the focuser names seen when I install unity, so I am wondering if this is an older ASCOM driver that is no longer being supported or updated by pegasus.

cheers,

Robin

Hello Robin
I am using the latest version of "Pegasus Unity"
Louis

Hi,

that's odd - your last log above shows the focuser selected
However, with Unity installed, I don't see that name in the list of available focusers
All the ASCOM entries from Unity have 'PegasusAstro' with no space at the start. I am just wondering if you also have the older ASCOM driver installed and are using that unintentionally, rather than the newer one that works with Unity.

cheers,

Robin

Hello Robin
I think I was using an old driver left over from before installing Pegasus Unity
I'll see what that gives
Louis

Hello Robin
On the other hand I get this message when I click "setup" Louis