Thanks for the response, Yes both are taken at the same temp, offset and gain. On review of my dark images, I may have some light leakage which is causing the higher background values.
Im going to look into that.
It only happens when i use lights with my narrowband filter, I haven't used flats for that very reason until I can narrow down this issue. All my lights and darks are taken in the same session with the same temp, gain and offset.
Yes, this is a calibrated light (stretched )its been clipped due to the delta in the background mean between Light and dark. Maybe I have some light leakage in my darks that I should probably check for that.
Thanks for responding,
So I was using the WBPP script in PI, and i did try using the Output pedestal, but the images seem to like detail or contrast. At the moment when shooting, I'm leaving out the darks as I cant seem to get them to work either manually or with WPBB. I have attached the stats to show what I mean.
I am using an Altai Astro 26C camera but shooting with a narrow band Quad filter. So I have read the mean background for these images is less than that of the dark. I have attached the Fits from my Dark/Light for comparison both shot at the same conditions Gain 100 Offset 20.
Has anyone else had any issues with EKOS not recognizing Altair cameras? Ever since I updated it during the week it won't connect or recognize the Altair camera. It recognizes the focuser which is plugged into USB on my Altair 26 C so the USB port is definitely working.
I have attached the logs in case anyone can spot anything?
My mount failed to solve its position after a meridian flip the other night and I was wondering if there was an issue or if it was something with my setup. I had it set to flip 0.2 degrees past.
That does not compute....robot brain overload seems I can reply to posts, but cant create new ones.
Sorry Jasem, I had no logs enabled last night. Will be trying again tonight.
I was using this feature last night in the northern hemisphere and doing a polar alignment away from the pole. I found the correction vectors recommended wherein the wrong direction. Also adjusting say Altitude the star never travelled along the yellow line or anywhere near it. So what I ended up doing was looking at the length of each vector and then moving the star that length for the corresponding direction.
I am using a Celestron AVX mount connected via HC and a 6 " RC scope with an AA26C camera. KSTARS is 3.5.2 stable build.
Is there something I need to check or configure to correct this performance?
I tried posting a new post, but it kept bringing me kept refreshing the posting page with the I am not a robot box. There was or is no indication as to whether my post has been submitted and waiting approval or whether it just hasn't posted at all. Should there be a waiting approval pop up?
Good afternoon everyone and a happy new year to you!
I am using a Canon 1100D as my imaging camera and an Altair Astro GP130 as my Guide camera. When I take images with my Canon in the CCD module the image is displayed and I can make out my target. However when I try to use the Focuser module or the Plate solving module the images are taken as FITS and I can't see any stars in the images, so plate-solving fails also I struggle to find any stars to focus on.
I have attached 2 images taken with the CCD module one saved as native
Thank you for taking the time to respond, I figured out the problem as it turns out I'm an idiot, For some reason, my sensor size wasn't correct it was off by a couple of pixels so when i was taking FITS images during the capture it failed to frame it properly. Once I corrected the sensor size back to what it should be the issue was resolved.
Apologies for the wild goose chase.
I'm running Kstars on a raspberry Pi when I try to launch it with gdb i get the following error
Reading symbols from kstars...Reading symbols from /usr/lib/debug/.build-id/4b/1326405df8204912d7ccbebd917e9cb832e314.debug...done.
Starting program: /usr/bin/kstars
Program received signal SIGSEGV, Segmentation fault.
0x76fd9dde in ?? () from /lib/ld-linux-armhf.so.3
I updated Ekos 2 weeks ago and was using it for the first time tonight since. Every time i went to capture an image in the focuser tab, it would take the image but as it was trying to load it would keep crashing when I was using my Canon DSLR. This would cause the canon driver to crash and I would have to restart it. However, I could take sequences and preview snapshots in the image tab without issue with my DSLR. If i then tried to autofocus it would crash the Canon driver. (I should note that I could capture a frame with my guide camera without issue).
Here is the excerpt from the log during the crash:
[2019-02-23T22:49:20.584 GMT DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 1100D : "[DEBUG] read_libraw: raw_width: 4352 top_margin 18 left_margin 62 first_visible_pixel 78398 "
[2019-02-23T22:49:20.584 GMT DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 1100D : "[DEBUG] read_libraw: rawdata.sizes.width: 4290 rawdata.sizes.height 2856 memsize 24504480 bayer_pattern RGGB "
[2019-02-23T22:49:20.665 GMT DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 1100D : "[DEBUG] read_libraw: memsize (24504480) naxis (2) w (4290) h (2856) bpp (16) pattern (RGGB) "
[2019-02-23T22:49:20.701 GMT DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 1100D : "[DEBUG] Subframing... subFrameSize: 50 - oneFrameSize: 50 - startY: 2852 - endY: 2857 - lineW: 10 - subX: 4278 "
[2019-02-23T22:49:20.751 GMT DEBG ][ org.kde.kstars.indi] - INDI Server: "Child process 13836 died"
[2019-02-23T22:49:20.751 GMT DEBG ][ org.kde.kstars.indi] - INDI Server: "2019-02-23T22:49:20: Driver indi_canon_ccd: stderr EOF"
[2019-02-23T22:49:20.751 GMT DEBG ][ org.kde.kstars.indi] - INDI Server: "2019-02-23T22:49:20: Driver indi_canon_ccd: restart #1"
[2019-02-23T22:49:20.751 GMT DEBG ][ org.kde.kstars.indi] - INDI Server: "2019-02-23T22:49:20: Driver indi_canon_ccd: pid=4892 rfd=5 wfd=21 efd=22"
Would anyone have any ideas as to what's going wrong?