Incidentally, I thought this might be interesting visually. In Blinking through last night I noticed one with a doubling of sorts. Notice how all the bright stars have a companion at about the 7 o'clo

I can, but those large spikes to me seemed more about the mount than guiding, so I thought I would start here. If no other advice in a day or so will head over there. Thanks. Linwood

Something has changed. My guiding was great, usually in the 0.2-0.35 range, occasionally less than 0.2. The last three outings it has been awful, in comparison. I had a theory -- the jet stream dipped

I have the same, and it's simple to tie them together by just doing a powerpole black (only) and running it between the two rig runners. Then if you switch to one supply, or batteries, etc. it's alway

My understanding is you should check it, so that the adjustments are scaled by DEC. It is not changing the tracking rate (i.e. what APPM is governing) but the guiding adjustment pulse. Here from their

Have you considered allowing your ASCOM driver to communicate over IP with APCC? For many of us that would completely get rid of the Eltima's need, I think, as well as the last mount related COM port.

#APCC

That may not matter. At the distance from the sensor, the prism will cast a very ill defined shadow, much like dust on filters. I.e. stars may show through it. I have their OAG-L and originally positi

There is a "verify model" run you can do, which runs a new model (does not need to be same point count) using the currently loaded model, so you can see how close the various slews come to the expecte

You can use the "Direct guide" guider under equipment, and NINA will do a dither by slightly moving the mount.

I am (1.9.3.3). And I guess my main concern is knowing when to be annoyed. I assume if it can't read the encoder it just goes by dead reckoning, until it can? I.e. it does not interrupt any operation?

Last night I imaged, everything worked fine, the mount parked (2) about 3am, at 8am or so I woke up, did a slew-to-zenith to do my flats. Two errors popped up: Error reading from DEC encoder and No Re

I'm on NINA Beta 34 which is hot off the presses today, and running 6.5Sp1, and there was no such warning, perhaps you were on the non-SP1 version or I think there was a pre-release Sp1? I'm curious a

I have no idea specifically but have been on-and-off looking for a similar path from my homemade weather station, which has a GPS. For time sync this is easy -- NTP to windows, set APCC to sync the mo

Thank you for pursuing and fixing what is obviously a rare error. I'll grab the new version. Though I shall be careful in that area regardless, and move on to finding even more obscure ways to break t

When users complained that the new GUI on Teslas was inconvenient, Musk famously responded "User Input Equals Error". So his theory is if the user just does nothing and lets the software do it all, ev

What can I say, breaking software is a gift. Or a curse. Yes, now that I realize the cause, the solution is obvious. I renamed them because I have two OTA's, and planned to reuse the models, and the n

No, still running the released version of 6.5SP1, I tend to have enough stuff break around me without asking for trouble with the latest version of ascom. But if you think it will help I can. So it do

Sorry, Ray, when I say it was because of the model name, I meant it was because I renamed the model and the model name APCC was expecting was not present. It's easily re-creatable for me. Last night I

Thanks, Ray. Several things to digest here. And I have a different slant on the theories below after more research. First, I was indeed doing a test of a new star analysis program on NINA. It is quite

I was doing a three point polar alignment in NINA, as I do every night, and when it started slewing (usually a small movement to be just off the pole), the DEC axis spun clockwise (as viewed from behi