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

I am using "Passive" mode. Here are the settings I've put into the dome because of the dome rotation issue I get. I've up the settling time to try and allow the dome to have time to finish rotating as

Hi Tony, Maybe in a future version, but it really isn't needed in your case. Just correctly configuring APPM should do the trick. As mentioned in the link I provided, you should configure APPM to

Is it possible that a feature such as redoing a failed point in a new model - on the same night - can be put into APPM? Usually a failed point for me is that APPM decides to start taking an image even

You missed the point I made about searching first. :-) No you cannot redo a point. And nor do you need to redo the point provided there are lots of other successful points (say 80% or more

No, haven't asked the question about redoing a point that has failed - can it be redone for that model or not? I'm trying to use SGP (forgot about POTH) :). SGP does not seem to be the best wrt moving

Hi Tony, Haven't you asked this question before? https://ap-gto.groups.io/g/main/topic/help_with_appm_and_dome/76099333 BTW: a hint to anyone asking questions. In case a question has been asked

If a point fails during the mapping run - is there a way to redo it at that time or do you need to redo a complete new run? Also, sometimes it seems that the dome is still slewing when the camera