And tell or ask them what exactly? Remember, guidng via ST4 on the USB3 versions works in PHD2. Just not in Ekos...

In PHD2 you're using ZWO driver or INDI driver?

I use the ZWO driver and on-cam guiding. I didn't even know it was possible to use the INDI driver in PHD2.

I was using the ZWO driver that shows up in the PhD2 drop down menu. I don't remember whether that was there before I installed Indi and Ekos and whether the PhD2 ZWO driver is dependent upon the installation of Indi or whether the driver was included in one of the last PhD2 updates.
I agree with wvreeven: This problem's got to be rooted somewhere in Ekos, since the ST4 guiding worked until the January 29 update. Besides, nobody working at ZWO, they are out of the office until February 23 to celebrate Chinese New Year.

Agreed, this is not Pi3 dependent. I also have Zotac PI332 pico with 4 GB of RAM running Ubuntu Mate 16.04. Behaves exactly the same in all respects as the Pi3 does.

I tried this again now with the USB2 version of the ASI120MM and now I replicate the same problem I am having with the USB3 version! Sending guide pulses through the ASI120MM and ST4 connection from inside Indi Control panel and ZWO Guider Control results in movement in one direction only, with the mount rapidly drifting away. Guide pulses sent to the mount directly work fine in all 4 directions. I have not tried guiding in the field yet, will have to wait for at least one week, since I will be out of town again for the next few days.

*face palm*

I found the problem. It was indeed a commit I merged a while back. So while checking the code again, I noted the WE guide function was using NS direction. It's fixed, compile now or wait until tomorrow PPA. Sorry about that, should have checked the code first.

That’s great Jasem! Can’t wait for tomorrow!

I see that I introduced this bug. I tested the code using the ST4 port on an ASI174mini, but I was doing so on my Losmandy Titan, which still needed its worm block adjusted, and I put down the bad RMS to that, rather than a copy and paste error in the code!

Thanks for finding and fixing this.

De nada!

That's great, Jasem! I am glad to find out I wasn't crazy and that I could be of some help with the troubleshooting.
Let's do it again sometime! )

And thanks for all the great work you are putting into maintaining this outstanding platform! I don't think most users realize how much work must be going into this.
Salut!

wvreeven, I am very sorry, totally my fault! Those settings would make the deviations on your mount worse. I have two mounts, an Atlas Pro for my backyard and an iOptron SmartEQPro+ for traveling and grab and go. The values I gave you were for the SmartEQ, not for the Atlas. Even with those proportional gains, I can barely keep the guide errors within the 2" window on the SmartEQ. That mount has THE worst periodic error I can imagine!
For the Atlas Pro, I had to reduce the proportional gain - for guiding through the mount directly, not through the camera - from 133% to 100% with a guide rate of 0.5x sidereal. I.e. I reduced the amplitude of the corrections and thus the oscillations you and I have been seeing when guiding directly through the mount. With those gain values, guiding was good in my case. If you still see disproportional deflections, you may want to try to reduce the proportional gain further, I am not saying that I reached the optimal set point yet.
Hope that fixes the problem for you as well.
Best
Jo

Thanks for the warning, Jo, and no problem. Last night I tried guiding with the ST4 port again (after updating KStars, indi etc) but unfortunately it still didn’t work. For internal guiding via EQMod I already had reset the configuration so no harm done there. I’ll try with lower Proportional Gain next time and see if that helps. Thanks!


Clear skies, Wouter