![]() ![]() Voyager is just unaware, and raises an errors or timeouts on dome commands.įor now, the ASCOM Device Hub puts me two steps ahead and one step back. FromPlum Amazing:MountWatcher is a Mac OSX application used to organize, automate and monitor the mounting of Windows (SMB) and Apple (AFP) volumes/shares/disks. My dragscripts tend to fail dome actions late in the run, but the dome still executes these commands. Use flag -v to enable verbose output: the script will report start/stop events of eligible containers and print all detected file changes. Use the hand controllers update cable with a USB to serial adapter (or serial port) on the computer with your planetarium software set to talk to a Celestron mount. Use the hand controller to align the mount and do the 2-3 star sky alignment. Duplicate notification - a single change triggers 2 notifications to the container ), try event debounce feature: docker-volume-watcher -debounce 0.1. The second is also dependent on the exact model of the mount you have. This works if you can find the ADH interface, but I can not manage it from an unattended dragscript yet.Īn easy way to find the ADH interface is press and click on the ADH.įinally, the ADH seems to revert to this partially connected mode from time to time. If you experience duplicate notification issue (e.g. I resolve this in the ADH interface by manually disconnecting and re-connecting the dome. 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. Applies to: Windows Server 2022, Windows Server 2019, Windows Server 2016. mount-watcher: 16/24 GFileMonitor: add APPEARED event Fri Jan 16 23:59:33 GMT. ![]() To overcome this, every piece of software spawned by Voyager needs to access the mount driver through the ASCOM Dome Hub. longomatch Only apply the visibility hack on Microsoft Windows. This second instance of the mount driver fails to access to the com port. 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. The ADH manages the connection of Run as Administrator client programs, and ASCOM drivers run as User. The ASCOM Device Hub seems to launch ASCOM drivers as User, not Administrator. I run Voyager as Administrator, so all programs and drivers spawned by Voyager also run as Administrator. Just configured it with the dimensions of my gear to get the scope centred in the slit throughout the sky. SynScan App version 1.00 or above is required. Sharity 3.2: SMB/CIFS file system for Unix, mounts files from Windows. The new release has updated documentation. After installation, choose 'SynScan App Driver' as your telescope in the ASCOM client's ASCOM Telescope Chooser. MountWatcher 1.5: auto organize, automate, monitor, mounting, volumes. This ASCOM driver allows ASCOM clients to connect to SynScan App running on Windows, Android or iOS. ![]() 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. ASCOM Driver for SynScan App Version 1.4.0. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |