It definitely should, if you enable 'autofocus' in the filter settings, as you have in your screenshot.
So far it always did this for me, independent of the 'refocus every ...' settings (I use auto and refocus every 0.8 degrees, and that works fine). This is without scheduler, only running a sequence from the 'capture' tab.

Read More...

Peter Sütterlin replied to the topic 'Issues with latest build' in the forum. 3 weeks ago

Hmm, doesn't work for me sad.png
Still crashes as soon as kstars is fully up.  I compiled ekosdebugger with debug symbols and ran it in gdb.  BT is attached, so it dies in DebuggerView::connectEkosDBus if I interpret that correctly(?).  Or is it an issue related to QTversions?  I'm running 5.15.2.
 

Read More...

This looks a lot like the issues I had with my CEM60EC.  The issue had been that after the dither two threads were trying to do guide exposures, terminating each other fast.  So the guide cycle had changed (in my case) from ~5s to 1.8s - and the EC mount doesn't like that, and started doing insane moves.  See this post and follow-ups.
However, Jasem had fixed that in a commit 3 weeks ago, so I'd expect that is taken care of....  Still it might be worth checking the logfile for exposure aborts...

 

Read More...

Peter Sütterlin replied to the topic 'Issues with latest build' in the forum. 4 weeks ago

No news on the crash.  Kstars ran without a single hickup all night.  Same binaries and sequence....
 

Read More...

Peter Sütterlin replied to the topic 'Re:Issues with latest build' in the forum. 4 weeks ago

Thanks for the explanation, Eric!
What I was talking about was when you just open KStars, then EKOS, and go to the scheduler tab.  I.e., with no sequence etc. loaded.  For me this looks like this:

 



The old versions showed todays (rather: tonights....) twilight limits where the red scribble is.  I always check(ed) this when starting up to have an idea about available time.  Or is there another place in kstars to get this info easily?

Read More...

Peter Sütterlin replied to the topic 'Issues with latest build' in the forum. 4 weeks ago

Hmm.   I even had it on disk already (ekosdebugger).  So I did a 'git pull' and generated a new executable.  But I don't get far.  It starts, I can select modules to track and launch kstars, and it starts logging some thread info, but then crashes

Cannot construct placeholder type QDBusRawType
Aborted (core dumped)
and the ekosdebugger window is gone.  gdb and kstars keep running, but as soon as I start up INDI, also kstars dies....
So I'll have to rely on coredump for now it looks.
 

Read More...

Peter Sütterlin replied to the topic 'Issues with latest build' in the forum. 4 weeks ago

Yeah, just wanted to report those somewhere - is there a specific issue tracker for his work, or is doing it here 'OK'?

As for the EKOS debugger - will have to see where to get it.  Is that on github somewhere?  Though a BT from gdb on the coredump (once I have a valid one....) should be OK, too, or not?
 

Read More...

Peter Sütterlin created a new topic ' Issues with latest build' in the forum. 4 weeks ago

I had an observing run with the latest git version of kstars (kstars-3.5.4-2157_g7498a113d, self compiled)
While stability had improved (3.5.4-2110_ga4b519ad1 was crashing repeatedly while just guiding), this one still died during focusing after the second filter change (which unfortunately costed me 50% of the rare good night sad.png ).
It died with a segfault, and even created a coredump.  But unfortunately systemd-coredump limits size to at most 2GB, not enough for kstars:

BFD: warning: /home/pit/core.kstars.1000.9e88338e5e684b33aa6b617f427a7e42.16666.1625442302000000 is truncated: expected core file size >= 3329597440, found: 2147483648
I've increased the limit now - or are such backtraces not too helpful?

Other things I noticed:
  • EKOS scheduler used to print the twilight times for the current day, but no longer does sad.png
  • The new colors of the additional catalogs have room for improvement.  E.g., I disabled the LDN catalog because that red color is completely killing the sky view (IMO, of course).  Unfortunately I found no place to change that color.  User error, or not implemented?
  • Right-clicking a target (e.g., to get the detail view), has always been a bit random when zoomed in.  But right now it's close to impossible for larger targets.  E.g., I view IC4628 at 4.9 degree FOV.  No matter where I click within that cyan diamond, it only tells 'Empty Sky'.  To 'find' the target, I first have to zoom out to around 37 degree FOV to get a 'match' on right-click on the second or third try....
  • For the above case (IC4628) the info-box in the upper right corner says (only) 'ESO 332-EN14' - not very helpful for most users, I'd assume.


Read More...

Peter Sütterlin replied to the topic 'Ekos Kstars issue' in the forum. 4 weeks ago

Go to Settings->EKOS, in the 'General' tab select 'independent window'. Probably do the same for the FITSViewer (in the FITS tab of Settings).
AFAIR you have to restart KStars for that to take effect.

Read More...

Just compiled latest git, including Jasems Patches of the last  days (48dcd0023a2d and 6337561bbc).

With those, BL and REVERSE settings are there again, jay!
 

Read More...