Guido Muesch replied to the topic 'A better FITS viewer?' in the forum. 11 hours 54 minutes 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. 12 hours 17 minutes 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. 2 days 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. 3 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. 4 months 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. 4 months 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. 4 months 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. 5 months 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. 5 months 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. 5 months 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...

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

@AradoSKYindi:
Where are the INDI-QHYCCDcamera.rule and INDI- QHYCCD.rule coming from? The original INDI 3rdparty drivers come with a QHYCCD rule file called "85-qhyccd.rules".
In this file both pairs 1618:0920 and 1618:0921 can be found. For the first pair the firmware is loaded with the help of "fxload". Then the QHYCCD device renumerates and comes back as 1618:0921, which triggers the second rule which just sets the permission to read/write for everybody.
Same holds for 1618:0940 and 1618:0941.

Ideally there should not be any tinkering necessary with the rules files. I was suspecting that maybe another package or manual editing interfered with the original rules files.

Also a -D without an argument does not make sense. Something must be wrong there.

CS
Guido

Read More...

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

Have you also checked /etc/udev/rules.d? Any rules there that match 1618:0920?
udev does not stop with the first matching rule it finds. It executes all of them.
I suspect it finds two rules: one with the error and one successfully loading the firmware.

Read More...

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

Hi Charles,

Good! At least some progress.

FX3 refers to the Cypress USB interface chip used in these cameras. The FX2 is for USB2 and FX3 for USB3. The QHY5 family only uses FX2.

In the first of your last two posts you see two lines with failing fxload. The second post only shows the second failing fxload line. What is strange is that the device address after "-D" is missing. I guess you have two matching udev rules that trigger fxload. The first one was successful now that you have an actual fxload, therefore the camera briefly worked in INDI.
So you might look for udev rules files in /etc/udev/rules.d and/lib/udev/rules.d and delete the wrong one. Hard to say which one. You can rename a rule file and append ".disabled" (any suffix would do) to try out.

That the camera stopped working in INDI is unrelated to fxload. I have had issues with streaming before, also with a non-QHYCCD camera. I do not use it anymore. With my ZWO ASI 224mc I also have to switch the camera to a different mode (LUMA instead of RGB), which is annoying. I use the focuser tab instead, which can loop single image acquisitions.

CS
Guido

Read More...