When Cooling Power is stopped, SC breaks connection with camera

[Menno555]

Hi Robin

I have a thing here where, when I have gradually warmed the camera after a session and then uncheck the Cooling Power checkbox, SC breaks all connection to the camera and gives the red error bar on top.
Weird thing after that, is that SC forgets the last used settings of the camera. When the camera is reconnected, SC sets it to SER format instead of FITS, sets it to 50ms instead of the usual 500ms, the USB settings are also not as usual.
During setup for the session and the session itself, everything works just fine. Checked USB connections (both physical and on PC) and there everything is also fine.
Attached is the log to when the disconnect happend. As far as I can see it starts with:

Warning 03:25:28.770670 #28 Error when trying to refresh Cooler Power : Exception of type 'ASICameraException' : Error 'ErrorCameraClosed' from call to ASIGetControlValue(cameraId=0, controlType=CoolerPowerPerc)

SC v4.1.12419.0 64bit
Windows 11 Pro
Zwo ASI071MC Pro

Menno

[admin]

Hi Menno,

thanks for the report - I think I might know what is happening here...

I added some code a while back that fetches a custom name from ZWO cameras to display in the menu if you have 2 or more of the same model (so you can tell them apart). To get the custom name you have to briefly connect to the camera, read the name, then disconnect. All fine so far...

In your log, a USB device disconnected at 03:04:33. That makes SharpCap flag that the list of cameras might be out of date since a USB device has been removed. I think you probably opened the 'Cameras' menu at 03:25:28, which made SharpCap check to see what devices were still around as it knew it's internal list might be out of date. That ended up re-detecting the ASI071MC, but as part of the process it opened/read name/closed the camera. Looks like that 'close' as part of the device list update is also closing the camera for the main part of SharpCap, which I didn't expect (but maybe I should have expected it...). Everything after that is just a response to the camera unexpectedly being gone...

I will have a look - should be able to fix that fairly quickly.

cheers,

Robin

[Menno555]

Mmm nope, no opening of the Camera menu.
My normal workflow is to first in SC disconnect the manual filter wheel (no physical filterwheel attached, I use it to get the used filter in the FITS header), then disconnect my mount (that is the USB disconnect you see at 03:04:33 cause it runs through a USB WiFi adapter which I disconnect in Windows then also) and then slowly let the temperature of the camera go up with 5 degrees Celsius steps.
When the camera cooling power is then at 0, I disconnect the camera and close it in the Camera menu.
But in this case the whole camera gets closed as soon as I disconnect it in SC, so there was no Camera menu used. Maybe I did open it to see what was going on after the disconnect but I don't recall that.

Menno

[admin]

Hi Menno,

must be something else that triggered the pending scan for new devices to actually happen then (it's not just opening the camera menu, but that's the most common one). I repro'd the issue by

* Open camera
* Camera menu, select 'Rescan' which manually flags the camera list as out-of-date
* Open camera menu again - camera closes

I have a fix which will be online to download in about 10 minutes

cheers,

Robin

[Menno555]

Thanks Robin
Looks like it's going to be clear tonight, so I will try it out.

Menno

[Menno555]

Hi Robin

Everything went well tonight, bug seems fixed

Menno