Hi John

Sorry!  I personally used this possibility for SX-Wheels (not MDPD) successfully, and was not aware of the restrictions with MDPD-drivers. I remember however that it is/was? possible to tweak such drivers with custom XML-files (/usr/share/indi). Perhaps somebody has done it this way and can help?

Read More...

Hi John

It can be done with 'Custom Drivers'! (Tools/Devices/Custom Drivers ...)
You can create as many aliases for a driver as you want. Name one 'ASI Color' and another 'ASI Monochrome'. After a restart of KStars you can create two profiles with the respective alias driver name. Start each one seperately and save the configuration. Now you can choose between mono-profile and color-profile with the correct filternames in the slots.

Read More...

Sorry folks, I was away for two weeks and couldn't reach the forum meanwhile. I wrote the little patch to save the binning value for guiding.
The idea was to handle the "guider binning"  independently from the "indi control panel" parameters if - and only if - the camera has a guider head! This way - I thought - it is possible to use the camera either directly as an imaging camera with the "native" binning (set in "indi control panel") or as the "guiding" camera with the binning settings in "ekos guider tab". In the case of the presence of a "guider head" this value is corresponding to the binning value set in the "guider head" tab of the "indi control pannel".
So what happened to Kevin is exactly that: Because the "simulator camera" has a "guider head" the value of the binning set in there overwrote the binning in the ""ekos guider tab". Of course the flaw of the patch was, that it didn't reset the value to the guider head value immediately. In addition there wasn't (and still isn't!) any information about this feature.
IMHO the question is now the following: Should the feature of a "guider head" be preserved or should it be abandoned?
I'm looking forward to hear your views.

Read More...

Toni Schriber replied to the topic 'Internal guider questions' in the forum. 4 months ago

Hi Alfred
You are right: Mode 'SEPMultistar' always uses 'Autostar'. I was able to write a small patch that corrects the display of the 'Autostar'-checkbox. It is now checked and greyed out if the guider is in 'SEPMultistar' mode. I hope it will be merged in the new version of KStars.

Read More...

Many, many thanks for the hint! You are obviously right: Using 'localhost' instead of 'sternwarte' in the host field works like a charm. grin.png

Read More...

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...

Sorry! I was wrong! blush.png The file I mentioned ('kstars.kcfg') is produced when you make 'KStars' and it is used by other parts of the program while making. The file you found ('~/.config/kstarsrc') is effectivly the place where the settings are saved. You will find the guider settings under [Guide].

Read More...

Running a remote machine with INDI-Webmanager can cause a totally missmatched connection procedure if you do not control the start of indiserver via 'profile editor' ('INDI Web Manager' not checked!).
In my case I cannot connect directly the ports 7624(indiserver) and 8624(webmanager) at the remote site. I have to install an SSH-tunnel for them and to start the drivers with the webmanager "by hand" (through SSH). The first connection from my home PC works well. However when disconnecting and reconnecting from home I get a lot of error messages from the mount: As far I was able to analyze the situation, it seems that EKOS wants to adjust some mount settings (like time and location) BEFORE connecting to the mount!
Please note: This happens only if EKOS is not in control of the webmanager (see above). Reconnecting is handled well and EKOS establishes a connection BEFORE sending more settings. (I tested it on the internal network of our observatory)

Read More...