Re: Losing Communications with the Mount
To add to Ray's post, we had issues with the scope at SRO which was wired (CAT5) but through a switch instead of the direct computer connect. When I discovered this I had the guys at SRO wire the mount directly to the 2nd LAN connection on the computer. Of course the IP address of the CP4 had to be discovered and the address used but since there hasn't been a single COM error. Worth the effort if not wired from computer to mount even if a second LAN connection is only available via an addon card. Our motherboard had 2 native LAN connections.toggle quoted messageShow quoted text
From: email@example.com <firstname.lastname@example.org> On Behalf Of Ray Gralak
Sent: Wednesday, May 5, 2021 6:10 AM
Subject: Re: [ap-gto] Losing Communications with the Mount
Today I started playing with APCC and started to define the horizon,If the mount won't ping, there could be a network or power issue.
Are you directly connecting the computer to the mount? Or, is it going through a network router/switch/hub?
Try replacing the network cable(s) and any hub/switch.
Also, try raising the timeout value slightly in APCC. You should not need to go over 300 msecs for most requests. The mount will respond to most requests very quickly, but depending on the performance of your computer, the responses might not make it back through the network protocol stack to APCC before a timeout occurs.
Lastly, try switching the network protocol type. In APCC, if you are using UDP, try TCP instead, or vice versa.