Herrhausen wrote: 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?
Just want to compare it against mine and try with both.
Herrhausen wrote: 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.
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.
Try version indi-qhy-bleeding-1.7.5-28.1. (Issue #765, Pull Request #766)
Any one else had a chance to try KStars/Ekos with the new Fedora 29 release? I upgraded shortly after it was released and got a clear night this past Saturday. Well, I didn't get far -- Could not get guiding to calibrate.
Now, I had been using PHD2 due to the QHY5 loop/stop driver hang in Ekos. The problem manifests itself as a time out largely during RA reverse. Many attempts to diagnose the issue with PHD2, I tried Ekos/Internal with the QHY5 driver -- same thing.
So, I turned to the simulators. I did not expect it, but I can reproduce this issue using nothing but the simulators.
Here is my latest attempt with the simulators (Guider: CCD Simulator Guider, Via: CCD Simulator):
2018-11-05T14:23:38 GUIDE_RA: Scope cannot reach the start point after 35 iterations. Possible mount or backlash problems...
2018-11-05T14:21:33 RA drifting reverse...
2018-11-05T14:21:16 RA drifting forward...
2018-11-05T14:21:16 Calibration started.
2018-11-05T14:21:16 Auto star selected.
I would be real curious to know if any others out there can reproduce this with other Fedora 29 installs.
Sadly, the loop/stop driver crash still present at least in Fedora 29.
[ 96.123571] usb 1-1: new high-speed USB device number 6 using xhci_hcd [ 96.249902] usb 1-1: New USB device found, idVendor=1856, idProduct=0011, bcdDevice= 0.00 [ 96.249912] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 96.304221] usb 1-1: USB disconnect, device number 6 [ 98.044484] usb 1-1: new high-speed USB device number 7 using xhci_hcd [ 98.171024] usb 1-1: config 1 interface 0 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 98.171317] usb 1-1: New USB device found, idVendor=16c0, idProduct=296d, bcdDevice= 0.00 [ 98.171323] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 98.171328] usb 1-1: Product: QHY5-CMOS [ 98.171333] usb 1-1: Manufacturer: QHY_CAMS [ 152.110271] show_signal_msg: 18 callbacks suppressed [ 152.110276] indi_qhy_ccd: segfault at 2d0 ip 00007f5c5a781950 sp 00007fffc9cdf620 error 4 in libpthread-2.28.so[7f5c5a77e000+f000] [ 152.110294] Code: 48 89 7c 24 f8 64 48 8b 04 25 10 00 00 00 f0 48 0f b1 54 24 f8 c3 0f 1f 40 00 f3 0f 1e fa 41 56 41 55 41 54 55 53 48 83 ec 40 <44> 8b 87 d0 02 00 00 64 48 8b 04 25 28 00 00 00 48 89 44 24 38 31