Storing of settings in KStars, EKOS and INDIlib has it own logic and is historically grown. ( I remember there was an entry in the forum regarding that subject, but I don't find it on the quick.)

As far as I understand the philosophy of EKOS, the settings related to capture images and NOT bound to the cam are saved in [Capture] . Therefore the binning of the cam is stored in the related XML-file (where indiserver is running), other settings (like 'CaptureDirectory', 'DefaultObserver', ...) are saved in 'kstarsrc' (where KStars is running). From both places they are transferred to the EKOS-module 'CCD'.

In EKOS-Module 'Guide' however things are a bit different: The settings used are saved predominantly under [Guide] regardless of the cam. (In fact there are a lot of cams which are multipurpose devices: Either they can be used for imaging or for guiding.) There is a very interesting point though: If you look at the CCDSimulator (starting with 'Simulators'-profile), in the 'INDI Control Panel' you can find a so called 'Guider Head", which follows your idea: In this place you can set actually some properties (e.g. binning) for the cam if used as guider! This settings override the ones in 'kstarsrc'. I don't know if there is a real camdriver implementing this feature. At least until now, I didn't find one.

I think I will submit a merge request for the patch I wrote. This way - I hope - saving of guider-binning and guider-effectfilter will emerge in 3.5.5.

Read More...