Okay, so heres whats happening. When the Dark Frame was enabled it froze. So I disabled that feature. Now, when I run APPM the scope goes to Zenith as per normal and the status remains "Settling" but

Don't worry about APPM taking a dark frame. The scope could be slewing while taking the dark frame. It is done this way to save time. -Ray Gralak Author of PEMPro Author of APCC (Astro-Physics

Hi Ray, Gave it a go but it basically failed when it started to take the dark frame. I will try it without the dark frame enabled.

Nice quick fix there Ray! 🙂 From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <groups3@...> Sent: Sunday, October 4, 2020 5:03 PM To: main@ap-gto.groups.io

Hi Dale, The driver does cache many of the commands. However, what can slow the driver down is formatting the text and writing to the log file, especially on devices with slow disk write speeds. That

Hi Tony, I didn't realize the dome might stop and start slewing multiple times like in your video. I made a slight tweak to APPM to check dome slewing status in the settling state. If APPM sees the

I have tried active dome control with the same issue...the camera starts taking an image while the dome is still slewing. I always have the Nexdome driver selected...but IOT slave the mount to the

As another data point in this vein, we set NINA to poll drivers every 2 seconds by default. We found that some older hardware and/or their drivers have a tough time dealing with more frequent polling;

Tony, Have you tried using Active dome control mode? In APPM, you would instead point the dome control to the NexDome driver. APPM will then send the NexDome driver the mount's RA/Dec destination

Thanks. I had it set to 500msec but will set it to 2 seconds and see if that makes a difference. Roland

Hi Roland, > One thing you can do is to open the log file in APCC or the ASCOM driver and look to see what SkyX is doing at > startup. On mine I always see multiple errors with the above

Hi Ray, I did use the Hour Angle strategy. I think the issue is solely with SGP and the way it implements dome/scope slaving. I've brought this issue up with Jared (and the developer of the Nexdome

I have seen something similar with my SkyX on my laptop. If I have a Java app running on the laptop then SkyX will not operate correctly. It connects ok, shows "Tracking at Sidereal", but will not

Hi Tony, > I'm not sure whats up with SGP wrt dome control - but it always waits until the scope has stopped slewing before > it evens begins to think about rotating the dome. Ideally both should

One of the few times I wish I wasn't in a dome....doing a large APPM modei :)

>>>I'm slewing at 600x which seems comfortable. Are you in a dome? I'm slewing at 1200x. it's fast, but i usually only get a small number of failed solves we're not in a dome - rolloff @ obstech --

The model I ran was only a "small" one at 109 pts - but having to build in delays so that the dome has time to travel made that model take close to 2 hrs to do. I'm not sure whats up with SGP wrt dome

i had my 1600 set to 3 seconds, but we'll see if the added settle time makes a difference the slew speed can also affect this, and the 1600 slews pretty fast! i may look at slowing that down as well

IIRC its stated somewhere that a 2 sec settling time is ample for the AP mounts - but like you I find I need more time (especially when dithering). I've moved up to 6 sec at the moment and will see

>>>But whatever, so far I've only had 2 points fail. only 2 points failing is quite good FYI i was redoing a 100+ point model and took the time to watch some of the solver images being captured I