any hope that the fps prpblem can be solved? I would love to have the dual use functionality of DS and planetary imaging.

CS, Markus

Read More...

KStars shows the same wrong debayered images. I think there is no need for a manual offset setting, just a setting to keep the original Bayer matrix by allowing only even sized ROIs and offsets.

Markus

Read More...

using my QHY462C camera for planetary imaging, EKOS writes SER files with the wrong header. I get files declared as MONO and without a Bayer matrix declaration. A bit of a nuisance for the further processing. The Omegon driver of my other camera does this right but has other problems (other topic).

CS, Markus

Read More...

I tried to do some planetary imaging with my Omegon veTEC 571C and had two problems:

1) I get max 6.9fps no matter how small the ROI is set. The driver seems to always download the full frame.
2) the ROI setting does not take the Bayer matrix into consideration. An option to have only even spaces offsets and szes would be helpfull or if oddly sized the bayer matrix setting in the header must be set to the right format. eg RGGB -> GRBG

CS, Markus

Read More...

I use the latest stable release of EKOS/Kstars/INDI with the EQMOD driver on a x86 laptop running Ubuntu 22.04. Goto to a star position works flawlessly as expected. After two or three moves/plate solves the position is good within a few arcseconds. But for planets or deep sky objects it does not work. There is always an offset between the real position and the assumed position. This is pretty weird because the solver knows the real position and Kstars knows and draws the real position of the planet/nebula but no further move is done. I have attached a screen shot of the situation. I can manually center the planet and sync but a goto will move the telescope again to the offset position. I must do something wrong/stupid, maybe a missing config option, I don't know. About a year ago, I used a RPI4 with the astroberry distro without this problem.

CS, Markus

Read More...

all good with Kstars 3.6.1 Stable and Indilib v.1.9.8!
THANK YOU!

Markus

Read More...

installed the latest nightly build, but get a crash loop after connecting.
org.kde.kstars.indi: INDI driver "indi_toupcam_ccd" crashed!

Markus

Read More...

Hi Jasem,

could you elaborate bit more on what exactly should be done. I have tested it with Kstars 3.6.0 Stable and
org.kde.kstars: Welcome to KStars 3.6.1 Beta
org.kde.kstars: Build: 2022-09-17T21:16:43Z
with no change, still the FITS files do not conform. Do I have to use a nightly build of indilib and 3rd party drivers on my remote PC?

Markus

Read More...

stacking pictures I took in June (EKOS/INDI May versions with toupcam driver) with pictures taken recently (EKOS/INDI July versions with toupcam driver) I got errors. Closer inspection showed that the June files conform to the FITS standard with HDU/file size being a multiple of 2880 bytes and the newer files do not conform.

Could this issue please be resolved in the next version?

Markus

Read More...

I use an Omegon veTEC 571M/C with the "Touptek" driver and this works reasonably well since a few months. There is also an Omegon Pro driver available. For which camera models is this driver made?
Currently the Touptek driver still uses the SDK version of 202110. I have noticed that Omegon has a newer SDK made available for download: nimax-img.de/Produktdownloads/68723_4_SD...loads/68723_4_SDK.7z
Would it make sense to include this SDK with the next release? Or maybe use it just for the Omegon Pro driver?

CS, Markus

Read More...

worked on my freshly installed RPI with 4GB RAM and Ubuntu 22.04. One caveat is that I had to increase the default swap size from 1GB to 2GB otherwise the kstars compile failed.
Maybe you would like to add the indiweb install to the script and/or indistarter. I guess most potential users would want it.

Markus

Read More...

is the script designed for Raspbian or Ubuntu 22.04 LTS?

Markus

Read More...

my FITS files generated by EKOS (with Toupcam driver) do not have the OBJECT keyword set to the Target name. It's always UNKNOWN although the target is known and appended as Prefix to the filename. I searched around but could not find the option to make this work or maybe it is a bug?

Markus

Read More...

the DBUS problem reappeared after a reboot and this time I found the solution without another reboot. The environment variable XDG_RUNTIME_DIR has to be set to /run/user/$UID.

Markus

Read More...