Oooops I speak to quick. The camera is running on my desktop but not on my laptop a Toshiba Portege R930. At the connection, I have a message in Kstars saying "No QHY camera detected power on ? (Indi)".
Very curious, my laptop is newer than my desktop ! HELP !
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 04f2:b369 Chicony Electronics Co., Ltd
Bus 001 Device 004: ID 8087:07da Intel Corp.
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
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 1618:c183
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I'm continuing my investigations. I installed a Win10 on my laptop, broadcast driver wdm, ascom driver and system driver.
EZCAP seems to runs.
Firecapture recognises the camera but do anything.
Sharpcap runs with the ascom driver, slowly.
It seems to be an OS problem of Ubuntu. I don't know how to do.
2- Edit a new shell script file named indi_qhy_ccd. I used vi, you can use a fancier editor if you like it more. I'm afraid I'm old school
#sudo vi indi_qhy_ccd
with these contents:
3- Make it executable:
#sudo chmod 755 indi_qhy_ccd
4- Modify /etc/sudoers to not ask for password when executing the script. This has to be done using the "visudo" command. DO NOT use any other editor or you risk losing root access to the computer if file ends with syntax errors.
Best way to do this will depend on distro. But adding to the end of the file this should work in most, if not any of them:
ALL ALL = (root) NOPASSWD:/usr/bin/indi_qhy_ccd_binary
In my case, what I did is:
%sudo ALL = (root) NOPASSWD:/usr/bin/indi_qhy_ccd_binary
This means that members of group sudo can execute /usr/bin/indi_qhy_ccd_binary as root without being asked for password.
After that, I'm able to connect to my polemaster executing kstars as non-privileged user.
Please note that this approach has some problems/limitations. In first place, we will be calling the closed-source QHYSDK as root. If you have any problem with that and still want to go ahead, you should do it in a machine only used for imaging and disconnected from the Internet, or in a virtual machine or docker container. And secondly, the next indi_qhy_ccd update will overwrite the newly created shell script. It can solve the issue, or not. In case not, we always could rename it again and re-create the shell script (or keep a copy in our homedir)
Note for developers: First approach I tried was setting the setuid bit in indi_qhy_ccd. For some reason, it dit not work. But setting it in qhy_ccd_test did.
Hi! Wrote a long and detailed answer and got lost when tried to send it... So I'll make it short this time...
Same problem with Polemaster and Astroberry server. Tracked down to permissions problem (probably within the QHY SDK?). One solution is to run kstars as root. A more elegant one is to run only indi_qhy_ccd as root. What I did is rename indi_qhy_ccd (i.e. indi_qhy_ccd_binary), create a shell script with this name that calls "sudo indi_qhy_ccd_binary", and add the script to the sudoers file with no password flags. Line could be something like this:
ALL = (root) NOPASSWD:/usr/bin/indi_qhy_ccd_binary
Please note that sudoers file should only be edited by using the "visudo" command, or you risk losing privileged access to the computer if you make any mistakes.
Then it works. It will be rewritten by next driver update, of course, and leaving indi_qhy_ccd_binary file. If the new driver works without issue, that's it, you can delete this file. If not you can still delete it, rename the new indi_qhy_ccd, and re-create the shell script.
As a note to developers, I also tried setting the setuid bit of indi_qhy_ccd, but that did not work. It worked setting it in qhy_ccd_test though...
Finaly, the issue is caused by the power of the USB port not enought on this laptop and others. I try the camera with the laptop newer than mine and the result was the same.
So I bought this afternoon an usb3 hub powered 2A, and the camera becames a c184 type.
It runs well with Firecapture. With Kstars I have the connection. I can modify the parameter panel. But it fails to capture an image. The field "Exposition" into the panel Progression inits with the specified exposition, but does not move. And Ekos seems to circle until I stop the capture.
Not enought power ?