I tried the log using: $ indiserver -l /home/tg/ indi_moonlite_focus indi_asi_ccd &
tg@:~$ cat 2020-06-05.islog
2020-06-05T21:06:35: MoonLite: [INFO] Auto search is disabled.
Started ekos with the profile set to remote/localhost connecting to the drivers
Examined the log again:
tg@:~$ cat 2020-06-05.islog
2020-06-05T21:06:35: MoonLite: [INFO] Auto search is disabled.
2020-06-05T21:07:21: MoonLite: [INFO] Detected firmware version 2.0
2020-06-05T21:07:21: MoonLite: [INFO] MoonLite is online. Getting focus parameters...
2020-06-05T21:07:21: MoonLite: [INFO] MoonLite is online.
2020-06-05T21:07:21: MoonLite: [INFO] MoonLite parameters updated, focuser ready for use.
2020-06-05T21:07:21: MoonLite: [INFO] Loading device configuration...
2020-06-05T21:07:21: MoonLite: [INFO] Device configuration applied.
2020-06-05T21:07:22: ZWO CCD ASI1600MM Pro: [INFO] Setting intital bandwidth to AUTO on connection.
2020-06-05T21:07:22: ZWO CCD ASI1600MM Pro: [INFO] CCD is online. Retrieving basic data.
2020-06-05T21:07:22: ZWO CCD ASI1600MM Pro: [INFO] The CCD Temperature is 0.000
2020-06-05T21:07:22: ZWO CCD ASI174MM Mini: [INFO] Setting intital bandwidth to AUTO on connection.
2020-06-05T21:07:22: ZWO CCD ASI174MM Mini: [INFO] CCD is online. Retrieving basic data.
2020-06-05T21:07:22: ZWO CCD ASI174MM Mini: [INFO] The CCD Temperature is 28.600
2020-06-05T21:07:22: ZWO CCD ASI1600MM Pro: [INFO] Loading device configuration...
2020-06-05T21:07:22: ZWO CCD ASI1600MM Pro: [INFO] Upload settings set to client only.
2020-06-05T21:07:23: ZWO CCD ASI1600MM Pro: [INFO] Device configuration applied.
2020-06-05T21:07:23: ZWO CCD ASI1600MM Pro: [INFO] World Coordinate System is enabled.
2020-06-05T21:07:23: ZWO CCD ASI174MM Mini: [INFO] Loading device configuration...
2020-06-05T21:07:23: ZWO CCD ASI174MM Mini: [INFO] Upload settings set to client only.
2020-06-05T21:07:23: ZWO CCD ASI174MM Mini: [INFO] Device configuration applied.
Well I suppose you could ssh in and look at the drivers log file, would that serve the purpose?
[tg@tcup ~]$ indiserver -help
2020-06-05T13:02:49: startup: indiserver -help
Usage: indiserver [options] driver [driver ...]
Purpose: server for local and remote INDI drivers
INDI Library: 1.8.1
Code 1.8.1-tgz. Protocol 1.7.
-l d : log driver messages to <d>/YYYY-MM-DD.islog
-m m : kill client if gets more than this many MB behind, default 128
-d m : drop streaming blobs if client gets more than this many MB behind, default 5. 0 to disable
-p p : alternate IP port, default 7624
-r r : maximum driver restarts on error, default 10
-f path : Path to fifo for dynamic startup and shutdown of drivers.
-v : show key events, no traffic
-vv : -v + key message content
-vvv : -vv + complete xml
driver : executable or device@host[:port
Reading through the entries under
provides a good overview. You generally monitor and control the indi
drivers from a client running locally or remotely. KStars/Ekos can also be run on the Rpi although it will be under powered. More common I think is for a client to communicate remotely to a Rpi running the drivers.
Just came across this product which indicates it is free / open source. It interfaces with various editors. Perhaps it would help to explore the Ekos code base.
Just curious I tried with an old image, and image colour looks much the same. Taking it over to PixInsight debayer & stretch shows signs of life.
I have just gone through a OS install to run ubuntu 18.04 and the latest indi 1.8.5 is for the most part setup.
So far with the roof Arduino connected I have not yet managed to reproduce the problem.
It is a clean install to the extent that no old libraries or 3rdparty programs were carried over. I did retain all the property settings in the home directory.
I sent Christophe a new roof driver source with the addition of a 1 second delay in the handshake routine to see if slowing it down a bit helps.
[root@chai tg]# dnf list --installed kstars-bleeding
kstars-bleeding.x86_64 3.4.1-4.3 @lupinix-indi-bleeding
[root@chai tg]# dnf list --installed libindi-bleeding
libindi-bleeding.x86_64 1.8.1-1.42 @lupinix-indi-bleeding
Some success here although left with not being sure about how to get there.
I do not have the problem with Ekos overlaying the other windows, just the KStars window. I am using cinnamon to provide the window management. If Ekos has focus perhaps Control-k will hide/restore it?
After deleting the Ekos profile and creating a new one the issue with blocking on wanting to take darks persisted. I often have trouble with the Calibration button in the CCD imaging tab. It comes into play when not taking Flats and there is no apparent need for it to get involved. It is hard to get it to retain the desired setting and it keeps reverting to previously used state. Changing other settings on the imaging screen and the Calibration button leaps back into life.
After an hour or so of messing it settled into a manual mode under a Bias setting. I have never discovered what makes it finally accept the setting wanted and preserve them from one usage to the next. The request to cover the telescope continued but I was then able to continue from it. The first screen shot shows the settings. KStars crashed after continuing when attempting to take the image. Running under the debugger took longer to crash, interestingly before it did it put up a fits image. However the image was of the current desktop that only occurred the one time. The KStars log is attached. It was now creating bias.fits files before crashing attempting to display them, a sample bias file is available if of any use at:
After finally getting images what seems to have solved the crashing is noticing the size of the bias was 16M when it should
be 32MB. The asi1600 setting had reverted to 8 bits instead of 16 at some point. After changing that good fits images are being produced and no more requests to cover the telescope. Hopefully it will continue to work for a while.
Probably not related but the instructions I follow say not to reference cmake in the same directory. so I use cmake ../
mkdir build && cd build
cmake ../kstars -DCMAKE_INSTALL_PREFIX=/usr
sudo make install
Also on Fedora. I can't help but can confirm cap error message.
For a while have been getting the KStars crash when starting Ekos. It takes perhaps 6 times before it stays up. I am running it by manually starting indiserver first followed by an Ekos auto connect, that seems to avoid the crash.
I have 2 telescopes and have changed setup from refractor to SCT a couple of nights ago. The flipflat was removed from the Ekos profile. Changed the park position. Then discovered the reason the mount was going off in strange directions was because KStars had decided I was now in Korea. Spent most of the time setting up the different focuser which seemed to go well ending with an auto focus. Then when attempting to get an image ran into the cap error which was surprising since it was not part of the profile. I got stuck at that point and it had dropped below freezing so gave up for the night.
Next day I tried to look into it but can no longer get the ZWO cameras to work. I saw that Fedora had not had any indi updates since April 3rd. I tried a rebuild of KStars and indi but it did not change the camera situation. In case someone recognizes this. They both appear to be partially connected in some way with just 3 tabs showing. I had this issue one time before but can not remember how to get around it. It was something simple, I thought it was a missing 85-asi.rules but that is there.
When you use the exit full screen, while it stays full screen, do the maximize, minimize buttons show up in the top right hand corner? If so that will get you out of it.
Does super+H (the windows key)+H, how about ALT+F8 for changing size.
Some respond to F11 or Escape
A question on translation, in particular for a driver. I am not understanding what is involved. I had assumed that using the INDI system calls would result in i18n handling when the button or label was built into a GUI representation. In Christophe's images above some of the driver's buttons and labels are translated but not others. Similar situation in the Observatory panel.
In the Observatory "Close" button appears to be translated, though hard to see on my screen, but "Close" in the driver is not translated.
Not sure what locale Christophe is using but have not yet managed to get my Fedora/Cinnamon system to properly display KDE Qt5 applications by changing to fr_FR.UTF-8.
Before resorting to a Ubuntu build to experiment with I wanted to ask Is there something that can be done in the driver to enable the translations?
The roll off roof driver was derived from the rolloff simulator driver. The Park/Unpark is the same, inherited from the Dome and controlled from the Observatory. github.com/wotalota/indi-rolloffino
My response to Christophe was that I could not change the Observatory. That power management was not really the domain of the roof driver. I use something like: www.digital-loggers.com/lpc.html . He wanted something within KStars so the auxiliary button was added and his Arduino code could choose to use that as a power on/off request.
If you test more of the other panels you might find similar problem. It sounds like the "responsivity" issue in another thread.