Great thx Rob. I tested last night, here is my feedback...
1. On startup I had 2 optical trains (OTs) created for me... Primary and Secondary. Primary was the main scope, Secondary was for my OAG. I initially assumed as I have 1 optical train (OAG) that I could remove the Secondary and select my guide cam as "Guider" in the OT (which was how Primary was created for me by the system). This is wrong. The "Guider" is the device receiving guide pulses so in my case needs to be the mount.
2. Having got past 1) I noticed that most of my default parameters on focus / align / guiding had not been carried across to 3.6.1 so I went through all tabs re-establishing parameters. Some parameters were carried across like GPG worm period so its a bit unclear which parameters are carried across and which aren't.
3. All devices connected correctly.
4. PA worked as expected.
5. Guiding was tricky due to intermittent cloud but worked I would say as expected.
5a. Varying number go guide stars > 10 worked as expected.
5b. Dark guiding worked but I couldn't discern any improvement but that may be because of tough guiding conditions. I think I need to play around with it some more as I probably didn't have it configured properly. Just 1 comment on dark guiding... it would be nice to have some feedback on the guiding screen that dark guiding is activated (or not). This is the same as GPG... the only way to tell whether its on/off is to look at the config setup.
6. Focus worked as expected.
7. Sky map worked as expected.
8. Capture worked as expected.
9. Mosaic tool worked as expected.
10. Scheduler worked as expected.
11. Meridian Flip worked as expected.
12. Ekos ran through the night without seg faulting despite some tough conditions.
13. I usually bring my scope indoors to take flats in the morning. I don't bother connecting my mount (as there's no point). With 3.6.1 if all devices in the OTs are not connected you can't do anything. So I connected my mount and usability returned. This is a limitation of OTs. Taking flats (once all devices are connected) worked as expected.
So overall I think 3.6.1 worked well for me last night.
I'm guessing you mean the backlash field in Focus (or in Indi on the focuser tab)?
There is a check in focus that the backlash field is activated if the focuser supports backlash and inactive otherwise. I had a quick look at the moonlight driver and it looks like it doesn't support backlash (although I'm not an expert here so could be wrong). I don't know if that is because the focuser doesn't support backlash or a limitation in the driver.
This would be consistent with you seeing that the field is inactive.
Focus should work fine with the 5 * Initial Step Size but will be a few seconds slower due to the "unnecessary" in/out focus movement. The "5" is hardcoded in the program so, at the moment, the only way to change it would be to build you own version of kstars.
Just out of interest what would you want to set it to?
There's nothing obvious that I can see in the log. You have focus, scheduler, capture and guiding all active at around the time. These segfaults are hard to diagnose unless you can catch where it is in debug at the time. I run focus at bin 2 but usually capture at bin 1 so if this is related to the problem it must be an edge case. Still, if you think its related you could try focus at bin 1 and see if you still get the issue.
Worth putting verbose mode on in the logging for the active modules to see if you can capture any more clues, and consider running kstars under some form of debugger (if you are able to).
The focus section of the kstars handbook is a good place to start...
Oh, nice. That should be great! I'm really interested to see some focus images. I can run them through star extraction. I have been doing some research to try to improve star detection with SEP so if this turns out to be a problem then I might be able to help a bit.
The software handles the backlash compensation. The exposure of backlash on the Mechanics tab is a convenience to avoid having to use the indi tab (both are kept in sync).
For L1P it works as follows:
Backlash: All mechanical devices with gears suffer from backlash. In a typical focuser there will be a dead zone where changing direction (e.g. from “in” to “out”) results in movement of the focuser by a few ticks, but no actual movement of the optical train.
The Linear 1 Pass algorithm (like the Linear algorithm) provides backlash compensation in the 2 places during an auto focus run when the focuser moves outwards:
The initial outward movement of Initial Step Size * Out Step Multiple at the start of the run.
When the inward pass is complete and Ekos has determined the best focus position and moves outward to it.
Linear 1 Pass will extend (by x ticks) the outward movement, and then, as a separate movement it will move inward by x ticks. So it always approaches the desired position in an inward direction.
There are 2 schemes that can be used:
Set Backlash to 0. Ekos will use a value of 5 * Initial Step Size.
Set Backlash > 0. EKOS will use this value in its backlash calculations. There will probably be instructions with your focuser for determining the value of Backlash. It is not necessary to set an exact value for either Linear or Linear 1 Pass to work correctly; all that is required is that the value set in Backlash is >= the actual backlash value. For example, if you measure backlash and get a value around 100, any value >=100 will work equally well. For example, set Backlash = 200.
So the Max Travel is there to protect the focuser from moving beyond its bounds and damaging itself. So I would set it high enough that it doesn't get "in the way" of an autofocus run otherwise you'll get compromised (=poor) results. Focus will persevere and try to do its best but the constraint is just unnecessary. As a guide set it to at least 2 * number steps * initial step size. Personally, I set mine way above this so I know it won't compromise the autofocus run.
I would always start focusing from near to focus. You can do this quite easily manually or get close enough and do an autofocus run and then that's the start point for the night.
As far as the 5s guide exposure I don't know what's going on there. Sounds strange. I was messaging Jasem earlier and he confirmed that setting ZWO CCD driver in the Indi profile would handle both cameras (which is what I do BTW). Have you got the latest version of the driver?
Happy to take a look at your focus pictures when you next try things. I'm guessing you have a scope with a central obstruction, hence the tricky situation with out of focus stars.
I had a quick look at the log...
Starting focus with Detection: "SEP" Algorithm: "Linear 1 Pass" Box size: 64 Subframe: no Autostar: yes Full frame: yes [ 5 %, 60 %] Step Size: 50 Threshold: 150 Gaussian Sigma: 1.5 Gaussian Kernel size: 5 Multi row average: 3 Tolerance: 1 Frames: 1 Maximum Travel: 200 Curve Fit: "Parabola" Use Weights: no R2 Limit: 0
A couple of things jump out at me.
1. Max Travel set to 200. Why is this so low? You are constraining the autofocus run. I would set it to 2000 (unless that gives you other issues). If the run is constrained then you won't get a proper curve. I also see log failures due to this.
2. Use weights = no. I would recommend setting this to yes.
If you send me a couple of focus frames (1 in focus, 1 as far out of focus as the autorun takes things) then I'll take a look at these. Be good if you can screenshot the SEP profile options you are using as well.
This is the option to check to save the focus images...
I see. I think if moving 50 steps is unpredictable (backlash aside) then you're going to struggle with autofocus in general, as all the algorithms assume some sort of predictability in the focuser. Maybe somebody else on here with an Olympus may have some tricks.
You can control the backlash movement by setting the backlash amount. When changing direction, the focuser will add this to the previously calculated movement. So you try playing around with this.
That said... what you were initially trying, the Linear algorithm, might be your best hope as it uses heuristics on the second past to try to stop at the best place rather than moving straight to a pre-calculated point.
Welcome to Ekos!
It looks like you're using the Linear algorithm. What you probably want is the Linear 1 Pass algorithm. Its also worth taking a look at the focus section of the Kstars manual...
Hope this helps!