Peter Sütterlin replied to the topic 'Announcing StellarSolver 2.0' in the forum. 3 days ago

Hi Rob,

thanks for the explanation. Yes, I've switched to that branch to test it with my ASI183MC - I have it attached to a Canon FD lens, and first test gave me some star bloat. I hope that I get some improvement of the AF routine there with the new default, but also wanted to test it comparing green with all-channel average.

But then I'll (of course) patiently wait until the handles will show up in KStars :D

Read More...

Peter Sütterlin replied to the topic 'Announcing StellarSolver 2.0' in the forum. 3 days ago

Hi Rob,

just compiling kstars against the new colorChannels version :)
I wonder if there's a config file for the library that selects the default handling. Or is that fixed at compile time?

Read More...

Peter Sütterlin replied to the topic 'OAG FOV' in the forum. 7 days ago

In the 'FOV symbols' section you can create/edit one of the proper size, and give it an offset relative to the pointing coordinate. I did that when I used an OAG. Drawback is that it isn't linked to the sensor FOV, i.e., it will not flip to the other side when crossing the meridian. But you can create a second one for that.

Read More...

Try to discard any mount/pointing model you might have stored. And don't sync to anything close to the pole, this is a singular point, and slightest errors translate into massive deviations.

Read More...

That is similar to what I'm running, an EAF on the main scope, and an Pegasus DMFC on the secondary/guider. No issues with that.

I'd have expected that multiple EAF would work similar to multiple EFW. I have two, botha 5 and a 7 slot. If only one is connected it shows up as 'ASI EFW', if both are connected it's 'ASI EFW 0' and ASI EFW 1'. It's still easy to mess up the configuration though (I have a post here about that :( )
I think I never tried it with the EAF - I do have two of them, but at separate telescopes, so it's not an quick and easy test...

Read More...

I have two cameras connected to my computer, both with a ZWO filterwheel: An ASI2600 with the 36mm 7-filter wheel, and an ASI1600 with the 5-filter EFWmini. They used to show up as wheels ASI EFW 0 (7-slot) and ASI EFW 1 (5-slot). For both I have set up the filter names, and for the 7-slot wheel I also set up filter focus offsets and AF locks.

Obviously this worked flawless so far because I always plugged the compunent in the same way. But recently I managed to switch the two cables of the cameras (the FW are connected to the internal hubs of the cameras) when plugging them into my mount computer. After starting INDI, the 5-wheel was wheel 0, and the 7-wheel was 1. The really bad part however was that all settings were deleted and a default configuration was created, without my focus offsets etc.

Is there an easy way to prevent that from happening again? The standard way to give unique names to devices via udev doesn't work for ZWO units, as they are HID devices :(
Any tips?

Read More...

Hey Ron,

that's great to hear! And makes me wonder: Do you use a color camera?
I did have comparable issues (with star detection) when using a color camera as guider, and everything started working when switching to LUMA mode, or bin 2x2.....

And a short remark again to that different-stars issue: On first hand, seeing and defocus determine the point spread function for the image, and in theory this PSF is the same everywhere. So the shape (and thus things like FWHM etc.) are the same for all stars, and it doesn't really matter which of them you use.
In praxis, especially for short exposures, seeing will vary over the FOV, and averaging over many stars will give you a much better estimate of the seeing than a single star. The same is the case for the instrumental PSF, that can vary across the image: Collimation errors, as mentioned already, curvature of the focal plane (mainly for refractors) etc. Also there you usually want to get the best field-averaged focus. And again, the errors there do not depend on the star, only on position in FOV, and as long as your star ensemble is spread uniformly across the FOV it doesn't matter which ones are used....

Read More...

Well, the idea of HFR etc. is that it is normalized to max/total intensity, which takes care of different star intensities. Strong deviations there should only happen if stars saturate, and that should usually not happen for many of them.
Don't mess up star sizes with what you see on screen - those are basically 'cut' at a fixed absolute intensity, and therefore apparent star sizes do seem to vary a lot...

Other issues can be that the range you scan is too large, and you start seeing pupil shapes in the far-from-focus parts. Depending on your optics, that can largely irritate the detection algorithms.

My experience with linear is that you definitely want to start quite close to focus, and don't go too far out. To ensure that, I usually pre-focus the very first filter of the day manually (usually with video mode on a bright star), and then apply filter offsets at filter changes before running AF (I do that on any filter change, i.e., every 1-3 hours or so. Also refocus-on-temperature and/or regular refocus (time-based) might help.

The only thing that really upsets my focus curves is seeing. If that is bad, or - even worse - highly variable, you likely have to increase exposure time and/or average several measurements per focus setting.

My 2¢

Read More...

Peter Sütterlin replied to the topic 'NUC10 vs RPI4b/SSD' in the forum. 8 months ago

Interesting.  My PN40 is officially only speced for 19V, but I run it on 12V all the time, without issues.  After all there's nothing within such a computer that runs on 19V - that (most of the time) is only to guarantee a stable 12V when converted down.  So I'd just try it with 12V.  You might just need a strong enough PSU or large enough battery that doesn't drop below 12V, as an i7 might well need some power...
 

Read More...

Seems to work indeed. Thanks a lot - that was really irritating.

Read More...

Go to 'Scale & Position' and disable hinting ("Use Scale", "Use Position")
And/or try other "Option profiles" for the Stellarsolver

Read More...