Starting tomorrow you'll get an updated QHY driver. It is built on a newer QHY SDK. Please test and report here. You can enable verbose logging, but it will not be logged to the regular INDI log file. Instead, you'll find another detailed log file under /tmp, you won't miss it.

Great news. What cameras are supported.?

ASAIK, all the cameras. No color support yet.

How can we get the new driver? . BTW, is it open-source ?

It's not built yet due to some issues, will be build in a couple of hours. The driver is open source, the SDK is closed source for now.

I updated my driver code a few days ago (driver version 1.6) and I can't seem to get my QHY5-II to stay connected for very long. Symptom is "FITS image failed to load, aborting..." and, after then disconnecting and reconnecting, "Error: Init Camera failed (-1)". Sometimes it also takes out KStars entirely, at which point journalctl shows:


journalctl also often shows:


Is there anything I can do to help debug issues? Indi server is running on Arch Linux, client on Kubuntu 15.10.

I've just updated both my client and server side with the very latest KStars/Indi/Ekos and kernel and run indiserver with just the indi_qhy_ccd driver (-vvv). Then, in Ekos I've started the focuser framing with a 10 ms exposure.

The driver works initially but, after a few frames, the client side indi_qhy_ccd crashes with a segmentation fault in libusb_get_next_timeout (libusb-1.0.so.0) and this then takes out KStars on the server side; bt in gdb doesn't show anything useful, the register dump I think shows that the default libusb context is being used:


I've attached the driver log file from /tmp in case it is of any use. The failure mode is pretty consistent so I can reproduce with any debug that might be of interest.

[EDIT]

Trying a few more times the QHY driver doesn't always segfault but it does always cause KStars to segfault. I've run KStars under Valgrind and the output, along with the particular FITS image that caused it to completely die, is attached.

[EDIT]

Noting the thread here: indilib.org/forum/ekos/1205-fits-open-er...y-not-simple-or.html, I tried setting the Indi dialog box to "Compressed" rather than "Raw" (even though I don't want compressed as a I have a fast Ethernet link from the client to the server) and the FITS format now appears to be recognised. Switch it back to "Raw" and the format is not recognised again. The driver appears to be obeying the change, in that with "Compressed" set there is a significant delay before transmission of the image and then a much shorter transmission time, so could it be that the Indi client end is somehow trying to decompress a non-compressed image?

An updated SDK shall be released in a couple of days, so we'll see.

Dear Jasem

is there any Dedicated driver for the QHYCWF2 ( OVER USB ) ??? NOW???

Is there an updated version of the driver for Ubuntu Mate arm (Raspberry)
The latest driver 201901300913 corrects (sort of) the temperature control issue on the qhy9. Thanks for that!
However the driver in the Raspberry (Ubuntu Mate arm) says it's latest version and it is 201901081657. This is older than the desktop driver and this does not work. Temperature on qhy9 cannot be controlled with this version.

Thank you!

I am testing a QHY 183c camera with indi-qhy-ccd and libqhy 4.0.13 (nightly build) on an RPI3 B+ with Ubuntu Mate 18.04.

When I start the server and connect to it, the indi_qhy_ccd driver produces an invalid pointer error for realloc() and dies.
<code>2019-02-19T21:35:22: Driver indi_qhy_ccd: restart #2
2019-02-19T21:35:22: Driver indi_qhy_ccd: pid=1116 rfd=11 wfd=19 efd=20
2019-02-19T21:35:22: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|InitQHYCCDResource|InitQHYCCDResource | START
2019-02-19T21:35:22: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|InitQHYCCDResource| InitQHYCCDResource END
2019-02-19T21:35:22: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|ScanQHYCCD|ScanQHYCCD
2019-02-19T21:35:22: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|ScanQHYCCD| SCAN start
2019-02-19T21:35:22: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|DeviceIsQHYCCD|vid = 1618 pid = c184
2019-02-19T21:35:22: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|QHY5IIISeriesMatch| QHY5IIISeriesMatch | mainseries = 4044
2019-02-19T21:35:22: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|QHY5IIISeriesMatch| QHY5IIISeriesMatch | color = 1
2019-02-19T21:35:22: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|InitQHYCCDClass|InitQHYCCDClass(camtype,index): 4045 0
2019-02-19T21:35:22: Driver indi_qhy_ccd: QHYCCD|QHY5III183BASE.CPP|QHY5III183BASE|QHY5III183BASE
2019-02-19T21:35:22: Driver indi_qhy_ccd: QHYCCD|QHY5III183BASE.CPP|ResetParameters| START
2019-02-19T21:35:22: Driver indi_qhy_ccd: QHYCCD|QHY5III183BASE.CPP|ResetParameters| END
2019-02-19T21:35:22: Driver indi_qhy_ccd: QHYCCD|QHYCAM.CPP|vendRXD|vendRXD
2019-02-19T21:35:22: Driver indi_qhy_ccd: QHYCCD|QHYBASE.CPP|GetFWVersion|GetFWVersion
2019-02-19T21:35:22: Driver indi_qhy_ccd: QHYCCDRD|QHYCCD.CPP|InitQHYCCDClass|nSize ccdimagew ccdimageh 5544 3684
2019-02-19T21:35:22: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|InitQHYCCDClass|imagequeuelength 0x5178580 framelength 0x5178580
2019-02-19T21:35:22: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|ScanQHYCCD| Scan init the imagequeue,nSize=85427584
2019-02-19T21:35:22: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|GetIdFromCam|GetIdFromCam
2019-02-19T21:35:22: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|ScanQHYCCD|ScanQHYCCD numdev=1
2019-02-19T21:35:22: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|ScanQHYCCD| Scan finished. Return nid=1
2019-02-19T21:35:22: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|GetQHYCCDId|GetQHYCCDId
2019-02-19T21:35:22: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|GetQHYCCDId| GetQHYCCDId | START
2019-02-19T21:35:22: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|GetQHYCCDId|QHYCCD GetQHYCCDId | index=0 id=QHY183C-61ea5e4a9249e26a
2019-02-19T21:35:22: Driver indi_qhy_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2019-02-19T21:35:22: Driver indi_qhy_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2019-02-19T21:35:22: Driver indi_qhy_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD
2019-02-19T21:35:22: Driver indi_qhy_ccd: snooping on Focuser Simulator.ABS_ROTATOR_ANGLE
2019-02-19T21:35:22: Driver indi_qhy_ccd: snooping on CCD Simulator.FILTER_SLOT
2019-02-19T21:35:22: Driver indi_qhy_ccd: snooping on CCD Simulator.FILTER_NAME
2019-02-19T21:35:22: Driver indi_qhy_ccd: snooping on SQM.SKY_QUALITY
2019-02-19T21:35:22: Driver indi_qhy_ccd: snooping on SynScan.EQUATORIAL_EOD_COORD
2019-02-19T21:35:22: Driver indi_qhy_ccd: snooping on SynScan.TELESCOPE_INFO
2019-02-19T21:35:22: Driver indi_qhy_ccd: snooping on SynScan.GEOGRAPHIC_COORD
2019-02-19T21:35:22: Driver indi_qhy_ccd: snooping on QHY CCD QHY183C-61ea5e4.FILTER_SLOT
2019-02-19T21:35:22: Driver indi_qhy_ccd: snooping on QHY CCD QHY183C-61ea5e4.FILTER_NAME
2019-02-19T21:36:00: Driver indi_qhy_ccd: realloc(): invalid pointer
2019-02-19T21:36:00: Driver indi_qhy_ccd: stderr EOF
Child process 1116 died
</code>

However, I've also tested this nightly build an an x86_64 machine, where I was able to connect and take pictures with ekos.

That is somewhat interesting, since with the stable 4.0.1 release I was unable to take pictures at all due to a hanging in the download process. Neither ARM nor x86_64 worked for me. The log file was filled with vendRXD messages after the exposure was done. I hope to see this fixed in an upcoming release.

Thanks for all your priceless time in making INDI such a powerful tool for us