Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

QHY cameras, unable to establish connection #117

Open
0ctane opened this issue Oct 11, 2024 · 2 comments
Open

QHY cameras, unable to establish connection #117

0ctane opened this issue Oct 11, 2024 · 2 comments

Comments

@0ctane
Copy link

0ctane commented Oct 11, 2024

I have 2 qhy cameras that don't want to connect. QHY163M and QHY-II-5-M. Raspberry Pi 4. Astroarch 1.9 release.

kstars-3.7.3-1-aarch64 is up to date
astro_dmx-2.9.7-1-aarch64 is up to date
astrometry.net-0.96-1-aarch64 is up to date
libindi-2.1.0-1-aarch64 is up to date

The Ekos console panel says:

2024-10-11T17:54:14 Unable to establish:

  • QHY CCD
    Please ensure the device is connected and powered on.

dmesg show the devices connect:

[ 4169.457871] usb 1-1.3: new high-speed USB device number 13 using xhci_hcd
[ 4169.558226] usb 1-1.3: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64
[ 4169.558278] usb 1-1.3: config 1 interface 0 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64
[ 4169.558637] usb 1-1.3: New USB device found, idVendor=1618, idProduct=0921, bcdDevice= 0.00
[ 4169.558660] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4169.558675] usb 1-1.3: Product: QHY5-II
[ 4169.558688] usb 1-1.3: Manufacturer: QHY-CCD

When trying to start up the connection, a dialog appears saying, "INDI Driver indi_qhy_ccd crashed."

@0ctane 0ctane changed the title QHY cameras, unable tomestablish connection QHY cameras, unable to establish connection Oct 11, 2024
@MattBlack85
Copy link
Collaborator

hi @0ctane can you try the following command and report back the output?

indiserver -vvv indi_qhy_ccd

@0ctane
Copy link
Author

0ctane commented Oct 12, 2024

@MattBlack85 , that command did show problems with the connection, but it looks like by fixing #116, this is resolved. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants