I think fxload was a different issue.
The disconnects are still happening to me as well. I have managed to get some longer runs between disconnects.
Avoid running autofocus. Save the images to the RP3, then FTP them over. Seems to help.
When it does disconnect, just reboot the PR3 from command line and you can get it responding again.

Yes, the fxload issue is separate, except that the disconnects make an additional complication. You are right in that the focusing seems to be where the disconnects seem to happen the most.
The RealVNC Viewer's file transfer functionality seems to be working better for me than ftp/scp/sftp.

libqhy should now depend on fxload (not fxload-libusb) which should work for all fx2 & fx3 cameras.

Thanks. I see that the udev rules were updated for just using fxload. Unfortunately, it looks like fxload was removed from my RPi3 with that last update. Which build are you using, since not all fxload support usb3?

I got it working like this
1. Run ethernet out to the RP3
2. Save images to the RP3, FTP them over
3. Avoid autofocus. Just capture, make a focus adjustment, then capture again.
The issue seems to be how the commands are being sent to the cam over Wifi, when it is hard wired to the router it works. Packets are being lost or something. It seems like its related to when an exposure finishes.

It may work normally without doing the FTP and manual focus over ethernet, I haven't it yet.

Edit:

Still having issues.

We're almost there with the latest update. I found that fxload is present again and it works with USB3. However, the 85-qhy.rules file has /usr/bin/fxload listed as the path for a number of cameras farther down on the list (older cameras at the top of the list correctly had /sbin/fxload). Once I did a search/replace to make them all /sbin/fxload, plug-and-play with the 163M was restored.

Good catch. Fixed.

This is extremely frustrating. Few months later and still getting random disconnects with the QHY163M in INDI. I may just sell the camera. Is there a comparable camera other than the ASI1600 that actually works with INDI?


Thanks

How does it disconnect exactly? No response? Is it a crash? or what? Do you have to do some action to get the disconnect?

Same as detailed in the posts above. It just stops responding to Ekos. Other equipment works fine still. In the driver, the camera won't let me disconnect, connect, ect, all the little lights turn yellow.

If I restart just Ekos, it says the QHY Camera not found. The only way to get it to reconnect is to restart the RP3. It seems to happen after the camera completes an exposure, the exposure never registers in ekos as complete, then it freezes up and wont to anything else until the RP3 is restarted. I have no indication as to what is causing the issue expect that the USB traffic setting seems to affect it. If I set the USB traffic to 29, it will crash sooner. If I set it to 40, it will crash sooner. I can get it to go for a while on setting 32 but it still eventually crashes.

The RP3 is hardwired to the router, and I'm saving the images local to the PR3.

I had an ATIK 414EXM working on this same system without issue.

Does the disconnect problem happen on a laptop/PC with USB3 ports?
I think what you are experiencing is related to the high bandwidth of the camera. I too would have the 163M drop out on my Pi3, no matter what the USB speed setting. I don't see that problem when commented to my Linux PC through. Also, my (new) Rock64 which has USB 3 does not seem to drop the 163M (only have been testing for 2 days).

Yes, it would happen when I connect to the PR3 with USB3 as well so I switched to USB2 because it was more stable.

The Rock64 runs INDI okay? I may give that a shot then.