Wolfgang Reissenberger replied to the topic 'Re:Perfecting the Scheduler' in the forum. 2 days ago

Hi Eric,
reusing the interval would be great, this would resolve my problem.

-Wolfgang

Read More...

Wolfgang Reissenberger replied to the topic 'Re:Perfecting the Scheduler' in the forum. 1 week ago

Hi Eric,
I think it depends how the capture part is used. If it is used defining all captures for a single target, it makes sense having these features there. If it is used like I do where the capture part contains only one sequence and the scheduler defines how often it is repeated, at least the time-related features like re-focusing every x minutes is less helpful since one sequence is shorter than a typical re-focusing interval.

But maybe it makes sense to step back and think about the characteristics of the capture tab and the sequence tab. What do you think of the following:

  • The capture tab contains all aspects to ensure, that a certain amount of frames are taken with a defined quality. That means, HFR-based re-focusing and guiding-deviations belong to this tab.
  • The scheduler tab contains overall control and all time-related aspects. That means, time interval based re-focusing should belong to this tab, since such an interval is strictly time related and independent of a selected target. If we think this very consequently, I would propose shift meridian flipping here as well.

What do you think about this?

-Wolfgang
p.s.: forcing focusing before each sequence would not be very helpful in my case. One typical LLRGB sequence takes 2x8+3*4=28 min, that means every half an hour a re-focusing will occur. This is too often, so I would not be helpful. As a workaround, I will enlarge a single sequence so that it is slightly longer than the refocusing-interval.

Read More...

Wolfgang Reissenberger replied to the topic 'Perfecting the Scheduler' in the forum. 2 weeks ago

Hi Eric,
may I add one topic to the whish list? Currently, re-focussing is determined on the photography tab, where the single sequence is running. In my setup, a sequence is very simple: LLRGB - and then repeated by the scheduler. In the schedule I defined refocusing after 60min.
In this setup refocusing never happens, since one sequence takes 2*8+3*4min = 28min.

Would it not make more sense having these definitions on the scheduler side rather on the sequence tab?
Cheers
Wolfgang

Read More...

Hi Sergio,
I can confirm the problem, my Moravian G2-8300 with external filter wheel shows the same behavior.
My setup: Raspberry Pi 3b with Raspbian 9.0 and INDI 1.7.2.
Wolfgang

Read More...

Hi Markku,
you are right, Alt+Space is the magic combination.
Thanks a lot!
Wolfgang

Read More...

Wolfgang Reissenberger replied to the topic 'Re:Perfecting the Scheduler' in the forum. 2 months ago

Hi folks,
I am not sure whether I got all points right in the thread, so please excuse, if I bring up a topic here that is already addressed.

But first of all: the scheduler is THE killer application for me. Thanks a lot, it brings kstars on a completely new level.

Back to my problem. As far as I understood, when a job fails after several retries (for example during focussing), the job is marked as "ABORTED". But this might be too strict for example if clouds pass by.

So it could happen, that a certain job could not be executed for a while. If other jobs are present that could run, OK, let them run. But what happens, if all jobs are aborted? In my case, I only have one single job. In this case, EKOS is terminated, right? At least this happens in my case.

What would be the suggested behavior: I would like having a "retry after a certain amount of time" and restart the aborted job.

Does that make sense to you?
Cheers
Wolfgang

Read More...

Wolfgang Reissenberger replied to the topic 'Avalon mzero Stargo with lx200 protocol' in the forum. 2 months ago

Hi Ken,
feel free to submit a pull request. Any help is warmly welcome!
Wolfgang

Read More...

Wolfgang Reissenberger replied to the topic 'Avalon mzero Stargo with lx200 protocol' in the forum. 2 months ago

Hm, strange. Mine worked that way.
There are no fix plans when I shift it to INDI. Currently I am collaborating with CanisUrsa who takes care of the focuser part. When the focuser and the telescope are working on my repository it might be the right time to announce it for beta-testing and shift it to INDI.

Read More...

Wolfgang Reissenberger replied to the topic 'Avalon mzero Stargo with lx200 protocol' in the forum. 2 months ago

For setting the 4 speeds please use the ASCOM client. I haven't implemented changing the speeds yet.
Concerning pulse guiding: same thing, maybe it works occasionally, but I did not change the behavior of the underlying lx200telescope implementation. Does pulse guiding work?

Read More...

Yes, you are right. Under KDE it's working fine, LXDE has problems when the window is placed in the top left corner.

Wolfgang

Read More...

Hi,
I have small problems with the fits viewer tool under kstars 2.9.4 and Raspbian. The window of the fits viewer tool is placed on the top margin of the screen. It cannot be moved, since it has no window bar on top. The only option is to use File > Close.

Any hints?

Wolfgang

Read More...

Wolfgang Reissenberger replied to the topic 'Got no stars is gsc installed error' in the forum. 2 months ago

Thanks, great. I am using Raspbian, not Ubuntu. So I am afraid I have to build it from the sources.

Wolfgang

Read More...

Wolfgang Reissenberger replied to the topic 'Got no stars is gsc installed error' in the forum. 2 months ago

Aaaah, sorry, I just read the first posts. This one does not work anymore:
launchpad.net/~mutlaqja/+archive/ppa/+files/gsc_1.0.orig.tar.gz

Wolfgang

Read More...

Wolfgang Reissenberger replied to the topic 'Got no stars is gsc installed error' in the forum. 2 months ago

Hi Jasem,
the link does not work any more. Could you help, please?
Wolfgang

Read More...

Wolfgang Reissenberger replied to the topic 'KStars 2.9.3 on MacOS crashes during imaging' in the forum. 2 months ago

I could reproduce the crash last night. It seems that it corresponds to a restarted schedule. Initially, the schedule ran OK, but after I while kstars did not react any more - only the "spinning pizza" was turning. The strange thing: it nevertheless seems to work in the background - at least for a while.

After this, I killed kstars and restarted the (saved) schedule. The scheduler mentioned something about calibration frames and jumped directly to imaging - and crashed during the first image acquisition.

Is it possible that this behavior is created by an INDI version incompatibility? On the server I am using v1.7.0 plus my own Avalon driver, the client contains v1.6.8 or so of INDI.

After this crash I started kstars on my Raspberry which is running the server - and everything went flawlessly.

Wolfgang

Read More...

Wolfgang Reissenberger replied to the topic 'KStars 2.9.3 on MacOS crashes during imaging' in the forum. 2 months ago

OK, thanks for the hints. Tomorrow I am back home and can check, if I can find something in the console log. And skies should be fine, so I will go for the next session with debugging enabled.

Read More...

Wolfgang Reissenberger replied to the topic 'Avalon mzero Stargo with lx200 protocol' in the forum. 2 months ago

Thanks for the hint. I opened another thread here .

Wolfgang

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!