This may sound like a little bit of a naive question, as I've only seriously been using Ekos for about six months, and am still getting orientated with the system.
I've thought about this a few times, usually just after crashing the system by forgetting to set the correct solver profile for when I've changed the camera/scope over from guide to imager and then running a solve action, and am wondering if it's possible to create module profiles for specific camera/scope/maybe focuser combinations.  In this, I'm thinking if I've got camera a/scope a (in the align module as an example) then being able to set the solver as astap, and when going to solve then it loads the settings I've already pre-selected or saved from last time and brings them up, but then if selecting camera b/scope b it automatically loads the pre-associated settings like the internal solver and associated profile, gain level, maybe autofilling the checkbox for applying darks, etc.  Also a similar concept in the focus module, with things like tolerance, min/max steps, backlash, etc.
I've had a look around to see if it's possible though not in the scripting engine as I've not looked too deeply in to that yet, I've not found anything but with the amount of configuration and different options within the kStars/Ekos environment, it could be something I've overlooked somewhere; does something like this exist or is it not implemented within the system?
Thanks in advance for any pointers you may be able to give me with this!

Read More...