Greg replied to the topic 'Troubleshooting lost guide star' in the forum. 3 days ago

Maybe, but I don't think so. I had a 64x64 box set in the guide module (above I said 36x36 - edited for accuracy). I've seen other stars fit in a sub like that in the past, so that would make it possible. However, if I compare the center of the two subs from the main camera as ONE (where I wanted to be centered) and TWO (where I ended up) it's too far. In fact, that motion takes the center of ONE right off the guide chip. Yet, the log only shows it being out by ~37 pixels (assuming that is what diff refers to - can someone confirm?).

[2018-02-21T03:44:07.331 MST DEBG ][     org.kde.kstars.ekos.guide] - -------> BEFORE ROTATION Diff RA:  -27.001  DEC:  36.9

Here's an example - screencap from kstars with a FOV of the guider. My guider is on-axis (ONAG) so this is the FOV my guider sees.

This is centered on ONE:



And centered on TWO:



If you flip the images in my earlier post you can see that the stars move that amount.

Very interesting.

Read More...

Greg replied to the topic 'Troubleshooting lost guide star' in the forum. 3 days ago

Logfile attached.

File Attachment:

File Name: guiding_gone_mad_2018-02-21-2.zip
File Size: 2,457 KB


Read More...

Greg created a new topic ' Troubleshooting lost guide star' in the forum. 3 days ago

I was asleep and didn't witness it. That's a good thing, right? Nevertheless, it seems I lost the guide star, or at least guiding just stopped working. Ekos aborted guiding and restarted automatically. Guiding resumed and the next image began. Also a good thing. But, I found my subs on either side looked like this:

I'm posting this both in search of ideas (below) and in hopes that others might benefit from ideas around troubleshooting guiding.

Properly centered:



Uh, what? Calculating the center of the two shows they're 0.20 degrees off from each other. Wow.


Checking the logs, I see this event directly between these two subs:
[2018-02-21T03:44:07.330 MST DEBG ][     org.kde.kstars.ekos.guide] - Received guide frame.
[2018-02-21T03:44:07.330 MST DEBG ][     org.kde.kstars.ekos.guide] - Tracking Square  QRect(22,4 32x32)
[2018-02-21T03:44:07.331 MST DEBG ][     org.kde.kstars.ekos.guide] - ################## BEGIN PROCESSING ##################
[2018-02-21T03:44:07.331 MST DEBG ][     org.kde.kstars.ekos.guide] - Star    X :  37.1411  Y  :  19.6493
[2018-02-21T03:44:07.331 MST DEBG ][     org.kde.kstars.ekos.guide] - Reticle X :  71.6676  Y  : 66.8336
[2018-02-21T03:44:07.331 MST DEBG ][     org.kde.kstars.ekos.guide] - Star    RA:  29.0457  DEC:  15.3665
[2018-02-21T03:44:07.331 MST DEBG ][     org.kde.kstars.ekos.guide] - Reticle RA:  56.0468  DEC:  52.2665
[b][2018-02-21T03:44:07.331 MST DEBG ][     org.kde.kstars.ekos.guide] - -------> BEFORE ROTATION Diff RA:  -27.001  DEC:  36.9
[2018-02-21T03:44:07.331 MST DEBG ][     org.kde.kstars.ekos.guide] - -------> AFTER ROTATION  Diff RA:  27.1894  DEC:  -36.761[/b]
[2018-02-21T03:44:07.331 MST DEBG ][     org.kde.kstars.ekos.guide] - RA channel ticks:  22  DEC channel ticks:  22
[2018-02-21T03:44:07.331 MST DEBG ][     org.kde.kstars.ekos.guide] - Processing Axes
[2018-02-21T03:44:07.331 MST DEBG ][     org.kde.kstars.ekos.guide] - At # 22 drift[ 0 ][ 22 ] =  27.1894  , t_delta:  27.1894
[2018-02-21T03:44:07.331 MST DEBG ][     org.kde.kstars.ekos.guide] - delta         [ 0 ]=  27.1894
[2018-02-21T03:44:07.331 MST DEBG ][     org.kde.kstars.ekos.guide] - drift_integral[ 0 ]=  9.75255
[2018-02-21T03:44:07.331 MST DEBG ][     org.kde.kstars.ekos.guide] - pulse_length  [ 0 ]=  3624
[2018-02-21T03:44:07.331 MST DEBG ][     org.kde.kstars.ekos.guide] - Direction     :  Decrease RA
[2018-02-21T03:44:07.331 MST DEBG ][     org.kde.kstars.ekos.guide] - At # 22 drift[ 1 ][ 22 ] =  -36.7613  , t_delta:  -36.7613
[2018-02-21T03:44:07.331 MST DEBG ][     org.kde.kstars.ekos.guide] - delta         [ 1 ]=  -36.7613
[2018-02-21T03:44:07.331 MST DEBG ][     org.kde.kstars.ekos.guide] - drift_integral[ 1 ]=  -12.5693
[2018-02-21T03:44:07.331 MST DEBG ][     org.kde.kstars.ekos.guide] - pulse_length  [ 1 ]=  4900
[2018-02-21T03:44:07.331 MST DEBG ][     org.kde.kstars.ekos.guide] - Direction     :  Decrease DEC
[2018-02-21T03:44:07.331 MST DEBG ][     org.kde.kstars.ekos.guide] - ################## FINISH PROCESSING ##################
[b][2018-02-21T03:44:07.332 MST DEBG ][     org.kde.kstars.ekos.guide] - Aborting "Guiding"[/b]

Guiding aborted, presumably because the guide star moved outside of the box (36x36). I'll be testing guiding without a box the next good night of weather. Regardless, I like to know how and why a system does the things that it does.

I happen to log RA/Dec to a different system every 10 seconds and noticed that both diverged in a very short time frame in between the two subs above. No slew commands were captured, so the input must have been from the guiding system in Ekos:



And here is the result of the diffs in the Ekos log file during the entire evening:



And for reference, what it looked like in a normal state:



So, in spite of all of this data I can still only guess:

- Maybe clouds came through? Some of the subs suggest it as a possibility but I'm not sure of it.
- Did the quality of the guide star change somehow?
- Did the guide star really move? Not sure - sometimes I find it guiding or focusing on nothing.
- Did the mount slew or otherwise get moved? External logs show the mount did not slew, but RA and Dec did adjust by way of guiding.

Is there any other data point I'm missing? If not, it might be good to have two things for the wish list:

- A way to log the quality of the guide star. Perhaps ADU count of the guide star from guide frame to guide frame would be good?
- Also nice - the RA & Dec of the guide star used!

- Greg

Read More...

Greg replied to the topic 'Difficulties With Dithering' in the forum. 3 days ago

knro wrote: Checking the logs it looks like that the dithering process was proceeding normally, but capture was not triggered for some reason. Anyone having similar issues with dither?


I see that. It captures for several iterations, then it doesn't.

I just checked my log files from last night. All appears to be fine.

Read More...

Greg replied to the topic 'Auto Select Star failing frequently on guiding and focusing' in the forum. 1 week ago

Just build and tested the latest git pull. In this case, the sequence bins as before, but no subframing occurs for any of the subs. Logfile attached.

Read More...

Greg replied to the topic 'Auto Select Star failing frequently on guiding and focusing' in the forum. 2 weeks ago

If we don't need stars I guess dust donuts will do. I pointed at my flat panel and let ambient light illuminate it. Results....

NOTE: I don't use binning for focusing or alignment, so I'm not sure if this is relevant. I only use binning on my guide camera (SX Ultrastar). I did not test that one yet.

I set up an image capture as follows:
- Light001 binned 2x2 full frame
- Light002 binned 2x2, subframe set to coords 1790,1448 with 1000x1000 size <- did not subframe!
- Light003 binned 1x1, subframe as above <- did not subframe!
- Light004 binned 2x2, subframe as above <- subframed
- Light004 binned 1x1, subframe set as above <- subframed

Fits files, log files, and the .esq file are here:

www.dropbox.com/sh/p0zgs1vl5td91hn/AAAS5...IzQQGIbCWmKBZZa?dl=0

I'm going to run this with the guide camera to see what happens.

Read More...

Greg replied to the topic 'Auto Select Star failing frequently on guiding and focusing' in the forum. 2 weeks ago

I'll give those tests a shot once the weather clears up. In the meanwhile, I've attached the focus log that goes with the images above. I didn't trim it. The first focusing attempt is the one that resulted in no stars. The second is after I reset it. Some observations:

- The subframes are close to each other but do not overlap.
- If I use pixinsight and create a preview for each subframe on the full field one of them has a star dead center and the other is just background
- The coordinate difference between these two subframes is +75,+51. This made me think of this post I made a few days ago, Although the axis are swapped, the numbers are interestingly identical. Hmm...

File Attachment:

File Name: focus_nostars.txt
File Size: 117 KB


Read More...

Greg replied to the topic 'Auto Select Star failing frequently on guiding and focusing' in the forum. 2 weeks ago

Happened again tonight. Here are some fits:

www.dropbox.com/sh/e705ujqttflnw2a/AADPE...t_a9Jyb9gEPxrna?dl=0

There's a full frame as captured by the focus module, and a sub that it picked with no stars. Finally, restarting it had it find a star. A sub of that found star is included. Focus completed at HRF 1.34.

Read More...

Greg replied to the topic 'Auto Select Star failing frequently on guiding and focusing' in the forum. 2 weeks ago

Thanks. I've rebuilt and will try again.

In the meanwhile I turned "Detect Stars in Image" on the guiding tab with the image I made the screenshot from above with. This is the result:



I see similar results with the focus module when it happens. There are two different cameras at play here. The main camera is an FLI ML16200, guider is an SX Ultrastar.

Read More...

Greg replied to the topic 'Auto Select Star failing frequently on guiding and focusing' in the forum. 2 weeks ago

Yeah, I thought the failure rate seemed kinda high. It always seems to happen when I'm not looking.

I have a guiding subframe that caused the failure last night still in the guide module, but when I open it in the fits viewer and save it, no other program (pixinsight, kstars, tsx) can open it. They all give an error. You can see the file here:

www.dropbox.com/s/l739tx3hpwzlhmy/nostars.fits?dl=0

Here's a screen capture of it. I've see it have a star in the subframe and miss selecting it too. The focus module sometimes selects multiple close stars as a single star. A good example is the trapezium in M42.



Read More...

Greg created a new topic ' Auto Select Star failing frequently on guiding and focusing' in the forum. 2 weeks ago

I've been having a bit of trouble with auto select star for focusing and guiding. About 35% of the time the guiding and/or focusing modules miss and select background with no stars. In these cases the focusing or calibration will be attempted regardless of no stars being present. When this happens I can abort and restart the process, and it usually finds a star when I do that. I often have to click "reset" on the focus tab to force it to get rid of the subframe (maybe always, not sure). Exposure length doesn't appear to be a problem as there are plenty of stars with good signal in these cases. Guider is set to 10s binned 2x2, and focusing is on L at 3 seconds, 1x1.

Any ideas on how to improve the success rate? I see mention of moving to sextractor for star identification. Maybe this is what is needed?

Read More...

Greg replied to the topic 'Scheduler Job Start Condition - add "Twilight"' in the forum. 2 weeks ago

It seems like ASAP does this. This was not immediately clear to me. I took it as "start immediately", which would then fail due to the job constraints.

Read More...

Greg created a new topic ' Dark frames - some with overscan, others without?' in the forum. 2 weeks ago

I captured some dark frames in two sets across two days. I noticed that the frames from the first day do not match the frames from the second day. The frames from the first day don't show any overscan area, and are 4500x3600. The frames from the second day are also 4500x3600 but appear to have a margin at the top of 51 pixels and at the left of 76 pixels. I presume this is the overscan area. This is how I've seen most of my images when captured with Ekos - with the margin. If I remove the margin in pixinsight, the hot pixels in both sets of subs line up. However, this leaves the second set with missing areas of pixels at the bottom and right side of the image. FITS headers look identical save for the timestamp and filter assignment. I have not seen this behavior with TheSkyX.

I have no idea what changed, or how to ensure this won't happen periodically. Logs don't show anything interesting but I didn't have debug on for the ccd.

My camera is an FLI ML16200. I'm running a build of Ekos from the git repository on Xenial, and the indiserver from git as well. It is possible that one set was running the git version of indi and the other was running from the PPA. I see no settings specific to overscan areas in the indi manager.

Any ideas?

Read More...

Greg created a new topic ' Scheduler Job Start Condition - add "Twilight"' in the forum. 2 weeks ago

It would be handy to have "Twilight" as a job start up condition, possibly with an offset. For example, "Start the job at Twilight +15m", etc.

This would also help prevent jobs from failing to start when the time is set prior to local astronomical twilight when the job constraint "twilight" is set. A condition where you might want this is if the job runs all night and you want it to stop at astronomical dawn.

Read More...

Greg replied to the topic 'CCD/Capture module Limit Settings greyed out' in the forum. 3 weeks ago

Finally a clear(ish) night. I ran a few test scheduled jobs.

The focus HFR value will auto-populate after a successful focusing run. However, once guiding calibration begins the HFR values reset to zero. The guiding value does not get set once guiding starts.

Read More...

Greg replied to the topic 'CCD/Capture module Limit Settings greyed out' in the forum. 3 weeks ago

OK. They are now able to be selected. Will continue to test. Thanks!

Read More...

Greg replied to the topic 'packages have unmet dependencies for kstars bleeding' in the forum. 4 weeks ago

What OS version? Presuming that you're on Ubuntu or a derivative, try:

sudo apt-get update
apt-get install --fix-missing


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!