I forgot to mention... included is a demo of a glitch (starting at 9:02) when I try to get the Drift Plot tab back. The arrow that is supposed to do it, doesn't work reliably.

Jasem,

I had a similar problem a while back:

indilib.org/forum/ekos/3026-change-to-gu...h-recent-update.html

You solved the issue back then, it was an older mistake in the guide module code, as I recall.

Maybe that same error was reintroduced during a recent update???

Best

Jo

PS: That problem was specific for the ZWO ASI120MM I was using as a guide cam, the same one pug is using according to his log. It did not affect other guide cams.

When I did the tests 3 days ago my setup wasn't balanced since I did not have the main instrument installed. Today I did the same test again with all equipment well balanced and the result remains the same: Calibration fails when subframe is activated and succeeds when it's not.

I have to come back to this issue since it still remains. It's unrelated to my equipment since it occurs with simulators, too.

I noticed in the logfile that pulse duration was changed from 500ms to 1000ms. As I see it, that's why the initial position isn't reached but "jumped over".
Log and video attached.

I not have read all thread, report only my issue ( solved ) with calibration.
I have Celestron GPS mount and in indi mount options I have "absolutely" to set "Use Pulse Cmd" off
if this option is on ...not calibrate.

Try it if it's for you too .. I repeat, I did not read the whole thread, in case you're talking about something else ... excuse my intrusion.

Bye.

Thanks for your suggestion. I think in the Telescope simulator (that's what I used in this example) there is no such option. At least I can't see it.

You need to track before you guide.

Same result. If I got you right... New log attached.

If you try the same, does it yield different results? Did you try a real test at night, calibrating with subframe enabled using your equipment attached?

I just tested in my observatory and it guided fine.

Puzzling. I tried again in the sky. Whatever I do, the pulse duration of the third step back in RA is doubled as well as all following pulses. Why is that? I certainly did not tell Ekos to double the pulse duration. What''s the difference? I'm running the lastest Ekos/Indi, ASI 294, Losmandy G-11. What else can I try to figure out where the 2000ms pulse duration comes from? Is it possible that the problem lies within the Losmandy driver? [Edit: Well, it would not occur in simulators then]

The screen recording can be found here:
www.sendspace.com/file/2132no

Thanks for the log. I found the issue. The problem was when Auto-Select star was disabled, the code was not updating the subframed star coordinates properly. This is now fixed in GIT and should be available in Nightly later.

Is *this* where the 2000ms pulses came from? Since the guide star position wasn't updated correctly, ekos thought my mount was off/suffering from backlash thus increased pulse duration ?