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 ?

I did a nightly update last night, and this issue still remains. I am unable to calibrate with the sub-frame box checked.

This is weird since last night it did work here, after months of 100% fails. Edit: I had GIT pulled so maybe the latest code for whatever reason didn't make it into the nightlies? Are you running 18.04 or 16.04? I saw the 16.04 AMD64 version failed to build.

If you have the logs with GUIDE enabled, then it might shed some idea. What's the build date for your KStars? You can find this in the Help --> About KStars window.

There's a known issue reported in the forum that relates to odd coordinates passed for subframing by PHD2 to V4L2 CCDs, if that could ever be the case for some of you.

-Eric