Hi!

My QHY5LII-M works fine without other USB devices connected to KStars. As soon as I connect other USB devices (Moonlite focuser or/and EQMod with ftdi to UART converter) to KStars the camera stop working. dmesg gives:

System is Ubuntu 14.10 i386, Dell Latitude D610, KStars version 2.3.0, INDI Library: 1.1.0 Code $Rev: 2039 $. Protocol 1.7.

After some minor changes to indy-qhy I was able to build it against the original QHYCCD_Linux library. Now the camera works without any USB issues.

Can I get the sources of your version of qhyccd? That would make debugging a lot easier.

Hi!

I finally got around to try the new QHY driver with my Qhy2Pro and I does not play ball. Here is some info:

INDI Library: 1.1.0
Code $Rev: 2039 $. Protocol 1.7.
Linux observatory 3.18.7-v7+ #755 SMP PREEMPT Thu Feb 12 17:20:48 GMT 2015 armv7l GNU/Linux

[ 6.719291] usb 1-1.2: new high-speed USB device number 5 using dwc_otg
[ 6.829551] usb 1-1.2: config 1 interface 0 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64
[ 6.842503] usb 1-1.2: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64
[ 6.856283] usb 1-1.2: New USB device found, idVendor=16c0, idProduct=2971
[ 6.856296] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6.856305] usb 1-1.2: Product: QHY-2PRO
[ 6.856315] usb 1-1.2: Manufacturer: QHY-CCD

pi@observatory ~ $ indiserver -v indi_qhy_ccd
2015-04-12T07:44:31: startup: indiserver -v indi_qhy_ccd
2015-04-12T07:44:31: Driver indi_qhy_ccd: pid=6018 rfd=3 wfd=6 efd=7
2015-04-12T07:44:31: listening to port 7624 on fd 4
2015-04-12T07:44:31: Driver indi_qhy_ccd: Open QHYCCD error

Any idea how to debug this?

Best Regards,
Søren

QHY is updating their armv7l driver, so please wait a couple of days until they submit one.

Testing the QHY5LII-M on a more powerful System with latest indi, qhyccd, and Kstars versions installed. It runs without the USB crash. But as soon as I connect other USB devices to Kstars, indi_qhy_ccd produces about 60 to 70 % of CPU load. USB devices connected to the computer but not to KStars doesn't interfere with indi_qhy_ccd. With connecting the QHY5LII-M to a separate USB host port all works fine with 8 to 20 % CPU load.

Testing System:
CPU: Intel(R) Xeon(R) CPU E3-1230 V2 @ 3.30GHz
OS: Kubuntu 15.04 amd64

Hi!
I found the Problem It's the missing USB Traffic parameter. qhy_ccd.h has:
but it's not fully implemented in qhy_ccd.cpp yet. I've tested with Lin-guider and have the same USB problems until I set the traffic value to 79.

Best Regards,
Daniel

Daniel, you're using the old driver which is not supported now.

No, I switched back to the latest svn (Revision: 2211) drivers. Because the old driver produces massive image errors with vertical bars. Locks like the Chip was not reading out evenly with a lot jitter. To make it clear:

old driver: very low cpu usage 1 to 2% but with image errors
new driver: very high cpu usage 20 to 50 % without any image errors
LinGuider: very low cpu usage 0.5 to 1.5 % without any image errors

With "old driver" I means the old "libqhy" not the even older "indi-qhy-old" driver.

BTW: Neither indi-qhy nor libqhy are thread-safe. No locking mechanism to prevent one client to change the cameras data structure while another client grabs an image.

I implemented USB Traffic in the new driver, not sure if it works with libqhy yet, please test.

Jasem, thank you very much for your quick reply. Unfortunately libqhy seems to completely ignores the USB traffic settings.
Also the current libqhy disables and ignores the USB Speed settings.

I'll ask Zhirong Li to change this.

PS: Thanks for the great work on libindi, KStars, and Ekos