Here's the procedure I've had to use in Windows 10 and SGP. It allows me to control temperature (and see both temp and power levels) on a QHY247C. If I don;t follow this sequence, I basically have no control over or idea of what the cameras is doing for cooling.

- Power OFF everything, including the PC
- Power ON the QHY 247C
- Power ON the USB3 Hub
- Power ON PC
- Launch SGP and connect camera

I wonder if this same procedure might help with INDI. I had to switch over to Windows because of problems with QHY's Linux drivers so I can't test this procedure myself with INDI at the moment.

I don't believe the issue lies within INDI. EKOS/INDI should enable/disable cooling, set the target temperature, and the QHY Linux driver/camera firmware/TEC controller should look after the rest and INDI should be able to poll the camera for the CCD chip temp. It appears that none of this is working.

When I run this under Windows using Nebulosity 4.x, it works fine. I'm assuming the camera firmware is the same (it may not be as I can't verify what, if anything, the Windows driver loads into the camera), and the TEC controller is the same. I think everything points to the QHY Linux driver.

But then, I might be entirely wrong too ...

jmh

I tested the QHY5M with the new SDK and had two issues:

- Activating live video does open a window but nothing can be seen in it. The Live Video icon turns green as it should be the case. After closing the live video (the icon turns red) the QHY5M is "blocked" and no pictures can be taken. Trying to do so results in "QHY CCD QHY5-M- : "[ERROR] GetQHYCCDSingleFrame error (-1)"
A logfile is attached.

- Taking a 3s picture takes 6s plus data transfer. Taking a 5s picture takes 10s plus data transfer and so on. I believe a first attempt fails and a second attempt is successful, that's why it takes 2x the exposure time to take the picture.

[2018-12-05T18:13:18.647 CET DEBG ][ org.kde.kstars.indi] - QHY CCD QHY5-M- : "[DEBUG] Taking a 3.00000 seconds frame... "
[2018-12-05T18:13:21.644 CET DEBG ][ org.kde.kstars.indi] - QHY CCD QHY5-M- : "[DEBUG] GetQHYCCDSingleFrame Blocking read call. "
[2018-12-05T18:13:21.644 CET DEBG ][ org.kde.kstars.indi] - QHY CCD QHY5-M- : "[DEBUG] QHYCCD | GetSingleFrame: badframenum 0 "
[2018-12-05T18:13:21.644 CET DEBG ][ org.kde.kstars.indi] - QHY CCD QHY5-M- : "[DEBUG] QHYCCD | qhyccd.cpp | GetQHYCCDSingleFrame294 1| readnum = 0 badframenum = 0 flagquit = 0 "
[2018-12-05T18:13:21.644 CET DEBG ][ org.kde.kstars.indi] - QHY CCD QHY5-M- : "[DEBUG] QHYCCD | qhyccd.cpp | GetQHYCCDSingleFrame294 1| ret = -1 readnum = 0 badframenum = 0 flagquit = 0 "
[2018-12-05T18:13:21.711 CET DEBG ][ org.kde.kstars.indi] - QHY CCD QHY5-M- : "[DEBUG] readUSB2B p_size=1600200 p_num=1 "
[2018-12-05T18:13:21.713 CET DEBG ][ org.kde.kstars.indi] - QHY CCD QHY5-M- : "[DEBUG] i=0 "
[2018-12-05T18:13:24.825 CET DEBG ][ org.kde.kstars.indi] - QHY CCD QHY5-M- : "[DEBUG] QHYCCD | qhyccd.cpp | GetQHYCCDSingleFrame294 | ret = 0 readnum = 0 badframenum = 0 flagquit = 0 "
[2018-12-05T18:13:24.827 CET DEBG ][ org.kde.kstars.indi] - QHY CCD QHY5-M- : "[DEBUG] qhyccd | testsingleframe imgdata=0x7effc0f19b80 "
[2018-12-05T18:13:24.827 CET DEBG ][ org.kde.kstars.indi] - QHY CCD QHY5-M- : "[DEBUG] QHYCCD | GetSingleFrame: badframenum readnum 0 ret 0 "
[2018-12-05T18:13:24.827 CET DEBG ][ org.kde.kstars.indi] - QHY CCD QHY5-M- : ""
[2018-12-05T18:13:24.827 CET DEBG ][ org.kde.kstars.indi] - QHY CCD QHY5-M- : "[DEBUG] QHYCCD | qhyccd.cpp | GetQHYCCDSingleFrame294 | readnum = 1 badframenum = 0 flagquit = 0 "
[2018-12-05T18:13:24.827 CET DEBG ][ org.kde.kstars.indi] - QHY CCD QHY5-M- : "[DEBUG] QHYCCD | QHYCCD.CPP GetQHYCCDSingleFrame | ret w h bpp channels 0 1280 1024 8 1 "
[2018-12-05T18:13:24.828 CET DEBG ][ org.kde.kstars.indi] - QHY CCD QHY5-M- : "[DEBUG] GetQHYCCDSingleFrame Blocking read call complete. "
[2018-12-05T18:13:24.828 CET DEBG ][ org.kde.kstars.indi] - QHY CCD QHY5-M- : "[DEBUG] Download complete. "

I hope this helps solve the problem. Full log file is attached.

Hello Herrhausen,

If you could please, post your QHY CCD QHY5-M-_config.xml and the dmesg log from host 192.168.2.40. I'll try to see if I can reproduce these issues over the next few days.

-Chris

Hi Chris, many thanks for looking into it!

This is the config.xml. I have to re-produce the dmesg output. Is there anything you're looking for in particular?

Here is the dmesg output:

[ 1158.670687] usb 1-6: new high-speed USB device number 5 using ehci-pci
[ 1158.827130] usb 1-6: New USB device found, idVendor=1781, idProduct=0c7c
[ 1158.827137] usb 1-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1158.855543] usb 1-6: USB disconnect, device number 5
[ 1160.634990] usb 1-6: new high-speed USB device number 6 using ehci-pci
[ 1160.791399] usb 1-6: config 1 interface 0 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64
[ 1160.791767] usb 1-6: New USB device found, idVendor=16c0, idProduct=296d
[ 1160.791772] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1160.791776] usb 1-6: Product: QHY5-CMOS
[ 1160.791780] usb 1-6: Manufacturer: QHY_CAMS

Just want to compare it against mine and try with both.

-Chris

Before I borrow my friend's QHY8, I'd like to know if any changes have been made to this camera driver at all. We tried a few months back, but we had several difficulties, with the firmware first, which wouldn't work with the camera at all and had to download a different one, and we were then unable to stop a capture without locking the camera up.
If anyone thinks it would be a good thing to try, I can get the camera and make a few tests.
Thanks for any info!

I noticed that version 4.0.11 of the QHY driver was released. I can't find any documentation indicating what was changed, but my old QHY8 now works for captures greater than 86.4 seconds. Note I used different firmware than what comes with the driver - I attached a version to a message earlier in this thread.

You'll have to copy it over the default firmware that is installed with the driver. Attach the camera to your computer. The device should be listed as 1618:6001 when you run lsusb.

Start indiserver, kstars with the appropriate configuration and you should be able to use the camera.

Regards,

jmh

Where did you download it from?

The attachment is missing from that message. Can you repost that firmware please?

Firmware attached. You need to copy it to QHY8.HEX in the firmware directory - this forum only allows files with specific extensions. I originally downloaded this from the old QHY forums.

Regards,

jmh