Running latest KStars built from source, as of a couple days ago.
When I run the PAA, it takes a picture and solves, and tries to move the mount. About 1 second later I get an error that says "Mount aborted. Please restart the process and reduce the speed." I did what it said and reduced the speed, but no difference.
Looking in the log, it starts out saying "First mount rotation remaining degrees: 30". Then about 1 second later it says "First mount rotation remaining degrees: 150.582". I'm guessing that's the cause of the problem.
I am going to try doing a "git bisect" to find out when this stopped working.
I seem to remember that if you checked the "Abort if guiding deviation > xxx arcsecs" checkbox, it would abort the current capture and try again. Now it seems to abort the entire sequence and moves on to the next filter. Actually it's worse than that. I was capturing Red. It aborted, skipped Green, then went onto Blue.
Am I remembering incorrectly, or has this changed?
The current align module behavior is giving me a lot of grief. I normally use Stellarium as my planetarium program, and I command mount moves from there. However, after doing a Goto from Stellarium, and then trying to do an align in Ekos, definitely causes undesired behavior, especially if I've done any slewing from KStars previously.
It seems the Align module remembers the last commanded position from KStars, and always wants to align to that, and not to what I've slewed the mount to. This is especially problematic, as the two positions can be many tens of degrees apart, and the Align module will plate solve and sync according to the old position, really throwing the model out of whack.
Why can't we just align to the current RA/Dec reported by the mount? When I do a slew, either from KStars, or from Stellarium, or any place really, the RA/Dec of the mount will be the desired position. Why can't Align just use that?
It seems if I select Sync, it works as intended. But then I have to slew again from Stellarium. Then go back to Ekos, and Sync again. And check the error. And repeat.
I seem to remember this working properly at some point in the past. Has this changed?
If you plug the USB cable directly into your computer instead of the Pegasus hub, does the system then recognize the port?
Fantastic news! I've also noticed the problems reported in this thread. I am looking forward to testing these fixes. Doesn't look like it will be any time soon, though. Nothing but clouds this time of year.
After you change it to your desired rate, did you go to the Options tab in the EQMod driver, and click the Save button next to Configuration?
I'm glad you got things working.
However, if it were me, I'd much rather use the guidescope and ASI120mm for polar alignment than a DSLR. The main reason is when it comes time to adjust the alt/az bolts, you want to loop images quite quickly, about 1 per second. I've never been able to loop images from a DSLR anywhere near that fast. Faster looping of images makes the polar alignment routine so much more pleasant. And don't worry about accuracy, the resolution of a guide scope with the guide camera is plenty high enough to get you a good polar alignment. If you're autoguiding, you only need to be within a few arc-minutes of "perfect".
Yes, that is correct.
That's mostly correct. But you need to enable PEC in the INDI control panel for the mount to actually use it. When you power the mount on, that feature is turned off until you explicitly enable it.
But yes, I used PEMPro in Windows, let it collect about an hour's worth of data, created the curve in PEMPro. Now here's the important part. It will ask you to save the curve to EQMod. Say no to that, it won't do what we want. Instead, in PEMPro, go to the PEC playback tab, and start playing back the PEC curve. Then in the EQMod control panel, expand it so all the controls are visible, and press the "record PEC" button on the far right side. That is how you actually upload the PEC curve into the mount's firmware.
Heh, my high school physics teacher used to always tell us, a number without a unit of measure is meaningless. Ekos is mostly pretty good about that (showing what the unit of measure is along with the number). PixInsight is terrible about that.
Even though the driver is called EQMod, it actually has nothing to do with the Windows ASCOM driver by the same name. In particular, there is no place to put a PPEC file for the driver to use.
To upload a PEC curve to the mount, the easiest thing to do is to do it via Windows and PEMPro.
Unfortunately, when you clicked the button to record the PEC to the mount, all you did was record an empty curve (a flatline). This is because while it is recording, it is "listening" for guiding pulses, and uses those to create the internal PEC model in the mount. But because you had guiding output disabled, you didn't actually record anything.
Please note that using PHD2 to try to create a PEC curve will not be optimal. It will record all the noise resulting from bad seeing, etc. since it will only record for a single worm period. Software like PEMPro will collect data over many worm cycles, create a smoothed curve, and can then upload that to the mount (through the Windows ASCOM driver).
To add some confusion, the Windows ASCOM driver can do its own PEC, independent of the PEC stored internal to the mount. That's not what we want. We want the PEC to be stored in the mount, so that when we reboot into Linux for INDI, the PEC is inside the mount and will just work.
The messages about the PEC being disabled while guiding are normal messages, which should probably be removed (or turned into debug messages). When you have PEC enabled in the mount, guiding pulses can end up being ignored or truncated. So to overcome that, the driver will turn off PEC, send the guiding pulse, then turn PEC back on. Those are the messages you are seeing, and is nothing to be concerned about.
I also get the same results. If I bin my guide camera 1x1 (ASI290mm mini) it usually takes a few seconds after receiving the image and issuing the guide pulse and taking the next image. Binning 2x2 does speed things up, but still takes at least a second.
I do find this to be a bit weird, since on the autofocus tab, with full field enabled, it takes a couple seconds to find all the stars when binning 1x1 on my ASI1600mm Pro. If I bin 2x2 or especially 4x4, it's extremely fast. So I would expect the guiding tab to find the stars pretty fast, since it is lower resolution than my imaging camera.