I am using the ASCOM Device Hub (ADH) with an AP mount and NexDome in the Southern Hemisphere because it gets the dome geometry RIGHT. Exactly right. Just configured it with the dimensions of my gear to get the scope centred in the slit throughout the sky.
Connection is a different issue.
I run Voyager as Administrator, so all programs and drivers spawned by Voyager also run as Administrator. The ASCOM Device Hub seems to launch ASCOM drivers as User, not Administrator. The ADH manages the connection of Run as Administrator client programs, and ASCOM drivers run as User.
If I try to connect an Administrator mode client (say PHD2 or MountWatcher.exe etc spawned by Voyager) directly to the mount driver, the system spawns another instance of the mount driver as Administrator. This second instance of the mount driver fails to access to the com port. To overcome this, every piece of software spawned by Voyager needs to access the mount driver through the ASCOM Dome Hub.
I find when Voyager connects to it’s ASCOM devices, the ASCOM Device Hub reports that it is connected to the NexDome driver but it cannot access the dome azimuth or shutter status. I resolve this in the ADH interface by manually disconnecting and re-connecting the dome. This works if you can find the ADH interface, but I can not manage it from an unattended dragscript yet.
An easy way to find the ADH interface is press [ALT][TAB] and click on the ADH.
Finally, the ADH seems to revert to this partially connected mode from time to time. My dragscripts tend to fail dome actions late in the run, but the dome still executes these commands. Voyager is just unaware, and raises an errors or timeouts on dome commands.
For now, the ASCOM Device Hub puts me two steps ahead and one step back.
Here is how to bring up the DH app once voyager connects.
Tom let me know more about your problem if it continues. I checked my Voyage logs from and my problems was not Voyager or the dome. Hopefully there is private message function.
It would be best to take it off line here .
I can put you in touch with the developer if you continue to have problems.
Then I do not need to launch ADH seperately but can let Voyager do it? When Voyager does open it then the scope info (Azimuth etc) should automatically populate ADH - which I do not think is happening at the moment?
At the moment, if I do have the mount set to “ASCOM.Device Hub.Telescope” (instead of selecting the AP driver) then I always get the following error:
I found abit more about what may be going on. When I click on the properties for the AP mount in ADH I get this error read out (basically saying it can’t connect to the V2 driver).
Yes looks like there is a problem connecting the AP driver to the hub. This is not coming from Voyager.
Your Voyager settings are correct. When the hub functions correctly, you should be able to disconnect the scope and dome from the hub. Then close the hub app. Voyager is will connect the hub and dependent devices to the hub
You need to troubleshoot the AP driver.
Make sure the scope is on and properly connected.
When it works correctly you won’t see this error.
Are able to connect with POTH or ASCOMDome?
The hub connections must be tested and working by itself. If the scope is properly connecting it should show RA and DEC etc on the Device window hub in red letters ( Or similar for POTH).
If you keep receiving errors like this you will need to try the ASCOM IO forum for help.
This beyond our help on this forum since it is an ASCOM or AP problem.
Yes. POTH seems to work/connect fine and I can get the scope data if I connect with ADH manually (not through Voyager). Will investigated the ASCOM IO forum.
You also mentioned its possible to get the developer directly involved?
The AP driver was hard coded to always run as admin (not sure how) and disabling that solved the problem. PHD was trying to run and connect to the driver, which spawned a second driver in Admin mode. So, I disabled admin mode for Voyager on Tony’s machine and now everything works perfectly.
The ASCOM Hub is hard coded to not allow elevated rights. Why the developer did that, I have no idea.
How can you tell if A-P ASCOM driver was running in admin mode? A-P ASCOM driver is not a executable program so how did you control admin mode for A-P ASCOM driver? Did you do that by disabling admin mode for Voyager?
I imaged last night with Voyager and after reading your message in this thread and just a few minutes ago I checked A-P ASCOM mount driver file of my laptop and it’s not set to admin. Does the mount need to be connected to laptop in order to put A-P ASCOM driver as admin? My equipment is put away so I cannot connect to the mount and laptop at the moment.
OK, it turned out I don’t need the mount. Even without any devices connected to laptop, I clicked on “CONNECT” button of Voyager’s Startup window and I can see A-P V2 ASCOM driver and it says “ADMIN” above of ASCOM logo. Then I disabled admin for Voyager and sure enough, the “ADMIN” label was no longer there. It does not necessarily mean A-P ASCOM driver was put in admin mode, does it?
Anyway, I’m glad Tony got it resolved. Next time I image, I will run Voyager with admin mode disabled.
Using Voyager in no admin mode must have behavior on correct working. You can lost official support.
Typically an application must run with the privilege that user asked, if Voyager running like admin and open an application that run for first time this application must run in admin mode (like correctly do the AP driver) . If this application are harded code to run in normal user isn’t compatible with Voyager.
