Amazing! Thank you, I had a feeling it might have been something like that, as you mentioned the base classes have gone through a ton of updates, my next step before seeing this was going to be to recompile kstars/ekos.

Would that fix the problem?

Read More...

Thanks for the advice Wouter. I wasn't clear enough, am also getting the same bug/crash on EQModI. The point of mentioning other drivers is that it appears that this crashing behaviour is more widespread than a single driver and therefor might give us a clue as to where the problem was introduced.

Read More...

I'm having the same problem with NexDome and ASI driver from most recent build. Has anyone logged a defect on Github?

Read More...

It's a great idea - again how it's implemented is less of a big deal than that the Camera and Filterwheel driver are able to communicate. I'll take a look at the code for implementing shutters and see how easy it is to hack (suspect the naming convention will be a faster solution, that way the Filter Class doesn't need to be extended to add a checkbox, the camera just needs to snoop the Filterwheel driver to see if it's got a filter called "roblikeshissleep" ;-) (p.s. me too)

Read More...

Easy with the scheduler - simply setup a Sequence with your simple pattern (3/1/1/1) and then get teh Scheduler to "Repeat" the sequence 10 times.

Personally and from experience, I WOULD NOT recommend it for two reasons;
#1 Flats. In my experience unless you've got a very accurate filter wheel, the chances of it changing dust patterns between shots is high every time you move the filter position. at a minimum set your wheel to be unidirectional, helps to counteract backlash.
#2 Focus. Unless you're confident in your filters being par focal, you're going to need to adjust focus for each change, again, this might require a lengthly refocus routine unless you have a very accurate focuser able to move between focus offsets 9this becomes more important at faster f-ratios where the CFD is tiny).

There is a good reason to take the approach you outlined and that is of course that you are more likely to get even sky coverage from shot to shot but this brings me to my final piece of advice;
#3 - shoot one filter per night, with multiple targets if you've got time to kill versus multiple filters one target - that way you get consistent elevations per target per filter, at the risk of being clouded over the following night. Having said that I know people who've been shooting the same target for years at a time, building up data as they go.

If this sounds like Mono+filters is more complicated and fiddly than OSC, it's because it is - shooting with filters is really rewarding but it's a more methodical mindset than OSC.

Read More...

Amazing! Such a simple idea, but effective!

Read More...

Great suggestion! I meant to include this as a feature request in the kstars Git.

TheSkyX has a similar feature, if a filter slot is given the description/name !shutter!, then TSX uses that filter slot as a substitute for a mechanical shutter when taking darks.

A great idea and one that would be awesome in Kstars/Ekos (not sure if INDI would end to change, I suspect not).

Read More...