Just a thought...could it be that the qhy driver should be invoked with an argument that
specifies the USB port to use. If the driver is loaded only once (because of the same camera manufacturer)
the cameras are concurrenting for the same port or the second is not handled by the driver.
I can also connect a QHY5L-II-M and QHY163M at the same time. However, stability of the faster USB3 devices is questionable on the Raspberry Pi 3. My 163M likes to disconnect occasionally, and I suspect it is due to the high data transfer rate that the Pi cannot handle.
Yes, still affected...
I updated today before starting acquiring.
This is the setup:
Camera:
QHY 5LII-M
QHY 183C
Packages:
qhy-firmware-1.1.1-3.1.noarch
indi-eqmod-bleeding-1.6.3-5.1.x86_64
lupinix-indi-bleeding-1.0-182.2.noarch
libqhy-1.1.1-3.1.x86_64
libindi-bleeding-1.6.3-4.1.x86_64
indi-qhy-bleeding-1.6.3-5.1.x86_64
I found on my Rock64 that sometimes only my QHY5L-II-M would connect, and sometimes both it and my 163M would connect. When the 163M wouldn't connect, sometime shutting down indi, pulling and reinserting the 163M, and restarting indi would make it appear. I don't seem to have that specific issue with my RPi3 though.