Hi Juergen, fx3load does not come with a ubuntu 22.04 install, you must go get the updated version as described above by Kevin Ross:

If "lsusb" shows "Cypress" and not "QHYCCD" then that probably means the firmware wasn't loaded. Unfortunately, the fxload utility that's packaged is out of date. You must download and build one that supports newer USB3 cameras from

sourceforge.net/projects/fx3load/

After you build it, copy it to /sbin/fxload, and either unplug/replug the camera, or reboot

You end up with a newer version of the file named fxload

Hi Ron,
thank you for clarifiing So the fx3load will "produce" the new fxload... But for the moment I stay with 3.6.2, since we have CS after a very long bad weather period and I dont will risk my sessions

CS
Juergen

I am having the same issue with a QHY5ii-L Mono, which is a USB 2.0 device.

It was working perfectly with KStars (on a laptop, with Ubuntu 20.04, and everything from Jasem's PPA).

At some point the QHY stopped working. I cannot say when, because it has been over a year since I last setup.

The symptom is that the QHY INDI driver will crash when Ekos is started.

Investigating further, I found that lsusb only shows the major/minor numbers (1618:0920) with no description beside it.

I then created a file in udev/rules.d like so:

The is a snippet from the larger file under /lib that contains entries for loading the firmware for all QHY devices.
But there is one significant change. The original had /sbin/fxload, but the utility is in /usr/sbin/fxload, so that is changed accordingly.

Restarted udev, and now the device is identified correctly as follows:

So that is an improvement.

But the driver still crashes when INDI starts.

What info can I provide to help resolve this issue?

Please use Ekos Debugger and share the driver crash backtrace.

Installed ekosdebugger, started it in INDI mode with only the QHY and a mount simulator.

It aborted when it could not find the qhyccd.ini file. I downloaded the default file from QHY's web site.

It went a bit further, but still didn't work.

The log from ekosdebugger is attached.

Hello,
I put my setup outside this night.
I used Stellarmate 1.7.5, QHY294C, QHY224C, with a Mak180.
lsusb list the two cameras as QHYCCD294C-V220905 and QHYCCD Titan224U.

Connections with Ekos OK. But after a numbers of capture, the QHY294C driver crashed and by the way, the system also.
I replace the 294C, by an ASI183MM, with no issues at all. No issue with the 224C as a guide.

Hello,
I just did some tests as I bought a new Mele 3Q for test environment. After completely new setup of the PC with Ubuntu 22.04.1 and installing Kstars from ppa (KStars 3.6.3 and INDI 2.0.0) and also FireCapture 2.7.10 it was NOT possible to connect my QHY (in this case the QHY 5III 174 mono) to either Kstars or Firecapture. lsusb tells me "Cypress Westbridge".
So I searched for the fxload and found it in /sbin. BUT it was a file with ca. 18kB dated from April 2018. So I copied the fxload from my productive system (still Kstars 3.6.2 and INDI 1.9.9) which has about 26kB and dated from July 2022 to the Test system. AFTER THAT IT WORKED for both Kstars and Firecapture

So either one compiles the new fxload or copies the fxload from the old working system.

Perhaps that helps others who stumble over that issue!

What I dont understand is why there is this old fx version...

Thanks for the info.

In my case, I have a fairly recent package for fxload from Jasem's PPA

1.0+202207071916~ubuntu20.04.1

It does load the firmware successfully and the camera is recognized in lsusb.

But then INDI crashes if I start with the QHY enabled.

Dont know if it helps, but here is my version of fxload (copy to /sbin/) Had to zip it for upload. Perhaps you can try it...




I have to do more tests tomorrow (take some pictures) But FireCapture worked flawlessly, and Kstars / INDI started without crash, but I didnt took pictures with Kstars...

I don't think that will make any difference, because the one I have already identifies the camera correctly.
Also, the size and timestamp on your fxload are identical to the one I have (26776 and July 7, 2022).

My issue is with INDI, and I attached the debug output from ekosdebug.
Hopefully there is something in it that can help Jasem pinpoint the issue.

Here is a comment that may help someone ...

The symptom is that a working QHY guide camera will not work, and the INDI driver will crash.

The issue is a mismatch between the fxload and indi-qhy packages as to where the fxload binary is.
This issue is in the stable, as well as nightly builds.

The fxload package has:
But the rules file in the libqhy package has all the rules set with /sbin/fxload

Example partial entry:

This prevents the firmware from being loaded.

Editing the rules file to change the path from /sbin/fxload to /usr/sbin/fxload makes the firmware loads successfully.

But I don't want to run the nightly packages, since they can introduce occasional bugs.
So, I purged all packages, and installed again from the stable PPA.

This time, the QHY camera worked out of the box with no editing of the rules file.

It turns out that this time around the fxload package is installed from Ubuntu's repo , not from Jasem's PPA, and it has the fxload binary under /sbin, as you can see in the file list .

Another thing that I did was to edit the Ekos profile (from Ekos main screen, the pen icon), to delete the QHY device, and re-add it again from the list, under the QHY heading.

I can confirm that linux mint 21 (ubuntu 22.04 based) is still shipped with the wrong fxload version. Fortunately I kept the version I built with mint 20 and works also for 21