QHYCCD

QHYCCD Software Developer Zone => QHYCCD SDK FOR WINDOWS => Topic started by: QHYceced on December 03, 2020, 06:51:16 AM

Title: ONE page for drivers etc.
Post by: QHYceced on December 03, 2020, 06:51:16 AM
Hello
Recently got a QHY294c and last night I had a couple of hours clear and wished to install and check it out, but ended up with another wasted 2 hours for nothing.

I have very little time and 'Northern England - UK' can be ridiculously covered all the time and I am in a valley therefore weather forecasts are often wrong and I guesstimate it myself and get it mainly right - + I even have a narrow view of sky on 'supposed to be' Bortle 5.

Well could not detect it at all - nice start & I am NOT into SDKs at all... yet.

But my main question is: where is a ONE page only for installing 'whatever necessary' ?

Second, is there a Quick startup guide with 'correct' links?
I have no problems with computers and computing, but I am not a developer - even thou I played a bit with 'Python' during lock down!
;p]

I am on Windows 10 Pro

Thank you for a reply

M
Title: Re: ONE page for drivers etc.
Post by: QHYceced on December 03, 2020, 06:56:54 AM


Well could not detect it at all - nice start & I am NOT into SDKs at all... yet.

But my main question is: where is a ONE page only for installing 'whatever necessary' ?

Second, is there a Quick startup guide with 'correct' links?
I have no problems with computers and computing, but I am not a developer - even thou I played a bit with 'Python' during lock down!
;p]

I am on Windows 10 Pro

Thank you for a reply

M



Well found this link:
https://www.qhyccd.com/index.php?m=content&c=index&a=lists&catid=194

But a well made page would be FAR better - one for idiots in particular.

Just a though, it would increase QHYCCD status, in my view!
Title: Re: ONE page for drivers etc.
Post by: QHYceced on December 03, 2020, 07:27:57 AM
... just installed EZcap with QHYCCD version 20-6-23-0 on a windows 10 laptop.

Same blooming problem - then tried 3 other USB ports and ONE has detected it!

Those ports ALL work and other ports you could hear WIN10 detecting then disconnecting straight away!


In my view the problems is either the camera or the cable [which I will replace now] or the Drivers - which i believe IS ... the problem!

Nightmare of 'standard' connections - ridiculous!


Title: Re: ONE page for drivers etc.
Post by: QHYceced on December 03, 2020, 07:54:30 AM
OK, now it started to work normally!

On ANY USB !

In my view this is a Driver problem or it was still installing in background and disconnecting it a couple of times made WIN10 detect it.

I see it on Sharpcap too now.

I will have to re-install on my PC [more powerful too] then see if I can do some Darks.

I have read generally you set it up to 100-120 gain.

It certainly makes you waste time installing.
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on December 03, 2020, 03:08:30 PM
M,
I own a QHY294C.  Unity gain=1500  Setting the gain to 1600 puts the camera close to unity gain but it also the lowest gain that puts the camera into it's HGC mode which has the low read noise.  I generated my DARKs at these two gains. Also be aware that the whitebalance values(R,G,B) for the QHY294C are 64.  The QHY driver sets the whitebalance values  to 64 but I know that older versions of Sharpcap were setting the whitebalance values to 16.

You mentioned a gain of 100-120???  Those gain values are most likely for the ASI294mc.

Peter
Title: Re: ONE page for drivers etc.
Post by: QinXiaoXu on December 03, 2020, 07:19:44 PM
Hi,
    Do you also have other issue?If so,please let me know.
    And about download page,sorry for the bad experience to you,I will tell this to my colleague to improve it.
Best Regards,
QinXiaoXu
Title: Re: ONE page for drivers etc.
Post by: QHYceced on December 06, 2020, 06:28:45 AM
M,
I own a QHY294C.  Unity gain=1500  Setting the gain to 1600 puts the camera close to unity gain but it also the lowest gain that puts the camera into it's HGC mode which has the low read noise.  I generated my DARKs at these two gains. Also be aware that the white balance values(R,G,B) for the QHY294C are 64.  The QHY driver sets the white balance values  to 64 but I know that older versions of Sharpcap were setting the white balance values to 16.

You mentioned a gain of 100-120???  Those gain values are most likely for the ASI294mc.

Peter

Hi
Thanks for the valuable input.

Correct, 120 is for the ASI, I read the 1500-1600 [1601 starts I think] on Sharpcap for QHY.

I am getting older and I am learning more now than 20 years ago!!

I noticed that the Balance goes at 64 by itself.

I am still battling to get the Sensor Analysis - tried artificial light and white-light [weather]!

I set the Histogram at 65% [on the white curve] and Exposure on 150-250ms depending on situation.

Cannot get it done - tried 2 days at least 20 times.

A few months back had similar problems with QHY174M I used on Mars [only captured it once - weather was bad] and I managed after a few tries and it was on artificial light, if I remember well.

I also noticed that if you get near 200-220 Exposure at 65% [capping telescope with white 'stuff'] image starts to flicker as if camera is switching!

I am getting confused now.

It almost always stops saying to adjust light which was perfect at beginning.

Some time [twice I think] I managed to get the first line of green Measurement Graph crosses e/ADU [If I am not wrong] and then stops.

Do not know what to do now.

Although it is not really a 'must' to do Sensor Analysis as when you have correct setting your eye just do OK with Histogram, of course Analylsis will put camera at its best.

I am now stuck.

M
Title: Re: ONE page for drivers etc.
Post by: QHYceced on December 06, 2020, 06:37:25 AM
Hi,
    Do you also have other issue?If so,please let me know.
    And about download page,sorry for the bad experience to you,I will tell this to my colleague to improve it.
Best Regards,
QinXiaoXu

Hi
I am sorry too for being a bit despotic.

It is not my nature, but I like neat information.

The important one must be on ONE page and concise so anyone of any level will understand.

Am I right in believing the SDK when it installs also updates Camera Firmware?
That would explain why it was not detected initially - in my 'nobody's' view!.
M

PS I find myself to do at least 3-5 reCaptcha every time I post - mayvbe server should be set to recognise IP comparing it with the logged in person posting and ask one Captcha ?

Title: Re: ONE page for drivers etc.
Post by: QHYceced on December 06, 2020, 06:58:03 AM
OK ... I think I know what it is happening now.

- SharpCap 3.2.6457.0 (64 bit) - maybe I should try the 32bit - I remember there are some problems sometimes.
- Camera is on a SW 72ED prime focus
- Daylight - using a tee-shirt 1-2-3 time folded - it depends, sometimes I used the camera foamy containers as a cap [ just fits the 72ED] as a diffuser and shirt, I come up with 65% at ~230 Exposure - stable thin enough peak on White wave
- camera RGB on 64, RAW 16 1x1 [it is not upgraded to use 2x2 yet - do not think I will need to really]
- DDR buffer was on, this time off
- QHYCCD_Win_AllInOne.20.06.26.36 is installed

No change.

BUT ... I noticed Sharpcap reverse RGB to 16 - so it might be the problem I am having.

Should I use different .DLL for Sharpcap - I did update it

As Freddy Mercury sang: I am going slightly mad!

 ;D
Title: Re: ONE page for drivers etc.
Post by: QHYceced on December 06, 2020, 07:22:36 AM
Just realised I am on:  QHYCCD Software Developer Zone  !

Sorry - just my life at present is a mess, my brain frying - need a mental cooler like the QHYCCD !
Title: Re: ONE page for drivers etc.
Post by: QHYceced on December 06, 2020, 08:25:22 AM
I believe I must keep this post on this area as it is all c0nnected in my view.

What I have done now.

I have latest .DLL set on Sharpcap.

Now getting darker - wasted all morning!

Camera onto SW 72ED with white diffuser or shirt - no difference!

Exp: 235
Histo: 32%
RGB: 16 [auto set]

set exp to 239 NO CHANGE !
set to 245 NO CHANGE !
set to 255 Histo goes to 40% and starts to flicker with a white fascia on top ~15% of screen  !
set to 265-275-285-295 - as above!
set to 325 flickers oscillating at 50-55% - no white fascia!


What the heck is going on?

In my view - more as an electronics technician, than a developer, there is a problem between driver and hardware and confirms what Robin of Sharpcap stated.

There seems to be a number of QHYCCD cameras of various model doing this: cannot keep steady at minimal Exposure changes - maybe all of them.

I am really tired of this, I have spent money I do not have and paying for it.

Just annoyed!

Can QHYCCD finally fix all these annoying continuous problems?

Maybe I should have real;ly spent more and get an ASI - just to hopefully avoid all this mess I do not really need in my life.

I am trying to set up things for retirement and I seem to only get grief!!

Then to make it worse, I need to pass 5-20 [yes 20] reCaptcha for each post!

TIRED !
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on December 06, 2020, 09:53:48 AM
SharpCap's sensor analysis will not work with the QHY294C...been there...consulted with Robin...no luck.  The video mode for the QHY294C is erratic. I told Robin that the QHY294C default RGB needs to be set to 64...sounds like that hasn't happened.  Video with the QHY294C is frustrating which is strange because the imaging chip is suppose to be superior as a security video camera. There are several posts on this forum from me regarding issues with video, drivers and fullwell capacity.

The QHY294C is very good at taking astrophotos...and that is what you should focus on.  You should concentrate on building your DARK library. I got my QHY294C in January, 2020 and this year I took virtually every photo at GAIN=1600.  To me, this is the sweet spot (low noise and large dynamic range). I generated my DARK library at GAIN=1600 and temperature=0C.  Exposures of 60, 100, 200, 300 and 600 seconds. 600s was used exclusively for narrowband imaging.  Over this winter I will add more DARKs but move to -10C.  I have taken some images at -10C and the DARK taken at 0C does a great job of compensating the amp glow.  I just checked and I was shocked to see that this year I have taken 174Gb of photos.

Sharpcap has helped to highlight the issues with video for this camera. Hopefully QHY will iron out these issues soon.  In the meantime, you need to avoid struggling with video and Sharpcap's sensor analysis.

Peter
Title: Re: ONE page for drivers etc.
Post by: QinXiaoXu on December 06, 2020, 07:20:25 PM
Hi,
    We released a new driver for QHY294C,this version modified the method of count exposure.You can try it,https://www.qhyccd.com/file/repository/latestSoftAndDirver/Driver/QHYCamerasDriver20201127.zip (https://www.qhyccd.com/file/repository/latestSoftAndDirver/Driver/QHYCamerasDriver20201127.zip)
    And please disconnect power and USB connection firstly,and install the driver.
Best Regards,
QinXiaoXu
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on December 07, 2020, 09:57:32 PM
QinXiaoXu,
I did some testing with https://www.qhyccd.com/file/repository/latestSoftAndDirver/Driver/QHYCamerasDriver20201127.zip

While the sensor analysis seems to work better and the video appears more stable I noticed that the read noise does not change when switching from LGC to HGC at GAIN=1600.  I suspect that the HGC mode is not being selected. The noise in a BIAS frame at GAIN=1600 is identical to the noise in a BIAS frame at GAIN=1599.  Also the mean value of the pixel values stay the same...there should be a significant drop in mean value when the GAIN=1600

OLD 1599 BIAS.jpg and OLD 1600 BIAS.jpg are what my master BIAS frames originally looked like for GAIN=1599 and 1600. Notice the changes in Mean and Std. Dev. values.

New 1599 Again.jpg and New 1600 again.jpg are what my master BIAS frames look like when using these new drivers. Notice that the changes in Mean and Std. Dev. values are very small.

Peter

P.S. I also noticed that the whitebalance parameters are now 16.  My original drivers were setting them to 64 and the 64 value was the correct value.  Now I find that even if I change back to the original drivers the correct values for whitebalance are 16.  This is not a big problem for me but it needs to be documented and users should be made aware of this change.
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on December 08, 2020, 02:11:22 PM
QinXiaoXu,

Some additional information. 
-The firmware I have been using for the past year is timestamped 2019/11/6.  This latest camera firmware is timestamped 2020/11/23.
-I was able to get the Sharpcap sensor analysis to run once using the original 2019/11/6 firmware. The result are shown in "Sensor AnalysisOriginal Firmware.jpg".

-I tried the Sensor Analysis several times and as long as I used an exposure of roughly 800 to 900mS to start the routine, I found it was able to run thru the entire routine. Watching the screen as this routine executed I could see that the video was much more stable.  Typically this routine could never find an exposure that gave consistent histograms.  The result from the sensor analysis shows some unusual problems which make me think that the HGC is not being selected at GAIN >= 1600.  The "Sensor Analysis New Firmware16.jpg" is a screen capture of a typical result. The "16" simply refers to the fact that I had the whitebalance values set to 16.

Conclusion:
I believe your work to improve the video timing has worked well.  This version of the QHY294C driver has to be declared faulty because it does not seem to support the LGC/HGC switching at GAIN >=1600.

Peter
Title: Re: ONE page for drivers etc.
Post by: QinXiaoXu on December 08, 2020, 07:14:27 PM
Hi,
    Thanks for your test and feedback,I will let my colleague know this.
Best Regards,
QinXiaoXu
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on December 09, 2020, 11:05:25 AM
Some more comments...
-I also noticed that when using the new version of the driver that the sharpcap histograms were much more stable when I was changing the USB Traffic parameter.  With the original version of the driver I noticed that the histograms would vary a huge amount.

-I did some experimenting with taking FLATs and found that my camera appears to be working better.  Originally, if I would take FLATs at GAIN=1600 I had to be careful to avoid exposures yielding pixel values above 70%.  The camera would act as if it was clamping the pixels values due to a limited fullwell capacity. I detailed this issue in a previous post titled "QHY294C LGC/HGC Characteristics".  After I tried this new driver and then went back to the original driver there are two distinct changes in  my camera's behavior...

1)The correct whitebalance value for my camera is now 16...previously it was 64
2)The limited fullwell capacity issue showing up at GAIN=1600 seems to have disappeared.  I can now take FLAT frames at GAIN=1600 at any exposure level.  Pixel levels all the way up to 100% do not show the fullwell capacity issue.  The only exception I saw was when I tried using a USB Traffic value of zero.  This seemed to bring back the fullwell capacity issue.

This fullwell capacity issues causes all the pixel values to be limited to a mean value of 48,000 counts with a bell curve distribution of possible values.  When this fullwell capacity issue is happening it is impossible to achieve a pixel value close to maximum (65,534).  I also checked that the read noise for the camera is dropping when I use GAIN=1600 so I believe that the LGC/HGC logic is working correctly.

Peter
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on December 13, 2020, 09:14:30 PM
Sorry for my confusion.  The whitebalance parameters for my camera have always been equal to 16.  I got confused with how Sharpcap was originally setting the whitebalance to 64.

Peter
Title: Re: ONE page for drivers etc.
Post by: QinXiaoXu on December 14, 2020, 07:17:38 PM
Hi,
    We released a new version driver for QHY294C,it fixed the issue of RGB gain setting,maybe this can help you,you can try it.https://www.qhyccd.com/file/repository/latestSoftAndDirver/Driver/QHYCamerasDriver20201212.zip (https://www.qhyccd.com/file/repository/latestSoftAndDirver/Driver/QHYCamerasDriver20201212.zip)
Best Regards,
QinXiaoXu
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on December 15, 2020, 10:18:26 AM
QinXiaoXu,
Can you explain what the original problem was with RGB gain setting? I was not aware of this issue? I will let you know what improvements I see with this driver update.

I would suggest that the zip file contain a txt file that explains the changes and revision history. This is standard practice for most software developers.

Peter
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on December 15, 2020, 12:55:41 PM
QinXiaoXu,
I just finished testing https://www.qhyccd.com/file/repository/latestSoftAndDirver/Driver/QHYCamerasDriver20201212.zip

The QHY294C driver version is 2020/12/11
I created BIAS frames at GAIN=1599 and 1600.  They are identical and they are identical to my original BIAS frames at GAIN=1599.  This means that my QHY294C is not switching from LGC to HGC at GAIN=1600.  I did not bother testing anything else because this means the low noise features of this camera cannot be accessed with this version of the driver.

Peter
Title: Re: ONE page for drivers etc.
Post by: QinXiaoXu on December 16, 2020, 07:31:26 PM
Hi,
    I modified a new version SDK for QHY294,it modified the gain settiing,you can try it.This SDK is 32 bits,you can try it with 32 bits version SharpCap 3.2.
    About RGB issue,it is old version driver can't setup RGB gain correctly.And txt file is available,I will add it at next version.
Best Regards,
QinXiaoXu
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on December 18, 2020, 04:06:52 PM
QinXiaoXu,
I performed testing on the latest SDK   qhyccd.dll v2020.12.11  I used QHY294C firmware v2020.12.11
Sharpcap 32b was able to perform the sensor analysis.  I tried using USB3 and USB2 and the analysis worked using both. 

The one problem, which caused the sensor analysis to fail several times, was when it was testing the camera at it's highest gain.  This required the fastest exposure times.  This required the exposure to be adjusted by 0.1mS increments.  The analysis would try 2.1mS and then try 2.2, 2.3,...2.9, 3.0mS.  For all of these exposure times the actual exposure did not change.  It appeared as if the exposure time was not changing.  Once the analysis tried 3.1mS the exposure changed significantly.  This caused the analysis to hunt back and forth.  Most times it would alarm that the exposure was not responding and would stop the analysis.  Randomly it would succeed and continue.

Before I ran the sensor analysis I tried adjusting the USB Traffic.  This dramatically affected the exposure and some times caused the exposure to flip between what appeared to be two vastly different exposures. For the sensor analysis I used a USB Traffic value of 50.

The camera was correctly switching between LGC and HGC.  When I took exposures at GAIN=1600 I noticed that the fullwell limitation at 10,000e- was happening again.  This is easy to repeat.  Just point the camera at a bright wall and take an exposure at GAIN=1600 with an exposure that should cause the camera to saturate.  You should notice that the pixels did not saturate.  A histogram will show that the histogram peaks are at ~48,000 counts.


Peter
Title: Re: ONE page for drivers etc.
Post by: QHYceced on December 19, 2020, 09:40:35 AM
I finally managed nearly a week ago to do the Sensor Analysis after I updated driver [although I do not know why it still is the same June 2020 dated file] and got this:

Addition, Robin of SharpCap said it looks odd !

ADDED NEW SENSOR ANALYSIS after further update to latest  camera drivers 22 Dec 2020 ...

Second image below is today ... am I correct the e/ADU has improved at 1500 ? Not an expert ...
Title: Re: ONE page for drivers etc.
Post by: QHYceced on December 19, 2020, 10:20:41 AM
Regarding the drivers page etc. I mentioned earlier on this thread ... on this page:
https://www.qhyccd.com/index.php?m=content&c=index&a=show&catid=94&id=9&cut=2 (https://www.qhyccd.com/index.php?m=content&c=index&a=show&catid=94&id=9&cut=2)

I still see old driver.

Maybe this page should be updated, so one can check there if there are any updates.

Another problem is: QHYCCD software asks you to supply your email when installing to get 6 months more warranty and it 'never' accepts it or at least it seems not to!

It would be nice to have that working and list all those that supplied an email within a database to send 'every' update QHYCCD does to all signed up customers and also would be nice to get an extended 6 months warranty as promised!

I noticed today every time I reply in this forums, after posting it I get re-directed to a main page and not back to the same thread.

Just informing you

Mauro
Title: Re: ONE page for drivers etc.
Post by: QinXiaoXu on December 20, 2020, 07:39:01 PM
QinXiaoXu,
I performed testing on the latest SDK   qhyccd.dll v2020.12.11  I used QHY294C firmware v2020.12.11
Sharpcap 32b was able to perform the sensor analysis.  I tried using USB3 and USB2 and the analysis worked using both. 

The one problem, which caused the sensor analysis to fail several times, was when it was testing the camera at it's highest gain.  This required the fastest exposure times.  This required the exposure to be adjusted by 0.1mS increments.  The analysis would try 2.1mS and then try 2.2, 2.3,...2.9, 3.0mS.  For all of these exposure times the actual exposure did not change.  It appeared as if the exposure time was not changing.  Once the analysis tried 3.1mS the exposure changed significantly.  This caused the analysis to hunt back and forth.  Most times it would alarm that the exposure was not responding and would stop the analysis.  Randomly it would succeed and continue.

Before I ran the sensor analysis I tried adjusting the USB Traffic.  This dramatically affected the exposure and some times caused the exposure to flip between what appeared to be two vastly different exposures. For the sensor analysis I used a USB Traffic value of 50.

The camera was correctly switching between LGC and HGC.  When I took exposures at GAIN=1600 I noticed that the fullwell limitation at 10,000e- was happening again.  This is easy to repeat.  Just point the camera at a bright wall and take an exposure at GAIN=1600 with an exposure that should cause the camera to saturate.  You should notice that the pixels did not saturate.  A histogram will show that the histogram peaks are at ~48,000 counts.


Peter
Hi,
    Let us analyse issues,so now the issue is if you use 2020.11.27 version driver and old version SDK,camera can make the sensor analysis work better and the video appears more stable,but can't switch HGC and LGC when gain=1600,and if you use new version(2020.12.11) driver and new version SDK I sent to you,camera can switch HGC and LGC when gain=1600,but will have the issue of exposure changed significantly at 3.1ms and fullwell limitation issue,right?
Best Regards,
QinXiaoXu
Title: Re: ONE page for drivers etc.
Post by: QinXiaoXu on December 20, 2020, 07:42:35 PM
Regarding the drivers page etc. I mentioned earlier on this thread ... on this page:
https://www.qhyccd.com/index.php?m=content&c=index&a=show&catid=94&id=9&cut=2 (https://www.qhyccd.com/index.php?m=content&c=index&a=show&catid=94&id=9&cut=2)

I still see old driver.

Maybe this page should be updated, so one can check there if there are any updates.

Another problem is: QHYCCD software asks you to supply your email when installing to get 6 months more warranty and it 'never' accepts it or at least it seems not to!

It would be nice to have that working and list all those that supplied an email within a database to send 'every' update QHYCCD does to all signed up customers and also would be nice to get an extended 6 months warranty as promised!

I noticed today every time I reply in this forums, after posting it I get re-directed to a main page and not back to the same thread.

Just informing you

Mauro
Hi,
    About email unlock issue,you can contact my@qhyccd.com,and the driver download linke is here:https://www.qhyccd.com/index.php?m=content&c=index&a=show&catid=141&id=62&tdsourcetag=s_pctim_aiomsg (https://www.qhyccd.com/index.php?m=content&c=index&a=show&catid=141&id=62&tdsourcetag=s_pctim_aiomsg)
Best Regards,
QinXiaoXu
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on December 21, 2020, 02:30:52 PM
QinXiaoXu,
I performed testing on the latest SDK   qhyccd.dll v2020.12.11  I used QHY294C firmware v2020.12.11
Sharpcap 32b was able to perform the sensor analysis.  I tried using USB3 and USB2 and the analysis worked using both. 

The one problem, which caused the sensor analysis to fail several times, was when it was testing the camera at it's highest gain.  This required the fastest exposure times.  This required the exposure to be adjusted by 0.1mS increments.  The analysis would try 2.1mS and then try 2.2, 2.3,...2.9, 3.0mS.  For all of these exposure times the actual exposure did not change.  It appeared as if the exposure time was not changing.  Once the analysis tried 3.1mS the exposure changed significantly.  This caused the analysis to hunt back and forth.  Most times it would alarm that the exposure was not responding and would stop the analysis.  Randomly it would succeed and continue.

Before I ran the sensor analysis I tried adjusting the USB Traffic.  This dramatically affected the exposure and some times caused the exposure to flip between what appeared to be two vastly different exposures. For the sensor analysis I used a USB Traffic value of 50.

The camera was correctly switching between LGC and HGC.  When I took exposures at GAIN=1600 I noticed that the fullwell limitation at 10,000e- was happening again.  This is easy to repeat.  Just point the camera at a bright wall and take an exposure at GAIN=1600 with an exposure that should cause the camera to saturate.  You should notice that the pixels did not saturate.  A histogram will show that the histogram peaks are at ~48,000 counts.


Peter
Hi,
    Let us analyse issues,so now the issue is if you use 2020.11.27 version driver and old version SDK,camera can make the sensor analysis work better and the video appears more stable,but can't switch HGC and LGC when gain=1600,and if you use new version(2020.12.11) driver and new version SDK I sent to you,camera can switch HGC and LGC when gain=1600,but will have the issue of exposure changed significantly at 3.1ms and fullwell limitation issue,right?
Best Regards,
QinXiaoXu

RIGHT... but... "exposure changed significantly at 3.1mS" should be "exposure can only be changed in 1mS increments. For the sensor analysis to work well the exposure needs to change in 0.1mS increments or smaller".

I experimented at other exposures(1,2,3,4,5,6,7mS) and found that the histogram would only react for 1mS changes.

Peter
Title: Re: ONE page for drivers etc.
Post by: QinXiaoXu on December 21, 2020, 07:17:43 PM
Hi,
    Maybe for QHY294C,its minimum exposure step is 1ms,I need inquire this to Dr.Qiu.
Best Regards,
QinXiaoXu
Title: Re: ONE page for drivers etc.
Post by: QinXiaoXu on December 22, 2020, 08:00:35 PM
Hi,
    I inquired this to Dr.Qiu,he told me the minmum exposure of QHY294C is one line period,it is about tens of microseconds,and when I test,if I setup traffic to be 0,I can get change when setup 2.1 2.2 2.3 2.4 2.5ms.
Best Regards,
QinXiaoXu
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on December 22, 2020, 10:34:21 PM
QinXiaoXu,
Can you confirm that you can see the same result with the GAIN=3624 (highest possible).  Do you believe that the USB Traffic value affects this issue?

Peter
Title: Re: ONE page for drivers etc.
Post by: QHYceced on December 23, 2020, 08:18:42 AM
Regarding the drivers page etc. I mentioned earlier on this thread ... on this page:
https://www.qhyccd.com/index.php?m=content&c=index&a=show&catid=94&id=9&cut=2 (https://www.qhyccd.com/index.php?m=content&c=index&a=show&catid=94&id=9&cut=2)

I still see old driver.

....

I noticed today every time I reply in this forums, after posting it I get re-directed to a main page and not back to the same thread.

Just informing you

Mauro
Hi,
    About email unlock issue,you can contact my@qhyccd.com,and the driver download linke is here:https://www.qhyccd.com/index.php?m=content&c=index&a=show&catid=141&id=62&tdsourcetag=s_pctim_aiomsg (https://www.qhyccd.com/index.php?m=content&c=index&a=show&catid=141&id=62&tdsourcetag=s_pctim_aiomsg)
Best Regards,
QinXiaoXu


Hi
Yes, I got the links from Cloudy Nights forums and bookmarked them into a QHYCCD folder.

I also sent you email.

Thanks
M
Title: Re: ONE page for drivers etc.
Post by: QHYceced on December 23, 2020, 08:24:40 AM
QinXiaoXu,
I did some testing with https://www.qhyccd.com/file/repository/latestSoftAndDirver/Driver/QHYCamerasDriver20201127.zip

While the sensor analysis seems to work better and the video appears more stable I noticed that the .......
New 1599 Again.jpg and New 1600 again.jpg are what my master BIAS frames look like when using these new drivers. Notice that the changes in Mean and Std. Dev. values are very small.

Peter

P.S. I also noticed that the whitebalance parameters are now 16.  My original drivers were setting them to 64 and the 64 value was the correct value.  Now I find that even if I change back to the original drivers the correct values for whitebalance are 16.  This is not a big problem for me but it needs to be documented and users should be made aware of this change.

Out of curiosity, which program did you use for the Histogram?

I also see RGB well aligned!

Just learning ... I am still re-reading this thread and see below other posts now that I found quietness in our house!!!
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on December 23, 2020, 09:27:38 AM
I have written a program for LIGHT frame calibration specifically for astrophotographers that wish to learn how to use BIAS, FLATs, DARKs and DARKFLAT frames.  Right now I have a google group set-up for my users...
https://groups.google.com/g/calights

Soon I hope to have a website so that it is easier for potential users to find my app

Peter
Title: Re: ONE page for drivers etc.
Post by: QinXiaoXu on December 23, 2020, 07:38:49 PM
QinXiaoXu,
Can you confirm that you can see the same result with the GAIN=3624 (highest possible).  Do you believe that the USB Traffic value affects this issue?

Peter
    Yes,I checked gain=3624,traffic=0 just now,I can see histogram have change when setup 2.1 2.2 2.3 2.4 ~ 3.0 ms.
Best Regards,
QinXiaoXu
Title: Re: ONE page for drivers etc.
Post by: QHYceced on December 26, 2020, 08:55:26 AM
I have written a program for LIGHT frame calibration specifically for astrophotographers that wish to learn how to use BIAS, FLATs, DARKs and DARKFLAT frames.  Right now I have a google group set-up for my users...
https://groups.google.com/g/calights

Soon I hope to have a website so that it is easier for potential users to find my app

Peter


Thanks!
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on December 26, 2020, 10:15:35 AM
QinXiaoXu,
I did some testing and found that 0.1 increments in exposure times is more predictable when USB traffic =0.  This is true for all gains and for USB3 or USB2 connections.  As I increased USB Traffic I found that 0.1 increments were not always possible.  Sometimes an increment would not have an effect but the next increment would have an effect.

For using the SharpCap sensor analysis, QHY294C (non Pro version) users should set the USB Traffic to zero.

Peter
Title: Re: ONE page for drivers etc.
Post by: QHYceced on December 27, 2020, 08:12:14 AM
Just adding something else ...I understand this is a working progress ... I am still waiting to get ONE night - at least 4 clear sky hours in northern UK ... pfff

Robin [SharpCap] confirms Sensor Analysis is weird:

https://forums.sharpcap.co.uk/viewtopic.php?f=28&t=3081&sid=3989c15507c01dc06ff3710a927d7d0e&start=20
Title: Re: ONE page for drivers etc.
Post by: QinXiaoXu on December 28, 2020, 07:17:48 PM
QinXiaoXu,
I did some testing and found that 0.1 increments in exposure times is more predictable when USB traffic =0.  This is true for all gains and for USB3 or USB2 connections.  As I increased USB Traffic I found that 0.1 increments were not always possible.  Sometimes an increment would not have an effect but the next increment would have an effect.

For using the SharpCap sensor analysis, QHY294C (non Pro version) users should set the USB Traffic to zero.

Peter
    Yes,I got the same result,I think I need add this to Q&A or camera's manual to let people know it when use camera.
Best Regards,
QinXiaoXu
Title: Re: ONE page for drivers etc.
Post by: bflachsbart on December 30, 2020, 06:51:51 AM
This fullwell capacity issues causes all the pixel values to be limited to a mean value of 48,000 counts with a bell curve distribution of possible values.  When this fullwell capacity issue is happening it is impossible to achieve a pixel value close to maximum (65,534).  I also checked that the read noise for the camera is dropping when I use GAIN=1600 so I believe that the LGC/HGC logic is working correctly.

Hi Peter,

I ran into the same problem with the full well clamping when taking flat frames at 1700 gain with my QHY294C (non pro version) the other day.

I got aware of the problem when I used the flats calibration wizard of SGP and it always recommended a 5 sec (!) exposure no matter how bright my flat panel was.

So I had a closer look at this strange behaviour using the latest Sharp Cap Version 3.2.6457.0 and the driver contained in the stable all-in-one system pack (20.06.26.36).

It is clearly visible in the attached screenshots, that while the 0.5 sec exposure histogram is okay, the 2 sec exposure histogram taken with the same flat panel brightness is faulty. On a side note: The uneven channels in the okay histogram are due to the fact that the flats are taken through a Baader UHC filter.

I've tested the latest driver 2020.12.28 and this doesn't show the full well clamping. But it has another problem, because the gain settings above around 2000 don't work as expected, the camera seems to switch back to 0 gain above 2000 or so.

Another user in this thread reported, that the SharpCap sensor analysis also looks weird with this driver and I can confirm this:
With the 20.06.26.36 driver, I've never manged to succesfully finish the SharpCap sensor analysis.
With the 2020.12.28 driver, the sensor analysis succeeded but my joy was only very short. The read noise curve is increasing with a huge step about 2000 gain, as if the gain is set back to 0.
This can also be observed when looking at the histogram in SharpCap while sliding the gain control gently to the right side: The histrogram is also moving to the right side but about 2000 gain it is jumping all the way back to the very left side.

I've also tested this with the beta all-in-one system pack (20.11.29.17) but even this driver already has this probem.

So I switched back to the original stable driver 20.06.26.36 and did some further testing regarding that full-well clamping effect. I've found out that there are two ways to prevent this strange full-well clamping:

1.) setting the USB traffic all the way up, e.g. to  255
2.) leaving the USB traffic at a low value, e.g. 0 but setting the amp glow supression to off.

With either of these setting, the full-well clamping is entirely disapearing for me.

I'm not sure what to do now, I would like two have the best of both worlds/drivers.

The 20.06.26.36 driver has the full-well clamping issue, but the newer drivers 20.11.29.17 and 2020.12.28 have the gain issue above gain 2000.

It seems there isn't a driver for the QHY294C without any issues ?


best regards
Bernd
 










Title: Re: ONE page for drivers etc.
Post by: pmwolsley on December 30, 2020, 11:42:04 AM
Bernd,
Thanks for your work-around solutions for the fullwell limiting.  All of these observations help QHYCCD to understand what is going on and to address this issue.  Right now I  am happy that QHY is discussing this issue here and they are offering updates that address specific issues. I believe QHY can solve this issue but it may take a few weeks.  This fullwell limit issue most dramatically affects FLATs and you are now an expert on how this issue behaves. 

The recent drivers released by QHY have QHY294C related bugs.  The QHY5III drivers and the QHYCCD.DLL need to work together and I think this was the issue with the bizarre sensor analysis result.  As I understand it...the LGC/HGC control is thru the QHYCCD.DLL and this code became broken when the QHY5III drivers were updated.  QHY is aware of this issue and the latest versions...
qhyccd.dll 2020/12/11
QHY294C Firmware 2020/12/11
do correct the bizarre sensor analysis except for the fact that the USB Traffic needs to be set to zero so that the analysis can work correctly at the highest camera gain(3624).

The fullwell limitation still exists and I have randomly seen this issue go away but couldn't repeat it.  I will try your workarounds.  It's up to QHY to look at you workarounds and re-code their drivers/dll so that users don't stumble over these issues.

Peter
Title: Re: ONE page for drivers etc.
Post by: QinXiaoXu on December 30, 2020, 07:26:08 PM
Hi,
    I need report these to Dr.Qiu,thanks for the feedback.
Best Regards,
QinXiaoXu
Title: Re: ONE page for drivers etc.
Post by: QHYceced on January 03, 2021, 09:24:14 AM
I was just trying to do Flats in-house by using the 'pleb-way' - because of many constrictions I have to try and enjoy this hobby and my limited knowledge!

i.e. just focus on something near the house that is at least 20x FL of camera-telescope setup as suggested by other more expert amateur.

I have a nice chimney at about 25m [AR152 988 x0.8 = ~16m at least. I even tuned focuser a bit more inward remembering my older 178c/m used to focus at around 60mm [on the focuser] - so I set it there and should be very near focus + marked orientation of camera - in case I move it.

Anyway, I am not sure of two things - I have not done any Deep Sky in the last 2-3 years and forgot everything + when I do it, i am not at it for many days...

1. should I leave RGB as is - not doing any adjustment? I used a t-shirt 3-4 times folded over lens + led-light - I know it is blueish generally speaking and I see I could do Flats at ~135ms
2. then I thought lets try at 2x2 - just curious - I like experimenting and see images below 1x1 and 2x2
I could do flats with RGB spot on at ~33ms - Que?
I thought whether I leave it at 1x1 or 2x2 it should not change anything as it is NOT unlocked.

I am confused now!!

Still need some help on the RGB bit - if possible - thanks

Mauro



Title: Re: ONE page for drivers etc.
Post by: QHYceced on January 03, 2021, 09:38:04 AM
...

1. should I leave RGB as is - not doing any adjustment? I used a t-shirt 3-4 times folded over lens + led-light - I know it is blueish generally speaking and I see I could do Flats at ~135ms
2. then I thought lets try at 2x2 - just curious - I like experimenting and see images below 1x1 and 2x2
I could do flats with RGB spot on at ~33ms - Que?
I thought whether I leave it at 1x1 or 2x2 it should not change anything as it is NOT unlocked.

I am confused now!!

Still need some help on the RGB bit - if possible - thanks

Mauro


... and result is - respectively 1x1 and then 2x2:

Title: Re: ONE page for drivers etc.
Post by: QHYceced on January 03, 2021, 09:42:23 AM
I did clean lens today!

That is why it is nice -   ;)

Shall I keep it in 2x2 ?
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on January 03, 2021, 01:52:19 PM
Mauro,
My suggestions are to leave the RGB settings on the camera alone.  The default settings provided by the driver are fine.  I shoot all of my LIGHTs, FLATs, BIAS, DARKs etc at 1x1 binning.  Once you have a stacked result you can determine if binning is needed.  If you bin your flats at 2x2 then everything else has to be binned 2x2.  Don't be thinking about saving disk space.  If you are running out of disk space then consider buying an external USB drive and pull all the files you don't immediately need onto it.

Peter
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on January 13, 2021, 01:44:01 PM
Hi,
    I need report these to Dr.Qiu,thanks for the feedback.
Best Regards,
QinXiaoXu

QinXiaoXu,
Has there been any progress on the issues raised here?

Best Regards,
Peter
Title: Re: ONE page for drivers etc.
Post by: QinXiaoXu on January 13, 2021, 07:23:47 PM
Hi,
    I asked this issue to Dr.Qiu,he has not reply me,when he reply me,I will let you know.
Best Regards,
QinXiaoXu
Title: Re: ONE page for drivers etc.
Post by: QinXiaoXu on January 13, 2021, 11:37:24 PM
Hi,
    Dr.Qiu has assigned this work to my colleague,he is modifying driver and SDK now.
Best Regards,
QinXiaoXu
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on January 27, 2021, 03:00:00 PM
QinXiaoXu,
Has your colleague been able to modify the driver and SDK?

Best Regards,
Peter
Title: Re: ONE page for drivers etc.
Post by: QinXiaoXu on January 27, 2021, 07:13:57 PM
Hi,
    He is modifying it,but because of end of year,the process will be a little slow.
Best Regards,
QinXiaoXu
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on February 15, 2021, 10:58:46 AM
QinXiaoXu,
Anything new to report concerning updates to the driver and SDK for the QHY294C?

Peter
Title: Re: ONE page for drivers etc.
Post by: QHYceced on February 16, 2021, 07:27:09 AM
QinXiaoXu,
Anything new to report concerning updates to the driver and SDK for the QHY294C?

Peter

I have abandoned it for now - They are probably doing it now - I personally guess a couple of weeks !

Bad weather any way ...
Title: Re: ONE page for drivers etc.
Post by: QinXiaoXu on February 18, 2021, 07:14:08 PM
Hi,
    I'm not very known about the process,I go back here from holiday just now.Maybe you can contact him directly,his email is my@qhyccd.com.
Best Regards,
QinXiaoXu
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on February 19, 2021, 10:08:15 PM
QinXiaoXu,
No problem. I just decided to send you a reminder every two weeks.  Let us know what his plans are.

Peter
Title: Re: ONE page for drivers etc.
Post by: QiuHY on February 23, 2021, 06:23:06 AM
Hello,

       In next SDK / system release (should be about one week) We will change all of the QHY294C stuff (system driver and SDK code ) to the same with QHY294C-PRO.  The only different is it has no 47MP mode. I think this should solve something in this topic.

Best regards,
Qiu Hongyun
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on February 23, 2021, 12:34:33 PM
Qiu Hongyun,
That's wonderful news.  Thank-you for your efforts...they are greatly appreciated.

Peter
Title: Re: ONE page for drivers etc.
Post by: QHYceced on February 24, 2021, 09:31:34 AM
Hello,

      ...  The only different is it has no 47MP mode...

Best regards,
Qiu Hongyun
???

Hi
Do you mean owners of the QHY294c which have the Firmware modified as QHY294PROC will 'not' be able to use the 47M ?

I hope not, as I 'specifically' purchased this camera 'knowing' - as you stated on your website - that it can be unlocked to be able to use the 47M.

In my case as per many others I guess, the 'main' reason I purchased it [very much being debt for it] was because of the Unlock and be able to use it with short 'and' long focal length telescopes I have.

I sincerely hope you get it to work 'very' soon.

Regards
M
Title: Re: ONE page for drivers etc.
Post by: bflachsbart on February 27, 2021, 11:46:51 AM
Hi,

I've just tested the 2021.02.25 driver release which was supposed to fix all problems (?) with the 294C (non pro version) which were discussed here.

Unfortunately the gain issue described in my reply #30 on december 30th isn't fixed:
When I increase the gain setting at a given flat panel brightness the histogram is moving to the right as expected but somewhere above 2000 gain it still jumps all the way back to the left as if there is a kind of wrap around or overflow.
According to the specs the 294C should work with gain settings up to around 3500, but it seems to fall back to 0 above 2000.

I can reproduce this issue with the latest ShaprCap Version 3.2.6480.0 no matter if I connect with the native driver or with the Ascom driver. And even with EZCAP this behaviour can easily be oberved.

It's very frustrating that these problems don't get fixed.
The drop in the gain will for example prevent a succesful sensor analysis in SharpCap as another user here already described.

I'm very disapointed that there is still no driver without issues for this camera.
I've spent 1000 Euro for it and I think it's justified to expect that QHYCCD provides flawless drivers for this product?

best regards
Bernd


 



Title: Re: ONE page for drivers etc.
Post by: borgwz on February 28, 2021, 01:51:17 AM
Hi,

I've just tested the 2021.02.25 driver release which was supposed to fix all problems (?) with the 294C (non pro version) which were discussed here.

Unfortunately the gain issue described in my reply #30 on december 30th isn't fixed:
When I increase the gain setting at a given flat panel brightness the histogram is moving to the right as expected but somewhere above 2000 gain it still jumps all the way back to the left as if there is a kind of wrap around or overflow.
According to the specs the 294C should work with gain settings up to around 3500, but it seems to fall back to 0 above 2000.

I can reproduce this issue with the latest ShaprCap Version 3.2.6480.0 no matter if I connect with the native driver or with the Ascom driver. And even with EZCAP this behaviour can easily be oberved.

It's very frustrating that these problems don't get fixed.
The drop in the gain will for example prevent a succesful sensor analysis in SharpCap as another user here already described.

I'm very disapointed that there is still no driver without issues for this camera.
I've spent 1000 Euro for it and I think it's justified to expect that QHYCCD provides flawless drivers for this product?

best regards
Bernd



Bernd,

You must use the latest drivers AND the new SDK. It works fine for me at least.


Use the Allinone Driver 210226. At the bottom of the website.
https://www.qhyccd.com/html/prepub/log_en.html#!log_en.md (https://www.qhyccd.com/html/prepub/log_en.html#!log_en.md)


Marcel
Title: Re: ONE page for drivers etc.
Post by: bflachsbart on February 28, 2021, 09:28:07 AM
Hi Marcel,

thanks for the hint, I didn't notice the all-in-one package at the bottom of the page.
Since the SDK 21.02.01 at the top of the page matched the qhyccd.dll version 21.2.1 of SharpCap 3.2.6480.0  I supposed I was at the latest SDK version. But you are right, the sdk in the all-in-one package 21.02.26 is newer.

So I uninstalled everything and reinstalled from the 21.02.26 all-in-one package.

I'm happy to report that the gain issue above 2000 is now solved for me and there isn't any histogram clamping as with the old stable driver.

My apologies to QHYCCD for my unjustified criticism.

One thing is very strange though:
With the old drivers I had a maximum frame size of 4164 x 2796 pixel in SharpCap which matches the specification on the QHYCCD website for the 294C.

With the 21.02.26 driver SharCap captures at 4164 x 2822 and there is no entry for 4164 x 2796 in the dropdown.
It seems that a vertical overscan area is included?
In video mode the entire frame seems to have valid data while in still mode there is a black border at the bottom and (!) at the right side.

bst regards
Bernd
Title: Re: ONE page for drivers etc.
Post by: QinXiaoXu on February 28, 2021, 07:21:12 PM
Hello,

      ...  The only different is it has no 47MP mode...

Best regards,
Qiu Hongyun
???

Hi
Do you mean owners of the QHY294c which have the Firmware modified as QHY294PROC will 'not' be able to use the 47M ?

I hope not, as I 'specifically' purchased this camera 'knowing' - as you stated on your website - that it can be unlocked to be able to use the 47M.

In my case as per many others I guess, the 'main' reason I purchased it [very much being debt for it] was because of the Unlock and be able to use it with short 'and' long focal length telescopes I have.

I sincerely hope you get it to work 'very' soon.

Regards
M
Hi,
    Don't worry,this update will not lock 47MP mode for QHY294C,you still can update it to QHY294PROC.
Best Regards,
QinXiaoXu
Title: Re: ONE page for drivers etc.
Post by: QinXiaoXu on February 28, 2021, 07:25:03 PM
Hi Marcel,

thanks for the hint, I didn't notice the all-in-one package at the bottom of the page.
Since the SDK 21.02.01 at the top of the page matched the qhyccd.dll version 21.2.1 of SharpCap 3.2.6480.0  I supposed I was at the latest SDK version. But you are right, the sdk in the all-in-one package 21.02.26 is newer.

So I uninstalled everything and reinstalled from the 21.02.26 all-in-one package.

I'm happy to report that the gain issue above 2000 is now solved for me and there isn't any histogram clamping as with the old stable driver.

My apologies to QHYCCD for my unjustified criticism.

One thing is very strange though:
With the old drivers I had a maximum frame size of 4164 x 2796 pixel in SharpCap which matches the specification on the QHYCCD website for the 294C.

With the 21.02.26 driver SharCap captures at 4164 x 2822 and there is no entry for 4164 x 2796 in the dropdown.
It seems that a vertical overscan area is included?
In video mode the entire frame seems to have valid data while in still mode there is a black border at the bottom and (!) at the right side.

bst regards
Bernd
Hi,
    This update is update QHY294C,make it has same function with QHY294PROC's 11MP mode.So its image resolution is same with QHY294PROC.
    I think I need let my colleague know this and modify website information.
Best Regards,
QinXiaoXu
Title: Re: ONE page for drivers etc.
Post by: bflachsbart on March 01, 2021, 11:34:08 AM
Hi QinXiaoXu,
 
Quote
Don't worry,this update will not lock 47MP mode for QHY294C,you still can update it to QHY294PROC.

How can I upgrade my 294C to 294PROC ?
Is there a firmware Update and instructions how to do that ?

thanks and best regards
Bernd
 
Title: Re: ONE page for drivers etc.
Post by: QinXiaoXu on March 01, 2021, 07:17:59 PM
Hi QinXiaoXu,
 
Quote
Don't worry,this update will not lock 47MP mode for QHY294C,you still can update it to QHY294PROC.

How can I upgrade my 294C to 294PROC ?
Is there a firmware Update and instructions how to do that ?

thanks and best regards
Bernd
Hi,
    This need update FPGA,more details you can contact cha@qhyccd.com.
Best Regards,
QinXiaoXu
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on March 02, 2021, 10:46:16 AM
QinXiaoXu,
I have E-mailed Cha requesting information about the QHY294CPRO upgrade. I also asked if this information could be kept on the QHYCCD website so that all QHY294C customers can read it.

Best Regards,
Peter
Title: Re: ONE page for drivers etc.
Post by: QHYceced on March 02, 2021, 11:03:54 AM
Hi QinXiaoXu,
 
Quote
Don't worry,this update will not lock 47MP mode for QHY294C,you still can update it to QHY294PROC.

How can I upgrade my 294C to 294PROC ?
Is there a firmware Update and instructions how to do that ?

thanks and best regards
Bernd
Hi,
    This need update FPGA,more details you can contact cha@qhyccd.com.
Best Regards,
QinXiaoXu




OK

Title: Re: ONE page for drivers etc.
Post by: QHYceced on March 02, 2021, 11:41:08 AM
 ;D ;D ;D

This camera is becoming a farce now!

The main problem is in the title of this thread!!!

Installed QHYCCD_Win_AllInOne.21.02.26.18 and nothing works ...

Seriously thinking of sending it back ...

Title: Re: ONE page for drivers etc.
Post by: QHYceced on March 02, 2021, 12:10:18 PM
No used SharpCap 3.2.6480 (64 bit) and re-installed drivers from QHYCCD_Win_AllInOne.21.02.20.13 ... just the driver.

Back to normal:

1. beautiful colours on 11M and almost dark pointing it to neighbours roof
2. 47M is now very clear but MONO - I never seen Colours on 47M ... ever yet
Title: Re: ONE page for drivers etc.
Post by: QinXiaoXu on March 02, 2021, 08:04:51 PM
;D ;D ;D

This camera is becoming a farce now!

The main problem is in the title of this thread!!!

Installed QHYCCD_Win_AllInOne.21.02.26.18 and nothing works ...

Seriously thinking of sending it back ...
    Well,you mean after updating driver and SDK to newest version,your camera still have issue?
Best Regards,
QinXiaoXu
Title: Re: ONE page for drivers etc.
Post by: QHYceced on March 03, 2021, 03:21:12 AM
;D ;D ;D

This camera is becoming a farce now!

The main problem is in the title of this thread!!!

Installed QHYCCD_Win_AllInOne.21.02.26.18 and nothing works ...

Seriously thinking of sending it back ...
    Well,you mean after updating driver and SDK to newest version,your camera still have issue?
Best Regards,
QinXiaoXu


I mean after re-installing QHYCCD_Win_AllInOne.21.02.20.13 I now am back as it was, but with 47M 'seems' without any lines etc. - very clear, but still MONO and not colour.

Why do we have to endure all this pain since November 2020 to make a camera work as it was supposed to work from the beginning.

I still do not understand why the decision to put the QHY294c and PROC on sale and still did not have a fully working software and drivers.

I would understand tweaks, not continuously modifying it ... I am seriously thinking to change hobby now ... - it is just frustrating to get all these problems after one spends a lot of money expecting to solve most problems ...
Title: Re: ONE page for drivers etc.
Post by: QinXiaoXu on March 03, 2021, 11:02:07 PM
Hi,
    Sorry for this,this is because QHY294's 47MP mode used quardbayer,this is a new bayer format,it is hard to analyse data,so we developed QHY294C first when develop 11MP,and publiced the QHY294PROC when developed 47MP mode.And now we are delveloping the new function for quardbayer,this will take some time.
Best Regards,
QinXiaoXu
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on March 05, 2021, 10:06:57 AM
I finally had a chance to test the 20210226 AllInOne update and the fullwell limitation issue is fixed.  Here are my findings.

1)I was able to run the Sharpcap 32b sensor analysis and it shows that the camera performs correctly.  The LGC/HGC modes work correctly.  I had to take care when performing the sensor analysis because it would fail right after it tested the read noise characteristic.  You need to watch and when it asks to remove the lens cap you need to do this as quickly as possible otherwise the routine will time-out claiming the exposure time is too large.  I will contact Robin about this issue. The results of this test are shown in [Sharpcap32.jpg].

2)I did some BIAS frames at GAIN=1599 and GAIN=1600.  The drop in mean values and noise are in keeping with the reduction of read noise that happens at GAIN=1600.

3)The fullwell issue originally looked like [10 seconds at GN=1600.jpg] This is what the histogram did look like if an overexposed image were taken.  Now the values are clamped at 65,535 which is perfect.

Thank-you for all your efforts

Peter
Title: Re: ONE page for drivers etc.
Post by: QHYceced on March 06, 2021, 04:04:10 AM
Hi,
    Sorry for this,this is because QHY294's 47MP mode used quardbayer,this is a new bayer format,it is hard to analyse data,so we developed QHY294C first when develop 11MP,and publiced the QHY294PROC when developed 47MP mode.And now we are delveloping the new function for quardbayer,this will take some time.
Best Regards,
QinXiaoXu



I understand it takes time doing 'things', but the fact still remains, we unwillingly are the testers now ...

OK ...

Title: Re: ONE page for drivers etc. - Reinstalled 21.02.26 all-in-one package version
Post by: QHYceced on March 06, 2021, 05:12:42 AM
Hi
Finally found some free time - do not know for how long!

I did a clean-up and uninstalled everything.
Reinstalled 21.02.26 all-in-one package version.

Device manager detects it as QHY5IIIseries_IO, but Sharpcap BETA 4.0.7438.0 does not see camera - so probably ... too BETA ...!

I see it on 3.2.6480 (64bit) - I copied/pasted QHYCCD files on both versions:

1. pointed to neighbour's roof at 11M, Raw 16, 1x1, Debayer ON - I guess RGGB
2. I see RGB set to 120 - have these setting been changed and made same as ZWO ? Just curious.
3. Set Gain to 1601 and Exposure to 0.592 ms, Temp 0?C

Light is variable as Sun come and goes ...

Here is Sharpcap PrtScr
Title: Re: ONE page for drivers etc.
Post by: QHYceced on March 06, 2021, 05:17:02 AM
... and this is at 47M - exposure 1.18ms

Title: Re: ONE page for drivers etc.
Post by: QHYceced on March 06, 2021, 05:19:02 AM
Not done any Flats or Darks with this re-install.

I will wait for release of 47M RGB ... and maybe if weather and time permits it, I might even try it on a AR152/988 as 11M

Title: Re: ONE page for drivers etc.
Post by: pmwolsley on March 07, 2021, 09:11:19 AM
QHYceced,
When I did my testing of my QHY294C (no firmware update) the whitebalance values were all set to 16. I use my own custom software and it uses the default values provided in the QHY driver.  I know that within the last year I had posted to Robin at Sharpcap about his program changing the whitebalance values to 64 which he corrected.  It may be that this same problem has creeped back in because of the new camera designation.  I suspect that if you modified the whitebalance values back to 16 you will see that the spikeyness of the histogram will go away.  Also the image will be darker by the ratio of 16:120.

QHY needs to confirm that the default whitebalance values for a QHY294PROC are 16 and not 120.

Can you post an 47M image where you deselect the debayer preview.  When Sharpcap provides the debayer preview it is assuming the classic bayer pattern which is not true for the 47M image.  At present, the 47M image is a greyscale image.

Peter
Title: Re: ONE page for drivers etc.
Post by: QinXiaoXu on March 07, 2021, 07:39:09 PM
Hi,
    I asked this to my colleague,he told me now the default calue is 120.
    And for QHYceced,yes,we will developing it as soon as possible,please wait some time.
Best Regards,
QinXiaoXu
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on March 08, 2021, 10:46:22 AM
QHYceced,
Can you put up a 47M image you took during the daytime...maybe of your neighbor's roof. It will be huge so if you could put it up on dropbox or something similar and post a link to it here.

I would love to take a look at it.  Use the 120 whitebalance values as per QinXiaoXu.

Many thanks

Peter
Title: Re: ONE page for drivers etc.
Post by: QHYceced on March 11, 2021, 09:28:50 AM
QHYceced,
Can you put up a 47M image you took during the daytime...maybe of your neighbor's roof. It will be huge so if you could put it up on dropbox or something similar and post a link to it here.

I would love to take a look at it.  Use the 120 whitebalance values as per QinXiaoXu.

Many thanks

Peter

There it is - .TIFF , Debayer off, 16 RGB set - I have to say it did clear the Histograms - not talking about the spikes which went away with Debayer off, but the fact at 16 RGB it is a clear nice wave!

I have done a TIFF ~60Mb - while a FIT would have been ~91M and not visible on browsers.

That OK?

https://www.dropbox.com/s/gxv7xk2t2bep2xn/2021-03-11-1523_3-Capture_00001.tif?dl=0

Might be a bit dark.


This is a second one but RGB at 30 - I think I remember to ave read of people using it at 30 !
It seems 30 is the limit before wave start to be noisy.

https://www.dropbox.com/s/jvezoi157oa3chp/2021-03-11-1533_7-Capture_00002.tif?dl=0

Please note, although I am an Electronics Technician, I do not know much on Optics and Cameras - be gentle with me, please.
 ;)
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on March 11, 2021, 01:39:56 PM
QHYceced,
Thanks very much for your images.  I can clearly see the quad bayer pattern in the data when you zoom in on the data.  The dark spots are the clusters of red pixels. I also looked at the individual data and my bet is that the correct whitebalance value for your camera is 16 in 47M mode. Here is my reasoning.

When the QHY294PROC generates a 47M image it does this using a 12b A/D converter.  QHY scales this data up so that it fills the full 16b.  This results in the data being multiplied by 16. The A/D converter generates values that increase as 0, 1, 2, 3, 4... The corresponding values in the image file increase as 0, 16, 32, 48, 64...  This only happens when the whitebalance parameters are set to the default values.  The values in the first image 2021-03-11-1523_3-Capture_00001.tif increase by 16.  This is the image where you said the whitebalance values were set to 16.

When I look at the second image you sent the values increase by a modulated amount.  Most of the values increase by 32 but every seventh value increases by 16. This happens when the whitebalance values are increased above their default values. For this second image you said that the whitebalance value was set to 30.

If you set the whitebalance to something less than 16 you will find that the values continue to increase by 16 because this is the minimum change allowed for a 12b camera.  If you switch back to 11M mode the A/D converter is operating in 14b mode.  In 14b mode the minimum allowed change drops to 4.

So, my opinion is that the default whitebalance value for the QHY294PROC is 16 regardless of whether the camera is operating in 11M or 47M mode. 16 is also the default whitebalance value for the QHY294C.  Hopefully QHY will confirm this.

Peter
Title: Re: ONE page for drivers etc.
Post by: QinXiaoXu on March 11, 2021, 07:08:42 PM
Hi,
    Well,here is a thing I need inquire,did you update QHY294C camera's FPGA to QHY294PROC?If not,it will only have one read mode(11MP),although you can seem to read mode on SharpCap.
Best Regards,
QinXiaoXu
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on March 12, 2021, 08:44:40 AM
QinXiaoXu,
I have not had the FPGA updated for my QHY294C.  When I use Sharpcap with the latest all-in-one drivers and SDK there are two mode available in Sharpcap.  They are 11M and NOT EXIST.  I never bothered testing whether the camera would function in the NOT EXIST mode.  If you study the screen captures from QHYceced you can tell that he is able to select a 47M mode for his camera so Sharpcap believes that QHYceced's camera supports the 47M mode.

Peter
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on March 14, 2021, 12:27:00 PM
QHYceced,

I invented a very simple custom bayer scheme for the 47M images.  It certainly is not perfect but it might be a way for QHY294PROC owners to begin experimenting with 47M images. I converted your 47M TIFF images into FITS images and used Deep Sky Stacker(DSS) to display the resulting images.  I zoomed in to a very stylish bird poop in your image of the neighbor's roof.

47M Original.jpg
This is what your original image looks like.  DSS does not understand the custom bayer pattern in 47M images so you end up with a checkboard pattern on a grey image.  The darker squares of pixels are the red pixels.

47M Custom Bayer.jpg
This is what this same close-up looks like using my custom bayer algorithm. My algorithm just shuffles the pixels around to achieve a standard RGGB bayer pattern.  Every red pixel in the original is treated as a red pixel in the custom bayer image.  This is also true for the green and for the blue pixels. The image is not perfect but if several astro images were stacked, the result might have smooth transitions.

47M Legend.jpg
This is what the entire image looks like using my custom bayer algorithm.  The arrow points to the stylish bird poop.

Peter

Title: Re: ONE page for drivers etc.
Post by: QinXiaoXu on March 14, 2021, 08:52:08 PM
Hi,
    I asked balance default value to my colleague,he told me,47MP mode has not be developed,so 47MP has no defalut RGB value.And I checked the source code,the RGB default value is 16,not 120.
Best Regards,
QinXiaoXu
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on March 15, 2021, 08:33:38 AM
QHYceced,

Here is what the histogram looks like with my custom bayer algorithm.

Peter
Title: Re: ONE page for drivers etc.
Post by: QHYceced on March 21, 2021, 09:45:12 AM
Hi,
    I asked balance default value to my colleague,he told me,47MP mode has not be developed,so 47MP has no defalut RGB value.And I checked the source code,the RGB default value is 16,not 120.
Best Regards,
QinXiaoXu

OK, Sharpcap loads 294PROC at 120 ... so Sharpcap must have reverted to older wrong settings - it was fixed in a earlier stable version
Title: Re: ONE page for drivers etc.
Post by: QHYceced on March 21, 2021, 09:48:26 AM
QHYceced,

I invented a very simple custom bayer scheme for the 47M images.  ...

47M Custom Bayer.jpg
This is what this same close-up looks like using my custom bayer algorithm. My algorithm just shuffles the pixels around to achieve a standard RGGB bayer pattern.  Every red pixel in the original is treated as a red pixel in the custom bayer image.  This is also true for the green and for the blue pixels. The image is not perfect but if several astro images were stacked, the result might have smooth transitions.

47M Legend.jpg
This is what the entire image looks like using my custom bayer algorithm.  The arrow points to the stylish bird poop.

Peter

Interesting ...

I did manage to get 'some' imaging with Moon and clouds in a very difficult household - at present, I cannot get anything done! ahahhahaa

I am trying to see what the results are and I was a bit confused to see the RED very much to the left - if I am not wrong. I cannot do things properly = as mentioned I am no expert on optics or colorimetry.

I will see what I get out - mine is a 294PROC by the way ...
Title: Re: ONE page for drivers etc.
Post by: QHYceced on March 21, 2021, 09:50:47 AM
QHYceced,

Here is what the histogram looks like with my custom bayer algorithm.

Peter

I think it confirms what I thought I had seen ... I am waiting for a few clear HOURS to test a bit.
I purchased this camera as my last camera [!] prior to retirement in a few years - never say last camera in Astronomy!
 ;D

See Histograms images from SER Player of 3 Moon videos I've got done yesterday - to give an idea of what was coming out ...
Title: Re: ONE page for drivers etc.
Post by: borgwz on March 23, 2021, 01:59:29 AM
Hi,
    I asked balance default value to my colleague,he told me,47MP mode has not be developed,so 47MP has no defalut RGB value.And I checked the source code,the RGB default value is 16,not 120.
Best Regards,
QinXiaoXu

OK, Sharpcap loads 294PROC at 120 ... so Sharpcap must have reverted to older wrong settings - it was fixed in a earlier stable version

Hi,

to load the default camera settings into Sharpcap, you have to hold down the Ctrl key while connecting the camera in the camera menu. Then Sharpcap loads the standard settings of the driver with RGB 16 values.

regards
Marcel
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on March 23, 2021, 09:19:45 AM
QHYceced,
You are certainly learning lots about digital cameras.  A few concepts to understand.
1)The Whitebalance values should be set to the default (16) for all of your work.  [The only exception is when you are displaying a live video and you wish to have the colors "look nice". For this exception you will want to have the red whitebalance set to 32, the green whitebalance set to 16 and the blue whitebalance set to 24.]
2)All of the programs you are going to use to digitally develop your astrophotos will prefer that the whitebalance values be equal. This is both for the pixel values and for the noise content in the image [advanced topic for later]
3)This equal whitebalance philosophy is built into virtually all cameras and it can be a real "can of worms" if you mess with it.

The end result of all of this is that the red pixel values are virtually always less than the green pixels. It's not uncommon to see that the red pixel values are 1/2 the value of the green pixels...this is normal and all of your software understands this situation.  Your blue pixels values will be less than your green pixels and typically larger than your red pixels...this is also normal and all of your software understands this situation.

Your histograms display exactly what I just described which means everything is working just fine.  The red histogram is significantly less than the green histogram.  The blue histogram is larger than the red histogram but less than the green histogram.

These histogram relationships are typical when you are imaging a white object like the moon.  If the object is reddish then the green and blue histograms which shift to the left and may be less than the red histogram.  When the object has color then the histogram shift around so you are lucky that you did this test using the moon.

Peter
Title: Re: ONE page for drivers etc.
Post by: QHYceced on April 05, 2021, 03:46:11 AM
Hi,
    I asked balance default value to my colleague,he told me,47MP mode has not be developed,so 47MP has no defalut RGB value.And I checked the source code,the RGB default value is 16,not 120.
Best Regards,
QinXiaoXu

OK, Sharpcap loads 294PROC at 120 ... so Sharpcap must have reverted to older wrong settings - it was fixed in a earlier stable version

Hi,

to load the default camera settings into Sharpcap, you have to hold down the Ctrl key while connecting the camera in the camera menu. Then Sharpcap loads the standard settings of the driver with RGB 16 values.

regards
Marcel

Thanks, but it seems not to do it in my  case.
I wish it did.

But ... I have saved last time I used it within Sharpcap and now load settings from Capture Profiles/Load
Title: Re: ONE page for drivers etc.
Post by: QHYceced on April 05, 2021, 04:18:36 AM
QHYceced,
You are certainly learning lots about digital cameras.  A few concepts to understand.
1)The Whitebalance values should be set to the default (16) for all of your work.  [The only exception is when you are displaying a live video and you wish to have the colors "look nice". For this exception you will want to have the red whitebalance set to 32, the green whitebalance set to 16 and the blue whitebalance set to 24.]
2)All of the programs you are going to use to digitally develop your astrophotos will prefer that the whitebalance values be equal. This is both for the pixel values and for the noise content in the image [advanced topic for later]
3)This equal whitebalance philosophy is built into virtually all cameras and it can be a real "can of worms" if you mess with it.
...

Peter

Thanks Peter for taking the time to give me this clear information and yes, I just gathered info lately and slowly understood the White-balance philosophy and the 'keeping' RGB same level.
Got that now.

2 days ago I managed to get the AR152/988mm out and fit the 294PROC through a Orion 0.8x and a standard CLS-ccd 2" filter and done 3x 20 Sharpcap Stacks of 60s  - total 60 minute.

Camera Data:

Debayer Preview=On
Output Format=FITS files (*.fits)
Binning=1x1
Capture Area=4164x2822
Colour Space=RAW16
Read Mode=11M MODE
Force Still Mode=Off
Enable Live Broadcast=Off
Use DDR Buffer=On
USB Traffic=0
Offset=29 ... CORRECT ?
Amp Noise Reduction=On
Frame Rate Limit=Maximum
Gain=1601 ... CORRECT ?
Exposure=60370.2832909253
Timestamp Frames=Off
White Bal (B)=16
White Bal (G)=16
White Bal (R)=16
Contrast=0
Brightness=0
Gamma=1
Temperature=-15.1 - TIP to all of you - Use a 5A PSU for this camera, that way temperature will be super stable as PSU is only working up to 60% of its capacity - almost cold!

I also did 10x Darks and applied them and seem to have cleared image decently, I did FLATS after and badly - should have done them earlier and well then applied with darks - learned lesson, I actually forgot about it.

That is my main problem now, I seem I cannot do proper FLAT with any Cmos camera with the exception of my old DSLR, thanks to BYOS setting it automatically did very good flats!

In fact during the years I almost always got better result using DSLR than the Cmos!

I also wrapped a 70cm dew heater all around the 0.8 (from camera to focuser] + another 70cm wrapped around the AR152 lens.

In short and concise my problems still are:

FLATS = are rubbish - any practical tips? - I do have a A3 LED panel and use that now for uniformity, I also leave its white cover to smooth the light and yes I know they generally are blueish lights.
(I end up creating flat from Lights to reduce 'steaming' middle usual fog!)

I have been reading about flats, but it still is not too clear to me - I am an idiot with 125 IQ - incredible how 90 IQ I can be some time!  :P

HEATING:
Does the 294PROC need its own heater on the front - to keep CMOS glass clear?
Mine 'was' a NON-Pro version upgraded, I assume it does not have internal heater?

Here are Dew Heater wrapping and an image of the Leo Triplet - 3x 20m of 60s each = total 60m

Take into account, I did not do a extremely good focus just yet, but I managed to get an 'Excellent'  Polar Alignment and managed 60s with no guiding - although I guess 45s would have been better!

PANDA EYES:
using a refractor! Although not much of it - only on very bright stars, maybe my CLS-CCD is NOT really a CCD?

NEXT: I will get back in using PHD2 if needed.

Thanks for the help
M

PS this thread will be of good use for many at my level.



Title: Re: ONE page for drivers etc.
Post by: QHYceced on April 05, 2021, 09:57:01 AM
... and just to add to the fire ... !

I just remembered I needed to re-do Sensor Analysis as when I did ... I think I did it when it was still a QHY294c, not is a QHY294PROC.

See previous first and latest one:

Does this mean Unity Gain as changed?

I see old one as expected to 1500-1600 and new analysis to 2500.

I am confised.

Bear in mind Analysis went well straight away within 5-10 minutes - last time I got frustrated it worked on after many tries, but if I am not wrong it was to do with QHY software ...

If I can I will try either tonight or tomorrow night - it seems it clears but 'windy' ... mmm
Title: Re: ONE page for drivers etc.
Post by: pmwolsley on April 05, 2021, 03:03:56 PM
QHYceced,

Lots to reply to...

Very nice astropic.

-My stock QHY294C camera has a heater element for the camera objective glass. I have not seen any fogging. I don't think you need the heater band as shown in your picture. I have to believe that the factory QHY294CPRO also has an objective glass heater.

-Offset=29 I use an OFFSET of zero for all GAINs. I would like it if QHY allowed OFFSET to be negative. Using a positive value is OK but it takes away from dynamic range. You need to look at BIAS frames with different values for OFFSET and decide what is the smallest value to use with minimal clipping at zero. That's how I decided on an OFFSET of zero. Dark Current and Light Pollution will push up the average pixel values so clipping at zero is not a concern for me.  I have a very dark site that I image at and I always use an OFFSET of zero.

Take a look at my photos www.astrohobby.ca

GAIN=1601  This is fine. The camera actually switches to HGC mode at GAIN=1600...I've proven this. Once you get comfortable with the camera you can experiment with other gains[advanced topic].

-I don't know where you live but if the weather is cold then the cooler will be barely working. The power supply will be cold. Don't expect the same if you use the camera inside your house. At -15C it will be working hard.
More on this later...

-DARKs at the same temperature/GAIN/OFFSET/EXPOSURE as your LIGHT frames are vital for the QHY294 cameras.  Dark current is significant with this camera.

-I struggle with FLATs also. Can you put a sample FLAT on dropbox and also let me know how you took the FLAT? If you take FLATs and DARKFLATs using the same conditions then it does not matter at what GAIN or COOLING you used.

I have a B4 light panel that I just started using. To soon to tell if it is better. My light panel seems to be pure white. The histograms look like white light with no strong blue hue.

-Panda Eyes...that's the first time I heard that description. Can you get me a link to a website that has good information on panda eyes?

As for your sensor analysis images. The first one is rubbish. That must have been when the SDK and driver were messed up.

The second one is not much better. It does show the read noise dropping as the camera switched from LGC to HGC. The e/ADU, Read Noise(e), Full Well(e), Relative Gain, Rel Gain(db) values are rubbish. Only the Gain Value and the Dynamic Range (Stops) values are useful.

Also...The cooler target was set to -15 and the temp feedback was -13.6.  The cooler was operating at 100%!!! You must avoid running the cooler continuously at 100% power. It significantly decreases the operating life of the cooler. This is important to remember when you are taking DARKs inside the house. Try to put the camera in a cool environment if your are going to be taking -15C DARKs...otherwise you will shorten the life of the cooler and the camera temperature may not be constant because the cooler is running hard. You want constant temperatures for all of your imaging...including DARKs.

Peter
P.S. If you want to discuss FLATs for the QHY294C can you start another topic in a section not specific to SDK and driver issues.  A lot of what it already here is not easy for anyone else to find.


Title: Re: ONE page for drivers etc.
Post by: QHYceced on April 06, 2021, 05:59:36 AM
Peter

Very nice astropic.
Thanks

-My stock QHY294C camera has a heater element for the camera objective glass. I have not seen any fogging. I don't think you need the heater band as shown in your picture. I have to believe that the factory QHY294CPRO also has an objective glass heater.

Yes, I guess it is internal, bear in mind mine is a 294c but upgraded as 294PROC = same camera - it seems this camera has its internal own dew control...

-Offset=29 I use an OFFSET of zero for all GAINs. I would like it if QHY allowed OFFSET to be negative. Using a positive value is OK but it takes away from dynamic range. You need to look at BIAS frames with different values for OFFSET and decide what is the smallest value to use with minimal clipping at zero. That's how I decided on an OFFSET of zero. Dark Current and Light Pollution will push up the average pixel values so clipping at zero is not a concern for me.  I have a very dark site that I image at and I always use an OFFSET of zero.

I can certainly try it, I am Bortle 4.5 I believe, although since street lights became LED, it actually is better because they are lower height and pointing down and in my view I might even be 5.5 now - neighbours might be more of a problem than street lights, as their light shines on our yard and I guess there also are some reflection form the garage top fascia - brilliant white! - I do use a very large black blanket over washing line and pushed up with at line pole to about 2.5-3m - it does help. Personally initially I thught to give it 10 Offset, but I have read many using 15 up to 30, so I pushed it up, but I understand situations are different - will try 10 tonight - it seems going to be better than yesterday

Take a look at my photos www.astrohobby.ca
I had a quick look yesterday and will be back to try and learn - I feel thick on this field!

GAIN=1601  This is fine. The camera actually switches to HGC mode at GAIN=1600...I've proven this. Once you get comfortable with the camera you can experiment with other gains[advanced topic].
Yes

-I don't know where you live but if the weather is cold then the cooler will be barely working. The power supply will be cold. Don't expect the same if you use the camera inside your house. At -15C it will be working hard.
More on this later...

North East England UK - we are having another ~7 days Cold Snap N-NW

-DARKs at the same temperature/GAIN/OFFSET/EXPOSURE as your LIGHT frames are vital for the QHY294 cameras.  Dark current is significant with this camera.

-I struggle with FLATs also. Can you put a sample FLAT on dropbox and also let me know how you took the FLAT? If you take FLATs and DARKFLATs using the same conditions then it does not matter at what GAIN or COOLING you used.

I only done it once but after Lights and I am not sure of settings - I guess I will only take Darks and Flats, no other - I am trying to make my life easier ;p], I might have left it at 1601 Gain [possibly 1-2ms] and adjusted to be 'visually' dark grey, I am really not good with Flats, this time I will do it first, so I can apply it with Darks and see what happens, I guess another evening wasted testing.


I have read someone stating this:

Flats - x50 @ 4.75s target ADU of 22000 using an LED light panel and white t-shirt


I do not know how to target 22000 ADU within SharpCap, I guess they use a program that allows you to do that.

I will try to also use this, if I do not forget: https://www.sharpcap.co.uk/sharpcap/features/smart-histogram (https://www.sharpcap.co.uk/sharpcap/features/smart-histogram)


I have a B4 light panel that I just started using. To soon to tell if it is better. My light panel seems to be pure white. The histograms look like white light with no strong blue hue.

-Panda Eyes...that's the first time I heard that description. Can you get me a link to a website that has good information on panda eyes?
That is simply when you get the Blue-Violet halo around stars, a problem with non-apo and / or when the CLD-CCD filter is not good or a visual one is used... if I remember well

As for your sensor analysis images. The first one is rubbish. That must have been when the SDK and driver were messed up.
The first one is the one I did publish earlier on this sane thread and it is similar to one you published too up to 1500 Gain - they are the same then mine goes differently ... mmm

The second one is not much better. It does show the read noise dropping as the camera switched from LGC to HGC. The e/ADU, Read Noise(e), Full Well(e), Relative Gain, Rel Gain(db) values are rubbish. Only the Gain Value and the Dynamic Range (Stops) values are useful.

Also...The cooler target was set to -15 and the temp feedback was -13.6.  The cooler was operating at 100%!!!
This time  #Power was inadvertently set = Auto - I switched that off and let cooler at 151 power and it now stays at 59% maintaining -15?C
You must avoid running the cooler continuously at 100% power. It significantly decreases the operating life of the cooler. This is important to remember when you are taking DARKs inside the house. Try to put the camera in a cool environment if your are going to be taking -15C DARKs...otherwise you will shorten the life of the cooler and the camera temperature may not be constant because the cooler is running hard. You want constant temperatures for all of your imaging...including DARKs.

The power supply actually was not the same I use, although both 12v 5A, I believe this PSU is rubbish and not really 5A - should have used other one which normally does not ever reach 100%.
I have now set telescope outside - as I did play with my DIY Solar Scope a bit and now setup AR152 + 294proc with usual good PSU and set it to -15. I will re-do sensor analysis and also do Darks 30s 45s 60s - this camera I am guessing works better on 30-45s


Peter
P.S. If you want to discuss FLATs for the QHY294C can you start another topic in a section not specific to SDK and driver issues.  A lot of what it already here is not easy for anyone else to find.

You are right, I apologise ...
Title: Re: ONE page for drivers etc.
Post by: QHYceced on April 06, 2021, 06:18:05 AM
Here is the new thread:
https://www.qhyccd.com/bbs/index.php?topic=8579.0 (https://www.qhyccd.com/bbs/index.php?topic=8579.0)

QHY294c and QHY294PROC - doing FLATS - it seems I cannot do them well = HELP!
Title: Re: ONE page for drivers etc.
Post by: QHYceced on April 07, 2021, 06:24:48 AM
Hello
Last night was hell .... not talking about that now.

Anyway, I re-did Sensor Analysis today and found 'my way' of doing it properly.

I believe 'now' it is as one would expect it to be and I also barely remember last night while using SharpCap 'brain' button, it did tell me 1750 and minimum of 87s exposures and now looking at latest Analysis, I believe SharpCap is correct ... I am learning ...



Title: Re: ONE page for drivers etc.
Post by: pmwolsley on April 07, 2021, 02:51:58 PM
Looks good. QHY SDK and driver are working well.

Peter
Title: Re: ONE page for drivers etc.
Post by: QHYceced on April 08, 2021, 05:15:43 AM
Looks good. QHY SDK and driver are working well.

Peter

Yes, learning a bit, I thought it was OK ... and I just remembered, I seemed to have had problems with Sharpcap latest stable version, suddenly the other night - had problem getting signal from camera, then connected using Ezcap and it was fine. So, I guess it was a Sharpcap problem.

I then tried the Beta I had installed and updated it to latest 4.0.7596.0 (23/03/2021) ... BUT ... I installed the 32bit version, now qhy294 works without manually replacing QHYCCD.dll.
I managed to do test flats as well and the Sensor Analysis too was with the nightly - will use this one next time and if it works fine, I will not update it.

Let's see what happens next time I am outside!

I have been in Lockdown3 since after Christmas going back to work on Monday ... finally ... I need a distraction = work and my hobbies!

Mauro

Title: Re: ONE page for drivers etc.
Post by: QHYceced on April 25, 2021, 05:13:46 AM
I had at least 4 times this - with Beta or Stable SharpCap versions:

1. it shut down while it was taking dark
2. it shut down while it was taking lights - after the first hour I went to check and it shot down - restarted another 1h session
3. I then last time it shut down re-run the stable one and camera was not detected 'by SharpCap ' - although it was detected by PC
Started/restarted SharpCap - connected/disconnected each section of camera cables and then SharpCap found it, but upon selecting it, there was [in my view] no handshaking between camera and there was nothing on SharpCap screen!

4. started Beta 4.** version and it finally went back to normal!

Robin of SharpCap  says it is to do with Camera information sent or not to SharpCap and I really tend to believe him.

This also mean, QHY294c or PROC software/firmware still has problems, never mind the 47M we are still waiting for.

I was starting to have almost all working fine now and this started to bother us - wasted 1 hour the other night, that could have been taking lights!

It seems there is always a blooming problem and for me is very hard to keep doing Astro-imaging having weather unstable, little time, narrow view of the sky and all I need is software stable!

It seems impossible in 2021, not just QHY - anything really and Microsoft WIN10 has become a sewer too and I am probably going to switch to Ubuntu, when I can do full cloning of HDD and then install Ubuntu.

I am just trying to get a decent 'working' setup that I can use happily for when I retire in some years.

Is QHY software/firmware stable now? Are we going to get the 47M ? UPDATED
I saw other thread mentioning the latest QHYCCD.dll and I confirm it works with 47M only on RGB24 - if I find the time I will try it on The Moon maybe

... just telling the happenings !

😋
Title: Re: ONE page for drivers etc.
Post by: QinXiaoXu on April 25, 2021, 08:48:36 PM
Hi,
    I replied you and sent a new SDK in your another topic.
Best Regards,
QinXiaoXu