I'm trying to configure Ekos with a ZWO 1600 for imaging, and a ZWO 290 for guiding.
I don't see how to do that. In the configuration setup, I selected ZWO CCD for both Guider and CCD in the Profile editor.
I connect both cameras, start up Indi, but we only get one camera tab in the indi window, and don't think we have the guider connected.
Is this possible? How should we proceed?
I can confirm that 2 ZWO cameras are ok. I use the same ZWO driver (specified separately) for imaging and guiding cam (183, 290). Both function ok. The guider shows as expected via the KStars/Ekos GUI guide output, and I get main telescope images via the normal FITs viewer output. Now if only that pesky memory leak in the FITs viewer would get solved so we can use it again.....
I currently run an ASI071MC Pro (main camera) and an ASI178MM (guider) and set them up in the Profile editor as you do by choosing ZWO CCD for both cameras. I run them on a Pi 3 (Ubuntu), PI 4 (Raspbian Buster), and Tinkerboard (Ubuntu Armbian).
At present they work fine on all these platforms, however about a year or so back I was having a similar problem as you describe. I worked around it by plugging the ASI071MCPro into the USB port first then followed by the ASI178MM. Another method that worked was to connect the ASI178MM to the USB hub on the back of the ASI071MC Pro. Ultimately this was corrected by a driver update many months back and I have not had any problem since then. I did an indoor test earlier today while setting up the PI 4 and both cameras operated correctly (the PI 4 was booted up with both cameras already plugged into the two USB 3 ports). Maybe this workaround will get you going until the solution is found.
Hope that helps!
Borg 45ED (as guider)
Astro-Physics 900GTO with GTOCP3
ZWO ASI071MC Pro
ZWO ASI178MM (Guider)
Educated guess, but since the ZWO site does a side-by-side comparison of the 533 MC pro to the 183MC pro, and knowing that their driver supports most if not all of their cameras, I don't see anything in the specs that would suggest that the existing ZWO camera driver in KStars/Ekos wouldn't drive it correctly. I think the issue at the moment is that Pi4, USB3.0, and ZWO USB3.0 capable cameras don't play well with Pi4. The Pi4 hotspot is locking up when connecting to a USB3.0 port (see other posts). Most of us who have ZWO 3.0 cams are using the USB2.0 ports on our Pi4s until this issue gets resolved. This is definitely not ideal, and we all wait anxiously for that issue to be solved. The only other issue is that it seems that for the higher resolution cams, there's either a memory leak or thread sync issue that is affecting use of preview and FITS viewer (again, see other posts). Otherwise, these OSC cams work well under KStars/Ekos. I have an ASI183MC Pro and I like it.
That's discouraging about USB3 support under Pi4 with ZWO cameras as I just upgraded for that reason in anticipation of getting the 533. I could live with USB2 until it's resolved as I am tired of leaving my DSLR out in the weather. I've seen the memory leak error myself on Pi3 to where it grinds to a halt and no longer responds properly to click via noVNC.
I tried 2 ZWO cameras yesterday for the first time. I selected ZWO CCD for CCD and nothing for Guider, both cameras showed up and worked fine. If you select ZWO CCD for CCD and Guider in the profile editor, won't that start two Indi_asi_ccd instances?
Skywatcher Evostar 72 ED DSPro
Explore Scientific ED 102
ASI 1600Mm Pro ASI EFW Mini
DeepSky Dad AF1 motor focus
ASI 120MM Mini and Bresser (Touptek) 290 Guidecams
Sykwatch EvoGuide 50/242 and NoName 50/175 Guidescopes
Raspberry Pi 3 and 4