Sure, you can run multiple INDI or INDIGO servers side by side, use -p port to specify port number.

But in this particular case it is not actually necessary, INDIGO server on the same port handles legacy INDI protocol and also XML and JSON INDIGO protocols (and also HTTP of web based control panel).

You need native INDI server only in case you want to use "snoop" between INDI drivers.

Peter

Oh! So i could load INDIGO, have my ASCOM drivers connecting, and connect KStars at the same time, on one port?

Yes, that's the intention. And you can also connect with web browser and manage the server or setup drivers. Peter

Okay, last thing - how do I load other drivers that arent included with INDIGO? For example, I need to load Lx200 AP and Moonlite Focus.

Add -i indi_driver_name to indigo_server arguments. Try indigo_server --help for other options. Peter

Yeah I tried that, and this is what I get:

Yes, that's correct. INDIGO driver is dynamic library executed directly within INDIGO server, while INDI driver is for INDIGO server remote server (just using pipes instead of network). Peter

Can you point me at the code and documentation? I wouldn't mind having a crack at an ASCOM telescope (i.e. mount) driver

Code is here: github.com/indigo-astronomy/indigo and some developers info (quite incomplete) is here: www.indigo-astronomy.org/for-developers.html . Peter

Nice initiative! I see you are using a BSD-type license, but what does this condition mean exactly?
I couldn't find it in the official 3-Clause BSD license here: opensource.org/licenses/BSD-3-Clause

It means, that you can integrate it with your own solution, but can't just resell without any other added value. Peter

Does INDIGO allow Skysafari and INDI to connect to the mount, say a CGEM, at the same time?

Not sure how I missed this thread. I just switched from ser2net to nexbridge to see if the connection performance is any better when using SkySafari and INDI on the RPI3. I do plan to install INDIGO and try it, as I am trying planetary imaging for the first time. RPI3 was used to capture my first SER file. The fps was low (about 7-9 fps), so I plan to use a windows PC to see if the fps can be increased, as I explore Jupiter. If the Windows PC ASCOM can connect to the INDIGO on the RPI3, and still allow Skysafari on iOS to also monitor the CGEM it would be sweet!

The RPI3 is almost completely controlled via web page (it is not pretty as I am not a web page designer), including initiating the dist-upgrade, monitoring RPI3 time vs mac/iOS time, and mounting of USB.

Controlling the gear via the RPI3, image capture and sequencing too, is really nice; as long as I do not accidentally power it all off LOL.

Cheers!