×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

QHY183M not detected

  • 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
5 years 11 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
5 years 11 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
5 years 11 months ago #24747

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 guys

I received word from Jan that SDK version 2.0.5 supports the QHY183M. I downloaded the SDK and was able to compile the testapp. It detects the camera fine and isn't complaining at all.
All tests were on a linux PC, there is no ARM SDK to download so far.

best
Niko
5 years 9 months ago #26265

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

Replied by Jasem Mutlaq on topic QHY183M not detected

INDI PPA Nightly should have the build later tonight. I'll work on it now.
The following user(s) said Thank You: Niko Kivel
5 years 9 months ago #26267

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

Hey Jasem

SDK 2.0.6 is out.
If you tell me how I can compile the stuff myself, I stop asking you to do it for me :)

The QHY183M has a bug in 2.0.5 that limits the exposure to 1 s, anything higher is just sending a flat image filled with identical numbers. I hope this is the bugfix that addresses this issue.

best
Niko
5 years 9 months ago #26367

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

Replied by Jasem Mutlaq on topic QHY183M not detected

Should be in the INDI PPA Nightly build later today.
The following user(s) said Thank You: Niko Kivel
5 years 9 months ago #26369

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

me again,

SDK 2.0.7 is out, supposedly with the greater than one-second exposure fix.

best
Niko
5 years 9 months ago #26872

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

Replied by Jasem Mutlaq on topic QHY183M not detected

Thanks, I'll release an update soon.

EDIT: Should be in PPA nightly later tonight.
The following user(s) said Thank You: Niko Kivel
Last edit: 5 years 8 months ago by Jasem Mutlaq.
5 years 9 months ago #26886

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

Many Thanks!

Silly question maybe, but is there a way to set Gain and Offset from the 'CCD' tab?

best
Niko
5 years 8 months ago #27041

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

  • Posts: 454
  • Thank you received: 51

Replied by Patrick on topic QHY183M not detected

Hello,
I decided today to substitute my QHY183M to my Nikon 5300 with which I had lot of troubles yesterday (I will explain it in another post).
I have used the QHY183M successfully on May as I was on linux Mint 18.3. I switched to linux Mint 20 (Ulyana) on my notepad on July.

www.flickr.com/photos/106827807@N06/4994...n/dateposted-public/

But todaythe cam is no more detected.
I don't know if it comes from the Cypress WestBridge driver of linux or from QHY sdk or anything else. If somebody have any idea.
I am a bit desperate with none of my imagers working good.

Here are the results of tries to detect the camera:

** lsusb ***
Bus 002 Device 003: ID 0a5c:5801 Broadcom Corp. BCM5880 Secure Applications Processor with fingerprint swipe sensor
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0c45:649d Microdia
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 046d:c404 Logitech, Inc. TrackMan Wheel
Bus 003 Device 004: ID 413c:81a3 Dell Computer Corp. Dell Wireless 5570 HSPA+ (42Mbps) Mobile Broadband Card
<strong>Bus 003 Device 010: ID 1618:c183 Cypress WestBridge</strong>
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

** indiserver **

indiserver -vvv indi_qhy_ccd
2020-09-03T06:36:29: startup: indiserver -vvv indi_qhy_ccd
2020-09-03T06:36:29: Driver indi_qhy_ccd: pid=6870 rfd=3 wfd=6 efd=7
2020-09-03T06:36:29: listening to port 7624 on fd 4
2020-09-03T06:36:29: Driver indi_qhy_ccd: sending msg copy 1 nq 1:
<getProperties version='1.7'/>

2020-09-03T06:36:29: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|InitQHYCCDResource()|START
2020-09-03T06:36:29: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|InitQHYCCDResource|auto_detect_camera:false,call InitQHYCCDResourceInside
2020-09-03T06:36:29: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|START
2020-09-03T06:36:29: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|PCIE clear info structure 0
2020-09-03T06:36:29: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|PCIE clear info structure 1
2020-09-03T06:36:29: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|PCIE clear info structure 2
2020-09-03T06:36:29: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|PCIE clear info structure 3
2020-09-03T06:36:29: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|PCIE clear info structure 4
2020-09-03T06:36:29: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|PCIE call fpga_list
2020-09-03T06:36:29: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|numdev set to 0
2020-09-03T06:36:29: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|END
2020-09-03T06:36:29: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|InitQHYCCDResource()|END
2020-09-03T06:36:29: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|ScanQHYCCD|START
2020-09-03T06:36:29: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|ScanQHYCCD|Call ScanQHYCCDInside
2020-09-03T06:36:29: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|ScanQHYCCDInside|START|numdev set to 0
2020-09-03T06:36:29: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|ScanQHYCCD|scan pcie camera numdev = 0
2020-09-03T06:36:29: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|ScanQHYCCDInside|ScanQHYCCD numdev=0
2020-09-03T06:36:29: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|ScanQHYCCDInside|END|Return nid=0
2020-09-03T06:36:29: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|ScanQHYCCD|END|return numdev 0
2020-09-03T06:36:29: Driver indi_qhy_ccd: read message 'No QHY cameras detected. Power on?'

** qhy_ccd_test **

QHY Test CCD using SingleFrameMode, Version: 1.00
QHYCCD|QHYCCD.CPP|InitQHYCCDResource()|START
QHYCCD|QHYCCD.CPP|InitQHYCCDResource|auto_detect_camera:false,call InitQHYCCDResourceInside
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|START
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|PCIE clear info structure 0
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|PCIE clear info structure 1
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|PCIE clear info structure 2
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|PCIE clear info structure 3
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|PCIE clear info structure 4
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|PCIE call fpga_list
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|numdev set to 0
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|END
QHYCCD|QHYCCD.CPP|InitQHYCCDResource()|END
SDK resources initialized.
QHYCCD|QHYCCD.CPP|ScanQHYCCD|START
QHYCCD|QHYCCD.CPP|ScanQHYCCD|Call ScanQHYCCDInside
QHYCCD|QHYCCD.CPP|ScanQHYCCDInside|START|numdev set to 0
QHYCCD|QHYCCD.CPP|ScanQHYCCD|scan pcie camera numdev = 0
QHYCCD|QHYCCD.CPP|ScanQHYCCDInside|ScanQHYCCD numdev=0
QHYCCD|QHYCCD.CPP|ScanQHYCCDInside|END|Return nid=0
QHYCCD|QHYCCD.CPP|ScanQHYCCD|END|return numdev 0
No QHYCCD camera found, please check USB or power.
Last edit: 3 years 6 months ago by Patrick.
3 years 6 months ago #59304

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,
I work for QHYCCD company and also develop Java software for them and TSX pluging. Yesterday, I have noticed the same problem you have explained here after uploaded the latest version from the QHYCCD SVN repository, so all my applications stopped working. So, the current version of the driver returns zero detected cameras even if some are visible on the bus using lsusb command.
I have already reported this bug to quy who is developing their driver. He told me, he had several times changed scan usb function so, he is looking on this problem to fix it asap. Sorry for that problem, maybe you could download older driver.
Than you,
Jan
The following user(s) said Thank You: Jasem Mutlaq, Jack
3 years 6 months ago #59305

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

Time to create page: 1.433 seconds