SharpCap Forums

SharpCap v4.1.12717.0 (X64, 64 bit) running on an HP Envy i7-13700H Laptop
ASI2400MC-Pro camera, full frame, Bin1, RAW16, FITS

I've attached three logs. This problem happened three times in a row and then I gave up trying to figure out what happened.

I was taking flat frames and the flat(bias) was fine, then I wanted to take a flat(dark) and each time the process got to the point where I'm supposed to cover the telescope it failed. My workflow is to replace the filter drawer filter with a dark filter, turn off the light panel and then hit the proceed button. Each time SharpCap was frozen (locked up) when I came back to the laptop after switching the filter and turning off the light panel. The first time it did so with a strange histogram (attached). The next two times it just froze with the last histogram from the light panel. It appears to be a camera failure.

I was thinking it had to be related to switching off the light panel but don't really see how that would cause the camera to fail. By that time I gave up on the flat(dark) and proceeded to image with a flat(bias). The light panel is a Gerd Neumann Aurora so perhaps the EL foil produces some kind of field when switched off that scrambles the brain of the 2400.

This is the first time using the Aurora with the ACL200 so perhaps the close proximity of the panel to the camera is the issue. Plus it's a 315mm panel since I also use it with a C11.

Hi,

all three logs look like the underlying cause of the problem is dropped frames from the camera - you can see the 'Capturing : 0 frames (7 dropped)' in the status bar of your screenshot and the matching evidence of dropped frames can be seen in the logs. In one of the logs, SharpCap actually tries to reset the camera to get some images out of it after going for more than 60s without any frames arriving.

Also visible in the screenshot is that the 'Turbo USB' setting for the camera is set to 'Auto' and has a value of 100. Turning that off of auto and turning the value down to the minimum (40) would be my first suggestion - it will drop the frame rate, but should give a big boost to reliability and may be all that's needed to deal with this problem.

cheers,

Robin

Robin,

This is similar to my 294MM experience where things change when reopening, even when the remember camera settings box is checked. I don't use "Auto" for any settings but somehow the 2400 opened with the Turbo USB on Auto and I missed it. I'll make sure my startup workflow includes a review of every camera setting. I change cameras a kits a lot and profiles don't work for me either. It's my fault for not checking all the settings.

Mike

Hi Mike,

you could also try using the capture profiles functionality to save the settings you want for the camera, then set that as the 'default' profile for the camera in the 'Manage...' capture profiles window. When that's set up, the camera will always go back to those settings when you open it (again, if for some reason the settings load causes the camera to have an error, SharpCap clears the 'default' tag to avoid getting stuck in a loop where each time you try to open the camera it loads settings that cause the camera to fail).

What I will do is add a red notification if the default profile for a camera or the autosave settings get dumped due to a problem - that will at least give people a chance to spot this issue.

cheers,

Robin