Hi Damian,
it looks like the problem does not occur anymore in the upcoming 3.6.2. I tried the autofocus routine with a setup without a filter wheel and did not experience a crash.

Give it a try to compile KStars from sources, it's not that difficult for people who could use gdb :-)

If you need assistance, take a look here invent.kde.org/education/kstars/-/tree/master#building

HTH
Wolfgang

Read More...

Is there a log file available? That would be really helpful. It seems like the problem is around capturing a frame for focusing.

And, in case if not, what is your exact configuration? It sounds like you are using a color camera that does obviously does not require a filter wheel.

Read More...

Hi Gilles,
isn’t it possible to use the AUX1 port? Or do you use it already for focusing?

Wolfgang

Read More...

The sequence did not abort because the capture module already waited for a meridian flip to happen.

Read More...

The message is unusual, since it comes before the state MOUNT_FLIP_RUNNING is reached. From your log it looks like that the slew for the meridian flip wasn't initiated by EKOS.

Read More...

Doesn't sound good, Peter! Could you please provide the log of last night as well?

In your second log above there is one strange entry:

[2022-11-04T01:00:38.725 WET INFO ][     org.kde.kstars.ekos.guide] - "Mount is slewing. Aborting guide..."
This happens before the mount module initiates the slew to trigger the flip. Is it possible that your mount triggers the slew on its own outside of KStars/EKOS?

Since the mount slews before the meridian flip is issued, guiding aborts before the meridian flip is started by EKOS. Therefore, guiding is not restarted after the flip since EKOS thinks guiding wasn't running before the meridian flip.

Wolfgang

Read More...

If you want to run the same job twice, you need to increase the number of iterations of the second one. This is necessary as long as you have the „remember job progress“ selected.

The reason behind is that the number of repeats is used to calculate how many frames need to be captured until the job completes

Take a LLRGB capture sequence and set two repeats. Then this job will run as long as 4xL, 2xR, 2xG, 2xB is present. If this succeeds during the first night, the job will be completed. Otherwise, in the next night you can restart the job and it will run as long as all frames are present. If e.g. only one G is missing, it will capture exactly this frame.

If you add the same job twice, it will be completed as soon as the first one is completed.

What you mean is that with the second run you want to double the number of frames to be captured. Therefore you need to set the repeat value of the second job to the double value of the first one.

After the first one has completed, the second one will be considered. Before starting, the scheduler recognises that there are already some frames present and will run only as long as the calculated number of the second job have been captured.

This might sound complicated, but it gives you the option to restart jobs over several nights. If you want a strict behaviour without taking into account of existing frames, deselect the remember job progress option.

HTH
Wolfgang

Read More...

This is a “feature” that happens to those who used early versions of the optical trains implementation. It should happen only once per profile and should be gone if the workaround was applied once.

Read More...

Are you using the scheduler?

Read More...

That doesn’t sound nice. Please post your logs for further advice.

Cheers
Wolfgang

Read More...

Wolfgang Reissenberger replied to the topic 'custom mount' in the forum. 1 week ago

Hello Rui,
welcome to the INDI forum and greetings to Portugal!

I‘m not sure whether I understand your question. If you are using motors and goto controllers from an eq6 system on your custom built mount, it should work with the standard eqmod INDI driver, as long as your goto controller is not modified.

HTH
Wolfgang

Read More...

Sounds like remember job progress is selected. Try to add the job with 4 times. Then it will run twice again until it is completed.

The explanation is, that the number of repeats is used Tito calculate, how many frames should be captured. If there are already some present (from a previous night or from another job), these frames are considered and the job will only try to run until the overall amount is reached.

HTH
Wolfgang

Read More...

Wolfgang Reissenberger replied to the topic 'Issues with Ekos' in the forum. 1 month ago

Fixed in invent.kde.org/education/kstars/-/merge_requests/768.

Thanks for reporting it
Wolfgang

Read More...

Hi Simon,
take a look here, I guess that’s the explanation:
www.raspberrypi.com/news/bullseye-camera-system/

Wolfgang

Read More...