iccd1 wrote: > Hello, > > I am trying to solve an issue with CdC 2.76 not seeing my Celestron > GPS 11 when using NexHub (virtual com port hub) and the AIRcable > USB/Serial 3 wireless system. Not sure if the issue is with CdC, > NexHub or AIRcable 3, though I suspect the AIRcable 3. > > CdC will work over AIRcable 3 if it is the only program using the > assigned com port (com port 4). It also works with NexHub (Master > com port=4, Slave com port=6, CdC assigned to Slave 6) when using a > wired USB to Serial connection to the telescope. CdC does not see > the telescope (timesout) when using NexHub and AIRcable 3. Other > program such as "NSO Observers List" and "Next Control Pad" work > with NexHub and AIRcable 3, though each displays a timout at the end > of its hexadecimal line code when observing communications with a > serial sniffer. I have been able to adjust the timeout parameter on > NexHub. NexHub's default timeout is 1 second. I have adjusted the > timeout from 1 to 9 seconds with CdC not seeing the telescope > (timesout). > > I was wondering what the timeout configuration is for CdC? I looked > for a config.ini or similar file in CdC but did not see one.
CdC will be using the ASCOM driver for the scope. The timeout is initially 1 second while it's identifying the scope but is then set to 4 or 5 seconds. It won't cope with timeouts on the serial port while connecting. I wouldn't expect other applications to connect at the same time as CdC because the serial port is in use the whole time the scope is connected and I wouldn't expect it to connect if other programs have connected first. Chris
