Hi. I tested it on astroberry/kstars , and also my old Ekos pi server. Unfortunately I updated these a week or so ago so they are all on the same QHY sdk version 21.7.3. Same result (or lack of) in each case.
I also noticed that sometimes the camera does not initialise as you say. Disconnect from Ekos, pull out the usb cable put it back in and camera starts
fine but no filter wheel.
Maybe I am looking in the wrong area ? I was presuming I would get an extra tab in the ccd section of indi control panel ? Nothing there.
When all is powered on the motor in the FW runs for a few seconds, the status light blinks then goes solid green for 2 seconds and then goes off. Hopefully that is all how it is supposed to go ? Broken/misconfigured hardware or some problem with indi_qhy_ccd ?
Ok. I changed it to USB mode by pressing the mode button (red light). So connecting usb cable (power still provided to FW from camera 4 pin cable)
and adding QHYCFW3 to profile it seems to work. Not really what I want as I already have ZWO EFW which works with this camera but is not
a very neat solution.
Bottom line FW does work but not in 4pin mode.
Any ideas to debug what's gone wrong with 4pin mode appreciated.
Hi Stefan. Glad to see it is possible. I'm using kstars 3.5.4 and I already upgraded to the latest sdk of 21.17.4 but no luck with that combination. I'm beginning to think there is some sort of
hardware issue/incompatibilty. Though I would presume the electronics should be identical
across the different cfw3 variations. Yes I can confirm I don't get the filter wheel tab in
indi control panel when the camera is loaded. I will try some earlier sdk versions but already spent too much time on this. Thanks - at least you confirmed I am not on a total wild goose hunt.
Ok I attached it to my Windows 10 workstation.
EZCAP_QT can't control the filter wheel (this is QHY's own software I think)
Sharpcap doesn't detect it.
APT can't rotate the wheel.
Broken gear I think. Will contact supplier. Thanks for your support.
Sorry to hear that. If the FW indicates 4pin mode and has sufficiant 12V supply and none of the control software is able to communicate I would suspect the FW to be defective, too.
Hopefully your supplier will help.
Yep. According to Sharpcap the 4 pin mode setup should be detected automatically without ASCOM drivers and it just isn't. Also EZCAP_QT is qhy software so if that can't do it I don't think indi has much hope. Not such a big issue. I can get by using usb until I get a fix. It's a shame
QHY kit is obviously built like a tank and made to last...........
Hi Stefan, I am in contact with Cha at QHY. I am just wondering if the problem is the camera or the FW.
When I plug the QHY294M with FW in 4 pin mode into my indi server and immediately type in a terminal window:
I get the following output:
[88253.519410] usb 1-10: new high-speed USB device number 5 using xhci_hcd
[88253.667699] usb 1-10: New USB device found, idVendor=1618, idProduct=c296, bcdDevice= 1.00
[88253.667705] usb 1-10: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[88253.667708] usb 1-10: Product: WestBridge
[88253.667711] usb 1-10: Manufacturer: Cypress
[88253.667714] usb 1-10: SerialNumber: 0000000004BE
[88253.771214] usb 1-10: USB disconnect, device number 5
[88254.083480] usb 2-5: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[88254.104010] usb 2-5: LPM exit latency is zeroed, disabling LPM.
[88254.104659] usb 2-5: New USB device found, idVendor=1618, idProduct=c297, bcdDevice= 0.00
[88254.104664] usb 2-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[88254.104668] usb 2-5: Product: QHY294P-V210220
[88254.104671] usb 2-5: Manufacturer: QHYCCD
(ignore he long decimal numbers on the left).
This is exactly the same as I get without the FW.
Just wondering if it shows anything different when the FW is working and connected (4pin mode) ?
Hi Nick, here is what I get from dmesg with connected FW:
[ 2.513647] usb 1-1.1: new high-speed USB device number 3 using xhci_hcd
[ 2.654591] usb 1-1.1: New USB device found, idVendor=1618, idProduct=c296, bcdDevice= 1.00
[ 2.654613] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.654631] usb 1-1.1: Product: WestBridge
[ 2.654648] usb 1-1.1: Manufacturer: Cypress
[ 2.654664] usb 1-1.1: SerialNumber: 0000000004BE
[ 6.000733] usb 1-1.1: USB disconnect, device number 3
[ 6.153968] usb 2-1: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 6.195279] usb 2-1: LPM exit latency is zeroed, disabling LPM.
[ 6.196336] usb 2-1: New USB device found, idVendor=1618, idProduct=c297, bcdDevice= 0.00
[ 6.196362] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6.196385] usb 2-1: Product: QHY294P-V210220
[ 6.196402] usb 2-1: Manufacturer: QHYCCD
Thanks Stefan. I can't think of anything else that might be different (apart from no FW appearing in my setup) ?
Cha (qhy guy) seems keen to do something but progress slow due to 8 hour time diff on emails........
Worst case I will attach a mini hub to FW and use USB mode - same setup as when I use ZWO EFW.....
If the FW works via its USB connector then there might be a problem related to the 4-PIN connection between the FW and qhy294.
Maybe the cable or one of the connectors are broken or there is something disconnected inside of the cam or the FW.
Chan should know ways to verify that.