Ok, very good!
I finally undestrand a little bit better how the DBus interfaces works.
hoping to do something pleasing, i post here a simple code to reach the focus section of ekos and print its introspection
import dbus import time bus = dbus.SessionBus() kstars = bus.get_object("org.kde.kstars", "/KStars") ekos_obj=bus.get_object("org.kde.kstars", "/KStars/Ekos") e_iface=dbus.Interface(ekos_obj,"org.kde.kstars.Ekos") e_iface.start() time.sleep(1.0) focus = bus.get_object("org.kde.kstars", "/KStars/Ekos/Focus") print(focus.Introspect())
Ok, some progress has been made.
I can connect, checks the connection and also set the camera properties through the indi dbus interface.
Now I need to use some special functionality of ekos, like the autofocus. Looking in the introspection file of ekos, I didn't find any method that start the autofocus routine.
By now, the only way that came to mind is to load a scheduler with the autofocus setp selected. But is there another method? Maybe more simply and more "command line" like?
I try to look at the API reference of Kstars and Ekos, but I think that the methods reported are only valid for C language and not for python bindings.
I found that setting FORCE BULB "Off", the exposure on the camera change and set the time that I chose on the INDI driver, but using these settings the camera have a wired behaviour: after one or two shots it disconnets and reboot automatically!!!
Can anyone tell me what happens?
FAST EXP. : DISABLE
FORCE BULB: DISABLE
CAPUTER TARGET: RAM
SD IMAGE: SAVE
I have a problem with Kstars/Ekos and the Sony Alpha 7 mark III. I noticed that the exposure time written on the exif is wrong, and it is the exposure of the previous shots. I don't know what is the real problem, but I noticed that when the camera connects to the PC, it automatically takes an exposure without save it. Thus my idea is that the exif of this image is attaching on the next exposure.
What do you think about?
I need to write a script that automates Kstar and Ekos to start, connect devices, start sequence and so on..
For now I’m at the beginning, and this is my code:
import os import logging import time import shlex, subprocess import sys from dbus import glib glib.init_threads() import dbus bus = dbus.SessionBus() def open_ekos_window(bus): kstars = bus.get_object("org.kde.kstars", "/KStars") main_window = dbus.Interface(kstars, 'org.kde.KMainWindow') main_window.activateAction('ekos') ekos_object = bus.get_object("org.kde.kstars", # Connection name "/KStars/Ekos" # Object's path ) # Get Ekos interface E_iface = dbus.Interface(ekos_object, 'org.kde.kstars.Ekos') # Start Ekos E_iface.start() def main(): open_ekos_window(bus) if __name__ == '__main__': main()
Ok, this is exactly what I was worried about :')
Anyway, thanks Peter.
I use Kstar/Ekos software to control the Sony A7iii, I need to get the image in FITS mode and I would use the compressed raw format, that reduced the image size from 45Mb to 23Mb. But I noticed that if I choose to download the image direct in FITS format their size still remain of 45 Mb even I switch to the compressed format (option avaible directly on the camera and not in the INDI driver). On the other hand if I choose to download the image in the NATIVE format, the compressed option take effect and the result image is about 23 Mb.
So I would ask you if is it possible to obtain the FITS image in the compressed format or it is possible only for the NATIVE raw format?
I'm working on a project that involves the construction of various stations, each of these is composed by:
- DLSR camera
- Weather sensors
- maybe other minor devices
All these devices are controlled by a raspberry, in particular i try to use the astroberry distro. My target is to be able to send an e-mail to the raspberry with the instruction and it should be working in automation mode.
So i'm here to ask you some help and idea to create the instruction file. I know that it is possible to use the D-Bus protocol to comunicate with Kstar, but i'm a novice in this field and i don't know where to start.
In addition to this, i need to perform not also a kstar function but also ekos function, infact i need to launch autofocus run, plate solve, launch many image sequences during the night, as also as implement some arrest routine when some trigger is activated (e.g. bad weather condition) and retry after some period. Eventually I have to fill the fits header of the image with the coordinates, the time at wich the exposure was take etc..
I hope I was clear (even though my bad English).
Any help is welcome!!
Thanks for the advice oui, but yesterday i've tried to use CCDciel instead of kstar, but the problem still be present. If i try to do a sequence of bias after some frames the software lost the connection with the camera. This suggest me that the issue is in the indi drive of the camera maybe.
What do you think?
Hi, the return value is 256
Hi, i've enabled all debug i think, i've created a profile with only QHY driver and i've tested it doing a bias. After 2/3 frame the connection with the camera fall down, even though this time ekos isn't crashed.
Leave in attached the logs file.
In any case thanks a lot for the support
Of course! My equipment is: QHY294mm pro( QHYCFW3), Asi120mm mini,astroberry focuser, indi eqmod.Here in attached i put the last logs file of kstar. Looking at the file i can't see anything that reporting a crash, but only some captuer aborted, but i'm sure that during this interval ekos and kstar crashed.
Hi guys in these first attempt to use qhy294m with astroberry, sometimes ekos crashed and automatically close all windows!! This is a huge problem that bring me away a lot of time. Also sometimes happen that the camera connection fall down and i must restart driver or disconnect and riconnect the camera.
Please can anyone help me?
Thanks a lot and sorry for my horrible english i'm italian