Ideas:
- There were issues when disabling one of several cameras, it would affect the other cameras with the symptoms you describe. Fixed in latest git, so if you have access to nightly builds give it a try.

- As for debug, you have to enable/configure that before starting/connecting to INDI. Click on the 'Logs' button in the Setup tab. There you can configure the debug logging.

- Is this using a Pi computer? Most issues I read were with them. Except for the case in the first point, I usually don't have download issues with the cameras (1600, 183, 290mini)

Thank you! I did not realize the debugger required some prior input before enabling it. I have not configured any of the debugging options as you describe, so that is certainly why that button doesn’t work!

I’m running on MacOS. Do you know if it’s possibly for me to build the DMG from the latest git? Or do I need special SDK tools to make that happen?

The night I ran into this problem, I was using a Macbook Pro, but I have also ran into this problem when testing out my RPI. I read somewhere that this could be because of a bandwidth issue when plugging multiple things into a single USB hub? All my stuff is plugged into a powered hub. I read something about the USB 2.0 ASI120mm not always playing nicely with other devices, such as my ASI183mc.

I’ve never heard of bandwidth/traffic issues on a USB hub before today. I figured that a USB 3.0 hub would have more than enough bandwidth to deal with an autoguider and imaging camera. Is that a legitimate cause that I should look into further?