Re: PHD2 versus ASCOM driver
Had a really good night with the Mach2 under clear but moonlit skies. PHD2 ran reasonable well with defaultDon't believe that!
One of the PHD2 devs tried to provide an example but it turned out to be a faulty test. If PHD2 or any other application is using multithreaded operations the process has to be carefully coded to send the commands on the same thread. .Net framework applications automatically do that under the hood, but non-.Net applications, like PHD2 and CDC, do not. Those applications need special synchronization logic to prevent possible deadlocks. Unless they made that change PHD2 can cause a deadlock in the driver. They don't seem to accept that explanation but neither they can they seem to create a deadlock when using Net ASCOM client applications.
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver