Re: COM Errors w/APCC
Thanks Ray,toggle quoted messageShow quoted text
Biggest problem with remote imaging is not "seeing/touching" the systems. As
far as I know the cable to the mount (CP4) from the switch was replaced, the
switch itself (or at least requested) but nothing was said about the cable
from their switch to their network switch. I haven't seen any sign of the
computer cycling on/off as would be possible if the heat sync/fan was dirty
Guess I'll need to ask the SRO crew a few more questions.....
From: firstname.lastname@example.org <email@example.com> On Behalf Of Ray Gralak
Sent: Monday, April 12, 2021 8:58 AM
Subject: Re: [ap-gto] COM Errors w/APCC
Looking at your logs, it is probably a network issue but that may be
difficult to pin down. Since you replaced the switch and cable(s), it could
be the Ethernet port on the computer, the Ethernet driver, or a Windows
operation causing a delay in responses.
It could also be the computer has issues, especially if it was left out in a
potentially hazardous environment (e.g. cold weather, and smoke from fires
that approached SRO last year).
BTW, you said *the* CAT5e cable was replaced, but there should be at least
two cables: computer to switch, and switch to mount. Were both replaced?
-----Original Message-----already have an additional 7 COM errors. APCC just switched from TCP to COM
3 while looking at the log file for this morning. The log files can be found
41125.zip?dl=0> . This is an up to date CP4 on an AP3600GTO as well as ASCOM
driver and APCC Pro being up to date.