I did a fresh git pull and now I am unable to reproduce the issue. Don't know wheter or not it has anything to do with the fresh git pull. In any case it had hampered my tests for several days. Should it re-emerge I'll post a video. Weird!

Hi Pit, everyone

FWIW and as Hy asked, it's working OK with the simulator from git a few days ago:
kstars: be4c957b6e971acac17f325fcac796e20e864cfe
indi: 3b4d0fe80c821bd1241e1dc801550dcd6f19d097

Logs attached.
Try the latest git?

Anyway, HTH and clear skies,
Steve


 

Hi Steve,

thanks for the check!
I have meanwhile verified that it is not the version of the ZWO SDK. I upgraded that one to 1.18, and didn't have issues last night.

Just checked the indi git, and there haven't been relevant changes since June 1. So I doubt that would change things.... I'll try to verify the simulator also works here, that should at least narrow down the issue a bit.

So I compiled todays git for both indi and kstars.  As I was afraid, no change.  As soon as dither is finished and guiding is resumed EKOS (or INDI) start aborting the ongoing guide exposures:It seems to me a command is sent to capture a frame, although guiding has never been stopped, and an exposure is already going on!?
I tried twice, same error, then reverted INDI back to the May 3 version (no downgrade of kstars.  So either it is fully within INDI, or some protocol has changed in INDI that EKOS doesn't comply with?

I checked the successful logs.  It seems, also with the old INDI version the first exposure after the guiding is resumed truncates the ongoing exposure, if I look at the timestamps:That is only 2.7 seconds between the two messages 'taking a 4.5s frame'.  But there it's only for this single moment.  All other exposures are taken properly, whereas for the new INDI it looks as if two processes were trying to expose, and they abort the exposure of the other....
(Sorry if I sound weird - just typing what comes to my mind...)

If someone has a smart idea how to narrow this down, I'm all ears!

 

Thanks for the report. I'll test tonight in the observatory and see if I can replicate this.

Video and logfile of the ASI guide cam freeze. After a while both ASI cams are lost and don't show up in lsusb anymore. All other devices are OK. All on latest GIT.

The logfile says:
[2021-06-06T00:59:16.886 CEST INFO ][           org.kde.kstars.indi] - ZWO CCD ASI294MC :  "[INFO] Starting the video stream with target exposure 0.100000 s (Max theoritical FPS 10) "
[2021-06-06T00:59:32.015 CEST INFO ][           org.kde.kstars.indi] - ZWO CCD ASI294MC :  "[INFO] Starting the video stream with target exposure 0.500000 s (Max theoritical FPS 2) "
[2021-06-06T00:59:32.016 CEST INFO ][           org.kde.kstars.indi] - ZWO CCD ASI294MC :  "[ERROR] Failed to set exposure duration (ASI_ERROR_GENERAL_ERROR). "

Thanks for checking!
A note:  I had mentioned May 3 as date of the working INDI version, but had only looked at the install date...
But it is actually as of April 26 (status commit 538ab217325838e2d53fb0f512087d1524149ed2)

I've prepared some intermediate compiles to narrow it down, but will have clouds the coming days
 

Dithering worked just fine in my test tonight with M17.

 

Thanks for checking!
That indeed looks like the guider cycle time is unchanged by the dither. Then again, it was already shorter than mine. Or it is somehow related to the camera? I use two ZWO cameras....
Unfortunately, weather prevents further tests here at the moment

I suspect this is an ASI driver/lib issue. Since Jasem doesn't use them, the issue doesn't show with his setup. Simulators guiding works as expected, too.



I might have a 20% chance to test guiding with my ASI combo tonight.

that would be a great test! I had, however, already tested the latest libASI, which did work with the old INDI, but not with the newer ones.

I managed to guide for a while although conditions were very bad. While guiding, I did not recognize any issues. However, I saw the Indi log window reported double requests for guide images after dithering. The amount of information in my logfile is overwhelming and I can't see whether it confirms the issue you reported. It's attached so everybody can have a look.

What I found though was the process of producing master dark images for the darks libary did not work at all. It crashed KStars multiple times when the master dark was computed and I never got a full run completed. After ~10 crashes I gave up.