Driver will not connect when no shutter hardware is present

[Tony Benjamin]

Using the new “Beta” ASCOM driver and firmware 3.0.0.0 I cannot connect to the Dome. I am using the correct COM port (COM4) and the driver does seem to be working - but POTH times out when I try to connect (see pic).

Here is the log file and the time of occurrence is around 2:54.

[Tim Long]

@Tony Benjamin There is some interesting stuff in the log file you’ve provided but I’m finding it difficult to interpret. There seems to be a problem right away at the start of the log, then there’s a session that appears to have worked. I have a request. Could you first delete all of the log files, then try to reproduce the issue you are seeing in as few steps as possible, then attach that new log file? It can also help if you can make a note of the time (to second accuracy) when the problem occurs and that will help me find it in the log file from the time stamps.

[Tim Long]

Issue has merit but awaits further input from reporter.

[Tony Benjamin]

I attached the new log above. I opened the ASCOM POTH Scope-Dome Hub program at 6:35 PM and tried connecting the dome to it at 6:35:10 PM, but all I got was this message:

Error connecting to dome

1CE - POTH

**The remote server doesn’t exist or is unavailable

**I’m assuming that this ASCOM utility (POTH Scope-Dome Hub) is the correct one I should be trying?

[Tony Benjamin]

I tried connecting the dome to Voyageur but I got an error that it could not connect (see pic).

I attached the log for this one above (I tried to connect at exactly 7:31 PM).+

[Tony Benjamin]

Also, forgot to mention…I only have the Rotator.hex file installed - as I do not have a Shutter!!

[Tim Long]

Change title to reflect the actual problem

[Tim Long]

Issue #39 was marked as a duplicate of this issue.

[Tim Long]

Issue #39 was marked as a duplicate of this issue.

[Tim Long]

Added a checkbox in the setup dialog that controls whether the driver will attempt to use the shutter. Unchecked by default.