SharpCap Forums

Hi YI,

you are still seeing the same issue that SharpCap is asking the camera to stop an exposure in progress and the request neither succeeds nor fails - it just gets stuck with SharpCap waiting for it to happen. Unfortunately this is one of the worst things to have to cope with - if the request failed with an error I could ignore the error and carry on, but you can't ignore it getting stuck as the program is stuck inside the ZWO SDK code, not in my code

If I had that model of camera to test with and could make the error happen myself, I could experiment with sending commands to the camera in different orders and things like that to see if I could fix the issue. However, since no one else has reported this error with the 6200 camera or any others, I am not even sure if I would see the error myself when testing with the same camera - it could just be some subtle aspect of your configuration that we haven't discovered yet.

Have you tried using any of the older versions of SharpCap 4.1 that are still available to download on the downloads page? There are versions going back to 4.1.10970 from August 2023. If the oldest of those happens to work then you could step through a few at a time, hoping to find the point that the versions go from working to breaking - knowing that point would let me work out the code changes made between the two versions and perhaps pin down the cause more easily.

cheers,

Robin

Robin

Thank you for your consideration.

As I wrote before, in V3.2 you can switch using the ini file without any problems.

I'll try it with the older V4.1.

Y.I.

Robin

An error occurred with v4.1.10970.0 as well.
I couldn't close the software, so I ended it with the task manager.
All v4.1 versions seem to have the same problem.

Y.I.

Ok, thanks for trying it out.

Sadly it's exactly the same problem - the application is stuck waiting for the camera to stop taking an exposure. I looked back at the history of the code and that attempt to stop the exposure at that point has been there since 2017, so it actually happens in version 3.2, but clearly doesn't cause any issues there. I don't want to make big changes based on this issue, since I still think it is a rare occurrence (if it happened to everyone, I'd have heard about it by now), and the StopExposure is there for a valid reason.

What I am going to try is to make the stop exposure request only happen if the camera is currently taking an exposure - that might get us past that point if the problem is maybe that the stop exposure request isn't needed at that point. In the best case, it might fix the problem, however it's also possible that the whole camera SDK is in some sort of broken state at that point and that we see the failure with stop exposure because it's the first thing that SharpCap tries to do after the SDK gets itself into a broken state. If that's the case then we will just see the software getting stuck on the next camera request.

Anyway, the next version (probably 2 weeks or so, since I am on vacation next week) will have this change.

cheers,

Robin

Robin

Thank you for your help.
Unfortunately, the result was the same.
I wonder if it's a problem specific to my camera.
I will continue to use it without the INI file for the time being.

Y.I.

Hi,

actually, the experimental change I mentioned above isn't in the version 4.1.13447 that you tested - I haven't released a version with that change in yet, but hope to do so next week.

thanks,

Robin

I tried it with SharpCap v4.1.13584.0, but an error occurred.
It works without any problems if I don't use the INI file, so I'd like to continue using it as is.

Y.I.

Hi,

same error again sadly, so the change didn't help (or, the conditions required for the change to have any effect weren't satisfied).

Unfortunately unless I can find some other way to attack this problem (like making it happen with a camera that I have to test with), I don't think I have any other things to try. Do you have any other ZWO cameras? Does an equivalent issue happen with them, or just with the 6200?

cheers,

Robin

Thank you for your consideration.

I got the same result when I changed PCs, so it doesn't seem to be the PC.

I only have the 6200, so I don't have anything else to try.

I'm getting used to the manual Camera Control.

I'll operate it without using profiles.

Y.I.