Here is a log file. It sees the QHY600 main camera but no mention at all of the QHY585 Guide camera.
Read More...
After updating to indilib 2.0.6 my QHY585 guide camera is no longer picked up by indi when I run it via kstars. My main QHY600 is and they both showup OK in lsusb:
Bus 005 Device 003: ID 1618:0586 QHYCCD QHY585U3G20-20230914
Bus 005 Device 004: ID 1618:c601 QHYCCD QHY600U3G20-20230614
I think the fact they are both appearing properly as QHY devices implies fxload etc is OK and comms exist. This makes me think it may be a indi driver issue. Any ideas?
Read More...
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?
Read More...
Its cloudy tonight so I can't do a full test on adaptive focus but it does look like the temperature is updating more regularly with the change.
Read More...
The polling period is 500 ms which is the default I think and consistent with others observations of temperature updates every 5 seconds. In my case it appears the temperature only updates when I do a focus run which means adaptive focus doesn't do anything.
Read More...
I am thinking of going in this direction so, in anticipation, I am starting to try running as if I were remote. I just bought some Kasa smart plugs and will being working to have a suite of targets teed up and see how it all goes while still walking to my scope in the backyard and taking off the telegizmos cover. Eventually I would like to get a Robodome of equivalent so I can image when I am out of town. This way I can debug things in advance and see if I need to switch to another control system. My main concern is my filter wheel sometimes gets stuck and I have to unscrew the cover and jog the spring, hard to automate…
Read More...
The serial write issue has never reoccurred but I am having issues with temperature update. I am running the latest Esatto firmware (3.5.13) and kstars 3.6.7. The temperature seems to update sporadically and goes long periods without updating despite varying outdoor temperature.
Read More...
Filter changes have gone wonky on my QHY600 - when I change it hangs - if I change again to same filter it works. kstars 3.6.7
Read More...
The serial write error is not reproducible and I have seen the temperature update with the newly modified driver from GitHub. I am now on business travel so can’t do comprehensive testing to confirm it is well and truly fixed but will do so on my return. My other system has a Nitecrawler focuser and the temperature does update there so it isn’t a common issue across different devices although it could be in other drivers I suppose.
Read More...
Updated driver doesn't fix it. Now getting a serial write error
2023-10-10T14:22:21: [ERROR] Serial write error: Timeout error
Read More...
This independent observations seems to confirm a driver problem. I will post a bug report on GitHub.
Read More...
There is primaluce software but it’s windows only, I will try and find a way to get it connected and verify it works.
Read More...
Polling is set to 500 ms. The Indi control panel for esatto environment tab shows the motor temp and external temp. External temp is stuck on the value when the driver loaded, the motor temp changes. Log file attached with various focus runs all show same temp (19.12).
Read More...