Thanks very much for your findings, that's great!
I will hopefully be able to give it a try with your recommended settings whenever the clouds roll out, i.e. by the end of the week.
Being away from my system I can't give specifics but I found similar issues with the gpsd rules file conflicting with other USB serial devices. I had to comment out the specific gps device rules that were conflicting.
Furthermore there also is a conflict with the Davis Vantage device which grabs a port, even though I do not have a Davis Vantage, and makes connecting my Esatto focuser (IIRC) fail. I thus has to remove the 99-vantage.rules file to fix the issue.
I can provide specifics when I get back home, if needed.
I can confirm that NoMachine works very nicely for two independant instances of KStars/Ekos, controlling two mounts and telescopes, using ODroid C4. That will likely come in handy this winter as I can control everything from inside the house.
Not specifically the answer you're looking for but from what I read you are setting up an All-Sky camera, using Ekos and Indilib. You may be interested in a self contained All-Sky camera that does not use Ekos and Indi, such as the one presented by Thomas Jacquin on github.com/thomasjacquin/allsky .
His All-Sky can make use of diverse cameras such as: Raspberry Pi HQ camera, ASI120MC*, ASI120MM*, ASI120MC-S, ASI120MM-S, ASI224MC, ASI178MC, ASI185MC, ASI290MC, ASI1600MC, and are controlled by a Raspberry Pi. It may or may not satisfy your specific requirements but it may be worthwhile to take a look as it allows setting many operation parameters.
Hope this helps.
I had the same problem, with 'indiserver' disappearing after I wanted to reinstall indi-full, on Ubuntu Mate 20.04. Re-installing, for unknown reasons, did not install indiserver. That's when I decided to rebuild from sources, as noone, then, made any mention of that issue.
I don't recall that happening on other platforms than my Odroid.
I got the same problem when building indi-3rdparty from source on an ODroid C4 (Ubuntu Mate 20.04).
Looking at the CMakeLists.txt, I found out that I could disable the build for 'playerone' by setting the "option(WITH_PLAYERONE "Install Player One Astronomy's Camera Driver" On)" line to 'Off', thus getting rid of the error.
Not useful for those updating through standard update procedure but at least there is a workaround.
What scope do you have on the mount? I suspect an RC scope (10 inch?) but not sure as it also looks a bit like an SCT but the focuser and what looks like collimations screws raise doubts on my part.
I did not know that the StarGo2 could be used with the M-Uno! I thought it was meant for the new M-Due.
Differences between the two controllers could explain the problem but, as other things seem to work correctly, that would be surprising.
Good luck and keep us posted.
Check that the slew "Speed:" button, in the PAA window, next to the "Direction:" button, is set to "Max" and not a slower speed. My M-Uno PAA speed was set to "Guide" and I thought that the mount was not slewing but it was, at a painfully slow speed. Changing it to "Max" solved the problem.
That may, or maybe not, be your problem though.
I am also using the Avalon M-Zero OBS mount with the following configuration:
William Optics GTF81 OTA
ZWO ASI1600MM Pro main camera with EFW
ZWO ASI290MM (guide cam) on OAG
ODroid N2 running Ubuntu Mate
Pegasus Astro Pocket Power Box Advanced
Avalon M-Zero OBS mount USB connected (from INDI mount general info, M-Zero firmware is Avalon - 62.0 - 11062019 )
I never encountered a situation like yours and even though I need to refine my polar alignment, the targets I shoot have always been within the field of view of the ASI1600 sensor. On that regard, I do not quite understand what may be wrong. One thing that may be different is that I do not use the Avalon hand controller and, as such, it is not connected to my mount. You may try to use the mount without the hand controller to see if that solves this problem.
Looking forward to see V3! Have fun building it.
IIRC, you need the GSC catalog to solve with the simulator. Could you have forgotten to install it on your iMac?
"sudo apt install gsc"
I noticed that you specify a "-j3" option when making, is that so that it can 'make' the software without failing on the ODroid N2? I had tried "-j4" on the C4 and make failed before completion so I reverted back to "-j2".