×

INDI Library v1.9.1 Released (26 Jun 2021)

Bi-monthly INDI Library v1.9.1 is released bringing a few new drivers and improvements to existing drivers.

QHY183M not detected

  • Posts: 38
  • Thank you received: 1
Hi

I've got a problem with my brand new QHY183M. It recognized by OS (Linux Mint) , but the indiserver (v1.6.3) complains that it can't find a device.
2018-02-03T17:27:02: Driver indi_qhy_ccd: read message    'No QHY cameras detected. Power on?'
[  341.097770] usb 5-1: new high-speed USB device number 3 using xhci_hcd
[  341.298318] usb 5-1: New USB device found, idVendor=1618, idProduct=c183
[  341.298323] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  341.298326] usb 5-1: Product: WestBridge 
[  341.298329] usb 5-1: Manufacturer: Cypress
[  341.298331] usb 5-1: SerialNumber: 0000000004BE
[  341.358081] usb 5-1: USB disconnect, device number 3
[  341.621277] usb 6-1: new SuperSpeed USB device number 2 using xhci_hcd
[  341.638773] usb 6-1: LPM exit latency is zeroed, disabling LPM.
[  341.639635] usb 6-1: New USB device found, idVendor=1618, idProduct=c184
[  341.639639] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  341.639642] usb 6-1: Product: Q183-Cool
[  341.639644] usb 6-1: Manufacturer: QHYCCD

any help very much appreciated

cheers
Niko
3 years 5 months ago #22916

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

Replied by Jasem Mutlaq on topic QHY183M not detected

What's the output of this?
dpkg-query -W fxload
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
3 years 5 months ago #22918

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

  • Posts: 38
  • Thank you received: 1

Replied by Niko Kivel on topic QHY183M not detected

Hi
$> dpkg-query -W fxload
fxload	1.0~201712271246~ubuntu16.04.1
3 years 5 months ago #22919

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

  • Posts: 38
  • Thank you received: 1

Replied by Niko Kivel on topic QHY183M not detected

Hi Jasem

I also bypassed the "85-qhy.rules" to prevent the firmware from been automatically uploaded by udev. I then manually loaded the firmware with `fxload` ... which seems fine to me.
$> fxload -v -t fx3 -I /lib/firmware/qhy/QHY183.img -D /dev/bus/usb/005/003
microcontroller type: fx3
single stage:  load on-chip memory
open RAM image /lib/firmware/qhy/QHY183.img
write on-chip, addr 0x00100 len 4096 (0x1000)
write on-chip, addr 0x01100 len 4096 (0x1000)
write on-chip, addr 0x02100 len  800 (0x0320)
write on-chip, addr 0x40003000 len 4096 (0x1000)
write on-chip, addr 0x40004000 len 4096 (0x1000)
write on-chip, addr 0x40005000 len 4096 (0x1000)
write on-chip, addr 0x40006000 len 4096 (0x1000)
write on-chip, addr 0x40007000 len 4096 (0x1000)
write on-chip, addr 0x40008000 len 4096 (0x1000)
write on-chip, addr 0x40009000 len 4096 (0x1000)
write on-chip, addr 0x4000a000 len 4096 (0x1000)
write on-chip, addr 0x4000b000 len 4096 (0x1000)
write on-chip, addr 0x4000c000 len 4096 (0x1000)
write on-chip, addr 0x4000d000 len 4096 (0x1000)
write on-chip, addr 0x4000e000 len 4096 (0x1000)
write on-chip, addr 0x4000f000 len 4096 (0x1000)
write on-chip, addr 0x40010000 len 4096 (0x1000)
write on-chip, addr 0x40011000 len 4096 (0x1000)
write on-chip, addr 0x40012000 len 4096 (0x1000)
write on-chip, addr 0x40013000 len 4096 (0x1000)
write on-chip, addr 0x40014000 len 4096 (0x1000)
write on-chip, addr 0x40015000 len 4096 (0x1000)
write on-chip, addr 0x40016000 len 4096 (0x1000)
write on-chip, addr 0x40017000 len 4096 (0x1000)
write on-chip, addr 0x40018000 len 4096 (0x1000)
write on-chip, addr 0x40019000 len 4096 (0x1000)
write on-chip, addr 0x4001a000 len 4096 (0x1000)
write on-chip, addr 0x4001b000 len 4096 (0x1000)
write on-chip, addr 0x4001c000 len 4096 (0x1000)
write on-chip, addr 0x4001d000 len 4096 (0x1000)
write on-chip, addr 0x4001e000 len 4096 (0x1000)
write on-chip, addr 0x4001f000 len 4096 (0x1000)
write on-chip, addr 0x40020000 len 4096 (0x1000)
write on-chip, addr 0x40021000 len 4096 (0x1000)
write on-chip, addr 0x40022000 len 4096 (0x1000)
write on-chip, addr 0x40023000 len 2028 (0x07ec)
write on-chip, addr 0x40030000 len 4096 (0x1000)
write on-chip, addr 0x40031000 len 4096 (0x1000)
write on-chip, addr 0x40032000 len   72 (0x0048)
write on-chip, addr 0x40010460 len    0 (0x0000)
... WROTE: 150356 bytes, 40 segments, avg 3758
3 years 5 months ago #22921

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

Replied by Jasem Mutlaq on topic QHY183M not detected

Ok QHY just confirmed that the QHY183M is still not supported on Linux, but they're working on adding support soon. Will let you know once an updated SDK is available.
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
3 years 5 months ago #22935

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

  • Posts: 38
  • Thank you received: 1

Replied by Niko Kivel on topic QHY183M not detected

Thanks for letting me know
3 years 5 months ago #22939

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

  • Posts: 27
  • Thank you received: 5
I was just thinking about buying the same camera. Lucky me got to search in the forum :)

Thanks for sharing your experience!

Inviato dal mio BLA-L09 utilizzando Tapatalk
3 years 4 months ago #24687

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

  • Posts: 38
  • Thank you received: 1

Replied by Niko Kivel on topic Re:QHY183M not detected

It seems as if they are working on the driver. Last news are now 2 weeks old and the report was something like "I try to do it asap", which is pretty much worthless in terms of a timeline. But, I'm not complaining, I haven't seen the sky in the last 5 month for more than 3 consecutive hours :(
3 years 3 months ago #24711

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

183 is already supported in INDI now.
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
3 years 3 months ago #24734

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

  • Posts: 38
  • Thank you received: 1

Replied by Niko Kivel on topic QHY183M not detected

Oops, didn't know that, thanks for adding it! :woohoo:
Jan promised me to keep me posted on the development.
anyway, I can't make it run :(
dmesg:
[ 2107.126221] usb 1-1.2: new high-speed USB device number 5 using ehci-pci
[ 2107.235675] usb 1-1.2: New USB device found, idVendor=1618, idProduct=c183
[ 2107.235680] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2107.235684] usb 1-1.2: Product: WestBridge 
[ 2107.235687] usb 1-1.2: Manufacturer: Cypress
[ 2107.235689] usb 1-1.2: SerialNumber: 0000000004BE
[ 2107.458147] usb 1-1.2: USB disconnect, device number 5
[ 2107.682218] usb 1-1.2: new high-speed USB device number 6 using ehci-pci
[ 2107.792222] usb 1-1.2: New USB device found, idVendor=1618, idProduct=c184
[ 2107.792227] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2107.792230] usb 1-1.2: Product: Q183-Cool
[ 2107.792233] usb 1-1.2: Manufacturer: QHYCCD
so, there is a camera detected by the OS ...

indiserver startup:
bigblue@odroid:~$ indiserver -vvv indi_qhy_ccd 
2018-04-01T18:01:54: startup: indiserver -vvv indi_qhy_ccd 
2018-04-01T18:01:54: Driver indi_qhy_ccd: pid=805 rfd=3 wfd=6 efd=7
2018-04-01T18:01:54: listening to port 7624 on fd 4
2018-04-01T18:01:54: Driver indi_qhy_ccd: sending msg copy 1 nq 1:
<getProperties version='1.7'/>
 
2018-04-01T18:01:54: Driver indi_qhy_ccd: stderr EOF
Child process 805 died
Well, that repeats itself for another 9 times, but fails

and finally qhy_ccd_test:
bigblue@odroid:~$ qhy_ccd_test 
-----------------------------------
2018-04-01 18:03:00:480: qhyccd: cons() start...
-----------------------------------
2018-04-01 18:03:00:493: qhyccd: pthread_mutexattr_init success.
2018-04-01 18:03:00:493: qhyccd: pthread_mutexattr_settype success.
2018-04-01 18:03:00:493: qhyccd: pthread_mutex_init success.
-----------------------------------
2018-04-01 18:03:00:493: qhyccd: cons end...
-----------------------------------
QHY Test CCD using SingleFrameMode, Version: 1.00
SDK resources initialized.
2018-04-01 18:03:00:494: qhyccd: ScanQHYCCD start...
2018-04-01 18:03:00:494: qhyccd: ScanQHYCCD - Total number of USB devices : 10
2018-04-01 18:03:00:494: qhyccd: ScanQHYCCD - New number of QHYCCD devices: 1
2018-04-01 18:03:00:494: qhyccd: ScanQHYCCD - Old number of QHYCCD devices: -1
2018-04-01 18:03:00:494: qhyccd: QHYCCDSeriesMatch: idx 0, pHandle 0x4da768, cydev[0].pid = c184
2018-04-01 18:03:00:494: qhyccd: QHY5IIISeriesMatch(handle: 0x4da768, mainseries: 4044) start...
2018-04-01 18:03:00:496: qhyccd: QHY5IIISeriesMatch retVal: 0, end...
2018-04-01 18:03:00:496: qhyccd: InitQHYCCDClass camtype = 0 idx = 0
2018-04-01 18:03:00:496: Unknown camera type: 0

indilib, git:
bigblue@odroid:~/indi$ git log --pretty=format:"%h - %an, %ar : %s"
1b9b311 - Jasem Mutlaq, 11 hours ago : Do not open shutter in bias frames

hardware, Odroid XU4 with Ubuntu 16.04.4 LTS,
compiled with: gcc version 7.2.0 (Ubuntu/Linaro 7.2.0-1ubuntu1~16.04)

If you guys need any more info, let me know.
Thanks again for the effort
Niko
3 years 3 months ago #24743

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

  • Posts: 9
  • Thank you received: 6

Replied by Jan on topic QHY183M not detected

Niko,
the QHY183M is not implemented yet inside the 2.0 release. The driver supports the QHY183C camera only. We are working on that, so I suppose to finish it soon. Also, there still is problem with QHY128C camera and I work to fix this too.
Please note, we are reworking qhyccd driver, so please be patient...
Thank you,
Jan
The following user(s) said Thank You: Jasem Mutlaq, Niko Kivel
3 years 3 months ago #24746

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

  • Posts: 9
  • Thank you received: 6

Replied by Jan on topic QHY183M not detected

Hi all,
based on reading of your messages, I would like to add the following:
The original qhy driver worked mostly for Windows, but there was a little support for Linux and Mac. The driver was and still is a combination of classical programming in C and basic OOP techniques in C++. This combination is very difficult to understand because you change some part of the code somewhere and this has an influence on other part(s) of the code. I will not go to the details, so what we are doing now is moving the code to follow the OOP rules.
Since version 2.0.0, there is, for example, quite new detection and support for multiple cameras. The driver should support up to 5 cameras now. This still requires a litte modification when user unplug some camera on the fly and plug another one. The driver itself utilizes asynchronous support (bulk transfer) from libusb including multithreaded support from linux, so it has to be done very carefully.
The main problem is, that I have to support all previously released driver's I/O funtions and do all changes behind that scene to be fully backware compatible. These are reasons, why it goes not so fast I would like to do... The good thing is that I have mostly all QHYCCD cameras to my stock, which helps with development very much.
Thanks for your understanding.
Jan
The following user(s) said Thank You: Ales
3 years 3 months ago #24747

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

Time to create page: 1.111 seconds