×
INDI Library v1.8.1 Released (09 Sep 2019)

Monthly maintenance release INDI v1.8.1

QHY5 INDI driver

5 years 8 months ago
milosz
Junior Boarder
Junior Boarder
Posts: 39
Karma: 1
More
Topic Author
QHY5 INDI driver #379
Hi,

I tried guiding with QHY5 today and had some trouble connecting to the camera. When the camera is freshly connected to USB INDI driver can't connect to it. After I ran qhy_ccd_test INDI driver was able to connect to the camera, but only if indiserver was run as root. Interestingly USB VID/PID changed after running qhy_ccd_test (I suppose camera does some kind of re-enumeration). I didn't notice such behavior when using QHY5 under Windows (VID?PID change). I guess running indiserver as a root isn't the best idea. Is there anything I can do to sole this problem?

Cheers,
milosz

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

5 years 8 months ago
polakovic
Platinum Boarder
Platinum Boarder
Posts: 712
Karma: 14
More
QHY5 INDI driver #380
Hi Milosz,

PID changed because it is renumerated after firmware upload. If driver can't connect unless indiserver is ran as root it probably means that you don't have correct /etc/udev/rules.d/85-qhy.rules installed.

Peter

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

5 years 8 months ago
milosz
Junior Boarder
Junior Boarder
Posts: 39
Karma: 1
More
Topic Author
QHY5 INDI driver #381
Hi Peter,

Thanks for quick reply, but missing udev rule is not the guilty one. The camera is listed on USB as:
Bus 001 Device 015: ID 1618:0901

I installed the INDI QHY driver from sources downloaded yesterday. There is rule for that in the 85-qhy.rules:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1618", ATTRS{idProduct}=="0901", MODE="0666"

This line appears there twice. I'm wondering if this might be a reason for misbehavior.

milosz

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

5 years 8 months ago
polakovic
Platinum Boarder
Platinum Boarder
Posts: 712
Karma: 14
More
QHY5 INDI driver #382
You are right, there is a bug in rules file generator code :-( I will fix it tonight, but in the meantime add line like this to 85-qhy.rules file:

SUBSYSTEMS=="usb", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="296d", MODE="0666"

It is a rule for initialized camera... Peter

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

5 years 8 months ago
milosz
Junior Boarder
Junior Boarder
Posts: 39
Karma: 1
More
Topic Author
QHY5 INDI driver #383
indiserver doesn't go to the point of sending the firmware. It stops on acquiring the USB device. Here is the lsusb output and indiserver start:

milosz@nbwasilewski:~$ lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 0557:2008 ATEN International Co., Ltd UC-232A Serial Port [pl2303]
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 004: ID 0b97:7762 O2 Micro, Inc. Oz776 SmartCard Reader
Bus 002 Device 003: ID 0b97:7761 O2 Micro, Inc. Oz776 1.1 Hub
Bus 002 Device 002: ID 413c:a005 Dell Computer Corp. Internal 2.0 Hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 019: ID 1618:0901
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
milosz@nbwasilewski:~$ indiserver indi_qhy_ccd
2013-12-29T23:09:47: startup: indiserver indi_qhy_ccd
2013-12-29T23:09:47: Driver indi_qhy_ccd: VID: 5656, PID: 2305
2013-12-29T23:09:47: Driver indi_qhy_ccd: libusb_open -> LIBUSB_ERROR_ACCESS

I restarted udev (and the laptop) several times after installing the driver. I suppose the rule is not activated or is conflicting with something.

milosz

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

5 years 8 months ago
polakovic
Platinum Boarder
Platinum Boarder
Posts: 712
Karma: 14
More
QHY5 INDI driver #384
Can you try

ls -l /dev/bus/usb/001/019

(or something like this, I don't have linux machine) to check if rule was activated and device is really accessible for anybody?

You don't need to use indiserver to experiment with the camera, qhy_ccd_test is using the same code just with much more verbose logging.

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

5 years 8 months ago
milosz
Junior Boarder
Junior Boarder
Posts: 39
Karma: 1
More
Topic Author
QHY5 INDI driver #385
I think I found the guilty one. I run udeadm test and found this line.
MODE 0664 /lib/udev/rules.d/91-permissions.rules:36

Since the qhyccd.rules has the number 85 the 666 is overwritten by 91-permissions.rules. This doesn't happen for atik, which has number 99. I changed the qhyccd.rules file name to 95-qhyccd.rules and it solved the problem. I'm not sure why it had number 85 before, but you might consider number higher than 91 to fix the problem I experienced :) However 'proper' solution should be creating INDI group (or sth like this) and adding it to udev rules. Than user can be added to this group and permissions.rules will not overwrite the permission.

milosz

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

5 years 8 months ago
polakovic
Platinum Boarder
Platinum Boarder
Posts: 712
Karma: 14
More
QHY5 INDI driver #386
Great! Thank you, I will rename the rules file to 99-... to avoid this problem. Peter

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

5 years 6 months ago
broadcastyourseb
Expert Boarder
Expert Boarder
Posts: 118
More
QHY5 INDI driver #824
Hello Indi community,

I have some trouble with my QHY5 camera. Nothing happen, the red light never turns on. I'm using the latest version of kstars and other libray (indi-qhy and qhy-firmware) with the mutlaqja's ppa under linux mint 16.
The command lsusb return this :
Bus 002 Device 008: ID 16c0:0818 Van Ooijen Technische Informatica

The value 0818 is missing the rules file. I had this line in the file in the uninitialized devices part :
SUBSYSTEMS=="usb", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="0818", MODE="0666"

It doesn't fix my problem. When I try indiserver indi_qhy_ccd, the command only returns :
2014-03-22T02:56:04: startup: indiserver indi_qhy_ccd

I manage to load myself the firmware with the command fxload and the light finally turn on. The lsusb return :
SUBSYSTEMS=="usb", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="296d", MODE="0666"

Can you help me please ?

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

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

5 years 5 months ago
polakovic
Platinum Boarder
Platinum Boarder
Posts: 712
Karma: 14
More
QHY5 INDI driver #835
Hi Sebastien, I've added PID 0818 for uninitialized camera to the driver and USB rules. You can build it from source or wait a couple of hours while it will be available on INDI PPA. Peter
The following user(s) said Thank You broadcastyourseb

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

5 years 5 months ago 5 years 5 months ago by broadcastyourseb. Reason: Find the trunk source r1548
broadcastyourseb
Expert Boarder
Expert Boarder
Posts: 118
More
QHY5 INDI driver #836
Eureka. The PID/VID appears also in the source of the driver. :blush:

My QHY5 camera is working fine after the build of the trunk source. I will also ckeck the future update of the PPA.
Thank you Peter and thank you to the whole indi's team. You make a really good job.

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

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

5 years 5 months ago
Astrodan
Expert Boarder
Expert Boarder
Posts: 139
More
QHY5 INDI driver #850
Hello,

I believe this may be a camera with a fouled address. I am unfamiliar with any QHY5 which had PID 0818. That is not to say they did not build one, but, I would suggest asking Qiu on the QHYCCD.com forum if this is a valid QHY5 address. Various addresses were used for the QHY5 depending on the geographic distribution of the camera.

As for rule 85, it used to be in the 40's, but we're getting older. :-)

Best wishes,
Dan

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

Time to create page: 0.633 seconds