For the sake of closing my reported issues with ASI1600 & AS462MC as guider...
Yesterday I was able to nicely have indiserver recognize both cams at the same time connected to a feeded HUB and HUB to RPi4's indiserver.
I IMG-toasted a new SD card and started configuring everything from scracth. I'll move to SDD shortly and see what happens (speed x 8 !!) I also used "aliasses" for cameras.
At least now I have an working SD with Astroberry 2.0.4 and a lowenergy-consuming-PC W10 with Kstars/Ekos 3.6.0 connecting to RPi4.
Cheers & clear skies!
From a completely newbie:
I'm having the same nightmare trying to recognize at the sametime both ASI1600MM and ASI462MC for guiding, connected both to same powered USB 3.0 HUB. If connected individually, ASI1600 is recognized by Ekos connecting through indiserver (only one ZWO COM driver with same default executable file indi_asi_single_ccd); while asi462MC sometimes connect some others don't.
I am even so desperate as to pull some github code for new driver asi_ccd (from here: github.com/indilib/indi-3rdparty/tree/master/indi-asi) and try to compile it. Thinking outloud, this branch's description would definetively help me by associating driver with serial number for the specific camera so they do not get entangled.
RPI's OS nicely detects both cameras as 'lsusb -v' comand lists, so my amateur's though is that the problem could be in indiserver and drivers selected for ZWOs cams (or even in the fifo pipeline defined) I also tried running a different indiserver (only for guiding cam) with different ports/pipeline etc and id did not work.
Anyway, Could you please tell me if you could guide normally (guider cam connected through main camera) and all options of main and guider cam works independently?
Many thanks and clear skies!