pauledd replied to the topic 'v4l2 CCD & guiding issue' in the forum. 2 days ago

ok, thanks, with 3 digits I get only 10 steps but I will see if that is sufficient.

Read More...

pauledd replied to the topic 'v4l2 CCD & guiding issue' in the forum. 2 days ago

Reporting back: some kind off success! (with the crappy cam)

After playing around with guiding settings, exposure values and guide stars and calibration attempts
I found the DEC axis had a huge backlash. I observed this while doing calibration. After calibration completes
the first DEC direction I noticed the star needed some more iterations to begin to move to the opposite direction.
So I step by step increased the DEC backlash value and re-did the calibration. As I reached 500 microsteps I saw
the guide star imeadiately began to move with the DEC drifting reverse.
Since then my SIG(RA/DEC)" values stayed below 1.5 quite for a while. I still have some problems to control the
guide cam image quality. It flickers quite heavy and has a lot of jpeg-like comression artifacts, but as I can remember I selected MJPEG as streaming format. I will
try to switch to YUY2 but that makes the data size quite big for my wlan connection and might interfere guiding while ekos is downloading finished images.
Nevertheless I did a 10 minutes exposure and the stars still looked quite round .
bildschirmfoto_2017-09-19_08-18-57.png

@knro
Is it possible to change the decimals of the "Exp:" doublespinbox from 2 to 4? Because I can set my cameras exposure only in 100 steps (Exp: 0,01 = 100), but
with this cam I really need singe steps adjustments (Exp: 0,0001 = 1) . You dont need to change that in kstars for anyone because I think I am the only one with that strange crappy settings behaviour, so I would change the code on my git clone only. But I couldn't find the location where to put QDoubleSpinBox::setDecimals(4)...

Read More...

pauledd replied to the topic 'v4l2 CCD & guiding issue' in the forum. 4 days ago

Oh, ok, I didn't knew that the values are related. I try next clear night.

I have another problem. My guide scope is only 180mm focal lenght and I set under calibration settings
Pulse to max 5000 and Iteration also to max 10. Even with that settings the guide star moves only a tiny bit
compared to the whole image frame during the whole calibration, so I ve a ~50% of the calibration fails due to the star not moving enough. Is there something I can do/tweak further to make the guide star move more? Because I read a lot of people use their 8x50 viewfinder as a guide scope without issues.

Read More...

pauledd replied to the topic 'v4l2 CCD & guiding issue' in the forum. 4 days ago

well, on my RPi2 (were the cam is connected) I've running latest stable kernel for raspberry from git:
4.4.20-raspberrypi-v7+
On my kstars client I've kernel 4.11.1.

Ive not really a performance issue, more an settings issue.

I just run "v4l2-compliance" on the device and I get:

...
Control ioctls:
                fail: v4l2-test-controls.cpp(74): def < min || def > max
                fail: v4l2-test-controls.cpp(204): invalid control 00980900
                test VIDIOC_QUERY_EXT_CTRL/QUERYMENU: FAIL
                fail: v4l2-test-controls.cpp(306): node->controls.find(qctrl.id) == node->controls.end()
                test VIDIOC_QUERYCTRL: FAIL
                test VIDIOC_G/S_CTRL: OK
                fail: v4l2-test-controls.cpp(576): g_ext_ctrls worked even when no controls are present
                test VIDIOC_G/S/TRY_EXT_CTRLS: FAIL
                test VIDIOC_(UN)SUBSCRIBE_EVENT/DQEVENT: OK (Not Supported)
                test VIDIOC_G/S_JPEGCOMP: OK (Not Supported)
                Standard Controls: 0 Private Controls: 0
...
Total: 43, Succeeded: 39, Failed: 4, Warnings: 1

And "v4l2-ctl --all" gives:
Driver Info (not using libv4l2):
        Driver name   : uvcvideo
        Card type     : USB 2.0 Camera
        Bus info      : usb-3f980000.usb-1.5.3
        Driver version: 4.4.20
        Capabilities  : 0x84200001
                Video Capture
                Streaming
                Extended Pix Format
                Device Capabilities
        Device Caps   : 0x04200001
                Video Capture
                Streaming
                Extended Pix Format
Priority: 2
Video input : 0 (Camera 1: ok)
Format Video Capture:
        Width/Height      : 800/600
        Pixel Format      : 'YUYV'
        Field             : None
        Bytes per Line    : 1600
        Size Image        : 960000
        Colorspace        : sRGB
        Transfer Function : Default
        YCbCr/HSV Encoding: Default
        Quantization      : Default
        Flags             : 
Crop Capability Video Capture:
        Bounds      : Left 0, Top 0, Width 800, Height 600
        Default     : Left 0, Top 0, Width 800, Height 600
        Pixel Aspect: 1/1
Selection: crop_default, Left 0, Top 0, Width 800, Height 600
Selection: crop_bounds, Left 0, Top 0, Width 800, Height 600
Streaming Parameters Video Capture:
        Capabilities     : timeperframe
        Frames per second: 20.000 (20/1)
        Read buffers     : 0
                     brightness (int)    : min=-64 max=64 step=1 default=-8193 value=0
                       contrast (int)    : min=0 max=64 step=1 default=57343 value=0
                     saturation (int)    : min=0 max=128 step=1 default=57343 value=0
                            hue (int)    : min=-40 max=40 step=1 default=-8193 value=0
 white_balance_temperature_auto (bool)   : default=1 value=0
                          gamma (int)    : min=72 max=500 step=1 default=57343 value=72
                           gain (int)    : min=0 max=100 step=1 default=57343 value=0
           power_line_frequency (menu)   : min=0 max=2 default=1 value=0
      white_balance_temperature (int)    : min=2800 max=6500 step=1 default=57343 value=2800
                      sharpness (int)    : min=0 max=6 step=1 default=57343 value=0
         backlight_compensation (int)    : min=0 max=2 step=1 default=57343 value=0
                  exposure_auto (menu)   : min=0 max=3 default=0 value=1
              exposure_absolute (int)    : min=1 max=5000 step=1 default=157 value=2000
         exposure_auto_priority (bool)   : default=0 value=0

The weirdness starts at "brightness"... min -64 max +64.. so I would expect default at 0 but it is at -8192???. Same for contrast, saturation,hue and so on. And It doesnt matter where I put the cam on. Even on my Client PC with the 4.11.1. kernel I get the same behaviour so I think its not a kernel issue. May the cam's firmware or the part of electronics that stores the default values is simply crappy...

Read More...

pauledd replied to the topic 'HFR DSLR & FWHM' in the forum. 4 days ago

My HFR did also improve the last session to 2.3, but I had to focus manually. I think I need to tweak the step size in ekos and/or if possible, smaller step size in the astroberry focuser code, my stepper currently run at 1/2 step size...

Read More...

pauledd thanked nMAC in topic HFR DSLR & FWHM 4 days ago
pauledd replied to the topic 'v4l2 CCD & guiding issue' in the forum. 5 days ago

This camera (ov2710-1E) drives me crazy! Or maybe its the linux uvc driver... Even if I try to set exposure directly with v4l2-ctl it does weird things.
First, if I set exposure step by step from 0 to 20 the image gets brighter from 0-10. Then from 11 its dark again and gets brighter again to 20... I could repeat up to +5000. So the controls seems not to increase linear.
Second, if I list all controls ranges and look for the default values some of them are totaly out of bounds. Maybe the camera is reporting back wrong values.

Because of that and its bad low light performance I think I give up on that cam and going to effort an ASI174MM early next year or chistmas. I hope this cam will give me a more distinct control over exposure adjustments and more guiding stars...

Read More...

pauledd created a new topic ' v4l2 CCD & guiding issue' in the forum. 6 days ago

I dug out my USB-Webcam to prepare a new guiding test.
I have quite an issue:
If I start streaming the V4L2 CCD device I can adjust all image settings in the "V4l2 Control" tab and watch it live in the stream window.
The problem is if I then stop streaming and go to the EKOS Guide tab and do a CAPTURE
all controls in the image adjustments return to some kind of weird default value. For example
the exposure value jumps from my adjusted 7 to 5000... making a total overexposured image and guiding impossible. Also if I press LOOP in the guiding tab I cant adjust the v4l2 image parameters, they immediately jump back to the weird vales.

I made a video that shows the issue:
[video]
Anyone else having this problem?

Read More...

pauledd replied to the topic 'HFR DSLR & FWHM' in the forum. 7 days ago

1.2 - 1.5 ... wow okay. I usually use ISO400 and 0.5seconds to focus and as you wrote medium to small stars. But I live in a slight valley in a mid-big city with a river in fromt of my telescope, so I would not expect a much lower HFR here dye to atmospheric conditions but I am still practizing all the stuff :)

Read More...

pauledd replied to the topic 'HFR DSLR & FWHM' in the forum. 7 days ago

Thanks, I found a good short explanation:
www.diffractionlimited.com/help/maximdl/Half-Flux.htm

Read More...

pauledd created a new topic ' HFR DSLR & FWHM' in the forum. 7 days ago

Hi

While playing with my focuser and my Canon 700D I wonder what the "HFR" value actually means?
Is it related somehow with the "FWHM" that I can analyse on stars in my preprocessing
software?

What HFR values would you expect with your DSLR similar to my Canon700D?
My best HFR on my 150/600 Newton with the Canon was ~3.6.

Read More...

pauledd replied to the topic 'astrometry Solver failed' in the forum. 3 weeks ago

I updated kstars and reinstalled astrometry from git, I still get the error:

I use ccd/telescope-simulators to "load&slew" a fits to test solve.

log window:

2017-08-31T08:42:45 Solver failed. Try again.
2017-08-31T08:42:45 Field center: (RA,Dec) = (148.884788, 69.073028) deg.
Field center: (RA H:M:S, Dec D:M:S) = (09:55:32.349, +69:04:22.902).
Field size: 2.34511 x 1.56542 degrees
Field rotation angle: up is -173.251 degrees E of N
Field parity: neg
Creating new FITS file "/home/paul/astro/ekos/ballplantzAus.new"...
2017-08-31T08:42:45 Field: /home/paul/astro/ekos/ballplantzAus.fits
2017-08-31T08:42:45 Field 1: solved with index index-4211.fits.
Field 1 solved: writing to file /home/paul/astro/ekos/ballplantzAus.solved to indicate this.
2017-08-31T08:42:45 log-odds ratio 87.0142 (6.16277e+37), 11 match, 0 conflict, 19 distractors, 15 index.
  RA,Dec = (148.886,69.0735), pixel scale 1.62084 arcsec/pix.
  Hit/miss:   Hit/miss: ++-+---+----+--------++---++++(best)----------------------------------------------------------------------
2017-08-31T08:42:45 Field 1 did not solve (index index-4212.fits, field objects 1-10).
2017-08-31T08:42:45 Field 1 did not solve (index index-4213.fits, field objects 1-10).
2017-08-31T08:42:45 Only searching for solutions within 15 degrees of RA,Dec (135,69)
2017-08-31T08:42:45 Reading file "/home/paul/astro/ekos/ballplantzAus.axy"...
2017-08-31T08:42:08 Solving...
2017-08-31T08:42:08 Reading sort column "FLUX"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
Done
2017-08-31T08:42:08 simplexy: found 2739 sources.
2017-08-31T08:42:06 Downsampling by 2...
2017-08-31T08:42:06 Extracting sources...
2017-08-31T08:42:06 Reading input file 1 of 1: "/home/paul/astro/ekos/ballplantzAus.fits"...
2017-08-31T08:42:06 /usr/bin/solve-field -O --no-plots --no-verify --resort --downsample 2 -3 135 -4 69 -5 15 -L 84.5429 -H 154.817 -u aw --config /usr/etc/astrometry.cfg -W /tmp/solution.wcs /home/paul/astro/ekos/ballplantzAus.fits
2017-08-31T08:42:06 Starting solver...
2017-08-31T08:42:06 Solver iteration #1
2017-08-31T08:42:06 Using solver options: -O --no-plots --no-verify --resort --downsample 2 -3 135 -4 69 -5 15 -L 84.5429 -H 154.817 -u aw

I tried the same fits from the command line and thats what I get:
LANG=en solve-field -O -z 2 -p ~/astro/ekos/ballplantzAus.fits  
Reading input file 1 of 1: "/home/paul/astro/ekos/ballplantzAus.fits"...
Extracting sources...
Downsampling by 2...
simplexy: found 2739 sources.
Solving...
Reading file "/home/paul/astro/ekos/ballplantzAus.axy"...
Field 1 did not solve (index index-4219.fits, field objects 1-10).
Field 1 did not solve (index index-4218.fits, field objects 1-10).
Field 1 did not solve (index index-4217.fits, field objects 1-10).
Field 1 did not solve (index index-4216.fits, field objects 1-10).
Field 1 did not solve (index index-4215.fits, field objects 1-10).
Field 1 did not solve (index index-4214.fits, field objects 1-10).
Field 1 did not solve (index index-4213.fits, field objects 1-10).
Field 1 did not solve (index index-4212.fits, field objects 1-10).
  log-odds ratio 87.0142 (6.16277e+37), 11 match, 0 conflict, 19 distractors, 15 index.
  RA,Dec = (148.886,69.0735), pixel scale 1.62084 arcsec/pix.
  Hit/miss:   Hit/miss: ++-+---+----+--------++---++++(best)----------------------------------------------------------------------
Field 1: solved with index index-4211.fits.
Field 1 solved: writing to file /home/paul/astro/ekos/ballplantzAus.solved to indicate this.
Field: /home/paul/astro/ekos/ballplantzAus.fits
Field center: (RA,Dec) = (148.884788, 69.073028) deg.
Field center: (RA H:M:S, Dec D:M:S) = (09:55:32.349, +69:04:22.902).
Field size: 2.34511 x 1.56542 degrees
Field rotation angle: up is -173.251 degrees E of N
Field parity: neg
Creating new FITS file "/home/paul/astro/ekos/ballplantzAus.new"...
Speicherzugriffsfehler (segmentation fault)
I dont know why this happens but maybe this is simply because the git code is "work in progress".
So it solves the image but it cannot create this *.new file. Maybe thats the point where ekos says "solver failed".
I really dont want to dig deeper in astrometry git code or search my whole system again for errors, from now I will simply use the 0.70 version.

Read More...

pauledd replied to the topic 'glowing in the dark (mirror up) on canon' in the forum. 3 weeks ago

Oh so I was doing it wrong the whole time... I will stop using it for now.
Thanks for the enlightenment!

Read More...

pauledd created a new topic ' glowing in the dark (mirror up) on canon' in the forum. 3 weeks ago

Hi

Just a side note. Yesterday I took a series of dark frames with my Canon EOS 700D. I normaly
do this right after the lights frames. I tried to do the light frames with "mirror up" function and for my understanding
it can be enabled in ekos by

mirror_up_ekos.jpg

So it came to the darks and I still had viewfinder "on" and thats what I get when I do darks with mirror up:

dark_mirror_up_glow.jpg

I spend hours to find out what was the cause of this until I remembered the mirror up.
So my whole series was a useless set of darks with some strange glow on the lower right side. I have no idea why this happens.
Canon users, just be warned.
where this comes from.

Read More...

pauledd thanked Jasem Mutlaq in topic astrometry Solver failed 3 weeks ago
pauledd replied to the topic 'astrometry Solver failed' in the forum. 3 weeks ago

Thanks, will try tomorrow.

Read More...

pauledd replied to the topic 'astrometry Solver failed' in the forum. 3 weeks ago

I get nothing, thats why I added "--help".

Without grep I get this (on the git version):

paul@Gummi ~/build/astrometry.net $ solve-field
ERROR: You didn't specify any files to process.


Read More...

pauledd replied to the topic 'astrometry Solver failed' in the forum. 3 weeks ago

I reverted to Revision 0.70 and it solves now offline.
Its maybe not always a good idea to use git versions...:dry:

Read More...

pauledd replied to the topic 'astrometry Solver failed' in the forum. 3 weeks ago

sure, its from git:
solve-field --help | grep Revision
Revision 0.72-10-g55c1d51c, date Thu_Aug_17_21:29:50_2017_+0000.

Read More...

pauledd created a new topic ' astrometry Solver failed' in the forum. 3 weeks ago

Hi

In the past days I updated everything (kstars, astrometry, indi) and now ekos cannot solve locally anymore.
But in the log I can clearly see that it was successful with solving

[2017-08-29T21:01:28.163 CEST INFO ][     org.kde.kstars.ekos.align] - "Field 1: solved with index index-4109.fits."
[2017-08-29T21:01:28.172 CEST INFO ][     org.kde.kstars.ekos.align] - "Field 1 solved: writing to file /tmp/fitsLR1683.solved to indicate this."
[2017-08-29T21:01:28.186 CEST INFO ][     org.kde.kstars.ekos.align] - "Field: /tmp/fitsLR1683"
[2017-08-29T21:01:28.188 CEST INFO ][     org.kde.kstars.ekos.align] - "Field center: (RA,Dec) = (144.953336, 81.804515) deg.\nField center: (RA H:M:S, Dec D:M:S) = (09:39:48.801, +81:48:16.252).\nField size: 2.34263 x 1.56456 degrees\nField rotation angle: up is -170.427 degrees E of N\nField parity: neg\nCreating new FITS file \"/tmp/fitsLR1683.new\"..."

In the log I get this:
[2017-08-29T20:58:11.379 CEST INFO ][     org.kde.kstars.ekos.align] - "Starting solver..."
[2017-08-29T20:58:11.379 CEST INFO ][     org.kde.kstars.ekos.align] - "/usr/bin/solve-field -O --no-plots --no-verify --resort --downsample 2 -L 89.2398 -H 147.78 -u aw --config /usr/etc/astrometry.cfg -W /tmp/solution.wcs /tmp/fitsmK1683"
[2017-08-29T20:58:11.402 CEST INFO ][     org.kde.kstars.ekos.align] - "Reading input file 1 of 1: \"/tmp/fitsmK1683\"..."
[2017-08-29T20:58:11.656 CEST INFO ][     org.kde.kstars.ekos.align] - "Extracting sources..."
[2017-08-29T20:58:11.689 CEST INFO ][     org.kde.kstars.ekos.align] - "Downsampling by 2..."
[2017-08-29T20:58:13.888 CEST INFO ][     org.kde.kstars.ekos.align] - "simplexy: found 2512 sources."
[2017-08-29T20:58:14.160 CEST INFO ][     org.kde.kstars.ekos.align] - "Reading sort column \"FLUX\"\nSorting sort column\nmmapping input file\nCopying table header.\nWriting row 0\nDone"
[2017-08-29T20:58:14.247 CEST INFO ][     org.kde.kstars.ekos.align] - "Solving..."
[2017-08-29T20:58:14.253 CEST INFO ][     org.kde.kstars.ekos.align] - "Reading file \"/tmp/fitsmK1683.axy\"..."
[2017-08-29T21:01:11.311 CEST INFO ][     org.kde.kstars.ekos.align] - "Solver timed out"
[2017-08-29T21:01:11.314 CEST INFO ][     org.kde.kstars.ekos.align] - "Capturing image..."
[2017-08-29T21:01:11.492 CEST INFO ][           org.kde.kstars.indi] - GPhoto CCD :  "Starting 5 sec exposure "
[2017-08-29T21:01:21.293 CEST INFO ][           org.kde.kstars.indi] - GPhoto CCD :  "Exposure done, downloading image... "
[2017-08-29T21:01:22.118 CEST INFO ][           org.kde.kstars.fits] - Loading FITS file  "/tmp/fitsLR1683"
[2017-08-29T21:01:22.538 CEST INFO ][     org.kde.kstars.ekos.align] - "Image received."
[2017-08-29T21:01:22.542 CEST INFO ][     org.kde.kstars.ekos.align] - "Starting solver..."
[2017-08-29T21:01:22.542 CEST INFO ][     org.kde.kstars.ekos.align] - "/usr/bin/solve-field -O --no-plots --no-verify --resort --downsample 2 -L 89.2398 -H 147.78 -u aw --config /usr/etc/astrometry.cfg -W /tmp/solution.wcs /tmp/fitsLR1683"
[2017-08-29T21:01:22.547 CEST INFO ][     org.kde.kstars.ekos.align] - "Reading input file 1 of 1: \"/tmp/fitsLR1683\"..."
[2017-08-29T21:01:22.770 CEST INFO ][     org.kde.kstars.ekos.align] - "Extracting sources..."
[2017-08-29T21:01:22.801 CEST INFO ][     org.kde.kstars.ekos.align] - "Downsampling by 2..."
[2017-08-29T21:01:25.041 CEST INFO ][     org.kde.kstars.ekos.align] - "simplexy: found 2090 sources."
[2017-08-29T21:01:25.141 CEST INFO ][     org.kde.kstars.ekos.align] - "Reading sort column \"FLUX\"\nSorting sort column\nmmapping input file\nCopying table header.\nWriting row 0\nDone"
[2017-08-29T21:01:25.229 CEST INFO ][     org.kde.kstars.ekos.align] - "Solving..."
[2017-08-29T21:01:25.264 CEST INFO ][     org.kde.kstars.ekos.align] - "Reading file \"/tmp/fitsLR1683.axy\"..."
[2017-08-29T21:01:28.085 CEST INFO ][     org.kde.kstars.ekos.align] - "log-odds ratio 423.957 (1.32459e+184), 55 match, 0 conflict, 42 distractors, 63 index.\n  RA,Dec = (144.959,81.8046), pixel scale 1.62258 arcsec/pix.\n  Hit/miss:   Hit/miss: ++++++++++++++++++++++++++++++-+--+++--+++--+-++-+++-+++---+-++--+-+---+-------+----------+-----+(best)---"
[2017-08-29T21:01:28.163 CEST INFO ][     org.kde.kstars.ekos.align] - "Field 1: solved with index index-4109.fits."
[2017-08-29T21:01:28.172 CEST INFO ][     org.kde.kstars.ekos.align] - "Field 1 solved: writing to file /tmp/fitsLR1683.solved to indicate this."
[2017-08-29T21:01:28.186 CEST INFO ][     org.kde.kstars.ekos.align] - "Field: /tmp/fitsLR1683"
[2017-08-29T21:01:28.188 CEST INFO ][     org.kde.kstars.ekos.align] - "Field center: (RA,Dec) = (144.953336, 81.804515) deg.\nField center: (RA H:M:S, Dec D:M:S) = (09:39:48.801, +81:48:16.252).\nField size: 2.34263 x 1.56456 degrees\nField rotation angle: up is -170.427 degrees E of N\nField parity: neg\nCreating new FITS file \"/tmp/fitsLR1683.new\"..."
[2017-08-29T21:01:28.188 CEST INFO ][     org.kde.kstars.ekos.align] - "Solver failed. Try again."

If I switch to online solver it solves it.

Any ideas anyone?

Attached Full log

Read More...

Login



3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!