Hi Jasem,

Thanks a lot! That indeed solves my issue. As I am using Astroberry exclusively remote, I wasn't even aware that there is sound. :-)

Regards + CS
Guido

Read More...

OK, I found the following in the log files. Kstars/Ekos seems to run out of file handles:

[2021-11-13T17:06:21.665 CET INFO ][   org.kde.kstars.ekos.capture] - "Capturing 1.000-second  image..."
[2021-11-13T17:06:21.798 CET DEBG ][           org.kde.kstars.indi] - ZWO CCD ASI294MC Pro : "[DEBUG] StartExposure->setexp : 1.000s "
[2021-11-13T17:06:25.223 CET DEBG ][           org.kde.kstars.indi] - ZWO CCD ASI294MC Pro : "[DEBUG] Uploading file. Ext: fits, Size: 23397120, sendImage? Yes, saveImage? No "
[2021-11-13T17:06:25.648 CET DEBG ][           org.kde.kstars.indi] - ZWO CCD ASI294MC Pro : "[DEBUG] BLOB transfer took 0.310453 seconds "
[2021-11-13T17:06:25.649 CET DEBG ][           org.kde.kstars.indi] - ZWO CCD ASI294MC Pro : "[DEBUG] Upload complete "
[2021-11-13T17:06:25.915 CET DEBG ][           org.kde.kstars.indi] - Image received. Mode: "Normal" Size: 23397120
[2021-11-13T17:06:26.060 CET INFO ][           org.kde.kstars.indi] - "FITS" file saved to "/home/astroberry/Ekos/Light/test_Light_473.fits"
[2021-11-13T17:06:26.060 CET DEBG ][           org.kde.kstars.fits] - Reading file buffer ( "22.3 MiB" )
[2021-11-13T17:06:28.304 CET INFO ][   org.kde.kstars.ekos.capture] - "Download Time: 2.65 s, New Download Time Estimate: 2.65 s."
[2021-11-13T17:06:28.319 CET INFO ][   org.kde.kstars.ekos.capture] - "Received image 473 out of 500."
[2021-11-13T17:06:28.334 CET INFO ][   org.kde.kstars.ekos.capture] - "Captured /home/astroberry/Ekos/Light/test_Light_473.fits"
[2021-11-13T17:06:29.908 CET DEBG ][           org.kde.kstars.fits] - FITHistogram: JMIndex  1
[2021-11-13T17:06:30.183 CET DEBG ][                       default] - WARNING: Phonon::createPath: Cannot connect  Phonon::MediaObject ( no objectName ) to  Phonon::AudioOutput ( no objectName ).
[2021-11-13T17:06:33.738 CET DEBG ][           org.kde.kstars.indi] - ZWO CCD ASI294MC Pro : "[DEBUG] Uploading file. Ext: fits, Size: 23397120, sendImage? Yes, saveImage? No "
[2021-11-13T17:06:34.166 CET DEBG ][           org.kde.kstars.indi] - ZWO CCD ASI294MC Pro : "[DEBUG] BLOB transfer took 0.313525 seconds "
[2021-11-13T17:06:34.167 CET DEBG ][           org.kde.kstars.indi] - ZWO CCD ASI294MC Pro : "[DEBUG] Upload complete "
[2021-11-13T17:06:34.415 CET DEBG ][           org.kde.kstars.indi] - Image received. Mode: "Normal" Size: 23397120
[2021-11-13T17:06:34.549 CET INFO ][           org.kde.kstars.indi] - "FITS" file saved to "/home/astroberry/Ekos/Light/test_Light_473.fits"
[2021-11-13T17:06:34.551 CET DEBG ][           org.kde.kstars.fits] - Reading file buffer ( "22.3 MiB" )
[2021-11-13T17:06:36.773 CET INFO ][   org.kde.kstars.ekos.capture] - "Download Time: 2.60 s, New Download Time Estimate: 2.65 s."
[2021-11-13T17:06:36.787 CET INFO ][   org.kde.kstars.ekos.capture] - "Received image 474 out of 500."
[2021-11-13T17:06:36.801 CET INFO ][   org.kde.kstars.ekos.capture] - "Captured /home/astroberry/Ekos/Light/test_Light_473.fits"
[2021-11-13T17:06:36.840 CET WARN ][                       default] - QProcessPrivate::createPipe: Cannot create pipe 0x977e3bc: Too many open files
[2021-11-13T17:06:38.420 CET DEBG ][           org.kde.kstars.fits] - FITHistogram: JMIndex  1

"Too many open files": So there seems to be some kind of resource leak. Any ideas?

Regards + CS
Guido

Read More...

I experience Kstars/Ekos freezing on large image sequences. I am using the latest INDI Kstars/Ekos available on Astroberry as of today (2021-11-12).
My camera is a ZWO ASI294mc pro. For testing puposes I defined an imaging sequence of 500 frames (1s exposure). At frame 480 the sequence number does not get increased anymore and the frame "test_Light_480.fits" gets overwritten until the 500 frames are finished (can be seen by the timestamp of the file). When this starts, the following messages start appearing:

Found one coordinate representation.
Found one coordinate representation.
Found one coordinate representation.

(kstars:3450): GStreamer-CRITICAL **: 11:14:17.334: gst_poll_get_read_gpollfd: assertion 'set != NULL' failed

(kstars:3450): GStreamer-CRITICAL **: 11:14:17.334: gst_poll_get_read_gpollfd: assertion 'set != NULL' failed
Found one coordinate representation.

(kstars:3450): GStreamer-CRITICAL **: 11:14:25.592: gst_poll_get_read_gpollfd: assertion 'set != NULL' failed

(kstars:3450): GStreamer-CRITICAL **: 11:14:25.595: gst_poll_get_read_gpollfd: assertion 'set != NULL' failed

(kstars:3450): GStreamer-CRITICAL **: 11:14:25.596: gst_poll_get_read_gpollfd: assertion 'set != NULL' failed
Found one coordinate representation.

The "Found one ..." appears with every frame, but now GStreamer starts complaining. How does gstreamer fit into this? I thought the INDI driver would be talking to the ZWO library and the INDI protocol to Ekos.

Finally, when I close the FITS Viewer after the sequence has finished and I trigger another image capture, the same GStreamer messages will appear, the FITS Viewer window will pop up, but freeze and stay white. The whole Kstars/Ekos needs to be killed now.

This does not happen when using a camera with a smaller sensor (ASI 224mc, 1Mpix instead of 11). And I can also not reproduce this on my Laptop (Ubuntu 20.04 LTS, x64). It looks a bit like a memory issue, but Kstars uses 15% according to top (on a Pi4 with 4GB) and the filesystem also had plenty of space left.

I managed to compile Kstars from GIT yesterday (3.5.6 stable) and it shows exactly the same behavior.

Any suggestions on what to test to narrow down the issue?

Regards + CS
Guido

Read More...

Odiug replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 1 year ago

Thanks! Good to know.

I had a frustrating evening yesterday when I wanted to switch my mount from Equatorial to AltAz und therefore needed to recompile OnStep. It moved in unexplainable ways and also parked in different positions. At some point I switched to the latest Release and it began to move reasonable again. But after a "move to home" it got stuck. An "unpark" was not successful. "Tracking enable" however was successful. Later I figured out that it works when I set a park position. OnStep's internal state handling is sometimes a bit inconsistent. After some more issues (timezone was 1h off) I finally got it working.

OK, this was all unrelated to INDI, as I reconfigured my mount to AltAz for visual observation and I am using a Basic Handcontroller and the OnStep App for controlling the mount. However I used INDI inbetween when I was trying to figure out what was going wrong.

Sorry for venting my frustration with OnStep. Let's hope Howard makes the Beta a final stable release before putting all his energy into OnStepX. ;-)

CS
Guido

Read More...

Odiug replied to the topic 'Driver OnStep (LX200 like) for INDI' in the forum. 1 year ago

Which OnStep version does the OnStep driver expect, or was developed against? I assume features, behavior and capabilities can vary. Latest release is 3.16. When I experimented with OnStep focuser support, I was told by Howard, that master would be safe currently (end 2020). Therefor my current version is 4.17j.

Anything you driver developers can recommend? Better stick with Release?

CS
Guido

Read More...

Odiug replied to the topic 'Can't use exposure time < 2 sec.' in the forum. 2 years ago

Thanks for the hint. I will try it.

Regards + CS
Guido

Read More...

Odiug replied to the topic 'Can't use exposure time < 2 sec.' in the forum. 2 years ago

Hmmm, I had a similar experience yesterday when using my equipment after weeks of bad weather.
In my case it is <1s when capture fails. Cameras are ASI 294mc (main) and ASI 224mc (guiding). Both cameras fail at <1s.
System is an RP4 running Astroberry and updated yesterday as well. Astroberry only has the "stable" branch available. So no updates for INDI and KStars since a while.

However, I remember that short exposures have worked before, but I cannot recall how long ago that was.

CS
Guido

Read More...

Odiug replied to the topic 'Problem with Polar Alignment' in the forum. 2 years ago

I can confirm, that I experienced the same issue: Mount not stopping on moving to the next position in polar alignement.
I also remember having that issue quite a while ago and then it was fixed for a while. But currently (latest up to date Astroberry) it is again present.

I am anyway desperately waiting for a new stable release to have this bloody OnStep issue (crash on unpark) fixed.
INDI/EKOS/Kstars is great, but sometimes drives me nuts!

Regards + CS
Guido

Read More...

Have you tried this:
pypi.org/project/colour-demosaicing/

I used it a while ago when I experimented with processing FITS files with Python scripts.

CS
Guido

Read More...

Why running Siril and PSS on the RP4? Both programs are quite computational intense. I usually run it on a more powerful machine. Well, only a laptop, but I am already considering to switch from 8GB to 16GB RAM. The latest Siril feels slower. Maybe due to the internal 32bit float representation.

PSS also uses a lot of RAM. I hardly managed to process a recording of Mars with 5000 frames at 640x480 on my 8GB laptop.

Otherwise I am currently stuck with the same issue: Broken INDI with OnStep driver in stable. Currently I am too lazy to built INDI/Kstars from scratch and hope the fix will soon find its way into stable.

CS
Guido

Read More...