5/17/2023 0 Comments Mountwatcher for windows![]() ![]() It therefore doesn't need to be running all the time. SurplusMeter itself is now merely a viewer/controller. Traffic monitoring is now done by an invisible agent application (SurplusMeterAgent). SurplusMeter 2.0: keep track of Internet traffic volume. MountWatcher 1.0: auto organize, automate, monitor mounting of volumes. The new release has interface improvements. IP Observer 0.7: shows IP address/open ports and informs by email. The latest release new application and toolbar icons, one window instead of two, no global floating window, main window is resizable. ![]() ![]() Mail Archiver X 1.5b4: archive, clean and browse your email. The new release has improved log and metadata cache file finding and updated Chinese localization. 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.AppZapper 1.3.2: completely remove apps with drag and drop simplicity. My dragscripts tend to fail dome actions late in the run, but the dome still executes these commands. 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. 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. To overcome this, every piece of software spawned by Voyager needs to access the mount driver through the ASCOM Dome Hub. 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. 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.
0 Comments
Leave a Reply. |