Hi Martin. I have have no problems with the QHY294M as long as I use a good quality powered USB3 hub - I use the Anker 12V powered hub (see my earlier post). Also make sure you are using an adequate power supply for the PI. A PI4 needs a minimum of 3A@ 5.1V when attaching power hungry USB kit.
The only issue I had originally was that the fxload program in the package I installed was out of date and did not support the camera.
I updated it from the QHY SDK (32bit arm for Astroberry). To check fxload use fxload -V:
[EKOS]$ fxload -V
Jul 16 2021 (development)
This is a recent one. If it is years out of date then update it.
QHY cameras all seem to require more power via usb than ZWO equivalent ones.
Hi Stefan. Yes it seems very lkely. It's just same as when I connect the camera without the FW.
No comms to FW via camera. I've checked the cable for continuity - all pins seem to be connected to the RJ12 so either problem inside camera or inside FW.........
My ZWO EFW (5 slot used with colour cam): plugged it in and it worked - end of story.......
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.....
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) ?
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...........
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.
I meant sdk 21.07.16 (libqhyccd.so.220.127.116.11)..........
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 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. 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 ?
Hi Jasem. Yes I have tested many many times on 2 different servers. I am currently just running a
test using telescope simulator and qhy kit connected to my workstation via usb3 and powered with separate 12v power brick. Not all that sure about how to enable more logging. I get this
in indi control panel at startup:
2021-07-30T06:00:14: [INFO] Debug is disabled.
2021-07-30T06:00:14: [INFO] World Coordinate System is enabled.
2021-07-30T06:00:14: [INFO] Device configuration applied.
2021-07-30T06:00:14: [INFO] USB Buffer updated to 512
2021-07-30T06:00:14: [INFO] USB Traffic updated to 0
2021-07-30T06:00:14: [INFO] Offset updated to 8
2021-07-30T06:00:14: [INFO] Gain updated to 1600
2021-07-30T06:00:14: [INFO] Upload settings set to client only.
2021-07-30T06:00:14: [INFO] Loading device configuration...
2021-07-30T06:00:14: [INFO] USB Traffic Settings: Value: 0 Min: 0 Max: 255 Step 13
2021-07-30T06:00:14: [INFO] Offset Settings: Value: 0 Min: 0 Max: 200 Step 1
2021-07-30T06:00:14: [INFO] Gain Settings: Value: 1 Min: 0 Max: 3624 Step 1
2021-07-30T06:00:14: [INFO] Humidity Support: False
2021-07-30T06:00:14: [INFO] Camera exposure limits: Min: 0.000001s Max: 3600s Step 0s
2021-07-30T06:00:14: [INFO] Current read mode: 11M MODE (4164x2822)
2021-07-30T06:00:14: [INFO] Sensor resolution for mode 47M MODE: 8336x5648 px
2021-07-30T06:00:14: [INFO] Mode 1: 47M MODE
2021-07-30T06:00:14: [INFO] Sensor resolution for mode 11M MODE: 4164x2822 px
2021-07-30T06:00:14: [INFO] Mode 0: 11M MODE
2021-07-30T06:00:14: [INFO] Number of read modes: 2
2021-07-30T06:00:14: [INFO] Using QHY SDK version 21.7.3
2021-07-30T06:00:11: [INFO] Connected to QHY294PROM-8afa9343bb46964a3.
2021-07-30T06:00:11: [INFO] Debug is enabled.
No errors but no indication that CFW3 is connected, but the camera works fine.
I just received a QHYCFW3S-SR filter wheel for use with my QHY294M camera, I have attached the CFW3 to the camera using the 4 pn RJ11.
As I understand I only need to use the indi_qhy_ccd and the CFW3 should appear when Ekos starts the camera. However this doesn't appear to happen.
There are no messages in the indi control panel to show CFW3 has been detected and no options or filter values available in the camera tab of Ekos.
When the CFW3 is connected it makes whirring sound (good) and the status light blinks and lights green for 2 seconds which indicated that 4pin mode
is set inside the CFW3. The camera is powered by a 10A 12v power brick so no power issue. The camera is connected via usb3 and I can take images
I tested it both remotely on raspberry pi (Ubuntu 20,x arm64) and locally on intel workstation (Ubuntu 20.x x86-64). Kstars and all packages are fully up to date (29 July 2021). QHY SDK version 21.7.3. The camera works fine, but no filter wheel.
I guess I am missing something.
The problem is that on my ubuntu 20.x server dists only python3 was installed but some of the code for indi-web
has #!/usr/bin/python scripts.
I made a link:
sudo ln -s python3 python
Now indi-web reads and writes the correct configs .
This explains why it was working both locally and remotely when starting indiserver manually
but broke when using indi-web.
Ok. I think it is some sort of file problem.
If I use your URL it works fine.
If I use some script to download your data to local file every 60 seconds:
while true ; do curl -s aagsolo.lunatico.es:10800/cgi-bin/cgiLastData -o cgiLastData; sleep 60; done
and change the File option to point to the full path of the file cgiLastData then same problem as before. I get a straight line
connecting the startup value and the first update then no more updates.
Permissions fine - it is rw rw r ....
Will go for break and think about it.