However, this does not explain the issue APCC not being able to find the CP4 box on the network.
APCC uses a UDP broadcast message. Make sure that your firewall allows that.
And again (as I said :-) make sure you disable any unused network adapters on your computer in case the UDP broadcast is being sent by windows out the wrong network port (s).
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver
From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of Rodolphe
Sent: Thursday, June 25, 2020 1:04 PM
Subject: Re: [ap-gto] Weird issues - ASCOM driver (5.30.10) - Mach1 - APCC and PHD2 #ASCOM_V2_Driver
It looks like the Windows update may have changed the decimal point setting. Have you tried changing the
Windows setting to swap "." and "," so that they are equivalent to what the mount expects? In the above log
messages the mount will not understand a comma in the RA and declination values.
I have changed the settings as suggested.
Also switched to TCP.
I will now have to wait for clear skies to confirm.
However, this does not explain the issue APCC not being able to find the CP4 box on the network. I tried that
again after the TCP switch: it consistently returns no result - Win10 feature update may be a reason for that. I'll
stick a yellow note on my computer screen "/!\ Stay away from Win updates on the imaging computer".
Thanks a lot for your feedback and insights.