For some reason, MS has yet to make this procedure easy, even in Win11.
1. Go to Start -> All Apps -> Astro-Physics
2. Right-click APCC, select More, then Open File Location
3. In the resulting File Explorer window, right click the APCC shortcut and COPY it.
4. In the same File Explorer window, or a new one, paste this in the location field:
%APPDATA%\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
5. Paste the APCC shortcut into there
If you don't want it starting up anymore, or don't want it doing that on a temporary basis, you can go to Start -> Settings -> Apps -> Startup Apps and hit the slider on it to turn that off.
/dale
toggle quoted message
Show quoted text
On Dec 14, 2022, at 14:43, Brian Valente <bvalente@...> wrote:
Dale's suggestions are always at least slightly better than mine ;)
I'm going to update my process with his additional settings
On Wed, Dec 14, 2022 at 12:39 PM Dale Ghent <daleg@...> wrote:
I do similar as Brian. I go a step further and launch APCC automatically on boot, from Windows' Startup Apps. I leave the auto-connect to mount option off, though, because it might not always be on or connected. Of course, this is a dedicated imaging PC.
On Dec 14, 2022, at 12:38, Brian Valente <bvalente@...> wrote:
Hi Steve
My preferred approach which I think is close to the recommended approach:
- I use REST API for connection between APCC and ASCOM
- launch APCC and connect to mount
- click connect on mount from within third party apps. that will launch the ascom driver and connect with APCC (or in the case of multiple apps connect to the already running ASCOM)
in my experience connecting via third party app without first launch APCC and connecting to the mount causes issues for me
On Wed, Dec 14, 2022 at 10:20 AM Steve <stevebusch77@...> wrote:
Just my 2 cents......I use APCC, APV2, Sharpcap, and Stellarium. I launch APCC, hit the connect button, then hit the connect button for the driver like Emelio use to do. Then I launch Sharpcap and Stellarium and connect those. Last night, I tried the preferred order according the manuals by allowing one of the 3rd party software to bring up the driver (and not hit the connect button). Everything came up ok, however, throughout evening Stellarium and Sharpcap would sometimes freeze like the commands were not getting to the mount. I'd have to reboot (close and open them) the programs to make them work again. I finally shut eveything down and went back to my original order of bringing the APV2 driver up before the 3rd party software....things worked smoothly again with no glitches. So, that's the order that works for me. Not sure if it's right but it works. I have all the latest updates and I think I have all the settings correct in APCC. My vote would be to keep the APV2 connect button, or maybe I'm missing something? Maybe someone could explain the behavior...I think you find what works with your software/computer and just "go" with it. Thanks. steve
--
Brian
Brian Valente
astro portfolio https://www.brianvalentephotography.com/astrophotography/
portfolio brianvalentephotography.com
astrobin https://www.astrobin.com/users/bvalente/
--
Brian
Brian Valente
astro portfolio https://www.brianvalentephotography.com/astrophotography/
portfolio brianvalentephotography.com
astrobin https://www.astrobin.com/users/bvalente/
