As best I can tell, the limits are not stored with the profile. When I make a change, it appears in all profiles. It does seem like it should be per profile, but I guess not.

Read More...

I can see how that would be annoying. I would make it easier to find support requests, I just do not know if there is enough interest in this specific topic to support a new category.

Read More...

Thanks Bill,

Made me define a new profile with the same devices. The same unwanted values showed up but now changes are retained. Don't know what it means but guess I'll go ahead and customize that profile instead of my usual one.
/Tom

Read More...

Looks like that fixed it. Thanks, Jasem!!!!

Read More...

Jean-Luc, it sounds like you've got this sorted but I've attached screenshots of my set up for opticat trains and guiding just FYI. I think this is the similar to what Bill was describing.

Good luck!
Fred

FWIW: I'm not seeing that problem on the Mac version of KStars/Ekos. I've changed the values several times and it is always remembered next time I start up.

Read More...

Hi can this camera be controlled via stellarmate? Thanks

Read More...

That's fine, I wonder why I had set it to Mount once, probably a misclick while trying to adjust something else.
Thank-you for helping.

Read More...

Probably because it give you ability to run automatic tests where you can set predetermined date and time and run some sequence.

That could be handled in Ekos (I imagine) by allowing an offset from system time, or to stop it.

Read More...

KStars 3.7.0
The limits settings on the Ekos mount tab do not seem to be retained across Ekos starts.
I can change the settings but they get set back to those shown the next time Ekos starts.
Purge all configuration doesn't reach it. I have been looking around for a save option and in the KStars database but can't see a way to manually edit the selections.

This is oversight from time when KStars was only planetarium so you wanted to have clock with ability to go forward and backward. For some reason they keep using this simulated clock withing Ekos too. Probably because it give you ability to run automatic tests where you can set predetermined date and time and run some sequence.

I started to work on option that will lock KStars clock to system clock. So if you set NTP or GPS synchronisation you should never see this issue again.

Read More...

I think you've nailed it here Bill. The Mac concerned is on the observatory and it does go to sleep for long periods when I'm not imaging.

Your post, together with the code inspection from Nou, shows that KStars does not have a robust approach to timekeeping.

I have tried changing the time setting to 'Mount updates KStars', since in my case that is a TCP link to TheSkyX, which does have robust timekeeping. but I have't seen any improvement yet.

Another problem with the set of 3 options (i.e. beyond the problem that there is no option of computer clock or NTP) is that they miss some obvious use cases. Imagine you have a GPS-based time (so 'GPS updates KStars'). Then you would also want 'KStars updates all devices' but selecting that option deselects the GPS.

Read More...

Don't you have a guide camera? You can't guide using the main camera while also using it for imaging.

I have two trains, one specifying the image camera. This is set as the one to use in the CCD tab. I also have a Guide train that specifies the guide camera as the Camera. It also specifies the mount as the "Guide via" device.

Read More...

Well, then I feel lost.
I just have one imager and the mount. No extra device dedicated to guiding.
So, shouldn't I set guiding to none ?
Also, as I don't use extra guiding device, the train is the same in all tabs.
I'll check as soon as I can take photos again, but I think I had to do this way, otherwise it did not work at the time I set it up.
Then, I don't modify anything that works, until I face situations where it fails.

Read More...