×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

Ekos/INDI and QHY 5L-II connection problem

  • Posts: 205
  • Thank you received: 19
Hi,

I'm on a Gentoo system trying to get kstars/ekos going.

I've built the code from source - kstars and indi-code from instructions I found in the forum.

I've been able to get ekos to start up connections to my telescope, canon dslr and moonlite focuser, but I've had problems with the QHY5 and the SBIG St-i. I'll ignore the ST-i for now and deal with the QHY5.

The system recognises the camera and the qhy_ccd_test passes when I run it (as my user). When I try to get ekos to connect, all I get is a red light, nothing more. I've tried to switch on the debugging but can't see any output. I notice there's an option to load a configuration file in the indi panel for the QHY, but I don't have one of these - do I need one?

How can I go about working out what is wrong? Any pointers?

P.S. I'm really looking forward to getting this working and leaving Windows behind - ekos looks fantastic!
10 years 2 months ago #595

Please Log in or Create an account to join the conversation.

I see that QHY driver is supposed to print debug messages, but I can't get any messages when I run it locally. Peter can you weigh on this?

Regarding SBIG, I also have an SBIG ST-I and it's working fine here. Did you install SBIG Library? There is also a udev rules file that needs fxload to load the firmware, you have fxload? Can you post lsusb and dmesg outputs?
10 years 2 months ago #596

Please Log in or Create an account to join the conversation.

  • Posts: 712
  • Thank you received: 174
Hi, is it really QHY5? There is a lot of variants of this camera and they are incompatible to each other and sometime to itself :-)

Jasem, QHY5 produces 8-bit FITS, is Ekos prepared for this? Peter
10 years 2 months ago #597

Please Log in or Create an account to join the conversation.

  • Posts: 205
  • Thank you received: 19
Thanks for the replies. I'll start a separate thread on the ST-i .

It's a QHY 5L-II-C specifically.

dmesg output when I plug it in:
[  212.159066] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0008
[  212.159380] hub 2-1:1.0: port 3, status 0101, change 0001, 12 Mb/s
[  212.263531] hub 2-1:1.0: debounce: port 3: total 100ms stable 100ms status 0x101
[  212.274535] hub 2-1:1.0: port 3 not reset yet, waiting 10ms
[  212.336589] usb 2-1.3: new high-speed USB device number 7 using ehci-pci
[  212.347584] hub 2-1:1.0: port 3 not reset yet, waiting 10ms
[  212.421907] usb 2-1.3: udev 7, busnum 2, minor = 134
[  212.421919] usb 2-1.3: New USB device found, idVendor=1618, idProduct=0920
[  212.421925] usb 2-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  212.422121] usb 2-1.3: usb_probe_device
[  212.422128] usb 2-1.3: configuration #1 chosen from 1 choice
[  212.422332] usb 2-1.3: adding 2-1.3:1.0 (config #1, interface 0)
[  212.671476] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0008
[  212.671791] hub 2-1:1.0: port 3, status 0100, change 0001, 12 Mb/s
[  212.671809] usb 2-1.3: USB disconnect, device number 7
[  212.671815] usb 2-1.3: unregistering device
[  212.671821] usb 2-1.3: unregistering interface 2-1.3:1.0
[  212.671944] usb 2-1.3: usb_disable_device nuking all URBs
[  212.775946] hub 2-1:1.0: debounce: port 3: total 100ms stable 100ms status 0x100
[  214.208721] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0008
[  214.209041] hub 2-1:1.0: port 3, status 0101, change 0001, 12 Mb/s
[  214.313177] hub 2-1:1.0: debounce: port 3: total 100ms stable 100ms status 0x101
[  214.324182] hub 2-1:1.0: port 3 not reset yet, waiting 10ms
[  214.386236] usb 2-1.3: new high-speed USB device number 8 using ehci-pci
[  214.397241] hub 2-1:1.0: port 3 not reset yet, waiting 10ms
[  214.472053] usb 2-1.3: default language 0x0409
[  214.472489] usb 2-1.3: udev 8, busnum 2, minor = 135
[  214.472501] usb 2-1.3: New USB device found, idVendor=1618, idProduct=0921
[  214.472506] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  214.472511] usb 2-1.3: Product: QHY5-II 12-5-1   
[  214.472515] usb 2-1.3: Manufacturer: QHC-CCD  
[  214.472725] usb 2-1.3: usb_probe_device
[  214.472731] usb 2-1.3: configuration #1 chosen from 1 choice
[  214.472839] usb 2-1.3: adding 2-1.3:1.0 (config #1, interface 0)

qhy_ccd_test output:

File Attachment:

File Name: qhy_tst.txt
File Size:12 KB
10 years 2 months ago #598
Attachments:

Please Log in or Create an account to join the conversation.


Yes Ekos can handle 8, 16, and 32 bit images. Is there a reason why I don't see any debug output from the qhy driver? is there anything to set?
10 years 2 months ago #601

Please Log in or Create an account to join the conversation.

  • Posts: 712
  • Thank you received: 174
QHY5-IIL is not supported yet. The problem is (among others) that it can't be distinguished from QHY5-II, it has the same VID/PID, but is incompatible with QHY5-II.

Actually the only working QHY camera is basic model of QHY5, there is a skeleton of the generic driver but the rest is waiting for information/hardware/resources/etc...

I will look at debug output from QHY5 driver but it is probably unrelated issue.
10 years 2 months ago #602

Please Log in or Create an account to join the conversation.

  • Posts: 205
  • Thank you received: 19
Ok thanks for that info. I'll park this for now and concentrate on the ST-i.

Are you aware of this thread on the QHY site: qhyccd.com/ccdbbs/index.php?topic=4026.0 ? Maybe it might help?
10 years 2 months ago #603

Please Log in or Create an account to join the conversation.

  • Posts: 712
  • Thank you received: 174
Yes, I know this thread, unfortunately it doesn't help at all :-(
The following user(s) said Thank You: Chris Ryan
10 years 2 months ago #605

Please Log in or Create an account to join the conversation.

  • Posts: 55
  • Thank you received: 1
Hello everybody,
I am new of INDI and Ekos and I can't wait to have it running on a Raspberry!
I have already tested all functions ok about my Canon DLRS and now it's the turn of my QHY5-II (the mono version).
I can confirm that even this version has the same behaviuor described from Lazjen but it's weird it is correctly recognize from Lin_guider.
Please let me know whether you need some help as tester for this issue and I will be happy to do it in my free time!

Thanks for all your appreciated work.

Cheers,
Giovanni.
10 years 2 months ago #631

Please Log in or Create an account to join the conversation.

  • Posts: 155
  • Thank you received: 10
Hello,

While the QHY5 INDI connection and driver were release by Geoff, the working code for the QHY5L series cameras was handled by Andrew(Galaxy Master) and Giampiero.(yumpy67). Unfortunately, there is some confusion on the licensing of the source codes as posted here: /indi-code-1427-trunk/3rdparty/indi-qhy. In that code, there is a clear proprietary copyright stating: " QHY5L-II CCD INDI Driver
*
* Copyright (c) 2013 CloudMakers, s. r. o. All Rights Reserved.
*"
Until this code is released by GPL licensing, I fear my friends can not assist with the QHY5L or other QHY camera development. I personally feel this is a mistake in understanding which QHY code sources(hex firmware) are protected and which are GPL Open Source.

I will offer this link as possible code source alternative: github.com/OpenSkyProject

Best wishes,
Dan
10 years 2 months ago #633

Please Log in or Create an account to join the conversation.

  • Posts: 712
  • Thank you received: 174
Hi Dan, the headers in source code and COPYRIGHT.txt are updated, LICENSE.txt is added, if you feel that something is not correct yet, just let me know. We have really no intention to block further QHY driver open source development in any way and I hope support for more cameras will be added soon. Peter
10 years 2 months ago #636

Please Log in or Create an account to join the conversation.

  • Posts: 155
  • Thank you received: 10
My apology Peter, I was getting the wrong code which has yet to reflect your changes. Yes, this looks fine.
Since I know the OSI code is working on my QHY9 and QHY5L-II, I beg you to incorporate it. We noticed that you did only 1x1 binning with the cameras and have not attempted temperature control yet. Is there any way we may help to merge this into your INDI routine?

Dan
10 years 2 months ago #644

Please Log in or Create an account to join the conversation.

Time to create page: 0.271 seconds