Guido Muesch replied to the topic 'Dubious drift graphics' in the forum. 3 months ago

It actually confused and frustrated me quite a lot, that I had those incredible good results with a QHY5 at 2x2 binning, but could not get an ASI 224mc at 1x1 to guide at all. It just went all over the place and aborted. Now it's clear that the proportional gain was much too high, as I was using the settings from the 2x2 binning.
I only got suspicious recently when I started to play around with PHD2 guiding. There QHY5 and ASI224mc worked fine as expected. With this experience I got back to INDI's internal guider and used the default recommended proportional gain values and it worked with both cameras at roughly the same RMS performance only 2x higher than I was experiencing with 2x2 binning.
As a side note: PHD2 performs a bit better than the internal guider for me, so I am using this for now.

CS Guido

Read More...

Guido Muesch replied to the topic 'Dubious drift graphics' in the forum. 3 months ago

I made the same observation. With 2x2 binning I had RMS values "too good to be true". But for 2x2 binning to work well, I also had to set the proportional gain much higher than recommended (2x - 4x). Could that be affected as well?

CS
Guido

Read More...

Guido Muesch replied to the topic 'Default wifi option on boot up' in the forum. 4 months ago

I am using a high gain USB WiFi stick with Astroberry, additionally to the builtin WiFi. The builtin WiFi still works as an access point, whereas the external WiFi stick will try to connect to my home network. I sometimes had issues getting a good connection to my home WLAN network outside in the garden. The external USB stick was an improvement. Also, if the connection to my home network got stuck, I can still connect directly to Astroberry as a fallback.
I cannot remember the details, but setting it up was straight forward with the network manager.

CS
Guido

Read More...

Guido Muesch replied to the topic 'A better FITS viewer?' in the forum. 9 months ago

Astroberry uses swapping to a compressing RAM disk (maybe the default for Ubuntu Mate). That might be helpful when unused program parts are put away in a compressed form to provide more memory for active programs. But I think it is not a good idea when memory is already scarce.

I am using a swapfile now with swappiness set to 0 (only swap when absolutely necessary). On zooming in FITS Viewer the Pi did become very slow, as expected due to swapping to sd-card, but KStars FITS Viewer did not crash yet.

What you have to do:
$ sudo apt install dphys-swapfile

You can configure it in /etc/dphys-swapfile, but default settings seem to be OK. It will use a 2GB swapfile (Maybe too big. I guess the Pi will become unusable before this is fully used)
Set swappiness to 0 by adding "vm.swappiness = 0" to the end of /etc/sysctl.conf.

Regards
Guido

Read More...

Guido Muesch replied to the topic 'A better FITS viewer?' in the forum. 9 months ago

Just looked at "top" when I ran KStars on my PC (instead of the Pi3).
When zooming in to 400% in the Fits Viewer, the RES column in top exceeds 2GB. That would probably easily explain KStars crashing on the Pi.
The Pi does not really use any swap, just /dev/zram0, an in memory ram disk with compression, I assume.

However it also sometimes crashes when just using Auto Stretch with full Ekos running. Maybe it is also already low on memory.

Still it should not crash but check and handle any memory issues.

Maybe, I should go for a Pi4 with 4GB soon.

Regards
Guido

Read More...

Guido Muesch replied to the topic 'A better FITS viewer?' in the forum. 9 months ago

Unfortunately I get a SIGSEGV immediatly at startup:

astroberry@astroberry:~$ gdb -ex run --args kstars
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabihf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from kstars...Reading symbols from /usr/lib/debug/.build-id/2f/f06cd9509561a1816cfb4441a4f165c88c4c5b.debug...done.
done.
Starting program: /usr/bin/kstars 

Program received signal SIGSEGV, Segmentation fault.
0x76fd9dde in ?? () from /lib/ld-linux-armhf.so.3
(gdb) 

Without gdb KStars used to work normally.
Any idea what is causing the gdb debugging to fail?

Regards
Guido

Read More...

Guido Muesch replied to the topic 'A better FITS viewer?' in the forum. 9 months ago

Odiug wrote: BTW, I did not experience a crash with the INDI Fits Viewer yet. But I only have a ZWO ASI 224mc with a small sensor (1304x976). That would also hint at a memory issue, but Jasem already said he had fixed it...


OK, now that I bought a ZWO ASI 294mc pro, I'll take this back!
I now also experience frequent crashes with displaying pictures of the new camera (11MP, 4144x2822) in Fits Viewer : often when applying Auto Stretch and reproducable when zooming in.

Is there anything I can do to help debugging?
KStars version: 3.3.8 build: 2019-11-16T00:06:30Z
running under Astroberry on a Pi3.

CS
Guido

Read More...

Guido Muesch replied to the topic 'A better FITS viewer?' in the forum. 12 months ago

Unfortunately there are not many FITS viewers that display color FITS from INDI. E.g. DS9 only displays grey values and does not recognize the bayer information in the header. Or am I missing something?

BTW, I did not experience a crash with the INDI Fits Viewer yet. But I only have a ZWO ASI 224mc with a small sensor (1304x976). That would also hint at a memory issue, but Jasem already said he had fixed it...

Guido

Read More...

Guido Muesch replied to the topic 'QHY5 not found by Ekos' in the forum. 1 year ago

You could also try to use indi-ssag. The Starshoot Autoguider is in fact a QHY5.

However this driver works a bit different. For indi-qhy, the firmware for the QHY5 is loaded by the udev kernel mechanism, with the help of fxload and a udev rule which can either be found in /lib/udev/rules.d or /etc/udev/rules.d. In my case it is 85-qhy.rules.

The indi-ssag driver needs to find an uninitialized SSAG or QHY5, because it loads the firmware on its own. For this the loading of the firmware via udev must be prevented. If 85-qhy.rules is found in /lib/udev/rules.d the cleanest way to disable is "ln -s /dev/null /etc/udev/rules.d/85-qhy.rules", because a rule file under /etc/udev/rules.d shadows a rule file with the same name under /lib/udev/rules.d.

What do you want to use the QHY5 for? It's quite outdated and especially the Linux firmware has some (hidden) issues (Indeed for some strange reason, Windows loads a different, slightly simpler and I assume slightly older firmware ).
I probably should write down my findings about the QHY5/SSAG from my experience in building a QHY5 clone and analyzing the firmware, but I didn't find the time yet.

CS
Guido

Read More...

Guido Muesch replied to the topic 'Any news on QHY294C support?' in the forum. 1 year ago

So is anybody using a QHY294C under INDI so far?

I am interested in a 294c based camera due to size, pixel size, full well capacity and low read noise. There is ZWO, QHYCCD and Altair Astro. The ZWO seems to work, but according to Cloudynights it originally had some color artifact issues. But it seems the issue is partly related to taking short exposure flat frames where the sensor behaves differently. However the QHY version claims to have a better built quality (more even cooling concept). I don't know about the Altair. I have the general impression that the driver support from ZWO is better than QHYCCD and Altair Astro, but I am open to suggestions.

CS
Guido

Read More...

Guido Muesch replied to the topic 'New Camera - well new to me !' in the forum. 1 year ago

Indeed the ToupTek ATR3-16000-KPA sounded like an interesting camera, but looking for information, I cannot find anything on ToupTek's website.
There is an ATR3CCD Series mentioned but no ATR3-16000-KPA. Has this product already been discarded?
This gives me some doubts on how well it might be supported by their SDK in the future.

Any comments on that?

CS
Guido

Read More...

Guido Muesch replied to the topic 'QHY5 not found by Ekos' in the forum. 1 year ago

@CRW4096:
BTW, thanks for the pictures, but I would actually need to get close up shots of all PCBs from both sides, so I can see the traces.

Anybody else who has a QHY5-II and could make detailled PCB pictures? Maybe I should post this as a seperate topic...
I am interested in the differences in wiring between QHY5 and QHY5-II.

Regards
Guido

Read More...

Guido Muesch replied to the topic 'QHY5 not found by Ekos' in the forum. 1 year ago

Be aware that udev executes ALL rules that match. Not only the first one.

However if the same rules filename exists in /etc/udev/rules.d and /lib/udev/rules.d only the one in /etc is used.
That allows you to disable rules files from /lib by creating symlinks to /dev/null under the same name in /etc, without interfering with the rules files installed by packages under /lib, who are subject to being updated.

Guido

Read More...

Guido Muesch replied to the topic 'QHY5 not found by Ekos' in the forum. 1 year ago

@AradoSKYindi:
You have both 85-QHYCCD.RULES and 85-QHY-CAMERAS.RULES?
Maybe one is a leftover from an older install or different package.

Ah, I see, Jasem also wonders what is in the second file...

CS
Guido

Read More...