Image download fails when capturing a frame with bin 2x2, with a QHY294C, native driver

[Former user]

Nina 1.10, x64 QHY294C, QHY native driver, files copied from SDK 2019-11-15

Imaging works well in general, but when bin 2x2 is selected, image download fails.

• Connect Camera
• Go to "Imaging" section
• Set bin to "bin 2x2"
• Capture a frame

The image is not available, status is stuck at "Downloading", where normally (in my case) it would auto-stretch, debayer then be available in the "Image" section.

When this happens, I can't capture anymore unless I disconnect (inside nina) camera and reconnect.

Relevant entries from the log, written only when I disconnect the camera (inside nina):

[2020-01-24T16:02:58]    [ERROR]     [MemberName] CaptureImage
[2020-01-24T16:02:58]    [ERROR]     [FileName] E:\Projects\nina\NINA\ViewModel\ImagingVM.cs
[2020-01-24T16:02:58]    [ERROR]     [Message] Error retrieving image data from camera!    at NINA.Model.MyCamera.QHYCamera.<>c__DisplayClass174_0.<<DownloadExposure>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NINA.ViewModel.Equipment.Camera.CameraVM.<Download>d__69.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NINA.ViewModel.ImagingVM.<>c__DisplayClass78_0.<<CaptureImage>b__0>d.MoveNext()

[2020-01-24T16:02:58]    [ERROR]     [MemberName] SnapImage
[2020-01-24T16:02:58]    [ERROR]     [FileName] E:\Projects\nina\NINA\ViewModel\ImagingVM.cs
[2020-01-24T16:02:58]    [ERROR]     [Message] Error retrieving image data from camera!    at NINA.ViewModel.ImagingVM.<>c__DisplayClass78_0.<<CaptureImage>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NINA.ViewModel.ImagingVM.<CaptureAndPrepareImage>d__76.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at NINA.ViewModel.ImagingVM.<SnapImage>d__103.MoveNext()

[Eric Walden]

I’ll say that with native driver QHY600 any attempt to use 2x2 binning crashes NINA out hard. I don’t have log files handy as I am off site now.

[Dale Ghent]

I’ve alerted QHY to this last month, but haven’t heard back regarding it. I have a QHY294C as well and am able to reproduce this. I also have a QHY183M, which also does 2x2 binning, and it produces binned images just fine.

The problem is when our driver runs the SDK function that retrieves the image from the camera after the exposure completes. The function never returns, and appears to consume a large amount of memory before crashing and taking NINA with it. When QHY returns from the lunar new year holiday, I will ask that they continue to look into this.

[Daniel Lorenzo]

This issue has been created by me. I will also add that I tried a bit with ascom driver too.

When capturing in bin2, i get a completely overexposed image although it was low signal (a dark with leaks).

After capturing in bin2, reverting to bin1 get me back a low signal image, but all pixels are offset by 1pixel, like a grid ..and this is the debayered image.

And after all that, disconnecting the ascom driver and connecting the native driver, it is stuck on Download after capturing, whether it is bin1 or bin2. I have to restart NINA to make it work again.

[Daniel Lorenzo]

Tested again, there is bin1 and bin2 works well with ascom driver, but when bin is selected once with ascom, then app requires a restart to be able to capture with native driver again (no matter which bin, even unselected).

[Dale Ghent]

Yes, I am aware of the 2x2 binning failure states. This also occurs with the QHY600, as also stated. The issue is known and has already been raised with QHY, but I have not heard back from then about it. As I explained in my previous entry on this issue report, I hope to hear from them when they return from their new year holiday.

[Daniel Lorenzo]

a new SDK version is available:
https://www.qhyccd.com/index.php?m=content&c=index&a=show&catid=127&id=162

[Dale Ghent]

It is already in the current 1.10 build. It is highly suggested that users update their USB driver as well:

https://www.qhyccd.com/index.php?m=content&c=index&a=show&catid=141&id=62

[Daniel Lorenzo]

I have great improvements under sharpcap, for my low powered computer in my obsy, since they added the “usb traffic” control.

I’m also able to use bin2 normally. There was quirks before or even not working sometimes (all frames dropped).

I’m hoping it may resolve issues with bin2 in NINA. I already use the nightly 1.10 from 2 weeks ago, but I guess I have to download the latest nightly.

SDK version: 2020-02-03

[Daniel Lorenzo]

Tested all latest and bin2 is still an issue
NINA 1.10 # 58
SDK 20.2.3.0

[Dale Ghent]

Yes still aware of this. I emailed QHY last week about it but have not received a response as of yet.

[Frank Zoltowski]

I’m not sure this is an SDK problem. I have a 600M and version 1.9 did the 2x2 binning correctly. When I tried 1.10, 2x2 was OK in that it did not crash, but the file sizes were all 180 Mb in size, vs around 120Mb for a normal image and 30 Mb for a 2x2 (Issue 398). In these cases, the FITS headers were OK such that when you loaded them into PI and saved them, the file sizes were correct with no loss of data. When this was fixed, the file size is correct for a 1x1, but any 2x2 binning takes out NINA. The SDK (19.11.15?…the previous) did not change between when I used 1.9 and 1.10 and it’s correction for the 600M file sizes. I noted this in issue 411.

[Daniel Lorenzo]

@Frank Zoltowski Have you tried with an alternative app such as SharpCap?

[Frank Zoltowski]

Daniel,

My pc that I use with my 600M did not have SharpCap on it,but I installed it. The 600M works in 2x2 binning if the force single frame is off. As soon as I set it to “on”, it crashes. So maybe there is an underlying SDK problem. The 600M 2x2 binning did work with 1.9 as I have a library full of 2x2 dark frames taken with it. Since 1.10, nothing though.

[Dale Ghent]

Problem found and patch submitted. Read all about it in pull request #449

[Daniel Lorenzo]

woohoo, nice job

[Stefan B]

Fix in Nightly #62