When I set up my RPi to run both ekos and indi, it works pretty well ... most of the time (I'll get to that).
When I try to run Ekos on my laptop and connect to indi on the astroberry RPi, it always fails to recognize at least one device.
Often, it will be one of the two cameras, either the main ccd or the guide camera.
Sometimes, Ekos will report that it simply couldn't find one of the devices. Other times, there is an error message to the effect that a USB port was either not found, or in use by another device.
So I suspect this has more to do with USB and less with indi. I'm running a Pegasus Powerbox to supply power to the mount and all the devices, including the Pi. I currently have the cameras and the mount USB connections going to the powerbox.
After shutting down the remote Ekos session, if I try to restart the local Ekos on the RPi, it gets very confused and cannot find two or more devices. I have been resorting to shutting down the Pi, and powering down the entire system, to somehow "clear" the error state.
How can I debug this? Does INDI keep some cache of the usb ports it used the last time a session started? Or is this more an issue at the OS level? I've also noticed that the devices are very finicky about establishing usb connections depending on when you physically connect them. What's the best sequence? Connect everything while power is off, then power up the hub, and then the Pi?
A quick note: I set up a profile just using Zwo CCD for the main camera, and leaving the guide camera blank. The guide connects to the main via USB, both are Zwo.
So far, it's working very well, either locally from the RPi, or remotely from kstars on my Mac.
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?
I would use the basic asi_ccd driver (found under ZWO -> ZWO CCD) driver for both cameras (as opposed to the asi_single_ccd driver). I believe it will just work out-of-the-box, labeling each camera by its model name, e.g. something like ZWO CCD ASI 1600 MM, and ZWO CCD ASI 462 MC, or something like that. I've done that many times with the ASI1600MM and the ASI 294MC.
BTW, It can get more complicated if you have the same camera model for both imaging and guiding--one will be labeled 1 and the other 2, I think, and I don't think it's deterministic which gets a 1 and which 2. I switched to both imaging and guiding with ASI1600s. Since they are not interchangable (one is connected to the filter-wheel and one not), this can be a problem. Because of that, in the recent pre-release software, I added the ability in the asi_ccd driver to nickname ZWO cameras, and the nicknames are tied to their serial numbers, just as you suggest. (Not all ZWO cameras reveal their serial numbers over the ASI API, but many do, so it only works for those cameras).
FWIW, my experience with all of the above is only with local ekos and local INDI, but the device naming really only happens on the INDI server, so I'm not sure why local/remote would matter.
Using the configuration in my last reply, I am able to independently control both ASI cameras now, no problems connecting. I've taken various test shots, played with gain, etc. I haven't had any clear nights to try guiding yet, but I'm hopeful that since the 120MM-S can be told to capture photos, then that should be enough.
Hardware: ASI183MC main camera, ASI120MM guide camera.
USB3 port on main wired to USB3 port on Pegasus powerbox
USB3 port on guide wired to USB2 port (!) on main, per ZWO recommendation
Pegasus communicates with astroberry via USB3-USB3 connection.
For the ekos profile, I have only
CCD: ZWO CCD
no entry for guide camera.
Indi seems to want to pick up the guide camera from the main, also somewhere in ZWO or ekos documentation? Not sure.
This profile causes the main camera to use the indi_asi_ccd process, and I think the guide uses it also. I think I was getting some kind of conflicts, maybe at usb bus level, when I had a profile with zwo camera 1 and zwo camera 2, as each one was associated with the indi_asi_single_ccd process..... But all this is speculation, based upon trying a lot of different combinations.
Last edit: 1 year 6 months ago by Wes Mitchell. Reason: clarify usb connections