Apologies if this has been dealt with elsewhere but, as a new Indi user, I am a little confused about some operations that may be 'old hat' to others..

As far as I can see, there are two separate operations in general: starting a service and connecting the kit to that service.
Then, I can see there are several ways to do each. Services could be started at the command line, or within some client app. In the kstars/Ekos environment it seems you can do this either from the device manager in kstars directly, or from Ekos. For connecting, you can do this (apparently) from the service control panel (that pops up after you start the service) or, in Ekos, from the 'connect' button in the top right. (I assume other clients may have similar connect buttons)
Assuming the above is right (but please do correct if I am labouring under any misapprehensions) it seemed to me that not all combinations are equal...

Thus, I almost gave up on Indi at first because it couldn't connect reliably to my mount. (AZ-EQ6 with EQMOD service). I had selected EQMOD in Ekos (with CCD simulator), started Indi in Ekos, and then tried to connect from within the EQMOD pop-up panel. This didn't work. Then I used the 'master connect' from within Ekos and - voila! all was well!

So is this behaviour to be expected? If so, what are the 'rules of engagement' for starting services and connecting? Is there some ordering assumed and the Ekos 'master' connect does this for you?

many thanks

Kevin

Read More...