×

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

Bi-monthly release with minor bug fixes and improvements

QHY5 INDI driver

  • Posts: 712
  • Thank you received: 174

Replied by Peter Polakovic on topic QHY5 INDI driver

This question was asked many times on qhyccd.com before, life is too short and hard enough to do it again. It is much easier to add PID to the driver :)
10 years 5 days ago #852

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

  • Posts: 155
  • Thank you received: 10

Replied by Dan Holler on topic QHY5 INDI driver

Hello Peter,

I hear you loud and clear on this. I have just asked for some help on the QHYCCD forum and I believe that Dr. Qiu will respond to my request that QHY review the udev rules and publish (or help me publish) a single udev rules with all the camera VID:PIDs which should exist.

The problem with the QHY5 camera is, the camera can be inadvertently reprogrammed with random addresses. There is a posting on the QHYCCD forum addressing a physical fix for this problem. However, it does involve opening the camera and cutting a trace on the camera board.

I am also trying to get the SDK officially updated. There are several issues with the code which presently being distributed.

Best wishes,
Dan
10 years 4 days ago #853

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

  • Posts: 3
  • Thank you received: 0

Replied by Ronnie on topic QHY5 INDI driver

How do I get this latest fix to my Raspberry PI?
10 years 4 days ago #854

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

  • Posts: 155
  • Thank you received: 10

Replied by Dan Holler on topic QHY5 INDI driver

I am not certain I know if the Raspberry PI fix question pertains to the fouled QHY5 address, but the answer to the QHY5 address fix is found here:

qhyccd.com/ccdbbs/index.php?PHPSESSID=6f...8f12f7f&topic=2702.0

There are 3 file attachments on that thread attached to a posting by Dr. Qiu. If carefully followed, a QHY5 camera should be on a standard VID:PID as assigned. After the pc board is properly jumpered, the problem should not repeat.

Best wishes,
Dan
10 years 4 days ago #856

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

  • Posts: 112
  • Thank you received: 12

Replied by Sébastien on topic QHY5 INDI driver

Hello,

I'm agree with Peter that life is too short. It's less dangerous for my camera adding the vid/pid of the indi driver than reprogramming the eeprom and open my QHY5 to fix the PCB. I'm interisting in changing my vid/pid but I don't want to install a Windows OS in order to fix manufacturer's bug. If you have a fix running under Linux, I'm listening to you.

My QHY5 is a french camera sold by m42optic.fr.

Sébastien.
Linux Mint 19 Cinnamon using PPA for latest KStars-bleeding and INDI
Raspberry Pi 3 B+ with StellarMate
Atik 314E - ASI120M - CG5 with Celestron C9.25
10 years 4 days ago #858

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

  • Posts: 712
  • Thank you received: 174

Replied by Peter Polakovic on topic QHY5 INDI driver


Hi Ronnie, what fix do you mean? To support PID 0818 by QHY5 driver you need to build it from source, but unless you have the same faulty camera as Sebastien it has no sense for you. Otherwise you can use the following procedure: 14-raspberry-pi.html

Peter
10 years 4 days ago #859

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

Replied by Jasem Mutlaq on topic QHY5 INDI driver

I updated the Raspberry PI packages to include the latest QHY changes. Please download and re-install.
10 years 3 days ago #860

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

  • Posts: 155
  • Thank you received: 10

Replied by Dan Holler on topic QHY5 INDI driver

I would point out that if a camera has a changed VID:PID, it is not possible to know if other functions have been altered. Anytime a camera is showing a defective condition, the manufacturer or distributor should be contacted. That said, I realize that a camera might not be under warranty and that costs might prohibit this action.

The QHY5 uses an Aptina ccd. If Aptina offers a Linux version of the flash software for their ccd, you may be able to use it to repair your camera. Ths discussion is not for this forum and I would suggest you contact QHY on the QHYCCD forum.

Best wishes,
Dan
10 years 3 days ago #861

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

  • Posts: 112
  • Thank you received: 12

Replied by Sébastien on topic QHY5 INDI driver

Hello,

Just because I like to find answer, I had to ckeck that my camera works well like manufactuers built it. On the qhyccd website, I found the QHY5 latest driver, download it and install it on virtual machine. Here is what I found in the qhy5.inf file :



[qhyccd.NTamd64]
"QHY5 Driver"=USB_Install,USB\VID_16C0&PID_0818
"QHY5 Driver"=USB_Install,USB\VID_16C0&PID_081A
"QHY5 Driver"=USB_Install,USB\VID_16C0&PID_296E
"MagZero5 Driver"=USB_Install,USB\VID_16C0&PID_2968
"QHY5 Driver"=USB_Install,USB\VID_16C0&PID_296A
"QHY5 Driver"=USB_Install,USB\VID_1781&PID_0C7C
"QHY5 Driver"=USB_Install,USB\VID_1618&PID_0901
"QHY5 Driver"=USB_Install,USB\VID_16C0&PID_296C
"QHY5 Driver"=USB_Install,USB\VID_16C0&PID_2986

In conclusion, my camera works fine and if I compare the qhy5.inf file with the latest indi cpp files (in the file qhygeneric.cpp commit r1548)

{ 0x1618, 0x0901, "QHY5LOADER.HEX", "QHY5.HEX" }, ok
{ 0x1618, 0x1002, "QHY5LOADER.HEX", "QHY5.HEX" }, really exist ??
{ 0x0547, 0x1002, "QHY5LOADER.HEX", "QHY5.HEX" }, really exist ??
{ 0x16c0, 0x296a, "QHY5LOADER.HEX", "QHY5.HEX" }, ok
{ 0x16c0, 0x0818, "QHY5LOADER.HEX", "QHY5.HEX" }, ok

VID_16C0&PID_081A is missing
VID_16C0&PID_296E is missing
VID_1781&PID_0C7C is missing
VID_16C0&PID_296C is missing
VID_16C0&PID_2986 is missing

Peter, you tell me the PPA will be updated in couple of hour. I check every day and the fix you've made never comes. Actually the qhy driver version is 1.2+r61.139 in the PPA repository. You know why ?
Linux Mint 19 Cinnamon using PPA for latest KStars-bleeding and INDI
Raspberry Pi 3 B+ with StellarMate
Atik 314E - ASI120M - CG5 with Celestron C9.25
Last edit: 10 years 10 hours ago by Sébastien. Reason: missing attachment
10 years 10 hours ago #890

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

  • Posts: 712
  • Thank you received: 174

Replied by Peter Polakovic on topic QHY5 INDI driver

OK, all missing VID/PID combinations for QHY5 are now added to rules file and driver code.

It seems, that PPA for QHY is just 12 hours old, am I right Jasem? Peter
The following user(s) said Thank You: Sébastien
10 years 1 hour ago #891

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

  • Posts: 112
  • Thank you received: 12

Replied by Sébastien on topic QHY5 INDI driver

Thank you Peter.

For the PPA that's right. I installed an update yesterday but the rules file is an old file.
When I enter this command
cat /etc/udev/rules.d/99-qhyccd.rules
The last line of the uninitialized devices part is :
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1618", ATTRS{idProduct}=="8140", MODE="0666"
And the command
ls -l 99-qhyccd.rules
returns :
-rw-r--r-- 1 root root 3733 mars  27 02:12 99-qhyccd.rules

What is the link between the ppa update version (1.2+r61.139) and the version of the commit (actually r1567)

Sébastien.
Linux Mint 19 Cinnamon using PPA for latest KStars-bleeding and INDI
Raspberry Pi 3 B+ with StellarMate
Atik 314E - ASI120M - CG5 with Celestron C9.25
10 years 44 minutes ago #892

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

  • Posts: 155
  • Thank you received: 10

Replied by Dan Holler on topic QHY5 INDI driver

Hello,

Yes, this is doing the right things for the QHY5 INDI portion. I have suggested that 2 other QHY INDI discussion come to this forum for the remainder of the QHY9 camera INDI driver.

Peter, do you think we should begin a new thread or continue along this one? I can only presently test the QHY9c and QHY11c cameras, but could test QHY2, QHY5, QHY7 and QHY5L-II.

Best wishes gentlemen,
Dan
9 years 11 months ago #893

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

Time to create page: 0.509 seconds