I think I am having issues of two INDI servers /not) talking to each other:

My Avalon M-Uno mount is controlled by the new StarGO2 Pro controller, which is based on a Raspberry Pi 4 and runs its own local INDI server (starts automatically upon booting). It has it‘s own StarGO2 telescope (mount) driver which is detected, recognized and usable by external computers and EKOS, PHD, SkySafari, etc…. But I guess these are all INDI clients and not INDI servers.

Now I like to use my ASIAIR Pro, which seems to have its own INDI server. The ASIAIR does not allow me, or does not seem to have the option, to choose and use the INDI driver on the remote INDI server. So I can only use the available INDI drivers on the ASIAR… They seem to be very limited in functionality or not connecting at all. ZWO is not really responding to my request to fix this.

Actually, I have a similar issue when using INDIGO from my MacBook. In order to use INDIGO properly, I would need to have an INDIGO server on the StarGO2 RPi4. Not an option yet.

With ZWO not replying and no INDIGO server, is there a way to copy/install the StarGO2 INDI driver on the RP of the ASIAIR? Or are there other possible workarounds?

It also seems to me, the two INDI servers are conflicting each other.

Any help is highly appreciated.

BTW, remote login (VNC or Anydesk) to the StarGO2 is not my favorite solution.


 

Read More...