1. Does QHY600 support hardware binning?
The CMOS sensor itself has some binning function but it should not be the hardware binning (FD binning). And also the binning in the sensor is based on the location of the bayer color . it means it will binning with the same position of the same color.And for monochrom QHY600 sensor, it is still use such a position to do binning. So we think it is not a good solution for the monochrom binning.
And since the very low readout noise of the QHY600, so the digital binning may bring more advantage. First , it can increase the fullwell. Binning at 2*2 will gives four times of the fullwell. Second, it will increase the AD sample depth. Binning at 2*2 will give 18bit data range. For readout noise, the N*N digital binning will cause the readout noise become SQR(N*N）= N times. For example, if the readout noise is 1.9e at 1*1 binning. The 2*2 digital binning readout noise will become 1.9*SQR(2*2)=3.8e.
2. What's the absolutely QE of QHY600？
SONY does not release the official absolutely QE curve of the sensor. There is only a relativity QE graph. (Can be found on QHY600 specification page). But we did a some experiment of testing the absolutely QE of QHY600 by comparing with a known QE sensor. . The article can be found at https://www.qhyccd.com/index.php?m=content&c=index&a=show&catid=23&id=261 The current test results shows a very high QE, it looks too high. We will find more sensor to do this work again.
3. How to set the gain, offset and readmode at the first using
4. Meet "Out of Memory"
Please make sure the QHYCCD SDK had been update to the last version. 2019.10.8 (V6.0.3) or later. The previous two version has a memory leak bug and it will cause more memory lost . And if it is still out of memory, it maybe the memory not enough in 32bit memory space. Since the 61mega pixels, the QHY600 require big memory. The SDK will use about more than twice of the size of the image data (in mono version it is 120MB per frame. so SDK need about 300MB, for color version it is 360MB per frame , so the SDK need about 800MB) And the image acquire software need one or more . For x86 system , the totally memory space is 4GB, many other X86 software will take this space so it maybe not enough memory there. We recommend to use the x64 software, like the X64 SharpCAP, X64 N.I.N.A software. If you are using the X86 software. it is best to close other software to reduce the 4GB space usage