I have a new QHY5-III 585C guide camera which I am trying to get working with kstars/ekos (3.65 and 2.0.2) on ubuntu. I have been using a QHY600M for imaging with no problem. Adding the 585 it doesn't show up in Indi control panel, even if I unplug the QHY600. Looking at syslog it seems like it is repeatedly connecting and disconnecting:

Jun 8 19:48:40 plutoniborg mtp-probe: bus: 4, device: 87 was not an MTP device
Jun 8 19:49:12 plutoniborg kernel: [ 2367.977868] usb 4-1.3: USB disconnect, device number 87
Jun 8 19:49:12 plutoniborg kernel: [ 2368.224049] usb 4-1.3: new high-speed USB device number 88 using xhci_hcd
Jun 8 19:49:12 plutoniborg kernel: [ 2368.341382] usb 4-1.3: New USB device found, idVendor=1618, idProduct=0585, bcdDevice= 1.00
Jun 8 19:49:12 plutoniborg kernel: [ 2368.341395] usb 4-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jun 8 19:49:12 plutoniborg kernel: [ 2368.341399] usb 4-1.3: Product: WestBridge
Jun 8 19:49:12 plutoniborg kernel: [ 2368.341402] usb 4-1.3: Manufacturer: Cypress
Jun 8 19:49:12 plutoniborg kernel: [ 2368.341404] usb 4-1.3: SerialNumber: 0000000004BE
Jun 8 19:49:12 plutoniborg mtp-probe: checking bus 4, device 88: "/sys/devices/pci0000:00/0000:00:08.1/0000:05:00.3/usb4/4-1/4-1.3"
Jun 8 19:49:12 plutoniborg mtp-probe: bus: 4, device: 88 was not an MTP device
Jun 8 19:49:12 plutoniborg mtp-probe: checking bus 4, device 88: "/sys/devices/pci0000:00/0000:00:08.1/0000:05:00.3/usb4/4-1/4-1.3"
Jun 8 19:49:12 plutoniborg mtp-probe: bus: 4, device: 88 was not an MTP device
Jun 8 19:49:44 plutoniborg kernel: [ 2400.234741] usb 4-1.3: USB disconnect, device number 88
Jun 8 19:49:44 plutoniborg kernel: [ 2400.476038] usb 4-1.3: new high-speed USB device number 89 using xhci_hcd


this just continues to cycle with the device number incrementing. Both cameras are connecting through a Pegasus Powerbox Advance Gen 2 (the USB3 ports). Any ideas what might be going on?

It looks like there is no entry for QHY5-III 585C in 85-qhyccd.rules - could this be an issue with SDK version?

I'll try to update the SDK in the next week and hopefully they included it in the rules file.

For reference in case anyone has this problem the issue was I had an 85-qhyccd.rules file in /etc/udev/rules.d which was leftover from previous self compile of the sdk. This overrides /lib/udev/rules.d which was updating so I missed the newer cameras. Deleting the /etc version fixed it.

After updating to latest version of kstars and Indi 2.0.6 which includes new QHY driver I again can't connect to QHY5III585C guide camera. Unlike previously there isn't a /etc/udev/rules.d/85-qhyccd.riules file and the /lib/udev/rules.d file has a 585 listing

The log states:

Feb 12 19:58:46 plutoniborg kernel: [726813.512402] usb 5-1.4: new SuperSpeed USB device number 3 using xhci_hcd
Feb 12 19:58:46 plutoniborg kernel: [726813.533291] usb 5-1.4: LPM exit latency is zeroed, disabling LPM.
Feb 12 19:58:46 plutoniborg kernel: [726813.534276] usb 5-1.4: New USB device fo
und, idVendor=1618, idProduct=0586, bcdDevice= 0.00
Feb 12 19:58:46 plutoniborg kernel: [726813.534293] usb 5-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 12 19:58:46 plutoniborg kernel: [726813.534300] usb 5-1.4: Product: QHY585U3G20-20230914
Feb 12 19:58:46 plutoniborg kernel: [726813.534306] usb 5-1.4: Manufacturer: QHYCCD
Feb 12 19:58:46 plutoniborg mtp-probe: checking bus 5, device 3: "/sys/devices/pci0000:00/0000:00:08.1/0000:05:00.3/usb5/5-1/5-1.4"
Feb 12 19:58:46 plutoniborg mtp-probe: bus: 5, device: 3 was not an MTP device
Feb 12 19:58:46 plutoniborg mtp-probe: checking bus 5, device 3: "/sys/devices/pci0000:00/0000:00:08.1/0000:05:00.3/usb5/5-1/5-1.4"
Feb 12 19:58:46 plutoniborg mtp-probe: bus: 5, device: 3 was not an MTP device
Feb 12 19:58:48 plutoniborg ModemManager[921]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:08.1/0000:05:00.3/usb4/4-1/4-1.1': not supported by any plugin


any ideas?