Hello,
Its me again with some new problem.
First one:
Ekos doesn't like exposures from the QHY5LII color.





The log of the driver:
The log file of kstars

Second one:

The QHY driver looks to crash and remain active even after stopping indiserver. Then the next time we start indiserver, if we don't take care to suppress the remaining process, the QHY is unusable.
Process list after disconnecting the qhy and stopping indiserver:

Turn off auto-debayer in KStars Options --> Advcanced --> FITS Viewer

Is there something to do to remove remaining qhy driver process after stopping indiserver ?

you can runto clean up any remaining drivers

Would it be possible to do it automatically when we stop the indiserver ?

Another little problem, when I make test of the autoguiding camera and this is not on a sky with stars, if I keep subframe checked the exposure process never end.
In this situation the qhy driver process crashes, maybe wait for some handshake, and remain active in process list. Might be nice to have a timeout to end the subframe search in autoguiding to avoid this.

When you stop the server, it stops all the drivers as well, this is from day #1. I just tested subframing in guide module with my QHY5II as well and it worked fine. I suspect there are some build issues somewhere as I can't replicate this here.

You are half right Jasem, this is partially a question of subframe.

In fact I can reproduce or not reproduce the problem following those sequences:

1st sequence:
1/ Go to exposure tab
2/ take an exposure -->OK
3/ switch to the autoguiding tab
4/ check subframe
5/ take capture --> KO

2nd sequence:
1/ Goto autoguiding tab -->OK
2/ check subframe
3/ Take a capture --> OK
4/ toggle to exposure tab
5/ Take a capture --> KO

3rd sequence
1/ Goto exposure tab
2/ Take a capture -->OK
3/ toggle to autoguiding tab
4/ Uncheck subframe
5/ Take a capture --> OK

4th sequence:
1/ Goto autoguiding tab
2/ Uncheck subframe
3/ Take capture -->OK
4/ Toggle to autoguiding tab
5/ Take capture -->OK

And this is in case of a KO when you disconnect all and stop the indiserver that the qhy driver remain active.
Maybe I have unwrapped one of the 1st or 2nd sequence.

Tell me please if you can reproduce the sequences. That will tell me if my installation is defective.

As you can see below I don't get any crash. You might want to try to debug the QHY driver to see what's causing it to crash.

indilib.org/images/videos/qhy_stuff.mkv

I ever reproduce the problem.
I must admit that I am perplex. I join the logs files here. But browsing them didn't teach me nothing.
Maybe you can discern some weird behaviour.
What do you advise me to do ?

When Debugging a driver that crashes, you debug it in GDB, not via sending logs as explained in the Read Before you Post Any Support Request article. So for your case, run:
Then connect to INDI QHY driver, then when a crash happens, go back to the gdb console and type in bt to get the backtrace and post that here. Good luck!

Hello Jasem,
I tested the qhy driver in debug mode. There is no crash message in the debug windows. It just stay silent and hang when if after a preview I take a capture with subframe.
I can't explain this bizarre behaviour. I am more and more perplex.